[Kernel-packages] [Bug 1917471] Re: [SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which causes Bus Fatal Error when rebooting system with BCM5720 NIC
>https://people.canonical.com/~khfeng/tg3-poweroff/
This one does not show the issue.
--
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/1917471
Title:
[SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which
causes Bus Fatal Error when rebooting system with BCM5720 NIC
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
[IMPACT]
This is being reported by a hardware partner as it is being noticed a
lot both in their internal testing teams and also being reported with
some frequency by customers who are seeing these messages in their
logs and thus it is generating an unusualy high volume of support
calls from the field.
In 5.4, commit d60cd06331a3566d3305b3c7b566e79edf4e2095 was introduced
upstream and pulled into Ubuntu between 5.4.0-58.64 and 5.4.0-59.65.
Upstream, these errors were discovered and that patch was reverted
(see Fix Below). We carry the revert commit in all subsequent Focal
HWE kernels starting at 5.12, but the fix was never pulled back into
Focal 5.4.
according to the hardware partner:
the following error messages are observed when rebooting a machine
that uses the BCM5720 chipset, which is a widely used 1GbE controller
found on LOMs and OCP NICs as well as many PCIe NIC models.
[ 146.429212] shutdown[1]: Rebooting.
[ 146.435151] kvm: exiting hardware virtualization
[ 146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is
called outbound_intr_mask:0x4009
[ 148.088133] [qede_unload:2236(eno12409)]Link is down
[ 148.183618] qede :31:00.1: Ending qede_remove successfully
[ 148.518541] [qede_unload:2236(eno12399)]Link is down
[ 148.625066] qede :31:00.0: Ending qede_remove successfully
[ 148.762067] ACPI: Preparing to enter system sleep state S5
[ 148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 5
[ 148.803731] {1}[Hardware Error]: event severity: recoverable
[ 148.810191] {1}[Hardware Error]: Error 0, type: fatal
[ 148.816088] {1}[Hardware Error]: section_type: PCIe error
[ 148.822391] {1}[Hardware Error]: port_type: 0, PCIe end point
[ 148.829026] {1}[Hardware Error]: version: 3.0
[ 148.834266] {1}[Hardware Error]: command: 0x0006, status: 0x0010
[ 148.841140] {1}[Hardware Error]: device_id: :04:00.0
[ 148.847309] {1}[Hardware Error]: slot: 0
[ 148.852077] {1}[Hardware Error]: secondary_bus: 0x00
[ 148.857876] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f
[ 148.865145] {1}[Hardware Error]: class_code: 02
[ 148.870845] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x0001
[ 148.879842] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
[ 148.886575] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
[ 148.894823] tg3 :04:00.0: AER: aer_status: 0x0010, aer_mask:
0x0001
[ 148.902795] tg3 :04:00.0: AER:[20] UnsupReq (First)
[ 148.910234] tg3 :04:00.0: AER: aer_layer=Transaction Layer,
aer_agent=Requester ID
[ 148.918806] tg3 :04:00.0: AER: aer_uncor_severity: 0x000ef030
[ 148.925558] tg3 :04:00.0: AER: TLP Header: 4001 030f
90028090
[ 148.933984] reboot: Restarting system
[ 148.938319] reboot: machine restart
The hardware partner did some bisection and observed the following:
Kernel version Fatal Error
5.4.0-42.46 No
5.4.0-45.49 No
5.4.0-47.51 No
5.4.0-48.52 No
5.4.0-51.56 No
5.4.0-52.57 No
5.4.0-53.59 No
5.4.0-54.60 No
5.4.0-58.64 No
5.4.0-59.65 yes
5.4.0-60.67 yes
[FIX]
The fix is to apply this patch from upstream:
commit 9d3fcb28f9b9750b474811a2964ce022df56336e
Author: Josef Bacik
Date: Tue Mar 16 22:17:48 2021 -0400
Revert "PM: ACPI: reboot: Use S5 for reboot"
This reverts commit d60cd06331a3566d3305b3c7b566e79edf4e2095.
This patch causes a panic when rebooting my Dell Poweredge r440. I do
not have the full panic log as it's lost at that stage of the reboot and
I do not have a serial console. Reverting this patch makes my system
able to reboot again.
Example:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1917471
The hardware partner has preemptively pulled our 5.4 tree, applied the
fix and tested it in their labs and determined that this does resolve
the issue.
[TEST CASE]
Install the patched kernel on a machine that uses a BCM5720 LOM and reboot
the machine and see that the errors no longer appear.
To manage notifications about this bug go to:
https://bugs.lau
[Kernel-packages] [Bug 1971151] Re: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
@Sumit - Any update on the above query? -- 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/1971151 Title: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: In Progress Bug description: Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h dde822e21700 scsi: mpi3mr: Update driver version to 8.0.0.69.0 04dfa01e77ea scsi: mpi3mr: Add support for NVMe passthrough 937a6f2c4f2e scsi: mpi3mr: Expose adapter state to sysfs 83959ce5204a scsi: mpi3mr: Add support for PEL commands eb8a3217cd7d scsi: mpi3mr: Add support for MPT commands 455aac4f7a13 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header a212ebe7d4b1 scsi: mpi3mr: Add support for driver commands 7fbaf8b0d8b8 scsi: mpi3mr: Add bsg device support Thanks, Sumit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+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 1917471] Re: [SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which causes Bus Fatal Error when rebooting system with BCM5720 NIC
>https://people.canonical.com/~khfeng/clear-bus-master/
We see the original issue with this kernel.
--
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/1917471
Title:
[SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which
causes Bus Fatal Error when rebooting system with BCM5720 NIC
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
[IMPACT]
This is being reported by a hardware partner as it is being noticed a
lot both in their internal testing teams and also being reported with
some frequency by customers who are seeing these messages in their
logs and thus it is generating an unusualy high volume of support
calls from the field.
In 5.4, commit d60cd06331a3566d3305b3c7b566e79edf4e2095 was introduced
upstream and pulled into Ubuntu between 5.4.0-58.64 and 5.4.0-59.65.
Upstream, these errors were discovered and that patch was reverted
(see Fix Below). We carry the revert commit in all subsequent Focal
HWE kernels starting at 5.12, but the fix was never pulled back into
Focal 5.4.
according to the hardware partner:
the following error messages are observed when rebooting a machine
that uses the BCM5720 chipset, which is a widely used 1GbE controller
found on LOMs and OCP NICs as well as many PCIe NIC models.
[ 146.429212] shutdown[1]: Rebooting.
[ 146.435151] kvm: exiting hardware virtualization
[ 146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is
called outbound_intr_mask:0x4009
[ 148.088133] [qede_unload:2236(eno12409)]Link is down
[ 148.183618] qede :31:00.1: Ending qede_remove successfully
[ 148.518541] [qede_unload:2236(eno12399)]Link is down
[ 148.625066] qede :31:00.0: Ending qede_remove successfully
[ 148.762067] ACPI: Preparing to enter system sleep state S5
[ 148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 5
[ 148.803731] {1}[Hardware Error]: event severity: recoverable
[ 148.810191] {1}[Hardware Error]: Error 0, type: fatal
[ 148.816088] {1}[Hardware Error]: section_type: PCIe error
[ 148.822391] {1}[Hardware Error]: port_type: 0, PCIe end point
[ 148.829026] {1}[Hardware Error]: version: 3.0
[ 148.834266] {1}[Hardware Error]: command: 0x0006, status: 0x0010
[ 148.841140] {1}[Hardware Error]: device_id: :04:00.0
[ 148.847309] {1}[Hardware Error]: slot: 0
[ 148.852077] {1}[Hardware Error]: secondary_bus: 0x00
[ 148.857876] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f
[ 148.865145] {1}[Hardware Error]: class_code: 02
[ 148.870845] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x0001
[ 148.879842] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
[ 148.886575] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
[ 148.894823] tg3 :04:00.0: AER: aer_status: 0x0010, aer_mask:
0x0001
[ 148.902795] tg3 :04:00.0: AER:[20] UnsupReq (First)
[ 148.910234] tg3 :04:00.0: AER: aer_layer=Transaction Layer,
aer_agent=Requester ID
[ 148.918806] tg3 :04:00.0: AER: aer_uncor_severity: 0x000ef030
[ 148.925558] tg3 :04:00.0: AER: TLP Header: 4001 030f
90028090
[ 148.933984] reboot: Restarting system
[ 148.938319] reboot: machine restart
The hardware partner did some bisection and observed the following:
Kernel version Fatal Error
5.4.0-42.46 No
5.4.0-45.49 No
5.4.0-47.51 No
5.4.0-48.52 No
5.4.0-51.56 No
5.4.0-52.57 No
5.4.0-53.59 No
5.4.0-54.60 No
5.4.0-58.64 No
5.4.0-59.65 yes
5.4.0-60.67 yes
[FIX]
The fix is to apply this patch from upstream:
commit 9d3fcb28f9b9750b474811a2964ce022df56336e
Author: Josef Bacik
Date: Tue Mar 16 22:17:48 2021 -0400
Revert "PM: ACPI: reboot: Use S5 for reboot"
This reverts commit d60cd06331a3566d3305b3c7b566e79edf4e2095.
This patch causes a panic when rebooting my Dell Poweredge r440. I do
not have the full panic log as it's lost at that stage of the reboot and
I do not have a serial console. Reverting this patch makes my system
able to reboot again.
Example:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1917471
The hardware partner has preemptively pulled our 5.4 tree, applied the
fix and tested it in their labs and determined that this does resolve
the issue.
[TEST CASE]
Install the patched kernel on a machine that uses a BCM5720 LOM and reboot
the machine and see that the errors no longer appear.
To manage notifications about this bug go to:
ht
[Kernel-packages] [Bug 1982104] Re: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes
** Description changed: [Impact] - Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server which is targeting Telco workloads. + Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server. Attaching the console logs. Currently, it looks like disabling VT-D option in BIOS settings helps mitigate the issue. Console logs indicate something is wrong in iommu/dmar subsystem. [Fix] The IOMMU driver shares the pasid table for PCI alias devices. When the RID2PASID entry of the shared pasid table has been filled by the first device, the subsequent device will encounter the "DMAR: Setup RID2PASID failed" failure as the pasid entry has already been marked as present. As the result, the IOMMU probing process will be aborted. On the contrary, when any alias device is hot-removed from the system, for example, by writing to /sys/bus/pci/devices/.../remove, the shared RID2PASID will be cleared without any notifications to other devices. As the result, any DMAs from those rest devices are blocked. Sharing pasid table among PCI alias devices could save two memory pages for devices underneath the PCIe-to-PCI bridges. Anyway, considering that those devices are rare on modern platforms that support VT-d in scalable mode and the saved memory is negligible, it's reasonable to remove this part of immature code to make the driver feasible and stable. [Test Case] 1. use the target machine(Intel Sapphire Rapids) and install the kernel with the fix. 2. boot the target machine 3. check dmesg if the error message exists [ 8.120527] pci :03:01.0: DMAR: Setup RID2PASID failed [Where problems could occur] After enable intel_iommu, the errors may be occurred. We need to figure out one by one once the related errors are triggered in the future. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1982104 Title: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server. Attaching the console logs. Currently, it looks like disabling VT-D option in BIOS settings helps mitigate the issue. Console logs indicate something is wrong in iommu/dmar subsystem. [Fix] The IOMMU driver shares the pasid table for PCI alias devices. When the RID2PASID entry of the shared pasid table has been filled by the first device, the subsequent device will encounter the "DMAR: Setup RID2PASID failed" failure as the pasid entry has already been marked as present. As the result, the IOMMU probing process will be aborted. On the contrary, when any alias device is hot-removed from the system, for example, by writing to /sys/bus/pci/devices/.../remove, the shared RID2PASID will be cleared without any notifications to other devices. As the result, any DMAs from those rest devices are blocked. Sharing pasid table among PCI alias devices could save two memory pages for devices underneath the PCIe-to-PCI bridges. Anyway, considering that those devices are rare on modern platforms that support VT-d in scalable mode and the saved memory is negligible, it's reasonable to remove this part of immature code to make the driver feasible and stable. [Test Case] 1. use the target machine(Intel Sapphire Rapids) and install the kernel with the fix. 2. boot the target machine 3. check dmesg if the error message exists [ 8.120527] pci :03:01.0: DMAR: Setup RID2PASID failed [Where problems could occur] After enable intel_iommu, the errors may be occurred. We need to figure out one by one once the related errors are triggered in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982104/+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 1948626] Re: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1948626 Title: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: [Impact] NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers. TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis. Here is code that implements TP8009 and TP8010: https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas [Fix] 1. Update kernel with TP8010 kernel patches: a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907 b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0 c. nvme: add CNTRLTYPE definitions for 'identify controller https://lore.kernel.org/all/66fc4f03-ed5c-4727-ba94-c23daf7d6...@oracle.com/ [Test Case] 1. Compile libnvme and nvme-stas packages from github using the kernel with these patches. 2. Test libnvme and nvme-stas packages [Where problems could occur] Regression risk for these patches are low [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches_2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+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 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
@Jeff - I have sent them via email to you and Michael. Please check. -- 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/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+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 1961955] Re: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream
It is currently only cosmetic, lspci only impact. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1961955 Title: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream Status in hwdata package in Ubuntu: Fix Released Status in hwdata source package in Focal: New Status in hwdata source package in Jammy: Incomplete Bug description: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET 1b4b: 2241: 1028: 2196 ROR-N100 Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1961955/+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 1961955] Re: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream
These are new storage controllers launched/to-be-launched by Dell. Unless hwdata carries these ids, lspci will show them as a generic storage controller, not the exact model name. This impact is on lspci and any other tools which rely on model names displayed in lspci. Hence the request to include in Jammy and Focal which are both supported on the platforms having these new storage controllers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1961955 Title: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream Status in hwdata package in Ubuntu: Fix Released Status in hwdata source package in Focal: New Status in hwdata source package in Jammy: Incomplete Bug description: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET 1b4b: 2241: 1028: 2196 ROR-N100 Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1961955/+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 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
** Attachment removed: "nvidia-bug-report log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934620/+attachment/5592914/+files/nvidia-bug-report.log.gz -- 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/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+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 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
Uploaded the requested logs. -- 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/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+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 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
** Attachment added: "nvidia-bug-report log" https://bugs.launchpad.net/dellserver/+bug/1934620/+attachment/5592914/+files/nvidia-bug-report.log.gz -- 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/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+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 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
Team is working on getting the required GPU setup. -- 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/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+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 1973127] [NEW] Ubuntu 22.04 installation crashes
Private bug reported: Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server which is targeting Telco workloads. Attaching the console logs. Currently, it looks like disabling VT-D option in BIOS settings helps mitigate the issue. Console logs indicate something is wrong in iommu/dmar subsystem. ** Affects: dellserver Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private ** Description changed: - Ubuntu 22.04 installation crashes + Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server which is targeting Telco workloads. + Attaching the console logs. + + Currently, it looks like disabling VT-D option in BIOS settings helps mitigate the issue. + Console logs indicate something is wrong in iommu/dmar subsystem. -- 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/1973127 Title: Ubuntu 22.04 installation crashes Status in dellserver: New Status in linux package in Ubuntu: New Bug description: Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server which is targeting Telco workloads. Attaching the console logs. Currently, it looks like disabling VT-D option in BIOS settings helps mitigate the issue. Console logs indicate something is wrong in iommu/dmar subsystem. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1973127/+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 1961955] Re: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream
Hi Michael, These ids are not included in Jammy having hwdata/jammy,now 0.357-1 all [installed]. Request you to help get these included in the SRUs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1961955 Title: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream Status in hwdata package in Ubuntu: Incomplete Status in hwdata source package in Focal: New Status in hwdata source package in Jammy: Incomplete Bug description: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET 1b4b: 2241: 1028: 2196 ROR-N100 Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1961955/+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 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
** Also affects: dellserver Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971955 Title: systemd-udevd call unshare process when attaching nvme volume Status in dellserver: New Status in linux package in Ubuntu: Invalid Status in snapd package in Ubuntu: New Bug description: env: PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 (Jammy Jellyfish)" VERSION_CODENAME=jammy # lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 host connect dellemc powerstore with nvme-tcp connection # nvme list-subsys nvme-subsys0 - NQN=nqn.1988-11.com.dell:powerstore:00:d42d581e674f2B16F2E2 \ +- nvme1 tcp traddr=172.16.100.165 trsvcid=4420 live +- nvme2 tcp traddr=172.16.200.164 trsvcid=4420 live +- nvme3 tcp traddr=172.16.200.165 trsvcid=4420 live +- nvme4 tcp traddr=172.16.100.164 trsvcid=4420 live when attaching new volume to host. systemd-udevd trigger unshare process to run snap import command on new volumes and it fail. volume finally map to host. it doesn't affect volume usage. but some udev rule need to check for this strange behavior. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33374]: nvme0n234: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n234' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33371]: nvme0n232: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n232' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33378]: nvme0n236: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n236' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33384]: nvme0n239: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n239' failed with exit code 1. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 6 08:14 seq crw-rw 1 root audio 116, 33 May 6 08:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-04 (2 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. 8 channel internal hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/6p, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/14/2021 dmi.bios.release: 2.13 dmi.bios.version: 2.13.0 dmi.board.name: 072T6D dmi.board.version: A01 dmi.chassis.type: 23 dmi.modalias: dmi:bvn:bvr2.13.0:bd05/14/2021:br2.13:svn:pn:pvr:rvn:rn072T6D:rvrA01:cvn:ct23:cvr:skuSKU=NotProvided;ModelName=: dmi.product.sku: SKU=NotProvided;ModelName= To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1971955/+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 1970621] [NEW] [Ubuntu 22.04] Update nvme-cli to v2.0
Public bug reported: Request you to update nvme-cli to v2.0 which has several fixes and features required for NVMe over TCP. nvme-cli v2.0 also depends on libnvme, inclusion of which is requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948636 ** Affects: dellserver Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: nvme-cli (Ubuntu) Importance: Undecided Status: New ** Also affects: nvme-cli (Ubuntu) Importance: Undecided Status: New ** Also affects: dellserver Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970621 Title: [Ubuntu 22.04] Update nvme-cli to v2.0 Status in dellserver: New Status in linux package in Ubuntu: Incomplete Status in nvme-cli package in Ubuntu: New Bug description: Request you to update nvme-cli to v2.0 which has several fixes and features required for NVMe over TCP. nvme-cli v2.0 also depends on libnvme, inclusion of which is requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948636 To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1970621/+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 1948626] Re: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
Michael, The test kernel listed here is 5.13 kernel, but jammy is of v5.15 kernel. Is this going to be for Jammy? https://people.canonical.com/~mreed/lp_1948626_nvme_tcp/ -- 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/1948626 Title: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Impact] NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers. TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis. Here is code that implements TP8009 and TP8010: https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas [Fix] 1. Update kernel with TP8010 kernel patches: a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907 b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0 c. nvme: add CNTRLTYPE definitions for 'identify controller https://lore.kernel.org/all/66fc4f03-ed5c-4727-ba94-c23daf7d6...@oracle.com/ [Test Case] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+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 1948626] Re: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
@~reshmi-susheela-aravind - will you be able to look into this? -- 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/1948626 Title: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Impact] NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers. TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis. Here is code that implements TP8009 and TP8010: https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas [Fix] 1. Update kernel with TP8010 kernel patches: a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907 b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0 c. nvme: add CNTRLTYPE definitions for 'identify controller https://lore.kernel.org/all/66fc4f03-ed5c-4727-ba94-c23daf7d6...@oracle.com/ [Test Case] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+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 1961955] Re: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream
https://github.com/vcrhonek/hwdata/commit/ae144d896eea90e527a57276accaf0da043c9f83 added the ROR-N100 to upstream hwdata. Request you to pull this as well into Jammy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1961955 Title: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream Status in hwdata package in Ubuntu: Incomplete Status in hwdata source package in Focal: New Status in hwdata source package in Jammy: Incomplete Bug description: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET 1b4b: 2241: 1028: 2196 ROR-N100 Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1961955/+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 1968034] [NEW] Ubuntu 22.04 Feature master tracker: Boot from NVMe over TCP
Private bug reported: This is a master feature tracker to track the bits of Boot from NVMe over TCP feature. Feature includes: 1. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626 Update kernel, Add pkgs - libnvme and nvme-stas. 2. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948636 Include libnvme pkg in jammy 3. https://bugs.launchpad.net/ubuntu/+source/dasbus/+bug/1948644 Include python3-dasbus in jammy 4. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625 Include and update nvme-stas pkg 5. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948627 6. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948630 Update dracut 7. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948631 Update efibootmgr 8. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948634 Update subiquity to detect and install os into nvme/tcp lun. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- 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/1968034 Title: Ubuntu 22.04 Feature master tracker: Boot from NVMe over TCP Status in linux package in Ubuntu: New Bug description: This is a master feature tracker to track the bits of Boot from NVMe over TCP feature. Feature includes: 1. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626 Update kernel, Add pkgs - libnvme and nvme-stas. 2. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948636 Include libnvme pkg in jammy 3. https://bugs.launchpad.net/ubuntu/+source/dasbus/+bug/1948644 Include python3-dasbus in jammy 4. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625 Include and update nvme-stas pkg 5. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948627 6. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948630 Update dracut 7. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948631 Update efibootmgr 8. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948634 Update subiquity to detect and install os into nvme/tcp lun. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968034/+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 1965241] Re: Include DPC Fixes in Ubuntu 22.04 and 20.04
** Also affects: dellserver Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965241 Title: Include DPC Fixes in Ubuntu 22.04 and 20.04 Status in dellserver: New Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: Impact: Recovery from DownPort Containment events fail and the NVMe endpoint is not accessible in some scenarios. Fix: These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu 20.04.5: Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=00823dcbdd415c868390feaca16f0265101efab4 Not yet pulled PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=ea401499e943c307e6d44af6c2b4e068643e7884 Test Case: To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1965241/+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 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
Hi Jeff, Original repro machine had ~1TB memory. Previously attached log snip: Memory: 1055972180K/1073051196K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 17079016K reserved, 0K cma-reserved) -- 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/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+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 1917471] Re: [Regression] Bus Fatal Error observed when reboot on BCM5720
Hi Jeff,
I think we should now go ahead with the SRU request for the fix.
rmmod tg3 does not help workaround the issue.
Fix details:
Revert "PM: ACPI: reboot: Use S5 for reboot"
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/kernel?h=v5.17-rc7&id=9d3fcb28f9b9750b474811a2964ce022df56336e
--
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/1917471
Title:
[Regression] Bus Fatal Error observed when reboot on BCM5720
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
In Progress
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
following error messages are observed
[ 146.429212] shutdown[1]: Rebooting.
[ 146.435151] kvm: exiting hardware virtualization
[ 146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is
called outbound_intr_mask:0x4009
[ 148.088133] [qede_unload:2236(eno12409)]Link is down
[ 148.183618] qede :31:00.1: Ending qede_remove successfully
[ 148.518541] [qede_unload:2236(eno12399)]Link is down
[ 148.625066] qede :31:00.0: Ending qede_remove successfully
[ 148.762067] ACPI: Preparing to enter system sleep state S5
[ 148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 5
[ 148.803731] {1}[Hardware Error]: event severity: recoverable
[ 148.810191] {1}[Hardware Error]: Error 0, type: fatal
[ 148.816088] {1}[Hardware Error]: section_type: PCIe error
[ 148.822391] {1}[Hardware Error]: port_type: 0, PCIe end point
[ 148.829026] {1}[Hardware Error]: version: 3.0
[ 148.834266] {1}[Hardware Error]: command: 0x0006, status: 0x0010
[ 148.841140] {1}[Hardware Error]: device_id: :04:00.0
[ 148.847309] {1}[Hardware Error]: slot: 0
[ 148.852077] {1}[Hardware Error]: secondary_bus: 0x00
[ 148.857876] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f
[ 148.865145] {1}[Hardware Error]: class_code: 02
[ 148.870845] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x0001
[ 148.879842] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
[ 148.886575] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
[ 148.894823] tg3 :04:00.0: AER: aer_status: 0x0010, aer_mask:
0x0001
[ 148.902795] tg3 :04:00.0: AER:[20] UnsupReq (First)
[ 148.910234] tg3 :04:00.0: AER: aer_layer=Transaction Layer,
aer_agent=Requester ID
[ 148.918806] tg3 :04:00.0: AER: aer_uncor_severity: 0x000ef030
[ 148.925558] tg3 :04:00.0: AER: TLP Header: 4001 030f
90028090
[ 148.933984] reboot: Restarting system
[ 148.938319] reboot: machine restart
I have observed the following. when I test older kernel
Kernel version Fatal Error
5.4.0-42.46 No
5.4.0-45.49 No
5.4.0-47.51 No
5.4.0-48.52 No
5.4.0-51.56 No
5.4.0-52.57 No
5.4.0-53.59 No
5.4.0-54.60 No
5.4.0-58.64 No
5.4.0-59.65 yes
5.4.0-60.67 yes
later I have bisect kernel between 5.4.0-58.64 and 5.4.0-59.65.
looks like due to the following patch we are observing this issue. The
driver is not handling D3 state properly
PCI/ACPI: Whitelist hotplug ports for D3 if power managed by ACPI
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
focal.git/commit/?id=b9319dd02269593911403dd5d684368bcef3261d
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917471/+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 1965241] [NEW] Include DPC Fixes in Ubuntu 22.04 and 20.04
Public bug reported: These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Without these, recovery from DPC event fails and NVMe endpoint is not accessible for some of the scenarios. Upstream kernel patches to be included into Ubuntu 22.04 SRU and into Ubuntu 20.04.5: PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=00823dcbdd415c868390feaca16f0265101efab4 PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=ea401499e943c307e6d44af6c2b4e068643e7884 ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1965241 Title: Include DPC Fixes in Ubuntu 22.04 and 20.04 Status in linux package in Ubuntu: Incomplete Bug description: These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Without these, recovery from DPC event fails and NVMe endpoint is not accessible for some of the scenarios. Upstream kernel patches to be included into Ubuntu 22.04 SRU and into Ubuntu 20.04.5: PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=00823dcbdd415c868390feaca16f0265101efab4 PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=ea401499e943c307e6d44af6c2b4e068643e7884 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965241/+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 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
** Information type changed from Private to Public -- 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/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: New Status in linux package in Ubuntu: Incomplete Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+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 1961955] Re: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream
Looks like pci.ids are pulled-in once in a month. We will wait for the next update to it in Apr. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1961955 Title: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream Status in hwdata package in Ubuntu: Incomplete Status in hwdata source package in Focal: New Status in hwdata source package in Jammy: Incomplete Bug description: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET 1b4b: 2241: 1028: 2196 ROR-N100 Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1961955/+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 1961955] Re: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream
** Description changed: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET + 1b4b: 2241: 1028: 2196 ROR-N100 Thanks. ** Description changed: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however - new form factors are being launched by Dell which are having new - subsystem-ids. + new form factors are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET - 1b4b: 2241: 1028: 2196 ROR-N100 + 1b4b: 2241: 1028: 2196 ROR-N100 Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1961955 Title: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream Status in hwdata package in Ubuntu: New Status in hwdata source package in Focal: New Status in hwdata source package in Jammy: New Bug description: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET 1b4b: 2241: 1028: 2196 ROR-N100 Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1961955/+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 1948636] Re: Ubuntu 22.04 Feature Request-NVMe: Include libnvme package
** Information type changed from Private to Public -- 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/1948636 Title: Ubuntu 22.04 Feature Request-NVMe: Include libnvme package Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: Upstream (Keith Busch) has started to revive libnvme with the hope of having nvme-cli use libnvme in future. New features like CDC client will be developed on libnvme. Upstream plans are to make libnvme a standalone package that other projects would depend on. We request that Ubuntu 22.04 carry the new libnvme package. https://github.com/linux-nvme/libnvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948636/+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 1948644] Re: Ubuntu 22.04 Feature Request-Include python-dasbus pacakge
** Information type changed from Private to Public -- 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/1948644 Title: Ubuntu 22.04 Feature Request-Include python-dasbus pacakge Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: Dell requests the python-dasbus package in Ubuntu 22.04. nvme-stas, the CDC client implementation in Linux requires python-dasbus to interface with dbus to receive messages from avahi-daemon. python-dasbus is actively maintained and preferred over python-pydbus. https://pypi.org/project/dasbus/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948644/+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 1948626] Re: Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
TP-8010 code was recently made public. Marking this report public now. ** Information type changed from Private to Public -- 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/1948626 Title: Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers. TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis. Here is code that implements TP8009 and TP8010: https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+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 1961955] [NEW] Request to pull-in new HBA & BOSS N1 PCI-ids from upstream
Public bug reported: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET Thanks. ** Affects: hwdata (Ubuntu) Importance: Undecided Status: New ** Description changed: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream + HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however + new form factors are being launched by Dell which are having new + subsystem-ids. - HBA350i are shipping cards supported from SLES15-SP1 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. + BOSS-N1 is planned support in Ubuntu 20.04 onwards. - BOSS-N1 is planned support in SLES15-SP3 onwards. - - Request is to pull these new pci-ids into SLES15-SP3 and SLES15-SP4. - + Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1961955 Title: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream Status in hwdata package in Ubuntu: New Bug description: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1961955/+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 1933359] Re: [SRU][Ubuntu 21.10][Broadcom] mpi3mr driver submission request
Hi Michael, Sanity check is complete with the new impish proposed kernel 5.13.0-28.31. Please help take this forward. -- 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/1933359 Title: [SRU][Ubuntu 21.10][Broadcom] mpi3mr driver submission request Status in linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Committed Bug description: [Impact] Broadcom is coming up with next generation high performance Storage IO and RAID controllers. For details, follow: https://www.spinics.net/lists/linux-scsi/msg147868.html This family of controllers is managed by "mpi3mr" Linux device driver(written from scratch). First patchset of the driver is accepted by Linux upstream. The driver is available in git branch - 5.14/scsi-staging of Linux SCSI tree: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git The driver will be part of 5.14 mainline Linux kernel release. Here is the list of commit ids: [Fixes] 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints 74e1f30a2868 scsi: mpi3mr: Add EEDP DIF DIX support 28cbe2f420d3 scsi: mpi3mr: Add support for DSN secure firmware check 2f9c4d520aa6 scsi: mpi3mr: Add support for PM suspend and resume 44dc724f5eec scsi: mpi3mr: Wait for pending I/O completions upon detection of VD I/O timeout 71e80106d059 scsi: mpi3mr: Print pending host I/Os for debugging f061178e0762 scsi: mpi3mr: Complete support for soft reset 463429f8dd5c scsi: mpi3mr: Add support for threaded ISR 392bbeb85b2a scsi: mpi3mr: Hardware workaround for UNMAP commands to NVMe drives 82141ddba90a scsi: mpi3mr: Allow certain commands during pci-remove hook 0ea177343f1f scsi: mpi3mr: Add change queue depth support e844adb1fbdc scsi: mpi3mr: Implement SCSI error handler hooks 8f9c6173ca46 scsi: mpi3mr: Add bios_param SCSI host template hook ff9561e910fc scsi: mpi3mr: Print IOC info for debugging 54dfcffb4191 scsi: mpi3mr: Add support for timestamp sync with firmware fb9b04574f14 scsi: mpi3mr: Add support for recovering controller e36710dc06e3 scsi: mpi3mr: Additional event handling 8e653455547a scsi: mpi3mr: Add support for PCIe device event handling 13ef29ea4aa0 scsi: mpi3mr: Add support for device add/remove event handling 672ae26c8216 scsi: mpi3mr: Add support for internal watchdog thread 023ab2a9b4ed scsi: mpi3mr: Add support for queue command processing c9566231cfaf scsi: mpi3mr: Create operational request and reply queue pair 824a156633df scsi: mpi3mr: Base driver code c4f7ac64616e scsi: mpi3mr: Add mpi30 Rev-R headers and Kconfig Please include this driver in Ubuntu 21.10 release. Let me know for any questions. [Testing] Load the driver Run IO [Regression Risk] No extra test cases are needed, normal regression test cases such as driver load & running IOs are enough. [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/impish/+ref/mpi3mr_driver_bcom2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933359/+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 1933359] Re: [SRU][Ubuntu 21.10][Broadcom] mpi3mr driver submission request
Hi Michael, Sanity check on the above kernel is a Pass. ** Tags removed: impish verification-needed-impish ** Tags added: verification-done-impish -- 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/1933359 Title: [SRU][Ubuntu 21.10][Broadcom] mpi3mr driver submission request Status in linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Committed Bug description: [Impact] Broadcom is coming up with next generation high performance Storage IO and RAID controllers. For details, follow: https://www.spinics.net/lists/linux-scsi/msg147868.html This family of controllers is managed by "mpi3mr" Linux device driver(written from scratch). First patchset of the driver is accepted by Linux upstream. The driver is available in git branch - 5.14/scsi-staging of Linux SCSI tree: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git The driver will be part of 5.14 mainline Linux kernel release. Here is the list of commit ids: [Fixes] 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints 74e1f30a2868 scsi: mpi3mr: Add EEDP DIF DIX support 28cbe2f420d3 scsi: mpi3mr: Add support for DSN secure firmware check 2f9c4d520aa6 scsi: mpi3mr: Add support for PM suspend and resume 44dc724f5eec scsi: mpi3mr: Wait for pending I/O completions upon detection of VD I/O timeout 71e80106d059 scsi: mpi3mr: Print pending host I/Os for debugging f061178e0762 scsi: mpi3mr: Complete support for soft reset 463429f8dd5c scsi: mpi3mr: Add support for threaded ISR 392bbeb85b2a scsi: mpi3mr: Hardware workaround for UNMAP commands to NVMe drives 82141ddba90a scsi: mpi3mr: Allow certain commands during pci-remove hook 0ea177343f1f scsi: mpi3mr: Add change queue depth support e844adb1fbdc scsi: mpi3mr: Implement SCSI error handler hooks 8f9c6173ca46 scsi: mpi3mr: Add bios_param SCSI host template hook ff9561e910fc scsi: mpi3mr: Print IOC info for debugging 54dfcffb4191 scsi: mpi3mr: Add support for timestamp sync with firmware fb9b04574f14 scsi: mpi3mr: Add support for recovering controller e36710dc06e3 scsi: mpi3mr: Additional event handling 8e653455547a scsi: mpi3mr: Add support for PCIe device event handling 13ef29ea4aa0 scsi: mpi3mr: Add support for device add/remove event handling 672ae26c8216 scsi: mpi3mr: Add support for internal watchdog thread 023ab2a9b4ed scsi: mpi3mr: Add support for queue command processing c9566231cfaf scsi: mpi3mr: Create operational request and reply queue pair 824a156633df scsi: mpi3mr: Base driver code c4f7ac64616e scsi: mpi3mr: Add mpi30 Rev-R headers and Kconfig Please include this driver in Ubuntu 21.10 release. Let me know for any questions. [Testing] Load the driver Run IO [Regression Risk] No extra test cases are needed, normal regression test cases such as driver load & running IOs are enough. [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/impish/+ref/mpi3mr_driver_bcom2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933359/+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 1933359] Re: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request
Hi Michael, Can you please help incorporate this driver in upcoming release of 20.04 HWE? -- 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/1933359 Title: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: Broadcom is coming up with next generation high performance Storage IO and RAID controllers. For details, follow: https://www.spinics.net/lists/linux-scsi/msg147868.html This family of controllers is managed by "mpi3mr" Linux device driver(written from scratch). First patchset of the driver is accepted by Linux upstream. The driver is available in git branch - 5.14/scsi-staging of Linux SCSI tree: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git The driver will be part of 5.14 mainline Linux kernel release. Here is the list of commit ids: 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints 74e1f30a2868 scsi: mpi3mr: Add EEDP DIF DIX support 28cbe2f420d3 scsi: mpi3mr: Add support for DSN secure firmware check 2f9c4d520aa6 scsi: mpi3mr: Add support for PM suspend and resume 44dc724f5eec scsi: mpi3mr: Wait for pending I/O completions upon detection of VD I/O timeout 71e80106d059 scsi: mpi3mr: Print pending host I/Os for debugging f061178e0762 scsi: mpi3mr: Complete support for soft reset 463429f8dd5c scsi: mpi3mr: Add support for threaded ISR 392bbeb85b2a scsi: mpi3mr: Hardware workaround for UNMAP commands to NVMe drives 82141ddba90a scsi: mpi3mr: Allow certain commands during pci-remove hook 0ea177343f1f scsi: mpi3mr: Add change queue depth support e844adb1fbdc scsi: mpi3mr: Implement SCSI error handler hooks 8f9c6173ca46 scsi: mpi3mr: Add bios_param SCSI host template hook ff9561e910fc scsi: mpi3mr: Print IOC info for debugging 54dfcffb4191 scsi: mpi3mr: Add support for timestamp sync with firmware fb9b04574f14 scsi: mpi3mr: Add support for recovering controller e36710dc06e3 scsi: mpi3mr: Additional event handling 8e653455547a scsi: mpi3mr: Add support for PCIe device event handling 13ef29ea4aa0 scsi: mpi3mr: Add support for device add/remove event handling 672ae26c8216 scsi: mpi3mr: Add support for internal watchdog thread 023ab2a9b4ed scsi: mpi3mr: Add support for queue command processing c9566231cfaf scsi: mpi3mr: Create operational request and reply queue pair 824a156633df scsi: mpi3mr: Base driver code c4f7ac64616e scsi: mpi3mr: Add mpi30 Rev-R headers and Kconfig Please include this driver in Ubuntu 21.10 release. Let me know for any questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933359/+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 1933359] Re: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request
Hi Michael, Sanity check on the above kernel is a Pass. -- 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/1933359 Title: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: Broadcom is coming up with next generation high performance Storage IO and RAID controllers. For details, follow: https://www.spinics.net/lists/linux-scsi/msg147868.html This family of controllers is managed by "mpi3mr" Linux device driver(written from scratch). First patchset of the driver is accepted by Linux upstream. The driver is available in git branch - 5.14/scsi-staging of Linux SCSI tree: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git The driver will be part of 5.14 mainline Linux kernel release. Here is the list of commit ids: 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints 74e1f30a2868 scsi: mpi3mr: Add EEDP DIF DIX support 28cbe2f420d3 scsi: mpi3mr: Add support for DSN secure firmware check 2f9c4d520aa6 scsi: mpi3mr: Add support for PM suspend and resume 44dc724f5eec scsi: mpi3mr: Wait for pending I/O completions upon detection of VD I/O timeout 71e80106d059 scsi: mpi3mr: Print pending host I/Os for debugging f061178e0762 scsi: mpi3mr: Complete support for soft reset 463429f8dd5c scsi: mpi3mr: Add support for threaded ISR 392bbeb85b2a scsi: mpi3mr: Hardware workaround for UNMAP commands to NVMe drives 82141ddba90a scsi: mpi3mr: Allow certain commands during pci-remove hook 0ea177343f1f scsi: mpi3mr: Add change queue depth support e844adb1fbdc scsi: mpi3mr: Implement SCSI error handler hooks 8f9c6173ca46 scsi: mpi3mr: Add bios_param SCSI host template hook ff9561e910fc scsi: mpi3mr: Print IOC info for debugging 54dfcffb4191 scsi: mpi3mr: Add support for timestamp sync with firmware fb9b04574f14 scsi: mpi3mr: Add support for recovering controller e36710dc06e3 scsi: mpi3mr: Additional event handling 8e653455547a scsi: mpi3mr: Add support for PCIe device event handling 13ef29ea4aa0 scsi: mpi3mr: Add support for device add/remove event handling 672ae26c8216 scsi: mpi3mr: Add support for internal watchdog thread 023ab2a9b4ed scsi: mpi3mr: Add support for queue command processing c9566231cfaf scsi: mpi3mr: Create operational request and reply queue pair 824a156633df scsi: mpi3mr: Base driver code c4f7ac64616e scsi: mpi3mr: Add mpi30 Rev-R headers and Kconfig Please include this driver in Ubuntu 21.10 release. Let me know for any questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933359/+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 1948623] [NEW] Ubuntu 22.04 Feature: Disable Kconfig CONFIG_PCI_REALLOC_ENABLE_AUTO option
Private bug reported: Coming from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934620 , request you to disable Kconfig option - CONFIG_PCI_REALLOC_ENABLE_AUTO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- 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/1948623 Title: Ubuntu 22.04 Feature: Disable Kconfig CONFIG_PCI_REALLOC_ENABLE_AUTO option Status in linux package in Ubuntu: New Bug description: Coming from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934620 , request you to disable Kconfig option - CONFIG_PCI_REALLOC_ENABLE_AUTO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948623/+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 1933359] Re: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request
Dell wants this driver to be a part of Ubuntu 20.04.4 GA ISO (HWE kernel of 20.04.4) to handle the installation scenarios. Let us know if this is not going to be the case. -- 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/1933359 Title: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Status in linux source package in Impish: Confirmed Bug description: Broadcom is coming up with next generation high performance Storage IO and RAID controllers. For details, follow: https://www.spinics.net/lists/linux-scsi/msg147868.html This family of controllers is managed by "mpi3mr" Linux device driver(written from scratch). First patchset of the driver is accepted by Linux upstream. The driver is available in git branch - 5.14/scsi-staging of Linux SCSI tree: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git The driver will be part of 5.14 mainline Linux kernel release. Here is the list of commit ids: 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints 74e1f30a2868 scsi: mpi3mr: Add EEDP DIF DIX support 28cbe2f420d3 scsi: mpi3mr: Add support for DSN secure firmware check 2f9c4d520aa6 scsi: mpi3mr: Add support for PM suspend and resume 44dc724f5eec scsi: mpi3mr: Wait for pending I/O completions upon detection of VD I/O timeout 71e80106d059 scsi: mpi3mr: Print pending host I/Os for debugging f061178e0762 scsi: mpi3mr: Complete support for soft reset 463429f8dd5c scsi: mpi3mr: Add support for threaded ISR 392bbeb85b2a scsi: mpi3mr: Hardware workaround for UNMAP commands to NVMe drives 82141ddba90a scsi: mpi3mr: Allow certain commands during pci-remove hook 0ea177343f1f scsi: mpi3mr: Add change queue depth support e844adb1fbdc scsi: mpi3mr: Implement SCSI error handler hooks 8f9c6173ca46 scsi: mpi3mr: Add bios_param SCSI host template hook ff9561e910fc scsi: mpi3mr: Print IOC info for debugging 54dfcffb4191 scsi: mpi3mr: Add support for timestamp sync with firmware fb9b04574f14 scsi: mpi3mr: Add support for recovering controller e36710dc06e3 scsi: mpi3mr: Additional event handling 8e653455547a scsi: mpi3mr: Add support for PCIe device event handling 13ef29ea4aa0 scsi: mpi3mr: Add support for device add/remove event handling 672ae26c8216 scsi: mpi3mr: Add support for internal watchdog thread 023ab2a9b4ed scsi: mpi3mr: Add support for queue command processing c9566231cfaf scsi: mpi3mr: Create operational request and reply queue pair 824a156633df scsi: mpi3mr: Base driver code c4f7ac64616e scsi: mpi3mr: Add mpi30 Rev-R headers and Kconfig Please include this driver in Ubuntu 21.10 release. Let me know for any questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933359/+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 1935034] Re: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1935034 Title: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: New Status in linux source package in Hirsute: New Status in linux source package in Impish: Fix Released Bug description: [Impact] This is a feature request to update the mpt3sas driver to latest version in upstream 38.100.00.00 in Ubuntu 21.10 and Ubuntu 20.04. This will allow users to use fixes and enhancements that landed upstream in 5.14. For this reason, Broadcom and Dell have requested to pull these patches to update the mpt3sas driver to the current upstream version. I could see both Ubuntu 21.10 and 20.04 HWE has mpt3sas driver v36.100.00.00, following are the commit ID's to update to 38.100.00.00 [Fixes] 8b3c803529 scsi: mpt3sas: Signedness bug in _base_get_diag_triggers() 39718fe7ad scsi: mpt3sas: Fix spelling mistake in Kconfig "compatiblity" -> "compatibility" bfb3f00c06 scsi: mpt3sas: Simplify bool comparison d309ae0732 scsi: mpt3sas: Fix ReplyPostFree pool allocation 664f0dce20 scsi: mpt3sas: Add support for shared host tagset for CPU hotplug 688c1a0a13 scsi: mpt3sas: Additional diagnostic buffer query interface 446b5f3d3f scsi: mpt3sas: Update driver version to 37.100.00.00 8278807abd scsi: core: Add scsi_device_busy() wrapper 020b0f0a31 scsi: core: Replace sdev->device_busy with sbitmap e015e0ded1 scsi: mpt3sas: Fix misspelling of _base_put_smid_default_atomic() 2111ba8781 scsi: mpt3sas: Move a little data from the stack onto the heap cf9e575e62 scsi: mpt3sas: Fix a bunch of potential naming doc-rot 54cb88dc30 scsi: mpt3sas: Fix a couple of misdocumented functions/params 782a1ab33f scsi: mpt3sas: Fix some kernel-doc misnaming issues a50bd64616 scsi: mpt3sas: Do not use GFP_KERNEL in atomic context a1c4d77413 scsi: mpt3sas: Replace unnecessary dynamic allocation with a static one d6adc251dd scsi: mpt3sas: Force PCIe scatterlist allocations to be within same 4 GB region 7dd847dae1 scsi: mpt3sas: Force chain buffer allocations to be within same 4 GB region 970ac2bb70 scsi: mpt3sas: Force sense buffer allocations to be within same 4 GB region 58501fd937 scsi: mpt3sas: Force reply buffer allocations to be within same 4 GB region 2e4e858732 scsi: mpt3sas: Force reply post buffer allocations to be within same 4 GB region c569de899b scsi: mpt3sas: Force reply post array allocations to be within same 4 GB region 37067b9793 scsi: mpt3sas: Update driver version to 37.101.00.00 a8d548b0b3 scsi: mpt3sas: Fix a few kernel-doc issues 3401ecf7fc scsi: mpt3sas: Fix error return code of mpt3sas_base_attach() 206a3afa94 scsi: mpt3sas: Fix a typo 4c51f95696 scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES c0629d70ca scsi: mpt3sas: Fix endianness for ActiveCablePowerRequirement 3c8604691d scsi: mpt3sas: Block PCI config access from userspace during reset 16660db3fc scsi: mpt3sas: Fix out-of-bounds warnings in _ctl_addnl_diag_query 3ad0b1da0d scsi: mpt3sas: Fix two kernel-doc headers 2910a4a9e9 scsi: mpt3sas: Documentation cleanup e2fac6c44a scsi: mpt3sas: Fix deadlock while cancelling the running firmware event 19a622c39a scsi: mpt3sas: Handle firmware faults during first half of IOC init a0815c45c8 scsi: mpt3sas: Handle firmware faults during second half of IOC init f2b1e9c6f8 scsi: core: Introduce scsi_build_sense() 84a84cc6af scsi: mpt3sas: Fix fall-through warnings for Clang cf750be8e6 scsi: mpt3sas: Fix Coverity reported issue d6c2ce435f scsi: mpt3sas: Fix error return value in _scsih_expander_add() Note: We have already posted patch to update driver version to 38.100.00.00 Other patches are already available in upstream . [Testing] Load the driver Run IO [Regression Risk] No extra test cases are needed, normal regression test cases such as driver load & running IOs are enough. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935034/+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 1933359] Re: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request
Installed linux-image-unsigned, linux-modules & linux-modules-extra from the above link. # modinfo mpi3mr modinfo: ERROR: Module mpi3mr not found. # uname -r 5.13.0-18-generic Hi Michael, Looks like this kernel is missing mpi3mr. Can you please look into it? -- 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/1933359 Title: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: Broadcom is coming up with next generation high performance Storage IO and RAID controllers. For details, follow: https://www.spinics.net/lists/linux-scsi/msg147868.html This family of controllers is managed by "mpi3mr" Linux device driver(written from scratch). First patchset of the driver is accepted by Linux upstream. The driver is available in git branch - 5.14/scsi-staging of Linux SCSI tree: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git The driver will be part of 5.14 mainline Linux kernel release. Here is the list of commit ids: 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints 74e1f30a2868 scsi: mpi3mr: Add EEDP DIF DIX support 28cbe2f420d3 scsi: mpi3mr: Add support for DSN secure firmware check 2f9c4d520aa6 scsi: mpi3mr: Add support for PM suspend and resume 44dc724f5eec scsi: mpi3mr: Wait for pending I/O completions upon detection of VD I/O timeout 71e80106d059 scsi: mpi3mr: Print pending host I/Os for debugging f061178e0762 scsi: mpi3mr: Complete support for soft reset 463429f8dd5c scsi: mpi3mr: Add support for threaded ISR 392bbeb85b2a scsi: mpi3mr: Hardware workaround for UNMAP commands to NVMe drives 82141ddba90a scsi: mpi3mr: Allow certain commands during pci-remove hook 0ea177343f1f scsi: mpi3mr: Add change queue depth support e844adb1fbdc scsi: mpi3mr: Implement SCSI error handler hooks 8f9c6173ca46 scsi: mpi3mr: Add bios_param SCSI host template hook ff9561e910fc scsi: mpi3mr: Print IOC info for debugging 54dfcffb4191 scsi: mpi3mr: Add support for timestamp sync with firmware fb9b04574f14 scsi: mpi3mr: Add support for recovering controller e36710dc06e3 scsi: mpi3mr: Additional event handling 8e653455547a scsi: mpi3mr: Add support for PCIe device event handling 13ef29ea4aa0 scsi: mpi3mr: Add support for device add/remove event handling 672ae26c8216 scsi: mpi3mr: Add support for internal watchdog thread 023ab2a9b4ed scsi: mpi3mr: Add support for queue command processing c9566231cfaf scsi: mpi3mr: Create operational request and reply queue pair 824a156633df scsi: mpi3mr: Base driver code c4f7ac64616e scsi: mpi3mr: Add mpi30 Rev-R headers and Kconfig Please include this driver in Ubuntu 21.10 release. Let me know for any questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933359/+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 1935034] Re: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04
Hi Michael, Driver version check Install and boot 12hr stress test 12hr reboot loop All these tests went fine with the above proposed kernel. Please help include the updates into SRU. -- 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/1935034 Title: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04 Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Status in linux source package in Hirsute: New Status in linux source package in Impish: Confirmed Bug description: [Impact] This is a feature request to update the mpt3sas driver to latest version in upstream 38.100.00.00 in Ubuntu 21.10 and Ubuntu 20.04. This will allow users to use fixes and enhancements that landed upstream in 5.14. For this reason, Broadcom and Dell have requested to pull these patches to update the mpt3sas driver to the current upstream version. I could see both Ubuntu 21.10 and 20.04 HWE has mpt3sas driver v36.100.00.00, following are the commit ID's to update to 38.100.00.00 [Fixes] 8b3c803529 scsi: mpt3sas: Signedness bug in _base_get_diag_triggers() 39718fe7ad scsi: mpt3sas: Fix spelling mistake in Kconfig "compatiblity" -> "compatibility" bfb3f00c06 scsi: mpt3sas: Simplify bool comparison d309ae0732 scsi: mpt3sas: Fix ReplyPostFree pool allocation 664f0dce20 scsi: mpt3sas: Add support for shared host tagset for CPU hotplug 688c1a0a13 scsi: mpt3sas: Additional diagnostic buffer query interface 446b5f3d3f scsi: mpt3sas: Update driver version to 37.100.00.00 8278807abd scsi: core: Add scsi_device_busy() wrapper 020b0f0a31 scsi: core: Replace sdev->device_busy with sbitmap e015e0ded1 scsi: mpt3sas: Fix misspelling of _base_put_smid_default_atomic() 2111ba8781 scsi: mpt3sas: Move a little data from the stack onto the heap cf9e575e62 scsi: mpt3sas: Fix a bunch of potential naming doc-rot 54cb88dc30 scsi: mpt3sas: Fix a couple of misdocumented functions/params 782a1ab33f scsi: mpt3sas: Fix some kernel-doc misnaming issues a50bd64616 scsi: mpt3sas: Do not use GFP_KERNEL in atomic context a1c4d77413 scsi: mpt3sas: Replace unnecessary dynamic allocation with a static one d6adc251dd scsi: mpt3sas: Force PCIe scatterlist allocations to be within same 4 GB region 7dd847dae1 scsi: mpt3sas: Force chain buffer allocations to be within same 4 GB region 970ac2bb70 scsi: mpt3sas: Force sense buffer allocations to be within same 4 GB region 58501fd937 scsi: mpt3sas: Force reply buffer allocations to be within same 4 GB region 2e4e858732 scsi: mpt3sas: Force reply post buffer allocations to be within same 4 GB region c569de899b scsi: mpt3sas: Force reply post array allocations to be within same 4 GB region 37067b9793 scsi: mpt3sas: Update driver version to 37.101.00.00 a8d548b0b3 scsi: mpt3sas: Fix a few kernel-doc issues 3401ecf7fc scsi: mpt3sas: Fix error return code of mpt3sas_base_attach() 206a3afa94 scsi: mpt3sas: Fix a typo 4c51f95696 scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES c0629d70ca scsi: mpt3sas: Fix endianness for ActiveCablePowerRequirement 3c8604691d scsi: mpt3sas: Block PCI config access from userspace during reset 16660db3fc scsi: mpt3sas: Fix out-of-bounds warnings in _ctl_addnl_diag_query 3ad0b1da0d scsi: mpt3sas: Fix two kernel-doc headers 2910a4a9e9 scsi: mpt3sas: Documentation cleanup e2fac6c44a scsi: mpt3sas: Fix deadlock while cancelling the running firmware event 19a622c39a scsi: mpt3sas: Handle firmware faults during first half of IOC init a0815c45c8 scsi: mpt3sas: Handle firmware faults during second half of IOC init f2b1e9c6f8 scsi: core: Introduce scsi_build_sense() 84a84cc6af scsi: mpt3sas: Fix fall-through warnings for Clang cf750be8e6 scsi: mpt3sas: Fix Coverity reported issue d6c2ce435f scsi: mpt3sas: Fix error return value in _scsih_expander_add() Note: We have already posted patch to update driver version to 38.100.00.00 Other patches are already available in upstream . [Testing] Load the driver Run IO [Regression Risk] No extra test cases are needed, normal regression test cases such as driver load & running IOs are enough. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935034/+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 1934428] Re: Request to pull-in new PERC11 PCI-id from upstream
** Description changed: Request to pull-in new PERC11 PCI-ids from upstream. PERC-11 are shipping cards supported since Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. Request is to pull these new pci-ids into future releases Ubuntu 20.04. PCI-id details: - 1000:00e6:1028:2171 PERC H750 Mini - 1000:00e6:1028:2172 PERC H355 Adapter - 1000:00e6:1028:2173 PERC H355 Front - 1000:00e6:1028:2174 PERC H350 Mini - 1000:00e6:1028:2176 PERC H750 Adapter - 1000:00e6:1028:2177 PERC H350 Adapter + 1000:10e2:1028:2171 PERC H750 Mini + 1000:10e6:1028:2172 PERC H355 Adapter + 1000:10e6:1028:2173 PERC H355 Front + 1000:10e6:1028:2174 PERC H350 Mini + 1000:10e2:1028:2176 PERC H750 Adapter + 1000:10e6:1028:2177 PERC H350 Adapter External links: https://pci-ids.ucw.cz/read/PC/1000/10e2 https://pci-ids.ucw.cz/v2.2/pci.ids -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1934428 Title: Request to pull-in new PERC11 PCI-id from upstream Status in dellserver: New Status in hwdata package in Ubuntu: New Bug description: Request to pull-in new PERC11 PCI-ids from upstream. PERC-11 are shipping cards supported since Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. Request is to pull these new pci-ids into future releases Ubuntu 20.04. PCI-id details: 1000:10e2:1028:2171 PERC H750 Mini 1000:10e6:1028:2172 PERC H355 Adapter 1000:10e6:1028:2173 PERC H355 Front 1000:10e6:1028:2174 PERC H350 Mini 1000:10e2:1028:2176 PERC H750 Adapter 1000:10e6:1028:2177 PERC H350 Adapter External links: https://pci-ids.ucw.cz/read/PC/1000/10e2 https://pci-ids.ucw.cz/v2.2/pci.ids To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934428/+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 1935034] Re: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04
Hi Michael, Driver version check Install and boot 12hr stress test 12hr reboot loop All these tests went fine with the above test kernel. -- 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/1935034 Title: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04 Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Status in linux source package in Hirsute: New Status in linux source package in Impish: Confirmed Bug description: This is a feature request to update the mpt3sas driver to latest version in upstream 38.100.00.00 in Ubuntu 21.10 and Ubuntu 20.04. This will allow users to use fixes and enhancements that landed upstream in 5.14. For this reason, Broadcom and Dell have requested to pull these patches to update the mpt3sas driver to the current upstream version. I could see both Ubuntu 21.10 and 20.04 HWE has mpt3sas driver v36.100.00.00, following are the commit ID's to update to 38.100.00.00 8b3c803529 scsi: mpt3sas: Signedness bug in _base_get_diag_triggers() 39718fe7ad scsi: mpt3sas: Fix spelling mistake in Kconfig "compatiblity" -> "compatibility" bfb3f00c06 scsi: mpt3sas: Simplify bool comparison d309ae0732 scsi: mpt3sas: Fix ReplyPostFree pool allocation 664f0dce20 scsi: mpt3sas: Add support for shared host tagset for CPU hotplug 688c1a0a13 scsi: mpt3sas: Additional diagnostic buffer query interface 446b5f3d3f scsi: mpt3sas: Update driver version to 37.100.00.00 8278807abd scsi: core: Add scsi_device_busy() wrapper 020b0f0a31 scsi: core: Replace sdev->device_busy with sbitmap e015e0ded1 scsi: mpt3sas: Fix misspelling of _base_put_smid_default_atomic() 2111ba8781 scsi: mpt3sas: Move a little data from the stack onto the heap cf9e575e62 scsi: mpt3sas: Fix a bunch of potential naming doc-rot 54cb88dc30 scsi: mpt3sas: Fix a couple of misdocumented functions/params 782a1ab33f scsi: mpt3sas: Fix some kernel-doc misnaming issues a50bd64616 scsi: mpt3sas: Do not use GFP_KERNEL in atomic context a1c4d77413 scsi: mpt3sas: Replace unnecessary dynamic allocation with a static one d6adc251dd scsi: mpt3sas: Force PCIe scatterlist allocations to be within same 4 GB region 7dd847dae1 scsi: mpt3sas: Force chain buffer allocations to be within same 4 GB region 970ac2bb70 scsi: mpt3sas: Force sense buffer allocations to be within same 4 GB region 58501fd937 scsi: mpt3sas: Force reply buffer allocations to be within same 4 GB region 2e4e858732 scsi: mpt3sas: Force reply post buffer allocations to be within same 4 GB region c569de899b scsi: mpt3sas: Force reply post array allocations to be within same 4 GB region 37067b9793 scsi: mpt3sas: Update driver version to 37.101.00.00 a8d548b0b3 scsi: mpt3sas: Fix a few kernel-doc issues 3401ecf7fc scsi: mpt3sas: Fix error return code of mpt3sas_base_attach() 206a3afa94 scsi: mpt3sas: Fix a typo 4c51f95696 scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES c0629d70ca scsi: mpt3sas: Fix endianness for ActiveCablePowerRequirement 3c8604691d scsi: mpt3sas: Block PCI config access from userspace during reset 16660db3fc scsi: mpt3sas: Fix out-of-bounds warnings in _ctl_addnl_diag_query 3ad0b1da0d scsi: mpt3sas: Fix two kernel-doc headers 2910a4a9e9 scsi: mpt3sas: Documentation cleanup e2fac6c44a scsi: mpt3sas: Fix deadlock while cancelling the running firmware event 19a622c39a scsi: mpt3sas: Handle firmware faults during first half of IOC init a0815c45c8 scsi: mpt3sas: Handle firmware faults during second half of IOC init f2b1e9c6f8 scsi: core: Introduce scsi_build_sense() 84a84cc6af scsi: mpt3sas: Fix fall-through warnings for Clang cf750be8e6 scsi: mpt3sas: Fix Coverity reported issue d6c2ce435f scsi: mpt3sas: Fix error return value in _scsih_expander_add() Note: We have already posted patch to update driver version to 38.100.00.00 Other patches are already available in upstream . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935034/+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 1933790] Re: Request to pull-in new HBA11 PCI-id from upstream
Works fine with the updated git code. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1933790 Title: Request to pull-in new HBA11 PCI-id from upstream Status in dellserver: New Status in hwdata package in Ubuntu: New Bug description: HBA-11 is a shipping card supported since early Ubuntu 20.04 onwards, however a new form factor is being launched by which has a new subsystem-id. Request is to pull this pci-id to upcoming Ubuntu 20.04 builds. PCI-id details: 1000:00e6:1028:2175 External links: http://pci-ids.ucw.cz/read/PC/1000/00e6/10282175 https://pci-ids.ucw.cz/v2.2/pci.ids To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1933790/+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 1934428] Re: Request to pull-in new PERC11 PCI-id from upstream
Works fine with the updated git code. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1934428 Title: Request to pull-in new PERC11 PCI-id from upstream Status in dellserver: New Status in hwdata package in Ubuntu: New Bug description: Request to pull-in new PERC11 PCI-ids from upstream. PERC-11 are shipping cards supported since Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. Request is to pull these new pci-ids into future releases Ubuntu 20.04. PCI-id details: 1000:00e6:1028:2171 PERC H750 Mini 1000:00e6:1028:2172 PERC H355 Adapter 1000:00e6:1028:2173 PERC H355 Front 1000:00e6:1028:2174 PERC H350 Mini 1000:00e6:1028:2176 PERC H750 Adapter 1000:00e6:1028:2177 PERC H350 Adapter External links: https://pci-ids.ucw.cz/read/PC/1000/10e2 https://pci-ids.ucw.cz/v2.2/pci.ids To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934428/+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 1934428] Re: Request to pull-in new PERC11 PCI-id from upstream
root@ubuntu:/home/ubuntu/hwdata# make install mkdir -p -m 755 /usr/share/hwdata for foo in pci.ids usb.ids oui.txt iab.txt pnp.ids ; do \ install -m 644 $foo /usr/share/hwdata ;\ done mkdir -p -m 755 /usr/lib/modprobe.d install -m 644 -T blacklist.conf /usr/lib/modprobe.d/dist-blacklist.conf Hi Michael, The ids are to be added to 'pci.ids' file. I see you have added to 'pci.id' file which won't install during 'make install'. Could you please correct the file reflecting changes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1934428 Title: Request to pull-in new PERC11 PCI-id from upstream Status in dellserver: New Status in hwdata package in Ubuntu: New Bug description: Request to pull-in new PERC11 PCI-ids from upstream. PERC-11 are shipping cards supported since Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. Request is to pull these new pci-ids into future releases Ubuntu 20.04. PCI-id details: 1000:00e6:1028:2171 PERC H750 Mini 1000:00e6:1028:2172 PERC H355 Adapter 1000:00e6:1028:2173 PERC H355 Front 1000:00e6:1028:2174 PERC H350 Mini 1000:00e6:1028:2176 PERC H750 Adapter 1000:00e6:1028:2177 PERC H350 Adapter External links: https://pci-ids.ucw.cz/read/PC/1000/10e2 https://pci-ids.ucw.cz/v2.2/pci.ids To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934428/+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 1933790] Re: Request to pull-in new HBA11 PCI-id from upstream
root@ubuntu:/home/ubuntu/hwdata# make install mkdir -p -m 755 /usr/share/hwdata for foo in pci.ids usb.ids oui.txt iab.txt pnp.ids ; do \ install -m 644 $foo /usr/share/hwdata ;\ done mkdir -p -m 755 /usr/lib/modprobe.d install -m 644 -T blacklist.conf /usr/lib/modprobe.d/dist-blacklist.conf Hi Michael, The ids are to be added to 'pci.ids' file. I see you have added to 'pci.id' file which won't install during 'make install'. Could you please correct the file reflecting changes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1933790 Title: Request to pull-in new HBA11 PCI-id from upstream Status in dellserver: New Status in hwdata package in Ubuntu: New Bug description: HBA-11 is a shipping card supported since early Ubuntu 20.04 onwards, however a new form factor is being launched by which has a new subsystem-id. Request is to pull this pci-id to upcoming Ubuntu 20.04 builds. PCI-id details: 1000:00e6:1028:2175 External links: http://pci-ids.ucw.cz/read/PC/1000/00e6/10282175 https://pci-ids.ucw.cz/v2.2/pci.ids To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1933790/+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 1933790] Re: Request to pull-in new HBA11 PCI-id from upstream
Hi Michael, I could not find it in impish-devel file. https://git.launchpad.net/ubuntu/+source/hwdata/plain/pci.ids?h=applied/ubuntu/impish-devel Can you please verify? Details: PCI-id details: 1000:00e6:1028:2175 Card name: HBA350i Adapter -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1933790 Title: Request to pull-in new HBA11 PCI-id from upstream Status in dellserver: New Status in hwdata package in Ubuntu: New Bug description: HBA-11 is a shipping card supported since early Ubuntu 20.04 onwards, however a new form factor is being launched by which has a new subsystem-id. Request is to pull this pci-id to upcoming Ubuntu 20.04 builds. PCI-id details: 1000:00e6:1028:2175 External links: http://pci-ids.ucw.cz/read/PC/1000/00e6/10282175 https://pci-ids.ucw.cz/v2.2/pci.ids To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1933790/+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 1934428] [NEW] Request to pull-in new PERC11 PCI-id from upstream
Private bug reported: Request to pull-in new PERC11 PCI-ids from upstream. PERC-11 are shipping cards supported since Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. Request is to pull these new pci-ids into future releases Ubuntu 20.04. PCI-id details: 1000:00e6:1028:2171 PERC H750 Mini 1000:00e6:1028:2172 PERC H355 Adapter 1000:00e6:1028:2173 PERC H355 Front 1000:00e6:1028:2174 PERC H350 Mini 1000:00e6:1028:2176 PERC H750 Adapter 1000:00e6:1028:2177 PERC H350 Adapter External links: https://pci-ids.ucw.cz/read/PC/1000/10e2 https://pci-ids.ucw.cz/v2.2/pci.ids ** Affects: dellserver Importance: Undecided Status: New ** Affects: hwdata (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private ** Also affects: dellserver Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1934428 Title: Request to pull-in new PERC11 PCI-id from upstream Status in dellserver: New Status in hwdata package in Ubuntu: New Bug description: Request to pull-in new PERC11 PCI-ids from upstream. PERC-11 are shipping cards supported since Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. Request is to pull these new pci-ids into future releases Ubuntu 20.04. PCI-id details: 1000:00e6:1028:2171 PERC H750 Mini 1000:00e6:1028:2172 PERC H355 Adapter 1000:00e6:1028:2173 PERC H355 Front 1000:00e6:1028:2174 PERC H350 Mini 1000:00e6:1028:2176 PERC H750 Adapter 1000:00e6:1028:2177 PERC H350 Adapter External links: https://pci-ids.ucw.cz/read/PC/1000/10e2 https://pci-ids.ucw.cz/v2.2/pci.ids To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934428/+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 1932119] [NEW] Ubuntu 22.04 Feature: Include mpi3mr driver
Private bug reported: Please help include the upcoming PERC/HBA driver – mpi3mr which got accepted upstream into v5.14: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/log/drivers/scsi/mpi3mr?h=5.14 /scsi-staging We need this driver included in Ubuntu 22.04 LTS kernels. ** Affects: dellserver Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: dellserver ** Also affects: dellserver Importance: Undecided Status: New ** Information type changed from Public to Private -- 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/1932119 Title: Ubuntu 22.04 Feature: Include mpi3mr driver Status in dellserver: New Status in linux package in Ubuntu: New Bug description: Please help include the upcoming PERC/HBA driver – mpi3mr which got accepted upstream into v5.14: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/log/drivers/scsi/mpi3mr?h=5.14 /scsi-staging We need this driver included in Ubuntu 22.04 LTS kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1932119/+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 1926517] Re: [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES
** Attachment added: "sosreport - groovy proposed" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926517/+attachment/5503425/+files/sosreport-sujith-groovyproposed-2021-06-09-tlnmqhq.tar.xz -- 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/1926517 Title: [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] Whenever the driver is adding a vSES to virtual-phys list it is reinitializing the list head. Hence those vSES devices which were added previously are lost. [FIXES] Stop reinitializing the list every time a new vSES device is added. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=4c51f9569651 CommitID: 4c51f956965120b3441cdd39c358b87daba13e19 [TESTING] Load the mpt3sas driver on the system where Brodcom's HBA 9500 Tri-Mode Storage Adapter (IT HBA Aero/Ventura) is connected to two backplanes (so that two vSES device get configured on the HBA). After loading the driver user should able to access both the vSES devices. Also even after performing host reset operation user must able to access both the vSES devices. i.e. lsscsi must list both the vSES devices after loading the driver and also after performing host reset operation. [REGRESSION RISK] There is no regression risk with this bug fix patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926517/+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 1926517] Re: [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES
We have verified focal-proposed kernel and groovy-proposed kernels. Fix is working fine. We can list both enclosures in lsscsi. Focal-proposed: #uname -r 5.4.0-75-generic #lsscsi -g [2:0:0:0]diskHGST HUH721212AL5205 NM05 /dev/sda /dev/sg0 [2:0:1:0]diskATA ST2000NM0033-9ZM GA6C /dev/sdb /dev/sg1 [2:0:2:0]diskHGST HUS726020ALS210 KU27 /dev/sdc /dev/sg2 [2:0:3:0]diskATA HUS722T1TALA600 MU03 /dev/sdd /dev/sg3 [2:0:4:0]enclosu DP BP15G+ 3.04 - /dev/sg4 [2:0:5:0]diskTOSHIBA AL15SEB060NY EF04 /dev/sde /dev/sg5 [2:0:6:0]diskATA INTEL SSDSC2BX40 DL2B /dev/sdf /dev/sg6 [2:0:7:0]diskTOSHIBA AL15SEB24EQY EF05 /dev/sdg /dev/sg7 [2:0:8:0]diskATA ST1000NX0443 NB33 /dev/sdh /dev/sg8 [2:0:9:0]enclosu DP BP15G+ 3.43 - /dev/sg9 Groovy-proposed: #uname -r 5.8.0-56-generic #lsscsi -g [2:0:0:0]diskHGST HUH721212AL5205 NM05 /dev/sda /dev/sg0 [2:0:1:0]diskATA ST2000NM0033-9ZM GA6C /dev/sdb /dev/sg1 [2:0:2:0]diskHGST HUS726020ALS210 KU27 /dev/sdc /dev/sg2 [2:0:3:0]diskATA HUS722T1TALA600 MU03 /dev/sdd /dev/sg3 [2:0:4:0]enclosu DP BP15G+ 3.04 - /dev/sg4 [2:0:5:0]diskTOSHIBA AL15SEB060NY EF04 /dev/sde /dev/sg5 [2:0:6:0]diskATA INTEL SSDSC2BX40 DL2B /dev/sdf /dev/sg6 [2:0:7:0]diskTOSHIBA AL15SEB24EQY EF05 /dev/sdg /dev/sg7 [2:0:8:0]diskATA ST1000NX0443 NB33 /dev/sdh /dev/sg8 [2:0:9:0]enclosu DP BP15G+ 3.43 - /dev/sg9 ** Attachment added: "sosreport - focal proposed" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926517/+attachment/5503424/+files/sosreport-sujith-focalproposed-2021-06-09-ltpizuw.tar.xz -- 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/1926517 Title: [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] Whenever the driver is adding a vSES to virtual-phys list it is reinitializing the list head. Hence those vSES devices which were added previously are lost. [FIXES] Stop reinitializing the list every time a new vSES device is added. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=4c51f9569651 CommitID: 4c51f956965120b3441cdd39c358b87daba13e19 [TESTING] Load the mpt3sas driver on the system where Brodcom's HBA 9500 Tri-Mode Storage Adapter (IT HBA Aero/Ventura) is connected to two backplanes (so that two vSES device get configured on the HBA). After loading the driver user should able to access both the vSES devices. Also even after performing host reset operation user must able to access both the vSES devices. i.e. lsscsi must list both the vSES devices after loading the driver and also after performing host reset operation. [REGRESSION RISK] There is no regression risk with this bug fix patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926517/+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 1926517] Re: [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES
** Tags removed: verification-needed-focal verification-needed-groovy ** Tags added: verification-done-focal verification-done-groovy -- 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/1926517 Title: [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] Whenever the driver is adding a vSES to virtual-phys list it is reinitializing the list head. Hence those vSES devices which were added previously are lost. [FIXES] Stop reinitializing the list every time a new vSES device is added. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=4c51f9569651 CommitID: 4c51f956965120b3441cdd39c358b87daba13e19 [TESTING] Load the mpt3sas driver on the system where Brodcom's HBA 9500 Tri-Mode Storage Adapter (IT HBA Aero/Ventura) is connected to two backplanes (so that two vSES device get configured on the HBA). After loading the driver user should able to access both the vSES devices. Also even after performing host reset operation user must able to access both the vSES devices. i.e. lsscsi must list both the vSES devices after loading the driver and also after performing host reset operation. [REGRESSION RISK] There is no regression risk with this bug fix patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926517/+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 1811660] Re: [SRU] Unable to modify/create-namespace over NVDIMM-N
This is a kernel issue and we have seen this with upstream kernels and verified the fixes on upstream kernels. I expect bionic kernel 4.15 and above kernels to display this defect. Although I have not tried applying only the kernel fix on bionic, the test kernel shared above shows that original defect is resolved, however another one has popped up. This indicates that a few more patches are required to get the complete namespace modification functionality working. -- 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/1811660 Title: [SRU] Unable to modify/create-namespace over NVDIMM-N Status in The Dell-poweredge project: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Users are unable to modify or create namespaces over NVDIMM-N [Test Case] Steps to Reproduce: 1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & NVDIMM firmware to latest available to customers. 2. Install and boot to Ubuntu 18.04 3. Notice that no pmems are enumerated. 4. Try #ndctl create-namespace -> Failure with device or resource busy. Actual results: No pmems are enumerated, cannot create namespaces. If pmems are already present, then cannot modify the namespaces. Expected results: namespace creation should be possible [Regression Potential] The Regression Risk is low, Intel not impacted but Dell is. [Other Info] Additional Info: * Seen with upstream linux-4.20.2 also. * Upstream bug report - https://github.com/pmem/ndctl/issues/78 * Upstream kernel patch: https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html Request you to incorporate it in bionic and xenial kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1811660/+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 1811660] Re: [SRU] Unable to modify/create-namespace over NVDIMM-N
Another issue pops-up, looks like there are a few nvdimm patches that require backporting: # ndctl create-namespace -e "namespace0.0" -m fsdax -f -vvv libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (256 byte) labels libndctl: ndctl_dimm_enable: nmem0: failed to enable libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: sizeof_namespace_index: nmem0: label area (1024) too small to host (128 byte) labels libndctl: ndctl_dimm_enable: nmem0: failed to enable enable_labels:945: region0: failed to initialize labels namespace_reconfig:977: region0: no idle namespace seed failed to reconfigure namespace: No such device root@ubuntu:~# ndctl -v 61.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/1811660 Title: [SRU] Unable to modify/create-namespace over NVDIMM-N Status in The Dell-poweredge project: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Users are unable to modify or create namespaces over NVDIMM-N [Test Case] Steps to Reproduce: 1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & NVDIMM firmware to latest available to customers. 2. Install and boot to Ubuntu 18.04 3. Notice that no pmems are enumerated. 4. Try #ndctl create-namespace -> Failure with d
[Kernel-packages] [Bug 1795453] Re: [SRU] IO's are issued with incorrect Scatter Gather Buffer
Can we also get the above fixes in Xenial HWE kernels? I suppose Xenial HWE kernel is a fork of bionic LTS kernels.. -- 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/1795453 Title: [SRU] IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller [Test Case] Steps found in comment #60 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/60 [Regression Potential] The patches in Comment #59 have been accepted upstream. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/59 [Other Info] Product : Broadcom (LSI) Megaraid H840 controller --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7415 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor:
[Kernel-packages] [Bug 1811660] Re: Unable to modify/create-namespace over NVDIMM-N
Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811785 -- 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/1811660 Title: Unable to modify/create-namespace over NVDIMM-N Status in The Dell-poweredge project: New Status in linux package in Ubuntu: Incomplete Bug description: Steps to Reproduce: 1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & NVDIMM firmware to latest available to customers. 2. Install and boot to Ubuntu 18.04 3. Notice that no pmems are enumerated. 4. Try #ndctl create-namespace -> Failure with device or resource busy. Actual results: No pmems are enumerated, cannot create namespaces. If pmems are already present, then cannot modify the namespaces. Expected results: namespace creation should be possible Additional Info: * Seen with upstream linux-4.20.2 also. * Upstream bug report - https://github.com/pmem/ndctl/issues/78 * Upstream kernel patch: https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html Request you to incorporate it in bionic and xenial kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1811660/+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 1811660] Re: Unable to modify/create-namespace over NVDIMM-N
** Also affects: dell-poweredge Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811660 Title: Unable to modify/create-namespace over NVDIMM-N Status in The Dell-poweredge project: New Status in linux package in Ubuntu: Incomplete Bug description: Steps to Reproduce: 1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & NVDIMM firmware to latest available to customers. 2. Install and boot to Ubuntu 18.04 3. Notice that no pmems are enumerated. 4. Try #ndctl create-namespace -> Failure with device or resource busy. Actual results: No pmems are enumerated, cannot create namespaces. If pmems are already present, then cannot modify the namespaces. Expected results: namespace creation should be possible Additional Info: * Seen with upstream linux-4.20.2 also. * Upstream bug report - https://github.com/pmem/ndctl/issues/78 * Upstream kernel patch: https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html Request you to incorporate it in bionic and xenial kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1811660/+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 1811660] Re: Unable to modify/create-namespace over NVDIMM-N
Fix: acpi/nfit: Block function zero DSMs https://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git/commit/?h=libnvdimm-fixes&id=11189c1089da413aa4b5fd6be4c4d47c78968819 acpi/nfit: Fix command-supported detection https://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git/commit/?h=libnvdimm-fixes&id=5e9e38d0db1d29efed1dd4cf9a70115d33521be7 -- 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/1811660 Title: Unable to modify/create-namespace over NVDIMM-N Status in linux package in Ubuntu: Incomplete Bug description: Steps to Reproduce: 1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & NVDIMM firmware to latest available to customers. 2. Install and boot to Ubuntu 18.04 3. Notice that no pmems are enumerated. 4. Try #ndctl create-namespace -> Failure with device or resource busy. Actual results: No pmems are enumerated, cannot create namespaces. If pmems are already present, then cannot modify the namespaces. Expected results: namespace creation should be possible Additional Info: * Seen with upstream linux-4.20.2 also. * Upstream bug report - https://github.com/pmem/ndctl/issues/78 * Upstream kernel patch: https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html Request you to incorporate it in bionic and xenial kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811660/+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 1811660] Re: Unable to modify/create-namespace over NVDIMM-N
It can be seen across all 14G Dell EMC servers carrying NVDIMM-N. Current setup I have is a T640 with 1.6.13 BIOS and NVDIMM fw version-9324 -- 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/1811660 Title: Unable to modify/create-namespace over NVDIMM-N Status in linux package in Ubuntu: Incomplete Bug description: Steps to Reproduce: 1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & NVDIMM firmware to latest available to customers. 2. Install and boot to Ubuntu 18.04 3. Notice that no pmems are enumerated. 4. Try #ndctl create-namespace -> Failure with device or resource busy. Actual results: No pmems are enumerated, cannot create namespaces. If pmems are already present, then cannot modify the namespaces. Expected results: namespace creation should be possible Additional Info: * Seen with upstream linux-4.20.2 also. * Upstream bug report - https://github.com/pmem/ndctl/issues/78 * Upstream kernel patch: https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html Request you to incorporate it in bionic and xenial kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811660/+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 1811660] Re: Unable to modify/create-namespace over NVDIMM-N
Issue seen across all kernels of Ubuntu 18.04 -- 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/1811660 Title: Unable to modify/create-namespace over NVDIMM-N Status in linux package in Ubuntu: Incomplete Bug description: Steps to Reproduce: 1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & NVDIMM firmware to latest available to customers. 2. Install and boot to Ubuntu 18.04 3. Notice that no pmems are enumerated. 4. Try #ndctl create-namespace -> Failure with device or resource busy. Actual results: No pmems are enumerated, cannot create namespaces. If pmems are already present, then cannot modify the namespaces. Expected results: namespace creation should be possible Additional Info: * Seen with upstream linux-4.20.2 also. * Upstream bug report - https://github.com/pmem/ndctl/issues/78 * Upstream kernel patch: https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html Request you to incorporate it in bionic and xenial kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811660/+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 1811660] [NEW] Unable to modify/create-namespace over NVDIMM-N
Private bug reported: Steps to Reproduce: 1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & NVDIMM firmware to latest available to customers. 2. Install and boot to Ubuntu 18.04 3. Notice that no pmems are enumerated. 4. Try #ndctl create-namespace -> Failure with device or resource busy. Actual results: No pmems are enumerated, cannot create namespaces. If pmems are already present, then cannot modify the namespaces. Expected results: namespace creation should be possible Additional Info: * Seen with upstream linux-4.20.2 also. * Upstream bug report - https://github.com/pmem/ndctl/issues/78 * Upstream kernel patch: https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html Request you to incorporate it in bionic and xenial kernels. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- 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/1811660 Title: Unable to modify/create-namespace over NVDIMM-N Status in linux package in Ubuntu: New Bug description: Steps to Reproduce: 1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & NVDIMM firmware to latest available to customers. 2. Install and boot to Ubuntu 18.04 3. Notice that no pmems are enumerated. 4. Try #ndctl create-namespace -> Failure with device or resource busy. Actual results: No pmems are enumerated, cannot create namespaces. If pmems are already present, then cannot modify the namespaces. Expected results: namespace creation should be possible Additional Info: * Seen with upstream linux-4.20.2 also. * Upstream bug report - https://github.com/pmem/ndctl/issues/78 * Upstream kernel patch: https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html Request you to incorporate it in bionic and xenial kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811660/+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 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer
Broadcom submitted the fix upstream: https://marc.info/?l=linux-scsi&m=154514161019901&w=2 https://marc.info/?l=linux-scsi&m=154514161319908&w=2 https://marc.info/?l=linux-scsi&m=154514161619911&w=2 and the commit IDs of these patches from upstream: 894169db1246 scsi: megaraid_sas: Use 63-bit DMA addressing 7b9e2d348c2a scsi: megaraid_sas: driver version update Please include them in the Ubuntu 18.04 LTS kernels. -- 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/1795453 Title: IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: Confirmed Bug description: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7415 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:b
[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer
The 63bit dma_mask was just a test to understand the adress-wraparound by the fw. Nothing specific. PERC didn't go offline. Always ended up with OOM btw. -- 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/1795453 Title: IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: Confirmed Bug description: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7415 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7415 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415 dmi.sys.vendor: Dell Inc. --- ProblemType:
[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer
@sasikumarpc - We observed this scenario where the PERC goes offline: sgl_ptr->Address = f000 sgl_ptr->Length = 1000 We do not see a roll-over here.. Kernel is indicating to read 0x1000 bytes starting from address 0xf000 i.e till 0x which very well aligns with 64 bit dma_mask being assigned by megaraid_sas driver. Looks like kernel is working as expected based on the dma_mask set by megaraid_sas driver. Once the 32bit address gets exhausted, the kernel tries to get buffer based on 64bit dma_mask top-down. We are suspecting that the PERC firmware might not be able to handle this corner case. PERC did not go offline by changing the dma_mask to 63, and these initial results looks to be supporting this stance on fw. Can you please check this and revert? -- 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/1795453 Title: IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: Confirmed Bug description: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7415 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-i
[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer
With the 4.18.0-8-generic kernel, I see AMD IOMMU IO_PAGE_FAULTs for invalid addresses AMD-Vi: Event logged [IO_PAGE_FAULT device=e1:00.0 domain=0x address=0xfffd14c0 flags=0x0030] PERC controller is still present btw, but the vdbench stress crashed due to this page faults. ** Attachment added: "4.18 - amd- iommu - page_faults" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/+attachment/5204196/+files/4.18-stress_fails-page_faults.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/1795453 Title: IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: Confirmed Bug description: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7415 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: D
[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer
I see the disks going offline during stress in mainline 4.19.0-041900rc7-generic as well. Although the symptoms look different in 4.15 and 4.18 kernels, I feel the bug is not fixed; address being accessed is still out-of-range in this 16GB server. -- 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/1795453 Title: IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: Confirmed Bug description: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7415 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7415 dmi.product.sku
[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer
With latest 4.15 LTS kernels, I see the vdbench process crash and the PERC controller and the related disks go offline.. ** Attachment added: "4.15 - vdbench - disks go offline" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/+attachment/5204195/+files/4.15-stress_fails.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/1795453 Title: IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: Confirmed Bug description: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7415 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.pro
[Kernel-packages] [Bug 1798056] [NEW] [Feature] Set kernel config - IPMI_PANIC_EVENT
Private bug reported: We have a requirement to trigger Panic event from Linux IPMI native driver to BMC in case of kernel panic. To achieve this, linux IPMI driver should be built with kernel config IPMI_PANIC_EVENT to be set. However, it is not set with shipping Ubuntu version. Can we get this IPMI_PANIC_EVENT set with the future releases of Ubuntu 18.04? I will update the business justification later. ** Affects: dell-poweredge Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: dell-poweredge Importance: Undecided Status: New ** Information type changed from Public to Private -- 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/1798056 Title: [Feature] Set kernel config - IPMI_PANIC_EVENT Status in The Dell-poweredge project: New Status in linux package in Ubuntu: New Bug description: We have a requirement to trigger Panic event from Linux IPMI native driver to BMC in case of kernel panic. To achieve this, linux IPMI driver should be built with kernel config IPMI_PANIC_EVENT to be set. However, it is not set with shipping Ubuntu version. Can we get this IPMI_PANIC_EVENT set with the future releases of Ubuntu 18.04? I will update the business justification later. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1798056/+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 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer
@sasikumarpc - Ok. So when you say below v4.18 kernel fixes it, does it mean with increased memory or is it with the same setup where the issue was originally seen? Issue resolved Kernel Version - 4.18.0-8-generic -- 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/1795453 Title: IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: Confirmed Bug description: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7415 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7415 dmi.product.sku: SKU=
[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer
> Also another version (other than default version of Ubuntu 18.04.01) of 4.15 kernel fixes the issue Can you share this kernel version as well? -- 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/1795453 Title: IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: Incomplete Bug description: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7415 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7415 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug Ap
[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer
sasikumarpc - Can you share the specific kernel versions that you are using, where the issue is fixed? Can you also share the logs of pass & failure cases? -- 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/1795453 Title: IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: Incomplete Bug description: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/+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 1797587] [NEW] Intel NVMe drives timeout when nvme format is attempted
Private bug reported: Every time you run an nvme format on a Intel NVMe drive (whether specifying the secure/crypto erase options or not), the format apparently works (drive is wiped clean) but the drive's admin queue (queue 0) times out, making the nvme device driver flag an error and reset the controller. Here's an example: nvme-cli-1.5 # ./nvme format -l 0 /dev/nvme1 NVME Admin command error:ABORT_REQ(7) nvme-cli-1.5 # dmesg|tail -1 [79725.404910] nvme nvme1: I/O 151 QID 0 timeout, reset controller Patch required: https://github.com/torvalds/linux/commit/62843c2e4226057c83f520c74fe9c81a1891c331 Request you to include the patch for LTS kernel 4.15 of Ubuntu 18.04 ** Affects: dell-poweredge Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private ** Also affects: dell-poweredge Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797587 Title: Intel NVMe drives timeout when nvme format is attempted Status in The Dell-poweredge project: New Status in linux package in Ubuntu: New Bug description: Every time you run an nvme format on a Intel NVMe drive (whether specifying the secure/crypto erase options or not), the format apparently works (drive is wiped clean) but the drive's admin queue (queue 0) times out, making the nvme device driver flag an error and reset the controller. Here's an example: nvme-cli-1.5 # ./nvme format -l 0 /dev/nvme1 NVME Admin command error:ABORT_REQ(7) nvme-cli-1.5 # dmesg|tail -1 [79725.404910] nvme nvme1: I/O 151 QID 0 timeout, reset controller Patch required: https://github.com/torvalds/linux/commit/62843c2e4226057c83f520c74fe9c81a1891c331 Request you to include the patch for LTS kernel 4.15 of Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1797587/+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 1794110] Re: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD
@jsalisbury - Unfortunately we do not have that info in hand. I'll check if we can try getting it. I see the patches in HWE 4.18 kernel of 18.04.2. Thanks for including them in it. -- 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/1794110 Title: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD Status in The Dell-poweredge project: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: Max Payload Size for the NVMe device is not getting programmed correctly. The OS is trying to set the device MPS to match Root Port which is greater than Capability of Device, instead of looking for lowest common denominator. This is fixed in upstream kernel version 4.19. Below are the commits that fix the issue. Please help include them in Ubuntu releases. PCI: Skip MPS logic for Virtual Functions (VFs) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4 PCI: Match Root Port's MPS to endpoint's MPSS as necessary https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=9f0e89359775ee21fe1ea732e34edb52aef5addf To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1794110/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD
reboot is triggered using #systemctl reboot. systemd timeout of 30min does not help, system stays hung. Needs a manual power-reset. -- 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/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD Status in dellserver: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1796130] Re: Patches for Additional NVME Support
Description: These missing patches are basically to improve Ubuntu kernel support for NVMe Surprise Removel/hot-plug of NVMe disks. The patch list shared and formed above is from comparing the 4.18 HWE kernel that is already present in the -proposed apt repo. We would like to have these included into the HWE kernel 4.18 of 18.04.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/1796130 Title: Patches for Additional NVME Support Status in The Dell-poweredge project: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: Dell is requesting these patches for inclusion into 18.04.2 for additional NVME support PCI: Check for PCIe Link downtraining https://github.com/torvalds/linux/commit/2d1ce5ec2117d16047334a1aa4b62e0cfb5a0605 PCI/AER: Add sysfs attributes to provide AER stats and breakdown https://github.com/torvalds/linux/commit/81aa5206f9a7 PCI/AER: Honor "pcie_ports=native" even if HEST sets FIRMWARE_FIRST https://github.com/torvalds/linux/commit/7af02fcd84c1 PCI/AER: Don't clear AER bits if error handling is Firmware-First https://github.com/torvalds/linux/commit/45687f96c112 PCI: pciehp: Differentiate between surprise and safe removal https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/commit/?h=pci/hotplug&id=e76ac5875f5d5848558edc79a0869bf20765fec3 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1796130/+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 1794110] Re: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD
The cosmic test-kernel based on v4.18 is a Pass. Please include them in planned HWE kernels of 18.04.2 that is based on v4.18. The bionic test-kernel based on v4.15 is a Fail. This requires a few more patches to be included. -- 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/1794110 Title: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD Status in The Dell-poweredge project: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: Max Payload Size for the NVMe device is not getting programmed correctly. The OS is trying to set the device MPS to match Root Port which is greater than Capability of Device, instead of looking for lowest common denominator. This is fixed in upstream kernel version 4.19. Below are the commits that fix the issue. Please help include them in Ubuntu releases. PCI: Skip MPS logic for Virtual Functions (VFs) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4 PCI: Match Root Port's MPS to endpoint's MPSS as necessary https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=9f0e89359775ee21fe1ea732e34edb52aef5addf To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1794110/+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 1796631] [NEW] dcdbas: Add support for WSMT ACPI table
Private bug reported: Business case (Partner benefit): Dell: dcdbas driver is used to raise SMIs. Dell System BIOS will implement support for WSMT table soon. This change in dcdbas driver will implement support for WSMT table. Patch details: If the WSMT ACPI table is present and indicates that a fixed communication buffer should be used, use the firmware-specified buffer instead of allocating a buffer in memory for communications between the dcdbas driver and firmare. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/drivers/firmware?id=12c956c4f32e08799de452abe1e1ec6021b1e41f For details on WSMT, please refer to the 'Links to ACPI-related Documents' section below - http://www.uefi.org/acpi https://msdn.microsoft.com/windows/hardware/drivers/bringup/acpi-system- description-tables#wsmt Requesting this patch to be included into Ubuntu 18.04.2 HWE kernels. ** Affects: dell-poweredge Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private ** Also affects: dell-poweredge Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796631 Title: dcdbas: Add support for WSMT ACPI table Status in The Dell-poweredge project: New Status in linux package in Ubuntu: New Bug description: Business case (Partner benefit): Dell: dcdbas driver is used to raise SMIs. Dell System BIOS will implement support for WSMT table soon. This change in dcdbas driver will implement support for WSMT table. Patch details: If the WSMT ACPI table is present and indicates that a fixed communication buffer should be used, use the firmware-specified buffer instead of allocating a buffer in memory for communications between the dcdbas driver and firmare. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/drivers/firmware?id=12c956c4f32e08799de452abe1e1ec6021b1e41f For details on WSMT, please refer to the 'Links to ACPI-related Documents' section below - http://www.uefi.org/acpi https://msdn.microsoft.com/windows/hardware/drivers/bringup/acpi- system-description-tables#wsmt Requesting this patch to be included into Ubuntu 18.04.2 HWE kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1796631/+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 1794110] Re: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD
Thank you for sharing a test-kernel. We will test it and revert back here with test-results. Thanks, Sujith -- 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/1794110 Title: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD Status in The Dell-poweredge project: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: Max Payload Size for the NVMe device is not getting programmed correctly. The OS is trying to set the device MPS to match Root Port which is greater than Capability of Device, instead of looking for lowest common denominator. This is fixed in upstream kernel version 4.19. Below are the commits that fix the issue. Please help include them in Ubuntu releases. PCI: Skip MPS logic for Virtual Functions (VFs) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4 PCI: Match Root Port's MPS to endpoint's MPSS as necessary https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=9f0e89359775ee21fe1ea732e34edb52aef5addf To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1794110/+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 1794110] [NEW] MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD
Public bug reported: Max Payload Size for the NVMe device is not getting programmed correctly. The OS is trying to set the device MPS to match Root Port which is greater than Capability of Device, instead of looking for lowest common denominator. This is fixed in upstream kernel version 4.19. Below are the commits that fix the issue. Please help include them in Ubuntu releases. PCI: Skip MPS logic for Virtual Functions (VFs) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4 PCI: Match Root Port's MPS to endpoint's MPSS as necessary https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=9f0e89359775ee21fe1ea732e34edb52aef5addf ** Affects: dell-poweredge Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Also affects: dell-poweredge Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794110 Title: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD Status in The Dell-poweredge project: New Status in linux package in Ubuntu: Incomplete Bug description: Max Payload Size for the NVMe device is not getting programmed correctly. The OS is trying to set the device MPS to match Root Port which is greater than Capability of Device, instead of looking for lowest common denominator. This is fixed in upstream kernel version 4.19. Below are the commits that fix the issue. Please help include them in Ubuntu releases. PCI: Skip MPS logic for Virtual Functions (VFs) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4 PCI: Match Root Port's MPS to endpoint's MPSS as necessary https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=9f0e89359775ee21fe1ea732e34edb52aef5addf To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1794110/+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 1772434] Re: Broadcom: IT (HBA) Driver Enablement in 18.04 (Patches)
Can you guys share the release plans for kernel-4.15.0-33.36? We have a installation/boot failure with HBA330 and the patches in this list are fixing it. -- 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/1772434 Title: Broadcom: IT (HBA) Driver Enablement in 18.04 (Patches) Status in dellserver: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: The purpose of this bug is to track the patches needed to enable the IT (HBA) driver into 18.04. Below are upstream commit ids of IT driver which went in over the in- box driver of Ubuntu18.04 OS’s base kernel, 864449eea7c600596e305ffdc4a6a846414b222c scsi: mpt3sas: Do not mark fw_event workqueue as WQ_MEM_RECLAIM 6f9e09fd6488de7661ee20efb5d8ab4e05a59735 scsi: mpt3sas: clarify mmio pointer types 40114bde9773ccaf9ad77233ac2cc9039f0f2941 scsi: mpt3sas: Do not use 32-bit atomic request descriptor for Ventura controllers. b4472d7180894c96b6133ef5ff3df50836591eaa scsi: mpt3sas: Introduce function to clone mpi reply. e5747439366c1079257083f231f5dd9a84bf0fd7 scsi: mpt3sas: Introduce function to clone mpi request. 182ac784b41faee02e8b44cd7149575258ad6858 scsi: mpt3sas: Introduce Base function for cloning. 22ae5a3c2599381cf7aaa5aca25c515a3166adcc scsi: mpt3sas: Introduce API to get BAR0 mapped buffer address 0448f0195124e33f11d15b7d1e1cab959989eee7 scsi: mpt3sas: Configure reply post queue depth, DMA and sgl tablesize. c520691b38cde1d94f53e5782feba892f5645043 scsi: mpt3sas: Add PCI device ID for Andromeda. 4a8842de8db4953fdda7866626b78b12fb8adb97 scsi: mpt3sas: fix an out of bound write 61dfb8a5fb7e93e692856026fa4c778a27f28984 scsi: mpt3sas: make function _get_st_from_smid static dbec4c9040edc15442c3ebdb65408aa9d3b82c24 scsi: mpt3sas: lockless command submission 272e253c7bcabfeef5f4d0aaed94a413e13e520f scsi: mpt3sas: simplify _wait_for_commands_to_complete() 6da999fe5a9285c2a78f3cf1e768abcd48d7607e scsi: mpt3sas: simplify mpt3sas_scsi_issue_tm() 74fcfa5371b7a681e864d3a9d3b9ecfd5737d8ea scsi: mpt3sas: simplify task management functions b0cd285eb57cd3cb18d882565c22d39bccffe7f0 scsi: mpt3sas: always use first reserved smid for ioctl passthrough 9961c9bbf2b43acaaf030a0fbabc9954d937ad8c scsi: mpt3sas: check command status before attempting abort 12e7c6782bc58128392b768fc2a87b230414a2a5 scsi: mpt3sas: Introduce mpt3sas_get_st_from_smid() 02a386df3678275b01eec71fee39735c379e4a2a scsi: mpt3sas: open-code _scsih_scsi_lookup_get() 6a2d4618aef3d4ffb83514e5e58a091d61e54a03 scsi: mpt3sas: separate out _base_recovery_check() 05303dfb738066ad597d7feb422ff9fa2d3d8ef3 scsi: mpt3sas: use list_splice_init() ba4494d47bd02e5757b449a2ccfa3ff87bc8 scsi: mpt3sas: set default value for cb_idx f49d4aed1315a7b766d855f1367142e682b0cc87 scsi: mpt3sas: Proper handling of set/clear of "ATA command pending" flag. 45b7aef7fb7d5f5bfa3a2a6727f1accf7660f6fd scsi: mpt3sas: Remove unused variable requeue_event To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1772434/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD
Any update on this? -- 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/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD Status in dellserver: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in systemd source package in Bionic: New Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1779605] Re: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen
** Attachment added: "dmesg - test-kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779605/+attachment/5161476/+files/dmesg-test-kernel.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/1779605 Title: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen Status in dellserver: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When installing and booting to Ubuntu 18.04 Server, we see this error being shown on screen (Attached Screenshot) Setup details- Take a DellEMC 14G server and start installation of Ubuntu 18.04 Server. Observe this message in #dmesg. Cosmetic error message, no functionality loss. Upstream patch details: https://www.spinics.net/lists/linux-acpi/msg81863.html Please include these in future builds of Ubuntu 18.04. Uploading the #dmesg logs. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1779605/+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 1779605] Re: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen
Verified the test-kernel shared in the above link on the same setup where the issue was seen with bionic kernels. Uploading dmesg. Issue seems to be fixed and change observed now is: [0.229581] Detected 1 PCC Subspaces [0.229581] Registering PCC driver as Mailbox controller -- 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/1779605 Title: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen Status in dellserver: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When installing and booting to Ubuntu 18.04 Server, we see this error being shown on screen (Attached Screenshot) Setup details- Take a DellEMC 14G server and start installation of Ubuntu 18.04 Server. Observe this message in #dmesg. Cosmetic error message, no functionality loss. Upstream patch details: https://www.spinics.net/lists/linux-acpi/msg81863.html Please include these in future builds of Ubuntu 18.04. Uploading the #dmesg logs. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1779605/+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 1779605] Re: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen
The v4 was proposed and applied: https://patchwork.kernel.org/patch/10404957/ I feel only the 3/3 (3rd patch in whole series) is enough to deal with this bug. If you could give me a test kernel, I shall verify it and confirm it here. -- 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/1779605 Title: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen Status in dellserver: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When installing and booting to Ubuntu 18.04 Server, we see this error being shown on screen (Attached Screenshot) Setup details- Take a DellEMC 14G server and start installation of Ubuntu 18.04 Server. Observe this message in #dmesg. Cosmetic error message, no functionality loss. Upstream patch details: https://www.spinics.net/lists/linux-acpi/msg81863.html Please include these in future builds of Ubuntu 18.04. Uploading the #dmesg logs. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1779605/+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 1748689] Re: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2"
** Also affects: dellserver Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748689 Title: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2" Status in dellserver: New Status in linux package in Ubuntu: Confirmed Bug description: Xubuntu 17.10 artful Kernel: x86_64 Linux 4.13.0-32.35-generic cifs-utils 2:6.7-1 smbclient 2:4.6.7+dfsg-1ubuntu3.1 Mounting an SMB share with sec=ntlmssp,vers=3.0,credentials=/home/.smbcredentials,dir_mode=0777,file_mode=0777 in /etc/fstab gives the error: "CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2" in dmesg. Shares mounted this way are readable, but writing data to them (or using programs such as EasyTAG to write to them) ultimately fails. This bug did not occur in kernel 4.10. Mounting the share(s) with vers=1.0 does not give the error, but this is a haphazard fix as SMB v3.0 carries many security features with it not avaliable in SMB 1.0. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=/dev/mapper/DeusVitam--vg-swap_1 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=/dev/mapper/hostname--vg-root ro splash quiet amdgpu.cik_support=1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: Tags: artful Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to artful on 2018-02-05 (7 days ago) UserGroups: libvirt libvirtd sudo wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-E/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd03/16/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-E/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1748689/+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 1779605] Re: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen
Moving back to 'Confirmed' as mentioned in c#3, since dmesg logs are already attached. If more logs are required, please let me know. ** 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/1779605 Title: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen Status in dellserver: New Status in linux package in Ubuntu: Confirmed Bug description: When installing and booting to Ubuntu 18.04 Server, we see this error being shown on screen (Attached Screenshot) Setup details- Take a DellEMC 14G server and start installation of Ubuntu 18.04 Server. Observe this message in #dmesg. Cosmetic error message, no functionality loss. Upstream patch details: https://www.spinics.net/lists/linux-acpi/msg81863.html Please include these in future builds of Ubuntu 18.04. Uploading the #dmesg logs. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1779605/+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 1779605] Re: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen
** Attachment added: "Screenshot" https://bugs.launchpad.net/dellserver/+bug/1779605/+attachment/5158528/+files/PCCT_error.jpg -- 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/1779605 Title: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen Status in dellserver: New Status in linux package in Ubuntu: New Bug description: When installing and booting to Ubuntu 18.04 Server, we see this error being shown on screen (Attached Screenshot) Setup details- Take a DellEMC 14G server and start installation of Ubuntu 18.04 Server. Observe this message in #dmesg. Cosmetic error message, no functionality loss. Upstream patch details: https://www.spinics.net/lists/linux-acpi/msg81863.html Please include these in future builds of Ubuntu 18.04. Uploading the #dmesg logs. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1779605/+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 1779605] [NEW] [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen
Public bug reported: When installing and booting to Ubuntu 18.04 Server, we see this error being shown on screen (Attached Screenshot) Setup details- Take a DellEMC 14G server and start installation of Ubuntu 18.04 Server. Observe this message in #dmesg. Cosmetic error message, no functionality loss. Upstream patch details: https://www.spinics.net/lists/linux-acpi/msg81863.html Please include these in future builds of Ubuntu 18.04. Uploading the #dmesg logs. ** Affects: dellserver Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/1779605/+attachment/5158527/+files/dmesg.txt ** Also affects: dellserver Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779605 Title: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen Status in dellserver: New Status in linux package in Ubuntu: New Bug description: When installing and booting to Ubuntu 18.04 Server, we see this error being shown on screen (Attached Screenshot) Setup details- Take a DellEMC 14G server and start installation of Ubuntu 18.04 Server. Observe this message in #dmesg. Cosmetic error message, no functionality loss. Upstream patch details: https://www.spinics.net/lists/linux-acpi/msg81863.html Please include these in future builds of Ubuntu 18.04. Uploading the #dmesg logs. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1779605/+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 1748689] Re: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2"
I see this on 4.13.0-45-generic of Ubuntu 16.04 HWE kernels. -- 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/1748689 Title: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2" Status in linux package in Ubuntu: Confirmed Bug description: Xubuntu 17.10 artful Kernel: x86_64 Linux 4.13.0-32.35-generic cifs-utils 2:6.7-1 smbclient 2:4.6.7+dfsg-1ubuntu3.1 Mounting an SMB share with sec=ntlmssp,vers=3.0,credentials=/home/.smbcredentials,dir_mode=0777,file_mode=0777 in /etc/fstab gives the error: "CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2" in dmesg. Shares mounted this way are readable, but writing data to them (or using programs such as EasyTAG to write to them) ultimately fails. This bug did not occur in kernel 4.10. Mounting the share(s) with vers=1.0 does not give the error, but this is a haphazard fix as SMB v3.0 carries many security features with it not avaliable in SMB 1.0. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=/dev/mapper/DeusVitam--vg-swap_1 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=/dev/mapper/hostname--vg-root ro splash quiet amdgpu.cik_support=1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: Tags: artful Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to artful on 2018-02-05 (7 days ago) UserGroups: libvirt libvirtd sudo wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-E/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd03/16/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-E/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748689/+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 1778717] Re: Ubuntu 18.04 guest hangs during diskio stress
Moving back to Confirmed state - since all the available logs are already uploaded. ** 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/1778717 Title: Ubuntu 18.04 guest hangs during diskio stress Status in dellserver: New Status in linux package in Ubuntu: Confirmed Bug description: Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and Ubuntu 18.04 (latest updates) guest. Guest has 3 data disks apart from the boot disk. All these disks are exposed through "ParaVirtual SCSI controller" from the host ESXi 6.7. Run diskio stress on all the 3 data disks for overnight. Guest goes unresponsive (even ping fails) in between. Only way to recover is to reset the guest. Logs do not indicate much on this error. Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of different hits. We have tried mainline kernel v4.18-rc-2 and have hit the issue there as well. Changing the SCSI controller to "LSI Logic SAS adapter" helps and we have not seen any crash/hang here. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1778717/+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 1778717] Re: Ubuntu 18.04 guest hangs during diskio stress
* Also hit with 16.04.4 HWE kernel 4.13.0-45-generic. * Not seen with LTS kernel 4.4 of Ubuntu 16.04 ** Also affects: dellserver Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778717 Title: Ubuntu 18.04 guest hangs during diskio stress Status in dellserver: New Status in linux package in Ubuntu: Confirmed Bug description: Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and Ubuntu 18.04 (latest updates) guest. Guest has 3 data disks apart from the boot disk. All these disks are exposed through "ParaVirtual SCSI controller" from the host ESXi 6.7. Run diskio stress on all the 3 data disks for overnight. Guest goes unresponsive (even ping fails) in between. Only way to recover is to reset the guest. Logs do not indicate much on this error. Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of different hits. We have tried mainline kernel v4.18-rc-2 and have hit the issue there as well. Changing the SCSI controller to "LSI Logic SAS adapter" helps and we have not seen any crash/hang here. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1778717/+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 1778717] Re: Ubuntu 18.04 guest hangs during diskio stress
** Attachment added: "screenshot-2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778717/+attachment/5156771/+files/image-2018-06-22-14-48-57-801.png -- 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/1778717 Title: Ubuntu 18.04 guest hangs during diskio stress Status in dellserver: New Status in linux package in Ubuntu: Confirmed Bug description: Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and Ubuntu 18.04 (latest updates) guest. Guest has 3 data disks apart from the boot disk. All these disks are exposed through "ParaVirtual SCSI controller" from the host ESXi 6.7. Run diskio stress on all the 3 data disks for overnight. Guest goes unresponsive (even ping fails) in between. Only way to recover is to reset the guest. Logs do not indicate much on this error. Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of different hits. We have tried mainline kernel v4.18-rc-2 and have hit the issue there as well. Changing the SCSI controller to "LSI Logic SAS adapter" helps and we have not seen any crash/hang here. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1778717/+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 1778717] Re: Ubuntu 18.04 guest hangs during diskio stress
** Attachment added: "screenshot-1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778717/+attachment/5156770/+files/image-2018-06-25-10-13-05-871.png -- 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/1778717 Title: Ubuntu 18.04 guest hangs during diskio stress Status in dellserver: New Status in linux package in Ubuntu: Confirmed Bug description: Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and Ubuntu 18.04 (latest updates) guest. Guest has 3 data disks apart from the boot disk. All these disks are exposed through "ParaVirtual SCSI controller" from the host ESXi 6.7. Run diskio stress on all the 3 data disks for overnight. Guest goes unresponsive (even ping fails) in between. Only way to recover is to reset the guest. Logs do not indicate much on this error. Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of different hits. We have tried mainline kernel v4.18-rc-2 and have hit the issue there as well. Changing the SCSI controller to "LSI Logic SAS adapter" helps and we have not seen any crash/hang here. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1778717/+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 1778717] [NEW] Ubuntu 18.04 guest hangs during diskio stress
Public bug reported: Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and Ubuntu 18.04 (latest updates) guest. Guest has 3 data disks apart from the boot disk. All these disks are exposed through "ParaVirtual SCSI controller" from the host ESXi 6.7. Run diskio stress on all the 3 data disks for overnight. Guest goes unresponsive (even ping fails) in between. Only way to recover is to reset the guest. Logs do not indicate much on this error. Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of different hits. We have tried mainline kernel v4.18-rc-2 and have hit the issue there as well. Changing the SCSI controller to "LSI Logic SAS adapter" helps and we have not seen any crash/hang here. ** Affects: dellserver Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bionic ** Attachment added: "log files inside /var/log/" https://bugs.launchpad.net/bugs/1778717/+attachment/5156769/+files/var-log-ubuntu1804-vm.zip -- 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/1778717 Title: Ubuntu 18.04 guest hangs during diskio stress Status in dellserver: New Status in linux package in Ubuntu: Confirmed Bug description: Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and Ubuntu 18.04 (latest updates) guest. Guest has 3 data disks apart from the boot disk. All these disks are exposed through "ParaVirtual SCSI controller" from the host ESXi 6.7. Run diskio stress on all the 3 data disks for overnight. Guest goes unresponsive (even ping fails) in between. Only way to recover is to reset the guest. Logs do not indicate much on this error. Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of different hits. We have tried mainline kernel v4.18-rc-2 and have hit the issue there as well. Changing the SCSI controller to "LSI Logic SAS adapter" helps and we have not seen any crash/hang here. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1778717/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers
I think I narrowed it down to these: v4.14 - No issue observed v4.15-rc-1 - Issue observed Wherever the issue is observed, if I blacklist or rmmod ahci driver before reboot, no issue is observed (because the SATA ODD is gone now). -- 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/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers Status in dellserver: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in systemd source package in Bionic: New Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers
I am observing that in the absence of any network (interfaces not configured for dhcp/static) I can see the graceful reboot halting almost every reboot. * Issue is observed with Ubuntu 18.04 kernel 4.15.0-23-generic * Also observed with 4.18-rc1 hosted at http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc1 Attaching the log which contains failure for both these cases. Do you think systemd could be the suspect? ** Attachment added: "4.18 fail and 4.15.0-23 fail" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777674/+attachment/5154491/+files/nf_odd.log -- 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/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers Status in dellserver: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in systemd source package in Bionic: New Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers
Update: I was under the assumption that kvm/kvm_amd module was the suspect. But I was wrong. Reason - I tried performing '#modprobe -r kvm_amd kvm' before issuing '#systemctl reboot' in the reboot script and the system still halted with Ubuntu 18.04 kernel. @jsalisbury - I will keep it today and update you by tomorrow. -- 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/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers Status in dellserver: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in systemd source package in Bionic: New Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers
Moving the bug-report back to Confirmed since these logs like "kvm exiting hardware virt" and the logs post this are not stored on the physical disks (reason - disks are already unmounted). Such logs are available only in the console logs which are already uploaded in this report. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => New ** 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/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers Status in dellserver: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers
Logs where the hang is not seen: [ 75.448494] kvm: exiting hardware virtualization [ 76.187482] reboot: Restarting system [ 76.191663] reboot: machine restart [ 76.197621] ACPI MEMORY or I/O RESET_REG. The last 3 lines are not seen when the hang is observed. ** Attachment added: "console-logs-no-failure-case" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777674/+attachment/5154317/+files/console-logs-no-failure.txt ** Also affects: dellserver Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers Status in dellserver: New Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1777674] [NEW] Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers
Public bug reported: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. ** Affects: dellserver Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "console-logs" https://bugs.launchpad.net/bugs/1777674/+attachment/5154314/+files/console-logs.txt ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers Status in dellserver: New Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+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
