← Back to team overview

kernel-packages team mailing list archive

[Bug 1582858] Missing required logs.


This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1582858

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  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:

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

  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: