Or maybe not as 4.6 seems to fix that race. Though I found one change in
the ALUA handler post 4.6 which modifies the handling of missing VPD
identification (which leads to the "No device descriptors found"
message):
commit fe8b9534a0a0356f8a76467e2c561194bdb53c84
Author: Hannes Reinecke <h...@suse.de>
Date: Fri May 6 10:34:35 2016 +0200
scsi_dh_alua: do not fail for unknown VPD identification
Not every device will return a useable VPD identification, but still
might support ALUA. Rather than disable ALUA support we should be
allowing the device identification to be empty and attach individual
ALUA device handler to each devices.
--
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
--
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
