Daniel, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following: 1) The one to test is at the very top line at the top of the page (not the daily folder). 2) The release names are irrelevant. 3) The folder time stamps aren't indicative of when the kernel actually was released upstream. 4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .
If testing on your main install would be inconvenient, one may: 1) Install Ubuntu to a different partition and then test this there. 2) Backup, or clone the primary install. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Also, you don't need to apport-collect further unless specifically requested to do so. Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results. Thank you for your understanding. ** Tags removed: blade ** Tags added: bios-outdated-2016.03.07 -- 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/1590072 Title: kernel 4.4.0-21.37-generic in 16.04 sees no disks on HP ProLiant BL465c Gen8 if IOMMU is enabled Status in linux package in Ubuntu: Incomplete Bug description: When trying to install 16.04 LTS on a BL465c Gen8, the default kernel 4.4.0-21.37-generic does not detect the disks with IOMMU enabled. Using the HP iLO Cli, shows that the server have some hardware error: enclosure68-a> show server status 4 Blade #4 Status: Power: On Current Wattage used: 343 Health: Failed Unit Identification LED: Blinking Virtual Fan: 100% Diagnostic Status: Internal Data OK Management Processor OK I/O Configuration OK Power OK Cooling OK Location OK Device Failure Failed Device Degraded OK VCM Configured Other iLO Network OK Mezzanine Card OK This device failure in the blade is OK after a reboot. Disabling IOMMU on BIOS and the 16.04 installation goes successfully. I tried to enable IOMMU after the installation and the problem appears. The disk is not detected and it can't boot normally. Ubuntu 14.04 LTS boots and run fine on these machines. dmesg ouput with IOMMU enabled. [ 82.295300] HP HPSA Driver (v 3.4.14-0) [ 82.295327] hpsa 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control [ 82.295350] hpsa 0000:03:00.0: MSI-X capable controller [ 82.295993] pps_core: LinuxPPS API ver. 1 registered [ 82.295996] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giome...@linux.it> [ 82.297857] PTP clock support registered [ 82.316730] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.712.30-0 (2014/02/10) [ 82.320096] AVX version of gcm_enc/dec engaged. [ 82.320100] AES CTR mode by8 optimization enabled [ 82.320501] ACPI: PCI Interrupt Link [I0C0] enabled at IRQ 36 [ 82.320614] bnx2x 0000:04:00.0: msix capability found [ 82.320755] bnx2x 0000:04:00.0: part number 0-0-0-0 [ 82.443473] ACPI: PCI Interrupt Link [I0C1] enabled at IRQ 37 [ 82.443510] bnx2x 0000:04:00.1: msix capability found [ 82.443615] bnx2x 0000:04:00.1: part number 0-0-0-0 [ 82.563309] ipmi_si IPI0001:00: Found new BMC (man_id: 0x00000b, prod_id: 0x2020, dev_id: 0x13) [ 82.563320] ipmi_si IPI0001:00: IPMI kcs interface initialized [ 82.566422] bnx2x 0000:04:00.0 eno1: renamed from eth0 [ 82.585454] bnx2x 0000:04:00.1 eno2: renamed from eth1 [ 207.105793] hpsa 0000:03:00.0: board not ready, timed out. dmesg with IOMMU disabled. [ 80.818467] HP HPSA Driver (v 3.4.14-0) [ 80.818493] hpsa 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control [ 80.818514] hpsa 0000:03:00.0: MSI-X capable controller [ 80.818878] hpsa 0000:03:00.0: Logical aborts not supported [ 80.818881] hpsa 0000:03:00.0: HP SSD Smart Path aborts not supported [ 80.819325] pps_core: LinuxPPS API ver. 1 registered [ 80.819328] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giome...@linux.it> [ 80.821272] PTP clock support registered [ 80.838135] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.712.30-0 (2014/02/10) [ 80.838402] bnx2x 0000:04:00.0: msix capability found [ 80.838535] bnx2x 0000:04:00.0: part number 0-0-0-0 [ 80.841536] AVX version of gcm_enc/dec engaged. [ 80.841541] AES CTR mode by8 optimization enabled [ 80.864399] scsi host4: hpsa [ 80.872507] hpsa 0000:03:00.0: scsi 4:3:0:0: added RAID HP P220i controller SSDSmartPathCap- En- Exp=1 [ 80.872513] hpsa 0000:03:00.0: scsi 4:0:0:0: masked Direct-Access ATA VK0240GDJXU PHYS DRV SSDSmartPathCap- En- Exp=0 [ 80.872517] hpsa 0000:03:00.0: scsi 4:0:1:0: masked Direct-Access ATA VK0240GDJXU PHYS DRV SSDSmartPathCap- En- Exp=0 [ 80.872521] hpsa 0000:03:00.0: scsi 4:1:0:0: added Direct-Access HP LOGICAL VOLUME RAID-1(+0) SSDSmartPathCap- En- Exp=1 [ 80.873094] scsi 4:0:0:0: RAID HP P220i 6.68 PQ: 0 ANSI: 5 [ 80.873416] scsi 4:1:0:0: Direct-Access HP LOGICAL VOLUME 6.68 PQ: 0 ANSI: 5 [ 80.873775] scsi 4:0:0:0: Attached scsi generic sg1 type 12 [ 80.874046] sd 4:1:0:0: Attached scsi generic sg2 type 0 [ 80.874081] sd 4:1:0:0: [sda] 468792000 512-byte logical blocks: (240 GB/224 GiB) [ 80.874308] sd 4:1:0:0: [sda] Write Protect is off [ 80.874312] sd 4:1:0:0: [sda] Mode Sense: 73 00 00 08 [ 80.874395] sd 4:1:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 80.875958] sd 4:1:0:0: [sda] Attached SCSI disk --- ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperVersion: 1.376 DistroRelease: Ubuntu 16.10 IwConfig: lo no wireless extensions. eno2 no wireless extensions. eno1 no wireless extensions. LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160607) MachineType: HP ProLiant BL465c Gen8 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware 1.158 RfKill: Tags: yakkety Uname: Linux 4.4.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/02/2014 dmi.bios.vendor: HP dmi.bios.version: A26 dmi.chassis.type: 28 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrA26:bd11/02/2014:svnHP:pnProLiantBL465cGen8:pvr:cvnHP:ct28:cvr: dmi.product.name: ProLiant BL465c Gen8 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
