[Kernel-packages] [Bug 1773024] Re: Errors at boot
Dell XPS 15 9570 and same error. $ uname -a Linux sinan-XPS-15-9570 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- 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/1773024 Title: Errors at boot Status in linux package in Ubuntu: Confirmed Bug description: LOGS DMESG: [0.048089] ACPI: Added _OSI(Module Device) [0.048090] ACPI: Added _OSI(Processor Device) [0.048091] ACPI: Added _OSI(3.0 _SCP Extensions) [0.048091] ACPI: Added _OSI(Processor Aggregator Device) [0.049587] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.049598] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.049607] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.049615] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.049676] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.049684] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.049692] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.049700] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.049760] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.049768] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.049776] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.049783] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.049843] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.049851] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.049859] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.049867] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.049925] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.049933] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.049941] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.049948] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.050008] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.050016] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.050024] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.050032] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.050091] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.050099] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.050107] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.050115] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.050173] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.050181] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.050190] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.050198] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.050258] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.050267] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.050274] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.050282] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.050342] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.050350] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.050357] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.050365] ACPI Exception: Could not find/resolve
[Kernel-packages] [Bug 1732804] Re: [Zesty/Artful] On ARM64 PCIE physical function passthrough guest fails to boot
I confirm that the test kernel fixes the issue. I was able to assign intel e1000e card to the guest machine and shutdown properly without observing any errors on the host OS. guest lspci [root@localhost ~]# 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 01:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06) 02:00.0 SCSI storage controller: Red Hat, Inc Virtio SCSI (rev 01) [root@localhost ~]# host lspci ubuntu@ubuntu:~$ uname -a Linux ubuntu 4.13.0-17-generic #20~lp1732804+build.1-Ubuntu SMP Fri Nov 17 00:45:36 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux ubuntu@ubuntu:~$ lspci 0001:00:00.0 PCI bridge: Qualcomm Datacenter Technologies QDF2400 PCI Express Root Port 0002:00:00.0 PCI bridge: Qualcomm Datacenter Technologies QDF2400 PCI Express Root Port 0002:01:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06) 0004:00:00.0 PCI bridge: Qualcomm Datacenter Technologies QDF2400 PCI Express Root Port 0005:00:00.0 PCI bridge: Qualcomm Datacenter Technologies QDF2400 PCI Express Root Port -- 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/1732804 Title: [Zesty/Artful] On ARM64 PCIE physical function passthrough guest fails to boot Status in linux package in Ubuntu: Incomplete Bug 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: :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: 02 [109920.909378] vfio-pci :01:00.0: aer_status: 0x0004, aer_mask: 0x [109920.916675] Malformed TLP [109920.916678] vfio-pci :01:00.0: aer_layer=Transaction Layer, aer_agent=Receiver ID [109920.924573] vfio-pci :01:00.0: aer_uncor_severity: 0x00062010 [109920.930736] vfio-pci :01:00.0: TLP Header: 4a008040 0100 0100 [109920.938548] vfio-pci :01:00.0: broadcast error_detected message [109921.965056] pcieport :00:00.0: downstream link has been reset [109921.965062] vfio-pci :01:00.0: broadcast mmio_enabled message [109921.965066] vfio-pci :01:00.0: broadcast resume message [109921.965070] vfio-pci :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 :05:00.0: mlx5_core_set_issi:778:(pid 152): Failed to query ISSI err(-1) status(0) synd(0) [2.582424] mlx5_core :05:00.0: failed to set issi [2.616756] mlx5_core :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 st