igb i210 probe of pci device failed with error -2

Bug #1639810 reported by Chris J Arges
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Chris J Arges
Xenial
Fix Released
Medium
Unassigned
Yakkety
Fix Released
Medium
Unassigned

Bug Description

[Impact]

Intel I210 NIC may show:
'igb: probe of 0000:07:00.0 failed with error -2'
Upon boot after power has been completely disconnected.

I was able to bisect it down to commit 2a3cdead8b408351fa1e3079b220fa331480ffbc
Upon further investigation it was determined that firmware may not properly initialize I347AT4_PAGE_SELECT causing the probe of an igb i210 NIC to fail.

This also happens with the linux 4.9-rc4.

[Fix]

https://patchwork.ozlabs.org/patch/690464/
This patch adds an addition zeroing of this register during igb_get_phy_id to workaround this issue.

[Test Case]

Completely power down machine with intel igb 210 NIC. Power on and ensure igb device is properly probed and initialized.

Changed in linux (Ubuntu Xenial):
importance: Undecided → Medium
Changed in linux (Ubuntu Yakkety):
importance: Undecided → Medium
Changed in linux (Ubuntu Xenial):
status: New → Triaged
Changed in linux (Ubuntu Yakkety):
status: New → Triaged
tags: added: chris-arges
tags: added: is-back
tags: added: yay
tags: added: kernel-da-key
Revision history for this message
Chris J Arges (arges) wrote :

https://patchwork.ozlabs.org/patch/700615/

Note, since 2a3cdead8b408351fa1e3079b220fa331480ffbc is backported to xenial, this also affects Xenial.

Luis Henriques (henrix)
Changed in linux (Ubuntu Xenial):
status: Triaged → Fix Committed
Changed in linux (Ubuntu Yakkety):
status: Triaged → Fix Committed
Revision history for this message
John Donnelly (jpdonnelly) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-xenial
Revision history for this message
John Donnelly (jpdonnelly) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-yakkety
Revision history for this message
Chris J Arges (arges) wrote :

I have verified that indeed the i210 devices comes up as expected:
Before:
[ 4.479855] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
[ 4.479857] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 4.534131] igb 0000:02:00.0: added PHC on eth0
[ 4.534133] igb 0000:02:00.0: Intel(R) Gigabit Ethernet Network Connection
[ 4.534134] igb 0000:02:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 00:15:b2:a9:0a:f8
[ 4.534207] igb 0000:02:00.0: eth0: PBA No: 106300-000
[ 4.534208] igb 0000:02:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
[ 4.588119] igb 0000:02:00.1: added PHC on eth1
[ 4.588121] igb 0000:02:00.1: Intel(R) Gigabit Ethernet Network Connection
[ 4.588122] igb 0000:02:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 00:15:b2:a9:0a:f9
[ 4.588195] igb 0000:02:00.1: eth1: PBA No: 106300-000
[ 4.588196] igb 0000:02:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
[ 4.588530] igb: probe of 0000:07:00.0 failed with error -2

Using 4.4.0-62-generic:

[ 4.268189] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
[ 4.268191] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 4.321463] igb 0000:02:00.0: added PHC on eth0
[ 4.321465] igb 0000:02:00.0: Intel(R) Gigabit Ethernet Network Connection
[ 4.321466] igb 0000:02:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 00:15:b2:aa:1e:e6
[ 4.321539] igb 0000:02:00.0: eth0: PBA No: 106300-000
[ 4.321540] igb 0000:02:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
[ 4.376939] igb 0000:02:00.1: added PHC on eth1
[ 4.376940] igb 0000:02:00.1: Intel(R) Gigabit Ethernet Network Connection
[ 4.376942] igb 0000:02:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 00:15:b2:aa:1e:e7
[ 4.377015] igb 0000:02:00.1: eth1: PBA No: 106300-000
[ 4.377016] igb 0000:02:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
[ 4.403411] igb 0000:07:00.0: added PHC on eth2
[ 4.403413] igb 0000:07:00.0: Intel(R) Gigabit Ethernet Network Connection
[ 4.403415] igb 0000:07:00.0: eth2: (PCIe:2.5Gb/s:Width x1) 00:15:b2:aa:1e:e9
[ 4.403463] igb 0000:07:00.0: eth2: PBA No: 000300-000
[ 4.403464] igb 0000:07:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)

tags: added: verification-done-xenial
removed: verification-needed-xenial
Revision history for this message
Chris J Arges (arges) wrote :

