[Kernel-packages] [Bug 1934557] Re: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop
Hi Simon: You got this laptop a bit earlier. This issue is in progress. Also could you upload the panel EDID? $ sudo apt install read-edid $ sudo get-edid > p14s2a.edid ** Changed in: linux (Ubuntu) Assignee: (unassigned) => AaronMa (mapengyu) -- 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/1934557 Title: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop Status in linux package in Ubuntu: New Bug description: Backlight does not change. Neither with the keys, nor with the slider. Values in /sys/class/backlight/amdgpu_bl0/brightness do change. However without effect on the actual brightness of the screen, which seems to be stuck at maximum brightness. Following the instructions from here: https://wiki.ubuntu.com/Kernel/Debugging/Backlight ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: simon 1886 F pulseaudio /dev/snd/pcmC2D0p: simon 1886 F...m pulseaudio /dev/snd/controlC1: simon 1886 F pulseaudio /dev/snd/controlC0: simon 1886 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 3 09:46:53 2021 InstallationDate: Installed on 2021-07-03 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 21A0CTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 1.5 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET35W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrR1MET35W(1.05):bd04/23/2021:br1.5:efr1.5:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0CTO1WW dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934557/+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 1930813] Re: [Asus Zenbook UX306] touchpad not recognised after upgrade 21.04
Could u attach the dmesg log of booting with kernel 5.6.19? Because from the current log, there's no touchpad information (i2c or serio interfaced?). -- 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/1930813 Title: [Asus Zenbook UX306] touchpad not recognised after upgrade 21.04 Status in linux package in Ubuntu: Incomplete Bug description: Touchpad doesn't work anymore after upgrading to 21.04 on a notebook asus zenbook UX306. Worked perfectly before upgrade ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thilu 11394 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Jun 4 09:15:12 2021 InstallationDate: Installed on 2020-04-23 (406 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 04f2:b56b Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305UAB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=884c588c-71bb-489c-a602-bb6c0463c7c0 ro quiet splash acpi_backlight=vendor vt.handoff=7 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 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-04 (0 days ago) dmi.bios.date: 08/09/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305UAB.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305UAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305UAB.301:bd08/09/2016:br5.11:svnASUSTeKCOMPUTERINC.:pnUX305UAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305UAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX305UAB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930813/+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 1931044] Re: SynPS/2 Synaptics TouchPad choppy movement after suspend
Can you add the "i8042.reset=1" to the kernel boot command line and see if it helps? -- 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/1931044 Title: SynPS/2 Synaptics TouchPad choppy movement after suspend Status in linux package in Ubuntu: New Bug description: Sometimes touchpad input becomes very laggy. It seems to be related to suspending the laptop. I think it also has to do with other mice being plugged in/out. Often, suspending and waking up immediately afterwards makes the pointer fluent again. This is not the only problem I see with this touchpad/driver: Sometimes the pointer stops moving horizontally as if it got stuck in a scrolling gesture. Sometimes the pointer (almost) stops moving completely. Suspending often but not always helps. I am not sure whether these problems are related. I am happy to debug the problem, but I don't know where to start. >> xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=10 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=9[slave keyboard (3)] ↳ ThinkPad Extra Buttons id=12 [slave keyboard (3)] ↳ Integrated Camera: Integrated C id=13 [slave keyboard (3)] >> lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal >> cat /proc/bus/input/devices ... I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input5 U: Uniq= H: Handlers=mouse0 event5 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=66080001103 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931044/+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 1931377] Re: Touchpad stopped working randomly while using anydesk as a client. Does not fix after a reboot. An external keyboard works.
Can you add the "i8042.reset=1" to the kernel boot command line and see if it helps? -- 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/1931377 Title: Touchpad stopped working randomly while using anydesk as a client. Does not fix after a reboot. An external keyboard works. Status in linux package in Ubuntu: New Bug description: Devices: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input7 U: Uniq= H: Handlers=rfkill kbd event6 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=0bda Product=58e3 Version=0003 N: Name="Lenovo EasyCamera: Lenovo EasyC" P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input8 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input9 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input10 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input11 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=1997 Product=2433 Version=0101 N: Name=" mini keyboard" P: Phys=usb-:00:14.0-1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:1997:2433.0001/input/input123 U: Uniq= H: Handlers=sysrq kbd event5 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=1997 Product=2433 Version=0101 N: Name=" mini keyboard" P: Phys=usb-:00:14.0-1/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:1997:2433.0002/input/input124 U: Uniq= H: Handlers=mouse0 event11 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0003 Vendor=1997 Product=2433 Version=0101 N: Name=" mini keyboard System Control" P: Phys=usb-:00:14.0-1/input2 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.2/0003:1997:2433.0003/input/input125 U: Uniq= H: Handlers=kbd event12 B: PROP=0 B: EV=13 B: KEY=c000 10 0 B: MSC=10 I: Bus=0003 Vendor=1997 Product=2433 Version=0101 N: Name=" mini keyboard Consumer Control" P: Phys=usb-:00:14.0-1/input2 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.2/0003:1997:2433.0003/input/input126 U: Uniq= H: Handlers=kbd event13 B: PROP=0 B: EV=1f B: KEY=3f000301ff 0 0 48317aff32d bfd6 1 130ff38b17c000 677bfad9415fed 19ed6804400 1002 B: REL=1040 B: ABS=1 B: MSC=10 (Includes my backup keyboard+mouse combo. Keyboard still works.) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-55-generic 5.8.0-55.62 ProcVersionSignature: Ubuntu 5.8.0-55.62-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 AudioDevicesInUse: USER
[Kernel-packages] [Bug 1921762] Re: Warning message "Could not determine valid watermarks for inherited state" on boot with B-4.15
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921762 Title: Warning message "Could not determine valid watermarks for inherited state" on boot with B-4.15 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: [Impact] Warning message found in dmesg after boot to the desktop: [2.458131] [ cut here ] [2.458132] Could not determine valid watermarks for inherited state [2.458196] WARNING: CPU: 2 PID: 184 at /build/linux-LfLFRN/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [2.458196] Modules linked in: i915(+) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i2c_algo_bit drm_kms_helper aesni_intel syscopyarea sysfillrect sysimgblt e1000e fb_sys_fops aes_x86_64 ahci crypto_simd glue_helper cryptd drm libahci sdhci_pci ptp sdhci pps_core wmi video [2.458209] CPU: 2 PID: 184 Comm: systemd-udevd Not tainted 4.15.0-140-generic #144-Ubuntu [2.458210] Hardware name: Dell Inc. Latitude 7250/0N248W, BIOS A15 12/26/2016 [2.458252] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [2.458253] RSP: 0018:b2f741e879b0 EFLAGS: 00010286 [2.458255] RAX: RBX: 9bb980b1 RCX: 85c63aa8 [2.458256] RDX: 0001 RSI: 0096 RDI: 0247 [2.458256] RBP: b2f741e87a40 R08: 02ed R09: 0004 [2.458257] R10: 0040 R11: 0001 R12: 9bb980c9e400 [2.458258] R13: 9bb980e18400 R14: ffea R15: 9bb980b10358 [2.458260] FS: 7f77eb758680() GS:9bb99f50() knlGS: [2.458261] CS: 0010 DS: ES: CR0: 80050033 [2.458261] CR2: 55c29ae999e8 CR3: 000401508003 CR4: 003606e0 [2.458263] Call Trace: [2.458298] i915_driver_load+0xa73/0xe60 [i915] [2.458331] i915_pci_probe+0x42/0x70 [i915] [2.458334] local_pci_probe+0x47/0xa0 [2.458336] pci_device_probe+0xf1/0x1d0 [2.458339] driver_probe_device+0x395/0x4a0 [2.458341] __driver_attach+0xcc/0xf0 [2.458343] ? driver_probe_device+0x4a0/0x4a0 [2.458346] bus_for_each_dev+0x70/0xc0 [2.458348] driver_attach+0x1e/0x20 [2.458349] bus_add_driver+0x1c7/0x270 [2.458351] ? 0xc05b9000 [2.458352] driver_register+0x60/0xe0 [2.458353] ? 0xc05b9000 [2.458356] __pci_register_driver+0x5a/0x60 [2.458387] i915_init+0x5c/0x5f [i915] [2.458390] do_one_initcall+0x52/0x1a0 [2.458392] ? __vunmap+0xb5/0xe0 [2.458395] ? _cond_resched+0x19/0x40 [2.458397] ? kmem_cache_alloc_trace+0x167/0x1d0 [2.458400] ? do_init_module+0x27/0x211 [2.458402] do_init_module+0x5f/0x211 [2.458405] load_module+0x16bd/0x1f30 [2.458408] ? ima_post_read_file+0x96/0xa0 [2.458411] SYSC_finit_module+0xfc/0x120 [2.458413] ? SYSC_finit_module+0xfc/0x120 [2.458415] SyS_finit_module+0xe/0x10 [2.458418] do_syscall_64+0x73/0x130 [2.458419] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [2.458421] RIP: 0033:0x7f77eb260639 [2.458422] RSP: 002b:7ffdeca5fd78 EFLAGS: 0246 ORIG_RAX: 0139 [2.458423] RAX: ffda RBX: 55c29ae761e0 RCX: 7f77eb260639 [2.458424] RDX: RSI: 7f77eaf3f105 RDI: 0012 [2.458425] RBP: 7f77eaf3f105 R08: R09: 7ffdeca5fe90 [2.458425] R10: 0012 R11: 0246 R12: [2.458426] R13: 55c29ae65870 R14: 0002 R15: 55c29ae761e0 [2.458428] Code: e9 46 fc ff ff 48 c7 c6 f7 cd 76 c0 48 c7 c7 4f c1 76 c0 e8 54 e1 1a c4 0f 0b e9 73 fe ff ff 48 c7 c7 40 26 78 c0 e8 41 e1 1a c4 <0f> 0b e9 4b fe ff ff 48 c7 c6 04 ce 76 c0 48 c7 c7 4f c1 76 c0 [2.458447] ---[ end trace d6878199e768615f ]--- Upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=105992 Possible fix: https://github.com/torvalds/linux/commit/bd4cd03c81010dcd4e6f0e02e4c15f44aefe12d1 Test kernel: https://people.canonical.com/~phlin/kernel/watermark/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-140-generic 4.15.0-140.144 ProcVersionSignature: Ubuntu 4.15.0-140.144-generic 4.15.18 Uname: Linux 4.15.0-140-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sam2618 F pulseaudio /dev/snd/controlC0: sam2618 F pulseaudio
[Kernel-packages] [Bug 1926579] Re: On TGL platforms screen shows garbage when browsing website by scrolling mouse
** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New -- 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/1926579 Title: On TGL platforms screen shows garbage when browsing website by scrolling mouse 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: New Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact] On Dell TGL platforms screen shows garbage when browsing website by scrolling mouse [Fix] This patch fixes the issue https://patchwork.freedesktop.org/patch/430153/?series=89348=1 [Test] Verified on Dell TGL-H platforms. [Where problems could occur] It disable PSR2 on A0 and B0 TGL-H platforms, should introduce no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926579/+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 1934499] Re: New BPF helpers to query conntrack and to generate/validate SYN cookies
** Changed in: linux-bluefield (Ubuntu) Assignee: (unassigned) => Bodong Wang (bodong-wang) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1934499 Title: New BPF helpers to query conntrack and to generate/validate SYN cookies Status in linux-bluefield package in Ubuntu: New Bug description: Ticket for the patch series that adds new BPF helpers to query conntrack and to generate SYN cookies for forwarded connections. * Explain the bug(s) This patch series aims to accelerate iptables synproxy module with XDP. The stage that generates and checks SYN cookies is stateless and can be implemented in XDP. * Brief explanation of fixes This patch series adds new BPF helpers: * bpf_ct_lookup_tcp to lookup CT status of a TCP connection. * bpf_tcp_raw_gen_syncookie to generate SYN cookies without a listening socket on the same host (to be used with iptables synproxy module). * bpf_tcp_raw_check_syncookie to check SYN cookies generated by the previos helper (to be used with iptables synproxy module). * bpf_tcp_raw_gen_tscookie to generate timestamp cookies, which encode additional information like SACK permission, ECN support, window scale. The format is compatible with iptables synproxy module. These new helpers allow to accelerate the iptables synproxy module. This series also includes some dependency patches backported from upstream. * How to test Use an XDP application that generates and checks SYN cookies, leveraging the new helpers. * What it could break. Nothing should be broken, only new functionality is added, and some patches are backported from upstream. CONFIG_NF_CONNTRACK is changed from m to y, which is also not expected to break existing functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934499/+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 1934617] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returne
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1934617 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: New Bug description: This error occurred during distro upgrade from 20.04 to 20.10. the broadcom kernel source crapped out. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jul 4 23:12:53 2021 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to groovy on 2021-07-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1934617/+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 1926579] Re: On TGL platforms screen shows garbage when browsing website by scrolling mouse
commit 8804325861be242a420d68c0175127a5947ac35a Author: Gwan-gyeong Mun Date: Thu Apr 22 19:05:44 2021 +0300 drm/i915/display: Disable PSR2 if TGL Display stepping is B1 from A0 TGL PSR2 hardware tracking shows momentary flicker and screen shift if TGL Display stepping is B1 from A0. It has been fixed from TGL Display stepping C0. HSDES: 18015970021 HSDES: 2209313811 BSpec: 55378 v2: Add checking of PSR2 manual tracking (Jose) Cc: José Roberto de Souza Signed-off-by: Gwan-gyeong Mun Reviewed-by: José Roberto de Souza Signed-off-by: José Roberto de Souza Link: https://patchwork.freedesktop.org/patch/msgid/20210422160544.2427123-1-gwan-gyeong@intel.com -- 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/1926579 Title: On TGL platforms screen shows garbage when browsing website by scrolling mouse 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.10 source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact] On Dell TGL platforms screen shows garbage when browsing website by scrolling mouse [Fix] This patch fixes the issue https://patchwork.freedesktop.org/patch/430153/?series=89348=1 [Test] Verified on Dell TGL-H platforms. [Where problems could occur] It disable PSR2 on A0 and B0 TGL-H platforms, should introduce no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926579/+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 1934617] [NEW] package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess retur
Public bug reported: This error occurred during distro upgrade from 20.04 to 20.10. the broadcom kernel source crapped out. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jul 4 23:12:53 2021 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to groovy on 2021-07-05 (0 days ago) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1934617 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: New Bug description: This error occurred during distro upgrade from 20.04 to 20.10. the broadcom kernel source crapped out. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jul 4 23:12:53 2021 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to groovy on 2021-07-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1934617/+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 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
Following a discussion with Chris, I checked /usr/share/alsa/ucm2/ and discovered that /usr/share/alsa/ucm2/hda-dsp/ was missing. I created it and put the files from https://github.com/alsa-project /alsa-ucm-conf/tree/master/ucm2/hda-dsp in it. I then restarted the computer and selected the 5.10.0-1035-oem kernel provided by Chris. Now, not only the sound output works as expected from internal speakers, but the internal microphone works as well! I can also plug headsets using the Jack output and the sound is output as expected. I attach pulseaudio logs for reference (without any headset connected). ** Attachment added: "pulseaudio-info.logs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5509024/+files/pulseaudio-info.logs -- 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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+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 1738534] Re: Processor turbo dsiabled/throttled after suspend
I am still having this problem on a Dell XPS 9360 running Ubuntu 21.04. -- 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/1738534 Title: Processor turbo dsiabled/throttled after suspend Status in linux package in Ubuntu: Confirmed Bug description: After suspending/resuming my laptop on battery power, I noticed choppy video playback. I've narrowed it down to the CPU being locked to lower frequencies after suspend/resume (only on battery). Plugging the laptop back in does not restore the normal performance, nor does suspend/resume after plugging it back in. The performance doesn't drop until after the suspend/resume, I'm not sure if it is _supposed_ to throttle when on battery, but either way the behaviour is wrong. Doing a full shutdown and restart restores the performance to normal. Prior to a suspend/resume cycle, cpupower reports: $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 3.00 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.26 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Afterwards, the frequency is clamped (cpufreq-set -r --max=3.0GHz has no effect) and turbo is disabled: $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 1.80 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 950 MHz (asserted by call to kernel) boost state support: Supported: no Active: no 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Trying to re-enable turbo mode by setting the no_turbo intel_pstate /sys/ entry back to 0 is rejected: $ echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo 0 tee: /sys/devices/system/cpu/intel_pstate/no_turbo: Operation not permitted However, these two commands *do* work around the problem, forcing turbo mode back on and then restoring the normal frequency range: sudo x86_energy_perf_policy --turbo-enable 1 sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz I also see this error in dmesg after some resumes (but the above problem sometimes happens without this error message): Dec 16 11:36:25 shauns-laptop kernel: intel_pstate: Turbo disabled by BIOS or unavailable on processor ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 1194 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 16 11:18:12 2017 InstallationDate: Installed on 2017-12-14 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 001 Device 004: ID 2232:1024 Silicon Motion Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-19-generic root=UUID=7352de8c-0017-44e1-81fb-0145ad9c1185 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 SourcePackage: linux UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1932367] Re: Pixel format change broken for Elgato Cam Link 4K
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 in Ubuntu. https://bugs.launchpad.net/bugs/1932367 Title: Pixel format change broken for Elgato Cam Link 4K Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Triaged Bug description: [Impact] The Elgato Cam Link 4K HDMI video capture card reports to support three different pixel formats, where the first format depends on the connected HDMI device. ``` $ v4l2-ctl -d /dev/video0 --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [1]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [2]: 'YU12' (Planar YUV 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) ``` Changing the pixel format to anything besides the first pixel format does not work: ``` $ v4l2-ctl -d /dev/video0 --try-fmt-video pixelformat=YU12 Format Video Capture: Width/Height : 3840/2160 Pixel Format : 'NV12' (Y/CbCr 4:2:0) Field : None Bytes per Line: 3840 Size Image: 12441600 Colorspace: sRGB Transfer Function : Rec. 709 YCbCr/HSV Encoding: Rec. 709 Quantization : Default (maps to Limited Range) Flags : ``` User space applications like VLC might show an error message on the terminal in that case: ``` libv4l2: error set_fmt gave us a different result than try_fmt! ``` Depending on the error handling of the user space applications, they might display a distorted video, because they use the wrong pixel format for decoding the stream. [Fix] The Elgato Cam Link 4K responds to the USB video probe VS_PROBE_CONTROL/VS_COMMIT_CONTROL with a malformed data structure: The second byte contains bFormatIndex (instead of being the second byte of bmHint). The first byte is always zero. The third byte is always 1. The firmware bug was reported to Elgato on 2020-12-01 and it was forwarded by the support team to the developers as feature request. There is no firmware update available since then. The latest firmware for Elgato Cam Link 4K as of 2021-03-23 has MCU 20.02.19 and FPGA 67. Therefore correct the malformed data structure for this device. The change was successfully tested with VLC, OBS, and Chromium using different pixel formats (YUYV, NV12, YU12), resolutions (3840x2160, 1920x1080), and frame rates (29.970 and 59.940 fps). [Test Case] Connect an input device to the Cam Link 4K and try all three pixel formats with VLC: vlc v4l2:///dev/video0 --v4l2-chroma=NV12 vlc v4l2:///dev/video0 --v4l2-chroma=YU12 [Other Info] The fix was reviewed and accepted by the subsystem maintainer and will be included upstream: https://git.linuxtv.org/media_stage.git/commit/?id=4c6e0976295add7f0ed94d276c04a3d6f1ea8f83 Attached a backported patch for Ubuntu. I successfully tested it with Linux 5.11 on Ubuntu 21.04 and Linux 5.8 on Ubuntu 20.10. It should work on older kernel versions as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932367/+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
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-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-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Fix Committed 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 1932029] Re: Support builtin revoked certificates
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 in Ubuntu. https://bugs.launchpad.net/bugs/1932029 Title: Support builtin revoked certificates Status in linux package in Ubuntu: New Bug description: [Impact] Upstream linux kernel now supports configuring built-in revoked certificates for the .blacklist keyring. Add support in our kernel configuration to have built-in revoked certificates. Revoke UEFI amd64 & arm64 2012 signing certificate. Under UEFI Secureboot with lockdown, shim may attempt to communicate revoked certificates to the kernel and depending on how good EFI firmware is, this may or may not succeed. By having these built-in, it will be prohibited to kexec file_load older kernels that were signed with now revoked certificates, however one boots. [Test Plan] * Boot kernel directly, or just with grub, and without shim * Check that $ sudo keyctl list %:.blacklist Contains assymetric 2012 key. [Where problems could occur] * Derivative and per-arch kernels may need to revoke different keys, thus this should be evaluated on per arch & flavour basis as to which keys to revoke. [Other Info] * In theory, this only needs to be revoked on amd64 and arm64, but empty revocation list is not allowed by the kernel configury, thus at the moment revoking 2012 UEFI cert for all architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029/+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 1931725] Re: initramfs-tools & kernel: use zstd as the default compression method
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 in Ubuntu. https://bugs.launchpad.net/bugs/1931725 Title: initramfs-tools & kernel: use zstd as the default compression method Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: New Bug description: Turns out that loading is always the slow part in loading initramfs into memory and decompressing it since decompression is always the final 10-20% or so of the task. It therefore makes sense to use a good compressor that shrinks the initramfs as much as possible with little decompression overhead. Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in decompression, the image size is much smaller with zstd than lz4, and since ~80-90% of the boot time is loading the image it makes sense to use zstd. Attached is a libreoffice spread sheet showing typical load and decompression times for a fairly standard 3.4 GHZ intel box with data for load times for a 5400 RPM, 7200 RPM and SATA SSD drives. The conclusions from the test results (attached) show: 1. Loading time is always significantly slower than decompression time. 2. ZSTD is 5x slower than LZ4 in decompression speed but produces far better compressed images 3. Given that loading time is the major factor in loading + decompression, ZSTD is best for kernel and initramfs boot timings. (Also refer to https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3 /kernel-compression-method.txt for some raw data on drive load speeds for the same UEFI box I did a couple of years ago). amd64 supports zstd, but s390x does not. Will use this bug to enable zstd support on s390x. Upstream submitted patch https://lore.kernel.org/linux-s390/20210615114150.325080-1-dimitri.led...@canonical.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931725/+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
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-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: Confirmed 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 1930745] Re: AT Translated Set 2 keyboard locks up seemingly randomly, infinitely repeating last pressed key
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1930745 Title: AT Translated Set 2 keyboard locks up seemingly randomly, infinitely repeating last pressed key Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: I am running Ubuntu 20.04.2 LTS on my ThinkPad L15 laptop. From time to time the keyboard gets stuck / locked up. Sometimes it takes days to happen, sometimes it happens within a few minutes. It also does not seem to depend on the programs I am running, it seems to be entirely random. Basically, I am working/playing on the laptop and then suddenly the key I pressed last "gets stuck" and the keyboard does not respond any more. Other than that everything is running fine and I can still use the mouse and so on, but logging out does not resolve the issue and only a restart seems to work. I have also tried connecting a USB keyboard while the problem is occurring. The external keyboard is then detected and works fine, the built-in keyboard stops sending the signal and remains unresponsive. I have already mentioned the problem here, but it could not be resolved: https://ubuntuforums.org/showthread.php?t=2460675 I have also contacted Lenovo Hardware Support, and ran their tests, but those did not return anything, so they said it was not a hardware issue. My best guess is that it is a bug in the driver for the AT Translated Set 2 keyboard (I have the German keyboard layout), which is listed as supported hardware. Current and latest driver version is 1.0.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 3 13:45:29 2021 InstallationDate: Installed on 2020-12-29 (156 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1930745/+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 1836030] Re: enable realtek ethernet device ASPM function
I also believe this change has caused https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/ ASPM must be disabled completely to avoid network malfunction issue.Even ubuntu 21.04 with kernel 5.11 sees this issue.Any one from Ubuntu is seeing this bug. pls change the following code: from rc = pci_disable_link_state(pdev, PCIE_LINK_STATE_L1_1); to rc = pci_disable_link_state(pdev, PCIE_LINK_STATE_L0S | PCIE_LINK_STATE_L1); -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1836030 Title: enable realtek ethernet device ASPM function Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: = SRU for 5.4 Focal kernel === [Impact] The PC state stays at PC3 if r8169 driver doesn't enable ASPM. [Fix] Applied same series of patches from v5.5-rc1 and disable ASPM L1.1 only, instead of disable ASPM completely. [Test] Verified on machines with realtek Ethernet device, the Ethernet works well after S3 test 30 times and the system can enter PC10. [Regression Potential] Low, from realtek engineer, r8169 driver supports ASPM L0s and L1, and we only disable ASPM L1.1 which is pretty safe and should be disabled by default. == SRU for 5.0 OEM OSP1 kernel = [Impact] The PC state stays at PC3 if realtek ethernet doesn't enable ASPM. [Fix] Discussed with upstream and they would like to use sysfs to toggle the ASPM link states, but the patches didn't get merged yet, so we merger them as SAUCE patches. [Test] Verified on machines with realtek ethernet device, the ethernet works well and the system can enter PC10. [Regression Potential] High. From upstream maintainer, enable realtek ethernet ASPM may lead to some serious issue, so regression is expected. Those regression should come from old realtek chips, we'll make sure all new platforms with realtek NIC have no any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836030/+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 1836030] Re: enable realtek ethernet device ASPM function
I also believe this change has caused https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/ Disabling ASPM L1.1 will cause network malfunctional with AER errors on my system.Is someone from Ubuntu helping with issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1836030 Title: enable realtek ethernet device ASPM function Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: = SRU for 5.4 Focal kernel === [Impact] The PC state stays at PC3 if r8169 driver doesn't enable ASPM. [Fix] Applied same series of patches from v5.5-rc1 and disable ASPM L1.1 only, instead of disable ASPM completely. [Test] Verified on machines with realtek Ethernet device, the Ethernet works well after S3 test 30 times and the system can enter PC10. [Regression Potential] Low, from realtek engineer, r8169 driver supports ASPM L0s and L1, and we only disable ASPM L1.1 which is pretty safe and should be disabled by default. == SRU for 5.0 OEM OSP1 kernel = [Impact] The PC state stays at PC3 if realtek ethernet doesn't enable ASPM. [Fix] Discussed with upstream and they would like to use sysfs to toggle the ASPM link states, but the patches didn't get merged yet, so we merger them as SAUCE patches. [Test] Verified on machines with realtek ethernet device, the ethernet works well and the system can enter PC10. [Regression Potential] High. From upstream maintainer, enable realtek ethernet ASPM may lead to some serious issue, so regression is expected. Those regression should come from old realtek chips, we'll make sure all new platforms with realtek NIC have no any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836030/+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 1934602] [NEW] package linux-modules-5.11.0-22-generic (not installed) failed to install/upgrade: »/lib/modules/5.11.0-22-generic/kernel/net/sunrpc/sunrpc.ko.dpkg-new« kann nich
Public bug reported: Got this information during standard update. ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-modules-5.11.0-22-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kai 14811 F pulseaudio CasperMD5CheckResult: unknown Date: Sun Jul 4 10:40:14 2021 ErrorMessage: »/lib/modules/5.11.0-22-generic/kernel/net/sunrpc/sunrpc.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig HibernationDevice: RESUME=UUID=c9ae6d89-0e2c-4169-8c2d-23c885210557 InstallationDate: Installed on 2011-01-09 (3828 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=6b86d3cb-fd5b-488a-a96f-7daf9cd9f59e ro resume=/dev/md1 other-option=value noplymouth video=SVIDEO-1:d PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: grub-pc 2.04-1ubuntu45 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Title: package linux-modules-5.11.0-22-generic (not installed) failed to install/upgrade: »/lib/modules/5.11.0-22-generic/kernel/net/sunrpc/sunrpc.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: Upgraded to hirsute on 2021-06-01 (33 days ago) dmi.bios.date: 07/11/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd07/11/2013:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute -- 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/1934602 Title: package linux-modules-5.11.0-22-generic (not installed) failed to install/upgrade: »/lib/modules/5.11.0-22-generic/kernel/net/sunrpc/sunrpc.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig Status in linux package in Ubuntu: New Bug description: Got this information during standard update. ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-modules-5.11.0-22-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kai 14811 F pulseaudio CasperMD5CheckResult: unknown Date: Sun Jul 4 10:40:14 2021 ErrorMessage: »/lib/modules/5.11.0-22-generic/kernel/net/sunrpc/sunrpc.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig HibernationDevice: RESUME=UUID=c9ae6d89-0e2c-4169-8c2d-23c885210557 InstallationDate: Installed on 2011-01-09 (3828 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=6b86d3cb-fd5b-488a-a96f-7daf9cd9f59e ro resume=/dev/md1 other-option=value noplymouth video=SVIDEO-1:d PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: grub-pc 2.04-1ubuntu45 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Title: package linux-modules-5.11.0-22-generic (not installed) failed to install/upgrade: »/lib/modules/5.11.0-22-generic/kernel/net/sunrpc/sunrpc.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: Upgraded to hirsute on 2021-06-01 (33 days ago) dmi.bios.date: 07/11/2013 dmi.bios.release: 4.6
[Kernel-packages] [Bug 1931131] Re: Update the 465 and the 460 NVIDIA driver series
I was able to get my hands on a card to upgrade from a GTX 1070 to an RTX 3060 Ti LHR (Low Hash Rate). Assuming this driver version to be necessary for the new LHR cards but I did not test the previous version, so that might not be correct. The basic GNOME desktop and Chromium browser seem to work. -- 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/1931131 Title: Update the 465 and the 460 NVIDIA driver series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: New Status in nvidia-graphics-drivers-465 package in Ubuntu: In Progress Status in nvidia-settings package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Status in linux source package in Hirsute: In Progress Status in nvidia-graphics-drivers-390 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: Update the 465 and the 460 NVIDIA driver series, and add support for Linux 5.13 to all the driver series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460.84 == * New upstream release (LP: #1931131): - Added support for the following GPUs: GeForce RTX 3080 Ti * debian/additional_card_ids: - Drop the additional IDs. * debian/rules: - Skip lines that start with "#" in debian/additional_card_ids. * debian/templates/dkms_nvidia.conf.in: - Drop buildfix_kernel_5.13.patch.
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/4.15.0.150.137)
All autopkgtests for the newly accepted linux-meta (4.15.0.150.137) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux/4.15.0-150.155 (i386, amd64, ppc64el) 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 [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 1786013] Autopkgtest regression report (linux-meta-aws/5.4.0.1053.55)
All autopkgtests for the newly accepted linux-meta-aws (5.4.0.1053.55) for focal have finished running. The following regressions have been reported in tests triggered by the package: v4l2loopback/0.12.3-1ubuntu0.4 (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-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: 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 1786013] Autopkgtest regression report (linux-meta-aws-5.4/5.4.0.1053.35)
All autopkgtests for the newly accepted linux-meta-aws-5.4 (5.4.0.1053.35) 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 (arm64, amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) zfs-linux/0.7.5-1ubuntu16.11 (arm64, 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-aws-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 1863939] Re: Linux 5.4 from focal repo does not boot on Lenovo Yoga C630 WOS, while Linux 5.4 from mainline PPA does boot
Issue is still reproducible with Linux 5.13 on Ubuntu 21.10. At the same time, Linux 5.13 from mainline PPA works fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1863939 Title: Linux 5.4 from focal repo does not boot on Lenovo Yoga C630 WOS, while Linux 5.4 from mainline PPA does boot Status in linux package in Ubuntu: Confirmed Status in linux-snapdragon package in Ubuntu: New Bug description: Hello! I found that both of generic and snapdragon kernels from focal repository (5.4.0-14-generic and 5.4.0-14-snapdragon was tested) does not boot on Lenovo Yoga C630 WOS. Boot process hang at "Loading device tree blob..." (which means I can not provide apport report, because I can not boot kernel from focal repository, and apport refuse to collect information with other kernels). At the same time snapdragon kernel from https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.4.20/ boot mostly fine (albeit with https://bugzilla.kernel.org/show_bug.cgi?id=204685 and https://bugs.launchpad.net/bugs/1863761 ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863939/+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 1903612] Re: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel
Thanks Po-Hsu Lin. The patch version of the kmod Package worked fine in my environment as well. # cd ~/kmod/tools # ./modinfo vfio-pci name: vfio_pci filename: (builtin) description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) # dpdk-devbind --status Network devices using DPDK-compatible driver Network devices using kernel driver === :02:00.0 'NetXtreme BCM5717 Gigabit Ethernet PCIe 1665' if=eno1 drv=tg3 unused=vfio-pci *Active* :02:00.1 'NetXtreme BCM5717 Gigabit Ethernet PCIe 1665' if=eno2 drv=tg3 unused=vfio-pci :0e:00.0 '82571EB/82571GB Gigabit Ethernet Controller (Copper) 10bc' if=enp14s0f0 drv=e1000e unused=vfio-pci :0e:00.1 '82571EB/82571GB Gigabit Ethernet Controller (Copper) 10bc' if=enp14s0f1 drv=e1000e unused=vfio-pci :0f:00.0 '82571EB/82571GB Gigabit Ethernet Controller (Copper) 10bc' if=enp15s0f0 drv=e1000e unused=vfio-pci :0f:00.1 '82571EB/82571GB Gigabit Ethernet Controller (Copper) 10bc' if=enp15s0f1 drv=e1000e unused=vfio-pci # dpdk-devbind -b vfio-pci :0f:00.0 # dpdk-devbind --status Network devices using DPDK-compatible driver :0f:00.0 '82571EB/82571GB Gigabit Ethernet Controller (Copper) 10bc' drv=vfio-pci unused=e1000e Network devices using kernel driver === :02:00.0 'NetXtreme BCM5717 Gigabit Ethernet PCIe 1665' if=eno1 drv=tg3 unused=vfio-pci *Active* :02:00.1 'NetXtreme BCM5717 Gigabit Ethernet PCIe 1665' if=eno2 drv=tg3 unused=vfio-pci :0e:00.0 '82571EB/82571GB Gigabit Ethernet Controller (Copper) 10bc' if=enp14s0f0 drv=e1000e unused=vfio-pci :0e:00.1 '82571EB/82571GB Gigabit Ethernet Controller (Copper) 10bc' if=enp14s0f1 drv=e1000e unused=vfio-pci :0f:00.1 '82571EB/82571GB Gigabit Ethernet Controller (Copper) 10bc' if=enp15s0f1 drv=e1000e unused=vfio-pci Testing Environment: # lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 18.04.5 LTS Release:18.04 Codename: bionic # uname -a Linux ml110gen9 5.4.0-77-generic #86~18.04.1-Ubuntu SMP Fri Jun 18 01:23:22 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux # apt list -a dpdk Listing... Done dpdk/bionic-updates,now 17.11.10-0ubuntu0.1 amd64 [installed] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in kmod package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Confirmed Status in kmod source package in Bionic: Confirmed Status in linux-hwe source package in Bionic: Confirmed Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI
[Kernel-packages] [Bug 1923660] Re: Remote control events repeat several times
*** This bug is a duplicate of bug 1926030 *** https://bugs.launchpad.net/bugs/1926030 I can confirm that the problem is fixed in Ubuntu 20.04 with kernel 5.8.0-59 Issue is solved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1923660 Title: Remote control events repeat several times Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: I think that after latest kernel update to Linux 5.8.0-49-generic there is an issue related (at least) to IR remote control input devices. After a key is pressed the event is repeated 95 times. This is not related to lirc. This behaviour can be seen by utilizing evtest. After I have pressed a key there are several events recognized by evtest: $ evtest No device specified, trying to scan all of /dev/input/event* Not running as root, no devices may be available. Available devices: ... /dev/input/event3:ITE8708 CIR transceiver ... Select the device event number [0-24]: 3 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x1283 product 0x0 version 0x0 Input device name: "ITE8708 CIR transceiver" Supported events: ... Event: time 1618343077.094251, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343077.094251, -- SYN_REPORT Event: time 1618343077.226238, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343077.226238, -- SYN_REPORT Event: time 1618343077.358229, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343077.358229, -- SYN_REPORT Event: time 1618343077.490292, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343077.490292, -- SYN_REPORT Event: time 1618343077.622249, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343077.622249, -- SYN_REPORT Event: time 1618343077.754271, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343077.754271, -- SYN_REPORT Event: time 1618343077.886254, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343077.886254, -- SYN_REPORT Event: time 1618343078.018248, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343078.018248, -- SYN_REPORT Event: time 1618343078.150253, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343078.150253, -- SYN_REPORT Event: time 1618343078.282255, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343078.282255, -- SYN_REPORT Event: time 1618343078.414254, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343078.414254, -- SYN_REPORT Event: time 1618343078.546247, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343078.546247, -- SYN_REPORT Event: time 1618343078.678255, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343078.678255, -- SYN_REPORT Event: time 1618343078.810294, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343078.810294, -- SYN_REPORT Event: time 1618343078.942244, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343078.942244, -- SYN_REPORT Event: time 1618343079.074261, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343079.074261, -- SYN_REPORT Event: time 1618343079.206257, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343079.206257, -- SYN_REPORT Event: time 1618343079.338268, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343079.338268, -- SYN_REPORT Event: time 1618343079.470268, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343079.470268, -- SYN_REPORT Event: time 1618343079.602231, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343079.602231, -- SYN_REPORT Event: time 1618343079.734274, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343079.734274, -- SYN_REPORT Event: time 1618343079.866261, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343079.866261, -- SYN_REPORT Event: time 1618343079.998272, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343079.998272, -- SYN_REPORT Event: time 1618343080.130260, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343080.130260, -- SYN_REPORT Event: time 1618343080.262262, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1618343080.262262, -- SYN_REPORT
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.4.0.1052.54)
All autopkgtests for the newly accepted linux-meta-aws (5.4.0.1052.54) for focal have finished running. The following regressions have been reported in tests triggered by the package: lxc/1:4.0.6-0ubuntu1~20.04.1 (arm64, amd64) systemd/245.4-4ubuntu3.7 (amd64) v4l2loopback/0.12.3-1ubuntu0.4 (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-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: 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
