[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium -- 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/1990985 Title: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: IMPACT: Old, circa 2002 chipsets have a bug: they don't go idle when they are supposed to. So, a workaround was added to slow the CPU down and ensure that the CPU waits a bit for the chipset to actually go idle. This workaround is ancient and has been in place in some form since the original kernel ACPI implementation. But, this workaround is very painful on modern systems. The "inl()" can take thousands of cycles (see Link: for some more detailed numbers and some fun kernel archaeology). First and foremost, modern systems should not be using this code. Typical Intel systems have not used it in over a decade because it is horribly inferior to MWAIT-based idle. Despite this, people do seem to be tripping over this workaround on AMD system today. Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD systems from tripping over the workaround. Remotely modern Intel systems use intel_idle instead of this code and will, in practice, remain unaffected by the dummy wait. Reported-by: K Prateek Nayak Suggested-by: Rafael J. Wysocki Signed-off-by: Dave Hansen Reviewed-by: Mario Limonciello Tested-by: K Prateek Nayak Link: https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com FIX: This issue pertains to all Zen based processors starting with Naples(Zen1). All LTS releases will need this fix: https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9 TESTCASE: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+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 1990425] Re: Keyboard inoperative on Asus Vivobook S5402ZA
** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990425 Title: Keyboard inoperative on Asus Vivobook S5402ZA Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: [Impact] * The builtin keyboard on the Asus S5402ZA doesn't work with any currently released kernel. [Fix] * 6e5cbe7c4b41824e500acbb42411da692d1435f1 ACPI: resource: Add ASUS model S5402ZA to quirks * https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux- pm.git/commit/?h=bleeding- edge&id=6e5cbe7c4b41824e500acbb42411da692d1435f1 * e12dee3736731e24b1e7367f87d66ac0fcd73ce7 ACPI: resource: Skip IRQ override on Asus Vivobook K3402ZA/K3502ZA * https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux- pm.git/commit/?h=bleeding- edge&id=e12dee3736731e24b1e7367f87d66ac0fcd73ce7 * These are from the upstream linux-pm tree, accepted for Linux 6.1, https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/ [Test Plan] * Install Ubuntu on an Asus S5402ZA and verify that the internal keyboard doesn't work. * Install kernel with the above patches. * Boot into patched kernel and verify that the internal keyboard now works. [Where problems could occur] * These patches could cause the keyboard to not work if there are differences in hardware/firmware revisions. [Other Info] * The patch requires e12dee3736731e24b1e7367f87d66ac0fcd73ce7 for the addition of the quirk mechanism. * e12dee373673 includes quirks for the Asus K3402ZA/K3502ZA models. These were tested and accepted by upstream. See bug below. * The patchset has been tested on an Asus S5402ZA with a test kernel and found to work. * Upstream bug tracker: https://bugzilla.kernel.org/show_bug.cgi?id=216158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990425/+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 1991215] [NEW] test_verifier in ubuntu_bpf failed with 40 test cases on Jammy
Public bug reported: With the bpf build issue fixed (bug 1980517) on Jammy, the ubuntu_bpf test can now be tested. There are 40 failures discovered in test_verifier: #21/u BPF_ATOMIC_AND without fetch FAIL #21/p BPF_ATOMIC_AND without fetch FAIL #22/u BPF_ATOMIC_AND with fetch FAIL #22/p BPF_ATOMIC_AND with fetch FAIL #23/u BPF_ATOMIC_AND with fetch 32bit FAIL #23/p BPF_ATOMIC_AND with fetch 32bit FAIL #24/u BPF_ATOMIC_AND with fetch - r0 as source reg FAIL #24/p BPF_ATOMIC_AND with fetch - r0 as source reg FAIL #25/p BPF_ATOMIC bounds propagation, mem->reg FAIL #26/u atomic compare-and-exchange smoketest - 64bit FAIL #26/p atomic compare-and-exchange smoketest - 64bit FAIL #27/u atomic compare-and-exchange smoketest - 32bit FAIL #27/p atomic compare-and-exchange smoketest - 32bit FAIL #30/u BPF_W cmpxchg should zero top 32 bits FAIL #30/p BPF_W cmpxchg should zero top 32 bits FAIL #31/p Dest pointer in r0 - succeed, check 2 FAIL #33/p Dest pointer in r0 - succeed, check 4 FAIL #35/u BPF_ATOMIC_FETCH_ADD smoketest - 64bit FAIL #35/p BPF_ATOMIC_FETCH_ADD smoketest - 64bit FAIL #36/u BPF_ATOMIC_FETCH_ADD smoketest - 32bit FAIL #36/p BPF_ATOMIC_FETCH_ADD smoketest - 32bit FAIL #41/u BPF_ATOMIC OR without fetch FAIL #41/p BPF_ATOMIC OR without fetch FAIL #42/u BPF_ATOMIC OR with fetch FAIL #42/p BPF_ATOMIC OR with fetch FAIL #43/u BPF_ATOMIC OR with fetch 32bit FAIL #43/p BPF_ATOMIC OR with fetch 32bit FAIL #44/u BPF_W atomic_fetch_or should zero top 32 bits FAIL #44/p BPF_W atomic_fetch_or should zero top 32 bits FAIL #45/u atomic exchange smoketest - 64bit FAIL #45/p atomic exchange smoketest - 64bit FAIL #46/u atomic exchange smoketest - 32bit FAIL #46/p atomic exchange smoketest - 32bit FAIL #47/u BPF_ATOMIC XOR without fetch FAIL #47/p BPF_ATOMIC XOR without fetch FAIL #48/u BPF_ATOMIC XOR with fetch FAIL #48/p BPF_ATOMIC XOR with fetch FAIL #49/u BPF_ATOMIC XOR with fetch 32bit FAIL #49/p BPF_ATOMIC XOR with fetch 32bit FAIL #150/p calls: trigger reg2btf_ids[reg->type] for reg->type > __BPF_REG_TYPE_MAX FAIL ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Tags: 5.15 jammy sru-20220919 ubuntu-bpf ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) 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/1991215 Title: test_verifier in ubuntu_bpf failed with 40 test cases on Jammy Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: With the bpf build issue fixed (bug 1980517) on Jammy, the ubuntu_bpf test can now be tested. There are 40 failures discovered in test_verifier: #21/u BPF_ATOMIC_AND without fetch FAIL #21/p BPF_ATOMIC_AND without fetch FAIL #22/u BPF_ATOMIC_AND with fetch FAIL #22/p BPF_ATOMIC_AND with fetch FAIL #23/u BPF_ATOMIC_AND with fetch 32bit FAIL #23/p BPF_ATOMIC_AND with fetch 32bit FAIL #24/u BPF_ATOMIC_AND with fetch - r0 as source reg FAIL #24/p BPF_ATOMIC_AND with fetch - r0 as source reg FAIL #25/p BPF_ATOMIC bounds propagation, mem->reg FAIL #26/u atomic compare-and-exchange smoketest - 64bit FAIL #26/p atomic compare-and-exchange smoketest - 64bit FAIL #27/u atomic compare-and-exchange smoketest - 32bit FAIL #27/p atomic compare-and-exchange smoketest - 32bit FAIL #30/u BPF_W cmpxchg should zero top 32 bits FAIL #30/p BPF_W cmpxchg should zero top 32 bits FAIL #31/p Dest pointer in r0 - succeed, check 2 FAIL #33/p Dest pointer in r0 - succeed, check 4 FAIL #35/u BPF_ATOMIC_FETCH_ADD smoketest - 64bit FAIL #35/p BPF_ATOMIC_FETCH_ADD smoketest - 64bit FAIL #36/u BPF_ATOMIC_FETCH_ADD smoketest - 32bit FAIL #36/p BPF_ATOMIC_FETCH_ADD smoketest - 32bit FAIL #41/u BPF_ATOMIC OR without fetch FAIL #41/p BPF_ATOMIC OR without fetch FAIL #42/u BPF_ATOMIC OR with fetch FAIL #42/p BPF_ATOMIC OR with fetch FAIL #43/u BPF_ATOMIC OR with fetch 32bit FAIL #43/p BPF_ATOMIC OR with fetch 32bit FAIL #44/u BPF_W atomic_fetch_or should zero top 32 bits FAIL #44/p BPF_W atomic_fetch_or should zero top 32 bits FAIL #45/u atomic exchange smoketest - 64bit FAIL #45/p atomic exchange smoketest - 64bit FAIL #46/u atomic exchange smoketest - 32bit FAIL #46/p atomic exchange smoketest - 32bit FAIL #47/u BPF_ATOMIC XOR without fetch FAIL #47/p BPF_ATOMIC XOR without fetch FAIL #48/u BPF_ATOMIC XOR with fetch FAIL #48/p BPF_ATOMIC XOR with fetch FAIL #49/u BPF_ATOMIC XOR with fetch 32bit FAIL #49/p BPF_ATOMIC XOR with fetc
[Kernel-packages] [Bug 1991215] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1991215 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) Status: New => 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/1991215 Title: test_verifier in ubuntu_bpf failed with 40 test cases on Jammy Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: With the bpf build issue fixed (bug 1980517) on Jammy, the ubuntu_bpf test can now be tested. There are 40 failures discovered in test_verifier: #21/u BPF_ATOMIC_AND without fetch FAIL #21/p BPF_ATOMIC_AND without fetch FAIL #22/u BPF_ATOMIC_AND with fetch FAIL #22/p BPF_ATOMIC_AND with fetch FAIL #23/u BPF_ATOMIC_AND with fetch 32bit FAIL #23/p BPF_ATOMIC_AND with fetch 32bit FAIL #24/u BPF_ATOMIC_AND with fetch - r0 as source reg FAIL #24/p BPF_ATOMIC_AND with fetch - r0 as source reg FAIL #25/p BPF_ATOMIC bounds propagation, mem->reg FAIL #26/u atomic compare-and-exchange smoketest - 64bit FAIL #26/p atomic compare-and-exchange smoketest - 64bit FAIL #27/u atomic compare-and-exchange smoketest - 32bit FAIL #27/p atomic compare-and-exchange smoketest - 32bit FAIL #30/u BPF_W cmpxchg should zero top 32 bits FAIL #30/p BPF_W cmpxchg should zero top 32 bits FAIL #31/p Dest pointer in r0 - succeed, check 2 FAIL #33/p Dest pointer in r0 - succeed, check 4 FAIL #35/u BPF_ATOMIC_FETCH_ADD smoketest - 64bit FAIL #35/p BPF_ATOMIC_FETCH_ADD smoketest - 64bit FAIL #36/u BPF_ATOMIC_FETCH_ADD smoketest - 32bit FAIL #36/p BPF_ATOMIC_FETCH_ADD smoketest - 32bit FAIL #41/u BPF_ATOMIC OR without fetch FAIL #41/p BPF_ATOMIC OR without fetch FAIL #42/u BPF_ATOMIC OR with fetch FAIL #42/p BPF_ATOMIC OR with fetch FAIL #43/u BPF_ATOMIC OR with fetch 32bit FAIL #43/p BPF_ATOMIC OR with fetch 32bit FAIL #44/u BPF_W atomic_fetch_or should zero top 32 bits FAIL #44/p BPF_W atomic_fetch_or should zero top 32 bits FAIL #45/u atomic exchange smoketest - 64bit FAIL #45/p atomic exchange smoketest - 64bit FAIL #46/u atomic exchange smoketest - 32bit FAIL #46/p atomic exchange smoketest - 32bit FAIL #47/u BPF_ATOMIC XOR without fetch FAIL #47/p BPF_ATOMIC XOR without fetch FAIL #48/u BPF_ATOMIC XOR with fetch FAIL #48/p BPF_ATOMIC XOR with fetch FAIL #49/u BPF_ATOMIC XOR with fetch 32bit FAIL #49/p BPF_ATOMIC XOR with fetch 32bit FAIL #150/p calls: trigger reg2btf_ids[reg->type] for reg->type > __BPF_REG_TYPE_MAX FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991215/+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 1991113] Re: "source" PKA driver Kconfig in mellanox/Kconfig
** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1991113 Title: "source" PKA driver Kconfig in mellanox/Kconfig Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: PKA driver Kconfig needs to be "sourced" in mellanox/Kconfig. This makes MLXBF_PKA config option visible by the kernel configuration system and is needed to actually build PKA driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1991113/+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 1991112] Re: mlxbf_gige: compute MDIO period based on i1clk
** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid ** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1991112 Title: mlxbf_gige: compute MDIO period based on i1clk Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: The following upstream patch should be cherry picked to jammy kernel: 3a1a274e933f mlxbf_gige: compute MDIO period based on i1clk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1991112/+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 1989495] Re: mlxbf_gige: need to clear MDIO gateway lock after read
** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989495 Title: mlxbf_gige: need to clear MDIO gateway lock after read Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] The BlueField-2 GIGE logic accesses the MDIO device via reads/writes to a gateway (GW) register. The MDIO GW lock is set after read. Make sure to always clear to indicate that the GW register is not being used. If the lock is mistakenly interpreted as ACTIVE, then subsequent MDIO accesses will be blocked and PHY device will be inaccessible. [Fix] For each MDIO read and write transaction, the last step should be to clear the MDIO GW lock. [Test Case] Boot the BlueField-2 platform Bring up the "oob_net0" interface via DHCP or static IP Ping and file transfer over "oob_net0" should work properly Bounce the "oob_net0" interface a few times and repeat tests [Regression Potential] * Low risk for causing a regression, tested well in our lab. [Other] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989495/+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 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989172 Title: mlxbf-pmc: error when reading unprogrammed events Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+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 1991220] [NEW] "dpc: probe of 0000:00:10.0:pcie010 failed with error -524" errors are found in Ubuntu18.04.6
Public bug reported: 1. Power on SUT and install Ubuntu 18.04.6 (ubuntu-18.04.6-live-server-amd64.iso) 2. Boot into OS then run dmesg to check if there are unexpected errors or warnings. (=> failed, there are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 ) Expected behaviors: 2. There are no unexpected errors or warnings in dmesg. Current behaviors: 2. Tthere are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 Hardware information: Server MTM: SE350/360 V2 Hakuba (Icelake -D) OS installed: ubuntu-18.04.6-live-server-amd64 BMC Version: 0.90 (Build ID: USX313E) UEFI Version: 1.10 (Build ID: IYE101N) LXPM Version: 4.00 (Build ID: EAL103Y) CPU: Intel(R) Xeon(R) D-2775TE CPU @ 2.00GHz DIMM: ThinkSystem 32GB TruDDR4 3200 MHz (2Rx4 1.2V) RDIMM - SAM*1 IO Config: I/O Board: 25Gb/10Gb I/O Board RAID: NA NIC: uptech usb rj45 Storage: M.2 SSD: ThinkSystem M.2 7450P 960GB Read Intensive NVMe PCIe 4.0 x4 NHS SSD, 2280*2 PSU: Mean Well SE-600-48 600W/48V Debug information: 1. Double confirm with 20.04.5 and 22.04 and there are no this errors in those two Ubuntu OS. ** 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/1991220 Title: "dpc: probe of :00:10.0:pcie010 failed with error -524" errors are found in Ubuntu18.04.6 Status in linux package in Ubuntu: New Bug description: 1. Power on SUT and install Ubuntu 18.04.6 (ubuntu-18.04.6-live-server-amd64.iso) 2. Boot into OS then run dmesg to check if there are unexpected errors or warnings. (=> failed, there are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 ) Expected behaviors: 2. There are no unexpected errors or warnings in dmesg. Current behaviors: 2. Tthere are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 Hardware information: Server MTM: SE350/360 V2 Hakuba (Icelake -D) OS installed: ubuntu-18.04.6-live-server-amd64 BMC Version: 0.90 (Build ID: USX313E) UEFI Version: 1.10 (Build ID: IYE101N) LXPM Version: 4.00 (Build ID: E
[Kernel-packages] [Bug 1991220] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1991220 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => 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/1991220 Title: "dpc: probe of :00:10.0:pcie010 failed with error -524" errors are found in Ubuntu18.04.6 Status in linux package in Ubuntu: Incomplete Bug description: 1. Power on SUT and install Ubuntu 18.04.6 (ubuntu-18.04.6-live-server-amd64.iso) 2. Boot into OS then run dmesg to check if there are unexpected errors or warnings. (=> failed, there are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 ) Expected behaviors: 2. There are no unexpected errors or warnings in dmesg. Current behaviors: 2. Tthere are dpc errors in dmesg: [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524 [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524 [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524 [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524 [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524 [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524 [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524 [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524 [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524 [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 Hardware information: Server MTM: SE350/360 V2 Hakuba (Icelake -D) OS installed: ubuntu-18.04.6-live-server-amd64 BMC Version: 0.90 (Build ID: USX313E) UEFI Version: 1.10 (Build ID: IYE101N) LXPM Version: 4.00 (Build ID: EAL103Y) CPU: Intel(R) Xeon(R) D-2775TE CPU @ 2.00GHz DIMM: ThinkSystem 32GB TruDDR4 3200 MHz (2Rx4 1.2V) RDIMM - SAM*1 IO Config: I/O Board: 25Gb/10Gb I/O Board RAID: NA NIC: uptech usb rj45 Storage: M.2 SSD: ThinkSystem M.2 7450P 960GB Read Intensive NVMe PCIe 4.0 x4 NHS SSD, 2280*2 PSU: Mean Well SE-600-48 600W/48V Debug information: 1. Double confirm with 20.04.5 and 22.04 and there are no this errors in those two Ubuntu OS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991220/+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 1990945] Re: i915: Add GuC v70.1.1 for all platforms
** Changed in: linux-firmware (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1990945
Title:
i915: Add GuC v70.1.1 for all platforms
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Kinetic:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Intel Quake N i915 for kernel 5.19+ will need v70.1.1 firmware files.
[Fix]
Upstream commit ab0d8c137d42 ("i915: Add GuC v70.1.1 for all platforms").
[Test Case]
With v69 firmware, kernel prints:
kernel: i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin
is recommended, but only i915/adlp_guc_69.0.3.bin was found
New firmware would silence this line.
[Where problems could occur]
Firmware update, little knowledge to what was actually fixed, and the
actual revision being used is guarded by kernel.
[Other Info]
This update already exists in Kinetic, so only Jammy is nominated.
== original bug report ==
Quake N i915 for kernel 5.19+ will need the firmware files listed in the
following mail post:
https://www.spinics.net/lists/intel-gfx/msg295995.html
We are targeting Quake N to release with 6.0-oem kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990945/+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 1990212] Re: ADL-P-IOTG graphics cause Ubuntu 22.10 hang
@quanxian, we've found the patches that cause the system hang on J0 devices as following. a8951f369fde UBUNTU: SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD 9942df2fda84 UBUNTU: SAUCE: vmd: fixup bridge ASPM by driver name instead -- 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/1990212 Title: ADL-P-IOTG graphics cause Ubuntu 22.10 hang Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] ADL-P platform from IOTG will have hang issue. when blacklist i915, the system will back to well. but with official 5.19 kernel which support ADL-P (IOTG), we don't find this issue. Canonical please check what addition patches has been included your i915 driver that cause system hang. [HW/SW Information] Target Kernel: 5.19 Target Release: 22.10 Alder Lake -P from Intel IOTG [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1990212/+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 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
Anbox Cloud is affected by this too. We used shiftfs by default until our 1.14 release in May 2022. According to the metrics we have there are still a few users around with the 1.13 release which enables shiftfs on ZFS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+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 1991215] Re: test_verifier in ubuntu_bpf failed with 40 test cases on Jammy
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1991215 Title: test_verifier in ubuntu_bpf failed with 40 test cases on Jammy Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Bug description: With the bpf build issue fixed (bug 1980517) on Jammy, the ubuntu_bpf test can now be tested. There are 40 failures discovered in test_verifier: #21/u BPF_ATOMIC_AND without fetch FAIL #21/p BPF_ATOMIC_AND without fetch FAIL #22/u BPF_ATOMIC_AND with fetch FAIL #22/p BPF_ATOMIC_AND with fetch FAIL #23/u BPF_ATOMIC_AND with fetch 32bit FAIL #23/p BPF_ATOMIC_AND with fetch 32bit FAIL #24/u BPF_ATOMIC_AND with fetch - r0 as source reg FAIL #24/p BPF_ATOMIC_AND with fetch - r0 as source reg FAIL #25/p BPF_ATOMIC bounds propagation, mem->reg FAIL #26/u atomic compare-and-exchange smoketest - 64bit FAIL #26/p atomic compare-and-exchange smoketest - 64bit FAIL #27/u atomic compare-and-exchange smoketest - 32bit FAIL #27/p atomic compare-and-exchange smoketest - 32bit FAIL #30/u BPF_W cmpxchg should zero top 32 bits FAIL #30/p BPF_W cmpxchg should zero top 32 bits FAIL #31/p Dest pointer in r0 - succeed, check 2 FAIL #33/p Dest pointer in r0 - succeed, check 4 FAIL #35/u BPF_ATOMIC_FETCH_ADD smoketest - 64bit FAIL #35/p BPF_ATOMIC_FETCH_ADD smoketest - 64bit FAIL #36/u BPF_ATOMIC_FETCH_ADD smoketest - 32bit FAIL #36/p BPF_ATOMIC_FETCH_ADD smoketest - 32bit FAIL #41/u BPF_ATOMIC OR without fetch FAIL #41/p BPF_ATOMIC OR without fetch FAIL #42/u BPF_ATOMIC OR with fetch FAIL #42/p BPF_ATOMIC OR with fetch FAIL #43/u BPF_ATOMIC OR with fetch 32bit FAIL #43/p BPF_ATOMIC OR with fetch 32bit FAIL #44/u BPF_W atomic_fetch_or should zero top 32 bits FAIL #44/p BPF_W atomic_fetch_or should zero top 32 bits FAIL #45/u atomic exchange smoketest - 64bit FAIL #45/p atomic exchange smoketest - 64bit FAIL #46/u atomic exchange smoketest - 32bit FAIL #46/p atomic exchange smoketest - 32bit FAIL #47/u BPF_ATOMIC XOR without fetch FAIL #47/p BPF_ATOMIC XOR without fetch FAIL #48/u BPF_ATOMIC XOR with fetch FAIL #48/p BPF_ATOMIC XOR with fetch FAIL #49/u BPF_ATOMIC XOR with fetch 32bit FAIL #49/p BPF_ATOMIC XOR with fetch 32bit FAIL #150/p calls: trigger reg2btf_ids[reg->type] for reg->type > __BPF_REG_TYPE_MAX FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991215/+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 1942160] Re: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
** Changed in: linux-oem-5.17 (Ubuntu) Status: Fix Committed => Invalid -- 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/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: Fix Released Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.13 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.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux-oem-5.17 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] VMD PCI-E bridges on ADL-M/P/S use new device IDs and therefore not covered by previous LTR reset fix in bug 1896598. [Fix] Additional entires to vmd_bridge_tbl in drivers/pci/quirks.c is requierd: * ADL-M: [8086:464d] * ADL-P: [8086:51b0] * ADL-S: [8086:7ab4] [Test Case] $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' ... 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ [Where problems could occur] This will reset zeroed PCI_LTR_MAX_SNOOP_LAT and PCI_LTR_MAX_NOSNOOP_LAT values to a fixed 3145728ns that is used on Windows. Devices might want to set itself to a smaller value, but while this is not yet correctly supported by VMD controller driver, so the device power consumption might be little worse than ideal. [Other Info] VMD ASPM was first supported for Tiger Lake cpus, so all kernel versions newer than 5.6 should have already the supporting function. This patch targets Alder Lake cpus that are supported since 5.10-oem and on. == original bug report == * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384, https://bugs.launchpad.net/bugs/1896598. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE
[Kernel-packages] [Bug 1990212] Re: ADL-P-IOTG graphics cause Ubuntu 22.10 hang
Canonical doesn't reproduce this issue because their hardware should be new. but we need point out the commits above maybe bring some hang issue and flicker issue for graphics. I will close this bug since we root cause this. Thanks All ** Changed in: intel Status: New => Fix Released -- 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/1990212 Title: ADL-P-IOTG graphics cause Ubuntu 22.10 hang Status in intel: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] ADL-P platform from IOTG will have hang issue. when blacklist i915, the system will back to well. but with official 5.19 kernel which support ADL-P (IOTG), we don't find this issue. Canonical please check what addition patches has been included your i915 driver that cause system hang. [HW/SW Information] Target Kernel: 5.19 Target Release: 22.10 Alder Lake -P from Intel IOTG [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1990212/+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 1990212] Re: ADL-P-IOTG graphics cause Ubuntu 22.10 hang
fix released as upgrading hardware SOC and BIOS to latest. Old ADL-P will have this issue. revert the commits above will also fix 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/1990212 Title: ADL-P-IOTG graphics cause Ubuntu 22.10 hang Status in intel: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] ADL-P platform from IOTG will have hang issue. when blacklist i915, the system will back to well. but with official 5.19 kernel which support ADL-P (IOTG), we don't find this issue. Canonical please check what addition patches has been included your i915 driver that cause system hang. [HW/SW Information] Target Kernel: 5.19 Target Release: 22.10 Alder Lake -P from Intel IOTG [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1990212/+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 1990870] Re: Cannot update sutton.newell OEM packages since upgrade to LTS 22.04
Here is what was upgraded : Install: systemd-hwe-hwdb:amd64 (249.11.1, automatic) Upgrade: udev:amd64 (249.11-0ubuntu3.4, 249.11-0ubuntu3.6), systemd-timesyncd:amd64 (249.11-0ubuntu3.4, 249.11-0ubuntu3.6), libpam-systemd:amd64 (249.11-0ubuntu3.4, 249.11-0ubuntu3.6), oem-sutton.newell-meta:amd64 (4.0newell5, 22.04sutton1), libsystemd0:amd64 (249.11-0ubuntu3.4, 249.11-0ubuntu3.6), libnss-systemd:amd64 (249.11-0ubuntu3.4, 249.11-0ubuntu3.6), libudev-dev:amd64 (249.11-0ubuntu3.4, 249.11-0ubuntu3.6), systemd:amd64 (249.11-0ubuntu3.4, 249.11-0ubuntu3.6), libudev1:amd64 (249.11-0ubuntu3.4, 249.11-0ubuntu3.6), systemd-sysv:amd64(249.11-0ubuntu3.4, 249.11-0ubuntu3.6) -- 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/1990870 Title: Cannot update sutton.newell OEM packages since upgrade to LTS 22.04 Status in OEM Priority Project: Fix Committed Status in OEM Processes: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: My laptop is a Lenovo T14s, that I put under Kubuntu 20.04 LTS. Since I've upgraded my distribution to Kubuntu 22.04 , I've lost graphic acceleration, and any “apt update” will trigger this message : ««« W: http://deb.anydesk.com/dists/all/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. W: Le fichier configuré « sutton.newell/binary-amd64/Packages » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/binary-i386/Packages » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/i18n/Translation-fr » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/i18n/Translation-en » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/i18n/Translation-fr_FR » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/dep11/Components-amd64.yml » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/dep11/icons-48x48.tar » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/dep11/icons-64x64.tar » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/dep11/icons-64...@2.tar » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/dep11/icons-128x128.tar » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/cnf/Commands-amd64 » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) »»» (Roughly translated : « The file « sutton.newell/binary-amd64/Packages » won't be used because the depot « http://lenovo.archive.canonical.com jammy InRelease » doesn't have the source « sutton.newell » (mistake in sources.list ?) ») --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xavier 1608 F pulseaudio /dev/snd/controlC1: xavier 1608 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-20 (280 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) MachineType: LENOVO 20WMCTO1WW Package: linux (not inst
[Kernel-packages] [Bug 1990870] Re: Cannot update sutton.newell OEM packages since upgrade to LTS 22.04
@xaviermd, Thanks your feedback, the oem-sutton.newell-meta is expected, it's used to help generate the OEM repository. -- 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/1990870 Title: Cannot update sutton.newell OEM packages since upgrade to LTS 22.04 Status in OEM Priority Project: Fix Committed Status in OEM Processes: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: My laptop is a Lenovo T14s, that I put under Kubuntu 20.04 LTS. Since I've upgraded my distribution to Kubuntu 22.04 , I've lost graphic acceleration, and any “apt update” will trigger this message : ««« W: http://deb.anydesk.com/dists/all/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. W: Le fichier configuré « sutton.newell/binary-amd64/Packages » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/binary-i386/Packages » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/i18n/Translation-fr » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/i18n/Translation-en » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/i18n/Translation-fr_FR » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/dep11/Components-amd64.yml » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/dep11/icons-48x48.tar » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/dep11/icons-64x64.tar » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/dep11/icons-64...@2.tar » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/dep11/icons-128x128.tar » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) W: Le fichier configuré « sutton.newell/cnf/Commands-amd64 » ne sera pas pris en compte car le dépôt « http://lenovo.archive.canonical.com jammy InRelease » ne dispose pas de la source « sutton.newell » (erreur de saisie dans sources.list ?) »»» (Roughly translated : « The file « sutton.newell/binary-amd64/Packages » won't be used because the depot « http://lenovo.archive.canonical.com jammy InRelease » doesn't have the source « sutton.newell » (mistake in sources.list ?) ») --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xavier 1608 F pulseaudio /dev/snd/controlC1: xavier 1608 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-20 (280 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) MachineType: LENOVO 20WMCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1049-oem root=UUID=f92a4fe4-5538-4055-9493-57eb678e2898 ro intel_iommu=on vfio-pci.ids=8086:4905 ProcVersionSignature: Ubuntu 5.14.0-1049.56-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1049-oem N/A linux-backports-modules-5.14.0-1049-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.14.0-1049-oem x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-24 (33 days ago)
[Kernel-packages] [Bug 1976473] Re: [Dell G15 5515] Unable to change screen brightness in ubuntu desktop
yup I am also facing a bug, sometimes it does not work. Found a solution for it just run sudo update-grub and restart the system. -- 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/1976473 Title: [Dell G15 5515] Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Confirmed Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 1991254] [NEW] No HDMI sound output from alsa in server (no KMS)
Public bug reported: During ISO testing of the beta Ubuntu Server 22.10 for Raspberry Pi armhf image, on a Raspberry Pi 4B, I noted that the HDMI "sound card" no longer appears in /proc/asound/cards; only the Headphones output (from the AUX socket on the board) appears. I checked with the current linux-raspi in the release pocket (5.19.0-1001-raspi), and the new one in proposed (5.19.0-1002-raspi), and both exhibit the same issue. On Kinetic: $ cat /proc/asound/cards 0 [Headphones ]: bcm2835_headpho - bcm2835 Headphones bcm2835 Headphones On Jammy: $ cat /proc/asound/cards 0 [b1 ]: bcm2835_hdmi - bcm2835 HDMI 1 bcm2835 HDMI 1 1 [Headphones ]: bcm2835_headpho - bcm2835 Headphones bcm2835 Headphones ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Summary changed: - No HDMI sound output from alsa + No HDMI sound output from alsa in server (no KMS) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1991254 Title: No HDMI sound output from alsa in server (no KMS) Status in linux-raspi package in Ubuntu: New Bug description: During ISO testing of the beta Ubuntu Server 22.10 for Raspberry Pi armhf image, on a Raspberry Pi 4B, I noted that the HDMI "sound card" no longer appears in /proc/asound/cards; only the Headphones output (from the AUX socket on the board) appears. I checked with the current linux-raspi in the release pocket (5.19.0-1001-raspi), and the new one in proposed (5.19.0-1002-raspi), and both exhibit the same issue. On Kinetic: $ cat /proc/asound/cards 0 [Headphones ]: bcm2835_headpho - bcm2835 Headphones bcm2835 Headphones On Jammy: $ cat /proc/asound/cards 0 [b1 ]: bcm2835_hdmi - bcm2835 HDMI 1 bcm2835 HDMI 1 1 [Headphones ]: bcm2835_headpho - bcm2835 Headphones bcm2835 Headphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1991254/+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 1991286] [NEW] package linux-tools-5.15.0-48 (not installed) failed to install/upgrade: tentative de remplacement de « /usr/lib/libcpupower.so.5.15.0-48 », qui appartient aussi
Public bug reported: Bonjour, Des paquets synaptic ne s'installent pas. Avec Synaptic, il est difficile de savoir quoi installer alors qu'avec Ubuntu Software, les icones informaient tout de suite de quoi il s'agissait. Ubuntu software ne fonctionne pas, comment faire ? Avec mes remerciements Marie-Hélène ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-5.15.0-48 (not installed) ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marie 1863 F pulseaudio /dev/snd/controlC0: marie 1863 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Sep 29 16:12:08 2022 ErrorMessage: tentative de remplacement de « /usr/lib/libcpupower.so.5.15.0-48 », qui appartient aussi au paquet linux-lowlatency-tools-5.15.0-48 5.15.0-48.54 InstallationDate: Installed on 2022-08-21 (39 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. X540YA ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b3fc9ef4-e867-41a1-97ad-05154adeece5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux Title: package linux-tools-5.15.0-48 (not installed) failed to install/upgrade: tentative de remplacement de « /usr/lib/libcpupower.so.5.15.0-48 », qui appartient aussi au paquet linux-lowlatency-tools-5.15.0-48 5.15.0-48.54 UpgradeStatus: Upgraded to jammy on 2022-08-21 (38 days ago) dmi.bios.date: 12/31/2019 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X540YA.323 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X540YA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX540YA.323:bd12/31/2019:br4.6:svnASUSTeKCOMPUTERINC.:pnX540YA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540YA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X540YA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1991286 Title: package linux-tools-5.15.0-48 (not installed) failed to install/upgrade: tentative de remplacement de « /usr/lib/libcpupower.so.5.15.0-48 », qui appartient aussi au paquet linux-lowlatency-tools-5.15.0-48 5.15.0-48.54 Status in linux package in Ubuntu: New Bug description: Bonjour, Des paquets synaptic ne s'installent pas. Avec Synaptic, il est difficile de savoir quoi installer alors qu'avec Ubuntu Software, les icones informaient tout de suite de quoi il s'agissait. Ubuntu software ne fonctionne pas, comment faire ? Avec mes remerciements Marie-Hélène ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-5.15.0-48 (not installed) ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marie 1863 F pulseaudio /dev/snd/controlC0: marie 1863 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Sep 29 16:12:08 2022 ErrorMessage: tentative de remplacement de « /usr/lib/libcpupower.so.5.15.0-48 », qui appartient aussi au paquet linux-lowlatency-tools-5.15.0-48 5.15.0-48.54 InstallationDate: Installed on 2022-08-21 (39 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. X540YA ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b3fc9ef4-e867-41a1-97ad-05154adeece5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux Title: package linux-tools-5.15.0-48 (not installed) failed to install/upgrade: t
[Kernel-packages] [Bug 1991285] [NEW] systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144
Public bug reported: This is a scripted bug report about ADT failures while running systemd tests for linux/5.4.0-128.144 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1991285 Title: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144 Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.4.0-128.144 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144
To me it looks like the boot-and-services sub-tests got a lot less reliable on armhf in Focal. The previous systemd version had a higher chance of passing those. There always was root-unittests which required multiple attempts. But now from about 10 attempts there was one which had root-unittests only failing and the rest was roughly split between boot-and-services or both failing. -- 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/1991285 Title: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144 Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.4.0-128.144 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1986798] Re: Remove unused variable from i915 psr
This bug is awaiting verification that the linux-
gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
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/1986798
Title:
Remove unused variable from i915 psr
Status in linux package in Ubuntu:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
Compiler warns unused variable after commit 0c1d6921b07c ("UBUNTU:
SAUCE: drm/i915/display/psr: Reinstate fix for TGL + AUO panel flicker")
[Fix]
The variable is unused, remove it.
[Test]
Compiler no longer warns about it.
[Where problems could occur]
Nothing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986798/+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 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux-
gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-hwe-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+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 1983498] Re: Jammy: Add OVS Internal Port HW Offload to mlx5 driver
This bug is awaiting verification that the linux- gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1983498 Title: Jammy: Add OVS Internal Port HW Offload to mlx5 driver Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] A request has been made, originating from https://bugs.launchpad.net/bugs/1980730, to add support for OVS internal port offload for the mlx5 driver. This feature takes care of certain traffic workloads that are not currently being offloaded to the hardware. [Test Case] Tested by the requester. [Where things could go wrong] These changes could potentially introduce regressions in behavior of the mlx5 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983498/+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 1983297] Re: Additional fix for TGL + AUO panel flickering
This bug is awaiting verification that the linux- gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1983297 Title: Additional fix for TGL + AUO panel flickering Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel" alone used to fix the issue on the AUO panel. But the panel starts to flicker like crazy on top of the new stable commits. [Fix] Backport full fix for PSR2 selective fetch, but only enable it on TGL + specific AUO panel. The last three patches which enable PSR2 on ADL-P are dropped. [Test] Originally the backport regressed ADL + BOE panel, so this time we put extra effort to ensure those system are unaffected, while TGL + AUO panel is still fixed. [Where problems could occur] Most code changes only have functional impact when PSR2 selective fetch is enabled. Some of changes are under more general call path for hardware cursor rendering. Notes are added to describe the functional impact for each patch, so if regression really occurrs it's easier to spot the offending commit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983297/+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 1981390] Re: Mass Storage Gadget driver truncates device >2TB
This bug is awaiting verification that the linux-
gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
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/1981390
Title:
Mass Storage Gadget driver truncates device >2TB
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
I tried to use f_mass_storage to expose a 16TB hard drive attached to
Raspberry Pi to another computer.
On the remote computer the recognised drive has incorrect capacity and the
data is truncated.
After some debugging I noted the problem is caused by a bug in the
read capacity function of f_mass_storage in kernel version prior to
5.15, which had already been fixed upstream in mainline kernel since
v5.16
https://lore.kernel.org/all/20210914052728.23369-1-nikita.yo...@cogentembedded.com/
I tried the kernel from https://github.com/raspberrypi/linux version
rpi-5.16.y and confirmed that the problem is fixed at v5.16.
I wonder if the fix can be backported to the Ubuntu kernel.
Thank you very much!
Current kernel package version: linux-raspi (5.15.0-1011.13) jammy
Hardware: Raspberry Pi 4B
[Fix]
Backport commit bedbac5f66bf ("usb: gadget: storage: add support for
media larger than 2T")
[Test case]
See above.
[Where problems could occur]
Modifications are limited to the USB gadget mass storage driver, so
problems should only be seen on a client that uses this driver to
expose a USB drive to an attached USB host.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981390/+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 1980925] Re: [SRU] bcache deadlock during read IO in writeback mode
This bug is awaiting verification that the linux- gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1980925 Title: [SRU] bcache deadlock during read IO in writeback mode Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: [Impact] When Random Read I/O is started with a test like - fio --name=read_iops --directory=/home/ubuntu/bcache_mount/ --size=16G --ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=128 --rw=randread --randrepeat=0 or random read-writes with a test like, fio --filename=/home/ubuntu/bcache_mount/cachedfile --size=15GB --direct=1 --rw=randrw --bs=4k --ioengine=libaio --iodepth=128 --name=iops-test-job --randrepeat=0 traces are seen in the kernel log, [ 4473.699902] INFO: task bcache_writebac:1835 blocked for more than 120 seconds. [ 4474.050921] Not tainted 5.15.50-051550-generic #202206251445 [ 4474.350883] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4474.731391] task:bcache_writebac state:D stack:0 pid: 1835 ppid: 2 flags:0x4000 [ 4474.731408] Call Trace: [ 4474.731411] [ 4474.731413] __schedule+0x23d/0x5a0 [ 4474.731433] schedule+0x4e/0xb0 [ 4474.731436] rwsem_down_write_slowpath+0x220/0x3d0 [ 4474.731441] down_write+0x43/0x50 [ 4474.731446] bch_writeback_thread+0x78/0x320 [bcache] [ 4474.731471] ? read_dirty_submit+0x70/0x70 [bcache] [ 4474.731487] kthread+0x12a/0x150 [ 4474.731491] ? set_kthread_struct+0x50/0x50 [ 4474.731494] ret_from_fork+0x22/0x30 [ 4474.731499] The bug exists till kernel 5.15.50-051550-generic The reproducer is pasted below: # uname -a Linux bronzor 5.15.50-051550-generic #202206251445 SMP Sat Jun 25 14:51:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sdd 8:48 0 279.4G 0 disk └─sdd18:49 060G 0 part └─bcache0 252:0060G 0 disk /home/ubuntu/bcache_mount nvme0n1 259:00 372.6G 0 disk └─nvme0n1p1 259:2015G 0 part └─bcache0 252:0060G 0 disk /home/ubuntu/bcache_mount fio --name=read_iops --directory=/home/ubuntu/bcache_mount --size=12G --ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=128 --rw=randread --group_reporting=1 read_iops: (g=0): rw=randread, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128 fio-3.28 Starting 1 process read_iops: Laying out IO file (1 file / 12288MiB) The test does not progress beyond a few minutes, and this trace is then seen in the kernel log, [ 4473.699902] INFO: task bcache_writebac:1835 blocked for more than 120 seconds. [ 4474.050921] Not tainted 5.15.50-051550-generic #202206251445 [ 4474.350883] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4474.731391] task:bcache_writebac state:D stack:0 pid: 1835 ppid: 2 flags:0x4000 [ 4474.731408] Call Trace: [ 4474.731411] [ 4474.731413] __schedule+0x23d/0x5a0 [ 4474.731433] schedule+0x4e/0xb0 [ 4474.731436] rwsem_down_write_slowpath+0x220/0x3d0 [ 4474.731441] down_write+0x43/0x50 [ 4474.731446] bch_writeback_thread+0x78/0x320 [bcache] [ 4474.731471] ? read_dirty_submit+0x70/0x70 [bcache] [ 4474.731487] kthread+0x12a/0x150 [ 4474.731491] ? set_kthread_struct+0x50/0x50 [ 4474.731494] ret_from_fork+0x22/0x30 [ 4474.731499] [Fix] These 3 fixes are needed for the SRU. dea3560e5f31965165bcf34ecf0b47af28bfd155, 6445ec3df23f24677064a327dce437ef3e02dc6, dc60301fb408e06e0b718c0980cdd31d2b238bee I have built these fixes into kernel 5.15.0-39-generic (jammy) and tested to verify the problem is fixed. [Regression Potential] Regression potential should be minimal. I have not seen any potential drawbacks or harmful effects of this fix in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : ht
[Kernel-packages] [Bug 1978820] Re: Jammy Charmed OpenStack deployment fails over connectivity issues when using converged OVS bridge for control and data planes
This bug is awaiting verification that the linux- gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1978820 Title: Jammy Charmed OpenStack deployment fails over connectivity issues when using converged OVS bridge for control and data planes Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Released Bug description: Platform: OpenStack Yoga, Ubuntu 22.04 Jammy, Kernel 5.15.0-37-generic Charmed Openstack deployment with HW Offload over Jammy series will look ok until Vault initialization phase, then after initializing Vault all DB-related apps will end up in block/error state over "Failed to connect to MYSQL". Connectivity testing between DB containers located on different nodes will show there is unexplained sporadic packet loss preventing proper communication between the DB related apps. This will happen when the following conditions are met: 1. Control plane (oam, internal spaces) is configured as vlan interfaces on the same OVS bridge used for data plane (over high speed NIC with HW Offload capabilities). 2. OVS was set with HW offload=true (will happen by OVN chrams after Vault initialization) 3. NIC was not yet set to "switchdev" mode (netplan file will be created by OVN chrams after Vault initialization, however will take affect only after node is rebooted) The root cause is the following missing kernel patch: https://patchwork.kernel.org/project/netdevbpf/patch/20220531205447.99236-3-sa...@kernel.org/ To reproduce: Deploy charmed openstack with HW offload while using control plane on the high speed NIC OVS bridge. Before initializing Vault login to one of the innoDB instances and ping the other 2 instances - all ok. Manually enable OVS HW Offload, ping will become inconsistent. Workaround: After the deployment bring-up phase, BEFORE enabling Vault, login to the nodes and manually create 150-charm-ovn.yaml (example below). Then reboot one node after another. When nodes recover proceed with Vault initialization to complete the deployment. #root@node3:/home/ubuntu# cat /etc/netplan/150-charm-ovn.yaml ### # [ WARNING ] # Configuration file maintained by Juju. Local changes may be overwritten. # Config managed by ovn-chassis charm ### network: version: 2 ethernets: ens1f0: virtual-function-count: 8 embedded-switch-mode: switchdev delay-virtual-functions-rebind: true ens1f1: virtual-function-count: 8 embedded-switch-mode: switchdev delay-virtual-functions-rebind: true --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 4 10:46 seq crw-rw 1 root audio 116, 33 Jul 4 10:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=UUID=db1801a9-daa1-4386-b2ec-c65a40bc5dd3 ro intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/05/2015 dmi.bios.release: 1.32 dmi.bios.vendor: HP dmi.bios.version: P89 d
[Kernel-packages] [Bug 1980951] Re: [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list
This bug is awaiting verification that the linux- gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1980951 Title: [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * A kernel Oops occurs when a device is removed from the cio_ignore list (that is used to hide ccw devices) on a system with non-I/O subchannels (e.g. SCM or CHSC subchannels). * As a result, previously ignored devices cannot be activated again, and new devices cannot be found. [Fix] * 0c3812c347bf 0c3812c347bfb0dc213556a195e79850c55702f5 "s390/cio: derive cdev information only for IO-subchannels" [Test Plan] * An IBM zSystems or LinuxONE LPAR with with non-I/O subchannels. * Ubuntu Server 22.04 LTS (with GA kernel 5.15) installed. * Define a cio_ignore list (to hide ccw devices). * Remove a device from the cio_ignore list. * Due to hardware requirements this test needs to be conducted by IBM. [Where problems could occur] * General problems may occur with ccw device activation/deactivation in case the new initialization is erroneous. * Issues may also have an impact on the type of ccw devices, and may no longer be limited to non-I/O subchannels. * Things could still go wrong in case cdev is still not properly derived from sch-type SUBCHANNEL_TYPE_IO. [Other Info] * The commit is upstream since kernel 5.16 (next-20220315). __ ---Problem Description from Peter--- A kernel oops occurs when a device is removed from the cio_ignore list on a system with non-I/O subchannels (e.g. SCM or CHSC subchannels). As a result, previously ignored devices cannot be activated, and new devices cannot be found. ---uname output--- Linux localhost 5.15.0-40-generic #43-Ubuntu SMP Wed Jun 15 12:53:53 UTC 2022 s390x s390x s390x GNU/Linux Machine Type = s390x ---Steps to Reproduce--- On an s390x-LPAR with non-I/O subchannels, remove a device from the cio_ignore list. Oops output: [ 51.597505] Unable to handle kernel pointer dereference in virtual kernel address space [ 51.597516] Failing address: 2081e99191e98000 TEID: 2081e99191e98803 [ 51.597520] Fault in home space mode while using kernel ASCE. [ 51.597524] AS:82adc007 R3:0024 [ 51.597665] Oops: 0038 ilc:3 [#1] SMP [ 51.597671] Modules linked in: scm_block chsc_sch vfio_ccw mdev vfio_iommu_type1 vfio eadm_sch sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua drm i2c_core drm_panel_orientation_quirks ip_tables x_tables btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_ xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear pkey zcrypt crc32_vx_s390 ghash_s390 prng chacha_s390 libchacha aes_s390 des_s390 libdes qeth_l2 bridge stp llc zfcp qeth qdio scsi_transport_fc ccwgroup sha512_s390 sha256_s390 sha1_s390 sha_common [ 51.597735] CPU: 6 PID: 1418 Comm: cio_ignore Not tainted 5.15.0-40-generic #43-Ubuntu [ 51.597740] Hardware name: IBM 2964 NC9 702 (LPAR) [ 51.597742] Krnl PSW : 0704e0018000 81b0c632 (__unset_online+0x22/0x70) [ 51.597752]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [ 51.597756] Krnl GPRS: 0001 004a3ca8 038007e49000 2081e99191e98528 [ 51.597760] 81b0c610 81b07f10 [ 51.597762]02aa 81b0c610 038007e49000 038007a6bc98 [ 51.597765]941f9200 03ffa8cf95e0 81818900 038007a6bbf8 [ 51.597773] Krnl Code: 81b0c624: a784000cbrc 8,81b0c63c [ 51.597773]81b0c628: e3303022ltg %r3,32(%r3) [ 51.597773] #81b0c62e: a7840007brc 8,81b0c63c [ 51.597773] >81b0c632: e3303212lt %r3,512(%r3) [ 51.597773]81b0c638: a7740007brc 7,
[Kernel-packages] [Bug 1978297] Re: [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211
This bug is awaiting verification that the linux- gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1978297 Title: [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211 Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] When bootup Jammy kernel, it shows callrace: kernel: kernel: UBSAN: invalid-load in /home/u/aaron/bionic/net/mac80211/status.c:1164:21 kernel: load of value 216 is not a valid value for type '_Bool' kernel: CPU: 9 PID: 0 Comm: swapper/9 Not tainted 5.15.36+ #12 kernel: Hardware name: LENOVO 21D2SIT061/21D2SIT061, BIOS N3GET30W (1.11 ) 05/27/2022 kernel: Call Trace: kernel: kernel: dump_stack_lvl+0x4a/0x5f kernel: dump_stack+0x10/0x12 kernel: ubsan_epilogue+0x9/0x45 kernel: __ubsan_handle_load_invalid_value.cold+0x44/0x49 kernel: ieee80211_tx_status_ext.cold+0x1e/0xb0 [mac80211] kernel: ? percpu_ref_kill_and_confirm+0xd0/0xd0 kernel: ? rht_key_get_hash.isra.0+0x19/0x20 [mac80211] kernel: ? sta_info_hash_lookup+0xac/0x100 [mac80211] kernel: ieee80211_tx_status+0x72/0xa0 [mac80211] kernel: ieee80211_tasklet_handler+0xa2/0xd0 [mac80211] kernel: tasklet_action_common.constprop.0+0xc0/0xf0 kernel: tasklet_action+0x22/0x30 kernel: __do_softirq+0xd9/0x2e3 kernel: irq_exit_rcu+0x8c/0xb0 kernel: common_interrupt+0x8a/0xa0 kernel: kernel: kernel: asm_common_interrupt+0x1e/0x40 kernel: RIP: 0010:cpuidle_enter_state+0xd9/0x620 kernel: Code: 3d b4 85 3d 5c e8 57 a7 6b ff 49 89 c7 0f 1f 44 00 00 31 ff e8 a8 b3 6b ff 80 7d d0> kernel: RSP: 0018:9e2dc01f7e38 EFLAGS: 0246 kernel: RAX: 8dfdb6870b00 RBX: 8df6c3ab6c00 RCX: 00023cd33784 kernel: RDX: 00023d103fa8 RSI: 00023cd33784 RDI: kernel: RBP: 9e2dc01f7e88 R08: 00023cd33d63 R09: 000aae60 kernel: R10: 0004 R11: 071c71c71c71c71c R12: a4ce65a0 kernel: R13: 0003 R14: 0003 R15: 00023cd33d63 kernel: ? cpuidle_enter_state+0xc8/0x620 kernel: ? sched_clock_local+0x13/0x90 kernel: cpuidle_enter+0x2e/0x40 kernel: do_idle+0x203/0x2a0 kernel: cpu_startup_entry+0x20/0x30 kernel: start_secondary+0x12a/0x180 kernel: secondary_startup_64_no_verify+0xc2/0xcb kernel: kernel: [Fix] The size of the status_driver_data field was not adjusted when the is_valid_ack_signal field was added. Adjust the struct size accordingly. [Test] Verified on hardware, no error. [Where problems could occur] Low risk, It may break wifi driver. Minor changes in title of "Copyright" when backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978297/+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 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors
This bug is awaiting verification that the linux- gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1983143 Title: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released 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 Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Summary] No video output on Thunderbolt monitor. 1. Connect monitor to DUT directly 2. Connect monitor to DUT via Docking System can detect the monitor and able to change display mode but no output on the monitor [Steps to reproduce] 1. Boot to OS 2. Plug an external monitor via thunderbolt port [Expected result] Display on external monitor normally [Actual result] No vidoe ouput on external monitor [Failure rate] 3/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983143/+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 1978145] Re: Request to back port vmci patches to Ubuntu kernel
This bug is awaiting verification that the linux-
gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
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/1978145
Title:
Request to back port vmci patches to Ubuntu kernel
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification
[Impact]
The request is to bring vmci to TOT and back port the following patches into
Ubuntu kernels.
1. fac608138c6136126faadafa5554cc0bbabf3c44 ("VMCI: dma dg: whitespace
formatting change for vmci register defines")
2. e283a0e8b7ea83915e988ed059384af166b444c0 ("VMCI: dma dg: add MMIO access
to registers")
3. eed2298d936087a1c85e0fa6f7170028e4f4fded ("VMCI: dma dg: detect DMA
datagram capability")
4. 8cb520bea1470ca205980fbf030ed1f472f4af2f ("VMCI: dma dg: set OS page
size")
5. cc68f2177fcbfe2dbe5e9514789b96ba5995ec1e ("VMCI: dma dg: register dummy
IRQ handlers for DMA datagrams")
6. 5ee109828e73bbe4213c373988608d8f33e03d78 ("VMCI: dma dg: allocate send
and receive buffers for DMA datagrams")
7. 22aa5c7f323022477b70e044eb00e6bfea9498e8 ("VMCI: dma dg: add support for
DMA datagrams sends")
8. 463713eb6164b6577f8e91447c7745628215531b ("VMCI: dma dg: add support for
DMA datagrams receive")
9. 77e861619baea5a7c934e47fda74b03c0b072aec ("VMCI: Fix some error handling
paths in vmci_guest_probe_device()")
10. c8e9b30ccae605bf1dbeaf03971f9b83f70b928d ("VMCI: Release
notification_bitmap in error path")
11. 5df0e734b8c39598effe0f17e5bd8ff7748a0693 ("VMCI: Check exclusive_vectors
when freeing interrupt 1")
12. 1f7142915d304804a9bd952245fce92786b1b62f ("VMCI: Add support for ARM64")
13. ba03a9bbd17b149c373c0ea44017f35fc2cd0f28 ("VMCI: Release resource if the
work is already queued")
There is a new version of the VMCI device. Patches #1 to #11 provide
support for that, see [1] for some information on what is new. #12
adds arm64 support (we only support the new version of the VMCI device
in arm64, but both old and new versions of VMCI device are supported
in x86). #13 is a general bugfix. All 13 patches can build on both
x86 and arm64.
[1]
https://lore.kernel.org/all/20220203131237.3380-1-jhan...@vmware.com
[Test Case]
VMWARE tested
[Where things could go wrong]
The VMCI device driver could fail.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978145/+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 1978244] Re: [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
This bug is awaiting verification that the linux- gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1978244 Title: [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Bug description: [Impact] Screen corruption can occur when s2idle resume. [Fix] Check that DMCUB is running and wait for auto-load. [Test] Verified on hardware, stress s2idle and passed. [Where problems could occur] Low risk, It may break s2idle on AMD GPU driver. This commit is in 5.17. OEM kernels already got this commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978244/+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: Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events
This bug is awaiting verification that the linux- gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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: Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events Status in dellserver: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released 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 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 3134689f98 PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() [Test Case] 1. Disable the memory space of NVMe end point device 2. Issue IO to the device 3. Observe dmesg. dmesg shows that EDR event is generated, link is contained and NVMe device is recovered. 2. Observe the dmesg [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/test_dpc_1965241 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 1959973] Re: [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto)
This bug is awaiting verification that the linux- gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1959973 Title: [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto) Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * This is a hardware enablement SRU in support of IBM z15 and LinuxONE III (FC 115) secure execution feature. * It adds a misc character device to expose some Ultravisor functions to userspace. * The device is only available if the (optional) Ultravisor Facility (158) is present in the system. * Two Ultravisor calls are supported: - Query Ultravisor Information (QUI) and - Receive Attestation Measurement (Attest[ation]) * This is in support of for example. external frameworks, specific deployment models or especially potentially regulatory requirements. [Fix] * 4689752c79fa 4689752c79fa30e91b49b39a9fba93c4d1f3e20c "drivers/s390/char: Add Ultravisor io device" * eb3de2d8f78d eb3de2d8f78d893303891d879f941c47f2f2d13d "s390/uv_uapi: depend on CONFIG_S390" * patch to set kernel config option 'CONFIG_S390_UV_UAPI=y' [Test Plan] * An IBM z15 or LinuxONE III LPAR with FC 115 enabled is required. * Installation of Ubuntu Server 22.04 LTS on top. * Install a kernel that incl. the above patches/commits (that has the kernel config option 'CONFIG_S390_UV_UAPI' enabled). * Activate the kernel (reboot) and look for the existence of the uvdevice '/dev/uv'. * Use a userspace test program that makes use of the new misc device by exploiting 'ATTEST'. * Due to hardware requirements this test needs to be conducted by IBM. [Where problems could occur] * The definitions in uv_cmds_inst and uv_feat_ind could be wrong and the codes wrong or mixed up, which would lead to a broken functionality/interface. * The uvdevice header definitions could be erroneous, defining an wrong interface. * The newly added kernel options could be implemented in a wrong way, so that it doesn't enable the 'uvdevice', but unlikely. * The implementation of the device itself in 'uvdevice.c' could be broken by wrong or broken pointer arithmetics, wrong method arguments, wrong sizeof/length calculations, which - in worst case - could entirely crash a system. * The ioctl control block implementation could be wrong in a way, that it doesn't properly handle the case where the facility is not available in the system. * Entry point, copy and check routines could be wrong, allowing non-desired calls. * This is an s390x-only functionality, that is only available on IBM z15 / LinuxONE III systems and newer, and only is the optional feature 'FC 115' in place, which is limited to 'secure-execution' workloads. [Other Info] * The above commit is marked to be merged into 5.19-rc2, and since the planned target kernel for kinetic is 5.19, the SRU is not needed for kinetic. __ KVM: Attestation support for Secure Execution (crypto) Description: Provide attestations support, e.g. for external frameworks, specific deployment models or potentially regulatory requirements. Request Type: Kernel - Enhancement from IBM Upstream Acceptance: In Progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959973/+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
This bug is awaiting verification that the linux- gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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 Released 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 1953613] Re: GPIO character device v1 API not enabled in kernel
This bug is awaiting verification that the linux- gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device v1 API not enabled in kernel Status in linux package in Ubuntu: Fix Released Status in linux-allwinner-5.17 package in Ubuntu: Invalid Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-starfive-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-allwinner-5.17 source package in Jammy: Fix Released Status in linux-hwe-5.17 source package in Jammy: Fix Committed Status in linux-starfive-5.17 source package in Jammy: Fix Released Bug description: [Impact] * The libgpiod2 library and gpiod tools shipped in Jammy don't work. * These tools are meant to replace the old sysfs interface and be a better and more efficient way to manipulate GPIOs from userspace. Unfortunately the latest release is still using v1 of the character device kernel API which is not enabled in Ubuntu kernels. * This is Kent Gibsons reply on the linux-gpio mailing list: On Tue, Jul 12, 2022 at 09:48:45AM +0200, Alexandre Ghiti wrote: > Hi, > > Ubuntu kernels do not enable GPIO_CDEV_V1 as it is deprecated, but the > libgpiod package that we ship is still based on the latest version > 1.6.3 which does not implement the API v2. So I'd like to update > libgpiod, do you have any recommendations about what branch/sha1 I > should use? Do you plan to make a release that implements the API v2? > Firstly, libgpiod is Bart's library so he is the authority, but this is my understanding... TLDR: You should keep GPIO_CDEV_V1 enabled. v1 is deprecated from a development perspective, so all new feature development will occur on v2, and new applications should target v2. Existing apps targetting v1, be that directly or via libgpiod v1.6.3, will require GPIO_CDEV_V1 until they migrate to v2. The mainline kernel will continue to support v1 while userspace transitions. libgpiod v2 is in active development, and should reach its first release shortly. Note that it is NOT a plugin replacement for v1. It has a different API, for similar reasons to why we had to switch in the kernel, so apps will need to be actively migrated. I wouldn't suggest making any effort to package libgpiod v2 until Bart makes an official release. Cheers, Kent. [Test Plan] * Run gpioinfo on a machine with exposed GPIOs and check that it lists the GPIOs and doesn't error with gpioinfo: error creating line iterator: Invalid argument [Where problems could occur] * There may be code and scripts that hasn't been tested with a working libgpiod2/gpiod tools and uncover latent bugs. [Other Info] Original bug text: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-
[Kernel-packages] [Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)
This bug is awaiting verification that the linux-
gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
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/1884232
Title:
touchpad and touchscreen doesn't work at all on ACER Spin 5
(SP513-54N)
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
E820 reserved retire memory window, and make other hot-added devices unable
to get the required memory window.
[Fix]
It only can be fixed by a list of quirk to mark those machines out, and
requires below commits from v5.19-rc1 and v5.19-rc3
a2b36ffbf5b6 x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820
regions"
d341838d776a x86/PCI: Disable E820 reserved region clipping via quirks
fa6dae5d8208 x86/PCI: Add kernel cmdline options to use/ignore E820 reserved
regions
4c5e242d3e93 x86/PCI: Clip only host bridge windows for E820 regions
31bf0f433325 x86: Log resource clipping for E820 regions
93d256cd3c1e x86/PCI: Eliminate remove_e820_regions() common subexpressions
[Test]
Verified by the bug reporter.
[Where problems could occur]
The 6 commits are all clean cherry-picked, and the sixth commit reverts the
third commit which are the 2 commits that do real functional changes.
a2b36ffbf5b6 ("x86/PCI: Revert \"x86/PCI: Clip only host bridge windows for
E820 regions\"")
4c5e242d3e93 ("x86/PCI: Clip only host bridge windows for E820 regions")
The fourth and and fifth commits introduce a new quirk to ignore E820
reserved regions and the quirk only affects the listed machines.
Drivers that operates E820 table may fail if we ignore the E820 regions, but
it should have no impact on the listed consumer PCs.
===
Touchpad is not working at all on ACER Spin 5 SP513-54N.
According to
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29
I am creating this kernel bug issue.
There are more issues, too, like touchscreen not working and Ubuntu
not installable - see here if interrested
https://askubuntu.com/questions/1251719/
I would like to run Ubuntu on this machine and I am willing to help
with any debug or kernel tweaking... Please let me know.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-26-generic 5.4.0-26.30
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 4195 F pulseaudio
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 19 10:44:58 2020
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Acer Spin SP513-54N
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
RelatedPackageVersions:
linux-restricted-modules-5.4.0-26-generic N/A
linux-backports-modules-5.4.0-26-generic N/A
linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2020
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.00
dmi.board.name: Caboom_IL
dmi.board.vendor: IL
dmi.board.version: V1.00
dmi.chassis.type: 31
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.00
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00:
dmi.product.family: Spin 5
dmi.product.name: Spin SP513-54N
dmi.product.sku:
dmi.product.version: V1.00
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : htt
[Kernel-packages] [Bug 1976248] Re: Revert PPC get_user workaround
This bug is awaiting verification that the linux- gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1976248 Title: Revert PPC get_user workaround Status in linux package in Ubuntu: Fix Committed Status in zfs-linux package in Ubuntu: Fix Committed Status in linux source package in Impish: Fix Committed Status in zfs-linux source package in Impish: New Status in linux source package in Jammy: Fix Released Status in zfs-linux source package in Jammy: New Status in linux source package in Kinetic: Fix Committed Status in zfs-linux source package in Kinetic: Fix Committed Bug description: [Impact] * A change of kernel symbol license allows to drop a PPC specific workaround in zfs-dkms to use the regular (better) code paths. * See details in: https://git.launchpad.net/ubuntu/+source/zfs- linux/tree/debian/patches/4900-ppc-get-user-workaround.patch https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009242 [Test Plan] * linux: apply https://github.com/torvalds/linux/commit/d9e5c3e9e75162f845880535957b7fd0b4637d23 * zfs-dkms: revert https://git.launchpad.net/ubuntu/+source/zfs- linux/tree/debian/patches/4900-ppc-get-user-workaround.patch * Build on kernel with zfs module on ppc * Ensure that zfs.ko successfully loads and works * Test that root on zfs installations work on ppc (however, Ubuntu currently doesn't provide an installation method to achieve this, so this bit of verification might be hard to complete) [Where problems could occur] * linux: the patch only changes the symbol licensing and the potential tainteness status of the kernel, without any observable user or kernel space impacts * zfs-dkms: The PPC workaround patch is known to be buggy, and the new arch-independent codepath may now use optimized codepaths inside kernel resulting in a different behavior as observed by user-space (operation successful, EFAULT not returned) matching the behavior of all other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976248/+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 1973104] Re: e1000e report hardware hang
This bug is awaiting verification that the linux- gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1973104 Title: e1000e report hardware hang Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] e1000e hardware unit hang after s2idle May 06 15:34:49 ubuntu kernel: e1000e :00:1f.6 enp0s31f6: Detected Hardware Unit Hang: TDH <1> TDT <5> next_to_use <5> next_to_clean <1> buffer_info[next_to_clean]: time_stamp <1000587f0> next_to_watch <1> jiffies <1000589c0> next_to_watch.status <0> MAC Status <40080283> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status <3000> PCI Status <10> [Fix] Below commits fix this issue which have been included in v5.19-rc8 https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20220508070905.1878172-1-sasha.nef...@intel.com/ 6cfa45361d3e Revert "e1000e: Fix possible HW unit hang after an s0ix exit" b49feacbeffc e1000e: Enable GPT clock before sending message to CSME [Test] Verified on the target machine, and confirmed the issue is gone. [Where problems could occur] The impact is low, it keeps the GPT clock enabled for CSME when e1000e_pm_resume() is called. With the new fix, the old workaround could be removed. I can't see this may introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1973104/+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 1991285] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1991285 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => 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/1991285 Title: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.4.0-128.144 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1961338] Re: Disable unprivileged BPF by default
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1018.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1961338 Title: Disable unprivileged BPF by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Unprivileged users have access to BPF, allowing them to execute code in the kernel under their control. Though restricted and verified, a lot of security issues have been uncovered over the years, indicating that it should be disabled by default in order to protect our users. Admins can reenable that access or give CAP_BPF to programs if needed. [Test case] A qa-regression-testing testcase has been added that checks for the ability to load BPF programs under different circumstances. [Potential regression] Users who rely on unprivileged BPF access will need to change the setting or give CAP_BPF to their programs. Also, sysctl and bpf code might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+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 1991286] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991286 Title: package linux-tools-5.15.0-48 (not installed) failed to install/upgrade: tentative de remplacement de « /usr/lib/libcpupower.so.5.15.0-48 », qui appartient aussi au paquet linux-lowlatency-tools-5.15.0-48 5.15.0-48.54 Status in linux package in Ubuntu: Confirmed Bug description: Bonjour, Des paquets synaptic ne s'installent pas. Avec Synaptic, il est difficile de savoir quoi installer alors qu'avec Ubuntu Software, les icones informaient tout de suite de quoi il s'agissait. Ubuntu software ne fonctionne pas, comment faire ? Avec mes remerciements Marie-Hélène ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-5.15.0-48 (not installed) ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marie 1863 F pulseaudio /dev/snd/controlC0: marie 1863 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Sep 29 16:12:08 2022 ErrorMessage: tentative de remplacement de « /usr/lib/libcpupower.so.5.15.0-48 », qui appartient aussi au paquet linux-lowlatency-tools-5.15.0-48 5.15.0-48.54 InstallationDate: Installed on 2022-08-21 (39 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. X540YA ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b3fc9ef4-e867-41a1-97ad-05154adeece5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux Title: package linux-tools-5.15.0-48 (not installed) failed to install/upgrade: tentative de remplacement de « /usr/lib/libcpupower.so.5.15.0-48 », qui appartient aussi au paquet linux-lowlatency-tools-5.15.0-48 5.15.0-48.54 UpgradeStatus: Upgraded to jammy on 2022-08-21 (38 days ago) dmi.bios.date: 12/31/2019 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X540YA.323 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X540YA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX540YA.323:bd12/31/2019:br4.6:svnASUSTeKCOMPUTERINC.:pnX540YA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540YA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X540YA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991286/+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 1980951] Re: [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list
linux-gkeop-5.15 is out of scope for this bug (does not exist for s390x). To unblock the process I'll add the 'verification-done-focal' tag. ** 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/1980951 Title: [UBUNTU 22.04] Kernel oops while removing device from cio_ignore list Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * A kernel Oops occurs when a device is removed from the cio_ignore list (that is used to hide ccw devices) on a system with non-I/O subchannels (e.g. SCM or CHSC subchannels). * As a result, previously ignored devices cannot be activated again, and new devices cannot be found. [Fix] * 0c3812c347bf 0c3812c347bfb0dc213556a195e79850c55702f5 "s390/cio: derive cdev information only for IO-subchannels" [Test Plan] * An IBM zSystems or LinuxONE LPAR with with non-I/O subchannels. * Ubuntu Server 22.04 LTS (with GA kernel 5.15) installed. * Define a cio_ignore list (to hide ccw devices). * Remove a device from the cio_ignore list. * Due to hardware requirements this test needs to be conducted by IBM. [Where problems could occur] * General problems may occur with ccw device activation/deactivation in case the new initialization is erroneous. * Issues may also have an impact on the type of ccw devices, and may no longer be limited to non-I/O subchannels. * Things could still go wrong in case cdev is still not properly derived from sch-type SUBCHANNEL_TYPE_IO. [Other Info] * The commit is upstream since kernel 5.16 (next-20220315). __ ---Problem Description from Peter--- A kernel oops occurs when a device is removed from the cio_ignore list on a system with non-I/O subchannels (e.g. SCM or CHSC subchannels). As a result, previously ignored devices cannot be activated, and new devices cannot be found. ---uname output--- Linux localhost 5.15.0-40-generic #43-Ubuntu SMP Wed Jun 15 12:53:53 UTC 2022 s390x s390x s390x GNU/Linux Machine Type = s390x ---Steps to Reproduce--- On an s390x-LPAR with non-I/O subchannels, remove a device from the cio_ignore list. Oops output: [ 51.597505] Unable to handle kernel pointer dereference in virtual kernel address space [ 51.597516] Failing address: 2081e99191e98000 TEID: 2081e99191e98803 [ 51.597520] Fault in home space mode while using kernel ASCE. [ 51.597524] AS:82adc007 R3:0024 [ 51.597665] Oops: 0038 ilc:3 [#1] SMP [ 51.597671] Modules linked in: scm_block chsc_sch vfio_ccw mdev vfio_iommu_type1 vfio eadm_sch sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua drm i2c_core drm_panel_orientation_quirks ip_tables x_tables btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_ xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear pkey zcrypt crc32_vx_s390 ghash_s390 prng chacha_s390 libchacha aes_s390 des_s390 libdes qeth_l2 bridge stp llc zfcp qeth qdio scsi_transport_fc ccwgroup sha512_s390 sha256_s390 sha1_s390 sha_common [ 51.597735] CPU: 6 PID: 1418 Comm: cio_ignore Not tainted 5.15.0-40-generic #43-Ubuntu [ 51.597740] Hardware name: IBM 2964 NC9 702 (LPAR) [ 51.597742] Krnl PSW : 0704e0018000 81b0c632 (__unset_online+0x22/0x70) [ 51.597752]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [ 51.597756] Krnl GPRS: 0001 004a3ca8 038007e49000 2081e99191e98528 [ 51.597760] 81b0c610 81b07f10 [ 51.597762]02aa 81b0c610 038007e49000 038007a6bc98 [ 51.597765]941f9200 03ffa8cf95e0 81818900 038007a6bbf8 [ 51.597773] Krnl Code: 81b0c624: a784000cbrc 8,81b0c63c [ 51.597773]81b0c628: e3303022ltg %r3,32(%r3) [ 51.597773] #81b0c62e: a7840007brc 8,81b0c63c [ 51.597773] >81b0c632: e3303212lt %r3,512(%r3) [ 51.597773]81b0c638: a7740007brc 7,81b0c646 [ 51.597773]81b0c63c: a729lghi%r2,0 [ 51.597773]81b0c640: c0f400089854brcl 15,81c1f6e8 [ 51.597773]81b0c646: ebeff0880024stmg %r14,%r15,136(%r15) [ 51.597818] Call Trace: [ 51.597820] [<81b0c632>] __unset_online+0x22/0x70 [ 51.597824] ([<818188e6>] bus_for_each_dev+0x66/0xc0) [ 51
[Kernel-packages] [Bug 1959973] Re: [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto)
linux-gkeop-5.15 is out of scope for this bug (does not exist for s390x). To unblock the process I'll add the 'verification-done-focal' tag. ** 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/1959973 Title: [22.04 FEAT] KVM: Attestation support for Secure Execution (crypto) Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * This is a hardware enablement SRU in support of IBM z15 and LinuxONE III (FC 115) secure execution feature. * It adds a misc character device to expose some Ultravisor functions to userspace. * The device is only available if the (optional) Ultravisor Facility (158) is present in the system. * Two Ultravisor calls are supported: - Query Ultravisor Information (QUI) and - Receive Attestation Measurement (Attest[ation]) * This is in support of for example. external frameworks, specific deployment models or especially potentially regulatory requirements. [Fix] * 4689752c79fa 4689752c79fa30e91b49b39a9fba93c4d1f3e20c "drivers/s390/char: Add Ultravisor io device" * eb3de2d8f78d eb3de2d8f78d893303891d879f941c47f2f2d13d "s390/uv_uapi: depend on CONFIG_S390" * patch to set kernel config option 'CONFIG_S390_UV_UAPI=y' [Test Plan] * An IBM z15 or LinuxONE III LPAR with FC 115 enabled is required. * Installation of Ubuntu Server 22.04 LTS on top. * Install a kernel that incl. the above patches/commits (that has the kernel config option 'CONFIG_S390_UV_UAPI' enabled). * Activate the kernel (reboot) and look for the existence of the uvdevice '/dev/uv'. * Use a userspace test program that makes use of the new misc device by exploiting 'ATTEST'. * Due to hardware requirements this test needs to be conducted by IBM. [Where problems could occur] * The definitions in uv_cmds_inst and uv_feat_ind could be wrong and the codes wrong or mixed up, which would lead to a broken functionality/interface. * The uvdevice header definitions could be erroneous, defining an wrong interface. * The newly added kernel options could be implemented in a wrong way, so that it doesn't enable the 'uvdevice', but unlikely. * The implementation of the device itself in 'uvdevice.c' could be broken by wrong or broken pointer arithmetics, wrong method arguments, wrong sizeof/length calculations, which - in worst case - could entirely crash a system. * The ioctl control block implementation could be wrong in a way, that it doesn't properly handle the case where the facility is not available in the system. * Entry point, copy and check routines could be wrong, allowing non-desired calls. * This is an s390x-only functionality, that is only available on IBM z15 / LinuxONE III systems and newer, and only is the optional feature 'FC 115' in place, which is limited to 'secure-execution' workloads. [Other Info] * The above commit is marked to be merged into 5.19-rc2, and since the planned target kernel for kinetic is 5.19, the SRU is not needed for kinetic. __ KVM: Attestation support for Secure Execution (crypto) Description: Provide attestations support, e.g. for external frameworks, specific deployment models or potentially regulatory requirements. Request Type: Kernel - Enhancement from IBM Upstream Acceptance: In Progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959973/+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 1990394] [NEW] Wifi and Bluetooth with rtl8852be not working
You have been subscribed to a public bug: Realtek rtl8852be Wifi and Bluetooth not working on Kubuntu 22.04 and Ubuntu 22.10 (daily, 20.9.2022). Works on 22.04 just by compiling it yourself as Kernel-Module. 04:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device b852 Subsystem: Lenovo Device 4853 Flags: bus master, fast devsel, latency 0, IRQ 81, IOMMU group 14 I/O ports at 2000 [size=256] Memory at d050 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: rtl8852be Kernel modules: 8852be ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment kinetic rtl8852be -- Wifi and Bluetooth with rtl8852be not working https://bugs.launchpad.net/bugs/1990394 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990394] Re: Wifi and Bluetooth with rtl8852be not working
** Tags added: kinetic ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990394 Title: Wifi and Bluetooth with rtl8852be not working Status in linux package in Ubuntu: New Bug description: Realtek rtl8852be Wifi and Bluetooth not working on Kubuntu 22.04 and Ubuntu 22.10 (daily, 20.9.2022). Works on 22.04 just by compiling it yourself as Kernel-Module. 04:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device b852 Subsystem: Lenovo Device 4853 Flags: bus master, fast devsel, latency 0, IRQ 81, IOMMU group 14 I/O ports at 2000 [size=256] Memory at d050 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: rtl8852be Kernel modules: 8852be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990394/+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 1990394] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1990394 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => 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/1990394 Title: Wifi and Bluetooth with rtl8852be not working Status in linux package in Ubuntu: Incomplete Bug description: Realtek rtl8852be Wifi and Bluetooth not working on Kubuntu 22.04 and Ubuntu 22.10 (daily, 20.9.2022). Works on 22.04 just by compiling it yourself as Kernel-Module. 04:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device b852 Subsystem: Lenovo Device 4853 Flags: bus master, fast devsel, latency 0, IRQ 81, IOMMU group 14 I/O ports at 2000 [size=256] Memory at d050 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: rtl8852be Kernel modules: 8852be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990394/+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 1991130] Re: Fix lrm transitional autogenerate
** Description changed: [Impact] The kernel lrm packages have a mechanism to auto-generate transitional packages by adding a line to 'debian/package.config' in the following format transitional Example: transitional 450-oem-20.04 450-generic amd64 When being processed by 'debian/scripts/gen-rules.lrm' the autogenerated - contents are added to 'debian/control.d/transitionals-local', however, + contents are added to 'debian/control.d/transitionals-local'. However, this file is not included in the final 'debian/control' for packages which does not contain the default variant '--' (see debian/rules.in). This is intentional to prevent unwanted transitionals. However, there are some cases where we want to transition packages to kernels which are not the default variant in a series (e.g. hwe kernels). + + [Fix] + + The proposed fix is to add a new command "migrate", which does exactly + what "transitional" does but adding the content to + 'debian/control.d/migrate-local' which would get added to the final + 'debian/control' independently of the source's variants. + + [Test Case] + + Add "migrate" entries to 'debian/package.config' and check whether they + get added to 'debian/control' even for non default variant packages. + + [Where problems could occur] + + If not used correctly, unwanted transitionals could be generated causing + issues to the archive. However, this is a new command and should not + impact any of the previously set transitionals and it needs to be + explicitly used. ** Summary changed: - Fix lrm transitional autogenerate + Add lrm autogenerated transitional independent of variants -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1991130 Title: Add lrm autogenerated transitional independent of variants Status in linux-restricted-modules-hwe-5.15 package in Ubuntu: Invalid Status in linux-restricted-modules-hwe-5.15 source package in Focal: In Progress Bug description: [Impact] The kernel lrm packages have a mechanism to auto-generate transitional packages by adding a line to 'debian/package.config' in the following format transitional Example: transitional 450-oem-20.04 450-generic amd64 When being processed by 'debian/scripts/gen-rules.lrm' the autogenerated contents are added to 'debian/control.d/transitionals- local'. However, this file is not included in the final 'debian/control' for packages which does not contain the default variant '--' (see debian/rules.in). This is intentional to prevent unwanted transitionals. However, there are some cases where we want to transition packages to kernels which are not the default variant in a series (e.g. hwe kernels). [Fix] The proposed fix is to add a new command "migrate", which does exactly what "transitional" does but adding the content to 'debian/control.d/migrate-local' which would get added to the final 'debian/control' independently of the source's variants. [Test Case] Add "migrate" entries to 'debian/package.config' and check whether they get added to 'debian/control' even for non default variant packages. [Where problems could occur] If not used correctly, unwanted transitionals could be generated causing issues to the archive. However, this is a new command and should not impact any of the previously set transitionals and it needs to be explicitly used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.15/+bug/1991130/+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 1991151] Re: mlxbf_gige: need to revert SAUCE patch for "clear MDIO gateway lock"
** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1991151 Title: mlxbf_gige: need to revert SAUCE patch for "clear MDIO gateway lock" Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: In Progress Bug description: SRU Justification: [Impact] The Jammy repo contains the following SAUCE patch: UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read This patch is now in mainline Linux kernel, so the SAUCE patch can be reverted and replaced with the upstream commit SHA. [Fix] The fix requires two parts, the first of which is addressed by this bug. A second bug will be created to add the upstream commit to the repo. The fix to this bug is a revert of the SAUCE patch 8d2dbbd437a1 UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read [Test Case] Boot platform and bring up "oob_net0" interface properly Test that network traffic works properly [Regression Potential] Low, as this logic is well tested. [Other] Will add a note to this bug with the second bug's number, after the second bug is created. The second bug is for adding the upstream commit to the Jammy repo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1991151/+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 1961338] Re: Disable unprivileged BPF by default
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1018.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1961338 Title: Disable unprivileged BPF by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Unprivileged users have access to BPF, allowing them to execute code in the kernel under their control. Though restricted and verified, a lot of security issues have been uncovered over the years, indicating that it should be disabled by default in order to protect our users. Admins can reenable that access or give CAP_BPF to programs if needed. [Test case] A qa-regression-testing testcase has been added that checks for the ability to load BPF programs under different circumstances. [Potential regression] Users who rely on unprivileged BPF access will need to change the setting or give CAP_BPF to their programs. Also, sysctl and bpf code might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+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 1806437]
This is fixed by the following commit which will be in 6.1: https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=review-hans&id=134038b075cb1dae21623499d765973d286ac94a -- 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/1806437 Title: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.390738] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 12:49:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806437/+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 1806437]
Thanks a lot! I am looking forward to kernel 6.1... -- 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/1806437 Title: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.390738] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 12:49:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806437/+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 1806437]
(In reply to Laurent Bonnaud from comment #18) > Thanks a lot! I am looking forward to kernel 6.1... Was this anything but just cosmetic? I looked at the patch and am running it now and nothing in the dmesg has changed (nor any functionality) except the messages aren't printed any longer. -- 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/1806437 Title: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.390738] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 12:49:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806437/+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 1806437]
During the architectural design of the WMI subsystem an assumption was made that there was a 1:1 mapping of WMI GUIDs (that is they're unique). This hasn't caused MAJOR functional problems, but this was proven wrong, as it's possible to fetch multiple BMOFs. This change makes it so that if you have the wmi-bmof driver loaded on your system you'll be able to fetch all of the BMOFs. If you look in /sys/bus/wmi/devices, you should see more entries with this patch in place. If the same GUID is used multiple times on a system for any reason beside wmi-bmof, that driver may need to be changed too. -- 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/1806437 Title: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.390738] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 12:49:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806437/+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 1806437] Re: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
** Changed in: linux Status: Confirmed => Fix Released -- 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/1806437 Title: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.390738] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 12:49:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806437/+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 1990964] Re: FTBFS on kinetic
** Tags added: foundations-todo -- 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/1990964 Title: FTBFS on kinetic Status in linux package in Ubuntu: In Progress Status in strace package in Ubuntu: New Bug description: As can be seen in [1], strace FTBFS in kinetic: this is caused by the kernel headers (linux-libc-dev) which do not define F_GETLK64 and other on 64b builds because the kernel contains a bogus commit (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in fcntl.h"). This commit actually did the opposite of what it was supposed to do, namely defining those macros even on 64b builds. There is an attempt here to fix this which was not merged yet: https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/ [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic- amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+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 1990621] Re: PXE Boot contains wrong suggested link to ISO for live file system
** Tags added: foundations-todo -- 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/1990621 Title: PXE Boot contains wrong suggested link to ISO for live file system Status in casper package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: When PXE booting without pulling in squashfs correctly the system tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release contains a link to the old version which is not present anymore. --- Unable to find a medium containing a live file system Attempt interactive netboot from a URL? yes no (default yes): Two methods available for IP configuration: * static: for static IP configuration * dhcp: for automatic IP configuration static dhcp (default 'dhcp'): vlan id (optional): https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso (default) https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso url: http_proxy (optional): [ 125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443) wget: server returned error: HTTP/1.1 404 Not Found done. Unable to find a medium containing a live file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1990621/+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 1989298] Re: amdgpu nullptr and video freeze
This problem did not occur on 6.0.0-06rc7-generic for 2 days, even with VA-API enabled. As I have moved on to 22.10, I will try to downgrade to the stable 5.19 and see if the problem still exists. -- 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/1989298 Title: amdgpu nullptr and video freeze Status in linux package in Ubuntu: Confirmed Bug description: # The majority of kernel bug are hardware specific so be sure to note what hardware/device is being used. - AMD RX 460 2GB - Dual but different ASUS monitors - Android ADB, but it always worked alone and was idle for 1 hour prior to the problem # Document any known steps to reproduce the bug. - Cold boot no hibernate - ADB stuff 2 hours before - Mesa is 22.1.7~kisak1~j - google-chrome-stable started with '/usr/bin/env LANGUAGE=ja_JP:ja LANG=ja_JP.UTF-8 /usr/bin/google-chrome-stable --enable-features=WebUIDarkMode,VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder --force-dark-mode %U' - Watching a twitch.tv stream at 3x speed at source (1080p) resolution (VDAVideoDecoder/vaapi) maximized on left DVI monitor - Konsole with `sensors` on right HDMI monitor - Locked screen for 5+ minutes with stream on - Unlocked screen then tried to play/pause stream a few times. The sound changed started/stopped but there were no video changes but the mouse moved - I tried to focus the Konsole window but its decorations didn't change color - CTRL-ALT-F1 didn't respond until after a few seconds - The TTY was a blank terminal with a solid non-blinking cursor - I SSHed in and ran `dmesg` without problem - I might have been able to reboot with SSH, but I held down the power button instead # Also note whether the bug exists in previous kernel versions of Ubuntu or if it's a regression from previous kernel versions. - I did not experience runtime amdgpu problems in any Linux 5.x versions - Suspend/resume to mem/disk has always failed 80% of the time, and even on Windows 10 - RAM used to be buggy a few years ago but I replaced one ram stick # Finally, it's critical to also make sure to test the latest development Ubuntu kernel version as well as the latest upstream mainline kernel. This bug appears probabilistic and I don't know how to test it even on the current kernel version ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: home 1230 F pulseaudio /dev/snd/controlC1: home 1230 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Sep 11 19:58:18 2022 HibernationDevice: RESUME=UUID=21d61484-fe9b-4310-9390-d5f5d17510d8 MachineType: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic root=UUID=29b85a8a-08f8-42be-8629-fb6e88d149d6 ro text pcie_port_pm=off resume=UUID=21d61484-fe9b-4310-9390-d5f5d17510d8 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-04 (130 days ago) dmi.bios.date: 05/19/2017 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K30BF_M32BF_A_F_K31BF_6 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd05/19/2017:br4.6:svnASUSTeKCOMPUTERINC.:pnK30BF_M32BF_A_F_K31BF_6:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnK30BF_M32BF_A_F_K31BF_6:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: Desktop dmi.product.name: K30BF_M32BF_A_F_K31BF_6 dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: home 1213 F pulseaudio /dev/snd/controlC1: home 1213 F pulseaudio CasperMD5CheckResult: unknown CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: ** (process:5211): WARNING **: 16:21:35.292: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
I've been asked to prepare a summary of the current status of this bug:
- there's a grub2 security update that's been published and then pulled:
https://launchpad.net/ubuntu/+source/grub2-unsigned/2.06-2ubuntu10/+publishinghistory
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1990684
- apt's dependency solver is being modified to handle updates that need
to phase identically
- once the apt update is released, then the grub security fixes can be
republished
- once the grub security fixes are republished, then this issue can be
addressed.
It appears there's an open question about the risks of jeremyszu's
changes possibly causing problems for older systems. The closest thing I
found in the linked thread was on this message:
https://lists.gnu.org/archive/html/grub-devel/2017-03/msg00033.html
> I seem to recall that the x86_64 port was being restricted due to
> known bad firmware encountered in the past. It could be that it would
> be worth adding an option to configure for enabling access to higher
> addresses, alternatively for retaining compatibility with the broken
> systems.
I haven't read through the patches nor the upstream issue tracker to
find out if these are recent problems or not, but this sounds like the
usual warning that grub is difficult to test, lives in firmwares that
may be ignored or otherwise horrible, etc. I hope we have a
representative sample of machines to test in our labs, as well as our
home offices, and in our wider community.
Was there a more specific problem that I missed?
Are there outstanding tasks that need doing that could be done before
the apt+security update steps are complete? Refreshing patches, or
skimming through issue trackers to find regressions from the patches,
etc?
Thanks
--
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/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-ge
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi-5.4/5.4.0.1071.71)
All autopkgtests for the newly accepted linux-meta-raspi-5.4 (5.4.0.1071.71) for bionic have finished running. The following regressions have been reported in tests triggered by the package: xtables-addons/unknown (arm64) wireguard-linux-compat/unknown (arm64) rtl8821ce/unknown (arm64) r8168/unknown (arm64) acpi-call/1.1.0-4 (arm64) ktap/unknown (arm64) dpdk/unknown (arm64) dm-writeboost/unknown (arm64) langford/unknown (arm64) linux-raspi-5.4/unknown (arm64) systemd/unknown (arm64) zfs-linux/unknown (arm64) bbswitch/0.8-4ubuntu1 (arm64) v4l2loopback/unknown (arm64) west-chamber/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-raspi-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1961338] Re: Disable unprivileged BPF by default
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1018.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1961338 Title: Disable unprivileged BPF by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Unprivileged users have access to BPF, allowing them to execute code in the kernel under their control. Though restricted and verified, a lot of security issues have been uncovered over the years, indicating that it should be disabled by default in order to protect our users. Admins can reenable that access or give CAP_BPF to programs if needed. [Test case] A qa-regression-testing testcase has been added that checks for the ability to load BPF programs under different circumstances. [Potential regression] Users who rely on unprivileged BPF access will need to change the setting or give CAP_BPF to their programs. Also, sysctl and bpf code might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+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 1991343] [NEW] package linux-modules-5.15.0-46-generic (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './boot/System.map-5.15.0-46-gener
Public bug reported: I can't upgrade my ubuntu distribution because this bug ubuntu 20.04.3 lts ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.15.0-46-generic (not installed) ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 AptOrdering: linux-modules-5.15.0-46-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 29 20:05:31 2022 ErrorMessage: no se pudieron copiar los datos extraídos de './boot/System.map-5.15.0-46-generic' a '/boot/System.map-5.15.0-46-generic.dpkg-new': fin de fichero o de flujo inesperado InstallationDate: Installed on 2021-03-08 (570 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.6 SourcePackage: linux-hwe-5.15 Title: package linux-modules-5.15.0-46-generic (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './boot/System.map-5.15.0-46-generic' a '/boot/System.map-5.15.0-46-generic.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1991343 Title: package linux-modules-5.15.0-46-generic (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './boot/System.map-5.15.0-46-generic' a '/boot/System.map-5.15.0-46-generic.dpkg-new': fin de fichero o de flujo inesperado Status in linux-hwe-5.15 package in Ubuntu: New Bug description: I can't upgrade my ubuntu distribution because this bug ubuntu 20.04.3 lts ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.15.0-46-generic (not installed) ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 AptOrdering: linux-modules-5.15.0-46-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 29 20:05:31 2022 ErrorMessage: no se pudieron copiar los datos extraídos de './boot/System.map-5.15.0-46-generic' a '/boot/System.map-5.15.0-46-generic.dpkg-new': fin de fichero o de flujo inesperado InstallationDate: Installed on 2021-03-08 (570 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.6 SourcePackage: linux-hwe-5.15 Title: package linux-modules-5.15.0-46-generic (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './boot/System.map-5.15.0-46-generic' a '/boot/System.map-5.15.0-46-generic.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1991343/+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 1990920] Re: Fix resume on AMD platforms when TBT monitor is plugged
** Merge proposal linked: https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800 ** Merge proposal linked: https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1990920 Title: Fix resume on AMD platforms when TBT monitor is plugged Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.17 source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] When TBT monitor is connected to AMD platform, system resume will hit stack corruption or BUG_ON() macro. [Fix] Revert the offending commit and handle MST properly. [Test] The system can resume normally and no more kernel splat. [Where problems could occur] The new logic is restriced to MST hub, so normal DP/HDMI usage should be unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990920/+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 1990330] Re: System hang during S3 test
** Merge proposal linked: https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800 ** Merge proposal linked: https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802 -- 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/1990330 Title: System hang during S3 test Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] It hangs while doing S3 test on the platform with CPU Intel(R) Pentium(R) Silver N6005 @ 2.00GHz [Fix] Can't reproduce this issue with v5.18-rc1 kernel, so bisecting the kernel and found this below commit 567511462387 mm/memcg: protect memcg_stock with a local_lock_t For safty, I backported the series of the patch https://www.spinics.net/lists/cgroups/msg31595.html But I still can reproduce the issue after applied those patches on top of 5.17 oem kernel. So, I did a second round of bisecting and found below commit is required, too a74c6c00b1cb mm/memremap: avoid calling kasan_remove_zero_shadow() for device private memory [Test] Done the S3 test 400 times on the target and it's still working well. [Where problems could occur] Hard to evaluate the impact, but from the overnight test, the memory usage is still low, so there should be no memory leakage, and can't find any fix patch for those applied commits from upstream and linux-next trees. The patches are all from v5.18-rc1, so we only need them to be applied on oem-5.17 kernel, and will let QA to do thoroughly tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990330/+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 1990242] Re: Intel graphic driver is not probing[8086:468b]
** Merge proposal linked: https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800 ** Merge proposal linked: https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1990242 Title: Intel graphic driver is not probing[8086:468b] Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Got blank screen after entered desktop [Fix] Below commit in linux-next fixes the issue. 6215a7c8f552 drm/i915: Add new ADL-S pci id [Test] Verified on the target machine. [Where problems could occur] It only adds an ID to the list, should be pretty safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990242/+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 1989046] Re: support independent clock and LED GPIOs for Intel IPU6 platforms
** Merge proposal linked: https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800 ** Merge proposal linked: https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802 -- 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/1989046 Title: support independent clock and LED GPIOs for Intel IPU6 platforms Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] When migrated from power_ctrl_logic driver to int3472, two additional independent CLK/LED GPIOs other than powerdown/reset must be probed exceptionally. [Fix] Vendor provided patch in https://github.com/intel/ipu6-drivers/blob/2b8a592dc63e117d8f5af5f32a10d7e0651832d2/patch/int3472-support-independent-clock-and-LED-gpios-5.17+.patch. [Test Case] Tested on both TGL/ADL platforms against nominated kernels. [Where problems could occur] This adds exceptional cases with fallbacks to the original function. No one else is affected. [Other Info] This is an essential part for switching from power_ctrl_logic based GPIO control mechanism to the generic, upstreamed int3472 driver. Affects all IPU6 platforms that are to run new IPU6 driver dump in 202208. == original bug report == Per https://github.com/intel/ipu6-drivers/commit/f771bd3cb9f324a393a75e068a039bd1f9611026 and https://github.com/intel/ipu6-drivers/commit/2b8a592dc63e117d8f5af5f32a10d7e0651832d2, additional fix for INT3472 is necessary to probe camera sensor GPIOs on Intel IPU6 platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989046/+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 1989647] Re: Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)
** Merge proposal linked: https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800 ** Merge proposal linked: https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1989647 Title: Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400) Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] There's possibility that system will hang and no video output of two external monitor with dGPU W6400 Monitor 1: ASUS ProArt PA238Q (FHD) Monitor 2: Dell P2415Q (4K) [Fix] Introduce the dmi quirk in amdgpu, and add dmi quirks to bypass the affected machine. [Test Case] Two ways to verify Method 1: 1. Cold boot with ASUS 2. Attach Dell monitor. ASUS is primary. 3. Switch display mode to single ASUS 4. Switch disaply mode back to Joing Displays. ASUS is primary Method 2: 1. Cold boot with two monitors. ASUS is primary 2. Unplug the DP cable of Dell monitor from DUT and wait for few seconds 3. Plug it back to DUT [Where problems could occur] Low, add a dmi quirk to bypass the target machine. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1989647/+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 1990240] Re: To support Intel Maple Ridge Thunderbolt [8086:1134]
** Merge proposal linked: https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800 ** Merge proposal linked: https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1990240 Title: To support Intel Maple Ridge Thunderbolt [8086:1134] Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] The TBT ID[8086:1134] the new project uses is not listed in the driver. [Fix] Intel submits this as we requested which is still in linux-next https://lore.kernel.org/linux-usb/20220908104320.3409720-1-gil.f...@intel.com/ [Where problems could occur] Adding only one ID, should be pretty safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990240/+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 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
** Merge proposal linked: https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800 ** Merge proposal linked: https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1988797 Title: pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non- Fatal), type=Transaction Layer, (Requester ID) Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Confirmed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: My kernel log periodically bursts with: [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.593393] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.598564] pcieport :00:1b.0:[20] UnsupReq (First) [10405.603829] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.614959] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.620296] pcieport :00:1b.0:[20] UnsupReq (First) [10405.625554] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.636495] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.641867] pcieport :00:1b.0:[20] UnsupReq (First) [10405.647169] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.658369] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.663803] pcieport :00:1b.0:[20] UnsupReq (First) [10405.669263] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.680699] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.686267] pcieport :00:1b.0:[20] UnsupReq (First) [10405.691759] pcieport :00:1b.0: AER: TLP Header: 3400 0152 This has happened even since I got the machine. It also happened with 5.15. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2477 F wireplumber /dev/snd/seq:dan2474 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 6 13:52:35 2022 InstallationDate: Installed on 2022-07-20 (47 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: Intel(R) Client Systems NUC12DCMi7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)
[Kernel-packages] [Bug 1990847] Re: Mobile broadband does not work after suspend on t460s with EM7455
** Description changed: - Mobile broadband does not work after suspend on Thinkpad t460s with built-in Sierra Wireless EM7455. - It switches constantly on and off then. The only solution to repair the situation is to go to Windows and switching on there. - After check in Settings > Mobile Broadband > Modem Details it looks like that after sleep the modem is not recognised any more. - --- + Mobile broadband does not work after suspend on Thinkpad t460s with built-in Sierra Wireless EM7455. It switches constantly on and off then (the icon). The only solution I see to repair the situation is to go to Windows and switching on there (reboot or shutdown does not help; didn't try hard reset). After check in Settings > Mobile Broadband > Modem Details it looks like that after sleep modem's sim is not recognised anymore i.e.: + - modem is recognised (Settings > Mobile Network > Modem Details >>> Device Details is populated correctly), but 'Modem Status' section in Modem Details window shows Carrier (nothing), Network Type: unknown, Signal Strenght: 0%, Network Status: Unknown) - that is of course with Mobile Network switch on. + Restarting Network Manager does not help. + + I don't know how to use cli to check sth. with modem. Also my report is + not filed about a specific source package so if someone know which + packages to point to it would be helpful. + + PS. This behavior is featured in in the net in different combinations + (lid, work only after suspend, and so on). + + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: x 1799 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: x 1799 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader - Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver - Bus 001 Device 007: ID 1199:9079 Sierra Wireless, Inc. EM7455 - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader + Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver + Bus 001 Device 007: ID 1199:9079 Sierra Wireless, Inc. EM7455 + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FAS0B000 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c5109461-1cbf-452e-b76d-a13b0e90ca86 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: - linux-restricted-modules-5.15.0-48-generic N/A - linux-backports-modules-5.15.0-48-generic N/A - linux-firmware 20220329.git681281e4-0ubuntu3.5 + linux-restricted-modules-5.15.0-48-generic N/A + linux-backports-modules-5.15.0-48-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy wayland-session Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/06/2022 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET88W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS0B000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN1CET88W(1.56):bd07/06/2022:br1.56:efr1.14:svnLENOVO:pn20FAS0B000:pvrThinkPadT460s:rvnLENOVO:rn20FAS0B000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS0B000 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO -- 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/1990847 Title: Mobile broadband does not work after suspend on t460s with EM7455 Status in linux package in Ubuntu: Confirmed Bug description: Mobile broadband does not work after suspend on Thinkpad t460s with built-in Sierra Wireless EM7455. It switches constantly on and off then (the icon). The only solution I see to repair the situation is to go to Windows and switching on there (reboot or shutdown does not help; didn't try hard reset). After check in Settings > Mobile Broadband > Modem Details it looks like that after sle
[Kernel-packages] [Bug 1991346] Re: ubuntu_bpf #143/p bpf_get_stack return R0 within range Did not run the program (not supported) cause call trace on 5.15 kernel
** Description changed: Issue caught by sut-scan, this is not a regression as we are suffering from another build issue in the past. + Spotted on Jammy 5.15.0-50-generic and can be found on variants. + Step to reproduce: 1. Build the ubuntu_bpf test 2. Run the following in tools/testing/selftests/bpf: $ sudo ./test_verifier 143 #143/p bpf_get_stack return R0 within range Did not run the program (not supported) OK Summary: 1 PASSED, 0 SKIPPED, 0 FAILED It will cause this call trace in dmesg: [ 107.750735] [ cut here ] [ 107.750739] trace type BPF program uses run-time allocation [ 107.750749] WARNING: CPU: 1 PID: 1429 at kernel/bpf/verifier.c:11449 check_map_prog_compatibility+0x231/0x2a0 [ 107.750755] Modules linked in: tls binfmt_misc nls_iso8859_1 input_leds serio_raw dm_multipath sch_fq_codel scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler msr drm efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd psmouse ixgbevf floppy [ 107.750782] CPU: 1 PID: 1429 Comm: test_verifier Not tainted 5.15.0-1021-aws #25-Ubuntu [ 107.750784] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 107.750786] RIP: 0010:check_map_prog_compatibility+0x231/0x2a0 [ 107.750788] Code: 50 3e 7f b7 4c 89 ef 41 be ea ff ff ff e8 47 d3 ff ff e9 e3 fe ff ff 48 c7 c7 c8 3c 7f b7 c6 05 98 41 fa 01 01 e8 f0 71 ab 00 <0f> 0b e9 0d ff ff ff 48 c7 c6 98 3d 7f b7 4c 89 ef 41 be ea ff ff [ 107.750790] RSP: 0018:af4900b8bb20 EFLAGS: 00010282 [ 107.750791] RAX: RBX: af490006d000 RCX: 0027 [ 107.750793] RDX: 989fabe60588 RSI: 0001 RDI: 989fabe60580 [ 107.750794] RBP: af4900b8bb48 R08: 0003 R09: fffc9738 [ 107.750795] R10: 0031 R11: 0001 R12: 989ec3bffc00 [ 107.750796] R13: 989ec4a4c000 R14: 0005 R15: [ 107.750798] FS: 7f46bb42() GS:989fabe4() knlGS: [ 107.750799] CS: 0010 DS: ES: CR0: 80050033 [ 107.750800] CR2: 55d91dc906fe CR3: 03a4c002 CR4: 001706e0 [ 107.750803] Call Trace: [ 107.750804] [ 107.750807] resolve_pseudo_ldimm64+0x134/0x5e0 [ 107.750810] bpf_check+0x690/0xf00 [ 107.750813] bpf_prog_load+0x4c8/0xb10 [ 107.750817] __sys_bpf+0x1af/0xe20 [ 107.750820] __x64_sys_bpf+0x1a/0x30 [ 107.750823] do_syscall_64+0x5c/0xc0 [ 107.750827] ? handle_mm_fault+0xd8/0x2c0 [ 107.750831] ? do_user_addr_fault+0x1e7/0x670 [ 107.750836] ? exit_to_user_mode_prepare+0x37/0xb0 [ 107.750840] ? irqentry_exit_to_user_mode+0x9/0x20 [ 107.750843] ? irqentry_exit+0x1d/0x30 [ 107.750845] ? exc_page_fault+0x89/0x170 [ 107.750847] entry_SYSCALL_64_after_hwframe+0x61/0xcb [ 107.750852] RIP: 0033:0x7f46bb53fa3d [ 107.750854] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 [ 107.750855] RSP: 002b:7ffc86ae6d08 EFLAGS: 0202 ORIG_RAX: 0141 [ 107.750857] RAX: ffda RBX: RCX: 7f46bb53fa3d [ 107.750858] RDX: 0080 RSI: 7ffc86ae6d90 RDI: 0005 [ 107.750859] RBP: 7ffc86ae6d20 R08: 7ffc86ae6c70 R09: 7ffc86ae6d90 [ 107.750860] R10: 7fff R11: 0202 R12: 7ffc86ae71b8 [ 107.750861] R13: 55d91dc721dd R14: 55d91dcdff38 R15: 7f46bb6d1040 [ 107.750864] [ 107.750865] ---[ end trace 2da671b5c0dfc28b ]--- ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) 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/1991346 Title: ubuntu_bpf #143/p bpf_get_stack return R0 within range Did not run the program (not supported) cause call trace on 5.15 kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: Issue caught by sut-scan, this is not a regression as we are suffering from another build issue in the past. Spotted on Jammy 5.15.0-50-generic and can be found on variants. Step to reproduce: 1. Build the ubuntu_bpf test 2. Run the following in tools/testing/selftests/bpf: $ sudo ./test_verifier 143 #143/p bpf_get_stack return R0 within range Did not run the program (not supported) OK Summary: 1 PASSED, 0 SKIP
[Kernel-packages] [Bug 1991346] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1991346 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) Status: New => 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/1991346 Title: ubuntu_bpf #143/p bpf_get_stack return R0 within range Did not run the program (not supported) cause call trace on 5.15 kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Issue caught by sut-scan, this is not a regression as we are suffering from another build issue in the past. Spotted on Jammy 5.15.0-50-generic and can be found on variants. Step to reproduce: 1. Build the ubuntu_bpf test 2. Run the following in tools/testing/selftests/bpf: $ sudo ./test_verifier 143 #143/p bpf_get_stack return R0 within range Did not run the program (not supported) OK Summary: 1 PASSED, 0 SKIPPED, 0 FAILED It will cause this call trace in dmesg: [ 107.750735] [ cut here ] [ 107.750739] trace type BPF program uses run-time allocation [ 107.750749] WARNING: CPU: 1 PID: 1429 at kernel/bpf/verifier.c:11449 check_map_prog_compatibility+0x231/0x2a0 [ 107.750755] Modules linked in: tls binfmt_misc nls_iso8859_1 input_leds serio_raw dm_multipath sch_fq_codel scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler msr drm efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd psmouse ixgbevf floppy [ 107.750782] CPU: 1 PID: 1429 Comm: test_verifier Not tainted 5.15.0-1021-aws #25-Ubuntu [ 107.750784] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 107.750786] RIP: 0010:check_map_prog_compatibility+0x231/0x2a0 [ 107.750788] Code: 50 3e 7f b7 4c 89 ef 41 be ea ff ff ff e8 47 d3 ff ff e9 e3 fe ff ff 48 c7 c7 c8 3c 7f b7 c6 05 98 41 fa 01 01 e8 f0 71 ab 00 <0f> 0b e9 0d ff ff ff 48 c7 c6 98 3d 7f b7 4c 89 ef 41 be ea ff ff [ 107.750790] RSP: 0018:af4900b8bb20 EFLAGS: 00010282 [ 107.750791] RAX: RBX: af490006d000 RCX: 0027 [ 107.750793] RDX: 989fabe60588 RSI: 0001 RDI: 989fabe60580 [ 107.750794] RBP: af4900b8bb48 R08: 0003 R09: fffc9738 [ 107.750795] R10: 0031 R11: 0001 R12: 989ec3bffc00 [ 107.750796] R13: 989ec4a4c000 R14: 0005 R15: [ 107.750798] FS: 7f46bb42() GS:989fabe4() knlGS: [ 107.750799] CS: 0010 DS: ES: CR0: 80050033 [ 107.750800] CR2: 55d91dc906fe CR3: 03a4c002 CR4: 001706e0 [ 107.750803] Call Trace: [ 107.750804] [ 107.750807] resolve_pseudo_ldimm64+0x134/0x5e0 [ 107.750810] bpf_check+0x690/0xf00 [ 107.750813] bpf_prog_load+0x4c8/0xb10 [ 107.750817] __sys_bpf+0x1af/0xe20 [ 107.750820] __x64_sys_bpf+0x1a/0x30 [ 107.750823] do_syscall_64+0x5c/0xc0 [ 107.750827] ? handle_mm_fault+0xd8/0x2c0 [ 107.750831] ? do_user_addr_fault+0x1e7/0x670 [ 107.750836] ? exit_to_user_mode_prepare+0x37/0xb0 [ 107.750840] ? irqentry_exit_to_user_mode+0x9/0x20 [ 107.750843] ? irqentry_exit+0x1d/0x30 [ 107.750845] ? exc_page_fault+0x89/0x170 [ 107.750847] entry_SYSCALL_64_after_hwframe+0x61/0xcb [ 107.750852] RIP: 0033:0x7f46bb53fa3d [ 107.750854] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 [ 107.750855] RSP: 002b:7ffc86ae6d08 EFLAGS: 0202 ORIG_RAX: 0141 [ 107.750857] RAX: ffda RBX: RCX: 7f46bb53fa3d [ 107.750858] RDX: 0080 RSI: 7ffc86ae6d90 RDI: 0005 [ 107.750859] RBP: 7ffc86ae6d20 R08: 7ffc86ae6c70 R09: 7ffc86ae6d90 [ 107.750860] R10: 7fff R11: 0202 R12: 7ffc86ae71b8 [ 107.750861] R13: 55d91dc721dd R14: 55d91dcdff38 R15: 7f46bb6d1040 [ 107.75086
[Kernel-packages] [Bug 1991346] Re: ubuntu_bpf #143/p bpf_get_stack return R0 within range Did not run the program (not supported) cause call trace on 5.15 kernel
Tested with the latest 5.15 mainline kernel 5.15.71-051571-generic, and this is still reproducible. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1991346 Title: ubuntu_bpf #143/p bpf_get_stack return R0 within range Did not run the program (not supported) cause call trace on 5.15 kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Bug description: Issue caught by sut-scan, this is not a regression as we are suffering from another build issue in the past. Spotted on Jammy 5.15.0-50-generic and can be found on variants. Step to reproduce: 1. Build the ubuntu_bpf test 2. Run the following in tools/testing/selftests/bpf: $ sudo ./test_verifier 143 #143/p bpf_get_stack return R0 within range Did not run the program (not supported) OK Summary: 1 PASSED, 0 SKIPPED, 0 FAILED It will cause this call trace in dmesg: [ 107.750735] [ cut here ] [ 107.750739] trace type BPF program uses run-time allocation [ 107.750749] WARNING: CPU: 1 PID: 1429 at kernel/bpf/verifier.c:11449 check_map_prog_compatibility+0x231/0x2a0 [ 107.750755] Modules linked in: tls binfmt_misc nls_iso8859_1 input_leds serio_raw dm_multipath sch_fq_codel scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler msr drm efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd psmouse ixgbevf floppy [ 107.750782] CPU: 1 PID: 1429 Comm: test_verifier Not tainted 5.15.0-1021-aws #25-Ubuntu [ 107.750784] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 107.750786] RIP: 0010:check_map_prog_compatibility+0x231/0x2a0 [ 107.750788] Code: 50 3e 7f b7 4c 89 ef 41 be ea ff ff ff e8 47 d3 ff ff e9 e3 fe ff ff 48 c7 c7 c8 3c 7f b7 c6 05 98 41 fa 01 01 e8 f0 71 ab 00 <0f> 0b e9 0d ff ff ff 48 c7 c6 98 3d 7f b7 4c 89 ef 41 be ea ff ff [ 107.750790] RSP: 0018:af4900b8bb20 EFLAGS: 00010282 [ 107.750791] RAX: RBX: af490006d000 RCX: 0027 [ 107.750793] RDX: 989fabe60588 RSI: 0001 RDI: 989fabe60580 [ 107.750794] RBP: af4900b8bb48 R08: 0003 R09: fffc9738 [ 107.750795] R10: 0031 R11: 0001 R12: 989ec3bffc00 [ 107.750796] R13: 989ec4a4c000 R14: 0005 R15: [ 107.750798] FS: 7f46bb42() GS:989fabe4() knlGS: [ 107.750799] CS: 0010 DS: ES: CR0: 80050033 [ 107.750800] CR2: 55d91dc906fe CR3: 03a4c002 CR4: 001706e0 [ 107.750803] Call Trace: [ 107.750804] [ 107.750807] resolve_pseudo_ldimm64+0x134/0x5e0 [ 107.750810] bpf_check+0x690/0xf00 [ 107.750813] bpf_prog_load+0x4c8/0xb10 [ 107.750817] __sys_bpf+0x1af/0xe20 [ 107.750820] __x64_sys_bpf+0x1a/0x30 [ 107.750823] do_syscall_64+0x5c/0xc0 [ 107.750827] ? handle_mm_fault+0xd8/0x2c0 [ 107.750831] ? do_user_addr_fault+0x1e7/0x670 [ 107.750836] ? exit_to_user_mode_prepare+0x37/0xb0 [ 107.750840] ? irqentry_exit_to_user_mode+0x9/0x20 [ 107.750843] ? irqentry_exit+0x1d/0x30 [ 107.750845] ? exc_page_fault+0x89/0x170 [ 107.750847] entry_SYSCALL_64_after_hwframe+0x61/0xcb [ 107.750852] RIP: 0033:0x7f46bb53fa3d [ 107.750854] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 [ 107.750855] RSP: 002b:7ffc86ae6d08 EFLAGS: 0202 ORIG_RAX: 0141 [ 107.750857] RAX: ffda RBX: RCX: 7f46bb53fa3d [ 107.750858] RDX: 0080 RSI: 7ffc86ae6d90 RDI: 0005 [ 107.750859] RBP: 7ffc86ae6d20 R08: 7ffc86ae6c70 R09: 7ffc86ae6d90 [ 107.750860] R10: 7fff R11: 0202 R12: 7ffc86ae71b8 [ 107.750861] R13: 55d91dc721dd R14: 55d91dcdff38 R15: 7f46bb6d1040 [ 107.750864] [ 107.750865] ---[ end trace 2da671b5c0dfc28b ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991346/+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 1988488] Re: Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
That change did not help, the display still did freeze. The content of /etc/environment was: PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin" MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 MUTTER_DEBUG_FORCE_KMS_MODE=simple The host OS is a minimal install of Ubuntu 22.04 LTS and for the VMs I use OpenZFS as storage. For these VMs the hardware is a 512GB Silicon Power nvme-SSD (3400/2300MB/s). -- 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/1988488 Title: Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel. Status in linux package in Ubuntu: Confirmed Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet 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=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988488/+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 1991215] Re: test_verifier in ubuntu_bpf failed with 40 test cases on Jammy 5.15 generic kernel
** Summary changed: - test_verifier in ubuntu_bpf failed with 40 test cases on Jammy + test_verifier in ubuntu_bpf failed with 40 test cases on Jammy 5.15 generic 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/1991215 Title: test_verifier in ubuntu_bpf failed with 40 test cases on Jammy 5.15 generic kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Bug description: With the bpf build issue fixed (bug 1980517) on Jammy, the ubuntu_bpf test can now be tested. There are 40 failures discovered in test_verifier: #21/u BPF_ATOMIC_AND without fetch FAIL #21/p BPF_ATOMIC_AND without fetch FAIL #22/u BPF_ATOMIC_AND with fetch FAIL #22/p BPF_ATOMIC_AND with fetch FAIL #23/u BPF_ATOMIC_AND with fetch 32bit FAIL #23/p BPF_ATOMIC_AND with fetch 32bit FAIL #24/u BPF_ATOMIC_AND with fetch - r0 as source reg FAIL #24/p BPF_ATOMIC_AND with fetch - r0 as source reg FAIL #25/p BPF_ATOMIC bounds propagation, mem->reg FAIL #26/u atomic compare-and-exchange smoketest - 64bit FAIL #26/p atomic compare-and-exchange smoketest - 64bit FAIL #27/u atomic compare-and-exchange smoketest - 32bit FAIL #27/p atomic compare-and-exchange smoketest - 32bit FAIL #30/u BPF_W cmpxchg should zero top 32 bits FAIL #30/p BPF_W cmpxchg should zero top 32 bits FAIL #31/p Dest pointer in r0 - succeed, check 2 FAIL #33/p Dest pointer in r0 - succeed, check 4 FAIL #35/u BPF_ATOMIC_FETCH_ADD smoketest - 64bit FAIL #35/p BPF_ATOMIC_FETCH_ADD smoketest - 64bit FAIL #36/u BPF_ATOMIC_FETCH_ADD smoketest - 32bit FAIL #36/p BPF_ATOMIC_FETCH_ADD smoketest - 32bit FAIL #41/u BPF_ATOMIC OR without fetch FAIL #41/p BPF_ATOMIC OR without fetch FAIL #42/u BPF_ATOMIC OR with fetch FAIL #42/p BPF_ATOMIC OR with fetch FAIL #43/u BPF_ATOMIC OR with fetch 32bit FAIL #43/p BPF_ATOMIC OR with fetch 32bit FAIL #44/u BPF_W atomic_fetch_or should zero top 32 bits FAIL #44/p BPF_W atomic_fetch_or should zero top 32 bits FAIL #45/u atomic exchange smoketest - 64bit FAIL #45/p atomic exchange smoketest - 64bit FAIL #46/u atomic exchange smoketest - 32bit FAIL #46/p atomic exchange smoketest - 32bit FAIL #47/u BPF_ATOMIC XOR without fetch FAIL #47/p BPF_ATOMIC XOR without fetch FAIL #48/u BPF_ATOMIC XOR with fetch FAIL #48/p BPF_ATOMIC XOR with fetch FAIL #49/u BPF_ATOMIC XOR with fetch 32bit FAIL #49/p BPF_ATOMIC XOR with fetch 32bit FAIL #150/p calls: trigger reg2btf_ids[reg->type] for reg->type > __BPF_REG_TYPE_MAX FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991215/+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 1988488] Re: Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
In the guest VM, what output do you get from: find /lib/modules -name vmwgfx.ko -- 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/1988488 Title: Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel. Status in linux package in Ubuntu: Confirmed Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet 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=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988488/+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 1988488] Re: Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
In the guest VM, what output do you get from: find /lib/modules -name vmwgfx.ko ? -- 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/1988488 Title: Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel. Status in linux package in Ubuntu: Confirmed Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet 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=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988488/+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 1991215] Re: test_verifier in ubuntu_bpf failed with 40 test cases on Jammy 5.15 generic kernel / J-5.15 oracle
For AWS / Azure / GCP / GKE, they are just failing with 3 failures: #27/u atomic compare-and-exchange smoketest - 32bit FAIL #30/u BPF_W cmpxchg should zero top 32 bits FAIL #150/p calls: trigger reg2btf_ids[reg->type] for reg->type > __BPF_REG_TYPE_MAX FAIL Please refer to bug 1991351 ** Summary changed: - test_verifier in ubuntu_bpf failed with 40 test cases on Jammy 5.15 generic kernel + test_verifier in ubuntu_bpf failed with 40 test cases on Jammy 5.15 generic kernel / J-5.15 oracle ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oracle (Ubuntu) Status: New => Invalid -- 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/1991215 Title: test_verifier in ubuntu_bpf failed with 40 test cases on Jammy 5.15 generic kernel / J-5.15 oracle Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oracle source package in Jammy: New Bug description: With the bpf build issue fixed (bug 1980517) on Jammy, the ubuntu_bpf test can now be tested. There are 40 failures discovered in test_verifier: #21/u BPF_ATOMIC_AND without fetch FAIL #21/p BPF_ATOMIC_AND without fetch FAIL #22/u BPF_ATOMIC_AND with fetch FAIL #22/p BPF_ATOMIC_AND with fetch FAIL #23/u BPF_ATOMIC_AND with fetch 32bit FAIL #23/p BPF_ATOMIC_AND with fetch 32bit FAIL #24/u BPF_ATOMIC_AND with fetch - r0 as source reg FAIL #24/p BPF_ATOMIC_AND with fetch - r0 as source reg FAIL #25/p BPF_ATOMIC bounds propagation, mem->reg FAIL #26/u atomic compare-and-exchange smoketest - 64bit FAIL #26/p atomic compare-and-exchange smoketest - 64bit FAIL #27/u atomic compare-and-exchange smoketest - 32bit FAIL #27/p atomic compare-and-exchange smoketest - 32bit FAIL #30/u BPF_W cmpxchg should zero top 32 bits FAIL #30/p BPF_W cmpxchg should zero top 32 bits FAIL #31/p Dest pointer in r0 - succeed, check 2 FAIL #33/p Dest pointer in r0 - succeed, check 4 FAIL #35/u BPF_ATOMIC_FETCH_ADD smoketest - 64bit FAIL #35/p BPF_ATOMIC_FETCH_ADD smoketest - 64bit FAIL #36/u BPF_ATOMIC_FETCH_ADD smoketest - 32bit FAIL #36/p BPF_ATOMIC_FETCH_ADD smoketest - 32bit FAIL #41/u BPF_ATOMIC OR without fetch FAIL #41/p BPF_ATOMIC OR without fetch FAIL #42/u BPF_ATOMIC OR with fetch FAIL #42/p BPF_ATOMIC OR with fetch FAIL #43/u BPF_ATOMIC OR with fetch 32bit FAIL #43/p BPF_ATOMIC OR with fetch 32bit FAIL #44/u BPF_W atomic_fetch_or should zero top 32 bits FAIL #44/p BPF_W atomic_fetch_or should zero top 32 bits FAIL #45/u atomic exchange smoketest - 64bit FAIL #45/p atomic exchange smoketest - 64bit FAIL #46/u atomic exchange smoketest - 32bit FAIL #46/p atomic exchange smoketest - 32bit FAIL #47/u BPF_ATOMIC XOR without fetch FAIL #47/p BPF_ATOMIC XOR without fetch FAIL #48/u BPF_ATOMIC XOR with fetch FAIL #48/p BPF_ATOMIC XOR with fetch FAIL #49/u BPF_ATOMIC XOR with fetch 32bit FAIL #49/p BPF_ATOMIC XOR with fetch 32bit FAIL #150/p calls: trigger reg2btf_ids[reg->type] for reg->type > __BPF_REG_TYPE_MAX FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991215/+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
