Bug 111223

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/