https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_334/fi-bxt-dsi/dmesg9.log ------------[ cut here ]------------ <4>[ 223.784342] igb: Failed to read reg 0x5b50! <4>[ 223.784415] WARNING: CPU: 1 PID: 17 at drivers/net/ethernet/intel/igb/igb_main.c:756 igb_rd32+0x6e/0x80 [igb] <4>[ 223.784420] Modules linked in: mei_hdcp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic i915 x86_pkg_temp_thermal coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel lpc_ich btusb btrtl btbcm btintel bluetooth igb snd_hda_intel snd_hda_codec snd_hwdep ecdh_generic ecc snd_hda_core ptp pps_core snd_pcm mei_me mei prime_numbers i2c_hid pinctrl_broxton pinctrl_intel <4>[ 223.784471] CPU: 1 PID: 17 Comm: kworker/1:0 Tainted: G U 5.3.0-rc1-gef1bb6d271fa-drmtip_334+ #1 <4>[ 223.784475] Hardware name: Intel Corp. Broxton P/Apollolake RVP1A, BIOS APLKRVPA.X64.0150.B11.1608081044 08/08/2016 <4>[ 223.784489] Workqueue: events igb_watchdog_task [igb] <4>[ 223.784504] RIP: 0010:igb_rd32+0x6e/0x80 [igb] <4>[ 223.784510] Code: ff ff 89 f3 48 c7 42 08 00 00 00 00 48 c7 c6 a1 b5 28 c0 89 44 24 04 e8 35 70 60 c7 89 de 48 c7 c7 40 c2 28 c0 e8 a2 6d e4 c6 <0f> 0b 8b 44 24 04 eb a4 66 2e 0f 1f 84 00 00 00 00 00 41 55 41 54 <4>[ 223.784515] RSP: 0018:ffff8eb2400efd98 EFLAGS: 00010282 <4>[ 223.784521] RAX: 0000000000000000 RBX: 0000000000005b50 RCX: 0000000000000006 <4>[ 223.784526] RDX: 0000000000001ca2 RSI: ffff8be33b35d630 RDI: ffff8be33b35cdc0 <4>[ 223.784530] RBP: 0000000000000000 R08: ffff8be33b35d630 R09: 0000000000000000 <4>[ 223.784535] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000801 <4>[ 223.784539] R13: 0000000000000002 R14: 0000000000000013 R15: 0000000000000000 <4>[ 223.784544] FS: 0000000000000000(0000) GS:ffff8be33ba80000(0000) knlGS:0000000000000000 <4>[ 223.784549] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4>[ 223.784553] CR2: 00007f26ce8ec3dc CR3: 0000000177858000 CR4: 00000000003406e0 <4>[ 223.784558] Call Trace: <4>[ 223.784570] ? collect_expired_timers+0xa0/0xa0 <4>[ 223.784587] igb_get_hw_semaphore_i210+0x22/0x150 [igb] <4>[ 223.784605] igb_acquire_swfw_sync_i210+0x4f/0xc0 [igb] <4>[ 223.784624] igb_read_phy_reg_82580+0x1c/0x50 [igb] <4>[ 223.784641] igb_watchdog_task+0x6ac/0x7e0 [igb] <4>[ 223.784657] process_one_work+0x245/0x5f0 <4>[ 223.784676] worker_thread+0x37/0x380 <4>[ 223.784687] ? process_one_work+0x5f0/0x5f0 <4>[ 223.784693] kthread+0x119/0x130 <4>[ 223.784699] ? kthread_park+0xa0/0xa0 <4>[ 223.784711] ret_from_fork+0x3a/0x50 <4>[ 223.784738] irq event stamp: 135932 <4>[ 223.784745] hardirqs last enabled at (135931): [<ffffffff8712efb0>] vprintk_emit+0x300/0x320 <4>[ 223.784752] hardirqs last disabled at (135932): [<ffffffff8700199a>] trace_hardirqs_off_thunk+0x1a/0x20 <4>[ 223.784759] softirqs last enabled at (135888): [<ffffffff87c002eb>] __do_softirq+0x2eb/0x465 <4>[ 223.784765] softirqs last disabled at (135881): [<ffffffff870ba04e>] irq_exit+0xae/0xc0 <4>[ 223.784778] WARNING: CPU: 1 PID: 17 at drivers/net/ethernet/intel/igb/igb_main.c:756 igb_rd32+0x6e/0x80 [igb] <4>[ 223.784783] ---[ end trace 4782d295f48f679a ]--- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_334/fi-bxt-dsi/igt@runner@aborted.html
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * BXT: igt@runner@aborted - fail - igb: Failed to read reg 0x5b50! - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_334/fi-bxt-dsi/igt@runner@aborted.html
For a change, it's not e1000e related but another Intel netdev!
Somebody ping the igb maintainers.
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * fi-bxt-dsi: igt@gem_softpin@noreloc-s3 - dmesg-warn- igb: Failed to read reg 0x5b50! - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_341/fi-bxt-dsi/igt@gem_softpin@noreloc-s3.html
A CI Bug Log filter associated to this bug has been updated: {- fi-bxt-dsi: igt@gem_softpin@noreloc-s3 - dmesg-warn- igb: Failed to read reg 0x5b50! -} {+ fi-bxt-dsi: igt@gem_softpin@noreloc-s3|igt@gem_ctx_isolation@vecs0-s3 - dmesg-warn- igb: Failed to read reg 0x5b50! +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_348/fi-bxt-dsi/igt@gem_ctx_isolation@vecs0-s3.html
A CI Bug Log filter associated to this bug has been updated: {- BXT: igt@runner@aborted - fail - igb: Failed to read reg 0x5b50! -} {+ BXT: igt@runner@aborted - fail - igb: Failed to read reg 0x5b50! +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_348/fi-bxt-dsi/igt@runner@aborted.html
A CI Bug Log filter associated to this bug has been updated: {- fi-bxt-dsi: igt@gem_softpin@noreloc-s3|igt@gem_ctx_isolation@vecs0-s3 - dmesg-warn- igb: Failed to read reg 0x5b50! -} {+ fi-bxt-dsi: igt@gem_softpin@noreloc-s3|igt@gem_ctx_isolation@vecs0-s3|igt@i915_suspend@sysfs-reader - dmesg-warn- igb: Failed to read reg 0x5b50! +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_350/fi-bxt-dsi/igt@i915_suspend@sysfs-reader.html
A CI Bug Log filter associated to this bug has been updated: {- BXT: igt@runner@aborted - fail - igb: Failed to read reg 0x5b50! -} {+ BXT: igt@runner@aborted - fail - igb: Failed to read reg 0x5b50! +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_350/fi-bxt-dsi/igt@runner@aborted.html
(In reply to Chris Wilson from comment #3) > Somebody ping the igb maintainers. Contacted Jeff Kirsher regarding this issue.
Please run the attached sutinfo1g.sh script to provide us necessary information about s/w and h/w. Can you explain how we could reproduce the issue? Some use steps or bash script? Thank you
Created attachment 145178 [details] script to provide s/w & h/w configuration details to run it you need to export pf variable with the network interface name you have issue: # pf=eth1 ./sutinfo1g.sh
A CI Bug Log filter associated to this bug has been updated: {- fi-bxt-dsi: igt@gem_softpin@noreloc-s3|igt@gem_ctx_isolation@vecs0-s3|igt@i915_suspend@sysfs-reader - dmesg-warn- igb: Failed to read reg 0x5b50! -} {+ fi-bxt-dsi: igt@gem_softpin@noreloc-s3|igt@gem_ctx_isolation@.*-s3|igt@i915_suspend@sysfs-reader - dmesg-warn- igb: Failed to read reg 0x5b50! +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_352/fi-bxt-dsi/igt@gem_ctx_isolation@rcs0-s3.html
A CI Bug Log filter associated to this bug has been updated: {- BXT: igt@runner@aborted - fail - igb: Failed to read reg 0x5b50! -} {+ BXT: igt@runner@aborted - fail - igb: Failed to read reg 0x5b50! +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_352/fi-bxt-dsi/igt@runner@aborted.html
Thanks for informing you dear friend https://b-zr.com
So the 0x5B50 register address for hardware supported by the igb driver is the Software Semaphore bit, that needs to be acquired to access the firmware or NVM on the NIC. It appears that we are not able to access this register, which either means your NVM is bad OR you have a hardware issue. You can try updating the NVM image with the latest NVM image available for your NIC on Intel's download center and if that does not resolve the issue, then you have a hardware issue with your NIC and it should be replaced.
A CI Bug Log filter associated to this bug has been updated: {- fi-bxt-dsi: igt@gem_softpin@noreloc-s3|igt@gem_ctx_isolation@.*-s3|igt@i915_suspend@sysfs-reader - dmesg-warn- igb: Failed to read reg 0x5b50! -} {+ fi-bxt-dsi KBL: igt@gem_* - dmesg-warn- igb: Failed to read reg 0x5b50! +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_360/fi-kbl-8809g/igt@gem_workarounds@suspend-resume-context.html
A CI Bug Log filter associated to this bug has been updated: {- BXT: igt@runner@aborted - fail - igb: Failed to read reg 0x5b50! -} {+ BXT: igt@runner@aborted - fail - igb: Failed to read reg 0x5b50! +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_368/fi-bxt-dsi/igt@runner@aborted.html
It was great http://hamsafarbar.com/ https://www.washtehran.ir/ https://www.ghasretalaie.com/ https://adinmoket.ir/ http://pakhshmoket.ir/
A CI Bug Log filter associated to this bug has been updated: {- BXT: igt@runner@aborted - fail - igb: Failed to read reg 0x5b50! -} {+ BXT: igt@runner@aborted - fail - igb: Failed to read reg 0x5b50! +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_378/fi-bxt-dsi/igt@runner@aborted.html
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * BXT: igt@kms_cursor_crc@pipe-b-cursor-suspend - dmesg-warn - igb 0000:01:00.0 enp1s0: Reset adapter - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_381/fi-bxt-dsi/igt@kms_cursor_crc@pipe-b-cursor-suspend.html
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * BXT: igt@runner@aborted - fail - Previous test: kms_cursor_crc (pipe-b-cursor-suspend) - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_381/fi-bxt-dsi/igt@runner@aborted.html
https://chikav.ir/%d9%86%d9%82%d8%af-%d9%88-%d8%a8%d8%b1%d8%b1%d8%b3%db%8c-%d8%a7%d9%be%d9%84%db%8c%da%a9%db%8c%d8%b4%d9%86/
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.