** Changed in: linux (Ubuntu Resolute)
Status: New => Fix Committed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147007
Title:
Resolute kernel 7.0-10 kernel hangs on chattr stress test
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Resolute:
Fix Committed
Bug description:
Summary:
Resolute Linux kernel 7.0-10 locks up on stress-ng chattr stress test
on am64, arm64, s390x, ppc64 (and maybe more) architectures.
Test procedure:
Install the Resulute daily server ISO into a VM, 8 CPU threads, 4GB
RAM, 25GB disk storage using ext4 as the file system. I'm using a
Intel(R) Core(TM) Ultra 9 285K for my server.
enable deb-src in /etc/apt/sources.list.d/*
sudo apt-get update
sudo apt-get build-dep stress-ng
git clone https://github.com/ColinIanKing/stress-ng
cd stress-ng
make clean
make -j 8
make verify-test-all
The chattr test takes a while and after a couple of minutes, the
chattr stressor produces repeated kernel errors:
INFO: task jbd2/dm-0.8:337 blocked for more than 122 seconds
This occurs on a range of architectures and is a regression from the
previous 6.x kernel results
This is a release blocker kernel issue in my opinon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147007/+subscriptions
суббота
[Bug 1763144] Re: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows
I am experiencing significant slowdowns for my X220 and T480 with noble.
And I believe this is the reasons, but I am not sure. My only solution
so far is to disable thermald completely.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1763144
Title:
Significantly lower power and thermal limits on ThinkPad T480s (and
probably others) than on Windows
Status in linux package in Ubuntu:
Invalid
Status in thermald package in Ubuntu:
Incomplete
Bug description:
A ThinkPad T480s under windows has a power limit of 44W, both short
and long term, with a thermal maximum of about 93C or so. Under Linux,
the power limits are 44W and 15W (short) or so, and the thermal limit
is 80C, causing a significant performance loss.
Looking at MSR and MCHBAR values, we can see that the values are
correctly at 44W in the MSR, but the MCHBAR is set to a lower value:
$ sudo rdmsr -a 0x610
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
$ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
0x0042816000dd8078
Setting the MCHBAR to the same value as the MSR register solves the problem. At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.
The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
-d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
in performance comparative to Windows.
Most of the analysis is based on the analysis in
https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/
This applies to all bionic kernels I have tested so far, including
Ubuntu 4.15.0-13.14-generic 4.15.10
---
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/pcmC2D0p: jak 5881 F...m pulseaudio
/dev/snd/controlC2: jak 5881 F.... pulseaudio
/dev/snd/controlC1: jak 5881 F.... pulseaudio
/dev/snd/controlC0: jak 5881 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-03-14 (28 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
MachineType: LENOVO 20L8S02D00
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware 1.173
Tags: bionic
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/22/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N22ET31W (1.08 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L8S02D00
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.modalias: dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480s
dmi.product.name: 20L8S02D00
dmi.product.version: ThinkPad T480s
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763144/+subscriptions
And I believe this is the reasons, but I am not sure. My only solution
so far is to disable thermald completely.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1763144
Title:
Significantly lower power and thermal limits on ThinkPad T480s (and
probably others) than on Windows
Status in linux package in Ubuntu:
Invalid
Status in thermald package in Ubuntu:
Incomplete
Bug description:
A ThinkPad T480s under windows has a power limit of 44W, both short
and long term, with a thermal maximum of about 93C or so. Under Linux,
the power limits are 44W and 15W (short) or so, and the thermal limit
is 80C, causing a significant performance loss.
Looking at MSR and MCHBAR values, we can see that the values are
correctly at 44W in the MSR, but the MCHBAR is set to a lower value:
$ sudo rdmsr -a 0x610
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
$ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
0x0042816000dd8078
Setting the MCHBAR to the same value as the MSR register solves the problem. At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.
The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
-d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
in performance comparative to Windows.
Most of the analysis is based on the analysis in
https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/
This applies to all bionic kernels I have tested so far, including
Ubuntu 4.15.0-13.14-generic 4.15.10
---
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/pcmC2D0p: jak 5881 F...m pulseaudio
/dev/snd/controlC2: jak 5881 F.... pulseaudio
/dev/snd/controlC1: jak 5881 F.... pulseaudio
/dev/snd/controlC0: jak 5881 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-03-14 (28 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
MachineType: LENOVO 20L8S02D00
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware 1.173
Tags: bionic
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/22/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N22ET31W (1.08 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L8S02D00
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.modalias: dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480s
dmi.product.name: 20L8S02D00
dmi.product.version: ThinkPad T480s
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763144/+subscriptions
пятница
[Bug 1786013] Autopkgtest regression report (linux-meta-nvidia-6.17/6.17.0-1015.15)
All autopkgtests for the newly accepted linux-meta-nvidia-6.17 (6.17.0-1015.15) for noble have finished running.
The following regressions have been reported in tests triggered by the package:
linux-nvidia-6.17/6.17.0-1015.15 (arm64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/noble/update_excuses.html#linux-meta-nvidia-6.17
[1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest-
failure/
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
The following regressions have been reported in tests triggered by the package:
linux-nvidia-6.17/6.17.0-1015.15 (arm64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/noble/update_excuses.html#linux-meta-nvidia-6.17
[1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest-
failure/
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-nvidia-6.8/6.8.0-1051.54~22.04.1)
All autopkgtests for the newly accepted linux-meta-nvidia-6.8 (6.8.0-1051.54~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-nvidia-6.8/6.8.0-1051.54~22.04.1 (arm64)
snapd/2.73+ubuntu22.04.1 (arm64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/jammy/update_excuses.html#linux-meta-nvidia-6.8
[1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest-
failure/
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
The following regressions have been reported in tests triggered by the package:
linux-nvidia-6.8/6.8.0-1051.54~22.04.1 (arm64)
snapd/2.73+ubuntu22.04.1 (arm64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/jammy/update_excuses.html#linux-meta-nvidia-6.8
[1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest-
failure/
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-azure-nvidia/6.8.0-1033.36)
All autopkgtests for the newly accepted linux-meta-azure-nvidia (6.8.0-1033.36) for noble have finished running.
The following regressions have been reported in tests triggered by the package:
linux-azure-nvidia/6.8.0-1033.36 (arm64)
systemd/255.4-1ubuntu8.14 (arm64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/noble/update_excuses.html#linux-meta-azure-nvidia
[1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest-
failure/
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
The following regressions have been reported in tests triggered by the package:
linux-azure-nvidia/6.8.0-1033.36 (arm64)
systemd/255.4-1ubuntu8.14 (arm64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/noble/update_excuses.html#linux-meta-azure-nvidia
[1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest-
failure/
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 2146761] Re: Bluetooth audio headset regression on 7.0.0-10-generic: Shokz OpenComm2 disconnects, works on 6.19.0-6-generic
Confirmed this fix on Ubuntu 26.04 (resolute), kernel 7.0.0-7-generic
(7.0.0-rc3).
Built bluetooth.ko from linux-source-7.0.0 with upstream commit
537b583e6af82ead3f7a1074d51d5765f647ff01 ("Bluetooth: L2CAP: Fix
regressions caused by reusing ident") applied to
net/bluetooth/l2cap_core.c and include/net/bluetooth/l2cap.h. Loaded the
patched module and the issue is resolved — A2DP transport channel
completes configuration, audio works, and HFP/HSP connects as well.
Without the fix, the L2CAP Configure Request for the AVDTP transport
channel reuses ident 1 (already used by the signaling channel), and the
headset drops it silently. This stalls A2DP for ~30 seconds until the
headset ABORTs.
Affected devices confirmed so far: Marshall Major IV, Bose QC35.
Detailed trace analysis and btmon captures in the upstream BlueZ issue:
https://github.com/bluez/bluez/issues/1992
** Bug watch added: github.com/bluez/bluez/issues #1992
https://github.com/bluez/bluez/issues/1992
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146761
Title:
Bluetooth audio headset regression on 7.0.0-10-generic: Shokz
OpenComm2 disconnects, works on 6.19.0-6-generic
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Resolute:
Confirmed
Bug description:
After the system update on March 29, 2026, my Bluetooth audio headset
(Shokz OpenComm2 / OpenComm2 by Shokz_II) stopped working on kernel
7.0.0-10-generic.
The headset either disconnects within about 10 seconds after
connect, or the connection is canceled and audio profiles fail to come
up.
If I reboot the same machine into the previous kernel
6.19.0-6-generic, the headset works again without changing userspace
packages or pairing state.
This looks like a kernel regression in 7.0.0-10-generic.
Working kernel:
6.19.0-6-generic
Linux book 6.19.0-6-generic #6-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 18 15:48:21 UTC 2026 x86_64 GNU/Linux
Broken kernel:
7.0.0-10-generic
From previous boot kernel log:
Linux version 7.0.0-10-generic (buildd@lcy02-amd64-051) (x86_64-linux-gnu-gcc (Ubuntu 15.2.0-15ubuntu2) 15.2.0, GNU ld (GNU Binutils for Ubuntu) 2.46) #10-Ubuntu SMP
PREEMPT_DYNAMIC Thu Mar 19 10:24:42 UTC 2026 (Ubuntu 7.0.0-10.10-generic 7.0.0-rc4)
Userspace versions at the time:
bluez 5.85-4
pipewire 1.6.2-1ubuntu1
wireplumber 0.5.13-1ubuntu1
gnome-shell 50.0-0ubuntu2
same userspace + new kernel fails.
Steps to reproduce:
1. Boot kernel 7.0.0-10-generic.
2. Power on the Shokz OpenComm2 headset.
3. Connect it from GNOME Settings or with bluetoothctl.
4. Wait a few seconds.
Expected result:
The headset should stay connected and its audio profile should become usable.
Actual result:
- Another Bluetooth device (Logitech Pebble mouse) still works, so this is not a total Bluetooth failure.
- I tested re-pairing the headset and rebooting the headset; that did not help on 7.0.0-10-generic.
- I tested disabling Bluetooth headset autoswitch behavior in WirePlumber; that did not fix it on 7.0.0-10-generic.
- There is no GNOME Shell crash here; this does not appear to be the old gnome-shell bug 2138654.
Relevant bluetoothd log lines from the broken boot:
- src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to A0:0C:C3:E1:3F:7C: Connection reset by peer (104)
- src/service.c:btd_service_connect() a2dp-sink profile connect failed for A0:0C:C3:E1:3F:7C: Device or resource busy
- profiles/audio/avdtp.c:avdtp_connect_cb() connect to A0:0C:C3:E1:3F:7C: Connection refused (111)
- profiles/audio/avctp.c:avctp_connect_cb() HUP or ERR on socket: Connection refused (111)
- profiles/audio/avctp.c:avctp_connect_cb() HUP or ERR on socket: Connection timed out (110)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146761/+subscriptions
(7.0.0-rc3).
Built bluetooth.ko from linux-source-7.0.0 with upstream commit
537b583e6af82ead3f7a1074d51d5765f647ff01 ("Bluetooth: L2CAP: Fix
regressions caused by reusing ident") applied to
net/bluetooth/l2cap_core.c and include/net/bluetooth/l2cap.h. Loaded the
patched module and the issue is resolved — A2DP transport channel
completes configuration, audio works, and HFP/HSP connects as well.
Without the fix, the L2CAP Configure Request for the AVDTP transport
channel reuses ident 1 (already used by the signaling channel), and the
headset drops it silently. This stalls A2DP for ~30 seconds until the
headset ABORTs.
Affected devices confirmed so far: Marshall Major IV, Bose QC35.
Detailed trace analysis and btmon captures in the upstream BlueZ issue:
https://github.com/bluez/bluez/issues/1992
** Bug watch added: github.com/bluez/bluez/issues #1992
https://github.com/bluez/bluez/issues/1992
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146761
Title:
Bluetooth audio headset regression on 7.0.0-10-generic: Shokz
OpenComm2 disconnects, works on 6.19.0-6-generic
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Resolute:
Confirmed
Bug description:
After the system update on March 29, 2026, my Bluetooth audio headset
(Shokz OpenComm2 / OpenComm2 by Shokz_II) stopped working on kernel
7.0.0-10-generic.
The headset either disconnects within about 10 seconds after
connect, or the connection is canceled and audio profiles fail to come
up.
If I reboot the same machine into the previous kernel
6.19.0-6-generic, the headset works again without changing userspace
packages or pairing state.
This looks like a kernel regression in 7.0.0-10-generic.
Working kernel:
6.19.0-6-generic
Linux book 6.19.0-6-generic #6-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 18 15:48:21 UTC 2026 x86_64 GNU/Linux
Broken kernel:
7.0.0-10-generic
From previous boot kernel log:
Linux version 7.0.0-10-generic (buildd@lcy02-amd64-051) (x86_64-linux-gnu-gcc (Ubuntu 15.2.0-15ubuntu2) 15.2.0, GNU ld (GNU Binutils for Ubuntu) 2.46) #10-Ubuntu SMP
PREEMPT_DYNAMIC Thu Mar 19 10:24:42 UTC 2026 (Ubuntu 7.0.0-10.10-generic 7.0.0-rc4)
Userspace versions at the time:
bluez 5.85-4
pipewire 1.6.2-1ubuntu1
wireplumber 0.5.13-1ubuntu1
gnome-shell 50.0-0ubuntu2
same userspace + new kernel fails.
Steps to reproduce:
1. Boot kernel 7.0.0-10-generic.
2. Power on the Shokz OpenComm2 headset.
3. Connect it from GNOME Settings or with bluetoothctl.
4. Wait a few seconds.
Expected result:
The headset should stay connected and its audio profile should become usable.
Actual result:
- Another Bluetooth device (Logitech Pebble mouse) still works, so this is not a total Bluetooth failure.
- I tested re-pairing the headset and rebooting the headset; that did not help on 7.0.0-10-generic.
- I tested disabling Bluetooth headset autoswitch behavior in WirePlumber; that did not fix it on 7.0.0-10-generic.
- There is no GNOME Shell crash here; this does not appear to be the old gnome-shell bug 2138654.
Relevant bluetoothd log lines from the broken boot:
- src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to A0:0C:C3:E1:3F:7C: Connection reset by peer (104)
- src/service.c:btd_service_connect() a2dp-sink profile connect failed for A0:0C:C3:E1:3F:7C: Device or resource busy
- profiles/audio/avdtp.c:avdtp_connect_cb() connect to A0:0C:C3:E1:3F:7C: Connection refused (111)
- profiles/audio/avctp.c:avctp_connect_cb() HUP or ERR on socket: Connection refused (111)
- profiles/audio/avctp.c:avctp_connect_cb() HUP or ERR on socket: Connection timed out (110)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146761/+subscriptions
[Bug 2146761] Re: Bluetooth audio headset regression on 7.0.0-10-generic: Shokz OpenComm2 disconnects, works on 6.19.0-6-generic
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146761
Title:
Bluetooth audio headset regression on 7.0.0-10-generic: Shokz
OpenComm2 disconnects, works on 6.19.0-6-generic
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Resolute:
Confirmed
Bug description:
After the system update on March 29, 2026, my Bluetooth audio headset
(Shokz OpenComm2 / OpenComm2 by Shokz_II) stopped working on kernel
7.0.0-10-generic.
The headset either disconnects within about 10 seconds after
connect, or the connection is canceled and audio profiles fail to come
up.
If I reboot the same machine into the previous kernel
6.19.0-6-generic, the headset works again without changing userspace
packages or pairing state.
This looks like a kernel regression in 7.0.0-10-generic.
Working kernel:
6.19.0-6-generic
Linux book 6.19.0-6-generic #6-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 18 15:48:21 UTC 2026 x86_64 GNU/Linux
Broken kernel:
7.0.0-10-generic
From previous boot kernel log:
Linux version 7.0.0-10-generic (buildd@lcy02-amd64-051) (x86_64-linux-gnu-gcc (Ubuntu 15.2.0-15ubuntu2) 15.2.0, GNU ld (GNU Binutils for Ubuntu) 2.46) #10-Ubuntu SMP
PREEMPT_DYNAMIC Thu Mar 19 10:24:42 UTC 2026 (Ubuntu 7.0.0-10.10-generic 7.0.0-rc4)
Userspace versions at the time:
bluez 5.85-4
pipewire 1.6.2-1ubuntu1
wireplumber 0.5.13-1ubuntu1
gnome-shell 50.0-0ubuntu2
same userspace + new kernel fails.
Steps to reproduce:
1. Boot kernel 7.0.0-10-generic.
2. Power on the Shokz OpenComm2 headset.
3. Connect it from GNOME Settings or with bluetoothctl.
4. Wait a few seconds.
Expected result:
The headset should stay connected and its audio profile should become usable.
Actual result:
- Another Bluetooth device (Logitech Pebble mouse) still works, so this is not a total Bluetooth failure.
- I tested re-pairing the headset and rebooting the headset; that did not help on 7.0.0-10-generic.
- I tested disabling Bluetooth headset autoswitch behavior in WirePlumber; that did not fix it on 7.0.0-10-generic.
- There is no GNOME Shell crash here; this does not appear to be the old gnome-shell bug 2138654.
Relevant bluetoothd log lines from the broken boot:
- src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to A0:0C:C3:E1:3F:7C: Connection reset by peer (104)
- src/service.c:btd_service_connect() a2dp-sink profile connect failed for A0:0C:C3:E1:3F:7C: Device or resource busy
- profiles/audio/avdtp.c:avdtp_connect_cb() connect to A0:0C:C3:E1:3F:7C: Connection refused (111)
- profiles/audio/avctp.c:avctp_connect_cb() HUP or ERR on socket: Connection refused (111)
- profiles/audio/avctp.c:avctp_connect_cb() HUP or ERR on socket: Connection timed out (110)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146761/+subscriptions
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146761
Title:
Bluetooth audio headset regression on 7.0.0-10-generic: Shokz
OpenComm2 disconnects, works on 6.19.0-6-generic
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Resolute:
Confirmed
Bug description:
After the system update on March 29, 2026, my Bluetooth audio headset
(Shokz OpenComm2 / OpenComm2 by Shokz_II) stopped working on kernel
7.0.0-10-generic.
The headset either disconnects within about 10 seconds after
connect, or the connection is canceled and audio profiles fail to come
up.
If I reboot the same machine into the previous kernel
6.19.0-6-generic, the headset works again without changing userspace
packages or pairing state.
This looks like a kernel regression in 7.0.0-10-generic.
Working kernel:
6.19.0-6-generic
Linux book 6.19.0-6-generic #6-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 18 15:48:21 UTC 2026 x86_64 GNU/Linux
Broken kernel:
7.0.0-10-generic
From previous boot kernel log:
Linux version 7.0.0-10-generic (buildd@lcy02-amd64-051) (x86_64-linux-gnu-gcc (Ubuntu 15.2.0-15ubuntu2) 15.2.0, GNU ld (GNU Binutils for Ubuntu) 2.46) #10-Ubuntu SMP
PREEMPT_DYNAMIC Thu Mar 19 10:24:42 UTC 2026 (Ubuntu 7.0.0-10.10-generic 7.0.0-rc4)
Userspace versions at the time:
bluez 5.85-4
pipewire 1.6.2-1ubuntu1
wireplumber 0.5.13-1ubuntu1
gnome-shell 50.0-0ubuntu2
same userspace + new kernel fails.
Steps to reproduce:
1. Boot kernel 7.0.0-10-generic.
2. Power on the Shokz OpenComm2 headset.
3. Connect it from GNOME Settings or with bluetoothctl.
4. Wait a few seconds.
Expected result:
The headset should stay connected and its audio profile should become usable.
Actual result:
- Another Bluetooth device (Logitech Pebble mouse) still works, so this is not a total Bluetooth failure.
- I tested re-pairing the headset and rebooting the headset; that did not help on 7.0.0-10-generic.
- I tested disabling Bluetooth headset autoswitch behavior in WirePlumber; that did not fix it on 7.0.0-10-generic.
- There is no GNOME Shell crash here; this does not appear to be the old gnome-shell bug 2138654.
Relevant bluetoothd log lines from the broken boot:
- src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to A0:0C:C3:E1:3F:7C: Connection reset by peer (104)
- src/service.c:btd_service_connect() a2dp-sink profile connect failed for A0:0C:C3:E1:3F:7C: Device or resource busy
- profiles/audio/avdtp.c:avdtp_connect_cb() connect to A0:0C:C3:E1:3F:7C: Connection refused (111)
- profiles/audio/avctp.c:avctp_connect_cb() HUP or ERR on socket: Connection refused (111)
- profiles/audio/avctp.c:avctp_connect_cb() HUP or ERR on socket: Connection timed out (110)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146761/+subscriptions
[Bug 2147174] Re: ThinkBook X G2 IAH: Intel IPU6 OV02C10 camera not working
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147174
Title:
ThinkBook X G2 IAH: Intel IPU6 OV02C10 camera not working
Status in linux package in Ubuntu:
New
Bug description:
Laptop: Lenovo ThinkBook X G2 IAH (21TU)
Camera: Intel IPU6 + OV02C10 (OVTI02C1:00)
Release: Ubuntu 26.04 (resolute)
Kernel: 6.19.0-6-generic
Problem:
The internal camera is detected by the system, but direct camera output is unusable.
System state:
- The Intel IPU6 device is detected.
- The OV02C10 sensor is detected.
- The camera is enumerated by PipeWire/libcamera as ov02c10.
- Direct camera capture is still broken.
What I see:
- The camera is present, but frames are white or flat gray instead of a real image.
- The problem reproduces with direct Intel HAL capture using icamerasrc device-name=ov02c10-uf.
- The problem is not limited to one application.
Relevant log messages:
- No static properties available for 'ov02c10'
- Configuration file 'ov02c10.yaml' not found
- Failed to create camera sensor helper for ov02c10
- Failed to open file /run/camera/ov02c10-uf_VIDEO.aiqd, error No such file or directory
What I tested:
- Direct icamerasrc capture with device-name=ov02c10-uf
- Different shipped OV02C10 tuning variants available in the installed camera stack
- None produced a correct image
Expected result:
A normal camera image.
Actual result:
The camera is detected, but the produced image is white or flat gray.
Additional system details:
- sys_vendor: LENOVO
- product_name: 21TU
- product_version: ThinkBook X G2 IAH
- product_sku: LENOVO_MT_21TU_BU_idea_FM_ThinkBook X G2 IAH
Installed camera-related packages include:
- intel-ipu6-dkms 0~git202602030803.cde4eb44-0ubuntu1
- libcamhal-ipu6epmtl 0~git202601200757.9899efa~ubuntu26.04.1
- libcamhal-common 0~git202601200757.9899efa~ubuntu26.04.1
- gstreamer1.0-icamera 0~git202509261737.4fb31db~ubuntu26.04.1
- libcamera-ipa 0.7.0-1ubuntu2
- libcamera0.7 0.7.0-1ubuntu2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147174/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147174
Title:
ThinkBook X G2 IAH: Intel IPU6 OV02C10 camera not working
Status in linux package in Ubuntu:
New
Bug description:
Laptop: Lenovo ThinkBook X G2 IAH (21TU)
Camera: Intel IPU6 + OV02C10 (OVTI02C1:00)
Release: Ubuntu 26.04 (resolute)
Kernel: 6.19.0-6-generic
Problem:
The internal camera is detected by the system, but direct camera output is unusable.
System state:
- The Intel IPU6 device is detected.
- The OV02C10 sensor is detected.
- The camera is enumerated by PipeWire/libcamera as ov02c10.
- Direct camera capture is still broken.
What I see:
- The camera is present, but frames are white or flat gray instead of a real image.
- The problem reproduces with direct Intel HAL capture using icamerasrc device-name=ov02c10-uf.
- The problem is not limited to one application.
Relevant log messages:
- No static properties available for 'ov02c10'
- Configuration file 'ov02c10.yaml' not found
- Failed to create camera sensor helper for ov02c10
- Failed to open file /run/camera/ov02c10-uf_VIDEO.aiqd, error No such file or directory
What I tested:
- Direct icamerasrc capture with device-name=ov02c10-uf
- Different shipped OV02C10 tuning variants available in the installed camera stack
- None produced a correct image
Expected result:
A normal camera image.
Actual result:
The camera is detected, but the produced image is white or flat gray.
Additional system details:
- sys_vendor: LENOVO
- product_name: 21TU
- product_version: ThinkBook X G2 IAH
- product_sku: LENOVO_MT_21TU_BU_idea_FM_ThinkBook X G2 IAH
Installed camera-related packages include:
- intel-ipu6-dkms 0~git202602030803.cde4eb44-0ubuntu1
- libcamhal-ipu6epmtl 0~git202601200757.9899efa~ubuntu26.04.1
- libcamhal-common 0~git202601200757.9899efa~ubuntu26.04.1
- gstreamer1.0-icamera 0~git202509261737.4fb31db~ubuntu26.04.1
- libcamera-ipa 0.7.0-1ubuntu2
- libcamera0.7 0.7.0-1ubuntu2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147174/+subscriptions
[Bug 2147193] Re: [Regression] WiFi hard-blocked on MSI Vector A16 with MT7922 on 6.17 HWE kernel (works on 6.8 GA)
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147193
Title:
[Regression] WiFi hard-blocked on MSI Vector A16 with MT7922 on 6.17
HWE kernel (works on 6.8 GA)
Status in linux package in Ubuntu:
New
Bug description:
Ubuntu 24.04.4 LTS
Kernel: 6.17.0-20-generic (HWE) — BROKEN
Kernel: 6.8.0-107-generic (GA) — WORKING
Hardware: MSI Vector A16 HX A8WHG
WiFi: MediaTek MT7922 (PCI ID: 14c3:7922), driver: mt7921e
BIOS: E15MMAMS.104
Problem:
After the 6.17 HWE kernel update, WiFi is permanently hard-blocked.
rfkill shows "Hard blocked: yes" with RFKILL_HW_BLOCK_REASON=0x1.
The regression is caused by mt7921_mcu_wf_rf_pin_ctrl() added in
kernels after 6.8, which polls the MT7922 MCU for RF pin state.
The MCU incorrectly reports "blocked" on this MSI laptop.
Additionally, MSI BIOS has a bug where WLAN ACPI objects are defined
in two SSDT tables (SSDT4 MSI_WLAN and SSDT24 AMD GPPRPL), causing
AE_ALREADY_EXISTS errors. This may contribute to incorrect hardware
state, though eliminating these errors via SSDT override did not
resolve the hard block.
Workaround:
Use kernel 6.8.0-107-generic (GA kernel). WiFi works perfectly.
Expected fix:
The upstream fix in kernel 6.19 (revert of broken MT792x commit)
addresses a different issue (firmware loading panic). The RF pin
polling regression may need a separate fix or a quirk for MSI
laptops where the MCU reports incorrect RF pin state.
Steps to reproduce:
1. Install Ubuntu 24.04 on MSI Vector A16 HX A8WHG
2. Install linux-image-generic-hwe-24.04 (kernel 6.17)
3. Reboot — WiFi is hard-blocked
4. Boot kernel 6.8 — WiFi works
ProcVersionSignature: Ubuntu 6.8.0-107.107-generic 6.8.12
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147193/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147193
Title:
[Regression] WiFi hard-blocked on MSI Vector A16 with MT7922 on 6.17
HWE kernel (works on 6.8 GA)
Status in linux package in Ubuntu:
New
Bug description:
Ubuntu 24.04.4 LTS
Kernel: 6.17.0-20-generic (HWE) — BROKEN
Kernel: 6.8.0-107-generic (GA) — WORKING
Hardware: MSI Vector A16 HX A8WHG
WiFi: MediaTek MT7922 (PCI ID: 14c3:7922), driver: mt7921e
BIOS: E15MMAMS.104
Problem:
After the 6.17 HWE kernel update, WiFi is permanently hard-blocked.
rfkill shows "Hard blocked: yes" with RFKILL_HW_BLOCK_REASON=0x1.
The regression is caused by mt7921_mcu_wf_rf_pin_ctrl() added in
kernels after 6.8, which polls the MT7922 MCU for RF pin state.
The MCU incorrectly reports "blocked" on this MSI laptop.
Additionally, MSI BIOS has a bug where WLAN ACPI objects are defined
in two SSDT tables (SSDT4 MSI_WLAN and SSDT24 AMD GPPRPL), causing
AE_ALREADY_EXISTS errors. This may contribute to incorrect hardware
state, though eliminating these errors via SSDT override did not
resolve the hard block.
Workaround:
Use kernel 6.8.0-107-generic (GA kernel). WiFi works perfectly.
Expected fix:
The upstream fix in kernel 6.19 (revert of broken MT792x commit)
addresses a different issue (firmware loading panic). The RF pin
polling regression may need a separate fix or a quirk for MSI
laptops where the MCU reports incorrect RF pin state.
Steps to reproduce:
1. Install Ubuntu 24.04 on MSI Vector A16 HX A8WHG
2. Install linux-image-generic-hwe-24.04 (kernel 6.17)
3. Reboot — WiFi is hard-blocked
4. Boot kernel 6.8 — WiFi works
ProcVersionSignature: Ubuntu 6.8.0-107.107-generic 6.8.12
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147193/+subscriptions
[Bug 2143480] Re: Questing: Failed to query NVIDIA devices
This bug is awaiting verification that the linux-
nvidia-6.17/6.17.0-1015.15 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-noble-linux-
nvidia-6.17' to 'verification-done-noble-linux-nvidia-6.17'. If the
problem still exists, change the tag 'verification-needed-noble-linux-
nvidia-6.17' to 'verification-failed-noble-linux-nvidia-6.17'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-nvidia-6.17-v2 verification-needed-noble-linux-nvidia-6.17
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143480
Title:
Questing: Failed to query NVIDIA devices
Status in linux package in Ubuntu:
Fix Released
Bug description:
Nova modules are enabled for questing with the following patchset.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139960
Because of this we nvidia cards are not being recognized. We need to
disable nove_core module.
nvidia-persistenced[9541]: Started (9541)
nvidia-persistenced[9537]: nvidia-persistenced failed to initialize. Check syslog for more details.
nvidia-persistenced[9541]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 122 has read and write permissions for those files.
systemd[1]: nvidia-persistenced.service: Control process exited, code=exited, status=1/FAILURE
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143480/+subscriptions
nvidia-6.17/6.17.0-1015.15 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-noble-linux-
nvidia-6.17' to 'verification-done-noble-linux-nvidia-6.17'. If the
problem still exists, change the tag 'verification-needed-noble-linux-
nvidia-6.17' to 'verification-failed-noble-linux-nvidia-6.17'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-nvidia-6.17-v2 verification-needed-noble-linux-nvidia-6.17
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143480
Title:
Questing: Failed to query NVIDIA devices
Status in linux package in Ubuntu:
Fix Released
Bug description:
Nova modules are enabled for questing with the following patchset.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139960
Because of this we nvidia cards are not being recognized. We need to
disable nove_core module.
nvidia-persistenced[9541]: Started (9541)
nvidia-persistenced[9537]: nvidia-persistenced failed to initialize. Check syslog for more details.
nvidia-persistenced[9541]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 122 has read and write permissions for those files.
systemd[1]: nvidia-persistenced.service: Control process exited, code=exited, status=1/FAILURE
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143480/+subscriptions
[Bug 2031531] Re: net:rtnetlink.sh in ubuntu_kernel_selftests failed with FAIL: address proto IPv4 / IPv6
This bug is awaiting verification that the linux-
nvidia-6.17/6.17.0-1015.15 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-noble-linux-
nvidia-6.17' to 'verification-done-noble-linux-nvidia-6.17'. If the
problem still exists, change the tag 'verification-needed-noble-linux-
nvidia-6.17' to 'verification-failed-noble-linux-nvidia-6.17'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-nvidia-6.17-v2 verification-needed-noble-linux-nvidia-6.17
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2031531
Title:
net:rtnetlink.sh in ubuntu_kernel_selftests failed with FAIL: address
proto IPv4 / IPv6
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Questing:
Fix Released
Status in linux source package in Resolute:
Fix Released
Bug description:
net:rtnetlink.sh in ubuntu_kernel_selftests is failing with address
proto IPv4 / IPv6 tests with J-oem-6.5 (6.5.0-1002.2)
Test log:
Running 'make run_tests -C net TEST_PROGS=rtnetlink.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
TAP version 13
1..1
# timeout set to 0
# selftests: net: rtnetlink.sh
# PASS: policy routing
# PASS: route get
# PASS: preferred_lft addresses have expired
# PASS: promote_secondaries complete
# PASS: tc htb hierarchy
# PASS: gre tunnel endpoint
# PASS: gretap
# PASS: ip6gretap
# PASS: erspan
# PASS: ip6erspan
# PASS: bridge setup
# PASS: ipv6 addrlabel
# PASS: set ifalias 9f185442-201a-49be-bf15-af9e9e51afb1 for test-dummy0
# PASS: vrf
# PASS: vxlan
# PASS: fou
# PASS: macsec
# PASS: ipsec
# PASS: ipsec_offload
# PASS: bridge fdb get
# PASS: neigh get
# PASS: bridge_parent_id
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# RTNETLINK answers: Cannot assign requested address
# RTNETLINK answers: Cannot assign requested address
# FAIL: address proto IPv4
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# RTNETLINK answers: Cannot assign requested address
# RTNETLINK answers: Cannot assign requested address
# FAIL: address proto IPv6
not ok 1 selftests: net: rtnetlink.sh # exit=1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031531/+subscriptions
nvidia-6.17/6.17.0-1015.15 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-noble-linux-
nvidia-6.17' to 'verification-done-noble-linux-nvidia-6.17'. If the
problem still exists, change the tag 'verification-needed-noble-linux-
nvidia-6.17' to 'verification-failed-noble-linux-nvidia-6.17'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-nvidia-6.17-v2 verification-needed-noble-linux-nvidia-6.17
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2031531
Title:
net:rtnetlink.sh in ubuntu_kernel_selftests failed with FAIL: address
proto IPv4 / IPv6
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Questing:
Fix Released
Status in linux source package in Resolute:
Fix Released
Bug description:
net:rtnetlink.sh in ubuntu_kernel_selftests is failing with address
proto IPv4 / IPv6 tests with J-oem-6.5 (6.5.0-1002.2)
Test log:
Running 'make run_tests -C net TEST_PROGS=rtnetlink.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
TAP version 13
1..1
# timeout set to 0
# selftests: net: rtnetlink.sh
# PASS: policy routing
# PASS: route get
# PASS: preferred_lft addresses have expired
# PASS: promote_secondaries complete
# PASS: tc htb hierarchy
# PASS: gre tunnel endpoint
# PASS: gretap
# PASS: ip6gretap
# PASS: erspan
# PASS: ip6erspan
# PASS: bridge setup
# PASS: ipv6 addrlabel
# PASS: set ifalias 9f185442-201a-49be-bf15-af9e9e51afb1 for test-dummy0
# PASS: vrf
# PASS: vxlan
# PASS: fou
# PASS: macsec
# PASS: ipsec
# PASS: ipsec_offload
# PASS: bridge fdb get
# PASS: neigh get
# PASS: bridge_parent_id
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# RTNETLINK answers: Cannot assign requested address
# RTNETLINK answers: Cannot assign requested address
# FAIL: address proto IPv4
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "local" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# Error: either "dev" is duplicate, or "proto" is a garbage.
# RTNETLINK answers: Cannot assign requested address
# RTNETLINK answers: Cannot assign requested address
# FAIL: address proto IPv6
not ok 1 selftests: net: rtnetlink.sh # exit=1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031531/+subscriptions
[Bug 2121200] Re: Enable RTL ASPM for new Dell platforms
This bug is awaiting verification that the linux-
nvidia-6.17/6.17.0-1015.15 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-noble-linux-
nvidia-6.17' to 'verification-done-noble-linux-nvidia-6.17'. If the
problem still exists, change the tag 'verification-needed-noble-linux-
nvidia-6.17' to 'verification-failed-noble-linux-nvidia-6.17'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-nvidia-6.17-v2 verification-needed-noble-linux-nvidia-6.17
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2121200
Title:
Enable RTL ASPM for new Dell platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Plucky:
Won't Fix
Status in linux-oem-6.14 source package in Plucky:
Invalid
Status in linux-oem-6.17 source package in Plucky:
Invalid
Status in linux source package in Questing:
Fix Released
Status in linux-oem-6.14 source package in Questing:
Invalid
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.14 source package in Resolute:
Invalid
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
To pass the energy star cert, the ASPM feature on RTL NIC should be enabled.
[Fix]
Enable the ASPM feature on all new Dell platforms, the family names are used on the new Dell platforms.
Alienware
Dell Laptops
Dell Pro Laptops
Dell Pro Max Laptops
Dell Desktops
Dell Pro Desktops
Dell Pro Max Desktops
Dell Pro Rugged Laptops
[Test]
1. check the value of /sys/power/suspend_stats/total_hw_sleep
2. suspend and resume the system
3. the value of /sys/power/suspend_stats/total_hw_sleep increases
[Where problems could occur]
The listed family names are used in the new Dell platforms, so should not impact the existing platforms. And Dell will push Realtek to fix the ASPM issue found on RTL NIC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2121200/+subscriptions
nvidia-6.17/6.17.0-1015.15 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-noble-linux-
nvidia-6.17' to 'verification-done-noble-linux-nvidia-6.17'. If the
problem still exists, change the tag 'verification-needed-noble-linux-
nvidia-6.17' to 'verification-failed-noble-linux-nvidia-6.17'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-nvidia-6.17-v2 verification-needed-noble-linux-nvidia-6.17
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2121200
Title:
Enable RTL ASPM for new Dell platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Plucky:
Won't Fix
Status in linux-oem-6.14 source package in Plucky:
Invalid
Status in linux-oem-6.17 source package in Plucky:
Invalid
Status in linux source package in Questing:
Fix Released
Status in linux-oem-6.14 source package in Questing:
Invalid
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.14 source package in Resolute:
Invalid
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
To pass the energy star cert, the ASPM feature on RTL NIC should be enabled.
[Fix]
Enable the ASPM feature on all new Dell platforms, the family names are used on the new Dell platforms.
Alienware
Dell Laptops
Dell Pro Laptops
Dell Pro Max Laptops
Dell Desktops
Dell Pro Desktops
Dell Pro Max Desktops
Dell Pro Rugged Laptops
[Test]
1. check the value of /sys/power/suspend_stats/total_hw_sleep
2. suspend and resume the system
3. the value of /sys/power/suspend_stats/total_hw_sleep increases
[Where problems could occur]
The listed family names are used in the new Dell platforms, so should not impact the existing platforms. And Dell will push Realtek to fix the ASPM issue found on RTL NIC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2121200/+subscriptions
[Bug 2124276] Re: noble/plucky: ubuntu_kselftests_ftrace fails 7 ftrace:test.d tests for riscv64 on openstack:riscv64.vm
This bug is awaiting verification that the linux-
nvidia-6.17/6.17.0-1015.15 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-noble-linux-
nvidia-6.17' to 'verification-done-noble-linux-nvidia-6.17'. If the
problem still exists, change the tag 'verification-needed-noble-linux-
nvidia-6.17' to 'verification-failed-noble-linux-nvidia-6.17'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-nvidia-6.17-v2 verification-needed-noble-linux-nvidia-6.17
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2124276
Title:
noble/plucky: ubuntu_kselftests_ftrace fails 7 ftrace:test.d tests for
riscv64 on openstack:riscv64.vm
Status in ubuntu-kernel-tests:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux-riscv package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Invalid
Status in linux-riscv source package in Jammy:
Confirmed
Status in linux source package in Noble:
Confirmed
Status in linux-riscv source package in Noble:
Confirmed
Status in linux source package in Plucky:
Won't Fix
Status in linux-riscv source package in Plucky:
Won't Fix
Status in linux source package in Questing:
Fix Released
Status in linux-riscv source package in Questing:
Fix Released
Status in linux source package in Resolute:
Invalid
Status in linux-riscv source package in Resolute:
Confirmed
Bug description:
7 tests in ubuntu kselftests (ftrace:test.d series) has been failing
for plucky (6.14.0-9.9.1 -> 6.14.0-32.32) and noble
(6.14.0-24.24.1~24.04.1 -> 6.14.0-32.32.1~24.04.1) on
openstack:riscv64.vm and testflinger riscv64.vm servers.
the tests are the following:
▲ FAILED ▼ ftrace:test.d--dynevent--add_remove_uprobe.tc
▲ FAILED ▼ ftrace:test.d--kprobe--kprobe_args.tc
▲ FAILED ▼ ftrace:test.d--kprobe--kprobe_args_comm.tc
▲ FAILED ▼ ftrace:test.d--kprobe--kprobe_args_symbol.tc
▲ FAILED ▼ ftrace:test.d--kprobe--kprobe_args_type.tc
▲ FAILED ▼ ftrace:test.d--kprobe--kprobe_args_user.tc
▲ FAILED ▼ ftrace:test.d--kprobe--kprobe_args_vfs.tc
Full log attached
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2124276/+subscriptions
nvidia-6.17/6.17.0-1015.15 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-noble-linux-
nvidia-6.17' to 'verification-done-noble-linux-nvidia-6.17'. If the
problem still exists, change the tag 'verification-needed-noble-linux-
nvidia-6.17' to 'verification-failed-noble-linux-nvidia-6.17'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-nvidia-6.17-v2 verification-needed-noble-linux-nvidia-6.17
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2124276
Title:
noble/plucky: ubuntu_kselftests_ftrace fails 7 ftrace:test.d tests for
riscv64 on openstack:riscv64.vm
Status in ubuntu-kernel-tests:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux-riscv package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Invalid
Status in linux-riscv source package in Jammy:
Confirmed
Status in linux source package in Noble:
Confirmed
Status in linux-riscv source package in Noble:
Confirmed
Status in linux source package in Plucky:
Won't Fix
Status in linux-riscv source package in Plucky:
Won't Fix
Status in linux source package in Questing:
Fix Released
Status in linux-riscv source package in Questing:
Fix Released
Status in linux source package in Resolute:
Invalid
Status in linux-riscv source package in Resolute:
Confirmed
Bug description:
7 tests in ubuntu kselftests (ftrace:test.d series) has been failing
for plucky (6.14.0-9.9.1 -> 6.14.0-32.32) and noble
(6.14.0-24.24.1~24.04.1 -> 6.14.0-32.32.1~24.04.1) on
openstack:riscv64.vm and testflinger riscv64.vm servers.
the tests are the following:
▲ FAILED ▼ ftrace:test.d--dynevent--add_remove_uprobe.tc
▲ FAILED ▼ ftrace:test.d--kprobe--kprobe_args.tc
▲ FAILED ▼ ftrace:test.d--kprobe--kprobe_args_comm.tc
▲ FAILED ▼ ftrace:test.d--kprobe--kprobe_args_symbol.tc
▲ FAILED ▼ ftrace:test.d--kprobe--kprobe_args_type.tc
▲ FAILED ▼ ftrace:test.d--kprobe--kprobe_args_user.tc
▲ FAILED ▼ ftrace:test.d--kprobe--kprobe_args_vfs.tc
Full log attached
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2124276/+subscriptions
Подписаться на:
Комментарии (Atom)