subject:"\[Kernel\-packages\] \[Bug 1653162\] Re\: System won't boot after upgrade to 16.04 with 4.4.0 kernel"

[Kernel-packages] [Bug 1653162] Re: System won't boot after upgrade to 16.04 with 4.4.0 kernel

2019-07-24 Thread Brad Figg

** Tags added: cscc

-- 
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:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux source package in Yakkety:
  Won't Fix

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.
   
   lono 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=
   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

[Kernel-packages] [Bug 1653162] Re: System won't boot after upgrade to 16.04 with 4.4.0 kernel

2019-03-21 Thread James Hanna

Follow up of my previous comment:

Compiled and installed RHEL 8 kernel. RHEL 8 aacraid driver does not
seem to have the bug.

System Rescue CD v5.2.2 (http://www.system-rescue-cd.org) aacraid module
does not encounter the bug.

However Debian did not boot "out of the box" if I installed either of
these kernels and generated initrd. It would always drop to a shell
after failing to mount the root volume, which was an ext4 MBR partition.
The partition mounts fine after booting System Rescue CD, and does not
suffer from the aacraid module bug.

Speculation: failure to mount at boot with RHEL 8 or System Rescue CD is
a Debian-specific init issue. Did not perform further troubleshooting
using the RAID card.

Pulled the CERC 1.5/6 ch RAID card and attached directly to the SATA
ports on the motherboard, to continue the project.

--
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:
Invalid
Status in linux source package in Xenial:
Invalid
Status in linux source package in Yakkety:
Won't Fix

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.

lono 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=
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

[Kernel-packages] [Bug 1653162] Re: System won't boot after upgrade to 16.04 with 4.4.0 kernel

2019-02-19 Thread James Hanna

Please forgive if this comment is outside etiquette.

I am trying to install Ubuntu or Debian on a Dell Poweredge 750, and get
this error after a few minutes of uptime:

aacraid: Host adapter abort request (0,0,0,0) [repeat >15x]
AAC: Host adapter BLINK LED 0xc7
AAC0: adapter kernel panic'd c7.
[last two lines repeat again twice]

Am installing in a workplace at request of IS Dept manager, to determine
feasibility of using Linux on a server to run SQL server. If it fails,
management probably won't consider using Linux, period.

The server has been running Windows 7 to support its previous role at
the company, and was not experiencing any issues of any kind.

Question: is there currently a workaround for this issue, so I can use
the Dell PowerEdge 750 hardware with a RAID-1 setup?

Considering moving the drives to non-RAID controller to avoid driver
issue. Not sure if this will work, but would like to avoid project
failure.

Thanks for your time and efforts here!