[Kernel-packages] [Bug 2033996] Re: ugreen bluetooth 5 usb RTL8761BUV not discovering device
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033996 Title: ugreen bluetooth 5 usb RTL8761BUV not discovering device Status in linux package in Ubuntu: Expired Bug description: MANUFACTURER: UGreen Chipset: RTL8761BUV Device: Bluetooth 5.0 Issue: This kernel(5.15.0-82) detects the usb dongle but the device itself can't detect any bluetooth devices. Resolution: Switched kernel to 6.2.0-31, but the support for the kernel is only up to February 2024, vs 5.15.0-82 which has support until April 2027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033996/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042706] Re: Kubuntu 23.10 freezes
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 If you upgraded to (k)Ubuntu 23.10 and rebooted & were able to login, then the ubuntu-release-upgrader package this bug has been filed against is no longer involved, and from your description, this reads as a support issue more than a bug report. This report can be converted to a question (making it about support) and even returned to bug report if after support it does look like you've discovered a bug, but I suggest seeking support first. I've thus changed status to "incomplete". IO error would imply a problem that needs exploration; if you can get SysRq responses then its not a crash/freeze of the base system, maybe free of GUI/or display output only. You can explore systemd logs (journalctl) & look for clues (dmesg being an example of a command only showing details of current boot thus won't be helpful if you've rebooted). This though is support related. I'll change package to 'linux' due to it working with older 6.2 kernel & reported issue only when using newer 6.5 kernel. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2042706 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Incomplete ** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042706 Title: Kubuntu 23.10 freezes Status in linux package in Ubuntu: Incomplete Bug description: I have upgraded from Kubuntu 23.04 to Kubuntu 23.10. After working for 2-7 minutes, everything becomes extremely unresponsive and freezes afterwards. The screen goes black (as if graphical shell has crashed and I am in the terminal). However, the whole system remains unresponsive. I cannot switch between terminals too (Ctrl+Alt+F) There was one symptom. When I was working in a Konsole window, and it went unresponsive. Then I managed to launch another window, and every single command returned "Input/output error" e.g.: $ ls bash: /usr/bin/ls: Input/output error I noticed I can work around the issue by switching from the 6.5.0 kernel to the older 6.2.0 one which was left from Kubuntu 23.04. The exact kernel package versions are: * linux-image-6.5.0-10-generic * linux-image-6.2.0-36-generic How can I debug the issue? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042706] [NEW] Kubuntu 23.10 freezes
You have been subscribed to a public bug: I have upgraded from Kubuntu 23.04 to Kubuntu 23.10. After working for 2-7 minutes, everything becomes extremely unresponsive and freezes afterwards. The screen goes black (as if graphical shell has crashed and I am in the terminal). However, the whole system remains unresponsive. I cannot switch between terminals too (Ctrl+Alt+F) There was one symptom. When I was working in a Konsole window, and it went unresponsive. Then I managed to launch another window, and every single command returned "Input/output error" e.g.: $ ls bash: /usr/bin/ls: Input/output error I noticed I can work around the issue by switching from the 6.5.0 kernel to the older 6.2.0 one which was left from Kubuntu 23.04. The exact kernel package versions are: * linux-image-6.5.0-10-generic * linux-image-6.2.0-36-generic How can I debug the issue? ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- Kubuntu 23.10 freezes https://bugs.launchpad.net/bugs/2042706 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040337] Re: Incorrect argument from SEV live-migration fix
This bug is awaiting verification that the linux-gcp/5.15.0-1047.55 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-gcp' to 'verification-done-jammy- linux-gcp'. If the problem still exists, change the tag 'verification- needed-jammy-linux-gcp' to 'verification-failed-jammy-linux-gcp'. 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-gcp-v2 verification-needed-jammy-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2040337 Title: Incorrect argument from SEV live-migration fix Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Bug description: [Impact] * Google requested fix to notify_range_enc_status_changed() passing incorrect argument. [Fix] * Upstream ac3f9c9f1b37 introduced change to notify_range_enc_status_changed() to accept page size instead of number of pages, but function was not updated. Updating to send correct argument. Upstream implementation changed with TDX support, and is unaffected, so no plans to upstream. [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00367134 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040337/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039732] Re: No graphic desktop environment on Google GCP instances
This bug is awaiting verification that the linux-gcp/5.15.0-1047.55 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-gcp' to 'verification-done-jammy- linux-gcp'. If the problem still exists, change the tag 'verification- needed-jammy-linux-gcp' to 'verification-failed-jammy-linux-gcp'. 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-gcp-v2 verification-needed-jammy-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039732 Title: No graphic desktop environment on Google GCP instances Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Google reports not being able to display graphic desktop environment. [Fix] * CONFIG_SYSFB_SIMPLEFB was initially enabled in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently disabled for amd64 in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not reflected in the GCP kernel config. [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression. Simple config change that was not taken from generic. [Other Info] * SF #00366439 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042707] [NEW] package nvidia-dkms-470 470.223.02-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned erro
Public bug reported: System reported an error and asked to submit a bug. Video resolution suddenly was stuck on 1024x768, after upgrade it restored back to 1080p ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-470 470.223.02-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 2 21:58:28 2023 ErrorMessage: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-12-28 (1406 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-dkms-470 470.223.02-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to jammy on 2022-06-25 (496 days ago) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2042707 Title: package nvidia-dkms-470 470.223.02-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: System reported an error and asked to submit a bug. Video resolution suddenly was stuck on 1024x768, after upgrade it restored back to 1080p ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-470 470.223.02-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 2 21:58:28 2023 ErrorMessage: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-12-28 (1406 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-dkms-470 470.223.02-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to jammy on 2022-06-25 (496 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2042707/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
This bug is awaiting verification that the linux-aws/6.2.0-1016.16 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-lunar-linux-aws' to 'verification-done-lunar- linux-aws'. If the problem still exists, change the tag 'verification- needed-lunar-linux-aws' to 'verification-failed-lunar-linux-aws'. 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-lunar-linux-aws-v2 verification-needed-lunar-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039191 Title: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization Status in linux-aws package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: Fix Committed Status in linux-aws source package in Lunar: Triaged Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: In Progress Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar [Fix] * Clean cherry pick from linux-next, commit 3e3255265291 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, isolated fix slightly modifying when value becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2039191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040039] Re: Ubuntu Server 22.04.3 randomly freezes
Hi @gco, Thanks for posting this. Although, your case is for VM and looks like the settings you have mentioned here are for the VM. I have a physical machine. Let me go through these docs and give it a try. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2040039 Title: Ubuntu Server 22.04.3 randomly freezes Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have a physical machine on which I have installed Ubuntu Server 22.04.3 . It randomly freezes. I read few forums and gathered previous boot report as well. Other information as requested: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-87-generic 5.15.0-87.97 ProcVersionSignature: Ubuntu 5.15.0-87.97-generic 5.15.122 Uname: Linux 5.15.0-87-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-87-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sat Oct 21 02:41:33 2023 InstallationDate: Installed on 2023-09-19 (31 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 2M/x2 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M MachineType: Gigabyte Technology Co., Ltd. H510M H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-87-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro RelatedPackageVersions: linux-restricted-modules-5.15.0-87-generic N/A linux-backports-modules-5.15.0-87-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2023 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F17 dmi.board.asset.tag: Default string dmi.board.name: H510M H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF17:bd03/10/2023:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnH510MH:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH510MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H510 MB dmi.product.name: H510M H dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040039/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042546] Re: Include cifs.ko in linux-modules package
This bug is awaiting verification that the linux-aws/6.2.0-1016.16 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-lunar-linux-aws' to 'verification-done-lunar- linux-aws'. If the problem still exists, change the tag 'verification- needed-lunar-linux-aws' to 'verification-failed-lunar-linux-aws'. 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-lunar-linux-aws-v2 verification-needed-lunar-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042546 Title: Include cifs.ko in linux-modules package Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification: [Impact] Commit: "smb: move client and server files to common directory fs/smb" introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For lunar:main this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. [How to reproduce it]: 1. Install the latest azure kernel 6.2.0-1016.16 2. Load cifs module $ modprobe cifs modprobe: FATAL: Module cifs not found in directory /lib/modules/6.2.0-1016-azure If modules-extra is installed, this works. [Fix] Replace fs/cifs/* with fs/smb/client/* in debian./control.d/.inclusiojn-list This is going to be done in s2023.10.02 cycle for derivatives. [Test Plan] 1. Apply the fix to one of the derivative (azure), build a new kernel and install it 2. Load cifs module $ modprobe cifs It should work without installing modules-extra. [Regression potential] Very low, it's a straightforward fix. [Other Info] Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked. There is also the possibility to do it via cranky fix, but owners may omit it during security updates and it's hard to enforce it. Plus, it is a one-time change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
This bug was fixed in the package mutter - 45.0-3ubuntu4 --- mutter (45.0-3ubuntu4) noble; urgency=medium * Cherry pick 4 commits to fix SIGKILL on lockscreen. (LP: #2034619) * Drop kms-impl-device-Inhibit-deadline-timer-on-amdgpu.patch -- Mario Limonciello Thu, 26 Oct 2023 10:27:44 -0500 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715734/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] syslog.txt
apport information
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715738/+files/syslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] rfkill.txt
apport information
** Attachment added: "rfkill.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715737/+files/rfkill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] modified.conffile..etc.bluetooth.main.conf.txt
apport information
** Attachment added: "modified.conffile..etc.bluetooth.main.conf.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715736/+files/modified.conffile..etc.bluetooth.main.conf.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] getfacl.txt
apport information
** Attachment added: "getfacl.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715735/+files/getfacl.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect
Thank you Daniel! Over the week I upgraded my laptop to Mantic, so can
no longer test for Jammy.
I still can't discover my logitech mice in Mantic, so maybe still the
same situation.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715733/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715731/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715730/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715732/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715729/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715728/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715727/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715726/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715725/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] Dependencies.txt
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715723/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715724/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect
apport information
** Tags added: apport-collected mantic wayland-session
** Description changed:
I lost the proprietary USB dongle and decided I wanted to try bluetooth
with this particular mouse. I am able to connect with bluetooth on
Windows 11, but the device doesn't even show up in `bluetoothctl scan
on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.27.0-0ubuntu5
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 23.10
+ InstallationDate: Installed on 2023-03-06 (242 days ago)
+ InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
+ InterestingModules: rfcomm bnep btusb bluetooth
+ MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
+ NonfreeKernelModules: zfs
+ Package: bluez 5.68-0ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+ LANG=en_US.UTF-8
+ PATH=(custom, no user)
+ SHELL=/usr/bin/zsh
+ TERM=xterm-256color
+ XDG_RUNTIME_DIR=
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
+ Tags: mantic wayland-session
+ Uname: Linux 6.5.0-10-generic x86_64
+ UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
+ UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
+ _MarkForUpload: True
+ dmi.bios.date: 07/18/2023
+ dmi.bios.release: 1.58
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N2HET75W (1.58 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20QDUS
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40709 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.25
+ dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
+ dmi.product.family: ThinkPad X1 Carbon 7th
+ dmi.product.name: 20QDUS
+ dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
+ dmi.product.version: ThinkPad X1 Carbon 7th
+ dmi.sys.vendor: LENOVO
+ hciconfig:
+ hci0:Type: Primary Bus: USB
+ BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
+ UP RUNNING PSCAN ISCAN INQUIRY
+ RX bytes:21473 acl:0 sco:0 events:2871 errors:0
+ TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
+ mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715722/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.25
dmi.modalias:
[Kernel-packages] [Bug 2042697] [NEW] Pull request to address thermal core issues
Public bug reported: The Grace development team has not been testing the 6.2 Ubuntu kernel but instead a newer kernel. When they run their thermal tests on a 6.2 kernel they are running into failures. Investigations have turned up several missing kernel patches. These patches are clean cherry-picks and have been tested and confirmed to fix the thermal issues we are seeing. ** Affects: linux-nvidia-6.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2042697 Title: Pull request to address thermal core issues Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: The Grace development team has not been testing the 6.2 Ubuntu kernel but instead a newer kernel. When they run their thermal tests on a 6.2 kernel they are running into failures. Investigations have turned up several missing kernel patches. These patches are clean cherry-picks and have been tested and confirmed to fix the thermal issues we are seeing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2042697/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038645] Re: Ubuntu Mate 22.04 scaling problem
However, I once found an entry saying that I can delete a file. I don't
remember the details, but it doesn't work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2038645
Title:
Ubuntu Mate 22.04 scaling problem
Status in nvidia-settings package in Ubuntu:
New
Bug description:
I changed monitor from 24" LG to 32" Samsung LS32A704NWPXEN
The situation looks like this:
1. 4K starts default, I can save settings to /etc/X11/xorg.conf only with
sudo chmod u+x /usr/share/screen-resolution-extra/nvidia-polkit
2. Problem I have with HDMI and DisplayPort, the situation is the same,
after changing from 1920x1080 to 4K I can see 1/4 of the screen
lower left part of the screen.
The problem does not occur from 4K to 1920x1080 when 4K is default.
To switch to 4K I need remove /etc/X11/xorg.conf and reboot system.
3. Scaling in Mate does not change the size of the Steam icon xD wtf? Why?
I have only option 100% and 200%.
4. Scaling with Nvidia, ( Option Underscan in second tab of nvidia-settings,
default is 0 )
I managed to check by placing the panel at the top and then changing the
scaling in nvidia
(because the image is cut off from the bottom)
It seems to me that this option does not scale, but crops the image.
Because the font and icon sizes looks identical.
Only the picture frame is cut off and the center remains.
5. This monitor does not have an image scaling option.
nvidia-settings 510.47.03-0ubuntu1
System Info
{
inxi -Fxxrzc0
System:
Kernel: 5.15.0-84-generic x86_64 bits: 64 compiler: gcc v: 11.4.0
Desktop: MATE 1.26.0 wm: marco dm: LightDM
Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
Machine:
Type: Desktop Mobo: MSI model: B150M PRO-VDH (MS-7982) v: 1.0
serial: UEFI: American Megatrends v: 3.H0
date: 07/10/2018
CPU:
Info: quad core model: Intel Core i5-6400 bits: 64 type: MCP
arch: Skylake-S rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 2256 high: 3219 min/max: 800/3300 cores: 1: 1271
2: 1623 3: 2912 4: 3219 bogomips: 21599
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: NVIDIA GA106 [Geforce RTX 3050] vendor: Gigabyte driver: nvidia
v: 525.125.06 pcie: speed: 2.5 GT/s lanes: 8 ports: active: none
off: HDMI-A-1 empty: DP-1,DP-2,HDMI-A-2 bus-ID: 01:00.0
chip-ID: 10de:2507
Display: x11 server: X.Org v: 1.21.1.4 compositors: 1: Picom v: 9
2: marco v: 1.26.0 driver: X: loaded: nvidia gpu: nvidia display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 69
Monitor-1: HDMI-0 res: 1920x1080 dpi: 70 diag: 801mm (31.5")
OpenGL: renderer: NVIDIA GeForce RTX 3050/PCIe/SSE2
v: 4.6.0 NVIDIA 525.125.06 direct render: Yes
...
Sensors:
System Temperatures: cpu: 29.8 C pch: 37.0 C mobo: 27.8 C gpu: nvidia
temp: 40 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos:
Packages: 3100 apt: 3082 snap: 18
Active apt repos in: /etc/apt/sources.list
1: deb http://pl.archive.ubuntu.com/ubuntu/ jammy main restricted
2: deb http://pl.archive.ubuntu.com/ubuntu/ jammy-updates main restricted
3: deb http://pl.archive.ubuntu.com/ubuntu/ jammy universe
4: deb http://pl.archive.ubuntu.com/ubuntu/ jammy-updates universe
5: deb http://pl.archive.ubuntu.com/ubuntu/ jammy multiverse
6: deb http://pl.archive.ubuntu.com/ubuntu/ jammy-updates multiverse
7: deb http://pl.archive.ubuntu.com/ubuntu/ jammy-backports main
restricted universe multiverse
8: deb http://security.ubuntu.com/ubuntu jammy-security main restricted
9: deb http://security.ubuntu.com/ubuntu jammy-security universe
10: deb http://security.ubuntu.com/ubuntu jammy-security multiverse
No active apt repos in:
/etc/apt/sources.list.d/minetestdevs-ubuntu-stable-jammy.list
Active apt repos in:
/etc/apt/sources.list.d/mozillateam-ubuntu-ppa-jammy.list
1: deb https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/ jammy main
2: deb-src https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/ jammy
main
Info:
Processes: 247 Uptime: 2h 7m Memory: 15.56 GiB used: 4.49 GiB (28.8%)
Init: systemd v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12
Shell: Bash v: 5.1.16 running-in: mate-terminal inxi: 3.3.13
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/2038645/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042546] Re: Include cifs.ko in linux-modules package
This bug is awaiting verification that the linux- hwe-6.2/6.2.0-37.38~22.04.1 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- hwe-6.2' to 'verification-done-jammy-linux-hwe-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.2' to 'verification-failed-jammy-linux-hwe-6.2'. 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-hwe-6.2-v2 verification-needed-jammy-linux-hwe-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042546 Title: Include cifs.ko in linux-modules package Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification: [Impact] Commit: "smb: move client and server files to common directory fs/smb" introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For lunar:main this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. [How to reproduce it]: 1. Install the latest azure kernel 6.2.0-1016.16 2. Load cifs module $ modprobe cifs modprobe: FATAL: Module cifs not found in directory /lib/modules/6.2.0-1016-azure If modules-extra is installed, this works. [Fix] Replace fs/cifs/* with fs/smb/client/* in debian./control.d/.inclusiojn-list This is going to be done in s2023.10.02 cycle for derivatives. [Test Plan] 1. Apply the fix to one of the derivative (azure), build a new kernel and install it 2. Load cifs module $ modprobe cifs It should work without installing modules-extra. [Regression potential] Very low, it's a straightforward fix. [Other Info] Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked. There is also the possibility to do it via cranky fix, but owners may omit it during security updates and it's hard to enforce it. Plus, it is a one-time change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042564] Re: Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4 Ubuntu 20.04 kernel
I'm currently bisecting the releases and kernels, using releases between 5.4 and 5.15 on an LXD VM. Releases 5.4 through 5.13 exhibit similar speeds, with 5.15 showing a drop-off. The numbers aren't quite the same as above, but that's likely due to setup: 5.4: 744MiB/s average 5.11: 785MiB/s average 5.13: 711MiB/s average 5.15: 602MiB/s average -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042564 Title: Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4 Ubuntu 20.04 kernel Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: We in the Canonical Public Cloud team have received report from our colleagues in Google regarding a potential performance regression with the 5.15 kernel vs the 5.4 kernel on ubuntu 20.04. Their test were performed using the linux-gkeop and linux-gkeop-5.15 kernels. I have verified with the generic Ubuntu 20.04 5.4 linux-generic and the Ubuntu 20.04 5.15 linux-generic-hwe-20.04 kernels. The tests were run using `fio` fio commands: * 4k initwrite: `fio --ioengine=libaio --blocksize=4k --readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sdc` * 4k overwrite: `fio --ioengine=libaio --blocksize=4k --readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sdc` My reproducer was to launch an Ubuntu 20.04 cloud image locally with qemu the results are below: Using 5.4 kernel ``` ubuntu@cloudimg:~$ uname --kernel-release 5.4.0-164-generic ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k --readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sda fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128 ... fio-3.16 Starting 8 processes Jobs: 8 (f=8): [W(8)][99.6%][w=925MiB/s][w=237k IOPS][eta 00m:01s] fiojob1: (groupid=0, jobs=8): err= 0: pid=2443: Thu Nov 2 09:15:22 2023 write: IOPS=317k, BW=1237MiB/s (1297MB/s)(320GiB/264837msec); 0 zone resets slat (nsec): min=628, max=37820k, avg=7207.71, stdev=101058.61 clat (nsec): min=457, max=56099k, avg=340.45, stdev=1707823.38 lat (usec): min=23, max=56100, avg=3229.78, stdev=1705.80 clat percentiles (usec): | 1.00th=[ 775], 5.00th=[ 1352], 10.00th=[ 1647], 20.00th=[ 2024], | 30.00th=[ 2343], 40.00th=[ 2638], 50.00th=[ 2933], 60.00th=[ 3261], | 70.00th=[ 3654], 80.00th=[ 4146], 90.00th=[ 5014], 95.00th=[ 5932], | 99.00th=[ 8979], 99.50th=[10945], 99.90th=[18220], 99.95th=[22676], | 99.99th=[32113] bw ( MiB/s): min= 524, max= 1665, per=100.00%, avg=1237.72, stdev=20.42, samples=4232 iops: min=134308, max=426326, avg=316855.16, stdev=5227.36, samples=4232 lat (nsec) : 500=0.01%, 750=0.01%, 1000=0.01% lat (usec) : 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%, 100=0.01% lat (usec) : 250=0.05%, 500=0.54%, 750=0.37%, 1000=0.93% lat (msec) : 2=17.40%, 4=58.02%, 10=22.01%, 20=0.60%, 50=0.07% lat (msec) : 100=0.01% cpu : usr=3.29%, sys=7.45%, ctx=1262621, majf=0, minf=103 IO depths: 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0% submit: 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1% issued rwts: total=0,83886080,0,8 short=0,0,0,0 dropped=0,0,0,0 latency : target=0, window=0, percentile=100.00%, depth=128 Run status group 0 (all jobs): WRITE: bw=1237MiB/s (1297MB/s), 1237MiB/s-1237MiB/s (1297MB/s-1297MB/s), io=320GiB (344GB), run=264837-264837msec Disk stats (read/write): sda: ios=36/32868891, merge=0/50979424, ticks=5/27498602, in_queue=1183124, util=100.00% ``` After upgrading to linux-generic-hwe-20.04 kernel and rebooting ``` ubuntu@cloudimg:~$ uname --kernel-release 5.15.0-88-generic ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k --readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sda fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128 ... fio-3.16 Starting 8 processes Jobs: 1 (f=1): [_(7),W(1)][100.0%][w=410MiB/s][w=105k IOPS][eta 00m:00s] fiojob1: (groupid=0, jobs=8): err= 0: pid=1438: Thu Nov 2 09:46:49 2023 write: IOPS=155k, BW=605MiB/s (634MB/s)(320GiB/541949msec); 0 zone resets slat (nsec): min=660, max=325426k, avg=10351.04, stdev=232438.50 clat (nsec): min=1100, max=782743k, avg=6595008.67, stdev=6290570.04 lat
[Kernel-packages] [Bug 2042000] Re: 6.2.0-36 kills usb wifi
I have a possibly related issue: after updating from 5.15.0-88 to 5.15.0-90 (on Nov 2, 2023), my external USB HDD stopped working. When booting into 5.15.0-88 it still works. Errors: nov 03 14:23:46 home kernel: usb 2-4: device descriptor read/8, error -71 nov 03 14:23:46 home kernel: usb 2-4: device descriptor read/8, error -71 nov 03 14:23:46 home kernel: usb 2-4: device descriptor read/8, error -71 nov 03 14:23:46 home kernel: usb 2-4: device descriptor read/8, error -71 nov 03 14:23:46 home kernel: usb 2-4: device descriptor read/8, error -71 nov 03 14:23:46 home kernel: usb 2-4: device descriptor read/8, error -71 nov 03 14:23:46 home kernel: usb 2-4: device descriptor read/8, error -71 nov 03 14:23:46 home kernel: usb 2-4: device descriptor read/8, error -71 nov 03 14:23:46 home kernel: usb usb2-port4: unable to enumerate USB device -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042000 Title: 6.2.0-36 kills usb wifi Status in linux package in Ubuntu: Incomplete Bug description: Installed the kernel update from 6.2.0-35 to 6.2.0-36 today (Oct 30, 2023). After reboot, USB WiFi dongle was no longer recognised. Rebooted into previous kernel (6.2.0-35) and have no issue. Not sure what broke, or if it is a regression of some sort. Also, how to upload the bug as stated below, when booting into that kernel does not allow WiFi connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042000/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042000] Re: 6.2.0-36 kills usb wifi
** Attachment added: "journalctl" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042000/+attachment/5715689/+files/journal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042000 Title: 6.2.0-36 kills usb wifi Status in linux package in Ubuntu: Incomplete Bug description: Installed the kernel update from 6.2.0-35 to 6.2.0-36 today (Oct 30, 2023). After reboot, USB WiFi dongle was no longer recognised. Rebooted into previous kernel (6.2.0-35) and have no issue. Not sure what broke, or if it is a regression of some sort. Also, how to upload the bug as stated below, when booting into that kernel does not allow WiFi connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042000/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041995] Re: pwr-mlxbf: support graceful reboot instead of soft reset
This bug is awaiting verification that the linux- bluefield/5.15.0-1031.33 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-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. 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-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2041995 Title: pwr-mlxbf: support graceful reboot instead of soft reset Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] There is a new feature request to replace the soft reset with a graceful reboot. We will use acpi events triggered by the irq in the pwr-mlxbf file to trigger the graceful reboot. [Fix] * Change the handling of GPIO7 (BF2) and GPIO6 (BF3). This gpio will trigger a graceful reboot instead of a forced reboot (soft reset). This is an acpi event. [Test Case] * trigger the gpio toggling from the BMC: ipmitool raw 0x32 0xA1 0x02 This should trigger a graceful reboot of the DPU. [Regression Potential] * make sure it works on BF2 and BF3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2041995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042455] Re: Devlink backport: Fix mlx5 driver hangs due to mlx5_sf_hw_table_init
This bug is awaiting verification that the linux- bluefield/5.15.0-1031.33 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-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. 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-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2042455 Title: Devlink backport: Fix mlx5 driver hangs due to mlx5_sf_hw_table_init Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: Summary: Machine hangs when loading OFED 2310 mlx5 driver at BlueField How to reproduce: # load the OFED driver Reason: BF got stuck and observed call trace "mlx5_sf_hw_table_init+0xf4/0x2d0 [mlx5_core] dmesg from minicom: [ 726.569928] INFO: task systemd-udevd:297 blocked for more than 604 seconds. [ 726.576895] Tainted: G OE 5.15.0-1029-bluefield #31-Ubuntu [ 726.584101] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.591913] task:systemd-udevd state:D stack:0 pid: 297 ppid: 280 flags:0x000d [ 726.600248] Call trace: [ 726.602680] __switch_to+0xf8/0x150 [ 726.606159] __schedule+0x2b8/0x790 [ 726.609634] schedule+0x64/0x140 [ 726.612850] schedule_preempt_disabled+0x18/0x24 [ 726.617453] __mutex_lock.constprop.0+0x1a0/0x680 [ 726.622141] __mutex_lock_slowpath+0x40/0x90 [ 726.626396] mutex_lock+0x64/0x70 [ 726.629695] devlink_resource_register+0x50/0x1a0 [ 726.634386] mlx5_sf_hw_table_init+0xf4/0x2d0 [mlx5_core] [ 726.639882] mlx5_init_one_devl_locked+0x1c8/0x784 [mlx5_core] [ 726.645791] probe_one+0x300/0x5f0 [mlx5_core] [ 726.650307] local_pci_probe+0x48/0xb4 [ 726.654043] pci_device_probe+0x18c/0x200 [ 726.658039] really_probe+0xd0/0x490 [ 726.661600] __driver_probe_device+0x148/0x190 [ 726.666029] driver_probe_device+0x48/0x180 [ 726.670198] __driver_attach+0x104/0x240 [ 726.674106] bus_for_each_dev+0x78/0xdc [ 726.677927] driver_attach+0x2c/0x40 [ 726.681486] bus_add_driver+0x154/0x270 [ 726.685307] driver_register+0x80/0x13c [ 726.689129] __pci_register_driver+0x4c/0x60 [ 726.693386] __init_backport+0xf0/0x1000 [mlx5_core] [ 726.698425] do_one_initcall+0x4c/0x250 [ 726.702248] do_init_module+0x50/0x260 [ 726.705983] load_module+0x9fc/0xbe0 [ 726.709543] __do_sys_finit_module+0xa8/0x114 [ 726.713885] __arm64_sys_finit_module+0x28/0x3c [ 726.718401] invoke_syscall+0x78/0x100 [ 726.722137] el0_svc_common.constprop.0+0x54/0x184 [ 726.726913] do_el0_svc+0x30/0xac [ 726.730215] el0_svc+0x48/0x160 [ 726.733341] el0t_64_sync_handler+0xa4/0x130 [ 726.737597] el0t_64_sync+0x1a4/0x1a8 [ 847.401924] INFO: task systemd-udevd:297 blocked for more than 724 seconds. [ 847.408891] Tainted: G OE 5.15.0-1029-bluefield #31-Ubuntu How to fix: This is related to https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2039869 and we need to backport/cherry-pick more patches from the series Patches are below Backport: f655dacb59ac net: devlink: remove unused locked functions Backport: 012ec02ae441 netdevsim: convert driver to use unlocked devlink API during init/fini Cherry-pick: eb0e9fa2c635 net: devlink: add unlocked variants of devlink_region_create/destroy() functions SKIP: 72a4c8c94efa mlxsw: convert driver to use unlocked devlink API during init/fini Backport: 70a2ff89369d net: devlink: add unlocked variants of devlink_dpipe*() functions Cherry-pick: 755cfa69c4ec net: devlink: add unlocked variants of devlink_sb*() functions Cherry-pick: c223d6a4bf6d net: devlink: add unlocked variants of devlink_resource*() functions Cherry-pick: 852e85a704c2 net: devlink: add unlocked variants of devling_trap*() functions Cherry-pick: e26fde2f5bef net: devlink: avoid false DEADLOCK warning reported by lock Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2042455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042525] Re: mlxbf-pmc: Support 64-bit counter and counting cycles
This bug is awaiting verification that the linux- bluefield/5.15.0-1031.33 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-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. 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-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2042525 Title: mlxbf-pmc: Support 64-bit counter and counting cycles Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Currently, there is no method to keep track of the cycle count when an event is being monitored. And since cycle count increments quickly, the 32-bit counter values could wrap around and hence support for 64-bit counters is also needed for the same. [Fix] Expose 2 additional sysfs entries: count_clock and use_odd_counter. These fields are supported in BlueField-3 PMC hardware and each bit in count_clock corresponds to each counter, while each bit in use_odd_counter corresponds to an even counter.Exposing these fields will allow the user to program any counter of choice to monitor the cycle count for the required duration. Similarly, use_odd_counter can be set to couple 2 adjacent odd and even counters to form a 64-bit counter. [Test Case] 1. Verify that count_clock and use_odd_counter sysfs entries are created for each BlueField-3 HW block. These are not supported by BlueField-1 or BlueField-2 HW. 2. Set any bit in count_clock and check if the corresponding counter values increment after enabling. 3. Set any bit in use_odd_counter and check if the cycle count increments on 2 counters with the odd counter being the lower 32 bits and the even counter being the upper 32 bits. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2042525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042527] Re: mlxbf-pmc: add support for clock_measure counters
This bug is awaiting verification that the linux- bluefield/5.15.0-1031.33 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-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. 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-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2042527 Title: mlxbf-pmc: add support for clock_measure counters Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Currently, the counters under the clock_measure HW block are not supported by the driver and is a new requirement for calculating performance metrics. [Fix] Add support for "clock_measure" block by passing the block info via ACPI. The events monitored by these counters is added to the driver and exposed via a new sysfs sub-directory for this block. [Test Case] Read any of the registers listed under the "clock_measure" sub-directory. These fields are read-only and hence all writes will be blocked by the driver. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2042527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
Reporting Thinkpad T14 of mine was affected, proposed mutterfix, it fixed the reported issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Committed Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042677] [NEW] [UBUNTU 23.04] PKCS#11 Applications fail to find libopencryptoki.so library due to missing /etc/ld.so.conf.d entry.
Public bug reported: --- Problem Description by Grgo M.@IBM --- PKCS#11 Applications fail to find libopencryptoki.so library due to missing /etc/ld.so.conf.d entry. ---uname output--- Linux SYSTEM 6.2.0-34-generic #34-Ubuntu SMP Mon Sep 4 12:26:49 UTC 2023 s390x s390x s390x GNU/Linux Machine Type = Manufacturer: IBM Type: 3931 Model: 704 A01 Sequence Code:00065DC8 ---Steps to Reproduce--- Use any application which uses dlopen interface to load libopencryptoki.so library. e.g. build opencryptoki testcases manually from official opencryptoki sources. # git clone https://github.com/opencryptoki/opencryptoki # cd opencryptoki # ./bootstrap.sh # ./configure --enable-testcases # make # ./testcases/crypto/ec_tests -slot 0 Userspace tool common name: opencryptoki 3.20.0+dfsg-0ubuntu1.1 The userspace tool has the following bit modes: 64bit Userspace rpm: opencryptoki Userspace tool obtained from project website: na == Comment: #2 - 2023-11-03 04:24:48 == Opencryptoki generates an appropriate ld.so.conf.d entry /etc/ld.so.conf.d/opencryptoki-$(target_cpu).conf during 'make install'. Ubuntu should include this into its package to allow applications to find the libopencryptoki.so library when using dlopen(). ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-203847 severity-high targetmilestone-inin2304 ** Tags added: architecture-s39064 bugnameltc-203847 severity-high targetmilestone-inin2304 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042677 Title: [UBUNTU 23.04] PKCS#11 Applications fail to find libopencryptoki.so library due to missing /etc/ld.so.conf.d entry. Status in linux package in Ubuntu: New Bug description: --- Problem Description by Grgo M.@IBM --- PKCS#11 Applications fail to find libopencryptoki.so library due to missing /etc/ld.so.conf.d entry. ---uname output--- Linux SYSTEM 6.2.0-34-generic #34-Ubuntu SMP Mon Sep 4 12:26:49 UTC 2023 s390x s390x s390x GNU/Linux Machine Type = Manufacturer: IBM Type: 3931 Model: 704 A01 Sequence Code:00065DC8 ---Steps to Reproduce--- Use any application which uses dlopen interface to load libopencryptoki.so library. e.g. build opencryptoki testcases manually from official opencryptoki sources. # git clone https://github.com/opencryptoki/opencryptoki # cd opencryptoki # ./bootstrap.sh # ./configure --enable-testcases # make # ./testcases/crypto/ec_tests -slot 0 Userspace tool common name: opencryptoki 3.20.0+dfsg-0ubuntu1.1 The userspace tool has the following bit modes: 64bit Userspace rpm: opencryptoki Userspace tool obtained from project website: na == Comment: #2 - 2023-11-03 04:24:48 == Opencryptoki generates an appropriate ld.so.conf.d entry /etc/ld.so.conf.d/opencryptoki-$(target_cpu).conf during 'make install'. Ubuntu should include this into its package to allow applications to find the libopencryptoki.so library when using dlopen(). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042677] [NEW] [UBUNTU 23.04] PKCS#11 Applications fail to find libopencryptoki.so library due to missing /etc/ld.so.conf.d entry.
You have been subscribed to a public bug: --- Problem Description by Grgo M.@IBM --- PKCS#11 Applications fail to find libopencryptoki.so library due to missing /etc/ld.so.conf.d entry. ---uname output--- Linux SYSTEM 6.2.0-34-generic #34-Ubuntu SMP Mon Sep 4 12:26:49 UTC 2023 s390x s390x s390x GNU/Linux Machine Type = Manufacturer: IBM Type: 3931 Model: 704 A01 Sequence Code:00065DC8 ---Steps to Reproduce--- Use any application which uses dlopen interface to load libopencryptoki.so library. e.g. build opencryptoki testcases manually from official opencryptoki sources. # git clone https://github.com/opencryptoki/opencryptoki # cd opencryptoki # ./bootstrap.sh # ./configure --enable-testcases # make # ./testcases/crypto/ec_tests -slot 0 Userspace tool common name: opencryptoki 3.20.0+dfsg-0ubuntu1.1 The userspace tool has the following bit modes: 64bit Userspace rpm: opencryptoki Userspace tool obtained from project website: na == Comment: #2 - 2023-11-03 04:24:48 == Opencryptoki generates an appropriate ld.so.conf.d entry /etc/ld.so.conf.d/opencryptoki-$(target_cpu).conf during 'make install'. Ubuntu should include this into its package to allow applications to find the libopencryptoki.so library when using dlopen(). ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-203847 severity-high targetmilestone-inin2304 -- [UBUNTU 23.04] PKCS#11 Applications fail to find libopencryptoki.so library due to missing /etc/ld.so.conf.d entry. https://bugs.launchpad.net/bugs/2042677 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception
** Changed in: linux (Ubuntu Noble) Status: New => Triaged ** Changed in: linux (Ubuntu Mantic) Status: New => Triaged ** Changed in: linux (Ubuntu Lunar) Status: New => Triaged ** Changed in: linux (Ubuntu Jammy) Status: New => Triaged ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042054 Title: 22.04.3, zen 4 7840, screen turn white exception Status in Linux: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Triaged Status in linux-oem-6.5 source package in Jammy: Triaged Status in linux source package in Lunar: Triaged Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Triaged Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Invalid Bug description: My screen suddenly turned completely white, then only the bottom half was white, but I can still operate the application window. When moving the application window, the bottom half of the screen turns the Ubuntu theme color. Only lock and unlock the screen or turn off the screen can fix the situation. There are some photo about the exception attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3 Uname: Linux 6.5.0-1006-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 12:26:24 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3818] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 83AM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: MKCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: XiaoXinPro 14 APH8 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8: dmi.product.family: XiaoXinPro 14 APH8 dmi.product.name: 83AM dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8 dmi.product.version: XiaoXinPro 14 APH8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 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/linux/+bug/2042054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception
From the upstream bug this is caused by PSR, so it's not a mesa issue. ** No longer affects: mesa (Ubuntu) ** No longer affects: mesa (Ubuntu Jammy) ** No longer affects: mesa (Ubuntu Lunar) ** No longer affects: mesa (Ubuntu Mantic) ** No longer affects: mesa (Ubuntu Noble) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042054 Title: 22.04.3, zen 4 7840, screen turn white exception Status in Linux: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Lunar: New Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: My screen suddenly turned completely white, then only the bottom half was white, but I can still operate the application window. When moving the application window, the bottom half of the screen turns the Ubuntu theme color. Only lock and unlock the screen or turn off the screen can fix the situation. There are some photo about the exception attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3 Uname: Linux 6.5.0-1006-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 12:26:24 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3818] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 83AM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: MKCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: XiaoXinPro 14 APH8 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8: dmi.product.family: XiaoXinPro 14 APH8 dmi.product.name: 83AM dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8 dmi.product.version: XiaoXinPro 14 APH8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 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/linux/+bug/2042054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042546] Re: Include cifs.ko in linux-modules package
This bug is awaiting verification that the linux-kvm/6.2.0-1017.17 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-lunar-linux-kvm' to 'verification-done-lunar- linux-kvm'. If the problem still exists, change the tag 'verification- needed-lunar-linux-kvm' to 'verification-failed-lunar-linux-kvm'. 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-lunar-linux-kvm-v2 verification-needed-lunar-linux-kvm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042546 Title: Include cifs.ko in linux-modules package Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification: [Impact] Commit: "smb: move client and server files to common directory fs/smb" introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For lunar:main this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. [How to reproduce it]: 1. Install the latest azure kernel 6.2.0-1016.16 2. Load cifs module $ modprobe cifs modprobe: FATAL: Module cifs not found in directory /lib/modules/6.2.0-1016-azure If modules-extra is installed, this works. [Fix] Replace fs/cifs/* with fs/smb/client/* in debian./control.d/.inclusiojn-list This is going to be done in s2023.10.02 cycle for derivatives. [Test Plan] 1. Apply the fix to one of the derivative (azure), build a new kernel and install it 2. Load cifs module $ modprobe cifs It should work without installing modules-extra. [Regression potential] Very low, it's a straightforward fix. [Other Info] Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked. There is also the possibility to do it via cranky fix, but owners may omit it during security updates and it's hard to enforce it. Plus, it is a one-time change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020091] Ubuntu 23.10 Installation error
Sir/Madam , When I install Ubuntu 23.10 on my PC then It shows error . I have attached error screenshot with my mail .Please suggest me to fix this error as soon as possible. Thanks. ** Attachment added: "ubuntu_error_2.png" https://bugs.launchpad.net/bugs/2020091/+attachment/5715644/+files/ubuntu_error_2.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2020091 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: I am unable update to while I type in terminal sudo apt-get update && sudo apt-get upgrade Please help me to solve my problem. Thank you. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ganesh 882 F wireplumber /dev/snd/seq:ganesh 879 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu May 18 18:37:00 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-02-08 (99 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=3757a187-5a56-49cb-b5b3-1ee6159919aa ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-23 (25 days ago) dmi.bios.date: 08/31/2022 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61 dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/31/2022:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040039] Re: Ubuntu Server 22.04.3 randomly freezes
Changing VM settings in /etc/sysctl.conf seems to have resolved freezes on my Ubuntu 22.04.3 kernel 5.15.0-88 server I added the following at the end of /etc/sysctl.conf : vm.min_free_kbytes = 2097152 vm.swappiness = 5 vm.dirty_background_ratio = 5 vm.dirty_ratio = 10 vm.dirty_writeback_centisecs = 500 vm.dirty_expire_centisecs = 3000 Then I ran sysctl -p /etc/sysctl.conf ... to perm save settings vm.min_free_kbytes and vm.swappiness seems to be the main ones doing the trick. These settings depend on your server config and main use so be sure to adapt accordingly. Documention can be found here : https://sysctl-explorer.net/vm I used tool to test new settings and to monitor cpu and mem alloc. i.e. stress --vm 8 --vm-bytes 8G --timeout 300 to stress test mem up to 64GB using 8 vm workers spinning during 5 minutes. For info, I have a 8GB swap Before changing these settings (=> default values), my server freezed when stress testing it to the RAM limit not using the swap. After, it gently switched to swap when approaching the RAM limit without freezing. Hope this helps someone else... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2040039 Title: Ubuntu Server 22.04.3 randomly freezes Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have a physical machine on which I have installed Ubuntu Server 22.04.3 . It randomly freezes. I read few forums and gathered previous boot report as well. Other information as requested: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-87-generic 5.15.0-87.97 ProcVersionSignature: Ubuntu 5.15.0-87.97-generic 5.15.122 Uname: Linux 5.15.0-87-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-87-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sat Oct 21 02:41:33 2023 InstallationDate: Installed on 2023-09-19 (31 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 2M/x2 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M MachineType: Gigabyte Technology Co., Ltd. H510M H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-87-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro RelatedPackageVersions: linux-restricted-modules-5.15.0-87-generic N/A linux-backports-modules-5.15.0-87-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2023 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F17 dmi.board.asset.tag: Default string dmi.board.name: H510M H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF17:bd03/10/2023:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnH510MH:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH510MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H510 MB dmi.product.name: H510M H dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to:
[Kernel-packages] [Bug 2042357] Re: Merge crash 8.0.3 into Noble
** Description changed: - 2023/10/31: please do not merge 8.0.3-1 yet (issue with .orig tarball) - - Work in progress; testing changes on PPA. + Work in progress; rebasing on 8.0.3+ds1-3, and testing. Debian bugs: https://bugs.debian.org/1054805 Please update crash to 8.0.3 https://bugs.debian.org/1055117 FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/2042357 Title: Merge crash 8.0.3 into Noble Status in crash package in Ubuntu: In Progress Status in crash package in Debian: New Bug description: Work in progress; rebasing on 8.0.3+ds1-3, and testing. Debian bugs: https://bugs.debian.org/1054805 Please update crash to 8.0.3 https://bugs.debian.org/1055117 FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2042357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042357] Re: Merge crash 8.0.3 into Noble
Debian crash 8.0.3+ds1-3 [1] addressed the gdb tarball issue. I'll update the merge, and proceed with build and tests. [1] https://tracker.debian.org/news/1475695/accepted- crash-803ds1-3-source-into-unstable/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/2042357 Title: Merge crash 8.0.3 into Noble Status in crash package in Ubuntu: In Progress Status in crash package in Debian: New Bug description: Work in progress; rebasing on 8.0.3+ds1-3, and testing. Debian bugs: https://bugs.debian.org/1054805 Please update crash to 8.0.3 https://bugs.debian.org/1055117 FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2042357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
We can confirm that this bug is no longer an issue with 5.4.0-166 being deployed on all our servers. We consider this bug solved. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Fix Released Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2030978] Re: kernel 6.5 changes cause UBSAN errors (patch included)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: broadcom-sta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to broadcom-sta in Ubuntu.
https://bugs.launchpad.net/bugs/2030978
Title:
kernel 6.5 changes cause UBSAN errors (patch included)
Status in broadcom-sta package in Ubuntu:
Confirmed
Bug description:
"On Linux 6.5, due to commit 2d47c6956ab3 ("ubsan: Tighten UBSAN_BOUNDS
on GCC"), flexible trailing arrays declared like `whatever_t foo[1];`
will generate warnings when CONFIG_UBSAN & co. is enabled."
Due to changes in kernel 6.5, we get this error in dmesg:
[ 28.818756]
[ 28.822952] UBSAN: array-index-out-of-bounds in
/var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_linux.c:1938:4
[ 28.82] index 2 is out of range for type 'ether_addr [1]'
[ 28.832900] CPU: 1 PID: 1232 Comm: avahi-daemon Tainted: P OE
6.5.0-rc4 #1
[ 28.836452] Hardware name: Apple Inc. MacBookPro11,3/Mac-2BD1B31983FE1663,
BIOS 432.60.3.0.0 10/27/2021
[ 28.839806] Call Trace:
[ 28.843091]
[ 28.846387] dump_stack_lvl+0x48/0x60
[ 28.849692] dump_stack+0x10/0x20
[ 28.852965] __ubsan_handle_out_of_bounds+0xc6/0x100
[ 28.856251] _wl_set_multicast_list+0x1fd/0x220 [wl]
[ 28.859191] wl_set_multicast_list+0x3a/0x80 [wl]
[ 28.861879] __dev_set_rx_mode+0x6a/0xc0
[ 28.864237] __dev_mc_add+0x82/0x90
[ 28.866587] dev_mc_add+0x10/0x20
[ 28.868920] igmp_group_added+0x198/0x1d0
[ 28.871102] ip_mc_inc_group+0x185/0x2b0
[ 28.873231] __ip_mc_join_group+0x108/0x170
[ 28.875170] ip_mc_join_group+0x10/0x20
[ 28.877111] do_ip_setsockopt+0x104d/0x1160
[ 28.878894] ? __sys_setsockopt+0xeb/0x1c0
[ 28.880657] ip_setsockopt+0x30/0xb0
[ 28.882326] udp_setsockopt+0x22/0x40
[ 28.883949] sock_common_setsockopt+0x14/0x20
[ 28.885554] __sys_setsockopt+0xde/0x1c0
[ 28.887063] __x64_sys_setsockopt+0x1f/0x30
[ 28.888564] do_syscall_64+0x55/0x80
[ 28.889952] ? syscall_exit_to_user_mode+0x26/0x40
[ 28.891226] ? __x64_sys_recvmsg+0x1d/0x20
[ 28.892450] ? do_syscall_64+0x61/0x80
[ 28.893651] ? do_syscall_64+0x61/0x80
[ 28.894796] entry_SYSCALL_64_after_hwframe+0x46/0xb0
[ 28.895942] RIP: 0033:0x7f0a97a7ddae
[ 28.897100] Code: 0f 1f 40 00 48 8b 15 69 60 0d 00 f7 d8 64 89 02 48 c7 c0
ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 49 89 ca b8 36 00 00 00 0f 05 <48> 3d 00
f0 ff ff 77 0a c3 66 0f 1f 84 00 00 00 00 00 48 8b 15 31
[ 28.898270] RSP: 002b:7fffb7b1b3f8 EFLAGS: 0246 ORIG_RAX:
0036
[ 28.899449] RAX: ffda RBX: 000c RCX:
7f0a97a7ddae
[ 28.900623] RDX: 0023 RSI: RDI:
000c
[ 28.901784] RBP: 0001 R08: 000c R09:
0004
[ 28.902895] R10: 7fffb7b1b404 R11: 0246 R12:
7fffb7b1b404
[ 28.904011] R13: 0014 R14: 55cc506ee078 R15:
55cc506eaf60
[ 28.905149]
[ 28.906228]
A patch is however available for this issue:
https://gist.github.com/joanbm/9cd5fda1dcfab9a67b42cc6195b7b269
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: bcmwl-kernel-source (not installed)
Uname: Linux 6.5.0-rc4 x86_64
NonfreeKernelModules: wl zfs
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Aug 10 10:40:27 2023
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
SourcePackage: broadcom-sta
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2030978/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042661] [NEW] package linux-modules-nvidia-535-6.2.0-36-generic 6.2.0-36.37~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-535-6.2.0-36-generic package pos
Public bug reported: System update ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-535-6.2.0-36-generic 6.2.0-36.37~22.04.1+1 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Nov 3 08:50:39 2023 ErrorMessage: installed linux-modules-nvidia-535-6.2.0-36-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-06 (27 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: linux-restricted-modules-hwe-6.2 Title: package linux-modules-nvidia-535-6.2.0-36-generic 6.2.0-36.37~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-535-6.2.0-36-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2042661 Title: package linux-modules-nvidia-535-6.2.0-36-generic 6.2.0-36.37~22.04.1+1 failed to install/upgrade: installed linux- modules-nvidia-535-6.2.0-36-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules-hwe-6.2 package in Ubuntu: New Bug description: System update ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-535-6.2.0-36-generic 6.2.0-36.37~22.04.1+1 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Nov 3 08:50:39 2023 ErrorMessage: installed linux-modules-nvidia-535-6.2.0-36-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-06 (27 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: linux-restricted-modules-hwe-6.2 Title: package linux-modules-nvidia-535-6.2.0-36-generic 6.2.0-36.37~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-535-6.2.0-36-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-6.2/+bug/2042661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017877] Re: Intel Wireless 7260 - bluetooth drops from USB bus almost immediately after connecting a device on the lastest firmware
I finally had some time to test this - no, this kernel argument doesn't seem to change anything. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2017877 Title: Intel Wireless 7260 - bluetooth drops from USB bus almost immediately after connecting a device on the lastest firmware Status in linux-firmware package in Ubuntu: Incomplete Bug description: The bluetooth in my Intel Wireless 7260 on my Thinkpad W541 resets almost immediately after a device connects. This is seen in dmesg as the device disconnecting and reconnecting to the USB bus with no other error messages, like this: [603851.305788] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603851.305827] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [603851.443776] Bluetooth: hci0: unexpected event for opcode 0xfc2f [603851.460922] Bluetooth: hci0: Intel BT fw patch 0x2a completed & activated [603871.948430] usb 3-11: USB disconnect, device number 36 [603872.273696] usb 3-11: new full-speed USB device number 37 using xhci_hcd [603872.422912] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [603872.422916] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [603872.437854] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603872.437873] Bluetooth: hci0: Intel device is already patched. patch num: 2a [603894.932755] input: JBL TUNE700BT (AVRCP) as /devices/virtual/input/input113 [603898.742664] usb 3-11: USB disconnect, device number 37 [603899.057916] usb 3-11: new full-speed USB device number 38 using xhci_hcd [603899.211235] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [603899.211241] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [603899.226972] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603899.226988] Bluetooth: hci0: Intel device is already patched. patch num: 2a [603909.785396] input: JBL TUNE700BT (AVRCP) as /devices/virtual/input/input114 [603914.565733] usb 3-11: USB disconnect, device number 38 [603916.905954] usb 3-11: new full-speed USB device number 39 using xhci_hcd [603917.055128] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [603917.055147] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [603917.071869] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603917.071877] Bluetooth: hci0: Intel device is already patched. patch num: 2a This has been a problem ever since I got this laptop, but recently I managed to fix it by downgrading the ibt firmware. I downgraded the /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq file to this version https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/intel/ibt- hw-37.7.10-fw-1.80.1.2d.d.bseq?id=fb328183532ffc7a1a54e84fb53467e275a95b79 and after that all problems stopped. System info: $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy linux-firmware linux-firmware: Installed: 20220329.git681281e4-0ubuntu3.12 Candidate: 20220329.git681281e4-0ubuntu3.12 Version table: *** 20220329.git681281e4-0ubuntu3.12 500 500 http://pl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 100 /var/lib/dpkg/status 20220329.git681281e4-0ubuntu1 500 500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages $ lspci - (see attachment) $ lsusb -v (see attachment) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: krzys_h1511 F pulseaudio /dev/snd/controlC2: krzys_h1511 F pulseaudio /dev/snd/controlC0: krzys_h1511 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-28 (3346 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20EGS2G300 Package: linux-firmware 20220329.git681281e4-0ubuntu3.12 [modified: lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-71-generic
[Kernel-packages] [Bug 2038539] Re: bluetooth connections are unstable with linux-image-6.5.0-6-generic and above (MANTIC)
comment #41 was with the 6.5.0-12 kernel version .. switching to the
older 6.5.0-5 kernel there are no issues (same software/hardware/just a
reboot to a different kernel)
.. so a definite kernel internal interaction appears indicated between
regular network and bluetooth network .. regular networking priority
higher than bluetooth? or a device driver change? I don't know enough
to check this out ..
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038539
Title:
bluetooth connections are unstable with linux-image-6.5.0-6-generic
and above (MANTIC)
Status in linux package in Ubuntu:
New
Bug description:
Seems some random network activity regularly breaks bluetooth connections..
headphones connect and reconnect or suffer breaks in sound etc.
Started with this kernel version linux-image-6.5.0-7 .. previous kernel
linux-image-6.5.0-5 works perfectly
Booting into the older kernel restores bluetooth stability.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: derk 1690 F wireplumber
/dev/snd/controlC0: derk 1690 F wireplumber
/dev/snd/seq:derk 1687 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Thu Oct 5 08:33:01 2023
InstallationDate: Installed on 2023-10-04 (1 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: L9CN21WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Slim 5 16ABR8
dmi.ec.firmware.release: 1.21
dmi.modalias:
dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8:
dmi.product.family: IdeaPad Slim 5 16ABR8
dmi.product.name: 82XG
dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8
dmi.product.version: IdeaPad Slim 5 16ABR8
dmi.sys.vendor: LENOVO
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: derk 1691 F wireplumber
/dev/snd/controlC0: derk 1691 F wireplumber
/dev/snd/seq:derk 1688 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-10-04 (12 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: L9CN21WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO
[Kernel-packages] [Bug 2038539] Re: bluetooth connections are unstable with linux-image-6.5.0-6-generic and above (MANTIC)
note: disconnecting from the network stops dropouts considerably to a
much more tolerable level.
I tried using flight mode but that kills bluetooth as well and turning
it on again resulted in a struggle to reconnect the headphones. ..
as a side note .. latest audio updates had just been installed .. so no
change in the underlying problem ..
definite interaction with regular network causes the problem .. a
traffic direction/priority issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038539
Title:
bluetooth connections are unstable with linux-image-6.5.0-6-generic
and above (MANTIC)
Status in linux package in Ubuntu:
New
Bug description:
Seems some random network activity regularly breaks bluetooth connections..
headphones connect and reconnect or suffer breaks in sound etc.
Started with this kernel version linux-image-6.5.0-7 .. previous kernel
linux-image-6.5.0-5 works perfectly
Booting into the older kernel restores bluetooth stability.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: derk 1690 F wireplumber
/dev/snd/controlC0: derk 1690 F wireplumber
/dev/snd/seq:derk 1687 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Thu Oct 5 08:33:01 2023
InstallationDate: Installed on 2023-10-04 (1 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: L9CN21WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Slim 5 16ABR8
dmi.ec.firmware.release: 1.21
dmi.modalias:
dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8:
dmi.product.family: IdeaPad Slim 5 16ABR8
dmi.product.name: 82XG
dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8
dmi.product.version: IdeaPad Slim 5 16ABR8
dmi.sys.vendor: LENOVO
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: derk 1691 F wireplumber
/dev/snd/controlC0: derk 1691 F wireplumber
/dev/snd/seq:derk 1688 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-10-04 (12 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: L9CN21WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version:
[Kernel-packages] [Bug 2042534] Re: System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm - 2R8DY
SRU: * https://lists.ubuntu.com/archives/kernel-team/2023-November/146722.html (jammy) * https://lists.ubuntu.com/archives/kernel-team/2023-November/146723.html (lunar) * https://lists.ubuntu.com/archives/kernel-team/2023-November/146724.html (mantic) ** Description changed: + [SRU Justification] + + [Impact] + + System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm - + 2R8DY. + + [Fix] + + Upstream firwmware WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30 + from https://github.com/kvalo/ath11k-firmware/commit/c2d15c3e0843fe25a1697db4f6fe0c8ab0b639b9 + should be used. + + [Test Case] + + Run suspend/resume stress test with fwts: + ``` + $ checkbox-cli run com.canonical.certification::stress-suspend-30-cycles-with-reboots-automated + ``` + + [Where problems could occur] + + The proposed firmware is opaque to us, expect every possible regression. + + [Other Info] + + At the time writing this pull request, this firmware blob is public released + in kvalo/ath11k-firmware only. While WCN6855 is enabled long time ago, nominate + for Jammy/Lunar/Mantic. Noble branch is not yet created so omitted for now. + + == original bug report == + [3.505614] kernel: ath11k_pci :06:00.0: wcn6855 hw2.1 [4.423498] kernel: ath11k_pci :06:00.0: chip_id 0x12 chip_family 0xb board_id 0xff soc_id 0x400c1211 [4.423502] kernel: ath11k_pci :06:00.0: fw_version 0x110b196e fw_build_timestamp 2022-12-22 12:54 fw_build_id WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23 Upstream firwmware WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30 from https://github.com/kvalo/ath11k-firmware/commit/c2d15c3e0843fe25a1697db4f6fe0c8ab0b639b9 should be used. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2042534 Title: System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm - 2R8DY Status in HWE Next: New Status in linux-firmware package in Ubuntu: Incomplete Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-firmware source package in Mantic: In Progress Status in linux-firmware source package in Noble: Incomplete Bug description: [SRU Justification] [Impact] System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm - 2R8DY. [Fix] Upstream firwmware WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30 from https://github.com/kvalo/ath11k-firmware/commit/c2d15c3e0843fe25a1697db4f6fe0c8ab0b639b9 should be used. [Test Case] Run suspend/resume stress test with fwts: ``` $ checkbox-cli run com.canonical.certification::stress-suspend-30-cycles-with-reboots-automated ``` [Where problems could occur] The proposed firmware is opaque to us, expect every possible regression. [Other Info] At the time writing this pull request, this firmware blob is public released in kvalo/ath11k-firmware only. While WCN6855 is enabled long time ago, nominate for Jammy/Lunar/Mantic. Noble branch is not yet created so omitted for now. == original bug report == [3.505614] kernel: ath11k_pci :06:00.0: wcn6855 hw2.1 [4.423498] kernel: ath11k_pci :06:00.0: chip_id 0x12 chip_family 0xb board_id 0xff soc_id 0x400c1211 [4.423502] kernel: ath11k_pci :06:00.0: fw_version 0x110b196e fw_build_timestamp 2022-12-22 12:54 fw_build_id WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23 Upstream firwmware WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30 from https://github.com/kvalo/ath11k-firmware/commit/c2d15c3e0843fe25a1697db4f6fe0c8ab0b639b9 should be used. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085]
Hello, https://glowoxygluta.com/glow-oxygluta-glutathione-capsules/ https://glowoxygluta.com/glow-oxygluta-glutathione-cream/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to:
[Kernel-packages] [Bug 2042654] [NEW] package linux-image-5.15.0-84-generic (not installed) failed to install/upgrade: unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-new': Operation not permitte
Public bug reported: Not able to install updates of ubuntu system is getting slow ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-84-generic (not installed) ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-83-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 3 15:14:34 2023 DpkgHistoryLog: Start-Date: 2023-11-03 15:13:01 Commandline: apt-get install -f Requested-By: admin1 (1000) Install: linux-hwe-5.15-headers-5.15.0-88:amd64 (5.15.0-88.98~20.04.1, automatic), linux-modules-extra-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, automatic), linux-modules-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, automatic), linux-headers-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, automatic), linux-image-5.15.0-84-generic:amd64 (5.15.0-84.93~20.04.1, automatic), linux-image-5.15.0-86-generic:amd64 (5.15.0-86.96~20.04.1, automatic), linux-image-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.15.0.86.96~20.04.44, 5.15.0.88.98~20.04.46), linux-image-generic-hwe-20.04:amd64 (5.15.0.86.96~20.04.44, 5.15.0.88.98~20.04.46), linux-generic-hwe-20.04:amd64 (5.15.0.86.96~20.04.44, 5.15.0.88.98~20.04.46) DuplicateSignature: package:linux-image-5.15.0-84-generic:(not installed) Unpacking linux-image-5.15.0-84-generic (5.15.0-84.93~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-2gOGNH/8-linux-image-5.15.0-84-generic_5.15.0-84.93~20.04.1_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-new': Operation not permitted ErrorMessage: unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-new': Operation not permitted InstallationDate: Installed on 2023-09-12 (51 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.4 SourcePackage: linux-signed-hwe-5.15 Title: package linux-image-5.15.0-84-generic (not installed) failed to install/upgrade: unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2042654 Title: package linux-image-5.15.0-84-generic (not installed) failed to install/upgrade: unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg- new': Operation not permitted Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Not able to install updates of ubuntu system is getting slow ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-84-generic (not installed) ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-83-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 3 15:14:34 2023 DpkgHistoryLog: Start-Date: 2023-11-03 15:13:01 Commandline: apt-get install -f Requested-By: admin1 (1000) Install: linux-hwe-5.15-headers-5.15.0-88:amd64 (5.15.0-88.98~20.04.1, automatic), linux-modules-extra-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, automatic), linux-modules-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, automatic), linux-headers-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, automatic), linux-image-5.15.0-84-generic:amd64 (5.15.0-84.93~20.04.1, automatic), linux-image-5.15.0-86-generic:amd64 (5.15.0-86.96~20.04.1, automatic), linux-image-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.15.0.86.96~20.04.44, 5.15.0.88.98~20.04.46), linux-image-generic-hwe-20.04:amd64 (5.15.0.86.96~20.04.44, 5.15.0.88.98~20.04.46), linux-generic-hwe-20.04:amd64 (5.15.0.86.96~20.04.44, 5.15.0.88.98~20.04.46) DuplicateSignature: package:linux-image-5.15.0-84-generic:(not installed) Unpacking linux-image-5.15.0-84-generic (5.15.0-84.93~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-2gOGNH/8-linux-image-5.15.0-84-generic_5.15.0-84.93~20.04.1_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-new': Operation not permitted ErrorMessage: unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-new': Operation not permitted InstallationDate: Installed on 2023-09-12 (51 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A
[Kernel-packages] [Bug 2042573] Re: arm64 atomic issues cause disk corruption
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042573 Title: arm64 atomic issues cause disk corruption Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] The mantic kernel introduced a regression in atomic operations on arm64 which causes all kinds of problems including file system corruptions, since commit "locking/atomic: scripts: restructure fallback ifdeffery". An example report of people encountering this in UTM with a arm64 generic kernel: https://github.com/utmapp/UTM/issues/4840 [Fix] Cherry-pick commit "locking/atomic: scripts: fix fallback ifdeffery" from linux-stable v6.5.6 [Test Plan] Boot test on an arm64 vm. [Where problems could occur] Since this is touching atomic operations, this has a wide impact on the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10
The new 6.5 kernel contains other changes beside the fix for NVME, so
the new issues may or may not be related. Please file a new bug and try
to provide some log of the failed boot (you can do a boot into 6.5 and
then reboot back into 6.2. Then "sudo journalctl -b-1" might contain
useful info to work with. Then mention the new bug number here. Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2040157
Title:
Unable to use nvme drive to install Ubuntu 23.10
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Bug description:
The 6.5 kernel in the 23.10 installer ISO is unable to work with an
NVME drive in the laptop, and it is not possible to install Ubuntu. It
might be related to Kernel bug
https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.
dmesg:
[ 42.116742] nvme nvme0: controller is down; will reset: CSTS=0x,
PCI_STATUS=0x
[ 42.116764] nvme nvme0: Does your device have a faulty power saving mode
enabled?
[ 42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0
pcie_aspm=off" and report a bug
[ 42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error
(sct 0x3 / sc 0x71)
[ 42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags
0x80700 phys_seg 1 prio class 2
[ 42.164760] nvme :04:00.0: Unable to change power state from D3cold to
D0, device inaccessible
[ 42.165160] nvme nvme0: Disabling device after reset failure: -19
[ 42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page
read
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 10:53:50 2023
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.product.sku: 07BF
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10
@copong This bug does not represent the entire latest 6.5 update,
therefore if you have a different issue, please create another bug
report and we can take action from there.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2040157
Title:
Unable to use nvme drive to install Ubuntu 23.10
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Bug description:
The 6.5 kernel in the 23.10 installer ISO is unable to work with an
NVME drive in the laptop, and it is not possible to install Ubuntu. It
might be related to Kernel bug
https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.
dmesg:
[ 42.116742] nvme nvme0: controller is down; will reset: CSTS=0x,
PCI_STATUS=0x
[ 42.116764] nvme nvme0: Does your device have a faulty power saving mode
enabled?
[ 42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0
pcie_aspm=off" and report a bug
[ 42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error
(sct 0x3 / sc 0x71)
[ 42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags
0x80700 phys_seg 1 prio class 2
[ 42.164760] nvme :04:00.0: Unable to change power state from D3cold to
D0, device inaccessible
[ 42.165160] nvme nvme0: Disabling device after reset failure: -19
[ 42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page
read
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 10:53:50 2023
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.product.sku: 07BF
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042573] Re: arm64 atomic issues cause disk corruption
** Changed in: linux (Ubuntu Mantic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042573 Title: arm64 atomic issues cause disk corruption Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: In Progress Bug description: SRU Justification: [Impact] The mantic kernel introduced a regression in atomic operations on arm64 which causes all kinds of problems including file system corruptions, since commit "locking/atomic: scripts: restructure fallback ifdeffery". An example report of people encountering this in UTM with a arm64 generic kernel: https://github.com/utmapp/UTM/issues/4840 [Fix] Cherry-pick commit "locking/atomic: scripts: fix fallback ifdeffery" from linux-stable v6.5.6 [Test Plan] Boot test on an arm64 vm. [Where problems could occur] Since this is touching atomic operations, this has a wide impact on the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042573] Re: arm64 atomic issues cause disk corruption
** Description changed: - The 6.5 kernel introduced a regression in atomic operations on arm64 - which causes all kinds of problems including file system corruptions. + SRU Justification: + + [Impact] + The mantic kernel introduced a regression in atomic operations on arm64 + which causes all kinds of problems including file system corruptions, + since commit "locking/atomic: scripts: restructure fallback + ifdeffery". An example report of people encountering this in UTM with a arm64 generic kernel: https://github.com/utmapp/UTM/issues/4840 - This is fixed by https://lore.kernel.org/linux-arm- - kernel/20230920142201.GG348037@frogsfrogsfrogs/T/ + [Fix] + Cherry-pick commit "locking/atomic: scripts: fix fallback ifdeffery" + from linux-stable v6.5.6 + + [Test Plan] + + Boot test on an arm64 vm. + + [Where problems could occur] + Since this is touching atomic operations, this has a wide impact on the + kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042573 Title: arm64 atomic issues cause disk corruption Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: New Bug description: SRU Justification: [Impact] The mantic kernel introduced a regression in atomic operations on arm64 which causes all kinds of problems including file system corruptions, since commit "locking/atomic: scripts: restructure fallback ifdeffery". An example report of people encountering this in UTM with a arm64 generic kernel: https://github.com/utmapp/UTM/issues/4840 [Fix] Cherry-pick commit "locking/atomic: scripts: fix fallback ifdeffery" from linux-stable v6.5.6 [Test Plan] Boot test on an arm64 vm. [Where problems could occur] Since this is touching atomic operations, this has a wide impact on the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042534] Re: System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm - 2R8DY
** Tags added: kern-8461 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2042534 Title: System hang at suspend stress test with WCN6856 WiFi 6E - Qualcomm - 2R8DY Status in HWE Next: New Status in linux-firmware package in Ubuntu: Incomplete Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-firmware source package in Mantic: In Progress Status in linux-firmware source package in Noble: Incomplete Bug description: [3.505614] kernel: ath11k_pci :06:00.0: wcn6855 hw2.1 [4.423498] kernel: ath11k_pci :06:00.0: chip_id 0x12 chip_family 0xb board_id 0xff soc_id 0x400c1211 [4.423502] kernel: ath11k_pci :06:00.0: fw_version 0x110b196e fw_build_timestamp 2022-12-22 12:54 fw_build_id WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23 Upstream firwmware WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30 from https://github.com/kvalo/ath11k-firmware/commit/c2d15c3e0843fe25a1697db4f6fe0c8ab0b639b9 should be used. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042573] Re: arm64 atomic issues cause disk corruption
** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042573 Title: arm64 atomic issues cause disk corruption Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: New Bug description: The 6.5 kernel introduced a regression in atomic operations on arm64 which causes all kinds of problems including file system corruptions. An example report of people encountering this in UTM with a arm64 generic kernel: https://github.com/utmapp/UTM/issues/4840 This is fixed by https://lore.kernel.org/linux-arm- kernel/20230920142201.GG348037@frogsfrogsfrogs/T/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038539] Re: bluetooth connections are unstable with linux-image-6.5.0-6-generic and above (MANTIC)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038539
Title:
bluetooth connections are unstable with linux-image-6.5.0-6-generic
and above (MANTIC)
Status in linux package in Ubuntu:
New
Bug description:
Seems some random network activity regularly breaks bluetooth connections..
headphones connect and reconnect or suffer breaks in sound etc.
Started with this kernel version linux-image-6.5.0-7 .. previous kernel
linux-image-6.5.0-5 works perfectly
Booting into the older kernel restores bluetooth stability.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: derk 1690 F wireplumber
/dev/snd/controlC0: derk 1690 F wireplumber
/dev/snd/seq:derk 1687 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Thu Oct 5 08:33:01 2023
InstallationDate: Installed on 2023-10-04 (1 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: L9CN21WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Slim 5 16ABR8
dmi.ec.firmware.release: 1.21
dmi.modalias:
dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8:
dmi.product.family: IdeaPad Slim 5 16ABR8
dmi.product.name: 82XG
dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8
dmi.product.version: IdeaPad Slim 5 16ABR8
dmi.sys.vendor: LENOVO
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: derk 1691 F wireplumber
/dev/snd/controlC0: derk 1691 F wireplumber
/dev/snd/seq:derk 1688 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-10-04 (12 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: L9CN21WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Slim 5 16ABR8
dmi.ec.firmware.release: 1.21
dmi.modalias:
[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)
> This is 'Fix Released', so all done from our perspective. I am willing to collect data automatically if the problem is not resolved. Today I don't see a problem. But only 5 days have passed, this is not the period in which one can understand that the problem has been solved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2031537 Title: Ethernet not stable 23.04 (RTL8168/8169) Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in linux-hwe-6.2 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] Ethernet is unstable with Realtek RTL8168h/8111h NIC and kernel 6.2 resulting in frequent transmit queue timeouts. Related to ASPM. See 'original description' below. [Test Case] Just regular usage for an extended period of time. No transmit queue timeouts with RTL8168h/8111h NICs. [Where Problems Could Occur] Modification are isolated to the r8169 driver so only machine where that driver is loaded are affected. Issues could show up as kernel crashes, stack traces, non-fnuctional wired network. [Original Description] hello, it is my first time reporting a pug hope it is the last there is thread here https://ubuntuforums.org/showthread.php?t=2489146=14151513 another user experienced similar issue my network work fine at startup keep working for hours then disconnect and cannot reconnect without a restart I tested the cable using another pc and it was working repluged with no difference I thought it is caused by nvidia driver so changed it and the problem persist I use systemd-networkd uname -a Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b) dmesg: [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): apparmor="ALLOWED" operation="file_perm" class="file" profile="libreoffice-oosplash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [Mon Aug 7 12:39:19 2023] [ cut here ] [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clmulni_intel rc_core [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus xhci_pci_renesas idma64 wmi pinctrl_cannonlake [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 6.2.0-26-generic #26-Ubuntu [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 2.13.1 05/10/2023 [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250 [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246 [Mon Aug 7 12:39:19 2023] RAX: RBX:
