kernel-packages team mailing list archive

[Stefan Bader <stefan.bader@xxxxxxxxxxxxx>]

Comparing that to the working 4.4 kernel it looks like device handler
fails to receive valid data. The info should look like this:

[    1.653229] sd 0:2:0:0: alua: supports implicit TPGS
[    1.653395] sd 0:2:0:0: alua: port group c339 rel port c339
[    1.653426] sd 0:2:0:0: alua: rtpg failed with 8070002
[    1.653459] sd 0:2:0:0: alua: port group c339 state A preferred supports TOlUSNA
[    1.653616] sd 0:2:0:0: Attached scsi generic sg13 type 0

While the exact symptoms differ, this sounds a bit like there might be
some relation to the device scan problems that are seen on zSeries (LP:
#1567602).

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

** 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/1588421

Title:
  linux: 4.6 kernel fails to boot on ppc64el multi-path system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/9759880/+files/linux-image-4.6.0-6-generic_4.6.0-6.7_ppc64el.deb
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/9759880/+files/linux-image-extra-4.6.0-6-generic_4.6.0-6.7_ppc64el.deb

  Provisioned modoc (ppc64el) with stock Xenial, then installed the
  above kernel. It eventually times out attempting to mount rootfs and
  drops to the busybox prompt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588421/+subscriptions