[Kernel-packages] [Bug 1950706] Re: VMs running under qemu+kvm can't use xsaves processor feature
This issue is still present today, on 5.4.0-153.170 Seems like the resolution is stalled. What can be done to get a fix out? -- 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/1950706 Title: VMs running under qemu+kvm can't use xsaves processor feature Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Invalid Bug description: Virtual machines running under qemu using KVM acceleration run with `-cpu host` can't use the xsaves feature of the processor. An example guest dmesg log is attached, see errors about "unchecked MSR access error". Using a `-cpu` model that doesn't advertise xsaves such as `EPYC` fixes the problem on the guest. The host cpu does support xsaves and Ubuntu doesn't seem to have any issues with it. The guest dmesg provided is running linux mainline 5.15, but the issue happens with every kernel version I've tried, including centos on 4.18.0. The host cpu is a Ryzen 5 3600 nested guests have trouble running in a guest with `-cpu host` or even `-cpu EPYC`. They tend to run, but freeze before they finish booting at random times. Not sure if it's related. Nested guests do seem to be able to run with `-cpu kvm64`. There are no dmesg errors when a nested guest freezes. The Ubuntu host version: Description:Ubuntu 20.04.3 LTS Release:20.04 # apt-cache policy qemu-system-x86 qemu-system-x86: Installed: 1:4.2-3ubuntu6.18 Candidate: 1:4.2-3ubuntu6.18 Version table: *** 1:4.2-3ubuntu6.18 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2-3ubuntu6.17 500 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:4.2-3ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu (not installed) ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Nov 12 00:19:10 2021 InstallationDate: Installed on 2021-10-20 (22 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) MachineType: System manufacturer System Product Name ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=screen-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=15509878-abfa-45b1-b8c2-c99db1ececf7 ro SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4002 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4002:bd06/15/2021:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950706/+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 1732990] Re: [Artful/Zesty] ACPI APEI error handling bug fixes
Validated the test kernel in the PPA by installing it onto a QDF2400 device running 16.04.3 Used JTAG to trigger multiple concurrent errors, and observed that all errors were parsed, instead of just the first one: root@ubuntu:/home/ubuntu# cat /sys/kernel/debug/tracing/trace # tracer: nop # # _-=> irqs-off # / _=> need-resched #| / _---=> hardirq/softirq #|| / _--=> preempt-depth #||| / delay # TASK-PID CPU# TIMESTAMP FUNCTION # | | | | | -0 [024] .ns. 462.341863: arm_event: affinity level: 2; MPIDR: ; MIDR: 510fc001; running state: 1; PSCI state: 0 97-overlayroot-2510 [024] ..s. 1010.705078: arm_event: affinity level: 2; MPIDR: ; MIDR: 510fc001; running state: 1; PSCI state: 0 97-overlayroot-2510 [024] ..s. 1010.705081: arm_event: affinity level: 2; MPIDR: ; MIDR: 510fc001; running state: 1; PSCI state: 0 97-overlayroot-2510 [024] ..s. 1010.705082: arm_event: affinity level: 2; MPIDR: ; MIDR: 510fc001; running state: 1; PSCI state: 0 97-overlayroot-2510 [024] ..s. 1010.705083: arm_event: affinity level: 2; MPIDR: ; MIDR: 510fc001; running state: 1; PSCI state: 0 The fixes to the PPA kernel address 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/1732990 Title: [Artful/Zesty] ACPI APEI error handling bug fixes Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Error records which have multiple errors in them will incorrectly report all errors after the first one. This results in garbage non-standard error trace events to be generated, and for AER and MC errors there will be no kernel action to help recover from these errors in the AER and EDAC drivers. [Fix] Patches in Linus tree fixes this issue: aaf2c2fb0f51 ACPI / APEI: clear error status before acknowledging the error c4335fdd3822 ACPI: APEI: fix the wrong iteration of generic error status block [Testing] Insert a e1000 pcie card into the system, run the following command that should generate PCIe correctable errors, you will see only the first error in each GHES report go to the AER driver rather than all errors from the GHES reports. $ sudo setpci -s 0002:00:00.0 0x70c.l=0x00808000;sudo setpci -s 0002:00:00.0 CAP_EXP+0x10.B=0x4b;sleep 1;sudo setpci -s 0002:00:00.0 CAP_EXP+0x10.B=0x48 Where "0002:00:00.0" being the root hub for the card. [Regression Potential] The two patches to ACPI APEI driver was cleanly cherry picked from linus's tree and applied to Artful and Zesty. The patches were tested on QDF2400 platform where it was found to issue and don't introduce any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732990/+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 1716033] Re: [SRU][Zesty] enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400
Validated. root@ubuntu:/home/ubuntu/andy/ibmtss930/utils# ./reg.sh -1 init tpm done Initialize Regression Test Keys Create a platform primary storage key INFO: Create a storage key under the primary key INFO: Create an unrestricted RSA signing key under the primary key INFO: Create an unrestricted ECC signing key under the primary key INFO: Create a restricted signing key under the primary key INFO: Create an RSA decryption key under the primary key INFO: Create a symmetric cipher key under the primary key INFO: Create a sha1 keyed hash key under the primary key INFO: Create a sha256 keyed hash key under the primary key INFO: Random Number Generator Stir Random INFO: Get Random INFO: Success - 1 Tests 0 Warnings root@ubuntu:/home/ubuntu/andy/ibmtss930/utils# -- 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/1716033 Title: [SRU][Zesty] enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400 Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400. Where, control area buffer address is greater than 32-bit. [Test] Currently only built for X64 & ACPI. [Fix] This is upstream: 19b7bf51fc3d tpm, tpm_crb: Handle 64-bit resource in crb_check_resource() 08eff49d63ca tpm/tpm_crb: Enable TPM CRB interface for ARM64 [Regression Potential] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716033/+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 1709123] Re: [SRU][Zesty] [QDF2400] pl011 E44 erratum patch needed for 2.0 firmware and 1.1 silicon
Validated ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- 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/1709123 Title: [SRU][Zesty] [QDF2400] pl011 E44 erratum patch needed for 2.0 firmware and 1.1 silicon Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Committed Bug description: [Impact] Another bug was found in the pl011/spcr code that implements the work-around for erratum E44. This erratum affects QDF2400 v1.1 silicon. The software bug is only exposed when using Firmware 2.0 or later (estimated release October 2017). To ensure compatibility with future firmware, the Ubuntu kernel should apply the aforementioned patch. Without this patch, customers using the 2.0 firmware and 1.1 silicon might not have a functional UART console, either sometimes or always. It is expected that this problem does not occur with 2.0 or later silicon. [Test Case] Upgrade firmware to v2.0 on a QDF2400 server with 1.1 silicon, and the kernel should fail to boot, with the patch applied, we should see no boot failure. [Fix] Following patch in linux-next fixes this issue: 37ef38f3f838 tty: pl011: fix initialization order of QDF2400 E44 [Regression Potential] This is a bug fix to tty driver and limited to qdf2400. Low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709123/+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 1716483] Re: [SRU][Zesty] Fix lscpu segfault on ARM64 with SMBIOS v2.0
Validated. Reported against FW 1.5. Validated against FW 2.0 Test: sudo apt-get install kexec-tools sudo kexec -l -d /boot/vmlinuz- --initrd=/boot/initrd.img- --reuse-cmd sudo kexec -e wait up to 10 minutes for the new kernel to boot System will crash at userspace boot without this fix. -- 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/1716483 Title: [SRU][Zesty] Fix lscpu segfault on ARM64 with SMBIOS v2.0 Status in linux package in Ubuntu: Incomplete Bug description: [Impact] On ARM64 systems with smbios v2.0, lscpu segfaults. This is caused by the fact that lspci issues a read() on /dev/mem at the offset where it expects to find the SMBIOS structure array. However, this region is classified as EFI_RUNTIME_SERVICE_DATA (as per the UEFI spec), and so it is omitted from the linear mapping. [Test] The issue was observed with kexec/kdump usecases when a FPDT ACPI table is presented to HLOS from the firmware. [Fix] Fixed upstream: 1151f838cb62 arm64: kernel: restrict /dev/mem read() calls to linear region [Regression Potential] The patch is confined to ARM64 arch, and applies only to systems with SMBIOS v2.0. Risk is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716483/+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 1688158] Re: [SRU][Zesty] Support SMMU passthrough using the default domain
Sorry for the delays. The nvme fio test didn't stress the system enough with this build, so I setup two systems with a direct wired, back to back, high performance network link and ran iperf. With the client in pass through, and the server in passthough/nonpassthrough, the data rate was slightly less than half in the nonpassthrough case. This is verified ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- 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/1688158 Title: [SRU][Zesty] Support SMMU passthrough using the default domain Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: [Impact] Have the SMMU come up in a passthrough configuration, and then allow subsequent translation for things such as VFIO. Rather than do this in each SMMU driver, it's much cleaner to allow the default domain to be configured to be something other than DMA. This patch series implements a command-line option to configure the default domain type. Currently, it supports "dma" and "identity" which is sufficient for the passthrough use-case. [Fix] The following patch series in linux-next adds this support to the kernel. 4a8d8a14c0d0 arm64: dma-mapping: Only swizzle DMA ops for IOMMU_DOMAIN_DMA fccb4e3b8ab0 iommu: Allow default domain type to be set on the kernel command line beb3c6a066bf iommu/arm-smmu-v3: Install bypass STEs for IOMMU_DOMAIN_IDENTITY domains 67560edcd8e5 iommu/arm-smmu-v3: Make arm_smmu_install_ste_for_dev return void 61bc671179f1 iommu/arm-smmu: Install bypass S2CRs for IOMMU_DOMAIN_IDENTITY domains 0834cc28fa56 iommu/arm-smmu: Restrict domain attributes to UNMANAGED domains To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688158/+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 1698448] RE: could you please help test kernel for bug #1698448
Kernel verified. Jeffrey Hugo Senior Engineer Qualcomm Datacenter Technologies, Inc. 1-303-247-5002 From: Manoj Iyer [mailto:manoj.i...@canonical.com] Sent: Monday, June 19, 2017 11:42 AM To: Jeff Hugo <jh...@qti.qualcomm.com> Cc: 1698...@bugs.launchpad.net; Timur Tabi <ti...@qti.qualcomm.com>; Tyler Baicar <tbai...@qti.qualcomm.com> Subject: could you please help test kernel for bug #1698448 Jeff, I have a kernel in PPA: https://launchpad.net/~centriq- team/+archive/ubuntu/lp1698448/ that has the patch for bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698448. PPA description has instructions for installing this kernel. Tyler suggests that we will need to inject and error prior to kernel boot to reproduce this issue ( I guess pulling a pcie card after fw initialization and before kernel boot might do it? ). I would need to have physical access to the system to do that kind of testing. The QDF2400 systems we have are in a data center which limits my ability to test this patch. Could someone from your team please test the patch using the test kernel in the PPA and post comments in the Ubuntu bug referenced above? FYI June 23rd is the deadline for submitting patches for the current SRU cycle. Thanks a ton! Manoj Iyer -- 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/1698448 Title: [SRU][Zesty] acpi: apei: check for pending errors when probing GHES entries Status in linux package in Ubuntu: Incomplete Bug description: [Impact] In addition to the RAS patches for which SRU were submitted under bug https://launchpad.net/bugs/1696570. We also require the following patch: f561618d9b80 acpi: apei: check for pending errors when probing GHES entries Without this patch pending RAS error at boot may not be handled correctly on the QDF2400 platforms, and could cause platform to reboot, or prevent future RAS issues from being reported. [Test] Run mce-tests suite. Inject an error before the kernel boots to reproduce the issue. [Fix] Fix is available in the linux ARM64 git repo maintained by Will Deacon: f561618d9b80 acpi: apei: check for pending errors when probing GHES entries. This patch needs to be applied on top of the RAS patches that were already submitted for SRU [Regression Potential] Small fix to handle pending errors right away. Low risk of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698448/+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 1688158] RE: [Bug #1688158] Please help test kernel for iommu.passthrough=0/1
group 0 (all jobs): READ: io=32384MB, aggrb=3236.8MB/s, minb=3236.8MB/s, maxb=3236.8MB/s, mint=10005msec, maxt=10005msec Disk stats (read/write): nvme0n1: ios=255788/0, merge=0/0, ticks=1246388/0, in_queue=1246788, util=99.05% Jeffrey Hugo Senior Engineer Qualcomm Datacenter Technologies, Inc. 1-303-247-5002 From: Manoj Iyer [mailto:manoj.i...@canonical.com] Sent: Thursday, May 11, 2017 9:23 PM To: Jeff Hugo <jh...@qti.qualcomm.com>; 1688...@bugs.launchpad.net Cc: Nate Watterson <nwatt...@qti.qualcomm.com>; Timur Tabi <ti...@qti.qualcomm.com> Subject: [Bug #1688158] Please help test kernel for iommu.passthrough=0/1 Jeff, I have back-ported patches to address "Support SMMU passthrough using the default domain". This adds a new kernel command line option iommu.passthrough=0/1 to Configure DMA to bypass the IOMMU for ARM64. http://bugs.launchpad.net/bugs/1688158 0 - Use IOMMU translation for DMA. 1 - Bypass the IOMMU for DMA. The test case recommended by Nate using 'fio' is: $ sudo apt update ; sudo apt install fio $ sudo fio --name=global --readonly --group_reporting --direct=1 --ioengine=libaio --rw=read --eta-newline=1s --size=1T --blocksize=512k --iodepth=32 --numjobs=1 --runtime=10s --name=nvme_0 --filename=/dev/nvme0n1 You can find the kernel and the instructions to install the kernel in the Centriq test PPA: https://launchpad.net/~centriq-team/+archive/ubuntu/test/ Nate and I have gone back and forth on testing these patches and finally came down to having this test run on an NVME device. Unfortunately I cant seem to find any nvme HW at this time, we would need to order these drive and could take time. Could you please test the kernel using the test case mentioned above and reply back to this email with test case out put for both cases. iommu.passthrough=0 and iommu.passthrough=1. We should see better performance (iops may be) with IOMMU bypassed for DMA (ie iommu.passthrough=1). The bug is cced on this email, so if you replay with a summary output in both cases it will be automatically recorded in the bug. Once I get your test results I will be able to make a case for SRUing these patches. Thanks a ton Manoj Iyer -- 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/1688158 Title: [SRU][Zesty] Support SMMU passthrough using the default domain Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Have the SMMU come up in a passthrough configuration, and then allow subsequent translation for things such as VFIO. Rather than do this in each SMMU driver, it's much cleaner to allow the default domain to be configured to be something other than DMA. This patch series implements a command-line option to configure the default domain type. Currently, it supports "dma" and "identity" which is sufficient for the passthrough use-case. [Fix] The following patch series in linux-next adds this support to the kernel. 4a8d8a14c0d0 arm64: dma-mapping: Only swizzle DMA ops for IOMMU_DOMAIN_DMA fccb4e3b8ab0 iommu: Allow default domain type to be set on the kernel command line beb3c6a066bf iommu/arm-smmu-v3: Install bypass STEs for IOMMU_DOMAIN_IDENTITY domains 67560edcd8e5 iommu/arm-smmu-v3: Make arm_smmu_install_ste_for_dev return void 61bc671179f1 iommu/arm-smmu: Install bypass S2CRs for IOMMU_DOMAIN_IDENTITY domains 0834cc28fa56 iommu/arm-smmu: Restrict domain attributes to UNMANAGED domains To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688158/+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 1688158] RE: [Bug #1688158] Please help test kernel for iommu.passthrough=0/1
Just FYI, it will likely take me a few days to get to this. Jeffrey Hugo Senior Engineer Qualcomm Datacenter Technologies, Inc. 1-303-247-5002 From: Manoj Iyer [mailto:manoj.i...@canonical.com] Sent: Thursday, May 11, 2017 9:23 PM To: Jeff Hugo <jh...@qti.qualcomm.com>; 1688...@bugs.launchpad.net Cc: Nate Watterson <nwatt...@qti.qualcomm.com>; Timur Tabi <ti...@qti.qualcomm.com> Subject: [Bug #1688158] Please help test kernel for iommu.passthrough=0/1 Jeff, I have back-ported patches to address "Support SMMU passthrough using the default domain". This adds a new kernel command line option iommu.passthrough=0/1 to Configure DMA to bypass the IOMMU for ARM64. http://bugs.launchpad.net/bugs/1688158 0 - Use IOMMU translation for DMA. 1 - Bypass the IOMMU for DMA. The test case recommended by Nate using 'fio' is: $ sudo apt update ; sudo apt install fio $ sudo fio --name=global --readonly --group_reporting --direct=1 --ioengine=libaio --rw=read --eta-newline=1s --size=1T --blocksize=512k --iodepth=32 --numjobs=1 --runtime=10s --name=nvme_0 --filename=/dev/nvme0n1 You can find the kernel and the instructions to install the kernel in the Centriq test PPA: https://launchpad.net/~centriq-team/+archive/ubuntu/test/ Nate and I have gone back and forth on testing these patches and finally came down to having this test run on an NVME device. Unfortunately I cant seem to find any nvme HW at this time, we would need to order these drive and could take time. Could you please test the kernel using the test case mentioned above and reply back to this email with test case out put for both cases. iommu.passthrough=0 and iommu.passthrough=1. We should see better performance (iops may be) with IOMMU bypassed for DMA (ie iommu.passthrough=1). The bug is cced on this email, so if you replay with a summary output in both cases it will be automatically recorded in the bug. Once I get your test results I will be able to make a case for SRUing these patches. Thanks a ton Manoj Iyer -- 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/1688158 Title: [SRU][Zesty] Support SMMU passthrough using the default domain Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Have the SMMU come up in a passthrough configuration, and then allow subsequent translation for things such as VFIO. Rather than do this in each SMMU driver, it's much cleaner to allow the default domain to be configured to be something other than DMA. This patch series implements a command-line option to configure the default domain type. Currently, it supports "dma" and "identity" which is sufficient for the passthrough use-case. [Fix] The following patch series in linux-next adds this support to the kernel. 4a8d8a14c0d0 arm64: dma-mapping: Only swizzle DMA ops for IOMMU_DOMAIN_DMA fccb4e3b8ab0 iommu: Allow default domain type to be set on the kernel command line beb3c6a066bf iommu/arm-smmu-v3: Install bypass STEs for IOMMU_DOMAIN_IDENTITY domains 67560edcd8e5 iommu/arm-smmu-v3: Make arm_smmu_install_ste_for_dev return void 61bc671179f1 iommu/arm-smmu: Install bypass S2CRs for IOMMU_DOMAIN_IDENTITY domains 0834cc28fa56 iommu/arm-smmu: Restrict domain attributes to UNMANAGED domains To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688158/+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 1689886] RE: [Bug #1689886] Please test this kernel and report results for SRU.
Manoj, how do you recommend utilizing the PPA? I downloaded the debian packages for linux-image and headers, used dpkg to install, and while it boots, many of the drivers are missing, so the test case cannot be executed. I attempted to go through DI, but pointing DI to the test PPA does not seem to install the correct kernel, and leaves the system in a non-bootable state. Jeffrey Hugo Senior Engineer Qualcomm Datacenter Technologies, Inc. 1-303-247-5002 From: Manoj Iyer [mailto:manoj.i...@canonical.com] Sent: Thursday, May 11, 2017 10:16 AM To: Joseph Chang <joech...@qti.qualcomm.com> Cc: Jeff Hugo <jh...@qti.qualcomm.com>; 1689...@bugs.launchpad.net Subject: RE: [Bug #1689886] Please test this kernel and report results for SRU. Joseph, Thanks for testing. Have you tested the kernel in the centriq test PPA with the patch applied? Or was it an upstream kernel? If you tested the kernel in centriq test PPA could you please post your test results here? Thanks Manoj On Thu, May 11, 2017 at 11:09 AM, Joseph Chang <joech...@qti.qualcomm.com<mailto:joech...@qti.qualcomm.com>> wrote: Hi, I already test the patch on REP and it really fix the kernel panic issue. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/ipmi/ipmi_ssif.c?id=6de65fcfdb51835789b245203d1bfc8d14cb1e06 Thank you, Joseph. From: Jeff Hugo Sent: Thursday, May 11, 2017 9:28 PM To: Manoj Iyer <manoj.i...@canonical.com<mailto:manoj.i...@canonical.com>>; 1689...@bugs.launchpad.net<mailto:1689...@bugs.launchpad.net> Cc: Joseph Chang <joech...@qti.qualcomm.com<mailto:joech...@qti.qualcomm.com>> Subject: RE: [Bug #1689886] Please test this kernel and report results for SRU. Yep, I’ll have it tested. Jeffrey Hugo Senior Engineer Qualcomm Datacenter Technologies, Inc. 1-303-247-5002 From: Manoj Iyer [mailto:manoj.i...@canonical.com] Sent: Wednesday, May 10, 2017 10:00 PM To: Jeff Hugo <jh...@qti.qualcomm.com<mailto:jh...@qti.qualcomm.com>>; 1689...@bugs.launchpad.net<mailto:1689...@bugs.launchpad.net> Cc: Joseph Chang <joech...@qti.qualcomm.com<mailto:joech...@qti.qualcomm.com>> Subject: [Bug #1689886] Please test this kernel and report results for SRU. Jeff, Could you please test the kernel in PPA https://launchpad.net/~centriq- team/+archive/ubuntu/test/ <%20https:/launchpad.net/~centriq- team/+archive/ubuntu/test/%20> that has Joeseph Chang's patch ipmi: Fix kernel panic at ipmi_ssif_thread() on a QDF2400 REP system and report your results? http://bugs.launchpad.net/bugs/1689886 <%20http:/bugs.launchpad.net/bugs/1689886%20> When you report the test results please include the output of the working ipmi command. Thanks Manoj Iyer -- 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/1689886 Title: [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin Status in linux package in Ubuntu: Incomplete Bug description: [Impact] $ sudo ipmitool fru print 0 Chassis Type : Rack Mount Chassis Chassis Part Number : Chassis Serial : Board Mfg Date : Wed Jan 4 14:18:00 2017 Board Mfg : WIWYNN Board Product : REP Board Board Serial : 12345 Board Part Number : Product Manufacturer : WIWYNN Product Name : REP Product Part Number : .. Product Version : EVT Product Serial : Product Asset Tag : ubuntu@ubuntu:~/FRU$ ubuntu@ubuntu:~/FRU$ sudo ipmitool fru write 0 fru.bin Fru Size : 1024 bytes Size to Write : 256 bytes [ 1815.412463] Unable to handle kernel NULL pointer dereference at virtual address 0025 [ 1815.419668] pgd = 219ca2168000 [ 1815.422986] [0025] *pgd=0003ee08d003, *pud=0003ee08e003, *pmd= [ 1815.431225] Internal error: Oops: 9604 [#1] SMP [ 1815.436086] Modules linked in: ipmi_devintf nls_utf8 nls_cp437 vfat fat aes_ce_blk ablk_helper cryptd aes_ce_cipher ghash_ce sha2_ce efi_pstore sha1_ce sg efivars ipmi_ssif ipmi_msghandler cppc_cpufreq i2c_qup i2c_core efivarfs autofs4 ext4 crc16 jbd2 mbcache sd_mod ahci_platform libahci_platform libahci xhci_plat_hcd libata xhci_hcd scsi_mod usbcore msm_emac sdhci_acpi sdhci usb_common pinctrl_qdf2xxx [ 1815.471677] CPU: 7 PID: 1950 Comm: kssif0042 Not tainted 4.7.0-2-generic #5~pdaw1.0+bandera.9-Ubuntu [ 1815.480789] Hardware name: Default string Default string/Default string, BIOS 5.12 12/12/2012 [ 1815.489296] task: edf1aa074380 ti: edf1a782 task.ti: edf1a782 [ 1815.496772] PC is at ipmi_ssif_thread+0x84/0x128 [ipmi_ssif] [ 1815.502407] LR is at ipmi_ssif_thread+0x6c/0x128 [ipmi_ssif] [ 1815.508046] pc : [] lr : [] pstate: 00400145 [ 1815.515424] sp : edf1a7823de0 [ 1815.518723] x29: edf1a7823de0 x28: [ 181
[Kernel-packages] [Bug 1689886] RE: [Bug #1689886] Please test this kernel and report results for SRU.
Tested on both SDP and REP. You want the following posted on the LP bug? root@null-8cfdf006971f:/home/ubuntu# uname -a Linux null-8cfdf006971f 4.10.0-20-generic #22~lp1689886+sru3-Ubuntu SMP Wed May 10 22:01:57 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux root@null-8cfdf006971f:/home/ubuntu# root@null-8cfdf006971f:/home/ubuntu# ipmitool fru read 0 fru0.bin Fru Size : 256 bytes Done root@null-8cfdf006971f:/home/ubuntu# root@null-8cfdf006971f:/home/ubuntu# ipmitool fru read 1 fru1.bin Fru Size : 256 bytes Done root@null-8cfdf006971f:/home/ubuntu# root@null-8cfdf006971f:/home/ubuntu# ipmitool fru print 0 Board Mfg Date: Sun Sep 12 12:55:00 2004 Board Mfg : QUALCOMM Board Product : ABW|SYS|CVR,2DPC|V3 Board Serial : N10MYKGC4 Board Part Number : 20-P7989-H1S root@null-8cfdf006971f:/home/ubuntu# uname -a Linux null-8cfdf006971f 4.10.0-20-generic #22~lp1689886+sru3-Ubuntu SMP Wed May 10 22:01:57 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux root@null-8cfdf006971f:/home/ubuntu# ipmitool fru read 0 fru0.bin Fru Size : 1024 bytes Done root@null-8cfdf006971f:/home/ubuntu# ipmitool fru read 1 fru1.bin Fru Size : 256 bytes Done root@null-8cfdf006971f:/home/ubuntu# ipmitool fru print 0 Chassis Type : Rack Mount Chassis Chassis Part Number : B81014010004 Chassis Serial: 716CJ0SA Board Mfg Date: Sat Apr 15 02:36:00 2017 Board Mfg : WIWYNN Board Product : QDF2400 Customer Reference Board Board Serial : B5501401D00571200032J0LA Board Part Number : B81.01410.0019 Product Manufacturer : WIWYNN Product Name : QDF2400 Reference Evaluation Platform Product Part Number : CV90-LA115-P900 Product Version : EVT Product Serial: B81014010004716CJ0SA Product Asset Tag : root@null-8cfdf006971f:/home/ubuntu# ipmitool fru print 1 Board Mfg Date: Tue Apr 25 05:46:00 2017 Board Mfg : WIWYNN Board Product : REP-1 PCIe riser P952 Board Serial : B5501404D003713EJ0LA Board Part Number : B81.01410.0013 Jeffrey Hugo Senior Engineer Qualcomm Datacenter Technologies, Inc. 1-303-247-5002 From: Jeff Hugo Sent: Thursday, May 11, 2017 11:42 AM To: 'Manoj Iyer' <manoj.i...@canonical.com> Cc: Joseph Chang <joech...@qti.qualcomm.com>; 1689...@bugs.launchpad.net Subject: RE: [Bug #1689886] Please test this kernel and report results for SRU. Hmm, that looks like it should work. I wonder why it didn’t seem to go well for me. I’ll give it another shot. Jeffrey Hugo Senior Engineer Qualcomm Datacenter Technologies, Inc. 1-303-247-5002 From: Manoj Iyer [mailto:manoj.i...@canonical.com] Sent: Thursday, May 11, 2017 11:21 AM To: Jeff Hugo <jh...@qti.qualcomm.com<mailto:jh...@qti.qualcomm.com>> Cc: Joseph Chang <joech...@qti.qualcomm.com<mailto:joech...@qti.qualcomm.com>>; 1689...@bugs.launchpad.net<mailto:1689...@bugs.launchpad.net> Subject: RE: [Bug #1689886] Please test this kernel and report results for SRU. On Thu, May 11, 2017 at 11:54 AM, Jeff Hugo <jh...@qti.qualcomm.com<mailto:jh...@qti.qualcomm.com>> wrote: Manoj, how do you recommend utilizing the PPA? I downloaded the debian packages for linux-image and headers, used dpkg to install, and while it boots, many of the drivers are missing, so the test case cannot be executed. The instructions to add the ppa and install the kernel etc are in the PPA: https://launchpad.net/~centriq-team/+archive/ubuntu/test/ in brief: sudo add-apt-repository ppa:centriq-team/test sudo apt-get update sudo apt-get install linux-image-4.10.0-20-generic linux-image-extra-4.10.0-20-generic If you have multiple versions of the kernel installed on your system and if you want to stop at the grub menu to select your kernel... you need to edit /etc/default/grub and comment out "GRUB_HIDDEN_TIMEOUT=0" before you install the kernel package (if you edited after you installed you can just run sudo update-grub2). This will drop you into the grub menu, where you can go into the "Advanced" tab and select the kernel you want to boot. I attempted to go through DI, but pointing DI to the test PPA does not seem to install the correct kernel, and leaves the system in a non-bootable state. Jeffrey Hugo Senior Engineer Qualcomm Datacenter Technologies, Inc. 1-303-247-5002 From: Manoj Iyer [mailto:manoj.i...@canonical.com] Sent: Thursday, May 11, 2017 10:16 AM To: Joseph Chang <joech...@qti.qualcomm.com<mailto:joech...@qti.qualcomm.com>> Cc: Jeff Hugo <jh...@qti.qualcomm.com<mailto:jh...@qti.qualcomm.com>>; 1689...@bugs.launchpad.net<mailto:1689...@bugs.launchpad.net> Subject: RE: [Bug #1689886] Please test this kernel and report results for SRU. Joseph, Thanks for testing. Have you tested the kernel in the centriq test PPA with the patch applied? Or was it an upstream kernel? If you tested the kernel in
[Kernel-packages] [Bug 1689886] RE: [Bug #1689886] Please test this kernel and report results for SRU.
Hmm, that looks like it should work. I wonder why it didn’t seem to go well for me. I’ll give it another shot. Jeffrey Hugo Senior Engineer Qualcomm Datacenter Technologies, Inc. 1-303-247-5002 From: Manoj Iyer [mailto:manoj.i...@canonical.com] Sent: Thursday, May 11, 2017 11:21 AM To: Jeff Hugo <jh...@qti.qualcomm.com> Cc: Joseph Chang <joech...@qti.qualcomm.com>; 1689...@bugs.launchpad.net Subject: RE: [Bug #1689886] Please test this kernel and report results for SRU. On Thu, May 11, 2017 at 11:54 AM, Jeff Hugo <jh...@qti.qualcomm.com<mailto:jh...@qti.qualcomm.com>> wrote: Manoj, how do you recommend utilizing the PPA? I downloaded the debian packages for linux-image and headers, used dpkg to install, and while it boots, many of the drivers are missing, so the test case cannot be executed. The instructions to add the ppa and install the kernel etc are in the PPA: https://launchpad.net/~centriq-team/+archive/ubuntu/test/ in brief: sudo add-apt-repository ppa:centriq-team/test sudo apt-get update sudo apt-get install linux-image-4.10.0-20-generic linux-image-extra-4.10.0-20-generic If you have multiple versions of the kernel installed on your system and if you want to stop at the grub menu to select your kernel... you need to edit /etc/default/grub and comment out "GRUB_HIDDEN_TIMEOUT=0" before you install the kernel package (if you edited after you installed you can just run sudo update-grub2). This will drop you into the grub menu, where you can go into the "Advanced" tab and select the kernel you want to boot. I attempted to go through DI, but pointing DI to the test PPA does not seem to install the correct kernel, and leaves the system in a non-bootable state. Jeffrey Hugo Senior Engineer Qualcomm Datacenter Technologies, Inc. 1-303-247-5002 From: Manoj Iyer [mailto:manoj.i...@canonical.com] Sent: Thursday, May 11, 2017 10:16 AM To: Joseph Chang <joech...@qti.qualcomm.com<mailto:joech...@qti.qualcomm.com>> Cc: Jeff Hugo <jh...@qti.qualcomm.com<mailto:jh...@qti.qualcomm.com>>; 1689...@bugs.launchpad.net<mailto:1689...@bugs.launchpad.net> Subject: RE: [Bug #1689886] Please test this kernel and report results for SRU. Joseph, Thanks for testing. Have you tested the kernel in the centriq test PPA with the patch applied? Or was it an upstream kernel? If you tested the kernel in centriq test PPA could you please post your test results here? Thanks Manoj On Thu, May 11, 2017 at 11:09 AM, Joseph Chang <joech...@qti.qualcomm.com<mailto:joech...@qti.qualcomm.com>> wrote: Hi, I already test the patch on REP and it really fix the kernel panic issue. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/ipmi/ipmi_ssif.c?id=6de65fcfdb51835789b245203d1bfc8d14cb1e06 Thank you, Joseph. From: Jeff Hugo Sent: Thursday, May 11, 2017 9:28 PM To: Manoj Iyer <manoj.i...@canonical.com<mailto:manoj.i...@canonical.com>>; 1689...@bugs.launchpad.net<mailto:1689...@bugs.launchpad.net> Cc: Joseph Chang <joech...@qti.qualcomm.com<mailto:joech...@qti.qualcomm.com>> Subject: RE: [Bug #1689886] Please test this kernel and report results for SRU. Yep, I’ll have it tested. Jeffrey Hugo Senior Engineer Qualcomm Datacenter Technologies, Inc. 1-303-247-5002 From: Manoj Iyer [mailto:manoj.i...@canonical.com] Sent: Wednesday, May 10, 2017 10:00 PM To: Jeff Hugo <jh...@qti.qualcomm.com<mailto:jh...@qti.qualcomm.com>>; 1689...@bugs.launchpad.net<mailto:1689...@bugs.launchpad.net> Cc: Joseph Chang <joech...@qti.qualcomm.com<mailto:joech...@qti.qualcomm.com>> Subject: [Bug #1689886] Please test this kernel and report results for SRU. Jeff, Could you please test the kernel in PPA https://launchpad.net/~centriq- team/+archive/ubuntu/test/ <%20https:/launchpad.net/~centriq- team/+archive/ubuntu/test/%20> that has Joeseph Chang's patch ipmi: Fix kernel panic at ipmi_ssif_thread() on a QDF2400 REP system and report your results? http://bugs.launchpad.net/bugs/1689886 <%20http:/bugs.launchpad.net/bugs/1689886%20> When you report the test results please include the output of the working ipmi command. Thanks Manoj Iyer -- 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/1689886 Title: QDF2400 kernel oops on ipmitool fru write 0 fru.bin Status in linux package in Ubuntu: Incomplete Bug description: [Impact] $ sudo ipmitool fru print 0 Chassis Type : Rack Mount Chassis Chassis Part Number : Chassis Serial : Board Mfg Date : Wed Jan 4 14:18:00 2017 Board Mfg : WIWYNN Board Product : REP Board Board Serial : 12345 Board Part Number : Product Manufacturer : WIWYNN Product Name : REP Product Part Number : .. Product Version : EVT Produ
[Kernel-packages] [Bug 1689886] RE: [Bug #1689886] Please test this kernel and report results for SRU.
Yep, I’ll have it tested. Jeffrey Hugo Senior Engineer Qualcomm Datacenter Technologies, Inc. 1-303-247-5002 From: Manoj Iyer [mailto:manoj.i...@canonical.com] Sent: Wednesday, May 10, 2017 10:00 PM To: Jeff Hugo <jh...@qti.qualcomm.com>; 1689...@bugs.launchpad.net Cc: Joseph Chang <joech...@qti.qualcomm.com> Subject: [Bug #1689886] Please test this kernel and report results for SRU. Jeff, Could you please test the kernel in PPA https://launchpad.net/~centriq- team/+archive/ubuntu/test/ <%20https:/launchpad.net/~centriq- team/+archive/ubuntu/test/%20> that has Joeseph Chang's patch ipmi: Fix kernel panic at ipmi_ssif_thread() on a QDF2400 REP system and report your results? http://bugs.launchpad.net/bugs/1689886 <%20http:/bugs.launchpad.net/bugs/1689886%20> When you report the test results please include the output of the working ipmi command. Thanks Manoj Iyer -- 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/1689886 Title: QDF2400 kernel oops on ipmitool fru write 0 fru.bin Status in linux package in Ubuntu: Incomplete Bug description: [Impact] $ sudo ipmitool fru print 0 Chassis Type : Rack Mount Chassis Chassis Part Number : Chassis Serial : Board Mfg Date : Wed Jan 4 14:18:00 2017 Board Mfg : WIWYNN Board Product : REP Board Board Serial : 12345 Board Part Number : Product Manufacturer : WIWYNN Product Name : REP Product Part Number : .. Product Version : EVT Product Serial : Product Asset Tag : ubuntu@ubuntu:~/FRU$ ubuntu@ubuntu:~/FRU$ sudo ipmitool fru write 0 fru.bin Fru Size : 1024 bytes Size to Write : 256 bytes [ 1815.412463] Unable to handle kernel NULL pointer dereference at virtual address 0025 [ 1815.419668] pgd = 219ca2168000 [ 1815.422986] [0025] *pgd=0003ee08d003, *pud=0003ee08e003, *pmd= [ 1815.431225] Internal error: Oops: 9604 [#1] SMP [ 1815.436086] Modules linked in: ipmi_devintf nls_utf8 nls_cp437 vfat fat aes_ce_blk ablk_helper cryptd aes_ce_cipher ghash_ce sha2_ce efi_pstore sha1_ce sg efivars ipmi_ssif ipmi_msghandler cppc_cpufreq i2c_qup i2c_core efivarfs autofs4 ext4 crc16 jbd2 mbcache sd_mod ahci_platform libahci_platform libahci xhci_plat_hcd libata xhci_hcd scsi_mod usbcore msm_emac sdhci_acpi sdhci usb_common pinctrl_qdf2xxx [ 1815.471677] CPU: 7 PID: 1950 Comm: kssif0042 Not tainted 4.7.0-2-generic #5~pdaw1.0+bandera.9-Ubuntu [ 1815.480789] Hardware name: Default string Default string/Default string, BIOS 5.12 12/12/2012 [ 1815.489296] task: edf1aa074380 ti: edf1a782 task.ti: edf1a782 [ 1815.496772] PC is at ipmi_ssif_thread+0x84/0x128 [ipmi_ssif] [ 1815.502407] LR is at ipmi_ssif_thread+0x6c/0x128 [ipmi_ssif] [ 1815.508046] pc : [] lr : [] pstate: 00400145 [ 1815.515424] sp : edf1a7823de0 [ 1815.518723] x29: edf1a7823de0 x28: [ 1815.524018] x27: x26: [ 1815.529313] x25: x24: [ 1815.534608] x23: edeeb9dbba08 x22: 219c9d0a3000 [ 1815.539903] x21: 219c9d0a2420 x20: edeeb9dbba00 [ 1815.545198] x19: edeeb9dbb800 x18: 0014 [ 1815.550494] x17: x16: [ 1815.555789] x15: x14: [ 1815.561084] x13: x12: 071c71c71c71c71c [ 1815.566379] x11: 00ba x10: 0960 [ 1815.571674] x9 : 0040 x8 : edf1ad28 [ 1815.576969] x7 : x6 : edf1aa9f9600 [ 1815.582264] x5 : edf1ad00 x4 : [ 1815.587560] x3 : 0026 x2 : 0025 [ 1815.592855] x1 : 0007 x0 : edf1aa2e4c00 [ 1815.598150] [ 1815.599626] Process kssif0042 (pid: 1950, stack limit = 0xedf1a7820020) [ 1815.606571] Stack: (0xedf1a7823de0 to 0xedf1a7824000) [ 1815.612301] 3de0: edf1a7823e20 219ca122cb1c edf1ab9d5800 219ca20cdfa8 [ 1815.620113] 3e00: 219ca1aa2ee8 edeeb9dbb800 219c9d09f590 edeeb9dbb800 [ 1815.627925] 3e20: 219ca11c4f10 219ca122ca30 edf1ab9d5800 [ 1815.635737] 3e40: [ 1815.643550] 3e60: 219ca12399a8 edeeb9dbb800 edf1 [ 1815.651363] 3e80: edf1a7823e88 edf1a7823e88 [ 1815.659175] 3ea0: edf1a7823ea8 edf1a7823ea8 cb88537fdc8ba500 [ 1815.666987] 3ec0: [ 1815.674800] 3ee0: [ 1815.682612] 3f00: 0
