This bug was fixed in the package linux - 4.8.0-19.21
---------------
linux (4.8.0-19.21) yakkety; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1629057
* 4.8.0 kernels do not complete boot process on VM (LP: #1627198)
- [Config] CONFIG_HARDENED_USERCOPY_PAGESPAN=n
* mount-image-callback cannot mount partitioned disk image (LP: #1628336)
- SAUCE: nbd: Only delay uevent until connected
* Support snaps inside of lxd containers (LP: #1611078)
- apparmor: add interface to be able to grab loaded policy
- securityfs: update interface to allow inode_ops, and setup from vfs fns
- apparmor: refactor aa_prepare_ns into prepare_ns and create_ns routines
- apparmor: add __aa_find_ns fn
- apparmor: add mkdir/rmdir interface to manage policy namespaces
- apparmor: fix oops in pivot_root mediation
- apparmor: fix warning that fn build_pivotroot discards const
- apparmor: add interface to advertise status of current task stacking
- apparmor: update policy permissions to consider ns being viewed/managed
- apparmor: add per ns policy management interface
- apparmor: bump domain stacking version to 1.2
* linux-image-extra-4.8.0-17-generic does not provide many sound card modules
(LP: #1628523)
- [Config] CONFIG_ZONE_DMA=y for generic
* Yakkety - disable ARCH_ZX (LP: #1628503)
- [Config] armhf: disable ARCH_ZX
* Enable switchdev config parameter for Yakkety (LP: #1628241)
- [Config] CONFIG_NET_SWITCHDEV=y for amd64/arm64
* Ubuntu 16.10 kernel v4.8: Installation failing on Habanero with Shiner card
(LP: #1628009)
- firmware: Update bnx2x to 7.13.1.0
* vNIC driver missing in 4.8 kernel package (LP: #1628187)
- [Config] Enable CONFIG_IBMVNIC=m
* Yakkety - armhf: MFD_TPS65217 and REGULATOR_TPS65217 are boot essential
(LP: #1628112)
- [Config] armhf: MFD_TPS65217=y && REGULATOR_TPS65217=y
* Miscellaneous Ubuntu changes
- Rebase to v4.8-rc8
- [Config] skip Ubuntu-4.8.0-18.20
- [Config] missing modules in armhf/s390x
* Miscellaneous Ubuntu changes
- rebase to v4.8-rc8
-- Leann Ogasawara <[email protected]> Sun, 25 Sep 2016
12:13:35 -0700
** Changed in: linux (Ubuntu Yakkety)
Status: Fix Committed => Fix Released
--
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/1628009
Title:
Ubuntu 16.10 kernel v4.8: Installation failing on Habanero with Shiner
card
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Yakkety:
Fix Released
Bug description:
Problem Description
====================================
Ubuntu 16.10 installer fails to configure network during installation. We are
using Shiner adapter with bnx2x driver. looks like ubuntu installer does not
have the firmware for it. Below is what I see in syslog:
/var/log # cat syslog | grep -i bnx2x
Sep 27 05:45:01 kernel: [ 53.610983] bnx2x: QLogic 5771x/578xx
10/20-Gigabit Ethernet Driver bnx2x 1.712.30-0 (2014/02/10)
Sep 27 05:45:01 kernel: [ 53.611167] bnx2x 0001:0c:00.0: msix capability
found
Sep 27 05:45:01 kernel: [ 53.628231] bnx2x 0001:0c:00.0: Using 64-bit DMA
iommu bypass
Sep 27 05:45:01 kernel: [ 53.628273] bnx2x 0001:0c:00.0: part number 0-0-0-0
Sep 27 05:45:01 kernel: [ 60.817161] bnx2x 0001:0c:00.1: msix capability
found
Sep 27 05:45:01 kernel: [ 60.835940] bnx2x 0001:0c:00.1: Using 64-bit DMA
iommu bypass
Sep 27 05:45:01 kernel: [ 60.835980] bnx2x 0001:0c:00.1: part number 0-0-0-0
Sep 27 05:45:01 kernel: [ 62.417124] bnx2x 0001:0c:00.2: msix capability
found
Sep 27 05:45:01 kernel: [ 62.435935] bnx2x 0001:0c:00.2: Using 64-bit DMA
iommu bypass
Sep 27 05:45:01 kernel: [ 62.435974] bnx2x 0001:0c:00.2: part number 0-0-0-0
Sep 27 05:45:01 kernel: [ 62.627147] bnx2x 0001:0c:00.3: msix capability
found
Sep 27 05:45:01 kernel: [ 62.643972] bnx2x 0001:0c:00.3: Using 64-bit DMA
iommu bypass
Sep 27 05:45:01 kernel: [ 62.644024] bnx2x 0001:0c:00.3: part number 0-0-0-0
Sep 27 05:45:01 kernel: [ 62.798136] bnx2x 0001:0c:00.0 enP1p12s0f0:
renamed from eth0
Sep 27 05:45:01 kernel: [ 62.976102] bnx2x 0001:0c:00.1 enP1p12s0f1:
renamed from eth1
Sep 27 05:45:01 kernel: [ 63.139992] bnx2x 0001:0c:00.2 enP1p12s0f2:
renamed from eth2
Sep 27 05:45:01 kernel: [ 63.279984] bnx2x 0001:0c:00.3 enP1p12s0f3:
renamed from eth3
Sep 27 05:46:03 kernel: [ 127.619915] bnx2x 0001:0c:00.0: Direct firmware
load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
Sep 27 05:46:03 kernel: [ 127.619917] bnx2x:
[bnx2x_init_firmware:13427(enP1p12s0f0)]Can't load firmware file
bnx2x/bnx2x-e2-7.13.1.0.fw
Sep 27 05:46:03 kernel: [ 127.619918] bnx2x:
[bnx2x_func_hw_init:5785(enP1p12s0f0)]Error loading firmware
Sep 27 05:46:03 kernel: [ 127.619921] bnx2x:
[bnx2x_nic_load:2727(enP1p12s0f0)]HW init failed, aborting
Sep 27 05:46:03 kernel: [ 128.051899] bnx2x 0001:0c:00.1: Direct firmware
load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
Sep 27 05:46:03 kernel: [ 128.051901] bnx2x:
[bnx2x_init_firmware:13427(enP1p12s0f1)]Can't load firmware file
bnx2x/bnx2x-e2-7.13.1.0.fw
Sep 27 05:46:03 kernel: [ 128.051902] bnx2x:
[bnx2x_func_hw_init:5785(enP1p12s0f1)]Error loading firmware
Sep 27 05:46:03 kernel: [ 128.051904] bnx2x:
[bnx2x_nic_load:2727(enP1p12s0f1)]HW init failed, aborting
Sep 27 05:46:03 kernel: [ 128.155912] bnx2x 0001:0c:00.2: Direct firmware
load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
Sep 27 05:46:03 kernel: [ 128.155915] bnx2x:
[bnx2x_init_firmware:13427(enP1p12s0f2)]Can't load firmware file
bnx2x/bnx2x-e2-7.13.1.0.fw
Sep 27 05:46:03 kernel: [ 128.155916] bnx2x:
[bnx2x_func_hw_init:5785(enP1p12s0f2)]Error loading firmware
Sep 27 05:46:03 kernel: [ 128.155919] bnx2x:
[bnx2x_nic_load:2727(enP1p12s0f2)]HW init failed, aborting
Sep 27 05:46:03 kernel: [ 128.279895] bnx2x 0001:0c:00.3: Direct firmware
load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
Sep 27 05:46:03 kernel: [ 128.279898] bnx2x:
[bnx2x_init_firmware:13427(enP1p12s0f3)]Can't load firmware file
bnx2x/bnx2x-e2-7.13.1.0.fw
Sep 27 05:46:03 kernel: [ 128.279899] bnx2x:
[bnx2x_func_hw_init:5785(enP1p12s0f3)]Error loading firmware
Sep 27 05:46:03 kernel: [ 128.279902] bnx2x:
[bnx2x_nic_load:2727(enP1p12s0f3)]HW init failed, aborting
Sep 27 05:46:11 kernel: [ 135.779921] bnx2x 0001:0c:00.2: Direct firmware
load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
Sep 27 05:46:11 kernel: [ 135.779924] bnx2x:
[bnx2x_init_firmware:13427(enP1p12s0f2)]Can't load firmware file
bnx2x/bnx2x-e2-7.13.1.0.fw
Sep 27 05:46:11 kernel: [ 135.779925] bnx2x:
[bnx2x_func_hw_init:5785(enP1p12s0f2)]Error loading firmware
Sep 27 05:46:11 kernel: [ 135.779928] bnx2x:
[bnx2x_nic_load:2727(enP1p12s0f2)]HW init failed, aborting
This is blocking netboot installation of Ubuntu 16.10. This had worked when I
tried installation when Ubuntu 16.10 had 4.4 kernel. This is regression issue
---uname output---
Linux pkvmhab008 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016
ppc64le GNU/Linux
Machine Type = 8348-21C
---boot type---
Network boot
---bootloader---
grub
---Kernel cmdline used to launch install---
cd /tmp
wget
http://ports.ubuntu.com/ubuntu-ports/dists/yakkety/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
wget
http://ports.ubuntu.com/ubuntu-ports/dists/yakkety/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
kexec -l /tmp/vmlinux -i /tmp/initrd.gz -c
---Bootloader protocol---
http
---Install repository type---
Internet repository
---Install repository Location---
http://ports.ubuntu.com/ubuntu-ports/dists/yakkety/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628009/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
