[Kernel-packages] [Bug 2061953] Re: intel_rapl_common: Add support for ARL and LNL
** Tags added: intel oem-priority originate-from-2044672 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2061953 Title: intel_rapl_common: Add support for ARL and LNL Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.8 package in Ubuntu: Fix Released Status in linux source package in Noble: New Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: [Impact] The installer doesn't work without blacklisting intel_rapl_common (snap mounts fail), unless these commits are added. Needs a oneliner fix for both platforms: 4add6e841a3e079 powercap: intel_rapl: Add support for Arrow Lake 876ed77fbed4450 powercap: intel_rapl: Add support for Lunar Lake-M paltform [Test case] Check that snaps work. [Regression potential] Can't regress other platforms, and if these would then fail in other ways, it's still likely better than before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2061953/+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 2061953] Re: intel_rapl_common: Add support for ARL and LNL
** Tags added: originate-from-203 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2061953 Title: intel_rapl_common: Add support for ARL and LNL Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.8 package in Ubuntu: Fix Released Status in linux source package in Noble: New Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: [Impact] The installer doesn't work without blacklisting intel_rapl_common (snap mounts fail), unless these commits are added. Needs a oneliner fix for both platforms: 4add6e841a3e079 powercap: intel_rapl: Add support for Arrow Lake 876ed77fbed4450 powercap: intel_rapl: Add support for Lunar Lake-M paltform [Test case] Check that snaps work. [Regression potential] Can't regress other platforms, and if these would then fail in other ways, it's still likely better than before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2061953/+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 2062412] Re: No input through internal microphone (Ryzen 6000)
*** This bug is a duplicate of bug 2061254 *** https://bugs.launchpad.net/bugs/2061254 This issue was already reported in #2061254. ** This bug has been marked a duplicate of bug 2061254 No mic detected - Ubuntu 24.04 Beta -- 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/2062412 Title: No input through internal microphone (Ryzen 6000) Status in linux package in Ubuntu: New Bug description: The microphone in a Thinkpad P14S (AMD) Gen 4 stopped working after updating from 23.10 to 24.04 Beta with kernel 6.8.0-22-generic. This is a known problem and a patch may be included in kernel 6.8.3. Is it possible to backport this patch? Or is the plan to wait for a kernel update? It would be good use the microphone in 24.04. The symptoms are exactly as described in https://bbs.archlinux.org/viewtopic.php?pid=2162297#p2162297 Reportedly the patch is included in https://github.com/zen-kernel/zen-kernel/blob/6.7/main/sound/soc/amd/yc/acp6x-mach.c#L59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062412/+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 2062534] Re: GDM3 autologin might be racy on GCP resulting in inconsistent state of the wayland setup of seat0
** Tags added: jammy -- 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/2062534 Title: GDM3 autologin might be racy on GCP resulting in inconsistent state of the wayland setup of seat0 Status in gdm3 package in Ubuntu: Confirmed Status in linux-gcp package in Ubuntu: Confirmed Bug description: This might not be a bug really about linux-gcp, but this is following the work on bug 2039732 and so far I could not reproduce that locally. Setup is 22.04 uptodate on GCP n2-standard instances, without GPU attached thus relying on vkms. I have reproduced locally a similar setup but on a KVM host. We rely on https://github.com/taskcluster/taskcluster/tree/main/workers/generic-worker#readme to run tasks on CI, and especially generic-worker will: - create a new task_XXX user - make it autologin in gdm3 config - generic-worker has code to probe for existence of the GNOME Wayland session before launching the task We relied on wl-clipboard package installed for verifying the status of wayland On top of that setup, here is the issue. We issue a TC task with payload: > export WAYLAND_DISPLAY=wayland-0 > export XDG_RUNTIME_DIR=/run/user/$(id -u) > wl-paste -l -p We expect that payload to report "No selection", but on GCP instances we mostly always end up with "This seat has no keyboard". There were also cases were the session would not be Wayland at all but rather X11. I think this suggests something around the availability of /dev/dri/card0, but forcing the gdm3 service to wait for its availability and adding extra waiting time after card0 is present would still not get us somewhere. We enabled gdm3 as well as mutter debugging but never found anything that would be a good lead on why it was not yet ready. At some point, the seat0 session of our user was shown as inactive and the active one was tied to gdm so we suspected this was the reason, but both forcing the session to be active and terminating the gdm session would still not unblock us. We also suspected the desktop to be locking itself so we disabled locking with the following, but iit did not help much: > cat > /etc/dconf/profile/user << EOF > user-db:user > system-db:local > EOF > > mkdir /etc/dconf/db/local.d/ > # dconf user settings > cat > /etc/dconf/db/local.d/00-tc-gnome-settings << EOF > # /org/gnome/desktop/session/idle-delay > [org/gnome/desktop/session] > idle-delay=uint32 0 > # /org/gnome/desktop/lockdown/disable-lock-screen > [org/gnome/desktop/lockdown] > disable-lock-screen=true > EOF > > sudo dconf update In the end, the only viable and reliable (verified over hundreds of runs now) fix that lasted was to add a "/bin/sleep 30" all to the gdm3 startup: > mkdir -p /etc/systemd/system/gdm.service.d/ > cat > /etc/systemd/system/gdm.service.d/gdm-wait.conf << EOF > [Unit] > Description=Extra 30s wait > [Service] > ExecStartPre=/bin/sleep 30 > EOF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2062534/+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 2062502] Re: linux-firmware package breaks iwlwifi
** Changed in: linux-firmware (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- 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/2062502 Title: linux-firmware package breaks iwlwifi Status in linux-firmware package in Ubuntu: New Bug description: This package version works: 20230919.git3672ccab-0ubuntu2.1 This one causes firmware SW errors and resets - breaking wifi in iwlwifi driver: 20230919.git3672ccab-0ubuntu2.9 I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade to ...2.9 of the linux-firmware package, I saw many errors that begin like this in syslog: 2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi :00:14.3: Queue 1 is stuck 0 12 2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. 2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi :00:14.3: Start IWL Error Log Dump: 2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi :00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+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 2062545] Re: Still, No keyboard after kernel update Linux t-l15 6.5.0-1020-oem
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- 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/2062545 Title: Still, No keyboard after kernel update Linux t-l15 6.5.0-1020-oem Status in linux package in Ubuntu: Confirmed Bug description: Hello, I use the ThinkPad L15 Gen4, BIOS version R24ET38W(1.21) together with Xubuntu 22.04.04 LTS kernel 6.5.0-1020-oem, the CPU type is i7-1355U. This combination gives still a not working keyboard after booting. Today the system has upgraded the kernel to Linux version 6.5.0-1020-oem this should solves the keyboard problem introduced in kernel 6.5.0-1019-oem and already reported in: - https://bugs.launchpad.net/bugs/2060727 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060866 This bug fix does not work, I still have no internal keyboard. For the moment I am using kernel 6.5.0-1018-oem which workes fine. Who can/will help? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062545/+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 2062562] Re: Keyboard not working after resume from suspend on Dell XPS 13 laptop
** Changed in: linux-signed (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2062562 Title: Keyboard not working after resume from suspend on Dell XPS 13 laptop Status in linux-signed package in Ubuntu: New Bug description: After upgrade to 6.5.0-27-generic keyboard stopped working when laptop comes back to life after suspend. When booted with 6.5.0-26-generic everything is fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2062562/+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 2062546] Re: Ubuntu 22.04 Lock Screen is changing the brightness level automatically - Asus Vivobook
** Changed in: linux-signed-hwe-6.5 (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2062546 Title: Ubuntu 22.04 Lock Screen is changing the brightness level automatically - Asus Vivobook Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Ubuntu 22.04 Lock Screen is changing the brightness level automatically - Asus Vivobook OLED 15. Also, fingerprint scanner seems not to work. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 17:38:06 2024 InstallationDate: Installed on 2024-04-18 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2062546/+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 2062950] Re: RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10
Thanks for the bug report. Most likely the problem is an HDMI connection
problem. Please try a new HDMI cable if you can. If you can't then
please try temporarily running the external monitor at a lower
resolution to see if the flicker then goes away.
If the flicker still persists then please attach a video of the issue
(recording on a phone is fine).
** Tags added: flicker multimonitor
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2062950
Title:
RE: Flickering problems on external monitor with HDMI after installing
Ubuntu 23.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
this is a continuation of the bug reported in
https://bugs.launchpad.net/ubuntu/+bug/2062504
I reinstalled ubuntu 23, and didn't install anything else. I'm still
having the flickering when connecting an HDMI to an external monitor.
please help
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 19 22:27:21 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
InstallationDate: Installed on 2024-04-20 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2024
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: R1UET46W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21B4S4QB00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76465 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias:
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
dmi.product.family: ThinkPad L13 Gen 3
dmi.product.name: 21B4S4QB00
dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
dmi.product.version: ThinkPad L13 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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/ubuntu/+source/linux/+bug/2062950/+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 2063074] [NEW] Waydroid breaks nouveau
Public bug reported: https://waydro.id/ The session is forced to logout. nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30070]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30070]] subc 0 class c597 mthd 17e0 data 0018 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30107]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30107]] subc 0 class c597 mthd 17e0 data 0018 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30145]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30145]] subc 0 class c597 mthd 17e0 data 0018 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 RenderThread[26039]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 RenderThread[26039]] subc 0 class c597 mthd 17e0 data 000c nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 RenderThread[26039]] subc 0 class c597 mthd 17e0 data 0060 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 8 [007f862000 RenderThread[26090]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 8 [007f862000 RenderThread[26090]] subc 0 class c597 mthd 17e0 data 0018 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:neo3373 F pipewire /dev/snd/controlC0: neo3373 F pipewire neo3377 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 07:32:35 2024 InstallationDate: Installed on 2024-03-22 (30 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-31-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash ipv6.disable=1 RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-11 (11 days ago) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Description changed: https://waydro.id/ + + The session is forced to logout. nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30070]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30070]] subc 0 class c597 mthd 17e0 data 0018 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30107]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30107]] subc 0 class c597 mthd 17e0 data 0018 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30145]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30145]] subc 0 class c597 mthd 17e0 data 0018 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 RenderThread[26039]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 RenderThread[26039]] subc 0 class c597 mthd 17e0 data 000c nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 RenderThread[26039]] subc 0 class c597 mthd 17e0 data 0060 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 8 [007f862000 RenderThread[26090]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c []
[Kernel-packages] [Bug 2063067] Re: Fix bluetooth connections with 3.0 device
** Description changed:
[Impact]
Bluetooth keyboard cannot be connected to Realtek BT controller.
[Fix]
It's a regression from Ubuntu-6.5.0-20.20 and Ubuntu-oem-6.5-6.5.0-1016.17
The bad commit:
c7f59461f5a78 ("Bluetooth: Fix a refcnt underflow problem for hci_conn")
+ Fix:
+ 7e74aa53a68bf ("Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST")
[Test]
Tested on hardware, the bt3.0 keyboard connects to host well.
[Where problems could occur]
It may break bluetooth.
The commit is already in v6.8-rc7,
SRU oem-6.5 and mantic.
--
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/2063067
Title:
Fix bluetooth connections with 3.0 device
Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-oem-6.5 package in Ubuntu:
New
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[Impact]
Bluetooth keyboard cannot be connected to Realtek BT controller.
[Fix]
It's a regression from Ubuntu-6.5.0-20.20 and Ubuntu-oem-6.5-6.5.0-1016.17
The bad commit:
c7f59461f5a78 ("Bluetooth: Fix a refcnt underflow problem for hci_conn")
Fix:
7e74aa53a68bf ("Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST")
[Test]
Tested on hardware, the bt3.0 keyboard connects to host well.
[Where problems could occur]
It may break bluetooth.
The commit is already in v6.8-rc7,
SRU oem-6.5 and mantic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063067/+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 2063002] Re: Add support for DCN 3.5
** Changed in: linux-firmware (Ubuntu Noble) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- 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/2063002 Title: Add support for DCN 3.5 Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Noble: New Bug description: Products with DCN 3.5 need linux-firmware to be added for noble. Matching kernel support is already in kernel 6.8. 6bfdacdd amdgpu: add DMCUB 3.5 firmware cb59bf73 amdgpu: add VPE 6.1.0 firmware 3ca35ef5 amdgpu: add VCN 4.0.5 firmware 9a3a6c61 amdgpu: add UMSCH 4.0.0 firmware 62cc1372 amdgpu: add SDMA 6.1.0 firmware b455dd24 amdgpu: add PSP 14.0.0 firmware 30c1adcb amdgpu: add GC 11.5.0 firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2063002/+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 2062452] Re: package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to install/upgrade: installed linux-headers-6.5.0-28-generic package post-installation script subprocess r
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
--
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/2062452
Title:
package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to
install/upgrade: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
New
Bug description:
linux-headers-6.5.0-27-generic
linux-headers-6.5.0-28-generic
linux-headers-generic-hwe-22.04
linux-generic-hwe-22.04
linux-headers-generic
linux-image-6.5.0-27-generic
linux-image-6.5.0-28-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-28-generic 6.5.0-28.29
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: talha-g1584 F wireplumber
/dev/snd/seq:talha-g1580 F pipewire
CasperMD5CheckResult: pass
Date: Fri Apr 19 07:46:04 2024
ErrorMessage: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-03-19 (31 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=a09c8968-b5f7-4fe1-a194-4150a0ca843e ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to
install/upgrade: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2021
dmi.bios.release: 1.25
dmi.bios.vendor: LENOVO
dmi.bios.version: DJCN25WW
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ThinkBook 15-IIL
dmi.ec.firmware.release: 1.20
dmi.modalias:
dmi:bvnLENOVO:bvrDJCN25WW:bd03/29/2021:br1.25:efr1.20:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL:skuLENOVO_MT_20SM_BU_idea_FM_Thinkbook15-IIL:
dmi.product.family: Thinkbook 15-IIL
dmi.product.name: 20SM
dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL
dmi.product.version: Lenovo ThinkBook 15-IIL
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062452/+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 2062950] [NEW] RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10
You have been subscribed to a public bug:
this is a continuation of the bug reported in
https://bugs.launchpad.net/ubuntu/+bug/2062504
I reinstalled ubuntu 23, and didn't install anything else. I'm still
having the flickering when connecting an HDMI to an external monitor.
please help
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 19 22:27:21 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
InstallationDate: Installed on 2024-04-20 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2024
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: R1UET46W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21B4S4QB00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76465 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias:
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
dmi.product.family: ThinkPad L13 Gen 3
dmi.product.name: 21B4S4QB00
dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
dmi.product.version: ThinkPad L13 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: amd64 apport-bug flicker mantic multimonitor ubuntu wayland-session
--
RE: Flickering problems on external monitor with HDMI after installing Ubuntu
23.10
https://bugs.launchpad.net/bugs/2062950
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 2062966] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- 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/2062966 Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1055.61 Status in linux package in Ubuntu: New Bug description: Hello, I wanted to measure the frequency of the processors on my machine, but I couldn't install the package. Thank you. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-tools-common:amd64: Install linux-tools-5.15.0-105:amd64: Install linux-tools-5.15.0-105-generic:amd64: Install linux-tools-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: misha 2313 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Sat Apr 20 13:21:12 2024 DpkgTerminalLog: Preparing to unpack .../linux-tools-common_5.15.0-105.115_all.deb ... Unpacking linux-tools-common (5.15.0-105.115) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-tools-common_5.15.0-105.115_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1055.61 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1055.61 InstallationDate: Installed on 2024-03-29 (21 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: HP HP Laptop 17-cn3xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic root=UUID=71c5bf0d-2969-489a-89a0-f76890efa677 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.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: linux Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1055.61 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2023 dmi.bios.release: 15.3 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8BBA dmi.board.vendor: HP dmi.board.version: 65.13 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 65.13 dmi.modalias: dmi:bvnInsyde:bvrF.03:bd07/18/2023:br15.3:efr65.13:svnHP:pnHPLaptop17-cn3xxx:pvrType1ProductConfigId:rvnHP:rn8BBA:rvr65.13:cvnHP:ct10:cvrChassisVersion:sku8D018EA#BED: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 17-cn3xxx dmi.product.sku: 8D018EA#BED dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062966/+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 2062951] Re: Random flickering with i915 on Linux 6.8
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- 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/2062951 Title: Random flickering with i915 on Linux 6.8 Status in linux package in Ubuntu: New Bug description: After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random. It happens after a moderate to heavy on screen activity like window switching, scrolling etc. It never happens when playing video or when there is no interaction using keyboard/pointer. It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region. Around the same time the following appears in kernel log: kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Happens on both X11 and Wayland on both KDE plasma and Mate (though less). I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7. Kernels 6.6, 6.5, 6.1 and older did not have that issue. Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD Graphics 520] Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26 Attaching kernel log for 6.8.0-28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951/+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 2062985] Re: ALSA Fails to detect any devices with kernel 6.8.0
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- 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/2062985 Title: ALSA Fails to detect any devices with kernel 6.8.0 Status in linux package in Ubuntu: New Bug description: Submitting this bug report from kernel 6.5.0 where it seems to work. When running aplay -l on kernel 6.8 the output is empty. And pulseaudio also shows an error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-28-generic 6.8.0-28.28 ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kyrboh 1363 F wireplumber /dev/snd/seq:kyrboh 1358 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Apr 20 21:15:03 2024 InstallationDate: Installed on 2023-11-04 (169 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic root=UUID=db41af68-2c72-4fc6-a654-5b0f2be10d62 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-28-generic N/A linux-backports-modules-6.5.0-28-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-20 (0 days ago) dmi.bios.date: 11/10/2022 dmi.bios.release: 1.31 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.31.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.31.0:bd11/10/2022:br1.31:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062985/+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 2062977] Re: Please backport d02c357e5bfa7dfd618b7b3015624beb71f58f1f
** Changed in: linux-azure (Ubuntu) Assignee: (unassigned) => Marcelo Cerri (mhcerri) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2062977 Title: Please backport d02c357e5bfa7dfd618b7b3015624beb71f58f1f Status in linux-azure package in Ubuntu: New Bug description: We've been starting to run the systemd integration tests on Github Actions, and noticed a soft lockup in of our VMs: """ [ 245.130625] INFO: task khugepaged:38 blocked for more than 122 seconds. [ 245.131669] Not tainted 6.8.7-arch1-1 #1 [ 245.132371] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 245.134651] INFO: task test-journal-ve:4563 blocked for more than 122 seconds. [ 245.136035] Not tainted 6.8.7-arch1-1 #1 [ 245.136921] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 253.516332] systemd[1]: Unmounting efi.mount... [ 253.535696] systemd[1]: efi.mount: Deactivated successfully. [ 253.537261] systemd[1]: Unmounted efi.mount. [ 345.502294] systemd[1006]: Created slice background.slice. [ 345.504159] systemd[1006]: Starting systemd-tmpfiles-clean.service... [ 345.537927] systemd[1006]: Finished systemd-tmpfiles-clean.service. [ 368.017373] INFO: task khugepaged:38 blocked for more than 245 seconds. [ 368.019120] Not tainted 6.8.7-arch1-1 #1 [ 368.020219] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 368.021719] INFO: task test-journal-ve:4563 blocked for more than 245 seconds. [ 368.023485] Not tainted 6.8.7-arch1-1 #1 [ 368.024593] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 490.891682] INFO: task khugepaged:38 blocked for more than 368 seconds. [ 490.893456] Not tainted 6.8.7-arch1-1 #1 [ 490.894594] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 490.896750] INFO: task test-journal-ve:4563 blocked for more than 368 seconds. [ 490.897930] Not tainted 6.8.7-arch1-1 #1 [ 490.898880] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. """ This is the same lockup as was already investigated in https://github.com/systemd/systemd-centos-ci/issues/720 and was traced to a missing backported commit in the *host* kernel, specifically d02c357e5bfa7dfd618b7b3015624beb71f58f1f (KVM: x86/mmu: Retry fault before acquiring mmu_lock if mapping is changing). See the linked issue for all the details. Can this commit please be backported to linux-azure to fix these soft lockups in VMs running on Github Actions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2062977/+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 2063067] Re: Fix bluetooth connections with 3.0 device
** Changed in: linux (Ubuntu Jammy)
Status: Invalid => In Progress
** Description changed:
[Impact]
Bluetooth keyboard cannot be connected to Realtek BT controller.
[Fix]
It's a regression from Ubuntu-6.5.0-20.20 and Ubuntu-oem-6.5-6.5.0-1016.17
The bad commit:
c7f59461f5a78 ("Bluetooth: Fix a refcnt underflow problem for hci_conn")
Fix:
7e74aa53a68bf ("Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST")
[Test]
Tested on hardware, the bt3.0 keyboard connects to host well.
[Where problems could occur]
It may break bluetooth.
The commit is already in v6.8-rc7,
- SRU oem-6.5 and mantic.
+ SRU Jammy, oem-6.5 and Mantic.
--
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/2063067
Title:
Fix bluetooth connections with 3.0 device
Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-oem-6.5 package in Ubuntu:
New
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[Impact]
Bluetooth keyboard cannot be connected to Realtek BT controller.
[Fix]
It's a regression from Ubuntu-6.5.0-20.20 and Ubuntu-oem-6.5-6.5.0-1016.17
The bad commit:
c7f59461f5a78 ("Bluetooth: Fix a refcnt underflow problem for hci_conn")
Fix:
7e74aa53a68bf ("Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST")
[Test]
Tested on hardware, the bt3.0 keyboard connects to host well.
[Where problems could occur]
It may break bluetooth.
The commit is already in v6.8-rc7,
SRU Jammy, oem-6.5 and Mantic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063067/+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 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
I can produce the error with two fresh installed VMs. Server - Debian 12 installed from debian-12.5.0-amd64-netinst.iso with current updates - kernel "Linux cifstest-server 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64 GNU/Linux" - cifs share as in #14 Client - Ubuntu 23.10 installed from ubuntu-23.10.1-desktop-amd64.iso with current updates - kernel "Linux cifs-client 6.5.0-28-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 28 23:46:48 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux" - cifs mount as in #14 - cd ~/share; touch abc; cp abc xyz -> "Killed" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Bug description: Remote filesystems mounted as CIFS are not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64). The remote filesystem is correctly mounted and seems to work but trying to write data to the filesystem ends in a kernel error exception. After that error the CIFS filesystem just became unusable. Previous Kernel version works correctly. = Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64) = # lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 # uname -a Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 6.5.0-27.28-generic 6.5.13 How to reproduce the problem For instance, I'm using KeePassXC (https://launchpad.net/ubuntu/+source/keepassxc) to update a database located at CIFS filesystem. Any change done to that database causes this Kernel error exception: abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: fffe abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0 abr 11 09:34:59 fpgmsi kernel: Oops: [#1] PREEMPT SMP NOPTI abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic #28-Ubuntu abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022 abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 abr 11 09:34:59 fpgmsi kernel: RAX: RBX: fffe RCX: abr 11 09:34:59 fpgmsi kernel: RDX: RSI: RDI: abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 R09: abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11: R12: abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70 abr 11 09:34:59 fpgmsi kernel: FS: 7bd4d594b6c0() GS:90753f80() knlGS: abr 11 09:34:59 fpgmsi kernel: CS: 0010 DS: ES: CR0: 80050033 abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 CR4: 00750ef0 abr 11 09:34:59 fpgmsi kernel: PKRU: 5554 abr 11 09:34:59 fpgmsi kernel: Call Trace: abr 11 09:34:59 fpgmsi kernel: abr 11 09:34:59 fpgmsi kernel: ? show_regs+0x6d/0x80 abr 11 09:34:59 fpgmsi kernel: ? __die+0x24/0x80 abr 11 09:34:59 fpgmsi kernel: ? page_fault_oops+0x99/0x1b0 abr 11 09:34:59 fpgmsi kernel: ? kernelmode_fixup_or_oops+0xb2/0x140 abr 11 09:34:59 fpgmsi kernel: ? __bad_area_nosemaphore+0x1a5/0x2c0 abr 11 09:34:59 fpgmsi kernel: ? bad_area_nosemaphore+0x16/0x30 abr 11 09:34:59 fpgmsi kernel: ? do_kern_addr_fault+0x7b/0xa0 abr 11 09:34:59 fpgmsi kernel: ? exc_page_fault+0x1a4/0x1b0 abr 11 09:34:59 fpgmsi kernel: ? asm_exc_page_fault+0x27/0x30 abr 11 09:34:59 fpgmsi
[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
** Description changed: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] - The in-tree vsc driver as of v6.8 still need a few fixes to archive the - same supportness to launched Intel IPU6 Camera devices. Commit 1,3, and + The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the + same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] - The dkms is created to be compatible of multiple versions, yet the in- - tree vsc driver transitioning should only happen for kernel >= v6.8. - That is, oem-6.8, noble and linux-unstable will be nominated. + The dkms is created to be compatible of multiple kernel versions, yet + the in-tree vsc driver transitioning should only happen for kernel >= + v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: In Progress Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: In Progress Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple kernel versions, yet the in-tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+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 1788044] Re: task kworker blocked for more than 120 seconds nouveau
This is the closest, most recent report I could find with something which also appears kernel related Kernel 6.5.0-27 -- works fine Kernel 6.5.0-28 -- graphics hard-hangs - sddm never displays, vtty can't be activated shh works, sddm and x11 processes can not be killed, reboot hangs, hard power cycle required I see reports like this literally for years, yet seemingly no resolution. Now I'm bit, in a way suspiciously kernel version related Common internet "use nvidia drivers" wisdom is unworkable as old nvidia hardware is not supported on 22.04 04:00.0 VGA compatible controller: NVIDIA Corporation MCP89 [GeForce 320M] (rev a2) Again, for me, this is with 22.04, kernel 6.5.0-28 All the various combinations of nouveau flags to kernel boot which have helped reduce garbage or sddm troubles don't help. Here's a relevant boot log: Apr 20 21:06:29 Konnekt sddm-greeter[922]: Adding view for "LVDS-1" QRect(0,0 1280x800) Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 216004 put 216088 ib_get 0007 ib_put 0007 state 800081a4 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 21608c put 217b7c ib_get 0009 ib_put 000a state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 218ff0 put 21932c ib_get 000d ib_put 0012 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219a48 put 219a64 ib_get 001f ib_put 0024 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219a64 put 219a7c ib_get 0021 ib_put 0024 state 8024 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219a7c put 219a8c ib_get 0023 ib_put 0024 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219a8c put 219ccc ib_get 0025 ib_put 002a state 8024 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219de8 put 219df8 ib_get 002f ib_put 0030 state 4004 (err: INVALID_MTHD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: CACHE_ERROR - ch 3 [sddm-greeter[922]] subc 0 mthd data 2000 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219ef0 put 21a2f0 ib_get 0033 ib_put 0038 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 0020b10960 put 0020b10ac8 ib_get 0042 ib_put 0044 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 21aff8 put 21bdf4 ib_get 004b ib_put 004c state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 21c248 put 21c620 ib_get 004d ib_put 004e state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 417a40 put 417a4c ib_get 0056 ib_put 0058 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 417b54 put 417b5c ib_get 005c ib_put 005e state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 4d3370 put 4d33f4 ib_get 0062 ib_put 0064 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 4db3c0 put 4db450 ib_get 0068 ib_put 006a state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 21d000 put 21d150 ib_get 006b ib_put 006c state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 417c50 put 417c5c ib_get 006e ib_put 0070 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 4d3630 put 4d3684 ib_get 007a
[Kernel-packages] [Bug 2062412] Re: No input through internal microphone (Ryzen 6000)
*** This bug is a duplicate of bug 2061254 *** https://bugs.launchpad.net/bugs/2061254 I tried mainline daily build 6.9.0-060900rc4daily20240420-generic. (Does it include commits that came a few hours before?) The microphone appears to be an acp63 device. Both snd_pci_acp6x and snd_pci_ps are loaded. Is the next step to blacklist snd_pci_acp6x? kernel: https://kernel.ubuntu.com/mainline/daily/2024-04-20/amd64/ commits: ASoC: amd: yc: Revert "add new YC platform variant (0x63) support" https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/?h=master- next=c58513355783d99af76c5b49e22cc4d275268d81 ASoC: amd: yc: Revert "Fix non-functional mic on Lenovo 21J2" https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/?h=master- next=575642e9cdf5ce526822a63daacb22802e4d64cd $ cat /proc/asound/cards 0 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0x785c8000 irq 90 1 [Generic_1 ]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0x785c irq 91 2 [acp63 ]: acp63 - acp63 LENOVO-21K5CTO1WW-ThinkPadP14sGen4 $ sudo lsmod | grep snd_pci snd_pci_ps 24576 0 snd_amd_sdw_acpi 16384 2 snd_sof_amd_acp,snd_pci_ps soundwire_amd 45056 2 snd_sof_amd_acp,snd_pci_ps snd_pci_acp6x 16384 0 snd_pci_acp5x 16384 0 snd_pcm 196608 14 snd_sof_amd_acp,snd_hda_codec_hdmi,snd_pci_acp6x,snd_hda_intel,snd_hda_codec,snd_sof,snd_ps_pdm_dma,snd_compress,snd_soc_core,snd_sof_utils,soundwire_amd,snd_hda_core,snd_pci_ps,snd_pcm_dmaengine snd_acp_config 20480 9 snd_rn_pci_acp3x,snd_pci_acp6x,snd_pci_acp5x,snd_sof_amd_rembrandt,snd_sof_amd_vangogh,snd_sof_amd_acp63,snd_acp_pci,snd_pci_ps,snd_sof_amd_renoir snd_soc_acpi 20480 3 snd_sof_amd_acp,snd_acp_config,snd_pci_ps snd_pci_acp3x 16384 0 -- 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/2062412 Title: No input through internal microphone (Ryzen 6000) Status in linux package in Ubuntu: New Bug description: The microphone in a Thinkpad P14S (AMD) Gen 4 stopped working after updating from 23.10 to 24.04 Beta with kernel 6.8.0-22-generic. This is a known problem and a patch may be included in kernel 6.8.3. Is it possible to backport this patch? Or is the plan to wait for a kernel update? It would be good use the microphone in 24.04. The symptoms are exactly as described in https://bbs.archlinux.org/viewtopic.php?pid=2162297#p2162297 Reportedly the patch is included in https://github.com/zen-kernel/zen-kernel/blob/6.7/main/sound/soc/amd/yc/acp6x-mach.c#L59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062412/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Hi, I believe that kernel 5.15.0-105-generic may not have have solved the issue entirely. I upgraded to 104 from -proposed, and then when 105 was available, I updated to 105, and then removed 104 and the -proposed repo entirely. While, the issue does not present itself as frequently, I still encounter similar if not the same CIFS errors that were not present in older kernels. After updating to 105, I no longer encountered the issue when I first connect to the SMB share. However, I encounter the issue during long file copies to an SMB share. After trying to copy 20GB of data to the smb server, the the copy is interrupted after some time, and then the mount point is broken and unable to be accessed. I am using dockers cifs volumes to mount smb shares into docker containers. The host uses cifs and mounts these into the /var/lib/docker/volumes/... directories which are remapped to containers in some way. I have encountered the issue on 105 after the following steps. On the host, I directly added a mount in `/etc/fstab`, updated `systemctl daemon-reload`, and mounted the share `mount -a`. I then copy 20GB of data to the share `cp -r /path/to/my/data /mnt/rf/data`. After about a minute, the copy terminates. In `dmesg`, I see the cifs errors. When I look at the host CIFS mount point, I can see that the folder is inaccessible. uname -a ``` Linux docker-gpu-01 5.15.0-105-generic #115-Ubuntu SMP Mon Apr 15 09:52:04 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux ``` apt list --installed | grep "cifs-utils" ``` cifs-utils/jammy-updates,jammy-security,now 2:6.14-1ubuntu0.1 amd64 [installed] ``` cat /etc/fstab ``` ... //10.0.6.2/rf /mnt/rf cifs uid=1000,gid=1000,credentials=/home/user/.smb 0 0 ``` sudo dmesg ``` [138420.302415] CIFS: Attempting to mount \\10.0.6.2\rf [138420.315798] CIFS: VFS: parse_server_interfaces: malformed interface info [138538.756550] CIFS: VFS: \\10.0.6.2 sends on sock 9d8f9284 stuck for 15 seconds [138538.757040] CIFS: VFS: \\10.0.6.2 Error -11 sending data on socket to server [138543.032429] CIFS: reconnect tcon failed rc = -13 [138543.051221] CIFS: VFS: No writable handle in writepages rc=-13 [138543.053159] CIFS: VFS: No writable handle in writepages rc=-13 [138543.063685] CIFS: VFS: No writable handle in writepages rc=-13 [138543.065707] CIFS: VFS: No writable handle in writepages rc=-13 [138543.077380] CIFS: VFS: No writable handle in writepages rc=-13 [138543.080055] CIFS: VFS: No writable handle in writepages rc=-13 [138543.090757] CIFS: VFS: No writable handle in writepages rc=-13 [138543.092996] CIFS: VFS: No writable handle in writepages rc=-13 [138543.151054] CIFS: VFS: \\10.0.6.2\media Close unmatched open for MID:116 ``` Notes: You can see that at `138420` I ran `mount -a` and the mount was added. There was an error `parse_server_interfaces: malformed interface info`, but the file system was mounted and available. Shortly after, I started the file transfer (I started it probably after 20-30 seconds.). This file transfer failed by `138538` and produced the `VFS: \\10.0.6.2 sends on sock 9d8f9284 stuck for 15 seconds` error. I can see on the sever that about `6GB/20GB` of data has transferred at this point. Finally, you can see that at `138543`, a different mount (managed by docker) failed with the error `VFS: \\10.0.6.2\media Close unmatched open for MID:116`. The storage system has a 1Gbps link to the server. Assuming 80MBps, the file copy would have made it through 6GB in about 75 seconds before it encountered this error, which is consistent with the dmesg timeline and my experience while watching the file copy. The mount point on the host now looks like this: sudo ls -hal /mnt ``` ls: cannot access '/mnt/rf': Permission denied total 8.0K drwxr-xr-x 3 root root 4.0K Apr 21 10:03 . drwxr-xr-x 19 root root 4.0K Mar 26 21:02 .. d? ? ?? ?? rf ``` I have not looked at the bugfix code, or the code that introduced the bug, but I am not fully convinced that the issue is solved. -- 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/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and
[Kernel-packages] [Bug 2060919] Re: cifs: Copying file to same directory results in page fault
** Summary changed: - Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). + cifs: Copying file to same directory results in page fault ** Description changed: - Remote filesystems mounted as CIFS are not working after update to - Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after updating - to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64). + BugLink: https://bugs.launchpad.net/bugs/2060919 - The remote filesystem is correctly mounted and seems to work but trying - to write data to the filesystem ends in a kernel error exception. After - that error the CIFS filesystem just became unusable. + [Impact] - Previous Kernel version works correctly. + Copying or modifying a file to the same directory within a cifs mount + results in a page fault, and the process that initiated the copy being + killed. This could be cp, nautilus, etc. - = - Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64) - = - # lsb_release -rd - No LSB modules are available. - Description: Ubuntu 23.10 - Release: 23.10 + This results in the following oops: - # uname -a - Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux + BUG: unable to handle page fault for address: fffe + #PF: supervisor read access in kernel mode + #PF: error_code(0x) - not-present page + PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0 + Oops: [#1] PREEMPT SMP NOPTI + CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic #28-Ubuntu + RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] + Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 + RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 + RAX: RBX: fffe RCX: + RDX: RSI: RDI: + RBP: aab6865ffc28 R08: 0001 R09: + R10: 00023854 R11: R12: + R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70 + FS: 7bd4d594b6c0() GS:90753f80() knlGS: + CS: 0010 DS: ES: CR0: 80050033 + CR2: fffe CR3: 00017022a000 CR4: 00750ef0 + PKRU: 5554 + Call Trace: + + ? show_regs+0x6d/0x80 + ? __die+0x24/0x80 + ? page_fault_oops+0x99/0x1b0 + ? kernelmode_fixup_or_oops+0xb2/0x140 + ? __bad_area_nosemaphore+0x1a5/0x2c0 + ? bad_area_nosemaphore+0x16/0x30 + ? do_kern_addr_fault+0x7b/0xa0 + ? exc_page_fault+0x1a4/0x1b0 + ? asm_exc_page_fault+0x27/0x30 + ? cifs_flush_folio+0x41/0xf0 [cifs] + ? cifs_flush_folio+0x37/0xf0 [cifs] + cifs_remap_file_range+0x172/0x660 [cifs] + do_clone_file_range+0x101/0x2d0 + vfs_clone_file_range+0x3f/0x150 + ioctl_file_clone+0x52/0xc0 + do_vfs_ioctl+0x68f/0x910 + ? __fget_light+0xa5/0x120 + __x64_sys_ioctl+0x7d/0xf0 + do_syscall_64+0x59/0x90 + ? kmem_cache_free+0x22/0x3e0 + ? putname+0x5b/0x80 + ? exit_to_user_mode_prepare+0x30/0xb0 + ? syscall_exit_to_user_mode+0x37/0x60 + ? do_syscall_64+0x68/0x90 + ? do_syscall_64+0x68/0x90 + ? do_syscall_64+0x68/0x90 - # cat /proc/version_signature - Ubuntu 6.5.0-27.28-generic 6.5.13 + There is no known workaround. - - How to reproduce the problem - - For instance, I'm using KeePassXC (https://launchpad.net/ubuntu/+source/keepassxc) to update a database located at CIFS filesystem. Any change done to that database causes this Kernel error exception: + [Fix] - abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: fffe - abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode - abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page - abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0 - abr 11 09:34:59 fpgmsi kernel: Oops: [#1] PREEMPT SMP NOPTI - abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic #28-Ubuntu - abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022 - abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] - abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 - abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 - abr 11 09:34:59 fpgmsi kernel: RAX:
[Kernel-packages] [Bug 2060904] Re: Fix the RTL8852CE BT FW Crash based on SER false alarm
** Description changed: + This is SRU template for linux kernel: + + [Impact] + + On a Dell laptop, let it connect to a WiFi router, connect a BT + device, then disconnect it, connect the bt device again, we expect + the device could be connected successfully, but it couldn't and + the BT firmeware crashed. + + [Fix] + + Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel + patches, here we send the MR for 2 kernel patches. The firmware PR was + already sent out. And one of the patches is from linux-next, the other is + from rtw.git and is going to be merged to linux-next soon. + + [Test Case] + + + With the upgraded firmware + kernel with the 2 kernel patches, bt + firmware will not crash anymore and bt could connect / disconnect + many many bt devices. + + [Where problems could occur] + + This MR comes from upstream commits, it has low possibility to + introduce regression. If the bt or wifi on this laptop couldn't + work as well as before, it is possible that this MR introduces + regression. According to our test, the wifi and bt could work well + with upgraded firmware. + + === This SRU template is for linux-firmware: BugLink: https://bugs.launchpad.net/bugs/2060904 [Impact] On a Dell laptop, let it connect to a WiFi router, connect a BT device, then disconnect it, connect the bt device again, we expect the device could be connected successfully, but it couldn't and the BT firmeware crashed. [Fix] Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel patches, here we send the MR for firmware first. And it is backward compatible, the upgraded firmware could work with kernel without those 2 patches as well as before. [Test Case] With the upgraded firmware + kernel without the 2 kernel patches, the wifi and bt could work as well / bad as before. With the upgraded firmware + kernel with the 2 kernel patches, bt firmware will not crash anymore and bt could connect / disconnect many many bt devices. [Where problems could occur] This MR comes from upstream commit, it has low possibility to introduce regression. If the bt or wifi on this laptop couldn't work as well as before, it is possible that this MR introduces regression. According to our test, the wifi and bt could work well with upgraded firmware. -- 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/2060904 Title: Fix the RTL8852CE BT FW Crash based on SER false alarm Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: New Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Mantic: New Status in linux-firmware source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux-oem-6.8 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: This is SRU template for linux kernel: [Impact] On a Dell laptop, let it connect to a WiFi router, connect a BT device, then disconnect it, connect the bt device again, we expect the device could be connected successfully, but it couldn't and the BT firmeware crashed. [Fix] Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel patches, here we send the MR for 2 kernel patches. The firmware PR was already sent out. And one of the patches is from linux-next, the other is from rtw.git and is going to be merged to linux-next soon. [Test Case] With the upgraded firmware + kernel with the 2 kernel patches, bt firmware will not crash anymore and bt could connect / disconnect many many bt devices. [Where problems could occur] This MR comes from upstream commits, it has low possibility to introduce regression. If the bt or wifi on this laptop couldn't work as well as before, it is possible that this MR introduces regression. According to our test, the wifi and bt could work well with upgraded firmware. === This SRU template is for linux-firmware: BugLink: https://bugs.launchpad.net/bugs/2060904 [Impact] On a Dell laptop, let it connect to a WiFi router, connect a BT device, then disconnect it, connect the bt device again, we
[Kernel-packages] [Bug 2060919] Re: cifs: Copying file to same directory results in page fault
Hi everyone, Thanks for helping to test the test kernel, and I am glad that it fixes the issue. I have written a SRU template and have set it as the description of the bug. I have submitted the revert to the Kernel team mailing list for SRU: Cover Letter: https://lists.ubuntu.com/archives/kernel-team/2024-April/150433.html Patch: https://lists.ubuntu.com/archives/kernel-team/2024-April/150434.html I'll go and have a talk to the kernel team now. This is a regression, yes, but I am not sure if they will be interested in respinning the 2024.04.01 SRU cycle to include the fix, due to it being quite late in the cycle. https://kernel.ubuntu.com/ We just did an emergency respin last week to fix bug 2060780, which was another cifs regression for the 5.15 series, with an unrelated cause. I'll write back with what the kernel team say, and hopefully give you an estimated time of release. If its this SRU cycle, or the next. Thanks, Matthew PS: Peter, I tried Debian 12.5 and I still can't reproduce the 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/2060919 Title: cifs: Copying file to same directory results in page fault Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/2060919 [Impact] Copying or modifying a file to the same directory within a cifs mount results in a page fault, and the process that initiated the copy being killed. This could be cp, nautilus, etc. This results in the following oops: BUG: unable to handle page fault for address: fffe #PF: supervisor read access in kernel mode #PF: error_code(0x) - not-present page PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0 Oops: [#1] PREEMPT SMP NOPTI CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic #28-Ubuntu RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 RAX: RBX: fffe RCX: RDX: RSI: RDI: RBP: aab6865ffc28 R08: 0001 R09: R10: 00023854 R11: R12: R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70 FS: 7bd4d594b6c0() GS:90753f80() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: fffe CR3: 00017022a000 CR4: 00750ef0 PKRU: 5554 Call Trace: ? show_regs+0x6d/0x80 ? __die+0x24/0x80 ? page_fault_oops+0x99/0x1b0 ? kernelmode_fixup_or_oops+0xb2/0x140 ? __bad_area_nosemaphore+0x1a5/0x2c0 ? bad_area_nosemaphore+0x16/0x30 ? do_kern_addr_fault+0x7b/0xa0 ? exc_page_fault+0x1a4/0x1b0 ? asm_exc_page_fault+0x27/0x30 ? cifs_flush_folio+0x41/0xf0 [cifs] ? cifs_flush_folio+0x37/0xf0 [cifs] cifs_remap_file_range+0x172/0x660 [cifs] do_clone_file_range+0x101/0x2d0 vfs_clone_file_range+0x3f/0x150 ioctl_file_clone+0x52/0xc0 do_vfs_ioctl+0x68f/0x910 ? __fget_light+0xa5/0x120 __x64_sys_ioctl+0x7d/0xf0 do_syscall_64+0x59/0x90 ? kmem_cache_free+0x22/0x3e0 ? putname+0x5b/0x80 ? exit_to_user_mode_prepare+0x30/0xb0 ? syscall_exit_to_user_mode+0x37/0x60 ? do_syscall_64+0x68/0x90 ? do_syscall_64+0x68/0x90 ? do_syscall_64+0x68/0x90 There is no known workaround. [Fix] The stacktrace is very similar to a regression reported to upstream 6.1.y: https://lore.kernel.org/linux- mm/a76b370f93cb928c049b94e1fde0d2da506dfcb2.ca...@amazon.com/T/ The thread mentions that: commit 7b2404a886f8b91250c31855d287e632123e1746 Author: David Howells Date: Fri Dec 1 00:22:00 2023 + Subject: cifs: Fix flushing, invalidation and file size with copy_file_range() Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7b2404a886f8b91250c31855d287e632123e1746 introduced the issue to Debian's 6.1 kernel. This got backported to Ubuntu in: commit 3adbe2ccd8b9b8fde93e03958d6176945794d288 Author: David Howells Date: Fri Dec 1 00:22:00 2023 + Subject: cifs: Fix flushing, invalidation and file size with copy_file_range() $ git describe --contains 3adbe2ccd8b9b8fde93e03958d6176945794d288 Ubuntu-6.5.0-20.20~107 Which we have been using for some time now, and is not the culprit. Reading the regression mailing list thread, they mention that things work differently in 6.1: > Yeah. __filemap_get_folio() works differently in v6.1.y. There it returns a > folio or NULL. In 6.7 it returns a folio or a negative error code. The error > check in
[Kernel-packages] [Bug 2063067] [NEW] Fix bluetooth connections with 3.0 device
Public bug reported:
[Impact]
Bluetooth keyboard cannot be connected to Realtek BT controller.
[Fix]
It's a regression from Ubuntu-6.5.0-20.20 and Ubuntu-oem-6.5-6.5.0-1016.17
The bad commit:
c7f59461f5a78 ("Bluetooth: Fix a refcnt underflow problem for hci_conn")
Fix:
7e74aa53a68bf ("Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST")
[Test]
Tested on hardware, the bt3.0 keyboard connects to host well.
[Where problems could occur]
It may break bluetooth.
The commit is already in v6.8-rc7,
SRU oem-6.5 and mantic.
** Affects: hwe-next
Importance: High
Assignee: AaronMa (mapengyu)
Status: In Progress
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-oem-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: Invalid
** Affects: linux-oem-6.5 (Ubuntu Jammy)
Importance: High
Status: In Progress
** Affects: linux (Ubuntu Mantic)
Importance: High
Status: In Progress
** Affects: linux-oem-6.5 (Ubuntu Mantic)
Importance: Undecided
Status: Invalid
** Tags: oem-priority originate-from-2058356 sutton
** Tags added: oem-priority originate-from-2058356 sutton
** Also affects: linux-oem-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.5 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.5 (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.5 (Ubuntu Mantic)
Status: New => Invalid
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: hwe-next
Assignee: (unassigned) => AaronMa (mapengyu)
** Changed in: hwe-next
Importance: Undecided => High
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => High
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: hwe-next
Status: New => In Progress
--
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/2063067
Title:
Fix bluetooth connections with 3.0 device
Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-oem-6.5 package in Ubuntu:
New
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[Impact]
Bluetooth keyboard cannot be connected to Realtek BT controller.
[Fix]
It's a regression from Ubuntu-6.5.0-20.20 and Ubuntu-oem-6.5-6.5.0-1016.17
The bad commit:
c7f59461f5a78 ("Bluetooth: Fix a refcnt underflow problem for hci_conn")
Fix:
7e74aa53a68bf ("Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST")
[Test]
Tested on hardware, the bt3.0 keyboard connects to host well.
[Where problems could occur]
It may break bluetooth.
The commit is already in v6.8-rc7,
SRU oem-6.5 and mantic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063067/+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 2062412] Re: No input through internal microphone (Ryzen 6000)
*** This bug is a duplicate of bug 2061254 *** https://bugs.launchpad.net/bugs/2061254 The microphone is working in gnome desktop sessions with mainline daily build 6.9.0-060900rc4daily20240420-generic. -- 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/2062412 Title: No input through internal microphone (Ryzen 6000) Status in linux package in Ubuntu: New Bug description: The microphone in a Thinkpad P14S (AMD) Gen 4 stopped working after updating from 23.10 to 24.04 Beta with kernel 6.8.0-22-generic. This is a known problem and a patch may be included in kernel 6.8.3. Is it possible to backport this patch? Or is the plan to wait for a kernel update? It would be good use the microphone in 24.04. The symptoms are exactly as described in https://bbs.archlinux.org/viewtopic.php?pid=2162297#p2162297 Reportedly the patch is included in https://github.com/zen-kernel/zen-kernel/blob/6.7/main/sound/soc/amd/yc/acp6x-mach.c#L59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062412/+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 2056706] Re: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0"
This bug was fixed in the package linux - 6.8.0-31.31 --- linux (6.8.0-31.31) noble; urgency=medium * noble/linux: 6.8.0-31.31 -proposed tracker (LP: #2062933) * Packaging resync (LP: #1786013) - [Packaging] debian.master/dkms-versions -- update from kernel-versions (main/d2024.04.04) -- Andrea Righi Fri, 19 Apr 2024 23:46:38 +0200 ** 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/2056706 Title: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0" Status in linux package in Ubuntu: Fix Released Bug description: After upgrading a homelab 24.04 test machine from 6.6 to 6.8 kernel that was recently introduced, the test machine started flooding the terminal with following messages: [ 1877.712068] BUG: Bad page state in process swapper/0 pfn:58919 The process name varies and appears to be whatever is currently doing something. I installed a fresh up to date copy to see if this could be replicated elsewhere and the outcome is the same. Both of the machines are VMs running under Xen with XCP-ng, although unsure if it's related. The issue produces a notable amount of syslog entries. If left running, the system will eventually go into a state where processes get stuck and do not react to systemd control, even when there's no notable load, no memory pressure nor is the disk space low. Booted back to 6.6 kernel the issue no longer happens. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 11 00:31 seq crw-rw+ 1 root audio 116, 33 Mar 11 00:31 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Mon Mar 11 00:36:24 2024 InstallationDate: Installed on 2024-03-11 (0 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily amd64 (20240222) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 002: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Xen HVM domU PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 LC_CTYPE=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=97002c6c-ab61-49d5-b937-891e4e8da514 ro RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2024 dmi.bios.release: 4.13 dmi.bios.vendor: Xen dmi.bios.version: 4.13 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.13:bd01/31/2024:br4.13:svnXen:pnHVMdomU:pvr4.13:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.13 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056706/+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 2050019] Re: [24.04 FEAT] [SEC2353] zcrypt: extend error recovery to deal with device scans
This bug was fixed in the package linux - 6.8.0-31.31 --- linux (6.8.0-31.31) noble; urgency=medium * noble/linux: 6.8.0-31.31 -proposed tracker (LP: #2062933) * Packaging resync (LP: #1786013) - [Packaging] debian.master/dkms-versions -- update from kernel-versions (main/d2024.04.04) -- Andrea Righi Fri, 19 Apr 2024 23:46:38 +0200 ** Changed in: linux (Ubuntu) Status: In Progress => 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/2050019 Title: [24.04 FEAT] [SEC2353] zcrypt: extend error recovery to deal with device scans Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Bug description: The error recovery of a crypto request currently fails if a device is not available or the device is not completely setup and bound if the device has been discovered due to a bus scan. If, during request handling, a device is lost and a bus scan is triggered the DD must wait for the bus scan (including the device binding) to complete before giving up on reties. This item is important to support life guest relocation where the APQN sets on the source and target guests differ. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2050019/+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 2051835] Re: [24.04 FEAT] Memory hotplug vmem pages (s390x)
This bug was fixed in the package linux - 6.8.0-31.31 --- linux (6.8.0-31.31) noble; urgency=medium * noble/linux: 6.8.0-31.31 -proposed tracker (LP: #2062933) * Packaging resync (LP: #1786013) - [Packaging] debian.master/dkms-versions -- update from kernel-versions (main/d2024.04.04) -- Andrea Righi Fri, 19 Apr 2024 23:46:38 +0200 ** Changed in: linux (Ubuntu Noble) Status: In Progress => 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/2051835 Title: [24.04 FEAT] Memory hotplug vmem pages (s390x) Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: The current s390 specific memory hotplug backend allocates 'struct page' management structures for all standby memory regions, when those standby regions are detected at ipl time. The reason for this is, that setting standby online memory is supposed to succeed especially in memory constrained environments, since lack of free memory is likely the reason why additional memory is brought online. If in such cases 'struct pages' would have to be allocated before memory could be brought up, this would likely fail, and contradict the whole rationale of memory hotplug. However pre-allocating memory for 'struct pages' comes with the downside that for highly unbalanced ratios of online/standby memory a system might even fail to ipl, because there is not enough memory available for all possible struct pages which are required for standby memory. The idea is to improve the situation: when standby memory is brought online, the memory for struct pages (and maybe other management structures) required for this new memory area should be taken from the online memory, instead of pre-allocating them. This would solve the problems with unbalanced ratios as described above. Note: there are intentions to tell customers that they should always define the maximum size of standby memory for their LPAR activation profiles. This would allow for maximum flexibility for all LPARs during runtime, given that the amount of standby memory cannot be changed during runtime. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2051835/+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 2062951] Re: Random flickering with i915 on Linux 6.8
Update: I did some preliminary testing and it seems like adding "intel_idle.max_cstate=4" to cmdline resolves the issue but probably at the power efficiency cost. I also tried "i915.enable_psr=0" but it didn't help just made the flickering a slightly different. -- 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/2062951 Title: Random flickering with i915 on Linux 6.8 Status in linux package in Ubuntu: New Bug description: After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random. It happens after a moderate to heavy on screen activity like window switching, scrolling etc. It never happens when playing video or when there is no interaction using keyboard/pointer. It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region. Around the same time the following appears in kernel log: kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Happens on both X11 and Wayland on both KDE plasma and Mate (though less). I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7. Kernels 6.6, 6.5, 6.1 and older did not have that issue. Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD Graphics 520] Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26 Attaching kernel log for 6.8.0-28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951/+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 2063060] [NEW] package linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4
Public bug reported: nvidia driver 390 dkms390 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Apr 21 23:45:13 2024 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 InstallationDate: Installed on 2024-04-02 (19 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216) 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.3 apt 2.4.12 SourcePackage: dkms Title: package linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2063060 Title: package linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 Status in dkms package in Ubuntu: New Bug description: nvidia driver 390 dkms390 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Apr 21 23:45:13 2024 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 InstallationDate: Installed on 2024-04-02 (19 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216) 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.3 apt 2.4.12 SourcePackage: dkms Title: package linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2063060/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
This bug was fixed in the package systemd - 255.4-1ubuntu8
---
systemd (255.4-1ubuntu8) noble; urgency=medium
* copy: ignore -EOPNOTSUPP from copy_file_range() (LP: #2058179)
File:
debian/patches/lp2058179-copy-ignore-EOPNOTSUPP-from-copy_file_range.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fc81bb680f5d5c8c5995fcf6ed7f55f739dcd6a7
-- Nick Rosbrook Fri, 19 Apr 2024 10:24:36 -0400
** Changed in: systemd (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in zfs-linux package in Ubuntu:
Fix Released
Status in systemd source package in Noble:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2062951] Re: Random flickering with i915 on Linux 6.8
** Tags added: kernel-bug regression-release -- 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/2062951 Title: Random flickering with i915 on Linux 6.8 Status in linux package in Ubuntu: New Bug description: After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random. It happens after a moderate to heavy on screen activity like window switching, scrolling etc. It never happens when playing video or when there is no interaction using keyboard/pointer. It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region. Around the same time the following appears in kernel log: kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Happens on both X11 and Wayland on both KDE plasma and Mate (though less). I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7. Kernels 6.6, 6.5, 6.1 and older did not have that issue. Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD Graphics 520] Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26 Attaching kernel log for 6.8.0-28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951/+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 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
** No longer affects: linux-raspi (Ubuntu) ** No longer affects: linux-hwe-6.5 (Ubuntu) ** No longer affects: linux-azure (Ubuntu) ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Assignee: Jose Ogando Justo (joseogando) => (unassigned) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Matthew Ruffell (mruffell) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: In Progress Bug description: Remote filesystems mounted as CIFS are not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64). The remote filesystem is correctly mounted and seems to work but trying to write data to the filesystem ends in a kernel error exception. After that error the CIFS filesystem just became unusable. Previous Kernel version works correctly. = Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64) = # lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 # uname -a Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 6.5.0-27.28-generic 6.5.13 How to reproduce the problem For instance, I'm using KeePassXC (https://launchpad.net/ubuntu/+source/keepassxc) to update a database located at CIFS filesystem. Any change done to that database causes this Kernel error exception: abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: fffe abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0 abr 11 09:34:59 fpgmsi kernel: Oops: [#1] PREEMPT SMP NOPTI abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic #28-Ubuntu abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022 abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 abr 11 09:34:59 fpgmsi kernel: RAX: RBX: fffe RCX: abr 11 09:34:59 fpgmsi kernel: RDX: RSI: RDI: abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 R09: abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11: R12: abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70 abr 11 09:34:59 fpgmsi kernel: FS: 7bd4d594b6c0() GS:90753f80() knlGS: abr 11 09:34:59 fpgmsi kernel: CS: 0010 DS: ES: CR0: 80050033 abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 CR4: 00750ef0 abr 11 09:34:59 fpgmsi kernel: PKRU: 5554 abr 11 09:34:59 fpgmsi kernel: Call Trace: abr 11 09:34:59 fpgmsi kernel: abr 11 09:34:59 fpgmsi kernel: ? show_regs+0x6d/0x80 abr 11 09:34:59 fpgmsi kernel: ? __die+0x24/0x80 abr 11 09:34:59 fpgmsi kernel: ? page_fault_oops+0x99/0x1b0 abr 11 09:34:59 fpgmsi kernel: ? kernelmode_fixup_or_oops+0xb2/0x140 abr 11 09:34:59 fpgmsi kernel: ? __bad_area_nosemaphore+0x1a5/0x2c0 abr 11 09:34:59 fpgmsi kernel: ? bad_area_nosemaphore+0x16/0x30 abr 11 09:34:59 fpgmsi kernel: ? do_kern_addr_fault+0x7b/0xa0 abr 11 09:34:59 fpgmsi kernel: ? exc_page_fault+0x1a4/0x1b0 abr 11 09:34:59 fpgmsi kernel: ? asm_exc_page_fault+0x27/0x30 abr 11 09:34:59 fpgmsi kernel: ? cifs_flush_folio+0x41/0xf0 [cifs] abr 11 09:34:59 fpgmsi kernel:
[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Hi Axel, Sorry about you getting spammed about all these verifications. The robot that posts these messages looks for the Launchpad bug number in the package changelogs, and just makes a post for every package it sees it in. You might not know, but Ubuntu has slightly over 100 kernels these days, across all series releases. These are split in the primary kernels, like -generic, and then all the derivatives like -aws, -azure, -gcp, -fips, -virtual, and so on, and then including the HWE kernels and their derivatives too. This got fixed in all the 5.15 kernels, so the robot goes crazy and spams those "please verify" comments for all the derivatives. We usually just verify the -generic kernel only, unless it has greater impact to one of those derivatives. There's no further action needed on your part. The fix won't be removed for not verifying a derivative you have never heard of. Hope that clears it up a bit. Thanks, Matthew -- 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/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2060914] Re: kernel NULL pointer dereference in ipu6 driver
** Tags added: oem-priority -- 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/2060914 Title: kernel NULL pointer dereference in ipu6 driver Status in OEM Priority Project: New Status in linux package in Ubuntu: New Bug description: pr 11 14:43:43 OCBYM2-DVT1-C3 kernel: BUG: kernel NULL pointer dereference, address: Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: #PF: supervisor read access in kernel mode Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: #PF: error_code(0x) - not-present page Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: PGD 0 P4D 0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Oops: [#1] PREEMPT SMP NOPTI Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CPU: 16 PID: 568 Comm: (udev-worker) Tainted: G O 6.8.0-22-generic #22-Ubuntu Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Hardware name: Dell Inc. Precision 5490/, BIOS 1.1.0 02/07/2024 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RIP: 0010:__wake_up_common+0x2f/0xb0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Code: 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 89 fb 48 83 c3 08 48 83 ec 08 48 8b 47 08 89 75 d4 89 55 d0 48 39 c3 74 51 4d 89 c7 <4c> 8b 00 41 89 ce 48 8d 78 e8 4d 8d 68 e8 eb 25 74 0c 41 83 e4 01 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RSP: 0018:b5ebc3063768 EFLAGS: 00010086 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RAX: RBX: 8fb79e181d50 RCX: Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RDX: RSI: 0003 RDI: 8fb79e181d48 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RBP: b5ebc3063798 R08: R09: Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: R10: R11: R12: 8fb79e181d48 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: R13: 0003 R14: 0246 R15: Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: FS: 77cceb6148c0() GS:8fc6cf60() knlGS: Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CR2: CR3: 0001068ae003 CR4: 00f70ef0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: DR0: DR1: DR2: Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: DR3: DR6: 07f0 DR7: 0400 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: PKRU: 5554 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Call Trace: Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? show_regs+0x6d/0x80 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? __die+0x24/0x80 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? page_fault_oops+0x99/0x1b0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? do_user_addr_fault+0x2ee/0x6b0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? exc_page_fault+0x83/0x1b0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? asm_exc_page_fault+0x27/0x30 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? __wake_up_common+0x2f/0xb0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: __wake_up+0x37/0x70 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: __vb2_queue_cancel+0xcd/0x300 [videobuf2_common] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: vb2_core_queue_release+0x23/0x70 [videobuf2_common] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: vb2_queue_release+0xe/0x20 [videobuf2_v4l2] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ipu_isys_queue_cleanup+0x12/0x20 [intel_ipu6_isys] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ipu_isys_video_cleanup+0x2e/0x40 [intel_ipu6_isys] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ipu_isys_csi2_be_soc_cleanup+0x37/0x50 [intel_ipu6_isys] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: isys_unregister_subdevices+0x40/0xa0 [intel_ipu6_isys] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: isys_probe+0x5c5/0xb80 [intel_ipu6_isys] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? kernfs_create_link+0x66/0xe0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ipu_bus_probe+0x72/0x130 [intel_ipu6] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: really_probe+0x1c4/0x410 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: __driver_probe_device+0x8c/0x180 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: driver_probe_device+0x24/0xd0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: __driver_attach+0x10b/0x210 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? __pfx___driver_attach+0x10/0x10 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: bus_for_each_dev+0x8a/0xf0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: driver_attach+0x1e/0x30 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: bus_add_driver+0x156/0x260 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: driver_register+0x5e/0x130 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? __pfx_isys_driver_init+0x10/0x10 [intel_ipu6_isys] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ipu_bus_register_driver+0x16/0x20 [intel_ipu6] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: isys_driver_init+0x15/0xff0 [intel_ipu6_isys] Apr 11 14:43:43
[Kernel-packages] [Bug 1788044] Re: task kworker blocked for more than 120 seconds nouveau
I have found a fix. First I tried adding "nouveau.modeset=0" to bootflags, which got me to boot but no greeter. sddm appeared to be happily running but it failed to start the display server restarting it did not help "startx" worked, which gave me hope It appeared the session "seat" had been determined by systemd to have "CanGraphical" false Then I found this: https://github.com/mikhailnov/systemd/commit/c00bf275fdfbad3a9db8934b5e266b6abbdb8443 There's a heuristic hack which sets CanGraphical when the kernel starts w/o graphics, but only if this is done via "nomodeset" rather than the driver-specific ".modeset" flags So I just added "nomodeset" to boot flags, and now not only does 6.5.0-28 boot and land at a working greeter again, but all the weird sddm graphics bugs i'd been encountering since 6.5 are gone. Hope this helps someone else... And maybe this kernel issue will get fixed, some day -- 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/1788044 Title: task kworker blocked for more than 120 seconds nouveau Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: I was using chromium when the whole system GUI stopped responding at 15:42. This corresponds to the system journal at that point: Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: runlist 0: scheduled for recovery Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: channel 15: killed Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: engine 0: scheduled for recovery Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: compiz[7682]: channel 15 killed! Aug 20 15:45:50 dh3930 kernel: INFO: task kworker/u24:4:14623 blocked for more than 120 seconds. Aug 20 15:45:50 dh3930 kernel: Not tainted 4.15.0-32-generic #35-Ubuntu Aug 20 15:45:50 dh3930 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 20 15:45:50 dh3930 kernel: kworker/u24:4 D0 14623 2 0x8000 Aug 20 15:45:50 dh3930 kernel: Workqueue: events_unbound nv50_disp_atomic_commit_work [nouveau] Aug 20 15:45:50 dh3930 kernel: Call Trace: Aug 20 15:45:50 dh3930 kernel: __schedule+0x291/0x8a0 Aug 20 15:45:50 dh3930 kernel: schedule+0x2c/0x80 Aug 20 15:45:50 dh3930 kernel: schedule_timeout+0x1cf/0x350 Aug 20 15:45:50 dh3930 kernel: ? nvif_object_ioctl+0x47/0x50 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nouveau_bo_rd32+0x2a/0x30 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nv84_fence_read+0x2e/0x30 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nouveau_fence_no_signaling+0x2a/0x80 [nouveau] Aug 20 15:45:50 dh3930 kernel: dma_fence_default_wait+0x1c7/0x260 Aug 20 15:45:50 dh3930 kernel: ? dma_fence_release+0xa0/0xa0 Aug 20 15:45:50 dh3930 kernel: dma_fence_wait_timeout+0x3e/0xf0 Aug 20 15:45:50 dh3930 kernel: drm_atomic_helper_wait_for_fences+0x63/0xc0 [drm_kms_helper] Aug 20 15:45:50 dh3930 kernel: nv50_disp_atomic_commit_tail+0x55/0x3b10 [nouveau] Aug 20 15:45:50 dh3930 kernel: nv50_disp_atomic_commit_work+0x12/0x20 [nouveau] Aug 20 15:45:50 dh3930 kernel: process_one_work+0x1de/0x410 Aug 20 15:45:50 dh3930 kernel: worker_thread+0x32/0x410 Aug 20 15:45:50 dh3930 kernel: kthread+0x121/0x140 Aug 20 15:45:50 dh3930 kernel: ? process_one_work+0x410/0x410 Aug 20 15:45:50 dh3930 kernel: ? kthread_create_worker_on_cpu+0x70/0x70 Aug 20 15:45:50 dh3930 kernel: ret_from_fork+0x35/0x40 The 'blocked for more than 120 seconds' message and call trace repeated every ~121 seconds until I rebooted. At that point, the following additional line appeared with the 'blocked for more than 120 seconds' message: Aug 20 16:01:51 dh3930 kernel: nouveau :01:00.0: chromium- browse[14187]: failed to idle channel 20 [chromium-browse[14187]] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2460 F pulseaudio /dev/snd/controlC0: david 2460 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 20 16:07:40 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9e4f3d6a-f1b3-40c0-8c97-97d861a7ce11 InstallationDate: Installed on 2016-10-24 (664 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-32-generic root=UUID=311cc681-166d-47bd-847d-f41c81578c1a ro rootflags=subvol=@
[Kernel-packages] [Bug 2062135] Re: Add Cirrus Logic CS35L56 amplifier support
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => Chris Chiu (mschiu77) ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Chris Chiu (mschiu77) ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Chris Chiu (mschiu77) -- 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/2062135 Title: Add Cirrus Logic CS35L56 amplifier support Status in HWE Next: 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: In Progress Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: SRU Jusitification for Kernel [Impact] Add a driver for the Cirrus Logic CS35L56 amplifier. This is not a standalone HDA device; it provides control of the CS35L56 for systems that use a combination of an HDA codec and CS35L56 amplifiers with audio routed through the HDA codec. If it's not enabled on HDA codec with this amplifier, there will be no sound if play audio via built-in speaker. [Fix] Backport the CS35L56 driver from kernel 6.9-rc [Test Case] 1. Install the kernel w/ CS35L56 driver enabled 2. Install the linux-firmware with latest CS35l56 supported 3. Play audio file on machines w/ CS35L56 amplifier and make sure it's OK [Where problems could occur] Only affects models which have CS35L56 amplifier. Should be no risk to others. = SRU Jusitification for linux-firmware [Impact] No sound if no CS35L56 firmware even the driver is enabled in Linux kernel. [Fix] Add release FW binary of CS35L56 to linux-firmware [Test Case] 1. Install the kernel w/ CS35L56 driver enabled 2. Install the linux-firmware with latest CS35l56 supported 3. Play audio file on machines w/ CS35L56 amplifier and make sure it's OK [Where problems could occur] New firmware is only loaded by the CS35L56, we only need to verify it on the target platform. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2062135/+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
