[Bug 1622894] Re: sg devices are not being created for SCSI storage controller devices starting from v4.4.0-30

Hi Joseph, Seems like it doesn't. Thanks, Amit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622894 Title: sg devices are not being created for SCSI storage controller devices starting from

[Bug 1611360] Re: Xenial 32-bit: multipath exits with SIGSEGV

Tested package multipath-tools | 0.5.0+git1.656f8865-5ubuntu7.1 successfully on xenial on i386 architecture. The test case basically follows the lines of the one described by Jon Grimm in comment #19. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug

[Bug 1611360] Re: Xenial 32-bit: multipath exits with SIGSEGV

Thanks Martin. As previously posted, I will test this package as soon as it is released to the Xenial repo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611360 Title: Xenial 32-bit: multipath

[Bug 1629644] Re: Trusty: failure to detect device with 0.4.9-3ubuntu7.5

Thanks. I want to perform a git bisection on this revision. I cloned the relevant bazaar branch (trusty-updated) but revision 0.4.9-3ubuntu7.5 does not exist there (neither in any other trusty branch). Any way in which I can get it? -- You received this bug notification because you are a

[Bug 1611360] Re: Xenial 32-bit: multipath exits with SIGSEGV

Hi Jon! Thanks, I was not aware of that :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611360 Title: Xenial 32-bit: multipath exits with SIGSEGV To manage notifications about this bug go to:

[Bug 1611360] Re: Xenial 32-bit: multipath exits with SIGSEGV

Thanks Jon Grimm and everyone else, but can you also fix it in Xenial? We are using Xenial on our servers as it is LTS, and giving support for Xenial to our customers for this very reason, and we did not intend to upgrade to Zesty anytime soon. I don't want to use pinning for that specific

[Bug 1629644] Re: Trusty: failure to detect device with 0.4.9-3ubuntu7.5

I made a mistake in the previous comment: I re-validated it a few times on my setup, the issue is present when upgrading from 7.4 to the proposed 7.5. ** Summary changed: - Trusty: failure to detect device with 0.4.9-3ubuntu7.6 + Trusty: failure to detect device with 0.4.9-3ubuntu7.5 -- You

[Bug 1629644] Re: Trusty: failure to detect device with 0.4.9-3ubuntu7.14

Thanks for the replies. @racb After further bisection I can now say the first version the issue occurs in is 0.4.9-3ubuntu7.6. @louis-bouchard Unfortunately, updating the initrd.img file and rebooting the server did not fix the issue. -- You received this bug notification because you are a

[Bug 1622894] Re: sg devices are not being created for SCSI storage controller devices starting from v4.4.0-30

Hi, any news? Should I re-open #1567602 (you can see from the bisection the commit leads to this issue)? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622894 Title: sg devices are not

[Bug 1622894] Re: sg devices are not being created for SCSI storage controller devices starting from v4.4.0-30

Finished the kernel bisection process, this is the result: "8d83f8015312b0d600157dd4b6a70ae6d9ee17f9 is the first bad commit commit 8d83f8015312b0d600157dd4b6a70ae6d9ee17f9 Author: Hannes Reinecke Date: Tue Dec 1 10:16:57 2015 +0100 scsi: Add scsi_vpd_tpg_id() Implement

[Bug 1629644] [NEW] Trusty: failure to detect device with 0.4.9-3ubuntu7.14

Public bug reported: When trying to detect a device with the latest 0.4.9-3ubuntu7.14 version, no device is detected. When downgrading to 0.4.9-3ubuntu7 everything works fine. See this console log for more detail: https://gist.github.com/amito/4108cd7ee895baecc9a6412e7c5fdeac ** Affects:

[Bug 1611360] Re: Xenial 32-bit: multipath exits with SIGSEGV

Ping? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611360 Title: Xenial 32-bit: multipath exits with SIGSEGV To manage notifications about this bug go to:

[Bug 1611360] Re: Xenial 32-bit: multipath exits with SIGSEGV

** Summary changed: - Segmentation fault on Xenial 32 bit + Xenial 32-bit: multipath exits with SIGSEGV -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611360 Title: Xenial 32-bit: multipath exits

[Bug 1622894] WifiSyslog.txt

apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1622894/+attachment/4739837/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1622894] ProcInterrupts.txt

apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1622894/+attachment/4739834/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1622894] JournalErrors.txt

apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1622894/+attachment/4739830/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1622894] UdevDb.txt

apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1622894/+attachment/4739836/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622894 Title:

[Bug 1622894] ProcEnviron.txt

apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1622894/+attachment/4739833/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622894

[Bug 1622894] ProcCpuinfo.txt

apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1622894/+attachment/4739832/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622894

[Bug 1622894] CurrentDmesg.txt

apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1622894/+attachment/4739829/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1622894] ProcModules.txt

apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1622894/+attachment/4739835/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622894

[Bug 1622894] Lspci.txt

apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1622894/+attachment/4739831/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622894 Title: sg

[Bug 1622894] Re: sg devices are not being created for SCSI storage controller devices starting from v4.4.0-30

apport information ** Tags added: apport-collected xenial ** Description changed: Most storage array expose a store controller device to logical unit 0. Following LP #1567602, when this happens and the alua driver is loaded, Ubuntu doesn't create the sg device for it, and linux fails to

[Bug 1622894] [NEW] sg devices are not being created for SCSI storage controller devices starting from v4.4.0-30

Public bug reported: Most storage array expose a store controller device to logical unit 0. Following LP #1567602, when this happens and the alua driver is loaded, Ubuntu doesn't create the sg device for it, and linux fails to discover the disks that are attached to higher logical unit numbers.