[Kernel-packages] [Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided => High ** Also affects: nvidia-graphics-drivers-495 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-495 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-495 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-495 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1964037] Re: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session
** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Confirmed ** Also affects: nvidia-graphics-drivers-495 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-495 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-495 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1964037 Title: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-495 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: This is on my weird desktop setup, with one monitor plugged into an AMD card and one into an NVIDIA card. When using the Wayland session, by default Shell will come up on the monitor connected to the AMD card, and the second (NVIDIA) monitor will be blank. Attempting to enable the second monitor in Display Settings will immediately and reproducibly crash gnome-shell. This is trivial for me to reproduce, so if you need patches tested I can easily do so. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0+bcachefs.git2026.1fa97551d-1.1-generic 5.15.2 Uname: Linux 5.15.0+bcachefs.git2026.1fa97551d-1-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 09:37:51 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-11-02 (125 days ago) InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 41.3-3ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 meta_monitor_mode_foreach_crtc () at /lib/x86_64-linux-gnu/libmutter-9.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to jammy on 2021-11-02 (124 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1964037/+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 1953264] Re: Ubuntu 21.10 Bluetooth adapter not detected
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953264 Title: Ubuntu 21.10 Bluetooth adapter not detected Status in linux package in Ubuntu: Expired Bug description: Bluetooth adapter not detected on machine running Ubuntu 21.10 with ASUS ROG B550-F. Upon clicking taskbar, bluetooth is shown as OFF. Expanding the bluetooth menu in the taskbar shows the option to turn OFF bluetooth. Going into the bluetooth settings, it says "No bluetooth found. Plugin a dongle to use bluetooth." ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-21-generic 5.13.0-21.21 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nabeel 2239 F pulseaudio /dev/snd/pcmC1D1p: nabeel 2239 F...m pulseaudio /dev/snd/controlC0: nabeel 2239 F pulseaudio CasperMD5CheckResult: pass Date: Sun Dec 5 23:38:54 2021 InstallationDate: Installed on 2021-09-06 (90 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUS System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-21-generic root=/dev/mapper/vgubuntu-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-15 (51 days ago) dmi.bios.date: 08/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2423 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-F GAMING (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2423:bd08/10/2021:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-FGAMING(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953264/+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 1967609] Re: Nvidia 510 driver causes screen corruption in X for Ubuntu 22.04
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-510 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1967609 Title: Nvidia 510 driver causes screen corruption in X for Ubuntu 22.04 Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: I was having strange un smooth scrolling in videos and video games, and sections of the GUI like the taskbar would disappear for a second or two. I moved to the 470 driver, and all the problems went away. I simple wanted to give you the pertinent information. Hopefully I have done that. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 07:06:47 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.103.01, 5.15.0-23-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/470.103.01, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-23-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU116M [GeForce GTX 1660 Ti Mobile] [17aa:3a46] InstallationDate: Installed on 2022-03-31 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: LENOVO 82B1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=3909483b-c0cc-449e-ac4b-024d9e0b353f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2020 dmi.bios.release: 1.14 dmi.bios.vendor: LENOVO dmi.bios.version: FSCN14WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05H dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrFSCN14WW:bd08/26/2020:br1.14:efr1.14:svnLENOVO:pn82B1:pvrLenovoLegion515ARH05H:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05H:skuLENOVO_MT_82B1_BU_idea_FM_Legion515ARH05H: dmi.product.family: Legion 5 15ARH05H dmi.product.name: 82B1 dmi.product.sku: LENOVO_MT_82B1_BU_idea_FM_Legion 5 15ARH05H dmi.product.version: Lenovo Legion 5 15ARH05H dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 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/nvidia-graphics-drivers-510/+bug/1967609/+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 1967609] [NEW] Nvidia 510 driver causes screen corruption in X for Ubuntu 22.04
You have been subscribed to a public bug: I was having strange un smooth scrolling in videos and video games, and sections of the GUI like the taskbar would disappear for a second or two. I moved to the 470 driver, and all the problems went away. I simple wanted to give you the pertinent information. Hopefully I have done that. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 07:06:47 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.103.01, 5.15.0-23-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/470.103.01, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-23-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU116M [GeForce GTX 1660 Ti Mobile] [17aa:3a46] InstallationDate: Installed on 2022-03-31 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: LENOVO 82B1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=3909483b-c0cc-449e-ac4b-024d9e0b353f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2020 dmi.bios.release: 1.14 dmi.bios.vendor: LENOVO dmi.bios.version: FSCN14WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05H dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrFSCN14WW:bd08/26/2020:br1.14:efr1.14:svnLENOVO:pn82B1:pvrLenovoLegion515ARH05H:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05H:skuLENOVO_MT_82B1_BU_idea_FM_Legion515ARH05H: dmi.product.family: Legion 5 15ARH05H dmi.product.name: 82B1 dmi.product.sku: LENOVO_MT_82B1_BU_idea_FM_Legion 5 15ARH05H dmi.product.version: Lenovo Legion 5 15ARH05H dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption jammy package-from-proposed ubuntu -- Nvidia 510 driver causes screen corruption in X for Ubuntu 22.04 https://bugs.launchpad.net/bugs/1967609 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 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 1967707] [NEW] Nvidia Wayland sessions sometimes flood the log with [clutter_frame_clock_notify_presented: code should not be reached]
Public bug reported: Nvidia Wayland sessions sometimes flood the log with: [ 13.105877] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.106163] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.112490] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.125302] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.142242] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached I've been seeing the issue for months although it only seems to happen *after* something has gone wrong in mutter. Not by default. Then when the messages start, restarting gnome-shell won't fix it. You have to reboot the whole machine so it seems like something has latched in the nvidia-drm kernel driver. ** Affects: mutter (Ubuntu) Importance: Undecided Assignee: Daniel van Vugt (vanvugt) Status: New ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: jammy nvidia nvidia-wayland wayland-session ** Tags added: jammy nvidia nvidia-wayland wayland-session ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Description changed: Nvidia Wayland sessions sometimes flood the log with: [ 13.105877] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.106163] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.112490] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.125302] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.142242] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached I've been seeing the issue for months although it only seems to happen *after* something has gone wrong in mutter. Not by default. Then when the messages start, restarting gnome-shell won't fix it. You - have to reboot the whole machine. + have to reboot the whole machine so it seems like something has latched + in the nvidia-drm kernel driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1967707 Title: Nvidia Wayland sessions sometimes flood the log with [clutter_frame_clock_notify_presented: code should not be reached] Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Nvidia Wayland sessions sometimes flood the log with: [ 13.105877] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.106163] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.112490] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.125302] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.142242] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached I've been seeing the issue for months although it only seems to happen *after* something has gone wrong in mutter. Not by default. Then when the messages start, restarting gnome-shell won't fix it. You have to reboot the whole machine so it seems like something has latched in the nvidia-drm kernel driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967707/+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 1949075] Re: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 21.10
** Tags added: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1949075 Title: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 21.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: After moving to Impish, my bluetooth headset doesn't automatically connect when I power it on (it was working fine on hirsute). When I go to the bluetooth settings, select it and click connect, the first time it disconnects immediately and I see this line in bluetoothd log: Oct 28 13:57:11 arrakis bluetoothd[1106]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down After that, clicking the connect button again makes it work. I'm not sure where to find info to debug this furhter ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 13:57:34 2021 InstallationDate: Installed on 2021-10-16 (11 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20F6CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:01:19:D5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:56756 acl:285 sco:0 events:6453 errors:0 TX bytes:3721263 acl:3477 sco:0 commands:2751 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949075/+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 1967702] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1967702 Title: Accessibility features have been disabled, modules like speakup_soft and others are missing Status in linux package in Ubuntu: Confirmed Bug description: From very old versions of Kernel for Ubuntu until version 5.13, accessibility features were enabled, allowing blind users to use screen readers in text mode, such as "speakup" via "espeakup" package. In Kernels 5.15 packages for Ubuntu 22.04 beta, such as "linux-image-5.15.0-23-generic", accessibility features are disabled (no justification for such occurrence was listed in the file "changelog.Debian.gz"), with this the espeakup application doesn't work, it depends on the missing speakup_soft module. Missing in the file "/boot/config-5.15.0-23-generic" comparing with the file "/boot/config-5.13.0-39-generic", the line CONFIG_ACCESSIBILITY=y and the following lines are also missing: # # Speakup console speech # CONFIG_SPEAKUP=m CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m CONFIG_SPEAKUP_SYNTH_DECTLK=m CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m CONFIG_SPEAKUP_SYNTH_DUMMY=m # end of Speakup console speech ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tiago 1259 F pulseaudio /dev/snd/pcmC0D0p: tiago 1259 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Apr 3 22:05:39 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220330) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3583 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=9e0e837b-49f2-4e10-945a-f7460bcc8286 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0KD03P dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.0:bd12/06/2021:br1.17:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0KD03P:rvrA03:cvnDellInc.:ct10:cvr:sku08CA: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+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 1967702] [NEW] Accessibility features have been disabled, modules like speakup_soft and others are missing
Public bug reported: >From very old versions of Kernel for Ubuntu until version 5.13, accessibility >features were enabled, allowing blind users to use screen readers in text >mode, such as "speakup" via "espeakup" package. In Kernels 5.15 packages for Ubuntu 22.04 beta, such as "linux-image-5.15.0-23-generic", accessibility features are disabled (no justification for such occurrence was listed in the file "changelog.Debian.gz"), with this the espeakup application doesn't work, it depends on the missing speakup_soft module. Missing in the file "/boot/config-5.15.0-23-generic" comparing with the file "/boot/config-5.13.0-39-generic", the line CONFIG_ACCESSIBILITY=y and the following lines are also missing: # # Speakup console speech # CONFIG_SPEAKUP=m CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m CONFIG_SPEAKUP_SYNTH_DECTLK=m CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m CONFIG_SPEAKUP_SYNTH_DUMMY=m # end of Speakup console speech ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tiago 1259 F pulseaudio /dev/snd/pcmC0D0p: tiago 1259 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Apr 3 22:05:39 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220330) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3583 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=9e0e837b-49f2-4e10-945a-f7460bcc8286 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0KD03P dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.0:bd12/06/2021:br1.17:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0KD03P:rvrA03:cvnDellInc.:ct10:cvr:sku08CA: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy -- 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/1967702 Title: Accessibility features have been disabled, modules like speakup_soft and others are missing Status in linux package in Ubuntu: Confirmed Bug description: From very old versions of Kernel for Ubuntu until version 5.13, accessibility features were enabled, allowing blind users to use screen readers in text mode, such as "speakup" via "espeakup" package. In Kernels 5.15 packages for Ubuntu 22.04 beta, such as "linux-image-5.15.0-23-generic", accessibility features are disabled (no justification for such occurrence was listed in the file "changelog.Debian.gz"), with this the espeakup application doesn't work, it depends on the missing speakup_soft module. Missing in the file "/boot/config-5.15.0-23-generic" comparing with the file "/boot/config-5.13.0-39-generic", the line CONFIG_ACCESSIBILITY=y and the following lines are also missing: # # Speakup console speech # CONFIG_SPEAKUP=m CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m CONFIG_SPEAKUP_SYNTH_DECTLK=m CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m CONFIG_SPEAKUP_SYNTH_DUMMY=m # end of Speakup console speech ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tiago
[Kernel-packages] [Bug 1939638] Re: [regression] USB device is not detected during boot
Hello Dries and Tilman,
Thank you for providing the logs and other relevant information. For
clarification, when you were testing if the issue still exists, was this
from cold boot or warm boot?
And if you sometimes see it working from cold boot it indeed seems to be very
racey. There now should be a 100ms power-on-to-good delay on all usb 3.0 hubs
since 5.4.0-97, which seems like it used to delay whatever race seems to be
going on when the roothubs are being registered (as per the discussion here
https://bugzilla.kernel.org/show_bug.cgi?id=214021), but maybe that isn't
enough to avoid the race in your case?
p.s. If you run lsusb -v as root you should be able to see the bPwrOn2PwrGood
value of the root hubs as 100ms.
Also, the patchset that seemed to directly address this issue got
reverted due to regressions and never seemed to be re-addressed
upstream... there seem to be a lot of fixes for those introduced
problems since then though so maybe it would make sense to reintroduce
those patches.
I will send an email to the upstream usb mailing list asking about this
and see what their thoughts are.
Thanks,
- Luke
** Bug watch added: Linux Kernel Bug Tracker #214021
https://bugzilla.kernel.org/show_bug.cgi?id=214021
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939638
Title:
[regression] USB device is not detected during boot
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-intel package in Ubuntu:
Confirmed
Status in linux-intel-5.13 package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux-intel source package in Focal:
Confirmed
Status in linux-intel-5.13 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in linux-intel source package in Hirsute:
Invalid
Status in linux-intel-5.13 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
The USB devices (keyboard, storage...) are failed to be detected when
connecting to the problematic root hubs which need longer PowerOn-to-PowerGood
delay than it claims in the hub descriptor. It's caused by the upstream fix
90d28fb53d4a ("usb: core: reduce power-on-good delay time of root hub").
[Fix]
Reverting the upstream fix until a formal fix been placed.
[Test Case]
1. Plug the USB device to the ports of problematic root hub.
2. Power on the machine.
3. Check if the USB device can work or not after boot.
[Regression Potential]
Low. The longer delay is proven safe in old kernels.
== Original Bug Description ==
[Summary]
The USB devices (keyboard, storage...) are failed to be detected during boot
after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However,
they will be detected and working ok after re-plugging. The kernel output shows
as down below during boot
[ 39.350435] hub 1-0:1.0: USB hub found
[ 39.398835] hub 1-0:1.0: 12 ports detected
[ 39.622744] usb usb1-port3: couldn't allocate usb_device
And when I plug out then plug in the same device, it shows
[57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd
[57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099,
bcdDevice= 1.14
[57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
After doing kernel bisecting, we found the upstream commit
https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2
makes the difference. It indicates that the delay for the root hub from
power_on to power_good is not long enough. There was no problem if the delay is
100 ms. From the Hub Descriptor of the root hub, the value is 10 * 2
milliseconds. And the XHCI spec also says in section 5.4.8
"""
The host is required to have power stable to the port within 20 milliseconds
of the '0' to '1' transition of PP. If PPC = '1', software is responsible for
waiting 20ms.
"""
The commit seems to follow the SPEC but could cause problems on some
hubs.
[Reproduce Steps]
1. Plug the USB device to the physical port #1 and #4 which belongs to
high-speed hub.
2. Power on the machine.
3. Check if the USB device can work or not after boot.
[Results]
Expected:
All usb devices connect to the hub should work OK.
Actual:
USB devices connects to high-speed hub can not be probed.
[Additional Information]
Kernel Version: focal 5.4.0-78 and hirsute 5.11.0-26
[Upstream bug]
https://bugzilla.kernel.org/show_bug.cgi?id=214021
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1939638/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help :
[Kernel-packages] [Bug 1944094] Re: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD
This issue is FIXED with Linux kernel 5.16.0 (tested with liquorix kernel). Details: https://gitlab.freedesktop.org/drm/amd/-/issues/1671 -- 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/1944094 Title: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Bug description: The screen brightness controls don't work on the Legion Slim 7 (AMD) laptop running in hybrid/dynamic mode. The backlight control files appear in /sys/class/backlight/amdgpu_bl0, and writing to /sys/class/backlight/amdgpu_bl0/brightness changes the value in /sys/class/backlight/amdgpu_bl0/actual_brightness, but the screen brightness always remains at 100%. I have tried kernel boot parameters: acpi_backlight=vendor amdgpu.backlight=0 but neither makes any difference. I have read that users with the Legion 7 AMD and Legion 5 Pro AMD can get the backlight working with the amdgpu.backlight=0 kernel boot parameter. One difference between them and this laptop is that it has advanced optimus, meaning that it can switch the laptop display between the amdgpu and nvidia card without rebooting, if that is at all relevant. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1978 F pulseaudio /dev/snd/controlC1: rocko 1978 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 20 09:20:33 2021 InstallationDate: Installed on 2021-09-15 (5 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 82K8 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.13.0-16-generic root=UUID=99f436de-d37c-4b3e-adb2-612443efc197 ro rootflags=subvol=@ quiet splash amdgpu.backlight=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1001) is not owned by us (uid 0), but by uid 1001! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.200 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: HACN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion S7 15ACH6 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLegionS715ACH6: dmi.product.family: Legion S7 15ACH6 dmi.product.name: 82K8 dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6 dmi.product.version: Legion S7 15ACH6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944094/+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 1967613] Re: Gnome session reset after docking station disconnects
Another case: [Sun Apr 3 22:13:48 2022] lenovo 0005:17EF:6048.0007: input,hidraw6: BLUETOOTH HID v3.12 Keyboard [ThinkPad Compact Bluetooth Keyboard with TrackPoint] on c8:e2:65:2f:b3:9e [Sun Apr 3 22:21:02 2022] wlp3s0: deauthenticating from 60:3d:26:8c:93:af by local choice (Reason: 3=DEAUTH_LEAVING) [Sun Apr 3 22:21:02 2022] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb 93955633 port 1: DPCD read on addr 0x60 for 1 bytes NAKed [Sun Apr 3 22:21:03 2022] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb 93955633 port 1: DPCD read on addr 0x60 for 1 bytes NAKed [Sun Apr 3 22:21:03 2022] PM: suspend entry (deep) [Sun Apr 3 22:21:03 2022] Filesystems sync: 0.006 seconds [Sun Apr 3 22:21:03 2022] Freezing user space processes ... (elapsed 0.276 seconds) done. [Sun Apr 3 22:21:03 2022] OOM killer disabled. [Sun Apr 3 22:21:03 2022] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [Sun Apr 3 22:21:03 2022] printk: Suspending console(s) (use no_console_suspend to debug) [Sun Apr 3 22:21:04 2022] [drm] free PSP TMR buffer [Sun Apr 3 22:21:04 2022] amdgpu :05:00.0: amdgpu: MODE2 reset [Sun Apr 3 22:21:04 2022] ACPI: EC: interrupt blocked [Sun Apr 3 22:21:04 2022] ACPI: Preparing to enter system sleep state S3 [Sun Apr 3 22:21:04 2022] ACPI: EC: event blocked [Sun Apr 3 22:21:04 2022] ACPI: EC: EC stopped [Sun Apr 3 22:21:04 2022] PM: Saving platform NVS memory [Sun Apr 3 22:21:04 2022] Disabling non-boot CPUs ... [Sun Apr 3 22:21:04 2022] IRQ 28: no longer affine to CPU1 [Sun Apr 3 22:21:04 2022] IRQ 41: no longer affine to CPU1 [Sun Apr 3 22:21:04 2022] IRQ 50: no longer affine to CPU1 [Sun Apr 3 22:21:04 2022] IRQ 91: no longer affine to CPU1 [Sun Apr 3 22:21:04 2022] IRQ 95: no longer affine to CPU1 [Sun Apr 3 22:21:04 2022] smpboot: CPU 1 is now offline [Sun Apr 3 22:21:04 2022] IRQ 27: no longer affine to CPU2 [Sun Apr 3 22:21:04 2022] IRQ 39: no longer affine to CPU2 [Sun Apr 3 22:21:04 2022] IRQ 48: no longer affine to CPU2 [Sun Apr 3 22:21:04 2022] IRQ 90: no longer affine to CPU2 [Sun Apr 3 22:21:04 2022] smpboot: CPU 2 is now offline [Sun Apr 3 22:21:04 2022] IRQ 26: no longer affine to CPU3 [Sun Apr 3 22:21:04 2022] smpboot: CPU 3 is now offline [Sun Apr 3 22:21:04 2022] smpboot: CPU 4 is now offline [Sun Apr 3 22:21:04 2022] smpboot: CPU 5 is now offline [Sun Apr 3 22:21:04 2022] ACPI: Low-level resume complete [Sun Apr 3 22:21:04 2022] ACPI: EC: EC started [Sun Apr 3 22:21:04 2022] PM: Restoring platform NVS memory [Sun Apr 3 22:21:04 2022] LVT offset 0 assigned for vector 0x400 [Sun Apr 3 22:21:04 2022] Enabling non-boot CPUs ... [Sun Apr 3 22:21:04 2022] x86: Booting SMP configuration: [Sun Apr 3 22:21:04 2022] smpboot: Booting Node 0 Processor 1 APIC 0x1 [Sun Apr 3 22:21:04 2022] microcode: CPU1: patch_level=0x08600103 [Sun Apr 3 22:21:04 2022] ACPI: \_SB_.PLTF.C001: Found 3 idle states [Sun Apr 3 22:21:04 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 22:21:04 2022] CPU1 is up [Sun Apr 3 22:21:04 2022] smpboot: Booting Node 0 Processor 2 APIC 0x2 [Sun Apr 3 22:21:04 2022] microcode: CPU2: patch_level=0x08600103 [Sun Apr 3 22:21:04 2022] ACPI: \_SB_.PLTF.C002: Found 3 idle states [Sun Apr 3 22:21:04 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 22:21:04 2022] CPU2 is up [Sun Apr 3 22:21:04 2022] smpboot: Booting Node 0 Processor 3 APIC 0x4 [Sun Apr 3 22:21:04 2022] microcode: CPU3: patch_level=0x08600103 [Sun Apr 3 22:21:04 2022] ACPI: \_SB_.PLTF.C003: Found 3 idle states [Sun Apr 3 22:21:04 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 22:21:04 2022] CPU3 is up [Sun Apr 3 22:21:04 2022] smpboot: Booting Node 0 Processor 4 APIC 0x5 [Sun Apr 3 22:21:04 2022] microcode: CPU4: patch_level=0x08600103 [Sun Apr 3 22:21:04 2022] ACPI: \_SB_.PLTF.C004: Found 3 idle states [Sun Apr 3 22:21:04 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 22:21:04 2022] CPU4 is up [Sun Apr 3 22:21:04 2022] smpboot: Booting Node 0 Processor 5 APIC 0x6 [Sun Apr 3 22:21:04 2022] microcode: CPU5: patch_level=0x08600103 [Sun Apr 3 22:21:04 2022] ACPI: \_SB_.PLTF.C005: Found 3 idle states [Sun Apr 3 22:21:04 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 22:21:04 2022] CPU5 is up [Sun Apr 3 22:21:04 2022] ACPI: Waking up from system sleep state S3 [Sun Apr 3 22:21:04 2022] ACPI: EC: interrupt unblocked [Sun Apr 3 22:21:04 2022] ACPI: EC: event unblocked [Sun Apr 3 22:21:04 2022] [drm] PCIE GART of 1024M enabled. [Sun Apr 3 22:21:04 2022] [drm] PTB located at 0x00F40090 [Sun Apr 3 22:21:04 2022] [drm] PSP is resuming... [Sun Apr 3 22:21:04 2022] pci :00:00.2: can't derive routing for PCI INT A [Sun Apr 3 22:21:04 2022] pci :00:00.2: PCI INT A: no GSI [Sun Apr 3 22:21:04 2022] [drm] reserve 0x40 from
[Kernel-packages] [Bug 1964695] Re: Pseudo-Terminals are broken, please backport fix from upstream
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1964695 Title: Pseudo-Terminals are broken, please backport fix from upstream Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Pseudo Terminals misbehave with lines that have exactly 65 characters *including* the terminating newline. This bug has existed since Kernel 5.12, see https://bugzilla.kernel.org/show_bug.cgi?id=215611 for details. It has recently been fixed, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3593030761630e09200072a4bd06468892c27be3 This fix has also been backported into official branches of older (LTS) kernel versions (5.10, 5.15, 5.16), see e.g. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.16.14=ee421a75a740d6d8579fb1426141312313287de2 Please backport it to the Ubuntu branch of 5.13 so the fix gets into 20.04LTS and I can finally use gdb in Eclipse CDT again ;) Cheers, Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964695/+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 1903920] Re: Warning message about cryptsetup during boot
The correct way to disable the warning seems to be to add RESUME=none to /etc/initramfs-tools/conf.d/resume if your swap has a /dev/urandom key. -- 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/1903920 Title: Warning message about cryptsetup during boot Status in linux package in Ubuntu: Confirmed Bug description: I have noticed that since upgrade to 20.04.1 (from 18.04), a warning message appears during boot: "cryptsetup: WARNING: Option 'size' missing in crypttab for plain dm-crypt mapping cryptswap1. Please read /usr/share/doc/cryptsetup-initramfs/README.initramfs.gz and add the correct 'size' option to your crypttab(5).". AFAICT, there is no problem however. I use ecryptfs to encrypt my home directory but I don't think it's related (since the message is related to swap). This message used to appear during updates under 18.04 but I never paid attention to it. I probably use the same setup since 16.04. Others have reported the problem (https://askubuntu.com/questions/1109463, https://medium.com/@anirudha/fixing-cryptsetup-wating-for-encrypted- source-device-swapfile-error-on-linux-boot-ubuntu-20-04-5483e0dcf9e9). From what I read: - The answers indicate to edit /etc/crypttab and add a value for size but I don't know what value to use. - It seems that before 20.04, just editing /etc/crypttab was enough but some users say that they need to manually regenerate the initramfs image after each update which is boring. I have asked the question at https://answers.launchpad.net/ubuntu/+question/693615 and @bernard010 suggested to open a bug report. I have found anything worth in dmesg though. As I said everything seems fine (boot proceeds normally, I can use the computer) but I expect that there is a way to permanently make this warning disappear. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2322 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 23:02:47 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-06 (1405 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 2570p ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=74d77edf-b4b7-4815-865f-b7602f3396b4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-53-generic N/A linux-backports-modules-5.4.0-53-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-10-04 (38 days ago) dmi.bios.date: 02/01/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ISB Ver. F.40 dmi.board.name: 17DF dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 61.21 dmi.chassis.asset.tag: CNU3229ST9 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ISBVer.F.40:bd02/01/2013:svnHewlett-Packard:pnHPEliteBook2570p:pvrA1029C1102:rvnHewlett-Packard:rn17DF:rvrKBCVersion61.21:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 2570p dmi.product.sku: C9S65EC#ABF dmi.product.version: A1029C1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903920/+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 1961581] Re: 'Synaptics touchpad' not detected as an input device on 'Fujitsu LIFEBOOK U7411'
@aletschius For me, running: “sudo modprobe i2c-hid-acpi” on the terminal worked. To avoid running this after every log-in, just add: “i2c-hid-acpi” in a new line to: “/etc/modules” -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1961581 Title: 'Synaptics touchpad' not detected as an input device on 'Fujitsu LIFEBOOK U7411' Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Touchpad used to work fine initially but I recently realised that it's not responding at all, since I'm mostly working with an external mouse. Therefore, I'm not sure when this problem started or what really caused it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 21 12:13:55 2022 InstallationDate: Installed on 2021-11-02 (111 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 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-5.13/+bug/1961581/+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 1964695] Re: Pseudo-Terminals are broken, please backport fix from upstream
** Attachment added: "simple testcase to reproduce the bug" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964695/+attachment/5576558/+files/ptytest_simple.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1964695 Title: Pseudo-Terminals are broken, please backport fix from upstream Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Pseudo Terminals misbehave with lines that have exactly 65 characters *including* the terminating newline. This bug has existed since Kernel 5.12, see https://bugzilla.kernel.org/show_bug.cgi?id=215611 for details. It has recently been fixed, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3593030761630e09200072a4bd06468892c27be3 This fix has also been backported into official branches of older (LTS) kernel versions (5.10, 5.15, 5.16), see e.g. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.16.14=ee421a75a740d6d8579fb1426141312313287de2 Please backport it to the Ubuntu branch of 5.13 so the fix gets into 20.04LTS and I can finally use gdb in Eclipse CDT again ;) Cheers, Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964695/+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 1964695] Re: Pseudo-Terminals are broken, please backport fix from upstream
Added testcase and patch ** Patch added: "patch from upstream that fixes the bug" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964695/+attachment/5576559/+files/fix_tty_64char_lines.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1964695 Title: Pseudo-Terminals are broken, please backport fix from upstream Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Pseudo Terminals misbehave with lines that have exactly 65 characters *including* the terminating newline. This bug has existed since Kernel 5.12, see https://bugzilla.kernel.org/show_bug.cgi?id=215611 for details. It has recently been fixed, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3593030761630e09200072a4bd06468892c27be3 This fix has also been backported into official branches of older (LTS) kernel versions (5.10, 5.15, 5.16), see e.g. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.16.14=ee421a75a740d6d8579fb1426141312313287de2 Please backport it to the Ubuntu branch of 5.13 so the fix gets into 20.04LTS and I can finally use gdb in Eclipse CDT again ;) Cheers, Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964695/+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 1949075] Re: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 21.10
This still happens on a clean 22.04 install (with 5.15.0-23-generic). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1949075 Title: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 21.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: After moving to Impish, my bluetooth headset doesn't automatically connect when I power it on (it was working fine on hirsute). When I go to the bluetooth settings, select it and click connect, the first time it disconnects immediately and I see this line in bluetoothd log: Oct 28 13:57:11 arrakis bluetoothd[1106]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down After that, clicking the connect button again makes it work. I'm not sure where to find info to debug this furhter ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 13:57:34 2021 InstallationDate: Installed on 2021-10-16 (11 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20F6CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:01:19:D5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:56756 acl:285 sco:0 events:6453 errors:0 TX bytes:3721263 acl:3477 sco:0 commands:2751 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949075/+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 1967613] Re: Gnome session reset after docking station disconnects
Another case, this time the same machine but another system: Pop OS! System: Pop Os! 21.10, GNOME 40.4.0, X11 Kernel: 5.16.15-76051615-generic Logs: [Sun Apr 3 19:14:50 2022] PM: suspend entry (deep) [Sun Apr 3 19:14:50 2022] Filesystems sync: 0.007 seconds [Sun Apr 3 19:14:52 2022] Bluetooth: hci0: Timed out waiting for suspend events [Sun Apr 3 19:14:52 2022] Bluetooth: hci0: Suspend timeout bit: 9 [Sun Apr 3 19:14:52 2022] Bluetooth: hci0: Suspend notifier action (3) failed: -110 [Sun Apr 3 19:14:52 2022] Freezing user space processes ... (elapsed 0.003 seconds) done. [Sun Apr 3 19:14:52 2022] OOM killer disabled. [Sun Apr 3 19:14:52 2022] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [Sun Apr 3 19:14:52 2022] printk: Suspending console(s) (use no_console_suspend to debug) [Sun Apr 3 19:14:52 2022] [drm] free PSP TMR buffer [Sun Apr 3 19:14:52 2022] amdgpu :05:00.0: amdgpu: MODE2 reset [Sun Apr 3 19:14:52 2022] ACPI: EC: interrupt blocked [Sun Apr 3 19:14:52 2022] ACPI: PM: Preparing to enter system sleep state S3 [Sun Apr 3 19:14:52 2022] ACPI: EC: event blocked [Sun Apr 3 19:14:52 2022] ACPI: EC: EC stopped [Sun Apr 3 19:14:52 2022] ACPI: PM: Saving platform NVS memory [Sun Apr 3 19:14:52 2022] Disabling non-boot CPUs ... [Sun Apr 3 19:14:52 2022] smpboot: CPU 1 is now offline [Sun Apr 3 19:14:52 2022] smpboot: CPU 2 is now offline [Sun Apr 3 19:14:52 2022] smpboot: CPU 3 is now offline [Sun Apr 3 19:14:52 2022] smpboot: CPU 4 is now offline [Sun Apr 3 19:14:52 2022] smpboot: CPU 5 is now offline [Sun Apr 3 19:14:52 2022] ACPI: PM: Low-level resume complete [Sun Apr 3 19:14:52 2022] ACPI: EC: EC started [Sun Apr 3 19:14:52 2022] ACPI: PM: Restoring platform NVS memory [Sun Apr 3 19:14:52 2022] LVT offset 0 assigned for vector 0x400 [Sun Apr 3 19:14:52 2022] Enabling non-boot CPUs ... [Sun Apr 3 19:14:52 2022] x86: Booting SMP configuration: [Sun Apr 3 19:14:52 2022] smpboot: Booting Node 0 Processor 1 APIC 0x1 [Sun Apr 3 19:14:52 2022] microcode: CPU1: patch_level=0x08600103 [Sun Apr 3 19:14:52 2022] ACPI: \_SB_.PLTF.C001: Found 3 idle states [Sun Apr 3 19:14:52 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 19:14:52 2022] CPU1 is up [Sun Apr 3 19:14:52 2022] smpboot: Booting Node 0 Processor 2 APIC 0x2 [Sun Apr 3 19:14:52 2022] microcode: CPU2: patch_level=0x08600103 [Sun Apr 3 19:14:52 2022] ACPI: \_SB_.PLTF.C002: Found 3 idle states [Sun Apr 3 19:14:52 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 19:14:52 2022] CPU2 is up [Sun Apr 3 19:14:52 2022] smpboot: Booting Node 0 Processor 3 APIC 0x4 [Sun Apr 3 19:14:52 2022] microcode: CPU3: patch_level=0x08600103 [Sun Apr 3 19:14:52 2022] ACPI: \_SB_.PLTF.C003: Found 3 idle states [Sun Apr 3 19:14:52 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 19:14:52 2022] CPU3 is up [Sun Apr 3 19:14:52 2022] smpboot: Booting Node 0 Processor 4 APIC 0x5 [Sun Apr 3 19:14:52 2022] microcode: CPU4: patch_level=0x08600103 [Sun Apr 3 19:14:52 2022] ACPI: \_SB_.PLTF.C004: Found 3 idle states [Sun Apr 3 19:14:52 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 19:14:52 2022] CPU4 is up [Sun Apr 3 19:14:52 2022] smpboot: Booting Node 0 Processor 5 APIC 0x6 [Sun Apr 3 19:14:52 2022] microcode: CPU5: patch_level=0x08600103 [Sun Apr 3 19:14:52 2022] ACPI: \_SB_.PLTF.C005: Found 3 idle states [Sun Apr 3 19:14:52 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 19:14:52 2022] CPU5 is up [Sun Apr 3 19:14:52 2022] ACPI: PM: Waking up from system sleep state S3 [Sun Apr 3 19:14:52 2022] ACPI: EC: interrupt unblocked [Sun Apr 3 19:14:52 2022] ACPI: EC: event unblocked [Sun Apr 3 19:14:52 2022] [drm] PCIE GART of 1024M enabled. [Sun Apr 3 19:14:52 2022] [drm] PTB located at 0x00F40090 [Sun Apr 3 19:14:52 2022] [drm] PSP is resuming... [Sun Apr 3 19:14:52 2022] pci :00:00.2: can't derive routing for PCI INT A [Sun Apr 3 19:14:52 2022] pci :00:00.2: PCI INT A: no GSI [Sun Apr 3 19:14:52 2022] nvme :04:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000d address=0xffb0f000 flags=0x] [Sun Apr 3 19:14:52 2022] nvme nvme0: 16/0/0 default/read/poll queues [Sun Apr 3 19:14:52 2022] nvme nvme1: 15/0/0 default/read/poll queues [Sun Apr 3 19:14:52 2022] [drm] reserve 0x40 from 0xf41f80 for PSP TMR [Sun Apr 3 19:14:52 2022] amdgpu :05:00.0: amdgpu: RAS: optional ras ta ucode is not available [Sun Apr 3 19:14:53 2022] amdgpu :05:00.0: amdgpu: RAP: optional rap ta ucode is not available [Sun Apr 3 19:14:53 2022] amdgpu :05:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [Sun Apr 3 19:14:53 2022] amdgpu :05:00.0: amdgpu: SMU is resuming... [Sun Apr 3 19:14:53 2022] amdgpu :05:00.0: amdgpu: dpm has been disabled [Sun Apr 3 19:14:53 2022] amdgpu :05:00.0:
[Kernel-packages] [Bug 1967613] Re: Gnome session reset after docking station disconnects
Another, fresh case log: [Sun Apr 3 17:54:39 2022] rfkill: input handler disabled [Sun Apr 3 17:55:10 2022] usb 1-1: new high-speed USB device number 14 using xhci_hcd [Sun Apr 3 17:55:10 2022] usb 1-1: New USB device found, idVendor=17ef, idProduct=a392, bcdDevice= d.24 [Sun Apr 3 17:55:10 2022] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [Sun Apr 3 17:55:10 2022] usb 1-1: Product: USB2.0 Hub [Sun Apr 3 17:55:10 2022] usb 1-1: Manufacturer: VIA Labs, Inc. [Sun Apr 3 17:55:11 2022] hub 1-1:1.0: USB hub found [Sun Apr 3 17:55:11 2022] hub 1-1:1.0: 4 ports detected [Sun Apr 3 17:55:12 2022] [drm] DP Alt mode state on HPD: 1 [Sun Apr 3 17:55:12 2022] [drm] DM_MST: starting TM on aconnector: 0a0777cb [id: 89] [Sun Apr 3 17:55:12 2022] usb 1-1.2: new high-speed USB device number 15 using xhci_hcd [Sun Apr 3 17:55:12 2022] usb 1-1.2: New USB device found, idVendor=0bda, idProduct=5411, bcdDevice= 1.04 [Sun Apr 3 17:55:12 2022] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [Sun Apr 3 17:55:12 2022] usb 1-1.2: Product: 4-Port USB 2.0 Hub [Sun Apr 3 17:55:12 2022] usb 1-1.2: Manufacturer: Generic [Sun Apr 3 17:55:12 2022] hub 1-1.2:1.0: USB hub found [Sun Apr 3 17:55:12 2022] hub 1-1.2:1.0: 4 ports detected [Sun Apr 3 17:55:12 2022] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ad36f11b port 1: DPCD read on addr 0x60 for 1 bytes NAKed [Sun Apr 3 17:55:12 2022] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ad36f11b port 1: DPCD read on addr 0x60 for 1 bytes NAKed [Sun Apr 3 17:55:12 2022] usb 1-1.3: new high-speed USB device number 16 using xhci_hcd [Sun Apr 3 17:55:12 2022] usb 1-1.3: New USB device found, idVendor=17ef, idProduct=a394, bcdDevice= d.23 [Sun Apr 3 17:55:12 2022] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [Sun Apr 3 17:55:12 2022] usb 1-1.3: Product: USB2.0 Hub [Sun Apr 3 17:55:12 2022] usb 1-1.3: Manufacturer: VIA Labs, Inc. [Sun Apr 3 17:55:12 2022] hub 1-1.3:1.0: USB hub found [Sun Apr 3 17:55:12 2022] hub 1-1.3:1.0: 4 ports detected [Sun Apr 3 17:55:12 2022] usb 2-1: new SuperSpeed USB device number 9 using xhci_hcd [Sun Apr 3 17:55:12 2022] usb 2-1: New USB device found, idVendor=17ef, idProduct=a391, bcdDevice= d.24 [Sun Apr 3 17:55:12 2022] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [Sun Apr 3 17:55:12 2022] usb 2-1: Product: USB3.1 Hub [Sun Apr 3 17:55:12 2022] usb 2-1: Manufacturer: VIA Labs, Inc. [Sun Apr 3 17:55:13 2022] hub 2-1:1.0: USB hub found [Sun Apr 3 17:55:13 2022] hub 2-1:1.0: 4 ports detected [Sun Apr 3 17:55:13 2022] usb 1-1.2.2: new full-speed USB device number 17 using xhci_hcd [Sun Apr 3 17:55:13 2022] usb 1-1.2.2: New USB device found, idVendor=25a7, idProduct=fa70, bcdDevice= 2.01 [Sun Apr 3 17:55:13 2022] usb 1-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [Sun Apr 3 17:55:13 2022] usb 1-1.2.2: Product: 2.4G Wireless Receiver [Sun Apr 3 17:55:13 2022] usb 1-1.2.2: Manufacturer: Compx ** Description changed: From time to time, GNOME session gets reset when usb-c cable from docking station gets disconnected. All applications gets closed and completely new, fresh GNOME session is created. This is not happening every single time, when the cable gets disconnected but in about 1/3 of cases. As I remember it's happening only when laptop is suspended or have screen locked. When the laptop is working, and screen isn't locked, it's not happening (I could be wrong but this is my observation). The bug is highly unpleasant because it's closing every single app on the computer, and every single process running in the current session. I'm almost sure it was happening for several last kernels, this is not a new issue, I had this problem for a long time (at least for 6 months). Attachment (20211018_210936.jpg) is related to it, it's the info I see on the screen when the bug occurs. - Short info: - Laptop: Thinkpad E14 Gen2 AMD, Ryzen 5 4500u, + Laptop: Thinkpad E14 Gen2 AMD, Ryzen 5 4500u, Sysytem: Ubuntu 21.10, GNOME 40.4.0, X11, kernel 5.13.0-39-generic, Docking station: Thinkpad USB-C Dock Gen2, 40AS, 20/06, 0090EU Logs: - -- CASE 1 --- + --- CASE 1 --- [Wed Mar 16 17:41:58 2022] sda: detected capacity change from 0 to 62333952 [Wed Mar 16 17:41:58 2022] sda: sda1 [Wed Mar 16 17:44:14 2022] usb 1-1: USB disconnect, device number 23 [Wed Mar 16 17:44:14 2022] usb 1-1.2: USB disconnect, device number 24 [Wed Mar 16 17:44:14 2022] usb 1-1.2.1: USB disconnect, device number 26 [Wed Mar 16 17:44:14 2022] [drm] DM_MST: stopping TM on aconnector: e676af82 [id: 89] [Wed Mar 16 17:44:14 2022] usb 2-1: USB disconnect, device number 14 [Wed Mar 16 17:44:14 2022] usb 2-1.1: USB
[Kernel-packages] [Bug 1908139] Re: ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2
The issue persists on Ubuntu 21.10 with Linux 5.13.0-39-generic. Plugging in Display Port into the docking station wakes up the external screen but does not produce an image (the screen stays black) the builtin screen also goes and remains black until Display Port is disconnected again. Dmesg reports: ``` [ 403.810921] [drm] DP Alt mode state on HPD: 1 [ 403.883530] [drm] DM_MST: starting TM on aconnector: c7e4d18b [id: 90] [ 404.002066] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb da8e8ece port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 404.094206] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb da8e8ece port 2: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 404.937533] usb 4-1.2.4: new full-speed USB device number 36 using xhci_hcd [ 405.057017] usb 4-1.2.4: New USB device found, idVendor=0409, idProduct=04c6, bcdDevice= 0.01 [ 405.057029] usb 4-1.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 405.057033] usb 4-1.2.4: Product: EA275UHD [ 405.057036] usb 4-1.2.4: Manufacturer: NEC [ 405.160140] hid-generic 0003:0409:04C6.001A: hiddev0,hidraw1: USB HID v1.10 Device [NEC EA275UHD] on usb-:06:00.3-1.2.4/input0 [ 409.602964] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb da8e8ece port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 409.638815] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb da8e8ece port 2: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 409.707465] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb da8e8ece port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 409.743267] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb da8e8ece port 2: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 409.812087] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb da8e8ece port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 409.847669] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb da8e8ece port 2: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 409.916745] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb da8e8ece port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 409.952273] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb da8e8ece port 2: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 417.157667] usb 4-1.2.4: USB disconnect, device number 36 [ 425.461698] [drm] DM_MST: stopping TM on aconnector: c7e4d18b [id: 90] ``` (The USB through DP seems to be working - the external screen has a device connected to it via USB) Connecting via HDMI through the docking station fails in the same way. In that case dmesg reports: ``` [ 515.176650] [drm] DP Alt mode state on HPD: 1 [ 515.247435] [drm] DM_MST: starting TM on aconnector: c7e4d18b [id: 90] [ 515.421788] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ea0c2bd3 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 515.490800] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ea0c2bd3 port 2: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 515.560598] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ea0c2bd3 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 515.643894] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ea0c2bd3 port 1: DPCD read on addr 0x60 for 1 bytes NAKed [ 515.878214] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ea0c2bd3 port 1: DPCD read on addr 0x60 for 1 bytes NAKed [ 521.725387] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ea0c2bd3 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 521.761095] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ea0c2bd3 port 2: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 521.796295] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ea0c2bd3 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 521.831504] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ea0c2bd3 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 521.866782] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ea0c2bd3 port 2: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 521.902464] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ea0c2bd3 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 521.937956] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ea0c2bd3 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 521.973705] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ea0c2bd3 port 2: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 522.008924] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ea0c2bd3 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 522.044159] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb ea0c2bd3 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed [ 522.079315] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb
[Kernel-packages] [Bug 1922406]
This no longer occurs for me on Fedora 35 with Kernel version 5.16.5-200.fc35.x86_64. I'm going to unsubscribe but leave this open, as I don't know where the fix was, and don't know the proper procedure for figuring out if this is both fixed & if the kernel has a test. -- 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/1922406 Title: Intel AX210 Wi-Fi card does not work since updating to 1.196 Status in Linux: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Fix Released Bug description: Running 21.04, updated daily. Since updating the linux-firmware package yesterday, the Wireless card does not work with current kernel (5.11.0-13). The error message is as follows: Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting for PNVM load! Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start RT ucode: -110 Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: iwl_trans_send_cmd bad state = 1 It **does** work with 5.11.0-11 (previous version) Distro: Ubuntu 21.04 (Hirsute Hippo) Machine: Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW date: 12/23/2020 CPU: Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP L2 cache: 4 MiB To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1922406/+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
