[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-08-01 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-07-04 06:42 EDT--- Verified succesfully with kernel 4.4.0-30-generic from xenial-proposed. Please promote to xenial now. --- Comment From ar...@de.ibm.com 2016-07-18 08:09 EDT--- Verified successfully running an installation in an

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-07-18 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-07-04 06:42 EDT--- Verified succesfully with kernel 4.4.0-30-generic from xenial-proposed. Please promote to xenial now. --- Comment From ar...@de.ibm.com 2016-07-18 08:09 EDT--- Verified successfully running an installation in an

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-07-18 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-07-04 06:42 EDT--- Verified succesfully with kernel 4.4.0-30-generic from xenial-proposed. Please promote to xenial now. --- Comment From ar...@de.ibm.com 2016-07-18 08:09 EDT--- Verified successfully running an installation in an

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-07-14 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-07-04 06:42 EDT--- Verified succesfully with kernel 4.4.0-30-generic from xenial-proposed. Please promote to xenial now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-07-14 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-07-04 06:42 EDT--- Verified succesfully with kernel 4.4.0-30-generic from xenial-proposed. Please promote to xenial now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-07-05 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-07-04 06:42 EDT--- Verified succesfully with kernel 4.4.0-30-generic from xenial-proposed. Please promote to xenial now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-07-05 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-07-04 06:42 EDT--- Verified succesfully with kernel 4.4.0-30-generic from xenial-proposed. Please promote to xenial now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-06-29 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-06-29 06:59 EDT--- Hi Stefan, very good. The diligent wins!! With this kernel I could not reproduce the symptom as described in the bug report. I suggest to go ahead with this, and by the way, it is also needed in the installer, where the

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-06-28 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-06-28 08:15 EDT--- (In reply to comment #60) > 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

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-06-22 Thread bugproxy
--- Comment From bbl...@de.ibm.com 2016-06-22 05:30 EDT--- *** Bug 142864 has been marked as a duplicate of this bug. *** -- 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

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-06-09 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-06-09 08:05 EDT--- (In reply to comment #54) > @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

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-06-07 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-06-07 11:45 EDT--- Hi Dimitri, any customer using a zEC12, z13 with zfcp Adaptor connected via FC Switch to DS8000 any model having uCode Level 7.5 or newer might be affected. V7000 Storage is not affected, AFAICS today. So, this is quite

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-05-25 Thread bugproxy
--- Comment From bbl...@de.ibm.com 2016-05-25 12:17 EDT--- Hello Canonical, after talking with different folks here and trying to figure out why this fails, we found the likely bug here, and its in the kernel after all. When scanning the SCSI LUNs behind a found FCP remote port (during

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-04-25 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-04-25 06:07 EDT--- @Canonical: Do you have the z13 connected via 16GB link via a switch to DS8870 - or via 8Gb link? - We could not reproduce this on 8Gb link. -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-04-21 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-04-21 11:35 EDT--- (In reply to comment #39) > > Thorsten please try to reproduce on a fully updated system, if not resolved > for you we have to start to sort out the remaining differences in our > environment. Yes, I did that during the

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-04-21 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-04-21 07:05 EDT--- I saw these problems today also on another machine / switch / DS8870 combination: DS8870 uCode was 5.7.51.1009, which is also the newer stream. Obviously the older stream 5.7.41.xx didn't show these problems. At least the

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-04-20 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-04-20 12:03 EDT--- Problem persists here with DS8700 uCode version 5.7.51.1041 (Code Bundle 87.51.38.0) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-04-20 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-04-20 11:35 EDT--- (In reply to comment #37) > 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

[Kernel-packages] [Bug 1567602] Comment bridged from LTC Bugzilla

2016-04-20 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-04-20 06:45 EDT--- The problem of LUNs not being properly discovered happened only on the following combination: Storage Server DS8870 AND ( auto LUN scan when onlining an NPIV enabled device OR scripted parallelized addition of LUNs) AND