[Kernel-packages] [Bug 1933617] Re: [ADL-S] Broken PMU hardware detected, using software events only.
SRU: https://lists.ubuntu.com/archives/kernel-team/2021-July/122353.html (impish, oem-5.13) -- 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/1933617 Title: [ADL-S] Broken PMU hardware detected, using software events only. Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: In Progress Bug description: [Summary] Broken PMU hardware detected, using software events on log 04 16:04:26 u-Inspiron kernel: Broken PMU hardware detected, using software events only. 04 16:04:26 u-Inspiron kernel: Failed to access perfctr msr (MSR 18e is ) 04 16:04:26 u-Inspiron kernel: rcu: Hierarchical SRCU implementation. 04 16:04:26 u-Inspiron kernel: NMI watchdog: Perf NMI watchdog permanently disabled 04 16:04:26 u-Inspiron kernel: smp: Bringing up secondary CPUs ... 04 16:04:26 u-Inspiron kernel: x86: Booting SMP configuration: [Reproduce Steps] 1. Boot to Ubuntu with 5.13 kernel 2. Intel PMU driver report Broken HW detected 3. journalctl -k [Results] Expected: PMU hardware works normally Actual: PMU borken hardware detected -- Upstream bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=213443 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933617/+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 1928405] Re: mkdir/rm/sleep/ls causes kernel 'BUG: unable to handle kernel paging request'
[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/1928405 Title: mkdir/rm/sleep/ls causes kernel 'BUG: unable to handle kernel paging request' Status in linux package in Ubuntu: Expired Bug description: I have a network of stock 16.04.2 LTS (Xenial Xerus) servers with entirely unmodified "4.4.0-62-generic #83-Ubuntu" kernel running on a private network; they run telemetry programs, mostly sh/php out of crontab, with very light user interaction for configuration via apache and extremely occasional adminstrator ssh access. They all are on the same hardware: same motherboard, same amount of RAM, vary similar very small SATA SSD disks. A recent fault made us examine the logs, and we see that since 2017 about half a dozen servers are reporting kernel bugs about once a month. BUG: unable to handle kernel paging request at 88032fc00062 CPU: 0 PID: 26071 Comm: mkdir Not tainted 4.4.0-62-generic #83-Ubuntu The details vary. The most common command is mkdir, but also rm, head, basename, ls, sleep. (There are every-minute cronjobs sh-scripts which run these commands.) About half of the logs show tainted (G, D) and have untainted. I have found no pattern with time of day, uptime, load (0.16, 0.22, 0.25 for following report), day of week. This is a typical syslog entry, from 2021-01-29; it has the same issue in March and May (Comm: mkdir, but tainted G D). Jan 29 19:50:17 hostname kernel: [2315584.884470] BUG: unable to handle kernel paging request at 88042fc80062 Jan 29 19:50:17 hostname kernel: [2315584.884500] IP: [] __inc_zone_state+0x19/0x60 Jan 29 19:50:17 hostname kernel: [2315584.884524] PGD 220b067 PUD 0 Jan 29 19:50:17 hostname kernel: [2315584.884538] Oops: 0002 [#1] SMP Jan 29 19:50:17 hostname kernel: [2315584.884552] Modules linked in: ppdev snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel coretemp snd_hda_codec serio_raw snd_hda_core snd_hwdep snd_pcm snd_timer snd lpc_ich shpchp soundcore parport_pc mac_hid 8250_fintek parport ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear psmouse ahci e1000e libahci ptp pps_core video fjes Jan 29 19:50:17 hostname kernel: [2315584.884744] CPU: 1 PID: 10730 Comm: mkdir Not tainted 4.4.0-62-generic #83-Ubuntu Jan 29 19:50:17 hostname kernel: [2315584.884760] Hardware name: /PD11TI, BIOS MTCDT10N.85T.0201.2014.1209.1030 12/09/2014 Jan 29 19:50:17 hostname kernel: [2315584.884779] task: 880034c13fc0 ti: 8800c8838000 task.ti: 8800c8838000 Jan 29 19:50:17 hostname kernel: [2315584.884795] RIP: 0010:[] [] __inc_zone_state+0x19/0x60 Jan 29 19:50:17 hostname kernel: [2315584.884816] RSP: :8800c883bc28 EFLAGS: 00010203 Jan 29 19:50:17 hostname kernel: [2315584.884842] RAX: 0001 RBX: ea000285d540 RCX: 0002 Jan 29 19:50:17 hostname kernel: [2315584.884878] RDX: 00030062 RSI: 0021 RDI: ea000285d540 Jan 29 19:50:17 hostname kernel: [2315584.884915] RBP: 8800c883bc28 R08: 81cd2dc4 R09: 81cd2db3 Jan 29 19:50:17 hostname kernel: [2315584.884951] R10: R11: 81cd2da2 R12: 88012fff7f80 Jan 29 19:50:17 hostname kernel: [2315584.884987] R13: 0080 R14: ea000285d500 R15: 88012fff77c0 Jan 29 19:50:17 hostname kernel: [2315584.885027] FS: 7fa2813a1800() GS:88012fc8() knlGS: Jan 29 19:50:17 hostname kernel: [2315584.885065] CS: 0010 DS: ES: CR0: 80050033 Jan 29 19:50:17 hostname kernel: [2315584.885088] CR2: 88042fc80062 CR3: 34f1 CR4: 06e0 Jan 29 19:50:17 hostname kernel: [2315584.885125] Stack: Jan 29 19:50:17 hostname kernel: [2315584.885144] 8800c883bcf0 811af98d 88012fff96c0 0001df4d6b62 Jan 29 19:50:17 hostname kernel: [2315584.885186] 880035327a10 880035327a00 8800c97a7628 8800c97a7628 Jan 29 19:50:17 hostname kernel: [2315584.885227] df4d6b62 880035327a00 88012fff96d0 Jan 29 19:50:17 hostname kernel: [2315584.885269] Call Trace: Jan 29 19:50:17 hostname kernel: [2315584.885296] [] zone_statistics+0x5d/0xa0 Jan 29 19:50:17 hostname kernel: [2315584.885324] [] __alloc_pages_nodemask+0x159/0x2a0 Jan 29 19:50:17 hostname kernel: [2315584.885355] [] alloc_pages_vma+0xbe/0x240 Jan 29 19:50:17 hostname kernel: [2315584.885383] []
[Kernel-packages] [Bug 1933617] Re: [ADL-S] Broken PMU hardware detected, using software events only.
Second thought. While there are still a few fixes for this issue not yet applied to linux-5.13 stable, nor on 5.13-oem/generic, so I think it's necessary to get this fixed first before new production grade hw becoming available. ** Changed in: hwe-next Status: Won't Fix => In Progress ** Changed in: linux-oem-5.13 (Ubuntu) Status: Won't Fix => In Progress ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Won't Fix => In Progress ** Changed in: linux-oem-5.13 (Ubuntu) Status: In Progress => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-5.13 (Ubuntu) Assignee: You-Sheng Yang (vicamo) => (unassigned) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/1933617 Title: [ADL-S] Broken PMU hardware detected, using software events only. Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: In Progress Bug description: [Summary] Broken PMU hardware detected, using software events on log 04 16:04:26 u-Inspiron kernel: Broken PMU hardware detected, using software events only. 04 16:04:26 u-Inspiron kernel: Failed to access perfctr msr (MSR 18e is ) 04 16:04:26 u-Inspiron kernel: rcu: Hierarchical SRCU implementation. 04 16:04:26 u-Inspiron kernel: NMI watchdog: Perf NMI watchdog permanently disabled 04 16:04:26 u-Inspiron kernel: smp: Bringing up secondary CPUs ... 04 16:04:26 u-Inspiron kernel: x86: Booting SMP configuration: [Reproduce Steps] 1. Boot to Ubuntu with 5.13 kernel 2. Intel PMU driver report Broken HW detected 3. journalctl -k [Results] Expected: PMU hardware works normally Actual: PMU borken hardware detected -- Upstream bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=213443 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933617/+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 1935892] Re: OEM 5.6 kernel is now transited to 5.10 but pre-signed nvidia is not and cause no nvidia driver after oem kernel transition
** Tags added: oem-priority originate-from-1935814 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1935892 Title: OEM 5.6 kernel is now transited to 5.10 but pre-signed nvidia is not and cause no nvidia driver after oem kernel transition Status in OEM Priority Project: New Status in linux-restricted-modules-oem-5.6 package in Ubuntu: New Bug description: If end user install nvidia driver using 20.04.2 stock image without connecting network and they will get the 5.6 oem kernel + 5.6 nvidia driver (linux-modules-nvidia-*). After the installation, the user will get 5.10 kernel + nvidia pre- signed 5.6 driver after dist-upgrade. It will cause there is no nvidia driver in the system. Below shows the candidates packages: # apt policy linux-oem-20.04 linux-oem-20.04: Installed: (none) Candidate: 5.10.0.1034.35 Version table: 5.10.0.1034.35 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 5.10.0.1033.34 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 5.6.0.1007.7 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages # apt policy linux-modules-nvidia-460-oem-20.04 linux-modules-nvidia-460-oem-20.04: Installed: (none) Candidate: 5.6.0-1056.60 Version table: 5.6.0-1056.60 500 500 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1935892/+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 1935754] Re: [HP EliteBook 850 G6] laptop brightness hotkey after latest update
yes I did it when I was checking it -- 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/1935754 Title: [HP EliteBook 850 G6] laptop brightness hotkey after latest update Status in linux package in Ubuntu: New Bug description: Hello! After recent update I have a problem brightness laptop button are turning my mic off instead of reduce or high it Could you fix it please? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4.2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 21:32:04 2021 InstallationDate: Installed on 2020-04-08 (458 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP EliteBook 850 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=78466619-ba7c-4459-92c2-58fc31c658f2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-15 (86 days ago) dmi.bios.date: 09/12/2019 dmi.bios.release: 3.0 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.03.00 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.52.00 dmi.chassis.asset.tag: 5CG9450KGR dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.82 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.03.00:bd09/12/2019:br3.0:efr82.82:svnHP:pnHPEliteBook850G6:pvr:rvnHP:rn8549:rvrKBCVersion52.52.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G6 dmi.product.sku: 7KP17EA#ACB dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 94:E6:F7:2D:22:F5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:21793 acl:0 sco:0 events:3343 errors:0 TX bytes:796729 acl:0 sco:0 commands:3321 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935754/+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 1935892] [NEW] OEM 5.6 kernel is now transited to 5.10 but pre-signed nvidia is not and cause no nvidia driver after oem kernel transition
Public bug reported: If end user install nvidia driver using 20.04.2 stock image without connecting network and they will get the 5.6 oem kernel + 5.6 nvidia driver (linux-modules-nvidia-*). After the installation, the user will get 5.10 kernel + nvidia pre- signed 5.6 driver after dist-upgrade. It will cause there is no nvidia driver in the system. Below shows the candidates packages: # apt policy linux-oem-20.04 linux-oem-20.04: Installed: (none) Candidate: 5.10.0.1034.35 Version table: 5.10.0.1034.35 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 5.10.0.1033.34 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 5.6.0.1007.7 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages # apt policy linux-modules-nvidia-460-oem-20.04 linux-modules-nvidia-460-oem-20.04: Installed: (none) Candidate: 5.6.0-1056.60 Version table: 5.6.0-1056.60 500 500 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages ** Affects: linux-restricted-modules-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Description changed: If end user install nvidia driver using 20.04.2 stock image without connecting network and they will get the 5.6 oem kernel + 5.6 nvidia driver (linux-modules-nvidia-*). After the installation, the user will get 5.10 kernel + nvidia pre- signed 5.6 driver after dist-upgrade. It will cause there is no nvidia driver in the system. + Below shows the candidates packages: + # apt policy linux-oem-20.04 linux-oem-20.04: - Installed: (none) - Candidate: 5.10.0.1034.35 - Version table: - 5.10.0.1034.35 500 - 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages - 5.10.0.1033.34 500 - 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages - 5.6.0.1007.7 500 - 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages + Installed: (none) + Candidate: 5.10.0.1034.35 + Version table: + 5.10.0.1034.35 500 + 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages + 5.10.0.1033.34 500 + 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages + 5.6.0.1007.7 500 + 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages # apt policy linux-modules-nvidia-460-oem-20.04 linux-modules-nvidia-460-oem-20.04: - Installed: (none) - Candidate: 5.6.0-1056.60 - Version table: - 5.6.0-1056.60 500 - 500 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages - 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages + Installed: (none) + Candidate: 5.6.0-1056.60 + Version table: + 5.6.0-1056.60 500 + 500 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages + 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1935892 Title: OEM 5.6 kernel is now transited to 5.10 but pre-signed nvidia is not and cause no nvidia driver after oem kernel transition Status in linux-restricted-modules-oem-5.6 package in Ubuntu: New Bug description: If end user install nvidia driver using 20.04.2 stock image without connecting network and they will get the 5.6 oem kernel + 5.6 nvidia driver (linux-modules-nvidia-*). After the installation, the user will get 5.10 kernel + nvidia pre- signed 5.6 driver after dist-upgrade. It will cause there is no nvidia driver in the system. Below shows the candidates packages: # apt policy linux-oem-20.04 linux-oem-20.04: Installed: (none) Candidate: 5.10.0.1034.35 Version table: 5.10.0.1034.35 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 5.10.0.1033.34 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 5.6.0.1007.7 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages # apt policy linux-modules-nvidia-460-oem-20.04 linux-modules-nvidia-460-oem-20.04: Installed: (none) Candidate: 5.6.0-1056.60 Version table: 5.6.0-1056.60 500 500 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-oem-5.6/+bug/1935892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1935754] Re: [HP EliteBook 850 G6] laptop brightness hotkey after latest update
Please run this command in a terminal: uname -a to verify you are really running 5.11.0-16.17 -- 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/1935754 Title: [HP EliteBook 850 G6] laptop brightness hotkey after latest update Status in linux package in Ubuntu: New Bug description: Hello! After recent update I have a problem brightness laptop button are turning my mic off instead of reduce or high it Could you fix it please? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4.2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 21:32:04 2021 InstallationDate: Installed on 2020-04-08 (458 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP EliteBook 850 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=78466619-ba7c-4459-92c2-58fc31c658f2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-15 (86 days ago) dmi.bios.date: 09/12/2019 dmi.bios.release: 3.0 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.03.00 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.52.00 dmi.chassis.asset.tag: 5CG9450KGR dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.82 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.03.00:bd09/12/2019:br3.0:efr82.82:svnHP:pnHPEliteBook850G6:pvr:rvnHP:rn8549:rvrKBCVersion52.52.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G6 dmi.product.sku: 7KP17EA#ACB dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 94:E6:F7:2D:22:F5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:21793 acl:0 sco:0 events:3343 errors:0 TX bytes:796729 acl:0 sco:0 commands:3321 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935754/+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 1935754] Re: [HP EliteBook 850 G6] laptop brightness hotkey after latest update
I've checked this kernel version 5.11.0-16.17 and it didn't fix the problem -- 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/1935754 Title: [HP EliteBook 850 G6] laptop brightness hotkey after latest update Status in linux package in Ubuntu: New Bug description: Hello! After recent update I have a problem brightness laptop button are turning my mic off instead of reduce or high it Could you fix it please? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4.2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 21:32:04 2021 InstallationDate: Installed on 2020-04-08 (458 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP EliteBook 850 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=78466619-ba7c-4459-92c2-58fc31c658f2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-15 (86 days ago) dmi.bios.date: 09/12/2019 dmi.bios.release: 3.0 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.03.00 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.52.00 dmi.chassis.asset.tag: 5CG9450KGR dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.82 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.03.00:bd09/12/2019:br3.0:efr82.82:svnHP:pnHPEliteBook850G6:pvr:rvnHP:rn8549:rvrKBCVersion52.52.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G6 dmi.product.sku: 7KP17EA#ACB dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 94:E6:F7:2D:22:F5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:21793 acl:0 sco:0 events:3343 errors:0 TX bytes:796729 acl:0 sco:0 commands:3321 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935754/+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 1934878] Re: Mute/mic LEDs no function on some HP platfroms
** Changed in: linux-oem-5.10 (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.10 in Ubuntu. https://bugs.launchpad.net/bugs/1934878 Title: Mute/mic LEDs no function on some HP platfroms Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on 1) HP ProBook 630 G8 Notebook PC 2) HP ProBook 445 G8 Notebook PC 3) HP ProBook 450 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934878/+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 1933752] Re: [Lenovo Legion 5 15ARH05] Touchpad + brightness
Ubuntu 20.10 will be EOL this month (https://wiki.ubuntu.com/Releases) Please try 21.04 and report bugs if the problem persists. -- 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/1933752 Title: [Lenovo Legion 5 15ARH05] Touchpad + brightness Status in linux package in Ubuntu: New Bug description: Touchpad not work Cant change brightness ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-59-generic 5.8.0-59.66 ProcVersionSignature: Ubuntu 5.8.0-59.66-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: prometheus 4120 F pulseaudio /dev/snd/controlC0: prometheus 4120 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 27 14:33:32 2021 InstallationDate: Installed on 2021-06-05 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=76FC4166FC4121AB loop=/hostname/disks/root.disk ro ipv6.disable=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-59-generic N/A linux-backports-modules-5.8.0-59-generic N/A linux-firmware1.190.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55756 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933752/+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 1935880] Re: lxc c2-m2 focal VM causes KVM internal error during PCI init
I filed this issue on the kernel because it initially appeared to follow the host kernel version. While it's very reproducible w/ v5.4, I wasn't able to reproduce it with v5.8 or v5.7. However, I've now found that was a false negative - it is still reproducible with v5.13, so the kernel may not be the correct component. -- 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/1935880 Title: lxc c2-m2 focal VM causes KVM internal error during PCI init Status in linux package in Ubuntu: Confirmed Bug description: Launching a 2 CPU 2G VM with lxc often cause a KVM internal error during boot. Reproducer: lxc launch ubuntu:20.04 dannf-test2 -t c2-m2 --vm QEMU will report a KVM internal error: KVM internal error. Suberror: 3 extra data[0]: 80ec extra data[1]: 31 extra data[2]: 81 extra data[3]: 3 RAX= RBX=0001 RCX=0001 RDX=021e RSI=88807851cba8 RDI=0001 RBP=c9077e90 RSP=c9077e78 R8 =29417eca R9 = R10=0400 R11=0400 R12=0001 R13=8880001c8c80 R14= R15= RIP=81757a74 RFL=0246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 00c0 CS =0010 00a09b00 DPL=0 CS64 [-RA] SS = 00c0 DS = 00c0 FS = 00c0 GS = 88807850 00c0 LDT= 00c0 TR =0040 fe036000 206f 8b00 DPL=0 TSS64-busy GDT= fe034000 007f IDT= fe00 0fff CR0=80050033 CR2= CR3=0240a000 CR4=001006a0 DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER=0d01 Code=00 85 c0 7e 07 0f 00 2d 16 93 4b 00 fb f4 8b 05 14 61 78 00 <65> 44 8b 25 b4 86 8b 7e 85 c0 0f 8f 85 00 00 00 5b 41 5c 41 5d 5d c3 65 8b 05 9e 86 8b 7e The last lines on the console: acpi PNP0A08:00: _OSC: OS supports [ASPM ClockPM Segments MSI HPX-Type3] acpi PNP0A08:00: _OSC: not requesting OS control; OS requires [ExtendedConfig ASPM ClockPM MSI] PCI host bridge to bus :00 pci_bus :00: root bus resource [io 0x-0x0cf7 window] pci_bus :00: root bus resource [io 0x0d00-0x window] pci_bus :00: root bus resource [mem 0x000a-0x000b window] pci_bus :00: root bus resource [mem 0x7a10-0xafff window] pci_bus :00: root bus resource [mem 0xc000-0xfebf window] pci_bus :00: root bus resource [mem 0x8-0xf window] pci_bus :00: root bus resource [bus 00-ff] pci :00:00.0: [8086:29c0] type 00 class 0x06 pci :00:01.0: [1b36:000c] type 01 class 0x060400 pci :00:01.0: reg 0x10: [mem 0xc1245000-0xc1245fff] pci :00:01.1: [1b36:000c] type 01 class 0x060400 pci :00:01.1: reg 0x10: [mem 0xc1244000-0xc1244fff] pci :00:01.2: [1b36:000c] type 01 class 0x060400 pci :00:01.2: reg 0x10: [mem 0xc1243000-0xc1243fff] pci :00:01.3: [1b36:000c] type 01 class 0x060400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935880/+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 1935880] Re: lxc c2-m2 focal VM causes KVM internal error during PCI init
I attached gdb to the VM[*] and retrieved the following backtrace from
the guest kernel:
(gdb) bt full
#0 pci_conf1_read (seg=, bus=, devfn=, reg=16, len=4, value=0xc901fa0c) at
/home/dannf/linux-kvm-5.4.0/arch/x86/pci/direct.c:35
flags = 582
__dummy =
__dummy2 =
__dummy =
__dummy2 =
#1 0x815a1964 in raw_pci_read (domain=, bus=, devfn=, reg=, len=,
val=) at /home/dannf/linux-kvm-5.4.0/arch/x86/pci/common.c:46
No locals.
#2 0x815a19a7 in pci_read (bus=, devfn=,
where=, size=, value=) at
/home/dannf/linux-kvm-5.4.0/arch/x86/include/asm/pci.h:45
No locals.
#3 0x8144f4c5 in pci_bus_read_config_dword (bus=,
devfn=, pos=, value=0xc901fa58) at
/home/dannf/linux-kvm-5.4.0/drivers/pci/access.c:65
res = -2147480816
flags =
data = 0
#4 0x8144f7f2 in pci_read_config_dword (dev=,
where=, val=) at
/home/dannf/linux-kvm-5.4.0/drivers/pci/access.c:550
No locals.
#5 0x8145142a in __pci_read_base (dev=0x888000d8d000,
type=pci_bar_unknown, res=0x888000d8d278, pos=16) at
/home/dannf/linux-kvm-5.4.0/drivers/pci/probe.c:196
l = 0
sz = 0
mask =
l64 =
sz64 =
mask64 =
orig_cmd = 7
region = {start = 18446683600570153584, end = 18446744071584749924}
inverted_region = {start = 18446683600570153600, end =
18446744071584749991}
#6 0x81451757 in pci_read_bases (dev=0x888000d8d000, howmany=2,
rom=56) at /home/dannf/linux-kvm-5.4.0/drivers/pci/probe.c:334
res =
pos = 0
reg =
res =
#7 0x81451dd4 in pci_setup_device (dev=0x888000d8d000) at
/home/dannf/linux-kvm-5.4.0/drivers/pci/probe.c:1854
class = 1540
cmd = 34750
hdr_type =
pos =
region = {start = 18446683600670950407, end = 18446744071583369946}
res =
#8 0x81452950 in pci_scan_device (devfn=,
bus=) at /home/dannf/linux-kvm-5.4.0/drivers/pci/probe.c:2301
dev = 0x888000d8d000
l = 793398
dev =
l =
#9 pci_scan_single_device (devfn=, bus=) at
/home/dannf/linux-kvm-5.4.0/drivers/pci/probe.c:2474
dev =
dev =
#10 pci_scan_single_device (bus=0x888000c76c00, devfn=11) at
/home/dannf/linux-kvm-5.4.0/drivers/pci/probe.c:2464
dev = 0x0
#11 0x81452a02 in pci_scan_slot (bus=0x888000c76c00, devfn=8) at
/home/dannf/linux-kvm-5.4.0/drivers/pci/probe.c:2560
fn = 3
nr = 3
dev =
#12 0x81453a71 in pci_scan_child_bus_extend (bus=0x888000c76c00,
available_buses=) at
/home/dannf/linux-kvm-5.4.0/drivers/pci/probe.c:2770
used_buses =
normal_bridges =
hotplug_bridges =
start =
devfn = 16
fn =
cmax =
max =
dev =
nr_devs =
__mptr =
#13 0x81453c6b in pci_scan_child_bus (bus=) at
/home/dannf/linux-kvm-5.4.0/drivers/pci/probe.c:2900
No locals.
#14 0x814896df in acpi_pci_root_create (root=,
ops=, info=0x8880001e5600, sysdata=) at
/home/dannf/linux-kvm-5.4.0/drivers/acpi/pci_root.c:931
ret =
busnum =
device =
node =
bus = 0x888000c76c00
host_bridge =
obj =
#15 0x815a0c00 in pci_acpi_scan_root (root=0x88891b00) at
/home/dannf/linux-kvm-5.4.0/arch/x86/pci/acpi.c:368
info =
domain = 0
busnum =
node =
bus = 0x8880001e5600
#16 0x814893be in acpi_pci_root_add (device=0x888000c78000,
not_used=) at
/home/dannf/linux-kvm-5.4.0/drivers/acpi/pci_root.c:603
segment = 0
bus = 18446744071594171520
status =
result =
root =
handle = 0x888000d121e0
no_aspm = 0
hotadd =
is_pcie =
#17 0x81482cd9 in acpi_scan_attach_handler (device=) at
/home/dannf/linux-kvm-5.4.0/drivers/acpi/scan.c:1985
devid = 0x81ca77c0
handler =
hwid = 0x8880001f21c0
ret =
hwid =
ret =
__mptr =
devid =
handler =
__mptr =
#18 acpi_bus_attach (device=0x888000c78000) at
/home/dannf/linux-kvm-5.4.0/drivers/acpi/scan.c:2029
child =
ejd = 0x888000c79890
ret =
#19 0x81482c48 in acpi_bus_attach (device=0x888000c79800) at
/home/dannf/linux-kvm-5.4.0/drivers/acpi/scan.c:2050
child = 0x888000c78000
ejd = 0x888000c7a090
ret =
#20 0x81482c48 in acpi_bus_attach (device=0x888000c7a000) at
/home/dannf/linux-kvm-5.4.0/drivers/acpi/scan.c:2050
child = 0x888000c79800
ejd = 0x0
ret =
#21 0x81484bc3 in acpi_bus_scan (handle=0x) at
/home/dannf/linux-kvm-5.4.0/drivers/acpi/scan.c:2102
device = 0x888000c7a000
#22
[Kernel-packages] [Bug 1935880] [NEW] lxc c2-m2 focal VM causes KVM internal error during PCI init
Public bug reported: Launching a 2 CPU 2G VM with lxc often cause a KVM internal error during boot. Reproducer: lxc launch ubuntu:20.04 dannf-test2 -t c2-m2 --vm QEMU will report a KVM internal error: KVM internal error. Suberror: 3 extra data[0]: 80ec extra data[1]: 31 extra data[2]: 81 extra data[3]: 3 RAX= RBX=0001 RCX=0001 RDX=021e RSI=88807851cba8 RDI=0001 RBP=c9077e90 RSP=c9077e78 R8 =29417eca R9 = R10=0400 R11=0400 R12=0001 R13=8880001c8c80 R14= R15= RIP=81757a74 RFL=0246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 00c0 CS =0010 00a09b00 DPL=0 CS64 [-RA] SS = 00c0 DS = 00c0 FS = 00c0 GS = 88807850 00c0 LDT= 00c0 TR =0040 fe036000 206f 8b00 DPL=0 TSS64-busy GDT= fe034000 007f IDT= fe00 0fff CR0=80050033 CR2= CR3=0240a000 CR4=001006a0 DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER=0d01 Code=00 85 c0 7e 07 0f 00 2d 16 93 4b 00 fb f4 8b 05 14 61 78 00 <65> 44 8b 25 b4 86 8b 7e 85 c0 0f 8f 85 00 00 00 5b 41 5c 41 5d 5d c3 65 8b 05 9e 86 8b 7e The last lines on the console: acpi PNP0A08:00: _OSC: OS supports [ASPM ClockPM Segments MSI HPX-Type3] acpi PNP0A08:00: _OSC: not requesting OS control; OS requires [ExtendedConfig ASPM ClockPM MSI] PCI host bridge to bus :00 pci_bus :00: root bus resource [io 0x-0x0cf7 window] pci_bus :00: root bus resource [io 0x0d00-0x window] pci_bus :00: root bus resource [mem 0x000a-0x000b window] pci_bus :00: root bus resource [mem 0x7a10-0xafff window] pci_bus :00: root bus resource [mem 0xc000-0xfebf window] pci_bus :00: root bus resource [mem 0x8-0xf window] pci_bus :00: root bus resource [bus 00-ff] pci :00:00.0: [8086:29c0] type 00 class 0x06 pci :00:01.0: [1b36:000c] type 01 class 0x060400 pci :00:01.0: reg 0x10: [mem 0xc1245000-0xc1245fff] pci :00:01.1: [1b36:000c] type 01 class 0x060400 pci :00:01.1: reg 0x10: [mem 0xc1244000-0xc1244fff] pci :00:01.2: [1b36:000c] type 01 class 0x060400 pci :00:01.2: reg 0x10: [mem 0xc1243000-0xc1243fff] pci :00:01.3: [1b36:000c] type 01 class 0x060400 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Description changed: Launching a 2 CPU 2G VM with lxc often cause a KVM internal error during boot. Reproducer: lxc launch ubuntu:20.04 dannf-test2 -t c2-m2 --vm - QEMU will exit with a KVM internal error: + QEMU will report a KVM internal error: KVM internal error. Suberror: 3 extra data[0]: 80ec extra data[1]: 31 extra data[2]: 81 extra data[3]: 3 RAX= RBX=0001 RCX=0001 RDX=021e RSI=88807851cba8 RDI=0001 RBP=c9077e90 RSP=c9077e78 R8 =29417eca R9 = R10=0400 R11=0400 R12=0001 R13=8880001c8c80 R14= R15= RIP=81757a74 RFL=0246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 00c0 CS =0010 00a09b00 DPL=0 CS64 [-RA] SS = 00c0 DS = 00c0 FS = 00c0 GS = 88807850 00c0 LDT= 00c0 TR =0040 fe036000 206f 8b00 DPL=0 TSS64-busy GDT= fe034000 007f IDT= fe00 0fff CR0=80050033 CR2= CR3=0240a000 CR4=001006a0 - DR0= DR1= DR2= DR3= + DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER=0d01 Code=00 85 c0 7e 07 0f 00 2d 16 93 4b 00 fb f4 8b 05 14 61 78 00 <65> 44 8b 25 b4 86 8b 7e 85 c0 0f 8f 85 00 00 00 5b 41 5c 41 5d 5d c3 65 8b 05 9e 86 8b 7e - The last lines on the console: acpi PNP0A08:00: _OSC: OS supports [ASPM ClockPM Segments MSI HPX-Type3] acpi PNP0A08:00: _OSC: not requesting OS control; OS requires [ExtendedConfig ASPM ClockPM MSI] PCI host bridge to bus :00 pci_bus :00: root bus resource [io 0x-0x0cf7 window] pci_bus :00: root bus resource [io 0x0d00-0x window] pci_bus :00: root bus
[Kernel-packages] [Bug 1935846] Re: Sony Dualshock 4 usb dongle crashes the whole system
I assume you were referring to LTS kernel 5.4 used in Ubuntu20.04. I compiled a kernel with the proposed commit in below link. Let me know whether it fixes your problem and I will submit a SRU to kernel 5.4 if it does. https://people.canonical.com/~alexhung/LP1935846/ -- 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/1935846 Title: Sony Dualshock 4 usb dongle crashes the whole system Status in linux package in Ubuntu: New Bug description: The hid-sony driver has custom DS4 connect/disconnect logic for the DS4 dongle, which is a USB dongle acting as a proxy to Bluetooth connected DS4. The connect/disconnect logic works fine generally, however not in conjunction with Steam. Steam implements its own DS4 driver using hidraw. Both hid-sony and Steam are issuing their own HID requests and are racing each other during DS4 dongle connect/disconnect resulting in a kernel crash in hid-sony. The problem is that upon a DS4 connect to the dongle, hid-sony kicks of 'ds4_get_calibration_data' from within its dongle hotplug code. The calibration code issues raw HID feature report for reportID 0x02. When Steam is running, it issues a feature report for reportID 0x12 typically just prior to hid-sony requesting feature reportID 0x02. The result is that 'ds4_get_calibration_data' receives the data Steam requested as that's the HID report returing first. Currently this results in it processing invalid data, which ultimately results in a divide by zero upon a future 'dualshock4_parse_report'. The solution for now is to check within 'ds4_get_calibration_data' to check if we received data for the feature report we issued and if not retry. Please consider to add this patch to Ubuntu LTS kernels. Commit: https://github.com/torvalds/linux/commit/f5dc93b7875bcb8be77baa792cc9432aaf65365b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935846/+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 1930902] Re: screen goes white at plymouth w/ amdgpu sienna cichlid
Doesn't repro with 5.11 HWE builds, so I assume it's safe to not debug this and let it go invalid. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1930902 Title: screen goes white at plymouth w/ amdgpu sienna cichlid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: New Bug description: regression since 5.10.0-1026 Jun 4 07:56:37 lily kernel: [3.980436] amdgpu :09:00.0: [drm] fb0: amdgpudrmfb frame buffer device Jun 4 07:56:37 lily kernel: [4.007921] amdgpu :09:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 Jun 4 07:56:37 lily kernel: [4.007922] amdgpu :09:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 Jun 4 07:56:37 lily kernel: [4.007923] amdgpu :09:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 Jun 4 07:56:37 lily kernel: [4.007924] amdgpu :09:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 Jun 4 07:56:37 lily kernel: [4.007925] amdgpu :09:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 Jun 4 07:56:37 lily kernel: [4.007925] amdgpu :09:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 Jun 4 07:56:37 lily kernel: [4.007926] amdgpu :09:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 Jun 4 07:56:37 lily kernel: [4.007927] amdgpu :09:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 Jun 4 07:56:37 lily kernel: [4.007928] amdgpu :09:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 Jun 4 07:56:37 lily kernel: [4.007929] amdgpu :09:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 Jun 4 07:56:37 lily kernel: [4.007930] amdgpu :09:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 Jun 4 07:56:37 lily kernel: [4.007931] amdgpu :09:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0 Jun 4 07:56:37 lily kernel: [4.007932] amdgpu :09:00.0: amdgpu: ring sdma2 uses VM inv eng 14 on hub 0 Jun 4 07:56:37 lily kernel: [4.007932] amdgpu :09:00.0: amdgpu: ring sdma3 uses VM inv eng 15 on hub 0 Jun 4 07:56:37 lily kernel: [4.007933] amdgpu :09:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1 Jun 4 07:56:37 lily kernel: [4.007934] amdgpu :09:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1 Jun 4 07:56:37 lily kernel: [4.007935] amdgpu :09:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1 Jun 4 07:56:37 lily kernel: [4.007936] amdgpu :09:00.0: amdgpu: ring vcn_dec_1 uses VM inv eng 5 on hub 1 Jun 4 07:56:37 lily kernel: [4.007937] amdgpu :09:00.0: amdgpu: ring vcn_enc_1.0 uses VM inv eng 6 on hub 1 Jun 4 07:56:37 lily kernel: [4.007938] amdgpu :09:00.0: amdgpu: ring vcn_enc_1.1 uses VM inv eng 7 on hub 1 Jun 4 07:56:37 lily kernel: [4.007939] amdgpu :09:00.0: amdgpu: ring jpeg_dec uses VM inv eng 8 on hub 1 Jun 4 07:56:37 lily kernel: [4.008299] amdgpu :09:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:157 vmid:0 pasid:0, for process pid 0 thread pid 0) Jun 4 07:56:37 lily kernel: [4.008308] amdgpu :09:00.0: amdgpu: in page starting at address 0x0700 from client 18 Jun 4 07:56:37 lily kernel: [4.008311] amdgpu :09:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x073A Jun 4 07:56:37 lily kernel: [4.008314] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: DCEDMC (0x3) Jun 4 07:56:37 lily kernel: [4.008316] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 Jun 4 07:56:37 lily kernel: [4.008318] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x5 Jun 4 07:56:37 lily kernel: [4.008319] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Jun 4 07:56:37 lily kernel: [4.008321] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x1 Jun 4 07:56:37 lily kernel: [4.008322] amdgpu :09:00.0: amdgpu: RW: 0x0 Jun 4 07:56:37 lily kernel: [4.008326] fbcon: Taking over console Jun 4 07:56:37 lily kernel: [4.017984] [drm] Initialized amdgpu 3.40.0 20150101 for :09:00.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1930902/+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 1935866] [NEW] r8169 not working
Public bug reported: Whenever I reboot my computer, I am unable to connect to my network via ethernet. After running journalctl -xe I found the culprit to be the r8169 driver. == Steps to reproduce: == - Reboot computer - Try to connect to network My linux-modules package is linux-modules-5.11.0-7620-generic The kernel logs give me this error: > r8169 :04:00.0 enp4s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100) I uploaded a log of when I attempted to use modprobe r8169 here: https://pastebin.com/kPA1wM82 Here is the information about my network adapter from the output of lspci: > 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) And from ip link show: > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode > DEFAULT group default qlen 1000 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > 2: enp4s0: mtu 1500 qdisc fq_codel state UP > mode DEFAULT group default qlen 1000 > link/ether 18:c0:4d:2f:b0:7d brd ff:ff:ff:ff:ff:ff == Notes == - I am not running vanilla ubuntu, but Pop!_OS 21.04. I was referred here after attempting to report this on this github issue: https://github.com/pop-os/linux/issues/56 - My motherboard is a Gigabyte B450M DS3H with a Ryzen 2600 - The only way I have found to solve this is to use the r8168-dkms package and blacklist r8169 or rebooting into my Windows partition and then reboot back into Pop!_OS (however when restarting and trying to go back into Pop!_OS, r8169 throws that error again) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935866 Title: r8169 not working Status in linux package in Ubuntu: New Bug description: Whenever I reboot my computer, I am unable to connect to my network via ethernet. After running journalctl -xe I found the culprit to be the r8169 driver. == Steps to reproduce: == - Reboot computer - Try to connect to network My linux-modules package is linux-modules-5.11.0-7620-generic The kernel logs give me this error: > r8169 :04:00.0 enp4s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100) I uploaded a log of when I attempted to use modprobe r8169 here: https://pastebin.com/kPA1wM82 Here is the information about my network adapter from the output of lspci: > 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) And from ip link show: > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > 2: enp4s0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 > link/ether 18:c0:4d:2f:b0:7d brd ff:ff:ff:ff:ff:ff == Notes == - I am not running vanilla ubuntu, but Pop!_OS 21.04. I was referred here after attempting to report this on this github issue: https://github.com/pop-os/linux/issues/56 - My motherboard is a Gigabyte B450M DS3H with a Ryzen 2600 - The only way I have found to solve this is to use the r8168-dkms package and blacklist r8169 or rebooting into my Windows partition and then reboot back into Pop!_OS (however when restarting and trying to go back into Pop!_OS, r8169 throws that error again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935866/+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 1866591] Re: vmx_pending_event_test failed in ubuntu_kvm_unit_tests
** Changed in: ubuntu-kernel-tests Status: Confirmed => Triaged ** Tags added: hinted -- 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/1866591 Title: vmx_pending_event_test failed in ubuntu_kvm_unit_tests Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: Issue found on bare-metal node r5.metal, i3.metal, c5.metal timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.132aLPLaXz -smp 1 -cpu host,+vmx -append vmx_pending_event_test # -initrd /tmp/tmp.nWvh3t6ooD enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_pending_event_test FAIL: x86/vmx_tests.c:2184: Assertion failed: (expected) == (actual) LHS: 0x0012 - ''''''''''''''0001'0010 - 18 RHS: 00 - ''''''''''''''' - 0 Expected VMX_VMCALL, got VMX_EXC_NMI. STACK: 405e1c 405e46 4060e4 4061a1 401556 4039f1 400312 SUMMARY: 4 tests, 1 unexpected failures FAIL vmx_pending_event_test (4 tests, 1 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866591/+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 1935684] Re: vmx_init_signal_test in ubuntu_kvm_unit_tests fails on bionic/linux amd64
** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Tags added: hinted -- 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/1935684 Title: vmx_init_signal_test in ubuntu_kvm_unit_tests fails on bionic/linux amd64 Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: Issue found on node akis, with bionic/linux 4.15.0-150.155. This is not a regression as the failure can be found on previous releases. Error: filter = vmx_init_signal_test, test = vmx_init_signal_test Test suite: vmx_init_signal_test FAIL: INIT signal blocked when CPU in VMX operation filter = vmx_init_signal_test, test = vmx_sipi_signal_test Full log: Running 'kvm-ok' [stdout] INFO: /dev/kvm exists [stdout] KVM acceleration can be used Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_init_signal_test' [stdout] BUILD_HEAD=90a7d30e [stdout] timeout -k 1s --foreground 10 /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.BwMoFCX0Fv -smp 2 -cpu max,+vmx -m 2048 -append vmx_init_signal_test # -initrd /tmp/tmp.9wCF3rz6vO [stdout] enabling apic [stdout] enabling apic [stdout] paging enabled [stdout] cr0 = 80010011 [stdout] cr3 = 107f000 [stdout] cr4 = 20 [stdout] filter = vmx_init_signal_test, test = test_vmx_feature_control [stdout] filter = vmx_init_signal_test, test = test_vmxon [stdout] filter = vmx_init_signal_test, test = test_vmptrld [stdout] filter = vmx_init_signal_test, test = test_vmclear [stdout] filter = vmx_init_signal_test, test = test_vmptrst [stdout] filter = vmx_init_signal_test, test = test_vmwrite_vmread [stdout] filter = vmx_init_signal_test, test = test_vmcs_high [stdout] filter = vmx_init_signal_test, test = test_vmcs_lifecycle [stdout] filter = vmx_init_signal_test, test = test_vmx_caps [stdout] filter = vmx_init_signal_test, test = test_vmread_flags_touch [stdout] filter = vmx_init_signal_test, test = test_vmwrite_flags_touch [stdout] filter = vmx_init_signal_test, test = null [stdout] filter = vmx_init_signal_test, test = vmenter [stdout] filter = vmx_init_signal_test, test = preemption timer [stdout] filter = vmx_init_signal_test, test = control field PAT [stdout] filter = vmx_init_signal_test, test = control field EFER [stdout] filter = vmx_init_signal_test, test = CR shadowing [stdout] filter = vmx_init_signal_test, test = I/O bitmap [stdout] filter = vmx_init_signal_test, test = instruction intercept [stdout] filter = vmx_init_signal_test, test = EPT A/D disabled [stdout] filter = vmx_init_signal_test, test = EPT A/D enabled [stdout] filter = vmx_init_signal_test, test = PML [stdout] filter = vmx_init_signal_test, test = VPID [stdout] filter = vmx_init_signal_test, test = interrupt [stdout] filter = vmx_init_signal_test, test = nmi_hlt [stdout] filter = vmx_init_signal_test, test = debug controls [stdout] filter = vmx_init_signal_test, test = MSR switch [stdout] filter = vmx_init_signal_test, test = vmmcall [stdout] filter = vmx_init_signal_test, test = disable RDTSCP [stdout] filter = vmx_init_signal_test, test = int3 [stdout] filter = vmx_init_signal_test, test = into [stdout] filter = vmx_init_signal_test, test = exit_monitor_from_l2_test [stdout] filter = vmx_init_signal_test, test = invalid_msr [stdout] filter = vmx_init_signal_test, test = v2_null_test [stdout] filter = vmx_init_signal_test, test = v2_multiple_entries_test [stdout] filter = vmx_init_signal_test, test = fixture_test_case1 [stdout] filter = vmx_init_signal_test, test = fixture_test_case2 [stdout] filter = vmx_init_signal_test, test = invvpid_test_v2 [stdout] filter = vmx_init_signal_test, test = vmx_controls_test [stdout] filter = vmx_init_signal_test, test = vmx_host_state_area_test [stdout] filter = vmx_init_signal_test, test = vmx_guest_state_area_test [stdout] filter = vmx_init_signal_test, test = vmentry_movss_shadow_test [stdout] filter = vmx_init_signal_test, test = vmentry_unrestricted_guest_test [stdout] filter = vmx_init_signal_test, test = vmx_eoi_bitmap_ioapic_scan_test [stdout] filter = vmx_init_signal_test, test = vmx_hlt_with_rvi_test [stdout] filter = vmx_init_signal_test, test = apic_reg_virt_test [stdout] filter = vmx_init_signal_test, test = virt_x2apic_mode_test [stdout] filter = vmx_init_signal_test, test = vmx_apic_passthrough_test [stdout] filter = vmx_init_signal_test, test = vmx_apic_passthrough_thread_test [stdout] filter = vmx_init_signal_test, test = vmx_apic_passthrough_tpr_threshold_test [stdout] filter = vmx_init_signal_test, test = vmx_init_signal_test
[Kernel-packages] [Bug 1827866] Re: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X/B-KVM X-azure / X-aws
** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Tags added: hinted -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1827866 Title: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X/B-KVM X-azure / X-aws Status in ubuntu-kernel-tests: Triaged Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Xenial: New Status in linux-kvm source package in Xenial: New Status in linux-oracle source package in Xenial: New Status in linux-azure source package in Bionic: New Status in linux-kvm source package in Bionic: New Status in linux-oracle source package in Bionic: New Bug description: vmx_apicv_test from ubuntu_kvm_unit_tests failed on X-KVM: FAIL vmx_apicv_test (timeout; duration=10) the test was terminated with return code 124: # TESTNAME=vmx_apicv_test TIMEOUT=10 ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "apic_reg_virt_test virt_x2apic_mode_test" timeout -k 1s --foreground 10 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu host,+vmx -append apic_reg_virt_test virt_x2apic_mode_test # -initrd /tmp/tmp.K6b7rjmgp8 enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: apic_reg_virt_test --- Virtualize APIC accesses test --- PASS: xapic - reading 0x000: got APIC access exit @ page offset 0x000, want 0x000 PASS: xapic - writing 0x12345678 to 0x000: got APIC access exit @ page offset 0x000, want 0x000 PASS: xapic - reading 0x010: got APIC access exit @ page offset 0x010, want 0x010 PASS: xapic - writing 0x12345678 to 0x010: got APIC access exit @ page offset 0x010, want 0x010 PASS: xapic - reading 0x020: got APIC access exit @ page offset 0x020, want 0x020 PASS: xapic - writing 0x12345678 to 0x020: got APIC access exit @ page offset 0x020, want 0x020 PASS: xapic - reading 0x030: got APIC access exit @ page offset 0x030, want 0x030 PASS: xapic - writing 0x12345678 to 0x380: non-virtualized write; val is 0x12345678, want 0x12345678 PASS: xapic - reading 0x390: read 0x12345678, expected 0x12345678. PASS: xapic - writing 0x12345678 to 0x390: non-virtualized writqemu-system-x86_64: terminating on signal 15 from pid 1327 # echo $? 124 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1044-kvm 4.4.0-1044.50 ProcVersionSignature: Ubuntu 4.4.0-1044.50-kvm 4.4.177 Uname: Linux 4.4.0-1044-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon May 6 10:47:17 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827866/+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 1923284] Re: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test / vmx_hlt_with_rvi_test fails with timeout on Bionic
** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Tags added: hinted -- 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/1923284 Title: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test / vmx_hlt_with_rvi_test fails with timeout on Bionic Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test fails with timeout on Bionic 4.15.0-141.145 host rizzo this failed on the previous version of bionic 4.15.0-140.144 as well, so not a regression. vmx_host_state_area has an error before giving timeout: 04/10 01:29:18 DEBUG| utils:0153| [stderr] KVM: entry failed, hardware error 0x8021 04/10 01:29:18 DEBUG| utils:0153| [stderr] 04/10 01:29:18 DEBUG| utils:0153| [stderr] If you're running a guest on an Intel machine without unrestricted mode 04/10 01:29:18 DEBUG| utils:0153| [stderr] support, the failure can be most likely due to the guest entering an invalid 04/10 01:29:18 DEBUG| utils:0153| [stderr] state for Intel VT. For example, the guest maybe running in big real mode 04/10 01:29:18 DEBUG| utils:0153| [stderr] which is not supported on less recent Intel processors. 04/10 01:29:18 DEBUG| utils:0153| [stderr] 04/10 01:29:47 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 21956 (timeout) 04/10 01:29:47 DEBUG| utils:0153| [stdout] FAIL vmx_host_state_area (timeout; duration=30) vmx_intr_window_test / vmx_nmi_window_test shows passing until the timeout: 28. 04/10 01:29:49 DEBUG| utils:0153| [stdout] PASS: interrupt-window: active, RFLAGS.IF = 0: Activity state (0) is 'ACTIVE' 29. 04/10 01:30:19 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 22161 (timeout) 30. 04/10 01:30:19 DEBUG| utils:0153| [stdout] FAIL vmx_intr_window_test (timeout; duration=30) 31. 04/10 01:30:19 ERROR| test:0414| Exception escaping from test: -- 26. 04/10 01:30:24 DEBUG| utils:0153| [stdout] PASS: NMI-window: active, blocking by NMI: #UD handler executed once (actual 1 times) 27. 04/10 01:30:53 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 22570 (timeout) 28. 04/10 01:30:53 DEBUG| utils:0153| [stdout] FAIL vmx_nmi_window_test (timeout; duration=30) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923284/+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 1917616] Re: vmx test from ubuntu_kvm_unit_tests failed on Bionic/Focal
** Tags added: hinted
** Changed in: ubuntu-kernel-tests
Status: New => Triaged
--
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/1917616
Title:
vmx test from ubuntu_kvm_unit_tests failed on Bionic/Focal
Status in ubuntu-kernel-tests:
Triaged
Status in linux package in Ubuntu:
New
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
Appearing in bionic 5.4.0-67.75~18.04.1 affecting lowlatency and hwe
flavors.
2538. 02/25 00:10:11 DEBUG| utils:0153| [stdout] Unhandled exception 13 #GP
at ip 004071a3
2539. 02/25 00:10:11 DEBUG| utils:0153| [stdout] error_code=
rflags=00010006 cs=0008
2540. 02/25 00:10:11 DEBUG| utils:0153| [stdout] rax=0078
rcx=0809 rdx= rbx=0009
2541. 02/25 00:10:11 DEBUG| utils:0153| [stdout] rbp=0047efdf
rsi=0042568d rdi=0042568d
2542. 02/25 00:10:11 DEBUG| utils:0153| [stdout] r8=000a
r9=03f8 r10=000d r11=
2543. 02/25 00:10:11 DEBUG| utils:0153| [stdout] r12=
r13= r14=00403dcc r15=
2544. 02/25 00:10:11 DEBUG| utils:0153| [stdout] cr0=80010031
cr2=e000 cr3=00477000 cr4=2020
2545. 02/25 00:10:11 DEBUG| utils:0153| [stdout] cr8=0007
2546. 02/25 00:10:11 DEBUG| utils:0153| [stdout] STACK: @4071a3 40170b 4004dd
2547. 02/25 00:10:11 DEBUG| utils:0153| [stdout] FAIL vmx
2548. 02/25 00:10:11 ERROR| test:0414| Exception escaping from test:
2549. Traceback (most recent call last):
2550. File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
2551. _call_test_function(self.execute, *p_args, **p_dargs)
2552. File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
2553. return func(*args, **dargs)
2554. File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
2555. postprocess_profiled_run, args, dargs)
2556. File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
2557. self.run_once(*args, **dargs)
2558. File
"/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py",
line 80, in run_once
2559. raise error.TestError("Test failed for {}".format(test_name))
2560. TestError: Test failed for vmx
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1917616/+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 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Blacklist for what? ASPM L1? In mainline this wouldn't be needed because L1 is disabled per default. Downstream this could be an option, of course. -- 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/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Confirmed Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 32 7a 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d
[Kernel-packages] [Bug 1918692] Re: ubuntu-kvm-unit-test/vmx_apic_passthrough_thread reports assertion failure
** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Tags added: hinted -- 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/1918692 Title: ubuntu-kvm-unit-test/vmx_apic_passthrough_thread reports assertion failure Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: Confirmed Bug description: Running the ubuntu_kvm_unit_test/vmx_apic_passthrough_thread subtest on rumford shows the following failure: 14. 03/03 06:44:40 DEBUG| utils:0153| [stdout] Test suite: vmx_apic_passthrough_thread_test 15. 03/03 06:44:40 DEBUG| utils:0153| [stdout] FAIL: x86/vmx_tests.c:7705: Assertion failed: (0) == ((int)ioapic_read_redir(0xf).remote_irr) 16. 03/03 06:44:40 DEBUG| utils:0153| [stdout] LHS: 00 - ''''''''''''''' - 0 17. 03/03 06:44:40 DEBUG| utils:0153| [stdout] RHS: 0x0001 - '''''''''''''''0001 - 1 18. 03/03 06:44:40 DEBUG| utils:0153| [stdout] IOAPIC pass-through: remote_irr=0 after EOI 19. 03/03 06:44:40 DEBUG| utils:0153| [stdout] STACK: 4083de 40841a 40158a 403a60 400312 20. 03/03 06:44:40 DEBUG| utils:0153| [stdout] SUMMARY: 5 tests, 1 unexpected failures This sounds like some hardware related setup issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1918692/+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 1932966] Re: kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
** Tags added: hinted
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1932966
Title:
kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
Status in ubuntu-kernel-tests:
Confirmed
Status in linux-kvm package in Ubuntu:
Confirmed
Status in linux-kvm source package in Bionic:
Confirmed
Bug description:
Found this on B/KVM, current cycle (sru-20210531):
18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
18:27:11 DEBUG| [stderr] KVM internal error. Suberror: 1
18:27:11 DEBUG| [stderr] emulation failure
18:27:11 DEBUG| [stderr] RAX=000a RBX=e000
RCX=03fd RDX=03f8
18:27:11 DEBUG| [stderr] RSI=00419991 RDI=00419991
RBP=0051b440 RSP=0051b420
18:27:11 DEBUG| [stderr] R8 =000a R9 =03f8
R10=000d R11=
18:27:11 DEBUG| [stderr] R12=e000 R13=
R14=d000 R15=
18:27:11 DEBUG| [stderr] RIP=00400a0c RFL=00010006 [-P-] CPL=0
II=0 A20=1 SMM=0 HLT=0
18:27:11 DEBUG| [stderr] ES =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] CS =0008 00a09b00 DPL=0
CS64 [-RA]
18:27:11 DEBUG| [stderr] SS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] DS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] FS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] GS =0010 0051a4d0 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] LDT= 8200 DPL=0 LDT
18:27:11 DEBUG| [stderr] TR =0080 0041207a 8b00 DPL=0
TSS64-busy
18:27:11 DEBUG| [stderr] GDT= 0041100a 106f
18:27:11 DEBUG| [stderr] IDT= 0041 0fff
18:27:11 DEBUG| [stderr] CR0=80010011 CR2=
CR3=01007000 CR4=0220
18:27:11 DEBUG| [stderr] DR0= DR1=
DR2= DR3=
18:27:11 DEBUG| [stderr] DR6=0ff0 DR7=0400
18:27:11 DEBUG| [stderr] EFER=0500
18:27:11 DEBUG| [stderr] Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66
0f 6f 45 e0 <0f> 11 03 48 89 de 48 8d 7d e0 e8 f8 f9 ff ff 0f b6 f8 be a1 8f 41
00 b8 00 00 00 00 e8 05
18:28:40 DEBUG| [stderr] qemu-system-x86_64: terminating on signal 15 from
pid 13634 (timeout)
18:28:40 DEBUG| [stdout] FAIL emulator (timeout; duration=90s)
[...]
TestError: Test failed for emulator
18:28:40 ERROR| child process failed
18:28:40 DEBUG| Traceback (most recent call last):
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/parallel.py", line 25,
in fork_start
18:28:40 DEBUG| l()
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/job.py", line 505, in
18:28:40 DEBUG| l = lambda: test.runtest(self, url, tag, args, dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/test.py", line 125, in
runtest
18:28:40 DEBUG| job.sysinfo.log_after_each_iteration)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
913, in runtest
18:28:40 DEBUG| mytest._exec(args, dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
411, in _exec
18:28:40 DEBUG| _call_test_function(self.execute, *p_args, **p_dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
823, in _call_test_function
18:28:40 DEBUG| return func(*args, **dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
291, in execute
18:28:40 DEBUG| postprocess_profiled_run, args, dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
212, in _call_run_once
18:28:40 DEBUG| self.run_once(*args, **dargs)
18:28:40 DEBUG| File
"/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py",
line 82, in run_once
18:28:40 DEBUG| raise error.TestError("Test failed for
{}".format(test_name))
18:28:40 DEBUG| TestError: Test failed for emulator
18:28:41 INFO | ERROR ubuntu_kvm_unit_tests.emulator
ubuntu_kvm_unit_tests.emulator timestamp=1624040921localtime=Jun 18
18:28:41 Test failed for emulator
18:28:41 INFO | END ERROR ubuntu_kvm_unit_tests.emulator
ubuntu_kvm_unit_tests.emulator timestamp=1624040921localtime=Jun 18
18:28:41
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1932966/+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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
There is an upstream bug report https://bugzilla.kernel.org/show_bug.cgi?id=213391 Comment 9 suggest: "downgrade the firmware." Comment 15 claims: "20210315 seems to work fine here (on an E595)." ** Bug watch added: Linux Kernel Bug Tracker #213391 https://bugzilla.kernel.org/show_bug.cgi?id=213391 -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+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 1935794] Re: BlueZ release 5.60
This bug was fixed in the package bluez - 5.60-0ubuntu1 --- bluez (5.60-0ubuntu1) impish; urgency=medium * New upstream release 5.60 (LP: #1935794): - Fix issue with reading from RFKILL device node. - Fix issue with AVDTP and parsing capabilities. - Fix issue with UnregisterApplication handling. - Fix issue with RegisterProfile if UUID already exists. - Fix issue with GATT client attribute read with offset. - Fix issue with non-discoverable device and advertising monitor. * Drop upstreamed patch: Fix-reading-from-rfkill-socket.patch -- Daniel van Vugt Mon, 12 Jul 2021 16:36:13 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- 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/1935794 Title: BlueZ release 5.60 Status in bluez package in Ubuntu: Fix Released Bug description: http://www.bluez.org/release-of-bluez-5-60/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1935794/+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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Does the latest firmware in the firmware git tree help? https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/amdgpu -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+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 1935855] [NEW] dbgsym contains no debug symbols
Public bug reported: linux-image-unsigned-5.4.0-77-generic-dbgsym provides a /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm, but it does not contain any debug symbols. Compare: $ file /usr/lib/debug/boot/vmlinux-* /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=514891d64a7d18db4fa58aa5cfea213e0951ca9d, not stripped /usr/lib/debug/boot/vmlinux-5.4.0-77-generic: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=773d8ee85333fe092635f65d2b6850909085c11d, with debug_info, not stripped This is apparently because linux-kvm has CONFIG_DEBUG_INFO disabled. Is there a good reason for that? Does it have some adverse impact even when stripped? ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1935855 Title: dbgsym contains no debug symbols Status in linux-kvm package in Ubuntu: New Bug description: linux-image-unsigned-5.4.0-77-generic-dbgsym provides a /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm, but it does not contain any debug symbols. Compare: $ file /usr/lib/debug/boot/vmlinux-* /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=514891d64a7d18db4fa58aa5cfea213e0951ca9d, not stripped /usr/lib/debug/boot/vmlinux-5.4.0-77-generic: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=773d8ee85333fe092635f65d2b6850909085c11d, with debug_info, not stripped This is apparently because linux-kvm has CONFIG_DEBUG_INFO disabled. Is there a good reason for that? Does it have some adverse impact even when stripped? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1935855/+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 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Heiner, can we use something like DMI-based blacklist in the r8169 driver? Whitelist doesn't scale that well... -- 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/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Confirmed Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 32 7a 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d Apr 23 10:07:43 surprise
[Kernel-packages] [Bug 1933510] Re: Support for SFH changes in Yellow Carp
https://lists.ubuntu.com/archives/kernel-team/2021-July/122128.html ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided => Low ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Status: Invalid => Won't Fix ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Low -- 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/1933510 Title: Support for SFH changes in Yellow Carp Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: AMD Yellow carp will require some changes for sensor fusion hub in amd_sfh driver. The following changes are queued for kernel 5.14: https://patchwork.kernel.org/project/linux-input/cover/20210618081838.4156571-1-basavaraj.nati...@amd.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933510/+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 1934240] Re: Add Thunderbolt support for Intel Alder Lake
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1934240 Title: Add Thunderbolt support for Intel Alder Lake Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] Intel ADL TBT doesn't work. [Fix] Add ADL ID so TBT driver can probe. [Test] The driver is bound to the device in lspci. [Where problems could occur] These are new IDs, so no regression can happen. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1934240/+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 1930719] Re: Replace AMD nvme workaround from oem-5.10 with upstream version
** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1930719 Title: Replace AMD nvme workaround from oem-5.10 with upstream version Status in amd: Fix Committed Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Impish: New Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: The workaround carried in linux-oem-5.10 to support suspend to idle on AMD platforms: https://kernel.ubuntu.com/git/kernel-ppa/mirror/ubuntu- oem-5.10-focal.git/commit/drivers/nvme?h=oem-5.10-next=2d37b035a0f469d40ab0322b0f9dd7f2d43bc9b8 Should be replaced with what's going upstream for 5.14: http://git.infradead.org/nvme.git/commit/e21e0243e7b0f1c2a21d21f4d115f7b37175772a And please also apply it to oem-5.13. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1930719/+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 1934398] Re: Prevent spurious wakeups on amd s2idle
https://lists.ubuntu.com/archives/kernel-team/2021-July/122347.html ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- 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/1934398 Title: Prevent spurious wakeups on amd s2idle Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] Several AMD based OEM designs have spurious wakeups occurring from EC events during s2idle. This leads to non-functional wakeup sources or higher power consumption. [Fix] Prevent setting the GPE for the EC for wakeup source on AMD systems. [Test] Verify s2idle on OEM system. [Where problems could occur] Code is guarded to only run on AMD systems, which are just now getting s2idle support in oem kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934398/+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 1935853] [NEW] Fix second monitor hotplug on Intel TGP PCH
Public bug reported: [Impact] Intel TGP dekstop cannot detect second monitor. [Fix] Remove an IRQ setup routine and re-order some other IRQ setups. [Test] 1. Boot up the system with single monitor connected. 2. Hotplug second monitor. With the fix applied, the system can detect the 2nd monitor correctly. [Where problems could occur] This fix removed some special handling for early gen Core, so HPD on those old Core systems might be affected. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Tags: oem-priority originate-from-1933585 stella ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided => Medium ** Tags added: oem-priority originate-from-1933585 stella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1935853 Title: Fix second monitor hotplug on Intel TGP PCH Status in HWE Next: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Confirmed Bug description: [Impact] Intel TGP dekstop cannot detect second monitor. [Fix] Remove an IRQ setup routine and re-order some other IRQ setups. [Test] 1. Boot up the system with single monitor connected. 2. Hotplug second monitor. With the fix applied, the system can detect the 2nd monitor correctly. [Where problems could occur] This fix removed some special handling for early gen Core, so HPD on those old Core systems might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1935853/+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 1934398] Re: Prevent spurious wakeups on amd s2idle
** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Low ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Importance: Low => Medium ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided => Medium -- 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/1934398 Title: Prevent spurious wakeups on amd s2idle Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] Several AMD based OEM designs have spurious wakeups occurring from EC events during s2idle. This leads to non-functional wakeup sources or higher power consumption. [Fix] Prevent setting the GPE for the EC for wakeup source on AMD systems. [Test] Verify s2idle on OEM system. [Where problems could occur] Code is guarded to only run on AMD systems, which are just now getting s2idle support in oem kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934398/+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 1934428] Re: Request to pull-in new PERC11 PCI-id from upstream
** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1934428 Title: Request to pull-in new PERC11 PCI-id from upstream Status in dellserver: New Status in hwdata package in Ubuntu: New Bug description: Request to pull-in new PERC11 PCI-ids from upstream. PERC-11 are shipping cards supported since Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. Request is to pull these new pci-ids into future releases Ubuntu 20.04. PCI-id details: 1000:00e6:1028:2171 PERC H750 Mini 1000:00e6:1028:2172 PERC H355 Adapter 1000:00e6:1028:2173 PERC H355 Front 1000:00e6:1028:2174 PERC H350 Mini 1000:00e6:1028:2176 PERC H750 Adapter 1000:00e6:1028:2177 PERC H350 Adapter External links: https://pci-ids.ucw.cz/read/PC/1000/10e2 https://pci-ids.ucw.cz/v2.2/pci.ids To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934428/+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 1932166] Re: openafs/1.8.4~pre1-1ubuntu2.1 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
I can confirm that openafs-modules-dkms 1.8.4~pre1-1ubuntu2.2 can be built and loaded in focal with both 5.4.0-79-generic and 5.11.0-24-generic kernels. I have also tested starting the openafs- client.service systemd service. autopkgtest has also passed with both kernels: * 5.11.0-24.25~20.04.1 - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/openafs/20210709_104205_12531@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/o/openafs/20210709_104729_14c3f@/log.gz - armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/o/openafs/20210709_110044_46791@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/o/openafs/20210709_110044_46791@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/o/openafs/20210709_103426_14c3f@/log.gz * 5.4.0-79.88 - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/openafs/20210709_103628_491d4@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/o/openafs/20210709_103919_491d4@/log.gz - armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/o/openafs/20210709_105409_ddccd@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/o/openafs/20210709_103343_ddccd@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/o/openafs/20210709_103009_491d4@/log.gz ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932166 Title: openafs/1.8.4~pre1-1ubuntu2.1 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in openafs package in Ubuntu: Fix Released Status in linux-hwe-5.11 source package in Focal: New Status in openafs source package in Focal: Fix Committed Bug description: [Impact] Openafs 1.8.4~pre1-1ubuntu2.1 FTBFS when built against Linux 5.11 [Fix] Apply the attached debdiff (that is, in turn, a backport of upstream Linux build fixes), build the debs, install the dkms deb and build it against an installed 5.11 kernel: $ sudo dkms install openafs/1.8.4~pre1-1ubuntu2.1 -k $linux-5.11-version [Regression potential] The previous DKMS didn't build at all against 5.11. -- This is a scripted bug report about ADT failures while running openafs tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/openafs/20210611_211122_e1866@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/o/openafs/20210612_124646_ae454@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/o/openafs/20210611_212209_cd7d4@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/o/openafs/20210611_210636_9cb1d@/log.gz [Other] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932166/+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 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
@gilesco The server drivers do not work properly with my multi monitor setup, I get only the main monitor (DP), the other one (HDMI) is not detected. Everything works fine when I install 460.73 from Nvidia website, the manual way -- 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/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-465 package in Ubuntu: Triaged Bug description: I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute Jun 03 16:26:57 willow kernel: Oops: [#1] SMP PTI Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P OE 5.11.0-18-generic #19-Ubuntu Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019 Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09: 8e318220acb8 Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 R12: 0400 Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 R15: 0800 Jun 03 16:26:57 willow kernel: FS: 7f5807f38a40() GS:8e3466dc() knlGS: Jun 03 16:26:57 willow kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 CR4: 003706e0 Jun 03 16:26:57 willow kernel: DR0: DR1: DR2: Jun 03 16:26:57 willow kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jun 03 16:26:57 willow kernel: Call Trace: Jun 03 16:26:57 willow kernel: ? _nv015556rm+0x7fd/0x1020 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv027155rm+0x22c/0x4f0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017787rm+0x303/0x5e0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017789rm+0xe1/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv022829rm+0xed/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv023065rm+0x30/0x60 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv000704rm+0x16da/0x22b0 [nvidia] Jun 03 16:26:57 willow kernel: ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 03 16:26:57 willow kernel: ? nv_open_device+0x122/0x8e0 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_open+0x2b7/0x560 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 03 16:26:57 willow kernel: ? chrdev_open+0xf7/0x220 Jun 03 16:26:57 willow kernel: ? cdev_device_add+0x90/0x90 Jun 03 16:26:57 willow kernel: ? do_dentry_open+0x156/0x370 Jun 03 16:26:57 willow kernel: ? vfs_open+0x2d/0x30 Jun 03 16:26:57 willow kernel: ? do_open+0x1c3/0x340 Jun 03 16:26:57 willow kernel: ? path_openat+0x10a/0x1d0 Jun 03 16:26:57 willow kernel: ? do_filp_open+0x8c/0x130 Jun 03 16:26:57 willow kernel: ? __check_object_size+0x1c/0x20 Jun 03 16:26:57 willow kernel: ? do_sys_openat2+0x9b/0x150 Jun 03 16:26:57 willow kernel: ? __x64_sys_openat+0x56/0x90 Jun 03 16:26:57 willow kernel: ? do_syscall_64+0x38/0x90 Jun 03 16:26:57 willow kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) > Jun 03 16:26:57 willow kernel: sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c> Jun 03 16:26:57 willow kernel: CR2: 0170 Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]--- Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57
[Kernel-packages] [Bug 1935846] [NEW] Sony Dualshock 4 usb dongle crashes the whole system
Public bug reported: The hid-sony driver has custom DS4 connect/disconnect logic for the DS4 dongle, which is a USB dongle acting as a proxy to Bluetooth connected DS4. The connect/disconnect logic works fine generally, however not in conjunction with Steam. Steam implements its own DS4 driver using hidraw. Both hid-sony and Steam are issuing their own HID requests and are racing each other during DS4 dongle connect/disconnect resulting in a kernel crash in hid-sony. The problem is that upon a DS4 connect to the dongle, hid-sony kicks of 'ds4_get_calibration_data' from within its dongle hotplug code. The calibration code issues raw HID feature report for reportID 0x02. When Steam is running, it issues a feature report for reportID 0x12 typically just prior to hid-sony requesting feature reportID 0x02. The result is that 'ds4_get_calibration_data' receives the data Steam requested as that's the HID report returing first. Currently this results in it processing invalid data, which ultimately results in a divide by zero upon a future 'dualshock4_parse_report'. The solution for now is to check within 'ds4_get_calibration_data' to check if we received data for the feature report we issued and if not retry. Please consider to add this patch to Ubuntu LTS kernels. Commit: https://github.com/torvalds/linux/commit/f5dc93b7875bcb8be77baa792cc9432aaf65365b ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935846 Title: Sony Dualshock 4 usb dongle crashes the whole system Status in linux package in Ubuntu: New Bug description: The hid-sony driver has custom DS4 connect/disconnect logic for the DS4 dongle, which is a USB dongle acting as a proxy to Bluetooth connected DS4. The connect/disconnect logic works fine generally, however not in conjunction with Steam. Steam implements its own DS4 driver using hidraw. Both hid-sony and Steam are issuing their own HID requests and are racing each other during DS4 dongle connect/disconnect resulting in a kernel crash in hid-sony. The problem is that upon a DS4 connect to the dongle, hid-sony kicks of 'ds4_get_calibration_data' from within its dongle hotplug code. The calibration code issues raw HID feature report for reportID 0x02. When Steam is running, it issues a feature report for reportID 0x12 typically just prior to hid-sony requesting feature reportID 0x02. The result is that 'ds4_get_calibration_data' receives the data Steam requested as that's the HID report returing first. Currently this results in it processing invalid data, which ultimately results in a divide by zero upon a future 'dualshock4_parse_report'. The solution for now is to check within 'ds4_get_calibration_data' to check if we received data for the feature report we issued and if not retry. Please consider to add this patch to Ubuntu LTS kernels. Commit: https://github.com/torvalds/linux/commit/f5dc93b7875bcb8be77baa792cc9432aaf65365b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935846/+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 1933790] Re: Request to pull-in new HBA11 PCI-id from upstream
I'm pretty sure you meant "Public" not "Public Security" so I've changed it. ** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1933790 Title: Request to pull-in new HBA11 PCI-id from upstream Status in dellserver: New Status in hwdata package in Ubuntu: New Bug description: HBA-11 is a shipping card supported since early Ubuntu 20.04 onwards, however a new form factor is being launched by which has a new subsystem-id. Request is to pull this pci-id to upcoming Ubuntu 20.04 builds. PCI-id details: 1000:00e6:1028:2175 External links: http://pci-ids.ucw.cz/read/PC/1000/00e6/10282175 https://pci-ids.ucw.cz/v2.2/pci.ids To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1933790/+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 1875577] Re: Encrypted swap won't load on 20.04 with zfs root
** Description changed: + [Impact] + Encrypted swap partitions may not load correctly with ZFS root, due to ordering cycle on zfs-mount.service. + + [Test Plan] + 1. Install Ubuntu 20.04 using ZFS-on-root + 2. Add encrypted partition to /etc/crypttab: +swap/dev/nvme0n1p1 /dev/urandom swap,cipher=aes-xts-plain64,size=256 + 3. Add swap partition to /etc/fstab: +/dev/mapper/swapnoneswapsw 0 0 + 4. Reboot and check whether swap has loaded correctly, and whether boot logs show ordering cycle: + [6.638228] systemd[1]: systemd-random-seed.service: Found ordering cycle on zfs-mount.service/start + [6.639418] systemd[1]: systemd-random-seed.service: Found dependency on zfs-import.target/start + [6.640474] systemd[1]: systemd-random-seed.service: Found dependency on zfs-import-cache.service/start + [6.641637] systemd[1]: systemd-random-seed.service: Found dependency on cryptsetup.target/start + [6.642734] systemd[1]: systemd-random-seed.service: Found dependency on systemd-cryptsetup@swap.service/start + [6.643951] systemd[1]: systemd-random-seed.service: Found dependency on systemd-random-seed.service/start + [6.645098] systemd[1]: systemd-random-seed.service: Job zfs-mount.service/start deleted to break ordering cycle starting with systemd-random-seed.service/start + [ SKIP ] Ordering cycle found, skipping Mount ZFS filesystems + + [Where problems could occur] + Since we're changing the zfs-mount-generator service, regressions could show up during mounting of ZFS partitions. We should thoroughly test different scenarios of ZFS such as ZFS-on-root, separate ZFS partitions and the presence of swap, to make sure all partitions are mounted correctly and no ordering cycles are present. + + [Other Info] + This has been fixed upstream by the following commits: + * ec41cafee1da Fix a dependency loop [0] + * 62663fb7ec19 Fix another dependency loop [1] + + The patches above have been introduced in version 2.1.0, with upstream + backports to zfs-2.0. In Ubuntu, it's present in Groovy and later + releases, so it's still needed in Focal. + + $ rmadison -a source zfs-linux + zfs-linux | 0.8.3-1ubuntu12| focal | source + zfs-linux | 0.8.3-1ubuntu12.9 | focal-security | source + zfs-linux | 0.8.3-1ubuntu12.10 | focal-updates | source + zfs-linux | 0.8.4-1ubuntu11| groovy | source + zfs-linux | 0.8.4-1ubuntu11.2 | groovy-updates | source + zfs-linux | 2.0.2-1ubuntu5 | hirsute | source + zfs-linux | 2.0.3-8ubuntu5 | impish | source + + [0] https://github.com/openzfs/zfs/commit/ec41cafee1da + [1] https://github.com/openzfs/zfs/commit/62663fb7ec19 + + ORIGINAL DESCRIPTION + + root@eu1:/var/log# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal root@eu1:/var/log# apt-cache policy cryptsetup cryptsetup: - Installed: (none) - Candidate: 2:2.2.2-3ubuntu2 - Version table: - 2:2.2.2-3ubuntu2 500 - 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages + Installed: (none) + Candidate: 2:2.2.2-3ubuntu2 + Version table: + 2:2.2.2-3ubuntu2 500 + 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages OTHER BACKGROUND INFO: == 1. machine has 2 drives. each drive is partitioned into 2 partitions, zfs and swap + 2. Ubuntu 20.04 installed on ZFS root using debootstrap + (debootstrap_1.0.118ubuntu1_all) - 2. Ubuntu 20.04 installed on ZFS root using debootstrap (debootstrap_1.0.118ubuntu1_all) - - - 3. The ZFS root pool is a 2 partition mirror (the first partition of each disk) - + 3. The ZFS root pool is a 2 partition mirror (the first partition of + each disk) 4. /etc/crypttab is set up as follows: swap /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 /dev/urandom swap,cipher=aes-xts-plain64,size=256 swap /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802933-part2 /dev/urandom swap,cipher=aes-xts-plain64,size=256 - - WHAT I EXPECTED === I expected machine would reboot and have encrypted swap that used two devices under /dev/mapper - WHAT HAPPENED INSTEAD = - - On reboot, swap setup fails with the following messages in /var/log/syslog: + On reboot, swap setup fails with the following messages in + /var/log/syslog: Apr 28 17:13:01 eu1 kernel: [5.360793] systemd[1]: cryptsetup.target: Found ordering cycle on systemd-cryptsetup@swap.service/start Apr 28 17:13:01 eu1 kernel: [5.360795] systemd[1]: cryptsetup.target: Found dependency on systemd-random-seed.service/start Apr 28 17:13:01 eu1 kernel: [5.360796] systemd[1]: cryptsetup.target: Found dependency on zfs-mount.service/start Apr 28 17:13:01 eu1 kernel: [5.360797]
[Kernel-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
Upload to the bionic queue now ** Changed in: alsa-lib (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] "Cmedia Audio" is the sound card name of this usb audio dongle, and this string is got from usb string descriptor, that is to say the "Cmedia Audio" is hard-coded in the firmware of that usb dongle. Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't set string descriptor, then the audio driver sets a generic name "USB Audio Device" for them, if a dongle has string descriptor, it may have different string like "C-Media USB Headphone Set", and all dongles I met before don't have SPDIF interface. So If this SRU could introduce regression, it will happen on a Cmedia usb audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF playback device from the gnome-sound-setting. But this regression chance is very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in the string descriptor and it is very rare a usb audio dongle has SPDIF interface. So far we haven't met such a cmedia usb audio dongle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+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 1935794] Re: BlueZ release 5.60
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- 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/1935794 Title: BlueZ release 5.60 Status in bluez package in Ubuntu: Fix Committed Bug description: http://www.bluez.org/release-of-bluez-5-60/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1935794/+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 1933790] Re: Request to pull-in new HBA11 PCI-id from upstream
** Information type changed from Private to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1933790 Title: Request to pull-in new HBA11 PCI-id from upstream Status in dellserver: New Status in hwdata package in Ubuntu: New Bug description: HBA-11 is a shipping card supported since early Ubuntu 20.04 onwards, however a new form factor is being launched by which has a new subsystem-id. Request is to pull this pci-id to upcoming Ubuntu 20.04 builds. PCI-id details: 1000:00e6:1028:2175 External links: http://pci-ids.ucw.cz/read/PC/1000/00e6/10282175 https://pci-ids.ucw.cz/v2.2/pci.ids To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1933790/+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 1934428] Re: Request to pull-in new PERC11 PCI-id from upstream
** Information type changed from Private to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1934428 Title: Request to pull-in new PERC11 PCI-id from upstream Status in dellserver: New Status in hwdata package in Ubuntu: New Bug description: Request to pull-in new PERC11 PCI-ids from upstream. PERC-11 are shipping cards supported since Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. Request is to pull these new pci-ids into future releases Ubuntu 20.04. PCI-id details: 1000:00e6:1028:2171 PERC H750 Mini 1000:00e6:1028:2172 PERC H355 Adapter 1000:00e6:1028:2173 PERC H355 Front 1000:00e6:1028:2174 PERC H350 Mini 1000:00e6:1028:2176 PERC H750 Adapter 1000:00e6:1028:2177 PERC H350 Adapter External links: https://pci-ids.ucw.cz/read/PC/1000/10e2 https://pci-ids.ucw.cz/v2.2/pci.ids To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934428/+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 1786013] Autopkgtest regression report (linux-meta-azure/5.4.0.1053.51)
All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1053.51) for focal have finished running. The following regressions have been reported in tests triggered by the package: v4l2loopback/0.12.3-1ubuntu0.4 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 (amd64) 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/focal/update_excuses.html#linux-meta-azure [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1875577] Re: Encrypted swap won't load on 20.04 with zfs root
** Changed in: zfs-linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: zfs-linux (Ubuntu Focal) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1875577 Title: Encrypted swap won't load on 20.04 with zfs root Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Confirmed Bug description: root@eu1:/var/log# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal root@eu1:/var/log# apt-cache policy cryptsetup cryptsetup: Installed: (none) Candidate: 2:2.2.2-3ubuntu2 Version table: 2:2.2.2-3ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages OTHER BACKGROUND INFO: == 1. machine has 2 drives. each drive is partitioned into 2 partitions, zfs and swap 2. Ubuntu 20.04 installed on ZFS root using debootstrap (debootstrap_1.0.118ubuntu1_all) 3. The ZFS root pool is a 2 partition mirror (the first partition of each disk) 4. /etc/crypttab is set up as follows: swap /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 /dev/urandom swap,cipher=aes-xts-plain64,size=256 swap /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802933-part2 /dev/urandom swap,cipher=aes-xts-plain64,size=256 WHAT I EXPECTED === I expected machine would reboot and have encrypted swap that used two devices under /dev/mapper WHAT HAPPENED INSTEAD = On reboot, swap setup fails with the following messages in /var/log/syslog: Apr 28 17:13:01 eu1 kernel: [5.360793] systemd[1]: cryptsetup.target: Found ordering cycle on systemd-cryptsetup@swap.service/start Apr 28 17:13:01 eu1 kernel: [5.360795] systemd[1]: cryptsetup.target: Found dependency on systemd-random-seed.service/start Apr 28 17:13:01 eu1 kernel: [5.360796] systemd[1]: cryptsetup.target: Found dependency on zfs-mount.service/start Apr 28 17:13:01 eu1 kernel: [5.360797] systemd[1]: cryptsetup.target: Found dependency on zfs-load-module.service/start Apr 28 17:13:01 eu1 kernel: [5.360798] systemd[1]: cryptsetup.target: Found dependency on cryptsetup.target/start Apr 28 17:13:01 eu1 kernel: [5.360799] systemd[1]: cryptsetup.target: Job systemd-cryptsetup@swap.service/start deleted to break ordering cycle starting with cryptsetup.target/start . . . . . . Apr 28 17:13:01 eu1 kernel: [5.361082] systemd[1]: Unnecessary job for /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 was removed Also, /dev/mapper does not contain any swap devices: root@eu1:/var/log# ls -l /dev/mapper total 0 crw--- 1 root root 10, 236 Apr 28 17:13 control root@eu1:/var/log# And top shows no swap: MiB Swap: 0.0 total, 0.0 free, 0.0 used. 63153.6 avail Mem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1875577/+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 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
No, I simply implement the workaround in the kernel. Since ME isn't supported under Linux, there's a high chance that there won't be any proper solution soon. The patch can be found here: https://lkml.org/lkml/2021/7/12/2926 -- 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/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1026-oem N/A linux-backports-modules-5.10.0-1026-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1026-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE 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
[Kernel-packages] [Bug 1935833] Re: linux-azure CIFS DFS oops
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-azure (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 in Ubuntu. https://bugs.launchpad.net/bugs/1935833 Title: linux-azure CIFS DFS oops Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: Fix Committed Bug description: SRU Justification [Impact] A Microsoft customer is reporting a kernel oops when attempting a DFS connection. [Fix] a52930353eaf443489a350a135c5525a4acbbf56 cifs: handle empty list of targets in cifs_reconnect() baf3f08ef4083b76ca67b143e135213a7f941879 cifs: get rid of unused parameter in reconn_setup_dfs_targets() The addition of these 2 patches has been confirmed to prevent the oops. [Test Case] Mount a Windows DFS share [Where problems could occur] Mounts could continue to fail even though the kernel no longer crashes. [Other Info] SF: #00313885 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935833/+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 1786013] Autopkgtest regression report (linux-meta-azure-5.4/5.4.0.1053.32)
All autopkgtests for the newly accepted linux-meta-azure-5.4 (5.4.0.1053.32) for bionic have finished running. The following regressions have been reported in tests triggered by the package: v4l2loopback/0.10.0-1ubuntu1.2 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) asic0x/1.0.1-1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) zfs-linux/0.7.5-1ubuntu16.11 (amd64) 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-meta-azure-5.4 [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1931442] Re: Fujitsu U7311 I219-LM wired onboard slow RX speeds
*** This bug is a duplicate of bug 1927925 *** https://bugs.launchpad.net/bugs/1927925 ** This bug has been marked a duplicate of bug 1927925 Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) -- 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/1931442 Title: Fujitsu U7311 I219-LM wired onboard slow RX speeds Status in linux package in Ubuntu: Confirmed Bug description: Hello, i am having problem with very low RX speeds on my Fujitsu U7130 laptop's wired network with Intel I219-LM chip. When i start downloading any larger content, the speed is very low (ranging from 150kbps-6Mbps) or even the transfer completely stops. RX_errors are rising as well as rx_crc_errors when checking with "ethtool -S enp0s31f6". Link speed is auto-negotiated to 1000Mbps and lowering the speed manually is not having any effects on this issue. Wired TX speeds seems to be unaffected. Wireless speeds on the AX201 are as expected too. I did try to solve this problem upgrading from Ubuntu 20.04 to 21.04 and using various kernels (5.8, 5.10, 5.11, 5.12.9). I also tried to compile e1000e driver from sourceforge version 3.8.7 (https://sourceforge.net/projects/e1000/) with no joy. Bug #1927925 seems to be related as the behavior is the same, but in this case booting with kernel parameter "intel_idle.max_cstate=1" will not resolve the issue. lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 uname -a Linux IO 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy linux-image-5.11.0-18-generic linux-image-5.11.0-18-generic: Installed: 5.11.0-18.19 Candidate: 5.11.0-18.19 Version table: *** 5.11.0-18.19 500 500 http://cz.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 Packages 100 /var/lib/dpkg/status Thank you. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lk7r 2095 F pulseaudio /dev/snd/controlC0: lk7r 2095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-05-23 (17 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7311 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=b9466f2a-0840-40f4-8131-9b64200e5618 ro intel_idle.max_cstate=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 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 Tags: wayland-session hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-06-08 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 2.14 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.14 dmi.board.name: FJNB2E7 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7311 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.14:bd04/20/2021:br2.14:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7311:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7311: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7311 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+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 1935837] Re: x_tables errors may flood dmesg
commit 1b6cd67191e16a66f69c9881d878204c3143f03f ("netfilter: x_tables:
use pr ratelimiting in xt core") should be backported.
--
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/1935837
Title:
x_tables errors may flood dmesg
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
In Progress
Bug description:
[Impact]
User may spam dmesg with a lot of error messages.
[Fix]
ratelimit these error messages.
[Test case]
Run a test program that tries to create a mismatched x_tables entry in a
loop. Watch for dmesg.
[Potential regression]
Error messages may be missed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935837/+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 1935837] [NEW] x_tables errors may flood dmesg
Public bug reported: [Impact] User may spam dmesg with a lot of error messages. [Fix] ratelimit these error messages. [Test case] Run a test program that tries to create a mismatched x_tables entry in a loop. Watch for dmesg. [Potential regression] Error messages may be missed. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- 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/1935837 Title: x_tables errors may flood dmesg Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: [Impact] User may spam dmesg with a lot of error messages. [Fix] ratelimit these error messages. [Test case] Run a test program that tries to create a mismatched x_tables entry in a loop. Watch for dmesg. [Potential regression] Error messages may be missed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935837/+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 1935833] Re: linux-azure CIFS DFS oops
https://lists.ubuntu.com/archives/kernel-team/2021-July/122338.html -- 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/1935833 Title: linux-azure CIFS DFS oops Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] A Microsoft customer is reporting a kernel oops when attempting a DFS connection. [Fix] a52930353eaf443489a350a135c5525a4acbbf56 cifs: handle empty list of targets in cifs_reconnect() baf3f08ef4083b76ca67b143e135213a7f941879 cifs: get rid of unused parameter in reconn_setup_dfs_targets() The addition of these 2 patches has been confirmed to prevent the oops. [Test Case] Mount a Windows DFS share [Where problems could occur] Mounts could continue to fail even though the kernel no longer crashes. [Other Info] SF: #00313885 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935833/+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 1935833] [NEW] linux-azure CIFS DFS oops
Public bug reported: SRU Justification [Impact] A Microsoft customer is reporting a kernel oops when attempting a DFS connection. [Fix] a52930353eaf443489a350a135c5525a4acbbf56 cifs: handle empty list of targets in cifs_reconnect() baf3f08ef4083b76ca67b143e135213a7f941879 cifs: get rid of unused parameter in reconn_setup_dfs_targets() The addition of these 2 patches has been confirmed to prevent the oops. [Test Case] Mount a Windows DFS share [Where problems could occur] Mounts could continue to fail even though the kernel no longer crashes. [Other Info] SF: #00313885 ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Focal) Importance: Medium Status: In Progress ** Affects: linux-azure (Ubuntu Focal) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium -- 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/1935833 Title: linux-azure CIFS DFS oops Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] A Microsoft customer is reporting a kernel oops when attempting a DFS connection. [Fix] a52930353eaf443489a350a135c5525a4acbbf56 cifs: handle empty list of targets in cifs_reconnect() baf3f08ef4083b76ca67b143e135213a7f941879 cifs: get rid of unused parameter in reconn_setup_dfs_targets() The addition of these 2 patches has been confirmed to prevent the oops. [Test Case] Mount a Windows DFS share [Where problems could occur] Mounts could continue to fail even though the kernel no longer crashes. [Other Info] SF: #00313885 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935833/+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 1913259] Re: Intel AX201 Wi-Fi [8086:43f0] subsystem [1a56:1652]: Direct firmware load for (efault)128.ucode failed with error -2
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1913259
Title:
Intel AX201 Wi-Fi [8086:43f0] subsystem [1a56:1652]: Direct firmware
load for (efault)128.ucode failed with error -2
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
Invalid
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
Intel AX210 Wi-Fi [8086:43f0] subsystem [1a56:1652] requests invalid
firmware path and fails device init:
[ 4.146811] Intel(R) Wireless WiFi driver for Linux
[ 4.146866] iwlwifi :00:14.3: enabling device ( -> 0002)
[ 4.155371] iwlwifi :00:14.3: Direct firmware load for
(efault)128.ucode failed with error -2
[ 4.155388] iwlwifi :00:14.3: Direct firmware load for
(efault)127.ucode failed with error -2
...
[ 4.157058] iwlwifi :00:14.3: Direct firmware load for (efault)1.ucode
failed with error -2
[ 4.157068] iwlwifi :00:14.3: Direct firmware load for (efault)0.ucode
failed with error -2
[ 4.157070] iwlwifi :00:14.3: no suitable firmware found!
[ 4.157071] iwlwifi :00:14.3: minimum version required: (efault)0
[ 4.157072] iwlwifi :00:14.3: maximum version supported: (efault)128
[ 4.157073] iwlwifi :00:14.3: check
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
This is a design flaw in iwlwifi driver source.
In drivers/net/wireless/intel/iwlwifi/pcie/drv.c
static const struct pci_device_id iwl_hw_card_ids[] = {
{IWL_PCI_DEVICE(0x4232, 0x1201, iwl5100_agn_cfg)},
...
{IWL_PCI_DEVICE(0x43F0, PCI_ANY_ID, iwl_qu_long_latency_trans_cfg)},
...
};
The third argument to IWL_PCI_DEVICE macro will be assigned to driver_data
field
of struct pci_device_id. However, iwl5100_agn_cfg has type struct iwl_cfg, and
yet iwl_qu_long_latency_trans_cfg has type struct iwl_cfg_trans_params.
struct iwl_cfg_trans_params {
...
};
struct iwl_cfg {
struct iwl_cfg_trans_params trans;
const char *name;
const char *fw_name_pre;
...
};
It's fine to cast a pointer to struct iwl_cfg, but it's not always valid to
cast
a struct iwl_cfg_trans_params to struct iwl_cfg.
In function iwl_pci_probe, it tries to find an alternative cfg by iterating
throughout iwl_dev_info_table, but in our case, [8086:43f0] subsystem
[1a56:1652], all of the candidates will be skipped, and
iwl_qu_long_latency_trans_cfg will be assigned as the ultimate struct iwl_cfg,
which will be certainly wrong when you're trying to refer to anything beyond
sizeof(struct iwl_cfg_trans_params), e.g. cfg->fw_name_pre. In this case,
((struct iwl_cfg_trans_params*)_qu_long_latency_trans_cfg)->name will be
"'", and ((struct
iwl_cfg_trans_params*)_qu_long_latency_trans_cfg)->fw_name_pre
gives "(efault)", pure garbage data.
[Fix]
Commit 410f758529bc ("iwlwifi: add new cards for So and Qu family") in
v5.12-rc1
add a few additional entries to correctly catch this card.
[Test Case]
Booting from kernel built with aforementioned commit cherry-picked, WiFi
interface should be now up and working. Also tested this kernel against
several
iwlwifi supported models on the target and a previous generation platform.
[Where problems could occur]
This card failed initialization previously. With it being up and running, it
may
affect system stability if there are some undiscovered bugs related to this
new
model.
[Other Info]
This change has been backported to stable kernel v5.11.4, so skipped
nomination
for Hirsute/Unstable.
== Original bug report ==
00:14.3 Network controller [0280]: Intel Corporation Device [8086:43f0]
Subsystem: Bigfoot Networks, Inc. Device [1a56:1652]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-
Kernel modules: iwlwifi
In dmesg:
[ 4.146811] Intel(R) Wireless WiFi driver for Linux
[ 4.146866] iwlwifi :00:14.3: enabling device ( -> 0002)
[ 4.155371] iwlwifi :00:14.3: Direct firmware load for (efault)128.ucode
failed with error -2
[ 4.155388] iwlwifi :00:14.3: Direct firmware load for (efault)127.ucode
failed with error -2
[ 4.155486] iwlwifi :00:14.3: Direct firmware load for (efault)126.ucode
failed with error -2
[ 4.155585] iwlwifi
[Kernel-packages] [Bug 1935824] [NEW] drm:pipe_config_mismatch [i915]
Public bug reported: Recently acquired a new USB hub/dock which was working fine on the first day. On the second day, I got a hard lock the moment I logged in. After some more hard locks while troubleshooting, came to conclusion the issue lies with my secondary screen connected via display port to the USB hub. Initially I was greeted with the error below: drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun After adding intel_idle.max_cstate=4 to GRUB_CMDLINE_LINUX_DEFAULT, I got the following upon connecting USB hub/dock with the display port screen connected (suspended): [ +0.710628] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [ +1.542433] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in pixel_rate (expected 154000, found 307999) [ +0.000103] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in shared_dpll (expected f4b02026, found 87d317c5) [ +0.92] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) [ +0.87] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 154000, found 307999) [ +0.84] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) [ +0.04] [ cut here ] [ +0.01] pipe state doesn't match! [ +0.000182] WARNING: CPU: 1 PID: 1478 at drivers/gpu/drm/i915/display/intel_display.c:13159 verify_crtc_state+0x2ad/0x300 [i915] [ +0.02] Modules linked in: uas snd_usb_audio usb_storage snd_usbmidi_lib usbhid cdc_ether usbnet r8152 mii ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 ebtable_nat ebtable_broute ip6table_security iptable_security ip_set binfmt_misc veth nft_masq nft_chain_nat xt_conntrack nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter xt_CHECKSUM xt_MASQUERADE vboxnetadp(OE) vboxnetflt(OE) xt_tcpudp bridge stp llc vboxdrv(OE) zfs(PO) zunicode(PO) zlua(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter nf_tables nfnetlink ccm rfcomm cmac algif_hash aufs algif_skcipher af_alg bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc btusb btrtl btbcm btintel bluetooth ecdh_generic ecc overlay snd_hda_codec_hdmi mei_hdcp [ +0.62] intel_rapl_msr snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep joydev snd_pcm snd_seq_midi iwlmvm snd_seq_midi_event dell_laptop x86_pkg_temp_thermal snd_rawmidi intel_powerclamp ledtrig_audio mac80211 coretemp dell_smm_hwmon snd_seq libarc4 kvm_intel kvm iwlwifi dell_wmi snd_seq_device rapl dell_smbios dcdbas intel_cstate snd_timer snd mei_me processor_thermal_device ucsi_acpi intel_xhci_usb_role_switch input_leds intel_rapl_common typec_ucsi serio_raw cfg80211 dell_wmi_descriptor wmi_bmof soundcore hid_multitouch roles mei intel_soc_dts_iosf intel_pch_thermal typec int3403_thermal int340x_thermal_zone mac_hid intel_hid dell_smo8800 int3400_thermal acpi_pad acpi_thermal_rel sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 hid_generic i915 crct10dif_pclmul [ +0.57] crc32_pclmul i2c_algo_bit ghash_clmulni_intel drm_kms_helper aesni_intel syscopyarea crypto_simd sysfillrect sysimgblt r8169 fb_sys_fops ahci intel_lpss_pci i2c_hid intel_lpss cryptd realtek i2c_i801 psmouse idma64 libahci glue_helper virt_dma drm wmi hid video [ +0.26] CPU: 1 PID: 1478 Comm: Xorg Tainted: P OE 5.4.0-77-generic #86-Ubuntu [ +0.02] Hardware name: Dell Inc. Vostro 5471/08X87Y, BIOS 1.5.0 02/01/2018 [ +0.82] RIP: 0010:verify_crtc_state+0x2ad/0x300 [i915] [ +0.05] Code: b6 45 bf e9 8d fe ff ff 80 3d a5 81 10 00 00 0f b6 f0 48 c7 c7 a8 0c 55 c0 75 32 e8 7d e2 d4 ff e9 1e fe ff ff e8 05 f3 bf e0 <0f> 0b e9 1b ff ff ff e8 f9 f2 bf e0 0f 0b e9 85 fe ff ff e8 ed f2 [ +0.03] RSP: 0018:9d6b00be7a40 EFLAGS: 00010286 [ +0.03] RAX: RBX: 91d96b3602b0 RCX: 0006 [ +0.02] RDX: 0007 RSI: 0092 RDI: 91d97f6578c0 [ +0.02] RBP: 9d6b00be7a88 R08: 0461 R09: 0004 [ +0.02] R10: R11: 0001 R12: 91d96b2da800 [ +0.02] R13: 91d96b3602b8 R14: 91d96b36 R15: 91d96d81 [ +0.03] FS: 7fd0c98fea40() GS:91d97f64() knlGS: [ +0.03] CS: 0010 DS: ES:
[Kernel-packages] [Bug 1931497] Re: Patch To Fix Bug in the Linux Block Layer Responsible For Merging BIOs
This bug is awaiting verification that the 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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.
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-focal
--
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/1931497
Title:
Patch To Fix Bug in the Linux Block Layer Responsible For Merging
BIOs
Status in linux package in Ubuntu:
In Progress
Status in linux-azure package in Ubuntu:
New
Status in linux source package in Focal:
In Progress
Status in linux-azure source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Status in linux-azure source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
In Progress
Status in linux-azure source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
In Progress
Status in linux-azure source package in Impish:
New
Bug description:
[Impact]
There is a bug in the Linux block layer responsible for merging BIOs
that go across the page boundary. This bug was introduced in Linux 5.1
when the block layer BIO page tracking is enhanced to support multiple
pages.
Without this patch, data corruption can occur. The change to the
kernel block layer in Linux 5.1 changes the way multiple pages are
merged to a single block I/O descriptor, and how contiguous block I/O
descriptors are merged with previous descriptors.
If contiguous block I/O requests cross a page boundary of 4k, defined
by the hv_storvsc driver, the new block merge process can create two
pages of block I/O requests (the latter page with an offset) that
refer to the same physical sector on disk. This page list is then
assembled for the SCSI generic driver.
In the above scenario, when the block I/O request sizes are 512 bytes,
the Azure LIS driver (hv_storvsc module) is not able to correctly
parse the page array from the SCSI generic driver due to this bug in
Linux block layer and creates a potential overflow of offset I/O
requests and corruption of data on disk.
Mitigation of data loss is proven with filesystems with block size 4k.
When block I/O requests are of sizes 4k or multiples of 4k, they are
the page aligned in the memory and are not affected by the block I/O
merging algorithm introduced in Linux 5.1. Most modern file systems
use 4k I/O block size by default, thus mitigating this problem.
An upstream patch fixes this bug: commit
c9c9762d4d44dcb1b2ba90cfb4122dc11ceebf31 ("block: return the correct
bvec when checking for gaps")
Please include this patch in any supported kernels that are 5.1 or
later.
[Test Plan]
stress-ng --sequential 8 --class io -t 5m --times
[Where problems could occur]
Different incorrect pages could be wriiten to disk.
[Other Info]
This patch has already been released in all [FGHI] Azure kernels.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931497/+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 1875577] Re: Encrypted swap won't load on 20.04 with zfs root
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1875577 Title: Encrypted swap won't load on 20.04 with zfs root Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Confirmed Bug description: root@eu1:/var/log# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal root@eu1:/var/log# apt-cache policy cryptsetup cryptsetup: Installed: (none) Candidate: 2:2.2.2-3ubuntu2 Version table: 2:2.2.2-3ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages OTHER BACKGROUND INFO: == 1. machine has 2 drives. each drive is partitioned into 2 partitions, zfs and swap 2. Ubuntu 20.04 installed on ZFS root using debootstrap (debootstrap_1.0.118ubuntu1_all) 3. The ZFS root pool is a 2 partition mirror (the first partition of each disk) 4. /etc/crypttab is set up as follows: swap /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 /dev/urandom swap,cipher=aes-xts-plain64,size=256 swap /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802933-part2 /dev/urandom swap,cipher=aes-xts-plain64,size=256 WHAT I EXPECTED === I expected machine would reboot and have encrypted swap that used two devices under /dev/mapper WHAT HAPPENED INSTEAD = On reboot, swap setup fails with the following messages in /var/log/syslog: Apr 28 17:13:01 eu1 kernel: [5.360793] systemd[1]: cryptsetup.target: Found ordering cycle on systemd-cryptsetup@swap.service/start Apr 28 17:13:01 eu1 kernel: [5.360795] systemd[1]: cryptsetup.target: Found dependency on systemd-random-seed.service/start Apr 28 17:13:01 eu1 kernel: [5.360796] systemd[1]: cryptsetup.target: Found dependency on zfs-mount.service/start Apr 28 17:13:01 eu1 kernel: [5.360797] systemd[1]: cryptsetup.target: Found dependency on zfs-load-module.service/start Apr 28 17:13:01 eu1 kernel: [5.360798] systemd[1]: cryptsetup.target: Found dependency on cryptsetup.target/start Apr 28 17:13:01 eu1 kernel: [5.360799] systemd[1]: cryptsetup.target: Job systemd-cryptsetup@swap.service/start deleted to break ordering cycle starting with cryptsetup.target/start . . . . . . Apr 28 17:13:01 eu1 kernel: [5.361082] systemd[1]: Unnecessary job for /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 was removed Also, /dev/mapper does not contain any swap devices: root@eu1:/var/log# ls -l /dev/mapper total 0 crw--- 1 root root 10, 236 Apr 28 17:13 control root@eu1:/var/log# And top shows no swap: MiB Swap: 0.0 total, 0.0 free, 0.0 used. 63153.6 avail Mem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1875577/+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 1905591] Re: no brightness control in {455, 460} after update from 450
Hi All,
Please list the content of /sys/class/backlight folder.
--
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/1905591
Title:
no brightness control in {455,460} after update from 450
Status in OEM Priority Project:
New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Confirmed
Bug description:
On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce
GTX 1050 Ti Mobile]:
WORKS FINE:
nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1
NO BRIGHTNESS CONTROL:
nvidia-driver-455: 455.38-0ubuntu0.18.04.1
nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1
nvidia-driver-460: 460.39-0ubuntu0.18.04.1
*WORKAROUND: See comment #11 (add nvidia drivers to initramfs).
*Note that 460 fixes it for a 20.04 ThinkPad P73 per comment #6, but
not for my 18.04.5 Lenovo ThinkPad X1 per comment #5.
Updating to nvidia-driver-455 (or -460) results in loss of brightness
control. On boot, the laptop display brightness is somewhat less than
fully bright and cannot be changed. The brightness up/down keys do
pop up the gnome gui brightness widget, and
/sys/class/backlight/nvidia_0/* values do change, but the actual
display's brightness does not.
Problem occurs with either version of nvidia-driver-455 (the archive
or the ~graphics-drivers/PPA) or any version of -460.
Normal functionality returns if I downgrade to any version of nvidia-
driver-450.
Also observed: 455 and 460 temporarily display some pixel garbage
while mode-switching during the graphic login sequence. Only a minor
glitch, but note that 450 does not exhibit that issue either.
Note also that manually applying this to
/lib/systemd/system/nvidia-persistenced.service has no effect on the problem:
https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic
kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1905591/+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 1934741] Re: Add new PCI MMIO based thermal driver [8086:461d] for Intel Alder Lake
** Changed in: linux (Ubuntu Impish) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Impish) Importance: Undecided => High ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/1934741 Title: Add new PCI MMIO based thermal driver [8086:461d] for Intel Alder Lake Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: $ lspci -vvnns 00:04.0 00:04.0 Signal processing controller [1180]: Intel Corporation Device [8086:461d] (rev 01) Subsystem: Intel Corporation Device [8086:7270] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device [original] $ cat /sys/devices/virtual/thermal/thermal_zone*/type acpitz INT3400 Thermal TCPU x86_pkg_temp [patched] $ cat /sys/devices/virtual/thermal/thermal_zone*/type acpitz INT3400 Thermal TCPU TCPU_PCI x86_pkg_temp --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1367 F pulseaudio CasperMD5CheckResult: skip DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X130 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-06-18 (18 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. MachineType: Intel Corporation Alder Lake Client Platform Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-2006-oem root=UUID=a4f90fb9-1c2c-4d37-be7a-1b67b667c378 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-2006.6+lp1934660.1.adl.pmc.core-oem 5.13.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-2006-oem N/A linux-backports-modules-5.13.0-2006-oem N/A linux-firmware 1.187.15 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.13.0-2006-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 02/25/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2081.A02.2102250858 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2081.A02.2102250858:bd02/25/2021:efr1.25:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1001002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1001002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934741/+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 1935794] Re: BlueZ release 5.60
** Attachment added: "bluez_5.60-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1935794/+attachment/5510492/+files/bluez_5.60-0ubuntu1.debian.tar.xz -- 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/1935794 Title: BlueZ release 5.60 Status in bluez package in Ubuntu: In Progress Bug description: http://www.bluez.org/release-of-bluez-5-60/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1935794/+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 1935794] Re: BlueZ release 5.60
** Attachment added: "bluez_5.60.orig.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1935794/+attachment/5510491/+files/bluez_5.60.orig.tar.xz -- 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/1935794 Title: BlueZ release 5.60 Status in bluez package in Ubuntu: In Progress Bug description: http://www.bluez.org/release-of-bluez-5-60/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1935794/+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 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys
Is there already a solution other than power reset? I have this problem on Ubuntu 20.04.2 after logging to Windows 10. -- 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/1852071 Title: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: 1. Press fn+F3. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness down. 2. Press fn+F3 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness down. 1. Press fn+F4. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness up. 2. Press fn+F4 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 13:23:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8428] InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook Studio G5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1852071/+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 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
@Mario Did you had the chance to get the file stats of 10-enP53p0s0.link and to try what Lukas suggested in comment #47? -- 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/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition enP50s3832 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition enP50s3832 is not for us (backend 1) ** (generate:59965):
[Kernel-packages] [Bug 1935794] Re: BlueZ release 5.60
** Changed in: bluez (Ubuntu) Status: Triaged => In Progress -- 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/1935794 Title: BlueZ release 5.60 Status in bluez package in Ubuntu: In Progress Bug description: http://www.bluez.org/release-of-bluez-5-60/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1935794/+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 1876684] Re: fanotify09 case 3 (Events on files and dirs with both inode and mount marks) from ubuntu_ltp_syscalls failed
** Summary changed: - fanotify09 case 3 from ubuntu_ltp_syscalls failed + fanotify09 case 3 (Events on files and dirs with both inode and mount marks) from ubuntu_ltp_syscalls failed -- 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/1876684 Title: fanotify09 case 3 (Events on files and dirs with both inode and mount marks) from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: This is a new test case added 7 days ago [1] Test failed on Focal 5.4.0-29.33 with: fanotify09.c:150: FAIL: group 1 got event: mask 10 pid=41059 fd=24 path=/tmp/ltp-sL4wPwoPJ3/AuNN9M/mntpoint fanotify09.c:150: FAIL: group 2 got event: mask 10 pid=41059 fd=24 path=/tmp/ltp-sL4wPwoPJ3/AuNN9M/mntpoint [1] https://github.com/linux-test-project/ltp/commit/70ca1e8806d227d47c6801262d3f7983652159a4#diff-234c27c769cf07468a81748a0e7330dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1876684/+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 1935806] Re: Impish update: v5.13.1 upstream stable release
*** This bug is a duplicate of bug 1935807 *** https://bugs.launchpad.net/bugs/1935807 ** This bug has been marked a duplicate of bug 1935807 Impish update: v5.13.1 upstream stable release ** Description changed: + SRU Justification - 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: - 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: + v5.13.1 upstream stable release + from git://git.kernel.org/ -v5.13.1 upstream stable release -from git://git.kernel.org/ + Revert "KVM: x86/mmu: Drop kvm_mmu_extended_role.cr4_la57 hack" + Linux 5.13.1 -- 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/1935806 Title: Impish update: v5.13.1 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed 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: v5.13.1 upstream stable release from git://git.kernel.org/ Revert "KVM: x86/mmu: Drop kvm_mmu_extended_role.cr4_la57 hack" Linux 5.13.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935806/+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 1935583] Re: Kernel panic on Bionic 5.4.0-47-generic
There are many ways to corrupt stack or pointers to stack. Since this issue happens in out-of-tree mlx5 modules, it looks to me that where you shall look at. Please let us know if you can reproduce this issue without any out-of- tree module. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: kunpeng920 Status: Incomplete => Invalid -- 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/1935583 Title: Kernel panic on Bionic 5.4.0-47-generic Status in kunpeng920: Invalid Status in linux package in Ubuntu: Invalid Bug description: [Bug Description] Stack overflow in Kunpeng 920 32cores server, cause system reboot in production environment every month [Steps to Reproduce] 1)I cannot reproduce coz its a low-probability event [Actual Results] [1474521.296779] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.323300] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.349890] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.376451] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.411383] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.438042] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.455965] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.481140] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.508051] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.534519] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.561541] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.565243] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.596849] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.623516] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.659077] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.677128] Kernel panic - not syncing: corrupted stack end detected inside scheduler [1474521.685108] CPU: 7 PID: 5387 Comm: query_event Kdump: loaded Tainted: G OE 5.4.0-47-generic #51~18.04.1-Ubuntu [1474521.686201] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.689690] Unable to handle kernel paging request at virtual address 8027ce43b007 [1474521.689693] Mem abort info: [1474521.689695] ESR = 0x9605 [1474521.689698] EC = 0x25: DABT (current EL), IL = 32 bits [1474521.689700] SET = 0, FnV = 0 [1474521.689702] EA = 0, S1PTW = 0 [1474521.689703] Data abort info: [1474521.689705] ISV = 0, ISS = 0x0005 [1474521.689706] CM = 0, WnR = 0 [1474521.689710] swapper pgtable: 4k pages, 48-bit VAs, pgdp=014ac000 [1474521.689712] [8027ce43b007] pgd=2027f003, pud= [1474521.689719] Internal error: Oops: 9605 [#1] SMP [1474521.689722] Modules linked in: binfmt_misc xt_MASQUERADE iptable_nat nf_nat xt_tcpudp xt_multiport xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter rpcsec_gss_krb5 nfsv4 nfs fscache bonding nls_iso8859_1 ipmi_ssif joydev input_leds hns_roce_hw_v2 ib_uverbs ipmi_si spi_dw_mmio ipmi_devintf ipmi_msghandler spi_dw hisi_dma cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure mlx5_ib(OE) hibmc_drm realtek drm_vram_helper ttm drm_kms_helper hid_generic crct10dif_ce syscopyarea sysfillrect ghash_ce mlx5_core(OE) sysimgblt hisi_sas_v3_hw sha2_ce hns3 hisi_sas_main sha256_arm64 fb_sys_fops mlx_compat(OE) sha1_ce hclge libsas usbhid tls drm hid hnae3 megaraid_sas ahci [1474521.689802] scsi_transport_sas mlxfw(OE) gpio_dwapb aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [1474521.689814] CPU: 14 PID: 5899 Comm: tcp_upload Kdump: loaded Tainted: G OE 5.4.0-47-generic #51~18.04.1-Ubuntu [1474521.689816] Hardware name: [About Privacy Deleted], BIOS 1.39 06/11/2020 [1474521.689819] pstate: 0049 (nzcv daif +PAN -UAO) [1474521.689831] pc : kmem_cache_alloc+0x4c/0x220 [1474521.689835] lr : kmem_cache_alloc+0x44/0x220 [1474521.689836] sp : 800010073b90 [1474521.689838] x29: 800010073b90 x28: 0001 [1474521.689841] x27: 0027b78270c0 x26: 2027cc2b [1474521.689844] x25: 05ea x24: 0040 [1474521.689847] x23: 2027d3896000 x22: 800010c11a8c [1474521.689850] x21: 0a20 x20: 0007 [1474521.689852] x19: 2027d3896000 x18: 0014 [1474521.689856] x17: ea74f425 x16:
[Kernel-packages] [Bug 1935807] [NEW] Impish update: v5.13.1 upstream stable release
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: v5.13.1 upstream stable release from git://git.kernel.org/ Revert "KVM: x86/mmu: Drop kvm_mmu_extended_role.cr4_la57 hack" Linux 5.13.1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: Confirmed ** Description changed: + SRU Justification - 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: - 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: + v5.13.1 upstream stable release + from git://git.kernel.org/ -v5.13.1 upstream stable release -from git://git.kernel.org/ + Revert "KVM: x86/mmu: Drop kvm_mmu_extended_role.cr4_la57 hack" + Linux 5.13.1 -- 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/1935807 Title: Impish update: v5.13.1 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed 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: v5.13.1 upstream stable release from git://git.kernel.org/ Revert "KVM: x86/mmu: Drop kvm_mmu_extended_role.cr4_la57 hack" Linux 5.13.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935807/+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 1935806] [NEW] Impish update: v5.13.1 upstream stable release
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: v5.13.1 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: 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/1935806 Title: Impish update: v5.13.1 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed 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: v5.13.1 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935806/+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 1935017] Re: Possible io_uring regression with QEMU on Ubuntu's kernel
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux (Ubuntu)
Importance: High => Undecided
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu)
Assignee: Kamal Mostafa (kamalmostafa) => (unassigned)
--
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/1935017
Title:
Possible io_uring regression with QEMU on Ubuntu's kernel
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Groovy:
In Progress
Bug description:
Hi everyone.
Possible io_uring regression with QEMU on Ubuntu's kernel
With the latest Ubuntu 20.04's HWE kernel 5.8.0-59, I'm noticing some
weirdness when using QEMU/libvirt with the following storage
configuration:
QEMU version is 5.2+dfsg-9ubuntu3 and libvirt version is
7.0.0-2ubuntu2.
The guest VM is unable to handle I/O properly with io_uring, and nuking
io="io_uring" fixes the issue.
On one machine (EPYC 7742), the partition table cannot be read and on another
(Ryzen 9 3950X), ext4 detects weirdness with journaling and ultimately remounts
the guest disk to R/O:
[2.712321] virtio_blk virtio5: [vda] 3906519775 512-byte logical blocks
(2.00 TB/1.82 TiB)
[2.714054] vda: detected capacity change from 0 to 2000138124800
[2.963671] blk_update_request: I/O error, dev vda, sector 0 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.964909] Buffer I/O error on dev vda, logical block 0, async page read
[2.966021] blk_update_request: I/O error, dev vda, sector 1 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.967177] Buffer I/O error on dev vda, logical block 1, async page read
[2.968330] blk_update_request: I/O error, dev vda, sector 2 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.969504] Buffer I/O error on dev vda, logical block 2, async page read
[2.970767] blk_update_request: I/O error, dev vda, sector 3 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.971624] Buffer I/O error on dev vda, logical block 3, async page read
[2.972170] blk_update_request: I/O error, dev vda, sector 4 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.972728] Buffer I/O error on dev vda, logical block 4, async page read
[2.973308] blk_update_request: I/O error, dev vda, sector 5 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.973920] Buffer I/O error on dev vda, logical block 5, async page read
[2.974496] blk_update_request: I/O error, dev vda, sector 6 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.975093] Buffer I/O error on dev vda, logical block 6, async page read
[2.975685] blk_update_request: I/O error, dev vda, sector 7 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.976295] Buffer I/O error on dev vda, logical block 7, async page read
[2.980074] blk_update_request: I/O error, dev vda, sector 0 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.981104] Buffer I/O error on dev vda, logical block 0, async page read
[2.981786] blk_update_request: I/O error, dev vda, sector 1 op 0x0:(READ)
flags 0x0 phys_seg 1 prio class 0
[2.982083] ixgbe :06:00.0: Multiqueue Enabled: Rx Queue count = 63,
Tx Queue count = 63 XDP Queue count = 0
[2.982442] Buffer I/O error on dev vda, logical block 1, async page read
[2.983642] ldm_validate_partition_table(): Disk read failed.
Kernel 5.8.0-55 is fine, and the only io_uring-related change between
5.8.0-55 and 5.8.0-59 is the commit 4b982bd0f383 ("io_uring: don't
mark S_ISBLK async work as unbounded").
I'm hesitant to run lspci -vnvn and post other bug reporting logs as the
machine includes some proprietary hardware (quite unrelated to this specific
issue), but this issue is reproducible on multiple machines.
The another machine that I was able to reproduce this is running a production
software that needs to run 24/7, so I'm also hesitant to gather logs there too.
Thanks,
Regards
Update:
It was the commit 87c9cfe0fa1fb ("block: don't ignore REQ_NOWAIT for direct
IO").
(Upstream commit f8b78caf21d5bc3fcfc40c18898f9d52ed1451a5)
I've double checked by resetting the Git to
Ubuntu-hwe-5.8-5.8.0-59.66_20.04.1 and reverting that patch alone.
It fixes the issue.
It seems like this patch was backported to multiple stable trees, so I'm not
exactly sure why only Canonical's 5.8 is affected.
FWIW, 5.8.0-61 is also affected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935017/+subscriptions
[Kernel-packages] [Bug 1935754] Re: laptop brightness hotkey after latest update
Thanks. Can you try booting an older kernel version (like the original 5.11.0-16.17) and tell us if that avoids the issue? ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Summary changed: - laptop brightness hotkey after latest update + [HP EliteBook 850 G6] laptop brightness hotkey after latest update -- 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/1935754 Title: [HP EliteBook 850 G6] laptop brightness hotkey after latest update Status in linux package in Ubuntu: New Bug description: Hello! After recent update I have a problem brightness laptop button are turning my mic off instead of reduce or high it Could you fix it please? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4.2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 21:32:04 2021 InstallationDate: Installed on 2020-04-08 (458 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP EliteBook 850 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=78466619-ba7c-4459-92c2-58fc31c658f2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-15 (86 days ago) dmi.bios.date: 09/12/2019 dmi.bios.release: 3.0 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.03.00 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.52.00 dmi.chassis.asset.tag: 5CG9450KGR dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.82 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.03.00:bd09/12/2019:br3.0:efr82.82:svnHP:pnHPEliteBook850G6:pvr:rvnHP:rn8549:rvrKBCVersion52.52.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G6 dmi.product.sku: 7KP17EA#ACB dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 94:E6:F7:2D:22:F5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:21793 acl:0 sco:0 events:3343 errors:0 TX bytes:796729 acl:0 sco:0 commands:3321 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935754/+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 1928750] Re: Support mic-mute on Dell's platform
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928750 Title: Support mic-mute on Dell's platform Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] On Dell's platform, the MIC-Mute can't work. [Fix] Here's v8 patch, support MIC-Mute of dell e-privacy feature. Link: https://patchwork.kernel.org/project/alsa-devel/list/?series=477845 The set of patches has been verified and works well on dell's machine. In the upstream, Hans De Goede ask dell's developer to follow ucm2 and Dell will upstream v9. For the schedule, can't wait v9 and sru v8 first. In the feature, will sru the final solution. [Test Case] 1. fire "arecord record_file" 2. press mic-mute hot-key and wait 20s. 3. check the record file and can't hear voice. [Where problems could occur] Because the rt715 patch doesn't follow the ucm2, dell will upstream v9. In the future, will sru the final solution again. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1928750/+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 1935754] Re: laptop brightness hotkey after latest update
done ** Summary changed: - Problems with Blutooth and laptop brightness hotkey after lates update + laptop brightness hotkey after latest update ** Description changed: Hello! - After recent update I have several problems - 1. can't turn on/off my bluetooth - 2. brightness laptop button are turning my mic off instead of reduce or high it - + After recent update I have a problem brightness laptop button are + turning my mic off instead of reduce or high it Could you fix it please? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4.2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 21:32:04 2021 InstallationDate: Installed on 2020-04-08 (458 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP EliteBook 850 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=78466619-ba7c-4459-92c2-58fc31c658f2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-15 (86 days ago) dmi.bios.date: 09/12/2019 dmi.bios.release: 3.0 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.03.00 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.52.00 dmi.chassis.asset.tag: 5CG9450KGR dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.82 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.03.00:bd09/12/2019:br3.0:efr82.82:svnHP:pnHPEliteBook850G6:pvr:rvnHP:rn8549:rvrKBCVersion52.52.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G6 dmi.product.sku: 7KP17EA#ACB dmi.sys.vendor: HP hciconfig: - hci0:Type: Primary Bus: USB - BD Address: 94:E6:F7:2D:22:F5 ACL MTU: 1021:4 SCO MTU: 96:6 - UP RUNNING PSCAN ISCAN - RX bytes:21793 acl:0 sco:0 events:3343 errors:0 - TX bytes:796729 acl:0 sco:0 commands:3321 errors:0 + hci0:Type: Primary Bus: USB + BD Address: 94:E6:F7:2D:22:F5 ACL MTU: 1021:4 SCO MTU: 96:6 + UP RUNNING PSCAN ISCAN + RX bytes:21793 acl:0 sco:0 events:3343 errors:0 + TX bytes:796729 acl:0 sco:0 commands:3321 errors:0 ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- 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/1935754 Title: laptop brightness hotkey after latest update Status in bluez package in Ubuntu: New Bug description: Hello! After recent update I have a problem brightness laptop button are turning my mic off instead of reduce or high it Could you fix it please? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4.2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 21:32:04 2021 InstallationDate: Installed on 2020-04-08 (458 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP EliteBook 850 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=78466619-ba7c-4459-92c2-58fc31c658f2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-15 (86 days ago) dmi.bios.date: 09/12/2019 dmi.bios.release: 3.0 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.03.00 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.52.00 dmi.chassis.asset.tag: 5CG9450KGR dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.82 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.03.00:bd09/12/2019:br3.0:efr82.82:svnHP:pnHPEliteBook850G6:pvr:rvnHP:rn8549:rvrKBCVersion52.52.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G6 dmi.product.sku: 7KP17EA#ACB dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 94:E6:F7:2D:22:F5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:21793 acl:0 sco:0 events:3343 errors:0 TX bytes:796729 acl:0 sco:0 commands:3321 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1935754/+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
