** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
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/1567602
Title:
FCP devices are not detected correctly nor dete
This bug was fixed in the package linux - 4.4.0-31.50
---
linux (4.4.0-31.50) xenial; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1602449
* nouveau: boot hangs at blank screen with unsupported graphics cards
(LP: #1602340)
- SAUCE: drm: check for su
This bug was fixed in the package linux - 4.4.0-31.50
---
linux (4.4.0-31.50) xenial; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1602449
* nouveau: boot hangs at blank screen with unsupported graphics cards
(LP: #1602340)
- SAUCE: drm: check for su
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1567602
Title:
FCP devices are not detected correctly n
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
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/1567602
Title:
FCP devices are not detected correctly nor deter
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
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/1567602
Title:
FCP devices are not detected correctly nor
Added a new attempt. This time the pick-list is rather excessive.
Unfortunately the more likely changes come later. So while there might
be some patches which probably can be dropped, I fear the overall set
still will be big. (Download again:
http://people.canonical.com/~smb/lp1567602/)
5da8bf5 sc
Thanks Thorsten. So I have to go back and see what else might be
relevant. Just for reference the one patch I used (forgot to mention
this earlier) was the one below:
Author: Hannes Reinecke
Date: Tue Dec 1 10:16:44 2015 +0100
scsi_dh_alua: Use vpd_pg83 information
The SCSI device
Or better it should be 4.6+ at some point. I realized it still is a copy
of Xenial (4.4). But I would not worry about the fix there.
--
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/1567602
Set main task back to fix released as that is then devel release which
is 4.6+ and that is claimed to work.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
** Changed in: linux (Ubuntu)
Status: Fix Released => 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/1567602
sorry, cliecked something wrong. Please delete my changes.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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/1567602
Ti
** Changed in: ubuntu-z-systems
Status: Confirmed => In Progress
--
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/1567602
Title:
FCP devices are not detected correctly nor determini
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Stef
Hi Thorsten, so maybe (if the main issue is the inquiry) it is possible
to get away with just picking the change that appears to remove that in
favour of present device information. Could you try the kernel at
http://people.canonical.com/~smb/lp1567602/ in your environment and let
me know whether t
** Changed in: ubuntu-z-systems
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/1567602
Title:
FCP devices are not detected correctly nor deterministicall
@ Thorsten
We should be working together, because we do not have the mainframe
setup/config which reproduces / exhibits this bug. And possibly neither
upstream maintainer. It is common code, but the bug is triggered on
hardware config and platform that IBM ships.
** Changed in: linux (Ubuntu)
@Thorsten
A large affected userbase is important to us. What I was trying to point
out is that even without any added work done (e.g. figuring out where
the fix is, and backporting it to v4.4 series) this will be resolved in
the 14.04 series via hwe kernel.
At this point, this appears to be a lin
** Changed in: ubuntu-z-systems
Status: Triaged => Confirmed
--
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/1567602
Title:
FCP devices are not detected correctly nor deterministic
@ Benjamin
Thank you for your insights. Is it possible to determine a scope of
affected systems out there? So far a specific config is required to
trigger this bug it seems, but I'm not sure how common such a
configuration is. Extensive back-ports and reworks of the kernel are out
of the question.
** Changed in: ubuntu-z-systems
Status: New => Triaged
--
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/1567602
Title:
FCP devices are not detected correctly nor deterministically
16GB to the switch and from there 8GB to the DS8K.
The DS8K was only delivered with 8G DAs
--
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/1567602
Title:
FCP devices are not detected corr
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1567602
** Changed in: linux (Ubuntu)
Importance: High => Undecided
--
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/1567602
Title:
FCP devices are not detected correctly nor deterministically
** 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/1567602
Title:
FCP devices are not detected correctly nor deterministically
** Changed in: ubuntu-release-notes
Status: New => Fix Released
--
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/1567602
Title:
FCP devices are not detected correctly nor determinis
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Description changed:
- Scenario:
+ Release notes:
+ Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP
#1567602
** No longer affects: ubuntu-release-notes
--
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/1567602
Title:
FCP devices are not detected correctly nor deterministically
Status in Ubuntu on
Sorry no, what I meant was that I do not see any problem. All LUNs get
detected, no error message about alua.
--
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/1567602
Title:
FCP devices ar
FYI - Storage Server is on older version 5.7.41.1028
--
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/1567602
Title:
FCP devices are not detected correctly nor deterministically
Status in
Just to be sure I did a cross check on my lpar:
Cleaning my system to get an empty condition at the start
sudo chzdev zfcp-lun --all --disable --force
sudo chzdev zfcp-host --all --disable --force
sudo chzdev zfcp --all --disable --force
Now it looks like the one from Thorsten:
ubuntu@s1lp5:~$ l
I also tried to re-create this on one of the lpars we got. No luck
either. However I was using the latest kernel which was uploaded just
... I think yesterday (4.4.0-21). Thorsten, maybe you can try that
version, too. Just to be on the safe side.
The dmesg I get also shows that alua probing is don
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
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/1567602
Title:
FCP devices are not detected correctly nor
** Tags removed: targetmilestone-inin1604
** Tags added: targetmilestone-inin16041
--
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/1567602
Title:
FCP devices are not detected correctly no
Also w.r.t. multipath, disk-detect/multipath/enable is now enabled by
default on Ubuntu on s390x, thus multipath installer codepath should be
the one offered by the installer when the devices are scanned correctly.
Moving this bug report to kernel package, as it seems to me this is a
kernel issue a
So this is an upstream kernel regression with certain hardware
configuration? I'm looking into scans as seen on our hardware, but it
appears to be consistently discovered on our combinations of hardware,
but will stress test that more.
** Package changed: debian-installer (Ubuntu) => linux (Ubuntu
37 matches
Mail list logo