Hi Robert, I noticed your update and was going to submit the patch to
our 6.11 trees, but it appears to already be there. Maybe it just hasn't
made it into the update cycle yet, but it's headed that way.
Tim
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2098063
Title:
Missing support for USB-C Apple Magic Trackpad
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Oracular:
In Progress
Bug description:
Hi,
The Ubuntu kernel (at least 6.11.0-1015-oem) is missing support for
the USB-C version of the Apple Magic Trackpad. This is the only
version of the Magic Trackpad that can be purchased from Apple any
more. They no longer sell the Lightning version.
Support was added in upstream commit "HID: magicmouse: Apple Magic
Trackpad 2 USB-C driver support"
(https://github.com/torvalds/linux/commit/87a2f10395c82c2b4687bb8611a6c5663a12f9e7).
Can you please backport this commit to the Ubuntu kernel?
Without this commit the trackpad cannot scroll or do other gestures,
right click or middle click, tapping does not work, etc. All it can do
is move the mouse cursor and left click.
The Debian 6.1 and 6.12 kernels have this commit and the device works
fine on those kernels.
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098063/+subscriptions
пятница
[Bug 2098063] Re: Missing support for USB-C Apple Magic Trackpad
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Oracular)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Oracular)
Status: New => In Progress
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2098063
Title:
Missing support for USB-C Apple Magic Trackpad
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Oracular:
In Progress
Bug description:
Hi,
The Ubuntu kernel (at least 6.11.0-1015-oem) is missing support for
the USB-C version of the Apple Magic Trackpad. This is the only
version of the Magic Trackpad that can be purchased from Apple any
more. They no longer sell the Lightning version.
Support was added in upstream commit "HID: magicmouse: Apple Magic
Trackpad 2 USB-C driver support"
(https://github.com/torvalds/linux/commit/87a2f10395c82c2b4687bb8611a6c5663a12f9e7).
Can you please backport this commit to the Ubuntu kernel?
Without this commit the trackpad cannot scroll or do other gestures,
right click or middle click, tapping does not work, etc. All it can do
is move the mouse cursor and left click.
The Debian 6.1 and 6.12 kernels have this commit and the device works
fine on those kernels.
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098063/+subscriptions
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Oracular)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Oracular)
Status: New => In Progress
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2098063
Title:
Missing support for USB-C Apple Magic Trackpad
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Oracular:
In Progress
Bug description:
Hi,
The Ubuntu kernel (at least 6.11.0-1015-oem) is missing support for
the USB-C version of the Apple Magic Trackpad. This is the only
version of the Magic Trackpad that can be purchased from Apple any
more. They no longer sell the Lightning version.
Support was added in upstream commit "HID: magicmouse: Apple Magic
Trackpad 2 USB-C driver support"
(https://github.com/torvalds/linux/commit/87a2f10395c82c2b4687bb8611a6c5663a12f9e7).
Can you please backport this commit to the Ubuntu kernel?
Without this commit the trackpad cannot scroll or do other gestures,
right click or middle click, tapping does not work, etc. All it can do
is move the mouse cursor and left click.
The Debian 6.1 and 6.12 kernels have this commit and the device works
fine on those kernels.
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098063/+subscriptions
[Bug 2091719] Re: btrfs will WARN_ON() in btrfs_remove_qgroup() unnecessarily
Hi, I've done a few runs with the kernel and modules from proposed and
cannot reproduce the issue. Thank you for taking care of this!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2091719
Title:
btrfs will WARN_ON() in btrfs_remove_qgroup() unnecessarily
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Fix Committed
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2091719
[Impact]
The following commit for noble and oracular introduced two new WARN_ON() calls
in btrfs qgroup removals, and even though the author at the time believed they
would not be reachable, it turns out it can happen quite frequently in the
right conditions.
ubuntu-noble b2ad25ba539452f492805e5f7d94e80894aa860f
commit a776bf5f3c2300cfdf8a195663460b1793ac9847
Author: Qu Wenruo <wqu@suse.com>
Date: Fri Apr 19 14:29:32 2024 +0930
Subject: btrfs: slightly loosen the requirement for qgroup removal
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a776bf5f3c2300cfdf8a195663460b1793ac9847
$ git describe --contains b2ad25ba539452f492805e5f7d94e80894aa860f
Ubuntu-6.8.0-50.51~143
This primarily affects the systemd CI that runs integration tests on merge:
https://github.com/systemd/systemd/actions/runs/12297539029/job/34318915884?pr=35589
Kernel panic - not syncing: kernel: panic_on_warn set ...
CPU: 0 PID: 1316 Comm: (sd-clean) Not tainted 6.8.0-50-generic #51-Ubuntu
Call Trace:
<TASK>
dump_stack_lvl+0x27/0xa0
dump_stack+0x10/0x20
panic+0x366/0x3c0
? btrfs_remove_qgroup+0x271/0x490 [btrfs]
check_panic_on_warn+0x4f/0x60
__warn+0x95/0x160
? btrfs_remove_qgroup+0x271/0x490 [btrfs]
report_bug+0x17e/0x1b0
handle_bug+0x51/0xa0
exc_invalid_op+0x18/0x80
asm_exc_invalid_op+0x1b/0x20
RIP: 0010:btrfs_remove_qgroup+0x271/0x490 [btrfs]
Code: c0 0f 85 27 fe ff ff 48 8b 43 b0 4c 39 f0 75 d5 4d 8d b5 e0 08 00 00 4c 89 f7 e8 8a 45 19 e2 48 83 7b 98 00 0f 84 52 01 00 00 <0f> 0b 49 8b 45 10 a8 10 74 42 41 f6 85 d0 08 00 00 0c 75 38 48 83
? btrfs_remove_qgroup+0x266/0x490 [btrfs]
btrfs_ioctl+0x12b9/0x13a0 [btrfs]
? srso_alias_return_thunk+0x5/0xfbef5
? __seccomp_filter+0x368/0x570
? __fput+0x15e/0x2e0
__x64_sys_ioctl+0xa3/0xf0
x64_sys_call+0x12a3/0x25a0
do_syscall_64+0x7f/0x180
entry_SYSCALL_64_after_hwframe+0x78/0x80
[Fix]
The fix just landed in mainline as:
commit c0def46dec9c547679a25fe7552c4bcbec0b0dd2
Author: Qu Wenruo <wqu@suse.com>
Date: Mon Nov 11 07:29:07 2024 +1030
Subject: btrfs: improve the warning and error message for btrfs_remove_qgroup()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c0def46dec9c547679a25fe7552c4bcbec0b0dd2
The commit places the WARN_ON behind CONFIG_BTRFS_DEBUG, which silences the
warning for most users. It is safe to do so, as noted by the Author, as
the user space tool managing the qgroups would rescan them, to fix the
inconsistent view.
This is needed for both noble and oracular.
[Testcase]
The upstream systemd CI tests can consistently reproduce the issue, so the test
and proposed kernels will be run against the systemd CI for verification.
There is a test kernel available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/lp2091719-test
If you install it, the systemd CI will run to completion.
[Where problems could occur]
We are changing the WARN_ON() to occur only when CONFIG_BTRFS_DEBUG is enabled.
There is no other change in logic, so functionality should be the same as what
we have now.
If a regression were to occur, it would affect systems with btrfs filesystems
that are utilising subvolumes. It would not likely cause any data loss or disk
corruption, as userspace tools should be able to automatically fix up any
inconsistent views without user interaction.
[Other info]
Systemd upstream bisected the issue here:
https://github.com/systemd/systemd/pull/35567#issuecomment-2538160543
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2091719/+subscriptions
cannot reproduce the issue. Thank you for taking care of this!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2091719
Title:
btrfs will WARN_ON() in btrfs_remove_qgroup() unnecessarily
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Fix Committed
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2091719
[Impact]
The following commit for noble and oracular introduced two new WARN_ON() calls
in btrfs qgroup removals, and even though the author at the time believed they
would not be reachable, it turns out it can happen quite frequently in the
right conditions.
ubuntu-noble b2ad25ba539452f492805e5f7d94e80894aa860f
commit a776bf5f3c2300cfdf8a195663460b1793ac9847
Author: Qu Wenruo <wqu@suse.com>
Date: Fri Apr 19 14:29:32 2024 +0930
Subject: btrfs: slightly loosen the requirement for qgroup removal
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a776bf5f3c2300cfdf8a195663460b1793ac9847
$ git describe --contains b2ad25ba539452f492805e5f7d94e80894aa860f
Ubuntu-6.8.0-50.51~143
This primarily affects the systemd CI that runs integration tests on merge:
https://github.com/systemd/systemd/actions/runs/12297539029/job/34318915884?pr=35589
Kernel panic - not syncing: kernel: panic_on_warn set ...
CPU: 0 PID: 1316 Comm: (sd-clean) Not tainted 6.8.0-50-generic #51-Ubuntu
Call Trace:
<TASK>
dump_stack_lvl+0x27/0xa0
dump_stack+0x10/0x20
panic+0x366/0x3c0
? btrfs_remove_qgroup+0x271/0x490 [btrfs]
check_panic_on_warn+0x4f/0x60
__warn+0x95/0x160
? btrfs_remove_qgroup+0x271/0x490 [btrfs]
report_bug+0x17e/0x1b0
handle_bug+0x51/0xa0
exc_invalid_op+0x18/0x80
asm_exc_invalid_op+0x1b/0x20
RIP: 0010:btrfs_remove_qgroup+0x271/0x490 [btrfs]
Code: c0 0f 85 27 fe ff ff 48 8b 43 b0 4c 39 f0 75 d5 4d 8d b5 e0 08 00 00 4c 89 f7 e8 8a 45 19 e2 48 83 7b 98 00 0f 84 52 01 00 00 <0f> 0b 49 8b 45 10 a8 10 74 42 41 f6 85 d0 08 00 00 0c 75 38 48 83
? btrfs_remove_qgroup+0x266/0x490 [btrfs]
btrfs_ioctl+0x12b9/0x13a0 [btrfs]
? srso_alias_return_thunk+0x5/0xfbef5
? __seccomp_filter+0x368/0x570
? __fput+0x15e/0x2e0
__x64_sys_ioctl+0xa3/0xf0
x64_sys_call+0x12a3/0x25a0
do_syscall_64+0x7f/0x180
entry_SYSCALL_64_after_hwframe+0x78/0x80
[Fix]
The fix just landed in mainline as:
commit c0def46dec9c547679a25fe7552c4bcbec0b0dd2
Author: Qu Wenruo <wqu@suse.com>
Date: Mon Nov 11 07:29:07 2024 +1030
Subject: btrfs: improve the warning and error message for btrfs_remove_qgroup()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c0def46dec9c547679a25fe7552c4bcbec0b0dd2
The commit places the WARN_ON behind CONFIG_BTRFS_DEBUG, which silences the
warning for most users. It is safe to do so, as noted by the Author, as
the user space tool managing the qgroups would rescan them, to fix the
inconsistent view.
This is needed for both noble and oracular.
[Testcase]
The upstream systemd CI tests can consistently reproduce the issue, so the test
and proposed kernels will be run against the systemd CI for verification.
There is a test kernel available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/lp2091719-test
If you install it, the systemd CI will run to completion.
[Where problems could occur]
We are changing the WARN_ON() to occur only when CONFIG_BTRFS_DEBUG is enabled.
There is no other change in logic, so functionality should be the same as what
we have now.
If a regression were to occur, it would affect systems with btrfs filesystems
that are utilising subvolumes. It would not likely cause any data loss or disk
corruption, as userspace tools should be able to automatically fix up any
inconsistent views without user interaction.
[Other info]
Systemd upstream bisected the issue here:
https://github.com/systemd/systemd/pull/35567#issuecomment-2538160543
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2091719/+subscriptions
[Bug 2106275] [NEW] Enable OOB P-state control for Intel Sierra Forest/Granite Rapids
Public bug reported:
[Impact]
The intel_pstate module should not be loaded when OOB mode for P-state
control is enabled, but currently the Noble kernel is only able to
detect OOB mode up to Emerald Rapids CPUs. This patch enables detection
for Granite Rapids/Sierra Forest CPUs.
[Fix]
Cherry pick 3ca2a3d1e727 ("cpufreq: intel_pstate: Support Granite Rapids
and Sierra Forest OOB mode") into the Noble tree.
[Test plan]
Build tested only.
[Where problems could occur]
Risk of regression seems very low, but problems here could manifest as
the intel_pstate driver misbehaving on Sierra Forest/Granite Rapids
systems.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Description changed:
[Impact]
The intel_pstate module should not be loaded when OOB mode for P-state
control is enabled, but currently the Noble kernel is only able to
detect OOB mode up to Emerald Rapids CPUs. This patch enables detection
for Granite Rapids/Sierra Forest CPUs.
[Fix]
Cherry pick 3ca2a3d1e727 ("cpufreq: intel_pstate: Support Granite Rapids
and Sierra Forest OOB mode") into the Noble tree.
[Test plan]
Build tested only.
[Where problems could occur]
Risk of regression seems very low, but problems here could manifest as
the intel_pstate driver misbehaving on Sierra Forest/Granite Rapids
systems.
-
- [Where problems could occur]
-
- Low regression risk
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106275
Title:
Enable OOB P-state control for Intel Sierra Forest/Granite Rapids
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
New
Bug description:
[Impact]
The intel_pstate module should not be loaded when OOB mode for P-state
control is enabled, but currently the Noble kernel is only able to
detect OOB mode up to Emerald Rapids CPUs. This patch enables
detection for Granite Rapids/Sierra Forest CPUs.
[Fix]
Cherry pick 3ca2a3d1e727 ("cpufreq: intel_pstate: Support Granite
Rapids and Sierra Forest OOB mode") into the Noble tree.
[Test plan]
Build tested only.
[Where problems could occur]
Risk of regression seems very low, but problems here could manifest as
the intel_pstate driver misbehaving on Sierra Forest/Granite Rapids
systems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106275/+subscriptions
[Impact]
The intel_pstate module should not be loaded when OOB mode for P-state
control is enabled, but currently the Noble kernel is only able to
detect OOB mode up to Emerald Rapids CPUs. This patch enables detection
for Granite Rapids/Sierra Forest CPUs.
[Fix]
Cherry pick 3ca2a3d1e727 ("cpufreq: intel_pstate: Support Granite Rapids
and Sierra Forest OOB mode") into the Noble tree.
[Test plan]
Build tested only.
[Where problems could occur]
Risk of regression seems very low, but problems here could manifest as
the intel_pstate driver misbehaving on Sierra Forest/Granite Rapids
systems.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Description changed:
[Impact]
The intel_pstate module should not be loaded when OOB mode for P-state
control is enabled, but currently the Noble kernel is only able to
detect OOB mode up to Emerald Rapids CPUs. This patch enables detection
for Granite Rapids/Sierra Forest CPUs.
[Fix]
Cherry pick 3ca2a3d1e727 ("cpufreq: intel_pstate: Support Granite Rapids
and Sierra Forest OOB mode") into the Noble tree.
[Test plan]
Build tested only.
[Where problems could occur]
Risk of regression seems very low, but problems here could manifest as
the intel_pstate driver misbehaving on Sierra Forest/Granite Rapids
systems.
-
- [Where problems could occur]
-
- Low regression risk
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106275
Title:
Enable OOB P-state control for Intel Sierra Forest/Granite Rapids
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
New
Bug description:
[Impact]
The intel_pstate module should not be loaded when OOB mode for P-state
control is enabled, but currently the Noble kernel is only able to
detect OOB mode up to Emerald Rapids CPUs. This patch enables
detection for Granite Rapids/Sierra Forest CPUs.
[Fix]
Cherry pick 3ca2a3d1e727 ("cpufreq: intel_pstate: Support Granite
Rapids and Sierra Forest OOB mode") into the Noble tree.
[Test plan]
Build tested only.
[Where problems could occur]
Risk of regression seems very low, but problems here could manifest as
the intel_pstate driver misbehaving on Sierra Forest/Granite Rapids
systems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106275/+subscriptions
[Bug 2100027] Re: Bluetooth failure on reboot - Kernel 6.11.0-17 - Mediatek 7921
After 7 days of testing, investigation and general scrutiny, an
unexpected outcome bubbled to the surface.
Good news first:-
Bluetooth works perfectly with kernel 6.11.0-21
Bluetooth works perfectly with kernel 6.8.0-52
Unusual discovery:-
Bluetooth works perfectly with kernel 6.11.0-21 - only when both TPM and Secure Boot are enabled
Bluetooth works perfectly with kernel 6.8.0-52 - TPM and Secure Boot can be disabled and it still works perfectly
Having used Ubuntu for many years with both TPM and Secure Boot
disabled, it's surprising that I now have to enable both TPM and Secure
Boot to use Bluetooth with a recent kernel.
Lastly, following this discovery, I don't know where the Bluetooth problem resides:-
UEFI Firmware?
Kernel?
Mediatek mt7921 device?
TPM?
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2100027
Title:
Bluetooth failure on reboot - Kernel 6.11.0-17 - Mediatek 7921
Status in linux package in Ubuntu:
Triaged
Bug description:
Using kernel 6.11.0-17, Bluetooth works on first boot. If I reboot,
GUI settings shows Bluetooth Turned Off and the on/off slider is
completely inactive
Ubuntu 24.04.2 (fully upgraded)
Gnome 46 (Wayland)
GMKtec NucBox K2, AMD Ryzen™ 7 7735HS with Radeon™ Graphics × 16, Wifi
and bluetooth combined Mediatek mt7921
Bluetooth both first boot and reboot, performs flawlessly with Kernel
6.8.0-52 and earlier
I expected the Bluetooth adapter to be available upon a reboot with kernel 6.11.0-17
The Bluetooth adapter was inactive and could not be turned on
The Mediatek card mt7921 is an internal combined wifi and bluetooth
device and the wifi is unaffected in all kernels
I can resuscitate the bluetooth device:-
Close applications and power off
Remove the power cable
Press and hold the power button for more than 30 seconds
Re-attach power cable
Boot the PC
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.11.0-17-generic 6.11.0-17.17~24.04.2
ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
Uname: Linux 6.11.0-17-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 17:35:46 2025
InstallationDate: Installed on 2024-04-26 (305 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
SourcePackage: linux-signed-hwe-6.11
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: mark 3058 F.... pipewire
/dev/snd/controlC1: mark 3062 F.... wireplumber
/dev/snd/controlC0: mark 3062 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-04-26 (315 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: GMKtec NucBox K2
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-17-generic root=UUID=13a1f220-a4c5-4d7a-b455-718180ab846a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.11.0-17-generic N/A
linux-backports-modules-6.11.0-17-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.9
Tags: noble wayland-session
Uname: Linux 6.11.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sudo users
_MarkForUpload: True
dmi.bios.date: 04/26/2023
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 104
dmi.board.asset.tag: Default string
dmi.board.name: GMKtec
dmi.board.vendor: GMKtec
dmi.board.version: Version 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 1.3
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr104:bd04/26/2023:br5.24:efr1.3:svnGMKtec:pnNucBoxK2:pvrVersion1.0:rvnGMKtec:rnGMKtec:rvrVersion1.0:cvnDefaultstring:ct3:cvrDefaultstring:skuK2-001:
dmi.product.family: MINI
dmi.product.name: NucBox K2
dmi.product.sku: K2-001
dmi.product.version: Version 1.0
dmi.sys.vendor: GMKtec
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100027/+subscriptions
unexpected outcome bubbled to the surface.
Good news first:-
Bluetooth works perfectly with kernel 6.11.0-21
Bluetooth works perfectly with kernel 6.8.0-52
Unusual discovery:-
Bluetooth works perfectly with kernel 6.11.0-21 - only when both TPM and Secure Boot are enabled
Bluetooth works perfectly with kernel 6.8.0-52 - TPM and Secure Boot can be disabled and it still works perfectly
Having used Ubuntu for many years with both TPM and Secure Boot
disabled, it's surprising that I now have to enable both TPM and Secure
Boot to use Bluetooth with a recent kernel.
Lastly, following this discovery, I don't know where the Bluetooth problem resides:-
UEFI Firmware?
Kernel?
Mediatek mt7921 device?
TPM?
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2100027
Title:
Bluetooth failure on reboot - Kernel 6.11.0-17 - Mediatek 7921
Status in linux package in Ubuntu:
Triaged
Bug description:
Using kernel 6.11.0-17, Bluetooth works on first boot. If I reboot,
GUI settings shows Bluetooth Turned Off and the on/off slider is
completely inactive
Ubuntu 24.04.2 (fully upgraded)
Gnome 46 (Wayland)
GMKtec NucBox K2, AMD Ryzen™ 7 7735HS with Radeon™ Graphics × 16, Wifi
and bluetooth combined Mediatek mt7921
Bluetooth both first boot and reboot, performs flawlessly with Kernel
6.8.0-52 and earlier
I expected the Bluetooth adapter to be available upon a reboot with kernel 6.11.0-17
The Bluetooth adapter was inactive and could not be turned on
The Mediatek card mt7921 is an internal combined wifi and bluetooth
device and the wifi is unaffected in all kernels
I can resuscitate the bluetooth device:-
Close applications and power off
Remove the power cable
Press and hold the power button for more than 30 seconds
Re-attach power cable
Boot the PC
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.11.0-17-generic 6.11.0-17.17~24.04.2
ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
Uname: Linux 6.11.0-17-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 17:35:46 2025
InstallationDate: Installed on 2024-04-26 (305 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
SourcePackage: linux-signed-hwe-6.11
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: mark 3058 F.... pipewire
/dev/snd/controlC1: mark 3062 F.... wireplumber
/dev/snd/controlC0: mark 3062 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-04-26 (315 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: GMKtec NucBox K2
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-17-generic root=UUID=13a1f220-a4c5-4d7a-b455-718180ab846a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.11.0-17-generic N/A
linux-backports-modules-6.11.0-17-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.9
Tags: noble wayland-session
Uname: Linux 6.11.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sudo users
_MarkForUpload: True
dmi.bios.date: 04/26/2023
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 104
dmi.board.asset.tag: Default string
dmi.board.name: GMKtec
dmi.board.vendor: GMKtec
dmi.board.version: Version 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 1.3
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr104:bd04/26/2023:br5.24:efr1.3:svnGMKtec:pnNucBoxK2:pvrVersion1.0:rvnGMKtec:rnGMKtec:rvrVersion1.0:cvnDefaultstring:ct3:cvrDefaultstring:skuK2-001:
dmi.product.family: MINI
dmi.product.name: NucBox K2
dmi.product.sku: K2-001
dmi.product.version: Version 1.0
dmi.sys.vendor: GMKtec
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100027/+subscriptions
[Bug 2106091] Re: Missing bpftool binary on riscv64
okay, got this sorted on the kernel side.. hopefully without side-
effects
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106091
Title:
Missing bpftool binary on riscv64
Status in linux package in Ubuntu:
Confirmed
Status in xdp-tools package in Ubuntu:
Fix Released
Bug description:
For other architectures there is now a separate bpftool binary
package, however on riscv64 there appears to neither be a bpftool
binary pacakge nor a bpftool binary in the linux-rsicv-tools package.
This is likely a side effect of [0]. How can we enable building of
the bpftool binary package also for riscv64?
0: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/plucky/commit/?h=master-
next&id=ca6b092bd0bf5a5f3534857d04fca9384a03783f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106091/+subscriptions
effects
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106091
Title:
Missing bpftool binary on riscv64
Status in linux package in Ubuntu:
Confirmed
Status in xdp-tools package in Ubuntu:
Fix Released
Bug description:
For other architectures there is now a separate bpftool binary
package, however on riscv64 there appears to neither be a bpftool
binary pacakge nor a bpftool binary in the linux-rsicv-tools package.
This is likely a side effect of [0]. How can we enable building of
the bpftool binary package also for riscv64?
0: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/plucky/commit/?h=master-
next&id=ca6b092bd0bf5a5f3534857d04fca9384a03783f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106091/+subscriptions
[Bug 2106251] [NEW] Backport "PCI: Wait for device readiness with Configuration RRS" to N/O
Public bug reported:
GCP is requesting a backport of the patch d591f6804e7e "PCI: Wait for
device readiness with Configuration RRS" from upstream to the Noble and
Oracular kernels.
The following patches are required for the backport:
d591f6804e7e1310881c9224d72247a2b65039af PCI: Wait for device readiness with Configuration RRS
ce526e1b29c70cff175e3ab8d9cb7e3f24321498 PCI: Avoid FLR for Mediatek MT7922 WiFi
Impact:
- GCP states that they would like to leverage the flexibility that the patch affords over and above the typical PCI quirks treatment.
Testing:
- Boot-tested the changes in GCP environment on amd64 hardware.
Regression potential:
- The changes affect the PCI core and the Mediatek MT7922 WiFi driver. The PCI core is affected in the device wait logic. Latency between device reset and configuration accesses may be altered. The Mediatek driver introduces a quirk that specifies those devices don't implement FLR.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Noble)
Importance: Undecided
Assignee: Tim Whisonant (tswhison)
Status: In Progress
** Affects: linux (Ubuntu Oracular)
Importance: Undecided
Assignee: Tim Whisonant (tswhison)
Status: In Progress
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) => Tim Whisonant (tswhison)
** Changed in: linux (Ubuntu Oracular)
Status: New => In Progress
** Changed in: linux (Ubuntu Oracular)
Assignee: (unassigned) => Tim Whisonant (tswhison)
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106251
Title:
Backport "PCI: Wait for device readiness with Configuration RRS" to
N/O
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
In Progress
Bug description:
GCP is requesting a backport of the patch d591f6804e7e "PCI: Wait for
device readiness with Configuration RRS" from upstream to the Noble
and Oracular kernels.
The following patches are required for the backport:
d591f6804e7e1310881c9224d72247a2b65039af PCI: Wait for device readiness with Configuration RRS
ce526e1b29c70cff175e3ab8d9cb7e3f24321498 PCI: Avoid FLR for Mediatek MT7922 WiFi
Impact:
- GCP states that they would like to leverage the flexibility that the patch affords over and above the typical PCI quirks treatment.
Testing:
- Boot-tested the changes in GCP environment on amd64 hardware.
Regression potential:
- The changes affect the PCI core and the Mediatek MT7922 WiFi driver. The PCI core is affected in the device wait logic. Latency between device reset and configuration accesses may be altered. The Mediatek driver introduces a quirk that specifies those devices don't implement FLR.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106251/+subscriptions
GCP is requesting a backport of the patch d591f6804e7e "PCI: Wait for
device readiness with Configuration RRS" from upstream to the Noble and
Oracular kernels.
The following patches are required for the backport:
d591f6804e7e1310881c9224d72247a2b65039af PCI: Wait for device readiness with Configuration RRS
ce526e1b29c70cff175e3ab8d9cb7e3f24321498 PCI: Avoid FLR for Mediatek MT7922 WiFi
Impact:
- GCP states that they would like to leverage the flexibility that the patch affords over and above the typical PCI quirks treatment.
Testing:
- Boot-tested the changes in GCP environment on amd64 hardware.
Regression potential:
- The changes affect the PCI core and the Mediatek MT7922 WiFi driver. The PCI core is affected in the device wait logic. Latency between device reset and configuration accesses may be altered. The Mediatek driver introduces a quirk that specifies those devices don't implement FLR.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Noble)
Importance: Undecided
Assignee: Tim Whisonant (tswhison)
Status: In Progress
** Affects: linux (Ubuntu Oracular)
Importance: Undecided
Assignee: Tim Whisonant (tswhison)
Status: In Progress
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) => Tim Whisonant (tswhison)
** Changed in: linux (Ubuntu Oracular)
Status: New => In Progress
** Changed in: linux (Ubuntu Oracular)
Assignee: (unassigned) => Tim Whisonant (tswhison)
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106251
Title:
Backport "PCI: Wait for device readiness with Configuration RRS" to
N/O
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
In Progress
Bug description:
GCP is requesting a backport of the patch d591f6804e7e "PCI: Wait for
device readiness with Configuration RRS" from upstream to the Noble
and Oracular kernels.
The following patches are required for the backport:
d591f6804e7e1310881c9224d72247a2b65039af PCI: Wait for device readiness with Configuration RRS
ce526e1b29c70cff175e3ab8d9cb7e3f24321498 PCI: Avoid FLR for Mediatek MT7922 WiFi
Impact:
- GCP states that they would like to leverage the flexibility that the patch affords over and above the typical PCI quirks treatment.
Testing:
- Boot-tested the changes in GCP environment on amd64 hardware.
Regression potential:
- The changes affect the PCI core and the Mediatek MT7922 WiFi driver. The PCI core is affected in the device wait logic. Latency between device reset and configuration accesses may be altered. The Mediatek driver introduces a quirk that specifies those devices don't implement FLR.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106251/+subscriptions
[Bug 2100565] Re: kernel update broke Logitech G603 mouse over Bluetooth, other Bluetooth devices work fine
I'm experiencing the issue with my Logitech M570 mouse since updating to
Ubuntu 24.04.2 LTS this morning. It does not affect my Logitech M187
mouse (travel/backup). Halp pleees
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2100565
Title:
kernel update broke Logitech G603 mouse over Bluetooth, other
Bluetooth devices work fine
Status in linux package in Ubuntu:
Confirmed
Bug description:
For the full story, see this Ubuntu Discourse thread:
https://discourse.ubuntu.com/t/recent-kernel-update-broke-
logitech-g603-mouse-over-bluetooth-other-bluetooth-devices-work-
fine/55707/1
Short summary of our findings:
On Ubuntu 24.04 LTS, between kernel 6.10.14 and 6.11-rc1, my Logitech
G603 mouse breaks in that while it is paired and connected, no mouse
clicks nor mouse movements are registered in 6.11-rc1 or later. The
problem exists all the way to the current RC, 6.14-rc4. I discovered
the bug firsthand when running a recent Ubuntu apt update that jumped
me from kernel 6.8.0-51 to 6.11.0-17.
Another user not using Ubuntu reports the same problem with his non-
Logitech Bluetooth keyboard and mouse. What we have in common is the
Intel Bluetooth adapter, which is "ID 8087:0aaa Intel Corp. Bluetooth
9460/9560 Jefferson Peak (JfP)". Other users with other Intel adapters
such as the AX211 do not have the same problem. I also attached a CSR
USB-to-Bluetooth adapter to the affected system, and the mouse works
fine, even on the bad kernel versions 6.11-rc1 and up.
I did diagnostic testing using git bisect and building the LINUX
kernel from source on the affected machine. The sequence I found is
here:
git bisect start
git bisect bad 8400291e289ee6b2bf9779ff1c83a291501f017b
git bisect good 0c3836482481200ead7b416ca80c68a29cfdaabd
git bisect bad 280e36f0d5b997173d014c07484c03a7f7750668
git bisect good 0434dbe32053d07d658165be681505120c6b1abc
git bisect good 80ab5445da623540ea6303740015dd0210a06dc8
git bisect bad e2f710f97f3544df08ebe608c8157536e0ffb494
git bisect bad 586f14a6a182bbdb9404dc66464dcd8d0ac175a3
git bisect bad f6dc9214e526c2f735d93b5330f4dcd42a2b5308
git bisect good 464b99e77b3d024a319db0dabe917d04824039db
git bisect good b1c7cd6caaf6209ed9f7df59b61a2ac885eb79b3
git bisect bad fb5e4713fc185f6283ba0704edccea312253e805
git bisect bad 27489364299a2ddb5c54cd9f29a3f41bd8d151ab
git bisect good d4cc4ee48167b4c25abf49ead19412c29a1ad9f4
git bisect bad 08c22b52262041164990eef4b0e076bce173a3b2
git bisect bad f25b7fd36cc3a850e006aed686f5bbecd200de1b
The final result is that this commit is the one that breaks the mouse
for the Intel 9460/9560 adapter:
$ git bisect bad f25b7fd36cc3a850e006aed686f5bbecd200de1b
f25b7fd36cc3a850e006aed686f5bbecd200de1b is the first bad commit
commit f25b7fd36cc3a850e006aed686f5bbecd200de1b
Author: Ying Hsu <yinghsu@chromium.org>
Date: Wed May 29 08:00:00 2024 +0000
Bluetooth: Add vendor-specific packet classification for ISO data
When HCI raw sockets are opened, the Bluetooth kernel module doesn't
track CIS/BIS connections. User-space applications have to identify
ISO data by maintaining connection information and look up the mapping
for each ACL data packet received. Besides, btsnoop log captured in
kernel couldn't tell ISO data from ACL data in this case.
To avoid additional lookups, this patch introduces vendor-specific
packet classification for Intel BT controllers to distinguish
ISO data packets from ACL data packets.
Signed-off-by: Ying Hsu <yinghsu@chromium.org>
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
drivers/bluetooth/btintel.c | 25 +++++++++++++++++++++++--
include/net/bluetooth/hci_core.h | 1 +
net/bluetooth/hci_core.c | 16 ++++++++++++++++
3 files changed, 40 insertions(+), 2 deletions(-)
I am pretty sure this commit affects one file in the modules package,
but it might be in another package from the same kernel update. The
whole update from the apt.log is here:
Start-Date: 2025-02-12 12:54:16
Commandline: apt upgrade
Requested-By: me (1000)
Install: linux-hwe-6.11-tools-6.11.0-17:amd64 (6.11.0-17.17~24.04.2, automatic), linux-modules-extra-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-image-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-tools-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-hwe-6.11-headers-6.11.0-17:amd64 (6.11.0-17.17~24.04.2, automatic), linux-headers-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-modules-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic)
Upgrade: linux-headers-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-tools-common:amd64 (6.8.0-52.53, 6.8.0-53.55), base-files:amd64 (13ubuntu10.1, 13ubuntu10.2), bpftrace:amd64 (0.20.2-1ubuntu4.2, 0.20.2-1ubuntu4.3), linux-image-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-firmware:amd64 (20240318.git3b128b60-0ubuntu2.7, 20240318.git3b128b60-0ubuntu2.9), code:amd64 (1.97.0-1738713410, 1.97.1-1739197498), microsoft-edge-stable:amd64 (132.0.2957.140-1, 133.0.3065.59-1), linux-libc-dev:amd64 (6.8.0-52.53, 6.8.0-53.55)
End-Date: 2025-02-12 12:55:35
Start-Date: 2025-02-12 15:26:04
Commandline: apt autoremove
Requested-By: me (1000)
Remove: linux-modules-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-image-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-headers-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-tools-6.8.0-51:amd64 (6.8.0-51.52), linux-tools-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-headers-6.8.0-51:amd64 (6.8.0-51.52), linux-modules-extra-6.8.0-51-generic:amd64 (6.8.0-51.52)
End-Date: 2025-02-12 15:26:12
Currently, I can boot from kernel 6.10.14 and get my mouse working
again, so this is not a show-stopper bug.
I'm willing to help test/diagnose further, if needed.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-modules-6.11.0-17-generic 6.11.0-17.17~24.04.2
ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
Uname: Linux 6.11.0-17-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 27 14:33:40 2025
Dependencies:
InstallationDate: Installed on 2024-04-29 (304 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
SourcePackage: linux-hwe-6.11
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: dchang 3365 F.... pipewire
/dev/snd/controlC0: dchang 3370 F.... wireplumber
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-04-29 (309 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: Star Labs StarLite
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-17-generic root=UUID=40a0d991-e225-4f4b-8cb9-dee8d07c661a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.11.0-17-generic N/A
linux-backports-modules-6.11.0-17-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.9
Tags: noble
Uname: Linux 6.11.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 01/28/2025
dmi.bios.release: 24.8
dmi.bios.vendor: coreboot
dmi.bios.version: 25.01
dmi.board.name: StarLite
dmi.board.vendor: Star Labs
dmi.board.version: 1.0
dmi.chassis.type: 32
dmi.chassis.vendor: Star Labs
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 25.1
dmi.modalias: dmi:bvncoreboot:bvr25.01:bd01/28/2025:br24.8:efr25.1:svnStarLabs:pnStarLite:pvr1.0:rvnStarLabs:rnStarLite:rvr1.0:cvnStarLabs:ct32:cvr1.0:skuI5:
dmi.product.family: I5
dmi.product.name: StarLite
dmi.product.sku: I5
dmi.product.version: 1.0
dmi.sys.vendor: Star Labs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100565/+subscriptions
Ubuntu 24.04.2 LTS this morning. It does not affect my Logitech M187
mouse (travel/backup). Halp pleees
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2100565
Title:
kernel update broke Logitech G603 mouse over Bluetooth, other
Bluetooth devices work fine
Status in linux package in Ubuntu:
Confirmed
Bug description:
For the full story, see this Ubuntu Discourse thread:
https://discourse.ubuntu.com/t/recent-kernel-update-broke-
logitech-g603-mouse-over-bluetooth-other-bluetooth-devices-work-
fine/55707/1
Short summary of our findings:
On Ubuntu 24.04 LTS, between kernel 6.10.14 and 6.11-rc1, my Logitech
G603 mouse breaks in that while it is paired and connected, no mouse
clicks nor mouse movements are registered in 6.11-rc1 or later. The
problem exists all the way to the current RC, 6.14-rc4. I discovered
the bug firsthand when running a recent Ubuntu apt update that jumped
me from kernel 6.8.0-51 to 6.11.0-17.
Another user not using Ubuntu reports the same problem with his non-
Logitech Bluetooth keyboard and mouse. What we have in common is the
Intel Bluetooth adapter, which is "ID 8087:0aaa Intel Corp. Bluetooth
9460/9560 Jefferson Peak (JfP)". Other users with other Intel adapters
such as the AX211 do not have the same problem. I also attached a CSR
USB-to-Bluetooth adapter to the affected system, and the mouse works
fine, even on the bad kernel versions 6.11-rc1 and up.
I did diagnostic testing using git bisect and building the LINUX
kernel from source on the affected machine. The sequence I found is
here:
git bisect start
git bisect bad 8400291e289ee6b2bf9779ff1c83a291501f017b
git bisect good 0c3836482481200ead7b416ca80c68a29cfdaabd
git bisect bad 280e36f0d5b997173d014c07484c03a7f7750668
git bisect good 0434dbe32053d07d658165be681505120c6b1abc
git bisect good 80ab5445da623540ea6303740015dd0210a06dc8
git bisect bad e2f710f97f3544df08ebe608c8157536e0ffb494
git bisect bad 586f14a6a182bbdb9404dc66464dcd8d0ac175a3
git bisect bad f6dc9214e526c2f735d93b5330f4dcd42a2b5308
git bisect good 464b99e77b3d024a319db0dabe917d04824039db
git bisect good b1c7cd6caaf6209ed9f7df59b61a2ac885eb79b3
git bisect bad fb5e4713fc185f6283ba0704edccea312253e805
git bisect bad 27489364299a2ddb5c54cd9f29a3f41bd8d151ab
git bisect good d4cc4ee48167b4c25abf49ead19412c29a1ad9f4
git bisect bad 08c22b52262041164990eef4b0e076bce173a3b2
git bisect bad f25b7fd36cc3a850e006aed686f5bbecd200de1b
The final result is that this commit is the one that breaks the mouse
for the Intel 9460/9560 adapter:
$ git bisect bad f25b7fd36cc3a850e006aed686f5bbecd200de1b
f25b7fd36cc3a850e006aed686f5bbecd200de1b is the first bad commit
commit f25b7fd36cc3a850e006aed686f5bbecd200de1b
Author: Ying Hsu <yinghsu@chromium.org>
Date: Wed May 29 08:00:00 2024 +0000
Bluetooth: Add vendor-specific packet classification for ISO data
When HCI raw sockets are opened, the Bluetooth kernel module doesn't
track CIS/BIS connections. User-space applications have to identify
ISO data by maintaining connection information and look up the mapping
for each ACL data packet received. Besides, btsnoop log captured in
kernel couldn't tell ISO data from ACL data in this case.
To avoid additional lookups, this patch introduces vendor-specific
packet classification for Intel BT controllers to distinguish
ISO data packets from ACL data packets.
Signed-off-by: Ying Hsu <yinghsu@chromium.org>
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
drivers/bluetooth/btintel.c | 25 +++++++++++++++++++++++--
include/net/bluetooth/hci_core.h | 1 +
net/bluetooth/hci_core.c | 16 ++++++++++++++++
3 files changed, 40 insertions(+), 2 deletions(-)
I am pretty sure this commit affects one file in the modules package,
but it might be in another package from the same kernel update. The
whole update from the apt.log is here:
Start-Date: 2025-02-12 12:54:16
Commandline: apt upgrade
Requested-By: me (1000)
Install: linux-hwe-6.11-tools-6.11.0-17:amd64 (6.11.0-17.17~24.04.2, automatic), linux-modules-extra-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-image-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-tools-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-hwe-6.11-headers-6.11.0-17:amd64 (6.11.0-17.17~24.04.2, automatic), linux-headers-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-modules-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic)
Upgrade: linux-headers-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-tools-common:amd64 (6.8.0-52.53, 6.8.0-53.55), base-files:amd64 (13ubuntu10.1, 13ubuntu10.2), bpftrace:amd64 (0.20.2-1ubuntu4.2, 0.20.2-1ubuntu4.3), linux-image-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-firmware:amd64 (20240318.git3b128b60-0ubuntu2.7, 20240318.git3b128b60-0ubuntu2.9), code:amd64 (1.97.0-1738713410, 1.97.1-1739197498), microsoft-edge-stable:amd64 (132.0.2957.140-1, 133.0.3065.59-1), linux-libc-dev:amd64 (6.8.0-52.53, 6.8.0-53.55)
End-Date: 2025-02-12 12:55:35
Start-Date: 2025-02-12 15:26:04
Commandline: apt autoremove
Requested-By: me (1000)
Remove: linux-modules-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-image-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-headers-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-tools-6.8.0-51:amd64 (6.8.0-51.52), linux-tools-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-headers-6.8.0-51:amd64 (6.8.0-51.52), linux-modules-extra-6.8.0-51-generic:amd64 (6.8.0-51.52)
End-Date: 2025-02-12 15:26:12
Currently, I can boot from kernel 6.10.14 and get my mouse working
again, so this is not a show-stopper bug.
I'm willing to help test/diagnose further, if needed.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-modules-6.11.0-17-generic 6.11.0-17.17~24.04.2
ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
Uname: Linux 6.11.0-17-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 27 14:33:40 2025
Dependencies:
InstallationDate: Installed on 2024-04-29 (304 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
SourcePackage: linux-hwe-6.11
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: dchang 3365 F.... pipewire
/dev/snd/controlC0: dchang 3370 F.... wireplumber
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-04-29 (309 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: Star Labs StarLite
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-17-generic root=UUID=40a0d991-e225-4f4b-8cb9-dee8d07c661a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.11.0-17-generic N/A
linux-backports-modules-6.11.0-17-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.9
Tags: noble
Uname: Linux 6.11.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 01/28/2025
dmi.bios.release: 24.8
dmi.bios.vendor: coreboot
dmi.bios.version: 25.01
dmi.board.name: StarLite
dmi.board.vendor: Star Labs
dmi.board.version: 1.0
dmi.chassis.type: 32
dmi.chassis.vendor: Star Labs
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 25.1
dmi.modalias: dmi:bvncoreboot:bvr25.01:bd01/28/2025:br24.8:efr25.1:svnStarLabs:pnStarLite:pvr1.0:rvnStarLabs:rnStarLite:rvr1.0:cvnStarLabs:ct32:cvr1.0:skuI5:
dmi.product.family: I5
dmi.product.name: StarLite
dmi.product.sku: I5
dmi.product.version: 1.0
dmi.sys.vendor: Star Labs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100565/+subscriptions
[Bug 1978980] Re: [amdgpu] Wrong external screen resolution after wake up from sleep
My computer has the same problems: Kubuntu 24.04, Wayland, AMD Graphics
with Philips 499. The resolution jumps from 5120x1440 59.94 Hz to
3840x1080 after waking up from a longer break. After a restart,
everything is back to normal. I suspect it is due to the AMD driver.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1978980
Title:
[amdgpu] Wrong external screen resolution after wake up from sleep
Status in linux package in Ubuntu:
Confirmed
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04,
running KDE) I started experiencing a problem with external screen
resolution after the wake up from sleep. The monitor resolution is
small (1280x768) and doesn't respect the setting prior the sleep
(1920x1200).
After the wake up from sleep:
```
> xrandr
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm
1280x768 59.94*
# a list of lower resolutions
```
There is an error when trying to change the setting to the highest
resolution supported by the monitor (which is not included in the
above list).
```
> xrandr --output DisplayPort-1 --mode 1920x1200
xrandr: cannot find mode 1920x1200
```
After the turn off and turn on of the external monitor, the resolution
is somehow added to the xrandr list:
```
> xrandr
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm
1920x1200 59.95 +
# a list of resolutions
1280x768 59.94*
# a list of lower resolutions
```
Now it is possible to change the resolution:
```
> xrandr --output DisplayPort-1 --mode 1920x1200
# no output, the resolution was successfully changed
```
After the change, the resolution is successfully changed and xrandr
gives proper output:
```
> xrandr
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 535mm x 339mm
1920x1200 59.95*+
# a list of lower resolutions
```
The problem is not present on fresh start. However, it is consistently
present after the wake up from sleep.
What can cause the problem and how may I fix it?
Running AMD based laptop (Ryzen 7 3700U with integrated graphics), the
external monitor is connected via USB-C. There are no problems with
laptop screen resolution, only external monitor is affected.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
Uname: Linux 5.15.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu Jun 16 18:12:05 2022
DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller])
Subsystem: Lenovo ThinkPad E595 [17aa:5124]
InstallationDate: Installed on 2019-08-21 (1030 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20NE000BMC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-05-08 (39 days ago)
dmi.bios.date: 01/26/2022
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R11ET44W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20NE000BMC
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias: dmi:bvnLENOVO:bvrR11ET44W(1.24):bd01/26/2022:br1.24:efr1.24:svnLENOVO:pn20NE000BMC:pvrThinkPadE495:rvnLENOVO:rn20NE000BMC:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495:
dmi.product.family: ThinkPad E495
dmi.product.name: 20NE000BMC
dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
dmi.product.version: ThinkPad E495
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978980/+subscriptions
with Philips 499. The resolution jumps from 5120x1440 59.94 Hz to
3840x1080 after waking up from a longer break. After a restart,
everything is back to normal. I suspect it is due to the AMD driver.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1978980
Title:
[amdgpu] Wrong external screen resolution after wake up from sleep
Status in linux package in Ubuntu:
Confirmed
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04,
running KDE) I started experiencing a problem with external screen
resolution after the wake up from sleep. The monitor resolution is
small (1280x768) and doesn't respect the setting prior the sleep
(1920x1200).
After the wake up from sleep:
```
> xrandr
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm
1280x768 59.94*
# a list of lower resolutions
```
There is an error when trying to change the setting to the highest
resolution supported by the monitor (which is not included in the
above list).
```
> xrandr --output DisplayPort-1 --mode 1920x1200
xrandr: cannot find mode 1920x1200
```
After the turn off and turn on of the external monitor, the resolution
is somehow added to the xrandr list:
```
> xrandr
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm
1920x1200 59.95 +
# a list of resolutions
1280x768 59.94*
# a list of lower resolutions
```
Now it is possible to change the resolution:
```
> xrandr --output DisplayPort-1 --mode 1920x1200
# no output, the resolution was successfully changed
```
After the change, the resolution is successfully changed and xrandr
gives proper output:
```
> xrandr
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 535mm x 339mm
1920x1200 59.95*+
# a list of lower resolutions
```
The problem is not present on fresh start. However, it is consistently
present after the wake up from sleep.
What can cause the problem and how may I fix it?
Running AMD based laptop (Ryzen 7 3700U with integrated graphics), the
external monitor is connected via USB-C. There are no problems with
laptop screen resolution, only external monitor is affected.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
Uname: Linux 5.15.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu Jun 16 18:12:05 2022
DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller])
Subsystem: Lenovo ThinkPad E595 [17aa:5124]
InstallationDate: Installed on 2019-08-21 (1030 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20NE000BMC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-05-08 (39 days ago)
dmi.bios.date: 01/26/2022
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R11ET44W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20NE000BMC
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias: dmi:bvnLENOVO:bvrR11ET44W(1.24):bd01/26/2022:br1.24:efr1.24:svnLENOVO:pn20NE000BMC:pvrThinkPadE495:rvnLENOVO:rn20NE000BMC:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495:
dmi.product.family: ThinkPad E495
dmi.product.name: 20NE000BMC
dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
dmi.product.version: ThinkPad E495
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978980/+subscriptions
[Bug 2098961] Re: Severe network performance issues with Kernel 6.8.0-53 and 6.11.0-17 (Xubuntu) on Proxmox 8.3 (bnxt_en + VirtIO)
** Tags added: kernel-bug-reported-upstream
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2098961
Title:
Severe network performance issues with Kernel 6.8.0-53 and 6.11.0-17
(Xubuntu) on Proxmox 8.3 (bnxt_en + VirtIO)
Status in linux package in Ubuntu:
Triaged
Bug description:
Since upgrading to Kernel 6.8.0-53 and 6.11.0-17 on Xubuntu
22.04/24.04 VMs, we are experiencing extremely low network speeds
(100-200 KB/s) when running these VMs in a Proxmox 8.3.4 cluster with
AMD CPUs and Broadcom NetXtreme-E network adapters (bnxt_en driver).
With Kernel 6.8.0-31 inside the same Xubuntu VM, everything works as expected.
Other VMs (Debian, Ubuntu Server) running on the same Proxmox cluster are not affected.
The same Xubuntu VM, when moved to a different Proxmox cluster (Intel CPUs, Intel NICs, ZFS storage), runs fine with Kernel 6.8.0-53 and 6.11.0-17.
The issue only affects Xubuntu VMs running on a Proxmox 8.3.4 cluster with AMD CPUs, Broadcom NICs, and Ceph storage.
Expected behavior:
Network performance should be normal (10 Gbps or more) without issues.
Actual behavior:
Xubuntu VMs with Kernel 6.8.0-53 and 6.11.0-17 experience extremely slow network speeds (100-200 KB/s).
iperf3 tests show very low bandwidth (5-10 Mbps).
Disabling GSO, TSO, and GRO (ethtool -K ens18 tso off gso off gro off) did not improve performance.
Other VMs (Debian, Ubuntu Server) on the same cluster do not have this issue.
The issue disappears when booting Kernel 6.8.0-31 inside the same Xubuntu VM.
Steps to reproduce:
Proxmox environment:
Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
AMD CPU + Broadcom NetXtreme-E BCM57504 (bnxt_en driver) + Ceph storage
VMs running Xubuntu 22.04 or 24.04 with VirtIO network (virtio-net)
Inside the Xubuntu VM:
Install and boot Kernel 6.8.0-53 or Kernel 6.11.0-17
Test network performance:
wget -O /dev/null http://speed.hetzner.de/1GB.bin
iperf3 -c <server-ip> -P 4
→ Speed is extremely slow (~200 KB/s - 5 Mbps).
Reboot the VM with Kernel 6.8.0-31
sudo grub-reboot "Advanced options for Ubuntu>Ubuntu, with Linux 6.8.0-31-generic"
sudo reboot
→ Network performance returns to normal (10 Gbps+).
Hardware & environment details:
Proxmox cluster (affected environment):
Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
AMD CPUs
Broadcom NetXtreme-E BCM57504 25G SFP28 Ethernet (bnxt_en driver)
Ceph storage backend
VMs use VirtIO network adapter (virtio-net)
Bridging on Broadcom NICs
Working cluster (same Xubuntu VM, no issue):
Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
Intel CPUs
Intel I350 NICs (igb driver)
ZFS storage backend
Same Xubuntu VM works fine with Kernel 6.8.0-53 and 6.11.0-17
Debugging information:
Xubuntu VM Kernel versions (affected):
uname -r
6.8.0-53-generic
6.11.0-17-generic
Broadcom firmware version (Proxmox host):
ethtool -i enp67s0f0np0 | grep firmware
firmware-version: 229.0.154.0/pkg 229.1.123.0
dmesg output related to bnxt_en NICs (Proxmox host):
dmesg | grep bnxt
[ 2.324347] bnxt_en 0000:c5:00.0 (unnamed net_device) (uninitialized): Device requests max timeout of 60 seconds, may trigger hung task watchdog
[ 2.364280] bnxt_en 0000:c5:00.0 eth0: Broadcom BCM57504 NetXtreme-E 10Gb/25Gb/50Gb/100Gb/200Gb Ethernet found at mem b7030000, node addr 14:23:f2:5d:18:14
...
→ No critical errors, but timeout warnings and performance degradation.
Possible causes:
🔹 Regression in virtio-net or bnxt_en driver in Kernel 6.8.0-53 and 6.11.0-17
🔹 Interaction issue between virtio-net and bnxt_en on AMD + Broadcom hardware
🔹 Proxmox bridge settings on Broadcom NICs interacting with Xubuntu's Kernel 6.8.0-53 and 6.11.0-17
Next Steps & Further Tests
Since this is a production system with 200+ running VMs, we will
conduct further tests once we schedule maintenance.
Planned additional tests:
Test a fresh Ubuntu Server VM with Kernel 6.8.0-53 and 6.11.0-17 (to rule out Xubuntu-specific issues).
Verify bnxt_en and virtio-net driver versions in Kernel 6.8.0-31 vs. 6.8.0-53 and 6.11.0-17.
Check IRQ assignments and CPU affinity for VirtIO network interfaces.
📌 If this issue is already reported, please link to the relevant bug report.
📌 Otherwise, we are happy to provide further debugging information.
Summary:
Xubuntu VMs running Kernel 6.8.0-53 and 6.11.0-17 on a Proxmox 8.3.4 cluster with AMD CPUs + Broadcom NICs suffer from extreme network slowdowns (~200 KB/s).
Booting the same VM with Kernel 6.8.0-31 restores full performance.
Same Kernels work fine on Intel-based Proxmox clusters.
Disabling TSO, GSO, GRO does NOT fix the issue.
Likely a regression in virtio-net or bnxt_en.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-53-generic 6.8.0-53.55
ProcVersionSignature: Ubuntu 6.8.0-53.55-generic 6.8.12
Uname: Linux 6.8.0-53-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: sysadmin 1219 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Feb 20 11:52:51 2025
InstallationDate: Installed on 2025-02-20 (0 days ago)
InstallationMedia: Xubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827)
IwConfig:
lo no wireless extensions.
ens18 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-53-generic root=UUID=5f2acbcf-06d2-464a-83a0-12ef507709a5 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-53-generic N/A
linux-backports-modules-6.8.0-53-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.9
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-9.0
dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-9.0:cvnQEMU:ct1:cvrpc-i440fx-9.0:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-9.0
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098961/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2098961
Title:
Severe network performance issues with Kernel 6.8.0-53 and 6.11.0-17
(Xubuntu) on Proxmox 8.3 (bnxt_en + VirtIO)
Status in linux package in Ubuntu:
Triaged
Bug description:
Since upgrading to Kernel 6.8.0-53 and 6.11.0-17 on Xubuntu
22.04/24.04 VMs, we are experiencing extremely low network speeds
(100-200 KB/s) when running these VMs in a Proxmox 8.3.4 cluster with
AMD CPUs and Broadcom NetXtreme-E network adapters (bnxt_en driver).
With Kernel 6.8.0-31 inside the same Xubuntu VM, everything works as expected.
Other VMs (Debian, Ubuntu Server) running on the same Proxmox cluster are not affected.
The same Xubuntu VM, when moved to a different Proxmox cluster (Intel CPUs, Intel NICs, ZFS storage), runs fine with Kernel 6.8.0-53 and 6.11.0-17.
The issue only affects Xubuntu VMs running on a Proxmox 8.3.4 cluster with AMD CPUs, Broadcom NICs, and Ceph storage.
Expected behavior:
Network performance should be normal (10 Gbps or more) without issues.
Actual behavior:
Xubuntu VMs with Kernel 6.8.0-53 and 6.11.0-17 experience extremely slow network speeds (100-200 KB/s).
iperf3 tests show very low bandwidth (5-10 Mbps).
Disabling GSO, TSO, and GRO (ethtool -K ens18 tso off gso off gro off) did not improve performance.
Other VMs (Debian, Ubuntu Server) on the same cluster do not have this issue.
The issue disappears when booting Kernel 6.8.0-31 inside the same Xubuntu VM.
Steps to reproduce:
Proxmox environment:
Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
AMD CPU + Broadcom NetXtreme-E BCM57504 (bnxt_en driver) + Ceph storage
VMs running Xubuntu 22.04 or 24.04 with VirtIO network (virtio-net)
Inside the Xubuntu VM:
Install and boot Kernel 6.8.0-53 or Kernel 6.11.0-17
Test network performance:
wget -O /dev/null http://speed.hetzner.de/1GB.bin
iperf3 -c <server-ip> -P 4
→ Speed is extremely slow (~200 KB/s - 5 Mbps).
Reboot the VM with Kernel 6.8.0-31
sudo grub-reboot "Advanced options for Ubuntu>Ubuntu, with Linux 6.8.0-31-generic"
sudo reboot
→ Network performance returns to normal (10 Gbps+).
Hardware & environment details:
Proxmox cluster (affected environment):
Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
AMD CPUs
Broadcom NetXtreme-E BCM57504 25G SFP28 Ethernet (bnxt_en driver)
Ceph storage backend
VMs use VirtIO network adapter (virtio-net)
Bridging on Broadcom NICs
Working cluster (same Xubuntu VM, no issue):
Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
Intel CPUs
Intel I350 NICs (igb driver)
ZFS storage backend
Same Xubuntu VM works fine with Kernel 6.8.0-53 and 6.11.0-17
Debugging information:
Xubuntu VM Kernel versions (affected):
uname -r
6.8.0-53-generic
6.11.0-17-generic
Broadcom firmware version (Proxmox host):
ethtool -i enp67s0f0np0 | grep firmware
firmware-version: 229.0.154.0/pkg 229.1.123.0
dmesg output related to bnxt_en NICs (Proxmox host):
dmesg | grep bnxt
[ 2.324347] bnxt_en 0000:c5:00.0 (unnamed net_device) (uninitialized): Device requests max timeout of 60 seconds, may trigger hung task watchdog
[ 2.364280] bnxt_en 0000:c5:00.0 eth0: Broadcom BCM57504 NetXtreme-E 10Gb/25Gb/50Gb/100Gb/200Gb Ethernet found at mem b7030000, node addr 14:23:f2:5d:18:14
...
→ No critical errors, but timeout warnings and performance degradation.
Possible causes:
🔹 Regression in virtio-net or bnxt_en driver in Kernel 6.8.0-53 and 6.11.0-17
🔹 Interaction issue between virtio-net and bnxt_en on AMD + Broadcom hardware
🔹 Proxmox bridge settings on Broadcom NICs interacting with Xubuntu's Kernel 6.8.0-53 and 6.11.0-17
Next Steps & Further Tests
Since this is a production system with 200+ running VMs, we will
conduct further tests once we schedule maintenance.
Planned additional tests:
Test a fresh Ubuntu Server VM with Kernel 6.8.0-53 and 6.11.0-17 (to rule out Xubuntu-specific issues).
Verify bnxt_en and virtio-net driver versions in Kernel 6.8.0-31 vs. 6.8.0-53 and 6.11.0-17.
Check IRQ assignments and CPU affinity for VirtIO network interfaces.
📌 If this issue is already reported, please link to the relevant bug report.
📌 Otherwise, we are happy to provide further debugging information.
Summary:
Xubuntu VMs running Kernel 6.8.0-53 and 6.11.0-17 on a Proxmox 8.3.4 cluster with AMD CPUs + Broadcom NICs suffer from extreme network slowdowns (~200 KB/s).
Booting the same VM with Kernel 6.8.0-31 restores full performance.
Same Kernels work fine on Intel-based Proxmox clusters.
Disabling TSO, GSO, GRO does NOT fix the issue.
Likely a regression in virtio-net or bnxt_en.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-53-generic 6.8.0-53.55
ProcVersionSignature: Ubuntu 6.8.0-53.55-generic 6.8.12
Uname: Linux 6.8.0-53-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: sysadmin 1219 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Feb 20 11:52:51 2025
InstallationDate: Installed on 2025-02-20 (0 days ago)
InstallationMedia: Xubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827)
IwConfig:
lo no wireless extensions.
ens18 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-53-generic root=UUID=5f2acbcf-06d2-464a-83a0-12ef507709a5 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-53-generic N/A
linux-backports-modules-6.8.0-53-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.9
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-9.0
dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-9.0:cvnQEMU:ct1:cvrpc-i440fx-9.0:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-9.0
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098961/+subscriptions
[Bug 2104297] Re: not able to install a Power9 bare metal with Ubuntu 25.04 Plucky
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-power-systems
Status: New => In Progress
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2104297
Title:
not able to install a Power9 bare metal with Ubuntu 25.04 Plucky
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Bug description:
[ Impact ]
In ppc64el kernels, loading modules without any
__patchable_function_entries section would fail due to a
zero size allocation of executable memory for ftrace trampolines.
This causes boot failures when trying to boot the kernel on IBM Power 9
systems. In particular becasue IBM Power 9 tries to load i40e at boot
time, which fails.
The bug was introduced by commit eec37961a56a which landed in v6.13-rc1,
which assumed all modules have traceable functions.
[ Fix ]
Apply the following patch:
- https://lore.kernel.org/all/wlscshbqan2svtqkz5xc6v47tzndfnsvge7h4lbfn67zoplekl@elt2oxwhrp6f/T/
which has not landed in linux-next yet.
[ Test Plan ]
Compile and boot test the kernel on a Power 9 bare metal machine.
[ Where problems could occur ]
The patch simply removes an if branch which handles (incorrectly) errors during
module loading on ppc64 systems. The regression potential therefore is
very low.
-----
Not able to netboot install a Power9 bare metal. It fails because it
is not detecting network, after that the system goes to shell/busybox
```
Begin: Waiting up to 180 secs for any network device to become available ... Failure: Network device did not appear in time
done.
dhcpcd-10.1.0 starting
dev: loaded udev
[ 188.277865] 8021q: 802.1Q VLAN Support v1.8
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
Sleeping 30 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 60 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 90 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 120 seconds before retrying getting a DHCP lease
BusyBox v1.37.0 (Ubuntu 1:1.37.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2104297/+subscriptions
Status: New => In Progress
** Changed in: ubuntu-power-systems
Status: New => In Progress
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2104297
Title:
not able to install a Power9 bare metal with Ubuntu 25.04 Plucky
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Bug description:
[ Impact ]
In ppc64el kernels, loading modules without any
__patchable_function_entries section would fail due to a
zero size allocation of executable memory for ftrace trampolines.
This causes boot failures when trying to boot the kernel on IBM Power 9
systems. In particular becasue IBM Power 9 tries to load i40e at boot
time, which fails.
The bug was introduced by commit eec37961a56a which landed in v6.13-rc1,
which assumed all modules have traceable functions.
[ Fix ]
Apply the following patch:
- https://lore.kernel.org/all/wlscshbqan2svtqkz5xc6v47tzndfnsvge7h4lbfn67zoplekl@elt2oxwhrp6f/T/
which has not landed in linux-next yet.
[ Test Plan ]
Compile and boot test the kernel on a Power 9 bare metal machine.
[ Where problems could occur ]
The patch simply removes an if branch which handles (incorrectly) errors during
module loading on ppc64 systems. The regression potential therefore is
very low.
-----
Not able to netboot install a Power9 bare metal. It fails because it
is not detecting network, after that the system goes to shell/busybox
```
Begin: Waiting up to 180 secs for any network device to become available ... Failure: Network device did not appear in time
done.
dhcpcd-10.1.0 starting
dev: loaded udev
[ 188.277865] 8021q: 802.1Q VLAN Support v1.8
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
Sleeping 30 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 60 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 90 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 120 seconds before retrying getting a DHCP lease
BusyBox v1.37.0 (Ubuntu 1:1.37.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2104297/+subscriptions
[Bug 2104297] Re: not able to install a Power9 bare metal with Ubuntu 25.04 Plucky
** Description changed:
+ [ Impact ]
+
+ In ppc64el kernels, loading modules without any
+ __patchable_function_entries section would fail due to a
+ zero size allocation of executable memory for ftrace trampolines.
+ This causes boot failures when trying to boot the kernel on IBM Power 9
+ systems. In particular becasue IBM Power 9 tries to load i40e at boot
+ time, which fails.
+
+ The bug was introduced by commit eec37961a56a which landed in v6.13-rc1,
+ which assumed all modules have traceable functions.
+
+ [ Fix ]
+
+ Apply the following patch:
+ - https://lore.kernel.org/all/wlscshbqan2svtqkz5xc6v47tzndfnsvge7h4lbfn67zoplekl@elt2oxwhrp6f/T/
+ which has not landed in linux-next yet.
+
+ [ Test Plan ]
+
+ Compile and boot test the kernel on a Power 9 bare metal machine.
+
+ [ Where problems could occur ]
+
+ The patch simply removes an if branch which handles (incorrectly) errors during
+ module loading on ppc64 systems. The regression potential therefore is
+ very low.
+
+ -----
+
Not able to netboot install a Power9 bare metal. It fails because it is
not detecting network, after that the system goes to shell/busybox
```
Begin: Waiting up to 180 secs for any network device to become available ... Failure: Network device did not appear in time
done.
dhcpcd-10.1.0 starting
dev: loaded udev
[ 188.277865] 8021q: 802.1Q VLAN Support v1.8
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
Sleeping 30 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 60 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 90 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 120 seconds before retrying getting a DHCP lease
-
BusyBox v1.37.0 (Ubuntu 1:1.37.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
```
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2104297
Title:
not able to install a Power9 bare metal with Ubuntu 25.04 Plucky
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Bug description:
[ Impact ]
In ppc64el kernels, loading modules without any
__patchable_function_entries section would fail due to a
zero size allocation of executable memory for ftrace trampolines.
This causes boot failures when trying to boot the kernel on IBM Power 9
systems. In particular becasue IBM Power 9 tries to load i40e at boot
time, which fails.
The bug was introduced by commit eec37961a56a which landed in v6.13-rc1,
which assumed all modules have traceable functions.
[ Fix ]
Apply the following patch:
- https://lore.kernel.org/all/wlscshbqan2svtqkz5xc6v47tzndfnsvge7h4lbfn67zoplekl@elt2oxwhrp6f/T/
which has not landed in linux-next yet.
[ Test Plan ]
Compile and boot test the kernel on a Power 9 bare metal machine.
[ Where problems could occur ]
The patch simply removes an if branch which handles (incorrectly) errors during
module loading on ppc64 systems. The regression potential therefore is
very low.
-----
Not able to netboot install a Power9 bare metal. It fails because it
is not detecting network, after that the system goes to shell/busybox
```
Begin: Waiting up to 180 secs for any network device to become available ... Failure: Network device did not appear in time
done.
dhcpcd-10.1.0 starting
dev: loaded udev
[ 188.277865] 8021q: 802.1Q VLAN Support v1.8
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
Sleeping 30 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 60 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 90 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 120 seconds before retrying getting a DHCP lease
BusyBox v1.37.0 (Ubuntu 1:1.37.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2104297/+subscriptions
+ [ Impact ]
+
+ In ppc64el kernels, loading modules without any
+ __patchable_function_entries section would fail due to a
+ zero size allocation of executable memory for ftrace trampolines.
+ This causes boot failures when trying to boot the kernel on IBM Power 9
+ systems. In particular becasue IBM Power 9 tries to load i40e at boot
+ time, which fails.
+
+ The bug was introduced by commit eec37961a56a which landed in v6.13-rc1,
+ which assumed all modules have traceable functions.
+
+ [ Fix ]
+
+ Apply the following patch:
+ - https://lore.kernel.org/all/wlscshbqan2svtqkz5xc6v47tzndfnsvge7h4lbfn67zoplekl@elt2oxwhrp6f/T/
+ which has not landed in linux-next yet.
+
+ [ Test Plan ]
+
+ Compile and boot test the kernel on a Power 9 bare metal machine.
+
+ [ Where problems could occur ]
+
+ The patch simply removes an if branch which handles (incorrectly) errors during
+ module loading on ppc64 systems. The regression potential therefore is
+ very low.
+
+ -----
+
Not able to netboot install a Power9 bare metal. It fails because it is
not detecting network, after that the system goes to shell/busybox
```
Begin: Waiting up to 180 secs for any network device to become available ... Failure: Network device did not appear in time
done.
dhcpcd-10.1.0 starting
dev: loaded udev
[ 188.277865] 8021q: 802.1Q VLAN Support v1.8
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
Sleeping 30 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 60 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 90 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 120 seconds before retrying getting a DHCP lease
-
BusyBox v1.37.0 (Ubuntu 1:1.37.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
```
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2104297
Title:
not able to install a Power9 bare metal with Ubuntu 25.04 Plucky
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Bug description:
[ Impact ]
In ppc64el kernels, loading modules without any
__patchable_function_entries section would fail due to a
zero size allocation of executable memory for ftrace trampolines.
This causes boot failures when trying to boot the kernel on IBM Power 9
systems. In particular becasue IBM Power 9 tries to load i40e at boot
time, which fails.
The bug was introduced by commit eec37961a56a which landed in v6.13-rc1,
which assumed all modules have traceable functions.
[ Fix ]
Apply the following patch:
- https://lore.kernel.org/all/wlscshbqan2svtqkz5xc6v47tzndfnsvge7h4lbfn67zoplekl@elt2oxwhrp6f/T/
which has not landed in linux-next yet.
[ Test Plan ]
Compile and boot test the kernel on a Power 9 bare metal machine.
[ Where problems could occur ]
The patch simply removes an if branch which handles (incorrectly) errors during
module loading on ppc64 systems. The regression potential therefore is
very low.
-----
Not able to netboot install a Power9 bare metal. It fails because it
is not detecting network, after that the system goes to shell/busybox
```
Begin: Waiting up to 180 secs for any network device to become available ... Failure: Network device did not appear in time
done.
dhcpcd-10.1.0 starting
dev: loaded udev
[ 188.277865] 8021q: 802.1Q VLAN Support v1.8
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
Sleeping 30 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 60 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 90 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 120 seconds before retrying getting a DHCP lease
BusyBox v1.37.0 (Ubuntu 1:1.37.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2104297/+subscriptions
[Bug 2106209] [NEW] Starting disabling Bluetooth crashes the system
Public bug reported:
Starting / disabling Bluetooth crashes the system
When you start bluetooth then disable it for somerson and then you might start it again the system crashes sometimes. This has been an issue for some time now but i don't think ubuntu 24.10 suffered from this
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-image-6.14.0-13-generic 6.14.0-13.13
ProcVersionSignature: Ubuntu 6.14.0-13.13-generic 6.14.0
Uname: Linux 6.14.0-13-generic x86_64
ApportVersion: 2.32.0-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: levan 2495 F.... wireplumber
/dev/snd/seq: levan 2490 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 4 11:35:33 2025
InstallationDate: Installed on 2024-09-03 (213 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD
Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: Dell Inc. Latitude 5490
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-13-generic root=UUID=1eb2c982-5bda-4290-a15b-db32bb3fb452 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.14.0-13-generic N/A
linux-backports-modules-6.14.0-13-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to plucky on 2025-04-02 (2 days ago)
dmi.bios.date: 11/06/2024
dmi.bios.release: 1.38
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.38.0
dmi.board.name: 08NJ82
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: W36301498
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.38.0:bd11/06/2024:br1.38:svnDellInc.:pnLatitude5490:pvr:rvnDellInc.:rn08NJ82:rvrA00:cvnDellInc.:ct10:cvr:sku0816:
dmi.product.family: Latitude
dmi.product.name: Latitude 5490
dmi.product.sku: 0816
dmi.sys.vendor: Dell Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug plucky wayland-session
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106209
Title:
Starting disabling Bluetooth crashes the system
Status in linux package in Ubuntu:
New
Bug description:
Starting / disabling Bluetooth crashes the system
When you start bluetooth then disable it for somerson and then you might start it again the system crashes sometimes. This has been an issue for some time now but i don't think ubuntu 24.10 suffered from this
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-image-6.14.0-13-generic 6.14.0-13.13
ProcVersionSignature: Ubuntu 6.14.0-13.13-generic 6.14.0
Uname: Linux 6.14.0-13-generic x86_64
ApportVersion: 2.32.0-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: levan 2495 F.... wireplumber
/dev/snd/seq: levan 2490 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 4 11:35:33 2025
InstallationDate: Installed on 2024-09-03 (213 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD
Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: Dell Inc. Latitude 5490
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-13-generic root=UUID=1eb2c982-5bda-4290-a15b-db32bb3fb452 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.14.0-13-generic N/A
linux-backports-modules-6.14.0-13-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to plucky on 2025-04-02 (2 days ago)
dmi.bios.date: 11/06/2024
dmi.bios.release: 1.38
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.38.0
dmi.board.name: 08NJ82
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: W36301498
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.38.0:bd11/06/2024:br1.38:svnDellInc.:pnLatitude5490:pvr:rvnDellInc.:rn08NJ82:rvrA00:cvnDellInc.:ct10:cvr:sku0816:
dmi.product.family: Latitude
dmi.product.name: Latitude 5490
dmi.product.sku: 0816
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106209/+subscriptions
Starting / disabling Bluetooth crashes the system
When you start bluetooth then disable it for somerson and then you might start it again the system crashes sometimes. This has been an issue for some time now but i don't think ubuntu 24.10 suffered from this
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-image-6.14.0-13-generic 6.14.0-13.13
ProcVersionSignature: Ubuntu 6.14.0-13.13-generic 6.14.0
Uname: Linux 6.14.0-13-generic x86_64
ApportVersion: 2.32.0-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: levan 2495 F.... wireplumber
/dev/snd/seq: levan 2490 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 4 11:35:33 2025
InstallationDate: Installed on 2024-09-03 (213 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD
Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: Dell Inc. Latitude 5490
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-13-generic root=UUID=1eb2c982-5bda-4290-a15b-db32bb3fb452 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.14.0-13-generic N/A
linux-backports-modules-6.14.0-13-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to plucky on 2025-04-02 (2 days ago)
dmi.bios.date: 11/06/2024
dmi.bios.release: 1.38
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.38.0
dmi.board.name: 08NJ82
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: W36301498
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.38.0:bd11/06/2024:br1.38:svnDellInc.:pnLatitude5490:pvr:rvnDellInc.:rn08NJ82:rvrA00:cvnDellInc.:ct10:cvr:sku0816:
dmi.product.family: Latitude
dmi.product.name: Latitude 5490
dmi.product.sku: 0816
dmi.sys.vendor: Dell Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug plucky wayland-session
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106209
Title:
Starting disabling Bluetooth crashes the system
Status in linux package in Ubuntu:
New
Bug description:
Starting / disabling Bluetooth crashes the system
When you start bluetooth then disable it for somerson and then you might start it again the system crashes sometimes. This has been an issue for some time now but i don't think ubuntu 24.10 suffered from this
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-image-6.14.0-13-generic 6.14.0-13.13
ProcVersionSignature: Ubuntu 6.14.0-13.13-generic 6.14.0
Uname: Linux 6.14.0-13-generic x86_64
ApportVersion: 2.32.0-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: levan 2495 F.... wireplumber
/dev/snd/seq: levan 2490 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 4 11:35:33 2025
InstallationDate: Installed on 2024-09-03 (213 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD
Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: Dell Inc. Latitude 5490
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-13-generic root=UUID=1eb2c982-5bda-4290-a15b-db32bb3fb452 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.14.0-13-generic N/A
linux-backports-modules-6.14.0-13-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to plucky on 2025-04-02 (2 days ago)
dmi.bios.date: 11/06/2024
dmi.bios.release: 1.38
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.38.0
dmi.board.name: 08NJ82
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: W36301498
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.38.0:bd11/06/2024:br1.38:svnDellInc.:pnLatitude5490:pvr:rvnDellInc.:rn08NJ82:rvrA00:cvnDellInc.:ct10:cvr:sku0816:
dmi.product.family: Latitude
dmi.product.name: Latitude 5490
dmi.product.sku: 0816
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106209/+subscriptions
Подписаться на:
Сообщения (Atom)