This is the expected behavior. If you'd like to discuss a feature
request/change you can do it here:
https://community.broadcom.com/vmware-cloud-
foundation/communities/community-
home/digestviewer?communitykey=fb707ac3-9412-4fad-b7af-018f5da56d9f
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2081803
Title:
kernel >= 6.8.0-44.44 vmwgfx regression in Ubuntu 24.04.1 Desktop VM
guest (VMWare Workstation Pro 17.5.2/17.6)
Status in linux package in Ubuntu:
New
Bug description:
Acknowledgements
================
This bug was originally posed as a question:
https://answers.launchpad.net/ubuntu/+question/818765. Contributions
from actionparsnip, Phil B and Amir Cicak have been incorporated into
this report.
Expected behavior
=================
When running an Ubuntu 24.04.1 Desktop VM guest with linux-generic
6.8.0-44.44 in VMWare Workstation Pro 17.5.2/17.6 in full screen mode
with VMWare "Stretch guest" display preference set and using a 4k
(3840x2160) monitor, the detected screen resolutions selectable in the
Gnome Screen Display settings should be as follows:
3840x2160 (16:9)
2880x1800 (16:10)
2560x1600 (16:10)
2560x1440 (16:9)
1920x1440 (4:3)
etc.
Please also see the attached ubuntu24.04.1-vm-hw-version-21-open-vm-
tools-2:12.4.5-1-gnome-resolutions-expected.png.
Actual behavior
===============
The actual resolutions available in the Gnome Screen Display settings
do not include 4k (3840x2160) but strangely include a 4096x2160
resolution that exceeds the physical monitor resolution. The selected
resolution also defaults to 1280x800 (16:10).
4096x2160 (9:5)
2560x1600 (16:10)
2048x1152 (16:9)
1920x1440 (4:3)
etc.
Please also see the attached ubuntu24.04.1-vm-hw-version-21-open-vm-
tools-2:12.4.5-1-gnome-resolutions-actual.png.
xrandr also omits the 4k resolution so I do not believe this is a
Gnome specific issue:
$ xrandr|grep 3840
Although xrandr does not include the 4096 resolution, either:
$ xrandr |grep 4096
Tested versions:
- Ubuntu 24.04.1 Desktop VM guest
- linux-generic >= 6.8.0-44.44
- VMWare Workstation Pro 17.5.2/17.6 full screen display preferences set to "Stretch guest"
- Please note: I have only tested under VMWare Workstation Pro 17.5.2 due to unrelated issues upgrading to 17.6. However, Phil B confirmed the issue also affects 17.6 in their response to the original question: https://answers.launchpad.net/ubuntu/+question/818765.
- GNOME Shell 46.0 (as displayed by gnome-shell --version)
Workarounds, which show that the guest does technically support the 4k resolution
=================================================================================
Workaround option 1
-------------------
The following workaround has to be performed upon each boot, albeit it
can be automated - please see the attached vmware-missing-4k-res-
workaround.sh as an example.
1. In the Ubuntu 24.04.1 guest OS, explicitly set the guest screen
topology:
sudo vmwgfxctrl --set-topology 3840x2160+0+0
2. Toggle VMWare Workstation Pro out of and back into full screen
mode.
3. Observe the Gnome Screen Display settings now has 3840x2160 (16:9)
as the selected resolution.
4. Fractional scaling can also be manually set and will persist across
reboots.
Workaround option 2
-------------------
Ensure the VMWare Workstation Pro 17.5.2 settings:
- Display Preference:
- Autofit
- Autofit Window: disabled
- Autofit guest: disabled
- Full screen: Autofit guest (change guest resolution)
However, auto fitting the guest can break some scenarios for some
other guest VMs and VMWare Workstation Pro does not allow configuring
per-VM display preferences. So this workaround can be significantly
less convenient than the automated version of option 1.
Testing steps
=============
1. Ensure your system is connected to a single native 4k (3840x2160)
monitor. DisplayPort vs HDMI connector makes no difference. My monitor
supports DisplayPort 1.4 and HDMI 2.0.
2. (optional) I don't think it matters but my host OS was:
$ grep VERSION= /etc/os-release
VERSION="24.04.1 LTS (Noble Numbat)"
$ uname -r
6.8.0-45-generic
3. VMWare Workstation Pro 17.5.2 settings:
Edit->Preferences->Display
- Autofit
- Autofit window: disabled
- Autofit guest: disabled
- Full Screen
- Stretch guest (no resolution change): enabled
4. Ensure the Ubuntu 24.04.1 guest VM is using the latest VMWare
hardware version. This can be verified from the version in the VM's
.vmx file, which is 21 for 17.5.x:
$ grep virtualHW.version "$(ls *.vmx)"
virtualHW.version = "21"
According to Phil B, the latest VMWare Workstation Pro 17.6, which
I could not test due to unrelated upgrade errors, doesn't make a
difference.
5. Ensure the Ubuntu 24.04.1 guest VM has a kernel >= 6.8.0-44
$ uname -r
6.8.0-44-generic
$ dpkg -l linux-generic
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=========================================
ii linux-generic 6.8.0-44.44 amd64 Complete Generic Linux kernel and headers
In my case, one of my guests already had this version due to
upgrading from 23.10 to 24.04.1 on Sep 16 2024. However, if you have
already upgraded to the latest stable kernel (6.8.0-45.45), you can
downgrade the kernel as follows, assuming you did not explicitly
remove the old kernel:
4.1 Reboot the system, holding down the Shift key
4.2 In the Grub "Advanced options for Ubuntu", select the option for the 6.8.0-44-generic kernel
4.3 Once booted, confirm the kernel version:
$ uname -r
6.8.0-44-generic
6. Ensure the VM is using the latest open-vm-tools and open-vm-tools-
desktop
$ sudo apt update && sudo apt install open-vm-tools open-vm-tools-desktop
$ dpkg -l open-vm-*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===========================-==========================-============-=============================================================
ii open-vm-tools 2:12.4.5-1~ubuntu0.24.04.1 amd64 Open VMware Tools for virtual machines hosted on VMware (CLI)
un open-vm-tools-containerinfo <none> <none> (no description available)
ii open-vm-tools-desktop 2:12.4.5-1~ubuntu0.24.04.1 amd64 Open VMware Tools for virtual machines hosted on VMware (GUI)
un open-vm-tools-dev <none> <none> (no description available)
un open-vm-tools-salt-minion <none> <none> (no description available)
un open-vm-tools-sdmp <none> <none> (no description available)
7. If open-vm-tools or open-vm-tools-desktop were newly installed or
updated, reboot the VM just in case.
8. Display the VM in windowed mode.
9. In the VM, check the available resolutions in the Gnome Screen
Display settings are wrong:
4096x2160 (9:5)
2560x1600 (16:10)
2048x1152 (16:9)
1920x1440 (4:3)
etc.
10. Display the VM in full screen mode. Confirm the available resolutions are still wrong.
11. Observe the host log during boot. Logs are located under
/tmp/vmware-$USER and the number will be runtime dependent. The log
seemed to indicate VMWare is aware of the 4k resolution screen:
$ tail -f vmware-ui-3652.log |grep -i topology
2024-09-17T09:12:48.104Z In(05) vmui HandleGuestTopologyChange: main UI rect: 3840x2160 @ 0,0
2024-09-17T09:12:48.104Z In(05) vmui HandleGuestTopologyChange: Found 1 present screens
2024-09-17T09:12:48.104Z In(05) vmui HandleGuestTopologyChange: Windows for extra guest monitors will be shown
12. In the guest VM, /var/log/vmware* seemed to indicate
resolutionCheckForKMS is running, which according to
https://docs.vmware.com/en/VMware-
Tools/12.4.0/com.vmware.vsphere.vmwaretools.doc/GUID-0BD592B1-A300-4C09-808A-BB447FAE2C2A.html,
"Handles communicating guest user interface topology to the vmwgfx drm
(direct rendering manager) driver".
$ sudo grep -i resolution vmware*
...
vmware-vmsvc-root.log:[2024-09-17T09:12:49.394Z] [ message] [resolutionCommon] [1327] resolutionCheckForKMS: dlopen succeeded.
vmware-vmsvc-root.log:[2024-09-17T09:12:49.397Z] [ message] [resolutionCommon] [1327] resolutionCheckForKMS: System support available for resolutionKMS.
vmware-vmsvc-root.log:[2024-09-17T09:12:49.397Z] [ message] [vmtoolsd] [1327] Plugin 'resolutionKMS' initialized.
...
vmware-vmusr-REDACTED.log:[2024-09-17T09:14:52.683Z] [ message] [resolutionCommon] [3348] resolutionCheckForKMS: dlopen succeeded.
vmware-vmusr-REDACTED.log:[2024-09-17T09:14:52.685Z] [ message] [resolutionCommon] [3348] resolutionCheckForKMS: System support available for resolutionKMS.
vmware-vmusr-REDACTED.log:[2024-09-17T09:14:52.685Z] [ message] [resolutionSet] [3348] ResolutionToolkitInit: Backing off for resolutionKMS.
13. (optional) On Sep 24, 2024, for good measure I also verified that `sudo apt update && sudo apt upgrade` did not change the observed behavior so the latest Ubuntu stable release appears to be affected and I do not believe any other packages affect the observed behavior. Furthermore, the latest stable release kernel at this time was:
uname -r
6.8.0-45-generic
Testing steps - latest mainline kernel v6.11
============================================
The latest mainline kernel was also tested from
https://kernel.ubuntu.com/mainline/v6.11/ with the same observed
behavior.
1. Checksums of version used:
# Checksums, check with the command below:
# shasum -c CHECKSUMS
#
# Checksums-Sha1:
59d8a86a327389bafda66d18baaa4b8db6351e66 linux-headers-6.11.0-061100-generic_6.11.0-061100.202409151536_amd64.deb
98cf819f700c596a3a61d54ec3165a011ef842ea linux-headers-6.11.0-061100_6.11.0-061100.202409151536_all.deb
a479c725d1f846e2b7d7d45daf0f6ef7f5fe596b linux-image-unsigned-6.11.0-061100-generic_6.11.0-061100.202409151536_amd64.deb
2408c34f460a98883a046995be16831f03d7a60e linux-modules-6.11.0-061100-generic_6.11.0-061100.202409151536_amd64.deb
#
# Checksums-Sha256:
3d13b2ee8327e73d68220687604382847e43b9dcdf115e37b52bebb68cde4faf linux-headers-6.11.0-061100-generic_6.11.0-061100.202409151536_amd64.deb
9d296b9e5172cf78bf2fc535c72667c8cb0160a457617b580e79e82897cd0280 linux-headers-6.11.0-061100_6.11.0-061100.202409151536_all.deb
8881567927f704a03e80b7d7af2e94e6741af49e4a00c073ef5b3e70da631b89 linux-image-unsigned-6.11.0-061100-generic_6.11.0-061100.202409151536_amd64.deb
f2ad25b72ad8be3478a7d679e9ad70e4ed4c3d5904fcb75da76acebc82357717 linux-modules-6.11.0-061100-generic_6.11.0-061100.202409151536_amd64.deb
2. Install kernel in Ubuntu 24.04.1:
$ sudo dpkg -i *.deb
(Reading database ... 310509 files and directories currently installed.)
Preparing to unpack linux-headers-6.11.0-061100_6.11.0-061100.202409151536_all.deb ...
Unpacking linux-headers-6.11.0-061100 (6.11.0-061100.202409151536) over (6.11.0-061100.202409151536) ...
Preparing to unpack linux-headers-6.11.0-061100-generic_6.11.0-061100.202409151536_amd64.deb ...
Unpacking linux-headers-6.11.0-061100-generic (6.11.0-061100.202409151536) over (6.11.0-061100.202409151536) ...
Preparing to unpack linux-image-unsigned-6.11.0-061100-generic_6.11.0-061100.202409151536_amd64.deb ...
Unpacking linux-image-unsigned-6.11.0-061100-generic (6.11.0-061100.202409151536) over (6.11.0-061100.202409151536) ...
/var/lib/dpkg/info/linux-image-unsigned-6.11.0-061100-generic.postrm ... removing pending trigger
Preparing to unpack linux-modules-6.11.0-061100-generic_6.11.0-061100.202409151536_amd64.deb ...
Unpacking linux-modules-6.11.0-061100-generic (6.11.0-061100.202409151536) over (6.11.0-061100.202409151536) ...
Setting up linux-headers-6.11.0-061100 (6.11.0-061100.202409151536) ...
Setting up linux-headers-6.11.0-061100-generic (6.11.0-061100.202409151536) ...
Setting up linux-modules-6.11.0-061100-generic (6.11.0-061100.202409151536) ...
Setting up linux-image-unsigned-6.11.0-061100-generic (6.11.0-061100.202409151536) ...
Processing triggers for linux-image-unsigned-6.11.0-061100-generic (6.11.0-061100.202409151536) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.11.0-061100-generic
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.11.0-061100-generic
Found initrd image: /boot/initrd.img-6.11.0-061100-generic
Found linux image: /boot/vmlinuz-6.8.0-45-generic
Found initrd image: /boot/initrd.img-6.8.0-45-generic
Found linux image: /boot/vmlinuz-6.8.0-41-generic
Found initrd image: /boot/initrd.img-6.8.0-41-generic
Found memtest86+x64 image: /boot/memtest86+x64.bin
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
3. Reboot with the new kernel:
2.1 Reboot the system, holding down the Shift key
2.2 In the Grub "Advanced options for Ubuntu", select the option for the 6.11.0-061100-generic kernel
2.3 Once booted, confirm the kernel version:
$ uname -r
6.11.0-061100-generic
4. Same bug observed.
(optional) Testing steps - Fedora
=================================
In the original posted question, tests of a different distribution,
Fedora, were also conducted at actionparsnip's suggestion and
exhibited the same bug. This information is probably irrelevant now
that I've tested the latest mainline kernel but is included here for
completeness. Phil B's contribution:
"I just installed Fedora 40 in VMWare to find out:
uname -r
6.10.10-200.fc40.x86_64
Same problem. So it's kernel thing, I guess."
I also verified the same:
1. Installed SHA256 (Fedora-Workstation-Live-x86_64-40-1.14.iso) =
dd1faca950d1a8c3d169adf2df4c3644ebb62f8aac04c401f2393e521395d613
without installing updates
2. Worked fine but kernel is older than Phil B's
$ uname -r
6.8.5-301.fc40.x86_64
$ echo $XDG_SESSION_TYPE
wayland
$ gnome-shell --version
GNOME Shell 46.0
# After changing resolution in Gnome settings
$ xrandr |grep -o 3840x2160
3840x2160
3840x2160
3. Upgraded
$ sudo dnf check-update
4. Shutdown and reboot
5. Same bug encountered with same kernel as Phil B
$ uname -r
6.10.10-200.fc40.x86_64
$ echo $XDG_SESSION_TYPE
wayland
Identification of regression introduced in linux-generic 6.8.0-44.44
====================================================================
The bug appears to be a regression introduced with linux-generic
6.8.0-44.44. However, instead of bisecting the kernel, I arrived at
this conclusion based on observations from 2 of my existing guest VMs.
Phil B also confirmed "the issue arose when upgrading linux-generic
kernel from 6.8.0-41.41 to 6.8.0-44.44" when commenting on my original
posted question.
Ubuntu 24.04.1 VM Guest 1:
- Was already Ubuntu 24.04.1, screen resolution worked fine and kernel
was 6.8.0-41-generic from linux-generic 6.8.0-41.41:
$ uname -r
6.8.0-41-generic
$ dpkg -l linux-generic
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=========================================
ii linux-generic 6.8.0-41.41 amd64 Complete Generic Linux kernel and headers
- apt list --upgradeable |grep 'linux-' showed upgrades available to
6.8.0-45.45:
linux-generic/noble-updates 6.8.0-45.45 amd64 [upgradable from: 6.8.0-41.41]
linux-headers-generic/noble-updates 6.8.0-45.45 amd64 [upgradable from: 6.8.0-41.41]
linux-image-generic/noble-updates 6.8.0-45.45 amd64 [upgradable from: 6.8.0-41.41]
linux-libc-dev/noble-updates 6.8.0-45.45 amd64 [upgradable from: 6.8.0-41.41]
linux-tools-common/noble-updates,noble-updates 6.8.0-45.45 all [upgradable from: 6.8.0-41.41]
- Selectively upgrading the above resulted in the same bug upon
reboot:
sudo apt-get install --only-upgrade linux-generic linux-headers-
generic linux-image-generic linux-libc-dev linux-tools-common
Ubuntu 24.04.1 VM Guest 2:
- Was on Ubuntu 23.10, screen resolution worked fine and kernel was
6.5.0-44-generic:
```
$ uname -r
6.5.0-44-generic
```
- Upgrading to Ubuntu 24.04.01 resulted in the same bug.
- Unlike Guest 1, though, the kernel was the older 6.8.0-44-generic
due to the timing of my upgrade:
$ uname -r
6.8.0-44-generic
$ dpkg -l linux-generic
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=========================================
ii linux-generic 6.8.0-44.44 amd64 Complete Generic Linux kernel and headers
Hence, the above indicates:
- linux-generic 6.8.0-41.41 did not exhibit the bug
- linux-generic 6.8.0-44.44 exhibited the bug
Further evidence is from the two diffs listed at
https://launchpad.net/ubuntu/+source/linux/6.8.0-44.44:
1. diff from 6.8.0-41.41 (in ~canonical-kernel-team/ubuntu/ppa2) to 6.8.0-44.44
2. diff from 6.8.0-43.43 to 6.8.0-44.44 (6.0 KiB)
Only the first lists changes made to vmwgfx, which I believe is the
VMware Linux graphics driver:
- drm/vmwgfx: Refactor drm connector probing for display modes
- drm/vmwgfx: Filter modes which exceed graphics memory
- drm/vmwgfx: 3D disabled should not effect STDU memory limits
- drm/vmwgfx: Remove STDU logic from generic mode_valid function
- drm/vmwgfx: Don't memcmp equivalent pointers
Thus, it seems linux-generic 6.8.0-44.44 is responsible for the
regression in behavior due to the above changes. From the git
comments, these changes appear to correspond to upstream kernel
changes:
- drm/vmwgfx: Refactor drm connector probing for display modes --> https://github.com/torvalds/linux/commit/935f795045a6f9b13d28d46ebdad04bfea8750dd
- drm/vmwgfx: Filter modes which exceed graphics memory --> https://github.com/torvalds/linux/commit/426826933109093503e7ef15d49348fc5ab505fe
- drm/vmwgfx: 3D disabled should not effect STDU memory limits --> https://github.com/torvalds/linux/commit/fb5e19d2dd03eb995ccd468d599b2337f7f66555
- drm/vmwgfx: Remove STDU logic from generic mode_valid function --> https://github.com/torvalds/linux/commit/dde1de06bd7248fd83c4ce5cf0dbe9e4e95bbb91
- drm/vmwgfx: Don't memcmp equivalent pointers --> https://github.com/torvalds/linux/commit/5703fc058efdafcdd6b70776ee562478f0753acb
I am unsure of how to determine what upstream release the Ubuntu
kernel is based on as the info at
https://people.canonical.com/~kernel/info/kernel-version-map.html
appears to be out of date.
Appendix - Wayland vs X11 seems to be irrelevant
================================================
In my original posted question, Amir Cicak suggested that the bug only
affects Wayland, not X11 but did not provide detailed testing steps.
However, I was unable to reproduce their findings. Potentially they
have a different issue. Testing steps:
1. Confirm using Wayland
$ echo $XDG_SESSION_TYPE
wayland
2. Disable Wayland
sudo sed -i.bak -e 's/^#WaylandEnable=false/WaylandEnable=false/'
/etc/gdm3/custom.conf
3. Reboot to be sure
reboot
4. Confirm X11
$ echo $XDG_SESSION_TYPE
x11
5. Same bug observed.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-generic 6.8.0-45.45
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: redacted_username 2951 F.... pipewire
/dev/snd/controlC0: redacted_username 2955 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 24 17:54:44 2024
InstallationDate: Installed on 2023-04-03 (540 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
IwConfig:
lo no wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 001 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 004: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID
MachineType: VMware, Inc. VMware Virtual Platform
ProcFB: 0 vmwgfxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic root=/dev/mapper/vgubuntu-root ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.8.0-45-generic N/A
linux-backports-modules-6.8.0-45-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.3
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-09-16 (8 days ago)
dmi.bios.date: 11/12/2020
dmi.bios.release: 4.6
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.ec.firmware.release: 0.0
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081803/+subscriptions
вторник
[Bug 2063150] Re: No sound, stutters and clicks after upgrade to 24.04
Having this issue on a fresh 24.10 install:
Sound worked for a few minutes, then no more sound at all.
Blacklisting snd_soc_avs solved it.
Machine: Lenovo Legion Pro 7i
Kernel: 6.11.0-8-generic
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2063150
Title:
No sound, stutters and clicks after upgrade to 24.04
Status in linux package in Ubuntu:
Expired
Status in pipewire package in Ubuntu:
Invalid
Bug description:
After upgrading from Ubuntu 23.10 to 24.04, it does not work on the
computer.
Work with:
1) Bluetooth
2) Jack 3.5
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: pipewire 1.0.5-1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 22 15:52:58 2024
InstallationDate: Installed on 2024-03-25 (28 days ago)
InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010)
SourcePackage: pipewire
UpgradeStatus: Upgraded to noble on 2024-04-21 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063150/+subscriptions
Sound worked for a few minutes, then no more sound at all.
Blacklisting snd_soc_avs solved it.
Machine: Lenovo Legion Pro 7i
Kernel: 6.11.0-8-generic
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2063150
Title:
No sound, stutters and clicks after upgrade to 24.04
Status in linux package in Ubuntu:
Expired
Status in pipewire package in Ubuntu:
Invalid
Bug description:
After upgrading from Ubuntu 23.10 to 24.04, it does not work on the
computer.
Work with:
1) Bluetooth
2) Jack 3.5
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: pipewire 1.0.5-1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 22 15:52:58 2024
InstallationDate: Installed on 2024-03-25 (28 days ago)
InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010)
SourcePackage: pipewire
UpgradeStatus: Upgraded to noble on 2024-04-21 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063150/+subscriptions
[Bug 2048183] Re: Don't produce linux-*-cloud-tools-common, linux-*-tools-common and linux-*-tools-host binary packages
This bug is awaiting verification that the linux-
fips/5.15.0-125.135+fips1 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-jammy-linux-fips' to
'verification-done-jammy-linux-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-fips' to 'verification-
failed-jammy-linux-fips'.
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-jammy-linux-fips-v2 verification-needed-jammy-linux-fips
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2048183
Title:
Don't produce linux-*-cloud-tools-common, linux-*-tools-common and
linux-*-tools-host binary packages
Status in linux package in Ubuntu:
Fix Released
Status in linux-bluefield package in Ubuntu:
New
Status in linux-hwe-5.15 package in Ubuntu:
New
Status in linux-ibm package in Ubuntu:
New
Status in linux-intel-iotg package in Ubuntu:
New
Status in linux-intel-iotg-5.15 package in Ubuntu:
Confirmed
Status in linux-iot package in Ubuntu:
New
Status in linux-lowlatency package in Ubuntu:
Fix Released
Status in linux-lowlatency-hwe-5.15 package in Ubuntu:
New
Status in linux-nvidia package in Ubuntu:
New
Status in linux-nvidia-6.8 package in Ubuntu:
Invalid
Status in linux-xilinx-zynqmp package in Ubuntu:
New
Status in linux-hwe-5.15 source package in Focal:
New
Status in linux-ibm source package in Focal:
New
Status in linux-intel-iotg-5.15 source package in Focal:
New
Status in linux-iot source package in Focal:
New
Status in linux-lowlatency-hwe-5.15 source package in Focal:
New
Status in linux-hwe-6.5 source package in Jammy:
New
Status in linux-ibm source package in Jammy:
New
Status in linux-intel-iotg source package in Jammy:
New
Status in linux-lowlatency source package in Jammy:
New
Status in linux-nvidia source package in Jammy:
New
Status in linux-nvidia-6.5 source package in Jammy:
New
Status in linux-nvidia-6.8 source package in Jammy:
Fix Released
Status in linux-realtime source package in Jammy:
New
Status in linux-xilinx-zynqmp source package in Jammy:
New
Status in linux-ibm source package in Noble:
New
Status in linux-lowlatency source package in Noble:
New
Status in linux-nvidia source package in Noble:
Fix Committed
Status in linux-nvidia-lowlatency source package in Noble:
New
Bug description:
[Impact]
Some kernels produce linux-*-cloud-tools-common, linux-*-tools-common
and/or linux-*-tools-host binary deb packages. That is all wrong, only
the primary/main linux source package should produce these. These
packages result in install failures of the regular linux-cloud-tools-
common, linux-tools-common and linux-tools-host packages.
[Test Case]
Check list of built binary packages in LP and verify the packages are
not built.
[Where Problems Could Occur]
Already installed packages won't upgrade and become stale.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048183/+subscriptions
fips/5.15.0-125.135+fips1 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-jammy-linux-fips' to
'verification-done-jammy-linux-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-fips' to 'verification-
failed-jammy-linux-fips'.
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-jammy-linux-fips-v2 verification-needed-jammy-linux-fips
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2048183
Title:
Don't produce linux-*-cloud-tools-common, linux-*-tools-common and
linux-*-tools-host binary packages
Status in linux package in Ubuntu:
Fix Released
Status in linux-bluefield package in Ubuntu:
New
Status in linux-hwe-5.15 package in Ubuntu:
New
Status in linux-ibm package in Ubuntu:
New
Status in linux-intel-iotg package in Ubuntu:
New
Status in linux-intel-iotg-5.15 package in Ubuntu:
Confirmed
Status in linux-iot package in Ubuntu:
New
Status in linux-lowlatency package in Ubuntu:
Fix Released
Status in linux-lowlatency-hwe-5.15 package in Ubuntu:
New
Status in linux-nvidia package in Ubuntu:
New
Status in linux-nvidia-6.8 package in Ubuntu:
Invalid
Status in linux-xilinx-zynqmp package in Ubuntu:
New
Status in linux-hwe-5.15 source package in Focal:
New
Status in linux-ibm source package in Focal:
New
Status in linux-intel-iotg-5.15 source package in Focal:
New
Status in linux-iot source package in Focal:
New
Status in linux-lowlatency-hwe-5.15 source package in Focal:
New
Status in linux-hwe-6.5 source package in Jammy:
New
Status in linux-ibm source package in Jammy:
New
Status in linux-intel-iotg source package in Jammy:
New
Status in linux-lowlatency source package in Jammy:
New
Status in linux-nvidia source package in Jammy:
New
Status in linux-nvidia-6.5 source package in Jammy:
New
Status in linux-nvidia-6.8 source package in Jammy:
Fix Released
Status in linux-realtime source package in Jammy:
New
Status in linux-xilinx-zynqmp source package in Jammy:
New
Status in linux-ibm source package in Noble:
New
Status in linux-lowlatency source package in Noble:
New
Status in linux-nvidia source package in Noble:
Fix Committed
Status in linux-nvidia-lowlatency source package in Noble:
New
Bug description:
[Impact]
Some kernels produce linux-*-cloud-tools-common, linux-*-tools-common
and/or linux-*-tools-host binary deb packages. That is all wrong, only
the primary/main linux source package should produce these. These
packages result in install failures of the regular linux-cloud-tools-
common, linux-tools-common and linux-tools-host packages.
[Test Case]
Check list of built binary packages in LP and verify the packages are
not built.
[Where Problems Could Occur]
Already installed packages won't upgrade and become stale.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048183/+subscriptions
[Bug 2084493] Re: thinkpad having issues with freeze after boot
** Attachment added: "apport-collect 2084493.zip"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084493/+attachment/5828351/+files/apport-collect%202084493.zip
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084493
Title:
thinkpad having issues with freeze after boot
Status in linux package in Ubuntu:
Incomplete
Bug description:
after launching the kernel, the screen freezes when selecting linux
6.11.0.8
Ubuntu 24.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084493/+subscriptions
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084493/+attachment/5828351/+files/apport-collect%202084493.zip
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084493
Title:
thinkpad having issues with freeze after boot
Status in linux package in Ubuntu:
Incomplete
Bug description:
after launching the kernel, the screen freezes when selecting linux
6.11.0.8
Ubuntu 24.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084493/+subscriptions
[Bug 2084493] Re: thinkpad having issues with freeze after boot
This is how I made the full upgrade to Oracular.
Below I am sending a packet of logs, let me know if it is enough or other data are needed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084493
Title:
thinkpad having issues with freeze after boot
Status in linux package in Ubuntu:
Incomplete
Bug description:
after launching the kernel, the screen freezes when selecting linux
6.11.0.8
Ubuntu 24.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084493/+subscriptions
Below I am sending a packet of logs, let me know if it is enough or other data are needed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084493
Title:
thinkpad having issues with freeze after boot
Status in linux package in Ubuntu:
Incomplete
Bug description:
after launching the kernel, the screen freezes when selecting linux
6.11.0.8
Ubuntu 24.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084493/+subscriptions
[Bug 2064176] Re: LXD fan bridge causes blocked tasks
** Changed in: linux (Ubuntu Noble)
Status: Fix Released => 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/2064176
Title:
LXD fan bridge causes blocked tasks
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Noble:
Fix Committed
Bug description:
SRU Justification:
[Impact]
User can trigger a host crash on Jammy/Noble by launching
a container which uses Ubuntu FAN network in LXD.
[Fix]
A first proposed patch fixes RCU locking by releasing rcu_read_lock
on the skb discard codepath.
Second patch just use a proper way (dev_core_stats_tx_dropped_inc() function)
to increase netdev's tx_dropped statistic value.
[Test Plan]
As provided by Max Asnaashari:
# Install LXD from channel latest/stable
snap install lxd --channel latest/stable
# Configure LXD
lxd init --auto
# Create a FAN network
lxc network create lxdfan0 bridge.mode=fan ipv4.nat=true
# Launch a container using the FAN network
lxc launch ubuntu-minimal:22.04 c1 --network lxdfan0
# Try to interact with LXD
lxc ls
[Where problems could occur]
Change is local and only related to Ubuntu FAN code. I would not expect
any problems with this patchset.
Hi, cross posting this from
https://github.com/canonical/lxd/issues/12161
I've got a lxd cluster running across 3 VMs using the fan bridge. I'm
using a dev revision of LXD based on 6413a948. Creating a container
causes the trace in the attached syslog snippet; this causes the
container creation process to hang indefinitely. ssh logins, `lxc
shell cluster1`, and `ps -aux` also hang.
Apr 29 17:15:01 cluster1 kernel: [ 161.250951] ------------[ cut here ]------------
Apr 29 17:15:01 cluster1 kernel: [ 161.250957] Voluntary context switch within RCU read-side critical section!
Apr 29 17:15:01 cluster1 kernel: [ 161.250990] WARNING: CPU: 2 PID: 510 at kernel/rcu/tree_plugin.h:320 rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [ 161.251003] Modules linked in: nft_masq nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vxlan ip6_udp_tunnel udp_tunnel dummy br
idge stp llc zfs(PO) spl(O) nf_tables libcrc32c nfnetlink vhost_vsock vhost vhost_iotlb binfmt_misc nls_iso8859_1 intel_rapl_msr intel_rapl_common kvm_intel kvm irqbypass crct10dif
_pclmul crc32_pclmul virtio_gpu polyval_clmulni polyval_generic ghash_clmulni_intel sha256_ssse3 sha1_ssse3 virtio_dma_buf aesni_intel vmw_vsock_virtio_transport 9pnet_virtio xhci_
pci drm_shmem_helper i2c_i801 ahci 9pnet vmw_vsock_virtio_transport_common xhci_pci_renesas drm_kms_helper libahci crypto_simd joydev virtio_input cryptd lpc_ich virtiofs i2c_smbus
vsock psmouse input_leds mac_hid serio_raw rapl qemu_fw_cfg vmgenid nfsd dm_multipath auth_rpcgss scsi_dh_rdac nfs_acl lockd scsi_dh_emc scsi_dh_alua grace sch_fq_codel drm sunrpc
efi_pstore virtio_rng ip_tables x_tables autofs4
Apr 29 17:15:01 cluster1 kernel: [ 161.251085] CPU: 2 PID: 510 Comm: nmbd Tainted: P O 6.5.0-28-generic #29~22.04.1-Ubuntu
Apr 29 17:15:01 cluster1 kernel: [ 161.251089] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009)/LXD, BIOS unknown 2/2/2022
Apr 29 17:15:01 cluster1 kernel: [ 161.251091] RIP: 0010:rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [ 161.251095] Code: 08 f0 83 44 24 fc 00 48 89 de 4c 89 f7 e8 d1 af ff ff e9 1e fe ff ff 48 c7 c7 d0 60 56 88 c6 05 e6 27 40 02 01 e8 79 b2 f2 ff
<0f> 0b e9 bd fd ff ff a9 ff ff ff 7f 0f 84 75 fe ff ff 65 48 8b 3c
Apr 29 17:15:01 cluster1 kernel: [ 161.251098] RSP: 0018:ffffb9cbc11dbbc8 EFLAGS: 00010046
Apr 29 17:15:01 cluster1 kernel: [ 161.251101] RAX: 0000000000000000 RBX: ffff941ef7cb3f80 RCX: 0000000000000000
Apr 29 17:15:01 cluster1 kernel: [ 161.251103] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Apr 29 17:15:01 cluster1 kernel: [ 161.251104] RBP: ffffb9cbc11dbbe8 R08: 0000000000000000 R09: 0000000000000000
Apr 29 17:15:01 cluster1 kernel: [ 161.251106] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Apr 29 17:15:01 cluster1 kernel: [ 161.251111] R13: ffff941d893e9980 R14: 0000000000000000 R15: ffff941d80ad7a80
Apr 29 17:15:01 cluster1 kernel: [ 161.251113] FS: 00007c7dcbdb8a00(0000) GS:ffff941ef7c80000(0000) knlGS:0000000000000000
Apr 29 17:15:01 cluster1 kernel: [ 161.251115] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 29 17:15:01 cluster1 kernel: [ 161.251117] CR2: 00005a30877ae488 CR3: 0000000105888003 CR4: 0000000000170ee0
Apr 29 17:15:01 cluster1 kernel: [ 161.251122] Call Trace:
Apr 29 17:15:01 cluster1 kernel: [ 161.251128] <TASK>
Apr 29 17:15:01 cluster1 kernel: [ 161.251133] ? show_regs+0x6d/0x80
Apr 29 17:15:01 cluster1 kernel: [ 161.251145] ? __warn+0x89/0x160
Apr 29 17:15:01 cluster1 kernel: [ 161.251152] ? rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [ 161.251155] ? report_bug+0x17e/0x1b0
Apr 29 17:15:01 cluster1 kernel: [ 161.251172] ? handle_bug+0x46/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251187] ? exc_invalid_op+0x18/0x80
Apr 29 17:15:01 cluster1 kernel: [ 161.251190] ? asm_exc_invalid_op+0x1b/0x20
Apr 29 17:15:01 cluster1 kernel: [ 161.251202] ? rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [ 161.251205] ? rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [ 161.251208] __schedule+0xcc/0x750
Apr 29 17:15:01 cluster1 kernel: [ 161.251218] schedule+0x63/0x110
Apr 29 17:15:01 cluster1 kernel: [ 161.251222] schedule_hrtimeout_range_clock+0xbc/0x130
Apr 29 17:15:01 cluster1 kernel: [ 161.251238] ? __pfx_hrtimer_wakeup+0x10/0x10
Apr 29 17:15:01 cluster1 kernel: [ 161.251245] schedule_hrtimeout_range+0x13/0x30
Apr 29 17:15:01 cluster1 kernel: [ 161.251248] ep_poll+0x33f/0x390
Apr 29 17:15:01 cluster1 kernel: [ 161.251254] ? __pfx_ep_autoremove_wake_function+0x10/0x10
Apr 29 17:15:01 cluster1 kernel: [ 161.251257] do_epoll_wait+0xdb/0x100
Apr 29 17:15:01 cluster1 kernel: [ 161.251259] __x64_sys_epoll_wait+0x6f/0x110
Apr 29 17:15:01 cluster1 kernel: [ 161.251265] do_syscall_64+0x5b/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251270] ? do_epoll_ctl+0x3cb/0x860
Apr 29 17:15:01 cluster1 kernel: [ 161.251273] ? __task_pid_nr_ns+0x6c/0xc0
Apr 29 17:15:01 cluster1 kernel: [ 161.251279] ? exit_to_user_mode_prepare+0x30/0xb0
Apr 29 17:15:01 cluster1 kernel: [ 161.251284] ? syscall_exit_to_user_mode+0x37/0x60
Apr 29 17:15:01 cluster1 kernel: [ 161.251286] ? do_syscall_64+0x67/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251288] ? syscall_exit_to_user_mode+0x37/0x60
Apr 29 17:15:01 cluster1 kernel: [ 161.251300] ? do_syscall_64+0x67/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251304] ? syscall_exit_to_user_mode+0x37/0x60
Apr 29 17:15:01 cluster1 kernel: [ 161.251306] ? do_syscall_64+0x67/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251309] ? do_syscall_64+0x67/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251313] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
Apr 29 17:15:01 cluster1 kernel: [ 161.251316] RIP: 0033:0x7c7dcf325dea
Apr 29 17:15:01 cluster1 kernel: [ 161.251333] Code: 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 e8 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 5e c3 0f 1f 44 00 00 48 83 ec 28 89 54 24 18
Apr 29 17:15:01 cluster1 kernel: [ 161.251335] RSP: 002b:00007ffdde5e0278 EFLAGS: 00000246 ORIG_RAX: 00000000000000e8
Apr 29 17:15:01 cluster1 kernel: [ 161.251338] RAX: ffffffffffffffda RBX: 00005a30877a2ea0 RCX: 00007c7dcf325dea
Apr 29 17:15:01 cluster1 kernel: [ 161.251340] RDX: 0000000000000001 RSI: 00007ffdde5e02ac RDI: 0000000000000005
Apr 29 17:15:01 cluster1 kernel: [ 161.251341] RBP: 00005a3087794590 R08: 00000000000f423f R09: 00007ffdde5e0357
Apr 29 17:15:01 cluster1 kernel: [ 161.251343] R10: 00000000000003e8 R11: 0000000000000246 R12: 00005a30877a2f30
Apr 29 17:15:01 cluster1 kernel: [ 161.251345] R13: 00000000000003e8 R14: 0000000000000090 R15: 000000000000000a
Apr 29 17:15:01 cluster1 kernel: [ 161.251348] </TASK>
Apr 29 17:15:01 cluster1 kernel: [ 161.251349] ---[ end trace 0000000000000000 ]---
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064176/+subscriptions
Status: Fix Released => 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/2064176
Title:
LXD fan bridge causes blocked tasks
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Noble:
Fix Committed
Bug description:
SRU Justification:
[Impact]
User can trigger a host crash on Jammy/Noble by launching
a container which uses Ubuntu FAN network in LXD.
[Fix]
A first proposed patch fixes RCU locking by releasing rcu_read_lock
on the skb discard codepath.
Second patch just use a proper way (dev_core_stats_tx_dropped_inc() function)
to increase netdev's tx_dropped statistic value.
[Test Plan]
As provided by Max Asnaashari:
# Install LXD from channel latest/stable
snap install lxd --channel latest/stable
# Configure LXD
lxd init --auto
# Create a FAN network
lxc network create lxdfan0 bridge.mode=fan ipv4.nat=true
# Launch a container using the FAN network
lxc launch ubuntu-minimal:22.04 c1 --network lxdfan0
# Try to interact with LXD
lxc ls
[Where problems could occur]
Change is local and only related to Ubuntu FAN code. I would not expect
any problems with this patchset.
Hi, cross posting this from
https://github.com/canonical/lxd/issues/12161
I've got a lxd cluster running across 3 VMs using the fan bridge. I'm
using a dev revision of LXD based on 6413a948. Creating a container
causes the trace in the attached syslog snippet; this causes the
container creation process to hang indefinitely. ssh logins, `lxc
shell cluster1`, and `ps -aux` also hang.
Apr 29 17:15:01 cluster1 kernel: [ 161.250951] ------------[ cut here ]------------
Apr 29 17:15:01 cluster1 kernel: [ 161.250957] Voluntary context switch within RCU read-side critical section!
Apr 29 17:15:01 cluster1 kernel: [ 161.250990] WARNING: CPU: 2 PID: 510 at kernel/rcu/tree_plugin.h:320 rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [ 161.251003] Modules linked in: nft_masq nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vxlan ip6_udp_tunnel udp_tunnel dummy br
idge stp llc zfs(PO) spl(O) nf_tables libcrc32c nfnetlink vhost_vsock vhost vhost_iotlb binfmt_misc nls_iso8859_1 intel_rapl_msr intel_rapl_common kvm_intel kvm irqbypass crct10dif
_pclmul crc32_pclmul virtio_gpu polyval_clmulni polyval_generic ghash_clmulni_intel sha256_ssse3 sha1_ssse3 virtio_dma_buf aesni_intel vmw_vsock_virtio_transport 9pnet_virtio xhci_
pci drm_shmem_helper i2c_i801 ahci 9pnet vmw_vsock_virtio_transport_common xhci_pci_renesas drm_kms_helper libahci crypto_simd joydev virtio_input cryptd lpc_ich virtiofs i2c_smbus
vsock psmouse input_leds mac_hid serio_raw rapl qemu_fw_cfg vmgenid nfsd dm_multipath auth_rpcgss scsi_dh_rdac nfs_acl lockd scsi_dh_emc scsi_dh_alua grace sch_fq_codel drm sunrpc
efi_pstore virtio_rng ip_tables x_tables autofs4
Apr 29 17:15:01 cluster1 kernel: [ 161.251085] CPU: 2 PID: 510 Comm: nmbd Tainted: P O 6.5.0-28-generic #29~22.04.1-Ubuntu
Apr 29 17:15:01 cluster1 kernel: [ 161.251089] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009)/LXD, BIOS unknown 2/2/2022
Apr 29 17:15:01 cluster1 kernel: [ 161.251091] RIP: 0010:rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [ 161.251095] Code: 08 f0 83 44 24 fc 00 48 89 de 4c 89 f7 e8 d1 af ff ff e9 1e fe ff ff 48 c7 c7 d0 60 56 88 c6 05 e6 27 40 02 01 e8 79 b2 f2 ff
<0f> 0b e9 bd fd ff ff a9 ff ff ff 7f 0f 84 75 fe ff ff 65 48 8b 3c
Apr 29 17:15:01 cluster1 kernel: [ 161.251098] RSP: 0018:ffffb9cbc11dbbc8 EFLAGS: 00010046
Apr 29 17:15:01 cluster1 kernel: [ 161.251101] RAX: 0000000000000000 RBX: ffff941ef7cb3f80 RCX: 0000000000000000
Apr 29 17:15:01 cluster1 kernel: [ 161.251103] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Apr 29 17:15:01 cluster1 kernel: [ 161.251104] RBP: ffffb9cbc11dbbe8 R08: 0000000000000000 R09: 0000000000000000
Apr 29 17:15:01 cluster1 kernel: [ 161.251106] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Apr 29 17:15:01 cluster1 kernel: [ 161.251111] R13: ffff941d893e9980 R14: 0000000000000000 R15: ffff941d80ad7a80
Apr 29 17:15:01 cluster1 kernel: [ 161.251113] FS: 00007c7dcbdb8a00(0000) GS:ffff941ef7c80000(0000) knlGS:0000000000000000
Apr 29 17:15:01 cluster1 kernel: [ 161.251115] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 29 17:15:01 cluster1 kernel: [ 161.251117] CR2: 00005a30877ae488 CR3: 0000000105888003 CR4: 0000000000170ee0
Apr 29 17:15:01 cluster1 kernel: [ 161.251122] Call Trace:
Apr 29 17:15:01 cluster1 kernel: [ 161.251128] <TASK>
Apr 29 17:15:01 cluster1 kernel: [ 161.251133] ? show_regs+0x6d/0x80
Apr 29 17:15:01 cluster1 kernel: [ 161.251145] ? __warn+0x89/0x160
Apr 29 17:15:01 cluster1 kernel: [ 161.251152] ? rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [ 161.251155] ? report_bug+0x17e/0x1b0
Apr 29 17:15:01 cluster1 kernel: [ 161.251172] ? handle_bug+0x46/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251187] ? exc_invalid_op+0x18/0x80
Apr 29 17:15:01 cluster1 kernel: [ 161.251190] ? asm_exc_invalid_op+0x1b/0x20
Apr 29 17:15:01 cluster1 kernel: [ 161.251202] ? rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [ 161.251205] ? rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [ 161.251208] __schedule+0xcc/0x750
Apr 29 17:15:01 cluster1 kernel: [ 161.251218] schedule+0x63/0x110
Apr 29 17:15:01 cluster1 kernel: [ 161.251222] schedule_hrtimeout_range_clock+0xbc/0x130
Apr 29 17:15:01 cluster1 kernel: [ 161.251238] ? __pfx_hrtimer_wakeup+0x10/0x10
Apr 29 17:15:01 cluster1 kernel: [ 161.251245] schedule_hrtimeout_range+0x13/0x30
Apr 29 17:15:01 cluster1 kernel: [ 161.251248] ep_poll+0x33f/0x390
Apr 29 17:15:01 cluster1 kernel: [ 161.251254] ? __pfx_ep_autoremove_wake_function+0x10/0x10
Apr 29 17:15:01 cluster1 kernel: [ 161.251257] do_epoll_wait+0xdb/0x100
Apr 29 17:15:01 cluster1 kernel: [ 161.251259] __x64_sys_epoll_wait+0x6f/0x110
Apr 29 17:15:01 cluster1 kernel: [ 161.251265] do_syscall_64+0x5b/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251270] ? do_epoll_ctl+0x3cb/0x860
Apr 29 17:15:01 cluster1 kernel: [ 161.251273] ? __task_pid_nr_ns+0x6c/0xc0
Apr 29 17:15:01 cluster1 kernel: [ 161.251279] ? exit_to_user_mode_prepare+0x30/0xb0
Apr 29 17:15:01 cluster1 kernel: [ 161.251284] ? syscall_exit_to_user_mode+0x37/0x60
Apr 29 17:15:01 cluster1 kernel: [ 161.251286] ? do_syscall_64+0x67/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251288] ? syscall_exit_to_user_mode+0x37/0x60
Apr 29 17:15:01 cluster1 kernel: [ 161.251300] ? do_syscall_64+0x67/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251304] ? syscall_exit_to_user_mode+0x37/0x60
Apr 29 17:15:01 cluster1 kernel: [ 161.251306] ? do_syscall_64+0x67/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251309] ? do_syscall_64+0x67/0x90
Apr 29 17:15:01 cluster1 kernel: [ 161.251313] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
Apr 29 17:15:01 cluster1 kernel: [ 161.251316] RIP: 0033:0x7c7dcf325dea
Apr 29 17:15:01 cluster1 kernel: [ 161.251333] Code: 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 e8 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 5e c3 0f 1f 44 00 00 48 83 ec 28 89 54 24 18
Apr 29 17:15:01 cluster1 kernel: [ 161.251335] RSP: 002b:00007ffdde5e0278 EFLAGS: 00000246 ORIG_RAX: 00000000000000e8
Apr 29 17:15:01 cluster1 kernel: [ 161.251338] RAX: ffffffffffffffda RBX: 00005a30877a2ea0 RCX: 00007c7dcf325dea
Apr 29 17:15:01 cluster1 kernel: [ 161.251340] RDX: 0000000000000001 RSI: 00007ffdde5e02ac RDI: 0000000000000005
Apr 29 17:15:01 cluster1 kernel: [ 161.251341] RBP: 00005a3087794590 R08: 00000000000f423f R09: 00007ffdde5e0357
Apr 29 17:15:01 cluster1 kernel: [ 161.251343] R10: 00000000000003e8 R11: 0000000000000246 R12: 00005a30877a2f30
Apr 29 17:15:01 cluster1 kernel: [ 161.251345] R13: 00000000000003e8 R14: 0000000000000090 R15: 000000000000000a
Apr 29 17:15:01 cluster1 kernel: [ 161.251348] </TASK>
Apr 29 17:15:01 cluster1 kernel: [ 161.251349] ---[ end trace 0000000000000000 ]---
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064176/+subscriptions
[Bug 2081866] Re: Support ov05c10 camera sensor in Intel ipu-bridge
** Tags added: jira-somerville-1210
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2081866
Title:
Support ov05c10 camera sensor in Intel ipu-bridge
Status in linux package in Ubuntu:
New
Status in linux-oem-6.11 package in Ubuntu:
New
Status in linux source package in Noble:
New
Status in linux-oem-6.11 source package in Noble:
New
Status in linux source package in Oracular:
New
Status in linux-oem-6.11 source package in Oracular:
New
Bug description:
Proposed fix:
https://github.com/intel/ipu6-drivers/blob/master/patch/v6.8/0012-media-
Support-ov05c10-camera-sensor.patch
Camera sensor driver is only available in ipu6-drivers/oracular >=
0~git202407190257.9369b88e-0ubuntu1, which is only compiled along with
v6.11 kernels such as linux-6.11/oracular and linux-oem-6.11/noble.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081866/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2081866
Title:
Support ov05c10 camera sensor in Intel ipu-bridge
Status in linux package in Ubuntu:
New
Status in linux-oem-6.11 package in Ubuntu:
New
Status in linux source package in Noble:
New
Status in linux-oem-6.11 source package in Noble:
New
Status in linux source package in Oracular:
New
Status in linux-oem-6.11 source package in Oracular:
New
Bug description:
Proposed fix:
https://github.com/intel/ipu6-drivers/blob/master/patch/v6.8/0012-media-
Support-ov05c10-camera-sensor.patch
Camera sensor driver is only available in ipu6-drivers/oracular >=
0~git202407190257.9369b88e-0ubuntu1, which is only compiled along with
v6.11 kernels such as linux-6.11/oracular and linux-oem-6.11/noble.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081866/+subscriptions
[Bug 2084337] Re: [Intel 9460/9560] Bose QC35-II won't stay paired after upgrade to 24.10
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (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/2084337
Title:
[Intel 9460/9560] Bose QC35-II won't stay paired after upgrade to
24.10
Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
I've Bose QuietComfort 35 II bluetooth headphones/headset that I've
been using with Ubuntu for several years now. Since I upgraded to
Ubuntu 24.10 yesterday, the headset refuses to connect to Ubuntu until
I pair it again, every time.
This is how things worked with 24.04 LTS:
- I turn on the headset, it plays a little "I'm on" trill
- the headset autoconnects to my phone and plays a little "I'm connected trill"
- the headset autoconnects to my laptop and plays a little "I'm connected trill" (this was sometimes delayed by a few tens seconds, so sometimes I sped things up by running a shell script to `bluetoothctl connect $headset_mac_address`)
- I can now play sounds through the headset
This is how thigs go with 24.10:
- I turn on the headset, it plays a little "I'm on" trill
- the headset autoconnects to my phone and plays a little "I'm connected trill"
- the second connection never comes through
- I run `bluetoothctl connect $headset_mac_address` and I get
Attempting to connect to 60:AB:D2:43:49:4D
[CHG] Device 60:AB:D2:43:49:4D Connected: yes
Failed to connect: org.bluez.Error.Failed br-connection-unknown
- I open the Bose Connect app on my phone to look at the list of connections. It shows my phone and nothing else. It should be showing my laptop ("blynas") under History, and it used to do that before the upgrade.
- I click "Connect new..." in the phone app (or pull and hold the button on the headset itself to put it in pairing mode), I hear a "ready to be paired" trill, I run `bluetooth connect $headset_mac_address` again (or click connect in gnome-control-center), and it connects fine. I can play music and everything. "blynas" is shown in the Current list of connected devices
- I turn off the headset, I turn it back on
- the headset autoconnects to both the phone and the laptop, because I'm intentionally trying to reproduce the bug, so of course it won't bug.
Previously, whenever I turned the headset on after turning it off for
a longer span of time, I had to do the 'Connect new...' thing.
BTW once I tried to tell gnome-control-center to forget the headset,
then paired it fresh, which got me a fresh new LinkKey in
/var/lib/bluetooth/, and things worked fine until another turn-off-
wait-hours-turn-on-oh-hey-what-is-this-new-laptop-I-don't-know-her-do-
the-pairing-dance-again-please.
(I keep track of the link key changes because I have a Windows 10
partition on this machine and I sometimes boot it, so I need to keep
the link key synchronized between Ubuntu and the Windows registry,
otherwise the headset will work only in one of the two OSes. However
I haven't booted Windows in months if not years, so this should not be
relevant.)
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: bluez 5.77-0ubuntu1
ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0
Uname: Linux 6.11.0-8-generic x86_64
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 12 15:24:54 2024
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1949 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20Q0CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-8-generic root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to oracular on 2024-10-11 (1 days ago)
dmi.bios.date: 07/25/2023
dmi.bios.release: 1.80
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JETA2W (1.80 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias: dmi:bvnLENOVO:bvrN2JETA2W(1.80):bd07/25/2023:br1.80:efr1.15:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Q0_BU_Think_FM_ThinkPadX390:
dmi.product.family: ThinkPad X390
dmi.product.name: 20Q0CTO1WW
dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390
dmi.product.version: ThinkPad X390
dmi.sys.vendor: LENOVO
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 38:00:25:8D:A7:83 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN
RX bytes:90167 acl:152 sco:0 events:6236 errors:0
TX bytes:2703900 acl:2480 sco:0 commands:3016 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084337/+subscriptions
** Changed in: linux-firmware (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/2084337
Title:
[Intel 9460/9560] Bose QC35-II won't stay paired after upgrade to
24.10
Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
I've Bose QuietComfort 35 II bluetooth headphones/headset that I've
been using with Ubuntu for several years now. Since I upgraded to
Ubuntu 24.10 yesterday, the headset refuses to connect to Ubuntu until
I pair it again, every time.
This is how things worked with 24.04 LTS:
- I turn on the headset, it plays a little "I'm on" trill
- the headset autoconnects to my phone and plays a little "I'm connected trill"
- the headset autoconnects to my laptop and plays a little "I'm connected trill" (this was sometimes delayed by a few tens seconds, so sometimes I sped things up by running a shell script to `bluetoothctl connect $headset_mac_address`)
- I can now play sounds through the headset
This is how thigs go with 24.10:
- I turn on the headset, it plays a little "I'm on" trill
- the headset autoconnects to my phone and plays a little "I'm connected trill"
- the second connection never comes through
- I run `bluetoothctl connect $headset_mac_address` and I get
Attempting to connect to 60:AB:D2:43:49:4D
[CHG] Device 60:AB:D2:43:49:4D Connected: yes
Failed to connect: org.bluez.Error.Failed br-connection-unknown
- I open the Bose Connect app on my phone to look at the list of connections. It shows my phone and nothing else. It should be showing my laptop ("blynas") under History, and it used to do that before the upgrade.
- I click "Connect new..." in the phone app (or pull and hold the button on the headset itself to put it in pairing mode), I hear a "ready to be paired" trill, I run `bluetooth connect $headset_mac_address` again (or click connect in gnome-control-center), and it connects fine. I can play music and everything. "blynas" is shown in the Current list of connected devices
- I turn off the headset, I turn it back on
- the headset autoconnects to both the phone and the laptop, because I'm intentionally trying to reproduce the bug, so of course it won't bug.
Previously, whenever I turned the headset on after turning it off for
a longer span of time, I had to do the 'Connect new...' thing.
BTW once I tried to tell gnome-control-center to forget the headset,
then paired it fresh, which got me a fresh new LinkKey in
/var/lib/bluetooth/, and things worked fine until another turn-off-
wait-hours-turn-on-oh-hey-what-is-this-new-laptop-I-don't-know-her-do-
the-pairing-dance-again-please.
(I keep track of the link key changes because I have a Windows 10
partition on this machine and I sometimes boot it, so I need to keep
the link key synchronized between Ubuntu and the Windows registry,
otherwise the headset will work only in one of the two OSes. However
I haven't booted Windows in months if not years, so this should not be
relevant.)
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: bluez 5.77-0ubuntu1
ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0
Uname: Linux 6.11.0-8-generic x86_64
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 12 15:24:54 2024
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1949 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20Q0CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-8-generic root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to oracular on 2024-10-11 (1 days ago)
dmi.bios.date: 07/25/2023
dmi.bios.release: 1.80
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JETA2W (1.80 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias: dmi:bvnLENOVO:bvrN2JETA2W(1.80):bd07/25/2023:br1.80:efr1.15:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Q0_BU_Think_FM_ThinkPadX390:
dmi.product.family: ThinkPad X390
dmi.product.name: 20Q0CTO1WW
dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390
dmi.product.version: ThinkPad X390
dmi.sys.vendor: LENOVO
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 38:00:25:8D:A7:83 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN
RX bytes:90167 acl:152 sco:0 events:6236 errors:0
TX bytes:2703900 acl:2480 sco:0 commands:3016 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084337/+subscriptions
[Bug 2084337] Re: [Intel 9460/9560] Bose QC35-II won't stay paired after upgrade to 24.10
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/2084337
Title:
[Intel 9460/9560] Bose QC35-II won't stay paired after upgrade to
24.10
Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
I've Bose QuietComfort 35 II bluetooth headphones/headset that I've
been using with Ubuntu for several years now. Since I upgraded to
Ubuntu 24.10 yesterday, the headset refuses to connect to Ubuntu until
I pair it again, every time.
This is how things worked with 24.04 LTS:
- I turn on the headset, it plays a little "I'm on" trill
- the headset autoconnects to my phone and plays a little "I'm connected trill"
- the headset autoconnects to my laptop and plays a little "I'm connected trill" (this was sometimes delayed by a few tens seconds, so sometimes I sped things up by running a shell script to `bluetoothctl connect $headset_mac_address`)
- I can now play sounds through the headset
This is how thigs go with 24.10:
- I turn on the headset, it plays a little "I'm on" trill
- the headset autoconnects to my phone and plays a little "I'm connected trill"
- the second connection never comes through
- I run `bluetoothctl connect $headset_mac_address` and I get
Attempting to connect to 60:AB:D2:43:49:4D
[CHG] Device 60:AB:D2:43:49:4D Connected: yes
Failed to connect: org.bluez.Error.Failed br-connection-unknown
- I open the Bose Connect app on my phone to look at the list of connections. It shows my phone and nothing else. It should be showing my laptop ("blynas") under History, and it used to do that before the upgrade.
- I click "Connect new..." in the phone app (or pull and hold the button on the headset itself to put it in pairing mode), I hear a "ready to be paired" trill, I run `bluetooth connect $headset_mac_address` again (or click connect in gnome-control-center), and it connects fine. I can play music and everything. "blynas" is shown in the Current list of connected devices
- I turn off the headset, I turn it back on
- the headset autoconnects to both the phone and the laptop, because I'm intentionally trying to reproduce the bug, so of course it won't bug.
Previously, whenever I turned the headset on after turning it off for
a longer span of time, I had to do the 'Connect new...' thing.
BTW once I tried to tell gnome-control-center to forget the headset,
then paired it fresh, which got me a fresh new LinkKey in
/var/lib/bluetooth/, and things worked fine until another turn-off-
wait-hours-turn-on-oh-hey-what-is-this-new-laptop-I-don't-know-her-do-
the-pairing-dance-again-please.
(I keep track of the link key changes because I have a Windows 10
partition on this machine and I sometimes boot it, so I need to keep
the link key synchronized between Ubuntu and the Windows registry,
otherwise the headset will work only in one of the two OSes. However
I haven't booted Windows in months if not years, so this should not be
relevant.)
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: bluez 5.77-0ubuntu1
ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0
Uname: Linux 6.11.0-8-generic x86_64
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 12 15:24:54 2024
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1949 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20Q0CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-8-generic root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to oracular on 2024-10-11 (1 days ago)
dmi.bios.date: 07/25/2023
dmi.bios.release: 1.80
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JETA2W (1.80 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias: dmi:bvnLENOVO:bvrN2JETA2W(1.80):bd07/25/2023:br1.80:efr1.15:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Q0_BU_Think_FM_ThinkPadX390:
dmi.product.family: ThinkPad X390
dmi.product.name: 20Q0CTO1WW
dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390
dmi.product.version: ThinkPad X390
dmi.sys.vendor: LENOVO
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 38:00:25:8D:A7:83 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN
RX bytes:90167 acl:152 sco:0 events:6236 errors:0
TX bytes:2703900 acl:2480 sco:0 commands:3016 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084337/+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/2084337
Title:
[Intel 9460/9560] Bose QC35-II won't stay paired after upgrade to
24.10
Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
I've Bose QuietComfort 35 II bluetooth headphones/headset that I've
been using with Ubuntu for several years now. Since I upgraded to
Ubuntu 24.10 yesterday, the headset refuses to connect to Ubuntu until
I pair it again, every time.
This is how things worked with 24.04 LTS:
- I turn on the headset, it plays a little "I'm on" trill
- the headset autoconnects to my phone and plays a little "I'm connected trill"
- the headset autoconnects to my laptop and plays a little "I'm connected trill" (this was sometimes delayed by a few tens seconds, so sometimes I sped things up by running a shell script to `bluetoothctl connect $headset_mac_address`)
- I can now play sounds through the headset
This is how thigs go with 24.10:
- I turn on the headset, it plays a little "I'm on" trill
- the headset autoconnects to my phone and plays a little "I'm connected trill"
- the second connection never comes through
- I run `bluetoothctl connect $headset_mac_address` and I get
Attempting to connect to 60:AB:D2:43:49:4D
[CHG] Device 60:AB:D2:43:49:4D Connected: yes
Failed to connect: org.bluez.Error.Failed br-connection-unknown
- I open the Bose Connect app on my phone to look at the list of connections. It shows my phone and nothing else. It should be showing my laptop ("blynas") under History, and it used to do that before the upgrade.
- I click "Connect new..." in the phone app (or pull and hold the button on the headset itself to put it in pairing mode), I hear a "ready to be paired" trill, I run `bluetooth connect $headset_mac_address` again (or click connect in gnome-control-center), and it connects fine. I can play music and everything. "blynas" is shown in the Current list of connected devices
- I turn off the headset, I turn it back on
- the headset autoconnects to both the phone and the laptop, because I'm intentionally trying to reproduce the bug, so of course it won't bug.
Previously, whenever I turned the headset on after turning it off for
a longer span of time, I had to do the 'Connect new...' thing.
BTW once I tried to tell gnome-control-center to forget the headset,
then paired it fresh, which got me a fresh new LinkKey in
/var/lib/bluetooth/, and things worked fine until another turn-off-
wait-hours-turn-on-oh-hey-what-is-this-new-laptop-I-don't-know-her-do-
the-pairing-dance-again-please.
(I keep track of the link key changes because I have a Windows 10
partition on this machine and I sometimes boot it, so I need to keep
the link key synchronized between Ubuntu and the Windows registry,
otherwise the headset will work only in one of the two OSes. However
I haven't booted Windows in months if not years, so this should not be
relevant.)
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: bluez 5.77-0ubuntu1
ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0
Uname: Linux 6.11.0-8-generic x86_64
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 12 15:24:54 2024
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1949 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20Q0CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-8-generic root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to oracular on 2024-10-11 (1 days ago)
dmi.bios.date: 07/25/2023
dmi.bios.release: 1.80
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JETA2W (1.80 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias: dmi:bvnLENOVO:bvrN2JETA2W(1.80):bd07/25/2023:br1.80:efr1.15:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Q0_BU_Think_FM_ThinkPadX390:
dmi.product.family: ThinkPad X390
dmi.product.name: 20Q0CTO1WW
dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390
dmi.product.version: ThinkPad X390
dmi.sys.vendor: LENOVO
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 38:00:25:8D:A7:83 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN
RX bytes:90167 acl:152 sco:0 events:6236 errors:0
TX bytes:2703900 acl:2480 sco:0 commands:3016 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084337/+subscriptions
[Bug 2084337] Re: [Intel 9460/9560] Bose QC35-II won't stay paired after upgrade to 24.10
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (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/2084337
Title:
[Intel 9460/9560] Bose QC35-II won't stay paired after upgrade to
24.10
Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
I've Bose QuietComfort 35 II bluetooth headphones/headset that I've
been using with Ubuntu for several years now. Since I upgraded to
Ubuntu 24.10 yesterday, the headset refuses to connect to Ubuntu until
I pair it again, every time.
This is how things worked with 24.04 LTS:
- I turn on the headset, it plays a little "I'm on" trill
- the headset autoconnects to my phone and plays a little "I'm connected trill"
- the headset autoconnects to my laptop and plays a little "I'm connected trill" (this was sometimes delayed by a few tens seconds, so sometimes I sped things up by running a shell script to `bluetoothctl connect $headset_mac_address`)
- I can now play sounds through the headset
This is how thigs go with 24.10:
- I turn on the headset, it plays a little "I'm on" trill
- the headset autoconnects to my phone and plays a little "I'm connected trill"
- the second connection never comes through
- I run `bluetoothctl connect $headset_mac_address` and I get
Attempting to connect to 60:AB:D2:43:49:4D
[CHG] Device 60:AB:D2:43:49:4D Connected: yes
Failed to connect: org.bluez.Error.Failed br-connection-unknown
- I open the Bose Connect app on my phone to look at the list of connections. It shows my phone and nothing else. It should be showing my laptop ("blynas") under History, and it used to do that before the upgrade.
- I click "Connect new..." in the phone app (or pull and hold the button on the headset itself to put it in pairing mode), I hear a "ready to be paired" trill, I run `bluetooth connect $headset_mac_address` again (or click connect in gnome-control-center), and it connects fine. I can play music and everything. "blynas" is shown in the Current list of connected devices
- I turn off the headset, I turn it back on
- the headset autoconnects to both the phone and the laptop, because I'm intentionally trying to reproduce the bug, so of course it won't bug.
Previously, whenever I turned the headset on after turning it off for
a longer span of time, I had to do the 'Connect new...' thing.
BTW once I tried to tell gnome-control-center to forget the headset,
then paired it fresh, which got me a fresh new LinkKey in
/var/lib/bluetooth/, and things worked fine until another turn-off-
wait-hours-turn-on-oh-hey-what-is-this-new-laptop-I-don't-know-her-do-
the-pairing-dance-again-please.
(I keep track of the link key changes because I have a Windows 10
partition on this machine and I sometimes boot it, so I need to keep
the link key synchronized between Ubuntu and the Windows registry,
otherwise the headset will work only in one of the two OSes. However
I haven't booted Windows in months if not years, so this should not be
relevant.)
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: bluez 5.77-0ubuntu1
ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0
Uname: Linux 6.11.0-8-generic x86_64
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 12 15:24:54 2024
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1949 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20Q0CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-8-generic root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to oracular on 2024-10-11 (1 days ago)
dmi.bios.date: 07/25/2023
dmi.bios.release: 1.80
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JETA2W (1.80 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias: dmi:bvnLENOVO:bvrN2JETA2W(1.80):bd07/25/2023:br1.80:efr1.15:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Q0_BU_Think_FM_ThinkPadX390:
dmi.product.family: ThinkPad X390
dmi.product.name: 20Q0CTO1WW
dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390
dmi.product.version: ThinkPad X390
dmi.sys.vendor: LENOVO
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 38:00:25:8D:A7:83 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN
RX bytes:90167 acl:152 sco:0 events:6236 errors:0
TX bytes:2703900 acl:2480 sco:0 commands:3016 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084337/+subscriptions
** Changed in: bluez (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/2084337
Title:
[Intel 9460/9560] Bose QC35-II won't stay paired after upgrade to
24.10
Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
I've Bose QuietComfort 35 II bluetooth headphones/headset that I've
been using with Ubuntu for several years now. Since I upgraded to
Ubuntu 24.10 yesterday, the headset refuses to connect to Ubuntu until
I pair it again, every time.
This is how things worked with 24.04 LTS:
- I turn on the headset, it plays a little "I'm on" trill
- the headset autoconnects to my phone and plays a little "I'm connected trill"
- the headset autoconnects to my laptop and plays a little "I'm connected trill" (this was sometimes delayed by a few tens seconds, so sometimes I sped things up by running a shell script to `bluetoothctl connect $headset_mac_address`)
- I can now play sounds through the headset
This is how thigs go with 24.10:
- I turn on the headset, it plays a little "I'm on" trill
- the headset autoconnects to my phone and plays a little "I'm connected trill"
- the second connection never comes through
- I run `bluetoothctl connect $headset_mac_address` and I get
Attempting to connect to 60:AB:D2:43:49:4D
[CHG] Device 60:AB:D2:43:49:4D Connected: yes
Failed to connect: org.bluez.Error.Failed br-connection-unknown
- I open the Bose Connect app on my phone to look at the list of connections. It shows my phone and nothing else. It should be showing my laptop ("blynas") under History, and it used to do that before the upgrade.
- I click "Connect new..." in the phone app (or pull and hold the button on the headset itself to put it in pairing mode), I hear a "ready to be paired" trill, I run `bluetooth connect $headset_mac_address` again (or click connect in gnome-control-center), and it connects fine. I can play music and everything. "blynas" is shown in the Current list of connected devices
- I turn off the headset, I turn it back on
- the headset autoconnects to both the phone and the laptop, because I'm intentionally trying to reproduce the bug, so of course it won't bug.
Previously, whenever I turned the headset on after turning it off for
a longer span of time, I had to do the 'Connect new...' thing.
BTW once I tried to tell gnome-control-center to forget the headset,
then paired it fresh, which got me a fresh new LinkKey in
/var/lib/bluetooth/, and things worked fine until another turn-off-
wait-hours-turn-on-oh-hey-what-is-this-new-laptop-I-don't-know-her-do-
the-pairing-dance-again-please.
(I keep track of the link key changes because I have a Windows 10
partition on this machine and I sometimes boot it, so I need to keep
the link key synchronized between Ubuntu and the Windows registry,
otherwise the headset will work only in one of the two OSes. However
I haven't booted Windows in months if not years, so this should not be
relevant.)
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: bluez 5.77-0ubuntu1
ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0
Uname: Linux 6.11.0-8-generic x86_64
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 12 15:24:54 2024
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1949 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20Q0CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-8-generic root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to oracular on 2024-10-11 (1 days ago)
dmi.bios.date: 07/25/2023
dmi.bios.release: 1.80
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JETA2W (1.80 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias: dmi:bvnLENOVO:bvrN2JETA2W(1.80):bd07/25/2023:br1.80:efr1.15:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Q0_BU_Think_FM_ThinkPadX390:
dmi.product.family: ThinkPad X390
dmi.product.name: 20Q0CTO1WW
dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390
dmi.product.version: ThinkPad X390
dmi.sys.vendor: LENOVO
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 38:00:25:8D:A7:83 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN
RX bytes:90167 acl:152 sco:0 events:6236 errors:0
TX bytes:2703900 acl:2480 sco:0 commands:3016 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084337/+subscriptions
[Bug 2084474] Re: The brightness in my pc keeps getting full after this update
Did it start happening after you upgraded to a specific kernel version
or has it always been the case?
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084474
Title:
The brightness in my pc keeps getting full after this update
Status in gnome-settings-daemon package in Ubuntu:
New
Status in linux package in Ubuntu:
New
Bug description:
Even when i'm using the pc and when i type something on keyboard, it shows the brightness levels are full.
when i decreased the brightness it when full again when i started to type something on my keyboard.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 14 20:55:50 2024
DistUpgraded: 2024-09-14 23:18:12,706 DEBUG migrateToDeb822Sources()
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
Intel Corporation Tiger Lake-LP GT2 [UHD Graphics G4] [8086:9a78] (rev 01) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Tiger Lake-LP GT2 [UHD Graphics G4] [103c:87fe]
InstallationDate: Installed on 2023-12-23 (296 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera
Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: HP HP Laptop 15s-fr2xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic root=UUID=ea8f07ce-d1f7-4dca-a636-e8095e7cfaf2 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2024-09-14 (30 days ago)
dmi.bios.date: 07/04/2023
dmi.bios.release: 15.32
dmi.bios.vendor: AMI
dmi.bios.version: F.32
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 87FE
dmi.board.vendor: HP
dmi.board.version: 57.26
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 57.26
dmi.modalias: dmi:bvnAMI:bvrF.32:bd07/04/2023:br15.32:efr57.26:svnHP:pnHPLaptop15s-fr2xxx:pvr:rvnHP:rn87FE:rvr57.26:cvnHP:ct10:cvrChassisVersion:sku34W78PA#ACJ:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 15s-fr2xxx
dmi.product.sku: 34W78PA#ACJ
dmi.sys.vendor: HP
mtime.conffile..etc.init.d.apport: 2024-07-22T20:29:07
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1
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/gnome-settings-daemon/+bug/2084474/+subscriptions
or has it always been the case?
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084474
Title:
The brightness in my pc keeps getting full after this update
Status in gnome-settings-daemon package in Ubuntu:
New
Status in linux package in Ubuntu:
New
Bug description:
Even when i'm using the pc and when i type something on keyboard, it shows the brightness levels are full.
when i decreased the brightness it when full again when i started to type something on my keyboard.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 14 20:55:50 2024
DistUpgraded: 2024-09-14 23:18:12,706 DEBUG migrateToDeb822Sources()
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
Intel Corporation Tiger Lake-LP GT2 [UHD Graphics G4] [8086:9a78] (rev 01) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Tiger Lake-LP GT2 [UHD Graphics G4] [103c:87fe]
InstallationDate: Installed on 2023-12-23 (296 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera
Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: HP HP Laptop 15s-fr2xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic root=UUID=ea8f07ce-d1f7-4dca-a636-e8095e7cfaf2 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2024-09-14 (30 days ago)
dmi.bios.date: 07/04/2023
dmi.bios.release: 15.32
dmi.bios.vendor: AMI
dmi.bios.version: F.32
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 87FE
dmi.board.vendor: HP
dmi.board.version: 57.26
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 57.26
dmi.modalias: dmi:bvnAMI:bvrF.32:bd07/04/2023:br15.32:efr57.26:svnHP:pnHPLaptop15s-fr2xxx:pvr:rvnHP:rn87FE:rvr57.26:cvnHP:ct10:cvrChassisVersion:sku34W78PA#ACJ:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 15s-fr2xxx
dmi.product.sku: 34W78PA#ACJ
dmi.sys.vendor: HP
mtime.conffile..etc.init.d.apport: 2024-07-22T20:29:07
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1
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/gnome-settings-daemon/+bug/2084474/+subscriptions
[Bug 2084493] Re: thinkpad having issues with freeze after boot
I assume you did a full upgrade (do-release-upgrade) from Noble to
Oracular, right?
Can you attach the apport log to this bug? ("apport-collect 2084493"
should do that for you).
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084493
Title:
thinkpad having issues with freeze after boot
Status in linux package in Ubuntu:
Incomplete
Bug description:
after launching the kernel, the screen freezes when selecting linux
6.11.0.8
Ubuntu 24.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084493/+subscriptions
Oracular, right?
Can you attach the apport log to this bug? ("apport-collect 2084493"
should do that for you).
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084493
Title:
thinkpad having issues with freeze after boot
Status in linux package in Ubuntu:
Incomplete
Bug description:
after launching the kernel, the screen freezes when selecting linux
6.11.0.8
Ubuntu 24.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084493/+subscriptions
[Bug 2081685] Re: [Ubuntu 24.04-generic Kernel-6.8]Hard lockup on 8 Socket System, ThinkSystem SR950 V3.
You probably need to update just linux-image-unsigned, linux-modules and
linux-modules-extra packages: even if the have the same name/version
(6.8.0-32.32), they are actually different kernels - i'll try to better
differentiate the name next time.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2081685
Title:
[Ubuntu 24.04-generic Kernel-6.8]Hard lockup on 8 Socket System,
ThinkSystem SR950 V3.
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
New
Bug description:
There is CPU hard Lockup detected under Ubuntu 24.04 LTS (kernel
6.8.0-38). see attachment"dmesg0723-Lockup-Ubuntu24.04.log"
ubuntu@SR950V3:~$ cat /var/log/dmesg | grep -i lockup
[ 15.241164] kernel: watchdog: Watchdog detected hard LOCKUP on cpu
124
[ 15.241164] kernel: ? watchdog_hardlockup_check+0x1cb/0x3b0
Besides, the issue does not occur on upstream kernel 6.8，6.9, 6.10, 6.11-rc*, then only ubuntu kernel issue. see attachment "dmesg0923-No-Lockup-Kernel 6-10.log".
According to the dmesg log, the "hard lockup" is not a real lockup,
Because many CPU try to get cache_disable_lock spin lock at the same time when kernel boot. And competition has occurred here.
Every CPU's TLB will be flushed in the critical zone, the flushing TLB is a time-consuming operation, and there are so many CPUs,
so the false "hard lockup" was detected by kernel. To avoid customer confuse, when Canonical do the fix?
HW Config:
ThinkSystem SR950 V3
CPU: 8* Intel(R) Xeon(R) Platinum 8490H 60 Core 3.5GHz
MEM: 2TB = SK Hynix 356GB DDR5 4800MHz 3DS (2015.1GB)
Raid: ThinkSystem RAID 940-8i 4GB Flash PCIe Gen4 12Gb Adapter
Storage: Micron_7450_MTFDKBA960TFR *1
Samsung 30.7TB 24Gbps SAS 2.5" SSD
NIC: ThinkSystem Intel X710-T4L 10GBASE-T 4-Port OCP Ethernet Adapter
OS: ubuntu 24.04 LTS( kernel 6.8.0-38-generic)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081685/+subscriptions
linux-modules-extra packages: even if the have the same name/version
(6.8.0-32.32), they are actually different kernels - i'll try to better
differentiate the name next time.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2081685
Title:
[Ubuntu 24.04-generic Kernel-6.8]Hard lockup on 8 Socket System,
ThinkSystem SR950 V3.
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
New
Bug description:
There is CPU hard Lockup detected under Ubuntu 24.04 LTS (kernel
6.8.0-38). see attachment"dmesg0723-Lockup-Ubuntu24.04.log"
ubuntu@SR950V3:~$ cat /var/log/dmesg | grep -i lockup
[ 15.241164] kernel: watchdog: Watchdog detected hard LOCKUP on cpu
124
[ 15.241164] kernel: ? watchdog_hardlockup_check+0x1cb/0x3b0
Besides, the issue does not occur on upstream kernel 6.8，6.9, 6.10, 6.11-rc*, then only ubuntu kernel issue. see attachment "dmesg0923-No-Lockup-Kernel 6-10.log".
According to the dmesg log, the "hard lockup" is not a real lockup,
Because many CPU try to get cache_disable_lock spin lock at the same time when kernel boot. And competition has occurred here.
Every CPU's TLB will be flushed in the critical zone, the flushing TLB is a time-consuming operation, and there are so many CPUs,
so the false "hard lockup" was detected by kernel. To avoid customer confuse, when Canonical do the fix?
HW Config:
ThinkSystem SR950 V3
CPU: 8* Intel(R) Xeon(R) Platinum 8490H 60 Core 3.5GHz
MEM: 2TB = SK Hynix 356GB DDR5 4800MHz 3DS (2015.1GB)
Raid: ThinkSystem RAID 940-8i 4GB Flash PCIe Gen4 12Gb Adapter
Storage: Micron_7450_MTFDKBA960TFR *1
Samsung 30.7TB 24Gbps SAS 2.5" SSD
NIC: ThinkSystem Intel X710-T4L 10GBASE-T 4-Port OCP Ethernet Adapter
OS: ubuntu 24.04 LTS( kernel 6.8.0-38-generic)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081685/+subscriptions
Подписаться на:
Сообщения (Atom)