[Kernel-packages] [Bug 1947829] Re: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS
[5.656047] mt7921e :02:00.0: enabling device ( -> 0002) [5.656529] mt7921e :02:00.0: ASIC revision: 79610010 [5.787109] mt7921 mcu reset 0 [5.788869] mt7921 rx type 0x7 [5.788877] mt7921 eid 0x4 ext_eid 0x2 [5.70] mt76_rx_event eid 0x4 ext_eid 0x2 [5.789545] mt7921e :02:00.0: HW/SW Version: 0x8a108a10, Build Time: 20210612122717a [5.789548] mt7921 mcu reset 0 [5.790625] mt7921 rx type 0x7 [5.790625] mt7921 eid 0x1 ext_eid 0x0 [5.790626] mt76_rx_event eid 0x1 ext_eid 0x0 [5.790737] mt7921 mcu reset 0 [5.795575] mt7921 rx type 0x7 [5.795577] mt7921 eid 0x1 ext_eid 0x0 [5.795579] mt76_rx_event eid 0x1 ext_eid 0x0 [5.795591] mt7921 mcu reset 0 [5.795671] mt7921 rx type 0x7 [5.795671] mt7921 eid 0x4 ext_eid 0x3 [5.795672] mt76_rx_event eid 0x4 ext_eid 0x3 [5.796374] mt7921e :02:00.0: WM Firmware Version: 01, Build Time: 20210612122753 [5.796376] mt7921 mcu reset 0 [5.797540] mt7921 rx type 0x7 [5.797547] mt7921 eid 0x1 ext_eid 0x0 [5.797550] mt76_rx_event eid 0x1 ext_eid 0x0 [5.797966] mt7921 mcu reset 0 [5.802381] mt7921 rx type 0x7 [5.802382] mt7921 eid 0x1 ext_eid 0x0 [5.802383] mt76_rx_event eid 0x1 ext_eid 0x0 [5.802696] mt7921 mcu reset 0 [5.806039] mt7921 rx type 0x7 [5.806041] mt7921 eid 0x1 ext_eid 0x0 [5.806041] mt76_rx_event eid 0x1 ext_eid 0x0 [5.806075] mt7921 mcu reset 0 [5.807652] mt7921 rx type 0x7 [5.807656] mt7921 eid 0x1 ext_eid 0x0 [5.807659] mt76_rx_event eid 0x1 ext_eid 0x0 [5.808067] mt7921 mcu reset 0 [5.827134] mt7921 rx type 0x7 [5.827137] mt7921 eid 0x1 ext_eid 0x0 [5.827138] mt76_rx_event eid 0x1 ext_eid 0x0 [5.827172] mt7921e :02:00.0: Firmware init done [5.827177] mt7921 mcu reset 0 [5.831100] mt7921 rx type 0x7 [5.831103] mt7921 eid 0xec ext_eid 0x0 [5.831104] mt76_rx_event eid 0xec ext_eid 0x0 then repeatedly reset mcu forever. ** Attachment added: "dmesg_20210915" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1947829/+attachment/5534519/+files/dmesg_20210915 -- 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/1947829 Title: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: In Progress Status in linux-firmware source package in Impish: In Progress Bug description: [Reproduce Steps] 1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS. 2.During OOBE, Open the settings, there is no wireless settings in the panel,and the wifi cannot be used,issue occurred. [Results] Expected Result:The wireless settings should be exists and wifi can be used Actual Result:The wireless settings not exists and wifi can not be used To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1947829/+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 1947829] Re: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS
MT7921 is supported starting from Impish. Impish has already the latest
MT7921 bluetooth fw, but still misses the WiFi one, commit d34196f5
("linux-firmware: update firmware for MT7921 WiFi device").
** Also affects: linux-firmware (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-firmware (Ubuntu)
Status: New => Fix Released
** Also affects: linux-firmware (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: linux-firmware (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Impish)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux-firmware (Ubuntu Impish)
Importance: Undecided => High
** Changed in: linux-firmware (Ubuntu Focal)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-firmware (Ubuntu Impish)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
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/1947829
Title:
Cannot identified WLAN card MT7921 in Ubunut OS with Install OS
complete first OOBE Boot OS
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Focal:
In Progress
Status in linux-firmware source package in Impish:
In Progress
Bug description:
[Reproduce Steps]
1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS.
2.During OOBE, Open the settings, there is no wireless settings in the
panel,and the wifi cannot be used,issue occurred.
[Results]
Expected Result:The wireless settings should be exists and wifi can be used
Actual Result:The wireless settings not exists and wifi can not be used
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1947829/+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 1947829] [NEW] Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS
Public bug reported: [Reproduce Steps] 1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS. 2.During OOBE, Open the settings, there is no wireless settings in the panel,and the wifi cannot be used,issue occurred. [Results] Expected Result:The wireless settings should be exists and wifi can be used Actual Result:The wireless settings not exists and wifi can not be used ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Tags: hwe-networking-wifi oem-priority originate-from-1941014 somerville ** Tags added: oem-priority originate-from-1941014 somerville -- 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/1947829 Title: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: New Bug description: [Reproduce Steps] 1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS. 2.During OOBE, Open the settings, there is no wireless settings in the panel,and the wifi cannot be used,issue occurred. [Results] Expected Result:The wireless settings should be exists and wifi can be used Actual Result:The wireless settings not exists and wifi can not be used To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1947829/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
I don't believe `fimd` is sufficient, but running `stat` on a file was enough to trigger it for me. -- 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/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in zfs-linux source package in Impish: Fix Released Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_lookup+0x202/0x3b0 [zfs] zpl_lookup+0xca/0x1e0 [zfs] path_openat+0x6a2/0xfe0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+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 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
** Changed in: zfs-linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: zfs-linux (Ubuntu Focal) Importance: Undecided => High -- 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/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+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 1945211] Re: Fix cold plugged USB device on certain PCIe USB cards
** Tags removed: verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945211 Title: Fix cold plugged USB device on certain PCIe USB cards Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: [SRU Justification] [Impact] Cold plugged USB device was not detected on certain PCIe USB cards (like Inateck card connected to AM64 EVM or connected to J7200 EVM). And also the root hub mentioned in https://bugs.launchpad.net/bugs/1939638. Re-plugging the USB device always gets it enumerated. [Fix] As soonprimary roothub is registered, port status change is handled even before xHC is running and leads to cold plug USB devices not detected. Register both root hubs along with the secondary hcd for xhci. [Test Case] 1. Plug the USB device to the ports of problematic root hub. 2. Power on the machine. 3. Check if the USB device can work or not after boot. [Regression Potential] Low. It simply make sure both primary and secondary roothubs are registered along with the second HCD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945211/+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 1944955] Re: Update the 470 NVIDIA driver to 470.74
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Jammy) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: In Progress ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Impish) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Jammy) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Impish) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1944955 Title: Update the 470 NVIDIA driver to 470.74 Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Released Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Bug description: Update the 470 (UDA) NVIDIA series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.74 (470) == * New upstream release: - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Updated nvidia-bug-report.sh to search the systemd journal for gdm-x-session logs. - Fixed a bug that could prevent nvidia-xconfig from disabling the X Composite extension on version 1.20 of the X.org X server. - Fixed a build failure, "too many arguments to function 'get_user_pages'", when building the NVIDIA kernel module for Linux kernel v4.4.168. - Fixed a build failure, "implicit declaration of function do_gettimeofday", when building the NVIDIA kernel module for Linux kernel 5.0 release candidates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1944955/+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 1947820] [NEW] [SRU] Backport xorg-server 1.20.13 to focal
Public bug reported: [Impact] The delay phenomenon is serious in 'External display mode' during the 'On-demand' mode working. Please reference lp:1940247 and lp:1919118. [Fix] I installed 21.10 on Raptor12(ThinkPad-P15-Gen-2i), with xorg-server 2:1.20.13-1ubuntu1 and nvidia-495.38 test driver, this issue is solved. But in 20.04, it's still 2:1.20.11-1ubuntu1~20.04.2. [Test] On Raptor12(ThinkPad-P15-Gen-2i), P17 Gen 2 and P1 Gen 4, with latest 20.04, it could be reproduced. [Where problems could occur] Although the nvidia driver is not released, I thought it's no harm to upgrade xorg-server first. ** Affects: oem-priority Importance: Critical Assignee: Bin Li (binli) Status: New ** Affects: xorg-server Importance: Undecided Status: New ** Tags: oem-priority originate-from-1919118 sutton ** Also affects: xorg-server Importance: Undecided Status: New ** No longer affects: linux-firmware (Ubuntu) ** Tags added: oem-priority originate-from-1919118 sutton ** Changed in: oem-priority Assignee: (unassigned) => Bin Li (binli) ** Changed in: oem-priority Importance: Undecided => Critical ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1028 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1028 -- 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/1947820 Title: [SRU] Backport xorg-server 1.20.13 to focal Status in OEM Priority Project: New Status in X.Org X server: New Bug description: [Impact] The delay phenomenon is serious in 'External display mode' during the 'On-demand' mode working. Please reference lp:1940247 and lp:1919118. [Fix] I installed 21.10 on Raptor12(ThinkPad-P15-Gen-2i), with xorg-server 2:1.20.13-1ubuntu1 and nvidia-495.38 test driver, this issue is solved. But in 20.04, it's still 2:1.20.11-1ubuntu1~20.04.2. [Test] On Raptor12(ThinkPad-P15-Gen-2i), P17 Gen 2 and P1 Gen 4, with latest 20.04, it could be reproduced. [Where problems could occur] Although the nvidia driver is not released, I thought it's no harm to upgrade xorg-server first. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1947820/+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 1947819] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1947819 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947819 Title: Can't resume from sleep on on ThinkPad P14S Gen 2 Status in linux package in Ubuntu: Incomplete Bug description: If it goes to sleep, it doesn't wake back up again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947819/+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
All 7 packages were not yet available from software updater in focal but I managed to upgrade them using apt-get upgrade and seems to work fine. Thanks all again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. 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. E
[Kernel-packages] [Bug 1947819] [NEW] Can't resume from sleep on on ThinkPad P14S Gen 2
Public bug reported: If it goes to sleep, it doesn't wake back up again. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947819 Title: Can't resume from sleep on on ThinkPad P14S Gen 2 Status in linux package in Ubuntu: New Bug description: If it goes to sleep, it doesn't wake back up again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947819/+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 1947818] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1947818 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947818 Title: The fans are constantly whirring on ThinkPad P14S Gen 2 Status in linux package in Ubuntu: Incomplete Bug description: The fans are constantly whirring despite next to no CPU usage, it's quite loud, on versions 20.04, 21.04 and 21.10 it has the same issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947818/+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 1947818] [NEW] The fans are constantly whirring on ThinkPad P14S Gen 2
Public bug reported: The fans are constantly whirring despite next to no CPU usage, it's quite loud, on versions 20.04, 21.04 and 21.10 it has the same issues. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1947818 Title: The fans are constantly whirring on ThinkPad P14S Gen 2 Status in linux package in Ubuntu: Incomplete Bug description: The fans are constantly whirring despite next to no CPU usage, it's quite loud, on versions 20.04, 21.04 and 21.10 it has the same issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947818/+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 1944955] Re: Update the 470 NVIDIA driver to 470.74
as linux-modules-nvidia-470-oem-20.04d 5.14.0-1005.5 from update channel depends nvidia-dkms-470 470.74 but nvidia-dkms-470 470.74 still in proposed. This will beark OEM project process. Can we release this one already? ** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1944955 Title: Update the 470 NVIDIA driver to 470.74 Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Bug description: Update the 470 (UDA) NVIDIA series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.74 (470) == * New upstream release: - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Updated nvidia-bug-report.sh to search the systemd journal for gdm-x-session logs. - Fixed a bug that could prevent nvidia-xconfig from disabling the X Composite extension on version 1.20 of the X.org X server. - Fixed a build failure, "too many arguments to function 'get_user_pages'", when building the NVIDIA kernel module for Linux kernel v4.4.168. - Fixed a build failure, "implicit declaration of function do_gettimeofday", when building the NVIDIA kernel module for Linux kernel 5.0 release candidates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1944955/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
To check if any of the files in a given directory were corrupted due to this bug, would it be sufficient to run "sudo find ." and check if the command returns without any error or without getting stuck at a file? -- 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/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in zfs-linux source package in Impish: Fix Released Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_lookup+0x202/0x3b0 [zfs] zpl_lookup+0xca/0x1e0 [zfs] path_openat+0x6a2/0xfe0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+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 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
So removing quiet splash and adding noefi to grub and editing sudo xdg-open /etc/systemd/system.conf removing the # infront of #DefaultTimeoutStopSec=90s and changing the timeout to 10s instead of 90s Seem to have fixed my issue I found the last bit here: https://itsfoss.com/long-shutdown-linux/ Please comment and let me know if it solves it for you 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/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1594023/+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 1894064] Re: lubuntu groovy QA-test live session locked up
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1894064 Title: lubuntu groovy QA-test live session locked up Status in linux package in Ubuntu: Incomplete Bug description: Lubuntu groovy 'live' QA-test on hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600) Test went for some time, then on waking xscreensaver (testing for a bug), the session froze (news being streamed was still audible) I attempted to fix (see below), but was unable. On switching to text term (ctrl+alt+F4) audio ended (I was streaming news in firefox) & nothing responded (numlock & capslock had already stopped responding on GUI lock up). This report will be of little value I suspect, as the logs are of a new session given I was unable to recover the first session (which had the useful logs). Refer to iso.qa.ubuntu.com for test details.. Key paste from the link will be as follows --- ... this session went for some time, I had screensaver kick in, plus stated it looking for http://launchpad.net/bugs/1855220 (choppy issues) and didn't notice anything choppy (maybe these screens but a different box)... However after waking screensaver for a "preview" the session was not recoverable... news kept streaming so session was running.. but session appeared unrecoverable.. using ctrl+alt+F4 shut news up.. but screen did not change. black upper display still (it went black when I stopped xscreensaver preview, pointer visible on top display but won't move.. and bottom display shows a stuck flurry screen still). I was unable to recover session, could not use a text terminal either and strangely he numlock/capslock keys weren't even changing the LEDs on the keyboard.. No mouse movement after I tried to end xscreensaver preview. - the upper display had returned to black (flurry xscreensaver image gone where I was expecting the streaming firefox/news to return but no - mouse pointer was drawn on upper display - lower display stayed locked on a frozen flurry (xscreensaver) screen I've machine (with SysRq REISUB) and will file bug from there, alas as session is lost the bug report will be near meaningless, but filed for this QA anyway. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-16-generic 5.8.0-16.17 ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0 Uname: Linux 5.8.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1552 F pulseaudio /dev/snd/controlC1: lubuntu1552 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: LXQt CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 3 08:32:43 2020 IwConfig: lono wireless extensions. eno1 no wireless extensions. LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200902) MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.8.0-16-generic N/A linux-backports-modules-5.8.0-16-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2011 dmi.bios.release: 2.6 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.06 dmi.board.asset.tag: AUD14001GG dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: AUD14001GG dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.06:bd06/09/2011:br2.6:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.product.sku: XL510AV dmi.sys.vendor: Hewlett-Packard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1527 F pulseaudio
[Kernel-packages] [Bug 1946686] Re: Fix zfs_get_data access to files with wrong generation causing panics
Hello Andrew, 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.14 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/1946686 Title: Fix zfs_get_data access to files with wrong generation causing panics Status in zfs-linux package in Ubuntu: In Progress Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Hirsute: Fix Committed Status in zfs-linux source package in Impish: Fix Released Bug description: == SRU Focal/Hirsute == [Impact] ZFS: Fix a panic while acquiring a lock. If TX_WRITE is create on a file, and the file is later deleted and a new directory is created on the same object id, it is possible that when zil_commit happens, zfs_get_data will be called on the new directory. This may result in panic as it tries to do range lock. Upstream ZFS bug #10593, #11682, upstream fix: commit 296a4a369bc1078a694f88570972330985b3b1b8 Author: Chunwei Chen Date: Fri Mar 19 22:53:31 2021 -0700 Fix zfs_get_data access to files with wrong generation This patch fixes this issue by record the generation number during zfs_log_write, so zfs_get_data can check if the object is valid. The fix is already in Ubuntu ZFS 2.0.6 in Impish. The fix is a relatively simple backport with only minor backporting effort required in moving some of the module specific upstream changes into the pre- renamed module specific os specific parts of the ZFS module. [Test Plan] This is difficult to reproduce, see https://github.com/openzfs/zfs/issues/10593 The fix has been tested with the complete ubuntu autotest ZFS regression tests that exercise ZFS core functionality (smoke tests), file system POSIX compliance (fs tests), extra XFS tests and every mount option with stress-ng file I/O stress tests. [Where problems could occur] This fix could regress the ZIL (ZFS intent log) commit writes since it modifies this code to now checks for generation numbers. Testing with ZFS autotests with intent logs have not found any regressions, but there is a risk that the ZIL functionality is affected. This could lead to corruption. -- As mentioned at https://answers.launchpad.net/ubuntu/+source/zfs- linux/+question/696659, the following pull request fixes a panic acquiring a lock: https://github.com/openzfs/zfs/pull/11682 This fix does not appear to be a part of the latest Ubuntu 20.04 release: zfsutils-linux: Installed: 0.8.3-1ubuntu12.12 Candidate: 0.8.3-1ubuntu12.12 Version table: *** 0.8.3-1ubuntu12.12 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12.9 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 0.8.3-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Of note is this issue where the bug is reported against the Ubuntu 0.8.3 packages: https://github.com/openzfs/zfs/issues/10642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1946686/+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 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu12.13 --- zfs-linux (0.8.3-1ubuntu12.13) focal; urgency=medium * Fix zfs receive -s when using ZFS 2.x kernel drivers (LP: #1939177) - 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch - 4911-compat-nullify-action-handle.patch -- Colin Ian King Mon, 16 Aug 2021 15:55:52 +0100 ** Changed in: zfs-linux (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Fix Released Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+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 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
For some reason this doesn't seem to have the normal SRU verification tags, but this appears to be verified to me. Releasing. -- 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/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Fix Released Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+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 1939177] Update Released
The verification of the Stable Release Update for zfs-linux has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Fix Released Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+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 1662620] Re: "ip addr add" permits illegal labels
Hm. It's not clear what the actual user impact of this is? Reading from the original description, it seems that if a user uses an invalid label to set one address and *also* uses a valid label to set another address *then* tools can be confused? “Our parser is actually more lenient than the manpage states” on its own is definitely not SRU-worthy, but if it breaks other tools then maybe? On the other hand, from the bug it looks like if you *don't* mix valid and invalid labels then everything actually works? So this would potentially be breaking currently working setups? I think we need more information before determining whether this should be accepted as an SRU. ** Changed in: iproute2 (Ubuntu Bionic) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1662620 Title: "ip addr add" permits illegal labels Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Incomplete Bug description: [Impact] * The filter on label names does not match the intention by upstream nor the description in the man page * Fix by backporting upstream fix that strengthens the check [Test Plan] Bad case: root@b:~# ip addr add 1.1.1.1 label test1 dev eth0 "dev" (eth0) must match "label" (test1). root@b:~# ip addr add 1.1.1.1 label eth0-test dev eth0 root@b:~# ip addr show dev eth0 | grep test inet 1.1.1.1/32 scope global eth0-test With the fix it should look like: root@i:~# ip addr add 1.1.1.1 label test1 dev eth0 "label" (test1) must match "dev" (eth0) or be prefixed by "dev" with a colon. root@i:~# ip addr add 1.1.1.1 label eth0-test dev eth0 "label" (eth0-test) must match "dev" (eth0) or be prefixed by "dev" with a colon. root@i:~# ip addr show dev eth0 | grep test [Where problems could occur] * While the fix indeed "corrects" behavior I must say that if someone relied on the non-intended behavior it would now break e.g. his scripting or automation. [Other Info] * It was too easy to fix and too long dormant to ignore it further, but if the SRU team says this is too much regression risk relative to the gain we will mark it Won't Fix based on that decision. --- ip-address(8) manpage states: label NAME Each address may be tagged with a label string. In order to preserve compatibility with Linux-2.0 net aliases, this string must coincide with the name of the device or must be prefixed with the device name followed by colon. But you can omit the colon, "ip addr add" is ONLY checking the label is prefixed with the device: # ip addr add 1.1.1.1 label test1 dev eth0 "dev" (eth0) must match "label" (test1). # ip addr add 1.1.1.2 label eth0-test2 dev eth0 # ip addr add 1.1.1.3 label eth0:test3 dev eth0 Now ifconfig becomes confused about eth0-test2: # ifconfig eth0-test2 eth0-test2: error fetching interface information: Device not found # ifconfig eth0:test3 eth0:test3 Link encap:Ethernet HWaddr b0:d5:cc:fe:1d:7c inet addr:1.1.1.3 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:171 And daemons like ntpd also log errors about the interface with the illegal label: ntpd[7570]: eth0-test3: getting interface flags: No such device ## => many of this error per minute until: ntpd[7570]: Too many errors. Shutting up. So, I think ip addr show disallow adding address with illegal (as stated by his own documentation) labels, it must also check for the colon following the dev name. Version: 4.3.0-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1662620/+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 1947498] Re: zfs/zpool encryption crash on server 21.10
There's more trouble. I just copied several TB of data by zfs send | zfs recv from a 20.04 machine to this new machine. Worked well for hours, but at the end some crash messages, see attached second dmesg. ZFS as it comes with 21.10 is definitely not production ready. ** Attachment added: "dmesg output of kernel problems" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1947498/+attachment/5534455/+files/dmesg2 -- 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/1947498 Title: zfs/zpool encryption crash on server 21.10 Status in zfs-linux package in Ubuntu: New Bug description: Hi, just installed a new HPE microserver with SSD and four harddisks with new 21.10 server and tried to create a zpool with zpool create pool1 raidz2 /dev/sda /dev/sdb /dev/sdc /dev/sdd -O encryption=on -O keyformat=passphrase which reproducably crashed twice with the attached kernel message. The zpool then exists, but is not encrypted. zpool create pool1 raidz2 /dev/sda /dev/sdb /dev/sdc /dev/sdd without the option works and a subsequent zfs create pool1/sub -o encryption=on -o keyformat=passphrase works as well. Which is, however, not a real workaround for a fully encrypted pool (which worked under 20.04). regards ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: zfsutils-linux 2.0.6-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Oct 17 12:44:15 2021 InstallationDate: Installed on 2021-10-17 (0 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release amd64 (20211013) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1947498/+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 1947492] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534445/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534448/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534442/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534446/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534437/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534451/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534441/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534440/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534447/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534443/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/553/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534452/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534450/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534438/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534436/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534449/+files/RfKill.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/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534439/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534435/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947492/+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 1947492] Re: after update my laptop keyboard is not working
apport information ** Tags added: apport-collected ** Description changed: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.20 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: joseth 2859 F pulseaudio + /dev/snd/controlC0: joseth 2859 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + MachineType: Dell Inc. Inspiron 5458 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 + RelatedPackageVersions: + linux-restricted-modules-5.11.0-37-generic N/A + linux-backports-modules-5.11.0-37-generic N/A + linux-firmware 1.187.19 + Tags: focal + Uname: Linux 5.11.0-37-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/06/2015 + dmi.bios.release: 5.6 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A04 + dmi.board.name: 0V84JT + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/06/2015:br5.6:svnDellInc.:pnInspiron5458:pvr01:skuInspiron5458:rvnDellInc.:rn0V84JT:rvrA00:cvnDellInc.:ct9:cvr: + dmi.product.name: Inspiron 5458 + dmi.product.sku: Inspiron 5458 + dmi.product.version: 01 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1947492/+attachment/5534434/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947492 Title: after update my laptop keyboard is not working Status in linux package in Ubuntu: Incomplete Bug description: I have hardware issues on the new update, my laptop keyboard seems to be not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:57:44 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joseth 2859 F pulseaudio /dev/snd/controlC0: joseth 2859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: Dell Inc. Inspiron 5458 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=5c72b17e-5824-4f9f-a2a2-0b16ef4c1bdd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.11.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/06/2015 dmi.bios.release: 5.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0V84JT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell
[Kernel-packages] [Bug 1941708] Re: BlueZ 5.62 release
** Changed in: bluez (Ubuntu) Importance: Undecided => Wishlist ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1941708 Title: BlueZ 5.62 release Status in bluez package in Ubuntu: In Progress Bug description: BlueZ 5.62 release is out: https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941708/+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 1912811] Re: Update dwarves-dfsg in focal to version 1.21 from impish
This bug was fixed in the package dwarves-dfsg - 1.21-0ubuntu1~20.04 --- dwarves-dfsg (1.21-0ubuntu1~20.04) focal; urgency=medium * Backport new dwarves-dfsg to stable series without upgrading libbpf system-wide (LP: #1912811): + Update lib/bpf to libbpf_0.4.0-1ubuntu1. + Disable lto, since it is disabled in libbpf. + Build with embedded libbpf. + Drop libbpf-dev build dependency. + Lower debhelper-compat to 12. -- Dimitri John Ledkov Mon, 20 Sep 2021 13:10:02 +0100 ** Changed in: dwarves-dfsg (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: dwarves-dfsg (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libbpf in Ubuntu. https://bugs.launchpad.net/bugs/1912811 Title: Update dwarves-dfsg in focal to version 1.21 from impish Status in dwarves-dfsg package in Ubuntu: Invalid Status in libbpf package in Ubuntu: Fix Released Status in dwarves-dfsg source package in Bionic: In Progress Status in libbpf source package in Bionic: New Status in dwarves-dfsg source package in Focal: Fix Released Status in libbpf source package in Focal: Won't Fix Status in dwarves-dfsg source package in Groovy: Won't Fix Status in libbpf source package in Groovy: Won't Fix Status in dwarves-dfsg source package in Hirsute: Fix Released Status in libbpf source package in Hirsute: Won't Fix Bug description: [Impact] BTF is an extremely useful tool for BPF developers. Enabling BTF support in the HWE kernel requires pahole from dwarves-dfsg 1.21 or later, but in focal we have only 1.15. The simplest path for us to get a sufficiently updated version of pahole is to backport dwarves-dfsg from hirsute, which is at version 1.21 with v5.13 compat fixes. [Test Case] Building a v5.13 based kernel with CONFIG_DEBUG_INFO_BTF enabled fails with the version of pahole currently in focal, complaining that pahole 1.16 or later is needed. Building with a newer version of pahole is successful. [Where problems could occur] Moving the package forward carries significant risks. The biggest risk is clearly new bugs. There may also be interface changes which break existing workflows. I believe the following factors indicate that the level of risk here is acceptable: * Currently there are no bug reports open against the package in groovy (there are virtually no bug reports open at all against the package in fact). * I have done a review of the changes between 1.15 and 1.21. The bulk of the changes are for the required BTF support, and the vast majority of these are an update of its local copy of libbpf. The balance of the changes are bug fixes and enhancements to pahole, none of which look to change the user interface in a way which will break existing workflows. Note that in later releases libbpf is now packaged stand alone, so this SRU covers libbpf as well. * But also the 1.15 dwarves is kind of useless, as it doesn't work with latest kernels for the BPF features. * No packages in focal have dependencies or build dependencies on the dwarves package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811/+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 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
@arighi hi Andrea, any update on where this is going? is there anything else we can do to test or provide extra info? even "still investigating" would be good to know. ;) cheers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX 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.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+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 1947601] Re: Cannot start docker container on ubuntu 21.10 server for 64-bit raspberry pi
After downgrading the linux kernel to the latest version shipped with ubuntu 21.04 and rebooting, executing a docker container works in ubuntu 21.10 for 64-bit Raspberry Pi. The downgrading can be achieved like this: 1) Add the hirsute apt repositories to /etc/apt/sources.list 2) sudo apt install linux-image-5.11.0-1021-raspi 3) sudo flash-kernel --force 5.11.0-1021-raspi 4) Reboot. This indicates that there really is a problem with the current kernel in 21.10 that prevents execution of docker containers. -- 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/1947601 Title: Cannot start docker container on ubuntu 21.10 server for 64-bit raspberry pi Status in linux package in Ubuntu: Confirmed Bug description: Using the Ubuntu image for Raspberry Pi from here: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled- server-arm64+raspi.img.xz After installing the docker.io package, I cannot start a docker container. Example: $ sudo docker run --rm hello-world docker: Error response from daemon: failed to create endpoint pensive_greider on network bridge: failed to add the host (veth2102512) <=> sandbox (veth4fb66df) pair interfaces: operation not supported. This was working in the previous ubuntu release for 64 bit raspberry pi, 21.04. Searching for this error suggests it could be a problem with linux kernel module availability. Attaching info generated by ubuntu-bug for package linux-image-raspi. I can only attach 1 file, therefore inlining the ubuntu-bug info for package docker.io (output is far shorter than for the kernel): ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Oct 18 14:10:27 2021 Dependencies: adduser 3.118ubuntu5 apparmor 3.0.3-0ubuntu1 apt 2.3.9 apt-utils 2.3.9 bridge-utils 1.7-1ubuntu2 ca-certificates 20210119ubuntu1 containerd 1.5.5-0ubuntu3 dbus 1.12.20-2ubuntu2 debconf 1.5.77 debconf-i18n 1.5.77 dmsetup 2:1.02.175-2.1ubuntu3 dns-root-data 2021011101 dnsmasq-base 2.85-1ubuntu2 dpkg 1.20.9ubuntu2 gcc-11-base 11.2.0-7ubuntu2 git 1:2.32.0-1ubuntu1 git-man 1:2.32.0-1ubuntu1 gpgv 2.2.20-1ubuntu4 iproute2 5.10.0-4ubuntu1 iptables 1.8.7-1ubuntu2 less 551-2 libacl1 2.2.53-10ubuntu2 libapparmor1 3.0.3-0ubuntu1 libapt-pkg6.0 2.3.9 libatm1 1:2.5.1-4build1 libaudit-common 1:3.0-2ubuntu2 libaudit1 1:3.0-2ubuntu2 libbpf0 1:0.4.0-1ubuntu1 libbrotli1 1.0.9-2build3 libbsd0 0.11.3-1ubuntu2 libbz2-1.0 1.0.8-4ubuntu3 libc6 2.34-0ubuntu3 libcap-ng0 0.7.9-2.2build1 libcap2 1:2.44-1build1 libcap2-bin 1:2.44-1build1 libcom-err2 1.46.3-1ubuntu3 libcrypt1 1:4.4.18-4ubuntu1 libcurl3-gnutls 7.74.0-1.3ubuntu2 libdb5.3 5.3.28+dfsg1-0.8ubuntu1 libdbus-1-3 1.12.20-2ubuntu2 libdevmapper1.02.1 2:1.02.175-2.1ubuntu3 libelf1 0.185-1build1 liberror-perl 0.17029-1 libexpat1 2.4.1-2 libffi8 3.4.2-1ubuntu5 libgcc-s1 11.2.0-7ubuntu2 libgcrypt20 1.8.7-5ubuntu2 libgdbm-compat4 1.19-2 libgdbm6 1.19-2 libgmp10 2:6.2.1+dfsg-1ubuntu2 libgnutls30 3.7.1-5ubuntu1 libgpg-error0 1.38-2build1 libgssapi-krb5-2 1.18.3-6 libhogweed6 3.7.3-1 libidn2-0 2.3.1-1 libip4tc2 1.8.7-1ubuntu2 libip6tc2 1.8.7-1ubuntu2 libk5crypto3 1.18.3-6 libkeyutils1 1.6.1-2ubuntu1 libkrb5-3 1.18.3-6 libkrb5support0 1.18.3-6 libldap-2.5-0 2.5.6+dfsg-1~exp1ubuntu1 libldap-common 2.5.6+dfsg-1~exp1ubuntu1 liblocale-gettext-perl 1.07-4build1 liblz4-1 1.9.3-2 liblzma5 5.2.5-2 libmd0 1.0.3-3build1 libmnl0 1.0.4-3 libnetfilter-conntrack3 1.0.8-3 libnettle8 3.7.3-1 libnfnetlink0 1.0.1-3build1 libnftnl11 1.1.9-1 libnghttp2-14 1.43.0-1 libnsl2 1.3.0-2build1 libp11-kit0 0.23.22-1build1 libpam-cap 1:2.44-1build1 libpam-modules 1.3.1-5ubuntu11 libpam-modules-bin 1.3.1-5ubuntu11 libpam-runtime 1.3.1-5ubuntu11 libpam0g 1.3.1-5ubuntu11 libpcre2-8-0 10.37-0ubuntu2 libperl5.32 5.32.1-3ubuntu3 libpsl5 0.21.0-1.2 librtmp1 2.4+20151223.gitfa8646d.1-2build3 libsasl2-2 2.1.27+dfsg-2.1build1 libsasl2-modules 2.1.27+dfsg-2.1build1 libsasl2-modules-db 2.1.27+dfsg-2.1build1 libseccomp2 2.5.1-1ubuntu1 libselinux1 3.1-3build2 libsemanage-common 3.1-1ubuntu2 libsemanage1 3.1-1ubuntu2 libsepol1 3.1-1ubuntu2 libssh-4 0.9.6-1 libssl1.1 1.1.1l-1ubuntu1 libstdc++6 11.2.0-7ubuntu2 libsystemd0 248.3-1ubuntu8 libtasn1-6 4.16.0-2 libtext-charwidth-perl 0.04-10build1 libtext-iconv-perl 1.7-7build1 libtext-wrapi18n-perl 0.06-9 libtinfo6 6.2+20201114-2build1 libtirpc-common 1.3.2-2 libtirpc3 1.3.2-2 libudev1 248.3-1ubuntu8 libunistring2 0.9.10-6 libxtables12 1.8.7-1ubuntu2 libxxhash0 0.8.0-2build1 libzstd1 1.4.8+dfsg-2.1 lsb-base 11.1.0ubuntu3 ne
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.4.0.90.94)
All autopkgtests for the newly accepted linux-meta (5.4.0.90.94) for focal have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64, arm64, ppc64el) glibc/2.31-0ubuntu9.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947781] [NEW] Hirsute update: upstream stable patchset 2021-10-19
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-10-19 Ported from the following upstream stable releases: v5.10.67, v5.13.19 from git://git.kernel.org/ rtc: tps65910: Correct driver module alias io_uring: place fixed tables under memcg limits io_uring: add ->splice_fd_in checks io_uring: fail links of cancelled timeouts io-wq: fix wakeup race when adding new work btrfs: wake up async_delalloc_pages waiters after submit btrfs: reset replace target device to allocation state on close blk-zoned: allow zone management send operations without CAP_SYS_ADMIN blk-zoned: allow BLKREPORTZONE without CAP_SYS_ADMIN PCI/MSI: Skip masking MSI-X on Xen PV powerpc/perf/hv-gpci: Fix counter value parsing xen: fix setting of max_pfn in shared_info 9p/xen: Fix end of loop tests for list_for_each_entry ceph: fix dereference of null pointer cf selftests/ftrace: Fix requirement check of README file tools/thermal/tmon: Add cross compiling support clk: socfpga: agilex: fix the parents of the psi_ref_clk clk: socfpga: agilex: fix up s2f_user0_clk representation clk: socfpga: agilex: add the bypass register for s2f_usr0 clock pinctrl: stmfx: Fix hazardous u8[] to unsigned long cast pinctrl: ingenic: Fix incorrect pull up/down info soc: qcom: aoss: Fix the out of bound usage of cooling_devs soc: aspeed: lpc-ctrl: Fix boundary check for mmap soc: aspeed: p2a-ctrl: Fix boundary check for mmap arm64: mm: Fix TLBI vs ASID rollover arm64: head: avoid over-mapping in map_memory iio: ltc2983: fix device probe wcn36xx: Ensure finish scan is not requested before start scan crypto: public_key: fix overflow during implicit conversion block: bfq: fix bfq_set_next_ioprio_data() power: supply: max17042: handle fails of reading status register dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc() crypto: ccp - shutdown SEV firmware on kexec VMCI: fix NULL pointer dereference when unmapping queue pair media: uvc: don't do DMA on stack media: rc-loopback: return number of emitters rather than error s390/qdio: fix roll-back after timeout on ESTABLISH ccw s390/qdio: cancel the ESTABLISH ccw after timeout Revert "dmaengine: imx-sdma: refine to load context only once" dmaengine: imx-sdma: remove duplicated sdma_load_context libata: add ATA_HORKAGE_NO_NCQ_TRIM for Samsung 860 and 870 SSDs ARM: 9105/1: atags_to_fdt: don't warn about stack size f2fs: fix to do sanity check for sb/cp fields correctly PCI/portdrv: Enable Bandwidth Notification only if port supports it PCI: Restrict ASMedia ASM1062 SATA Max Payload Size Supported PCI: Return ~0 data on pciconfig_read() CAP_SYS_ADMIN failure PCI: xilinx-nwl: Enable the clock through CCF PCI: aardvark: Configure PCIe resources from 'ranges' DT property PCI: Export pci_pio_to_address() for module use PCI: aardvark: Fix checking for PIO status PCI: aardvark: Fix masking and unmasking legacy INTx interrupts HID: input: do not report stylus battery state as "full" f2fs: quota: fix potential deadlock pinctrl: remove empty lines in pinctrl subsystem pinctrl: armada-37xx: Correct PWM pins definitions scsi: bsg: Remove support for SCSI_IOCTL_SEND_COMMAND clk: rockchip: drop GRF dependency for rk3328/rk3036 pll types IB/hfi1: Adjust pkey entry in index 0 RDMA/iwcm: Release resources if iw_cm module initialization fails docs: Fix infiniband uverbs minor number scsi: BusLogic: Use %X for u32 sized integer rather than %lX pinctrl: samsung: Fix pinctrl bank pin count vfio: Use config not menuconfig for VFIO_NOIOMMU scsi: ufs: Fix memory corruption by ufshcd_read_desc_param() cpuidle: pseries: Fixup CEDE0 latency only for POWER10 onwards powerpc/stacktrace: Include linux/delay.h RDMA/efa: Remove double QP type assignment RDMA/mlx5: Delete not-available udata check cpuidle: pseries: Mark pseries_idle_proble() as __init f2fs: reduce the scope of setting fsck tag when de->name_len is zero openrisc: don't printk() unconditionally dma-debug: fix debugfs initialization order NFSv4/pNFS: Fix a layoutget livelock loop NFSv4/pNFS: Always allow update of a zero valued layout barrier NFSv4/pnfs: The layout barrier indicate a minimal value for the seqid SUNRPC: Fix potential memory corruption SUNRPC/xprtrdma: Fix reconnection locking SUNRPC query transport's source port sunrpc: Fix return value of get_srcport() scsi: fdomain: Fix error return code in fdomain_probe() pinctrl: single: Fix error return code in pcs_parse_bits_in_pinctrl_entry() powerpc/numa: Consider the max NUMA node for migratable LPAR scsi: smartpqi: Fix
[Kernel-packages] [Bug 1947780] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947780 Title: Kernel module ch341 bug Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.3 LTS Kernel module ch341 in Ubuntu kernels 5.4.0-88-generic and 5.4.0-89-generic cannot program any esp8266 modules like Wemos D1 mini which contain ch340 chip uart controller. In kernel 5.4.0-86-generic everything is working good. Communication over serial connection is working in both cases only programming using esptool is broken, kernel module do not react properly to response fom ch340 chip I suppose ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: boguslaw 1801 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Oct 19 21:14:32 2021 HibernationDevice: RESUME=UUID=924612b1-306e-46c9-bd1f-7324041efb4a MachineType: Dell Inc. Latitude E6400 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=e7494ee9-8c5d-4133-bc4b-57986641b724 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A34 dmi.board.name: 0RX493 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0RX493:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947780/+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 1947780] [NEW] Kernel module ch341 bug
Public bug reported: Ubuntu 20.04.3 LTS Kernel module ch341 in Ubuntu kernels 5.4.0-88-generic and 5.4.0-89-generic cannot program any esp8266 modules like Wemos D1 mini which contain ch340 chip uart controller. In kernel 5.4.0-86-generic everything is working good. Communication over serial connection is working in both cases only programming using esptool is broken, kernel module do not react properly to response fom ch340 chip I suppose ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: boguslaw 1801 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Oct 19 21:14:32 2021 HibernationDevice: RESUME=UUID=924612b1-306e-46c9-bd1f-7324041efb4a MachineType: Dell Inc. Latitude E6400 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=e7494ee9-8c5d-4133-bc4b-57986641b724 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A34 dmi.board.name: 0RX493 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0RX493:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Description changed: Ubuntu 20.04.3 LTS - - Kernel module ch341 in Ubuntu kernels 5.4.0-88-generic i 5.4.0-89-generic cannot program any esp8266 chips with ch340 chip uart controller. In kernel 5.4.0-86-generic everything is working good + Kernel module ch341 in Ubuntu kernels 5.4.0-88-generic and 5.4.0-89-generic cannot program any esp8266 modules like Wemos D1 mini which contain ch340 chip uart controller. In kernel 5.4.0-86-generic everything is working good. + Communication over serial connection is working in both cases only programming using esptool is broken, kernel module do not react properly to response fom ch340 chip I suppose ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: boguslaw 1801 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: boguslaw 1801 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Oct 19 21:14:32 2021 HibernationDevice: RESUME=UUID=924612b1-306e-46c9-bd1f-7324041efb4a MachineType: Dell Inc. Latitude E6400 PccardctlIdent: - Socket 0: -no product info available + Socket 0: + no product info available PccardctlStatus: - Socket 0: -no card + Socket 0: + no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=e7494ee9-8c5d-4133-bc4b-57986641b724 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-89-generic N/A - linux-backports-modules-5.4.0-89-generic N/A - linux-firmware1.187.19 + linux-restricted-modules-5.4.0-89-generic N/A + linux-backports-modules-5.4.0-89-generic N/A + linux-firmware1.187.19 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A34 dmi.board.name: 0RX493 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0RX493:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. -- 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/1947780 Title: Kernel module ch341 bug Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.3 LTS Kernel module ch341 in Ubuntu kernels 5.4.0-88-generic and 5.4.0-89-generic cannot program any esp8266 modules like Wemos D1 mini which contain ch340 chip uart controller. In kernel 5.4.0-86-generic everything is working good. Communication over serial connectio
[Kernel-packages] [Bug 1947623] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534394/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD
[Kernel-packages] [Bug 1947623] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534383/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C Integrate
[Kernel-packages] [Bug 1947623] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534382/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C Integrate
[Kernel-packages] [Bug 1947623] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534390/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C Integ
[Kernel-packages] [Bug 1947623] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534377/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C
[Kernel-packages] [Bug 1947623] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534381/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C Integrated Cam
[Kernel-packages] [Bug 1947623] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534384/+files/PaInfo.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/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C Integrated C
[Kernel-packages] [Bug 1947623] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534385/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C I
[Kernel-packages] [Bug 1947623] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534380/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C Integra
[Kernel-packages] [Bug 1947623] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534386/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Int
[Kernel-packages] [Bug 1947623] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534388/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated
[Kernel-packages] [Bug 1947623] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534379/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C Integrated Cam
[Kernel-packages] [Bug 1947623] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534391/+files/RfKill.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/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C Integrated C
[Kernel-packages] [Bug 1947623] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534393/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C Int
[Kernel-packages] [Bug 1947623] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534376/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C Integrated Camer
[Kernel-packages] [Bug 1947623] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534389/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C I
[Kernel-packages] [Bug 1947623] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534392/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C Integrated C
[Kernel-packages] [Bug 1947623] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534387/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C I
[Kernel-packages] [Bug 1947623] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1947623/+attachment/5534378/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947623 Title: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD Status in linux package in Ubuntu: Confirmed Bug description: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C Integra
[Kernel-packages] [Bug 1947623] Re: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD
apport information ** Tags added: apport-collected ** Description changed: Can't boot computer after upgrade to Ubuntu 21.10, with kernel 5.13.0.19.30, because of Kernel Panic Error. It seems to be a problem with: ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad Kernel 5.11.0-38 seems to work ok. Erorr: - [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) 1.738396] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0xOd. [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7 1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw version: 0x4 [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, bcdDevice= 1.00 [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device [ 1.777283] usb 3-3: Manufacturer: Generic [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, bcdDevice=20.01 [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.788191] usb 1-3: Product: Integrated Camera [ 1.790293] usb 1-3: Manufacturer: Azuremaue [ 1.792379] usb 1-3: SerialNuMber: [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 5.13.0-19-generic #19 -Ubuntu 1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW (1.16 ) 09/06/2021 [ 1.828936] Workqueue: events long serio handle_event [ 1.828936] Call Trace: [ 1.828936] show stack+0x52/0x58 [ 1.828936] dump stack+0x7d/0x9c [ 1.828936] panic+0x101/0x2e3 [ 1.828936] ? elantech change repurt id+0x1bf/0x1c4 [psmouse] [ 1.828936] __stack_chk_fail+0x14/0x20 [ 1.828936] elantech change report id+0x1bf/0x1c4 [psmouse] [ 1.828936] elantech_query_info.cold+0X316/0x594 [psmouse] [ 1.828936] elantech_init*0x34/0x160 [psmouse] [ 1.828936] ? synaptics send cmd*0x60/0x60 Ipsmousel [ 1.828936] psmouse_extensions+0x4b6/0x520 kpsmouse] [ 1.828936] psmouse switch_protocol+0x144/0x190 [psmouse] [ 1.828936] psmouse_connect+0xI85/0x3a0 [psmouse] [ 1.828936] seriodriver_probe+0x86/0x50 [ 1.828936] really_probe+0x245/0x4c0 [ 1.828936] driver_probe device+0xf0/0x160 [ 1.828936] device_driver attach+0xab/0xbO [ 1.828936] __driver_attach+0xbZ/0x140 [ 1.828936] ? device_driver_attach+0xbO/0xbO [ 1.828936] bus_foreachdeu+0x7e/0xc0 [ 1.828936] driver_attach+0xle/0x20 [ 1.828936] serio_handle_event+0xl0f/0x290 [ 1.828936] process_one_work+0x220/0x3c0 [ 1.828936] worker_thread+0x53/0x420 [ 1.828936] kthread+0xl1f/0x140 [ 1.828936] ? process_one_work+0x3c0/0x3c0 [ 1.828936] ? set_kthread_struct+0x50/0x50 [ 1.828936] ret_from_fork+0x22/0x30 [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation range: 0x000-0xbfff) [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] ]--- --- Computer: - Computer Summary --- -Computer- Processor : AMD Ryzen 5 4500U with Radeon Graphics Memory: 23817MB (6094MB used) Machine Type : Notebook Operating System : Ubuntu 21.10 Date/Time : pon, 18 Oct 2021, 20:41:12 -Display- Resolution: 2560x1440 pixels OpenGL Renderer : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, LLVM 12.0.1) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au -Input Devices- Power Button Lid Switch Sleep Button Power Button AT Translated Set 2 keyboard Video Bus ETPS/2 Elantech TrackPoint ETPS/2 Elantech Touchpad HD-Audio Generic HDMI/DP,pcm:3 HD-Audio Generic HDMI/DP,pcm:7 HD-Audio Generic HDMI/DP,pcm:8 ThinkPad Extra Buttons HD-Audio Generic Mic HD-Audio Generic Headphone Integrated Camera: Integrated C Integrated Camera: Integrated I Compx 2.4G Wireless Receiver Compx 2.4G Wireless Receiver Mouse Compx 2.4G Wireless Receiver Compx 2.4G Wireless Receiver Keyboard Compx 2.4G Wireless Receiver Consumer Control Compx 2.4G Wireless Receiver System Control Dell Computer Corp Dell Universal Receiver Dell Computer Corp Dell Universal Receiver Mouse
[Kernel-packages] [Bug 1931725] Re: initramfs-tools & kernel: use zstd as the default compression method
How to revert to old compression method for initramfs? Generating image with zstd is extremely slow and takes long time on slow CPU. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1931725 Title: initramfs-tools & kernel: use zstd as the default compression method Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Released Bug description: Turns out that loading is always the slow part in loading initramfs into memory and decompressing it since decompression is always the final 10-20% or so of the task. It therefore makes sense to use a good compressor that shrinks the initramfs as much as possible with little decompression overhead. Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in decompression, the image size is much smaller with zstd than lz4, and since ~80-90% of the boot time is loading the image it makes sense to use zstd. Attached is a libreoffice spread sheet showing typical load and decompression times for a fairly standard 3.4 GHZ intel box with data for load times for a 5400 RPM, 7200 RPM and SATA SSD drives. The conclusions from the test results (attached) show: 1. Loading time is always significantly slower than decompression time. 2. ZSTD is 5x slower than LZ4 in decompression speed but produces far better compressed images 3. Given that loading time is the major factor in loading + decompression, ZSTD is best for kernel and initramfs boot timings. (Also refer to https://kernel.ubuntu.com/~cking/boot-speed- eoan-5.3/kernel-compression-method.txt for some raw data on drive load speeds for the same UEFI box I did a couple of years ago). amd64 supports zstd, but s390x does not. Will use this bug to enable zstd support on s390x. Upstream submitted patch https://lore.kernel.org/linux-s390/20210615114150.325080-1-dimitri.led...@canonical.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947757] Re: NVMe Write Zeroes command has incorrect values for PI modes
** Package changed: ubuntu => linux-hwe-5.4 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1947757 Title: NVMe Write Zeroes command has incorrect values for PI modes Status in linux-hwe-5.4 package in Ubuntu: New Bug description: The attached screenshot of a PCIe trace snippet is from Ubuntu 20.04.3 LTS, k5.4.0-73-generic, with an NVMe controller formatted to 4K+8 DIX PI2 It shows - A Single-sector Write Zeroes command with SLBA=0x02E18439, ILBRT=0x0 (valid for PI2), PRCHK=0x0 (no checks), PRACT=0 *, DEAC=0 **. Command succeeds. - A Single-sector Read command with SLBA=0x02E18439, EILBRT=0x02E18439, PRCHK=0x5. Command rejected with ‘End to End Ref tag Check Error’. Using ILBRT/EILBRT=SLBA and PRCHK=0x5 is standard for PI2 Reads and Writes in Ubuntu (so making it no different to PI1); but if Ubuntu wants to use these values to successfully read data following a Write Zeroes command, the Write Zeroes command should either: a) set the PRACT bit, causing the controller to generate PI data in accordance with the PI mode*; or b) set the DEAC bit, causing the controller to generate standard Deallocated PI data** (all FFs) thus disabling all checks on the next Read via the AppTag/RefTag=0x rule. Relevant NVMe 1.4 text: * “If the Protection Information Action bit (PRACT) is cleared to ‘0’, then the protection information for this command shall be all zeroes. If the Protection Information Action bit (PRACT) is set to ‘1’, then the protection information shall be based on the End-to-end Data Protection Type Settings (DPS) field in the Identify Namespace data structure and the CDW14.ILBRT, CDW15. LBATM, and CDW15. LBAT fields in the Write Zeroes command. “ ** “If the Deallocate bit is cleared to ‘0’ in a Write Zeroes command… [the controller] shall return the protection information in that logical block based on CDW12.PRINFO in that Write Zeroes command. If the Deallocate bit (CDW12.DEAC) is set to ‘1’ in a Write Zeroes command… [the controller] shall return the protection information in that logical block as specified in section 6.7.1.1 [DSM]” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1947757/+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 1947757] [NEW] NVMe Write Zeroes command has incorrect values for PI modes
You have been subscribed to a public bug: The attached screenshot of a PCIe trace snippet is from Ubuntu 20.04.3 LTS, k5.4.0-73-generic, with an NVMe controller formatted to 4K+8 DIX PI2 It shows - A Single-sector Write Zeroes command with SLBA=0x02E18439, ILBRT=0x0 (valid for PI2), PRCHK=0x0 (no checks), PRACT=0 *, DEAC=0 **. Command succeeds. - A Single-sector Read command with SLBA=0x02E18439, EILBRT=0x02E18439, PRCHK=0x5. Command rejected with ‘End to End Ref tag Check Error’. Using ILBRT/EILBRT=SLBA and PRCHK=0x5 is standard for PI2 Reads and Writes in Ubuntu (so making it no different to PI1); but if Ubuntu wants to use these values to successfully read data following a Write Zeroes command, the Write Zeroes command should either: a) set the PRACT bit, causing the controller to generate PI data in accordance with the PI mode*; or b) set the DEAC bit, causing the controller to generate standard Deallocated PI data** (all FFs) thus disabling all checks on the next Read via the AppTag/RefTag=0x rule. Relevant NVMe 1.4 text: * “If the Protection Information Action bit (PRACT) is cleared to ‘0’, then the protection information for this command shall be all zeroes. If the Protection Information Action bit (PRACT) is set to ‘1’, then the protection information shall be based on the End-to-end Data Protection Type Settings (DPS) field in the Identify Namespace data structure and the CDW14.ILBRT, CDW15. LBATM, and CDW15. LBAT fields in the Write Zeroes command. “ ** “If the Deallocate bit is cleared to ‘0’ in a Write Zeroes command… [the controller] shall return the protection information in that logical block based on CDW12.PRINFO in that Write Zeroes command. If the Deallocate bit (CDW12.DEAC) is set to ‘1’ in a Write Zeroes command… [the controller] shall return the protection information in that logical block as specified in section 6.7.1.1 [DSM]” ** Affects: linux-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment nvme -- NVMe Write Zeroes command has incorrect values for PI modes https://bugs.launchpad.net/bugs/1947757 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 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 1947453] Re: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13
issue still reproduced with latest proposed kernel update (5.13.0-20.20) -- 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/1947453 Title: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13 Status in linux package in Ubuntu: Confirmed Bug description: After upgrade from ubuntu 21.04 to ubuntu 21.10 I am seeing black screen in wayland session and screen corruption in Xorg session ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 15:49:45 2021 DistUpgraded: 2021-10-16 08:19:20,349 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] [1043:1b70] InstallationDate: Installed on 2020-11-20 (329 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro iommu=soft quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 2026 F pulseaudio /dev/snd/controlC0: eugene 2026 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-11-20 (329 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 Tags: impish wayland-session Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis
[Kernel-packages] [Bug 1946686] Re: Fix zfs_get_data access to files with wrong generation causing panics
Inspecting the source code of zfs-linux for Impish and the patch uploaded for Hirsute it looks to me like this is already fixed in Impish so I'm setting this to Fix Released. ** Changed in: zfs-linux (Ubuntu Impish) Status: In Progress => Fix Released -- 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/1946686 Title: Fix zfs_get_data access to files with wrong generation causing panics Status in zfs-linux package in Ubuntu: In Progress Status in zfs-linux source package in Focal: In Progress Status in zfs-linux source package in Hirsute: Fix Committed Status in zfs-linux source package in Impish: Fix Released Bug description: == SRU Focal/Hirsute == [Impact] ZFS: Fix a panic while acquiring a lock. If TX_WRITE is create on a file, and the file is later deleted and a new directory is created on the same object id, it is possible that when zil_commit happens, zfs_get_data will be called on the new directory. This may result in panic as it tries to do range lock. Upstream ZFS bug #10593, #11682, upstream fix: commit 296a4a369bc1078a694f88570972330985b3b1b8 Author: Chunwei Chen Date: Fri Mar 19 22:53:31 2021 -0700 Fix zfs_get_data access to files with wrong generation This patch fixes this issue by record the generation number during zfs_log_write, so zfs_get_data can check if the object is valid. The fix is already in Ubuntu ZFS 2.0.6 in Impish. The fix is a relatively simple backport with only minor backporting effort required in moving some of the module specific upstream changes into the pre- renamed module specific os specific parts of the ZFS module. [Test Plan] This is difficult to reproduce, see https://github.com/openzfs/zfs/issues/10593 The fix has been tested with the complete ubuntu autotest ZFS regression tests that exercise ZFS core functionality (smoke tests), file system POSIX compliance (fs tests), extra XFS tests and every mount option with stress-ng file I/O stress tests. [Where problems could occur] This fix could regress the ZIL (ZFS intent log) commit writes since it modifies this code to now checks for generation numbers. Testing with ZFS autotests with intent logs have not found any regressions, but there is a risk that the ZIL functionality is affected. This could lead to corruption. -- As mentioned at https://answers.launchpad.net/ubuntu/+source/zfs- linux/+question/696659, the following pull request fixes a panic acquiring a lock: https://github.com/openzfs/zfs/pull/11682 This fix does not appear to be a part of the latest Ubuntu 20.04 release: zfsutils-linux: Installed: 0.8.3-1ubuntu12.12 Candidate: 0.8.3-1ubuntu12.12 Version table: *** 0.8.3-1ubuntu12.12 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12.9 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 0.8.3-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Of note is this issue where the bug is reported against the Ubuntu 0.8.3 packages: https://github.com/openzfs/zfs/issues/10642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1946686/+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 1946686] Re: Fix zfs_get_data access to files with wrong generation causing panics
Hello Andrew, or anyone else affected, Accepted zfs-linux into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/2.0.2-1ubuntu5.4 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: zfs-linux (Ubuntu Hirsute) 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/1946686 Title: Fix zfs_get_data access to files with wrong generation causing panics Status in zfs-linux package in Ubuntu: In Progress Status in zfs-linux source package in Focal: In Progress Status in zfs-linux source package in Hirsute: Fix Committed Status in zfs-linux source package in Impish: Fix Released Bug description: == SRU Focal/Hirsute == [Impact] ZFS: Fix a panic while acquiring a lock. If TX_WRITE is create on a file, and the file is later deleted and a new directory is created on the same object id, it is possible that when zil_commit happens, zfs_get_data will be called on the new directory. This may result in panic as it tries to do range lock. Upstream ZFS bug #10593, #11682, upstream fix: commit 296a4a369bc1078a694f88570972330985b3b1b8 Author: Chunwei Chen Date: Fri Mar 19 22:53:31 2021 -0700 Fix zfs_get_data access to files with wrong generation This patch fixes this issue by record the generation number during zfs_log_write, so zfs_get_data can check if the object is valid. The fix is already in Ubuntu ZFS 2.0.6 in Impish. The fix is a relatively simple backport with only minor backporting effort required in moving some of the module specific upstream changes into the pre- renamed module specific os specific parts of the ZFS module. [Test Plan] This is difficult to reproduce, see https://github.com/openzfs/zfs/issues/10593 The fix has been tested with the complete ubuntu autotest ZFS regression tests that exercise ZFS core functionality (smoke tests), file system POSIX compliance (fs tests), extra XFS tests and every mount option with stress-ng file I/O stress tests. [Where problems could occur] This fix could regress the ZIL (ZFS intent log) commit writes since it modifies this code to now checks for generation numbers. Testing with ZFS autotests with intent logs have not found any regressions, but there is a risk that the ZIL functionality is affected. This could lead to corruption. -- As mentioned at https://answers.launchpad.net/ubuntu/+source/zfs- linux/+question/696659, the following pull request fixes a panic acquiring a lock: https://github.com/openzfs/zfs/pull/11682 This fix does not appear to be a part of the latest Ubuntu 20.04 release: zfsutils-linux: Installed: 0.8.3-1ubuntu12.12 Candidate: 0.8.3-1ubuntu12.12 Version table: *** 0.8.3-1ubuntu12.12 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12.9 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 0.8.3-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Of note is this issue where the bug is reported against the Ubuntu 0.8.3 packages: https://github.com/openzfs/zfs/issues/10642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1946686/+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 1947708] Re: Cannot configure suspend-then-hibernate
Indeed, disabling secure boot fixes the problem. As far as I am concerned, this workaround is find with me. Thanks for your help Dan. -- 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/1947708 Title: Cannot configure suspend-then-hibernate Status in linux package in Ubuntu: Confirmed Bug description: Previous bug 1947617 was closed because my swap space was insufficient. Swap was increased to 24G and the problem remains. Configuring login to suspend-then-hiberrnate when the lid is off and configuring sleep so that hibernate happens 10 seconds after suspend, when trying to test with: sudo systemctl suspend-then-hibernate I get: Failed to suspend system, hibernate later via logind: Sleep verb "suspend-then-hibernate" not supported This could be a security vulnerability. If the user expects the system to suspend (and then lock) when the lid is off and it does not work, somebody could then just reopen the lid and get access. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu8 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: i3 Date: Tue Oct 19 11:51:50 2021 InstallationDate: Installed on 2021-10-14 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP ENVY x360 Convertible 13-ay0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=e85d08c2-ae82-4f0f-a625-a5012616c934 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 15.20 dmi.bios.vendor: Insyde dmi.bios.version: F.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 876E dmi.board.vendor: HP dmi.board.version: 12.52 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 12.52 dmi.modalias: dmi:bvnInsyde:bvrF.20:bd07/30/2021:br15.20:efr12.52:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:sku3V693EA#ABF:rvnHP:rn876E:rvr12.52:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx dmi.product.sku: 3V693EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.systemd.logind.conf: 2021-10-18T18:51:43.976989 mtime.conffile..etc.systemd.sleep.conf: 2021-10-18T18:52:04.283409 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947708/+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 1913442] Re: [Ubuntu 20.04] Problem leading IUCV service down (on s390x)
Hi Karsten, no, nothing needed on top. It's in status "Fix Committed", hence it's already available from the -proposed pocket of the Ubuntu archive, and will be migrated to -release with the next kernel update (which is a matter of days). (What I just didn't understood was https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913442/comments/18 maybe this was an accident ...) -- 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/1913442 Title: [Ubuntu 20.04] Problem leading IUCV service down (on s390x) Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: SRU Justification: == [Impact] * Problems occur in IBM z/VM's IUCV (Inter User Communication Vehicle) environments and its communication. * Errors like "usercopy: Kernel memory overwrite attempt detected to SLUB object 'dma-kmalloc-1 k' (offset 0, size 11)!" pop up and cause failures. * This is because IUCV uses kmalloc() with __GFP_DMA because of memory address restrictions. * The solution is to mark dma-kmalloc caches as usercopy caches. [Fix] * 49f2d2419d60a103752e5fbaf158cf8d07c0d884 49f2d2419d60 "usercopy: mark dma-kmalloc caches as usercopy caches" * Due to changes in the context of the upstream patch, a cherry-pick was not possible and the following backport was created: https://bugs.launchpad.net/bugs/1913442/+attachment/5457885/+files/commit_49f2d2419d60_backport.patch [Test Case] * Setup Ubuntu Server 20.04 on s390x system as IBM z/VM guest aka virtual machine. * Setup IUCV on z/VM: Setting up the (IUCV TCPIP) service machine: https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_t_iucv_tcpservice.html * Set up a Linux IUCV instance: https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_t_iucv_scen1_guest.html * Set up an IUCV direct: https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_c_iucv_connect.html * Make use of IUCV, for example using ssh on a direct connection. * Verify if the connections is stable and watch out for messages starting with "usercopy". [Regression Potential] * Problems could occur in case the create_kmalloc_cache call is done wrong, for example with wrong index, wrong size or just wrong comma separations. * Wrong size or index will probably lead to similar instability problems that exist today. * Problems in the syntax (commas etc.) will be detected at compile time. * But it's just a single line modification in function create_kmalloc_caches of /mm/slab_common.c, * so the change is very limited and quite traceable. * And it was in depth discussed here: https://lore.kernel.org/kernel-hardening/1515636190-24061-2-git-send-email-keesc...@chromium.org/ * a reviewed by a lot of kernel engineers (see provenance) * and it was already upstream accepted with kernel 5.8. [Other] * Since the commit is upstream accepted with 5.8, so it's already in impish and hirsute (and groovy). * Hence this kernel SRU submission is for Focal only and covers only the above single but common code commit/patch. __ When I deployed a Ubuntu20.04 instance with kernel version of 5.4.0-58-generic under z/VM, I saw below messages from kernel and the iucvserv program malfunctioned. Hence it caused some devices like network device configuration failure and deployment failure. Dec 14 22:02:26 ub2004img iucvserv: Receive OPNCLD4 0.0.0.1 pwd sent from IUCV client. Dec 14 22:02:26 ub2004img iucvserv: /etc/iucv_authorized_userid exists, check authorization. Dec 14 22:02:26 ub2004img iucvserv: senduserid=OPNCLD4, authuserid=OPNCLD4, len=7 Dec 14 22:02:26 ub2004img iucvserv: Current version is 0.0.0.1, upgraded version is 0.0.0.1 Dec 14 22:02:26 ub2004img iucvserv: Will execute the linux command pwd 2>&1; echo iucvcmdrc=$? sent from IUCV client. Dec 14 22:02:26 ub2004img iucvserv: result length=14, send message length=14,#012 /#012iucvcmdrc=0 Dec 14 22:02:26 ub2004img kernel: [63084.184649] [ cut here ] Dec 14 22:02:26 ub2004img kernel: [63084.184654] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'dma-kmalloc-1k' (offset 0, size 20)! Dec 14 22:02:26 ub2004img kernel: [63084.184680] WARNING: CPU: 1 PID: 697 at mm/usercopy.c:75 usercopy_warn+0xa0/0xd0 Dec 14 22:02:26 ub2004img kernel: [63084.184681] Modules linked in: tcp_diag udp_diag raw_diag inet_diag unix_diag xt_CT iptable_raw ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_conntrack nf_conntrack nf_defr ag_ipv6 nf_defrag_ipv4
[Kernel-packages] [Bug 1922955] Re: Screen artifacts on recent amd gpu with kernel > 5.11.0-11
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1922955 Title: Screen artifacts on recent amd gpu with kernel > 5.11.0-11 Status in linux package in Ubuntu: Fix Released Bug description: This is my first time filing a bug report, so apologies in advance for any mistakes and please feel free to point me in the right direction. I'm posting this for the kernel package because the problem is reliably eliminated by downgrading to 5.11.0-11 and reliably returns by upgrading to any greater version. I've been testing Hirsute as my daily driver for a couple of weeks on my PC with one of the recent AMD GPU's (6700XT). Everything was running flawlessly until the kernel upgrade from 5.11.0-11 to 5.11.0-13. After the upgrade I had a lot of artifacts (flashing squares of either the background or random colors) on the screen. Example picture attached. * I suspect it's only in parts that are being hardware-accelerated. Turning off hardware acceleration in chrome, eliminated them in the content part of the browser, but the windows title bar continues to be affected. * The gnome panels and application menu also have random square artifacts appearing and disappearing. * The issue exists both in X11 and Wayland sessions. * I see nothing out of the ordinary in dmesg or journalctl -r. * Downgrading to kernel 5.11.0-11 eliminates the issue. * I tried installing the latest mainline kernel (5.12-rc6), the issue returned, so I downgraded to 5.11.0-11 again (which fixed it). * To see if other packages I installed may be causing the issue, I did a clean install of the latest daily iso (20210407) and can confirm the issue is also in there. I'm happy to provide more information or testing. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-13-generic 5.11.0-13.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rob1654 F pulseaudio /dev/snd/controlC1: rob1654 F pulseaudio /dev/snd/controlC0: rob1654 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 7 20:48:15 2021 InstallationDate: Installed on 2021-04-07 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210407) MachineType: Micro-Star International Co., Ltd. MS-7C84 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=66ca562a-996d-408a-a49b-6225bfb86cb6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.196 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/01/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.61 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG X570 TOMAHAWK WIFI (MS-7C84) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.61:bd03/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570TOMAHAWKWIFI(MS-7C84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C84 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922955/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed
I'm on Hirsute and zfs -V reports: zfs-2.0.2-1ubuntu5.3 zfs-kmod-2.0.2-1ubuntu5.1 I'm guessing it's the zfs-kmod version that's important here - is that right? I'm not 100% sure from reading https://bugs.launchpad.net/ubuntu/+source/zfs- linux/+bug/1906476/comments/49 which version I need on Hirsute to ensure I don't have the buggy code. Luckily I've seem to have escaped any corruption, perhaps because none of my filesystems are encrypted. I've only ever used the ZFS kernel module binaries from the default hirsute repos for my Pi. Also, were the kernel module binaries for 21.04 from the 'default' repos affected by the bug? I can't tell from the comments above if they were or not. -- 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/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in zfs-linux source package in Impish: Fix Released Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_lookup+0x202/0x3b0 [zfs] zpl_lookup+0xca/0x1e0 [zfs] path_openat+0x6a2/0xfe0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad
[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.11 --- alsa-ucm-conf (1.2.2-1ubuntu0.11) focal; urgency=medium * d/p/0033-HDA-Intel-add-Boost-volume-control-for-Headset-Mic.patch Add Mic Boost in the HDA Intel ucm, after this change, when users adjust input volume, the Mic Boost could be adjusted as well as Capture Volume. (LP: #1930188) -- Hui Wang Tue, 14 Sep 2021 15:11:12 +0800 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. 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. Headp
[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.12 --- pulseaudio (1:13.99.1-1ubuntu3.12) focal; urgency=medium * d/p/0001-alsa-sink-source-set-volume-to-hw-immediately-if-ucm.patch Fix the output volume issue for machines with sof audio driver, if a machine uses sof audio driver, the headphone and speaker will share the output volume from UI, this patch will fix this issue, after applying this patch, the speaker and headphone will have independent volume. (LP: #1930188) -- Hui Wang Mon, 13 Sep 2021 12:11:14 +0800 ** Changed in: pulseaudio (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. 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, i
[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package alsa-ucm-conf - 1.2.4-2ubuntu1.4 --- alsa-ucm-conf (1.2.4-2ubuntu1.4) hirsute; urgency=medium * d/p/0007-HDA-Intel-add-Boost-volume-control-for-Headset-Mic.patch Add Mic Boost in the HDA Intel ucm, after this change, when users adjust input volume, the Mic Boost could be adjusted as well as Capture Volume. (LP: #1930188) -- Hui Wang Tue, 14 Sep 2021 11:08:28 +0800 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. 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. Hea
[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package pulseaudio - 1:14.2-1ubuntu1.2 --- pulseaudio (1:14.2-1ubuntu1.2) hirsute; urgency=medium * d/p/0001-alsa-sink-source-set-volume-to-hw-immediately-if-ucm.patch Fix the output volume issue for machines with sof audio driver, if a machine uses sof audio driver, the headphone and speaker will share the output volume from UI, this patch will fix this issue, after applying this patch, the speaker and headphone will have independent volume. (LP: #1930188) -- Hui Wang Mon, 13 Sep 2021 11:28:16 +0800 ** Changed in: pulseaudio (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. 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, i
[Kernel-packages] [Bug 1930188] Update Released
The verification of the Stable Release Update for pulseaudio has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. 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 wha
[Kernel-packages] [Bug 1939528] Re: Need support of Qualcomm WCN6856
SRU:
* https://lists.ubuntu.com/archives/kernel-team/2021-October/125018.html
(oem-5.14)
* https://lists.ubuntu.com/archives/kernel-team/2021-October/125045.html
(oem-5.13)
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.14 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided => Critical
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-oem-5.14 (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: linux-oem-5.14 (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: Incomplete => In Progress
** Description changed:
[SRU Justification]
[Impact]
- Qualcomm WCN6856 not supported yet.
+ Qualcomm WCN685x is not supported yet.
[Fix]
- Upstream fixes in thread
-
https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/
- has been merged in mainline starting from commit 755b1f73173e ("ath11k:
- add hw reg support for WCN6855").
+ Qualcomm WCN685x support are mostly available in linux-next and mainline
+ with one patch currently in kvalo/ath tree, and 3 additional in review.
[Test Case]
- TBD.
+
+ Test hardware connectivity, stability with basic checkbox tests:
+
+ $ lspci -nnk | grep Network -A 3
+ :02:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev
+ 01)
+ Subsystem: Foxconn International, Inc. Device [105b:e0b8]
+ Kernel driver in use: ath11k_pci
+ Kernel modules: ath11k_pci
[Where problems could occur]
+
While this introduces a new hardware, it might need further polishments.
+
+ [Other Info]
+
+ WCN685x WiFi 6E capability is still under development and is moved to
+ next milestone for oem projects. Firmware blobs for both WiFi and
+ Bluetooth are also needed and will be SRUed when a formal release is
+ made.
== original bug report ==
Wireless Driver support: PCI\VEN_17CB&DEV_1103&SUBSYS_E0B8105B&REV_01
BT driver support: USB\VID_0489&PID_E0C9&REV_0001
Wireless Driver support: PCI\VEN_17CB&DEV_1103&REV_01
BT driver support: USB\VID_0489&PID_E0CC&REV_0001
https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/
Already landed to mainline kernel v5.14-rc1.
--
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/1939528
Title:
Need support of Qualcomm WCN6856
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-firmware package in Ubuntu:
New
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-firmware source package in Focal:
Incomplete
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
In Progress
Status in linux source package in Hirsute:
Won't Fix
Status in linux-firmware source package in Hirsute:
New
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Incomplete
Status in linux-firmware source package in Impish:
New
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Qualcomm WCN685x is not supported yet.
[Fix]
Qualcomm WCN685x support are mostly available in linux-next and mainline
with one patch currently in kvalo/ath tree, and 3 additional in review.
[Test Case]
Test hardware connectivity, stability with basic checkbox tests:
$ lspci -nnk | grep Network -A 3
:02:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev
01)
Subsystem: Foxconn International, Inc. Device [105b:e0b8]
Kernel driver in use: ath11k_pci
Kernel modules: ath11k_pci
[Where problems could occur]
While this introduces a new hardware, it might need further
polishments.
[Other Info]
WCN685x WiFi 6E capability is still under development and is moved to
next milestone for oem projects. Firmware blobs for both WiFi and
Bluetooth are also needed and will be SRUed when a formal release is
made.
== original bug report ==
Wireless Driver support: PCI\VEN_17CB&DEV_1103&SUBSYS_E0B8105B&REV_01
BT driver support: USB\VID_0489&PID_E0C9&REV_0001
Wireless Driver support: PCI\VEN_17CB&DEV_1103&REV_01
BT driver support: USB\VID_0489&PID_E0CC&REV_0001
https://lore.kernel.org/linux-wireless/20210511162214
[Kernel-packages] [Bug 1943902] Re: NVME errors in confidential vms
This bug was fixed in the package linux-gcp-5.4 - 5.4.0-1055.59~18.04.1 --- linux-gcp-5.4 (5.4.0-1055.59~18.04.1) bionic; urgency=medium * bionic/linux-gcp-5.4: 5.4.0-1055.59~18.04.1 -proposed tracker (LP: #1947075) [ Ubuntu: 5.4.0-1055.59 ] * focal/linux-gcp: 5.4.0-1055.59 -proposed tracker (LP: #1947072) * NVME errors in confidential vms (LP: #1943902) - swiotlb: remove the tbl_dma_addr argument to swiotlb_tbl_map_single - driver core: add a min_align_mask field to struct device_dma_parameters - swiotlb: add a IO_TLB_SIZE define - swiotlb: factor out an io_tlb_offset helper - swiotlb: factor out a nr_slots helper - swiotlb: clean up swiotlb_tbl_unmap_single - swiotlb: refactor swiotlb_tbl_map_single - swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single - swiotlb: respect min_align_mask - nvme-pci: set min_align_mask - swiotlb: move orig addr and size validation into swiotlb_bounce - swiotlb: Fix the type of index - swiotlb: manipulate orig_addr when tlb_addr has offset -- Khalid Elmously Thu, 14 Oct 2021 03:47:52 -0400 ** Changed in: linux-gcp-5.4 (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1943902 Title: NVME errors in confidential vms Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp-5.4 package in Ubuntu: Invalid Status in linux-gcp-5.4 source package in Bionic: Fix Released Status in linux-gcp source package in Focal: Fix Released Bug description: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] Using nvme with swiotlb in confidential VMs can encounter hardware read/write errors. [Fix] The following upstream patches from v5.12 address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional nvme device attached: $ sudo mkfs.xfs -f /dev/nvme2n1 meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, refl ink=0 data = bsize=4096 blocks=524288, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 mkfs.xfs: pwrite failed: Input/output error Note the input/output error The error no longer happens with the fixes applied. [Regression Potential] Low risk as the patches are mostly clean-up and refactor. Regression in swiotlb could cause hardware read/write errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1943902/+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 1944600] Re: Bionic update: upstream stable patchset 2021-09-22
This bug was fixed in the package linux - 4.15.0-161.169
---
linux (4.15.0-161.169) bionic; urgency=medium
* bionic/linux: 4.15.0-161.169 -proposed tracker (LP: #1947358)
* Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on
r5.metal (LP: #1946149)
- SAUCE: Revert "PCI/MSI: Enforce MSI[X] entry updates to be visible"
- SAUCE: Revert "PCI/MSI: Enforce that MSI-X table entry is masked for
update"
linux (4.15.0-160.168) bionic; urgency=medium
* bionic/linux: 4.15.0-160.168 -proposed tracker (LP: #1944933)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.09.27)
* ext4 journal recovery fails w/ data=journal + mmap (LP: #1847340)
- jbd2: introduce/export functions
jbd2_journal_submit|finish_inode_data_buffers()
- jbd2, ext4, ocfs2: introduce/use journal callbacks
j_submit|finish_inode_data_buffers()
- ext4: data=journal: fixes for ext4_page_mkwrite()
- ext4: data=journal: write-protect pages on j_submit_inode_data_buffers()
- ext4: fix mmap write protection for data=journal mode
* CVE-2021-40490
- ext4: fix race writing to an inline_data file while its xattrs are
changing
* Bionic update: upstream stable patchset 2021-09-22 (LP: #1944600)
- iio: humidity: hdc100x: Add margin to the conversion time
- iio: adc: Fix incorrect exit of for-loop
- ASoC: intel: atom: Fix reference to PCM buffer address
- i2c: dev: zero out array used for i2c reads from userspace
- ACPI: NFIT: Fix support for virtual SPA ranges
- ASoC: cs42l42: Correct definition of ADC Volume control
- ASoC: cs42l42: Don't allow SND_SOC_DAIFMT_LEFT_J
- ASoC: cs42l42: Fix inversion of ADC Notch Switch control
- ASoC: cs42l42: Remove duplicate control for WNF filter frequency
- net: dsa: mt7530: add the missing RxUnicast MIB counter
- ppp: Fix generating ifname when empty IFLA_IFNAME is specified
- psample: Add a fwd declaration for skbuff
- net: Fix memory leak in ieee802154_raw_deliver
- net: bridge: fix memleak in br_add_if()
- tcp_bbr: fix u32 wrap bug in round logic if bbr_init() called after 2B
packets
- xen/events: Fix race in set_evtchn_to_irq
- vsock/virtio: avoid potential deadlock when vsock device remove
- powerpc/kprobes: Fix kprobe Oops happens in booke
- x86/tools: Fix objdump version check again
- x86/resctrl: Fix default monitoring groups reporting
- PCI/MSI: Enable and mask MSI-X early
- PCI/MSI: Do not set invalid bits in MSI mask
- PCI/MSI: Correct misleading comments
- PCI/MSI: Use msi_mask_irq() in pci_msi_shutdown()
- PCI/MSI: Protect msi_desc::masked for multi-MSI
- PCI/MSI: Mask all unused MSI-X entries
- PCI/MSI: Enforce that MSI-X table entry is masked for update
- PCI/MSI: Enforce MSI[X] entry updates to be visible
- vmlinux.lds.h: Handle clang's module.{c,d}tor sections
- mac80211: drop data frames without key on encrypted links
- x86/fpu: Make init_fpstate correct with optimized XSAVE
- ath: Use safer key clearing with key cache entries
- ath9k: Clear key cache explicitly on disabling hardware
- ath: Export ath_hw_keysetmac()
- ath: Modify ath_key_delete() to not need full key entry
- ath9k: Postpone key cache entry deletion for TXQ frames reference it
- dmaengine: usb-dmac: Fix PM reference leak in usb_dmac_probe()
- ARM: dts: am43x-epos-evm: Reduce i2c0 bus speed for tps65218
- dmaengine: of-dma: router_xlate to return -EPROBE_DEFER if controller is
not
yet available
- scsi: megaraid_mm: Fix end of loop tests for list_for_each_entry()
- scsi: scsi_dh_rdac: Avoid crash during rdac_bus_attach()
- scsi: core: Avoid printing an error if target_alloc() returns -ENXIO
- ARM: dts: nomadik: Fix up interrupt controller node names
- net: usb: lan78xx: don't modify phy_device state concurrently
- Bluetooth: hidp: use correct wait queue when removing ctrl_wait
- dccp: add do-while-0 stubs for dccp_pr_debug macros
- vhost: Fix the calculation in vhost_overflow()
- bnxt: don't lock the tx queue from napi poll
- net: 6pack: fix slab-out-of-bounds in decode_data
- ptp_pch: Restore dependency on PCI
- net: qlcnic: add missed unlock in qlcnic_83xx_flash_read32
- net: mdio-mux: Don't ignore memory allocation errors
- net: mdio-mux: Handle -EPROBE_DEFER correctly
- mmc: dw_mmc: Fix hang on data CRC error
- ALSA: hda - fix the 'Capture Switch' value change notifications
- ipack: tpci200: fix many double free issues in tpci200_pci_probe
- btrfs: prevent rename2 from exchanging a subvol with a directory from
different parents
- ASoC: intel: atom: Fix breakage for PCM buffer address setup
- locks: print a warning when mount fails due to lack of "mand" support
- fs: warn about impending deprecation of mandatory locks
- netfilter: nft_
[Kernel-packages] [Bug 1944754] Re: linux-tools-aws package does not contain libperf-jvmti.so
This bug was fixed in the package linux-aws - 4.15.0-1114.121 --- linux-aws (4.15.0-1114.121) bionic; urgency=medium * bionic/linux-aws: 4.15.0-1114.121 -proposed tracker (LP: #1947356) [ Ubuntu: 4.15.0-161.169 ] * bionic/linux: 4.15.0-161.169 -proposed tracker (LP: #1947358) * Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal (LP: #1946149) - SAUCE: Revert "PCI/MSI: Enforce MSI[X] entry updates to be visible" - SAUCE: Revert "PCI/MSI: Enforce that MSI-X table entry is masked for update" -- Ian May Fri, 15 Oct 2021 14:11:04 -0500 ** Changed in: linux-aws (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1944754 Title: linux-tools-aws package does not contain libperf-jvmti.so Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux-aws source package in Focal: Fix Committed Status in linux-aws source package in Hirsute: Fix Released Status in linux-aws source package in Impish: Fix Released Bug description: SRU Justification [Impact] For debugging purposes, on EC2, people will install linux-tools-$(uname -r) to help with debugging the system. This selects the kernel specific linux-tools package, and for the AWS variant, we are missing the library libperf-jvmti.so to enable tracing Java applications with perf. To get a libperf-jvmti.so library, we need to perform an additional and confusing step by installing linux-tools-generic to get a copy of the library. Customers on AWS EC2 should not have to do this. We would like the linux-tools-aws packages to contain libperf-jvmti.so. [Test Plan] Install linux-tools-aws, check for libperf-jvmti.so [Where problems could occur] Given that linux-tools-aws installs in a versioned (unique) directory, there should be no conflicts or possibility of regression. [Additional info] SF: #00319833 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1944754/+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 1847340] Re: ext4 journal recovery fails w/ data=journal + mmap
This bug was fixed in the package linux - 4.15.0-161.169
---
linux (4.15.0-161.169) bionic; urgency=medium
* bionic/linux: 4.15.0-161.169 -proposed tracker (LP: #1947358)
* Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on
r5.metal (LP: #1946149)
- SAUCE: Revert "PCI/MSI: Enforce MSI[X] entry updates to be visible"
- SAUCE: Revert "PCI/MSI: Enforce that MSI-X table entry is masked for
update"
linux (4.15.0-160.168) bionic; urgency=medium
* bionic/linux: 4.15.0-160.168 -proposed tracker (LP: #1944933)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.09.27)
* ext4 journal recovery fails w/ data=journal + mmap (LP: #1847340)
- jbd2: introduce/export functions
jbd2_journal_submit|finish_inode_data_buffers()
- jbd2, ext4, ocfs2: introduce/use journal callbacks
j_submit|finish_inode_data_buffers()
- ext4: data=journal: fixes for ext4_page_mkwrite()
- ext4: data=journal: write-protect pages on j_submit_inode_data_buffers()
- ext4: fix mmap write protection for data=journal mode
* CVE-2021-40490
- ext4: fix race writing to an inline_data file while its xattrs are
changing
* Bionic update: upstream stable patchset 2021-09-22 (LP: #1944600)
- iio: humidity: hdc100x: Add margin to the conversion time
- iio: adc: Fix incorrect exit of for-loop
- ASoC: intel: atom: Fix reference to PCM buffer address
- i2c: dev: zero out array used for i2c reads from userspace
- ACPI: NFIT: Fix support for virtual SPA ranges
- ASoC: cs42l42: Correct definition of ADC Volume control
- ASoC: cs42l42: Don't allow SND_SOC_DAIFMT_LEFT_J
- ASoC: cs42l42: Fix inversion of ADC Notch Switch control
- ASoC: cs42l42: Remove duplicate control for WNF filter frequency
- net: dsa: mt7530: add the missing RxUnicast MIB counter
- ppp: Fix generating ifname when empty IFLA_IFNAME is specified
- psample: Add a fwd declaration for skbuff
- net: Fix memory leak in ieee802154_raw_deliver
- net: bridge: fix memleak in br_add_if()
- tcp_bbr: fix u32 wrap bug in round logic if bbr_init() called after 2B
packets
- xen/events: Fix race in set_evtchn_to_irq
- vsock/virtio: avoid potential deadlock when vsock device remove
- powerpc/kprobes: Fix kprobe Oops happens in booke
- x86/tools: Fix objdump version check again
- x86/resctrl: Fix default monitoring groups reporting
- PCI/MSI: Enable and mask MSI-X early
- PCI/MSI: Do not set invalid bits in MSI mask
- PCI/MSI: Correct misleading comments
- PCI/MSI: Use msi_mask_irq() in pci_msi_shutdown()
- PCI/MSI: Protect msi_desc::masked for multi-MSI
- PCI/MSI: Mask all unused MSI-X entries
- PCI/MSI: Enforce that MSI-X table entry is masked for update
- PCI/MSI: Enforce MSI[X] entry updates to be visible
- vmlinux.lds.h: Handle clang's module.{c,d}tor sections
- mac80211: drop data frames without key on encrypted links
- x86/fpu: Make init_fpstate correct with optimized XSAVE
- ath: Use safer key clearing with key cache entries
- ath9k: Clear key cache explicitly on disabling hardware
- ath: Export ath_hw_keysetmac()
- ath: Modify ath_key_delete() to not need full key entry
- ath9k: Postpone key cache entry deletion for TXQ frames reference it
- dmaengine: usb-dmac: Fix PM reference leak in usb_dmac_probe()
- ARM: dts: am43x-epos-evm: Reduce i2c0 bus speed for tps65218
- dmaengine: of-dma: router_xlate to return -EPROBE_DEFER if controller is
not
yet available
- scsi: megaraid_mm: Fix end of loop tests for list_for_each_entry()
- scsi: scsi_dh_rdac: Avoid crash during rdac_bus_attach()
- scsi: core: Avoid printing an error if target_alloc() returns -ENXIO
- ARM: dts: nomadik: Fix up interrupt controller node names
- net: usb: lan78xx: don't modify phy_device state concurrently
- Bluetooth: hidp: use correct wait queue when removing ctrl_wait
- dccp: add do-while-0 stubs for dccp_pr_debug macros
- vhost: Fix the calculation in vhost_overflow()
- bnxt: don't lock the tx queue from napi poll
- net: 6pack: fix slab-out-of-bounds in decode_data
- ptp_pch: Restore dependency on PCI
- net: qlcnic: add missed unlock in qlcnic_83xx_flash_read32
- net: mdio-mux: Don't ignore memory allocation errors
- net: mdio-mux: Handle -EPROBE_DEFER correctly
- mmc: dw_mmc: Fix hang on data CRC error
- ALSA: hda - fix the 'Capture Switch' value change notifications
- ipack: tpci200: fix many double free issues in tpci200_pci_probe
- btrfs: prevent rename2 from exchanging a subvol with a directory from
different parents
- ASoC: intel: atom: Fix breakage for PCM buffer address setup
- locks: print a warning when mount fails due to lack of "mand" support
- fs: warn about impending deprecation of mandatory locks
- netfilter: nft_
[Kernel-packages] [Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
This bug was fixed in the package linux - 4.15.0-161.169
---
linux (4.15.0-161.169) bionic; urgency=medium
* bionic/linux: 4.15.0-161.169 -proposed tracker (LP: #1947358)
* Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on
r5.metal (LP: #1946149)
- SAUCE: Revert "PCI/MSI: Enforce MSI[X] entry updates to be visible"
- SAUCE: Revert "PCI/MSI: Enforce that MSI-X table entry is masked for
update"
linux (4.15.0-160.168) bionic; urgency=medium
* bionic/linux: 4.15.0-160.168 -proposed tracker (LP: #1944933)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.09.27)
* ext4 journal recovery fails w/ data=journal + mmap (LP: #1847340)
- jbd2: introduce/export functions
jbd2_journal_submit|finish_inode_data_buffers()
- jbd2, ext4, ocfs2: introduce/use journal callbacks
j_submit|finish_inode_data_buffers()
- ext4: data=journal: fixes for ext4_page_mkwrite()
- ext4: data=journal: write-protect pages on j_submit_inode_data_buffers()
- ext4: fix mmap write protection for data=journal mode
* CVE-2021-40490
- ext4: fix race writing to an inline_data file while its xattrs are
changing
* Bionic update: upstream stable patchset 2021-09-22 (LP: #1944600)
- iio: humidity: hdc100x: Add margin to the conversion time
- iio: adc: Fix incorrect exit of for-loop
- ASoC: intel: atom: Fix reference to PCM buffer address
- i2c: dev: zero out array used for i2c reads from userspace
- ACPI: NFIT: Fix support for virtual SPA ranges
- ASoC: cs42l42: Correct definition of ADC Volume control
- ASoC: cs42l42: Don't allow SND_SOC_DAIFMT_LEFT_J
- ASoC: cs42l42: Fix inversion of ADC Notch Switch control
- ASoC: cs42l42: Remove duplicate control for WNF filter frequency
- net: dsa: mt7530: add the missing RxUnicast MIB counter
- ppp: Fix generating ifname when empty IFLA_IFNAME is specified
- psample: Add a fwd declaration for skbuff
- net: Fix memory leak in ieee802154_raw_deliver
- net: bridge: fix memleak in br_add_if()
- tcp_bbr: fix u32 wrap bug in round logic if bbr_init() called after 2B
packets
- xen/events: Fix race in set_evtchn_to_irq
- vsock/virtio: avoid potential deadlock when vsock device remove
- powerpc/kprobes: Fix kprobe Oops happens in booke
- x86/tools: Fix objdump version check again
- x86/resctrl: Fix default monitoring groups reporting
- PCI/MSI: Enable and mask MSI-X early
- PCI/MSI: Do not set invalid bits in MSI mask
- PCI/MSI: Correct misleading comments
- PCI/MSI: Use msi_mask_irq() in pci_msi_shutdown()
- PCI/MSI: Protect msi_desc::masked for multi-MSI
- PCI/MSI: Mask all unused MSI-X entries
- PCI/MSI: Enforce that MSI-X table entry is masked for update
- PCI/MSI: Enforce MSI[X] entry updates to be visible
- vmlinux.lds.h: Handle clang's module.{c,d}tor sections
- mac80211: drop data frames without key on encrypted links
- x86/fpu: Make init_fpstate correct with optimized XSAVE
- ath: Use safer key clearing with key cache entries
- ath9k: Clear key cache explicitly on disabling hardware
- ath: Export ath_hw_keysetmac()
- ath: Modify ath_key_delete() to not need full key entry
- ath9k: Postpone key cache entry deletion for TXQ frames reference it
- dmaengine: usb-dmac: Fix PM reference leak in usb_dmac_probe()
- ARM: dts: am43x-epos-evm: Reduce i2c0 bus speed for tps65218
- dmaengine: of-dma: router_xlate to return -EPROBE_DEFER if controller is
not
yet available
- scsi: megaraid_mm: Fix end of loop tests for list_for_each_entry()
- scsi: scsi_dh_rdac: Avoid crash during rdac_bus_attach()
- scsi: core: Avoid printing an error if target_alloc() returns -ENXIO
- ARM: dts: nomadik: Fix up interrupt controller node names
- net: usb: lan78xx: don't modify phy_device state concurrently
- Bluetooth: hidp: use correct wait queue when removing ctrl_wait
- dccp: add do-while-0 stubs for dccp_pr_debug macros
- vhost: Fix the calculation in vhost_overflow()
- bnxt: don't lock the tx queue from napi poll
- net: 6pack: fix slab-out-of-bounds in decode_data
- ptp_pch: Restore dependency on PCI
- net: qlcnic: add missed unlock in qlcnic_83xx_flash_read32
- net: mdio-mux: Don't ignore memory allocation errors
- net: mdio-mux: Handle -EPROBE_DEFER correctly
- mmc: dw_mmc: Fix hang on data CRC error
- ALSA: hda - fix the 'Capture Switch' value change notifications
- ipack: tpci200: fix many double free issues in tpci200_pci_probe
- btrfs: prevent rename2 from exchanging a subvol with a directory from
different parents
- ASoC: intel: atom: Fix breakage for PCM buffer address setup
- locks: print a warning when mount fails due to lack of "mand" support
- fs: warn about impending deprecation of mandatory locks
- netfilter: nft_
[Kernel-packages] [Bug 1945043] Re: Impish: problem with bluetooth mouse: not connectable
>From personal experience, coincidentally, it happened to me that Ubuntu Mate >started without customizing the screens and only original GNOME was displayed. >In that case the bluetooth had no problems, the version I was using is the >MATE 20.04.3, with updates. I'm not using Impish at the moment but maybe this situation could be similar for this version too. Bye! -- 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/1945043 Title: Impish: problem with bluetooth mouse: not connectable Status in Ubuntu MATE: New Status in linux package in Ubuntu: Incomplete Bug description: Problem with bluetooth mouse: not connectable I have a bluetooth mouse that I use regularly with Ubuntu Mate 20.04.x I tried the impish version of Ubuntu Mate but, using the same notebook, the computer cannot recognize it, in the bluetooth search, and then connect it. I tested the functionality of the mouse and it works with other devices as well. The brand of the MEMTEQ mouse. I downloaded the Impish Mate version of 09-25-2021 and I made a fresh installation. I also proceeded to update (it only updated Firefox because I believe all other updates were included). Unfortunately the indicated problem has not been solved. With the updated Ubuntu Mate 20.04 LTS it works. I also used another Bluetooth adapter on another PC and the result is the same. Hello. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1945043/+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 1947761] Re: nvidia-dkms-450 450.66-0ubuntu0.20.04.1: nvidia kernel module failed to build
** Package changed: ubuntu => nvidia-graphics-drivers-450 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1947761 Title: nvidia-dkms-450 450.66-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: my computer is brand new and it started hanging on second day of usages and the mouse pad gets frozen and does not work anymore unless i force shutdown and reboot the system. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-450 450.66-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.10.0-1049.51-oem 5.10.52 Uname: Linux 5.10.0-1049-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.10.0-1049-oem Date: Sat Oct 16 14:28:30 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DuplicateSignature: dkms:nvidia-dkms-450:450.66-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/450.66/build/common/inc/nv-mm.h:149:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-01-28 (264 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 PackageVersion: 450.66-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-dkms-450 450.66-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1947761/+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 1947761] [NEW] nvidia-dkms-450 450.66-0ubuntu0.20.04.1: nvidia kernel module failed to build
You have been subscribed to a public bug: my computer is brand new and it started hanging on second day of usages and the mouse pad gets frozen and does not work anymore unless i force shutdown and reboot the system. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-450 450.66-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.10.0-1049.51-oem 5.10.52 Uname: Linux 5.10.0-1049-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.10.0-1049-oem Date: Sat Oct 16 14:28:30 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DuplicateSignature: dkms:nvidia-dkms-450:450.66-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/450.66/build/common/inc/nv-mm.h:149:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-01-28 (264 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 PackageVersion: 450.66-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-dkms-450 450.66-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- nvidia-dkms-450 450.66-0ubuntu0.20.04.1: nvidia kernel module failed to build https://bugs.launchpad.net/bugs/1947761 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 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 1945180] Re: vrf: fix refcnt leak with vxlan slaves
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1945180
Title:
vrf: fix refcnt leak with vxlan slaves
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
There are cases, where deleting a VRF device can hang waiting for the refcnt
to drop to 0, with the message:
unregister_netdevice: waiting for vrf1 to become free. Usage count = 1
This is fixed upstream with commit b87b04f5019e ("ipv4: Fix device
used for dst_alloc with local routes"), included in linux v5.13. The
original patch, which has introduced the bug, is included in linux
v4.10.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b87b04f5019e
[Test Case]
The upstream patch includes a test case, which describe how to
reproduce the bug.
[Regression Potential]
The patch affects ipv4 routing. It is straightforward, it links new
dst to a vrf device instead of the loopback if needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945180/+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
Hello Bijay, or anyone else affected, Accepted alsa-ucm-conf into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.4-2ubuntu5 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- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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. ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Committed Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. 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 f
[Kernel-packages] [Bug 1947557] Re: kernel panic: NULL pointer dereference in wb_timer_f()
** Description changed: + [Impact] + + It is possible to trigger a kernel panic with the latest impish kernel + running systemd autopkgtest using --enable-kvm with the test instances + created by systemd during the autotest. The panic happens in the host, + not in the guest VM executed by systemd. + + [Test case] + + Add --enable-kvm to the options in test/testdata/test-functions + (systemd), run `sudo autopkgtest . -- null`, wait for the panic to + happen. + + [Fix] + + https://lore.kernel.org/lkml/YW6N2qXpBU3oc50q@arighi-desktop/T/#u + + [Regression potential] + + The fix is addressing a race in the block layer (in the buffered write + throttling code - block/blk-wbt.c) between a disk being released and the + timer callback that periodically checks if the latency for a specific + block device has been exceeded. If the fix is not correct we may still + have a race in this code, that can still show potential kernel panics in + the block layer subsystem. + + [Original bug report] + I can trigger the following kernel panic with the latest impish kernel 5.13.0-19-generic, running systemd autopkgtest using --enable-kvm for the instances created by systemd to run the autotest: [ 119.987108] BUG: kernel NULL pointer dereference, address: 0098 [ 119.987617] #PF: supervisor read access in kernel mode [ 119.987971] #PF: error_code(0x) - not-present page - [ 119.988325] PGD 7c4a4067 P4D 7c4a4067 PUD 7bf63067 PMD 0 + [ 119.988325] PGD 7c4a4067 P4D 7c4a4067 PUD 7bf63067 PMD 0 [ 119.988697] Oops: [#1] SMP NOPTI [ 119.988959] CPU: 1 PID: 9353 Comm: cloud-init Not tainted 5.15-rc5+arighi-aws #rc5+arighi [ 119.989520] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 [ 119.990055] RIP: 0010:wb_timer_fn+0x44/0x3c0 [ 119.990376] Code: 41 8b 9c 24 98 00 00 00 41 8b 94 24 b8 00 00 00 41 8b 84 24 d8 00 00 00 4d 8b 74 24 28 01 d3 01 c3 49 8b 44 24 60 48 8b 40 78 <4c> 8b b8 98 00 00 00 4d 85 f6 0f 84 c4 00 00 00 49 83 7c 24 30 00 [ 119.991578] RSP: :b5f580957da8 EFLAGS: 00010246 [ 119.991937] RAX: RBX: RCX: 0004 [ 119.992412] RDX: RSI: RDI: 88f476d7f780 [ 119.992895] RBP: b5f580957dd0 R08: R09: [ 119.993371] R10: 0004 R11: 0002 R12: 88f476c84500 [ 119.993847] R13: 88f4434390c0 R14: R15: 88f4bdc98c00 [ 119.994323] FS: 7fb90bcd9c00() GS:88f4bdc8() knlGS: [ 119.994952] CS: 0010 DS: ES: CR0: 80050033 [ 119.995380] CR2: 0098 CR3: 7c0d6000 CR4: 06e0 [ 119.995906] Call Trace: [ 119.996130] ? blk_stat_free_callback_rcu+0x30/0x30 [ 119.996505] blk_stat_timer_fn+0x138/0x140 [ 119.996830] call_timer_fn+0x2b/0x100 [ 119.997136] __run_timers.part.0+0x1d1/0x240 [ 119.997470] ? kvm_clock_get_cycles+0x11/0x20 [ 119.997826] ? ktime_get+0x3e/0xa0 [ 119.998110] ? native_apic_msr_write+0x2c/0x30 [ 119.998456] ? lapic_next_event+0x20/0x30 [ 119.998779] ? clockevents_program_event+0x94/0xf0 [ 119.999150] run_timer_softirq+0x2a/0x50 [ 119.999465] __do_softirq+0xcb/0x26f [ 119.999764] irq_exit_rcu+0x8c/0xb0 [ 120.57] sysvec_apic_timer_interrupt+0x43/0x90 [ 120.000429] ? asm_sysvec_apic_timer_interrupt+0xa/0x20 [ 120.000836] asm_sysvec_apic_timer_interrupt+0x12/0x20 [ 120.001226] RIP: 0033:0x501969 [ 120.001486] Code: 8d 54 e5 00 4d 8b a2 80 02 00 00 4d 89 ba 88 02 00 00 4d 39 f4 75 0f e9 84 00 00 00 0f 1f 44 00 00 4c 39 f2 74 7a 49 8b 14 24 <4d> 89 e7 49 89 d4 49 81 7f 18 e0 33 8f 00 75 e7 48 85 d2 74 e7 49 [ 120.002793] RSP: 002b:7ffc407d68b0 EFLAGS: 0206 [ 120.003196] RAX: 008eaa20 RBX: 7ffc407d6930 RCX: [ 120.003711] RDX: 00d2d940 RSI: 7fb90b9522c0 RDI: 0001 [ 120.004224] RBP: 7ffc407d6940 R08: 7fb90a53df60 R09: [ 120.004750] R10: 00bc6130 R11: 0006 R12: 00d2dda0 [ 120.005262] R13: 00bc6100 R14: 00bc63b0 R15: 7fb90b4dde30 [ 120.005775] Modules linked in: essiv authenc crypto_simd cryptd dm_crypt scsi_debug isofs nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua kvm_amd ccp input_leds kvm joydev serio_raw sch_fq_codel msr drm ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear xhci_pci virtio_net ahci net_failover psmouse libahci virtio_blk failover xhci_pci_renesas [ 120.008799] CR2: 0098 [ 120.009077] ---[ end trace bfb8226a5f9067bc ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux
[Kernel-packages] [Bug 1947628] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1947628 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: impish -- 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/1947628 Title: VXLAN support is not present in kernel - Ubuntu 21.10 on Raspberry Pi 4 (64bit) Status in linux package in Ubuntu: Incomplete Bug description: Platform Information - Ubuntu 21.10, Linux 5.13.0-1008-raspi #9-Ubuntu SMP PREEMPT Wed Sep 29 08:27:44 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux The latest version of Ubuntu does not have VXLAN support. The following command confirms the same: modprobe vxlan modprobe: FATAL: Module vxlan not found in directory /lib/modules/5.13.0-1008-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947628/+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 1947628] Re: VXLAN support is not present in kernel - Ubuntu 21.10 on Raspberry Pi 4 (64bit)
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947628 Title: VXLAN support is not present in kernel - Ubuntu 21.10 on Raspberry Pi 4 (64bit) Status in linux package in Ubuntu: New Bug description: Platform Information - Ubuntu 21.10, Linux 5.13.0-1008-raspi #9-Ubuntu SMP PREEMPT Wed Sep 29 08:27:44 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux The latest version of Ubuntu does not have VXLAN support. The following command confirms the same: modprobe vxlan modprobe: FATAL: Module vxlan not found in directory /lib/modules/5.13.0-1008-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947628/+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 1947628] [NEW] VXLAN support is not present in kernel - Ubuntu 21.10 on Raspberry Pi 4 (64bit)
You have been subscribed to a public bug: Platform Information - Ubuntu 21.10, Linux 5.13.0-1008-raspi #9-Ubuntu SMP PREEMPT Wed Sep 29 08:27:44 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux The latest version of Ubuntu does not have VXLAN support. The following command confirms the same: modprobe vxlan modprobe: FATAL: Module vxlan not found in directory /lib/modules/5.13.0-1008-raspi ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment kernel-bug -- VXLAN support is not present in kernel - Ubuntu 21.10 on Raspberry Pi 4 (64bit) https://bugs.launchpad.net/bugs/1947628 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