# uname -r
4.8.0-36-generic
# dmesg | grep igb
[ 4.431586] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
[ 4.431586] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 4.484053] igb 0000:02:00.0: added PHC on eth0
[ 4.484054] igb 0000:02:00.0: Intel(R) Gigabit Ethernet Network Connection
[ 4.484056] igb 0000:02:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 00:15:b2:aa:1e:e6
[ 4.484130] igb 0000:02:00.0: eth0: PBA No: 106300-000
[ 4.484131] igb 0000:02:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
[ 4.535365] igb 0000:02:00.1: added PHC on eth1
[ 4.535366] igb 0000:02:00.1: Intel(R) Gigabit Ethernet Network Connection
[ 4.535368] igb 0000:02:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 00:15:b2:aa:1e:e7
[ 4.535440] igb 0000:02:00.1: eth1: PBA No: 106300-000
[ 4.535440] igb 0000:02:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
[ 4.566594] igb 0000:07:00.0: added PHC on eth2
[ 4.566595] igb 0000:07:00.0: Intel(R) Gigabit Ethernet Network Connection
[ 4.566596] igb 0000:07:00.0: eth2: (PCIe:2.5Gb/s:Width x1) 00:15:b2:aa:1e:e9
[ 4.566642] igb 0000:07:00.0: eth2: PBA No: 000300-000
[ 4.566643] igb 0000:07:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)
[ 15.307352] init: igb_uio_bind main process (2376) terminated with status 1

tags: added: verification-done-yakkety
removed: verification-needed-yakkety
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (10.8 KiB)

This bug was fixed in the package linux - 4.4.0-62.83

---------------
linux (4.4.0-62.83) xenial; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
    - LP: #1657430

  * Backport DP MST fixes to i915 (LP: #1657353)
    - SAUCE: i915_bpo: Fix DP link rate math
    - SAUCE: i915_bpo: Validate mode against max. link data rate for DP MST

  * Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue (LP: #1657281)
    - blk-mq: really fix plug list flushing for nomerge queues

linux (4.4.0-61.82) xenial; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
    - LP: #1656810

  * Xen MSI setup code incorrectly re-uses cached pirq (LP: #1656381)
    - SAUCE: xen: do not re-use pirq number cached in pci device msi msg data

  * nvme drive probe failure (LP: #1626894)
    - nvme: revert NVMe: only setup MSIX once

linux (4.4.0-60.81) xenial; urgency=low

  [ John Donnelly ]

  * Release Tracking Bug
    - LP: #1656084

  * Couldn't emulate instruction 0x7813427c (LP: #1634129)
    - KVM: PPC: Book3S PR: Fix illegal opcode emulation

  * perf: 24x7: Eliminate domain name suffix in event names (LP: #1560482)
    - powerpc/perf/hv-24x7: Fix usage with chip events.
    - powerpc/perf/hv-24x7: Display change in counter values
    - powerpc/perf/hv-24x7: Display domain indices in sysfs
    - powerpc/perf/24x7: Eliminate domain suffix in event names

  * i386 ftrace tests hang on ADT testing (LP: #1655040)
    - ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from using short jumps
      to it

  * VMX module autoloading if available (LP: #1651322)
    - powerpc: Add module autoloading based on CPU features
    - crypto: vmx - Convert to CPU feature based module autoloading

  * ACPI probe support for AD5592/3 configurable multi-channel converter
    (LP: #1654497)
    - SAUCE: iio: dac: ad5592r: Add ACPI support
    - SAUCE: iio: dac: ad5593r: Add ACPI support

  * Xenial update to v4.4.40 stable release (LP: #1654602)
    - btrfs: limit async_work allocation and worker func duration
    - Btrfs: fix tree search logic when replaying directory entry deletes
    - btrfs: store and load values of stripes_min/stripes_max in balance status
      item
    - Btrfs: fix qgroup rescan worker initialization
    - USB: serial: option: add support for Telit LE922A PIDs 0x1040, 0x1041
    - USB: serial: option: add dlink dwm-158
    - USB: serial: kl5kusb105: fix open error path
    - USB: cdc-acm: add device id for GW Instek AFG-125
    - usb: hub: Fix auto-remount of safely removed or ejected USB-3 devices
    - usb: gadget: f_uac2: fix error handling at afunc_bind
    - usb: gadget: composite: correctly initialize ep->maxpacket
    - USB: UHCI: report non-PME wakeup signalling for Intel hardware
    - ALSA: usb-audio: Add QuickCam Communicate Deluxe/S7500 to
      volume_control_quirks
    - ALSA: hiface: Fix M2Tech hiFace driver sampling rate change
    - ALSA: hda/ca0132 - Add quirk for Alienware 15 R2 2016
    - ALSA: hda - ignore the assoc and seq when comparing pin configurations
    - ALSA: hda - fix headset-mic problem on a Dell laptop
    - ALSA: hda - Gate the mic jack on HP Z1 Gen3 AiO
    - ALSA: hd...

Changed in linux (Ubuntu Xenial):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 4.8.0-37.39

---------------
linux (4.8.0-37.39) yakkety; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
    - LP: #1659381

  * Mouse cursor invisible or does not move (LP: #1646574)
    - drm/nouveau/disp/nv50-: split chid into chid.ctrl and chid.user
    - drm/nouveau/disp/nv50-: specify ctrl/user separately when constructing
      classes
    - drm/nouveau/disp/gp102: fix cursor/overlay immediate channel indices

 -- Benjamin M Romer <email address hidden> Wed, 25 Jan 2017 16:12:02 -0200

Changed in linux (Ubuntu Yakkety):
status: Fix Committed → Fix Released
Po-Hsu Lin (cypressyew)
Changed in linux (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.