[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.4.0.1113.106)
All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1113.106) for focal have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64) v4l2loopback/0.12.3-1ubuntu0.4 (amd64) 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/focal/update_excuses.html#linux-meta-azure [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 packaging 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 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled
This bug is awaiting verification that the linux-aws/5.4.0-1107.115 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! ** Tags added: kernel-spammed-focal-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023220 Title: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Trusty: Incomplete Status in linux-oem-6.1 source package in Trusty: Invalid Status in linux source package in Xenial: Incomplete Status in linux-oem-6.1 source package in Xenial: Invalid Status in linux source package in Bionic: Incomplete Status in linux-oem-6.1 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush the global TLB entries. This can lead to info leak or undefined behavior. [Mitigation] Boot with nopcid on affected systems. [Test case] There is no particular test case. [Potential regressions] This affects performance on the affected systems. TLB behavior could also be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+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 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt
This bug is awaiting verification that the linux-aws/5.4.0-1107.115 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! ** Tags added: kernel-spammed-focal-linux-aws -- 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/2023577 Title: cls_flower: off-by-one in fl_set_geneve_opt Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] An unprivileged user may cause an out-of-bounds write by setting up geneve options on the flower classifier. [Test case] https://seclists.org/oss-sec/2023/q2/219 [Potential regression] Users setting up geneve options on the flower tc classifier can be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023577/+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 2027914] Re: missing nvidia kernel module for generic kernel (linux-objects-nvidia-535-6.2.0-25-generic)
Hello Florian, This is interesting. I went from nvidia-525 to nvidia-535 and back to nvidia-525 and noticed that DKMS got installed as a separate package and cannot be removed (https://packages.ubuntu.com/lunar-updates/dkms). DKMS was not installed as a separate package initially on my system (before I went from nvidia-525 to nvidia-535, and probably at the time I was using an older kernel). So maybe the issue you are pointing is the reason for DKMS getting installed. Is there any downside to installing DKMS as a separate package? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2027914 Title: missing nvidia kernel module for generic kernel (linux-objects- nvidia-535-6.2.0-25-generic) Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: For latest generic kernel for Ubuntu 23.04 there in no package of kernel module. Present is for previous kernel: # aptitude search linux-objects-nvidia-535.*generic i A linux-objects-nvidia-535-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-open-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-open-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) There is no package for 6.2.0-25 kernel. So after upgrade to new kernel - gpu isn't working, as the module is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2027914/+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 2026592] Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on P9
I can see this issue on P8 node "dryden" with F-hwe-5.15 (5.15.0-78.85~20.04.1) # [15] Generic dynamic event - check if duplicate events are caught [FAIL] ** Tags added: 5.15 5.19 6.2 jammy kinetic lunar ubuntu-kernel-selftests -- 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/2026592 Title: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on P9 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Status in linux source package in Lunar: New Bug description: Issue found on: - Jammy 5.15.0-36.37 with Power9 baltar - Kinetic 5.19.0-47.49 with Power9 baltar - Lunar 6.2.0-25.25 with Power9 baltar Test failed with: # [15] Generic dynamic event - check if duplicate events are caught [FAIL] Test Log: make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' TAP version 13 1..1 # selftests: ftrace: ftracetest # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers [PASS] # [3] Basic trace clock test [PASS] # [4] Basic event tracing check [PASS] # [5] Change the ringbuffer size [PASS] # [6] Snapshot and tracing setting [PASS] # [7] trace_pipe and trace_marker [PASS] # [8] Test ftrace direct functions against tracers [UNRESOLVED] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] # [10] Generic dynamic event - add/remove eprobe events [PASS] # [11] Generic dynamic event - add/remove kprobe events [PASS] # [12] Generic dynamic event - add/remove synthetic events [PASS] # [13] Generic dynamic event - selective clear (compatibility) [PASS] # [14] Generic dynamic event - generic clear event [PASS] # [15] Generic dynamic event - check if duplicate events are caught [FAIL] # [16] event tracing - enable/disable with event level files [PASS] # [17] event tracing - restricts events based on pid notrace filtering [PASS] # [18] event tracing - restricts events based on pid [PASS] # [19] event tracing - enable/disable with subsystem level files [PASS] # [20] event tracing - enable/disable with top level files [PASS] # [21] Test trace_printk from module [PASS] # [22] ftrace - function graph filters with stack tracer [PASS] # [23] ftrace - function graph filters [PASS] # [24] ftrace - function pid notrace filters [PASS] # [25] ftrace - function pid filters [PASS] # [26] ftrace - stacktrace filter command [PASS] # [27] ftrace - function trace with cpumask [PASS] # [28] ftrace - test for function event triggers [PASS] # [29] ftrace - function trace on module [PASS] # [30] ftrace - function profiling [PASS] # [31] ftrace - function profiler with function tracing [PASS] # [32] ftrace - test reading of set_ftrace_filter [PASS] # [33] ftrace - test for function traceon/off triggers [PASS] # [34] ftrace - test tracing error log support [PASS] # [35] Test creation and deletion of trace instances while setting an event [PASS] # [36] Test creation and deletion of trace instances [PASS] # [37] Kprobe dynamic event - adding and removing [PASS] # [38] Kprobe dynamic event - busy event check [PASS] # [39] Kprobe dynamic event with arguments [PASS] # [40] Kprobe event with comm arguments [PASS] # [41] Kprobe event string type argument [PASS] # [42] Kprobe event symbol argument [PASS] # [43] Kprobe event argument syntax [PASS] # [44] Kprobes event arguments with types [PASS] # [45] Kprobe event user-memory access [UNSUPPORTED] # [46] Kprobe event auto/manual naming [PASS] # [47] Kprobe dynamic event with function tracer [PASS] # [48] Create/delete multiprobe on kprobe event [PASS] # [49] Kprobe event parser error log check [PASS] # [50] Kretprobe dynamic event with arguments [PASS] # [51] Kretprobe dynamic event with maxactive [PASS] # [52] Kretprobe %return suffix test [PASS] # [53] Register/unregister many kprobe events [PASS] # [54] Kprobe profile [PASS] # [55] Uprobe event parser error log check [PASS] # [56] test for the preemptirqsoff tracer [UNSUPPORTED] # [57] Meta-selftest: Checkbashisms [PASS] # [58] Test wakeup tracer [PASS] # [59] Test wakeup RT tracer [PASS] # [60] event trigger - test inter-event histogram trigger expected fail actions [XFAIL] # [61] event trigger - test field variable support [PASS] # [62] event trigger - test multiple actions on hist trigger [PASS] # [63] event trigger - test inter-event histogram trigger onchange action [PASS] # [64] event trigger - test inter-event histogram trigger onmatch action [PASS] # [65] event trigger - test inter-event histogram trigger onmatch-onmax action [PASS] #
[Kernel-packages] [Bug 2028322] Re: Enable Palo Alto Global Protect (PAGP) with SAML authentication working on the Ubuntu desktop supported via 20.04 LTS.
*** This bug is a duplicate of bug 2026771 *** https://bugs.launchpad.net/bugs/2026771 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028322 Title: Enable Palo Alto Global Protect (PAGP) with SAML authentication working on the Ubuntu desktop supported via 20.04 LTS. Status in intel: New Status in linux package in Ubuntu: New Bug description: 1. Feature Overview: Enable Palo Alto Global Protect (PAGP) with SAML authentication working on the Ubuntu desktop supported via 20.04 LTS. We propose 2 options: Option 1: Provide a backport of the OpenConnect and NetworkManager- OpenConnect packages from the Ubuntu Daily Build to Ubuntu 20.04 that will allow PAGP SAML authentication to work (it works in the current daily build for 23.10). OpenConnect version: v9.12-1 NetworkManager-OpenConnect version: 1.2.10-1 Option 2 (Preferred Option): Provide a backport of the 'gp-saml-gui' package which will allow PAGP SAML authentication to work (the current daily build for 23.10 will need to be updated first). gp-saml-gui minimum required version: 0.0~git20230417-1 gp-saml-gui current version (Ubuntu 23.10 daily build): 0.0~git20220831-1 2. Hardware: All 3. Upstream acceptance information: N/A 4. External links: N/A RDC Document #: N/A 5. Ubuntu Target: Ubuntu 20.04 LTS (Focal) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2028322/+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 2028320] Re: Enable Palo Alto Global Protect (PAGP) with SAML authentication working via NetworkManager on the Ubuntu desktop supported via 22.04 LTS.
*** This bug is a duplicate of bug 2026771 *** https://bugs.launchpad.net/bugs/2026771 ** Also affects: ubuntu Importance: Undecided Status: New ** No longer affects: ubuntu ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028320 Title: Enable Palo Alto Global Protect (PAGP) with SAML authentication working via NetworkManager on the Ubuntu desktop supported via 22.04 LTS. Status in intel: New Status in linux package in Ubuntu: New Bug description: 1. Feature Overview: Enable Palo Alto Global Protect (PAGP) with SAML authentication working via NetworkManager on the Ubuntu desktop supported via 22.04 LTS. Provide a backport of the OpenConnect and NetworkManager-OpenConnect packages from the Ubuntu Daily Build to Ubuntu 22.04 that will allow PAGP SAML authentication to work (it works in the current daily build for 23.10). OpenConnect version: v9.12-1 NetworkManager-OpenConnect version: 1.2.10-1 2. Hardware: All 3. Upstream acceptance information: N/A 4. External links: N/A RDC Document #: N/A 5. Ubuntu Target: Ubuntu 22.04 LTS (Jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2028320/+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 2020606] Re: net: openvswitch: fix race on port output
This bug is awaiting verification that the linux-bluefield/5.4.0-1068.74
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!
** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-focal
--
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/2020606
Title:
net: openvswitch: fix race on port output
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:
fix race on port output
* Explain the bug(s)
there is a race condition on port output
* brief explanation of fixes
We found that upstream linux has the same issue and fix
commit 066b86787fa3d97b7aefb5ac0a99a22dad2d15f8
Author: Felix Huettner
Date: Wed Apr 5 07:53:41 2023 +
net: openvswitch: fix race on port output
assume the following setup on a single machine:
1. An openvswitch instance with one bridge and default flows
2. two network namespaces "server" and "client"
3. two ovs interfaces "server" and "client" on the bridge
4. for each ovs interface a veth pair with a matching name and 32 rx and
tx queues
5. move the ends of the veth pairs to the respective network namespaces
6. assign ip addresses to each of the veth ends in the namespaces (needs
to be the same subnet)
7. start some http server on the server network namespace
8. test if a client in the client namespace can reach the http server
...
Fixes: 7f8a436eaa2c ("openvswitch: Add conntrack action")
Co-developed-by: Luca Czesla
Signed-off-by: Luca Czesla
Signed-off-by: Felix Huettner
Reviewed-by: Eric Dumazet
Reviewed-by: Simon Horman
Link: https://lore.kernel.org/r/ZC0pBXBAgh7c76CA@kernel-bug-kernel-bug
Signed-off-by: Jakub Kicinski
* How to test
After configuring QoS on BF-3:
Disable all priorities
Set priorities [0, 0, 0, 0, 0, 0, 0, 0]
Remove all policies
Remove all traffic classes
Add policy (policy_name=ND_traffic, traffic_type=RDMA, priority=5,
port=2, dscp=None)
Add policy (policy_name=TCP_traffic, traffic_type=TCP, priority=4,
port=26000, dscp=None)
Add traffic class two prio TC with prio_list=[5, 4], min_bw=76, algorithm=ETS
Enable QOS on adapter SLOT 5 Port 1
Restart driver (detach VFs -> restart with devcon -> attach VFs)
BF-3 sometimes stops responding. need to run it multiple times!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2020606/+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 2013383] Re: mlxbf-bootctl: support SMC call for setting ARM boot state
This bug is awaiting verification that the linux-bluefield/5.4.0-1068.74 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! ** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-focal -- 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/2013383 Title: mlxbf-bootctl: support SMC call for setting ARM boot state 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] Add a new SMC call which allows setting the ARM boot progress state to "OS is up". [Fix] * Add a new SMC call in mlxbf-bootctl which allows setting the ARM boot progress state to "OS is up". [Test Case] * Check that /sys/devices/platform/MLNXBF04:00/driver/os_up exists [Regression Potential] * No known regression because it is just adding a sysfs entry. It is backward compatible with older TAF images. If the SMC call is not supported by ATF, it is ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2013383/+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 2016039] Re: mlxbf-tmfifo: fix potential race
This bug is awaiting verification that the linux-bluefield/5.4.0-1068.74 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! ** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-focal -- 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/2016039 Title: mlxbf-tmfifo: fix potential race 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] This change is needed to avoid potential race of accessing the 'vq' pointer [Fix] The fix adds memory barrier for the is_ready flag and the 'vq' pointer access in mlxbf_tmfifo_virtio_find_vqs(), so updated in vq will be visible before accessing this pointer. [Test Case] Same functionality and testing as on BlueField-1/2/2. No functionality change. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2016039/+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 2021749] Re: mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors
This bug is awaiting verification that the linux-bluefield/5.4.0-1068.74 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! ** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-focal -- 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/2021749 Title: mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors 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] This change is needed to avoid potential tmfifo console stuck when network interface is down or receiving oversized packets. [Fix] Drop the Rx packets in the above cases. Since tmfifo is shared resource for both console and networking. Dropping such network packets can continue to process the fifo and avoid console stuck. [Test Case] Same functionality and testing as on BlueField-1/2/3. No functionality change. Add negative tests: 1. 'ifconfig tmfifo_net0 down' on ARM side during traffic, then verify rshim console doesn't stuck. 2. Config MTU to 4000 on rshim host and send oversized packet with command 'ping 192.168.100.2 -s 2000". It shouldn't cause any stuck. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2021749/+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 2022387] Re: mlxbf-gige: Fix intermittent no ip issue
This bug is awaiting verification that the linux-bluefield/5.4.0-1068.74 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! ** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-focal -- 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/2022387 Title: mlxbf-gige: Fix intermittent no ip issue Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] Although the link is up, and the PHY interrupt is cleared, there is no ip assigned. Nothing is being transmitted, and nothing is received. The RX error count keeps on increasing (check ifconfig oob_net0). After several minutes, the RX error count stagnates and the oob finally gets an ip and is pingable. [Fix] The issue is in the mlxbf_gige_rx_init function. As soon as the RX DMA is enabled, the RX CI reaches the max 128, it becomes equal to RX PI. And RX CI doesn't decrease since the code hasn't ran phy_start yet. The solution is to move the rx init after phy_start. [Test Case] * Check if the gige driver is loaded * Check that the oob_net0 interface is up and pingable from an external host * Do at ~1000 resets and powercycles and check the oon_net0 interface again [Regression Potential] * No known regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2022387/+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 2022370] Re: mlxbf-gige: Fix kernel panic at shutdown
This bug is awaiting verification that the linux-bluefield/5.4.0-1068.74 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! ** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-focal -- 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/2022370 Title: mlxbf-gige: Fix kernel panic at shutdown 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] We occasionally see a race condition (once every 350 reboots) where napi is still running (mlxbf_gige_poll) while a shutdown has been initiated through "reboot". Since mlxbf_gige_poll is still running, it tries to access a NULL pointer and as a result causes a kernel panic. [Fix] The fix is to explicitly disable napi and dequeue it during shutdown. mlxbf_gige_remove already calls: unregister_netdev->unregister_netdevice->unregister_netdev_queue-> rollback_registered->rollback_registered_many->dev_close_many-> __dev_close_many->ndo_stop->mlxbf_gige_stop which stops napi So use mlxbf_gige_remove in place of the existing shutdown logic. [Test Case] * Issue at least 1000 reboots from linux and make sure there is no panic caused by the mlxbf-gige driver. [Regression Potential] * since this issue is hard to reproduce, it hasn't been tested thoroughly yet. so it needs several reboot loops to validate it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2022370/+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 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled
This bug is awaiting verification that the linux-azure/5.4.0-1113.119 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! ** Tags removed: verification-done-focal ** Tags added: kernel-spammed-focal-linux-azure verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023220 Title: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Trusty: Incomplete Status in linux-oem-6.1 source package in Trusty: Invalid Status in linux source package in Xenial: Incomplete Status in linux-oem-6.1 source package in Xenial: Invalid Status in linux source package in Bionic: Incomplete Status in linux-oem-6.1 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush the global TLB entries. This can lead to info leak or undefined behavior. [Mitigation] Boot with nopcid on affected systems. [Test case] There is no particular test case. [Potential regressions] This affects performance on the affected systems. TLB behavior could also be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+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 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt
This bug is awaiting verification that the linux-azure/5.4.0-1113.119 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! ** Tags removed: verification-done-focal ** Tags added: kernel-spammed-focal-linux-azure verification-needed-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/2023577 Title: cls_flower: off-by-one in fl_set_geneve_opt Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] An unprivileged user may cause an out-of-bounds write by setting up geneve options on the flower classifier. [Test case] https://seclists.org/oss-sec/2023/q2/219 [Potential regression] Users setting up geneve options on the flower tc classifier can be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023577/+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 2023594] Re: Case [Azure] Fix VM crash/hang issues due to fast VF add/remove events
This bug is awaiting verification that the linux-azure/5.4.0-1113.119 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! ** Tags added: kernel-spammed-focal-linux-azure verification-needed-focal -- 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/2023594 Title: Case [Azure] Fix VM crash/hang issues due to fast VF add/remove events Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] A Linux guest on Hyper-V/Azure can occasionally crash during early Linux kernel boot due to a strange host behavior: 1. The host assigns a VF to the guest; 2. The host immediately unassigns the VF from the guest; //Dexuan: due to some race conditions bug in Linux vPCI driver, Linux can crash. 3. The host assigns the VF to the guest again. Starting late 2022 (around Nov 2022), Linux guests on Azure started to crash more frequently due to a host side update at that time: a new host/hypervisor feature of handling "correctable memory errors" can cause a lot of successive VF remove/add events, so the race conditions bug in Linux vPCI driver can surface much more easily. The Hyper-V team is implementing a batching mechanism so that the guest will get much less VF remove/add events (ETA: June 2023), but meanwhile we should also get the Linux race condition bugs fixed so that Linux guests won't crash even if it receives the successive VF remove/add events. [Test Plan] Microsoft tested [Regression potential] PCI devices may not get registered, or VMs may crash. [Other Info] SF: #00349076 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2023594/+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 2023695] Re: [Azure][MANA][VLANTagging] Support for VLAN Tagging for MANA
This bug is awaiting verification that the linux-azure/5.4.0-1113.119 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! ** Tags added: kernel-spammed-focal-linux-azure verification-needed-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/2023695 Title: [Azure][MANA][VLANTagging] Support for VLAN Tagging for MANA Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] This request is from MSFT LSG team to backport the MANA VLAN Tagging Support, the patch have been accepted upstream in and in the Linux next tree. https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b803d1fded40 [Test Plan] MSFT tested [Regression potential] Non-VLAN packets could be misclassified. [Other Info] SF: #00362474 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023695/+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 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader
$ cat /var/log/installer/media-info Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) -- 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/2027847 Title: Bump minimum /boot size in ubuntu-release-upgrader Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+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 2028309] [NEW] mlxbf-bootctl: Fix kernel panic due to buffer overflow
Public bug reported: SRU Justification: [Impact] Running the following LTP (linux-test-project) script, causes a kernel panic and a reboot of the DPU: ltp/testcases/bin/read_all -d /sys -q -r 10 The above test reads all directory and files under /sys. Reading the sysfs entry "large_icm" causes the kernel panic due to a garbage value returned via i2c read. That garbage value causes a buffer overflow in sprintf. [Fix] * Replace sprintf with snprintf. And also add missing lock and increase the buffer size to PAGE_SIZE. [Test Case] * Run from linux: ltp/testcases/bin/read_all -d /sys -q -r 10 [Regression Potential] no known regression ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- 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/2028309 Title: mlxbf-bootctl: Fix kernel panic due to buffer overflow Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Running the following LTP (linux-test-project) script, causes a kernel panic and a reboot of the DPU: ltp/testcases/bin/read_all -d /sys -q -r 10 The above test reads all directory and files under /sys. Reading the sysfs entry "large_icm" causes the kernel panic due to a garbage value returned via i2c read. That garbage value causes a buffer overflow in sprintf. [Fix] * Replace sprintf with snprintf. And also add missing lock and increase the buffer size to PAGE_SIZE. [Test Case] * Run from linux: ltp/testcases/bin/read_all -d /sys -q -r 10 [Regression Potential] no known regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2028309/+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 2009142] Re: nvidia-dkms-390 FTBS with linux 6.2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2009142 Title: nvidia-dkms-390 FTBS with linux 6.2 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-390 source package in Lunar: Fix Released Bug description: [Impact] nvidia-dkms-390 fails to build with linux 6.2: /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:244:21: error: ‘struct drm_mode_config’ has no member named ‘fb_base’ 244 | dev->mode_config.fb_base = 0; | ^ [Fix] Change the driver to support also the 6.2 kernel ABI. [Test case] With linux 6.2 installed, run: $ sudo apt install nvidia-dkms-390 [Regression potential] We may experience regressions in newer kernels (>= 6.2) that are using nvidia-dkms-390 (source code for previous kernels remain unchanged). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009142/+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 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader
You can confirm the release you originally installed on the system by looking at /var/log/installer/media-info. An example: $ cat /var/log/installer/media-info Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) -- 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/2027847 Title: Bump minimum /boot size in ubuntu-release-upgrader Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+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 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader
The purpose of the size check in u-r-u is to ensure that we don't fail mid-upgrade due to lack of disk space on /boot. But AIUI that's not what happened here to the bug submitter; this is an upgrade within an Ubuntu series between individual kernel packages. We should NOT have a check in u-r-u that refuses upgrades when /boot is less than the "ideal" size, only when we expect with a reasonable degree of confidence that /boot is too small to let the upgrade proceed. -- 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/2027847 Title: Bump minimum /boot size in ubuntu-release-upgrader Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+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 1853306] Re: [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part
--- Comment From mjros...@us.ibm.com 2023-07-20 13:50 EDT--- Verification of this kernel feature is complete. All tests were run using the kernel in jammy-proposed (5.15.0-79-generic #86-Ubuntu) on the host as well as in the KVM guest (except where otherwise noted, see below). Because the necessary qemu changes are not yet in jammy-proposed, I used a custom qemu build based on the launchpad qemu repository + applied the QEMU feature backport. I will do a second verification of the QEMU feature once that package is available. As for the testing itself: NVMe and RoCE testing went just as expected. During ISM testing, I did run into one issue that is not caused by this feature (therefore I am marking verification complete) but it is something that will need to be fixed separately once an upstream patch is available. Specifically, when using the jammy-proposed kernel in the KVM guest I noted occasional UBSAN array-index-out-of-bounds warnings from net/smc/af_smc.c -- This is not directly due to the code added by this feature or even due to being run in a KVM guest, but rather a bug in net/smc code (specifically the SMC_STAT_PAYLOAD_SUB macro) that is much more obvious when ubsan is enabled. I've already identified the root cause, verified that it also exists upstream, and reported the issue to the SMC maintainers along with a suggested fix - without UBSAN enabled no warning is issued but an incorrect performance status counter is quietly incremented. I had panic_on_warn enabled in the KVM guest, therefore the warning caused the guest to crash; otherwise I likely would not have noticed this issue at all. In order to complete all verification tests related to ISM devices, I proceeded with 2 different KVM guest kernel configurations and ran all ISM tests using both: 1) a custom built (upstream 6.4.0) guest kernel that did not include UBSAN 2) the jammy-proposed kernel that includes UBSAN but with panic_on_warn=0 All test scenarios passed with these guest kernels. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853306 Title: [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [ Impact ] * Currently the PCI passthrough implementation for s390x is based on intercepting PCI I/O instructions, which leads to a reduced I/O performance compared to the execution of PCI instructions directly in LPAR. * Hence users may face I/O bottlenecks when using PCI devices in passthrough mode based on the current implementation. * For avoiding this and to improve performance, the interpretive execution of the PCI store and PCI load instructions get enabled. * A further improvement is achieved by enabling the Adapter-Event-Notification Interpretation (AENI). * Since LTS releases are the main focus for stable and long running KVM workloads, it is highly desired to get this backported to the jammy kernel (and because the next LTS is still some time away). [ Test Plan ] * Hardware used: z14 or greater LPAR, PCI-attached devices (RoCE VFs, ISM devices, NVMe drive) * Setup: Both the kernel and QEMU features are needed for the feature to function (an upstream QEMU can be used to verify the kernel early), and the facility is only avaialble on z14 or newer. When any of those pieces is missing, the interpretation facility will not be used. When both the kernel and QEMU features are included in their respective packages, and running in an LPAR on a z14 or newer machine, this feature will be enabled automatically. Existing supported devices should behave as before with no changes required by an end-user (e.g. no changes to libvirt domain definitions) -- but will now make use of the interpretation facility. Additionally, ISM devices will now be eligible for vfio-pci passthrough (where before QEMU would exit on error if attempting to provide an ISM device for vfio-pci passthrough, preventing the guest from starting) * Testing will include the following scenarios, repeated each for RoCE, ISM and NVMe: 1) Testing of basic device passthrough (create a VM with a vfio-pci device as part of the libvirt domain definition, passing through a RoCE VF, an ISM device, or an NVMe drive. Verify that the device is available in the guest and functioning) 2) Testing of device hotplug/unplug (create a VM with a vfio-pci
[Kernel-packages] [Bug 2024427] Re: potential S3 issue for amdgpu Navi 31/Navi33
** Tags removed: verification-failed-jammy ** Tags added: verification-done-jammy -- 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/2024427 Title: potential S3 issue for amdgpu Navi 31/Navi33 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Triaged Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2024427 [Impact] Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms will sometimes fail to wake from S3. [Fix] kernel patches: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 firmware patches: * Navi31: ffe1a41e2ddb amdgpu: update GC 11.0.0 firmware for amd.5.5 release * Navi33: a5d7b4df1a76 amdgpu: update GC 11.0.2 firmware for amd.5.5 release [Test Case] $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Little we know about the firmware fixes. However, while with these commits have been pulled via stable kernel fixes, the driver begins to request new firmware blobs of a different filename. [Other Info] The kernel driver commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. Only linux/lunar has to be fixed. For the firmware parts, they have been included in linux-firmware/mantic, leaving linux-firmware/lunar and linux-firmware/jammy to be fixed. == original bug report == amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024427/+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 2024774] Re: AMD Rembrandt / Phoenix PSR-SU related freezes
** Tags added: verification-done-jammy
--
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/2024774
Title:
AMD Rembrandt / Phoenix PSR-SU related freezes
Status in Linux Firmware:
Fix Released
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 Lunar:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Released
Bug description:
[ Impact ]
When using kernel 6.2 or later AMD has enabled PSR selective update (PSR-SU).
After a non-deterministic amount of time the system may hang with a message
like this in the logs:
"[amdgpu :67:00.0: [drm] *ERROR* [CONNECTOR:78:eDP-1] commit wait timed
out]"
Affects users of laptops that contain:
* AMD Rembrandt (Yellow Carp) or AMD Phoenix (Pink Sardine) chips
* eDP panels with Parade TCONs (8-03 and 8-01 both reported to fail)
[ Test Plan ]
* Test an affected laptop with the newer firmware and ensure that PSR-SU
function can be enabled and system is stable.
* Ensure other functions such as hotplugging monitors and suspending
continue to work.
[ Where problems could occur ]
* Affected firmware only is loaded on Rembrandt and Phoenix laptops.
Problems would be localized to these machines.
[ Other Info ]
The minimum firmware needed to help these hangs:
* Rembrandt: 0x43a or later
* Phoenix: 0x8001000 or later
The following commit upgrades the firmware for Rembrandt
(amdgpu/yellow_carp_dmcub.bin) to 0x43c:
9dbd8ec2 ("amdgpu: DMCUB updates for various AMDGPU asics")
The following commit upgrades the firmware for Phoenix
(amdgpu/dcn_3_1_4_dmcub.bin) to 0x8001a00:
045b2136 ("amdgpu: update DMCUB to v0.0.172.0 for various AMDGPU ASICs")
The TCON in a given laptop can be identified from the DPCD with this script:
https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/psr.py
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2024774/+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 2027959] Re: Follow-up: potential S3 issue for amdgpu Navi 31/Navi33
Confirmed on a Phoenix laptop no longer see the fallback path with 6.1 1016-OEM kernel. marking verified. ** Tags added: verification-done-jammy -- 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/2027959 Title: Follow-up: potential S3 issue for amdgpu Navi 31/Navi33 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 Lunar: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Bug description: [SRU Justification] [Impact] Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms will sometimes fail to wake from S3. This is a follow-up to bug 2024427 to patch additional models. [Fix] firmware patches: * 60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release * 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release * 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 [Test Case] $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Little we know about the firmware fixes. However, while with these commits have been pulled via stable kernel fixes, the driver begins to request new firmware blobs of a different filename. [Other Info] For the firmware parts, they have been included in linux-firmware/mantic, leaving only linux-firmware/lunar and linux-firmware/jammy to be fixed. == original bug report == Per comment https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2024427/comments/15 from bug 2024427, more firmware blobs were requested to be pulled back to linux-firmware/lunar and jammy. They are: * ffe1a41e2 amdgpu: update GC 11.0.0 firmware for amd.5.5 release (already pulled in bug 2024427) * a5d7b4df1 amdgpu: update GC 11.0.2 firmware for amd.5.5 release (already pulled in bug 2024427) * 60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release * 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release * 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2027959/+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 1940080] Re: ubuntu-kernel-selftests.ftrace hangs on riscv64
** Merge proposal linked: https://code.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/+merge/446847 ** Merge proposal linked: https://code.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/+merge/447331 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1940080 Title: ubuntu-kernel-selftests.ftrace hangs on riscv64 Status in ubuntu-kernel-tests: New Status in linux-riscv package in Ubuntu: Confirmed Bug description: 08/12 22:10:03 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 08/12 22:10:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 08/12 22:10:45 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 08/12 22:10:51 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 08/12 22:10:56 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check[PASS] 08/12 22:11:01 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 08/12 22:11:06 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 08/12 22:11:11 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 08/12 22:11:15 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct functions against tracers [UNRESOLVED] 08/12 22:11:16 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct functions against kprobes [UNSUPPORTED] 08/12 22:11:20 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - add/remove kprobe events[FAIL] 08/12 22:11:21 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - add/remove synthetic events [UNSUPPORTED] 08/12 22:11:22 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event - selective clear (compatibility) [UNSUPPORTED] 08/12 22:11:22 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event - generic clear event [UNSUPPORTED] 08/12 22:11:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with event level files [PASS] 08/12 22:11:34 DEBUG| utils:0153| [stdout] # [15] event tracing - restricts events based on pid notrace filtering [PASS] 08/12 22:11:40 DEBUG| utils:0153| [stdout] # [16] event tracing - restricts events based on pid [PASS] 08/12 22:11:45 DEBUG| utils:0153| [stdout] # [17] event tracing - enable/disable with subsystem level files [PASS] 08/12 22:11:51 DEBUG| utils:0153| [stdout] # [18] event tracing - enable/disable with top level files [PASS] 08/12 22:11:58 DEBUG| utils:0153| [stdout] # [19] Test trace_printk from module [PASS] 08/12 22:12:15 DEBUG| utils:0153| [stdout] # [20] ftrace - function graph filters with stack tracer [PASS] 08/12 22:12:24 DEBUG| utils:0153| [stdout] # [21] ftrace - function graph filters [PASS] 08/12 22:12:35 DEBUG| utils:0153| [stdout] # [22] ftrace - function pid notrace filters [PASS] 08/12 22:12:46 DEBUG| utils:0153| [stdout] # [23] ftrace - function pid filters [PASS] 08/12 22:12:54 DEBUG| utils:0153| [stdout] # [24] ftrace - stacktrace filter command [PASS] 08/12 22:13:03 DEBUG| utils:0153| [stdout] # [25] ftrace - function trace with cpumask[PASS] 08/12 22:13:28 DEBUG| utils:0153| [stdout] # [26] ftrace - test for function event triggers [FAIL] 08/12 22:13:42 DEBUG| utils:0153| [stdout] # [27] ftrace - function trace on module [PASS] ** hang, whilst a lot more test cases are expected ** I.e. the next test case result should have been # [28] ftrace - function profiling Failure: # [10] Generic dynamic event - add/remove kprobe events [FAIL] # [26] ftrace - test for function event triggers [FAIL] nothing exciting in the dmesg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1940080/+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 2027914] Re: missing nvidia kernel module for generic kernel (linux-objects-nvidia-535-6.2.0-25-generic)
Another issue with the 6.2.0-25 kernel is in linux-modules-nvidia-525-generic: Provides: nvidia-dkms-525 (= 525.116.04-0ubuntu0.23.04.1), nvidia-prebuilt-kernel But nvidia-driver-525 Depends: nvidia-dkms-525 (>= 525.125.06) So the "dkms replacement" version provided by the pre-built modules package is too small. So it's currently impossible to install the nvidia-driver-525 package (I'm not sure if that package is strictly needed, it's probably just a metapackage to make updates work correctly) with the prebuilt modules. It will always try to get rid of the prebuild modules and install dkms instead. This has been going on for some time now. It looks like it might be correct in the -proposed packages, but I have only looked at the .deb file contents superficially. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2027914 Title: missing nvidia kernel module for generic kernel (linux-objects- nvidia-535-6.2.0-25-generic) Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: For latest generic kernel for Ubuntu 23.04 there in no package of kernel module. Present is for previous kernel: # aptitude search linux-objects-nvidia-535.*generic i A linux-objects-nvidia-535-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-open-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-open-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) There is no package for 6.2.0-25 kernel. So after upgrade to new kernel - gpu isn't working, as the module is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2027914/+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 2028267] Re: Apply additional patches to enable and resolve issues with the Orin platform
** Description changed: [Impact] - USB-C does not properly load firmware on a Jetson AGX devkit, and on all platforms the tegra-vic, tegra-nvdec, tegra-nvjpg, and tegra-nvenc modules fail to load. + USB-C does not properly load firmware on a Jetson AGX devkit, and on all platforms the tegra-vic, tegra-nvdec, tegra-nvjpg, and tegra-nvenc modules fail to load. Additionally, IGX currently requires the pci=pcie_bus_safe kernel parameter for Ethernet and Wi-Fi to work properly. [ 11.039654] tegra-vic 1534.vic: failed to get icc write handle [ 11.065685] tegra-nvdec 1548.nvdec: failed to get icc write handle [ 11.104539] tegra-nvjpg 1554.nvjpg: failed to get icc write handle [ 11.175208] tegra-nvenc 154c.nvenc: failed to get icc write handle --- [ 40.224020] ucsi_ccg 1-0008: failed to get FW build information [ 45.539420] ucsi_ccg 1-0008: con1: failed to register alt modes [ 45.589605] ucsi_ccg 1-0008: PPM init failed (-110) [Fix] - Cherry-pick the following commits: + Cherry-pick the following commits to resolve the above issues: memory: tegra: Add clients used by DRM in Tegra234 usb: typec: ucsi_ccg: Add OF support Revert "PCI: tegra194: Enable support for 256 Byte payload" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2028267 Title: Apply additional patches to enable and resolve issues with the Orin platform Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: [Impact] USB-C does not properly load firmware on a Jetson AGX devkit, and on all platforms the tegra-vic, tegra-nvdec, tegra-nvjpg, and tegra-nvenc modules fail to load. Additionally, IGX currently requires the pci=pcie_bus_safe kernel parameter for Ethernet and Wi-Fi to work properly. [ 11.039654] tegra-vic 1534.vic: failed to get icc write handle [ 11.065685] tegra-nvdec 1548.nvdec: failed to get icc write handle [ 11.104539] tegra-nvjpg 1554.nvjpg: failed to get icc write handle [ 11.175208] tegra-nvenc 154c.nvenc: failed to get icc write handle --- [ 40.224020] ucsi_ccg 1-0008: failed to get FW build information [ 45.539420] ucsi_ccg 1-0008: con1: failed to register alt modes [ 45.589605] ucsi_ccg 1-0008: PPM init failed (-110) [Fix] Cherry-pick the following commits to resolve the above issues: memory: tegra: Add clients used by DRM in Tegra234 usb: typec: ucsi_ccg: Add OF support Revert "PCI: tegra194: Enable support for 256 Byte payload" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2028267/+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 2028286] [NEW] Case [Azure][TDX] TDX Updated Patch set w/HCL
Public bug reported: SRU Justification [Impact] Miscrosoft has requested the inclusion of 5 patches in order to implement TDX with HCL. These patches will almost certainly be replaced over time by upstream commits. [Test Plan] Microsoft tested. [Regression Potential] TDX might not work in certain scenarios, e.g., TDX when HCL is present and glibc has not been updated. See SF: #00352899. [Other Info] SF: #00364214 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: SRU Justification [Impact] Miscrosoft has requested the inclusion of 5 patches in order to - implement TDX with HCL. + implement TDX with HCL. These patches will almost certainly be replaced + over time by upstream commits. [Test Plan] Microsoft tested. [Regression Potential] TDX might not work in certain scenarios, e.g., TDX when HCL is present and glibc has not been updated. [Other Info] SF: #00364214 ** Description changed: SRU Justification [Impact] Miscrosoft has requested the inclusion of 5 patches in order to implement TDX with HCL. These patches will almost certainly be replaced over time by upstream commits. [Test Plan] Microsoft tested. [Regression Potential] TDX might not work in certain scenarios, e.g., TDX when HCL is present - and glibc has not been updated. + and glibc has not been updated. See SF: #00352899. [Other Info] SF: #00364214 -- 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/2028286 Title: Case [Azure][TDX] TDX Updated Patch set w/HCL Status in linux package in Ubuntu: New Bug description: SRU Justification [Impact] Miscrosoft has requested the inclusion of 5 patches in order to implement TDX with HCL. These patches will almost certainly be replaced over time by upstream commits. [Test Plan] Microsoft tested. [Regression Potential] TDX might not work in certain scenarios, e.g., TDX when HCL is present and glibc has not been updated. See SF: #00352899. [Other Info] SF: #00364214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028286/+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 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
I noted that Lunar wasn't updated when I accepted this, but didn't want to block progress Jammy while I enquired. However, another SRU team member has confirmed that it is a requirement for hardware enablements for the latest stable release of Ubuntu to be enabled as well - otherwise users will be regressed when they upgrade. Please could you also upload a fix for Lunar? This will block the release to Jammy. I'll add a task to track that. Thanks! ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: firmware-sof (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: firmware-sof (Ubuntu Lunar) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Triaged Status in linux source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: New Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Incomplete Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: SRU Jusitification for firmware-sof [Impact] To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 [Fix] Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too [Test Case] Install the fixes on the target platform(RPL Dell SKU 0BDA) and verify the audio function. 1. Install the firmware-sof on platform(RPL) with Audio Smart AMP IC ALC1319D 2. Make sure the audio works 3. Also try above steps on other platforms(ADL/TGL) to make sure the audio keep working. [Where problems could occur] New firmware may affect ADL, RPL, and TGL platforms, we need to verify it on not only the target platform, but other existing platforms. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+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 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader
** Tags removed: rls-ll-incoming ** Tags added: foundations-todo -- 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/2027847 Title: Bump minimum /boot size in ubuntu-release-upgrader Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+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 2028267] Re: Apply additional patches to enable and resolve issues with the Orin platform
** Description changed: [Impact] USB-C does not properly load firmware on a Jetson AGX devkit, and on all platforms the tegra-vic, tegra-nvdec, tegra-nvjpg, and tegra-nvenc modules fail to load. [ 11.039654] tegra-vic 1534.vic: failed to get icc write handle [ 11.065685] tegra-nvdec 1548.nvdec: failed to get icc write handle [ 11.104539] tegra-nvjpg 1554.nvjpg: failed to get icc write handle [ 11.175208] tegra-nvenc 154c.nvenc: failed to get icc write handle --- [ 40.224020] ucsi_ccg 1-0008: failed to get FW build information [ 45.539420] ucsi_ccg 1-0008: con1: failed to register alt modes [ 45.589605] ucsi_ccg 1-0008: PPM init failed (-110) - [Fix] Cherry-pick the following commits: memory: tegra: Add clients used by DRM in Tegra234 usb: typec: ucsi_ccg: Add OF support + Revert "PCI: tegra194: Enable support for 256 Byte payload" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2028267 Title: Apply additional patches to enable and resolve issues with the Orin platform Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: [Impact] USB-C does not properly load firmware on a Jetson AGX devkit, and on all platforms the tegra-vic, tegra-nvdec, tegra-nvjpg, and tegra-nvenc modules fail to load. Additionally, IGX currently requires the pci=pcie_bus_safe kernel parameter for Ethernet and Wi-Fi to work properly. [ 11.039654] tegra-vic 1534.vic: failed to get icc write handle [ 11.065685] tegra-nvdec 1548.nvdec: failed to get icc write handle [ 11.104539] tegra-nvjpg 1554.nvjpg: failed to get icc write handle [ 11.175208] tegra-nvenc 154c.nvenc: failed to get icc write handle --- [ 40.224020] ucsi_ccg 1-0008: failed to get FW build information [ 45.539420] ucsi_ccg 1-0008: con1: failed to register alt modes [ 45.589605] ucsi_ccg 1-0008: PPM init failed (-110) [Fix] Cherry-pick the following commits to resolve the above issues: memory: tegra: Add clients used by DRM in Tegra234 usb: typec: ucsi_ccg: Add OF support Revert "PCI: tegra194: Enable support for 256 Byte payload" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2028267/+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 2024479] Re: kdump fails on big arm64 systems when offset is not specified
** Description changed: [Impact] kdump fails on arm64, on machines with a lot of memory when offset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel region. [Fix] To address this issue the following upstream commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the Focal 5.15 hwe kernel (from Jammy) will be fixed. [Test Plan] You need an arm64 machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump, configure the crash kernel size, and trigger a crash. - - Failing scenario (crashkernel >= 4G, without offset "@"): + 1) Failing scenario (crashkernel >= 4G, without offset "@"): It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. - - Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G') + 2) Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G') This must continue to work with the new patches (ie, no regressions), including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on Focal). [Regression Potential] KERNEL 5.15 - Jammy (and Focal via the HWE kernel): To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. kexec-tools - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without altering current functionality. Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features. kexec-tools - JAMMY, LUNAR, MANTIC: Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that the reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump. [Other] Commits to backport - MANTIC: kernel 6.3: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - LUNAR: kernel 6.2: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - KINETIC: WON'T FIX Kinetic won't be fixed as it is EOL soon. - JAMMY: kernel (5.15 kernel): a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified 4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel() 8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed 5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64 944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X
[Kernel-packages] [Bug 2024479] Re: kdump fails on big arm64 systems when offset is not specified
# VERIFICATION LUNAR kexec-tools On a lunar machine with 184G of memory, running 6.2 kernel install kexec-tools from proposed and triggered a crash. Crashdump file is generated successfully. root@biglunar:/var/crash# uname -rv 6.2.0-1005-azure #5-Ubuntu SMP Thu Jun 1 23:59:56 UTC 2023 root@biglunar:/var/crash# dpkg -l | grep kexec-tools ii kexec-tools1:2.0.22-2ubuntu3.1 arm64tools to support fast kexec reboots root@biglunar:/var/crash# cat /etc/default/grub grubgrub.d/ root@biglunar:/var/crash# cat /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" root@biglunar:/var/crash# ls 202307201417/ dmesg.202307201417 dump.202307201417 root@biglunar:/var/crash# ** Tags removed: verification-needed-lunar ** Tags added: verification-done-lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on big arm64 systems when offset is not specified Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in kexec-tools source package in Focal: Fix Committed Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: In Progress Status in kexec-tools source package in Jammy: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-hwe-5.15 source package in Jammy: Invalid Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in linux-hwe-5.15 source package in Kinetic: Invalid Status in kexec-tools source package in Lunar: Fix Committed Status in kexec-tools source package in Mantic: Fix Released Bug description: [Impact] kdump fails on arm64, on machines with a lot of memory when offset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel region. [Fix] To address this issue the following upstream commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the Focal 5.15 hwe kernel (from Jammy) will be fixed. [Test Plan] You need an arm64 machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump, configure the crash kernel size, and trigger a crash. - Failing scenario (crashkernel >= 4G, without offset "@"): It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. - Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G') This must continue to work with the new patches (ie, no regressions), including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on Focal). [Regression Potential] KERNEL 5.15 - Jammy (and Focal via the HWE kernel): To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. kexec-tools - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Thanks Michael, we will get this test kernel sanity tested and update
the results.
--
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/1988711
Title:
Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
Fix Released
Bug description:
[IMPACT/Justification]
There are numerous bug fixes included in the more recent version of lpfc That
Broadcom has asked to pull into Jammy and Kinetic to better support customers
in the field who are using the GA kernel and cant or wont move to the HWE
kernels. These all are limited to the lpfc driver itself, no patches to core
code are requested.
[FIX]
A few of these were already landed in Jammy, and all but 6 (ones landed in
6.0 upstream) were already in Kinetic.
b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into
lpfc_sli_prep_abort_xri()
ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved
configuration
ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF
WQE
0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in
queuecommand after VMID
35251b4d79db scsi: lpfc: Set PU field when providing D_ID in
XMIT_ELS_RSP64_CX iocb
f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with
malformed user input
4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in
lpfc_nvme_cancel_iocb()
1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for
nvme_admin_async_event cmd completion
ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for
aborted NVMe cmds
336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT
topology
b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is
aborted
6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after
starget_to_rport()
e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path
refactoring
24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path
refactoring
44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in
lpfc_ct_reject_event()
a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol
independent
ed913cf4a533 scsi: lpfc: Commonize VMID code location
fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for
NVMe I/O
e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
5099478e436f scsi: lpfc: Change VMID registration to be based on fabric
parameters
dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if
lpfc_err_lost_link()
4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in
rscn_recovery_check()
596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
92bd903da12b scsi: lpfc: Fix additional reference counting in
lpfc_bsg_rport_els()
db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in
lpfc_sli_prep_wqe()
a346f28ad231 scsi: lpfc: Remove unneeded variable
66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command
ef47575fd982 scsi: lpfc: Refactor cleanup of mailbox commands
d51cf5bd926c scsi: lpfc: Fix field overload in lpfc_iocbq data structure
1045592fc968 scsi: lpfc: Introduce FC_RSCN_MEMENTO flag for tracking post
RSCN completion
6c983d327b9e scsi: lpfc: Register for Application Services FC-4 type in
Fabric topology
6c8a3ce64b2c scsi: lpfc: Remove false FDMI NVMe FC-4 support for NPIV ports
c364c453d30a scsi: lpfc:
[Kernel-packages] [Bug 2028274] [NEW] watchdog: BUG: soft lockup - CPU#10 stuck for 134s! [DyingLightGame_:4256]
Public bug reported: Playing Dying Light 2 through steam/proton on Ubuntu 22.04 with nvidia 535. Game is perfect until I press quit in Dying Light 2's menu. The computer totally locks up and I have to hold the power button down. It happens every time. Downgrading to 525 with 'sudo apt install nvidia-driver-525 nvidia- dkms-525' fixed the issue. journalctl Jul 20 10:56:28 desktop kernel: watchdog: BUG: soft lockup - CPU#10 stuck for 134s! [DyingLightGame_:4256] Jul 20 10:56:28 desktop kernel: Modules linked in: vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc nls_iso8859_1 snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_usb_audio snd_hda_codec_realtek intel_rapl_msr snd_compress intel_rapl_common snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_codec_hdmi snd_usbmidi_lib x86_pkg_temp_thermal intel_powerclamp snd_rawmidi snd_seq_device coretemp mc snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi kvm_intel snd_hda_codec snd_hda_core xpad mei_hdcp snd_hwdep snd_pcm ff_memless joydev snd_timer kvm snd mei_me soundcore mei ee1004 intel_cstate intel_wmi_thunderbolt gigabyte_wmi wmi_bmof nvidia_uvm(POE) mac_hid acpi_pad acpi_tad sch_fq_codel msr pstore_blk ramoops pstore_zone reed_solomon efi_pstore ip _tables x_tables Jul 20 10:56:28 desktop kernel: 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 nvidia_drm(POE) nvidia_modeset(POE) hid_generic usbhid hid nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec aesni_intel rc_core crypto_simd cryptd drm r8169 ahci i2c_i801 xhci_pci i2c_smbus realtek libahci xhci_pci_renesas wmi video pinctrl_tigerlake Jul 20 10:56:28 desktop kernel: CPU: 10 PID: 4256 Comm: DyingLightGame_ Tainted: P OEL5.15.0-76-generic #83-Ubuntu Jul 20 10:56:28 desktop kernel: Hardware name: Gigabyte Technology Co., Ltd. H510M S2H/H510M S2H, BIOS F9 08/23/2021 Jul 20 10:56:28 desktop kernel: RIP: 0010:_nv039537rm+0x3b/0x80 [nvidia] Jul 20 10:56:28 desktop kernel: Code: d3 89 de 48 8d 55 0f c6 45 0f 00 e8 3f 4c 60 ff 80 7d 0f 00 41 89 c4 75 11 41 39 5d 10 76 20 49 8b 45 00 c1 eb 02 44 8b 24 98 <5b> 44 89 e0 41 5c 41 5d 48 83 c5 10 c3 0f 1f 84 00 00 00 00 00 be Jul 20 10:56:28 desktop kernel: RSP: 0018:bd0d839bf8f0 EFLAGS: 0202 Jul 20 10:56:28 desktop kernel: RAX: bd0d8200 RBX: 2440 RCX: 9100 Jul 20 10:56:28 desktop kernel: RDX: 952e995e596f RSI: 9100 RDI: 952de38c0008 Jul 20 10:56:28 desktop kernel: RBP: 952e995e5960 R08: 0020 R09: Jul 20 10:56:28 desktop kernel: R10: 9100 R11: 952e995e59c8 R12: 0001 Jul 20 10:56:28 desktop kernel: R13: 952de38c0bc8 R14: R15: Jul 20 10:56:28 desktop kernel: FS: 7fe4617b4040() GS:95355fc8() knlGS:7fee Jul 20 10:56:28 desktop kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 20 10:56:28 desktop kernel: CR2: 7f130400c000 CR3: 0001fca94005 CR4: 00770ee0 Jul 20 10:56:28 desktop kernel: PKRU: 5554 Jul 20 10:56:28 desktop kernel: Call Trace: Jul 20 10:56:28 desktop kernel: Jul 20 10:56:28 desktop kernel: ? _nv013076rm+0x10f/0x170 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv047477rm+0x20/0x30 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv030454rm+0x5a/0x110 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv030546rm+0x13f/0x340 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv030547rm+0x50/0x60 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv013174rm+0x86/0xc0 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv013170rm+0x3a4/0x400 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv044237rm+0xd1/0x1b0 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv041109rm+0x1e7/0x370 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv048377rm+0x40/0x95 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv035020rm+0x14d/0x2e0 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv048374rm+0xc5/0x460 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv002711rm+0xd/0x20 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv004074rm+0x19/0xb0 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv016053rm+0x51c/0x620 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv043216rm+0xab/0xe0 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv044933rm+0xac/0x130 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv044932rm+0x3e5/0x690 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv043119rm+0xd5/0x160 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv043120rm+0x41/0x70 [nvidia] Jul 20 10:56:28 desktop kernel: ? _nv000566rm+0x4d/0x60 [nvidia]
[Kernel-packages] [Bug 2028165] Re: nvidia-dkms-* FTBS with linux 6.5
** Patch added: "nvidia-graphics-drivers-525_525.125.06-0ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2028165/+attachment/5687461/+files/nvidia-graphics-drivers-525_525.125.06-0ubuntu2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2028165 Title: nvidia-dkms-* FTBS with linux 6.5 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Status in nvidia-graphics-drivers-390 source package in Mantic: New Status in nvidia-graphics-drivers-525 source package in Mantic: New Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21, from /var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] 164 |return get_user_pages_remote(tsk, mm, start, nr_pages, flags, | ^~~ | | | struct task_struct * ... [Fix] Apply the attached fix. [How to test] Install (and build) the patched packet. [Regression potential] The fix is composed of two patches: 1) the first patch simply garbage collect a reference to a function that was never used but that had the API changed in Linux 6.5 - so, it's a trivial change. 2) the second patch actually reimplement part of the vma scanning that was removed in __get_user_pages_locked() in upstream commit b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas array from internal GUP functions" - here is where most likely any regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+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 2028268] Re: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess r
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028268 Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: upgrading OS ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17 Uname: Linux 5.19.0-46-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parallels 2293 F pipewire parallels 2296 F wireplumber /dev/snd/pcmC0D0p: parallels 2293 F...m pipewire /dev/snd/seq:parallels 2293 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 20 14:41:04 2023 ErrorMessage: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-07 (377 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release arm64 (20220421) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=5a14ccf7-6bac-47b7-a3d6-6c10822fb10d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-07-20 (0 days ago) acpidump: dmi.bios.date: Mon, 27 Mar 2023 17:35:19 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 1.8.2 (23832) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr1.8.2(23832):bdMon,27Mar2023173519:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028268/+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 2028268] [NEW] package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess
Public bug reported: upgrading OS ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17 Uname: Linux 5.19.0-46-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parallels 2293 F pipewire parallels 2296 F wireplumber /dev/snd/pcmC0D0p: parallels 2293 F...m pipewire /dev/snd/seq:parallels 2293 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 20 14:41:04 2023 ErrorMessage: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-07 (377 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release arm64 (20220421) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=5a14ccf7-6bac-47b7-a3d6-6c10822fb10d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-07-20 (0 days ago) acpidump: dmi.bios.date: Mon, 27 Mar 2023 17:35:19 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 1.8.2 (23832) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr1.8.2(23832):bdMon,27Mar2023173519:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 lunar need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028268 Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: upgrading OS ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17 Uname: Linux 5.19.0-46-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parallels 2293 F pipewire parallels 2296 F wireplumber /dev/snd/pcmC0D0p: parallels 2293 F...m pipewire /dev/snd/seq:parallels 2293 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 20 14:41:04 2023 ErrorMessage: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-07 (377 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release arm64 (20220421) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=5a14ccf7-6bac-47b7-a3d6-6c10822fb10d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path
[Kernel-packages] [Bug 2028267] [NEW] Apply additional patches to enable and resolve issues with the Orin platform
Public bug reported: [Impact] USB-C does not properly load firmware on a Jetson AGX devkit, and on all platforms the tegra-vic, tegra-nvdec, tegra-nvjpg, and tegra-nvenc modules fail to load. [ 11.039654] tegra-vic 1534.vic: failed to get icc write handle [ 11.065685] tegra-nvdec 1548.nvdec: failed to get icc write handle [ 11.104539] tegra-nvjpg 1554.nvjpg: failed to get icc write handle [ 11.175208] tegra-nvenc 154c.nvenc: failed to get icc write handle --- [ 40.224020] ucsi_ccg 1-0008: failed to get FW build information [ 45.539420] ucsi_ccg 1-0008: con1: failed to register alt modes [ 45.589605] ucsi_ccg 1-0008: PPM init failed (-110) [Fix] Cherry-pick the following commits: memory: tegra: Add clients used by DRM in Tegra234 usb: typec: ucsi_ccg: Add OF support ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2028267 Title: Apply additional patches to enable and resolve issues with the Orin platform Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: [Impact] USB-C does not properly load firmware on a Jetson AGX devkit, and on all platforms the tegra-vic, tegra-nvdec, tegra-nvjpg, and tegra-nvenc modules fail to load. [ 11.039654] tegra-vic 1534.vic: failed to get icc write handle [ 11.065685] tegra-nvdec 1548.nvdec: failed to get icc write handle [ 11.104539] tegra-nvjpg 1554.nvjpg: failed to get icc write handle [ 11.175208] tegra-nvenc 154c.nvenc: failed to get icc write handle --- [ 40.224020] ucsi_ccg 1-0008: failed to get FW build information [ 45.539420] ucsi_ccg 1-0008: con1: failed to register alt modes [ 45.589605] ucsi_ccg 1-0008: PPM init failed (-110) [Fix] Cherry-pick the following commits: memory: tegra: Add clients used by DRM in Tegra234 usb: typec: ucsi_ccg: Add OF support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2028267/+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 2028165] Re: nvidia-dkms-* FTBS with linux 6.5
** Also affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2028165 Title: nvidia-dkms-* FTBS with linux 6.5 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Status in nvidia-graphics-drivers-390 source package in Mantic: New Status in nvidia-graphics-drivers-525 source package in Mantic: New Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21, from /var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] 164 |return get_user_pages_remote(tsk, mm, start, nr_pages, flags, | ^~~ | | | struct task_struct * ... [Fix] Apply the attached fix. [How to test] Install (and build) the patched packet. [Regression potential] The fix is composed of two patches: 1) the first patch simply garbage collect a reference to a function that was never used but that had the API changed in Linux 6.5 - so, it's a trivial change. 2) the second patch actually reimplement part of the vma scanning that was removed in __get_user_pages_locked() in upstream commit b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas array from internal GUP functions" - here is where most likely any regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+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 2026776] Re: arm64+ast2600: No Output from BMC's VGA port
** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-hwe-5.19 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Lunar) Importance: Undecided Status: New ** No longer affects: linux-hwe-5.19 (Ubuntu Lunar) ** No longer affects: linux-hwe-6.2 (Ubuntu Lunar) -- 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/2026776 Title: arm64+ast2600: No Output from BMC's VGA port Status in linux package in Ubuntu: New Status in linux-hwe-5.19 package in Ubuntu: Won't Fix Status in linux-hwe-6.2 package in Ubuntu: New Status in linux source package in Lunar: New Bug description: SRU Justification: [ Impact ] On systems that have the following combination of hardware 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ No output when connecting a display to the BMC's VGA port. [ Fix ] For AST2500+ MMIO should be enabled by default. [ Test Plan ] Test on targeted hardware to make sure BMC is displaying output. [ Where problems could occur ] Not aware of any potential problems, but any should be confined to ASPEED AST2500+ hardware. [ Other Info ] Patch is already in jammy/nvidia-5.19 and jammy/nvidia-6.2 and has been tested with affected BMC. [Issue] On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6=4327a6137ed43a091d900b1ac833345d60f32228 [Action] Please apply the following two backports to the appropriate Ubuntu HWE kernels: https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560 https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026776/+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 2028253] [NEW] update apparmor and LSM stacking patch set
Public bug reported: [Impact] Provide an updated patch set for apparmor / LSM stacking with all the custom features that we need in the Ubuntu kernel. This patch set is required to provide the proper confinement with snaps and other Ubuntu-specific security features. [Fix] Apply the latest updated patch set from: https://gitlab.com/jjohansen/apparmor-kernel [Test case] Run the apparmor test case suite. [Regression potential] This patch set introduces significant non-upstream changes to the security layer, so we may expect generic regressions in the kernel, especially running applications that are stressing the security layer (such as systemd, snapd, lxd, etc.). ** Affects: linux (Ubuntu) Importance: Critical Status: Confirmed ** Affects: linux (Ubuntu Mantic) Importance: Critical Status: Confirmed ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Mantic) Status: New => Confirmed ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Critical ** Description changed: [Impact] Provide an updated patch set for apparmor / LSM stacking with all the custom features that we need in the Ubuntu kernel. + This patch set is required to provide the proper confinement with snaps + and other Ubuntu-specific security features. + [Fix] Apply the latest updated patch set from: - https://gitlab.com/jjohansen/apparmor-kernel + https://gitlab.com/jjohansen/apparmor-kernel [Test case] Run the apparmor test case suite. [Regression potential] This patch set introduces significant non-upstream changes to the security layer, so we may expect generic regressions in the kernel, especially running applications that are stressing the security layer (such as systemd, snapd, lxd, etc.). -- 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/2028253 Title: update apparmor and LSM stacking patch set Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Confirmed Bug description: [Impact] Provide an updated patch set for apparmor / LSM stacking with all the custom features that we need in the Ubuntu kernel. This patch set is required to provide the proper confinement with snaps and other Ubuntu-specific security features. [Fix] Apply the latest updated patch set from: https://gitlab.com/jjohansen/apparmor-kernel [Test case] Run the apparmor test case suite. [Regression potential] This patch set introduces significant non-upstream changes to the security layer, so we may expect generic regressions in the kernel, especially running applications that are stressing the security layer (such as systemd, snapd, lxd, etc.). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028253/+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 2028251] [NEW] Mantic update: v6.4.4 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.4.4 upstream stable release from git://git.kernel.org/ Linux 6.4.4 sh: hd64461: Handle virq offset for offchip IRQ base and HD64461 IRQ sh: mach-dreamcast: Handle virq offset in cascaded IRQ demux sh: mach-highlander: Handle virq offset in cascaded IRL demux sh: mach-r2d: Handle virq offset in cascaded IRL demux block/partition: fix signedness issue for Amiga partitions io_uring: Use io_schedule* in cqring wait tty: serial: fsl_lpuart: add earlycon for imx8ulp platform wireguard: netlink: send staged packets when setting initial private key wireguard: queueing: use saner cpu selection wrapping netfilter: nf_tables: prevent OOB access in nft_byteorder_eval netfilter: nf_tables: do not ignore genmask when looking up chain by id netfilter: conntrack: Avoid nf_ct_helper_hash uses after free drm/amdgpu: check RAS irq existence for VCN/JPEG drm/amd/pm: add abnormal fan detection for smu 13.0.0 drm/amdgpu/sdma4: set align mask to 255 drm/amd/pm: revise the ASPM settings for thunderbolt attached scenario drm/amdgpu: Skip mark offset for high priority rings drm/amdgpu: make sure that BOs have a backing store drm/amdgpu: make sure BOs are locked in amdgpu_vm_get_memory LoongArch: Include KBUILD_CPPFLAGS in CHECKFLAGS invocation ovl: fix null pointer dereference in ovl_get_acl_rcu() ovl: let helper ovl_i_path_real() return the realinode ovl: fix null pointer dereference in ovl_permission() kbuild: add $(CLANG_FLAGS) to KBUILD_CPPFLAGS kbuild: Add KBUILD_CPPFLAGS to as-option invocation kbuild: Add CLANG_FLAGS to as-instr powerpc/vdso: Include CLANG_FLAGS explicitly in ldflags-y mips: Include KBUILD_CPPFLAGS in CHECKFLAGS invocation Input: ads7846 - fix pointer cast warning fs: no need to check source md/raid1-10: fix casting from randomized structure in raid1_submit_write() Input: ads7846 - Fix usage of match data blktrace: use inline function for blk_trace_remove() while blktrace is disabled leds: trigger: netdev: Recheck NETDEV_LED_MODE_LINKUP on dev rename ARM: orion5x: fix d2net gpio initialization ARM: dts: qcom: ipq4019: fix broken NAND controller properties override ARM: dts: qcom: msm8660: Fix regulator node names regulator: tps65219: Fix matching interrupts for their regulators ASoC: mediatek: mt8173: Fix snd_soc_component_initialize error path ASoC: mediatek: mt8173: Fix irq error path btrfs: do not BUG_ON() on tree mod log failure at __btrfs_cow_block() btrfs: fix extent buffer leak after tree mod log failure at split_node() btrfs: add missing error handling when logging operation while COWing extent buffer btrfs: fix race when deleting quota root from the dirty cow roots list btrfs: reinsert BGs failed to reclaim btrfs: add block-group tree to lockdep classes btrfs: bail out reclaim process if filesystem is read-only btrfs: delete unused BGs while reclaiming BGs btrfs: warn on invalid slot in tree mod log rewind btrfs: insert tree mod log move in push_node_left btrfs: fix dirty_metadata_bytes for redirtied buffers btrfs: add handling for RAID1C23/DUP to btrfs_reduce_alloc_profile ipvs: increase ip_vs_conn_tab_bits range for 64BIT usb: typec: ucsi: Mark dGPUs as DEVICE scope fs: Lock moved directories fs: Establish locking order for unrelated directories Revert "udf: Protect rename against modification of moved directory" Revert "f2fs: fix potential corruption when moving a directory" ext4: Remove ext4 locking of moved directory fs: avoid empty option when generating legacy mount string jffs2: reduce stack usage in jffs2_build_xattr_subsystem() nfsd: use vfs setgid helper shmem: use ramfs_kill_sb() for kill_sb method of ramfs-based tmpfs mm/damon/ops-common: atomically test and clear young on ptes and pmds autofs: use flexible array in ioctl structure integrity: Fix possible multiple allocation in integrity_inode_get() um: Use HOST_DIR for mrproper watch_queue: prevent dangling pipe pointer bcache: Fix __bch_btree_node_alloc to make the failure behavior consistent bcache: Remove unnecessary NULL point check in node allocations bcache: fixup btree_cache_wait list damage wifi: mt76: mt7921e: fix init command fail with enabled device wifi: cfg80211: fix receiving mesh packets without RFC1042 header wifi: ath10k: Serialize wake_tx_queue ops wifi: cfg80211: fix regulatory disconnect for non-MLO mmc: sdhci: fix DMA configure compatibility issue when 64bit DMA mode is used. mmc: mmci: Set PROBE_PREFER_ASYNCHRONOUS mmc: core: disable TRIM on Micron MTFC4GACAJCN-1M mmc: core: disable TRIM on Kingston EMMC04G-M627
[Kernel-packages] [Bug 2028250] [NEW] Mantic update: v6.4.3 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.4.3 upstream stable release from git://git.kernel.org/ Linux 6.4.3 fork: lock VMAs of the parent process when forking bootmem: remove the vmemmap pages from kmemleak in free_bootmem_page mm: call arch_swap_restore() from do_swap_page() mm: lock newly mapped VMA with corrected ordering mm: lock newly mapped VMA which can be modified after it becomes visible mm: lock a vma before stack expansion ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: 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/2028250 Title: Mantic update: v6.4.3 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.4.3 upstream stable release from git://git.kernel.org/ Linux 6.4.3 fork: lock VMAs of the parent process when forking bootmem: remove the vmemmap pages from kmemleak in free_bootmem_page mm: call arch_swap_restore() from do_swap_page() mm: lock newly mapped VMA with corrected ordering mm: lock newly mapped VMA which can be modified after it becomes visible mm: lock a vma before stack expansion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028250/+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 2028249] [NEW] Mantic update: v6.4.2 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.4.2 upstream stable release from git://git.kernel.org/ Linux 6.4.2 arch/arm64/mm/fault: Fix undeclared variable error in do_page_fault() drm/amdgpu: Validate VM ioctl flags. dm ioctl: Avoid double-fetch of version docs: Set minimal gtags / GNU GLOBAL version to 6.6.5 scripts/tags.sh: Resolve gtags empty index generation hugetlb: revert use of page_cache_next_miss() nubus: Partially revert proc_create_single_data() conversion Revert "cxl/port: Enable the HDM decoder capability for switch ports" nfs: don't report STATX_BTIME in ->getattr execve: always mark stack as growing down during early stack setup PCI/ACPI: Call _REG when transitioning D-states PCI/ACPI: Validate acpi_pci_set_power_state() parameter tools/nolibc: x86_64: disable stack protector for _start xtensa: fix lock_mm_and_find_vma in case VMA not found ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: 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/2028249 Title: Mantic update: v6.4.2 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.4.2 upstream stable release from git://git.kernel.org/ Linux 6.4.2 arch/arm64/mm/fault: Fix undeclared variable error in do_page_fault() drm/amdgpu: Validate VM ioctl flags. dm ioctl: Avoid double-fetch of version docs: Set minimal gtags / GNU GLOBAL version to 6.6.5 scripts/tags.sh: Resolve gtags empty index generation hugetlb: revert use of page_cache_next_miss() nubus: Partially revert proc_create_single_data() conversion Revert "cxl/port: Enable the HDM decoder capability for switch ports" nfs: don't report STATX_BTIME in ->getattr execve: always mark stack as growing down during early stack setup PCI/ACPI: Call _REG when transitioning D-states PCI/ACPI: Validate acpi_pci_set_power_state() parameter tools/nolibc: x86_64: disable stack protector for _start xtensa: fix lock_mm_and_find_vma in case VMA not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028249/+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 2028247] [NEW] Mantic update: v6.4.1 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.4.1 upstream stable release from git://git.kernel.org/ x86/microcode/AMD: Load late on both threads too x86/smp: Make stop_other_cpus() more robust x86/smp: Dont access non-existing CPUID leaf x86/smp: Remove pointless wmb()s from native_stop_other_cpus() x86/smp: Use dedicated cache-line for mwait_play_dead() x86/smp: Cure kexec() vs. mwait_play_dead() breakage cpufreq: amd-pstate: Make amd-pstate EPP driver name hyphenated can: isotp: isotp_sendmsg(): fix return error fix on TX path maple_tree: fix potential out-of-bounds access in mas_wr_end_piv() mm: introduce new 'lock_mm_and_find_vma()' page fault helper mm: make the page fault mmap locking killable arm64/mm: Convert to using lock_mm_and_find_vma() powerpc/mm: Convert to using lock_mm_and_find_vma() mips/mm: Convert to using lock_mm_and_find_vma() riscv/mm: Convert to using lock_mm_and_find_vma() arm/mm: Convert to using lock_mm_and_find_vma() mm/fault: convert remaining simple cases to lock_mm_and_find_vma() powerpc/mm: convert coprocessor fault to lock_mm_and_find_vma() mm: make find_extend_vma() fail if write lock not held execve: expand new process stack manually ahead of time mm: always expand the stack with the mmap write lock held HID: wacom: Use ktime_t rather than int when dealing with timestamps gup: add warning if some caller would seem to want stack expansion mm/khugepaged: fix regression in collapse_file() fbdev: fix potential OOB read in fast_imageblit() HID: hidraw: fix data race on device refcount HID: logitech-hidpp: add HIDPP_QUIRK_DELAYED_INIT for the T651. Revert "thermal/drivers/mediatek: Use devm_of_iomap to avoid resource leak in mtk_thermal_probe" sparc32: fix lock_mm_and_find_vma() conversion parisc: fix expand_stack() conversion csky: fix up lock_mm_and_find_vma() conversion xtensa: fix NOMMU build with lock_mm_and_find_vma() conversion Linux 6.4.1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: Confirmed ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v6.4.1 upstream stable release + from git://git.kernel.org/ -v6.4.1 upstream stable release -from git://git.kernel.org/ + x86/microcode/AMD: Load late on both threads too + x86/smp: Make stop_other_cpus() more robust + x86/smp: Dont access non-existing CPUID leaf + x86/smp: Remove pointless wmb()s from native_stop_other_cpus() + x86/smp: Use dedicated cache-line for mwait_play_dead() + x86/smp: Cure kexec() vs. mwait_play_dead() breakage + cpufreq: amd-pstate: Make amd-pstate EPP driver name hyphenated + can: isotp: isotp_sendmsg(): fix return error fix on TX path + maple_tree: fix potential out-of-bounds access in mas_wr_end_piv() + mm: introduce new 'lock_mm_and_find_vma()' page fault helper + mm: make the page fault mmap locking killable + arm64/mm: Convert to using lock_mm_and_find_vma() + powerpc/mm: Convert to using lock_mm_and_find_vma() + mips/mm: Convert to using lock_mm_and_find_vma() + riscv/mm: Convert to using lock_mm_and_find_vma() + arm/mm: Convert to using lock_mm_and_find_vma() + mm/fault: convert remaining simple cases to lock_mm_and_find_vma() + powerpc/mm: convert coprocessor fault to lock_mm_and_find_vma() + mm: make find_extend_vma() fail if write lock not held + execve: expand new process stack manually
[Kernel-packages] [Bug 2025444] Re: Mute/mic LEDs no function on some HP Platforms
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2025444 Title: Mute/mic LEDs no function on some HP Platforms Status in OEM Priority Project: Fix Committed Status in linux-oem-6.1 package in Ubuntu: New Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] The mic mute/audio mute LEDS are not work on some HP Platforms [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk on linux-oem-6.1, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2025444/+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 1981525] Re: Add support for Raptor Lake CPUs
There doesn't appear to be anything to sponsor here (yet?), so unsubscribing ubuntu-sponsors. You may resubscribe once there's a debdiff that needs sponsoring by us. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981525 Title: Add support for Raptor Lake CPUs Status in OEM Priority Project: Fix Committed Status in OEM Priority Project focal series: Fix Committed Status in thermald package in Ubuntu: Invalid Status in thermald source package in Focal: In Progress Status in thermald source package in Jammy: Fix Released Bug description: [Impact] * Support thermald on Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/354 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981525/+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 1981525] Re: Add support for Raptor Lake CPUs
** Changed in: thermald (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981525 Title: Add support for Raptor Lake CPUs Status in OEM Priority Project: Fix Committed Status in OEM Priority Project focal series: Fix Committed Status in thermald package in Ubuntu: Invalid Status in thermald source package in Focal: In Progress Status in thermald source package in Jammy: Fix Released Bug description: [Impact] * Support thermald on Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/354 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981525/+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 1989044] Re: RPL: Add INT3400 base path
** Also affects: thermald (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: thermald (Ubuntu Focal) Status: New => In Progress ** Changed in: thermald (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1989044 Title: RPL: Add INT3400 base path Status in thermald package in Ubuntu: New Status in thermald source package in Focal: In Progress Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * Add INT3400 base path for Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * check the thermald log. * Get the base path of INT3400. [Where problems could occur] * This change is to add path in INT3400 for Raptor Lake, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1989044/+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 1981525] Re: Add support for Raptor Lake CPUs
** Also affects: thermald (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: thermald (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981525 Title: Add support for Raptor Lake CPUs Status in OEM Priority Project: Fix Committed Status in OEM Priority Project focal series: Fix Committed Status in thermald package in Ubuntu: Invalid Status in thermald source package in Focal: In Progress Status in thermald source package in Jammy: Fix Released Bug description: [Impact] * Support thermald on Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/354 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981525/+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 2028237] Re: radeon ring issue & box unusuable
radeon ring messages that kept scrolling I believe are Jul 20 16:28:38 dc7700-3 kernel: radeon :01:00.0: ring 0 stalled for more than 10776msec Jul 20 16:28:38 dc7700-3 kernel: radeon :01:00.0: GPU lockup (current fence id 0x0ccb last fence id 0x0ccc on ring 0) or something similar.. refer attached from journactl ** Attachment added: "journalctrl.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028237/+attachment/5687345/+files/journalctrl.txt ** Changed in: linux (Ubuntu) Status: Incomplete => 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/2028237 Title: radeon ring issue & box unusuable Status in linux package in Ubuntu: New Bug description: Ubuntu Desktop mantic install attempted to - hp dc7700 (c2d-e6320, 8gb amd/ati rv610/radeon hd2400 pro/xt) I've had issues before with some old cards... this is a RADEON issue with 6.3 kernel probably. I wonder if this box (video card anyway) is too old for Linux 6.3 & later? though Xubuntu install still works correct, as have recent Lubuntu/LXQt installs... something in GNOME gives issues. (see http://iso.qa.ubuntu.com/qatracker/milestones/446/builds/282842/testcases/1761/results/) Two install attempts... one had unusual behavior; NO TRY/install appeared, with the box eventually appearing at desktop... on starting the install option available at GUI, the screen went black & I lost control of box. refer QA test log for details; but long waits & no details were obtained.. just black screen & inability to even use text terminal... I eventually concluded session was still running as I rebooted using SysRq REISUO Second install to box was as expected.. post install checks & untouched xubuntu mantic good, ubuntu desktop however had the following - PLYMOUTH appeared as TEXT without ubuntu logo (ie. Ubuntu 23.04 in text & dots) i believe the install is perfect.. however machine is unusable.. I believe radeon issues... from text terminal all looks as it should.. but GUI will login initially & looks correct, then I quickly lose control... multiple boots tried, on many I just lose control; black screen & nothing, black screen & cursor, or endless lines of radeon/ring- stalled & no other control. System is not crashed, as I can still SysRQ REISUO to end session, but no other control appears to exist. Second install QA-test PASSED as install is good (checks, mostly done at terminal though)... hardware having issues with radeon driver being a non-install issue ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.3.0-7-generic 6.3.0-7.7 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guiverc2457 F wireplumber /dev/snd/seq:guiverc2451 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 20 17:47:51 2023 InstallationDate: Installed on 2023-07-20 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230719) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=linux XDG_RUNTIME_DIR= ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.0-7-generic root=UUID=b395b94d-a495-4bad-9d83-25eb344c854a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.3.0-7-generic N/A linux-backports-modules-6.3.0-7-generic N/A linux-firmware 20230629.gitee91452d-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.release: 1.5 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:br1.5:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:skuET090AV: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028237/+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 1981525] Re: Add support for Raptor Lake CPUs
** Also affects: oem-priority/focal Importance: Critical Assignee: Dirk Su (dirksu) Status: Fix Committed ** Changed in: thermald (Ubuntu) Status: Fix Released => Invalid ** Changed in: thermald (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: thermald (Ubuntu) Assignee: koba (kobako) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981525 Title: Add support for Raptor Lake CPUs Status in OEM Priority Project: Fix Committed Status in OEM Priority Project focal series: Fix Committed Status in thermald package in Ubuntu: Invalid Status in thermald source package in Jammy: Fix Released Bug description: [Impact] * Support thermald on Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/354 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981525/+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 2025670] Re: amd_pmf: AMD 7840HS cpufreq locked at 400-544MHz after power unplugged
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1017.17
kernel in https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/proposed2 solves the problem. Please test the
kernel and update this bug with the results. If the problem is solved,
change the tag 'verification-needed-jammy' to 'verification-done-jammy'.
If the problem still exists, change the tag 'verification-needed-jammy'
to 'verification-failed-jammy'.
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!
** Tags added: verification-needed verification-needed-jammy
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Description changed:
+ [SRU Justification]
+
+ BugLink: https://bugs.launchpad.net/bugs/2025670
+
+ [Impact]
+
+ Call trace dumped in events workqueue power_supply_changed_work, and
+ cpufreq locked to 400-544MHz.
+
+ ```
+ [ 22.592162] Call Trace:
+ [ 22.592164]
+ [ 22.592164] ? rcu_note_context_switch+0x5e0/0x660
+ [ 22.592166] ? __warn+0x81/0x130
+ [ 22.592171] ? rcu_note_context_switch+0x5e0/0x660
+ [ 22.592172] ? report_bug+0x171/0x1a0
+ [ 22.592175] ? prb_read_valid+0x1b/0x30
+ [ 22.592177] ? handle_bug+0x3c/0x80
+ [ 22.592178] ? exc_invalid_op+0x17/0x70
+ [ 22.592179] ? asm_exc_invalid_op+0x1a/0x20
+ [ 22.592182] ? rcu_note_context_switch+0x5e0/0x660
+ [ 22.592183] ? acpi_ut_delete_object_desc+0x86/0xb0
+ [ 22.592186] ? acpi_ut_update_ref_count.part.0+0x22d/0x930
+ [ 22.592187] __schedule+0xc0/0x1410
+ [ 22.592189] ? ktime_get+0x3c/0xa0
+ [ 22.592191] ? lapic_next_event+0x1d/0x30
+ [ 22.592193] ? hrtimer_start_range_ns+0x25b/0x350
+ [ 22.592196] schedule+0x5e/0xd0
+ [ 22.592197] schedule_hrtimeout_range_clock+0xbe/0x140
+ [ 22.592199] ? __pfx_hrtimer_wakeup+0x10/0x10
+ [ 22.592200] usleep_range_state+0x64/0x90
+ [ 22.592203] amd_pmf_send_cmd+0x106/0x2a0 [amd_pmf
bddfe0fe3712aaa99acce3d5487405c5213c6616]
+ [ 22.592207] amd_pmf_update_slider+0x56/0x1b0 [amd_pmf
bddfe0fe3712aaa99acce3d5487405c5213c6616]
+ [ 22.592210] amd_pmf_set_sps_power_limits+0x72/0x80 [amd_pmf
bddfe0fe3712aaa99acce3d5487405c5213c6616]
+ [ 22.592213] amd_pmf_pwr_src_notify_call+0x49/0x90 [amd_pmf
bddfe0fe3712aaa99acce3d5487405c5213c6616]
+ [ 22.592216] notifier_call_chain+0x5a/0xd0
+ [ 22.592218] atomic_notifier_call_chain+0x32/0x50
+ ```
+
+ [Fix]
+
+ Upstream v6.4 fixed with commit
+
[146b6f6855e76](https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-
+ drivers-x86.git/commit/?h=fixes=146b6f6855e7656e8329910606595220c761daac)
+ ("platform/x86/amd/pmf: Register notify handler only if SPS is
+ enabled"). It has also been backported to stable trees v6.1.36 (oem-6.1
+ in v6.1.34 now), v6.2.15 (linux/lunar in v6.2.13 now), v6.3.10
+ (linux/mantic in v6.3.8 now).
+
+ [Test Case]
+
+ 1. boot with AC power cable connected
+ 2. unplug power cable and check cpufreq
+ 3. check no call trace found in dmesg
+
+ [Where problems could occur]
+
+ This patch installs only notify handler when the feature is fully
+ supported, so it's the right behavior.
+
+ [Other Info]
+
+ While we should receive this fix from stable fixes soon, nominate only
+ oem-6.1 to allow rolling out fix as soon as possible.
+
+ == original bug description ==
+
Upstream bugzilla https://bugzilla.kernel.org/show_bug.cgi?id=217571
This is specifically when a system advertises support for PMF, but
doesn't support static power slider for any reason.
Upstream fix in
https://github.com/torvalds/linux/commit/146b6f6855e7656e8329910606595220c761daac,
which has been backported to v6.1.36 (oem-6.1 in v6.1.34 now), v6.2.15
(linux/lunar in v6.2.13), v6.3.10 (linux/mantic in v6.3.8), v6.4.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2025670
Title:
amd_pmf: AMD 7840HS cpufreq locked at 400-544MHz after power unplugged
Status in linux package in Ubuntu:
New
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
New
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux source package in Mantic:
New
Status in linux-oem-6.1 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2025670
[Impact]
Call trace dumped in events workqueue power_supply_changed_work, and
cpufreq locked to 400-544MHz.
```
[ 22.592162]
[Kernel-packages] [Bug 2028237] Re: radeon ring issue & box unusuable
** Description changed: - will add details shortly + Ubuntu Desktop mantic install attempted to + - hp dc7700 (c2d-e6320, 8gb amd/ati rv610/radeon hd2400 pro/xt) + I've had issues before with some old cards... this is a RADEON issue + with 6.3 kernel probably. I wonder if this box (video card anyway) is + too old for Linux 6.3 & later? though Xubuntu install still works + correct, as have recent Lubuntu/LXQt installs... something in GNOME + gives issues. + + (see + http://iso.qa.ubuntu.com/qatracker/milestones/446/builds/282842/testcases/1761/results/) + + + Two install attempts... one had unusual behavior; NO TRY/install appeared, with the box eventually appearing at desktop... on starting the install option available at GUI, the screen went black & I lost control of box. + + refer QA test log for details; but long waits & no details were + obtained.. just black screen & inability to even use text terminal... I + eventually concluded session was still running as I rebooted using SysRq + REISUO + + Second install to box was as expected.. post install checks & untouched + xubuntu mantic good, ubuntu desktop however had the following + + - PLYMOUTH appeared as TEXT without ubuntu logo (ie. Ubuntu 23.04 in + text & dots) + + i believe the install is perfect.. however machine is unusable.. I + believe radeon issues... from text terminal all looks as it should.. but + GUI will login initially & looks correct, then I quickly lose control... + + multiple boots tried, on many I just lose control; black screen & + nothing, black screen & cursor, or endless lines of radeon/ring-stalled + & no other control. + + System is not crashed, as I can still SysRQ REISUO to end session, but no other control appears to exist. Second install QA-test PASSED as install is good (checks, mostly done at terminal though)... hardware having issues with radeon driver being a non-install issue ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.3.0-7-generic 6.3.0-7.7 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: guiverc2457 F wireplumber - /dev/snd/seq:guiverc2451 F pipewire + USERPID ACCESS COMMAND + /dev/snd/controlC0: guiverc2457 F wireplumber + /dev/snd/seq:guiverc2451 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 20 17:47:51 2023 InstallationDate: Installed on 2023-07-20 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230719) IwConfig: - lono wireless extensions. - - enp0s25 no wireless extensions. + lono wireless extensions. + + enp0s25 no wireless extensions. MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=linux - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=linux + XDG_RUNTIME_DIR= ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.0-7-generic root=UUID=b395b94d-a495-4bad-9d83-25eb344c854a ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-6.3.0-7-generic N/A - linux-backports-modules-6.3.0-7-generic N/A - linux-firmware 20230629.gitee91452d-0ubuntu1 + linux-restricted-modules-6.3.0-7-generic N/A + linux-backports-modules-6.3.0-7-generic N/A + linux-firmware 20230629.gitee91452d-0ubuntu1 RfKill: - + SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.release: 1.5 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:br1.5:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:skuET090AV: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard -- 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/2028237 Title: radeon ring issue & box unusuable Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop mantic install attempted to - hp dc7700 (c2d-e6320, 8gb amd/ati rv610/radeon hd2400 pro/xt) I've had issues before with some old cards... this is a RADEON issue with 6.3 kernel probably. I wonder if this box (video card anyway) is too old for Linux 6.3 & later? though Xubuntu install still works correct, as have recent Lubuntu/LXQt
[Kernel-packages] [Bug 2023638] Re: Various backlight issues with the 6.0/6.1 kernel
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1017.17 kernel in https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/proposed2 solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! ** Tags removed: verification-done-jammy ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2023638 Title: Various backlight issues with the 6.0/6.1 kernel Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] There are some new patches for new method to decide which backlight driver should be registered introduced since 6.1. And we backport some of them to 6.0-oem kernel which are not enough to solved all backlight issues. 1. dell_laptop created a non-working backlight driver before nvidia is loaded, that leads to the system can't adjust the display brightness. 2. acpi_backlight0 sometimes will be generated together with intel_backlight. [Fix] Below 2 commits from v6.3-rc6 prevent the acpi_backlight from being registered automatically(which have been included into ubuntu kernels through stable update) e506731c8f35 ACPI: video: Make acpi_backlight=video work independent from GPU driver 78dfc9d1d1ab ACPI: video: Add auto_detect arg to __acpi_video_get_backlight_type() Below patch prevents platform driver(dell_laptop) from creating backlight driver after win8. aa8a950a5d6b ACPI: video: Stop trying to use vendor backlight control on laptops from after ~2012 https://patchwork.kernel.org/project/linux-acpi/patch/20230608091258.7963-1-hdego...@redhat.com/ [Test] Verified on the dell platform which reports this issue. [Where problems could occur] The assumption of the not-yet-upstreamed commit regarding backlight control is that, after Windows 8, all laptop backlights are controlled either by ACPI or the native graphics driver. It impacts the laptops that do not follow the assumption and will lead to broken backlight interface. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023638/+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 2025444] Re: Mute/mic LEDs no function on some HP Platforms
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1017.17 kernel in https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/proposed2 solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2025444 Title: Mute/mic LEDs no function on some HP Platforms Status in OEM Priority Project: Fix Committed Status in linux-oem-6.1 package in Ubuntu: New Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] The mic mute/audio mute LEDS are not work on some HP Platforms [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk on linux-oem-6.1, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2025444/+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 2025195] Re: HDMI output with More than one child device for port B in VBT error
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1017.17 kernel in https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/proposed2 solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2025195 Title: HDMI output with More than one child device for port B in VBT error Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The HDMI monitor doesn't work, no events while plug/unplug then cable. [Fix] From the bug report[1], skip the return workaround the issue, so I created the DMI quirk to list affected platforms. Intel is submitting patches[2][3] to fix the issue, but it requires to backport huge drm structure changes, too. As there is no regression found with this workaround, it's safer to use the DMI quirk to handle this issue. 1. https://gitlab.freedesktop.org/drm/intel/-/issues/7709 2. https://patchwork.freedesktop.org/series/117641/ 3. https://patchwork.freedesktop.org/series/114200/ [Test] Verified by me, FE, and ODM. [Where problems could occur] I have no idea what might happen, so only make the workaround avaiable on the listed platforms. So far, no regressions have been observed with plug/unplug, switch modes, reboot, and suspend tests. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025195/+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 2028237] Re: radeon ring issue & box unusuable
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2028237 ** Tags added: iso-testing -- 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/2028237 Title: radeon ring issue & box unusuable Status in linux package in Ubuntu: Incomplete Bug description: will add details shortly ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.3.0-7-generic 6.3.0-7.7 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guiverc2457 F wireplumber /dev/snd/seq:guiverc2451 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 20 17:47:51 2023 InstallationDate: Installed on 2023-07-20 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230719) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=linux XDG_RUNTIME_DIR= ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.0-7-generic root=UUID=b395b94d-a495-4bad-9d83-25eb344c854a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.3.0-7-generic N/A linux-backports-modules-6.3.0-7-generic N/A linux-firmware 20230629.gitee91452d-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.release: 1.5 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:br1.5:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:skuET090AV: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028237/+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 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
Interesting, a new ~intermediate situation of bug 1. Its not
constraining that thermal envelope quite as much now. Thermald is
running, I guess bug 1 is still present but lessened since I reinstalled
it? Computer was not in use.
When running `stress -c 1` it places the task on the correct ideal core
(the one that clocks up to 4.8Ghz), but it bounces around between
1300mhz and 500mhz.
First log statement for the power envelope was at 2023-07-19T18:07:15
(roughly at boot) and then long_term_time and long_term_power suddenly
step down and stay that way at roughly 3 hours 30 minutes uptime.
(Current uptime is about 9 hours 50 minutes.)
2023-07-19T21:39:11
{'backup_rest': 281474976776192,
'locked': False,
'long_term_enabled': True,
'long_term_power': 65.0,
'long_term_time': 32.0,
'short_term_enabled': True,
'short_term_power': 160.0,
'short_term_time': 0.00244140625}
2023-07-19T21:39:13
{'backup_rest': 281474976776192,
'locked': False,
'long_term_enabled': True,
'long_term_power': 7.75,
'long_term_time': 28.0,
'short_term_enabled': True,
'short_term_power': 160.0,
'short_term_time': 0.00244140625}
here is your grep:
/sys/devices/system/cpu/intel_pstate/hwp_dynamic_boost:0
/sys/devices/system/cpu/intel_pstate/max_perf_pct:100
/sys/devices/system/cpu/intel_pstate/min_perf_pct:10
/sys/devices/system/cpu/intel_pstate/no_turbo:0
/sys/devices/system/cpu/intel_pstate/status:active
It will take a ~day for bug 2 to trigger, I will update and do the grep when
that happens. If I don't need to use this computer I will leave it on without
running my script to lock the power envelope at a higher value.
--
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/2026658
Title:
CPU frequency governor broken after upgrading from 22.10 to 23.04,
stuck at 400Mhz on Alder Lake
Status in linux package in Ubuntu:
New
Bug description:
I've tried to include as much detail as possible in this bug report, I
originally assembled it just after the release of ubuntu 23.04. There
has been no change since then.
I have had substantial performance problems since updating from ubuntu 22.10
to 23.04.
The computer in question is the 17 inch Razer Blade laptop from 2022 with an
intel i7-12800H.
Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing
has changed.)
This issue occurs regardless of whether the OpenRazer
(https://openrazer.github.io/) drivers etc are installed.
Description of problem:
I have discovered what may be two separate bugs involving low level power
management details on the cpu, they involve the cpu entering different types of
throttled states and never recovering. These issues appeared immediately after
upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with
plenty of thermal headroom, cpu temperatures cannot reach concerning values
except when using stress testing tools.
(I don't know how to propery untangle these two issues, so I'm posting
them as one. I apologize for the review complexity this causes, but I
think posting the information all in one spot is more constructive
here.)
High level testing notes:
- This issue occurs with use of both the intel_pstate driver and the cpufreq
driver. (I don't have the same level of detail for cpufreq, but the issue still
occurs.)
- I have additionally tested a handful of intel_pstate parameters (and
others) via grub kernel command line arguments to no effect. All testing
reported here was done with:
GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau"
GRUB_CMDLINE_LINUX=""
(loading nouveau caused problems for me on 22.10, I have not bothered
reinvestigating it on 23.04)
- There is a firmware update available from the manufacture when I boot into
Windows, I have not installed it (yet).
- - Update: I installed it. No change.
- Changing the cpu governor setting from "powersave" to "performance" using
`cpupower frequency-set -g performance` has no effect. (Note: this action is
separate from the intel_pstate's power-saver/balanced/performance setting
visible with the `powerprofilesctl` utility. It doesn't seem to be a governor
bug.
- - (There is a tertiary issue where I also see substantial (+50%)
performance degredation using the "performance" profile in a test suite I run
constantly for my job; that is clearly a problem but it is an unrelated bug
that has existed for quite some time.)
Summary and my own conclusions:
These are my takeaways, the ~raw data is in the followup section.
Bug 1)
The reported cpu power limits are progressively constrained over time. Once
this failure mode starts the performance never recovers.
- As this situation progresses the observed cpu speeds (I'm using htop)
list as 2800Mhz at idle, but the instant any load at all is placed on a cpu
core that core immediately drops to exactly
[Kernel-packages] [Bug 2028237] [NEW] radeon ring issue & box unusuable
Public bug reported: will add details shortly ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.3.0-7-generic 6.3.0-7.7 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guiverc2457 F wireplumber /dev/snd/seq:guiverc2451 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 20 17:47:51 2023 InstallationDate: Installed on 2023-07-20 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230719) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=linux XDG_RUNTIME_DIR= ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.0-7-generic root=UUID=b395b94d-a495-4bad-9d83-25eb344c854a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.3.0-7-generic N/A linux-backports-modules-6.3.0-7-generic N/A linux-firmware 20230629.gitee91452d-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.release: 1.5 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:br1.5:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:skuET090AV: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug iso-testing mantic ** 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/2028237 Title: radeon ring issue & box unusuable Status in linux package in Ubuntu: Incomplete Bug description: will add details shortly ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.3.0-7-generic 6.3.0-7.7 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guiverc2457 F wireplumber /dev/snd/seq:guiverc2451 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 20 17:47:51 2023 InstallationDate: Installed on 2023-07-20 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230719) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=linux XDG_RUNTIME_DIR= ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.0-7-generic root=UUID=b395b94d-a495-4bad-9d83-25eb344c854a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.3.0-7-generic N/A linux-backports-modules-6.3.0-7-generic N/A linux-firmware 20230629.gitee91452d-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.release: 1.5 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:br1.5:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:skuET090AV: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028237/+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 2028219] Re: radeon ring issue & box unusuable
** 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/2028219 Title: radeon ring issue & box unusuable Status in linux package in Ubuntu: Invalid Bug description: will add detail on other box shortly apport-collect on actual install (GUI isn't functional on actual box) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028219/+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 2028219] [NEW] radeon ring issue & box unusuable
Public bug reported: will add detail on other box shortly apport-collect on actual install (GUI isn't functional on actual box) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** 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/2028219 Title: radeon ring issue & box unusuable Status in linux package in Ubuntu: Incomplete Bug description: will add detail on other box shortly apport-collect on actual install (GUI isn't functional on actual box) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028219/+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 2013064] Re: ubuntu_ltp_kernel_misc.zram01 fails to create xfs on a device too small in lunar
** Tags added: ubuntu-ltp-kernel-misc -- 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/2013064 Title: ubuntu_ltp_kernel_misc.zram01 fails to create xfs on a device too small in lunar Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Lunar: Incomplete Bug description: 16637 zram01 5 TINFO: make xfs filesystem on /dev/zram3 16638 Filesystem must be larger than 300MB. 16639 Usage: mkfs.xfs 16640 /* blocksize */[-b size=num] 16641 /* config file */[-c options=xxx] 16642 /* metadata */[-m crc=0|1,finobt=0|1,uuid=xxx,rmapbt=0|1,reflink=0|1, 16643 inobtcount=0|1,bigtime=0|1] 16644 /* data subvol */[-d agcount=n,agsize=n,file,name=xxx,size=num, 16645 (sunit=value,swidth=value|su=num,sw=num|noalign), 16646 sectsize=num 16647 /* force overwrite */[-f] 16648 /* inode size */[-i perblock=n|size=num,maxpct=n,attr=0|1|2, 16649 projid32bit=0|1,sparse=0|1,nrext64=0|1] 16650 /* no discard */[-K] 16651 /* log subvol */[-l agnum=n,internal,size=num,logdev=xxx,version=n 16652 sunit=value|su=num,sectsize=num,lazy-count=0|1] 16653 /* label */[-L label (maximum 12 characters)] 16654 /* naming */[-n size=num,version=2|ci,ftype=0|1] 16655 /* no-op info only */[-N] 16656 /* prototype file */[-p fname] 16657 /* quiet */[-q] 16658 /* realtime subvol */[-r extsize=num,size=num,rtdev=xxx] 16659 /* sectorsize */[-s size=num] 16660 /* version */[-V] 16661 devicename 16662is required unless -d name=xxx is given. 16663is xxx (bytes), xxxs (sectors), xxxb (fs blocks), xxxk (xxx KiB), 16664 xxxm (xxx MiB), xxxg (xxx GiB), xxxt (xxx TiB) or xxxp (xxx PiB). 16665is xxx (512 byte blocks). 1 zram01 5 TFAIL: failed to make xfs on /dev/zram3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2013064/+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 2028217] [NEW] MTL: Add support for Mateor Lake
Public bug reported: [Impact] * Support thermald on Mateor Lake CPU. [Test Plan] * Use a machine with a Mateor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Mateor Lake in thermald, which won't impact other hardware. ** Affects: thermald (Ubuntu) Importance: Undecided Status: New ** Affects: thermald (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: thermald (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: thermald (Ubuntu Kinetic) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: thermald (Ubuntu Lunar) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Also affects: thermald (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: thermald (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: thermald (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: thermald (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: thermald (Ubuntu Focal) Status: New => In Progress ** Changed in: thermald (Ubuntu Jammy) Status: New => In Progress ** Changed in: thermald (Ubuntu Kinetic) Status: New => In Progress ** Changed in: thermald (Ubuntu Lunar) Status: New => In Progress ** Changed in: thermald (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Changed in: thermald (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: thermald (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) ** Changed in: thermald (Ubuntu Lunar) Assignee: (unassigned) => koba (kobako) ** Summary changed: - MTL: Add support for Meter Lake + MTL: Add support for Mateor Lake ** Description changed: - [Description] + [Impact] + + * Support thermald on Mateor Lake CPU. + + [Test Plan] + + * Use a machine with a Mateor Lake cpu. + + * systemctl status thermald + + * Status of thermald should be `running` + + [Where problems could occur] + + * This change is to add support for Mateor Lake in thermald, which + won't impact other hardware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2028217 Title: MTL: Add support for Mateor Lake Status in thermald package in Ubuntu: New Status in thermald source package in Focal: In Progress Status in thermald source package in Jammy: In Progress Status in thermald source package in Kinetic: In Progress Status in thermald source package in Lunar: In Progress Bug description: [Impact] * Support thermald on Mateor Lake CPU. [Test Plan] * Use a machine with a Mateor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Mateor Lake in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2028217/+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 2012260] Re: Add support for Alder Lake N
** Changed in: thermald (Ubuntu Kinetic) Status: New => In Progress ** Changed in: thermald (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) ** Changed in: thermald (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2012260 Title: Add support for Alder Lake N Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Status in thermald source package in Kinetic: In Progress Bug description: [Impact] * Support thermald on Alder Lake N CPU. [Test Plan] * Use a machine with a Alder Lake N cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Alder Lake N in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2012260/+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
