[Kernel-packages] [Bug 1597047] alkaid (amd64) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/alkaid__3.16.0-77.99~14.04.1__2016-07-01_05-32-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1597047] onza (amd64) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/onza__3.16.0-77.99~14.04.1__2016-07-01_04-33-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1597047] alkaid (i386) - tests ran: 77, failed: 0
tests ran: 77, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/alkaid__3.16.0-77.99~14.04.1__2016-07-01_02-52-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically
** 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 deterministically Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found Apr 6 12:57:10 main-menu[384]:
[Kernel-packages] [Bug 1597971] Re: kernel: signal return with invalid floating-point control
** Also affects: linux Importance: Undecided Status: New ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Andy Whitcroft (apw) -- 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/1597971 Title: kernel: signal return with invalid floating-point control Status in Linux: New Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Please backport: commit bcf4dd5f9ee096bd1510f838dd4750c35df4e38b Author: Martin SchwidefskyDate: Mon Jun 27 17:06:45 2016 +0200 s390: fix test_fp_ctl inline assembly contraints The test_fp_ctl function is used to test if a given value is a valid floating-point control. The inline assembly in test_fp_ctl uses an incorrect constraint for the 'orig_fpc' variable. If the compiler chooses the same register for 'fpc' and 'orig_fpc' the test_fp_ctl() function always returns true. This allows user space to trigger kernel oopses with invalid floating-point control values on the signal stack. This problem has been introduced with git commit 4725c86055f5bbdcdf "s390: fix save and restore of the floating-point-control register" Cc: sta...@vger.kernel.org # v3.13+ Reviewed-by: Heiko Carstens Signed-off-by: Martin Schwidefsky To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1597971/+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
[Kernel-packages] [Bug 1597047] onibi (amd64) - tests ran: 77, failed: 28
tests ran: 77, failed: 28; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/onibi__3.16.0-77.99~14.04.1__2016-07-01_00-12-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1597106] Re: linux-lts-trusty: 3.13.0-92.139~precise1 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Yung Shen (kaxing) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1597106 Title: linux-lts-trusty: 3.13.0-92.139~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-92.139~precise1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true kernel-stable-master-bug: 1597060 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597106/+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
[Kernel-packages] [Bug 1597060] Re: linux: 3.13.0-92.139 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Yung Shen (kaxing) -- 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/1597060 Title: linux: 3.13.0-92.139 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-92.139 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597060/+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
[Kernel-packages] [Bug 1597109] Re: linux: 3.2.0-106.147 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Yung Shen (kaxing) -- 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/1597109 Title: linux: 3.2.0-106.147 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug is for tracking the 3.2.0-106.147 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597109/+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
[Kernel-packages] [Bug 1597047] onza (i386) - tests ran: 20, failed: 1
tests ran: 20, failed: 1; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/onza__3.16.0-77.99~14.04.1__2016-07-01_02-47-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1597047] alkaid (amd64) - tests ran: 77, failed: 0
tests ran: 77, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/alkaid__3.16.0-77.99~14.04.1__2016-07-01_00-06-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1597047] onza (amd64) - tests ran: 20, failed: 0
tests ran: 20, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/onza__3.16.0-77.99~14.04.1__2016-07-01_00-57-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1597974] [NEW] ISST-LTE:pVM:monklp5:Ubuntu16.04.1:system crashed at lpfc_sli4_scmd_to_wqidx_distr
Public bug reported: ---Problem Description--- We have Ubuntu16.04.1 installed on our system and run DLPAR test for ZR1 adapter after some time it crashes at lpfc_sli4_scmd_to_wqidx_distr+0x30/0x100 Machine Type = 9119-MME*1085AE7 ---Debugger Data--- e:mon> e cpu 0xe: Vector: 300 (Data Access) at [c003d45335a0] pc: d3a374e0: lpfc_sli4_scmd_to_wqidx_distr+0x30/0x100 [lpfc] lr: d39d749c: lpfc_sli_calc_ring.part.20+0xdc/0x100 [lpfc] sp: c003d4533820 msr: 80019033 dar: 0 dsisr: 4000 current = 0xc003e06c2a20 paca= 0xc7af8500 softe: 0irq_happened: 0x01 pid = 17983, comm = scsi_eh_23 e:mon> r R00 = d39d749c R16 = R01 = c003d4533820 R17 = c003d4533cd0 R02 = d3a84160 R18 = c003d4533cb8 R03 = c003ee76a000 R19 = c003d87e5088 R04 = c003dad6a800 R20 = c003d4533cb0 R05 = c003dad6a870 R21 = 001e R06 = 0001 R22 = c18aab78 R07 = d3a84160 R23 = c003dad6a870 R08 = d3a2f830 R24 = c003dad6a800 R09 = 0004 R25 = c003d4533978 R10 = R26 = 0001 R11 = d3a59a50 R27 = R12 = 28533824 R28 = c003e841e000 R13 = c7af8500 R29 = c003ee76a000 R14 = c003d87e5000 R30 = c003dad6a800 R15 = c003d4533cb8 R31 = c003ee76a000 pc = d3a374e0 lpfc_sli4_scmd_to_wqidx_distr+0x30/0x100 [lpfc] cfar= c0008468 slb_miss_realmode+0x50/0x78 lr = d39d749c lpfc_sli_calc_ring.part.20+0xdc/0x100 [lpfc] msr = 80019033 cr = 28538828 ctr = c0ae3cf0 xer = 2010 trap = 300 dar = dsisr = 4000 e:mon> Stack trace output: e:mon> t [c003d4533850] d39d749c lpfc_sli_calc_ring.part.20+0xdc/0x100 [lpfc] [c003d4533890] d39df680 lpfc_sli_issue_iocb+0xf0/0x330 [lpfc] [c003d45338f0] d39e3824 lpfc_sli_issue_iocb_wait+0x264/0x680 [lpfc] [c003d45339d0] d3a32944 lpfc_send_taskmgmt+0x2d4/0x7d0 [lpfc] [c003d4533aa0] d3a33564 lpfc_device_reset_handler+0x114/0x210 [lpfc] [c003d4533b60] c075843c scsi_eh_ready_devs+0x68c/0xee0 [c003d4533c50] c075a91c scsi_error_handler+0x6bc/0x9e0 [c003d4533d80] c00e61e0 kthread+0x110/0x130 [c003d4533e30] c0009538 ret_from_kernel_thread+0x5c/0xa4 --- Exception: 0 at e:mon> e:mon> dl [10194.079284] sd 13:0:3:0: [sdaf] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [10194.079293] sd 13:0:3:0: [sdaf] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 00 80 00 [10194.079297] blk_update_request: I/O error, dev sdaf, sector 41942912 [10194.079313] device-mapper: multipath: Failing path 65:240. [10194.079351] sd 13:0:2:0: [sdab] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [10194.079360] sd 13:0:2:0: [sdab] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 00 80 00 [10194.079364] blk_update_request: I/O error, dev sdab, sector 41942912 [10194.079375] device-mapper: multipath: Failing path 65:176. [10194.102832] scsi 13:0:1:0: alua: Detached [10194.110320] sd 13:0:1:1: [sdh] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [10194.110324] sd 13:0:1:1: [sdh] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 00 80 00 [10194.110326] blk_update_request: I/O error, dev sdh, sector 41942912 [10194.110334] device-mapper: multipath: Failing path 8:112. [10194.110394] sd 13:0:2:1: [sdac] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [10194.110398] sd 13:0:2:1: [sdac] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 00 80 00 [10194.110401] blk_update_request: I/O error, dev sdac, sector 41942912 [10194.110407] device-mapper: multipath: Failing path 65:192. [10194.110439] sd 13:0:3:1: [sdag] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [10194.110448] sd 13:0:3:1: [sdag] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 00 80 00 [10194.110452] blk_update_request: I/O error, dev sdag, sector 41942912 [10194.110464] device-mapper: multipath: Failing path 66:0. [10194.118851] scsi 13:0:0:1: alua: Detached [10194.122868] sd 13:0:3:0: [sdaf] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [10194.122879] sd 13:0:3:0: [sdaf] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 00 80 00 [10194.122887] blk_update_request: I/O error, dev sdaf, sector 41942912 [10194.122911] device-mapper: multipath: Failing path 65:240. [10194.138865] scsi 13:0:2:0: alua: Detached [10194.158852] scsi 13:0:3:0: alua: Detached [10194.162199] sd 13:0:3:1: [sdag] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [10194.162204] sd 13:0:3:1: [sdag] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 00 80 00 [10194.162207] blk_update_request: I/O error, dev sdag, sector 41942912 [10194.162216] device-mapper: multipath: Failing path 66:0. [10194.162241] device-mapper:
[Kernel-packages] [Bug 1597974] [NEW] ISST-LTE:pVM:monklp5:Ubuntu16.04.1:system crashed at lpfc_sli4_scmd_to_wqidx_distr
You have been subscribed to a public bug: ---Problem Description--- We have Ubuntu16.04.1 installed on our system and run DLPAR test for ZR1 adapter after some time it crashes at lpfc_sli4_scmd_to_wqidx_distr+0x30/0x100 Machine Type = 9119-MME*1085AE7 ---Debugger Data--- e:mon> e cpu 0xe: Vector: 300 (Data Access) at [c003d45335a0] pc: d3a374e0: lpfc_sli4_scmd_to_wqidx_distr+0x30/0x100 [lpfc] lr: d39d749c: lpfc_sli_calc_ring.part.20+0xdc/0x100 [lpfc] sp: c003d4533820 msr: 80019033 dar: 0 dsisr: 4000 current = 0xc003e06c2a20 paca= 0xc7af8500 softe: 0irq_happened: 0x01 pid = 17983, comm = scsi_eh_23 e:mon> r R00 = d39d749c R16 = R01 = c003d4533820 R17 = c003d4533cd0 R02 = d3a84160 R18 = c003d4533cb8 R03 = c003ee76a000 R19 = c003d87e5088 R04 = c003dad6a800 R20 = c003d4533cb0 R05 = c003dad6a870 R21 = 001e R06 = 0001 R22 = c18aab78 R07 = d3a84160 R23 = c003dad6a870 R08 = d3a2f830 R24 = c003dad6a800 R09 = 0004 R25 = c003d4533978 R10 = R26 = 0001 R11 = d3a59a50 R27 = R12 = 28533824 R28 = c003e841e000 R13 = c7af8500 R29 = c003ee76a000 R14 = c003d87e5000 R30 = c003dad6a800 R15 = c003d4533cb8 R31 = c003ee76a000 pc = d3a374e0 lpfc_sli4_scmd_to_wqidx_distr+0x30/0x100 [lpfc] cfar= c0008468 slb_miss_realmode+0x50/0x78 lr = d39d749c lpfc_sli_calc_ring.part.20+0xdc/0x100 [lpfc] msr = 80019033 cr = 28538828 ctr = c0ae3cf0 xer = 2010 trap = 300 dar = dsisr = 4000 e:mon> Stack trace output: e:mon> t [c003d4533850] d39d749c lpfc_sli_calc_ring.part.20+0xdc/0x100 [lpfc] [c003d4533890] d39df680 lpfc_sli_issue_iocb+0xf0/0x330 [lpfc] [c003d45338f0] d39e3824 lpfc_sli_issue_iocb_wait+0x264/0x680 [lpfc] [c003d45339d0] d3a32944 lpfc_send_taskmgmt+0x2d4/0x7d0 [lpfc] [c003d4533aa0] d3a33564 lpfc_device_reset_handler+0x114/0x210 [lpfc] [c003d4533b60] c075843c scsi_eh_ready_devs+0x68c/0xee0 [c003d4533c50] c075a91c scsi_error_handler+0x6bc/0x9e0 [c003d4533d80] c00e61e0 kthread+0x110/0x130 [c003d4533e30] c0009538 ret_from_kernel_thread+0x5c/0xa4 --- Exception: 0 at e:mon> e:mon> dl [10194.079284] sd 13:0:3:0: [sdaf] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [10194.079293] sd 13:0:3:0: [sdaf] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 00 80 00 [10194.079297] blk_update_request: I/O error, dev sdaf, sector 41942912 [10194.079313] device-mapper: multipath: Failing path 65:240. [10194.079351] sd 13:0:2:0: [sdab] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [10194.079360] sd 13:0:2:0: [sdab] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 00 80 00 [10194.079364] blk_update_request: I/O error, dev sdab, sector 41942912 [10194.079375] device-mapper: multipath: Failing path 65:176. [10194.102832] scsi 13:0:1:0: alua: Detached [10194.110320] sd 13:0:1:1: [sdh] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [10194.110324] sd 13:0:1:1: [sdh] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 00 80 00 [10194.110326] blk_update_request: I/O error, dev sdh, sector 41942912 [10194.110334] device-mapper: multipath: Failing path 8:112. [10194.110394] sd 13:0:2:1: [sdac] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [10194.110398] sd 13:0:2:1: [sdac] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 00 80 00 [10194.110401] blk_update_request: I/O error, dev sdac, sector 41942912 [10194.110407] device-mapper: multipath: Failing path 65:192. [10194.110439] sd 13:0:3:1: [sdag] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [10194.110448] sd 13:0:3:1: [sdag] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 00 80 00 [10194.110452] blk_update_request: I/O error, dev sdag, sector 41942912 [10194.110464] device-mapper: multipath: Failing path 66:0. [10194.118851] scsi 13:0:0:1: alua: Detached [10194.122868] sd 13:0:3:0: [sdaf] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [10194.122879] sd 13:0:3:0: [sdaf] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 00 80 00 [10194.122887] blk_update_request: I/O error, dev sdaf, sector 41942912 [10194.122911] device-mapper: multipath: Failing path 65:240. [10194.138865] scsi 13:0:2:0: alua: Detached [10194.158852] scsi 13:0:3:0: alua: Detached [10194.162199] sd 13:0:3:1: [sdag] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [10194.162204] sd 13:0:3:1: [sdag] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 00 80 00 [10194.162207] blk_update_request: I/O error, dev sdag, sector 41942912 [10194.162216] device-mapper: multipath: Failing path 66:0.
[Kernel-packages] [Bug 1597971] [NEW] kernel: signal return with invalid floating-point control
Public bug reported: Please backport: commit bcf4dd5f9ee096bd1510f838dd4750c35df4e38b Author: Martin SchwidefskyDate: Mon Jun 27 17:06:45 2016 +0200 s390: fix test_fp_ctl inline assembly contraints The test_fp_ctl function is used to test if a given value is a valid floating-point control. The inline assembly in test_fp_ctl uses an incorrect constraint for the 'orig_fpc' variable. If the compiler chooses the same register for 'fpc' and 'orig_fpc' the test_fp_ctl() function always returns true. This allows user space to trigger kernel oopses with invalid floating-point control values on the signal stack. This problem has been introduced with git commit 4725c86055f5bbdcdf "s390: fix save and restore of the floating-point-control register" Cc: sta...@vger.kernel.org # v3.13+ Reviewed-by: Heiko Carstens Signed-off-by: Martin Schwidefsky ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-143266 severity-high targetmilestone-inin1604 ** Tags added: architecture-s39064 bugnameltc-143266 severity-high targetmilestone-inin1604 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- 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/1597971 Title: kernel: signal return with invalid floating-point control Status in linux package in Ubuntu: New Bug description: Please backport: commit bcf4dd5f9ee096bd1510f838dd4750c35df4e38b Author: Martin Schwidefsky Date: Mon Jun 27 17:06:45 2016 +0200 s390: fix test_fp_ctl inline assembly contraints The test_fp_ctl function is used to test if a given value is a valid floating-point control. The inline assembly in test_fp_ctl uses an incorrect constraint for the 'orig_fpc' variable. If the compiler chooses the same register for 'fpc' and 'orig_fpc' the test_fp_ctl() function always returns true. This allows user space to trigger kernel oopses with invalid floating-point control values on the signal stack. This problem has been introduced with git commit 4725c86055f5bbdcdf "s390: fix save and restore of the floating-point-control register" Cc: sta...@vger.kernel.org # v3.13+ Reviewed-by: Heiko Carstens Signed-off-by: Martin Schwidefsky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597971/+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
[Kernel-packages] [Bug 1597971] [NEW] kernel: signal return with invalid floating-point control
You have been subscribed to a public bug: Please backport: commit bcf4dd5f9ee096bd1510f838dd4750c35df4e38b Author: Martin SchwidefskyDate: Mon Jun 27 17:06:45 2016 +0200 s390: fix test_fp_ctl inline assembly contraints The test_fp_ctl function is used to test if a given value is a valid floating-point control. The inline assembly in test_fp_ctl uses an incorrect constraint for the 'orig_fpc' variable. If the compiler chooses the same register for 'fpc' and 'orig_fpc' the test_fp_ctl() function always returns true. This allows user space to trigger kernel oopses with invalid floating-point control values on the signal stack. This problem has been introduced with git commit 4725c86055f5bbdcdf "s390: fix save and restore of the floating-point-control register" Cc: sta...@vger.kernel.org # v3.13+ Reviewed-by: Heiko Carstens Signed-off-by: Martin Schwidefsky ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-143266 severity-high targetmilestone-inin1604 -- kernel: signal return with invalid floating-point control https://bugs.launchpad.net/bugs/1597971 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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
[Kernel-packages] [Bug 1597961] Status changed to Confirmed
This change was made by a bot. ** 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/1597961 Title: Qualcomm Atheros Bluetooth 4.0 not working on Ubuntu 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Acer Aspire E15 laptop (model number E5-573-54ZV) with Windows 10 and Bluetooth 4.0 adapter out of the box. While using Windows, I'm able to use the Bluetooth adapter. I've installed Ubuntu 16.04 in dual boot. While using Ubuntu, the Bluetooth adapter is the only piece of hardware that does not work. I've been instructed at Ask Ubuntu to file a bug report against package linux: http://askubuntu.com/q/791785/560233 A report made using AIDA64 for Windows shows: 04CA 3014 Qualcomm Atheros Bluetooth 4.0 I don't know if that helps, but my laptop also has an Atheros Wi-Fi adapter, which the AIDA report shows as Atheros AR9565 802.11b/g/n Wireless Network Adapter, a PCI device with ID 168C-0036. Some more info: $ lspci -knn | grep Net -A2; lsusb 03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01) Subsystem: Lite-On Communications Inc QCA9565 / AR9565 Wireless Network Adapter [11ad:0803] Kernel driver in use: ath9k Kernel modules: ath9k Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 002 Device 004: ID 1bcf:2c81 Sunplus Innovation Technology Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ uname -a Linux viny-notebook 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ dmesg | grep -i bluetooth [ 20.905534] Bluetooth: Core ver 2.21 [ 20.905548] Bluetooth: HCI device and connection manager initialized [ 20.905551] Bluetooth: HCI socket layer initialized [ 20.905553] Bluetooth: L2CAP socket layer initialized [ 20.905557] Bluetooth: SCO socket layer initialized [ 21.477624] Bluetooth: Can't change to loading configuration err [ 21.477654] Bluetooth: Loading patch file failed [ 124.347977] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 124.347980] Bluetooth: BNEP filters: protocol multicast [ 124.347985] Bluetooth: BNEP socket layer initialized ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinicius 1913 F pulseaudio /dev/snd/controlC1: vinicius 1913 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 30 22:27:24 2016 HibernationDevice: RESUME=UUID=8ab51bc9-dd7d-4e30-9c74-696b6bb851ef InstallationDate: Installed on 2016-06-23 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire E5-573 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=216c2bbc-7194-46dc-929e-2a02be497343 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.37 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-573 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597961/+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
[Kernel-packages] [Bug 1597047] phact (amd64) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/phact__3.16.0-77.99~14.04.1__2016-06-30_23-22-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1597047] onza (i386) - tests ran: 4, failed: 0
tests ran: 4, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/onza__3.16.0-77.99~14.04.1__2016-07-01_00-39-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1597047] onza (i386) - tests ran: 3, failed: 0
tests ran: 3, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/onza__3.16.0-77.99~14.04.1__2016-06-30_23-14-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1555786] Re: [Hyper-V] VM with ubuntu 32bit with linux-next does not boot
We have a patch that was created for 32bit and testing it now it's also resolving the upstream 32bit boot issue. Waiting for it to be accepted in upstream, so we should be done with any of the current bisect work. -- 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/1555786 Title: [Hyper-V] VM with ubuntu 32bit with linux-next does not boot Status in linux package in Ubuntu: Triaged Bug description: We identified that at least ubuntu (let's take 15.10) does not boot if installed in the 32bit architecture, and using the linux-next upstream kernel 4.5 on it. This has been seen on other distributions as well. We took both the official linux-next branch from kernel.org and the one from kernel.ubuntu.com v4.5-rc7. For the compilation process we went either with the 4.2 kernel config file from the installed running kernel, and also built the config separately. No errors have been encountered during the build or install process of the 4.5 kernel, however at boot, the VM will just hang. There are no call traces or messages at boot to show any pottential issue. Have you seen this on your end when testing the 32bit build? Attaching the full serial log for reference, however I don't see any errors in the kernel boot process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555786/+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
[Kernel-packages] [Bug 1597047] onza (amd64) - tests ran: 4, failed: 0
tests ran: 4, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/onza__3.16.0-77.99~14.04.1__2016-07-01_00-19-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1597047] onibi (i386) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-76.98~14.04.1/onibi__3.16.0-76.98~14.04.1__2016-06-30_23-07-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1597047] phact (i386) - tests ran: 20, failed: 1
tests ran: 20, failed: 1; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/phact__3.16.0-77.99~14.04.1__2016-06-30_21-43-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1597961] [NEW] Qualcomm Atheros Bluetooth 4.0 not working on Ubuntu 16.04
Public bug reported: Acer Aspire E15 laptop (model number E5-573-54ZV) with Windows 10 and Bluetooth 4.0 adapter out of the box. While using Windows, I'm able to use the Bluetooth adapter. I've installed Ubuntu 16.04 in dual boot. While using Ubuntu, the Bluetooth adapter is the only piece of hardware that does not work. I've been instructed at Ask Ubuntu to file a bug report against package linux: http://askubuntu.com/q/791785/560233 A report made using AIDA64 for Windows shows: 04CA 3014 Qualcomm Atheros Bluetooth 4.0 I don't know if that helps, but my laptop also has an Atheros Wi-Fi adapter, which the AIDA report shows as Atheros AR9565 802.11b/g/n Wireless Network Adapter, a PCI device with ID 168C-0036. Some more info: $ lspci -knn | grep Net -A2; lsusb 03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01) Subsystem: Lite-On Communications Inc QCA9565 / AR9565 Wireless Network Adapter [11ad:0803] Kernel driver in use: ath9k Kernel modules: ath9k Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 002 Device 004: ID 1bcf:2c81 Sunplus Innovation Technology Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ uname -a Linux viny-notebook 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ dmesg | grep -i bluetooth [ 20.905534] Bluetooth: Core ver 2.21 [ 20.905548] Bluetooth: HCI device and connection manager initialized [ 20.905551] Bluetooth: HCI socket layer initialized [ 20.905553] Bluetooth: L2CAP socket layer initialized [ 20.905557] Bluetooth: SCO socket layer initialized [ 21.477624] Bluetooth: Can't change to loading configuration err [ 21.477654] Bluetooth: Loading patch file failed [ 124.347977] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 124.347980] Bluetooth: BNEP filters: protocol multicast [ 124.347985] Bluetooth: BNEP socket layer initialized ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinicius 1913 F pulseaudio /dev/snd/controlC1: vinicius 1913 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 30 22:27:24 2016 HibernationDevice: RESUME=UUID=8ab51bc9-dd7d-4e30-9c74-696b6bb851ef InstallationDate: Installed on 2016-06-23 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire E5-573 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=216c2bbc-7194-46dc-929e-2a02be497343 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.37 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-573 dmi.product.version: V3.72 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1597961 Title: Qualcomm Atheros Bluetooth 4.0 not working on Ubuntu 16.04 Status in linux package in Ubuntu: New Bug description: Acer Aspire E15 laptop (model number E5-573-54ZV) with Windows 10 and Bluetooth 4.0 adapter out of the box. While using Windows, I'm able to use the Bluetooth adapter. I've installed Ubuntu 16.04 in dual boot. While using Ubuntu, the Bluetooth adapter is the only piece of hardware that does not work. I've been instructed at Ask Ubuntu to file a bug report against package linux: http://askubuntu.com/q/791785/560233 A report made using AIDA64 for Windows shows: 04CA 3014 Qualcomm Atheros Bluetooth 4.0 I don't know if that helps, but my laptop also has an Atheros Wi-Fi adapter, which the AIDA report shows as Atheros AR9565 802.11b/g/n Wireless Network Adapter, a PCI device with ID 168C-0036. Some more
[Kernel-packages] [Bug 1597047] alkaid (i386) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/alkaid__3.16.0-77.99~14.04.1__2016-06-30_23-15-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1597908] Re: linux-kernel: Freeing IRQ from IRQ context
I built a Xenial test kernel with a pick of commit: 287922eb0b The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1597908/ Can you test this kernel and see if it resolves 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/1597908 Title: linux-kernel: Freeing IRQ from IRQ context Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: It looks like the Ubuntu 16.04 took the nvme driver from 4.5 kernel, but is missing some critical block updates that it was depending on. Specifically this one moving the timeout handler to a work queue instead of a irq context timer task: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=287922eb0b186e2a5bf54fdd04b734c25c90035c This mismatch causes lots of warnings and errors during recovery from failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597908/+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
[Kernel-packages] [Bug 1597047] alkaid (amd64) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/alkaid__3.16.0-77.99~14.04.1__2016-06-30_22-24-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1597047] onza (amd64) - tests ran: 30, failed: 1
tests ran: 30, failed: 1; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/onza__3.16.0-77.99~14.04.1__2016-06-30_22-07-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1597047] onibi (amd64) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/onibi__3.16.0-77.99~14.04.1__2016-06-30_22-03-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1597895] Re: i915 crashes, lightdm unresponsive and VT switching impossible
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc5-yakkety/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1597895 Title: i915 crashes, lightdm unresponsive and VT switching impossible Status in linux package in Ubuntu: Incomplete Bug description: Some times after locking the screen and waking it up some time later via Fn (XF86WakeUp) lightdm accepts no input and Ctrl+Alt+Fx no longer work to switch to another VT. This is not always reproducible but I think it's triggered by clicking on lightdm's login dialog before it's ready. What usually happens when I wake up the screen: - the screen shows the lightdm dialog without a blinking cursor for a second - screen turns black (off?) for a second, as if its resolution changes - screen comes back, shows lightdm dialog, cursor begins to blink I will try to reproduce by clicking on the dialog before the screen goes black soon. This may be related to https://bugs.launchpad.net/ubuntu/+source /xserver-xorg-video-intel/+bug/1568604 - which affects my installation, too. Here's the relevant snippet from /var/log/syslog, I pressed the power button a few seconds after realizing the lock up: Jun 30 16:24:26 sbooblehat lightdm[4225]: ** (lightdm:4225): WARNING **: Error using VT_WAITACTIVE 7 on /dev/tty0: Interrupted system call Jun 30 16:24:26 sbooblehat org.gtk.vfs.Daemon[16609]: A connection to the bus can't be made Jun 30 16:24:28 sbooblehat acpid: client 16583[0:0] has disconnected Jun 30 16:24:29 sbooblehat systemd[1]: Started Getty on tty6. Jun 30 16:24:46 sbooblehat systemd[1]: Stopping User Manager for UID 108... Jun 30 16:24:46 sbooblehat systemd[16595]: Reached target Shutdown. Jun 30 16:24:46 sbooblehat systemd[16595]: Starting Exit the Session... Jun 30 16:24:46 sbooblehat systemd[16595]: Stopped target Default. Jun 30 16:24:46 sbooblehat systemd[16595]: Stopped target Basic System. Jun 30 16:24:46 sbooblehat systemd[16595]: Stopped target Paths. Jun 30 16:24:46 sbooblehat systemd[16595]: Stopped target Timers. Jun 30 16:24:46 sbooblehat systemd[16595]: Stopped target Sockets. Jun 30 16:24:46 sbooblehat systemd[16595]: Received SIGRTMIN+24 from PID 19198 (kill). Jun 30 16:24:46 sbooblehat systemd[1]: Stopped User Manager for UID 108. Jun 30 16:24:46 sbooblehat systemd[1]: Removed slice User Slice of lightdm. Jun 30 16:25:01 sbooblehat CRON[19216]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Jun 30 16:29:41 sbooblehat acpid: client connected from 19395[0:0] Jun 30 16:29:41 sbooblehat kernel: [23583.257132] [ cut here ] Jun 30 16:29:41 sbooblehat kernel: [23583.257170] WARNING: CPU: 2 PID: 4240 at /build/linux-BvkamA/linux-4.4.0/drivers/gpu/drm/drm_irq.c:1326 drm_wait_one_vblank+0x1b5/0x1c0 [drm]() Jun 30 16:29:41 sbooblehat kernel: [23583.257170] vblank wait timed out on crtc 0 Jun 30 16:29:41 sbooblehat kernel: [23583.257206] Modules linked in: rfcomm xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs bnep qmi_wwan cdc_wdm usbnet mii nls_iso8859_1 arc4 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media btusb btrtl btbcm btintel bluetooth qcserial usb_wwan usbserial intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul snd_hda_codec_hdmi snd_hda_codec_conexant ath9k snd_hda_codec_generic ath9k_common ath9k_hw snd_hda_intel snd_hda_codec input_leds snd_hda_core joydev snd_hwdep ath serio_raw mac80211 snd_pcm cfg80211 lpc_ich thinkpad_acpi nvram sn d_seq_midi snd_seq_midi_event mei_me shpchp mei snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore mac_hid kvm_intel kvm irqbypass ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp
[Kernel-packages] [Bug 1597908] Re: linux-kernel: Freeing IRQ from IRQ context
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Importance: Medium => High ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Xenial) 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/1597908 Title: linux-kernel: Freeing IRQ from IRQ context Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: It looks like the Ubuntu 16.04 took the nvme driver from 4.5 kernel, but is missing some critical block updates that it was depending on. Specifically this one moving the timeout handler to a work queue instead of a irq context timer task: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=287922eb0b186e2a5bf54fdd04b734c25c90035c This mismatch causes lots of warnings and errors during recovery from failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597908/+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
[Kernel-packages] [Bug 1567602] syslog for 445
Default Comment by Bridge ** Attachment added: "syslog for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693108/+files/445_syslog -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]:
[Kernel-packages] [Bug 1567602] partman for 445
Default Comment by Bridge ** Attachment added: "partman for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693151/+files/445_partman -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]:
[Kernel-packages] [Bug 1567602] syslog for 445, 2nd run
Default Comment by Bridge ** Attachment added: "syslog for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693124/+files/445_syslog_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] syslog for 445
Default Comment by Bridge ** Attachment added: "syslog for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693116/+files/445_syslog -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]:
[Kernel-packages] [Bug 1597573] Re: Network installer fails to detect network on AMD Overdrive (ARM64)
Do you plan on submitting your patch to the kernel team mainline list, kernel-t...@lists.ubuntu.com? ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => Medium ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Yakkety) Status: Confirmed => 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/1597573 Title: Network installer fails to detect network on AMD Overdrive (ARM64) Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Yakkety: Triaged Bug description: Kernel: 4.4.0-21.37 (xenial) Installer fails to detect the XGBE network interface on AMD Overdrive, making it impossible to proceed with the network installer. Checking the kernel udeb modules, we're missing amd-xgbe as part of nic-modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597573/+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
[Kernel-packages] [Bug 1567602] partman for 445, 2nd run
Default Comment by Bridge ** Attachment added: "partman for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693133/+files/445_partman_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] failing IPL after multipath installation
Default Comment by Bridge ** Attachment added: "failing IPL after multipath installation" https://bugs.launchpad.net/bugs/1567602/+attachment/4693127/+files/FCP_MP_reIPL_console.txt -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd'
[Kernel-packages] [Bug 1567602] partman for 445
Default Comment by Bridge ** Attachment added: "partman for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693173/+files/445_partman -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]:
[Kernel-packages] [Bug 1567602] partman for 445, 2nd run
Default Comment by Bridge ** Attachment added: "partman for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693168/+files/445_partman_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] failing IPL after multipath installation
Default Comment by Bridge ** Attachment added: "failing IPL after multipath installation" https://bugs.launchpad.net/bugs/1567602/+attachment/4693148/+files/FCP_MP_reIPL_console.txt -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd'
[Kernel-packages] [Bug 1567602] failing IPL after multipath installation
Default Comment by Bridge ** Attachment added: "failing IPL after multipath installation" https://bugs.launchpad.net/bugs/1567602/+attachment/4693106/+files/FCP_MP_reIPL_console.txt -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd'
[Kernel-packages] [Bug 1567602] syslog for 445, 2nd run
Default Comment by Bridge ** Attachment added: "syslog for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693153/+files/445_syslog_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] hw-summary for 445
Default Comment by Bridge ** Attachment added: "hw-summary for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693144/+files/445_hardware-summary -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] syslog for 445, 2nd run
Default Comment by Bridge ** Attachment added: "syslog for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693161/+files/445_syslog_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] failing IPL after multipath installation
Default Comment by Bridge ** Attachment added: "failing IPL after multipath installation" https://bugs.launchpad.net/bugs/1567602/+attachment/4693143/+files/FCP_MP_reIPL_console.txt -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd'
[Kernel-packages] [Bug 1567602] syslog for 445
Default Comment by Bridge ** Attachment added: "syslog for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693172/+files/445_syslog -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]:
[Kernel-packages] [Bug 1567602] hw-summary for 445
Default Comment by Bridge ** Attachment added: "hw-summary for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693110/+files/445_hardware-summary -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] hw-summary
Default Comment by Bridge ** Attachment added: "hw-summary" https://bugs.launchpad.net/bugs/1567602/+attachment/4693107/+files/hardware-summary -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]:
[Kernel-packages] [Bug 1567602] hw-summary for 445, 2nd run
Default Comment by Bridge ** Attachment added: "hw-summary for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693126/+files/445_hardware-summary_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6
[Kernel-packages] [Bug 1567602] partman for 445
Default Comment by Bridge ** Attachment added: "partman for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693117/+files/445_partman -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]:
[Kernel-packages] [Bug 1567602] hw-summary for 445, 2nd run
Default Comment by Bridge ** Attachment added: "hw-summary for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693147/+files/445_hardware-summary_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6
[Kernel-packages] [Bug 1567602] hw-summary
Default Comment by Bridge ** Attachment added: "hw-summary" https://bugs.launchpad.net/bugs/1567602/+attachment/4693157/+files/hardware-summary -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]:
[Kernel-packages] [Bug 1597908] Re: linux-kernel: Freeing IRQ from IRQ context
This system crashes making apport-collect not possible after the fact, though I confirm it is a bug. As the upstream nvme driver maintainer, I can recommend either which driver commits need to be reverted, or which kernel commit needs to be cherry-picked (preferring the latter :)). Here is a snippet of stack trace: <3>[51827.132142] BUG: scheduling while atomic: swapper/19/0/0x0100 <4>[51827.242686] Modules linked in: nvme binfmt_misc PlxSvc(OE) ipmi_devintf intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm irqbypass input_leds joydev sb_edac ipmi_ssif edac_core mei_me mei lpc_ich ioatdma shpchp ipmi_si ipmi_msghandler 8250_fintek acpi_pad acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear igb dca ptp ahci crct10dif_pclmul crc32_pclmul hid_generic mxm_wmi aesni_intel aes_x86_64 lrw gf128mul usbhid glue_helper ablk_helper pps_core cryptd hid libahci i2c_algo_bit fjes wmi <4>[51827.242743] CPU: 19 PID: 0 Comm: swapper/19 Tainted: GW OE 4.4.0-24-generic #43-Ubuntu <4>[51827.242746] Hardware name: Intel Corporation S2600WT2/S2600WT2, BIOS SE5C610.86B.11.01.0132.060620160917 06/06/2016 <4>[51827.242748] 0286 374975818f2884ca 88105de43a98 813eab23 <4>[51827.242752] 88105de56d00 88105de43aa8 810a5ceb <4>[51827.242762] 88105de43af8 818217d6 88105de43ac8 374975810013 <4>[51827.242765] Call Trace: <4>[51827.242768][] dump_stack+0x63/0x90 <4>[51827.242781] [] __schedule_bug+0x4b/0x60 <4>[51827.242788] [] __schedule+0x726/0xa30 <4>[51827.242792] [] schedule+0x35/0x80 <4>[51827.242797] [] schedule_timeout+0x129/0x270 <4>[51827.242802] [] ? trace_event_raw_event_tick_stop+0x120/0x120 <4>[51827.242807] [] msleep+0x2d/0x40 <4>[51827.242813] [] nvme_wait_ready+0x90/0x100 [nvme] <4>[51827.242818] [] nvme_disable_ctrl+0x40/0x50 [nvme] <4>[51827.242823] [] nvme_disable_admin_queue+0x8d/0x90 [nvme] <4>[51827.242828] [] nvme_dev_disable+0x29e/0x2c0 [nvme] <4>[51827.242833] [] ? __nvme_process_cq+0x200/0x200 [nvme] <4>[51827.242838] [] ? dev_warn+0x6c/0x90 <4>[51827.242843] [] nvme_timeout+0x110/0x1d0 [nvme] <4>[51827.242847] [] ? cpumask_next_and+0x2f/0x40 <4>[51827.242850] [] ? load_balance+0x18c/0x980 <4>[51827.242854] [] blk_mq_rq_timed_out+0x2f/0x70 <4>[51827.242857] [] blk_mq_check_expired+0x4e/0x80 <4>[51827.242861] [] bt_for_each+0xd8/0xe0 <4>[51827.242864] [] ? blk_mq_rq_timed_out+0x70/0x70 <4>[51827.242868] [] ? blk_mq_rq_timed_out+0x70/0x70 <4>[51827.242871] [] blk_mq_queue_tag_busy_iter+0x47/0xc0 <4>[51827.242875] [] ? blk_mq_attempt_merge+0xb0/0xb0 <4>[51827.242878] [] blk_mq_rq_timer+0x41/0xf0 <4>[51827.242882] [] call_timer_fn+0x35/0x120 <4>[51827.242885] [] ? blk_mq_attempt_merge+0xb0/0xb0 <4>[51827.242890] [] run_timer_softirq+0x23a/0x2f0 <4>[51827.242894] [] __do_softirq+0x101/0x290 <4>[51827.242899] [] irq_exit+0xa3/0xb0 <4>[51827.242902] [] smp_apic_timer_interrupt+0x42/0x50 <4>[51827.242905] [] apic_timer_interrupt+0x82/0x90 <4>[51827.242907][] ? cpuidle_enter_state+0x111/0x2b0 <4>[51827.242914] [] cpuidle_enter+0x17/0x20 <4>[51827.242918] [] call_cpuidle+0x32/0x60 <4>[51827.242921] [] ? cpuidle_select+0x13/0x20 <4>[51827.242925] [] cpu_startup_entry+0x290/0x350 <4>[51827.242929] [] start_secondary+0x154/0x190 <3>[51827.242934] bad: scheduling from the idle thread! ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1597908 Title: linux-kernel: Freeing IRQ from IRQ context Status in linux package in Ubuntu: Confirmed Bug description: It looks like the Ubuntu 16.04 took the nvme driver from 4.5 kernel, but is missing some critical block updates that it was depending on. Specifically this one moving the timeout handler to a work queue instead of a irq context timer task: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=287922eb0b186e2a5bf54fdd04b734c25c90035c This mismatch causes lots of warnings and errors during recovery from failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597908/+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
[Kernel-packages] [Bug 1567602] failing IPL after multipath installation
Default Comment by Bridge ** Attachment added: "failing IPL after multipath installation" https://bugs.launchpad.net/bugs/1567602/+attachment/4693178/+files/FCP_MP_reIPL_console.txt -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd'
[Kernel-packages] [Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu
Thanks, John. I copied all the test kernels back to: http://kernel.ubuntu.com/~jsalisbury/lp1571798/ Each test kernel is under the corresponding SHA1. -- 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/1571798 Title: Broadwell ECRC Support missing in Ubuntu Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: Here is the problem statement from the Dell team: When booting into Ubuntu 14.04.4 with a Broadwell CPU and an Intel Quick Assist Card, the memory location that corresponds to ECRC is set to 0x01e0, when the BIOS is setting this location 0x00a0 pre-OS boot. This causes the card to not function unless we implement the following workaround using setpci. “setpci –s AA:BB.C 160.w=0”, where AA:BB.C is the PCI Root Path for the Intel Quick Assit Card. We’ve verified the memory location is correct when booting to other OSes, such as RHEL 7.2 and Windows Server 2012 R2. If there is any information you can give as to why this may be occurring in Ubuntu or where we may start to debug when the memory is changed, we would appreciate it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571798/+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
[Kernel-packages] [Bug 1567602] syslog for 445
Default Comment by Bridge ** Attachment added: "syslog for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693137/+files/445_syslog -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]:
[Kernel-packages] [Bug 1567602] syslog for 445, 2nd run
Default Comment by Bridge ** Attachment added: "syslog for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693119/+files/445_syslog_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] hw-summary for 445, 2nd run
Default Comment by Bridge ** Attachment added: "hw-summary for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693163/+files/445_hardware-summary_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6
[Kernel-packages] [Bug 1567602] syslog for 445, 2nd run
Default Comment by Bridge ** Attachment added: "syslog for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693140/+files/445_syslog_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] hw-summary for 445
Default Comment by Bridge ** Attachment added: "hw-summary for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693118/+files/445_hardware-summary -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] hw-summary for 445, 2nd run
Default Comment by Bridge ** Attachment added: "hw-summary for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693113/+files/445_hardware-summary_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6
[Kernel-packages] [Bug 1567602] syslog for 445, 2nd run
Default Comment by Bridge ** Attachment added: "syslog for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693111/+files/445_syslog_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] hw-summary for 445, 2nd run
Default Comment by Bridge ** Attachment added: "hw-summary for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693121/+files/445_hardware-summary_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6
[Kernel-packages] [Bug 1597047] onza (i386) - tests ran: 10, failed: 0
tests ran: 10, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/onza__3.16.0-77.99~14.04.1__2016-06-30_20-56-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1567602] hw-summary for 445, 2nd run
Default Comment by Bridge ** Attachment added: "hw-summary for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693134/+files/445_hardware-summary_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6
[Kernel-packages] [Bug 1567602] failing IPL after multipath installation
Default Comment by Bridge ** Attachment added: "failing IPL after multipath installation" https://bugs.launchpad.net/bugs/1567602/+attachment/4693135/+files/FCP_MP_reIPL_console.txt -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd'
[Kernel-packages] [Bug 1567602] partman for 445, 2nd run
Default Comment by Bridge ** Attachment added: "partman for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693120/+files/445_partman_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] syslog for 445, 2nd run
Default Comment by Bridge ** Attachment added: "syslog for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693132/+files/445_syslog_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] partman for 445
Default Comment by Bridge ** Attachment added: "partman for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693109/+files/445_partman -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]:
[Kernel-packages] [Bug 1597574] Re: Config: missing AMD Seattle platform support
Do you plan on submitting your patch to the kernel team mainline list, kernel-t...@lists.ubuntu.com? ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Yakkety) Status: Confirmed => Triaged ** Tags added: kernel-da-key -- 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/1597574 Title: Config: missing AMD Seattle platform support Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Yakkety: Triaged Bug description: Kernel: 4.4.0-28.47 debian.master/config/config.common.ubuntu: # CONFIG_ARCH_SEATTLE is not set The AMD Seattle SoC is used by the AMD Overdrive board and LeMaker Cello. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597574/+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
[Kernel-packages] [Bug 1567602] hw-summary for 445
Default Comment by Bridge ** Attachment added: "hw-summary for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693123/+files/445_hardware-summary -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] hw-summary for 445
Default Comment by Bridge ** Attachment added: "hw-summary for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693139/+files/445_hardware-summary -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] syslog for 445
Default Comment by Bridge ** Attachment added: "syslog for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693129/+files/445_syslog -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]:
[Kernel-packages] [Bug 1567602] partman for 445, 2nd run
Default Comment by Bridge ** Attachment added: "partman for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693176/+files/445_partman_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] partman for 445, 2nd run
Default Comment by Bridge ** Attachment added: "partman for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693154/+files/445_partman_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] hw-summary
Default Comment by Bridge ** Attachment added: "hw-summary" https://bugs.launchpad.net/bugs/1567602/+attachment/4693128/+files/hardware-summary -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]:
[Kernel-packages] [Bug 1567602] partman for 445, 2nd run
Default Comment by Bridge ** Attachment added: "partman for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693162/+files/445_partman_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1597047] phact (amd64) - tests ran: 20, failed: 0
tests ran: 20, failed: 0; http://kernel.ubuntu.com/testing/3.16.0-77.99~14.04.1/phact__3.16.0-77.99~14.04.1__2016-06-30_20-10-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1597047 Title: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-77.99~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1597047/+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
[Kernel-packages] [Bug 1567602] hw-summary
Default Comment by Bridge ** Attachment added: "hw-summary" https://bugs.launchpad.net/bugs/1567602/+attachment/4693115/+files/hardware-summary -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]:
[Kernel-packages] [Bug 1567602] hw-summary for 445
Default Comment by Bridge ** Attachment added: "hw-summary for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693131/+files/445_hardware-summary -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] failing IPL after multipath installation
Default Comment by Bridge ** Attachment added: "failing IPL after multipath installation" https://bugs.launchpad.net/bugs/1567602/+attachment/4693122/+files/FCP_MP_reIPL_console.txt -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd'
[Kernel-packages] [Bug 1567602] failing IPL after multipath installation
Default Comment by Bridge ** Attachment added: "failing IPL after multipath installation" https://bugs.launchpad.net/bugs/1567602/+attachment/4693114/+files/FCP_MP_reIPL_console.txt -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd'
[Kernel-packages] [Bug 1567602] partman for 445, 2nd run
Default Comment by Bridge ** Attachment added: "partman for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693125/+files/445_partman_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] partman for 445
Default Comment by Bridge ** Attachment added: "partman for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693130/+files/445_partman -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]:
[Kernel-packages] [Bug 1567602] failing IPL after multipath installation
Default Comment by Bridge ** Attachment added: "failing IPL after multipath installation" https://bugs.launchpad.net/bugs/1567602/+attachment/4693156/+files/FCP_MP_reIPL_console.txt -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd'
[Kernel-packages] [Bug 1567602] partman for 445, 2nd run
Default Comment by Bridge ** Attachment added: "partman for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693112/+files/445_partman_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] hw-summary for 445
Default Comment by Bridge ** Attachment added: "hw-summary for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693152/+files/445_hardware-summary -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] hw-summary for 445, 2nd run
Default Comment by Bridge ** Attachment added: "hw-summary for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693177/+files/445_hardware-summary_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6
[Kernel-packages] [Bug 1567602] failing IPL after multipath installation
Default Comment by Bridge ** Attachment added: "failing IPL after multipath installation" https://bugs.launchpad.net/bugs/1567602/+attachment/4693170/+files/FCP_MP_reIPL_console.txt -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd'
[Kernel-packages] [Bug 1567602] hw-summary for 445, 2nd run
Default Comment by Bridge ** Attachment added: "hw-summary for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693169/+files/445_hardware-summary_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6
[Kernel-packages] [Bug 1567602] hw-summary for 445
Default Comment by Bridge ** Attachment added: "hw-summary for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693174/+files/445_hardware-summary -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] hw-summary for 445
Default Comment by Bridge ** Attachment added: "hw-summary for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693160/+files/445_hardware-summary -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] hw-summary
Default Comment by Bridge ** Attachment added: "hw-summary" https://bugs.launchpad.net/bugs/1567602/+attachment/4693149/+files/hardware-summary -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]:
[Kernel-packages] [Bug 1567602] syslog for 445, 2nd run
Default Comment by Bridge ** Attachment added: "syslog for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693175/+files/445_syslog_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10
[Kernel-packages] [Bug 1567602] partman for 445
Default Comment by Bridge ** Attachment added: "partman for 445" https://bugs.launchpad.net/bugs/1567602/+attachment/4693159/+files/445_partman -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10 s390-dasd[6877]:
[Kernel-packages] [Bug 1567602] failing IPL after multipath installation
Default Comment by Bridge ** Attachment added: "failing IPL after multipath installation" https://bugs.launchpad.net/bugs/1567602/+attachment/4693164/+files/FCP_MP_reIPL_console.txt -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd'
[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
I built the next test kernel, up to the following commit: ddc8f6feec76b5deea8090db015920a283006044 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1573062 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- 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/1573062 Title: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: memory_stress_ng, as part of server certification is failing for IBM Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is defined by the test locking up the server in an unrecoverable state which only a reboot will fix. I will be attaching screen and kern logs for the failures and a successful run on 14.04 on the same server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+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
[Kernel-packages] [Bug 1567602] syslog for 445, 2nd run
Default Comment by Bridge ** Attachment added: "syslog for 445, 2nd run" https://bugs.launchpad.net/bugs/1567602/+attachment/4693166/+files/445_syslog_2 -- 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 Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: 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 In that case do not use NPIV enabled zfcp adaptors. Scenario: Using Installer 432. No DASD devices, just two FCP CHPIDs with two LUNs each (configured for NPIV), provided via parmfile. I expect the installer to probe and detect the LUNs automatically once I enable the FCP CHPIDs. Repeated five times, I got different results each time. Detected LUNs vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2 which looks especially odd to me. Subsequent steps to create partitions and file systems in the installer fail. Following is one of the five cases with more details: After enabling CHPID 192b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 226.895139] scsi 0:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS [ 226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off [ 226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08 [ 226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk [ 287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3 [ 287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22) [ 287.117064] sd 0:0:0:1077493890: failed to add device handler: -22 [ 287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted As second step, I additionally enable CHPID 196b: ~ # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890 Vendor: IBM Model: 2107900 Rev: 1.27 Type: Direct-AccessANSI SCSI revision: 05 dmesg showing: [ 384.277394] scsi host1: zfcp [ 384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A [ 385.377511] scsi 1:0:0:1077493890: Direct-Access IBM 2107900 1.27 PQ: 0 ANSI: 5 [ 385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS [ 385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB) [ 385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off [ 385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08 [ 385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk [ 446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3 [ 446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22) [ 446.117048] sd 1:0:0:1077493890: failed to add device handler: -22 [ 446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while scanning, scan aborted Next, the installer warns that no disk drives were detected. I checked this on a system (installer 445) with two NPIV enabled FCP devices that have 4 LUNS each. I only get the first of four LUNs per adaptor: Apr 6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2 Apr 6 12:57:08 anna[2607]: 2016-04-06 12:57:08 URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1] Apr 6 12:57:09 main-menu[384]: INFO: Menu item 'driver-injection-disk-detect' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected Apr 6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected Apr 6 12:57:10