[Kernel-packages] [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1582858 Title: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled Status in linux package in Ubuntu: Expired Bug description: On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I know, not supported). After reboot, the new kernel was loaded by GRUB, but failed to find the disks installed in the system (setup working for almost 2 years, standard HP setup with the SATA controller in AHCI mode and AHCI enabled during BIOS). It then dropped to a shell in initramfs, after hundreds (thousands?) of identical errors: [...] AMD-Vi: Event Logged [IO_PAGE_FAULT] device=xxx adress=yyy flags=0x... and the final error messages: ata3: softreset failed (1st FIS failed) ata4: softreset failed (1st FIS failed) ata3: limiting SATA link speed to 1.5 Gbps ata3: softreset failed (1st FIS failed) ata4: limiting SATA link speed to 1.5 Gbps ata4: softreset failed (1st FIS failed) ata3: reset failed, giving up ata4: reset failed, giving up The system disks are on ata1 and ata2, though. I tried booting the system from different other 16.04 boot media (ubuntu-16.04-server-amd64.iso, ubuntu-16.04-desktop-amd64.iso) into a rescue system. I also got the [...] AMD-Vi: Event Logged ... messages. When the rescue shell was running, the system disks were also not detected, the installer I started as an experiment only offered the (USB disk) boot medium itself as installation target. The desktop installer and kernel then crashed with error messages about squashfs (sorry, didn't record those). Without any change, the same system boots without issues from a 14.04 boot image, all disks present. Also, the 16.04 system boots fine if the old 3.13.0-86 kernel is selected in the GRUB menu. After some fiddling around, I turned off the IOMMU in the server's BIOS (under PCiExpress) - and all went back to normal, without any change on the installed system. Kernel 4.4.0-22-generic now boots just fine from the LVM-Root. So this is WORKSFORME now, but maybe somebody should look into it. I do believe that Proliants are quite common out there. If needed, I'll provide more info if possible - but currently I wouldn't know what. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 17 18:50 seq crw-rw 1 root audio 116, 33 May 17 18:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=d46c7c15-9d36-4d87-930d-e43d447e8855 InstallationDate: Installed on 2012-12-22 (1244 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL165 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/vg0-root ro net.ifnames=0 rootfstype=ext4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2014-05-25 (725 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/27/2012 dmi.bios.vendor: HP dmi.bios.version: O37 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO37:bd07/27/2012:svnHP:pnProLiantDL165G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL165 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582858/+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
[Kernel-packages] [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
xormar, the release names are irrelevant for the purposes of testing. Regarding the server being in a datacenter, would you have access to its iLO interface? -- 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/1582858 Title: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled Status in linux package in Ubuntu: Incomplete Bug description: On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I know, not supported). After reboot, the new kernel was loaded by GRUB, but failed to find the disks installed in the system (setup working for almost 2 years, standard HP setup with the SATA controller in AHCI mode and AHCI enabled during BIOS). It then dropped to a shell in initramfs, after hundreds (thousands?) of identical errors: [...] AMD-Vi: Event Logged [IO_PAGE_FAULT] device=xxx adress=yyy flags=0x... and the final error messages: ata3: softreset failed (1st FIS failed) ata4: softreset failed (1st FIS failed) ata3: limiting SATA link speed to 1.5 Gbps ata3: softreset failed (1st FIS failed) ata4: limiting SATA link speed to 1.5 Gbps ata4: softreset failed (1st FIS failed) ata3: reset failed, giving up ata4: reset failed, giving up The system disks are on ata1 and ata2, though. I tried booting the system from different other 16.04 boot media (ubuntu-16.04-server-amd64.iso, ubuntu-16.04-desktop-amd64.iso) into a rescue system. I also got the [...] AMD-Vi: Event Logged ... messages. When the rescue shell was running, the system disks were also not detected, the installer I started as an experiment only offered the (USB disk) boot medium itself as installation target. The desktop installer and kernel then crashed with error messages about squashfs (sorry, didn't record those). Without any change, the same system boots without issues from a 14.04 boot image, all disks present. Also, the 16.04 system boots fine if the old 3.13.0-86 kernel is selected in the GRUB menu. After some fiddling around, I turned off the IOMMU in the server's BIOS (under PCiExpress) - and all went back to normal, without any change on the installed system. Kernel 4.4.0-22-generic now boots just fine from the LVM-Root. So this is WORKSFORME now, but maybe somebody should look into it. I do believe that Proliants are quite common out there. If needed, I'll provide more info if possible - but currently I wouldn't know what. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 17 18:50 seq crw-rw 1 root audio 116, 33 May 17 18:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=d46c7c15-9d36-4d87-930d-e43d447e8855 InstallationDate: Installed on 2012-12-22 (1244 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL165 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/vg0-root ro net.ifnames=0 rootfstype=ext4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2014-05-25 (725 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/27/2012 dmi.bios.vendor: HP dmi.bios.version: O37 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO37:bd07/27/2012:svnHP:pnProLiantDL165G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL165 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582858/+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
[Kernel-packages] [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
@penalvch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582858/comments/19 Which of the upstream kernels at http://kernel.ubuntu.com/~kernel- ppa/mainline/?C=N;O=D should I test to find the last bad/first good one? There is no v4.4.N-xenial kernel, so I don't really know where to start and what to test. There are almost 40 kernels between v4.4-wily and v4.6-yakkety ... Then there's the problem that the server is sitting in a data center and I have to be on site to en-/disable the iommu on each boot. This also makes the bisecting very tedious, so I have no idea when I will find the time to do it. One more question: To setup the build environment, the requird packages are all installed by apt-get build-dep linux-image-$(uname -r), or do I need anything else? -- 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/1582858 Title: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled Status in linux package in Ubuntu: Incomplete Bug description: On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I know, not supported). After reboot, the new kernel was loaded by GRUB, but failed to find the disks installed in the system (setup working for almost 2 years, standard HP setup with the SATA controller in AHCI mode and AHCI enabled during BIOS). It then dropped to a shell in initramfs, after hundreds (thousands?) of identical errors: [...] AMD-Vi: Event Logged [IO_PAGE_FAULT] device=xxx adress=yyy flags=0x... and the final error messages: ata3: softreset failed (1st FIS failed) ata4: softreset failed (1st FIS failed) ata3: limiting SATA link speed to 1.5 Gbps ata3: softreset failed (1st FIS failed) ata4: limiting SATA link speed to 1.5 Gbps ata4: softreset failed (1st FIS failed) ata3: reset failed, giving up ata4: reset failed, giving up The system disks are on ata1 and ata2, though. I tried booting the system from different other 16.04 boot media (ubuntu-16.04-server-amd64.iso, ubuntu-16.04-desktop-amd64.iso) into a rescue system. I also got the [...] AMD-Vi: Event Logged ... messages. When the rescue shell was running, the system disks were also not detected, the installer I started as an experiment only offered the (USB disk) boot medium itself as installation target. The desktop installer and kernel then crashed with error messages about squashfs (sorry, didn't record those). Without any change, the same system boots without issues from a 14.04 boot image, all disks present. Also, the 16.04 system boots fine if the old 3.13.0-86 kernel is selected in the GRUB menu. After some fiddling around, I turned off the IOMMU in the server's BIOS (under PCiExpress) - and all went back to normal, without any change on the installed system. Kernel 4.4.0-22-generic now boots just fine from the LVM-Root. So this is WORKSFORME now, but maybe somebody should look into it. I do believe that Proliants are quite common out there. If needed, I'll provide more info if possible - but currently I wouldn't know what. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 17 18:50 seq crw-rw 1 root audio 116, 33 May 17 18:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=d46c7c15-9d36-4d87-930d-e43d447e8855 InstallationDate: Installed on 2012-12-22 (1244 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL165 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/vg0-root ro net.ifnames=0 rootfstype=ext4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2014-05-25 (725 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/27/2012 dmi.bios.vendor: HP dmi.bios.version: O37 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO37:bd07/27/2012:svnHP:pnProLiantDL165G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL165 G7 dmi.sys.vendor: HP To manage
[Kernel-packages] [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
Daniel, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs. -- 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/1582858 Title: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled Status in linux package in Ubuntu: Incomplete Bug description: On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I know, not supported). After reboot, the new kernel was loaded by GRUB, but failed to find the disks installed in the system (setup working for almost 2 years, standard HP setup with the SATA controller in AHCI mode and AHCI enabled during BIOS). It then dropped to a shell in initramfs, after hundreds (thousands?) of identical errors: [...] AMD-Vi: Event Logged [IO_PAGE_FAULT] device=xxx adress=yyy flags=0x... and the final error messages: ata3: softreset failed (1st FIS failed) ata4: softreset failed (1st FIS failed) ata3: limiting SATA link speed to 1.5 Gbps ata3: softreset failed (1st FIS failed) ata4: limiting SATA link speed to 1.5 Gbps ata4: softreset failed (1st FIS failed) ata3: reset failed, giving up ata4: reset failed, giving up The system disks are on ata1 and ata2, though. I tried booting the system from different other 16.04 boot media (ubuntu-16.04-server-amd64.iso, ubuntu-16.04-desktop-amd64.iso) into a rescue system. I also got the [...] AMD-Vi: Event Logged ... messages. When the rescue shell was running, the system disks were also not detected, the installer I started as an experiment only offered the (USB disk) boot medium itself as installation target. The desktop installer and kernel then crashed with error messages about squashfs (sorry, didn't record those). Without any change, the same system boots without issues from a 14.04 boot image, all disks present. Also, the 16.04 system boots fine if the old 3.13.0-86 kernel is selected in the GRUB menu. After some fiddling around, I turned off the IOMMU in the server's BIOS (under PCiExpress) - and all went back to normal, without any change on the installed system. Kernel 4.4.0-22-generic now boots just fine from the LVM-Root. So this is WORKSFORME now, but maybe somebody should look into it. I do believe that Proliants are quite common out there. If needed, I'll provide more info if possible - but currently I wouldn't know what. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 17 18:50 seq crw-rw 1 root audio 116, 33 May 17 18:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=d46c7c15-9d36-4d87-930d-e43d447e8855 InstallationDate: Installed on 2012-12-22 (1244 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL165 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/vg0-root ro net.ifnames=0 rootfstype=ext4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2014-05-25 (725 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/27/2012 dmi.bios.vendor: HP dmi.bios.version: O37 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO37:bd07/27/2012:svnHP:pnProLiantDL165G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL165 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582858/+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
[Kernel-packages] [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
I have the same problem trying to install 16.04 server on many BL465c Gen8. Disabling IOMMU on BIOS it seems to fix the issue. -- 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/1582858 Title: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled Status in linux package in Ubuntu: Incomplete Bug description: On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I know, not supported). After reboot, the new kernel was loaded by GRUB, but failed to find the disks installed in the system (setup working for almost 2 years, standard HP setup with the SATA controller in AHCI mode and AHCI enabled during BIOS). It then dropped to a shell in initramfs, after hundreds (thousands?) of identical errors: [...] AMD-Vi: Event Logged [IO_PAGE_FAULT] device=xxx adress=yyy flags=0x... and the final error messages: ata3: softreset failed (1st FIS failed) ata4: softreset failed (1st FIS failed) ata3: limiting SATA link speed to 1.5 Gbps ata3: softreset failed (1st FIS failed) ata4: limiting SATA link speed to 1.5 Gbps ata4: softreset failed (1st FIS failed) ata3: reset failed, giving up ata4: reset failed, giving up The system disks are on ata1 and ata2, though. I tried booting the system from different other 16.04 boot media (ubuntu-16.04-server-amd64.iso, ubuntu-16.04-desktop-amd64.iso) into a rescue system. I also got the [...] AMD-Vi: Event Logged ... messages. When the rescue shell was running, the system disks were also not detected, the installer I started as an experiment only offered the (USB disk) boot medium itself as installation target. The desktop installer and kernel then crashed with error messages about squashfs (sorry, didn't record those). Without any change, the same system boots without issues from a 14.04 boot image, all disks present. Also, the 16.04 system boots fine if the old 3.13.0-86 kernel is selected in the GRUB menu. After some fiddling around, I turned off the IOMMU in the server's BIOS (under PCiExpress) - and all went back to normal, without any change on the installed system. Kernel 4.4.0-22-generic now boots just fine from the LVM-Root. So this is WORKSFORME now, but maybe somebody should look into it. I do believe that Proliants are quite common out there. If needed, I'll provide more info if possible - but currently I wouldn't know what. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 17 18:50 seq crw-rw 1 root audio 116, 33 May 17 18:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=d46c7c15-9d36-4d87-930d-e43d447e8855 InstallationDate: Installed on 2012-12-22 (1244 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL165 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/vg0-root ro net.ifnames=0 rootfstype=ext4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2014-05-25 (725 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/27/2012 dmi.bios.vendor: HP dmi.bios.version: O37 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO37:bd07/27/2012:svnHP:pnProLiantDL165G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL165 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582858/+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
[Kernel-packages] [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
xormar, the next step is to fully reverse commit bisect from kernel 4.4 to 4.6 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ? Please note, finding adjacent kernel versions is not fully commit bisecting. After the fix commit (not kernel version) has been identified, then please mark this report Status Confirmed. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Tags added: kernel-fixed-upstream-4.6 needs-reverse-bisect ** Tags added: regression-release ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1582858 Title: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled Status in linux package in Ubuntu: Incomplete Bug description: On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I know, not supported). After reboot, the new kernel was loaded by GRUB, but failed to find the disks installed in the system (setup working for almost 2 years, standard HP setup with the SATA controller in AHCI mode and AHCI enabled during BIOS). It then dropped to a shell in initramfs, after hundreds (thousands?) of identical errors: [...] AMD-Vi: Event Logged [IO_PAGE_FAULT] device=xxx adress=yyy flags=0x... and the final error messages: ata3: softreset failed (1st FIS failed) ata4: softreset failed (1st FIS failed) ata3: limiting SATA link speed to 1.5 Gbps ata3: softreset failed (1st FIS failed) ata4: limiting SATA link speed to 1.5 Gbps ata4: softreset failed (1st FIS failed) ata3: reset failed, giving up ata4: reset failed, giving up The system disks are on ata1 and ata2, though. I tried booting the system from different other 16.04 boot media (ubuntu-16.04-server-amd64.iso, ubuntu-16.04-desktop-amd64.iso) into a rescue system. I also got the [...] AMD-Vi: Event Logged ... messages. When the rescue shell was running, the system disks were also not detected, the installer I started as an experiment only offered the (USB disk) boot medium itself as installation target. The desktop installer and kernel then crashed with error messages about squashfs (sorry, didn't record those). Without any change, the same system boots without issues from a 14.04 boot image, all disks present. Also, the 16.04 system boots fine if the old 3.13.0-86 kernel is selected in the GRUB menu. After some fiddling around, I turned off the IOMMU in the server's BIOS (under PCiExpress) - and all went back to normal, without any change on the installed system. Kernel 4.4.0-22-generic now boots just fine from the LVM-Root. So this is WORKSFORME now, but maybe somebody should look into it. I do believe that Proliants are quite common out there. If needed, I'll provide more info if possible - but currently I wouldn't know what. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 17 18:50 seq crw-rw 1 root audio 116, 33 May 17 18:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=d46c7c15-9d36-4d87-930d-e43d447e8855 InstallationDate: Installed on 2012-12-22 (1244 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL165 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/vg0-root ro net.ifnames=0 rootfstype=ext4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2014-05-25 (725 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/27/2012 dmi.bios.vendor: HP dmi.bios.version: O37 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO37:bd07/27/2012:svnHP:pnProLiantDL165G7:pvr:cvnHP:ct23:cvr:
[Kernel-packages] [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
** Attachment added: "dmesg with iommu disabled" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582858/+attachment/4667057/+files/4.6.0.dmesg.txt ** Tags added: kernel-fixed-upstream -- 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/1582858 Title: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled Status in linux package in Ubuntu: Confirmed Bug description: On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I know, not supported). After reboot, the new kernel was loaded by GRUB, but failed to find the disks installed in the system (setup working for almost 2 years, standard HP setup with the SATA controller in AHCI mode and AHCI enabled during BIOS). It then dropped to a shell in initramfs, after hundreds (thousands?) of identical errors: [...] AMD-Vi: Event Logged [IO_PAGE_FAULT] device=xxx adress=yyy flags=0x... and the final error messages: ata3: softreset failed (1st FIS failed) ata4: softreset failed (1st FIS failed) ata3: limiting SATA link speed to 1.5 Gbps ata3: softreset failed (1st FIS failed) ata4: limiting SATA link speed to 1.5 Gbps ata4: softreset failed (1st FIS failed) ata3: reset failed, giving up ata4: reset failed, giving up The system disks are on ata1 and ata2, though. I tried booting the system from different other 16.04 boot media (ubuntu-16.04-server-amd64.iso, ubuntu-16.04-desktop-amd64.iso) into a rescue system. I also got the [...] AMD-Vi: Event Logged ... messages. When the rescue shell was running, the system disks were also not detected, the installer I started as an experiment only offered the (USB disk) boot medium itself as installation target. The desktop installer and kernel then crashed with error messages about squashfs (sorry, didn't record those). Without any change, the same system boots without issues from a 14.04 boot image, all disks present. Also, the 16.04 system boots fine if the old 3.13.0-86 kernel is selected in the GRUB menu. After some fiddling around, I turned off the IOMMU in the server's BIOS (under PCiExpress) - and all went back to normal, without any change on the installed system. Kernel 4.4.0-22-generic now boots just fine from the LVM-Root. So this is WORKSFORME now, but maybe somebody should look into it. I do believe that Proliants are quite common out there. If needed, I'll provide more info if possible - but currently I wouldn't know what. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 17 18:50 seq crw-rw 1 root audio 116, 33 May 17 18:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=d46c7c15-9d36-4d87-930d-e43d447e8855 InstallationDate: Installed on 2012-12-22 (1244 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL165 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/vg0-root ro net.ifnames=0 rootfstype=ext4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2014-05-25 (725 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/27/2012 dmi.bios.vendor: HP dmi.bios.version: O37 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO37:bd07/27/2012:svnHP:pnProLiantDL165G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL165 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582858/+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
[Kernel-packages] [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
I've tested with kernel 4.6.0 from linux- image-4.6.0-040600-generic_4.6.0-040600.201605151930_amd64.deb. The error does not appear with this kernel. Attaching dmesg with IOMMU en-/disabled and adding tag. -- 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/1582858 Title: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled Status in linux package in Ubuntu: Confirmed Bug description: On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I know, not supported). After reboot, the new kernel was loaded by GRUB, but failed to find the disks installed in the system (setup working for almost 2 years, standard HP setup with the SATA controller in AHCI mode and AHCI enabled during BIOS). It then dropped to a shell in initramfs, after hundreds (thousands?) of identical errors: [...] AMD-Vi: Event Logged [IO_PAGE_FAULT] device=xxx adress=yyy flags=0x... and the final error messages: ata3: softreset failed (1st FIS failed) ata4: softreset failed (1st FIS failed) ata3: limiting SATA link speed to 1.5 Gbps ata3: softreset failed (1st FIS failed) ata4: limiting SATA link speed to 1.5 Gbps ata4: softreset failed (1st FIS failed) ata3: reset failed, giving up ata4: reset failed, giving up The system disks are on ata1 and ata2, though. I tried booting the system from different other 16.04 boot media (ubuntu-16.04-server-amd64.iso, ubuntu-16.04-desktop-amd64.iso) into a rescue system. I also got the [...] AMD-Vi: Event Logged ... messages. When the rescue shell was running, the system disks were also not detected, the installer I started as an experiment only offered the (USB disk) boot medium itself as installation target. The desktop installer and kernel then crashed with error messages about squashfs (sorry, didn't record those). Without any change, the same system boots without issues from a 14.04 boot image, all disks present. Also, the 16.04 system boots fine if the old 3.13.0-86 kernel is selected in the GRUB menu. After some fiddling around, I turned off the IOMMU in the server's BIOS (under PCiExpress) - and all went back to normal, without any change on the installed system. Kernel 4.4.0-22-generic now boots just fine from the LVM-Root. So this is WORKSFORME now, but maybe somebody should look into it. I do believe that Proliants are quite common out there. If needed, I'll provide more info if possible - but currently I wouldn't know what. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 17 18:50 seq crw-rw 1 root audio 116, 33 May 17 18:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=d46c7c15-9d36-4d87-930d-e43d447e8855 InstallationDate: Installed on 2012-12-22 (1244 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL165 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/vg0-root ro net.ifnames=0 rootfstype=ext4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2014-05-25 (725 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/27/2012 dmi.bios.vendor: HP dmi.bios.version: O37 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO37:bd07/27/2012:svnHP:pnProLiantDL165G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL165 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582858/+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
[Kernel-packages] [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
** Attachment added: "dmesg with iommu enabled" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582858/+attachment/4667056/+files/4.6.0-iommu.dmesg.txt -- 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/1582858 Title: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled Status in linux package in Ubuntu: Confirmed Bug description: On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I know, not supported). After reboot, the new kernel was loaded by GRUB, but failed to find the disks installed in the system (setup working for almost 2 years, standard HP setup with the SATA controller in AHCI mode and AHCI enabled during BIOS). It then dropped to a shell in initramfs, after hundreds (thousands?) of identical errors: [...] AMD-Vi: Event Logged [IO_PAGE_FAULT] device=xxx adress=yyy flags=0x... and the final error messages: ata3: softreset failed (1st FIS failed) ata4: softreset failed (1st FIS failed) ata3: limiting SATA link speed to 1.5 Gbps ata3: softreset failed (1st FIS failed) ata4: limiting SATA link speed to 1.5 Gbps ata4: softreset failed (1st FIS failed) ata3: reset failed, giving up ata4: reset failed, giving up The system disks are on ata1 and ata2, though. I tried booting the system from different other 16.04 boot media (ubuntu-16.04-server-amd64.iso, ubuntu-16.04-desktop-amd64.iso) into a rescue system. I also got the [...] AMD-Vi: Event Logged ... messages. When the rescue shell was running, the system disks were also not detected, the installer I started as an experiment only offered the (USB disk) boot medium itself as installation target. The desktop installer and kernel then crashed with error messages about squashfs (sorry, didn't record those). Without any change, the same system boots without issues from a 14.04 boot image, all disks present. Also, the 16.04 system boots fine if the old 3.13.0-86 kernel is selected in the GRUB menu. After some fiddling around, I turned off the IOMMU in the server's BIOS (under PCiExpress) - and all went back to normal, without any change on the installed system. Kernel 4.4.0-22-generic now boots just fine from the LVM-Root. So this is WORKSFORME now, but maybe somebody should look into it. I do believe that Proliants are quite common out there. If needed, I'll provide more info if possible - but currently I wouldn't know what. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 17 18:50 seq crw-rw 1 root audio 116, 33 May 17 18:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=d46c7c15-9d36-4d87-930d-e43d447e8855 InstallationDate: Installed on 2012-12-22 (1244 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL165 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/vg0-root ro net.ifnames=0 rootfstype=ext4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2014-05-25 (725 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/27/2012 dmi.bios.vendor: HP dmi.bios.version: O37 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO37:bd07/27/2012:svnHP:pnProLiantDL165G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL165 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582858/+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
[Kernel-packages] [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
Re: comment#3 @jsalisbury: I'll try, but this will take some time. Please bear with me :-) -- 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/1582858 Title: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled Status in linux package in Ubuntu: Confirmed Bug description: On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I know, not supported). After reboot, the new kernel was loaded by GRUB, but failed to find the disks installed in the system (setup working for almost 2 years, standard HP setup with the SATA controller in AHCI mode and AHCI enabled during BIOS). It then dropped to a shell in initramfs, after hundreds (thousands?) of identical errors: [...] AMD-Vi: Event Logged [IO_PAGE_FAULT] device=xxx adress=yyy flags=0x... and the final error messages: ata3: softreset failed (1st FIS failed) ata4: softreset failed (1st FIS failed) ata3: limiting SATA link speed to 1.5 Gbps ata3: softreset failed (1st FIS failed) ata4: limiting SATA link speed to 1.5 Gbps ata4: softreset failed (1st FIS failed) ata3: reset failed, giving up ata4: reset failed, giving up The system disks are on ata1 and ata2, though. I tried booting the system from different other 16.04 boot media (ubuntu-16.04-server-amd64.iso, ubuntu-16.04-desktop-amd64.iso) into a rescue system. I also got the [...] AMD-Vi: Event Logged ... messages. When the rescue shell was running, the system disks were also not detected, the installer I started as an experiment only offered the (USB disk) boot medium itself as installation target. The desktop installer and kernel then crashed with error messages about squashfs (sorry, didn't record those). Without any change, the same system boots without issues from a 14.04 boot image, all disks present. Also, the 16.04 system boots fine if the old 3.13.0-86 kernel is selected in the GRUB menu. After some fiddling around, I turned off the IOMMU in the server's BIOS (under PCiExpress) - and all went back to normal, without any change on the installed system. Kernel 4.4.0-22-generic now boots just fine from the LVM-Root. So this is WORKSFORME now, but maybe somebody should look into it. I do believe that Proliants are quite common out there. If needed, I'll provide more info if possible - but currently I wouldn't know what. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 17 18:50 seq crw-rw 1 root audio 116, 33 May 17 18:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=d46c7c15-9d36-4d87-930d-e43d447e8855 InstallationDate: Installed on 2012-12-22 (1244 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL165 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/vg0-root ro net.ifnames=0 rootfstype=ext4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2014-05-25 (725 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/27/2012 dmi.bios.vendor: HP dmi.bios.version: O37 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO37:bd07/27/2012:svnHP:pnProLiantDL165G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL165 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582858/+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
[Kernel-packages] [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
I've run apport on the affected machine. Obviously, this is with the IOMMU disabled, else it wouldn't boot. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1582858 Title: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled Status in linux package in Ubuntu: Confirmed Bug description: On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I know, not supported). After reboot, the new kernel was loaded by GRUB, but failed to find the disks installed in the system (setup working for almost 2 years, standard HP setup with the SATA controller in AHCI mode and AHCI enabled during BIOS). It then dropped to a shell in initramfs, after hundreds (thousands?) of identical errors: [...] AMD-Vi: Event Logged [IO_PAGE_FAULT] device=xxx adress=yyy flags=0x... and the final error messages: ata3: softreset failed (1st FIS failed) ata4: softreset failed (1st FIS failed) ata3: limiting SATA link speed to 1.5 Gbps ata3: softreset failed (1st FIS failed) ata4: limiting SATA link speed to 1.5 Gbps ata4: softreset failed (1st FIS failed) ata3: reset failed, giving up ata4: reset failed, giving up The system disks are on ata1 and ata2, though. I tried booting the system from different other 16.04 boot media (ubuntu-16.04-server-amd64.iso, ubuntu-16.04-desktop-amd64.iso) into a rescue system. I also got the [...] AMD-Vi: Event Logged ... messages. When the rescue shell was running, the system disks were also not detected, the installer I started as an experiment only offered the (USB disk) boot medium itself as installation target. The desktop installer and kernel then crashed with error messages about squashfs (sorry, didn't record those). Without any change, the same system boots without issues from a 14.04 boot image, all disks present. Also, the 16.04 system boots fine if the old 3.13.0-86 kernel is selected in the GRUB menu. After some fiddling around, I turned off the IOMMU in the server's BIOS (under PCiExpress) - and all went back to normal, without any change on the installed system. Kernel 4.4.0-22-generic now boots just fine from the LVM-Root. So this is WORKSFORME now, but maybe somebody should look into it. I do believe that Proliants are quite common out there. If needed, I'll provide more info if possible - but currently I wouldn't know what. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 17 18:50 seq crw-rw 1 root audio 116, 33 May 17 18:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=d46c7c15-9d36-4d87-930d-e43d447e8855 InstallationDate: Installed on 2012-12-22 (1244 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL165 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/vg0-root ro net.ifnames=0 rootfstype=ext4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2014-05-25 (725 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/27/2012 dmi.bios.vendor: HP dmi.bios.version: O37 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO37:bd07/27/2012:svnHP:pnProLiantDL165G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL165 G7 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582858/+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
[Kernel-packages] [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
apport information ** Tags added: apport-collected ** Description changed: On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I know, not supported). After reboot, the new kernel was loaded by GRUB, but failed to find the disks installed in the system (setup working for almost 2 years, standard HP setup with the SATA controller in AHCI mode and AHCI enabled during BIOS). It then dropped to a shell in initramfs, after hundreds (thousands?) of identical errors: [...] AMD-Vi: Event Logged [IO_PAGE_FAULT] device=xxx adress=yyy flags=0x... and the final error messages: ata3: softreset failed (1st FIS failed) ata4: softreset failed (1st FIS failed) ata3: limiting SATA link speed to 1.5 Gbps ata3: softreset failed (1st FIS failed) ata4: limiting SATA link speed to 1.5 Gbps ata4: softreset failed (1st FIS failed) ata3: reset failed, giving up ata4: reset failed, giving up The system disks are on ata1 and ata2, though. I tried booting the system from different other 16.04 boot media (ubuntu-16.04-server-amd64.iso, ubuntu-16.04-desktop-amd64.iso) into a rescue system. I also got the [...] AMD-Vi: Event Logged ... messages. When the rescue shell was running, the system disks were also not detected, the installer I started as an experiment only offered the (USB disk) boot medium itself as installation target. The desktop installer and kernel then crashed with error messages about squashfs (sorry, didn't record those). Without any change, the same system boots without issues from a 14.04 boot image, all disks present. Also, the 16.04 system boots fine if the old 3.13.0-86 kernel is selected in the GRUB menu. After some fiddling around, I turned off the IOMMU in the server's BIOS (under PCiExpress) - and all went back to normal, without any change on the installed system. Kernel 4.4.0-22-generic now boots just fine from the LVM-Root. - So this is WORKSFORME now, but maybe somebody should look into it. I do - believe that Proliants are quite common out there. If needed, I'll - provide more info if possible - but currently I wouldn't know what. + So this is WORKSFORME now, but maybe somebody should look into it. I do believe that Proliants are quite common out there. If needed, I'll provide more info if possible - but currently I wouldn't know what. + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 May 17 18:50 seq + crw-rw 1 root audio 116, 33 May 17 18:50 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=d46c7c15-9d36-4d87-930d-e43d447e8855 + InstallationDate: Installed on 2012-12-22 (1244 days ago) + InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) + IwConfig: Error: [Errno 2] No such file or directory + MachineType: HP ProLiant DL165 G7 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + LANGUAGE=en_US:en + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/vg0-root ro net.ifnames=0 rootfstype=ext4 + ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-22-generic N/A + linux-backports-modules-4.4.0-22-generic N/A + linux-firmware1.157 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial + Uname: Linux 4.4.0-22-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2014-05-25 (725 days ago) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 07/27/2012 + dmi.bios.vendor: HP + dmi.bios.version: O37 + dmi.chassis.type: 23 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrO37:bd07/27/2012:svnHP:pnProLiantDL165G7:pvr:cvnHP:ct23:cvr: + dmi.product.name: ProLiant DL165 G7 + dmi.sys.vendor: HP ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1582858/+attachment/4666465/+files/CRDA.txt -- 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/1582858 Title: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled Status in linux package in Ubuntu: Confirmed Bug description: On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I know, not supported). After reboot, the new kernel was loaded by GRUB, but failed to find the disks installed in the system (setup working for almost 2 years, standard HP setup with the SATA controller in AHCI mode and AHCI enabled during BIOS). It then dropped to a shell in initramfs,
[Kernel-packages] [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety ** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1582858 Title: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled Status in linux package in Ubuntu: Incomplete Bug description: On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I know, not supported). After reboot, the new kernel was loaded by GRUB, but failed to find the disks installed in the system (setup working for almost 2 years, standard HP setup with the SATA controller in AHCI mode and AHCI enabled during BIOS). It then dropped to a shell in initramfs, after hundreds (thousands?) of identical errors: [...] AMD-Vi: Event Logged [IO_PAGE_FAULT] device=xxx adress=yyy flags=0x... and the final error messages: ata3: softreset failed (1st FIS failed) ata4: softreset failed (1st FIS failed) ata3: limiting SATA link speed to 1.5 Gbps ata3: softreset failed (1st FIS failed) ata4: limiting SATA link speed to 1.5 Gbps ata4: softreset failed (1st FIS failed) ata3: reset failed, giving up ata4: reset failed, giving up The system disks are on ata1 and ata2, though. I tried booting the system from different other 16.04 boot media (ubuntu-16.04-server-amd64.iso, ubuntu-16.04-desktop-amd64.iso) into a rescue system. I also got the [...] AMD-Vi: Event Logged ... messages. When the rescue shell was running, the system disks were also not detected, the installer I started as an experiment only offered the (USB disk) boot medium itself as installation target. The desktop installer and kernel then crashed with error messages about squashfs (sorry, didn't record those). Without any change, the same system boots without issues from a 14.04 boot image, all disks present. Also, the 16.04 system boots fine if the old 3.13.0-86 kernel is selected in the GRUB menu. After some fiddling around, I turned off the IOMMU in the server's BIOS (under PCiExpress) - and all went back to normal, without any change on the installed system. Kernel 4.4.0-22-generic now boots just fine from the LVM-Root. So this is WORKSFORME now, but maybe somebody should look into it. I do believe that Proliants are quite common out there. If needed, I'll provide more info if possible - but currently I wouldn't know what. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582858/+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
[Kernel-packages] [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: xenial -- 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/1582858 Title: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled Status in linux package in Ubuntu: Incomplete Bug description: On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I know, not supported). After reboot, the new kernel was loaded by GRUB, but failed to find the disks installed in the system (setup working for almost 2 years, standard HP setup with the SATA controller in AHCI mode and AHCI enabled during BIOS). It then dropped to a shell in initramfs, after hundreds (thousands?) of identical errors: [...] AMD-Vi: Event Logged [IO_PAGE_FAULT] device=xxx adress=yyy flags=0x... and the final error messages: ata3: softreset failed (1st FIS failed) ata4: softreset failed (1st FIS failed) ata3: limiting SATA link speed to 1.5 Gbps ata3: softreset failed (1st FIS failed) ata4: limiting SATA link speed to 1.5 Gbps ata4: softreset failed (1st FIS failed) ata3: reset failed, giving up ata4: reset failed, giving up The system disks are on ata1 and ata2, though. I tried booting the system from different other 16.04 boot media (ubuntu-16.04-server-amd64.iso, ubuntu-16.04-desktop-amd64.iso) into a rescue system. I also got the [...] AMD-Vi: Event Logged ... messages. When the rescue shell was running, the system disks were also not detected, the installer I started as an experiment only offered the (USB disk) boot medium itself as installation target. The desktop installer and kernel then crashed with error messages about squashfs (sorry, didn't record those). Without any change, the same system boots without issues from a 14.04 boot image, all disks present. Also, the 16.04 system boots fine if the old 3.13.0-86 kernel is selected in the GRUB menu. After some fiddling around, I turned off the IOMMU in the server's BIOS (under PCiExpress) - and all went back to normal, without any change on the installed system. Kernel 4.4.0-22-generic now boots just fine from the LVM-Root. So this is WORKSFORME now, but maybe somebody should look into it. I do believe that Proliants are quite common out there. If needed, I'll provide more info if possible - but currently I wouldn't know what. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582858/+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
