Activity log for bug #1732804

Date Who What changed Old value New value Message
2017-11-17 00:21:17 Manoj Iyer bug added bug
2017-11-17 00:30:06 Ubuntu Kernel Bot linux (Ubuntu): status New Incomplete
2017-11-17 00:30:08 Ubuntu Kernel Bot tags qdf2400 artful qdf2400
2017-11-17 00:40:16 Manoj Iyer nominated for series Ubuntu Bionic
2017-11-17 00:40:16 Manoj Iyer nominated for series Ubuntu Artful
2017-11-17 00:40:16 Manoj Iyer nominated for series Ubuntu Zesty
2017-11-18 06:08:05 Manoj Iyer description [Impact] Passing through a physical function like the Mellanox PCIE ethernet controller causes the guest to fail booting, and host reports Hardware Error. == Host == [109920.834703] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 4 [109920.842142] {1}[Hardware Error]: event severity: recoverable [109920.847848] {1}[Hardware Error]: precise tstamp: 2017-11-16 23:20:05 [109920.854385] {1}[Hardware Error]: Error 0, type: recoverable [109920.860111] {1}[Hardware Error]: section_type: PCIe error [109920.865718] {1}[Hardware Error]: port_type: 0, PCIe end point [109920.871708] {1}[Hardware Error]: version: 3.0 [109920.876343] {1}[Hardware Error]: command: 0x0006, status: 0x0010 [109920.882559] {1}[Hardware Error]: device_id: 0000:01:00.0 [109920.888113] {1}[Hardware Error]: slot: 0 [109920.892285] {1}[Hardware Error]: secondary_bus: 0x00 [109920.897489] {1}[Hardware Error]: vendor_id: 0x15b3, device_id: 0x1013 [109920.904172] {1}[Hardware Error]: class_code: 000002 [109920.909378] vfio-pci 0000:01:00.0: aer_status: 0x00040000, aer_mask: 0x00000000 [109920.916675] Malformed TLP [109920.916678] vfio-pci 0000:01:00.0: aer_layer=Transaction Layer, aer_agent=Receiver ID [109920.924573] vfio-pci 0000:01:00.0: aer_uncor_severity: 0x00062010 [109920.930736] vfio-pci 0000:01:00.0: TLP Header: 4a008040 00000100 01000000 00000000 [109920.938548] vfio-pci 0000:01:00.0: broadcast error_detected message [109921.965056] pcieport 0000:00:00.0: downstream link has been reset [109921.965062] vfio-pci 0000:01:00.0: broadcast mmio_enabled message [109921.965066] vfio-pci 0000:01:00.0: broadcast resume message [109921.965070] vfio-pci 0000:01:00.0: AER: Device recovery successful == Guest == EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [ 1.518252] kvm [1]: HYP mode not available [ 2.578929] mlx5_core 0000:05:00.0: mlx5_core_set_issi:778:(pid 152): Failed to query ISSI err(-1) status(0) synd(0) [ 2.582424] mlx5_core 0000:05:00.0: failed to set issi [ 2.616756] mlx5_core 0000:05:00.0: mlx5_load_one failed with error code -1 This is because, virtualization of physical functions are broken on systems with Maximum Payload Size bigger than 128. QDF2400 FW tries to maximize this setting. We have observed an MPS of 512 on QDF2400 systems. [Fix] Patches are in linux-next: 523184972b28 vfio/pci: Virtualize Maximum Payload Size 523184972b28 vfio/pci: Virtualize Maximum Payload Size [Testing] With the above patches applied the guest is able to boot when PCIE physical function is passthrough and we don't see the errors on the host system. == On the Guest == ubuntu@ubuntu-pcitest:~$ lspci 00:00.0 Host bridge: Red Hat, Inc. Device 0008 00:01.0 PCI bridge: Red Hat, Inc. Device 000c 00:01.1 PCI bridge: Red Hat, Inc. Device 000c 00:01.2 PCI bridge: Red Hat, Inc. Device 000c 00:01.3 PCI bridge: Red Hat, Inc. Device 000c 00:01.4 PCI bridge: Red Hat, Inc. Device 000c 00:01.5 PCI bridge: Red Hat, Inc. Device 000c 01:00.0 Ethernet controller: Red Hat, Inc Virtio network device (rev 01) 02:00.0 Communication controller: Red Hat, Inc Virtio console (rev 01) 03:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01) 04:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01) 05:00.0 Ethernet controller: Mellanox Technologies MT27700 Family [ConnectX-4] ubuntu@ubuntu-pcitest:~$ lsmod | grep mlx mlx5_core 471040 0 devlink 36864 1 mlx5_core ptp 28672 1 mlx5_core [Regression Potential] Two patches to drivers/vfio/pci were cleanly cherry picked from linux-next and applied to Artful/Zesty. Tested on ARM64 QDF2400 system and no regressions were found. [Impact] Passing through a physical function like the Mellanox PCIE ethernet controller causes the guest to fail booting, and host reports Hardware Error. == Host == [109920.834703] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 4 [109920.842142] {1}[Hardware Error]: event severity: recoverable [109920.847848] {1}[Hardware Error]: precise tstamp: 2017-11-16 23:20:05 [109920.854385] {1}[Hardware Error]: Error 0, type: recoverable [109920.860111] {1}[Hardware Error]: section_type: PCIe error [109920.865718] {1}[Hardware Error]: port_type: 0, PCIe end point [109920.871708] {1}[Hardware Error]: version: 3.0 [109920.876343] {1}[Hardware Error]: command: 0x0006, status: 0x0010 [109920.882559] {1}[Hardware Error]: device_id: 0000:01:00.0 [109920.888113] {1}[Hardware Error]: slot: 0 [109920.892285] {1}[Hardware Error]: secondary_bus: 0x00 [109920.897489] {1}[Hardware Error]: vendor_id: 0x15b3, device_id: 0x1013 [109920.904172] {1}[Hardware Error]: class_code: 000002 [109920.909378] vfio-pci 0000:01:00.0: aer_status: 0x00040000, aer_mask: 0x00000000 [109920.916675] Malformed TLP [109920.916678] vfio-pci 0000:01:00.0: aer_layer=Transaction Layer, aer_agent=Receiver ID [109920.924573] vfio-pci 0000:01:00.0: aer_uncor_severity: 0x00062010 [109920.930736] vfio-pci 0000:01:00.0: TLP Header: 4a008040 00000100 01000000 00000000 [109920.938548] vfio-pci 0000:01:00.0: broadcast error_detected message [109921.965056] pcieport 0000:00:00.0: downstream link has been reset [109921.965062] vfio-pci 0000:01:00.0: broadcast mmio_enabled message [109921.965066] vfio-pci 0000:01:00.0: broadcast resume message [109921.965070] vfio-pci 0000:01:00.0: AER: Device recovery successful == Guest == EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [ 1.518252] kvm [1]: HYP mode not available [ 2.578929] mlx5_core 0000:05:00.0: mlx5_core_set_issi:778:(pid 152): Failed to query ISSI err(-1) status(0) synd(0) [ 2.582424] mlx5_core 0000:05:00.0: failed to set issi [ 2.616756] mlx5_core 0000:05:00.0: mlx5_load_one failed with error code -1 This is because, virtualization of physical functions are broken on systems with Maximum Payload Size bigger than 128. QDF2400 FW tries to maximize this setting. We have observed an MPS of 512 on QDF2400 systems. [Fix] Patches are in linux-next: cf0d53ba4947 vfio/pci: Virtualize Maximum Read Request Size 523184972b28 vfio/pci: Virtualize Maximum Payload Size [Testing] With the above patches applied the guest is able to boot when PCIE physical function is passthrough and we don't see the errors on the host system. == On the Guest == ubuntu@ubuntu-pcitest:~$ lspci 00:00.0 Host bridge: Red Hat, Inc. Device 0008 00:01.0 PCI bridge: Red Hat, Inc. Device 000c 00:01.1 PCI bridge: Red Hat, Inc. Device 000c 00:01.2 PCI bridge: Red Hat, Inc. Device 000c 00:01.3 PCI bridge: Red Hat, Inc. Device 000c 00:01.4 PCI bridge: Red Hat, Inc. Device 000c 00:01.5 PCI bridge: Red Hat, Inc. Device 000c 01:00.0 Ethernet controller: Red Hat, Inc Virtio network device (rev 01) 02:00.0 Communication controller: Red Hat, Inc Virtio console (rev 01) 03:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01) 04:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01) 05:00.0 Ethernet controller: Mellanox Technologies MT27700 Family [ConnectX-4] ubuntu@ubuntu-pcitest:~$ lsmod | grep mlx mlx5_core 471040 0 devlink 36864 1 mlx5_core ptp 28672 1 mlx5_core [Regression Potential] Two patches to drivers/vfio/pci were cleanly cherry picked from linux-next and applied to Artful/Zesty. Tested on ARM64 QDF2400 system and no regressions were found.
2017-11-18 06:09:21 Manoj Iyer description [Impact] Passing through a physical function like the Mellanox PCIE ethernet controller causes the guest to fail booting, and host reports Hardware Error. == Host == [109920.834703] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 4 [109920.842142] {1}[Hardware Error]: event severity: recoverable [109920.847848] {1}[Hardware Error]: precise tstamp: 2017-11-16 23:20:05 [109920.854385] {1}[Hardware Error]: Error 0, type: recoverable [109920.860111] {1}[Hardware Error]: section_type: PCIe error [109920.865718] {1}[Hardware Error]: port_type: 0, PCIe end point [109920.871708] {1}[Hardware Error]: version: 3.0 [109920.876343] {1}[Hardware Error]: command: 0x0006, status: 0x0010 [109920.882559] {1}[Hardware Error]: device_id: 0000:01:00.0 [109920.888113] {1}[Hardware Error]: slot: 0 [109920.892285] {1}[Hardware Error]: secondary_bus: 0x00 [109920.897489] {1}[Hardware Error]: vendor_id: 0x15b3, device_id: 0x1013 [109920.904172] {1}[Hardware Error]: class_code: 000002 [109920.909378] vfio-pci 0000:01:00.0: aer_status: 0x00040000, aer_mask: 0x00000000 [109920.916675] Malformed TLP [109920.916678] vfio-pci 0000:01:00.0: aer_layer=Transaction Layer, aer_agent=Receiver ID [109920.924573] vfio-pci 0000:01:00.0: aer_uncor_severity: 0x00062010 [109920.930736] vfio-pci 0000:01:00.0: TLP Header: 4a008040 00000100 01000000 00000000 [109920.938548] vfio-pci 0000:01:00.0: broadcast error_detected message [109921.965056] pcieport 0000:00:00.0: downstream link has been reset [109921.965062] vfio-pci 0000:01:00.0: broadcast mmio_enabled message [109921.965066] vfio-pci 0000:01:00.0: broadcast resume message [109921.965070] vfio-pci 0000:01:00.0: AER: Device recovery successful == Guest == EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [ 1.518252] kvm [1]: HYP mode not available [ 2.578929] mlx5_core 0000:05:00.0: mlx5_core_set_issi:778:(pid 152): Failed to query ISSI err(-1) status(0) synd(0) [ 2.582424] mlx5_core 0000:05:00.0: failed to set issi [ 2.616756] mlx5_core 0000:05:00.0: mlx5_load_one failed with error code -1 This is because, virtualization of physical functions are broken on systems with Maximum Payload Size bigger than 128. QDF2400 FW tries to maximize this setting. We have observed an MPS of 512 on QDF2400 systems. [Fix] Patches are in linux-next: cf0d53ba4947 vfio/pci: Virtualize Maximum Read Request Size 523184972b28 vfio/pci: Virtualize Maximum Payload Size [Testing] With the above patches applied the guest is able to boot when PCIE physical function is passthrough and we don't see the errors on the host system. == On the Guest == ubuntu@ubuntu-pcitest:~$ lspci 00:00.0 Host bridge: Red Hat, Inc. Device 0008 00:01.0 PCI bridge: Red Hat, Inc. Device 000c 00:01.1 PCI bridge: Red Hat, Inc. Device 000c 00:01.2 PCI bridge: Red Hat, Inc. Device 000c 00:01.3 PCI bridge: Red Hat, Inc. Device 000c 00:01.4 PCI bridge: Red Hat, Inc. Device 000c 00:01.5 PCI bridge: Red Hat, Inc. Device 000c 01:00.0 Ethernet controller: Red Hat, Inc Virtio network device (rev 01) 02:00.0 Communication controller: Red Hat, Inc Virtio console (rev 01) 03:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01) 04:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01) 05:00.0 Ethernet controller: Mellanox Technologies MT27700 Family [ConnectX-4] ubuntu@ubuntu-pcitest:~$ lsmod | grep mlx mlx5_core 471040 0 devlink 36864 1 mlx5_core ptp 28672 1 mlx5_core [Regression Potential] Two patches to drivers/vfio/pci were cleanly cherry picked from linux-next and applied to Artful/Zesty. Tested on ARM64 QDF2400 system and no regressions were found. [Impact] Passing through a physical function like the Mellanox PCIE ethernet controller causes the guest to fail booting, and host reports Hardware Error. == Host == [109920.834703] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 4 [109920.842142] {1}[Hardware Error]: event severity: recoverable [109920.847848] {1}[Hardware Error]: precise tstamp: 2017-11-16 23:20:05 [109920.854385] {1}[Hardware Error]: Error 0, type: recoverable [109920.860111] {1}[Hardware Error]: section_type: PCIe error [109920.865718] {1}[Hardware Error]: port_type: 0, PCIe end point [109920.871708] {1}[Hardware Error]: version: 3.0 [109920.876343] {1}[Hardware Error]: command: 0x0006, status: 0x0010 [109920.882559] {1}[Hardware Error]: device_id: 0000:01:00.0 [109920.888113] {1}[Hardware Error]: slot: 0 [109920.892285] {1}[Hardware Error]: secondary_bus: 0x00 [109920.897489] {1}[Hardware Error]: vendor_id: 0x15b3, device_id: 0x1013 [109920.904172] {1}[Hardware Error]: class_code: 000002 [109920.909378] vfio-pci 0000:01:00.0: aer_status: 0x00040000, aer_mask: 0x00000000 [109920.916675] Malformed TLP [109920.916678] vfio-pci 0000:01:00.0: aer_layer=Transaction Layer, aer_agent=Receiver ID [109920.924573] vfio-pci 0000:01:00.0: aer_uncor_severity: 0x00062010 [109920.930736] vfio-pci 0000:01:00.0: TLP Header: 4a008040 00000100 01000000 00000000 [109920.938548] vfio-pci 0000:01:00.0: broadcast error_detected message [109921.965056] pcieport 0000:00:00.0: downstream link has been reset [109921.965062] vfio-pci 0000:01:00.0: broadcast mmio_enabled message [109921.965066] vfio-pci 0000:01:00.0: broadcast resume message [109921.965070] vfio-pci 0000:01:00.0: AER: Device recovery successful == Guest == EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [ 1.518252] kvm [1]: HYP mode not available [ 2.578929] mlx5_core 0000:05:00.0: mlx5_core_set_issi:778:(pid 152): Failed to query ISSI err(-1) status(0) synd(0) [ 2.582424] mlx5_core 0000:05:00.0: failed to set issi [ 2.616756] mlx5_core 0000:05:00.0: mlx5_load_one failed with error code -1 This is because, virtualization of physical functions are broken on systems with Maximum Payload Size bigger than 128. QDF2400 FW tries to maximize this setting. We have observed an MPS of 512 on QDF2400 systems. [Fix] Patches are in linux-next: 523184972b28 vfio/pci: Virtualize Maximum Payload Size cf0d53ba4947 vfio/pci: Virtualize Maximum Read Request Size [Testing] With the above patches applied the guest is able to boot when PCIE physical function is passthrough and we don't see the errors on the host system. == On the Guest == ubuntu@ubuntu-pcitest:~$ lspci 00:00.0 Host bridge: Red Hat, Inc. Device 0008 00:01.0 PCI bridge: Red Hat, Inc. Device 000c 00:01.1 PCI bridge: Red Hat, Inc. Device 000c 00:01.2 PCI bridge: Red Hat, Inc. Device 000c 00:01.3 PCI bridge: Red Hat, Inc. Device 000c 00:01.4 PCI bridge: Red Hat, Inc. Device 000c 00:01.5 PCI bridge: Red Hat, Inc. Device 000c 01:00.0 Ethernet controller: Red Hat, Inc Virtio network device (rev 01) 02:00.0 Communication controller: Red Hat, Inc Virtio console (rev 01) 03:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01) 04:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01) 05:00.0 Ethernet controller: Mellanox Technologies MT27700 Family [ConnectX-4] ubuntu@ubuntu-pcitest:~$ lsmod | grep mlx mlx5_core 471040 0 devlink 36864 1 mlx5_core ptp 28672 1 mlx5_core [Regression Potential] Two patches to drivers/vfio/pci were cleanly cherry picked from linux-next and applied to Artful/Zesty. Tested on ARM64 QDF2400 system and no regressions were found.
2017-11-21 00:00:20 Manoj Iyer linux (Ubuntu): assignee Manoj Iyer (manjo) Canonical Kernel Team (canonical-kernel-team)
2017-11-21 00:01:55 Manoj Iyer linux (Ubuntu): status Incomplete In Progress
2017-11-21 16:45:00 Joseph Salisbury bug task added linux (Ubuntu Artful)
2017-11-21 16:45:09 Joseph Salisbury bug task added linux (Ubuntu Zesty)
2017-11-21 16:45:19 Joseph Salisbury bug task added linux (Ubuntu Bionic)
2017-11-21 16:45:29 Joseph Salisbury linux (Ubuntu Artful): status New In Progress
2017-11-21 16:45:32 Joseph Salisbury linux (Ubuntu Zesty): status New In Progress
2017-11-21 16:45:36 Joseph Salisbury linux (Ubuntu Artful): importance Undecided Critical
2017-11-21 16:45:39 Joseph Salisbury linux (Ubuntu Zesty): importance Undecided Critical
2017-11-21 16:46:36 Joseph Salisbury linux (Ubuntu Bionic): assignee Canonical Kernel Team (canonical-kernel-team) Manoj Iyer (manjo)
2017-11-21 16:46:48 Joseph Salisbury linux (Ubuntu Artful): assignee Manoj Iyer (manjo)
2017-11-21 16:47:00 Joseph Salisbury linux (Ubuntu Zesty): assignee Manoj Iyer (manjo)
2017-11-22 15:20:33 Manoj Iyer bug added subscriber Sean Feole
2017-11-22 15:25:15 Manoj Iyer bug added subscriber Jeffrey Hugo
2018-01-05 16:26:52 Seth Forshee linux (Ubuntu Bionic): status In Progress Fix Committed
2018-02-04 01:17:20 Khaled El Mously linux (Ubuntu Artful): status In Progress Fix Committed
2018-02-14 09:38:22 Kleber Sacilotto de Souza tags artful qdf2400 artful qdf2400 verification-needed-artful
2018-02-14 09:39:56 Kleber Sacilotto de Souza linux (Ubuntu Zesty): status In Progress Won't Fix
2018-02-21 18:56:18 Launchpad Janitor linux (Ubuntu Artful): status Fix Committed Fix Released
2018-02-21 18:56:18 Launchpad Janitor cve linked 2017-15115
2018-02-21 18:56:18 Launchpad Janitor cve linked 2017-17712
2018-02-21 18:56:18 Launchpad Janitor cve linked 2017-5715
2018-02-21 18:56:18 Launchpad Janitor cve linked 2017-5753
2018-02-21 18:56:18 Launchpad Janitor cve linked 2017-5754
2018-02-21 18:56:18 Launchpad Janitor cve linked 2017-8824
2018-10-03 14:30:11 Joseph Salisbury linux (Ubuntu): status Fix Committed Fix Released
2018-10-03 14:30:14 Joseph Salisbury linux (Ubuntu Bionic): status Fix Committed Fix Released
2019-07-24 20:17:33 Brad Figg tags artful qdf2400 verification-needed-artful artful cscc qdf2400 verification-needed-artful