[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
Copied the finding from https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969142 since this bug is created long time. Pieces of log ``` 四 14 22:55:10 kernel: NVRM: GPU at PCI::01:00: GPU-581d669f-ec00-4588-ca5f-15ab24136974 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: Shader Program Header 18 Error 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: ESR 0x405840=0x8204 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: ESR 0x405848=0x8000 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=1270, Graphics Exception: ChID 0010, Class c597, Offset , Data ``` For nvidia-driver, u-d-c, we need to follow https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html to setup the parameters after some checks. I appended the parameters: options nvidia NVreg_TemporaryFilePath=/run options nvidia NVreg_PreserveVideoMemoryAllocations=1 and then the problem solved. Tried 510.60 as well and the problem is persistent. ** Tags added: jiayi wayland -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro q
[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2u
[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ve
[Kernel-packages] [Bug 1961622] Re: Wire Network Adapter Stop Working After Kernel Update
[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/1961622 Title: Wire Network Adapter Stop Working After Kernel Update Status in linux package in Ubuntu: Expired Bug description: lspci -nnk 00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04) Subsystem: Lenovo 8 Series/C220 Series Chipset Family MEI Controller [17aa:309f] Kernel driver in use: mei_me SysLog Output: Feb 21 12:30:47 black-pearl NetworkManager[992]: [1645468247.6264] device (eno1): Activation: starting connection 'Conexión cableada 1' (2758aa8f-5775-4404-8258-83760e13bc80) Feb 21 12:30:47 black-pearl NetworkManager[992]: [1645468247.6266] audit: op="connection-activate" uuid="2758aa8f-5775-4404-8258-83760e13bc80" name="Conexión cableada 1" pid=1854 uid=1000 result="success" Feb 21 12:30:47 black-pearl NetworkManager[992]: [1645468247.6270] device (eno1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Feb 21 12:30:47 black-pearl NetworkManager[992]: [1645468247.6279] device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Feb 21 12:30:47 black-pearl NetworkManager[992]: [1645468247.6392] device (eno1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Feb 21 12:30:47 black-pearl NetworkManager[992]: [1645468247.6395] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds) Feb 21 12:30:47 black-pearl NetworkManager[992]: [1645468247.6406] dhcp4 (eno1): dhclient started with pid 7899 Feb 21 12:30:47 black-pearl avahi-daemon[852]: Joining mDNS multicast group on interface eno1.IPv6 with address fe80::7d12:bae5:fccc:c841. Feb 21 12:30:47 black-pearl avahi-daemon[852]: New relevant interface eno1.IPv6 for mDNS. Feb 21 12:30:47 black-pearl avahi-daemon[852]: Registering new address record for fe80::7d12:bae5:fccc:c841 on eno1.*. Feb 21 12:30:47 black-pearl dhclient[7899]: DHCPREQUEST of 10.10.144.150 on eno1 to 255.255.255.255 port 67 (xid=0x6c31fad1) Feb 21 12:30:57 black-pearl dhclient[7899]: message repeated 2 times: [ DHCPREQUEST of 10.10.144.150 on eno1 to 255.255.255.255 port 67 (xid=0x6c31fad1)] Feb 21 12:31:07 black-pearl dhclient[7899]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 3 (xid=0xb315ff2c) Feb 21 12:31:10 black-pearl dhclient[7899]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 5 (xid=0xb315ff2c) Feb 21 12:31:15 black-pearl dhclient[7899]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 11 (xid=0xb315ff2c) Feb 21 12:31:26 black-pearl dhclient[7899]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 11 (xid=0xb315ff2c) Feb 21 12:31:33 black-pearl NetworkManager[992]: [1645468293.2903] dhcp4 (eno1): request timed out Feb 21 12:31:33 black-pearl NetworkManager[992]: [1645468293.2904] dhcp4 (eno1): state changed unknown -> timeout Feb 21 12:31:33 black-pearl NetworkManager[992]: [1645468293.3226] dhcp4 (eno1): canceled DHCP transaction, DHCP client pid 7899 Feb 21 12:31:33 black-pearl NetworkManager[992]: [1645468293.3226] dhcp4 (eno1): state changed timeout -> done Feb 21 12:31:33 black-pearl NetworkManager[992]: [1645468293.3228] device (eno1): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed') Feb 21 12:31:33 black-pearl NetworkManager[992]: [1645468293.3231] device (eno1): Activation: failed for connection 'Conexión cableada 1' Feb 21 12:31:33 black-pearl NetworkManager[992]: [1645468293.3235] device (eno1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Feb 21 12:31:33 black-pearl avahi-daemon[852]: Withdrawing address record for fe80::7d12:bae5:fccc:c841 on eno1. Feb 21 12:31:33 black-pearl avahi-daemon[852]: Leaving mDNS multicast group on interface eno1.IPv6 with address fe80::7d12:bae5:fccc:c841. Feb 21 12:31:33 black-pearl avahi-daemon[852]: Interface eno1.IPv6 no longer relevant for mDNS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961622/+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 1961630] Re: Thunderbolt display not working
[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/1961630 Title: Thunderbolt display not working Status in linux package in Ubuntu: Expired Bug description: My Thinkpad X1 Gen4 (20Y5000QUS) using Ubuntu 21.10 is unable to connect to Thunderbolt monitor (BENQ PD2272OU). It works as expected (monitor signal + USB devices) when I installed Windows 10 on the laptop so I have ruled out hardware issues. I have also tried with a Carbon Gen9 running Ubuntu 21.10 and it works as expected. The monitor "BENQ PD2272OU" is detected in the Thunderbolt pane as "Authorized" but no signal and no USB devices. I have installed all updates and firmware available in the "Software" app. I have checked the BIOS and I have "Wake on AC plug" enabled. At this point I am unsure what to try. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961630/+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 1970004] Re: tex shinobi is not being recognize by the kernel
lsusb -d 04d9:0407 -v Bus 007 Device 002: ID 04d9:0407 Holtek Semiconductor, Inc. Keyboard [TEX Shinobi] Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x04d9 Holtek Semiconductor, Inc. idProduct 0x0407 Keyboard [TEX Shinobi] bcdDevice3.10 iManufacturer 0 iProduct1 USB-HID Keyboard iSerial 3 0407 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0072 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 64 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 2 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 34 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber2 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 203 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber3 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bL
[Kernel-packages] [Bug 1970004] Re: tex shinobi is not being recognize by the kernel
I might close this issue since it might be a firmware issue. I have to contact the manufacturer. sigh -- 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/1970004 Title: tex shinobi is not being recognize by the kernel Status in linux package in Ubuntu: Confirmed Bug description: This keyboard only works with bluetooth on Linux. Plugging in the usb does not work https://tex.com.tw/products/shinobi?variant=16969883648090 Apr 22 17:21:16 miggy-To-be-filled-by-O-E-M kernel: [ 207.666827] usb usb6-port1: unable to enumerate USB device Apr 22 17:23:35 user-To-be-filled-by-O-E-M kernel: [ 346.114932] usb 6-1: new full-speed USB device number 20 using xhci_hcd Apr 22 17:23:58 user-To-be-filled-by-O-E-M kernel: [ 369.691397] usb 6-1: new full-speed USB device number 21 using xhci_hcd Apr 22 17:23:58 user-To-be-filled-by-O-E-M kernel: [ 369.827568] usb 6-1: device descriptor read/64, error -71 Apr 22 17:23:59 user-To-be-filled-by-O-E-M kernel: [ 370.279568] usb 6-1: device descriptor read/64, error -71 Apr 22 17:23:59 user-To-be-filled-by-O-E-M kernel: [ 370.515469] usb 6-1: new full-speed USB device number 22 using xhci_hcd Apr 22 17:25:44 user-To-be-filled-by-O-E-M kernel: [ 475.332599] usb 8-2: new full-speed USB device number 3 using xhci_hcd Apr 22 17:25:44 user-To-be-filled-by-O-E-M kernel: [ 475.468701] usb 8-2: device descriptor read/64, error -71 I do not see the keyboard in the lsusb output below. Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 002: ID 1532:0029 Razer USA, Ltd DeathAdder Black Edition Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 008 Device 002: ID 1bcf:2283 Sunplus Innovation Technology Inc. NexiGo N930AF FHD webcam Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 uname -a Linux user-To-be-filled-by-O-E-M 5.15.0-25-generic #25-Ubuntu SMP Wed Mar 30 15:54:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: miggy 2200 F pulseaudio /dev/snd/controlC1: miggy 2200 F pulseaudio /dev/snd/controlC0: miggy 2200 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 17:52:24 2022 InstallationDate: Installed on 2018-03-16 (1498 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ba13b71c-253d-4c72-8408-410f1ad09674 ro quiet splash amdgpu.cik_support=1 radeon.cik_support=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-18 (4 days ago) dmi.bios.date: 12/25/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd12/25/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M
[Kernel-packages] [Bug 1970004] Re: tex shinobi is not being recognize by the kernel
It seems like this device only works from usb-c port to usb-c port I have an arm device with a usb-c port and it see the device properly [ 203.438281] usb 7-1: new full-speed USB device number 2 using xhci-hcd [ 203.622725] usb 7-1: New USB device found, idVendor=04d9, idProduct=0407, bcdDevice= 3.10 [ 203.622772] usb 7-1: New USB device strings: Mfr=0, Product=1, SerialNumber=3 [ 203.622793] usb 7-1: Product: USB-HID Keyboard [ 203.622809] usb 7-1: SerialNumber: 0407 [ 203.642907] input: USB-HID Keyboard as /devices/platform/usb@fe80/fe80.usb/xhci-hcd.3.auto/usb7/7-1/7-1:1.0/0003:04D9:0407.0009/input/input20 [ 203.709294] hid-generic 0003:04D9:0407.0009: input,hidraw2: USB HID v1.11 Keyboard [USB-HID Keyboard] on usb-xhci-hcd.3.auto-1/input0 [ 203.711917] hid-generic 0003:04D9:0407.000A: hiddev97,hidraw3: USB HID v1.11 Device [USB-HID Keyboard] on usb-xhci-hcd.3.auto-1/input1 [ 203.714732] input: USB-HID Keyboard System Control as /devices/platform/usb@fe80/fe80.usb/xhci-hcd.3.auto/usb7/7-1/7-1:1.2/0003:04D9:0407.000B/input/input21 [ 203.779352] input: USB-HID Keyboard Consumer Control as /devices/platform/usb@fe80/fe80.usb/xhci-hcd.3.auto/usb7/7-1/7-1:1.2/0003:04D9:0407.000B/input/input22 [ 203.780301] input: USB-HID Keyboard Mouse as /devices/platform/usb@fe80/fe80.usb/xhci-hcd.3.auto/usb7/7-1/7-1:1.2/0003:04D9:0407.000B/input/input23 [ 203.782002] input: USB-HID Keyboard as /devices/platform/usb@fe80/fe80.usb/xhci-hcd.3.auto/usb7/7-1/7-1:1.2/0003:04D9:0407.000B/input/input24 [ 203.784397] hid-generic 0003:04D9:0407.000B: input,hidraw4: USB HID v1.11 Mouse [USB-HID Keyboard] on usb-xhci-hcd.3.auto-1/input2 [ 203.785461] usb-storage 7-1:1.3: USB Mass Storage device detected -- 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/1970004 Title: tex shinobi is not being recognize by the kernel Status in linux package in Ubuntu: Confirmed Bug description: This keyboard only works with bluetooth on Linux. Plugging in the usb does not work https://tex.com.tw/products/shinobi?variant=16969883648090 Apr 22 17:21:16 miggy-To-be-filled-by-O-E-M kernel: [ 207.666827] usb usb6-port1: unable to enumerate USB device Apr 22 17:23:35 user-To-be-filled-by-O-E-M kernel: [ 346.114932] usb 6-1: new full-speed USB device number 20 using xhci_hcd Apr 22 17:23:58 user-To-be-filled-by-O-E-M kernel: [ 369.691397] usb 6-1: new full-speed USB device number 21 using xhci_hcd Apr 22 17:23:58 user-To-be-filled-by-O-E-M kernel: [ 369.827568] usb 6-1: device descriptor read/64, error -71 Apr 22 17:23:59 user-To-be-filled-by-O-E-M kernel: [ 370.279568] usb 6-1: device descriptor read/64, error -71 Apr 22 17:23:59 user-To-be-filled-by-O-E-M kernel: [ 370.515469] usb 6-1: new full-speed USB device number 22 using xhci_hcd Apr 22 17:25:44 user-To-be-filled-by-O-E-M kernel: [ 475.332599] usb 8-2: new full-speed USB device number 3 using xhci_hcd Apr 22 17:25:44 user-To-be-filled-by-O-E-M kernel: [ 475.468701] usb 8-2: device descriptor read/64, error -71 I do not see the keyboard in the lsusb output below. Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 002: ID 1532:0029 Razer USA, Ltd DeathAdder Black Edition Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 008 Device 002: ID 1bcf:2283 Sunplus Innovation Technology Inc. NexiGo N930AF FHD webcam Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 uname -a Linux user-To-be-filled-by-O-E-M 5.15.0-25-generic #25-Ubuntu SMP Wed Mar 30 15:54:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: miggy 2200 F pulseaudio /dev/snd/controlC1: miggy 2200 F pulseaudio /dev/snd/controlC0: miggy 2200 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 17:52:24 2022 InstallationDate: Installed on 2018-03-16 (1498 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha
[Kernel-packages] [Bug 1861070] Re: Raspberry Pi 4B: USB OTG is not working
** Changed in: linux-raspi2 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861070 Title: Raspberry Pi 4B: USB OTG is not working Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Fix Released Status in linux-raspi source package in Focal: Fix Released Bug description: [Impact] On the RPI4B board, the usb-c power port could also work as a USB OTG mode, but we set the dwc2 driver to the host mode unconditionally, now set it to dual_role mode, then it could work in host/otg/peripheal mode. [Fix] Set USB_DWC2_DUAL_ROLE=y, USB_DWC2_HOST=n [Test Case] set the dtoverlay=dwc2,dr_mode=[otg|peripheral] in the config.txt, and isnmod the g_ether or g_cdc, on the host machine, we could see RPI4B work as a usb device. Because physical port limitation, could test dr_mode=host. [Regression Risk] Low, our eoan kernel choose dwc_otg driver for this port by default, very very few users will choose dwc2 driver, and the dwc2 driver is not enabled by default in our kernel. And bug reporter and I already tested that the peripheral mode works after this change. I am using Raspberry Pi 4B (4GB) and want to make use of the OTG functionality (g_ether). I cross checked with Raspbian to make sure it is not a hardware issue. Extract from dmesg of Ubuntu 19.10.1 with latest updates applied as of Jan 26th, 2020 via "apt-get update" and "apt-get full-upgrade": ... [1.514262] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [1.517365] dwc_otg: FIQ enabled [1.517376] dwc_otg: NAK holdoff enabled [1.517386] dwc_otg: FIQ split-transaction FSM enabled [1.517399] Module dwc_common_port init ... [6.358332] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [6.358388] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [6.358545] dwc2 fe98.usb: Configuration mismatch. dr_mode forced to host [6.409098] dwc2 fe98.usb: DWC OTG Controller [6.409399] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [6.409432] dwc2 fe98.usb: irq 23, io mem 0xfe98 ... [ 111.796714] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I think it is that "Configuration mismatch. dr_mode forced to host" log entry telling me that the port is acting as HOST mode instead of OTG mode. I have try putting these in usercfg.txt "dtoverlay=dwc2" "dtoverlay=dwc2,dr_mode=otg" "dtoverlay=dwc2,dr_mode=peripheral" and it will give the same result, no OTG functionality. On the same hardware running Raspbian Buster, it initialise successfully. Corresponding dmesg: ... [0.567531] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [0.570391] dwc_otg: FIQ enabled [0.570400] dwc_otg: NAK holdoff enabled [0.570409] dwc_otg: FIQ split-transaction FSM enabled [0.570421] Module dwc_common_port init ... [2.507634] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [2.511011] dwc2 fe98.usb: Linked as a consumer to regulator.0 [2.514450] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [2.731860] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm=1 [2.735511] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1 [2.735522] dwc2 fe98.usb: dwc2_check_params: Invalid parameter besl=1 [2.735533] dwc2 fe98.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1 [2.735582] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [2.752511] dwc2 fe98.usb: DWC OTG Controller [2.752554] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [2.752601] dwc2 fe98.usb: irq 36, io mem 0xfe98 ... [2.848843] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 [2.851601] g_ether gadget: g_ether ready [2.854580] dwc2 fe98.usb: bound driver g_ether [2.998525] dwc2 fe98.usb: new device is high-speed [3.075025] dwc2 fe98.usb: new device is high-speed [3.139338] dwc2 fe98.usb: new address 10 [3.154010] g_ether gadget: high-speed config #1: CDC Ethernet (ECM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1861070/+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 1970004] Re: tex shinobi is not being recognize by the kernel
TEX Electronics April 23, 9:32 AM CST Our keyboard include multi device Card reader TEX Electronics April 23, 9:32 AM CST HID Mouse TEX Electronics April 23, 9:32 AM CST HID Keyboard I am trying to contact Tex Shinobi support about the error above. I am thinking the keyboard has an internal usb hub. -- 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/1970004 Title: tex shinobi is not being recognize by the kernel Status in linux package in Ubuntu: Confirmed Bug description: This keyboard only works with bluetooth on Linux. Plugging in the usb does not work https://tex.com.tw/products/shinobi?variant=16969883648090 Apr 22 17:21:16 miggy-To-be-filled-by-O-E-M kernel: [ 207.666827] usb usb6-port1: unable to enumerate USB device Apr 22 17:23:35 user-To-be-filled-by-O-E-M kernel: [ 346.114932] usb 6-1: new full-speed USB device number 20 using xhci_hcd Apr 22 17:23:58 user-To-be-filled-by-O-E-M kernel: [ 369.691397] usb 6-1: new full-speed USB device number 21 using xhci_hcd Apr 22 17:23:58 user-To-be-filled-by-O-E-M kernel: [ 369.827568] usb 6-1: device descriptor read/64, error -71 Apr 22 17:23:59 user-To-be-filled-by-O-E-M kernel: [ 370.279568] usb 6-1: device descriptor read/64, error -71 Apr 22 17:23:59 user-To-be-filled-by-O-E-M kernel: [ 370.515469] usb 6-1: new full-speed USB device number 22 using xhci_hcd Apr 22 17:25:44 user-To-be-filled-by-O-E-M kernel: [ 475.332599] usb 8-2: new full-speed USB device number 3 using xhci_hcd Apr 22 17:25:44 user-To-be-filled-by-O-E-M kernel: [ 475.468701] usb 8-2: device descriptor read/64, error -71 I do not see the keyboard in the lsusb output below. Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 002: ID 1532:0029 Razer USA, Ltd DeathAdder Black Edition Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 008 Device 002: ID 1bcf:2283 Sunplus Innovation Technology Inc. NexiGo N930AF FHD webcam Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 uname -a Linux user-To-be-filled-by-O-E-M 5.15.0-25-generic #25-Ubuntu SMP Wed Mar 30 15:54:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: miggy 2200 F pulseaudio /dev/snd/controlC1: miggy 2200 F pulseaudio /dev/snd/controlC0: miggy 2200 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 17:52:24 2022 InstallationDate: Installed on 2018-03-16 (1498 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ba13b71c-253d-4c72-8408-410f1ad09674 ro quiet splash amdgpu.cik_support=1 radeon.cik_support=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-18 (4 days ago) dmi.bios.date: 12/25/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd12/25/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws/4.15.0-1128.137)
All autopkgtests for the newly accepted linux-restricted-modules-aws (4.15.0-1128.137) for bionic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.147-0ubuntu0.18.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-restricted-modules-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: metacity (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2233 https://gitlab.gnome.org/GNOME/mutter/-/issues/2233 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2233 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-410 in Ubuntu. https://bugs.launchpad.net/bugs/1799679 Title: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows Status in Mutter: Unknown Status in metacity package in Ubuntu: New Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Bug description: Nvidia driver causes Xorg to use 100% CPU and shows high lag and stutter... but only when dragging glxgears/glxheads, or any window over them. Other apps do not exhibit the problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 24 19:11:15 2018 InstallationDate: Installed on 2018-05-26 (151 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1799679/+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 1956177] Re: battery not detected by ACPI
Patrick, I just want to say a big “Thank You”. I have been struggling with this issue for about two months. Your DSDT files haven't worked on my laptop, even my touchpad stopped working after I applied it lol. What did work was dumping my own dsdt, decompiling and updating it, and recompiling it according to your instructions. I guess A3510 comes with a couple of variations, some have i3 cpu, some i5. Thanks again and cheers! -- 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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+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 1970004] 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/1970004 Title: tex shinobi is not being recognize by the kernel Status in linux package in Ubuntu: Confirmed Bug description: This keyboard only works with bluetooth on Linux. Plugging in the usb does not work https://tex.com.tw/products/shinobi?variant=16969883648090 Apr 22 17:21:16 miggy-To-be-filled-by-O-E-M kernel: [ 207.666827] usb usb6-port1: unable to enumerate USB device Apr 22 17:23:35 user-To-be-filled-by-O-E-M kernel: [ 346.114932] usb 6-1: new full-speed USB device number 20 using xhci_hcd Apr 22 17:23:58 user-To-be-filled-by-O-E-M kernel: [ 369.691397] usb 6-1: new full-speed USB device number 21 using xhci_hcd Apr 22 17:23:58 user-To-be-filled-by-O-E-M kernel: [ 369.827568] usb 6-1: device descriptor read/64, error -71 Apr 22 17:23:59 user-To-be-filled-by-O-E-M kernel: [ 370.279568] usb 6-1: device descriptor read/64, error -71 Apr 22 17:23:59 user-To-be-filled-by-O-E-M kernel: [ 370.515469] usb 6-1: new full-speed USB device number 22 using xhci_hcd Apr 22 17:25:44 user-To-be-filled-by-O-E-M kernel: [ 475.332599] usb 8-2: new full-speed USB device number 3 using xhci_hcd Apr 22 17:25:44 user-To-be-filled-by-O-E-M kernel: [ 475.468701] usb 8-2: device descriptor read/64, error -71 I do not see the keyboard in the lsusb output below. Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 002: ID 1532:0029 Razer USA, Ltd DeathAdder Black Edition Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 008 Device 002: ID 1bcf:2283 Sunplus Innovation Technology Inc. NexiGo N930AF FHD webcam Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 uname -a Linux user-To-be-filled-by-O-E-M 5.15.0-25-generic #25-Ubuntu SMP Wed Mar 30 15:54:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: miggy 2200 F pulseaudio /dev/snd/controlC1: miggy 2200 F pulseaudio /dev/snd/controlC0: miggy 2200 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 17:52:24 2022 InstallationDate: Installed on 2018-03-16 (1498 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ba13b71c-253d-4c72-8408-410f1ad09674 ro quiet splash amdgpu.cik_support=1 radeon.cik_support=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-18 (4 days ago) dmi.bios.date: 12/25/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd12/25/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.
[Kernel-packages] [Bug 1970004] [NEW] tex shinobi is not being recognize by the kernel
Public bug reported: This keyboard only works with bluetooth on Linux. Plugging in the usb does not work https://tex.com.tw/products/shinobi?variant=16969883648090 Apr 22 17:21:16 miggy-To-be-filled-by-O-E-M kernel: [ 207.666827] usb usb6-port1: unable to enumerate USB device Apr 22 17:23:35 user-To-be-filled-by-O-E-M kernel: [ 346.114932] usb 6-1: new full-speed USB device number 20 using xhci_hcd Apr 22 17:23:58 user-To-be-filled-by-O-E-M kernel: [ 369.691397] usb 6-1: new full-speed USB device number 21 using xhci_hcd Apr 22 17:23:58 user-To-be-filled-by-O-E-M kernel: [ 369.827568] usb 6-1: device descriptor read/64, error -71 Apr 22 17:23:59 user-To-be-filled-by-O-E-M kernel: [ 370.279568] usb 6-1: device descriptor read/64, error -71 Apr 22 17:23:59 user-To-be-filled-by-O-E-M kernel: [ 370.515469] usb 6-1: new full-speed USB device number 22 using xhci_hcd Apr 22 17:25:44 user-To-be-filled-by-O-E-M kernel: [ 475.332599] usb 8-2: new full-speed USB device number 3 using xhci_hcd Apr 22 17:25:44 user-To-be-filled-by-O-E-M kernel: [ 475.468701] usb 8-2: device descriptor read/64, error -71 I do not see the keyboard in the lsusb output below. Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 002: ID 1532:0029 Razer USA, Ltd DeathAdder Black Edition Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 008 Device 002: ID 1bcf:2283 Sunplus Innovation Technology Inc. NexiGo N930AF FHD webcam Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 uname -a Linux user-To-be-filled-by-O-E-M 5.15.0-25-generic #25-Ubuntu SMP Wed Mar 30 15:54:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: miggy 2200 F pulseaudio /dev/snd/controlC1: miggy 2200 F pulseaudio /dev/snd/controlC0: miggy 2200 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 17:52:24 2022 InstallationDate: Installed on 2018-03-16 (1498 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ba13b71c-253d-4c72-8408-410f1ad09674 ro quiet splash amdgpu.cik_support=1 radeon.cik_support=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-18 (4 days ago) dmi.bios.date: 12/25/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd12/25/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy wayland-session -- 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/1970004 Title: tex shinobi is not being recognize by the kernel Status in linux package in Ubuntu: Confirmed Bug description: This keyboard only works with bluetooth on Linux. Pluggi
[Kernel-packages] [Bug 1908894] Re: USB controllers disconnects after random time
This issue persists in Ubuntu 21.10. My external USB drives get disconnected randomly. Setting "XHCI Hand-off" in BIOS to Disabled *SOLVED* this problem for me. It seems kernel/Ubuntu fails to handle USB properly when given control over it by BIOS. My kernel log: Apr 22 23:57:43 phd kernel: usb 2-4: USB disconnect, device number 4 Apr 22 23:57:43 phd kernel: sd 7:0:0:0: [sde] Synchronizing SCSI cache Apr 22 23:57:43 phd kernel: sd 7:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK Apr 22 23:57:44 phd kernel: usb 2-4: new SuperSpeed USB device number 5 using xhci_hcd Apr 22 23:57:44 phd kernel: usb 2-4: New USB device found, idVendor=, idProduct=, bcdDevice= 1.44 Apr 22 23:57:44 phd kernel: usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Apr 22 23:57:44 phd kernel: usb 2-4: Product: USB 3.0 Apr 22 23:57:44 phd kernel: usb 2-4: Manufacturer: KESU Apr 22 23:57:44 phd kernel: usb 2-4: SerialNumber: 00128453 Apr 22 23:57:44 phd kernel: usb-storage 2-4:1.0: USB Mass Storage device detected Apr 22 23:57:44 phd kernel: scsi host8: usb-storage 2-4:1.0 Apr 22 23:57:45 phd kernel: scsi 8:0:0:0: Direct-Access KESU USB 3.0 2210 PQ: 0 ANSI: 6 Apr 22 23:57:45 phd kernel: sd 8:0:0:0: Attached scsi generic sg5 type 0 Apr 22 23:57:45 phd kernel: sd 8:0:0:0: [sdf] 976773164 512-byte logical blocks: (500 GB/466 GiB) Apr 22 23:57:45 phd kernel: sd 8:0:0:0: [sdf] Write Protect is off Apr 22 23:57:45 phd kernel: sd 8:0:0:0: [sdf] Mode Sense: 2f 00 00 00 Apr 22 23:57:45 phd kernel: sd 8:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 22 23:57:45 phd kernel: sdf: sdf1 Apr 22 23:57:45 phd kernel: sd 8:0:0:0: [sdf] Attached SCSI disk -- 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/1908894 Title: USB controllers disconnects after random time Status in linux package in Ubuntu: Confirmed Bug description: Since I installed Ubuntu on my new convertible laptop, I got issues with the USB. Just after boot my USB controller is working properly (I can connect usb sticks, mices, and my internal camera works) and at some point long after it suddenly stop working (mices suddenly stop moving even when used, webcam and sticks no more detected). This can happend few minuts after boot, or several days after. Yet I have not been able to find what triggers the failure. It happends at any time during normal usage of the computer, including during the usb usage. more concrete infos: after failure, I get $ dmesg [ 2671.894099] perf: interrupt took too long (2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 [ 3262.197917] xhci_hcd :03:00.3: Mismatch between completed Set TR Deq Ptr command & xHCI internal state. [ 3262.197927] xhci_hcd :03:00.3: ep deq seg = 8dafef36, deq ptr = 5f96ce32 [ 3262.198052] xhci_hcd :03:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x] [ 3267.250397] xhci_hcd :03:00.3: xHCI host not responding to stop endpoint command. [ 3267.250428] xhci_hcd :03:00.3: xHCI host controller not responding, assume dead [ 3267.250463] xhci_hcd :03:00.3: HC died; cleaning up [ 3267.250499] usb 1-3: USB disconnect, device number 2 [ 3267.311251] usb 1-4: USB disconnect, device number 3 and lsusb doesn't show my devices anymore, even the newly inserted ones config: Asus Zenbook flip 14 UM462DA ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jimy 1523 F pulseaudio /dev/snd/controlC0: jimy 1523 F pulseaudio /dev/snd/pcmC1D0p: jimy 1523 F...m pulseaudio /dev/snd/timer: jimy 1523 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Dec 21 11:51:08 2020 InstallationDate: Installed on 2020-07-28 (146 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 8087:0a2b Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX462DA ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=ba0f4ac4-b614-4882-83d6-485690f9a61a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-back
[Kernel-packages] [Bug 1969853] Re: Bluetooth doesn't work but seems active
** Package changed: ubuntu => bluez (Ubuntu) -- 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/1969853 Title: Bluetooth doesn't work but seems active Status in bluez package in Ubuntu: New Bug description: After updating to version 22.04, with kernel 5.15.0-25, Bluettoth stopped working via menu. Before I used versions 20.04 and 21.10, the latter with kernel 5.13, and Bluetooth was recognized normally. The bluetooth status in the terminal is this: diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago Docs: man:bluetoothd(8) Main PID: 1100 (bluetoothd) Status: "Running" Tasks: 1 (limit: 18808) Memory: 1.8M CPU: 66ms CGroup: /system.slice/bluetooth.service └─1100 /usr/lib/bluetooth/bluetoothd abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service... abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64 abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service. abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management interface 1.21 initialized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1969853/+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 1969853] [NEW] Bluetooth doesn't work but seems active
You have been subscribed to a public bug: After updating to version 22.04, with kernel 5.15.0-25, Bluettoth stopped working via menu. Before I used versions 20.04 and 21.10, the latter with kernel 5.13, and Bluetooth was recognized normally. The bluetooth status in the terminal is this: diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago Docs: man:bluetoothd(8) Main PID: 1100 (bluetoothd) Status: "Running" Tasks: 1 (limit: 18808) Memory: 1.8M CPU: 66ms CGroup: /system.slice/bluetooth.service └─1100 /usr/lib/bluetooth/bluetoothd abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service... abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64 abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service. abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management interface 1.21 initialized ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Bluetooth doesn't work but seems active https://bugs.launchpad.net/bugs/1969853 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez 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 1929791] Re: Bluetooth does not start if system boots from USB
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-raspi2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1929791 Title: Bluetooth does not start if system boots from USB Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Hello! I have a strange bug with Bluetooth on Raspberry Pi 4 8Gb and Ubuntu 21.04 (also had it on Ubuntu 20.10). It's internal Bluetooth adapder does not initialize, if I boot system from USB, wherein does not matter what I am using: 16 Gb USB Flash Drive, 2 Tb External USB HDD or 1 Tb External SSD. After system boot up, it shows me "no Bluetooth adapters found", hcidev also shows nothing. I'm getting hciuart.service error: === taras@taras-rpi:~$ systemctl status hciuart.service ● hciuart.service - Configure Bluetooth Modems connected by UART Loaded: loaded (/lib/systemd/system/hciuart.service; enabled; vendor prese> Active: failed (Result: exit-code) since Thu 2021-05-27 08:22:57 EEST; 3mi> Process: 599 ExecStart=/usr/bin/btuart (code=exited, status=1/FAILURE) тра 27 08:22:46 taras-rpi systemd[1]: Starting Configure Bluetooth Modems conne> тра 27 08:22:57 taras-rpi btuart[631]: Initialization timed out. тра 27 08:22:57 taras-rpi btuart[631]: bcm43xx_init тра 27 08:22:57 taras-rpi btuart[631]: Flash firmware /lib/firmware/brcm/BCM434> тра 27 08:22:57 taras-rpi btuart[631]: Set Controller UART speed to 300 bit> тра 27 08:22:57 taras-rpi systemd[1]: hciuart.service: Control process exited, > тра 27 08:22:57 taras-rpi systemd[1]: hciuart.service: Failed with result 'exit> тра 27 08:22:57 taras-rpi systemd[1]: Failed to start Configure Bluetooth Modem> === But if I continue reboot system, it may appear in 1-2 cases from 10. It'v very strange. If I disable this service manually via: === sudo systemctl disable hciuart.service === restart the system and run: === sudo systemctl start hciuart.service === Bluetooth adapter will appear in 100% cases. And if I boot Ubuntu from microSD card, everything works properly, Bluetooth starts all times. I thought, mb here is not enougth power for USB devices. I've bought USB hub with external power, but it does not help. Must say, that I don't have this problem on Raspberry Pi OS, I have it on USB HDD too and it works without any problems. Any suggestions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1929791/+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 1929791] Re: Bluetooth does not start if system boots from USB
I got the same bug. If hciuart.service was started before /dev/serial1 is created, it fails. Fixed by adding systemd override with "Requires" directive: # systemctl cat hciuart # /lib/systemd/system/hciuart.service [Unit] Description=Configure Bluetooth Modems connected by UART ConditionFileNotEmpty=/proc/device-tree/soc/gpio@7e20/bt_pins/brcm,pins After=dev-serial1.device [Service] Type=forking ExecStart=/usr/bin/btuart [Install] WantedBy=multi-user.target # /etc/systemd/system/hciuart.service.d/override.conf [Unit] Requires=dev-serial1.device < fix of this problem Here's what documentation says: After=: The units listed in this directive will be started before starting the current unit. This does not imply a dependency relationship and one must be established through the above directives if this is required. Requires=: This directive lists any units upon which this unit essentially depends. If the current unit is activated, the units listed here must successfully activate as well, else this unit will fail. These units are started in parallel with the current unit by default. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1929791 Title: Bluetooth does not start if system boots from USB Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Hello! I have a strange bug with Bluetooth on Raspberry Pi 4 8Gb and Ubuntu 21.04 (also had it on Ubuntu 20.10). It's internal Bluetooth adapder does not initialize, if I boot system from USB, wherein does not matter what I am using: 16 Gb USB Flash Drive, 2 Tb External USB HDD or 1 Tb External SSD. After system boot up, it shows me "no Bluetooth adapters found", hcidev also shows nothing. I'm getting hciuart.service error: === taras@taras-rpi:~$ systemctl status hciuart.service ● hciuart.service - Configure Bluetooth Modems connected by UART Loaded: loaded (/lib/systemd/system/hciuart.service; enabled; vendor prese> Active: failed (Result: exit-code) since Thu 2021-05-27 08:22:57 EEST; 3mi> Process: 599 ExecStart=/usr/bin/btuart (code=exited, status=1/FAILURE) тра 27 08:22:46 taras-rpi systemd[1]: Starting Configure Bluetooth Modems conne> тра 27 08:22:57 taras-rpi btuart[631]: Initialization timed out. тра 27 08:22:57 taras-rpi btuart[631]: bcm43xx_init тра 27 08:22:57 taras-rpi btuart[631]: Flash firmware /lib/firmware/brcm/BCM434> тра 27 08:22:57 taras-rpi btuart[631]: Set Controller UART speed to 300 bit> тра 27 08:22:57 taras-rpi systemd[1]: hciuart.service: Control process exited, > тра 27 08:22:57 taras-rpi systemd[1]: hciuart.service: Failed with result 'exit> тра 27 08:22:57 taras-rpi systemd[1]: Failed to start Configure Bluetooth Modem> === But if I continue reboot system, it may appear in 1-2 cases from 10. It'v very strange. If I disable this service manually via: === sudo systemctl disable hciuart.service === restart the system and run: === sudo systemctl start hciuart.service === Bluetooth adapter will appear in 100% cases. And if I boot Ubuntu from microSD card, everything works properly, Bluetooth starts all times. I thought, mb here is not enougth power for USB devices. I've bought USB hub with external power, but it does not help. Must say, that I don't have this problem on Raspberry Pi OS, I have it on USB HDD too and it works without any problems. Any suggestions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1929791/+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 1969992] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1969992 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** 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/1969992 Title: Bad display Status in linux package in Ubuntu: Incomplete Bug description: When using Cheese, image is displayed black and white and hatched ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 22:42:08 2022 InstallationDate: Installed on 2020-04-10 (742 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-09 (13 days ago) dmi.bios.date: 08/05/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: 970 Extreme4 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd08/05/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969992/+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 1969992] Re: Bad display
** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969992/+attachment/5582633/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202022-04-22%2022-51-01.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969992 Title: Bad display Status in linux package in Ubuntu: Incomplete Bug description: When using Cheese, image is displayed black and white and hatched ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 22:42:08 2022 InstallationDate: Installed on 2020-04-10 (742 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-09 (13 days ago) dmi.bios.date: 08/05/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: 970 Extreme4 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd08/05/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969992/+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 1969992] [NEW] Bad display
Public bug reported: When using Cheese, image is displayed black and white and hatched ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 22:42:08 2022 InstallationDate: Installed on 2020-04-10 (742 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-09 (13 days ago) dmi.bios.date: 08/05/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: 970 Extreme4 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd08/05/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug gstreamer-error jammy wayland-session ** Description changed: - When using Cheese, image is displayed black and white with hatched + When using Cheese, image is displayed black and white and hatched ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 22:42:08 2022 InstallationDate: Installed on 2020-04-10 (742 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. RelatedPackageVersions: - cheese41.1-1build1 - cheese-common 41.1-1build1 + cheese41.1-1build1 + cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-09 (13 days ago) dmi.bios.date: 08/05/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: 970 Extreme4 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd08/05/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. -- 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/1969992 Title: Bad display Status in linux package in Ubuntu: Incomplete Bug description: When using Cheese, image is displayed black and white and hatched ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 22:42:08 2022 InstallationDate: Installed on 2020-04-10 (742 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-09 (13 days ago) dmi.bios.date: 08/05/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: 970 Extreme4 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd08/05/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.v
[Kernel-packages] [Bug 1929209] Re: [i915] external monitor goes black for several seconds at a time, randomly
No one else has joined this bug, but it has continued to make life with my expensive monitor extremely annoying. And despite suggestions above, I am certain this is not a hardware problem. Here is new proof: yesterday, I initiated an upgrade (do-release-upgrade) to 22.04 from 21.10 from the command line. By chance, I tried full-screening a video while the upgrade was in progress. Amazingly, it worked flawlessly the entire duration of the upgrade! ! ! As soon as it was done and rebooted, I tried playing that video again and it did the black-screen / device searching every 3 seconds or so, as it always has. So, how can I reproduce the thing that the upgrade did?! It said something at the beginning about disabling screen lock or something like that, but I have tried turning off all such things in my settings already. -- 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/1929209 Title: [i915] external monitor goes black for several seconds at a time, randomly Status in linux package in Ubuntu: Confirmed Bug description: At times it is completely debilitating; at other times it does not happen for hours. The physical connections are clean and solid. I guess the attachments will show that I'm using Intel graphics hardware. The monitor is a very popular Samsung one. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 20 16:56:04 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (847 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (353 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929209/+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 1969897] Re: Battery report false in kernel 5.13.0-40-generic
Noticed this line in https://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_5.13.0-40.45/changelog QUOTE ACPI: battery: Add the ThinkPad "Not Charging" quirk UNQUOTE -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969991] [NEW] /proc/diskstats contains all 0s for a raid array
Public bug reported: This is an easily reproducible bug occurring in our cloud environment. The issue is that /proc/diskstats has all 0s for md0, a raid0 array. /sys/block/md0/stat also has all 0s. $ uname -r 5.13.0-1022-aws $ cat /proc/diskstats 7 0 loop0 344 0 20160 43 0 0 0 0 0 880 43 0 0 0 0 0 0 7 1 loop1 49 0 974 12 0 0 0 0 0 20 12 0 0 0 0 0 0 7 2 loop2 253 0 4720 47 0 0 0 0 0 228 47 0 0 0 0 0 0 7 3 loop3 6733 0 462030 271 0 0 0 0 0 19352 271 0 0 0 0 0 0 7 4 loop4 69 0 2456 26 0 0 0 0 0 36 26 0 0 0 0 0 0 7 5 loop5 42 0 944 11 0 0 0 0 0 16 11 0 0 0 0 0 0 7 6 loop6 11 0 28 0 0 0 0 0 0 4 0 0 0 0 0 0 0 7 7 loop7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 259 0 nvme0n1 12418 7104 947061 6454 94697 12570 1054464 78054 0 33540 84508 0 0 0 0 0 0 259 1 nvme0n1p1 12117 7104 936053 6381 94697 12570 1054464 78054 0 33472 84435 0 0 0 0 0 0 259 2 nvme1n1 8105 21 79736 4085 24991 30424 443720 1150 0 39332 5236 0 0 0 0 0 0 259 3 nvme2n1 1044 0 22470 191 16968 29804 374432 702 0 29344 893 0 0 0 0 0 0 9 0 md0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 $ cat /sys/block/md0/stat 00000000 000000000 We see this on all similarly configured instances with this kernel. With a slightly older kernel, the problem does not happen (using the same instance type): $ uname -r 5.11.0-1028-aws $ cat /proc/diskstats 7 0 loop0 385 0 23980 62 0 0 0 0 0 1072 62 0 0 0 0 0 0 7 1 loop1 57 0 2768 14 0 0 0 0 0 64 14 0 0 0 0 0 0 7 2 loop2 1274 0 80288 67 0 0 0 0 0 3308 67 0 0 0 0 0 0 7 3 loop3 125 0 4756 22 0 0 0 0 0 84 22 0 0 0 0 0 0 7 4 loop4 6928 0 485026 299 0 0 0 0 0 19676 299 0 0 0 0 0 0 7 5 loop5 1403 0 96676 84 0 0 0 0 0 4224 84 0 0 0 0 0 0 7 6 loop6 423 0 26558 60 0 0 0 0 0 1132 60 0 0 0 0 0 0 7 7 loop7 920 0 50490 43 0 0 0 0 0 2100 43 0 0 0 0 0 0 259 0 nvme0n1 263525 48497 11700905 168289 7397504 1092004 83304504 6618617 0 2318176 6786907 0 0 0 0 0 0 259 1 nvme0n1p1 261591 48497 11636377 167726 7397504 1092004 83304504 6618617 0 2318004 6786343 0 0 0 0 0 0 259 2 nvme2n1 210691 47 34312138 145597 4361154622 39741208 889622866304 947127588 0 405758020 951731842 51375 0 129566145192 4458656 0 0 259 3 nvme1n1 220561 171 34057770 148965 4363589540 40496575 889678501709 963085301 0 409181904 967699619 47256 0 129564097320 4465352 0 0 9 0 md0 375711 0 68340222 258768 7141406762 0 1779301368005 2040115436 0 421027688 2045172840 66637 0 259130242512 4798636 0 0 7 8 loop8 76 0 3766 1 0 0 0 0 0 44 1 0 0 0 0 0 0 7 9 loop9 66 0 2036 1 0 0 0 0 0 40 1 0 0 0 0 0 0 7 10 loop10 78 0 3022 1 0 0 0 0 0 32 1 0 0 0 0 0 0 7 11 loop11 23 0 64 0 0 0 0 0 0 8 0 0 0 0 0 0 0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-1022-aws 5.13.0-1022.24~20.04.1 ProcVersionSignature: User Name 5.13.0-1022.24~20.04.1-aws 5.13.19 Uname: Linux 5.13.0-1022-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 22 20:07:26 2022 Ec2AMI: ami-04cf18ef54851b02b Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: i3en.6xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-aws-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-aws-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1969991 Title: /proc/diskstats contains all 0s for a raid array Status in linux-signed-aws-5.13 package in Ubuntu: New Bug description: This is an easily reproducible bug occurring in our cloud environment. The issue is that /proc/diskstats has all 0s for md0, a raid0 array. /sys/block/md0/stat also has all 0s. $ uname -r 5.13.0-1022-aws $ cat /proc/diskstats 7 0 loop0 344 0 20160 43 0 0 0 0 0 880 43 0 0 0 0 0 0 7 1 loop1 49 0 974 12 0 0 0 0 0 20 12 0 0 0 0 0 0 7 2 loop2 253 0 4720 47 0 0 0 0 0 228 47 0 0 0 0 0 0 7 3 loop3 6733 0 462030 271 0 0 0 0 0 19352 271 0 0 0 0 0 0 7 4 loop4 69 0 2456 26 0 0 0 0 0 36 26 0 0 0 0 0 0 7 5 loop5 42 0 944 11 0 0 0 0 0 16 11 0 0 0 0 0 0 7 6 loop6 11 0 28 0 0 0 0 0 0 4 0 0 0 0 0 0 0 7 7 loop7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 259 0 nvme0n1 12418 7104 947061 6454 94697 12570 1054464 78054 0 33540 84508 0 0 0 0 0 0 259 1 nvme0n1p1 12117 7104 936053 6381 94697 12570 1054464 78
[Kernel-packages] [Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: Jeff Lane (bladernr) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967116 Title: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below: 334ae6459aa3 scsi: mpi3mr: Fix flushing !WQ_MEM_RECLAIM events warning 22754f7fbb40 scsi: mpi3mr: Bump driver version to 8.0.0.68.0 d44b5fefb22e scsi: mpi3mr: Fix memory leaks 21401408ddeb scsi: mpi3mr: Update the copyright year 999224612724 scsi: mpi3mr: Fix reporting of actual data transfer size b3911ab3a76e scsi: mpi3mr: Fix cmnd getting marked as in use forever 191a3ef58634 scsi: mpi3mr: Fix hibernation issue 04b27e538d50 scsi: mpi3mr: Update MPI3 headers 6d211f1d2635 scsi: mpi3mr: Fix printing of pending I/O count 580e6742205e scsi: mpi3mr: Fix deadlock while canceling the fw event 3bb3c24e268a scsi: mpi3mr: Fix formatting problems in some kernel-doc comments 5867b8569e64 scsi: mpi3mr: Fix some spelling mistakes c77b1f8a8fae scsi: mpi3mr: Bump driver version to 8.0.0.61.0 a91603a5d504 scsi: mpi3mr: Enhanced Task Management Support Reply handling c86651345ca5 scsi: mpi3mr: Use TM response codes from MPI3 headers afd3a5793fe2 scsi: mpi3mr: Add io_uring interface support in I/O-polled mode 95cca8d5542a scsi: mpi3mr: Print cable mngnt and temp threshold events 78b76a0768ef scsi: mpi3mr: Support Prepare for Reset event c1af985d27da scsi: mpi3mr: Add Event acknowledgment logic c5758fc72b92 scsi: mpi3mr: Gracefully handle online FW update operation b64845a7d403 scsi: mpi3mr: Detect async reset that occurred in firmware c0b00a931e5e scsi: mpi3mr: Add IOC reinit function fe6db6151565 scsi: mpi3mr: Handle offline FW activation in graceful manner 59bd9cfe3fa0 scsi: mpi3mr: Code refactor of IOC init - part2 e3605f65ef69 scsi: mpi3mr: Code refactor of IOC init - part1 a6856cc4507b scsi: mpi3mr: Fault IOC when internal command gets timeout 2ac794baaec9 scsi: mpi3mr: Display IOC firmware package version 13fd7b1555b6 scsi: mpi3mr: Handle unaligned PLL in unmap cmnds 4f08b9637f63 scsi: mpi3mr: Increase internal cmnds timeout to 60s ba68779a518d scsi: mpi3mr: Do access status validation before adding devices 17d6b9cf89cf scsi: mpi3mr: Add support for PCIe Managed Switch SES device ec5ebd2c14a9 scsi: mpi3mr: Update MPI3 headers - part2 d00ff7c31195 scsi: mpi3mr: Update MPI3 headers - part1 fbaa9aa48bb4 scsi: mpi3mr: Don't reset IOC if cmnds flush with reset status a83ec831b24a scsi: mpi3mr: Replace spin_lock() with spin_lock_irqsave() 9cf0666f34b1 scsi: mpi3mr: Add debug APIs based on logging_level bits 30e99f05f8b1 scsi: mpi3mr: Use scnprintf() instead of snprintf() 97e6ea6d7806 scsi: mpi3mr: Fix duplicate device entries when scanning through sysfs 1a30fd18f21b scsi: mpi3mr: Call scsi_done() directly 76a4f7cc5973 scsi: mpi3mr: Clean up mpi3mr_print_ioc_info() 92cc94adfce4 scsi: mpi3mr: Use the proper SCSI midlayer interfaces for PI 69868c3b6939 scsi: mpi3mr: Use scsi_cmd_to_rq() instead of scsi_cmnd.request aa0dc6a73309 scsi: mpi3mr: Fix W=1 compilation warnings 62e528b80d6b scsi: mpi3mr: Fix warnings reported by smatch a254eae30b45 scsi: mpi3mr: Fix error return code in mpi3mr_init_ioc() f9dc034d0402 scsi: mpi3mr: Fix missing unlock on error 2938bedd0efa scsi: mpi3mr: Fix error handling in mpi3mr_setup_isr() d46bdecd9f3c scsi: mpi3mr: Delete unnecessary NULL check d3d61f9c8c2d scsi: mpi3mr: Fix a double free 7b8a49881b01 scsi: mpi3mr: Fix fall-through warning for Clang 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints Thanks, Sumit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967116/+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 1969986] 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/1969986 Title: AMDGPU driver confused by two AMD GPUs Status in linux package in Ubuntu: Confirmed Bug description: When I start a game (Surviving Mars) via Steam the framerates are abysmal, somewhere between 10 to 20 fps. On 17.4.22 it still hit 60 fps. When my screen is attached to the 6600 XT card and the game is running, the following can be seen: jan-bart@barts-tuxbox:/sys$ cat ./devices/pci:00/:00:01.1/:10:00.0/:11:00.0/:12:00.0/pp_dpm_sclk 0: 500Mhz 1: 700Mhz * 2: 2900Mhz jan-bart@barts-tuxbox:/sys$ cat ./devices/pci:00/:00:08.1/:30:00.0/pp_dpm_sclk 0: 200Mhz 1: 700Mhz 2: 2000Mhz * jan-bart@barts-tuxbox:/sys$ lspci | grep VGA 12:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] (rev c1) 30:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne (rev c8) For some reason the clock of the unused graphics device is increased. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jan-bart 1677 F pulseaudio /dev/snd/controlC0: jan-bart 1677 F pulseaudio /dev/snd/controlC1: jan-bart 1677 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Apr 22 20:53:17 2022 InstallationDate: Installed on 2022-03-20 (32 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) MachineType: Micro-Star International Co., Ltd. MS-7C92 ProcFB: 0 amdgpudrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=cc17c347-c0ab-47b6-9c92-86a6b2826ddc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MPG B550I GAMING EDGE MAX WIFI (MS-7C92) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.80:bd12/21/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C92:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGB550IGAMINGEDGEMAXWIFI(MS-7C92):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C92 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969986/+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 1969966] Re: No support for Intel Killer AX1675i
** Description changed: I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 5511 laptop but can't get WiFi or Bluetooth. About WiFi I get these logs: - ➜ sudo dmesg|grep wifi -i + ➜ sudo dmesg|grep wifi -i [4.917786] Loading modules backported from iwlwifi [4.917787] iwlwifi-stack-public:master:9858:4c7cba27 [4.984194] Intel(R) Wireless WiFi driver for Linux [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002) [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, rfid=0x2010d000 [4.996123] iwlwifi: probe of :00:14.3 failed with error -22 About Bluetooth I get these logs: ➜ sudo dmesg|grep bluetooth -i [4.977780] Bluetooth: Core ver 2.22 [4.977793] NET: Registered PF_BLUETOOTH protocol family [4.977794] Bluetooth: HCI device and connection manager initialized [4.977799] Bluetooth: HCI socket layer initialized [4.977800] Bluetooth: L2CAP socket layer initialized [4.977803] Bluetooth: SCO socket layer initialized [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018 [5.003784] Bluetooth: hci0: Device revision is 0 [5.003787] Bluetooth: hci0: Secure boot is enabled [5.003788] Bluetooth: hci0: OTP lock is enabled [5.003788] Bluetooth: hci0: API lock is enabled [5.003789] Bluetooth: hci0: Debug lock is disabled [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.006774] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-19-0-3.sfi (-2) [5.007774] Bluetooth: hci0: MSFT supported features length mismatch [7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [7.023201] Bluetooth: BNEP filters: protocol multicast [7.023204] Bluetooth: BNEP socket layer initialized I'm in doubt about WiFi, since the message doesn't mention a missing firmware, but Bluetooth is very clear about it. + + + I'm using Ubuntu 22.04 LTS with bleeding edge kernel 5.17.4. I also tried with 5.18rc1 but no change -- 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/1969966 Title: No support for Intel Killer AX1675i Status in linux-firmware package in Ubuntu: New Bug description: I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 5511 laptop but can't get WiFi or Bluetooth. About WiFi I get these logs: ➜ sudo dmesg|grep wifi -i [4.917786] Loading modules backported from iwlwifi [4.917787] iwlwifi-stack-public:master:9858:4c7cba27 [4.984194] Intel(R) Wireless WiFi driver for Linux [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002) [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, rfid=0x2010d000 [4.996123] iwlwifi: probe of :00:14.3 failed with error -22 About Bluetooth I get these logs: ➜ sudo dmesg|grep bluetooth -i [4.977780] Bluetooth: Core ver 2.22 [4.977793] NET: Registered PF_BLUETOOTH protocol family [4.977794] Bluetooth: HCI device and connection manager initialized [4.977799] Bluetooth: HCI socket layer initialized [4.977800] Bluetooth: L2CAP socket layer initialized [4.977803] Bluetooth: SCO socket layer initialized [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018 [5.003784] Bluetooth: hci0: Device revision is 0 [5.003787] Bluetooth: hci0: Secure boot is enabled [5.003788] Bluetooth: hci0: OTP lock is enabled [5.003788] Bluetooth: hci0: API lock is enabled [5.003789] Bluetooth: hci0: Debug lock is disabled [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.006774] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-19-0-3.sfi (-2) [5.007774] Bluetooth: hci0: MSFT supported features length mismatch [7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [7.023201] Bluetooth: BNEP filters: protocol multicast [7.023204] Bluetooth: BNEP socket layer initialized I'm in doubt about WiFi, since the message doesn't mention a missing firmware, but Bluetooth is very clear about it. I'm using Ubuntu 22.04 LTS with bleeding edge kernel 5.17.4. I also tried with 5.18rc1 but no change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1969966/+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 1969986] [NEW] AMDGPU driver confused by two AMD GPUs
Public bug reported: When I start a game (Surviving Mars) via Steam the framerates are abysmal, somewhere between 10 to 20 fps. On 17.4.22 it still hit 60 fps. When my screen is attached to the 6600 XT card and the game is running, the following can be seen: jan-bart@barts-tuxbox:/sys$ cat ./devices/pci:00/:00:01.1/:10:00.0/:11:00.0/:12:00.0/pp_dpm_sclk 0: 500Mhz 1: 700Mhz * 2: 2900Mhz jan-bart@barts-tuxbox:/sys$ cat ./devices/pci:00/:00:08.1/:30:00.0/pp_dpm_sclk 0: 200Mhz 1: 700Mhz 2: 2000Mhz * jan-bart@barts-tuxbox:/sys$ lspci | grep VGA 12:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] (rev c1) 30:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne (rev c8) For some reason the clock of the unused graphics device is increased. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jan-bart 1677 F pulseaudio /dev/snd/controlC0: jan-bart 1677 F pulseaudio /dev/snd/controlC1: jan-bart 1677 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Apr 22 20:53:17 2022 InstallationDate: Installed on 2022-03-20 (32 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) MachineType: Micro-Star International Co., Ltd. MS-7C92 ProcFB: 0 amdgpudrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=cc17c347-c0ab-47b6-9c92-86a6b2826ddc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MPG B550I GAMING EDGE MAX WIFI (MS-7C92) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.80:bd12/21/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C92:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGB550IGAMINGEDGEMAXWIFI(MS-7C92):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C92 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1969986 Title: AMDGPU driver confused by two AMD GPUs Status in linux package in Ubuntu: New Bug description: When I start a game (Surviving Mars) via Steam the framerates are abysmal, somewhere between 10 to 20 fps. On 17.4.22 it still hit 60 fps. When my screen is attached to the 6600 XT card and the game is running, the following can be seen: jan-bart@barts-tuxbox:/sys$ cat ./devices/pci:00/:00:01.1/:10:00.0/:11:00.0/:12:00.0/pp_dpm_sclk 0: 500Mhz 1: 700Mhz * 2: 2900Mhz jan-bart@barts-tuxbox:/sys$ cat ./devices/pci:00/:00:08.1/:30:00.0/pp_dpm_sclk 0: 200Mhz 1: 700Mhz 2: 2000Mhz * jan-bart@barts-tuxbox:/sys$ lspci | grep VGA 12:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] (rev c1) 30:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne (rev c8) For some reason the clock of the unused graphics device is increased. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jan-bart 1677 F pulseaudio /dev/snd/controlC0: jan-bart 1677 F pulseaudio /dev/snd/controlC1: jan-bart 1677 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Apr 22 20:53:17 2022 InstallationDate: Installed on 2022-03-20 (32 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) MachineType:
[Kernel-packages] [Bug 1969966] Re: No support for Intel Killer AX1675i
I loaded the iwlwifi module with debug=1 option to get more details. I hope it helps ➜ sudo dmesg|grep wifi -i [6.484062] Loading modules backported from iwlwifi [6.484063] iwlwifi-stack-public:master:9858:4c7cba27 [6.576473] Intel(R) Wireless WiFi driver for Linux [6.577121] iwlwifi :00:14.3: enabling device ( -> 0002) [6.585684] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, rfid=0x2010d000 [6.585742] iwlwifi: probe of :00:14.3 failed with error -22 [ 177.897898] Intel(R) Wireless WiFi driver for Linux [ 177.898344] iwlwifi :00:14.3: iwl_trans_pcie_alloc HW REV: 0x351 [ 177.898865] iwlwifi :00:14.3: iwl_pcie_set_interrupt_capa MSI-X enabled. 16 interrupt vectors were allocated [ 177.898867] iwlwifi :00:14.3: iwl_pcie_set_interrupt_capa MSI-X enabled with rx queues 15, vec mask 0x0 [ 177.899758] iwlwifi :00:14.3: iwl_pcie_prepare_card_hw iwl_trans_prepare_card_hw enter [ 177.899782] iwlwifi :00:14.3: iwl_pcie_set_hw_ready hardware ready [ 177.899797] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, rfid=0x2010d000 [ 177.899803] iwlwifi :00:14.3: iwl_pcie_rx_free Free NULL rx context [ 177.899814] iwlwifi: probe of :00:14.3 failed with error -22 -- 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/1969966 Title: No support for Intel Killer AX1675i Status in linux-firmware package in Ubuntu: New Bug description: I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 5511 laptop but can't get WiFi or Bluetooth. About WiFi I get these logs: ➜ sudo dmesg|grep wifi -i [4.917786] Loading modules backported from iwlwifi [4.917787] iwlwifi-stack-public:master:9858:4c7cba27 [4.984194] Intel(R) Wireless WiFi driver for Linux [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002) [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, rfid=0x2010d000 [4.996123] iwlwifi: probe of :00:14.3 failed with error -22 About Bluetooth I get these logs: ➜ sudo dmesg|grep bluetooth -i [4.977780] Bluetooth: Core ver 2.22 [4.977793] NET: Registered PF_BLUETOOTH protocol family [4.977794] Bluetooth: HCI device and connection manager initialized [4.977799] Bluetooth: HCI socket layer initialized [4.977800] Bluetooth: L2CAP socket layer initialized [4.977803] Bluetooth: SCO socket layer initialized [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018 [5.003784] Bluetooth: hci0: Device revision is 0 [5.003787] Bluetooth: hci0: Secure boot is enabled [5.003788] Bluetooth: hci0: OTP lock is enabled [5.003788] Bluetooth: hci0: API lock is enabled [5.003789] Bluetooth: hci0: Debug lock is disabled [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.006774] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-19-0-3.sfi (-2) [5.007774] Bluetooth: hci0: MSFT supported features length mismatch [7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [7.023201] Bluetooth: BNEP filters: protocol multicast [7.023204] Bluetooth: BNEP socket layer initialized I'm in doubt about WiFi, since the message doesn't mention a missing firmware, but Bluetooth is very clear about it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1969966/+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 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
SRU: https://lists.ubuntu.com/archives/kernel-
team/2022-April/129683.html (V2: oem-5.14, jammy, unstable, oem-5.17)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1969434
Title:
build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
Status in backport-iwlwifi-dkms package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
New
Status in backport-iwlwifi-dkms source package in Focal:
New
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
New
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in backport-iwlwifi-dkms source package in Jammy:
Fix Released
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
New
Bug description:
[SRU Justfication]
[Impact]
Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress,
and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16.
Not reproducible on every platform with AX211 installed, and the chances
of such failures vary from one to another.
[Fix]
A few solutions were considered. The very first one is to ask Intel to
fix -64 firmware directly, and the answer is a solid no claimed -64 is
not the planned production version of AX211.
It's also possible to backport FW API from v5.16, but while iwlwifi FW
API is more or less a black box to us and the new FW APIs also depends
on updates on the wireless stack, this is going to be very risky and
actually we had regressions before after such backports.
The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on
the effected platforms. This means oem-5.14 and its migration target,
hwe-5.15 will not be able to drive this piece of hw flawlessly without
backport-iwlwifi-dkms installed.
However, while we need secureboot to be enabled on these platforms,
backport-iwlwifi-dkms must also be signed somehow. There are two
possible method to achieve this, too. One, to prebuild this dkms as zfs
and v4l2loopback does. However, while backport-iwlwifi-dkms generates
kernel modules with exactly the same name as the in-tree ones, when
prebuilt, they'll be available directly from the linux-modules package
and therefore overrides the in-tree ones always, turning the in-tree
driver completely useless and risk the stability of all other generic
installations.
The second one is to build backport-iwlwifi-dkms as nvidia graphic
drivers in the linux-restricted-modules source package. In this way,
affected platforms may install the corresponding packages when needed
without interfering others. However, l-r-m is for restricted modules
that needs special care of redistribution of its binaries, and
backport-iwlwifi-dkms is GPL licensed.
Here a similar but simpler process in the main kernel tree is
re-implemented. Two additional packages,
linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package
linux-modules-MODULE-FLAVOUR will be created.
[Test Case]
Test builds:
./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb
./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb
./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb
./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb
./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb
./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb
./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb
./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb
[Where problems could occur]
The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails
to build under this proposed process. Debdiff attached to the same
bug.
Different from nvidia packages built from l-r-m, the generated package
names do not carry an additional short version string, e.g. nvidia-410,
as there is no such necessity to build multiple versions of iwlwifi.
The modules are installed to /lib/modules//kernel/iwlwifi, not
iwlwifi-9858/.
== backport-iwlwifi-dkms SRU ==
In order to be compiled with dkms-build in kernel source package, the
kernel header dir will not be /lib/modules//build but a
temporary directory. This change specifies KLIB_BUILD from dkms
variable ${kernel_source_dir}.
[backport-iwlwifi-dkms]
Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build
--kernelsourcedir ...` and yet the dkms make command in this package
has:
MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver"
To manage notifications about this bug go to:
https://bugs
[Kernel-packages] [Bug 1969966] [NEW] No support for Intel Killer AX1675i
Public bug reported: I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 5511 laptop but can't get WiFi or Bluetooth. About WiFi I get these logs: ➜ sudo dmesg|grep wifi -i [4.917786] Loading modules backported from iwlwifi [4.917787] iwlwifi-stack-public:master:9858:4c7cba27 [4.984194] Intel(R) Wireless WiFi driver for Linux [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002) [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, rfid=0x2010d000 [4.996123] iwlwifi: probe of :00:14.3 failed with error -22 About Bluetooth I get these logs: ➜ sudo dmesg|grep bluetooth -i [4.977780] Bluetooth: Core ver 2.22 [4.977793] NET: Registered PF_BLUETOOTH protocol family [4.977794] Bluetooth: HCI device and connection manager initialized [4.977799] Bluetooth: HCI socket layer initialized [4.977800] Bluetooth: L2CAP socket layer initialized [4.977803] Bluetooth: SCO socket layer initialized [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018 [5.003784] Bluetooth: hci0: Device revision is 0 [5.003787] Bluetooth: hci0: Secure boot is enabled [5.003788] Bluetooth: hci0: OTP lock is enabled [5.003788] Bluetooth: hci0: API lock is enabled [5.003789] Bluetooth: hci0: Debug lock is disabled [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.006774] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-19-0-3.sfi (-2) [5.007774] Bluetooth: hci0: MSFT supported features length mismatch [7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [7.023201] Bluetooth: BNEP filters: protocol multicast [7.023204] Bluetooth: BNEP socket layer initialized I'm in doubt about WiFi, since the message doesn't mention a missing firmware, but Bluetooth is very clear about it. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- 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/1969966 Title: No support for Intel Killer AX1675i Status in linux-firmware package in Ubuntu: New Bug description: I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 5511 laptop but can't get WiFi or Bluetooth. About WiFi I get these logs: ➜ sudo dmesg|grep wifi -i [4.917786] Loading modules backported from iwlwifi [4.917787] iwlwifi-stack-public:master:9858:4c7cba27 [4.984194] Intel(R) Wireless WiFi driver for Linux [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002) [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, rfid=0x2010d000 [4.996123] iwlwifi: probe of :00:14.3 failed with error -22 About Bluetooth I get these logs: ➜ sudo dmesg|grep bluetooth -i [4.977780] Bluetooth: Core ver 2.22 [4.977793] NET: Registered PF_BLUETOOTH protocol family [4.977794] Bluetooth: HCI device and connection manager initialized [4.977799] Bluetooth: HCI socket layer initialized [4.977800] Bluetooth: L2CAP socket layer initialized [4.977803] Bluetooth: SCO socket layer initialized [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018 [5.003784] Bluetooth: hci0: Device revision is 0 [5.003787] Bluetooth: hci0: Secure boot is enabled [5.003788] Bluetooth: hci0: OTP lock is enabled [5.003788] Bluetooth: hci0: API lock is enabled [5.003789] Bluetooth: hci0: Debug lock is disabled [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.006774] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-19-0-3.sfi (-2) [5.007774] Bluetooth: hci0: MSFT supported features length mismatch [7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [7.023201] Bluetooth: BNEP filters: protocol multicast [7.023204] Bluetooth: BNEP socket layer initialized I'm in doubt about WiFi, since the message doesn't mention a missing firmware, but Bluetooth is very clear about it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1969966/+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 1924298] Re: accept returns duplicate endpoints under load
After spending some time I think I have narrowed down the bug fix to
Linux kernel 5.10-rc6.
The bug reproed on Ubuntu with kernel 5.10-rc4 but not on 5.10-rc6.
Here is a diff of the kernel sources between those two versions:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/?id=v5.10-rc6&id2=v5.10-rc4&dt=2
Of note are some changes to `net/ipv4/inet_hashtables.c`
Using `git blame` I think the most likely source of the bug fix was this
commit by Ricardo Dias:
https://github.com/torvalds/linux/commit/01770a166165738a6e05c3d911fb4609cc4eb416
The description for the commit describes a race condition which looks
like it could cause the bug:
"When such event happens, the TCP stack code has a race condition that
occurs between the momement a lookup is done to the established
connections hashtable to check for the existence of a connection for the
same client, and the moment that the child socket is added to the
established connections hashtable. As a consequence, this race condition
can lead to a situation where we add two child sockets to the
established connections hashtable and deliver two sockets to the
userspace program to the same client."
So for anyone who comes across this bug, the likely solution is to
update your OS to a version which uses kernel 5.10 or greater.
--
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/1924298
Title:
accept returns duplicate endpoints under load
Status in Linux:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
When accepting client connections under load, duplicate endpoints may
be returned. These endpoints will have different (usually sequential)
file descriptors but will refer to the same connection (same server
IP, same server port, same client IP, same client port). Both copies
of the endpoint appear to be functional.
Reproduction requires:
- compilation of the attached server.c program
- wrk (https://github.com/wg/wrk) to generate load
The steps to reproduce are:
- run 'server' application in one console window
- run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency
--timeout 1s http://localhost:/post; done' in a second console window
- run the same command in a third window to generate concurrent load
You may need to run additional instance of the wrk command in multiple
windows to trigger the issue.
When the problem occurs the server executable will exit and print some
debugging info. e.g.:
accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient
= 232
This indicates that the sockets with file descriptors 233 and 232 are
duplicates.
The issue has been reproduced on fully patched versions of Ubuntu
20.04 and 18.04. Other versions have not been tested.
This issue was originally observed in Java and was reported against the
Spring Framework:
https://github.com/spring-projects/spring-framework/issues/26434
Investigation from the Spring team and the Apache Tomcat team identified that
it appeared to be a JDK issue:
https://bugs.openjdk.java.net/browse/JDK-8263243
Further research from the JDK team determined that the issue was at
the OS level. Hence this report.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-71-generic 5.4.0-71.79
ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
Uname: Linux 5.4.0-71-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 15 12:52:53 2021
HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
InstallationDate: Installed on 2017-02-02 (1532 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig:
lono wireless extensions.
docker0 no wireless extensions.
eno1 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. Default string
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic
root=/dev/mapper/ubuntu--vg-root ro text
RelatedPackageVersions:
linux-restricted-modules-5.4.0-71-generic N/A
linux-backports-modules-5.4.0-71-generic N/A
linux-firmware1.187.10
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
dmi.bios.date: 06/13/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F22
dmi.board.asset.tag: Default string
dmi.board.name: X99-SLI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaults
[Kernel-packages] [Bug 1965611] Re: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources
Update: Upgraded Ubuntu to 22.04 LTS. Same behavior. Sometimes it turns on the second display (very rarely), but mostly Its blacked out until I do the input source switching thing. -- 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/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+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 1948626] Re: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
** Description changed: [Impact] NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers. TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis. Here is code that implements TP8009 and TP8010: https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas [Fix] 1. Update kernel with TP8010 kernel patches: a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907 b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0 c. - nvme: add CNTRLTYPE definitions for 'identify controller + nvme: add CNTRLTYPE definitions for 'identify controller https://lore.kernel.org/all/66fc4f03-ed5c-4727-ba94-c23daf7d6...@oracle.com/ [Test Case] [Other Info] - https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches_2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948626 Title: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Impact] NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers. TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis. Here is code that implements TP8009 and TP8010: https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas [Fix] 1. Update kernel with TP8010 kernel patches: a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907 b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0 c. nvme: add CNTRLTYPE definitions for 'identify controller https://lore.kernel.org/all/66fc4f03-ed5c-4727-ba94-c23daf7d6...@oracle.com/ [Test Case] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches_2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+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 1969897] Re: Battery report false in kernel 5.13.0-40-generic
second attachment ** Attachment added: "Screenshot from 2022-04-22 10-55-53.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+attachment/5582382/+files/Screenshot%20from%202022-04-22%2010-55-53.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] Re: Battery report false in kernel 5.13.0-40-generic
I have replicated the issue. Whilst logged into kernel 5.13.0-40-generic I removed power cable for a minute or so, re-inserted power cable and my battery indicator showed 96% and not charging. Restarted machine logging into kernel 5.13.0-39-generic and the battery indicator shows 100% and fully charged. See attached screenshots. ** Attachment added: "Screenshot from 2022-04-22 10-53-33.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+attachment/5582381/+files/Screenshot%20from%202022-04-22%2010-53-33.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582368/+files/ProcCpuinfo.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582369/+files/ProcCpuinfoMinimal.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] Re: Battery report false in kernel 5.13.0-40-generic
Result from terminal;- QUOTE dave@dave-ThinkPad-T410ssd:~$ apport-collect 1969897 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=WQ0jkjf30wTQwxs2vXxj&allow_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... dpkg-query: no packages found matching linux UNQUOTE ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582375/+files/WifiSyslog.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582376/+files/acpidump.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582371/+files/ProcInterrupts.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582367/+files/Lsusb-v.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582374/+files/UdevDb.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582373/+files/PulseList.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582372/+files/ProcModules.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582370/+files/ProcEnviron.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582366/+files/Lsusb-t.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582361/+files/CurrentDmesg.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582360/+files/CRDA.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582364/+files/Lspci-vt.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582362/+files/IwConfig.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582363/+files/Lspci.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582365/+files/Lsusb.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 1820 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 2519Y11 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.187.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] Re: Battery report false in kernel 5.13.0-40-generic
apport information ** Tags added: apport-collected focal ** Description changed: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.23 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: dave 1820 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-01-25 (451 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + MachineType: LENOVO 2519Y11 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=12cb61c8-5e8e-4182-9e7f-876650c6da04 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-40-generic N/A + linux-backports-modules-5.13.0-40-generic N/A + linux-firmware 1.187.29 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: focal + Uname: Linux 5.13.0-40-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 02/14/2013 + dmi.bios.release: 1.69 + dmi.bios.vendor: LENOVO + dmi.bios.version: 6IET85WW (1.45 ) + dmi.board.name: 2519Y11 + dmi.board.vendor: LENOVO + dmi.board.version: Not Available + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Not Available + dmi.ec.firmware.release: 1.24 + dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:br1.69:efr1.24:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: + dmi.product.family: ThinkPad T410 + dmi.product.name: 2519Y11 + dmi.product.version: ThinkPad T410 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1969897/+attachment/5582359/+files/AlsaInfo.txt -- 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: U
[Kernel-packages] [Bug 1968900] Re: linux-azure: Harmonize arm64 config settings with amd64
This bug is awaiting verification that the linux-azure/5.15.0-1005.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-jammy -- 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/1968900 Title: linux-azure: Harmonize arm64 config settings with amd64 Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: In Progress Status in linux-azure source package in Impish: In Progress Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Many arm64 config settings are unnecessarily different from amd64. [Test Case] Kernel regression test suite. [Where things could go wrong] Enabling or disabling config options may impact kernel behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1968900/+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 1969897] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1969897 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** 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/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1967579] Re: harden indirect calls against BHI attacks
This bug is awaiting verification that the linux-lowlatency/5.15.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1967579 Title: harden indirect calls against BHI attacks Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] Branch History Injection is made easier when all indirect calls are funneled through very few points where the retpolines were. By replacing the retpoline jumps by indirect calls whenever retpolines are disabled, BHI attacks are more difficult to execute as the BTB is not as fixed as before. [Fixes] Though there are fixes that allow retpoline,lfence to be directly replaced in the indirect calls, given that mitigation is not recommended for most of the situations, that hardening is not as important as the one that works for the spectre_v2=off option (the default one for systems with eIBRS). This latter one is present starting with 5.13, but backporting to 5.4 might be a good measure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967579/+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 1969897] Re: Battery report false in kernel 5.13.0-40-generic
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969897 Title: Battery report false in kernel 5.13.0-40-generic Status in linux package in Ubuntu: New Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969897/+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 1969897] [NEW] Battery report false in kernel 5.13.0-40-generic
You have been subscribed to a public bug: Description:Ubuntu 20.04.4 LTS Release:20.04 I think this is a power management, kernel and/or firmware issue. My laptop is old Lenovo T410. After recent updates my battery indicator shows a reduced percentage charge and reports is not charging. This is after booting into kernel 5.13.0-40-generic. If I reboot into kernel 5.13.0-39-generic the percentage charge does drop from 100% to 94% when unplugged. It reports that it is charging when plugged back in with an estimate of 14 minutes until full. This is what I would normally expect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.37 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 08:44:57 2022 InstallationDate: Installed on 2021-01-25 (451 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Battery report false in kernel 5.13.0-40-generic https://bugs.launchpad.net/bugs/1969897 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 1962349] Re: Bolt doesn't work with native USB4 hosts
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1962349 Title: Bolt doesn't work with native USB4 hosts Status in OEM Priority Project: New Status in bolt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in bolt source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in bolt source package in Impish: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] AMD Yellow Carp Host (issue this bug is about) -- * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` Alpine Ridge / Titan Ridge host (discrete controller) -- Start out on a host with discrete controller (Alpine Ridge or Titan Ridge) 1. sudo boltctl forget -a 2. Plug in dock 3. Make sure 'boltctl list' enumerates dock. 4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host) - If 0; try to manually enroll using 'boltctl enroll $UUID' - If 1; ensure that device automatically enrolled with bolt. GUI Check - Ensure that devices show up in the Settings GUI and are now able to authorize. Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization". [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. * There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. * I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962349/+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 1965496] Re: alsa: enable the cirrus-logic side-codec to make the speaker output sound
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965496 Title: alsa: enable the cirrus-logic side-codec to make the speaker output sound Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] We have a couple of lenovo latops models which have cirrus-logic side codec between realtek codec and speaker, it plays a role as amplifier, we need to enable this side-codec, otherwise the speaker can't output sound. [Fix] Backport codec patches and some i2c and acpi detection patches from mainline kernel and linux-next [Test] boot the patched kernel, run speaker test, both left and right channel could work well. [Where problems could occur] If it could introduce regression, it will be on soc wm_adsp codec drivers, since most of patch are adding new codec drivers, it will not touch existing codec drivers. If a machine with wm_adsp codec can't output sound or record sound, it means this SRU introduce the regression on wm_adsp driver, but this possibility is very low, since all patches are picked from mainline kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1965496/+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 1968892] Re: Micmute LED support for Zbook Fury 16 G9
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1968892 Title: Micmute LED support for Zbook Fury 16 G9 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] The audio mute key(F5) LED does not work. [Fix] Need this commit from v5.18-rc1 ce18f905a500 ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9 [Test] Verified on the target machine. [Where problems could occur] The modified hda_fixups, ALC245_FIXUP_CS35L41_SPI_2_HP_GPIO_LED, has the same contain as ALC245_FIXUP_CS35L41_SPI_2, but with new mic mute led gpio settings. So, if might affect the machines with the same chip ID that mic mute led is already working. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1968892/+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 1942160] Re: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: Fix Released Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux-oem-5.17 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] VMD PCI-E bridges on ADL-M/P/S use new device IDs and therefore not covered by previous LTR reset fix in bug 1896598. [Fix] Additional entires to vmd_bridge_tbl in drivers/pci/quirks.c is requierd: * ADL-M: [8086:464d] * ADL-P: [8086:51b0] * ADL-S: [8086:7ab4] [Test Case] $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' ... 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ [Where problems could occur] This will reset zeroed PCI_LTR_MAX_SNOOP_LAT and PCI_LTR_MAX_NOSNOOP_LAT values to a fixed 3145728ns that is used on Windows. Devices might want to set itself to a smaller value, but while this is not yet correctly supported by VMD controller driver, so the device power consumption might be little worse than ideal. [Other Info] VMD ASPM was first supported for Tiger Lake cpus, so all kernel versions newer than 5.6 should have already the supporting function. This patch targets Alder Lake cpus that are supported since 5.10-oem and on. == original bug report == * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384, https://bugs.launchpad.net/bugs/1896598. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdL
[Kernel-packages] [Bug 1956509] Re: Support AMD P-State cpufreq control mechanism
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1956509
Title:
Support AMD P-State cpufreq control mechanism
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
AMD P-State CPU performance scaling driver not yet supported on AMD Zen
based CPU series.
[Fix]
Mainline commits starting at commit d341db8f48ea ("x86/cpufeatures: Add
AMD Collaborative Processor Performance Control feature flag") from v5.17.
Even this committed, the defconfig will build it as module, and that
prevents AMD P-State driver from actually taking effect. Therefore an
additional fix to the kernel configs is necessary.
[Test Case]
$ sudo cpupower frequency-info
analyzing CPU 0:
driver: amd-pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 131 us
hardware limits: 400 MHz - 3.10 GHz
available cpufreq governors: conservative ondemand userspace powersave
performance schedutil
current policy: frequency should be within 1.60 GHz and 3.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 1.59 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3100MHz
Pstate-P1: 1800MHz
Pstate-P2: 1600MHz
[Where problems could occur]
The CPPC feature is implemented in two ways depending on underlying HW
details for the APU/CPU:
* Dedicated MSR
* Shared memory
The metrics used to measure power/performance efficiency don't show any
improvement on the designs that use shared memory. They do show
improvements in the MSR designs.
So the code will only enable it by default on the MSR implementation.
[Other Info]
Althought the v5.17 kernel and newer should have already this committed,
an additional fix to the kernel configs is necessary, and
unstable/oem-5.17 are also nominated (in a separate thread for they don't
need other parts but the config).
== original bug report ==
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-
pm.git/commit/?h=linux-
next&id=40181d67f1e9f1ac87af9c0c194e40ab2a081974
$ sudo cpupower frequency-info
analyzing CPU 0:
driver: amd-pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 131 us
hardware limits: 400 MHz - 3.10 GHz
available cpufreq governors: conservative ondemand userspace powersave
performance schedutil
current policy: frequency should be within 1.60 GHz and 3.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 1.59 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3100MHz
Pstate-P1: 1800MHz
Pstate-P2: 1600MHz
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1956509/+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 1967986] Re: Fix ADL, WD22TB4, Dual monitors display resolution can't reach 4K 60hz
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1967986 Title: Fix ADL, WD22TB4,Dual monitors display resolution can't reach 4K 60hz Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: New Bug description: [Impact] SUT attach WD22TB4 dock, plug in two 4K monitor, the monitor resolution can't reach 4K 60Hz [Fix] Fix maximum DP source rate. this patch should be taken first, 73867c8709) drm/i915/display: Remove check for low voltage sku for max dp source rate Then, on U/J/OEM-5.14, apply 3fd6afb623ba) drm/i915/intel_combo_phy: Print I/O voltage info, [Test Case] 1. Connect two 4K external monitor to WD22TB4 2. the monitor resolution can reach 4K 60Hz [Where problems could occur] Low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967986/+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 1968016] Re: Use kernel-testing repo from launchpad for ADT tests
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1968016 Title: Use kernel-testing repo from launchpad for ADT tests Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux-oem-5.14 source package in Trusty: Invalid Status in linux-oem-5.17 source package in Trusty: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-oem-5.14 source package in Xenial: Invalid Status in linux-oem-5.17 source package in Xenial: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux-oem-5.17 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: In ADT tests, we are still using the kernel-testing repo from kernel.ubuntu.com, it should be migrated to launchpad instead to align with our other testing repos. For autotest-client-tests repo change, it will needs to be handled in the kernel-testing repo directly, see bug 1968257. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968016/+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 1968475] Re: Fix broken HDMI audio on AMD PRO VII after S3
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1968475 Title: Fix broken HDMI audio on AMD PRO VII after S3 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] DP/HDMI audio on AMD PRO VII stops working after S3. [Fix] Ensure HDA function is suspended before ASIC reset so the subsequent resume can be carried out successfully. [Test] With the patch applied, DP/HDMI audio continues to work after S3. [Where problems could occur] The suspend_noirq phase should not trigger any interrupt, so if amdgpu_asic_reset() somehow raised IRQ, it can break the system. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1968475/+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
Re: [Kernel-packages] [Bug 1930925] Re: Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but 18.04 does)
Is there a set of builds between 19.04 and 19.10 that I could binary chop through? This would allow a developer to narrow down where the bug was introduced. Checking a build takes about half an hour, so if there were say one per day between April 2019 and October 2019, that would require 0.5 * log2 (180) hours, ie about 4 hours. Jon Thackray j...@pobox.com 0044 1223 276500 (home) 0044 7803 017991 (mobile) 0033 423354068 (France) -- Original Message -- From: "Daniel van Vugt" <1930...@bugs.launchpad.net> To: j...@pobox.com Sent: 22/04/2022 03:00:03 Subject: [Bug 1930925] Re: Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but 18.04 does) >** Tags added: jammy > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1930925 > >Title: > Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but > 18.04 does) > >Status in linux package in Ubuntu: > Confirmed > >Bug description: > I have recently acquired a acquired a desktop running ubuntu 20.04. I > have several computers and switch between them using this KVM >https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 > The other machines are either running windows or ubuntu 18.04 or > earlier. They are all fine, but the with 20.04 machine neither the > keyboard nor the mouse works. On the 18.04 machine I can see > > lsusb > Bus 002 Device 002: ID 8087:8000 Intel Corp. > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 002: ID 8087:8008 Intel Corp. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > and it is the Logitech, Inc. Unifying Receiver which appears when the > USB from the KVM is connected. On the 20.04 machine only this appears > > lsusb > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller > Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > I have tested installation discs from 19.04 onwards. The failure first > appears in 19.10 and is still present in 21.04 > > I can observe a similar problem with a dual boot laptop running > windows 10 and 20.04. With windows 10 I can use it with the KVM for > screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and > mouse do not work. This issue has also been observed here >https://unix.stackexchange.com/questions/646515/using-logitech-mouse- > keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed > it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). > > I had to report this originally against xorg as this bug reporting > system seems not to allow reporting of bugs against unknown packages. > I also had to report it through the ubuntu-bug executable as I've been > unable to find a way in launchpad of reporting a bug (as opposed to > getting a guided tour about reporting bugs). > > I am happy to supply more info and test fixes if I am asked but as > with this type of bug where something fails to happen rather than > something wrong happens I don't know what to look at. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-53-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > Date: Fri Jun 4 20:21:15 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DpkgLog: > > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. Device [1043:8694] > InstallationDate: Installed on 2021-05-14 (21 days ago) > InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 > (20210209.1) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller >Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Lsusb-t: >/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M >/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M >|__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M >|__ Port 13: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M >|__ Port 13: Dev 3, If 2, Class=H
[Kernel-packages] [Bug 1956509] Re: Support AMD P-State cpufreq control mechanism
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1956509
Title:
Support AMD P-State cpufreq control mechanism
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
AMD P-State CPU performance scaling driver not yet supported on AMD Zen
based CPU series.
[Fix]
Mainline commits starting at commit d341db8f48ea ("x86/cpufeatures: Add
AMD Collaborative Processor Performance Control feature flag") from v5.17.
Even this committed, the defconfig will build it as module, and that
prevents AMD P-State driver from actually taking effect. Therefore an
additional fix to the kernel configs is necessary.
[Test Case]
$ sudo cpupower frequency-info
analyzing CPU 0:
driver: amd-pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 131 us
hardware limits: 400 MHz - 3.10 GHz
available cpufreq governors: conservative ondemand userspace powersave
performance schedutil
current policy: frequency should be within 1.60 GHz and 3.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 1.59 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3100MHz
Pstate-P1: 1800MHz
Pstate-P2: 1600MHz
[Where problems could occur]
The CPPC feature is implemented in two ways depending on underlying HW
details for the APU/CPU:
* Dedicated MSR
* Shared memory
The metrics used to measure power/performance efficiency don't show any
improvement on the designs that use shared memory. They do show
improvements in the MSR designs.
So the code will only enable it by default on the MSR implementation.
[Other Info]
Althought the v5.17 kernel and newer should have already this committed,
an additional fix to the kernel configs is necessary, and
unstable/oem-5.17 are also nominated (in a separate thread for they don't
need other parts but the config).
== original bug report ==
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-
pm.git/commit/?h=linux-
next&id=40181d67f1e9f1ac87af9c0c194e40ab2a081974
$ sudo cpupower frequency-info
analyzing CPU 0:
driver: amd-pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 131 us
hardware limits: 400 MHz - 3.10 GHz
available cpufreq governors: conservative ondemand userspace powersave
performance schedutil
current policy: frequency should be within 1.60 GHz and 3.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 1.59 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3100MHz
Pstate-P1: 1800MHz
Pstate-P2: 1600MHz
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1956509/+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 1969326] Re: Enable hotspot feature for Realtek 8821CE
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1969326 Title: Enable hotspot feature for Realtek 8821CE Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The wifi hotspot doesn't work without the fix. [Fix] Realtek provides us the patches to add this feature which are still in linux-next. https://patchwork.kernel.org/project/linux-wireless/cover/20220407095858.46807-1-pks...@realtek.com/ ece31c93d4d6 rtw88: 8821c: fix debugfs rssi value f5207c122102 rtw88: do PHY calibration while starting AP f1c4dabfe68d rtw88: 8821c: Enable TX report for management frames f2217968ffda rtw88: Add update beacon flow for AP mode 6723c0cde84f rtw88: fix incorrect frequency reported c1edc86472fc rtw88: add ieee80211:sta_rc_update ops Realtek provides us another series of patches for 5.14, and it contains 5 commits, we'd verified this series of patches. [Test] Verified on the Realtek 8821CE card. [Where problems could occur] The patches are introducing new interfaces, I think it only has minimal impact to the origin behaviors. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969326/+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 1968861] Re: Support Cirrus audio codec configurations for Odin platform
** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1968861 Title: Support Cirrus audio codec configurations for Odin platform Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [Impact] CS8409 needs new configuration for Odin platform [Fix] Cirrus provides us 2 patches to add the support which are not in upstream yet ALSA: hda/cs8409: Add Speaker Playback Switch for Cyborg ALSA: hda/cs8409: Support new Odin Variants Below series of patch is required to be applied before these 2. https://lists.ubuntu.com/archives/kernel-team/2022-April/129223.html [Test] Verified on the target machine [Where problems could occur] The first commit only affects the new added Odin platform, and the second one do some modification for other platforms which is hard to know what may lead to. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1968861/+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 1969181] Re: [SRU][OEM-5.14] Fix iwlwifi iwl-nvm-parse.c warning
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1969181 Title: [SRU][OEM-5.14] Fix iwlwifi iwl-nvm-parse.c warning Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] With Intel wifi card [8086:51f0], boot with oem-5.14.0-1027+, the warning will be shown: Mar 14 23:30:36 Phoenix-1 kernel: Call Trace: Mar 14 23:30:36 Phoenix-1 kernel: Mar 14 23:30:36 Phoenix-1 kernel: iwl_mvm_get_regdomain+0xe2/0x1d0 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: iwl_mvm_get_current_regdomain+0x4c/0x50 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: iwl_mvm_init_mcc+0x81/0x1d0 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: ? iwl_acpi_get_dsm_u32+0x2f/0x60 [iwlwifi] Mar 14 23:30:36 Phoenix-1 kernel: iwl_mvm_up+0x87a/0xd70 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: __iwl_mvm_mac_start+0x2b/0x190 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: iwl_mvm_mac_start+0x50/0xb0 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: drv_start+0x40/0xd0 [mac80211] Mar 14 23:30:36 Phoenix-1 kernel: ieee80211_do_open+0x394/0x810 [mac80211] Mar 14 23:30:36 Phoenix-1 kernel: ieee80211_open+0x6c/0x90 [mac80211] [Fix] This warning is introduced by commit: commit 827b84824ef2d910930c9974765de592e77b5072 Author: Chia-Lin Kao (AceLan) Date: Wed Feb 23 18:40:13 2022 +0800 UBUNTU: SAUCE: iwlwifi: disable 6-7 GHz channels BugLink: https://bugs.launchpad.net/bugs/1961971 Disable UHB (ultra high band) channels on all AX210/AX211 cards Signed-off-by: Chia-Lin Kao (AceLan) Signed-off-by: Timo Aaltonen Replace the warning to debug info to avoid the error message. [Test] Verified on HW with Intel wifi card, no errors after boot. [Where problems could occur] It may break Intel wifi driver. Change the debug info only, it's unlikely. The issue is on oem-5.14 only, no need for other kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969181/+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 1969771] Re: Fix beacon loss for rtl8821ce on certain platforms
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1969771 Title: Fix beacon loss for rtl8821ce on certain platforms Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Incomplete Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] On the intel ADL-U platform, the rtl8821ce suffers the beacon loss frequently because the driver doesn't received any beacon from AP. It causes the wpa-supplicant to reconnect again and again. Given it's critical to user experience and the urgent schedule, we need to SRU before getting approval. [Fix] Realtek release a fix to disable the PCI completion timeout on rtl8821ce so the PCI bus won't get stuck and can handed the received packets to the driver correctly. [Test Case] 1. Connect the WiFi to internet by selecting a internet connected AP 2. ping 8.8.8.8 to check the internet connectivity for at least 5 minutes. 3. Make sure no 'CTRL-EVENT-BEACON-LOSS' event reported from wpa_supplicant [Where problems could occur] Risk should be Low. It's only applied for RTL8821CE to disable the completion timeout capability. == Original Bug Description == [Summary] Wireless keeps connection and loses connection repeatedly. Below test cases are failed: - wireless/wireless_connection_wpa_n_nm_wlp3s0 - after-suspend-wireless/wireless_connection_wpa_bg_nm_wlp3s0 - after-suspend-wireless/wireless_connection_wpa_ac_nm_wlp3s0 - after-suspend-wireless/wireless_connection_open_n_nm_wlp3s0 - after-suspend-wireless/wireless_connection_open_bg_nm_wlp3s0 - after-suspend-wireless/wireless_connection_open_ac_nm_wlp3s0 Issue is also observed on WVA4-DVT2-C1 [Steps to reproduce] 1. Boot into OS 2. Connect network by wireless 3. Run 'sudo apt update' [Expected result] Wireless connection won't break [Actual result] Wireless loses the connection and then connect network, after a while, issue happens again. [Failure rate] 10/10 [Additional information] CID: 202202-29949, 202202-29947 SKU: WMVA5-DVT2-C1, WVA4-DVT2-C1 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-olly-adl+X175 system-manufacturer: Dell Inc. system-product-name: Vostro 3520 bios-version: 0.5.4 CPU: 12th Gen Intel(R) Core(TM) i5-1235U (12x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4628] (rev 0c) :01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f9f] (rev a1) kernel-version: 5.14.0-1024-oem [Stage] Issue reported and logs collected at a later stage To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969771/+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 1968861] Re: Support Cirrus audio codec configurations for Odin platform
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1968861 Title: Support Cirrus audio codec configurations for Odin platform Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] CS8409 needs new configuration for Odin platform [Fix] Cirrus provides us 2 patches to add the support which are not in upstream yet ALSA: hda/cs8409: Add Speaker Playback Switch for Cyborg ALSA: hda/cs8409: Support new Odin Variants Below series of patch is required to be applied before these 2. https://lists.ubuntu.com/archives/kernel-team/2022-April/129223.html [Test] Verified on the target machine [Where problems could occur] The first commit only affects the new added Odin platform, and the second one do some modification for other platforms which is hard to know what may lead to. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1968861/+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 1969892] [NEW] Focal update: upstream stable patchset 2022-04-22
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-04-22 from git://git.kernel.org/ ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1969892 Title: Focal update: upstream stable patchset 2022-04-22 Status in linux-oem-5.14 package in Ubuntu: Confirmed Status in linux-oem-5.14 source package in Focal: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-04-22 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1969892/+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 1942624] Re: NVMe devices fail to probe due to ACPI power state change
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-oem-5.14 (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942624 Title: NVMe devices fail to probe due to ACPI power state change Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] * Specific NVMe devices fail to probe and become unusable after boot * Caused by an ACPI regression that doesn't correctly handle power states * Upstream regression commit: 7e4fdeafa61f ACPI: power: Turn off unused power resources unconditionally * Regression window for Ubuntu kernels includes 5.13 and 5.14 [Test Plan] * Boot affected kernel and validate whether NVMe device is usable * Check kernel logs for failed probe message: "can't change power state from D3Cold to D0 (config space inaccessible)" [Fix] * Fixed by not turning off power resources in unknown state * Fix was introduced by commit: bc2836859643 ACPI: PM: Do not turn off power resources in unknown state * Kernels starting with 5.15 (e.g. Jammy) not affected, as they already contain the fix above [Regression Potential] * NVMe devices continue failing to probe * Other devices become unusable after power state changes * Further regressions would affect power state of devices, possibly after boot -- [Original Description] NVME "can't change power state from D3Cold to D0 (config space inaccessible)" Bug with kernels after version 5.11.0-18 on Lenovo Ideapad 330-15ICH. The NVME drive with my root partition cannot be mounted at boot with an error "can't change power state from D3Cold to D0 (config space inaccessible)". I'm willing to help find a root cause if I don't need to spent too many hours. All Ubuntu kernels after 5.11.0-18 exhibit this bug, but I could boot properly with the official linux kernel 5.13.0. Thanks a lot for your help ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7503 F pulseaudio /dev/snd/pcmC0D0p: chris 7503 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 18:46:35 2021 InstallationDate: Installed on 2019-07-17 (779 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc EasyCamera Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 007: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9d963312-3a16-428d-8efd-f1323c6528f1 ro quiet nosplash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-03 (92 days ago) dmi.bios.date: 10/24/2018 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN29WW 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 ideapad 330-15ICH dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr7ZCN29WW:bd10/24/2018:br1.29:efr1.29:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942624/+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
