[Kernel-packages] [Bug 1938013] Re: 4.15.0-151 is freezing intel 5th gen ThinkPad (T450)
>From askubuntu.com: Sample from linux-image-4.15.0-151-generic.253271.crash: ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Date: Sun Jul 25 11:32:27 2021 Failure: oops OopsText: general protection fault: [#1] SMP PTI Modules linked in: xfs libcrc32c uas usb_storage rfcomm ccm ip6table_filter ip6_tables iptable_filter v4l2loopback(OE) snd_hrtimer cmac bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi nvidia_drm(POE) intel_rapl x86_pkg_temp_thermal nvidia_modeset(POE) intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek ghash_clmulni_intel snd_hda_codec_generic nvidia(POE) pcbc iwlmvm mac80211 snd_hda_intel aesni_intel snd_hda_codec aes_x86_64 crypto_simd glue_helper asus_nb_wmi cryptd asus_wmi snd_hda_core intel_cstate snd_hwdep intel_rapl_perf serio_raw sparse_keymap intel_wmi_thunderbolt iwlwifi snd_pcm snd_seq_midi snd_seq_midi_event cfg80211 uvcvideo btusb btrtl videobuf2_vmalloc btbcm snd_rawmidi videobuf2_memops btintel videobuf2_v4l2 drm_kms_helper bluetooth snd_seq xpad videobuf2_core ff_memless ecdh_generic drm videodev snd_seq_device snd_timer media fb_sys_fops snd syscopyarea sysfillrect sysimgblt mei_me idma64 soundcore virt_dma input_leds joydev mei processor_thermal_device intel_lpss_pci int340x_thermal_zone shpchp intel_pch_thermal intel_lpss intel_soc_dts_iosf elan_i2c mac_hid asus_wireless int3400_thermal acpi_pad acpi_thermal_rel sch_fq_codel ppa parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_asus hid_generic usbhid nvme r8169 ahci nvme_core mii libahci wmi i2c_hid hid video pinctrl_sunrisepoint CPU: 4 PID: 81 Comm: kswapd0 Tainted: P OE4.15.0-151-generic #157-Ubuntu Hardware name: ASUSTeK COMPUTER INC. G752VT/G752VT, BIOS G752VT.213 01/06/2016 RIP: 0010:find_get_entries+0x68/0x200 RSP: 0018:b54cc384f9d0 EFLAGS: 00010246 RAX: RBX: 000e RCX: 0006 RDX: 1800 RSI: 1000 RDI: 9730446816d0 RBP: b54cc384fa30 R08: 0800 R09: 0006 R10: 9730446817f8 R11: R12: b54cc384faf8 R13: b54cc384fa78 R14: 000c R15: 9730446817f8 FS: () GS:97360650() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0a520680c000 CR3: 0005c260a005 CR4: 003606e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: pagevec_lookup_entries+0x1e/0x30 truncate_inode_pages_range+0x127/0x960 ? xfs_mount_validate_sb+0x440/0x500 [xfs] ? __inode_wait_for_writeback+0x7e/0xf0 ? bit_waitqueue+0x40/0x40 truncate_inode_pages_final+0x4c/0x60 evict+0x188/0x1a0 dispose_list+0x39/0x50 prune_icache_sb+0x5a/0x80 super_cache_scan+0x137/0x1b0 shrink_slab.part.49+0x1e7/0x440 shrink_node+0x2e1/0x2f0 kswapd+0x2b1/0x710 kthread+0x121/0x140 ? mem_cgroup_shrink_node+0x190/0x190 ? kthread_create_worker_on_cpu+0x70/0x70 ret_from_fork+0x35/0x40 Code: c7 45 a8 00 00 00 00 48 89 75 b0 45 31 ff 4d 85 ff 0f 84 01 01 00 00 49 8b 17 48 85 d2 74 69 48 89 d0 83 e0 03 0f 85 5f 01 00 00 <48> 8b 42 20 48 8d 78 ff a8 01 48 0f 44 fa 8b 47 1c 85 c0 74 d7 RIP: find_get_entries+0x68/0x200 RSP: b54cc384f9d0 ---[ end trace aafa3a2a2c51a63e ]--- Package: linux-image-4.15.0-151-generic 4.15.0-151.157 SourcePackage: linux Tags: kernel-oops Uname: Linux 4.15.0-151-generic x86_64 -- 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/1938013 Title: 4.15.0-151 is freezing intel 5th gen ThinkPad (T450) Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From: https://askubuntu.com/questions/1353859/ubuntu-18-04-05-lts- desktop-hangs-with-since-kernel-4-15-0-151-and-systemd-237-3 Several crashes in /var/crash, here's the last one:- ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Date: Fri Jul 23 18:10:54 2021 Failure: oops OopsText: BUG: Bad rss-counter state mm:c098a229 idx:2 val:-1 usblp0: removed usblp 1-5:1.0: usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04F9 pid 0x02EC <44>[ 18.329026] systemd-journald[358]: File /var/log/journal/b022dca21fd4480baeeb84f47ab439d3/user-1000.journal corrupted or uncleanly shut down, renaming and replacing. vboxdrv: loading out-of-tree module taints kernel. vboxdrv: module verification failed: signature and/or required key missing - tainting kernel vboxdrv: Found 8 processor cores vboxdrv: TSC mode is Invariant, tentative frequency 2303999142 Hz vboxdrv: Successfully loaded version 6.1.24 r145767 (interface 0x00300
[Kernel-packages] [Bug 1937415] Re: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199
Circling back to this, I did make an attempt with linux-firmware 1.198 as base and then copying in just the firmwares that appeared relevant to the hardware in question from 1.199. However I was no longer able to reproduce the issue. Now I have installed the 1.199 package again and I have had no issues after one full day of use. I wonder if this only occurred on the first boot with the new firmware, or if some other external activity caused the issue? I'm going to mark this as incomplete for now as I can no longer reproduce, feel free to downgrade to Invalid if you deem that appropriate. ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- 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/1937415 Title: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199 Status in linux-firmware package in Ubuntu: Incomplete Bug description: After upgrading from linux-firmware 1.198 to 1.199 my connectivity became unstable and I could see repeating hardware resets in `dmesg` output. Downgrading to linux-firmware 1.198 again resolved the issue. Note: this bug was filed after downgrading the package, but hopefully apport would have caught the kernel logs from previous boot as well. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.199 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 15:25:46 2021 Dependencies: InstallationDate: Installed on 2021-01-18 (185 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.198 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd01/15/2021:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+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 1938013] Re: 4.15.0-151 is freezing intel 5th gen ThinkPad (T450)
My stacks are inconclusive I would think. Sometimes there was a hang without a stack. Some examples asre Jul 22 10:38:37 everholt kernel: [ 2317.070485] Hardware name: LENOVO 20EQS3B30L/20EQS3B30L, BIOS N1EET62W (1.35 ) 11/10/2016 Jul 22 10:38:37 everholt kernel: [ 2317.070486] Call Trace: Jul 22 10:38:37 everholt kernel: [ 2317.070492] dump_stack+0x6d/0x8b Jul 22 10:38:37 everholt kernel: [ 2317.070495] print_bad_pte+0x222/0x2e0 Jul 22 10:38:37 everholt kernel: [ 2317.070498] ? alloc_pages_current+0x6a/0xe0 Jul 22 10:38:37 everholt kernel: [ 2317.070501] _vm_normal_page+0x9c/0x100 Jul 22 10:38:37 everholt kernel: [ 2317.070503] unmap_page_range+0x53f/0xd00 Jul 22 10:38:37 everholt kernel: [ 2317.070506] unmap_single_vma+0x7d/0xf0 Jul 22 10:38:37 everholt kernel: [ 2317.070508] unmap_vmas+0x51/0xb0 Jul 22 10:38:37 everholt kernel: [ 2317.070511] exit_mmap+0xb5/0x1d0 Jul 22 10:38:37 everholt kernel: [ 2317.070514] mmput+0x57/0x140 Jul 22 10:38:37 everholt kernel: [ 2317.070516] do_exit+0x352/0xb90 Jul 22 10:38:37 everholt kernel: [ 2317.070518] do_group_exit+0x43/0xb0 Jul 22 10:38:37 everholt kernel: [ 2317.070520] get_signal+0x142/0x7a0 Jul 22 10:38:37 everholt kernel: [ 2317.070523] do_signal+0x37/0x720 Jul 22 10:38:37 everholt kernel: [ 2317.070527] ? do_futex+0x370/0x4e0 Jul 22 10:38:37 everholt kernel: [ 2317.070529] ? __switch_to+0x123/0x4e0 Jul 22 10:38:37 everholt kernel: [ 2317.070531] ? __switch_to_asm+0x35/0x70 Jul 22 10:38:37 everholt kernel: [ 2317.070533] ? __switch_to_asm+0x35/0x70 Jul 22 10:38:37 everholt kernel: [ 2317.070535] ? SyS_futex+0x13b/0x180 Jul 22 10:38:37 everholt kernel: [ 2317.070538] exit_to_usermode_loop+0x73/0xd0 Jul 22 10:38:37 everholt kernel: [ 2317.070540] do_syscall_64+0x121/0x130 Jul 22 10:38:37 everholt kernel: [ 2317.070541] entry_SYSCALL_64_after_hwframe+0x41/0xa6 Jul 22 10:38:37 everholt kernel: [ 2317.070544] RIP: 0033:0x7efc92868ad3 Jul 22 10:38:37 everholt kernel: [ 2317.070545] RSP: 002b:7efc5effc9a0 EFLAGS: 0246 ORIG_RAX: 00ca Jul 22 10:38:37 everholt kernel: [ 2317.070547] RAX: fe00 RBX: 56451b009460 RCX: 7efc92868ad3 Jul 22 10:38:37 everholt kernel: [ 2317.070548] RDX: RSI: 0080 RDI: 56451b00948c Jul 22 10:38:37 everholt kernel: [ 2317.070549] RBP: 56451b009484 R08: 0001 R09: Jul 22 10:38:37 everholt kernel: [ 2317.070550] R10: R11: 0246 R12: 56451b00948c Jul 22 10:38:37 everholt kernel: [ 2317.070552] R13: R14: 56451b016470 R15: 17b9 Jul 23 09:33:14 everholt kernel: [ 1770.530621] ? _nv029462rm+0x2c1/0x520 [nvidia] Jul 23 09:33:14 everholt kernel: [ 1770.530835] ? _nv029436rm+0x69/0x140 [nvidia] Jul 23 09:33:14 everholt kernel: [ 1770.531035] ? _nv002278rm+0x9/0x20 [nvidia] Jul 23 09:33:14 everholt kernel: [ 1770.531234] ? _nv003733rm+0x1b/0x80 [nvidia] Jul 23 09:33:14 everholt kernel: [ 1770.531435] ? _nv014655rm+0x706/0x770 [nvidia] Jul 23 09:33:14 everholt kernel: [ 1770.531636] ? _nv037695rm+0xb3/0x150 [nvidia] Jul 23 09:33:14 everholt kernel: [ 1770.531836] ? _nv037694rm+0x388/0x4e0 [nvidia] Jul 23 09:33:14 everholt kernel: [ 1770.531986] ? _nv036059rm+0xbe/0x140 [nvidia] Jul 23 09:33:14 everholt kernel: [ 1770.532134] ? _nv036060rm+0x42/0x70 [nvidia] Jul 23 09:33:14 everholt kernel: [ 1770.532282] ? _nv000566rm+0x41/0x50 [nvidia] Jul 23 09:33:14 everholt kernel: [ 1770.532464] ? _nv000723rm+0x73a/0xa90 [nvidia] Jul 23 09:33:14 everholt kernel: [ 1770.532645] ? _nv000723rm+0x710/0xa90 [nvidia] Jul 23 09:33:14 everholt kernel: [ 1770.532822] ? rm_ioctl+0x54/0xb0 [nvidia] Jul 23 09:33:14 everholt kernel: [ 1770.532824] ? __slab_free+0x153/0x2d0 Jul 23 09:33:14 everholt kernel: [ 1770.532943] ? nvidia_ioctl+0x186/0x8a0 [nvidia] Jul 23 09:33:14 everholt kernel: [ 1770.533066] ? nvidia_frontend_unlocked_ioctl+0x42/0x50 [nvidia] Jul 23 09:33:14 everholt kernel: [ 1770.533068] ? do_vfs_ioctl+0xa8/0x630 Jul 23 09:33:14 everholt kernel: [ 1770.533070] ? __secure_computing+0x3f/0x100 Jul 23 09:33:14 everholt kernel: [ 1770.533072] ? syscall_trace_enter+0xd7/0x2d0 Jul 23 09:33:14 everholt kernel: [ 1770.533074] ? SyS_ioctl+0x79/0x90 Jul 23 09:33:14 everholt kernel: [ 1770.533076] ? do_syscall_64+0x73/0x130 Jul 23 09:33:14 everholt kernel: [ 1770.533078] ? entry_SYSCALL_64_after_hwframe+0x41/0xa6 Jul 23 09:33:38 everholt kernel: [ 1794.684072] Call Trace: Jul 23 09:33:38 everholt kernel: [ 1794.684210] ? _nv039714rm+0xb0/0x1a0 [nvidia] Jul 23 09:33:38 everholt kernel: [ 1794.684384] ? rm_cleanup_file_private+0x42/0x160 [nvidia] Jul 23 09:33:38 everholt kernel: [ 1794.684505] ? nvidia_close+0x14e/0x2e0 [nvidia] Jul 23 09:33:38 everholt kernel: [ 1794.684628] ? nvidia_frontend_close+0x2f/0x50 [nvidia] Jul 23 09:33:38 everholt kernel: [ 1794.684632] ? __fput+0xea/0x220 Jul 23 09:33:38 everholt kernel: [ 1794.684633] ? __
[Kernel-packages] [Bug 1934261] Re: use debian source format 3.0 (native)
Helpful in what way? I don't think this will get past SRU review. -- 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/1934261 Title: use debian source format 3.0 (native) Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Groovy: Won't Fix Status in linux-firmware source package in Hirsute: Invalid Status in linux-firmware source package in Impish: Invalid Bug description: In Hirsute/Impish, debian source package Standards-Version moved to 4.5.0, and debian/source/format is created with content "3.0 (native)". It should be also helpful to backport this change to other maintaining series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1923162] Re: riscv64 images fail to boot in qemu
On Tue, 27 Jul 2021, 05:45 Brian Murray, <1923...@bugs.launchpad.net> wrote: > I'm sorry to be a bother here but I don't understand how u-boot failed > verification for hirsute but passed for focal when what are presumably > the same patches exist in both versions of the package. How could this > happen? Focal is on par with hirsute-release. Hirsute-proposed had newer version of patches that were incomplete and did not make it into impish either. Hence the hirsute-proposed was an orphan upload, neither forward ported nor backported. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Fix Released Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Focal: Invalid Status in u-boot source package in Focal: Fix Committed Status in u-boot-menu source package in Focal: Fix Committed Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: Confirmed Status in u-boot-menu source package in Hirsute: Fix Released Bug description: [Impact] * u-boot may crash when attempting to boot extlinux.conf which specifies fdtdir; the given u-boot config doesn't specify a dtb filename to load; autodetection tries to make one up using $soc & $board variables; and if one or both of them are not set (as it is the case for qemu) it would crash. Fix this crash by doing validation / checking when quering for $soc & $board variables in autodetectionn. [Test Plan] * Use qemu & uboot produced by the build that fixes this bug report properly and attempt to boot hirsute's riscv64+unmatched image. * It should boot correctly without a crash / qemu backtrace. [Where problems could occur] * This patch is bein upstreamed. If one is using external uboot (i.e. provided by some other vendor) it may still crash when trying to boot Ubuntu's riscv64 rootfs or cloud image. [Other Info] * Patch is being reviewed upstream https://lists.denx.de/pipermail/u-boot/2021-May/449176.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+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 1937056] Re: Touchpad not working with ASUS TUF F15
Output of cat /proc/bus/input/devices ** Attachment added: "devices.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937056/+attachment/5513973/+files/devices.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937056 Title: Touchpad not working with ASUS TUF F15 Status in linux package in Ubuntu: Incomplete Bug description: I am using Kubuntu 21.04 on my ASUS TUF F15 FX506HM_FX566HM. The touchpad isn't detected in Settings and neither in xinput, nor in cat /proc/bus/input/devices. Laptop model: ASUS TUF F15 FX506HM_FX566HM. Manufacturer of the Touchpad: Touchpad not detected When the symptom first appeared: From beginning Output of lsb_release -rd Description:Ubuntu 21.04 Release:21.04 Using kernel version 5.13.5. Also tried 5.13.1, 5.13.2, 5.13.4, 5.12.15, 5.11 Output of xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Asus Wireless Radio Control id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=11 [slave keyboard (3)] ↳ Intel HID events id=12 [slave keyboard (3)] ↳ Intel HID 5 button array id=13 [slave keyboard (3)] ↳ Asus WMI hotkeys id=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)] Output of lspci :00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 05) :00:01.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #1 (rev 05) :00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) :00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 05) :00:06.0 System peripheral: Intel Corporation Device 09ab :00:07.0 PCI bridge: Intel Corporation Tiger Lake-H Thunderbolt 4 PCI Express Root Port #0 (rev 05) :00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 05) :00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01) :00:0d.0 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 USB Controller (rev 05) :00:0d.2 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 NHI #0 (rev 05) :00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller :00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11) :00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11) :00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H Serial IO I2C Controller #0 (rev 11) :00:16.0 Communication controller: Intel Corporation Tiger Lake-H Management Engine Interface (rev 11) :00:1c.0 PCI bridge: Intel Corporation Device 43bf (rev 11) :00:1d.0 PCI bridge: Intel Corporation Device 43b6 (rev 11) :00:1f.0 ISA bridge: Intel Corporation Tiger Lake-H LPC/eSPI Controller (rev 11) :00:1f.3 Audio device: Intel Corporation Tiger Lake-H HD Audio Controller (rev 11) :00:1f.4 SMBus: Intel Corporation Tiger Lake-H SMBus Controller (rev 11) :00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H SPI Controller (rev 11) :01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1) :01:00.1 Audio device: NVIDIA Corporation Device 228e (rev a1) :2d:00.0 Network controller: MEDIATEK Corp. Device 7961 :2e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 1:e0:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #0 (rev 05) 1:e1:00.0 Non-Volatile memory controller: SK hynix Device 174a --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-25 (1 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: linux (not installed) Tag
[Kernel-packages] [Bug 1937056] Re: Touchpad not working with ASUS TUF F15
Output of dmesg ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937056/+attachment/5513975/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937056 Title: Touchpad not working with ASUS TUF F15 Status in linux package in Ubuntu: Incomplete Bug description: I am using Kubuntu 21.04 on my ASUS TUF F15 FX506HM_FX566HM. The touchpad isn't detected in Settings and neither in xinput, nor in cat /proc/bus/input/devices. Laptop model: ASUS TUF F15 FX506HM_FX566HM. Manufacturer of the Touchpad: Touchpad not detected When the symptom first appeared: From beginning Output of lsb_release -rd Description:Ubuntu 21.04 Release:21.04 Using kernel version 5.13.5. Also tried 5.13.1, 5.13.2, 5.13.4, 5.12.15, 5.11 Output of xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Asus Wireless Radio Control id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=11 [slave keyboard (3)] ↳ Intel HID events id=12 [slave keyboard (3)] ↳ Intel HID 5 button array id=13 [slave keyboard (3)] ↳ Asus WMI hotkeys id=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)] Output of lspci :00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 05) :00:01.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #1 (rev 05) :00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) :00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 05) :00:06.0 System peripheral: Intel Corporation Device 09ab :00:07.0 PCI bridge: Intel Corporation Tiger Lake-H Thunderbolt 4 PCI Express Root Port #0 (rev 05) :00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 05) :00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01) :00:0d.0 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 USB Controller (rev 05) :00:0d.2 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 NHI #0 (rev 05) :00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller :00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11) :00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11) :00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H Serial IO I2C Controller #0 (rev 11) :00:16.0 Communication controller: Intel Corporation Tiger Lake-H Management Engine Interface (rev 11) :00:1c.0 PCI bridge: Intel Corporation Device 43bf (rev 11) :00:1d.0 PCI bridge: Intel Corporation Device 43b6 (rev 11) :00:1f.0 ISA bridge: Intel Corporation Tiger Lake-H LPC/eSPI Controller (rev 11) :00:1f.3 Audio device: Intel Corporation Tiger Lake-H HD Audio Controller (rev 11) :00:1f.4 SMBus: Intel Corporation Tiger Lake-H SMBus Controller (rev 11) :00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H SPI Controller (rev 11) :01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1) :01:00.1 Audio device: NVIDIA Corporation Device 228e (rev a1) :2d:00.0 Network controller: MEDIATEK Corp. Device 7961 :2e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 1:e0:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #0 (rev 05) 1:e1:00.0 Non-Volatile memory controller: SK hynix Device 174a --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-25 (1 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: linux (not installed) Tags: hirsute Uname: Linux
[Kernel-packages] [Bug 1937031] Re: GPF in rtl2832
Hiya - I went for it - uninstalled various modules and installed the latest mainline kernel - 5.13.5 - and the problem no longer occurs. I installed from the .deb on https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.13.5/amd64/ Cheers James -- 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/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: Incomplete Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+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 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
I am currently using the 5.13.5 kernel from the Ubuntu kernel team here: https://kernel.ubuntu.com/~kernel-ppa/mainline/ I have also tested the 5.14.0rc2 kernel from the same repo. Can give rc3 a try too. -- 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/1938096 Title: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from the impish repos. To recreate: 1. Reboot a X1C9 machine and see that the touchpad works fine 2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a software suspend) 3. Resume from suspend and see that touchpad acts differently and less responsive than right after a clean boot What is expected: 1. Same responsive touchpad experience after resuming from suspend as right after a clean boot. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: pop:GNOME DistUpgraded: Fresh install DistroCodename: hirsute DistroRelease: Pop!_OS 21.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Xe Graphics [17aa:22d5] MachineType: LENOVO 20XW005PMX Package: libinput10 1.18.0-1 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet systemd.show_status=false loglevel=0 splash Tags: hirsute third-party-packages ubuntu Uname: Linux 5.13.5-051305-generic x86_64 UnreportableReason: This does not seem to be an official Pop!_OS package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 06/15/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET66W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XW005PMX 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.26 dmi.modalias: dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XW005PMX dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2pop0~1624392450~21.04~6fbdfd2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1938096/+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 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1938096 Title: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from the impish repos. To recreate: 1. Reboot a X1C9 machine and see that the touchpad works fine 2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a software suspend) 3. Resume from suspend and see that touchpad acts differently and less responsive than right after a clean boot What is expected: 1. Same responsive touchpad experience after resuming from suspend as right after a clean boot. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: pop:GNOME DistUpgraded: Fresh install DistroCodename: hirsute DistroRelease: Pop!_OS 21.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Xe Graphics [17aa:22d5] MachineType: LENOVO 20XW005PMX Package: libinput10 1.18.0-1 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet systemd.show_status=false loglevel=0 splash Tags: hirsute third-party-packages ubuntu Uname: Linux 5.13.5-051305-generic x86_64 UnreportableReason: This does not seem to be an official Pop!_OS package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 06/15/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET66W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XW005PMX 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.26 dmi.modalias: dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XW005PMX dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2pop0~1624392450~21.04~6fbdfd2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1938096/+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 1927749] Re: ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8
** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Released ** Changed in: ubuntu-kernel-tests Status: In Progress => 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/1927749 Title: ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8 Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Invalid Status in linux-aws source package in Focal: New Status in linux source package in Groovy: Fix Committed Status in linux-aws source package in Groovy: New Status in linux source package in Hirsute: Fix Committed Status in linux-aws source package in Hirsute: New Status in linux source package in Impish: Fix Released Status in linux-aws source package in Impish: New Bug description: [Impact] arm64 only focal/aws 5.8.0-1031.33~20.04.1-aws and 5.8.0-1032.34~20.04.1-aws - regression. Works fine on previous Focal cycle (5.8.0-1028.30~20.04.3-aws) and current Groovy 5.8. 12. 05/06 07:01:39 DEBUG| utils:0153| [stdout] TAP version 13 13. 05/06 07:01:39 DEBUG| utils:0153| [stdout] 1..1 14. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 15. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 16. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 17. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 18. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 19. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check [PASS] 20. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 21. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 22. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 23. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct functions against tracers [UNRESOLVED] 24. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] 25. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - add/remove kprobe events [PASS] 26. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - add/remove synthetic events [PASS] 27. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event - selective clear (compatibility) [PASS] 28. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event - generic clear event [PASS] 29. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with event level files [PASS] 30. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [15] event tracing - restricts events based on pid notrace filtering [FAIL] 31. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [16] event tracing - restricts events based on pid [PASS] 32. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [17] event tracing - enable/disable with subsystem level files [PASS] 33. 05/06 07:01:46 DEBUG| utils:0153| [stdout] # [18] event tracing - enable/disable with top level files [PASS] [Test Plan] * Run ftrace test from kernel selftests. [Where problems could occur] * Only kernel selftests should be affected. * ftrace test can have false positives or negatives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927749/+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 1875263] Re: linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan
** Changed in: linux-firmware (Ubuntu) Status: Fix Committed => Fix Released -- 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/1875263 Title: linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan Status in OEM Priority Project: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Released Status in linux-firmware source package in Eoan: Fix Released Bug description: [Impact] some ubuntu eoan/bionic users reported that the audio driver failed to initialize, then the audio didn't work. I checked the dmesg, found the sof driver planed to load sof-cfl.ri, but there is no this firmware under eoan or bionic. [Fix] I consulted with Intel audio team, they told me that the coffeelake platform could share the firmware with cnl/whl platoforms, so we could build a symbol link sof-cfl->sof-cnl. [Test Case] A couple of ubuntu users already tested it on Dell and Asus coffeelake laptops, it worked well. [Regression Risk] Low, users already tested it, and Intel audio team confirmed it is safe. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1875263/+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 1936452] Re: [SRU][F/H/I] Add MT7921 wifi fw
** Changed in: linux-firmware (Ubuntu Impish) Importance: Undecided => High -- 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/1936452 Title: [SRU][F/H/I] Add MT7921 wifi fw Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Hirsute: New Status in linux-firmware source package in Impish: New Bug description: SRU justification: [Impact] No support for MT7921 wifi card. [Fix] MT7921 needs both driver and firmware, driver is almost ready, add firmware first, then get driver bug fixed later. [Test] Verified on hardware, cold boot system wifi works fine. Reboot make it fail, but I will fix it in SRU of kernel patch. After that, it works fine. [Where problems could occur] The MT7921 wifi may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936452/+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 1931900] Re: Linux-firmware 1.197.1 breaks dual monitor on RX480, shows mirror display with "Unknown Device" under GUI
** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Invalid -- 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/1931900 Title: Linux-firmware 1.197.1 breaks dual monitor on RX480, shows mirror display with "Unknown Device" under GUI Status in linux-firmware package in Ubuntu: Invalid Bug description: linux-firmware 1.197.1 after updating, breaks dual displays on hdmi with RX480 on kernel # lsb_release -a LSB Version: core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description: Ubuntu 21.04 Release: 21.04 Codename: hirsute # lshw -c video *-display description: VGA compatible controller product: Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 logical name: /dev/fb0 version: c7 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom fb configuration: depth=32 driver=amdgpu latency=0 mode=1920x1080 visual=truecolor xres=1920 yres=1080 resources: iomemory:420-41f iomemory:410-40f irq:143 memory:42-43 memory:41-41001f ioport:3000(size=256) memory:5080-5083 memory:c-d # lspci -k | grep -EA3 'VGA|3D|Display' 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev c7) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 480 Kernel driver in use: amdgpu Kernel modules: amdgpu # glxinfo -B name of display: :0 display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: AMD (0x1002) Device: AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.40.0, 5.11.0-16-generic, LLVM 11.0.1) (0x67df) Version: 21.0.1 Accelerated: yes Video memory: 8192MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 Memory info (GL_ATI_meminfo): VBO free memory - total: 7571 MB, largest block: 7571 MB VBO free aux. memory - total: 7892 MB, largest block: 7892 MB Texture free memory - total: 7571 MB, largest block: 7571 MB Texture free aux. memory - total: 7892 MB, largest block: 7892 MB Renderbuffer free memory - total: 7571 MB, largest block: 7571 MB Renderbuffer free aux. memory - total: 7892 MB, largest block: 7892 MB Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 8192 MB Total available memory: 16384 MB Currently available dedicated video memory: 7571 MB OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.40.0, 5.11.0-16-generic, LLVM 11.0.1) OpenGL core profile version string: 4.6 (Core Profile) Mesa 21.0.1 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.0.1 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1931900/+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 1929439] Re: Not able to connect bluetooth microsoft designer mouse
** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929439 Title: Not able to connect bluetooth microsoft designer mouse Status in linux package in Ubuntu: Incomplete Bug description: The bluetooth on Ubuntu budgie is not showing Microsoft wireless designer mouse, but it works completely fine when I boot this laptop on windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.12 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.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: avtech 1000 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Mon May 24 10:52:08 2021 Dependencies: InstallationDate: Installed on 2021-05-22 (1 days ago) InstallationMedia: Ubuntu-Budgie 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210210.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY x360 m6 Convertible PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-53-generic root=UUID=4ee18edf-4d5d-42bc-be4d-52e744eeafff ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2020 dmi.bios.release: 15.61 dmi.bios.vendor: Insyde dmi.bios.version: F.61 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81AD dmi.board.vendor: HP dmi.board.version: 58.54 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 58.54 dmi.modalias: dmi:bvnInsyde:bvrF.61:bd11/09/2020:br15.61:efr58.54:svnHP:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHP:rn81AD:rvr58.54:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV dmi.product.name: HP ENVY x360 m6 Convertible dmi.product.sku: W2K45UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929439/+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 1918698] Re: Stale firmware symlink
** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released -- 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/1918698 Title: Stale firmware symlink Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Groovy: Fix Released Bug description: [Impact] On Groovy with linux-firmware 1.190.3: lrwxrwxrwx 1 root root 54 Jan 7 15:40 brcmfmac43455-sdio.raspberrypi,3-model-a-plus.txt -> brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt That link target is wrong and doesn't exist, it should be without the 'brcm/' prefix. [Test Case] $ ls -la /lib/firmware/brcm/brcmfmac43455* [Fix] The upstream fix is: commit a9993f8d3b241f70a691a5b81bf2cdb442c0e184 Author: Takashi Iwai Date: Tue Sep 8 12:16:56 2020 +0200 brcm: Fix a stale symlink for RPi3 model b+ The symlink for brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt was wrongly listed with the same subdirectory brcm, and this resulted in a stale symlink. Fix it. Signed-off-by: Takashi Iwai Signed-off-by: Josh Boyer [Where Problems Could Occur] Firmware is now loaded on Pi 3A+ at boot which didn't happen before so theoretically that could crash the kernel if it's buggy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1918698/+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 1938143] [NEW] Include product_sku info to modalias
Public bug reported: [Impact] When we add DMI quirks for the new platforms, it's hard to prevent from leaking its model name. Our customer doesn't like it. [Fix] Introduce the product sku modalias to DMI table, so that we can use more meaningless product sku string to match the platform. [Test] No real DMI quirk is added in this commit, so need to do any tests. [Where problems could occur] It's safe to add one more DMI entry, nothing could be affected. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938143 Title: Include product_sku info to modalias Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.10 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 Bug description: [Impact] When we add DMI quirks for the new platforms, it's hard to prevent from leaking its model name. Our customer doesn't like it. [Fix] Introduce the product sku modalias to DMI table, so that we can use more meaningless product sku string to match the platform. [Test] No real DMI quirk is added in this commit, so need to do any tests. [Where problems could occur] It's safe to add one more DMI entry, nothing could be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938143/+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 1932965] Re: selftests/net/rtnetlink - Failure in RISC-V (uuidgen command not found)
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-kernel-tests Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932965 Title: selftests/net/rtnetlink - Failure in RISC-V (uuidgen command not found) Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: Invalid Bug description: Found this on G/RISC-V, cycle sru-20210531: 02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found 02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found 02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found 02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found 02:41:52 DEBUG| [stdout] # FAIL: set interface alias test-dummy0 to 02:41:52 DEBUG| [stdout] # PASS: vrf 02:41:54 DEBUG| [stdout] # PASS: vxlan 02:41:55 DEBUG| [stdout] # PASS: fou 02:41:55 DEBUG| [stdout] # PASS: macsec 02:41:58 DEBUG| [stdout] # PASS: ipsec 02:42:01 DEBUG| [stdout] # PASS: ipsec_offload 02:42:02 DEBUG| [stdout] # PASS: bridge fdb get 02:42:03 DEBUG| [stdout] # PASS: neigh get 02:42:03 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1 Seems uuidgen is from package "uuid-runtime", not sure if this was not installed in the environment where test ran. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1932965/+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 1938143] Re: Include product_sku info to modalias
** Description changed: [Impact] + When we add DMI quirks for the new platforms, it's hard to prevent from leaking its model name. Our customer doesn't like it. [Fix] + Introduce the product sku modalias to DMI table, so that we can use more meaningless product sku string to match the platform. [Test] + No real DMI quirk is added in this commit, so need to do any tests. [Where problems could occur] + It's safe to add one more DMI entry, nothing could be affected. ** Tags added: oem-priority originate-from-1895110 somerville -- 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/1938143 Title: Include product_sku info to modalias Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.10 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 Bug description: [Impact] When we add DMI quirks for the new platforms, it's hard to prevent from leaking its model name. Our customer doesn't like it. [Fix] Introduce the product sku modalias to DMI table, so that we can use more meaningless product sku string to match the platform. [Test] No real DMI quirk is added in this commit, so need to do any tests. [Where problems could occur] It's safe to add one more DMI entry, nothing could be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1938143/+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 1932965] Re: selftests/net/rtnetlink - Failure in RISC-V (uuidgen command not found)
https://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/commit/?id=0ecd2f325f0983803ecf470728da97daad144ca5 ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932965 Title: selftests/net/rtnetlink - Failure in RISC-V (uuidgen command not found) Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: Invalid Bug description: Found this on G/RISC-V, cycle sru-20210531: 02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found 02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found 02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found 02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found 02:41:52 DEBUG| [stdout] # FAIL: set interface alias test-dummy0 to 02:41:52 DEBUG| [stdout] # PASS: vrf 02:41:54 DEBUG| [stdout] # PASS: vxlan 02:41:55 DEBUG| [stdout] # PASS: fou 02:41:55 DEBUG| [stdout] # PASS: macsec 02:41:58 DEBUG| [stdout] # PASS: ipsec 02:42:01 DEBUG| [stdout] # PASS: ipsec_offload 02:42:02 DEBUG| [stdout] # PASS: bridge fdb get 02:42:03 DEBUG| [stdout] # PASS: neigh get 02:42:03 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1 Seems uuidgen is from package "uuid-runtime", not sure if this was not installed in the environment where test ran. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1932965/+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 1934660] Re: intel_pmc_core driver is not probed on ADL
Roland, we're not going to backport since current generic kernels don't support Alder Lake. -- 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/1934660 Title: intel_pmc_core driver is not probed on ADL Status in HWE Next: New 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: Fix Released Bug description: [SRU Justification] [Impact] Missing driver for pmc_core on Intel Alder Lake platforms. [Fix] https://patchwork.kernel.org/project/platform- driver-x86/cover/cover.1625191274.git.gayatri.kamm...@intel.com/ [Test Case] $ ls /sys/bus/platform/drivers/intel_pmc_core ... INT33A1:00 [Where problems could occur] This adds driver support for a new platform. No regression by the definition can happen, but it may still suffer from incompleteness of userspace utility support. [Other Info] Alder Lake targets 5.13 kernels, so only Impish & oem-5.13 is proposed. == original bug description == [Summary] intel_pmc_core driver is not probed [Reproduce Steps] 1. $ ls /sys/bus/platform/drivers/intel_pmc_core 2. No INT33A1:00 device under the directory [Results] Expected: INT33A1:00 device is shown in the intel_pmc_core directory Actual: No device probed by intel_pmc_core successfully To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1934660/+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 1936255] Please test proposed package
Hello Seth, or anyone else affected, Accepted wireless-regdb into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireless- regdb/2021.07.14-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1936255 Title: New upstream release 2021.07.14 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Trusty: In Progress Status in wireless-regdb source package in Xenial: In Progress Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Groovy: Won't Fix Status in wireless-regdb source package in Hirsute: Fix Committed Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1936255/+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 1936255] Re: New upstream release 2021.07.14
Hello Seth, or anyone else affected, Accepted wireless-regdb into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireless- regdb/2021.07.14-0ubuntu1~21.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: wireless-regdb (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute ** Changed in: wireless-regdb (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1936255 Title: New upstream release 2021.07.14 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Trusty: In Progress Status in wireless-regdb source package in Xenial: In Progress Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Groovy: Won't Fix Status in wireless-regdb source package in Hirsute: Fix Committed Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1936255/+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 1936255] Please test proposed package
Hello Seth, or anyone else affected, Accepted wireless-regdb into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireless- regdb/2021.07.14-0ubuntu1~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: wireless-regdb (Ubuntu Groovy) Status: In Progress => Won't Fix ** Changed in: wireless-regdb (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1936255 Title: New upstream release 2021.07.14 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Trusty: In Progress Status in wireless-regdb source package in Xenial: In Progress Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Groovy: Won't Fix Status in wireless-regdb source package in Hirsute: Fix Committed Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1936255/+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 1930188] Re: Acer Aspire 5 sound driver issues
** Changed in: linux (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+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 1936255] Re: New upstream release 2021.07.14
Okay, accepted all of those that I could (groovy is now EOL and xenial is almost-ESM). But only after accepting them I noticed that those were source syncs (and anyway the PPA had -updates enabled) - wireless-regdb is usually kept in sync between updates and security. So normally I'd say we need this to be built in a security-enabled PPA. So if we want to release this to both updates and security, we either need to do a rebuild now or ask the security team to do one and release it to their pockets. That being said, I wonder if that's actually necessary. This feels like rather no-build-stuff package, so maybe it's still safe to get this into -security without a rebuild? Is the package actually doing any 'building', or just copying files around? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1936255 Title: New upstream release 2021.07.14 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Trusty: In Progress Status in wireless-regdb source package in Xenial: In Progress Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Groovy: Won't Fix Status in wireless-regdb source package in Hirsute: Fix Committed Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1936255/+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 1938149] [NEW] To support AMD W6600 and W6700
Public bug reported: [Impact] To support AMD Radeon Pro W6600/W6700 graphic card, we need some new firmware. [Fix] AMD suggests us to include below 2 commits, and to avoid conflicts I cherry pick sienna cichlid firmware from the beginning when it's been added. amdgpu: add initial dimgrey cavefish firmware from 21.20 https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=87619e4114cc631efcb6868dca54d481dc467034 amdgpu: update sienna cichlid firmware from 21.20 https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=4043da4f77f84b75a0f818ab7e83ead187ebf441 [Test] [Where problems could occur] ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Impish) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1938149 Title: To support AMD W6600 and W6700 Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Hirsute: New Status in linux-firmware source package in Impish: New Bug description: [Impact] To support AMD Radeon Pro W6600/W6700 graphic card, we need some new firmware. [Fix] AMD suggests us to include below 2 commits, and to avoid conflicts I cherry pick sienna cichlid firmware from the beginning when it's been added. amdgpu: add initial dimgrey cavefish firmware from 21.20 https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=87619e4114cc631efcb6868dca54d481dc467034 amdgpu: update sienna cichlid firmware from 21.20 https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=4043da4f77f84b75a0f818ab7e83ead187ebf441 [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1938149/+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 1938149] Re: To support AMD W6600 and W6700
** No longer affects: linux-firmware (Ubuntu Impish) ** Changed in: linux-firmware (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-firmware (Ubuntu Hirsute) Assignee: (unassigned) => AceLan Kao (acelankao) ** Description changed: [Impact] To support AMD Radeon Pro W6600/W6700 graphic card, we need some new firmware. [Fix] - AMD suggests us to include below 2 commits, and to avoid conflicts I cherry pick sienna cichlid firmware from the beginning when it's been added. + AMD suggests us to include below 2 commits, and to avoid conflicts I cherry pick sienna cichlid firmware from the beginning when it's been added. Impish already have both commits. amdgpu: add initial dimgrey cavefish firmware from 21.20 https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=87619e4114cc631efcb6868dca54d481dc467034 amdgpu: update sienna cichlid firmware from 21.20 https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=4043da4f77f84b75a0f818ab7e83ead187ebf441 [Test] [Where problems could occur] -- 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/1938149 Title: To support AMD W6600 and W6700 Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: In Progress Status in linux-firmware source package in Hirsute: In Progress Bug description: [Impact] To support AMD Radeon Pro W6600/W6700 graphic card, we need some new firmware. [Fix] AMD suggests us to include below 2 commits, and to avoid conflicts I cherry pick sienna cichlid firmware from the beginning when it's been added. Impish already have both commits. amdgpu: add initial dimgrey cavefish firmware from 21.20 https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=87619e4114cc631efcb6868dca54d481dc467034 amdgpu: update sienna cichlid firmware from 21.20 https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=4043da4f77f84b75a0f818ab7e83ead187ebf441 [Test] Verified on AMD Radeon Pro W6600 graphic card. [Where problems could occur] This series of patches introduce dimgrey cavefish and sienna cichlid firmware. The 2 GPUs are still new and have little chance to affect old platforms, should be safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1938149/+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 1938149] Re: To support AMD W6600 and W6700
** Description changed: [Impact] To support AMD Radeon Pro W6600/W6700 graphic card, we need some new firmware. [Fix] AMD suggests us to include below 2 commits, and to avoid conflicts I cherry pick sienna cichlid firmware from the beginning when it's been added. Impish already have both commits. amdgpu: add initial dimgrey cavefish firmware from 21.20 https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=87619e4114cc631efcb6868dca54d481dc467034 amdgpu: update sienna cichlid firmware from 21.20 https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=4043da4f77f84b75a0f818ab7e83ead187ebf441 [Test] + Verified on AMD Radeon Pro W6600 graphic card. [Where problems could occur] + This series of patches introduce dimgrey cavefish and sienna cichlid firmware. The 2 GPUs are still new and have little chance to affect old platforms, should be safe to include them. -- 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/1938149 Title: To support AMD W6600 and W6700 Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: In Progress Status in linux-firmware source package in Hirsute: In Progress Bug description: [Impact] To support AMD Radeon Pro W6600/W6700 graphic card, we need some new firmware. [Fix] AMD suggests us to include below 2 commits, and to avoid conflicts I cherry pick sienna cichlid firmware from the beginning when it's been added. Impish already have both commits. amdgpu: add initial dimgrey cavefish firmware from 21.20 https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=87619e4114cc631efcb6868dca54d481dc467034 amdgpu: update sienna cichlid firmware from 21.20 https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=4043da4f77f84b75a0f818ab7e83ead187ebf441 [Test] Verified on AMD Radeon Pro W6600 graphic card. [Where problems could occur] This series of patches introduce dimgrey cavefish and sienna cichlid firmware. The 2 GPUs are still new and have little chance to affect old platforms, should be safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1938149/+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 1938126] Re: System hangs up or make filesystem read-only
I didn't try the SysRq commands, as I didn't know about them. My impression was, that everything just stopped working, nothing except the hard reset seemed to cause any reaction, hardware or otherwise. The syslog didn't show anything unusual either. I compared several versions of the syslog after different freezes and didn't find any similarities in the last 5 minutes before it stopped working. A co-worker using Ubuntu 18.04. and kernel 4.15.0-151 also reported problems with freezes, that didn't occur in 4.15.0-147, but he didnt have the RO filesystem problem. I will check whether the SysRq commands work the next freeze. -- 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/1938126 Title: System hangs up or make filesystem read-only Status in linux package in Ubuntu: New Bug description: With kernel 4.15.0-151 the system very often (up to several times an hour) hangs up completely and doesn't react to input of any kind. It then has to be restarted the hard way (i.e. by prssing the power button for several seconds). At other times a message is displayed, saying that the file system is read-only, nothing can be saved to the hard disk anymore (i.e. no files written by applications like QtCreator). These problems haven't been observed after booting kernel 4.15.0-147. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-151-generic 4.15.0-151.157 ProcVersionSignature: Ubuntu 4.15.0-151.157-generic 4.15.18 Uname: Linux 4.15.0-151-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ymau 3910 F pulseaudio /dev/snd/controlC1: ymau 3910 F pulseaudio /dev/snd/controlC3: ymau 3910 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jul 27 07:57:48 2021 MachineType: LENOVO 20AN00E3GE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-151-generic root=UUID=61548d74-4a1e-4042-a755-9d9879c39a93 ro splash quiet vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-151-generic N/A linux-backports-modules-4.15.0-151-generic N/A linux-firmware 1.173.20 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: GLETA1WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00E3GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLETA1WW(2.55):bd04/20/2020:svnLENOVO:pn20AN00E3GE:pvrThinkPadT440p:rvnLENOVO:rn20AN00E3GE:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00E3GE dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938126/+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 1932165] Re: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Hello Kleber, or anyone else affected, Accepted lttng-modules into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lttng- modules/2.12.5-1ubuntu2~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: lttng-modules (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-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/1932165 Title: lttng-modules/2.12.2-1ubuntu1~20.04.2 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 lttng-modules package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in lttng-modules source package in Focal: Fix Committed Bug description: [Impact] lttng-modules-dkms is reporting many build errors with linux-hwe-5.11, because of many kernel ABI changes. [Fix] Backporting the individual patches to fix all the build errors would be a lot of work and the risk to introduce regressions would be pretty high, therefore it seems safer to update to the version that is also used in impish, that works with 5.11 and it's backward compatible (so it works also with 5.4). [Test] ubuntu_lttng_smoke_test from (git://kernel.ubuntu.com/ubuntu/autotest- client-tests) [Where problems could occur] This is a major version update, so it does not contain trivial changes as backporting individual patches/fixes, so there's a risk to see regressions with lttng (however potential regressions are *only* limited to lttng). However, this way is definitely safer than backporting all the individual changes to fix the all the kernel ABI changes introduced in 5.11. [Original bug report] This is a scripted bug report about ADT failures while running lttng- modules 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/l/lttng-modules/20210611_205859_b8295@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210612_123048_fc99b@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210611_210510_27086@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210611_210134_272f4@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932165/+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 1932165] Re: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
I also agree that maybe we should get the same package backported to hirsute? -- 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/1932165 Title: lttng-modules/2.12.2-1ubuntu1~20.04.2 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 lttng-modules package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in lttng-modules source package in Focal: Fix Committed Bug description: [Impact] lttng-modules-dkms is reporting many build errors with linux-hwe-5.11, because of many kernel ABI changes. [Fix] Backporting the individual patches to fix all the build errors would be a lot of work and the risk to introduce regressions would be pretty high, therefore it seems safer to update to the version that is also used in impish, that works with 5.11 and it's backward compatible (so it works also with 5.4). [Test] ubuntu_lttng_smoke_test from (git://kernel.ubuntu.com/ubuntu/autotest- client-tests) [Where problems could occur] This is a major version update, so it does not contain trivial changes as backporting individual patches/fixes, so there's a risk to see regressions with lttng (however potential regressions are *only* limited to lttng). However, this way is definitely safer than backporting all the individual changes to fix the all the kernel ABI changes introduced in 5.11. [Original bug report] This is a scripted bug report about ADT failures while running lttng- modules 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/l/lttng-modules/20210611_205859_b8295@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210612_123048_fc99b@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210611_210510_27086@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210611_210134_272f4@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932165/+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
Hello John, or anyone else affected, Accepted zfs-linux into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/0.8.3-1ubuntu12.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: zfs-linux (Ubuntu Focal) Status: In Progress => Fix Committed -- 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: Fix Committed Bug description: [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. Below is a list of suggested test scenarios that we should check for regressions: 1. ZFS-on-root + encrypted swap (see "Test Plan" section above) 2. Encrypted root + separate ZFS partitions 3. ZFS on LUKS 4. ZFS on dm-raid Although scenario 4 is usually advised against (ZFS itself should handle RAID), it's a good smoke test to validate that mount order is being handled correctly. [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
[Kernel-packages] [Bug 1937147] Re: Touchpad not working at all
The touchpad hit the error per the dmesg [1.731362] i2c_hid i2c-HTIX5288:00: supply vdd not found, using dummy regulator [1.731414] i2c_hid i2c-HTIX5288:00: supply vddl not found, using dummy regulator [1.733579] i2c_hid i2c-HTIX5288:00: weird size of HID descriptor (5) [1.733586] i2c_hid i2c-HTIX5288:00: Failed to fetch the HID Descriptor Could your provide the output of the command "cat /sys/class/dmi/id/sys_vendor"? -- 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/1937147 Title: Touchpad not working at all Status in linux package in Ubuntu: New Bug description: Using Ubuntu 20.04. Trackpad very occasionally works on boot, but rebooting causes it to not work again. Ive tried installing synaptics drivers and the like. But nothing works, Not even Updating to ubuntu 21.04. It doesnt even work on Mint or Lubuntu either. Ive tried everything pls help. The trackpad doesnt appear to be detected by the system on 99% of boot ups. But very occasionaly it will. Im using a bluetooth mouse to do this right now so that is what is shown below. But otherwise the touchpad is not detected at all. The one time I got it to detect the touchpad it showed up as a bunch of "Unknown"s in the input device list. I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:03/PNP0C09: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=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID events" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input3 U: Uniq= H: Handlers=rfkill kbd event3 B: PROP=0 B: EV=13 B: KEY=810003 504000 1e29400020 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID 5 button array" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=13 B: KEY=2 0 0 0 0 1 0 201c 0 B: MSC=10 I: Bus=0003 Vendor=0c45 Product=6366 Version=0100 N: Name="USB 2.0 Camera: USB Camera" P: Phys=usb-:00:15.0-7/button S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-7/1-7:1.0/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 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 event6 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input7 U: Uniq= H: Handlers=event7 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:0e.0/sound/card0/input8 U: Uniq= H: Handlers=event8 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:0e.0/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input13 U: Uniq= H: Handlers=e
[Kernel-packages] [Bug 1937056] Re: Touchpad not working with ASUS TUF F15
** Description changed: I am using Kubuntu 21.04 on my ASUS TUF F15 FX506HM_FX566HM. The touchpad isn't detected in Settings and neither in xinput, nor in cat /proc/bus/input/devices. Laptop model: ASUS TUF F15 FX506HM_FX566HM. - Manufacturer of the Touchpad: Touchpad not detected + Manufacturer of the Touchpad: Probably ELAN1203 When the symptom first appeared: From beginning Output of lsb_release -rd Description:Ubuntu 21.04 Release:21.04 Using kernel version 5.13.5. Also tried 5.13.1, 5.13.2, 5.13.4, 5.12.15, 5.11 Output of xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Asus Wireless Radio Control id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=11 [slave keyboard (3)] ↳ Intel HID events id=12 [slave keyboard (3)] ↳ Intel HID 5 button array id=13 [slave keyboard (3)] ↳ Asus WMI hotkeys id=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)] Output of lspci :00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 05) :00:01.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #1 (rev 05) :00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) :00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 05) :00:06.0 System peripheral: Intel Corporation Device 09ab :00:07.0 PCI bridge: Intel Corporation Tiger Lake-H Thunderbolt 4 PCI Express Root Port #0 (rev 05) :00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 05) :00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01) :00:0d.0 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 USB Controller (rev 05) :00:0d.2 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 NHI #0 (rev 05) :00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller :00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11) :00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11) :00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H Serial IO I2C Controller #0 (rev 11) :00:16.0 Communication controller: Intel Corporation Tiger Lake-H Management Engine Interface (rev 11) :00:1c.0 PCI bridge: Intel Corporation Device 43bf (rev 11) :00:1d.0 PCI bridge: Intel Corporation Device 43b6 (rev 11) :00:1f.0 ISA bridge: Intel Corporation Tiger Lake-H LPC/eSPI Controller (rev 11) :00:1f.3 Audio device: Intel Corporation Tiger Lake-H HD Audio Controller (rev 11) :00:1f.4 SMBus: Intel Corporation Tiger Lake-H SMBus Controller (rev 11) :00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H SPI Controller (rev 11) :01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1) :01:00.1 Audio device: NVIDIA Corporation Device 228e (rev a1) :2d:00.0 Network controller: MEDIATEK Corp. Device 7961 :2e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 1:e0:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #0 (rev 05) 1:e1:00.0 Non-Volatile memory controller: SK hynix Device 174a --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-25 (1 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.5-051305-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to hirsute on 2021-07-25 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Kernel Packages, which is sub
[Kernel-packages] [Bug 1938013] Re: 4.15.0-151 is freezing intel 5th gen ThinkPad (T450)
I think all data is a little inconclusive. There are things across many places which seem to go wrong in seemingly random patterns. Which makes me a little suspicious about locking (alternatively maybe memory management). Looking over the changes there was mutex change which seems subtly different than the change made to upstream kernels. Not obviously different enough to be a clear suspect but maybe worth trying. For this I would need someone volunteering to try the kernel I prepared at https://launchpad.net/~smb/+archive/ubuntu/bionic (still needs to finish building some arches). This is not a officially signed kernel, so it only should be tried if secure-boot is not used or can be disabled. The PPA can be added with "sudo apt-add-repository ppa:smb/bionic" (same command can also be used with --remove to get rid of it later). -- 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/1938013 Title: 4.15.0-151 is freezing intel 5th gen ThinkPad (T450) Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From: https://askubuntu.com/questions/1353859/ubuntu-18-04-05-lts- desktop-hangs-with-since-kernel-4-15-0-151-and-systemd-237-3 Several crashes in /var/crash, here's the last one:- ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Date: Fri Jul 23 18:10:54 2021 Failure: oops OopsText: BUG: Bad rss-counter state mm:c098a229 idx:2 val:-1 usblp0: removed usblp 1-5:1.0: usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04F9 pid 0x02EC <44>[ 18.329026] systemd-journald[358]: File /var/log/journal/b022dca21fd4480baeeb84f47ab439d3/user-1000.journal corrupted or uncleanly shut down, renaming and replacing. vboxdrv: loading out-of-tree module taints kernel. vboxdrv: module verification failed: signature and/or required key missing - tainting kernel vboxdrv: Found 8 processor cores vboxdrv: TSC mode is Invariant, tentative frequency 2303999142 Hz vboxdrv: Successfully loaded version 6.1.24 r145767 (interface 0x0030) VBoxNetFlt: Successfully started. VBoxNetAdp: Successfully started. Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 rfkill: input handler disabled [UFW BLOCK] IN=enp3s0f1 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=enp3s0f1 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=enp3s0f1 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 Package: linux-image-4.15.0-151-generic 4.15.0-151.157 SourcePackage: linux Tags: kernel-oops Uname: Linux 4.15.0-151-generic x86_64 --- The system is a laptop from Entroware based on Clevo and has 8 logical CPUs:- Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 158 Model name: Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz Stepping:10 CPU MHz: 2000.295 CPU max MHz: 4000. CPU min MHz: 800. BogoMIPS:4599.93 Virtualisation: VT-x L1d cache: 32K L1i cache: 32K L2 cache:256K L3 cache:8192K NUMA node0 CPU(s): 0-7 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi
[Kernel-packages] [Bug 1937056] Re: Touchpad not working with ASUS TUF F15
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1937056 Title: Touchpad not working with ASUS TUF F15 Status in linux package in Ubuntu: New Bug description: I am using Kubuntu 21.04 on my ASUS TUF F15 FX506HM_FX566HM. The touchpad isn't detected in Settings and neither in xinput, nor in cat /proc/bus/input/devices. Laptop model: ASUS TUF F15 FX506HM_FX566HM. Manufacturer of the Touchpad: Probably ELAN1203 When the symptom first appeared: From beginning Output of lsb_release -rd Description:Ubuntu 21.04 Release:21.04 Using kernel version 5.13.5. Also tried 5.13.1, 5.13.2, 5.13.4, 5.12.15, 5.11 Output of xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Asus Wireless Radio Control id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=11 [slave keyboard (3)] ↳ Intel HID events id=12 [slave keyboard (3)] ↳ Intel HID 5 button array id=13 [slave keyboard (3)] ↳ Asus WMI hotkeys id=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)] Output of lspci :00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 05) :00:01.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #1 (rev 05) :00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) :00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 05) :00:06.0 System peripheral: Intel Corporation Device 09ab :00:07.0 PCI bridge: Intel Corporation Tiger Lake-H Thunderbolt 4 PCI Express Root Port #0 (rev 05) :00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 05) :00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01) :00:0d.0 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 USB Controller (rev 05) :00:0d.2 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 NHI #0 (rev 05) :00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller :00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11) :00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11) :00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H Serial IO I2C Controller #0 (rev 11) :00:16.0 Communication controller: Intel Corporation Tiger Lake-H Management Engine Interface (rev 11) :00:1c.0 PCI bridge: Intel Corporation Device 43bf (rev 11) :00:1d.0 PCI bridge: Intel Corporation Device 43b6 (rev 11) :00:1f.0 ISA bridge: Intel Corporation Tiger Lake-H LPC/eSPI Controller (rev 11) :00:1f.3 Audio device: Intel Corporation Tiger Lake-H HD Audio Controller (rev 11) :00:1f.4 SMBus: Intel Corporation Tiger Lake-H SMBus Controller (rev 11) :00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H SPI Controller (rev 11) :01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1) :01:00.1 Audio device: NVIDIA Corporation Device 228e (rev a1) :2d:00.0 Network controller: MEDIATEK Corp. Device 7961 :2e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 1:e0:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #0 (rev 05) 1:e1:00.0 Non-Volatile memory controller: SK hynix Device 174a --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-25 (1 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.5-051305-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel Up
[Kernel-packages] [Bug 1936255] Re: New upstream release 2021.07.14
I wonder if we should really just do binary copies of it, just like we do with shim. If we set it to be compressed with xz. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1936255 Title: New upstream release 2021.07.14 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Trusty: In Progress Status in wireless-regdb source package in Xenial: In Progress Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Groovy: Won't Fix Status in wireless-regdb source package in Hirsute: Fix Committed Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1936255/+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 1909005] Re: Ubuntu does not resume (wake up) from suspend
Hello, I have the same problem on a Dell Latitude 5490 Ubuntu 20.04.1 kernel 5.8.0-63-generic #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:08 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- 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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1936255] Re: New upstream release 2021.07.14
It's pure datafiles arch:all package without any runtime deps, thus it is safe to copy to -security as is. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1936255 Title: New upstream release 2021.07.14 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Trusty: In Progress Status in wireless-regdb source package in Xenial: In Progress Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Groovy: Won't Fix Status in wireless-regdb source package in Hirsute: Fix Committed Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1936255/+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 1936255] Re: New upstream release 2021.07.14
$ dpkg-query -W wireless-regdb wireless-regdb 2021.07.14-0ubuntu1~18.04.1 $ sudo iw reg set 00 $ sudo iw reg get global country 00: DFS-UNSET (2402 - 2472 @ 40), (N/A, 20), (N/A) (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) $ sudo iw reg set US $ sudo iw reg get global country US: DFS-FCC (2400 - 2472 @ 40), (N/A, 30), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN (57240 - 71000 @ 2160), (N/A, 40), (N/A) ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1936255 Title: New upstream release 2021.07.14 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Trusty: In Progress Status in wireless-regdb source package in Xenial: In Progress Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Groovy: Won't Fix Status in wireless-regdb source package in Hirsute: Fix Committed Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1936255/+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 1934873] Re: ubuntu_aufs_smoke_test fails on Focal cloud v5.11
** Description changed: + [Impact] + + * Several Focal v5.11 edge kernels are missing AUFS. + + * This is a regression against previous Focal kernels (v5.4 and v5.8) + because it is expected to support same set of features on v5.11. + + [Test Plan] + + * Run ubuntu_aufs_smoke_test autotest. + + [Where problems could occur] + + * Mounting AUFS file system could succeed introducing a variety of + failures due to bugs in AUFS. + lp:1925407 disabled the test for Hirsute but now we have v5.11 edge kernels on Focal and it fails the same. It's not a regression but test should be hinted. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1934873 Title: ubuntu_aufs_smoke_test fails on Focal cloud v5.11 Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux-aws-5.11 package in Ubuntu: New Status in linux-azure-5.11 package in Ubuntu: New Status in linux-gcp-5.11 package in Ubuntu: New Status in linux-oracle-5.11 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-aws-5.11 source package in Focal: New Status in linux-azure-5.11 source package in Focal: New Status in linux-gcp-5.11 source package in Focal: New Status in linux-oracle-5.11 source package in Focal: In Progress Bug description: [Impact] * Several Focal v5.11 edge kernels are missing AUFS. * This is a regression against previous Focal kernels (v5.4 and v5.8) because it is expected to support same set of features on v5.11. [Test Plan] * Run ubuntu_aufs_smoke_test autotest. [Where problems could occur] * Mounting AUFS file system could succeed introducing a variety of failures due to bugs in AUFS. lp:1925407 disabled the test for Hirsute but now we have v5.11 edge kernels on Focal and it fails the same. It's not a regression but test should be hinted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934873/+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 1934873] Re: ubuntu_aufs_smoke_test fails on Focal cloud v5.11
** Changed in: linux-oracle-5.11 (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux-oracle-5.11 (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-oracle-5.11 (Ubuntu) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1934873 Title: ubuntu_aufs_smoke_test fails on Focal cloud v5.11 Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux-aws-5.11 package in Ubuntu: New Status in linux-azure-5.11 package in Ubuntu: New Status in linux-gcp-5.11 package in Ubuntu: New Status in linux-oracle-5.11 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-aws-5.11 source package in Focal: New Status in linux-azure-5.11 source package in Focal: New Status in linux-gcp-5.11 source package in Focal: New Status in linux-oracle-5.11 source package in Focal: Fix Committed Bug description: [Impact] * Several Focal v5.11 edge kernels are missing AUFS. * This is a regression against previous Focal kernels (v5.4 and v5.8) because it is expected to support same set of features on v5.11. [Test Plan] * Run ubuntu_aufs_smoke_test autotest. [Where problems could occur] * Mounting AUFS file system could succeed introducing a variety of failures due to bugs in AUFS. lp:1925407 disabled the test for Hirsute but now we have v5.11 edge kernels on Focal and it fails the same. It's not a regression but test should be hinted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934873/+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 1937031] Re: GPF in rtl2832
now my system is crashing loads from nouveau... so i can't run this kernel for too long - is there any other information you need? -- 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/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: Incomplete Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+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 1934809] Re: Backport support for AMD SMU statistics
Sounds good, thanks. ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Won't Fix -- 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/1934809 Title: Backport support for AMD SMU statistics 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: Won't Fix Status in linux-oem-5.13 source package in Focal: New 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: [Impact] AMD RN and CZN SOC can collect extra debugging data for s0i3. This information is useful for finding problems with IP blocks not going into correct states. [Fix] The following patch series adds support for these stats and will be included in 5.14. https://patchwork.kernel.org/project/platform-driver-x86/patch/20210629084803.248498-2-shyam-sundar@amd.com/ [Test] Check for extra debugfs files on amd platform. Verify that s0i3 shows successful enter (counter increases to non-zero). [Where problems could occur] The code is only used on amd platforms in s2idle. It would be specific to those platforms and cases (where it is adding support for debugging). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934809/+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 1937147] Re: Touchpad not working at all
Could u try this kernel https://people.canonical.com/~mschiu77/lp1937147/v1/ and give me the output of the command "dmesg"? Thanks -- 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/1937147 Title: Touchpad not working at all Status in linux package in Ubuntu: New Bug description: Using Ubuntu 20.04. Trackpad very occasionally works on boot, but rebooting causes it to not work again. Ive tried installing synaptics drivers and the like. But nothing works, Not even Updating to ubuntu 21.04. It doesnt even work on Mint or Lubuntu either. Ive tried everything pls help. The trackpad doesnt appear to be detected by the system on 99% of boot ups. But very occasionaly it will. Im using a bluetooth mouse to do this right now so that is what is shown below. But otherwise the touchpad is not detected at all. The one time I got it to detect the touchpad it showed up as a bunch of "Unknown"s in the input device list. I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:03/PNP0C09: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=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID events" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input3 U: Uniq= H: Handlers=rfkill kbd event3 B: PROP=0 B: EV=13 B: KEY=810003 504000 1e29400020 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID 5 button array" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=13 B: KEY=2 0 0 0 0 1 0 201c 0 B: MSC=10 I: Bus=0003 Vendor=0c45 Product=6366 Version=0100 N: Name="USB 2.0 Camera: USB Camera" P: Phys=usb-:00:15.0-7/button S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-7/1-7:1.0/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 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 event6 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input7 U: Uniq= H: Handlers=event7 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:0e.0/sound/card0/input8 U: Uniq= H: Handlers=event8 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:0e.0/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=0c76 Product=153f Version=0100 N: Name="USB PnP Audio Device" P: Phys=usb-:00:15.0-5.4.4.3/input3 S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-5/1-5.4/1-5.4.4/1-5.4.4.3/1-5.4.4.3:1.3/0003:0C76:153F.0001/input/input14 U: Uniq= H:
[Kernel-packages] [Bug 1938013] Re: 4.15.0-151 is freezing intel 5th gen ThinkPad (T450)
[ 2196.470134] do_trap: 20 callbacks suppressed [ 2196.470137] traps: gdbus[1711] trap invalid opcode ip:7f4dcea47cbd sp:7f4dcbca4c20 error:0 in libc-2.27.so[7f4dce933000+1e7000] [ 2197.267081] general protection fault: [#1] SMP PTI [ 2197.267389] Modules linked in: rfcomm ccm cmac bnep nls_iso8859_1 snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_hdmi snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core arc4 snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec intel_rapl iwlmvm x86_pkg_temp_thermal intel_powerclamp snd_hda_core coretemp mac80211 snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi snd_seq iwlwifi kvm snd_seq_device snd_timer irqbypass intel_cstate intel_rapl_perf hp_wmi snd joydev sparse_keymap input_leds wmi_bmof serio_raw intel_wmi_thunderbolt uvcvideo btusb videobuf2_vmalloc btrtl cfg80211 btbcm videobuf2_memops btintel soundcore bluetooth videobuf2_v4l2 videobuf2_core mei_me videodev shpchp media ecdh_generic processor_thermal_device [ 2197.271405] mei int340x_thermal_zone intel_pch_thermal intel_soc_dts_iosf int3400_thermal mac_hid hp_wireless acpi_thermal_rel acpi_pad sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 pcbc i2c_algo_bit aesni_intel drm_kms_helper syscopyarea sysfillrect aes_x86_64 crypto_simd glue_helper cryptd sysimgblt fb_sys_fops psmouse r8169 ahci drm mii libahci wmi video [ 2197.274805] CPU: 0 PID: 1710 Comm: gmain Not tainted 4.15.0-151-generic #157-Ubuntu [ 2197.275250] Hardware name: HP HP Notebook/81EB, BIOS F.45 10/16/2018 [ 2197.275627] RIP: 0010:perf_event_release_kernel+0x2f/0x2f0 [ 2197.275947] RSP: 0018:9c440265bc68 EFLAGS: 00010246 [ 2197.276250] RAX: RBX: 6800 RCX: [ 2197.276665] RDX: 0040 RSI: 9c440265bc78 RDI: 6800 [ 2197.277082] RBP: 9c440265bcb8 R08: 8ab257656a88 R09: [ 2197.277493] R10: R11: R12: 8ab257652f00 [ 2197.277906] R13: 8ab257654218 R14: 8ab257652f00 R15: 8ab2598debb0 [ 2197.278323] FS: 7f4dcc4a6700() GS:8ab26ec0() knlGS: [ 2197.278796] CS: 0010 DS: ES: CR0: 80050033 [ 2197.279133] CR2: 7f420c008000 CR3: 000249a0a005 CR4: 003606f0 [ 2197.279546] Call Trace: [ 2197.279701] unregister_hw_breakpoint+0x13/0x20 [ 2197.279973] flush_ptrace_hw_breakpoint+0x2b/0x60 [ 2197.280251] do_exit+0x3d1/0xb90 [ 2197.280450] do_group_exit+0x43/0xb0 [ 2197.280670] get_signal+0x142/0x7a0 [ 2197.280883] ? futex_wake+0x8f/0x180 [ 2197.281100] do_signal+0x37/0x720 [ 2197.281303] ? recalc_sigpending+0x1b/0x50 [ 2197.281551] ? _copy_from_user+0x3e/0x60 [ 2197.281790] exit_to_usermode_loop+0x73/0xd0 [ 2197.282047] do_syscall_64+0x121/0x130 [ 2197.282276] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 2197.282574] RIP: 0033:0x7f4dcea47cb9 [ 2197.282790] RSP: 002b:7f4dcc4a5c30 EFLAGS: 0293 ORIG_RAX: 0007 [ 2197.283232] RAX: fdfc RBX: 55f463601a50 RCX: 7f4dcea47cb9 [ 2197.283645] RDX: RSI: 0001 RDI: 55f463601a50 [ 2197.284053] RBP: 0001 R08: R09: 55f463601898 [ 2197.284465] R10: 55f4635f0c60 R11: 0293 R12: [ 2197.284879] R13: R14: 7f4dcfcd0070 R15: 0001 [ 2197.285291] Code: 41 57 41 56 41 55 41 54 48 8d 75 c0 53 48 89 fb 48 83 ec 28 48 89 75 c0 48 89 75 c8 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 <48> 8b 87 f8 01 00 00 48 85 c0 0f 84 84 02 00 00 48 8b 87 68 02 [ 2197.286397] RIP: perf_event_release_kernel+0x2f/0x2f0 RSP: 9c440265bc68 [ 2197.286840] ---[ end trace 52f8fce70bf8ddd8 ]--- [ 2197.287110] Fixing recursive fault but reboot is needed! -- 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/1938013 Title: 4.15.0-151 is freezing intel 5th gen ThinkPad (T450) Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From: https://askubuntu.com/questions/1353859/ubuntu-18-04-05-lts- desktop-hangs-with-since-kernel-4-15-0-151-and-systemd-237-3 Several crashes in /var/crash, here's the last one:- ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Date: Fri Jul 23 18:10:54 2021 Failure: oops OopsText: BUG: Bad rss-counter state mm:c098a229 idx:2 val:-1 usblp0: removed
[Kernel-packages] [Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-07-27 10:40 EDT--- Since the file /etc/systemd/network/10-enP53p0s0.link was removed it wasn't get generated again. Is there a way to get it generated again? -- 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:1
[Kernel-packages] [Bug 1937031] Re: GPF in rtl2832
Ok, so I think you can remove the mainline kernel and install "linux- oem-20.04c" kernel which is 5.13 based. Proprietary drivers will work on OEM kernel. -- 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/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: Incomplete Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+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] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-07-27 11:33 EDT---
Enable udev monitor:
udevadm --debug monitor --property >> udevadm_reload.txt
Steeps followed to retrieve logs:
- Checking actual status of the vLan:
root@ilabg13:~# date
Tue Jul 27 08:23:47 MST 2021
root@ilabg13:~# ip addr show dev enP53p0s0.171
10: enP53p0s0.171@enP53p0s0: mtu 9000 qdisc
noqueue state UP group default qlen 1000
link/ether 82:0c:9b:c9:78:f8 brd ff:ff:ff:ff:ff:ff
inet6 fe80::800c:9bff:fec9:78f8/64 scope link
valid_lft forever preferred_lft forever
- Reload udevadm
root@ilabg13:~# date
Tue Jul 27 08:24:22 MST 2021
root@ilabg13:~# udevadm control --reload; udevadm trigger; udevadm settle
- Try to assign ip via netplan
root@ilabg13:~# date
Tue Jul 27 08:26:01 MST 2021
root@ilabg13:~# netplan --debug apply
** (generate:3616109): DEBUG: 08:26:04.430: Processing input file
/etc/netplan/00-installer-config.yaml..
** (generate:3616109): DEBUG: 08:26:04.431: starting new processing pass
** (generate:3616109): DEBUG: 08:26:04.431: Processing input file
/etc/netplan/01-iscsi-config.yaml..
** (generate:3616109): DEBUG: 08:26:04.431: starting new processing pass
** (generate:3616109): DEBUG: 08:26:04.431: We have some netdefs, pass them
through a final round of validation
** (generate:3616109): DEBUG: 08:26:04.431: encdc0: setting default backend to 1
** (generate:3616109): DEBUG: 08:26:04.431: Configuration is valid
** (generate:3616109): DEBUG: 08:26:04.431: encdb0: setting default backend to 1
** (generate:3616109): DEBUG: 08:26:04.431: Configuration is valid
** (generate:3616109): DEBUG: 08:26:04.431: ence0f: setting default backend to 1
** (generate:3616109): DEBUG: 08:26:04.431: Configuration is valid
** (generate:3616109): DEBUG: 08:26:04.431: encdb0.160: setting default backend
to 1
** (generate:3616109): DEBUG: 08:26:04.431: Configuration is valid
** (generate:3616109): DEBUG: 08:26:04.431: enP50s3832: setting default backend
to 1
** (generate:3616109): DEBUG: 08:26:04.431: Configuration is valid
** (generate:3616109): DEBUG: 08:26:04.431: enP53p0s0.171: setting default
backend to 1
** (generate:3616109): DEBUG: 08:26:04.431: Configuration is valid
** (generate:3616109): DEBUG: 08:26:04.431: enP50s3832.170: setting default
backend to 1
** (generate:3616109): DEBUG: 08:26:04.431: Configuration is valid
** (generate:3616109): DEBUG: 08:26:04.431: enP53p0s0: setting default backend
to 1
** (generate:3616109): DEBUG: 08:26:04.431: Configuration is valid
** (generate:3616109): DEBUG: 08:26:04.431: encdc0.150: setting default backend
to 1
** (generate:3616109): DEBUG: 08:26:04.431: Configuration is valid
** (generate:3616109): DEBUG: 08:26:04.431: Generating output files..
** (generate:3616109): DEBUG: 08:26:04.431: openvswitch: definition ence0f is
not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.431: NetworkManager: definition ence0f
is not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.431: openvswitch: definition encdb0 is
not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.431: NetworkManager: definition encdb0
is not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.432: openvswitch: definition encdc0 is
not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.432: NetworkManager: definition encdc0
is not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.432: openvswitch: definition enP50s3832
is not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.432: NetworkManager: definition
enP50s3832 is not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.432: openvswitch: definition enP53p0s0
is not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.432: NetworkManager: definition
enP53p0s0 is not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.432: openvswitch: definition encdb0.160
is not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.432: NetworkManager: definition
encdb0.160 is not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.432: openvswitch: definition encdc0.150
is not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.432: NetworkManager: definition
encdc0.150 is not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.432: openvswitch: definition
enP53p0s0.171 is not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.432: NetworkManager: definition
enP53p0s0.171 is not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.432: openvswitch: definition
enP50s3832.170 is not for us (backend 1)
** (generate:3616109): DEBUG: 08:26:04.432: NetworkManager: definition
enP50s3832.170 is not for us (backend 1)
(generate:3616109): GLib-DEBUG: 08:26:04.432: posix_spawn avoided (fd close
requested)
(generate:3616109): GLib-DEBUG: 08:26:04.432: posix_spawn avoided (fd close
requested)
DEBUG:netplan generated networkd configuration changed, restarting networkd
DEBUG:ence0f not found in {}
DEBUG:encdb0 not found in {'ence0f': {'addresses': ['9.11.116.213/24'],
'
[Kernel-packages] [Bug 1929657] udevadm_reload
--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-07-27 11:37 EDT--- ** Attachment added: "udevadm_reload" https://bugs.launchpad.net/bugs/1929657/+attachment/5514091/+files/udevadm_reload.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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:
[Kernel-packages] [Bug 1935846] Re: Sony Dualshock 4 usb dongle crashes the whole system
Hello Alex! Thanks! Your kernel package works fine with my DS4 controller. -- 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: Fix Released Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Bug description: [Impact] Sony Dualshock 4 controller crashes systems. This is the result of a divide by zero when the driver processes requests from Steam and returns invalid data. More details are in the patch description. [Fix] Check whether data is valid and retry up to 3 times if needed. [Test Case] Tested by the bug reporter of LP:1935846. No more crashes after applying this patch. [Where problems could occur] None. The patch checks whether data is valid and retry 3 times before return -EILSEQ if it still fails. == Original descriptions == 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 1938199] [NEW] Focal update: v5.4.132 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.4.132 upstream stable release
from git://git.kernel.org/
ALSA: usb-audio: fix rate on Ozone Z90 USB headset
ALSA: usb-audio: Fix OOB access at proc output
ALSA: usb-audio: scarlett2: Fix wrong resume call
ALSA: intel8x0: Fix breakage at ac97 clock measurement
ALSA: hda/realtek: Add another ALC236 variant support
ALSA: hda/realtek: Improve fixup for HP Spectre x360 15-df0xxx
ALSA: hda/realtek: Fix bass speaker DAC mapping for Asus UM431D
ALSA: hda/realtek: Apply LED fixup for HP Dragonfly G1, too
media: dvb-usb: fix wrong definition
Input: usbtouchscreen - fix control-request directions
net: can: ems_usb: fix use-after-free in ems_usb_disconnect()
usb: gadget: eem: fix echo command packet response issue
USB: cdc-acm: blacklist Heimann USB Appset device
usb: dwc3: Fix debugfs creation flow
usb: typec: Add the missed altmode_id_remove() in typec_register_altmode()
xhci: solve a double free problem while doing s4
ntfs: fix validity check for file name attribute
copy_page_to_iter(): fix ITER_DISCARD case
iov_iter_fault_in_readable() should do nothing in xarray case
Input: joydev - prevent use of not validated data in JSIOCSBTNMAP ioctl
arm_pmu: Fix write counter incorrect in ARMv7 big-endian mode
ARM: dts: at91: sama5d4: fix pinctrl muxing
btrfs: send: fix invalid path for unlink operations after parent orphanization
btrfs: clear defrag status of a root if starting transaction fails
ext4: cleanup in-core orphan list if ext4_truncate() failed to get a
transaction handle
ext4: fix kernel infoleak via ext4_extent_header
ext4: return error code when ext4_fill_flex_info() fails
ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit
ext4: remove check for zero nr_to_scan in ext4_es_scan()
ext4: fix avefreec in find_group_orlov
ext4: use ext4_grp_locked_error in mb_find_extent
can: gw: synchronize rcu operations before removing gw job entry
can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after RCU
is done
can: peak_pciefd: pucan_handle_status(): fix a potential starvation issue in TX
path
mac80211: remove iwlwifi specific workaround that broke sta NDP tx
SUNRPC: Fix the batch tasks count wraparound.
SUNRPC: Should wake up the privileged task firstly.
perf/smmuv3: Don't trample existing events with global filter
KVM: PPC: Book3S HV: Workaround high stack usage with clang
s390/cio: dont call css_wait_for_slow_path() inside a lock
rtc: stm32: Fix unbalanced clk_disable_unprepare() on probe error path
iio: light: tcs3472: do not free unallocated IRQ
iio: ltr501: mark register holding upper 8 bits of ALS_DATA{0,1} and PS_DATA as
volatile, too
iio: ltr501: ltr559: fix initialization of LTR501_ALS_CONTR
iio: ltr501: ltr501_read_ps(): add missing endianness conversion
serial: mvebu-uart: fix calculation of clock divisor
serial: sh-sci: Stop dmaengine transfer in sci_stop_tx()
serial_cs: Add Option International GSM-Ready 56K/ISDN modem
serial_cs: remove wrong GLOBETROTTER.cis entry
ath9k: Fix kernel NULL pointer dereference during ath_reset_internal()
ssb: sdio: Don't overwrite const buffer if block_write fails
rsi: Assign beacon rate settings to the correct rate_info descriptor field
rsi: fix AP mode with WPA failure due to encrypted EAPOL
tracing/histograms: Fix parsing of "sym-offset" modifier
tracepoint: Add tracepoint_probe_register_may_exist() for BPF tracing
seq_buf: Make trace_seq_putmem_hex() support data longer than 8
powerpc/stacktrace: Fix spurious "stale" traces in raise_backtrace_ipi()
evm: Execute evm_inode_init_security() only when an HMAC key is loaded
evm: Refuse EVM_ALLOW_METADATA_WRITES only if an HMAC key is loaded
fuse: ignore PG_workingset after stealing
fuse: check connected before queueing on fpq->io
fuse: reject internal errno
spi: Make of_register_spi_device also set the fwnode
media: mdk-mdp: fix pm_runtime_get_sync() usage count
media: s5p: fix pm_runtime_get_sync() usage count
media: sh_vou: fix pm_runtime_get_sync() usage count
media: mtk-vcodec: fix PM runtime get logic
media: s5p-jpeg: fix pm_runtime_get_sync() usage count
media: sti/bdisp: fix pm_runtime_get_sync() usage count
media: exynos-gsc: fix pm_runtime_get_sync() usage count
spi: spi-loopback-test: Fix 'tx_buf' might be 'rx_buf'
spi: spi-topcliff-pch: Fix potential double free in pch_spi_process_messages()
spi: omap-100k: Fix the length judgment problem
regulator: uniphier: Add missing MODULE_DEVICE_TABLE
hwrng: exynos - Fix runtime PM imbalance on error
crypto: nx - add missing MODULE_DEVICE_TABLE
media: sti: fix obj-$(config
[Kernel-packages] [Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend
In addition to my previous comment: I have the latest bios for my laptop: 1.19.0 I also have tried these kernel versions: 5.4.0-26.30 5.11.0-25.27~20.04.1 without any success. I'm attaching report file from `apport-collect -p linux ` and I'm ready for any further debug. ** Attachment added: "apport.linux.muox5fp0.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+attachment/5514100/+files/apport.linux.muox5fp0.apport -- 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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1935034] Re: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04
Suganath Prabu - You appear to be missing some scaffolding patches. At
least 1ea18ac2e5f703e5648f663412ff6abab2f41def ("scsi: sbitmap: Export
sbitmap_weight") and c548e62bcf6adc7066ff201e9ecc88e536dd8890 ("scsi:
sbitmap: Move allocation hint into sbitmap").
Perhaps you should attempt to apply this list of commits yourself, then
submit a pull request.
--
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/1935034
Title:
Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
New
Status in linux source package in Hirsute:
New
Status in linux source package in Impish:
Confirmed
Bug description:
This is a feature request to update the mpt3sas driver to latest version in
upstream 38.100.00.00 in Ubuntu 21.10 and Ubuntu 20.04.
This will allow users to use fixes and enhancements that landed upstream in
5.14. For this reason,
Broadcom and Dell have requested to pull these patches to update the
mpt3sas driver to the current upstream version.
I could see both Ubuntu 21.10 and 20.04 HWE has mpt3sas driver
v36.100.00.00, following are the commit ID's to update to 38.100.00.00
8b3c803529 scsi: mpt3sas: Signedness bug in _base_get_diag_triggers()
39718fe7ad scsi: mpt3sas: Fix spelling mistake in Kconfig "compatiblity" ->
"compatibility"
bfb3f00c06 scsi: mpt3sas: Simplify bool comparison
d309ae0732 scsi: mpt3sas: Fix ReplyPostFree pool allocation
664f0dce20 scsi: mpt3sas: Add support for shared host tagset for CPU hotplug
688c1a0a13 scsi: mpt3sas: Additional diagnostic buffer query interface
446b5f3d3f scsi: mpt3sas: Update driver version to 37.100.00.00
8278807abd scsi: core: Add scsi_device_busy() wrapper
020b0f0a31 scsi: core: Replace sdev->device_busy with sbitmap
e015e0ded1 scsi: mpt3sas: Fix misspelling of _base_put_smid_default_atomic()
2111ba8781 scsi: mpt3sas: Move a little data from the stack onto the heap
cf9e575e62 scsi: mpt3sas: Fix a bunch of potential naming doc-rot
54cb88dc30 scsi: mpt3sas: Fix a couple of misdocumented functions/params
782a1ab33f scsi: mpt3sas: Fix some kernel-doc misnaming issues
a50bd64616 scsi: mpt3sas: Do not use GFP_KERNEL in atomic context
a1c4d77413 scsi: mpt3sas: Replace unnecessary dynamic allocation with a
static one
d6adc251dd scsi: mpt3sas: Force PCIe scatterlist allocations to be within
same 4 GB region
7dd847dae1 scsi: mpt3sas: Force chain buffer allocations to be within same 4
GB region
970ac2bb70 scsi: mpt3sas: Force sense buffer allocations to be within same 4
GB region
58501fd937 scsi: mpt3sas: Force reply buffer allocations to be within same 4
GB region
2e4e858732 scsi: mpt3sas: Force reply post buffer allocations to be within
same 4 GB region
c569de899b scsi: mpt3sas: Force reply post array allocations to be within
same 4 GB region
37067b9793 scsi: mpt3sas: Update driver version to 37.101.00.00
a8d548b0b3 scsi: mpt3sas: Fix a few kernel-doc issues
3401ecf7fc scsi: mpt3sas: Fix error return code of mpt3sas_base_attach()
206a3afa94 scsi: mpt3sas: Fix a typo
4c51f95696 scsi: mpt3sas: Only one vSES is present even when IOC has multi
vSES
c0629d70ca scsi: mpt3sas: Fix endianness for ActiveCablePowerRequirement
3c8604691d scsi: mpt3sas: Block PCI config access from userspace during reset
16660db3fc scsi: mpt3sas: Fix out-of-bounds warnings in _ctl_addnl_diag_query
3ad0b1da0d scsi: mpt3sas: Fix two kernel-doc headers
2910a4a9e9 scsi: mpt3sas: Documentation cleanup
e2fac6c44a scsi: mpt3sas: Fix deadlock while cancelling the running firmware
event
19a622c39a scsi: mpt3sas: Handle firmware faults during first half of IOC init
a0815c45c8 scsi: mpt3sas: Handle firmware faults during second half of IOC
init
f2b1e9c6f8 scsi: core: Introduce scsi_build_sense()
84a84cc6af scsi: mpt3sas: Fix fall-through warnings for Clang
cf750be8e6 scsi: mpt3sas: Fix Coverity reported issue
d6c2ce435f scsi: mpt3sas: Fix error return value in _scsih_expander_add()
Note:
We have already posted patch to update driver version to 38.100.00.00
Other patches are already available in upstream .
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935034/+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 1938013] Re: 4.15.0-151 is freezing intel 5th gen ThinkPad (T450)
For Stefan Bader(smb) >For this I would need someone volunteering to try the kernel I prepared at >https://launchpad.net/~smb/+archive/ubuntu/bionic (still needs to finish building some arches). >This is not a officially signed kernel, so it only should be tried if secure-boot is not used or >can be disabled. Tried this kernel on my Entroware system as per the initial reporter in this thread(Nick White). Bad news the system hung with just the mouse pointer showing prior to displaying the login screen. kern.log has lots of "^@" after dealing with the usblp. On the 147 kernel, the next thing after usblp is "usbcore: registered new interface driver usblp" and then Bluetooth. Appreciate that start up sequences may vary due to systemd. Nothing new in /var/crash. -- 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/1938013 Title: 4.15.0-151 is freezing intel 5th gen ThinkPad (T450) Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From: https://askubuntu.com/questions/1353859/ubuntu-18-04-05-lts- desktop-hangs-with-since-kernel-4-15-0-151-and-systemd-237-3 Several crashes in /var/crash, here's the last one:- ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Date: Fri Jul 23 18:10:54 2021 Failure: oops OopsText: BUG: Bad rss-counter state mm:c098a229 idx:2 val:-1 usblp0: removed usblp 1-5:1.0: usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04F9 pid 0x02EC <44>[ 18.329026] systemd-journald[358]: File /var/log/journal/b022dca21fd4480baeeb84f47ab439d3/user-1000.journal corrupted or uncleanly shut down, renaming and replacing. vboxdrv: loading out-of-tree module taints kernel. vboxdrv: module verification failed: signature and/or required key missing - tainting kernel vboxdrv: Found 8 processor cores vboxdrv: TSC mode is Invariant, tentative frequency 2303999142 Hz vboxdrv: Successfully loaded version 6.1.24 r145767 (interface 0x0030) VBoxNetFlt: Successfully started. VBoxNetAdp: Successfully started. Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 rfkill: input handler disabled [UFW BLOCK] IN=enp3s0f1 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=enp3s0f1 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=enp3s0f1 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:80:20:da:95:bc:56:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 Package: linux-image-4.15.0-151-generic 4.15.0-151.157 SourcePackage: linux Tags: kernel-oops Uname: Linux 4.15.0-151-generic x86_64 --- The system is a laptop from Entroware based on Clevo and has 8 logical CPUs:- Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 158 Model name: Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz Stepping:10 CPU MHz: 2000.295 CPU max MHz: 4000. CPU min MHz: 800. BogoMIPS:4599.93 Virtualisation: VT-x L1d cache: 32K L1i cache: 32K L2 cache:256K L3 cache:8192K NUMA node0 CPU(s): 0-7 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms i
[Kernel-packages] [Bug 1925261] Re: memory leak on AWS kernels when using docker
Kleber, I finally had some time to narrow down what commit fixes this issue for us today, below is the commit: commit 7514c0362ffdd9af953ae94334018e7356b31313 Merge: 9322c47b21b9 428fc0aff4e5 Author: Linus Torvalds Date: Sat Sep 5 13:28:40 2020 -0700 Merge branch 'akpm' (patches from Andrew) Merge misc fixes from Andrew Morton: "19 patches. Subsystems affected by this patch series: MAINTAINERS, ipc, fork, checkpatch, lib, and mm (memcg, slub, pagemap, madvise, migration, hugetlb)" * emailed patches from Andrew Morton : include/linux/log2.h: add missing () around n in roundup_pow_of_two() mm/khugepaged.c: fix khugepaged's request size in collapse_file mm/hugetlb: fix a race between hugetlb sysctl handlers mm/hugetlb: try preferred node first when alloc gigantic page from cma mm/migrate: preserve soft dirty in remove_migration_pte() mm/migrate: remove unnecessary is_zone_device_page() check mm/rmap: fixup copying of soft dirty and uffd ptes mm/migrate: fixup setting UFFD_WP flag mm: madvise: fix vma user-after-free checkpatch: fix the usage of capture group ( ... ) fork: adjust sysctl_max_threads definition to match prototype ipc: adjust proc_ipc_sem_dointvec definition to match prototype mm: track page table modifications in __apply_to_page_range() MAINTAINERS: IA64: mark Status as Odd Fixes only MAINTAINERS: add LLVM maintainers MAINTAINERS: update Cavium/Marvell entries mm: slub: fix conversion of freelist_corrupted() mm: memcg: fix memcg reclaim soft lockup memcg: fix use-after-free in uncharge_batch I also verified that the latest available Ubuntu 18.04 kernel as of today (5.4.0-1054.57~18.04.1) still hits this memory leak issue for us. Please let me know if you need any further information from us to hopefully get this fix pulled into the supported Ubuntu 18.04 AWS kernel. Thanks, Paul -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1925261 Title: memory leak on AWS kernels when using docker Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Focal: New Bug description: Ever since the "ubuntu-bionic-18.04-amd64-server-20200729" EC2 Ubuntu AMI was released which has the "5.3.0-1032-aws" kernel we have been hitting a 100% repro memory leak that causes our app that is running under docker to be OOM killed. The scenario is that we have an app running in a docker container and it occasionally catches a crash happening within itself and when that happens it creates another process which triggers a gdb dump of that parent app. Normally this works fine but under these specific kernels it causes the memory usage to grow and grow until it hits the maximum allowed memory for the container at which point the container is killed. I have tested using several of the latest available Ubuntu AMIs including the latest "ubuntu-bionic-18.04-amd64-server-20210415" which has the "5.4.0-1045-aws" kernel and the bug still exists. I also tested a bunch of the mainline kernels and found the fix was introduced for this memory leak in the v5.9-rc4 kernel (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9-rc4/CHANGES). Do you all have any idea if or when that set of changes will be backported into a supported kernel for Ubuntu 18.04 or 20.04? Release we are running: root@:~# lsb_release -rd Description: Ubuntu 18.04.5 LTS Release: 18.04 Docker / containerd.io versions: - containerd.io: 1.4.4-1 - docker-ce: 5:20.10.5~3-0~ubuntu-bionic Latest supported kernel I tried which still sees the memory leak: root@hostname:~# apt-cache policy linux-aws linux-aws: Installed: 5.4.0.1045.27 Candidate: 5.4.0.1045.27 Version table: *** 5.4.0.1045.27 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1007.7 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Thanks, Paul To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1925261/+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 1929831] Re: cifs: On cifs_reconnect, resolve the hostname again
** Changed in: linux-azure (Ubuntu Groovy) Status: In Progress => Won't Fix -- 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/1929831 Title: cifs: On cifs_reconnect, resolve the hostname again Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-azure source package in Groovy: Won't Fix Bug description: SRU Justification [Impact] The Microsoft CIFS team is requesting below patch to be backported for 5.4 Azure tuned kernel https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4e456b30f78c429b183db420e23b26cde7e03a78 A customer is encountering the bug fixed by this patch. [Fix] 7d397a034d5c45528c7bdf7fc3752c4793029cce cifs: rename reconn_inval_dfs_target() 7d6535b720421d58886d5590ffc3617d359aa871 cifs: Simplify reconnect code when dfs upcall is enabled 4e456b30f78c429b183db420e23b26cde7e03a78 cifs: On cifs_reconnect, resolve the hostname again. The first 2 patches are scaffolding to make the backport simpler. the 3rd patch is the bug fix. [Test Plan] The test kernel at https://launchpad.net/~timg- tpi/+archive/ubuntu/cifs-reconnect-sf00309672 has been found to fix the issue. [Where problems could occur] This could perturb CIFS connections in new and different ways. [Other Info] https://canonical.my.salesforce.com/5004K05pQNG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929831/+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 1929831] Re: cifs: On cifs_reconnect, resolve the hostname again
** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- 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/1929831 Title: cifs: On cifs_reconnect, resolve the hostname again Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: Fix Released Status in linux source package in Groovy: Won't Fix Status in linux-azure source package in Groovy: Won't Fix Bug description: SRU Justification [Impact] The Microsoft CIFS team is requesting below patch to be backported for 5.4 Azure tuned kernel https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4e456b30f78c429b183db420e23b26cde7e03a78 A customer is encountering the bug fixed by this patch. [Fix] 7d397a034d5c45528c7bdf7fc3752c4793029cce cifs: rename reconn_inval_dfs_target() 7d6535b720421d58886d5590ffc3617d359aa871 cifs: Simplify reconnect code when dfs upcall is enabled 4e456b30f78c429b183db420e23b26cde7e03a78 cifs: On cifs_reconnect, resolve the hostname again. The first 2 patches are scaffolding to make the backport simpler. the 3rd patch is the bug fix. [Test Plan] The test kernel at https://launchpad.net/~timg- tpi/+archive/ubuntu/cifs-reconnect-sf00309672 has been found to fix the issue. [Where problems could occur] This could perturb CIFS connections in new and different ways. [Other Info] https://canonical.my.salesforce.com/5004K05pQNG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929831/+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 1938221] [NEW] Fail to resume after hibernate. Image mismatch: architecture specific data
Public bug reported: I'm running Ubuntu 21.04 on a laptop and have been using hibernate flawlessly for a couple of months. More recently, resuming from hibernation stopped working and now falls back to complete restart. This is what I get from dmesg: [ 17.407048] kernel: PM: hibernation: resume from hibernation [ 17.409714] kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] [ 17.409717] kernel: PM: hibernation: Marking nosave pages: [mem 0x0004f000-0x0004] [ 17.409718] kernel: PM: hibernation: Marking nosave pages: [mem 0x0009e000-0x000f] [ 17.409721] kernel: PM: hibernation: Marking nosave pages: [mem 0xae6e9000-0xae6e] [ 17.409723] kernel: PM: hibernation: Marking nosave pages: [mem 0xaf0cd000-0xaf5abfff] [ 17.409744] kernel: PM: hibernation: Marking nosave pages: [mem 0xb1e4c000-0xb1ed3fff] [ 17.409747] kernel: PM: hibernation: Marking nosave pages: [mem 0xb2698000-0xb2698fff] [ 17.409748] kernel: PM: hibernation: Marking nosave pages: [mem 0xb54af000-0xb54a] [ 17.409749] kernel: PM: hibernation: Marking nosave pages: [mem 0xb54d8000-0xb54d8fff] [ 17.409751] kernel: PM: hibernation: Marking nosave pages: [mem 0xb7db3000-0xb7ff] [ 17.409761] kernel: PM: hibernation: Marking nosave pages: [mem 0xb8759000-0xb87f] [ 17.409765] kernel: PM: hibernation: Marking nosave pages: [mem 0xb8f9d000-0xb8ff] [ 17.409767] kernel: PM: hibernation: Marking nosave pages: [mem 0xba6f5000-0xba7f] [ 17.409773] kernel: PM: hibernation: Marking nosave pages: [mem 0xbbcec000-0x] [ 17.410626] kernel: PM: hibernation: Basic memory bitmaps created [ 17.481616] kernel: PM: Using 3 thread(s) for decompression [ 17.481620] kernel: PM: Loading and decompressing image data (835177 pages)... [ 17.481626] kernel: PM: hibernation: Image mismatch: architecture specific data [ 17.481627] kernel: PM: hibernation: Read 3340708 kbytes in 0.01 seconds (334070.80 MB/s) [ 17.482589] kernel: PM: Error -1 resuming [ 17.482594] kernel: PM: hibernation: Failed to load image, recovering. [ 17.482992] kernel: PM: hibernation: Basic memory bitmaps freed [ 17.483572] kernel: PM: hibernation: resume failed (-1) Here is some system information: $ cat /proc/version_signature Ubuntu 5.11.0-25.27-generic 5.11.22 $ cat /sys/power/state freeze mem disk $ cat /sys/power/disk [platform] shutdown reboot suspend test_resume $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash resume=UUID=a2be2098-* mem_sleep_default=deep ** 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/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data Status in linux package in Ubuntu: New Bug description: I'm running Ubuntu 21.04 on a laptop and have been using hibernate flawlessly for a couple of months. More recently, resuming from hibernation stopped working and now falls back to complete restart. This is what I get from dmesg: [ 17.407048] kernel: PM: hibernation: resume from hibernation [ 17.409714] kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] [ 17.409717] kernel: PM: hibernation: Marking nosave pages: [mem 0x0004f000-0x0004] [ 17.409718] kernel: PM: hibernation: Marking nosave pages: [mem 0x0009e000-0x000f] [ 17.409721] kernel: PM: hibernation: Marking nosave pages: [mem 0xae6e9000-0xae6e] [ 17.409723] kernel: PM: hibernation: Marking nosave pages: [mem 0xaf0cd000-0xaf5abfff] [ 17.409744] kernel: PM: hibernation: Marking nosave pages: [mem 0xb1e4c000-0xb1ed3fff] [ 17.409747] kernel: PM: hibernation: Marking nosave pages: [mem 0xb2698000-0xb2698fff] [ 17.409748] kernel: PM: hibernation: Marking nosave pages: [mem 0xb54af000-0xb54a] [ 17.409749] kernel: PM: hibernation: Marking nosave pages: [mem 0xb54d8000-0xb54d8fff] [ 17.409751] kernel: PM: hibernation: Marking nosave pages: [mem 0xb7db3000-0xb7ff] [ 17.409761] kernel: PM: hibernation: Marking nosave pages: [mem 0xb8759000-0xb87f] [ 17.409765] kernel: PM: hibernation: Marking nosave pages: [mem 0xb8f9d000-0xb8ff] [ 17.409767] kernel: PM: hibernation: Marking nosave pages: [mem 0xba6f5000-0xba7f] [ 17.409773] kernel: PM: hibernation: Marking nosave pages: [mem 0xbbcec000-0x] [ 17.410626] kernel: PM: hibernation: Basic memory bitmaps created [ 17.481616] kernel: PM: Using 3 thread(s) for decompression [ 17.481620] kernel: PM: Loading and decompressing image data (835177 pages)... [ 17.481626] kernel: PM: hibernation: Image mismatch: architecture specific data [ 17.481627] kernel: PM: hibernation: Read 3340708 kbytes in 0.01 seconds (334070.80 MB
[Kernel-packages] [Bug 1935846] Re: Sony Dualshock 4 usb dongle crashes the whole system
** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Alex Hung (alexhung) ** Changed in: linux (Ubuntu Focal) Assignee: Alex Hung (alexhung) => (unassigned) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Alex Hung (alexhung) -- 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: Fix Released Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Bug description: [Impact] Sony Dualshock 4 controller crashes systems. This is the result of a divide by zero when the driver processes requests from Steam and returns invalid data. More details are in the patch description. [Fix] Check whether data is valid and retry up to 3 times if needed. [Test Case] Tested by the bug reporter of LP:1935846. No more crashes after applying this patch. [Where problems could occur] None. The patch checks whether data is valid and retry 3 times before return -EILSEQ if it still fails. == Original descriptions == 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 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
Tested 5.14rc3 from https://kernel.ubuntu.com/~kernel-ppa/mainline now, and the issue occurs there as 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/1938096 Title: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from the impish repos. To recreate: 1. Reboot a X1C9 machine and see that the touchpad works fine 2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a software suspend) 3. Resume from suspend and see that touchpad acts differently and less responsive than right after a clean boot What is expected: 1. Same responsive touchpad experience after resuming from suspend as right after a clean boot. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: pop:GNOME DistUpgraded: Fresh install DistroCodename: hirsute DistroRelease: Pop!_OS 21.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Xe Graphics [17aa:22d5] MachineType: LENOVO 20XW005PMX Package: libinput10 1.18.0-1 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet systemd.show_status=false loglevel=0 splash Tags: hirsute third-party-packages ubuntu Uname: Linux 5.13.5-051305-generic x86_64 UnreportableReason: This does not seem to be an official Pop!_OS package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 06/15/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET66W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XW005PMX 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.26 dmi.modalias: dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XW005PMX dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2pop0~1624392450~21.04~6fbdfd2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1938096/+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 1938099] Re: Neither laptop kepboard nor touchpad work
As i predicted, it didn't last. Just Booted up and both keyboard and mousepad do not work again. -- 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/1938099 Title: Neither laptop kepboard nor touchpad work Status in linux package in Ubuntu: New Bug description: Both worked previously and at some point just stopped. I ran these commands in an attempt to fix but it may have worsened the issue: apt-get update apt-get install xserver-xorg-input-all apt-get install ubuntu-desktop apt-get install ubuntu-minimal apt-get install xorg xserver-xorg apt-get install xserver-xorg-input-evdev apt-get install xserver-xorg-video-vmware ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 1119 F pulseaudio /dev/snd/pcmC1D0p: alex 1119 F...m pulseaudio /dev/snd/controlC0: alex 1119 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Mon Jul 26 19:04:27 2021 InstallationDate: Installed on 2021-07-21 (5 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: TOSHIBA Satellite C875D ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=872c0009-76c1-4ee5-a2c2-f9845844dee0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2012 dmi.bios.release: 6.30 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PLCSC8 dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.ec.firmware.release: 6.0 dmi.modalias: dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr6.0:svnTOSHIBA:pnSatelliteC875D:pvrPSCBGU-001009:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite C875D dmi.product.sku: PSCBGU dmi.product.version: PSCBGU-001009 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938099/+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 1937321] [NEW] System freeze (amdgpu kernel crash on resume from suspend)
You have been subscribed to a public bug: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15-ef1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2021 dmi.bios.release: 15.34 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.19 dmi.modalias: dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-ef1xxx dmi.product.sku: 27A48UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 amdgpu apport-bug focal freeze ubuntu -- System freeze (amdgpu kernel crash on resume from suspend) https://bugs.launchpad.net/bugs/1937321 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937321] Re: System freeze
Thanks. It appears the problem is the 'amdgpu' kernel driver crashing on resume-from-suspend: Jul 26 14:29:32 HP-Laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=741, emitted seq=743 Jul 26 14:29:32 HP-Laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 Jul 26 14:29:32 HP-Laptop kernel: amdgpu :03:00.0: amdgpu: GPU reset begin! ... Jul 26 14:29:32 HP-Laptop kernel: Call Trace: Jul 26 14:29:32 HP-Laptop kernel: pm_uninit+0x16/0x20 [amdgpu] Jul 26 14:29:32 HP-Laptop kernel: stop_cpsch+0xa5/0xd0 [amdgpu] Jul 26 14:29:32 HP-Laptop kernel: kgd2kfd_suspend.part.0+0x35/0x50 [amdgpu] Jul 26 14:29:32 HP-Laptop kernel: kgd2kfd_pre_reset+0x3c/0x50 [amdgpu] Jul 26 14:29:32 HP-Laptop kernel: amdgpu_amdkfd_pre_reset+0x1a/0x20 [amdgpu] Jul 26 14:29:32 HP-Laptop kernel: amdgpu_device_gpu_recover.cold+0x204/0xc4a [amdgpu] Jul 26 14:29:32 HP-Laptop kernel: amdgpu_job_timedout+0x123/0x150 [amdgpu] ** Summary changed: - System freeze + System freeze (amdgpu kernel crash on resume from suspend) ** Package changed: ubuntu => linux (Ubuntu) ** Package changed: linux (Ubuntu) => linux-hwe-5.8 (Ubuntu) ** Tags added: suspend-resume -- 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/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) Status in linux-hwe-5.8 package in Ubuntu: Incomplete Bug description: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15-ef1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2021 dmi.bios.release: 15.34 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.19 dmi.modalias: dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-ef1xxx dmi.product.sku: 27A48UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1937321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchp
[Kernel-packages] [Bug 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)
Looks like it could be the same issue as bug 1917674. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1937321 Title: System freeze (amdgpu kernel crash on resume from suspend) Status in linux-hwe-5.8 package in Ubuntu: Incomplete Bug description: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15-ef1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2021 dmi.bios.release: 15.34 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.19 dmi.modalias: dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-ef1xxx dmi.product.sku: 27A48UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1937321/+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 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19)
See also bug 1937321. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.8 package in Ubuntu: Confirmed Bug description: Automatic suspension causes the system to freeze on resume. This doesn't happen if I suspend it manually by opening the system menu and pressing the suspend button. Suspension works flawlessly when it is triggered manually. When the system resumes from automatic suspension, the lock screen is visible but does not respond. It's frozen. A notification says something like "system will suspend shortly due to inactivity". It never goes away. The keyboard responds during this (at least for a while). The CAPS LOCK LED turns on and off as I press it (with no delay). Sometimes I can even switch to another TTY and kill the X server, which is why I'm reporting it against gnome-shell. When switching TTY is impossible, I use the "REISUB" combination to shut down. Either way, I always lose the running session. This is reproducible about 60% of the time. Eventually I ended up disabling it and relying only on manual suspension. # Additional information: 1) Ubuntu 20.04.2 LTS / Release: 20.04 2) gnome-shell 3.36.4-1ubuntu1~20.04.2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 3 16:56:01 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-01-31 (31 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 1884 F pulseaudio /dev/snd/controlC1: dsilva 1884 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-31 (49 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro Mechanical Gaming Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. B460MDS3H Package: linux-hwe-5.8 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 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.8.0-45-generic N/A linux-backports-modules-5.8.0-45-generic N/A linux-firmware1.187.10 RfKill: Tags: focal Uname: Linux 5.8.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/27/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: B460M DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B460 MB dmi.product.name: B460MDS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-
[Kernel-packages] [Bug 1938195] [NEW] Configuration for eGPU removed on update
You have been subscribed to a public bug: ThinkPad X1C9 running Kubuntu. I'm using an external nVidia GPU in an enclosure, attached via thunderbolt. I have applied updates over the last few weeks, and rebooted today. Got a black screen. Turns out an update back in mid June (22nd) removed the Option "AllowExternalGpus" "true" from my xorg.conf. Why is an update removing a vital configuration option enabling me to display my login screen? I had to re-edit the xorg.conf like an cave man from 20 years ago. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..52.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Tue Jul 27 16:42:11 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tp_smapi, 0.43, 5.11.0-22-generic, x86_64: installed tp_smapi, 0.43, 5.11.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Xe Graphics [17aa:22d5] NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d1] InstallationDate: Installed on 2021-05-14 (73 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f73d534c-9211-43d9-a8d5-fe9b6bb3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2021 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET47W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW 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.22 dmi.modalias: dmi:bvnLENOVO:bvrN32ET47W(1.23):bd03/26/2021:br1.23:efr1.22:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 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 ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu -- Configuration for eGPU removed on update https://bugs.launchpad.net/bugs/1938195 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938221] Re: Fail to resume after hibernate. Image mismatch: architecture specific data
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1938221 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data Status in linux package in Ubuntu: New Bug description: I'm running Ubuntu 21.04 on a laptop and have been using hibernate flawlessly for a couple of months. More recently, resuming from hibernation stopped working and now falls back to complete restart. This is what I get from dmesg: [ 17.407048] kernel: PM: hibernation: resume from hibernation [ 17.409714] kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] [ 17.409717] kernel: PM: hibernation: Marking nosave pages: [mem 0x0004f000-0x0004] [ 17.409718] kernel: PM: hibernation: Marking nosave pages: [mem 0x0009e000-0x000f] [ 17.409721] kernel: PM: hibernation: Marking nosave pages: [mem 0xae6e9000-0xae6e] [ 17.409723] kernel: PM: hibernation: Marking nosave pages: [mem 0xaf0cd000-0xaf5abfff] [ 17.409744] kernel: PM: hibernation: Marking nosave pages: [mem 0xb1e4c000-0xb1ed3fff] [ 17.409747] kernel: PM: hibernation: Marking nosave pages: [mem 0xb2698000-0xb2698fff] [ 17.409748] kernel: PM: hibernation: Marking nosave pages: [mem 0xb54af000-0xb54a] [ 17.409749] kernel: PM: hibernation: Marking nosave pages: [mem 0xb54d8000-0xb54d8fff] [ 17.409751] kernel: PM: hibernation: Marking nosave pages: [mem 0xb7db3000-0xb7ff] [ 17.409761] kernel: PM: hibernation: Marking nosave pages: [mem 0xb8759000-0xb87f] [ 17.409765] kernel: PM: hibernation: Marking nosave pages: [mem 0xb8f9d000-0xb8ff] [ 17.409767] kernel: PM: hibernation: Marking nosave pages: [mem 0xba6f5000-0xba7f] [ 17.409773] kernel: PM: hibernation: Marking nosave pages: [mem 0xbbcec000-0x] [ 17.410626] kernel: PM: hibernation: Basic memory bitmaps created [ 17.481616] kernel: PM: Using 3 thread(s) for decompression [ 17.481620] kernel: PM: Loading and decompressing image data (835177 pages)... [ 17.481626] kernel: PM: hibernation: Image mismatch: architecture specific data [ 17.481627] kernel: PM: hibernation: Read 3340708 kbytes in 0.01 seconds (334070.80 MB/s) [ 17.482589] kernel: PM: Error -1 resuming [ 17.482594] kernel: PM: hibernation: Failed to load image, recovering. [ 17.482992] kernel: PM: hibernation: Basic memory bitmaps freed [ 17.483572] kernel: PM: hibernation: resume failed (-1) Here is some system information: $ cat /proc/version_signature Ubuntu 5.11.0-25.27-generic 5.11.22 $ cat /sys/power/state freeze mem disk $ cat /sys/power/disk [platform] shutdown reboot suspend test_resume $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash resume=UUID=a2be2098-* mem_sleep_default=deep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+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 1938195] Re: Configuration for eGPU removed on update
Judging by the top of the config file it sounds like the Nvidia driver writing and overwriting it. There was an update to nvidia-graphics- drivers-460 on 21 July. In theory this is what /usr/share/X11/xorg.conf.d/ is for, to add custom configs that other packages won't touch. But I don't know if spreading the nvidia config across multiple files with potentially duplicate sections would work. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) -- 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/1938195 Title: Configuration for eGPU removed on update Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: ThinkPad X1C9 running Kubuntu. I'm using an external nVidia GPU in an enclosure, attached via thunderbolt. I have applied updates over the last few weeks, and rebooted today. Got a black screen. Turns out an update back in mid June (22nd) removed the Option "AllowExternalGpus" "true" from my xorg.conf. Why is an update removing a vital configuration option enabling me to display my login screen? I had to re-edit the xorg.conf like an cave man from 20 years ago. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..52.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Tue Jul 27 16:42:11 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tp_smapi, 0.43, 5.11.0-22-generic, x86_64: installed tp_smapi, 0.43, 5.11.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Xe Graphics [17aa:22d5] NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d1] InstallationDate: Installed on 2021-05-14 (73 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f73d534c-9211-43d9-a8d5-fe9b6bb3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2021 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET47W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW 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.22 dmi.modalias: dmi:bvnLENOVO:bvrN32ET47W(1.23):bd03/26/2021:br1.23:efr1.22:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 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/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1938195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : htt
[Kernel-packages] [Bug 1935584] Re: Fix host to pod traffic with ovn cluster using ovs internal port and tc offload
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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1935584 Title: Fix host to pod traffic with ovn cluster using ovs internal port and tc offload Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) When using ovs internal port with tc the redirect rules to internal port is back to ingress instead of egress. When we reinsert the skb we start from chain 0 but it could be ct state already set so matching rules on the internal port queue would miss. * brief explanation of fixes When reinserting skb back to ingress queue to restart tc classification then also reset ct. * How to test The setup was created by using ovn and testing iperf traffic from host container to VF pod. The result was ip set on the ovs bridge netdev (internal port) The rules were from rep to eventually the internal port and internal port to rep. The rules were with ct actions and chains tc-policy was set to skip-hw. Without the commit the traffic doesn’t work when hw-offload was true (offload to tc sw only) but does work with hw-offload false (ovs dp). * What it could break. Traffic not working in some cases using internal ports and CT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1935584/+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 1934819] Re: Fix err check for nf_conntrack_confirm
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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1934819 Title: Fix err check for nf_conntrack_confirm Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) Conntrack confirm operation wasn't checked, this could result in accepting packet which should be dropped. * brief explanation of fixes Match behavior of ovs and netfilter. Drop the packets which are not accepted. * How to test First observe packets accepted with status of NF_DROP without the fix. Then observe packets are correctly dropped with the patch. * What it could break. Nothing breaks, but fixing security hole. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934819/+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 1934822] Re: Possible memory leak of flow_block_cb
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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1934822 Title: Possible memory leak of flow_block_cb Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) When cleaning up the nf_table in tcf_ct_flow_table_cleanup_work there is no guarantee that the callback list, added to by nf_flow_table_offload_add_cb, is empty. This means that it is possible that the flow_block_cb memory allocated will be lost. * brief explanation of fixes Fix this by iterating the list and freeing the flow_block_cb entries before freeing the nf_table entry (via freeing ct_ft). * How to test With mlx5 driver registers flow block callback, cleaning up rule with action ct frees the ct_ft but with memory leak. * What it could break. Nothing breaks, memory leak is fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934822/+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
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-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: Invalid Status in linux-bluefield source package in Focal: Fix Committed 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 The series first cherry picked multiple upstream patches from xdp/bpf to support the new BPF helpers. Then it adds new BPF helpers on top of those upstream patches. * 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. 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 1934304] Re: i2c-mlxbf.c: prevent stack overflow in mlxbf_i2c_smbus_start_transaction
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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1934304 Title: i2c-mlxbf.c: prevent stack overflow in mlxbf_i2c_smbus_start_transaction Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] There could be stack overflow in mlxbf_i2c_smbus_start_transaction(). memcpy() is called in a loop while 'operation->length' upper bound is not checked and 'data_idx' also increments. More details: The operation length is verified by the caller functions so it cannot exceed I2C_SMBUS_BLOCK_MAX bytes (32 bytes) for each operation that is a part of the write. Data_desc array is 128 bytes in size. So potentially a request which consists of 4 writes, 32 bytes each can trigger an off-by-one or off-by-two overflow, because the first byte of data_desc is used by addr, effectively decreasing the available data_desc buffer size by one. Functions like mlx_smbus_i2c_block_func() that prepare the request also set the length of the first write operation to one and store the command id there, so the target buffer size again decreases data_desc by one, making it two bytes less than expected. [Fix] * Add a check for "operation->length" and data_idx and return error if reached upper bound. [Test Case] * Test the i2c-mlxbf.c driver using IPMB functionality. [Regression Potential] This fix returns a negative value to indicate that a transaction has failed. So it will catch more transactions failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934304/+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 1934401] Re: Control netfilter flow table timeouts via sysctl
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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1934401 Title: Control netfilter flow table timeouts via sysctl Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) TCP and UDP connections may be offloaded from nf conntrack to nf flow table. Offloaded connections are aged after 30 seconds of inactivity. Once aged, ownership is returned to conntrack with a hard coded tcp/udp pickup time of 120/30 seconds, after which the connection may be deleted. The current hard-coded pickup intervals may introduce a very aggressive aging policy. For example, offloaded tcp connections in established state will timeout from nf conntrack after just 150 seconds of inactivity, instead of 5 days. In addition, the hard-coded 30 second offload timeout period can significantly increase the hardware insertion rate requirements in some use cases. * Brief explanation of fixes This patchset provides the user with the ability to configure protocol specific offload timeout and pickup intervals via sysctl. The first and second patches revert the existing non-upstream solution. The next two patches introduce the sysctl configuration for tcp and udp protocols. The last patch modifies nf flow table aging mechanisms to use the configured time intervals. * How to test Control tcp/udp connection timeout using the following sysctl parameters: net.netfilter.nf_flowtable_tcp_pickup = 120 net.netfilter.nf_flowtable_tcp_timeout = 30 net.netfilter.nf_flowtable_udp_pickup = 30 net.netfilter.nf_flowtable_udp_timeout = 30 * What it could break. Existing configuration scripts – not kernel related To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934401/+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 1931843] Re: Update mlx-bootctl to access new fields in EEPROM MFG
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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1931843 Title: Update mlx-bootctl to access new fields in EEPROM MFG Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] The EEPROM MFG partition on BlueField-2 has been updated to include the VPD information for each card. In order to access these newly added fields, the mlx-bootctl driver needs to be updated to provide an access mechanism. [Fix] Add support for VPD fields in the EEPROM MFG and provide access to these via sysfs entries. The newly added sysfs entries are: sku (SKU ID), modl (Model Number), sn (Serial Number) and uuid (UUID). And the previously added opn_str sysfs has been renamed to opn. [Test Case] Though the driver provides read and write access through sysfs, the contents of the MFG partition are written during Manufacturing and then locked in order to protect the info. Writing to this partition will therefore require resetting the MFG info from the UEFI Device Manager, which will unlock the partition and allow for it to be reprogrammed. Reading the sysfs entries will print the contents of each field. It could also be empty if the field was not programmed earlier. [Regression Potential] Can be considered minimum, since the new fields have been added without interfering with the existing fields which might already be present in the EEPROM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1931843/+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 1929902] Re: [EHL] enable USB-dw3
@Jesse Sung The following is the response from the feature owner 1. This patch doesn’t change the functionality on the usb-dw3 for EHL, it mainly renames the PCI device define to ensure no misunderstanding on there’s an LP (low power version) available. 2. As for the effect on changing this, EHL will allow the PM runtime & other logic within dwc3 to use the ACPI DSM to put the IP into low power, as it depends on the specific PMU registers programming to truly set it to low power. Meanwhile, the other dwc3-pci functionality remains unaffected. I prefer to merge it into your kernel tree and it can run into low power mode if the platform has the capability. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929902 Title: [EHL] enable USB-dw3 Status in intel: New Status in linux package in Ubuntu: New Status in linux-intel package in Ubuntu: In Progress Bug description: Description Enable USB-dw3 for Elkhart Lake Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929902/+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
