kernel-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

Hmm, that's strange that they don't boot.  Can you also test the latest Trusty kernel from:
https://launchpad.net/ubuntu/+source/linux/3.11.0-12.19/+build/5088396

There are some hints on how to get further debug info from a boot
failure at:

https://wiki.ubuntu.com/DebuggingKernelBoot

As mentioned on the wiki, it would be great if you can attach a log file
which may have captured any messages you see. If you are unable to
capture a log file, a digital photo will work just as well. As a last
resort you can even copy messages down by hand.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1245938

Title:
  Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  We have a server (Dell R715) with two Intel x520 NIC's. If we run
  Ubuntu 12.04 on it, the NIC's works flawlessly (with stock kernel
  driver or with Intel compiled one), but if we upgrade release to
  12.10, 13.04 or 13.10, the NIC's stop working: either stock or Intel
  drivers fails with error:

  [  226.395766] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.18.7
  [  226.395770] Copyright (c) 1999-2013 Intel Corporation.
  [  226.395980] ixgbe: probe of 0000:22:00.0 failed with error -5
  [  226.396092] ixgbe: probe of 0000:22:00.1 failed with error -5
  [  226.396203] ixgbe: probe of 0000:23:00.0 failed with error -5
  [  226.396311] ixgbe: probe of 0000:23:00.1 failed with error -5

  I contacted Intel developers and they responded:

  "Hey Fernando,
  We (ixgbe) only returns EIO (error 5) for a couple of reasons.
   1) When we fail to io map (ioremap)
   2) If the eeprom checksum is incorrect.
   3) If the MAC address from the checksum is invalid

  Reasons 2 and 3 are related to the NIC's eeprom so if they worked with another system they should still be fine now.  If you really wanted to verify you could try out the NIC's on a known good system again to see if the eeprom somehow got corrupted.
  That pretty much leaves us with ioremap returning an error.  I'm not at all sure why your Ubuntu release would not like the way we are calling ioremap, but it might give you a place to start looking in Ubuntu changes.
  Thanks,
  -Don"

  If the server boot with kernel 3.2.0-55 (from grub menu) both NIC's
  works fine.

  Please let me know how can I help!

  Regards

  Fernando

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+subscriptions