kernel-packages team mailing list archive

[Rafael David Tinoco <rafael.tinoco@xxxxxxxxxxxxx>]

** Changed in: linux (Ubuntu)
     Assignee: Rafael David Tinoco (inaddy) => (unassigned)

-- 
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/1454286

Title:
  BNX2X firmware an hang on Trusty (3.13) and Utopic (3.16).

Status in linux package in Ubuntu:
  In Progress

Bug description:
  It was brought to my attention that BNX2X FIRMWARE is causing HW hangs
  on kernels 3.13 and 3.16 (until next power-cycle):

  Messages like this one:

  """
  Mar 30 13:42:05 host kernel: [3986360.755781] device em3 left promiscuous mode
  Mar 30 13:42:05 host kernel: [3986360.755849] br1: port 1(em3) entered disabled state
  Mar 30 13:42:05 host kernel: [3986360.756305] IPv6: ADDRCONF(NETDEV_UP): em3: link is not ready
  Mar 30 13:42:08 host kernel: [3986363.354376] device em3 entered promiscuous mode
  Mar 30 13:42:08 host kernel: [3986363.376093] bnx2x: [bnx2x_open:11791(em3)]Recovery flow hasn't been properly completed yet. Try again later.
  Mar 30 13:42:08 host kernel: [3986363.376093] If you still see this message after a few retries then power cycle is required.
  Mar 30 13:42:08 host kernel: [3986363.420113] bnx2x: [bnx2x_open:11791(em3)]Recovery flow hasn't been properly completed yet. Try again later.
  Mar 30 13:42:08 host kernel: [3986363.420113] If you still see this message after a few retries then power cycle is required.
  Mar 30 13:42:08 host kernel: [3986363.443840] IPv6: ADDRCONF(NETDEV_UP): br1: link is not ready
  """

  Are likely to be given in syslog whenever this happens.

  WORKAROUND: After providing the user a "linux-lts-vivid" and an
  updated linux-firmware package
  (https://launchpad.net/~inaddy/+archive/ubuntu/sf00080928/) the issue
  was fixed after package installation and power-cycle -> Power cycle is
  needed since previous firmware hangs HW until it is shutdown.

  My comments:

  """
  Actually after reading the Changelog for FW 7.10.51 (specifically the part "Chip may stall in very rare cases under heavy traffic with FW GRO enabled.") I think we might need to upgrade not only the FIRMWARE but also the DRIVER. 

  commit 626041248d3fb5b2fca5c9af172f00fa3bb6dcfe 
  Author: Yuval Mintz <Yuval.Mintz@xxxxxxxxxx> 
  Date: Sun Aug 17 16:47:46 2014 +0300 

  bnx2x: Update driver version to 1.710.5

  commit e42780b66aab88d3a82b6087bcd6095b90eecde7 
  Author: Dmitry Kravkov <Dmitry.Kravkov@xxxxxxxxxx> 
  Date: Sun Aug 17 16:47:43 2014 +0300 

  bnx2x: Utilize FW 7.10.51

  Observations:

  inaddy@alien:~/Bugs/customer/sf00080928/sources/trusty/linux-firmware-1.127.11$ find . | grep bnx2x 
  ./bnx2x 
  ./bnx2x/bnx2x-e1h-7.8.19.0.fw 
  ./bnx2x/bnx2x-e1-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1-7.8.19.0.fw 
  ./bnx2x/bnx2x-e2-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1h-7.8.17.0.fw 
  ./bnx2x/bnx2x-e2-7.8.19.0.fw 

  inaddy@alien:~/Bugs/customer/sf00080928/sources/utopic/linux-firmware-1.138.1$ find . | grep bnx2x 
  ./bnx2x 
  ./bnx2x/bnx2x-e1h-7.8.19.0.fw 
  ./bnx2x/bnx2x-e1-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1-7.8.19.0.fw 
  ./bnx2x/bnx2x-e2-7.10.51.0.fw 
  ./bnx2x/bnx2x-e1h-7.10.51.0.fw 
  ./bnx2x/bnx2x-e2-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1h-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1-7.10.51.0.fw 
  ./bnx2x/bnx2x-e2-7.8.19.0.fw 

  Firmware 7.10.51 is already present in Utopic but the commit to support it is only in 3.18.  It might be feasible to backport it to 3.16 (and use HWE) but not sure about 3.13 (to be resolved if this new firmware/driver fixes the issue).
  """

  I'll provide more comments right after my backport attempt (of this
  new version) is made.

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