I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.
Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug: 3.13 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-trusty/ 3.16 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-utopic/ 4.0 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/ 4.2 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-wily/ 4.4 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/ You don't have to test every kernel, just up until the kernel that first has this bug. Thanks in advance! ** Changed in: linux (Ubuntu) Importance: High => Critical ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Critical ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Tags removed: kernel-da-key ** Tags added: kernel-key -- 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/1653162 Title: System won't boot after upgrade to 16.04 with 4.4.0 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Yakkety: Triaged Bug description: I have a Dell PowerEdge 1800 with Dell CERC 1.5/6ch RAID controller in it. Everything worked fine under Ubuntu 14.04.1. When I upgraded to 16.04.1 the system won't boot. It can't find the root filesystem. I see errors about host adapter dead on the screen many times. This is with kernel 4.4.0-57 and with 4.8.0-32. When I switch back to kernel 3.13.0-105 the system boots just fine. I have mptbios 5.06.04. The CERC card says bios version 4.1-0 [Build 7403] When booting into the ercovery kernel I'm getting error messages about host adapter dead. Eventually I get a message: "aacraid: aac_fib_send: first asynchronous command timed out. Usually a result of a PCI interrupt routing problem update moher board BIOS or consider utilizing one of the SAFE mode kernel options (acpi, apic etc)" Using kernel parameter "intel_iommu=on" doesn't help. This was suggested on a post that I saw about these errors. Booting with "noapic" didn't help. Booting with "noapic noacpi" didn't help. I've also tried the dkms modules from Adaptec and that doesn't seem to help either. I can't figure out how to upgrade the firmware or BIOS on the system from Ubuntu either. This may be related to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551?comments=all --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=beec17b5-eac8-4e94-ac99-65b63c428b77 InstallationDate: Installed on 2014-02-24 (1039 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) IwConfig: eth1 no wireless extensions. lo no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Computer Corporation PowerEdge 1800 Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-105-generic root=UUID=83e1b87e-adb9-4798-a6e0-18d401c91a4a ro nosplash noplymouth ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-105-generic N/A linux-backports-modules-3.13.0-105-generic N/A linux-firmware 1.157.6 RfKill: Tags: xenial Uname: Linux 3.13.0-105-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-12-25 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/01/2004 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A00 dmi.board.name: 0X7500 dmi.board.vendor: Dell Computer Corporation dmi.board.version: A00 dmi.chassis.type: 17 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA00:bd09/01/2004:svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation:rn0X7500:rvrA00:cvnDellComputerCorporation:ct17:cvr: dmi.product.name: PowerEdge 1800 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653162/+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
