[Kernel-packages] [Bug 1931665] Re: HP EliteBook 845 G7 (Cezanne) S0iX not available due to the lack of amdgpu firmware for green_sardine
> For the purpose of an SRU to fix the pointed problem, we should only touch the Cezanne firmware (cherry-pick commit 15003b062125921d3b51256af5583c16a955db2b) ** Also affects: linux-firmware (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1931665 Title: HP EliteBook 845 G7 (Cezanne) S0iX not available due to the lack of amdgpu firmware for green_sardine Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Hirsute: New Bug description: OS: Ubuntu 20.04.2 Linux kernel: 5.10.0-1027-oem Linux firmware: 1.187.12 Device: HP EliteBook 845 G7 (Cezanne) Even though the soix changes have been merged with 5.10.0-1027-oem, AMD Cezanne amdgpu firmware files are not present in in Ubuntu linux- firmware 1.187.12. With the above packages, resume breaks. No error message in dmesg. If I replace /lib/firmware with contents from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20210511.tar.gz, suspend/resume works. During suspend, LCD backlight, fan & keyboard backlight turns off. After resume, everything is back to normal. No errors regarding AMD GPU. The current Ubuntu linux-firmware package is two months old & there are lots of amdgpu & radeon commits after that. Prefer a generic update to the latest fw package. If its AMD Cezanne specific, the fw file names prefix is "green_sardine". This is a public bug for landing for bug 1929104. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1931665/+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 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
Can you give me the dmesg from boot? I can at least know how the HID do the input mapping. -- 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/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I found that some of the Lenovo Lenovo Essential Wireless Keyboard Fn keys don't work. First one is Mute mic (Fn+F4), second one is Scissors (Fn+F10, probably hotkey for Windows Snipping Tool for selective screenshot).gnome-control-panel, xev and evtest doesn't react on pressing these buttons. Here what I was able to get via sudo cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"' : For Mute key 00 00 00 FF DC 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 For Scissors 00 00 00 FF DB 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asudak 2085 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 6 22:36:50 2021 InstallationDate: Installed on 2021-04-13 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-18 (17 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+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 1929444] Re: SD card initialization on insertion fails
https://lkml.org/lkml/2021/6/7/416 is accepted upstream. I'll backport it when it's in linux-next. -- 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/1929444 Title: SD card initialization on insertion fails Status in linux package in Ubuntu: Triaged Status in linux source package in Hirsute: Triaged Status in linux source package in Impish: Triaged Bug description: If I boot my laptop with an SD card (actually SDXC) in the MMC slot the system sees it and I can mount and use it. If I then unmount it, remove it then re-insert it I get this in the system ,og: [ 194.673108] mmc0: card e624 removed [ 205.462065] mmc0: cannot verify signal voltage switch [ 205.567479] mmc0: error -84 whilst initialising SD card and the card cannot then be used. It was OK in groovy. It's failing in hirsute. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.17.18 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gml44104153 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon May 24 17:36:49 2021 HibernationDevice: RESUME=UUID=03dec042-8ba2-48a8-8d19-373ca2e0829c InstallationDate: Installed on 2020-08-13 (284 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: PC Specialist LTD N150CU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=b21720c3-60bf-4298-9d73-743672f89216 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-17-generic N/A linux-backports-modules-5.11.0-17-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-13 (11 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+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 1931665] Re: HP EliteBook 845 G7 (Cezanne) S0iX not available due to the lack of amdgpu firmware for green_sardine
** Changed in: linux-firmware (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Hirsute) 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/1931665 Title: HP EliteBook 845 G7 (Cezanne) S0iX not available due to the lack of amdgpu firmware for green_sardine Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: In Progress Status in linux-firmware source package in Hirsute: In Progress Bug description: OS: Ubuntu 20.04.2 Linux kernel: 5.10.0-1027-oem Linux firmware: 1.187.12 Device: HP EliteBook 845 G7 (Cezanne) Even though the soix changes have been merged with 5.10.0-1027-oem, AMD Cezanne amdgpu firmware files are not present in in Ubuntu linux- firmware 1.187.12. With the above packages, resume breaks. No error message in dmesg. If I replace /lib/firmware with contents from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20210511.tar.gz, suspend/resume works. During suspend, LCD backlight, fan & keyboard backlight turns off. After resume, everything is back to normal. No errors regarding AMD GPU. The current Ubuntu linux-firmware package is two months old & there are lots of amdgpu & radeon commits after that. Prefer a generic update to the latest fw package. If its AMD Cezanne specific, the fw file names prefix is "green_sardine". This is a public bug for landing for bug 1929104. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1931665/+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 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
Performing verification for Groovy. I'm going to do three rounds of verification. The first is the testcase from this bug, showing block discard performance. The second is running through the regression reproducer from bug 1907262. The third will be results from my testing with my /home directory on a cloud instance with Raid10 backed disks, 3x customer testing and 2x community user testing. This will be in a separate comment closer to the release date once I have collected results. Starting with the testcase for this bug. I started a i3.8xlarge instance on AWS, enabled -proposed and installed 5.8.0-56-generic. From there, I ran through the testcase of making a Raid10 array, and formatting it with xfs, and block discard performance was excellent: https://paste.ubuntu.com/p/GGXfjCHfDR/ It took 5.7 seconds to format the array with xfs, and 2.3 seconds for a fstrim, as opposed to the 20 minutes it took beforehand. Performance with block discard is excellent. Moving onto the second testcase, the regression reproducer from bug 1907262. I started a n1-standard-2 VM on Google Cloud, and attached 2x NVMe scratch disks. I enabled -proposed and installed 5.8.0-56-generic. I ran through the testcase of making a Raid10 array, doing consistency checks, ensuring that mismatch count is 0, creating a file, deleting it, performing a fstrim, and more consistency checks, then taking the raid array down and bringing up one disk at a time, and performing a fsck.ext4. All disks came back clean: https://paste.ubuntu.com/p/75xWd4Z3NZ/ Since the block discard performance is there, and there is no apparent data corruption going on after a fstrim, I will mark this verified for Groovy. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- 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/1896578 Title: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.13-rc1. commit cf78408f937a67f59f5e90ee8e6cadeed7c128a8 Author: Xiao Ni Date: Thu Feb 4 15:50:43 2021 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://github.com/torvalds/linux/commit/cf78408f937a67f59f5e90ee8e6cadeed7c128a8 commit c2968285925adb97b9aa4ede94c1f1ab61ce0925 Author: Xiao Ni Date: Thu Feb 4 15:50:44 2021 +0800 Subject: md/raid10: extend r10bio devs to raid disks Link:
[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
Performing verification for Bionic. I'm going to do three rounds of verification. The first is the testcase from this bug, showing block discard performance. The second is running through the regression reproducer from bug 1907262. The third will be results from my testing with my /home directory on a cloud instance with Raid10 backed disks, 3x customer testing and 2x community user testing. This will be in a separate comment closer to the release date once I have collected results. Starting with the testcase for this bug. I started a i3.8xlarge instance on AWS, enabled -proposed and installed 4.15.0-145-generic. From there, I ran through the testcase of making a Raid10 array, and formatting it with xfs, and block discard performance was excellent: https://paste.ubuntu.com/p/Sr8tR9yhRd/ It took 3.2 seconds to format the array with xfs, and 1.0 seconds for a fstrim, as opposed to the 20 minutes it took beforehand. Performance with block discard is excellent. Moving onto the second testcase, the regression reproducer from bug 1907262. I started a n1-standard-2 VM on Google Cloud, and attached 2x NVMe scratch disks. I enabled -proposed and installed 4.15.0-145-generic. I ran through the testcase of making a Raid10 array, doing consistency checks, ensuring that mismatch count is 0, creating a file, deleting it, performing a fstrim, and more consistency checks, then taking the raid array down and bringing up one disk at a time, and performing a fsck.ext4. All disks came back clean: https://paste.ubuntu.com/p/h8gTd4JQ8Y/ Since the block discard performance is there, and there is no apparent data corruption going on after a fstrim, I will mark this verified for Bionic. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896578 Title: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.13-rc1. commit cf78408f937a67f59f5e90ee8e6cadeed7c128a8 Author: Xiao Ni Date: Thu Feb 4 15:50:43 2021 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://github.com/torvalds/linux/commit/cf78408f937a67f59f5e90ee8e6cadeed7c128a8 commit c2968285925adb97b9aa4ede94c1f1ab61ce0925 Author: Xiao Ni Date: Thu Feb 4 15:50:44 2021 +0800 Subject: md/raid10: extend r10bio devs to raid disks Lin
[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
Performing verification for Focal. I'm going to do three rounds of verification. The first is the testcase from this bug, showing block discard performance. The second is running through the regression reproducer from bug 1907262. The third will be results from my testing with my /home directory on a cloud instance with Raid10 backed disks, 3x customer testing and 2x community user testing. This will be in a separate comment closer to the release date once I have collected results. Starting with the testcase for this bug. I started a i3.8xlarge instance on AWS, enabled -proposed and installed 5.4.0-75-generic. From there, I ran through the testcase of making a Raid10 array, and formatting it with xfs, and block discard performance was excellent: https://paste.ubuntu.com/p/mdQ6Wjr4yK/ It took 6.6 seconds to format the array with xfs, and 3.8 seconds for a fstrim, as opposed to the 20 minutes it took beforehand. Performance with block discard is excellent. Moving onto the second testcase, the regression reproducer from bug 1907262. I started a n1-standard-2 VM on Google Cloud, and attached 2x NVMe scratch disks. I enabled -proposed and installed 5.4.0-75-generic. I ran through the testcase of making a Raid10 array, doing consistency checks, ensuring that mismatch count is 0, creating a file, deleting it, performing a fstrim, and more consistency checks, then taking the raid array down and bringing up one disk at a time, and performing a fsck.ext4. All disks came back clean: https://paste.ubuntu.com/p/jFHW26kcCK/ Since the block discard performance is there, and there is no apparent data corruption going on after a fstrim, I will mark this verified for Focal. ** 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/1896578 Title: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.13-rc1. commit cf78408f937a67f59f5e90ee8e6cadeed7c128a8 Author: Xiao Ni Date: Thu Feb 4 15:50:43 2021 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://github.com/torvalds/linux/commit/cf78408f937a67f59f5e90ee8e6cadeed7c128a8 commit c2968285925adb97b9aa4ede94c1f1ab61ce0925 Author: Xiao Ni Date: Thu Feb 4 15:50:44 2021 +0800 Subject: md/raid10: extend r10bio devs to raid disks Link: http
[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
Performing verification for Hirsute. I'm going to do three rounds of verification. The first is the testcase from this bug, showing block discard performance. The second is running through the regression reproducer from bug 1907262. The third will be results from my testing with my /home directory on a cloud instance with Raid10 backed disks, 3x customer testing and 2x community user testing. This will be in a separate comment closer to the release date once I have collected results. Starting with the testcase for this bug. I started a i3.8xlarge instance on AWS, enabled -proposed and installed 5.11.0-20-generic. From there, I ran through the testcase of making a Raid10 array, and formatting it with xfs, and block discard performance was excellent: https://paste.ubuntu.com/p/X5sdCGT78Y/ It took 4.6 seconds to format the array with xfs, and 2.8 seconds for a fstrim, as opposed to the 20 minutes it took beforehand. Performance with block discard is excellent. Moving onto the second testcase, the regression reproducer from bug 1907262. I started a n1-standard-2 VM on Google Cloud, and attached 2x NVMe scratch disks. I enabled -proposed and installed 5.11.0-20-generic. I ran through the testcase of making a Raid10 array, doing consistency checks, ensuring that mismatch count is 0, creating a file, deleting it, performing a fstrim, and more consistency checks, then taking the raid array down and bringing up one disk at a time, and performing a fsck.ext4. All disks came back clean: https://paste.ubuntu.com/p/Xy6CPCQXZN/ Since the block discard performance is there, and there is no apparent data corruption going on after a fstrim, I will mark this verified for Hirsute. ** Tags removed: verification-needed-hirsute ** Tags added: 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/1896578 Title: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.13-rc1. commit cf78408f937a67f59f5e90ee8e6cadeed7c128a8 Author: Xiao Ni Date: Thu Feb 4 15:50:43 2021 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://github.com/torvalds/linux/commit/cf78408f937a67f59f5e90ee8e6cadeed7c128a8 commit c2968285925adb97b9aa4ede94c1f1ab61ce0925 Author: Xiao Ni Date: Thu Feb 4 15:50:44 2021 +0800 Subject: md/raid10: extend r10bio devs to raid disks L
[Kernel-packages] [Bug 1907262] Re: raid10: discard leads to corrupted file system
Hi Thimo, Thanks for letting me know, and great to hear that things are working as expected. I'll check in with you in one week's time, to double check things are still going okay. I spent some time today performing verification on all the kernels in -proposed, testing block discard performance [1], and also running through the regression testcase from LP #1907262 [2]. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262 All kernels performed as expected, with block discard on 4x 1.9TB NVMe disks on an i3.8xlarge AWS instance taking 3-4 seconds, and the consistency checks performed returned clean disks, with no filesystem or data corruption. I have documented my tests in my verification messages: Hirsute: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/26 Groovy: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/27 Focal: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/28 Bionic: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/29 I have marked the launchpad bug as verified for all releases. I'm still running my own testing, with my /home directory being on a Raid10 array on a Google Cloud instance, and it has no issues. If things keep going well, we should see a release to -updates around the 21st of June, give or take a few days if any CVEs turn up. Thanks, Matthew -- 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/1907262 Title: raid10: discard leads to corrupted file system Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: Seems to be closely related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 After updating the Ubuntu 18.04 kernel from 4.15.0-124 to 4.15.0-126 the fstrim command triggered by fstrim.timer causes a severe number of mismatches between two RAID10 component devices. This bug affects several machines in our company with different HW configurations (All using ECC RAM). Both, NVMe and SATA SSDs are affected. How to reproduce: - Create a RAID10 LVM and filesystem on two SSDs mdadm -C -v -l10 -n2 -N "lv-raid" -R /dev/md0 /dev/nvme0n1p2 /dev/nvme1n1p2 pvcreate -ff -y /dev/md0 vgcreate -f -y VolGroup /dev/md0 lvcreate -n root-L 100G -ay -y VolGroup mkfs.ext4 /dev/VolGroup/root mount /dev/VolGroup/root /mnt - Write some data, sync and delete it dd if=/dev/zero of=/mnt/data.raw bs=4K count=1M sync rm /mnt/data.raw - Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (should be 0): cat /sys/block/md0/md/mismatch_cnt - Trigger the bug fstrim /mnt - Re-Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (probably in the range of N*1): cat /sys/block/md0/md/mismatch_cnt After investigating this issue on several machines it *seems* that the first drive does the trim correctly while the second one goes wild. At least the number and severity of errors found by a USB stick live session fsck.ext4 suggests this. To perform the single drive evaluation the RAID10 was started using a single drive at once: mdadm --assemble /dev/md127 /dev/nvme0n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root vgchange -a n /dev/VolGroup mdadm --stop /dev/md127 mdadm --assemble /dev/md127 /dev/nvme1n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root When starting these fscks without -n, on the first device it seems the directory structure is OK while on the second device there is only the lost+found folder left. Side-note: Another machine using HWE kernel 5.4.0-56 (after using -53 before) seems to have a quite similar issue. Unfortunately the risk/regression assessment in the aforementioned bug is not complete: the workaround only mitigates the issues during FS creation. This bug on the other hand is triggered by a weekly service (fstrim) causing severe file system corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+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 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
Hi Evan, Great to hear things are looking good for you and that the block discard performance is there. If possible, keep running the kernel from -proposed for a bit longer, just to make sure nothing comes up on longer runs. I spent some time today performing verification on all the kernels in -proposed, testing block discard performance [1], and also running through the regression testcase from LP #1907262 [2]. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262 All kernels performed as expected, with block discard on 4x 1.9TB NVMe disks on an i3.8xlarge AWS instance taking 3-4 seconds, and the consistency checks performed returned clean disks, with no filesystem or data corruption. I have documented my tests in my verification messages: Hirsute: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/26 Groovy: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/27 Focal: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/28 Bionic: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/29 I have marked the launchpad bug as verified for all releases. I'm still running my own testing, with my /home directory being on a Raid10 array on a Google Cloud instance, and it has no issues. If things keep going well, we should see a release to -updates around the 21st of June, give or take a few days if any CVEs turn up. Thanks, Matthew -- 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/1896578 Title: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.13-rc1. commit cf78408f937a67f59f5e90ee8e6cadeed7c128a8 Author: Xiao Ni Date: Thu Feb 4 15:50:43 2021 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://github.com/torvalds/linux/commit/cf78408f937a67f59f5e90ee8e6cadeed7c128a8 commit c2968285925adb97b9aa4ede94c1f1ab61ce0925 Author: Xiao Ni Date: Thu Feb 4 15:50:44 2021 +0800 Subject: md/raid10: extend r10bio devs to raid disks Link: https://github.com/torvalds/linux/commit/c2968285925adb97b9aa4ede94c1f1ab61ce0925 commit f2e7e269a7525317752d472bb48a549780e87d22 Author: Xiao Ni Date: Thu Feb 4 15:50:45 2021 +0800 Subject: md/raid10: pull the code that wait for blocked dev into one function Lin
[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
https://bugzilla.kernel.org/show_bug.cgi?id=213377 While testing, I reverted back to the original ubuntu OEM kernel 1026 and discovered, that the max_cstate-Parameter does not help while using that kernel. ** Bug watch added: Linux Kernel Bug Tracker #213377 https://bugzilla.kernel.org/show_bug.cgi?id=213377 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1026-oem N/A linux-backports-modules-5.10.0-1026-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1026-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.8/5.8.0.56.63~20.04.40)
All autopkgtests for the newly accepted linux-meta-hwe-5.8 (5.8.0.56.63~20.04.40) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.6 (armhf) linux-hwe-5.8/5.8.0-56.63~20.04.1 (arm64, ppc64el, s390x, amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (armhf, arm64, ppc64el, s390x) 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-hwe-5.8 [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 1931665] Re: HP EliteBook 845 G7 (Cezanne) S0iX not available due to the lack of amdgpu firmware for green_sardine
I'm marking this issue as INVALID as I probably rushed into the actions to be taken. ** Changed in: linux-firmware (Ubuntu Focal) Status: In Progress => Invalid ** Changed in: linux-firmware (Ubuntu Hirsute) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1931665 Title: HP EliteBook 845 G7 (Cezanne) S0iX not available due to the lack of amdgpu firmware for green_sardine Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Invalid Status in linux-firmware source package in Hirsute: Invalid Bug description: OS: Ubuntu 20.04.2 Linux kernel: 5.10.0-1027-oem Linux firmware: 1.187.12 Device: HP EliteBook 845 G7 (Cezanne) Even though the soix changes have been merged with 5.10.0-1027-oem, AMD Cezanne amdgpu firmware files are not present in in Ubuntu linux- firmware 1.187.12. With the above packages, resume breaks. No error message in dmesg. If I replace /lib/firmware with contents from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20210511.tar.gz, suspend/resume works. During suspend, LCD backlight, fan & keyboard backlight turns off. After resume, everything is back to normal. No errors regarding AMD GPU. The current Ubuntu linux-firmware package is two months old & there are lots of amdgpu & radeon commits after that. Prefer a generic update to the latest fw package. If its AMD Cezanne specific, the fw file names prefix is "green_sardine". This is a public bug for landing for bug 1929104. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1931665/+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 1904589] Re: zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4
Thank you!
--
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/1904589
Title:
zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Focal:
In Progress
Status in zfs-linux source package in Groovy:
Fix Released
Status in zfs-linux source package in Hirsute:
Fix Released
Bug description:
[Impact]
zfs_write() doesn't properly account partial copies done by
copy_from_user(), causing accesses past the end of objects and
triggering kernel panics.
[Test case]
The problem seems to be workload specific, there is not a specific
test case to reproduce the problem, but the bug seems to be pretty
well identified by the upstream commit reported below.
[Fix]
Apply upstream commit c9e3efdb3a6111b9795becc6594b3c52ba004522
("Bugfix/fix uio partial copies").
[Regression potential]
Upstream commit that is basically fixing potential out-of-bounds
accesses by properly checking partial copies done by copy_from_user()
and preventing kernel panics. Regression potential is minimal: it
seems unlikely to break other things if this change is applied.
[Original bug report]
Using latest zfs 0.8.3-1ubuntu12.4 on latest Ubuntu 20.04.1, I observe
a rare zfs panics that seem to be workload-specific which render a
server mostly unresponsive besides ssh still working. Attempting to
reboot the server in this state makes the shutdown hang forever.
You may want to consider backporting the fix released in zfs 0.8.4
into 20.04: https://github.com/openzfs/zfs/pull/10148
Log sample of panic:
```
Nov 17 16:06:15 hostname kernel: [3385134.716024] PANIC: zfs: accessing past
end of object c1c/2db52f (size=17408 access=7492+16428)
Nov 17 16:06:15 hostname kernel: [3385134.716072] Showing stack for process
3166846
Nov 17 16:06:15 hostname kernel: [3385134.716074] CPU: 25 PID: 3166846 Comm:
node Tainted: P O 5.4.0-48-generic #52-Ubuntu
Nov 17 16:06:15 hostname kernel: [3385134.716075] Hardware name:
Nov 17 16:06:15 hostname kernel: [3385134.716076] Call Trace:
Nov 17 16:06:15 hostname kernel: [3385134.716085] dump_stack+0x6d/0x9a
Nov 17 16:06:15 hostname kernel: [3385134.716097] spl_dumpstack+0x29/0x2b
[spl]
Nov 17 16:06:15 hostname kernel: [3385134.716102] vcmn_err.cold+0x60/0x99
[spl]
Nov 17 16:06:15 hostname kernel: [3385134.716106] ? _cond_resched+0x19/0x30
Nov 17 16:06:15 hostname kernel: [3385134.716108] ?
__kmalloc_node+0x20e/0x330
Nov 17 16:06:15 hostname kernel: [3385134.716113] ?
spl_kmem_alloc_impl+0xa8/0x100 [spl]
Nov 17 16:06:15 hostname kernel: [3385134.716190] ? __list_add+0x17/0x40
[zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716235]
zfs_panic_recover+0x6f/0x90 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716272] ?
dsl_dir_tempreserve_impl.isra.0.constprop.0+0xed/0x330 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716305]
dmu_buf_hold_array_by_dnode+0x3a0/0x490 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716338]
dmu_write_uio_dnode+0x4c/0x140 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716370]
dmu_write_uio_dbuf+0x4f/0x70 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716416] zfs_write+0xa1f/0xd40 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716419] ? d_absolute_path+0x74/0xb0
Nov 17 16:06:15 hostname kernel: [3385134.716421] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716423] ? __switch_to_asm+0x40/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716424] ? __switch_to_asm+0x40/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716425] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716427] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716474]
zpl_write_common_iovec+0xad/0x120 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716567] zpl_iter_write+0x56/0x90
[zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716570] do_iter_write+0x84/0x1a0
Nov 17 16:06:15 hostname kernel: [3385134.716574] ? futex_wake+0x8b/0x180
Nov 17 16:06:15 hostname kernel: [3385134.716577] do_writev+0x71/0x120
Nov 17 16:06:15 hostname kernel: [3385134.716581] do_syscall_64+0x57/0x190
Nov 17 16:06:15 hostname kernel: [3385134.716584] RIP: 0033:0x7fa366eee0cd
Nov 17 16:06:15 hostname kernel: [3385134.716587] RSP: 002b:7fa35e7fbde0
EFLAGS: 0293 ORIG_RAX: 0014
Nov 17 16:06:15 hostname kernel: [3385134.716590] RDX: 000c RSI:
0651c7b0 RDI: 001d
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1904589/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help :
[Kernel-packages] [Bug 1931677] [NEW] [SRU][F/G][linux-firmware] add realtek 8852a wifi fimware
Public bug reported: [Impact] Realtek 8852A wifi can not work without proper firmware. [Fix] Add realtek 8852a wifi fimware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with wifi ap, connect with 2.4G/5G, all good. [Where problems could occur] It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1931677 Title: [SRU][F/G][linux-firmware] add realtek 8852a wifi fimware Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Groovy: New Bug description: [Impact] Realtek 8852A wifi can not work without proper firmware. [Fix] Add realtek 8852a wifi fimware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with wifi ap, connect with 2.4G/5G, all good. [Where problems could occur] It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1931677/+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 1931677] Re: [SRU][F/G][linux-firmware] add realtek 8852a wifi fimware
** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-firmware (Ubuntu Groovy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-firmware (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Groovy) Status: New => In Progress -- 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/1931677 Title: [SRU][F/G][linux-firmware] add realtek 8852a wifi fimware Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: In Progress Status in linux-firmware source package in Groovy: In Progress Bug description: [Impact] Realtek 8852A wifi can not work without proper firmware. [Fix] Add realtek 8852a wifi firmware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with wifi ap, connect with 2.4G/5G, all good. [Where problems could occur] It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931677/+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 1931677] Re: [SRU][F/G][linux-firmware] add realtek 8852a wifi fimware
** Tags added: oem-priority originate-from-1921700 stella ** Description changed: [Impact] Realtek 8852A wifi can not work without proper firmware. [Fix] - Add realtek 8852a wifi fimware for driver. + Add realtek 8852a wifi firmware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with wifi ap, connect with 2.4G/5G, all good. [Where problems could occur] It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. -- 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/1931677 Title: [SRU][F/G][linux-firmware] add realtek 8852a wifi fimware Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: In Progress Status in linux-firmware source package in Groovy: In Progress Bug description: [Impact] Realtek 8852A wifi can not work without proper firmware. [Fix] Add realtek 8852a wifi firmware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with wifi ap, connect with 2.4G/5G, all good. [Where problems could occur] It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.11.0.20.21)
All autopkgtests for the newly accepted linux-meta (5.11.0.20.21) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: systemd/247.3-3ubuntu3 (armhf) 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/hirsute/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 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
I should have added that it would be best in this case to have the debug mode enabled for udevd, too: $ cat /etc/systemd/system/systemd-udevd.service.d/override.conf [Service] Environment=SYSTEMD_LOG_LEVEL=debug $ sudo systemctl daemon-reload && sudo systemctl restart systemd-udevd $ journalctl -b -u systemd-networkd -u systemd-udevd --no-pager (instead of -b you may do '--since="today"' and/or '--until="5 minutes ago"' or so to reduce the output) You may then trigger the udev rules directly, like: $ sudo udevadm trigger and once indirectly via netplan (and maybe via 'ip'). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdb0 is not for us (back
[Kernel-packages] [Bug 1931292] Re: Hirsute update: v5.11.22 upstream stable release
** Changed in: 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 linux in Ubuntu.
https://bugs.launchpad.net/bugs/1931292
Title:
Hirsute update: v5.11.22 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Hirsute:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.11.22 upstream stable release
from git://git.kernel.org/
KEYS: trusted: Fix memory leak on object td
tpm: fix error return code in tpm2_get_cc_attrs_tbl()
tpm, tpm_tis: Extend locality handling to TPM2 in tpm_tis_gen_interrupt()
tpm, tpm_tis: Reserve locality in tpm_tis_resume()
KVM: SVM: Make sure GHCB is mapped before updating
KVM: x86/mmu: Remove the defunct update_pte() paging hook
KVM/VMX: Invoke NMI non-IST entry instead of IST entry
ACPI: PM: Add ACPI ID of Alder Lake Fan
PM: runtime: Fix unpaired parent child_count for force_resume
cpufreq: intel_pstate: Use HWP if enabled by platform firmware
kvm: Cap halt polling at kvm->max_halt_poll_ns
ath11k: fix thermal temperature read
ALSA: usb-audio: Add Pioneer DJM-850 to quirks-table
fs: dlm: fix debugfs dump
fs: dlm: fix mark setting deadlock
fs: dlm: add errno handling to check callback
fs: dlm: add check if dlm is currently running
fs: dlm: change allocation limits
fs: dlm: check on minimum msglen size
fs: dlm: flush swork on shutdown
fs: dlm: add shutdown hook
tipc: convert dest node's address to network order
ASoC: Intel: bytcr_rt5640: Enable jack-detect support on Asus T100TAF
net/mlx5e: Use net_prefetchw instead of prefetchw in MPWQE TX datapath
net: stmmac: Set FIFO sizes for ipq806x
ASoC: rsnd: core: Check convert rate in rsnd_hw_params
Bluetooth: Fix incorrect status handling in LE PHY UPDATE event
i2c: bail out early when RDWR parameters are wrong
ALSA: hdsp: don't disable if not enabled
ALSA: hdspm: don't disable if not enabled
ALSA: rme9652: don't disable if not enabled
ALSA: bebob: enable to deliver MIDI messages for multiple ports
Bluetooth: Set CONF_NOT_COMPLETE as l2cap_chan default
Bluetooth: initialize skb_queue_head at l2cap_chan_create()
net/sched: cls_flower: use ntohs for struct flow_dissector_key_ports
net: bridge: when suppression is enabled exclude RARP packets
Bluetooth: check for zapped sk before connecting
selftests/powerpc: Fix L1D flushing tests for Power10
powerpc/32: Statically initialise first emergency context
net: hns3: remediate a potential overflow risk of bd_num_list
net: hns3: add handling for xmit skb with recursive fraglist
ip6_vti: proper dev_{hold|put} in ndo_[un]init methods
ASoC: Intel: bytcr_rt5640: Add quirk for the Chuwi Hi8 tablet
ice: handle increasing Tx or Rx ring sizes
Bluetooth: btusb: Enable quirk boolean flag for Mediatek Chip.
ASoC: rt5670: Add a quirk for the Dell Venue 10 Pro 5055
selftests: mptcp: launch mptcp_connect with timeout
i2c: Add I2C_AQ_NO_REP_START adapter quirk
Bluetooth: Do not set cur_adv_instance in adv param MGMT request
MIPS: Loongson64: Use _CACHE_UNCACHED instead of _CACHE_UNCACHED_ACCELERATED
coresight: Do not scan for graph if none is present
IB/hfi1: Correct oversized ring allocation
mac80211: Set priority and queue mapping for injected frames
mac80211: clear the beacon's CRC after channel switch
ASoC: soc-compress: lock pcm_mutex to resolve lockdep error
pinctrl: samsung: use 'int' for register masks in Exynos
rtw88: 8822c: add LC calibration for RTL8822C
mt76: mt7615: fix key set/delete issues
mt76: mt7615: support loading EEPROM for MT7613BE
mt76: mt76x0: disable GTK offloading
mt76: mt7915: always check return value from mt7915_mcu_alloc_wtbl_req
mt76: mt7915: fix key set/delete issue
mt76: mt7915: fix txpower init for TSSI off chips
mt76: mt7915: add wifi subsystem reset
i2c: imx: Fix PM reference leak in i2c_imx_reg_slave()
fuse: invalidate attrs when page writeback completes
virtiofs: fix userns
cuse: prevent clone
iwlwifi: pcie: make cfg vs. trans_cfg more robust
iwlwifi: queue: avoid memory leak in reset flow
powerpc/mm: Add cond_resched() while removing hpte mappings
ASoC: rsnd: call rsnd_ssi_master_clk_start() from rsnd_ssi_init()
Revert "iommu/amd: Fix performance counter initialization"
iommu/amd: Remove performance counter pre-initialization test
drm/amd/display: Force vsync flip when reconfiguring MPCC
selftests:
[Kernel-packages] [Bug 1930766] Re: Groovy update: upstream stable patchset 2021-06-03
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930766 Title: Groovy update: upstream stable patchset 2021-06-03 Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-06-03 Ported from the following upstream stable releases: v5.4.119, v5.10.37 from git://git.kernel.org/ Bluetooth: verify AMP hci_chan before amp_destroy bluetooth: eliminate the potential race condition when removing the HCI controller net/nfc: fix use-after-free llcp_sock_bind/connect Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" usb: roles: Call try_module_get() from usb_role_switch_find_by_fwnode() tty: moxa: fix TIOCSSERIAL jiffies conversions tty: amiserial: fix TIOCSSERIAL permission check USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions staging: greybus: uart: fix TIOCSSERIAL jiffies conversions USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check staging: fwserial: fix TIOCSSERIAL jiffies conversions tty: moxa: fix TIOCSSERIAL permission check staging: fwserial: fix TIOCSSERIAL permission check usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply usb: typec: tcpm: Address incorrect values of tcpm psy for pps supply usb: typec: tcpm: update power supply once partner accepts usb: xhci-mtk: remove or operator for setting schedule parameters usb: xhci-mtk: improve bandwidth scheduling with TT ASoC: samsung: tm2_wm5110: check of of_parse return value ASoC: Intel: kbl_da7219_max98927: Fix kabylake_ssp_fixup function MIPS: pci-mt7620: fix PLL lock check MIPS: pci-rt2880: fix slot 0 configuration FDDI: defxx: Bail out gracefully with unassigned PCI resource for CSR PCI: Allow VPD access for QLogic ISP2722 soc/tegra: regulators: Fix locking up when voltage-spread is out of range iio: inv_mpu6050: Fully validate gyro and accel scale writes iio:accel:adis16201: Fix wrong axis assignment that prevents loading iio:adc:ad7476: Fix remove handling sc16is7xx: Defer probe if device read fails phy: cadence: Sierra: Fix PHY power_on sequence misc: lis3lv02d: Fix false-positive WARN on various HP models phy: ti: j721e-wiz: Invoke wiz_init() before of_platform_device_create() misc: vmw_vmci: explicitly initialize vmci_notify_bm_set_msg struct misc: vmw_vmci: explicitly initialize vmci_datagram payload selinux: add proper NULL termination to the secclass_map permissions x86, sched: Treat Intel SNC topology as default, COD as exception md/bitmap: wait for external bitmap writes to complete during tear down md-cluster: fix use-after-free issue when removing rdev md: split mddev_find md: factor out a mddev_find_locked helper from mddev_find md: md_open returns -EBUSY when entering racing area md: Fix missing unused status line of /proc/mdstat mt76: mt7615: use ieee80211_free_txskb() in mt7615_tx_token_put() ipw2x00: potential buffer overflow in libipw_wx_set_encodeext() cfg80211: scan: drop entry from hidden_list on overflow rtw88: Fix array overrun in rtw_get_tx_power_params() FDDI: defxx: Make MMIO the configuration default except for EISA drm/qxl: use ttm bo priorities drm/panfrost: Clear MMU irqs before handling the fault drm/panfrost: Don't try to map pages that are already mapped drm/radeon: fix copy of uninitialized variable back to userspace drm/dp_mst: Revise broadcast msg lct & lcr drm/dp_mst: Set CLEAR_PAYLOAD_ID_TABLE as broadcast drm/amd/display: Reject non-zero src_y and src_x for video planes drm/amdgpu: fix concurrent VM flushes on Vega/Navi v2 ALSA: hda/realtek: Re-order ALC882 Acer quirk table entries ALSA: hda/realtek: Re-order ALC882 Sony quirk table entries ALSA: hda/realtek: Re-order ALC882 Clevo quirk table entries ALSA: hda/realtek: Re-order ALC269 HP quirk table entries ALSA: hda/realtek: Re-order ALC269 Acer quirk table entries ALSA: hda/realtek: Re-order ALC269 Dell quirk table entries ALSA: hda/realtek: Re-order ALC269 ASUS quirk table entries ALSA: hda/realtek: Re-order ALC269 Sony quirk table entries ALSA: hda/realtek: Re-order ALC269 Lenovo quirk table entries ALSA: hda/realtek: Re-order remaining ALC269 quirk table entries ALSA: hda/realtek:
[Kernel-packages] [Bug 1930095] Re: Groovy update: upstream stable patchset 2021-05-28
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930095 Title: Groovy update: upstream stable patchset 2021-05-28 Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-05-28 Ported from the following upstream stable releases: v5.4.118, v5.10.36 from git://git.kernel.org/ bus: mhi: core: Fix check for syserr at power_up bus: mhi: core: Clear configuration from channel context during reset bus: mhi: core: Sanity check values from remote device before use s390/disassembler: increase ebpf disasm buffer size vhost-vdpa: fix vm_flags for virtqueue doorbell mapping ACPI: custom_method: fix potential use-after-free issue ACPI: custom_method: fix a possible memory leak ftrace: Handle commands when closing set_ftrace_filter file ARM: 9056/1: decompressor: fix BSS size calculation for LLVM ld.lld arm64: dts: marvell: armada-37xx: add syscon compatible to NB clk node arm64: dts: mt8173: fix property typo of 'phys' in dsi node ecryptfs: fix kernel panic with null dev_name fs/epoll: restore waking from ep_done_scan() mtd: spi-nor: core: Fix an issue of releasing resources during read/write Revert "mtd: spi-nor: macronix: Add support for mx25l51245g" mtd: spinand: core: add missing MODULE_DEVICE_TABLE() mtd: rawnand: atmel: Update ecc_stats.corrected counter erofs: add unsupported inode i_format check spi: stm32-qspi: fix pm_runtime usage_count counter spi: spi-ti-qspi: Free DMA resources scsi: qla2xxx: Fix crash in qla2xxx_mqueuecommand() scsi: mpt3sas: Block PCI config access from userspace during reset mmc: uniphier-sd: Fix an error handling path in uniphier_sd_probe() mmc: uniphier-sd: Fix a resource leak in the remove function mmc: sdhci: Check for reset prior to DMA address unmap mmc: sdhci-pci: Fix initialization of some SD cards for Intel BYT-based controllers mmc: block: Update ext_csd.cache_ctrl if it was written mmc: block: Issue a cache flush only when it's enabled mmc: core: Do a power cycle when the CMD11 fails mmc: core: Set read only for SD cards with permanent write protect bit mmc: core: Fix hanging on I/O during system suspend for removable cards irqchip/gic-v3: Do not enable irqs when handling spurious interrups cifs: Return correct error code from smb2_get_enc_key cifs: fix out-of-bound memory access when calling smb3_notify() at mount point cifs: detect dead connections only when echoes are enabled. smb2: fix use-after-free in smb2_ioctl_query_info() btrfs: handle remount to no compress during compression x86/build: Disable HIGHMEM64G selection for M486SX btrfs: fix metadata extent leak after failure to create subvolume intel_th: pci: Add Rocket Lake CPU support btrfs: fix race between transaction aborts and fsyncs leading to use-after-free posix-timers: Preserve return value in clock_adjtime32() fbdev: zero-fill colormap in fbcmap.c cpuidle: tegra: Fix C7 idling state on Tegra114 bus: ti-sysc: Probe for l4_wkup and l4_cfg interconnect devices first staging: wimax/i2400m: fix byte-order issue spi: ath79: always call chipselect function spi: ath79: remove spi-master setup and cleanup assignment bus: mhi: core: Destroy SBL devices when moving to mission mode crypto: api - check for ERR pointers in crypto_destroy_tfm() crypto: qat - fix unmap invalid dma address usb: gadget: uvc: add bInterval checking for HS mode usb: webcam: Invalid size of Processing Unit Descriptor crypto: hisilicon/sec - fixes a printing error genirq/matrix: Prevent allocation counter corruption usb: gadget: f_uac2: validate input parameters usb: gadget: f_uac1: validate input parameters usb: xhci: Fix port minor revision PCI: PM: Do not read power state in pci_enable_device_flags() ARM: dts: BCM5301X: fix "reg" formatting in /memory node ARM: dts: ux500: Fix up TVK R3 sensors x86/build: Propagate $(CLANG_FLAGS) to $(REALMODE_FLAGS) x86/boot: Add $(CLANG_FLAGS) to compressed KBUILD_CFLAGS efi/libstub: Add $(CLANG_FLAGS) to x86 flags soc/tegra: pmc: Fix completion of power-gate toggling tee: optee: do not check memref size on return from Secure World soundwire: cadence: only prepare attached dev
[Kernel-packages] [Bug 1931158] Re: Focal update: v5.4.121 upstream stable release
** Changed in: 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 linux in Ubuntu.
https://bugs.launchpad.net/bugs/1931158
Title:
Focal update: v5.4.121 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.121 upstream stable release
from git://git.kernel.org/
x86/msr: Fix wr/rdmsr_safe_regs_on_cpu() prototypes
kgdb: fix gcc-11 warning on indentation
usb: sl811-hcd: improve misleading indentation
cxgb4: Fix the -Wmisleading-indentation warning
isdn: capi: fix mismatched prototypes
pinctrl: ingenic: Improve unreachable code generation
xsk: Simplify detection of empty and full rings
virtio_net: Do not pull payload in skb->head
PCI: thunder: Fix compile testing
dmaengine: dw-edma: Fix crash on loading/unloading driver
ARM: 9066/1: ftrace: pause/unpause function graph tracer in cpu_suspend()
ACPI / hotplug / PCI: Fix reference count leak in enable_slot()
Input: elants_i2c - do not bind to i2c-hid compatible ACPI instantiated
devices
Input: silead - add workaround for x86 BIOS-es which bring the chip up in a
stuck state
um: Mark all kernel symbols as local
um: Disable CONFIG_GCOV with MODULES
ARM: 9075/1: kernel: Fix interrupted SMC calls
scripts/recordmcount.pl: Fix RISC-V regex for clang
riscv: Workaround mcount name prior to clang-13
scsi: lpfc: Fix illegal memory access on Abort IOCBs
ceph: fix fscache invalidation
scsi: target: tcmu: Return from tcmu_handle_completions() if cmd_id not found
bridge: Fix possible races between assigning rx_handler_data and setting
IFF_BRIDGE_PORT bit
drm/amd/display: Fix two cursor duplication when using overlay
gpiolib: acpi: Add quirk to ignore EC wakeups on Dell Venue 10 Pro 5055
ALSA: hda: generic: change the DAC ctl name for LO+SPK or LO+HP
block: reexpand iov_iter after read/write
lib: stackdepot: turn depot_lock spinlock to raw_spinlock
net: stmmac: Do not enable RX FIFO overflow interrupts
ip6_gre: proper dev_{hold|put} in ndo_[un]init methods
sit: proper dev_{hold|put} in ndo_[un]init methods
ip6_tunnel: sit: proper dev_{hold|put} in ndo_[un]init methods
ipv6: remove extra dev_hold() for fallback tunnels
KVM: arm64: Initialize VCPU mdcr_el2 before loading it
tweewide: Fix most Shebang lines
scripts: switch explicitly to Python 3
Linux 5.4.121
UBUNTU: upstream stable to v5.4.121
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931158/+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 1930474] Re: Focal update: v5.4.120 upstream stable release
** Changed in: 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 linux in Ubuntu.
https://bugs.launchpad.net/bugs/1930474
Title:
Focal update: v5.4.120 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.120 upstream stable release
from git://git.kernel.org/
tpm: fix error return code in tpm2_get_cc_attrs_tbl()
tpm, tpm_tis: Extend locality handling to TPM2 in tpm_tis_gen_interrupt()
tpm, tpm_tis: Reserve locality in tpm_tis_resume()
KVM: x86/mmu: Remove the defunct update_pte() paging hook
PM: runtime: Fix unpaired parent child_count for force_resume
fs: dlm: fix debugfs dump
tipc: convert dest node's address to network order
ASoC: Intel: bytcr_rt5640: Enable jack-detect support on Asus T100TAF
net: stmmac: Set FIFO sizes for ipq806x
ASoC: rsnd: core: Check convert rate in rsnd_hw_params
i2c: bail out early when RDWR parameters are wrong
ALSA: hdsp: don't disable if not enabled
ALSA: hdspm: don't disable if not enabled
ALSA: rme9652: don't disable if not enabled
ALSA: bebob: enable to deliver MIDI messages for multiple ports
Bluetooth: Set CONF_NOT_COMPLETE as l2cap_chan default
Bluetooth: initialize skb_queue_head at l2cap_chan_create()
net: bridge: when suppression is enabled exclude RARP packets
Bluetooth: check for zapped sk before connecting
ip6_vti: proper dev_{hold|put} in ndo_[un]init methods
ASoC: Intel: bytcr_rt5640: Add quirk for the Chuwi Hi8 tablet
i2c: Add I2C_AQ_NO_REP_START adapter quirk
mac80211: clear the beacon's CRC after channel switch
pinctrl: samsung: use 'int' for register masks in Exynos
mt76: mt76x0: disable GTK offloading
cuse: prevent clone
ASoC: rsnd: call rsnd_ssi_master_clk_start() from rsnd_ssi_init()
Revert "iommu/amd: Fix performance counter initialization"
iommu/amd: Remove performance counter pre-initialization test
drm/amd/display: Force vsync flip when reconfiguring MPCC
selftests: Set CC to clang in lib.mk if LLVM is set
kconfig: nconf: stop endless search loops
ALSA: hda/hdmi: fix race in handling acomp ELD notification at resume
sctp: Fix out-of-bounds warning in sctp_process_asconf_param()
flow_dissector: Fix out-of-bounds warning in __skb_flow_bpf_to_target()
powerpc/smp: Set numa node before updating mask
ASoC: rt286: Generalize support for ALC3263 codec
ethtool: ioctl: Fix out-of-bounds warning in store_link_ksettings_for_user()
net: sched: tapr: prevent cycle_time == 0 in parse_taprio_schedule
samples/bpf: Fix broken tracex1 due to kprobe argument change
powerpc/pseries: Stop calling printk in rtas_stop_self()
drm/amd/display: fixed divide by zero kernel crash during dsc enablement
wl3501_cs: Fix out-of-bounds warnings in wl3501_send_pkt
wl3501_cs: Fix out-of-bounds warnings in wl3501_mgmt_join
qtnfmac: Fix possible buffer overflow in qtnf_event_handle_external_auth
powerpc/iommu: Annotate nested lock for lockdep
iavf: remove duplicate free resources calls
net: ethernet: mtk_eth_soc: fix RX VLAN offload
bnxt_en: Add PCI IDs for Hyper-V VF devices.
ia64: module: fix symbolizer crash on fdescr
ASoC: rt286: Make RT286_SET_GPIO_* readable and writable
thermal: thermal_of: Fix error return code of
thermal_of_populate_bind_params()
f2fs: fix a redundant call to f2fs_balance_fs if an error occurs
PCI: iproc: Fix return value of iproc_msi_irq_domain_alloc()
PCI: Release OF node in pci_scan_device()'s error path
ARM: 9064/1: hw_breakpoint: Do not directly check the event's
overflow_handler hook
rpmsg: qcom_glink_native: fix error return code of qcom_glink_rx_data()
NFSv4.2: Always flush out writes in nfs42_proc_fallocate()
NFS: Deal correctly with attribute generation counter overflow
PCI: endpoint: Fix missing destroy_workqueue()
pNFS/flexfiles: fix incorrect size check in decode_nfs_fh()
NFSv4.2 fix handling of sr_eof in SEEK's reply
rtc: fsl-ftm-alarm: add MODULE_TABLE()
ceph: fix inode leak on getattr error in __fh_to_dentry
rtc: ds1307: Fix wday settings for rx8130
net: hns3: fix incorrect configuration for igu_egu_hw_err
net: hns3: initialize the message content in hclge_get_link_mode()
net: hns3: add check for HNS3_NIC_STATE_INITED in hns3_reset_notify_up_enet()
net: hns3: fix for vxlan gpe tx checksum bug
net: hns3: use netif_tx_
[Kernel-packages] [Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From stefan.ra...@de.ibm.com 2021-06-10 03:55 EDT--- Makes me wonder if what we're seeing is a side-effect of --- Comment From stefan.ra...@de.ibm.com 2021-06-10 03:58 EDT--- Makes me wonder whether this could be a side-effect of the interface name, indeed. @Viktor/Niklas: Interface enP50s3832.170 gets an IP assigned, no problem. But enP53p0s0.171 does not, and Frank noticed that systemd spills out this message: enP53p0s0.171: link pending udev initialization... So could it be that systemd trips over the FID containing an alphabetic character, and never registers the interface as properly initialized..? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.
[Kernel-packages] [Bug 1931166] Re: Focal update: v5.4.124 upstream stable release
** Changed in: 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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1931166 Title: Focal update: v5.4.124 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.124 upstream stable release from git://git.kernel.org/ ALSA: hda/realtek: Headphone volume is controlled by Front mixer ALSA: usb-audio: scarlett2: Fix device hang with ehci-pci ALSA: usb-audio: scarlett2: Improve driver startup messages cifs: set server->cipher_type to AES-128-CCM for SMB3.0 NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return() iommu/vt-d: Fix sysfs leak in alloc_iommu() perf intel-pt: Fix sample instruction bytes perf intel-pt: Fix transaction abort handling perf scripts python: exported-sql-viewer.py: Fix copy to clipboard from Top Calls by elapsed Time report perf scripts python: exported-sql-viewer.py: Fix Array TypeError perf scripts python: exported-sql-viewer.py: Fix warning display proc: Check /proc/$pid/attr/ writes against file opener net: hso: fix control-request directions ath10k: Validate first subframe of A-MSDU before processing the list dm snapshot: properly fix a crash when an origin has no snapshots drm/amdgpu/vcn1: add cancel_delayed_work_sync before power gate drm/amdgpu/vcn2.0: add cancel_delayed_work_sync before power gate drm/amdgpu/vcn2.5: add cancel_delayed_work_sync before power gate selftests/gpio: Use TEST_GEN_PROGS_EXTENDED selftests/gpio: Move include of lib.mk up selftests/gpio: Fix build when source tree is read only kgdb: fix gcc-11 warnings harder Documentation: seccomp: Fix user notification documentation serial: core: fix suspicious security_locked_down() call misc/uss720: fix memory leak in uss720_probe thunderbolt: dma_port: Fix NVM read buffer bounds and offset issue mei: request autosuspend after sending rx flow control staging: iio: cdc: ad7746: avoid overwrite of num_channels iio: gyro: fxas21002c: balance runtime power in error path iio: adc: ad7768-1: Fix too small buffer passed to iio_push_to_buffers_with_timestamp() iio: adc: ad7124: Fix missbalanced regulator enable / disable on error. iio: adc: ad7124: Fix potential overflow due to non sequential channel numbers iio: adc: ad7793: Add missing error code in ad7793_setup() serial: 8250_pci: Add support for new HPE serial device serial: 8250_pci: handle FL_NOIRQ board flag USB: trancevibrator: fix control-request direction USB: usbfs: Don't WARN about excessively large memory allocations serial: tegra: Fix a mask operation that is always true serial: sh-sci: Fix off-by-one error in FIFO threshold register setting serial: rp2: use 'request_firmware' instead of 'request_firmware_nowait' USB: serial: ti_usb_3410_5052: add startech.com device id USB: serial: option: add Telit LE910-S1 compositions 0x7010, 0x7011 USB: serial: ftdi_sio: add IDs for IDS GmbH Products USB: serial: pl2303: add device id for ADLINK ND-6530 GC thermal/drivers/intel: Initialize RW trip to THERMAL_TEMP_INVALID usb: dwc3: gadget: Properly track pending and queued SG usb: gadget: udc: renesas_usb3: Fix a race in usb3_start_pipen() net: usb: fix memory leak in smsc75xx_bind spi: spi-geni-qcom: Fix use-after-free on unbind Bluetooth: cmtp: fix file refcount when cmtp_attach_device fails fs/nfs: Use fatal_signal_pending instead of signal_pending NFS: fix an incorrect limit in filelayout_decode_layout() NFS: Fix an Oopsable condition in __nfs_pageio_add_request() NFS: Don't corrupt the value of pg_bytes_written in nfs_do_recoalesce() NFSv4: Fix v4.0/v4.1 SEEK_DATA return -ENOTSUPP when set NFS_V4_2 config drm/meson: fix shutdown crash when component not probed net/mlx5e: Fix multipath lag activation net/mlx5e: Fix nullptr in add_vlan_push_action() net/mlx4: Fix EEPROM dump support Revert "net:tipc: Fix a double free in tipc_sk_mcast_rcv" tipc: wait and exit until all work queues are done tipc: skb_linearize the head skb when reassembling msgs spi: spi-fsl-dspi: Fix a resource leak in an error handling path net: dsa: mt7530: fix VLAN traffic leaks net: dsa: fix a crash if ->get_sset_count() fails net: dsa: sja1105: error out on unsupported PHY mode i2c: s3c2410: fix possible NULL point
[Kernel-packages] [Bug 1931160] Re: Focal update: v5.4.123 upstream stable release
** Changed in: 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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1931160 Title: Focal update: v5.4.123 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.123 upstream stable release from git://git.kernel.org/ usb: dwc3: gadget: Enable suspend events perf unwind: Fix separate debug info files when using elfutils' libdw's unwinder perf unwind: Set userdata for all __report_module() paths NFC: nci: fix memory leak in nci_allocate_device Linux 5.4.123 UBUNTU: upstream stable to v5.4.123 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931160/+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 1931159] Re: Focal update: v5.4.122 upstream stable release
** Changed in: 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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1931159 Title: Focal update: v5.4.122 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.122 upstream stable release from git://git.kernel.org/ firmware: arm_scpi: Prevent the ternary sign expansion bug openrisc: Fix a memory leak RDMA/siw: Properly check send and receive CQ pointers RDMA/siw: Release xarray entry RDMA/rxe: Clear all QP fields if creation failed scsi: ufs: core: Increase the usable queue depth scsi: qla2xxx: Fix error return code in qla82xx_write_flash_dword() RDMA/mlx5: Recover from fatal event in dual port mode RDMA/core: Don't access cm_id after its destruction platform/mellanox: mlxbf-tmfifo: Fix a memory barrier issue platform/x86: dell-smbios-wmi: Fix oops on rmmod dell_smbios RDMA/uverbs: Fix a NULL vs IS_ERR() bug ptrace: make ptrace() fail if the tracee changed its pid unexpectedly nvmet: seset ns->file when open fails locking/mutex: clear MUTEX_FLAGS if wait_list is empty due to signal btrfs: avoid RCU stalls while running delayed iputs cifs: fix memory leak in smb2_copychunk_range ALSA: dice: fix stream format for TC Electronic Konnekt Live at high sampling transfer frequency ALSA: intel8x0: Don't update period unless prepared ALSA: line6: Fix racy initialization of LINE6 MIDI ALSA: dice: fix stream format at middle sampling rate for Alesis iO 26 ALSA: firewire-lib: fix calculation for size of IR context payload ALSA: usb-audio: Validate MS endpoint descriptors ALSA: bebob/oxfw: fix Kconfig entry for Mackie d.2 Pro ALSA: hda: fixup headset for ASUS GU502 laptop Revert "ALSA: sb8: add a check for request_region" ALSA: firewire-lib: fix check for the size of isochronous packet payload ALSA: hda/realtek: reset eapd coeff to default value for alc287 ALSA: hda/realtek: Add some CLOVE SSIDs of ALC293 ALSA: hda/realtek: Fix silent headphone output on ASUS UX430UA ALSA: hda/realtek: Add fixup for HP OMEN laptop ALSA: hda/realtek: Add fixup for HP Spectre x360 15-df0xxx uio_hv_generic: Fix a memory leak in error handling paths Revert "rapidio: fix a NULL pointer dereference when create_workqueue() fails" rapidio: handle create_workqueue() failure Revert "serial: mvebu-uart: Fix to avoid a potential NULL pointer dereference" drm/amdgpu: disable 3DCGCG on picasso/raven1 to avoid compute hang drm/amdgpu: update gc golden setting for Navi12 drm/amdgpu: update sdma golden setting for Navi12 mmc: sdhci-pci-gli: increase 1.8V regulator wait xen-pciback: reconfigure also from backend watch handler dm snapshot: fix crash with transient storage and zero chunk size Revert "video: hgafb: fix potential NULL pointer dereference" Revert "net: stmicro: fix a missing check of clk_prepare" Revert "leds: lp5523: fix a missing check of return value of lp55xx_read" Revert "hwmon: (lm80) fix a missing check of bus read in lm80 probe" Revert "video: imsttfb: fix potential NULL pointer dereferences" Revert "ecryptfs: replace BUG_ON with error handling code" Revert "scsi: ufs: fix a missing check of devm_reset_control_get" Revert "gdrom: fix a memory leak bug" cdrom: gdrom: deallocate struct gdrom_unit fields in remove_gdrom cdrom: gdrom: initialize global variable at init time Revert "media: rcar_drif: fix a memory disclosure" Revert "rtlwifi: fix a potential NULL pointer dereference" Revert "qlcnic: Avoid potential NULL pointer dereference" Revert "niu: fix missing checks of niu_pci_eeprom_read" ethernet: sun: niu: fix missing checks of niu_pci_eeprom_read() net: stmicro: handle clk_prepare() failure during init scsi: ufs: handle cleanup correctly on devm_reset_control_get error net: rtlwifi: properly check for alloc_workqueue() failure ics932s401: fix broken handling of errors when word reading fails leds: lp5523: check return value of lp5xx_read and jump to cleanup code qlcnic: Add null check after calling netdev_alloc_skb video: hgafb: fix potential NULL pointer dereference vgacon: Record video mode changes with VT_RESIZEX vt: Fix character height handling with VT_RESIZEX tty: vt: always invoke vc->vc_sw->con_resize callback nvme-multipath: fix double initialization o
[Kernel-packages] [Bug 1931546] [NEW] No ethernet with alx driver upon wake up in 5.11
Public bug reported: alx driver does not correctly restart the ethernet upon waking up. The bug (new behavior) has been introduced somewhere in the 5.10 kernel series (indirectly?) and got fixed for 5.12 and 5.13. However, no backport for 5.11 (Ubuntu 21.04) exists. The fix: https://github.com/gregkh/linux/commit/a4dcfbc4ee2218abd567d81d795082d8d4afcdf6#diff-641218b365d6949b9f2bbc730a547b421c127283cd0a5b5fd85c07cc6729bb81 Using 5.12 solves the issue due to an implemented fix: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12.9/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1931546/+attachment/5503811/+files/lspci-vnvn.log -- 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/1931546 Title: No ethernet with alx driver upon wake up in 5.11 Status in linux package in Ubuntu: New Bug description: alx driver does not correctly restart the ethernet upon waking up. The bug (new behavior) has been introduced somewhere in the 5.10 kernel series (indirectly?) and got fixed for 5.12 and 5.13. However, no backport for 5.11 (Ubuntu 21.04) exists. The fix: https://github.com/gregkh/linux/commit/a4dcfbc4ee2218abd567d81d795082d8d4afcdf6#diff-641218b365d6949b9f2bbc730a547b421c127283cd0a5b5fd85c07cc6729bb81 Using 5.12 solves the issue due to an implemented fix: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12.9/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931546/+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 1930472] Re: Bionic update: upstream stable patchset 2021-06-01
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930472 Title: Bionic update: upstream stable patchset 2021-06-01 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-06-01 Ported from the following upstream stable releases: v4.14.233, v4.19.191 from git://git.kernel.org/ MIPS: Introduce isa-rev.h to define MIPS_ISA_REV MIPS: cpu-features.h: Replace __mips_isa_rev with MIPS_ISA_REV s390/disassembler: increase ebpf disasm buffer size ACPI: custom_method: fix potential use-after-free issue ACPI: custom_method: fix a possible memory leak arm64: dts: mt8173: fix property typo of 'phys' in dsi node ecryptfs: fix kernel panic with null dev_name spi: spi-ti-qspi: Free DMA resources mmc: block: Update ext_csd.cache_ctrl if it was written mmc: core: Do a power cycle when the CMD11 fails mmc: core: Set read only for SD cards with permanent write protect bit cifs: Return correct error code from smb2_get_enc_key btrfs: fix metadata extent leak after failure to create subvolume intel_th: pci: Add Rocket Lake CPU support fbdev: zero-fill colormap in fbcmap.c staging: wimax/i2400m: fix byte-order issue crypto: api - check for ERR pointers in crypto_destroy_tfm() usb: gadget: uvc: add bInterval checking for HS mode usb: gadget: f_uac1: validate input parameters usb: dwc3: gadget: Ignore EP queue requests during bus reset usb: xhci: Fix port minor revision PCI: PM: Do not read power state in pci_enable_device_flags() x86/build: Propagate $(CLANG_FLAGS) to $(REALMODE_FLAGS) tee: optee: do not check memref size on return from Secure World perf/arm_pmu_platform: Fix error handling spi: dln2: Fix reference leak to master spi: omap-100k: Fix reference leak to master intel_th: Consistency and off-by-one fix phy: phy-twl4030-usb: Fix possible use-after-free in twl4030_usb_remove() btrfs: convert logic BUG_ON()'s in replace_path to ASSERT()'s scsi: lpfc: Fix incorrect dbde assignment when building target abts wqe scsi: lpfc: Fix pt2pt connection does not recover after LOGO scsi: target: pscsi: Fix warning in pscsi_complete_cmd() media: ite-cir: check for receive overflow power: supply: bq27xxx: fix power_avg for newer ICs extcon: arizona: Fix some issues when HPDET IRQ fires after the jack has been unplugged media: media/saa7164: fix saa7164_encoder_register() memory leak bugs media: gspca/sq905.c: fix uninitialized variable power: supply: Use IRQF_ONESHOT drm/amdgpu : Fix asic reset regression issue introduce by 8f211fe8ac7c4f scsi: qla2xxx: Always check the return value of qla24xx_get_isp_stats() scsi: qla2xxx: Fix use after free in bsg scsi: scsi_dh_alua: Remove check for ASC 24h in alua_rtpg() media: em28xx: fix memory leak media: vivid: update EDID clk: socfpga: arria10: Fix memory leak of socfpga_clk on error return power: supply: generic-adc-battery: fix possible use-after-free in gab_remove() power: supply: s3c_adc_battery: fix possible use-after-free in s3c_adc_bat_remove() media: adv7604: fix possible use-after-free in adv76xx_remove() media: i2c: adv7511-v4l2: fix possible use-after-free in adv7511_remove() media: i2c: adv7842: fix possible use-after-free in adv7842_remove() media: dvb-usb: fix memory leak in dvb_usb_adapter_init media: gscpa/stv06xx: fix memory leak drm/msm/mdp5: Configure PP_SYNC_HEIGHT to double the vtotal drm/amdgpu: fix NULL pointer dereference scsi: lpfc: Fix crash when a REG_RPI mailbox fails triggering a LOGO response scsi: lpfc: Remove unsupported mbox PORT_CAPABILITIES logic scsi: libfc: Fix a format specifier ALSA: emu8000: Fix a use after free in snd_emu8000_create_mixer ALSA: hda/conexant: Re-order CX5066 quirk table entries ALSA: sb: Fix two use after free in snd_sb_qsound_build btrfs: fix race when picking most recent mod log operation for an old root arm64/vdso: Discard .note.gnu.property sections in vDSO openvswitch: fix stack OOB read while fragmenting IPv4 packets ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure NFSv4: Don't discard segments marked for return in _pnfs_return_layout() jffs2: Fix kasan slab-out-of-bounds probl
[Kernel-packages] [Bug 1930582] Re: Fix ICL PCH no picture after S3
** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930582 Title: Fix ICL PCH no picture after S3 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] Blank DP display after S3 on Intel GFX in ICL PCH desktop. [Fix] Use proper IRQ setup so the system in question can detect HPD after S3. [Test] Suspend and resume the system. No picture on DP display. With the patch applied, DP display works as expected. [Where problems could occur] It changes how the Intel GFX setup its HPD IRQ, so hotplug detection will be affected. This change is limited to ICL PCH. This is the second patch of "drm/i915/gen9bc: Handle TGP PCH during suspend/resume", but somehow it was omitted. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930582/+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 1829978] Re: cpuacct_100_100 from controllers test suite in LTP failed
Found on Azure Standard_B1ms instances: - hirsute/linux-azure 5.11.0-1007.7 - groovy/linux-azure 5.8.0-1033.35 - groovy/linux-azure 5.8.0-1034.36-azure - focal/linux-azure 5.8.0-1033.35~20.04.1 - focal/linux-azure 5.4.0-1049.51 - bionic/linux-azure 5.4.0-1049.51~18.04.1 Does not appear on other instances, therefore I propose to skip this part on Standard_B1ms. On Standard_B1ms this seems to be systemd runtime configuration limit. Visible in dmesg: [ 926.863344] LTP: starting cpuacct_100_100 (cpuacct.sh 100 100) [ 934.298505] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-3.scope -- 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/1829978 Title: cpuacct_100_100 from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Bug description: startup='Wed May 22 06:50:45 2019' cpuacct 1 TINFO: timeout per run is 0h 5m 0s cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes /opt/ltp/testcases/bin/cpuacct.sh: -2110094999: /opt/ltp/testcases/bin/cpuacct.sh: Cannot fork tag=cpuacct_100_100 stime=1558507845 dur=9 exit=exited stat=2 core=no cu=30 cs=53 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 06:59:27 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829978/+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 1921870] Re: [UBUNTU 21.04] tools/kvm_stat: Add restart delay
** Changed in: linux (Ubuntu Hirsute) Status: New => Fix Committed ** Description changed: + SRU Justification: + + [Impact] + + * Nice to have feature requested by IBM - a systemd service monitoring + KVM guests. + * Adds a new systemd service, not enabled by default. + + [Fix] + + * Install the systemd .service file when installing linux-tools-host + + [Test Plan] + + * dpkg -c linux-tools-host_5.11.0-18.19_all.deb + ./lib/systemd/system/kvm_stat.service + * Install the package and reboot + * Check if kvm_stat is present and not active after reboot: + ls -l /lib/systemd/system/kvm_stat.service + systemctl -a | grep kvm_stat + + [Where problems could occur] + + * Service can be enabled and started by mistake or by any further future + Makefile change (enabling all services installed by linux-tools-host). + + * The service logs into /var/log/kvm_stat.csv (not journal!) and package does + not provide logrotate by default, thus the logging could eat entire + disk space. + + -- Original Description -- + Description: tools/kvm_stat: Add restart delay Symptom: If the kvm service is enabled and the system rebooted, -Systemd's initial attempt to start the kvm unit file may -fail in case the kvm module is not loaded. However, once the -kvm module is loaded, the service is _not_ started. + Systemd's initial attempt to start the kvm unit file may + fail in case the kvm module is not loaded. However, once the + kvm module is loaded, the service is _not_ started. Problem: Since the unit file does not specify a delay for the retries, -Systemd restarts with a minimum delay a number of times -before giving up and disabling the service. Which means a -subsequent kvm module load will have kvm running without -monitoring. + Systemd restarts with a minimum delay a number of times + before giving up and disabling the service. Which means a + subsequent kvm module load will have kvm running without + monitoring. Solution: Add an appropriate delay in the unit file. Reproduction: (1) Enable the kvm service via systemctl -(2) Reboot -(3) Verify that the kvm module is not loaded & kvm service -not running -(4) Load the kvm module via 'modprobe kvm' -(5) Verify that the kvm service came up within the next -minute. + (2) Reboot + (3) Verify that the kvm module is not loaded & kvm service + not running + (4) Load the kvm module via 'modprobe kvm' + (5) Verify that the kvm service came up within the next + minute. Preventive:yes Just use the attached patch and you're good! -- 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/1921870 Title: [UBUNTU 21.04] tools/kvm_stat: Add restart delay Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: [Impact] * Nice to have feature requested by IBM - a systemd service monitoring KVM guests. * Adds a new systemd service, not enabled by default. [Fix] * Install the systemd .service file when installing linux-tools-host [Test Plan] * dpkg -c linux-tools-host_5.11.0-18.19_all.deb ./lib/systemd/system/kvm_stat.service * Install the package and reboot * Check if kvm_stat is present and not active after reboot: ls -l /lib/systemd/system/kvm_stat.service systemctl -a | grep kvm_stat [Where problems could occur] * Service can be enabled and started by mistake or by any further future Makefile change (enabling all services installed by linux-tools-host). * The service logs into /var/log/kvm_stat.csv (not journal!) and package does not provide logrotate by default, thus the logging could eat entire disk space. -- Original Description -- Description: tools/kvm_stat: Add restart delay Symptom: If the kvm service is enabled and the system rebooted, Systemd's initial attempt to start the kvm unit file may fail in case the kvm module is not loaded. However, once the kvm module is loaded, the service is _not_ started. Problem: Since the unit file does not specify a delay for the retries, Systemd restarts with a minimum delay a number of times before giving up and disabling the service. Which means a subsequent kvm module load will have k
[Kernel-packages] [Bug 1829978] Re: cpuacct_100_100 from controllers test suite in LTP failed
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Krzysztof Kozlowski (krzk) -- 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/1829978 Title: cpuacct_100_100 from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Bug description: startup='Wed May 22 06:50:45 2019' cpuacct 1 TINFO: timeout per run is 0h 5m 0s cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes /opt/ltp/testcases/bin/cpuacct.sh: -2110094999: /opt/ltp/testcases/bin/cpuacct.sh: Cannot fork tag=cpuacct_100_100 stime=1558507845 dur=9 exit=exited stat=2 core=no cu=30 cs=53 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 06:59:27 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829978/+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 1930976] Re: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
I have the same issue. I'm using an Nvidia 3070 and Ubuntu refuse to recognize it. I'm using 460 driver version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930976 Title: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers Status in linux-hwe-5.8 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Kernel: 5.8.0-55 The last kernel destroyed my Ubuntu 20.04.02 installation, something went wrong with some kernel packages. It seems like Ubuntu is unable to find my video card correctly and the device drivers from Nvidia don't seem to work anymore. I had to do a clean installation, but even that doesn't solve the problem. I think this is a serious issue that needs to be looked into. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jun 5 16:50:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation Device [10de:2206] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:403f] InstallationDate: Installed on 2021-06-05 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=4984fe2f-d45f-4734-884c-2426bcf10ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33j dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33j:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1930976/+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 1930707] Re: Mic-mute/mute LEDs not work on some HP platforms
** Changed in: 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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1930707 Title: Mic-mute/mute LEDs not work on some HP platforms Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on 1) HP ZBook Fury 17.3 Inch G8 Mobile Workstation PC 2) HP ZBook Fury 15.6 Inch G8 Mobile Workstation PC 3) HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC 4) HP EliteBook 855 G8 Notebook PC The right channel of internal speaker doesn't work on 1) HP ZBook Fury 17.3 Inch G8 Mobile Workstation PC 2) HP ZBook Fury 15.6 Inch G8 Mobile Workstation PC 3) HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC [Fix] These four platforms need specific quirk for different hardware layout. Thus, add the quirks for them. [Test] After applying the quirk, the LEDs/function are work good on 1) HP ZBook Fury 17.3 Inch G8 Mobile Workstation PC 2) HP ZBook Fury 15.6 Inch G8 Mobile Workstation PC 3) HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC 4) HP EliteBook 855 G8 Notebook PC [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs/function will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1930707/+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 1929803] Re: CirrusLogic: The default input volume is "0%" on Dell Warlock
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Hirsute)
Importance: High => Medium
** Changed in: linux (Ubuntu Impish)
Importance: High => Medium
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1929803
Title:
CirrusLogic: The default input volume is "0%" on Dell Warlock
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Fix Committed
Status in linux-oem-5.10 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
On some platforms with Cirrus CS8409 audio codec, DMIC volume default
value in kernel driver is 0, which follows no audio sound will be played
during installation and OOBE until being explicitly configured again via
GNOME Settings GUI or other methods.
[Fix]
Commit 527ff9550682 ("ALSA: hda/cirrus: Set Initial DMIC volume to -26
dB") currently landed in upstream tiwai/sound.git is required to address
this issue. It's a follow-up of commit 0e853a9c3937 ("ALSA: hda/cirrus:
Set Initial DMIC volume for Bullseye to -26 dB"), which is applied in
bug 1923557.
[Test Case]
Try to remove all the user space settings caches and reboot. The
detailed steps are:
# reboot to another system with access, e.g. livecd
livecd$ sudo mount /dev/nvme0n1p3 /mnt
livecd$ sudo rm /mnt/var/lib/alsa/asound.state
livecd$ sudo rm -rf /mnt/home/u/.config/pulse
livecd$ sudo reboot # reboot back
The original status is like:
$ amixer sget 'Internal Mic',0
Simple mixer control 'Internal Mic',0
Capabilities: cvolume cswitch
Capture channels: Front Left - Front Right
Limits: Capture 0 - 63
Front Left: Capture 0 [0%] [-51.00dB] [off]
Front Right: Capture 0 [0%] [-51.00dB] [off]
Expect 40% in the front left/right capture volumes.
$ amixer -c 1 sget 'Internal Mic',0
Simple mixer control 'Internal Mic',0
Capabilities: cvolume cswitch
Capture channels: Front Left - Front Right
Limits: Capture 0 - 63
Front Left: Capture 25 [40%] [-26.00dB] [on]
Front Right: Capture 25 [40%] [-26.00dB] [on]
[Where problems could occur]
This gives the default value of Cirrus CS8409 audio codec capture volume.
It was previously found on another platform, Bullseye, and fixed in bug
1923557, while latterly convinced being a common bug that should be
fixed without the quirk.
[Other Info]
By SRU we skipped a couple of refactoring changes in asound upstream
tree, so additional changes to the original patch are required to
backport. On v5.12 and on, say unstable, the fix can be cleanly
cherry-picked.
== original bug report ==
This is a similar bug to bug 1923557, which happens on Dell Bullseye. The
initial default input volume right after Ubuntu installation is set to 0% while
16% is expected.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: u 1519 F pulseaudio
/dev/snd/controlC0: u 1519 F pulseaudio
CasperMD5CheckResult: skip
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-proposed-release+X114
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-05-26 (5 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
MachineType: Dell Inc. Inspiron 15 3515
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1028-oem
root=UUID=dcda93ce-c1ec-4c02-9098-31756821d54d ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.10.0-1028.29-oem 5.10.35
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.10.0-1028-oem N/A
linux-backports-modules-5.10.0-1028-oem N/A
linux-firmware 1.187.12
Tags: focal
Uname: Linux 5.10.0-1028-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpl
[Kernel-packages] [Bug 1912511] Re: [SRU] Add support for E810 NIC to Ice Driver in Focal
** Changed in: 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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1912511 Title: [SRU] Add support for E810 NIC to Ice Driver in Focal Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [Impact] The Intel Ice driver in 5.4 does not contain the PCIIDs necessary to allow the driver to see the E810 network cards. Without this, users running Focal GA will be unable to deploy Ubuntu via MAAS, or use these cards at all post-install when installing from an ISO. The patch to resolve this landed in Groovy, so this should be a pretty straightforward pick to 5.4. The patch set is small. [Test Case] This is easily reproducible by simply trying to install Focal onto a system with an E810 NIC. The NIC is not recognized and thus is not configurable or usable. [Where problems could occur] All this patch does is add PCI ID information for E810 to the driver to enable a wider set of cards to be used. Problems should not involve regressions to existing supported hardware, if anything the biggest issue could be discovering that after adding the PCI IDs, further patches are necessary to fully enable support in the Ice driver. [Other Info] This was reported by a hardware partner and blocks certification for systems that use E810 based NICs as their primary network devices. Git repository: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/lp_1912511_e810_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912511/+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 1930976] Re: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
Hey Bas, I just found out how to fix it. sudo apt install --reinstall nvidia-driver-460 Works for me, good luck! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930976 Title: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers Status in linux-hwe-5.8 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Kernel: 5.8.0-55 The last kernel destroyed my Ubuntu 20.04.02 installation, something went wrong with some kernel packages. It seems like Ubuntu is unable to find my video card correctly and the device drivers from Nvidia don't seem to work anymore. I had to do a clean installation, but even that doesn't solve the problem. I think this is a serious issue that needs to be looked into. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jun 5 16:50:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation Device [10de:2206] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:403f] InstallationDate: Installed on 2021-06-05 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=4984fe2f-d45f-4734-884c-2426bcf10ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33j dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33j:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1930976/+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 1839912] Re: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED"
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839912 Title: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED" Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] test_maps bpf selftests is failing on bionic. [Regression potential] Kernel is not changed, but test may give a false pass with this change. [Test case] The fixed test has been run on the kernel in -proposed, and passes. After building it, just run ./test_maps from tools/testing/selftests/bpf/. -- This is at lease a test case regression with the proposed kernel: selftests: test_maps Allowed update sockmap '0:3' not in ESTABLISHED not ok 1..3 selftests: test_maps [FAIL] But with older kernel: selftests: test_maps test_maps: OK ok 1..3 selftests: test_maps [PASS] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 13 03:42 seq crw-rw 1 root audio 116, 33 Aug 13 03:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Aug 13 03:52:52 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839912/+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 1829978] Re: cpuacct_100_100 from controllers test suite in LTP failed
AWS t2.small (1 CPU, 2 GB RAM) fails the same on focal/linux-aws 5.4.0-1045-aws: cpuacct 1 TINFO: timeout per run is 0h 5m 0s cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes /home/ubuntu/ltp-install/testcases/bin/cpuacct.sh: 0: Cannot fork -- 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/1829978 Title: cpuacct_100_100 from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Bug description: startup='Wed May 22 06:50:45 2019' cpuacct 1 TINFO: timeout per run is 0h 5m 0s cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes /opt/ltp/testcases/bin/cpuacct.sh: -2110094999: /opt/ltp/testcases/bin/cpuacct.sh: Cannot fork tag=cpuacct_100_100 stime=1558507845 dur=9 exit=exited stat=2 core=no cu=30 cs=53 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 06:59:27 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829978/+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 1930976] Re: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
my problem is same with Bas which is after I updated to that kernel. I cannot go to the desktop and I have to reimage my PC and downgrade my kernel for this. Do you mean you update that driver via recovery mode on the GRUB bootloader? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930976 Title: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers Status in linux-hwe-5.8 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Kernel: 5.8.0-55 The last kernel destroyed my Ubuntu 20.04.02 installation, something went wrong with some kernel packages. It seems like Ubuntu is unable to find my video card correctly and the device drivers from Nvidia don't seem to work anymore. I had to do a clean installation, but even that doesn't solve the problem. I think this is a serious issue that needs to be looked into. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jun 5 16:50:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation Device [10de:2206] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:403f] InstallationDate: Installed on 2021-06-05 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=4984fe2f-d45f-4734-884c-2426bcf10ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33j dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33j:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1930976/+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 1829978] Re: cpuacct_100_100 from controllers test suite in LTP failed
AWS t3.xlarge (4 CPU, 16 GB RAM) is fine. If booted with maxcpus=1 - still works. If booted with mem=2048M, it fails the same as t2.small. -- 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/1829978 Title: cpuacct_100_100 from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Bug description: startup='Wed May 22 06:50:45 2019' cpuacct 1 TINFO: timeout per run is 0h 5m 0s cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes /opt/ltp/testcases/bin/cpuacct.sh: -2110094999: /opt/ltp/testcases/bin/cpuacct.sh: Cannot fork tag=cpuacct_100_100 stime=1558507845 dur=9 exit=exited stat=2 core=no cu=30 cs=53 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 06:59:27 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829978/+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 1829978] Re: cpuacct_100_100 from controllers test suite in LTP failed
** Changed in: ubuntu-kernel-tests Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829978 Title: cpuacct_100_100 from controllers test suite in LTP failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Bug description: startup='Wed May 22 06:50:45 2019' cpuacct 1 TINFO: timeout per run is 0h 5m 0s cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes /opt/ltp/testcases/bin/cpuacct.sh: -2110094999: /opt/ltp/testcases/bin/cpuacct.sh: Cannot fork tag=cpuacct_100_100 stime=1558507845 dur=9 exit=exited stat=2 core=no cu=30 cs=53 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 06:59:27 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829978/+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 1929516] Re: Failed to load DMC firmware i915/adls_dmc_ver2_01.bin
Committed, to be released in 1.187.15 or later.
** Changed in: linux-firmware (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1929516
Title:
Failed to load DMC firmware i915/adls_dmc_ver2_01.bin
Status in OEM Priority Project:
New
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Focal:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
It shows the firmware is missing, and runtime power management has been
disabled.
i915 :00:02.0: vgaarb: deactivate vga console
i915 :00:02.0: vgaarb: changed VGA decodes:
olddecodes=io+mem,decodes=io+mem:owns=io+mem
i915 :00:02.0: Direct firmware load for i915/adls_dmc_ver2_01.bin
failed with error -2
i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adls_dmc_ver2_01.bin. Disabling runtime power management.
i915 :00:02.0: [drm] DMC firmware homepage:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
[Fix]
cherry picked from linux-firmware commit 348d8a97 ("i915: Add DMC v2.01 for
ADL-S").
[Test]
Verified on Intel SDP
[Where problems could occur]
It's a new firmware for new GPU, not possible to introduce regressions.
[Other Info]
Impish has this already. And while ADL-S support begins since v5.13, only
focal (for oem-5.13) will be nominated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1929516/+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 1829978] Re: cpuacct_100_100 from controllers test suite in LTP failed
Sent patch upstream (LTP): https://lists.linux.it/pipermail/ltp/2021-June/023132.html -- 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/1829978 Title: cpuacct_100_100 from controllers test suite in LTP failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Bug description: startup='Wed May 22 06:50:45 2019' cpuacct 1 TINFO: timeout per run is 0h 5m 0s cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes /opt/ltp/testcases/bin/cpuacct.sh: -2110094999: /opt/ltp/testcases/bin/cpuacct.sh: Cannot fork tag=cpuacct_100_100 stime=1558507845 dur=9 exit=exited stat=2 core=no cu=30 cs=53 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 06:59:27 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.4/5.4.0.75.84~18.04.68)
All autopkgtests for the newly accepted linux-meta-hwe-5.4 (5.4.0.75.84~18.04.68) for bionic have finished running. The following regressions have been reported in tests triggered by the package: virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (i386, amd64) zfs-linux/0.7.5-1ubuntu16.11 (s390x, arm64, amd64, ppc64el) virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (i386, amd64) asic0x/1.0.1-1 (s390x) kpatch/0.5.0-0ubuntu1.1 (amd64) v4l2loopback/0.10.0-1ubuntu1.2 (s390x) lxc/3.0.3-0ubuntu1~18.04.1 (i386, s390x, arm64, amd64, ppc64el) systemd/237-3ubuntu10.47 (armhf) acpi-call/1.1.0-4 (s390x, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-hwe-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930707] Re: Mic-mute/mute LEDs not work on some HP platforms
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930707 Title: Mic-mute/mute LEDs not work on some HP platforms Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on 1) HP ZBook Fury 17.3 Inch G8 Mobile Workstation PC 2) HP ZBook Fury 15.6 Inch G8 Mobile Workstation PC 3) HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC 4) HP EliteBook 855 G8 Notebook PC The right channel of internal speaker doesn't work on 1) HP ZBook Fury 17.3 Inch G8 Mobile Workstation PC 2) HP ZBook Fury 15.6 Inch G8 Mobile Workstation PC 3) HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC [Fix] These four platforms need specific quirk for different hardware layout. Thus, add the quirks for them. [Test] After applying the quirk, the LEDs/function are work good on 1) HP ZBook Fury 17.3 Inch G8 Mobile Workstation PC 2) HP ZBook Fury 15.6 Inch G8 Mobile Workstation PC 3) HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC 4) HP EliteBook 855 G8 Notebook PC [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs/function will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1930707/+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 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
My bad. The USB VID/PID seem to be incorrect in my quirk. Please try https://people.canonical.com/~mschiu77/lp1927545/v3 and post me the output when pressing Fn+F4. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I found that some of the Lenovo Lenovo Essential Wireless Keyboard Fn keys don't work. First one is Mute mic (Fn+F4), second one is Scissors (Fn+F10, probably hotkey for Windows Snipping Tool for selective screenshot).gnome-control-panel, xev and evtest doesn't react on pressing these buttons. Here what I was able to get via sudo cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"' : For Mute key 00 00 00 FF DC 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 For Scissors 00 00 00 FF DB 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asudak 2085 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 6 22:36:50 2021 InstallationDate: Installed on 2021-04-13 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-18 (17 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+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 1931497] Re: Patch To Fix Bug in the Linux Block Layer Responsible For Merging BIOs
** Also affects: linux-azure (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Groovy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1931497
Title:
Patch To Fix Bug in the Linux Block Layer Responsible For Merging
BIOs
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Focal:
New
Status in linux-azure source package in Groovy:
New
Status in linux-azure source package in Hirsute:
New
Status in linux-azure source package in Impish:
New
Bug description:
There is a bug in the Linux block layer responsible for merging BIOs
that go across the page boundary. This bug was introduced in Linux 5.1
when the block layer BIO page tracking is enhanced to support multiple
pages.
Without this patch, data corruption can occur. The change to the
kernel block layer in Linux 5.1 changes the way multiple pages are
merged to a single block I/O descriptor, and how contiguous block I/O
descriptors are merged with previous descriptors.
If contiguous block I/O requests cross a page boundary of 4k, defined
by the hv_storvsc driver, the new block merge process can create two
pages of block I/O requests (the latter page with an offset) that
refer to the same physical sector on disk. This page list is then
assembled for the SCSI generic driver.
In the above scenario, when the block I/O request sizes are 512 bytes,
the Azure LIS driver (hv_storvsc module) is not able to correctly
parse the page array from the SCSI generic driver due to this bug in
Linux block layer and creates a potential overflow of offset I/O
requests and corruption of data on disk.
Mitigation of data loss is proven with filesystems with block size 4k.
When block I/O requests are of sizes 4k or multiples of 4k, they are
the page aligned in the memory and are not affected by the block I/O
merging algorithm introduced in Linux 5.1. Most modern file systems
use 4k I/O block size by default, thus mitigating this problem.
We have submitted a patch to Linux mainline kernel to fix this:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-
block.git/commit/?h=for-
next&id=c9c9762d4d44dcb1b2ba90cfb4122dc11ceebf31
c9c9762d4d44 ("block: return the correct bvec when checking for gaps")
Please include this patch in any supported kernels that are 5.1 or
later.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1931497/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931565] [NEW] pull in latest thermald bug fixes into thermald 2.4.3
Public bug reported: The upstream thermald 2.4.6 has been released with some more bug fixes that are pertinent to H/W available in older releases. Pull in these fixes: >From 2.4.6: commit 273a53a11da2a7302ad7a5bc7e3bf04f221ce4e2 Author: Srinivas Pandruvada Date: Mon Jun 7 16:47:47 2021 -0700 Use Adaptive PPCC limits for RAPL MMIO Set the correct device name as RAPL-MSR so that RAPL-MMIO can also set the correct default power limits. commit 2dd67300448fa4a2aa8f3e00ee5b604c73a1f7d9 Author: Srinivas Pandruvada Date: Mon Jun 7 16:45:14 2021 -0700 Increase power limit for disabled RAPL-MMIO Increase 100W to 200W as some desktop platform already have limit more than 100W. commit 3de1004a49d0d157573bbdc1097b2fbed056879f Author: Srinivas Pandruvada Date: Sun Jun 6 19:19:15 2021 -0700 Special case for default PSVT When there are no adaptive tables and only one default PSVT table is present with just one entry with MAX type. Add one additional entry as done for non default case. >From 2.4.5: commit 301a89284e9d74a9a1f8315c1673a548dcacda8c Author: Srinivas Pandruvada Date: Sat May 29 10:50:44 2021 -0700 Set a very high RAPL MSR PL1 with --adaptive After upgrading Dell Latitude 5420, again noticed performance degradation. The PPCC power limit for MSR RAPL PL1 is reduced to 15W. Even though we disable MSR RAPL with --adaptive option, it is not getting disabled. So MSR RAPL limits still playing role. To fix that set a very high MSR RAPL PL1 limit so that it never causes throttling. All throttling with --adaptive option is done using RAPL-MMIO. >From 2.4.4: commit ea4491971059259e46daad10ae850d3d530b02f2 Author: Srinivas Pandruvada Date: Thu Mar 11 10:06:15 2021 -0800 Fix error for condition names The current code caps the max name as the last condition name, which is "Power_Slider". So any condition more than 56 will be printing error, with "Power_Slider" as condition name. For example for condition = 57: Unsupported condition 57 (Power_slider) This is confusing during debug, so print "UNKNOWN" for condition name 56. commit 9115f2fb0b296a22a62908f2718ca873af2a452f Author: Srinivas Pandruvada Date: Tue Mar 9 16:36:13 2021 -0800 This is confusing during debug, so print "UNKNOWN" for condition name 56. commit 9115f2fb0b296a22a62908f2718ca873af2a452f Author: Srinivas Pandruvada Date: Tue Mar 9 16:36:13 2021 -0800 Check for alternate names for B0D4 device B0D4 can be named as TCPU or B0D4. So search for both names if failed to find one. commit 660ee6f1f6351e6c291c0699147231be402c2bb8 Author: Srinivas Pandruvada Date: Tue Mar 9 16:33:08 2021 -0800 Delete all trips from zones before psvt install Initially zones has all the trips from sysfs, which may have wrong settings. Instead of deleting only for matched psvt zones, delete for all zones. In this way only zones which are in PSVT will be present. commit 1ad03424f7f3d339521635f08377b323375b2747 Author: Srinivas Pandruvada Date: Tue Mar 9 11:36:27 2021 -0800 Disable legacy rapl cdev when rapl-mmio is in use Explicitly disable legacy rapl based on MSR interface when rapl-mmio is in use. This will prevent PL1/PL2 power limit from MSR based rapl, which may not be the correct one. commit 9b5c7a45021a5376be98d88b903daeb2d5f30ac4 Merge: 9e731de 45832e1 Author: Srinivas Pandruvada <3802550+spandruv...@users.noreply.github.com> Date: Thu Apr 1 12:09:54 2021 -0700 Merge pull request #295 from ColinIanKing/master Fix spelling mistakes found using codespell commit 45832e16290fec7353513b1ce03533b73b18f0c6 Author: Colin Ian King Date: Thu Mar 18 11:22:38 2021 + Fix spelling mistakes found using codespell There are a handful of spelling mistakes in comments and literal strings found by codespell. Fix these. Signed-off-by: Colin Ian King ** Affects: thermald (Ubuntu) Importance: Medium Assignee: Colin Ian King (colin-king) Status: In Progress ** Changed in: thermald (Ubuntu) Importance: Undecided => Medium ** Changed in: thermald (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: thermald (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1931565 Title: pull in latest thermald bug fixes into thermald 2.4.3 Status in thermald package in Ubuntu: In Progress Bug description: The upstream thermald 2.4.6 has been released with some more bug fixes that are pertinent to H/W available in older releases. Pull in these fixes: From 2.4.6: commit 273a53a11da2a7302ad7a5bc7e3bf04f221ce4e2 Author: Srinivas Pandruvada Date: Mon Jun 7 16:47:47 2021 -0700 Use Ad
[Kernel-packages] [Bug 1930100] Re: selftests/net/bpf - Failure in building bpf program on G/RISC-V (kernel 5.8)
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Krzysztof Kozlowski (krzk) -- 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/1930100 Title: selftests/net/bpf - Failure in building bpf program on G/RISC-V (kernel 5.8) Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Confirmed Bug description: I found the following failure in G/RISC-V, cycle sru-20210510 : 21:07:11 ERROR| [stderr] progs/test_vmlinux.c:24:18: error: use of undeclared identifier '__NR_nanosleep' 21:07:11 ERROR| [stderr] if (args->id != __NR_nanosleep) 21:07:11 ERROR| [stderr] ^ [...] 21:07:11 ERROR| [stderr] progs/test_vmlinux.c:60:12: error: use of undeclared identifier '__NR_nanosleep' 21:07:11 ERROR| [stderr] if (id != __NR_nanosleep) 21:07:11 ERROR| [stderr] ^ 21:07:11 ERROR| [stderr] progs/test_vmlinux.c:63:15: warning: implicit declaration of function 'PT_REGS_PARM1_CORE' is invalid in C99 [-Wimplicit-function-declaration] 21:07:11 ERROR| [stderr] ts = (void *)PT_REGS_PARM1_CORE(regs); 21:07:11 ERROR| [stderr] ^ [...] /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_tracing.h:298:29: note: expanded from macro '___bpf_concat' 21:07:12 ERROR| [stderr] #define ___bpf_concat(a, b) a ## b 21:07:12 ERROR| [stderr] ^ 21:07:12 ERROR| [stderr] :28:1: note: expanded from here 21:07:12 ERROR| [stderr] ___bpf_kprobe_args3 21:07:12 ERROR| [stderr] ^ 21:07:12 ERROR| [stderr] /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_tracing.h:359:29: note: expanded from macro '___bpf_kprobe_args3' 21:07:12 ERROR| [stderr] ___bpf_kprobe_args2(args), (void *)PT_REGS_PARM3(ctx) 21:07:12 ERROR| [stderr] ^~ 21:07:12 ERROR| [stderr] 10 warnings and 3 errors generated. 21:07:12 ERROR| [stderr] llc: error: llc: :1:1: error: expected top-level entity 21:07:12 ERROR| [stderr] BPF obj compilation failed 21:07:12 ERROR| [stderr] ^ 21:07:12 ERROR| [stderr] make[1]: *** [Makefile:376: /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/test_vmlinux.o] Error 1 21:07:12 ERROR| [stderr] make: *** [Makefile:159: all] Error 2 21:07:12 ERROR| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py", line 239, in run_once utils.system(cmd) File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system verbose=verbose).exit_status File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=2, Command returned non-zero exit status * Command: make -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= KDIR=/usr/src/linux-headers-5.8.0-26-generic Exit status: 2 See more on the attachment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1930100/+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 1894964] Re: Unable to build ubuntu_bpf test on Groovy 5.8 KVM kernel / F-5.8-hwe (blocking net test in ubuntu_kernel_selftests to build)
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Krzysztof Kozlowski (krzk) -- 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/1894964 Title: Unable to build ubuntu_bpf test on Groovy 5.8 KVM kernel / F-5.8-hwe (blocking net test in ubuntu_kernel_selftests to build) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Confirmed Bug description: Issue found on 5.8.0-1001.1 - kvm Test build failed with: Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs from latest version at 'include/uapi/linux/netlink.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' In file included from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:5, from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/kernel.h:8, from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.h:10, from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c:8: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c: In function ‘__func_get_name’: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:37:38: warning: nested extern declaration of ‘__compiletime_assert_0’ [-Wnested-externs] 37 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) | ^ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:16:15: note: in definition of macro ‘__compiletime_assert’ 16 | extern void prefix ## suffix(void) __compiletime_error(msg); \ | ^~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:37:2: note: in expansion of macro ‘_compiletime_assert’ 37 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) | ^~~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:39:37: note: in expansion of macro ‘compiletime_assert’ 39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg) | ^~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:50:2: note: in expansion of macro ‘BUILD_BUG_ON_MSG’ 50 | BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition) | ^~~~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c:20:2: note: in expansion of macro ‘BUILD_BUG_ON’ 20 | BUILD_BUG_ON(ARRAY_SIZE(func_id_str) != __BPF_FUNC_MAX_ID); | ^~~~ libbpf: failed to open format: No such file or directory Error: failed to load BTF from format: No such file or directory make[1]: *** [Makefile:190: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/vmlinux.h] Error 2 make[1]: *** Deleting file '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/vmlinux.h' make: *** [Makefile:157: all] Error 2 Please find attachment for the complete build log. As the ubuntu_kernel_selftests needs bpf to be built first, this will block the ubuntu_kernel_selftests/net to build as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1894964/+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 1931565] Re: pull in latest thermald bug fixes into thermald 2.4.3
** Description changed: + == SRU Justification [ HIRSUTE ] == + The upstream thermald 2.4.6 has been released with some more bug fixes - that are pertinent to H/W available in older releases. Pull in these - fixes: + that are pertinent to H/W available in older releases such as Hirsute. + These fix a variety of issues found on H/W in the field and such as + over-throttling, handling alternate ACPI object names for B0D4, handling + trip zones which may have wrong settings and disabling the legacy rapl + cdev when rapl-mmio is available. + + == The fixes == + + Pull in these fixes: From 2.4.6: commit 273a53a11da2a7302ad7a5bc7e3bf04f221ce4e2 Author: Srinivas Pandruvada Date: Mon Jun 7 16:47:47 2021 -0700 - Use Adaptive PPCC limits for RAPL MMIO - - Set the correct device name as RAPL-MSR so that RAPL-MMIO can - also set the correct default power limits. + Use Adaptive PPCC limits for RAPL MMIO + + Set the correct device name as RAPL-MSR so that RAPL-MMIO can + also set the correct default power limits. commit 2dd67300448fa4a2aa8f3e00ee5b604c73a1f7d9 Author: Srinivas Pandruvada Date: Mon Jun 7 16:45:14 2021 -0700 - Increase power limit for disabled RAPL-MMIO - - Increase 100W to 200W as some desktop platform already have limit - more than 100W. + Increase power limit for disabled RAPL-MMIO + + Increase 100W to 200W as some desktop platform already have limit + more than 100W. commit 3de1004a49d0d157573bbdc1097b2fbed056879f Author: Srinivas Pandruvada Date: Sun Jun 6 19:19:15 2021 -0700 - Special case for default PSVT - - When there are no adaptive tables and only one default PSVT table - is present with just one entry with MAX type. Add one additional - entry as done for non default case. - + Special case for default PSVT + + When there are no adaptive tables and only one default PSVT table + is present with just one entry with MAX type. Add one additional + entry as done for non default case. + From 2.4.5: commit 301a89284e9d74a9a1f8315c1673a548dcacda8c Author: Srinivas Pandruvada Date: Sat May 29 10:50:44 2021 -0700 - Set a very high RAPL MSR PL1 with --adaptive - - After upgrading Dell Latitude 5420, again noticed performance degradation. - The PPCC power limit for MSR RAPL PL1 is reduced to 15W. Even though we - disable MSR RAPL with --adaptive option, it is not getting disabled. So - MSR RAPL limits still playing role. - - To fix that set a very high MSR RAPL PL1 limit so that it never causes - throttling. All throttling with --adaptive option is done using RAPL-MMIO. + Set a very high RAPL MSR PL1 with --adaptive + + After upgrading Dell Latitude 5420, again noticed performance degradation. + The PPCC power limit for MSR RAPL PL1 is reduced to 15W. Even though we + disable MSR RAPL with --adaptive option, it is not getting disabled. So + MSR RAPL limits still playing role. + + To fix that set a very high MSR RAPL PL1 limit so that it never causes + throttling. All throttling with --adaptive option is done using RAPL-MMIO. From 2.4.4: commit ea4491971059259e46daad10ae850d3d530b02f2 Author: Srinivas Pandruvada Date: Thu Mar 11 10:06:15 2021 -0800 - Fix error for condition names - - The current code caps the max name as the last condition name, - which is "Power_Slider". So any condition more than 56 will be - printing error, with "Power_Slider" as condition name. For example - for condition = 57: - Unsupported condition 57 (Power_slider) - - This is confusing during debug, so print "UNKNOWN" for condition - name 56. + Fix error for condition names + + The current code caps the max name as the last condition name, + which is "Power_Slider". So any condition more than 56 will be + printing error, with "Power_Slider" as condition name. For example + for condition = 57: + Unsupported condition 57 (Power_slider) + + This is confusing during debug, so print "UNKNOWN" for condition + name 56. commit 9115f2fb0b296a22a62908f2718ca873af2a452f Author: Srinivas Pandruvada Date: Tue Mar 9 16:36:13 2021 -0800 - - This is confusing during debug, so print "UNKNOWN" for condition - name 56. + This is confusing during debug, so print "UNKNOWN" for condition + name 56. commit 9115f2fb0b296a22a62908f2718ca873af2a452f Author: Srinivas Pandruvada Date: Tue Mar 9 16:36:13 2021 -0800 - Check for alternate names for B0D4 device - - B0D4 can be named as TCPU or B0D4. So search for both names - if failed to find one. + Check for alternate names for B0D4 device + + B0D4 can be named as TCPU or B0D4. So search for both names + if failed to find one. commit 660ee6f1f6351e6c291c0699147231be402c2bb8 Author: Srinivas Pa
[Kernel-packages] [Bug 1907262] Re: raid10: discard leads to corrupted file system
Hi Matthew, Thanks for your effort to add this feature to the Ubuntu kernels. I installed linux-image-5.4.0-75-generic on 2021-06-08. Neither during normal work nor during manual fstrim any problems so far. Best regards, Thimo -- 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/1907262 Title: raid10: discard leads to corrupted file system Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: Seems to be closely related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 After updating the Ubuntu 18.04 kernel from 4.15.0-124 to 4.15.0-126 the fstrim command triggered by fstrim.timer causes a severe number of mismatches between two RAID10 component devices. This bug affects several machines in our company with different HW configurations (All using ECC RAM). Both, NVMe and SATA SSDs are affected. How to reproduce: - Create a RAID10 LVM and filesystem on two SSDs mdadm -C -v -l10 -n2 -N "lv-raid" -R /dev/md0 /dev/nvme0n1p2 /dev/nvme1n1p2 pvcreate -ff -y /dev/md0 vgcreate -f -y VolGroup /dev/md0 lvcreate -n root-L 100G -ay -y VolGroup mkfs.ext4 /dev/VolGroup/root mount /dev/VolGroup/root /mnt - Write some data, sync and delete it dd if=/dev/zero of=/mnt/data.raw bs=4K count=1M sync rm /mnt/data.raw - Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (should be 0): cat /sys/block/md0/md/mismatch_cnt - Trigger the bug fstrim /mnt - Re-Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (probably in the range of N*1): cat /sys/block/md0/md/mismatch_cnt After investigating this issue on several machines it *seems* that the first drive does the trim correctly while the second one goes wild. At least the number and severity of errors found by a USB stick live session fsck.ext4 suggests this. To perform the single drive evaluation the RAID10 was started using a single drive at once: mdadm --assemble /dev/md127 /dev/nvme0n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root vgchange -a n /dev/VolGroup mdadm --stop /dev/md127 mdadm --assemble /dev/md127 /dev/nvme1n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root When starting these fscks without -n, on the first device it seems the directory structure is OK while on the second device there is only the lost+found folder left. Side-note: Another machine using HWE kernel 5.4.0-56 (after using -53 before) seems to have a quite similar issue. Unfortunately the risk/regression assessment in the aforementioned bug is not complete: the workaround only mitigates the issues during FS creation. This bug on the other hand is triggered by a weekly service (fstrim) causing severe file system corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+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 1931574] [NEW] Lost network connection, seems like an older kernel bug
Public bug reported: I experience what seems the exact copy of the issue here after I have connected my Dell laptop to a Dell Monitor with an embedded Ethernet over USB-C/Thunderbolt (and USB-B High Speed Upstream Cable). Suddenly no network connection and it can not be restored for a long time or until reboot. https://bugzilla.kernel.org/show_bug.cgi?id=95711 [350895.699185] INFO: task kworker/3:1:11823 blocked for more than 120 seconds. [350895.699192] Tainted: G U W OE4.15.0-43-generic #46-Ubuntu [350895.699195] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [350895.699198] kworker/3:1 D0 11823 2 0x8000 [350895.699212] Workqueue: events rtl_work_func_t [r8152] [350895.699215] Call Trace: [350895.699224] __schedule+0x291/0x8a0 [350895.699228] schedule+0x2c/0x80 [350895.699232] rpm_resume+0x108/0x7d0 [350895.699237] ? wait_woken+0x80/0x80 [350895.699240] rpm_resume+0x584/0x7d0 [350895.699245] ? __switch_to_asm+0x34/0x70 [350895.699249] ? __switch_to_asm+0x40/0x70 [350895.699252] ? __switch_to_asm+0x34/0x70 [350895.699256] ? __switch_to_asm+0x40/0x70 [350895.699259] ? __switch_to_asm+0x34/0x70 [350895.699263] __pm_runtime_resume+0x4e/0x80 [350895.699267] usb_autopm_get_interface+0x22/0x60 [350895.699272] rtl_work_func_t+0x70/0x41e [r8152] [350895.699277] process_one_work+0x1de/0x410 [350895.699280] worker_thread+0x32/0x410 [350895.699285] kthread+0x121/0x140 [350895.699288] ? process_one_work+0x410/0x410 [350895.699292] ? kthread_create_worker_on_cpu+0x70/0x70 [350895.699297] ? do_syscall_64+0x73/0x130 [350895.699300] ? SyS_exit+0x17/0x20 [350895.699304] ret_from_fork+0x35/0x40 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 4820 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jun 10 14:49:39 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=adfb1128-00d7-41b1-be85-1d224e4ddd57 InstallationDate: Installed on 2018-12-31 (891 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=0807f9b3-f643-40c3-8e0c-ae2e30161acc ro locale=en_US quiet splash i915.modeset=1 i915.enable_rc6=1 i915.enable_fbc=1 i915.enable_guc_loading=1 i915.enable_guc_submission=1 i915.enable_huc=1 i915.enable_psr=1 i915.disable_power_well=0 i915.semaphores=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.20 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.15.1 dmi.board.name: 0PF86Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.15.1:bd03/09/2021:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1931574 Title: Lost network connection, seems like an older kernel bug Status in linux package in Ubuntu: New Bug description: I experience what seems the exact copy of the issue here after I have connected my Dell laptop to a Dell Monitor with an embedded Ethernet over USB-C/Thunderbolt (and USB-B High Speed Upstream Cable). Suddenly no network connection and it can not be restored for a long time or until reboot. https://bugzilla.kernel.org/show_bug.cgi?id=95711 [350895.699185] INFO: task kworker/3:1:11823 blocked for more than 120 seconds. [350895.699192] Tainted: G U W OE4.15.0-43-generic #46-Ubuntu [350895.699195] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [350895.699198] kworker/3:1 D0 11823 2 0x8000 [350895.699212] Workqueue: events rtl_work_func_t [r8152] [350895.699215] Call Trace: [350895.699224] __schedule+0x291/0x8a0 [350895.699228] schedule+0x2c/0x80 [350895.699232] rpm_resume+0x108/0x7d0 [350895.699237] ? wait_woken+0x80/0x80 [350895.699240] rpm_resume+0x584/
[Kernel-packages] [Bug 1931475] Re: Ubuntu only stable in safe graphics mode
This may not be accurate. To get a working computer, I ended up putting an old Nvidia gt630 card in. That works fine. However in an effort to get this logs, Ubuntu no longer even boots into the GUI if i remove that card. I can get to the Grub Menu, but it reboots at that point if I try and load Ubuntu normally . Safe Graphics mode still works though. ** Attachment added: "prevboot1.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931475/+attachment/5503870/+files/prevboot1.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/1931475 Title: Ubuntu only stable in safe graphics mode Status in linux package in Ubuntu: Incomplete Bug description: Brand new machine, Intel i5, Brand new install of 20.04 ubuntu using 5.11.0-18 kernel. BIOS updated to recent firmware. (5/11/2021 date) Machine will only stay running in safe graphics mode. When booting normal, GUI loads for about 5 seconds then reboots. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 9 14:04:22 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-06-09 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard SK-8115 Bus 001 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 7: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=5e92baa8-faf7-43e0-ab03-c43a1ec8a549 ro recovery nomodeset dis_ucode_ldr text SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2021 dmi.bios.release: 16.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1605 dmi.board.asset.tag: Default string dmi.board.name: PRIME B460-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1605:bd04/07/2021:br16.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB460-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.apport.crashdb.conf: 2021-06-09T13:25:26.012453 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931475/+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 1930980] Re: Hang on loading initial ramdisk on kernels 5.4.0-72+, 5.11.0-16+ with nvidia drivers 440+
I'm not sure I have the same bug, but since early June every time I plug my display port stuff in my computer freezes... I also have a lot going on in my dmesg ** Attachment added: "dmesg errors" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930980/+attachment/5503869/+files/display%20port%20plugged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930980 Title: Hang on loading initial ramdisk on kernels 5.4.0-72+, 5.11.0-16+ with nvidia drivers 440+ Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in nvidia-graphics-drivers-465 package in Ubuntu: New Bug description: Affected Ubuntu Versions: Release: 20.04 Kernel: 5.4.0-73,74 Nvidia Driver: 440,450,460,465 Kernel: 5.4.0-72 Nvidia Driver: 460, 465 Release: 21.04 Kernel: 5.11.0-16,18 Nvidia Driver: 440, 450, 460, 465 For 21.04 with all kernels, driver 390 works correctly Issue occurs during bootup where after starting to load the initial ramdisk, the system hangs indefinitely with no output. Booting in recovery mode and examining the logs, there is a series of bug messages. Updating motherboard bios to latest had no effect. Note: This exact hardware setup worked as recently as June 2, 2021 on ubuntu 20.04. After applying the latest set of OS updates and rebooting, the issue began occurring. Trace follows: Jun 4 21:51:06 ultra kernel: [7.262411] BUG: kernel NULL pointer dereference, address: Jun 4 21:51:06 ultra kernel: [7.262412] #PF: supervisor write access in kernel mode Jun 4 21:51:06 ultra kernel: [7.262413] #PF: error_code(0x0002) - not-present page Jun 4 21:51:06 ultra kernel: [7.262414] PGD 0 P4D 0 Jun 4 21:51:06 ultra kernel: [7.262415] Oops: 0002 [#1] SMP NOPTI Jun 4 21:51:06 ultra kernel: [7.262416] CPU: 3 PID: 998 Comm: Xorg Tainted: P IO 5.11.0-18-generic #19-Ubuntu Jun 4 21:51:06 ultra kernel: [7.262417] Hardware name: ASUS System Product Name/PRIME Z390-A, BIOS 1802 12/01/2020 Jun 4 21:51:06 ultra kernel: [7.262418] RIP: 0010:_nv008453rm+0xa8/0x5f0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.262673] Code: 8b 84 24 60 04 00 00 ba 01 00 00 00 4c 89 e6 48 89 df 4d 89 e5 e8 c8 64 c4 e0 41 89 c6 45 85 f6 0f 84 3c 02 00 00 48 8b 45 08 <4c> 89 28 5b 44 89 f0 41 5c 41 5d 41 5e 41 5f 48 83 c5 40 c3 0f 1f Jun 4 21:51:06 ultra kernel: [7.262675] RSP: 0018:be91018bf8c8 EFLAGS: 00010282 Jun 4 21:51:06 ultra kernel: [7.262676] RAX: RBX: a08c06e14008 RCX: Jun 4 21:51:06 ultra kernel: [7.262676] RDX: 0020 RSI: d9a4 RDI: a08c06e14008 Jun 4 21:51:06 ultra kernel: [7.262677] RBP: a08c0a0c5db0 R08: 0025 R09: a08c0a0c5d18 Jun 4 21:51:06 ultra kernel: [7.262678] R10: a08c06e14008 R11: a08c06e150a0 R12: a08c07440008 Jun 4 21:51:06 ultra kernel: [7.262678] R13: a08c07440010 R14: R15: a08c0a0c5de0 Jun 4 21:51:06 ultra kernel: [7.262679] FS: 7f7d29194a40() GS:a09b2dac() knlGS: Jun 4 21:51:06 ultra kernel: [7.262680] CS: 0010 DS: ES: CR0: 80050033 Jun 4 21:51:06 ultra kernel: [7.262680] CR2: CR3: 00010f6fe006 CR4: 003706e0 Jun 4 21:51:06 ultra kernel: [7.262681] DR0: DR1: DR2: Jun 4 21:51:06 ultra kernel: [7.262681] DR3: DR6: fffe0ff0 DR7: 0400 Jun 4 21:51:06 ultra kernel: [7.262682] Call Trace: Jun 4 21:51:06 ultra kernel: [7.262684] ? _nv032332rm+0x10c/0x280 [nvidia] Jun 4 21:51:06 ultra kernel: [7.262884] ? _nv032330rm+0x145/0x180 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263075] ? _nv014647rm+0x213/0x300 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263255] ? _nv014704rm+0x6dd/0xf80 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263435] ? _nv026937rm+0x226/0x4e0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263616] ? _nv016954rm+0x4a8/0x5e0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263819] ? _nv016956rm+0xdd/0x230 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264009] ? _nv09rm+0xcd/0x1d0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264256] ? _nv022467rm+0x30/0x60 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264394] ? _nv000701rm+0x143f/0x2100 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264552] ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264709] ? nv_open_device+0x122/0x8e0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264805] ? nvi
[Kernel-packages] [Bug 1931475] Re: Ubuntu only stable in safe graphics mode
** Attachment added: "prevboot2.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931475/+attachment/5503871/+files/prevboot2.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/1931475 Title: Ubuntu only stable in safe graphics mode Status in linux package in Ubuntu: Incomplete Bug description: Brand new machine, Intel i5, Brand new install of 20.04 ubuntu using 5.11.0-18 kernel. BIOS updated to recent firmware. (5/11/2021 date) Machine will only stay running in safe graphics mode. When booting normal, GUI loads for about 5 seconds then reboots. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 9 14:04:22 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-06-09 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard SK-8115 Bus 001 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 7: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=5e92baa8-faf7-43e0-ab03-c43a1ec8a549 ro recovery nomodeset dis_ucode_ldr text SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2021 dmi.bios.release: 16.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1605 dmi.board.asset.tag: Default string dmi.board.name: PRIME B460-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1605:bd04/07/2021:br16.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB460-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.apport.crashdb.conf: 2021-06-09T13:25:26.012453 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931475/+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 1904589] Re: zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4
Any chance of a fix for Focal Fossa? I'm seeing this issue crash my
server about 1-2 times per month...
--
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/1904589
Title:
zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Focal:
In Progress
Status in zfs-linux source package in Groovy:
Fix Released
Status in zfs-linux source package in Hirsute:
Fix Released
Bug description:
[Impact]
zfs_write() doesn't properly account partial copies done by
copy_from_user(), causing accesses past the end of objects and
triggering kernel panics.
[Test case]
The problem seems to be workload specific, there is not a specific
test case to reproduce the problem, but the bug seems to be pretty
well identified by the upstream commit reported below.
[Fix]
Apply upstream commit c9e3efdb3a6111b9795becc6594b3c52ba004522
("Bugfix/fix uio partial copies").
[Regression potential]
Upstream commit that is basically fixing potential out-of-bounds
accesses by properly checking partial copies done by copy_from_user()
and preventing kernel panics. Regression potential is minimal: it
seems unlikely to break other things if this change is applied.
[Original bug report]
Using latest zfs 0.8.3-1ubuntu12.4 on latest Ubuntu 20.04.1, I observe
a rare zfs panics that seem to be workload-specific which render a
server mostly unresponsive besides ssh still working. Attempting to
reboot the server in this state makes the shutdown hang forever.
You may want to consider backporting the fix released in zfs 0.8.4
into 20.04: https://github.com/openzfs/zfs/pull/10148
Log sample of panic:
```
Nov 17 16:06:15 hostname kernel: [3385134.716024] PANIC: zfs: accessing past
end of object c1c/2db52f (size=17408 access=7492+16428)
Nov 17 16:06:15 hostname kernel: [3385134.716072] Showing stack for process
3166846
Nov 17 16:06:15 hostname kernel: [3385134.716074] CPU: 25 PID: 3166846 Comm:
node Tainted: P O 5.4.0-48-generic #52-Ubuntu
Nov 17 16:06:15 hostname kernel: [3385134.716075] Hardware name:
Nov 17 16:06:15 hostname kernel: [3385134.716076] Call Trace:
Nov 17 16:06:15 hostname kernel: [3385134.716085] dump_stack+0x6d/0x9a
Nov 17 16:06:15 hostname kernel: [3385134.716097] spl_dumpstack+0x29/0x2b
[spl]
Nov 17 16:06:15 hostname kernel: [3385134.716102] vcmn_err.cold+0x60/0x99
[spl]
Nov 17 16:06:15 hostname kernel: [3385134.716106] ? _cond_resched+0x19/0x30
Nov 17 16:06:15 hostname kernel: [3385134.716108] ?
__kmalloc_node+0x20e/0x330
Nov 17 16:06:15 hostname kernel: [3385134.716113] ?
spl_kmem_alloc_impl+0xa8/0x100 [spl]
Nov 17 16:06:15 hostname kernel: [3385134.716190] ? __list_add+0x17/0x40
[zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716235]
zfs_panic_recover+0x6f/0x90 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716272] ?
dsl_dir_tempreserve_impl.isra.0.constprop.0+0xed/0x330 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716305]
dmu_buf_hold_array_by_dnode+0x3a0/0x490 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716338]
dmu_write_uio_dnode+0x4c/0x140 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716370]
dmu_write_uio_dbuf+0x4f/0x70 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716416] zfs_write+0xa1f/0xd40 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716419] ? d_absolute_path+0x74/0xb0
Nov 17 16:06:15 hostname kernel: [3385134.716421] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716423] ? __switch_to_asm+0x40/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716424] ? __switch_to_asm+0x40/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716425] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716427] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716474]
zpl_write_common_iovec+0xad/0x120 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716567] zpl_iter_write+0x56/0x90
[zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716570] do_iter_write+0x84/0x1a0
Nov 17 16:06:15 hostname kernel: [3385134.716574] ? futex_wake+0x8b/0x180
Nov 17 16:06:15 hostname kernel: [3385134.716577] do_writev+0x71/0x120
Nov 17 16:06:15 hostname kernel: [3385134.716581] do_syscall_64+0x57/0x190
Nov 17 16:06:15 hostname kernel: [3385134.716584] RIP: 0033:0x7fa366eee0cd
Nov 17 16:06:15 hostname kernel: [3385134.716587] RSP: 002b:7fa35e7fbde0
EFLAGS: 0293 ORIG_RAX: 0014
Nov 17 16:06:15 hostname kernel: [3385134.716590] RDX: 000c RSI:
0651c7b0 RDI: 001d
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1904589/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-pac
[Kernel-packages] [Bug 1931576] [NEW] Cloud kernels meta don't provide kernel-testing--*--modules-extra--preferred
Public bug reported: [Impact] ADT sets up the test environment by installing the image and modules-extra package via the virtual provides 'kernel-testing--linux---full--preferred' and 'kernel-testing--linux---modules-extra--preferred'. If those are not available, it falls back to using the real meta names as 'linux-image-' and 'linux-modules-extra-'. The 5.4 cloud kernels in Focal are not providing the virtual packages for 'kernel-testing--linux---modules-extra--preferred'. When the tests falls back to 'linux-modules-extra-', the new 5.8 cloud kernels are pulled for the tests as they are now the default sources. ADT log: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/a/acpi-call/20210609_092540_0a7a8@/log.gz [Fix] The meta packages need to be fixed to provide the necessary virtual packages for testing. [Where problems could occur] Adding new virtual meta packages could clash with existing names provided by other sources. However, if they existed ADT would have pulled them. ** Affects: linux-meta-azure (Ubuntu) Importance: Undecided Status: New ** Affects: linux-meta-azure-5.8 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-meta-azure (Ubuntu Focal) Importance: High Assignee: Kleber Sacilotto de Souza (kleber-souza) Status: New ** Affects: linux-meta-azure-5.8 (Ubuntu Focal) Importance: High Assignee: Kleber Sacilotto de Souza (kleber-souza) Status: New ** Also affects: linux-meta-azure (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-meta-azure (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-meta-azure (Ubuntu Focal) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Summary changed: - Cloud kernels meta don't provide kernesl-testing--*--modules-extra--preferred + Cloud kernels meta don't provide kernel-testing--*--modules-extra--preferred ** Also affects: linux-meta-azure-5.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta-azure-5.8 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-meta-azure-5.8 (Ubuntu Focal) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-azure in Ubuntu. https://bugs.launchpad.net/bugs/1931576 Title: Cloud kernels meta don't provide kernel-testing--*--modules-extra-- preferred Status in linux-meta-azure package in Ubuntu: New Status in linux-meta-azure-5.8 package in Ubuntu: New Status in linux-meta-azure source package in Focal: New Status in linux-meta-azure-5.8 source package in Focal: New Bug description: [Impact] ADT sets up the test environment by installing the image and modules-extra package via the virtual provides 'kernel-testing--linux---full--preferred' and 'kernel-testing--linux---modules-extra--preferred'. If those are not available, it falls back to using the real meta names as 'linux-image-' and 'linux-modules-extra-'. The 5.4 cloud kernels in Focal are not providing the virtual packages for 'kernel-testing--linux---modules-extra--preferred'. When the tests falls back to 'linux-modules-extra-', the new 5.8 cloud kernels are pulled for the tests as they are now the default sources. ADT log: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/a/acpi-call/20210609_092540_0a7a8@/log.gz [Fix] The meta packages need to be fixed to provide the necessary virtual packages for testing. [Where problems could occur] Adding new virtual meta packages could clash with existing names provided by other sources. However, if they existed ADT would have pulled them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-azure/+bug/1931576/+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 1904589] Re: zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4
I'll see why this has got stuck and sort this out for focal.
--
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/1904589
Title:
zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Focal:
In Progress
Status in zfs-linux source package in Groovy:
Fix Released
Status in zfs-linux source package in Hirsute:
Fix Released
Bug description:
[Impact]
zfs_write() doesn't properly account partial copies done by
copy_from_user(), causing accesses past the end of objects and
triggering kernel panics.
[Test case]
The problem seems to be workload specific, there is not a specific
test case to reproduce the problem, but the bug seems to be pretty
well identified by the upstream commit reported below.
[Fix]
Apply upstream commit c9e3efdb3a6111b9795becc6594b3c52ba004522
("Bugfix/fix uio partial copies").
[Regression potential]
Upstream commit that is basically fixing potential out-of-bounds
accesses by properly checking partial copies done by copy_from_user()
and preventing kernel panics. Regression potential is minimal: it
seems unlikely to break other things if this change is applied.
[Original bug report]
Using latest zfs 0.8.3-1ubuntu12.4 on latest Ubuntu 20.04.1, I observe
a rare zfs panics that seem to be workload-specific which render a
server mostly unresponsive besides ssh still working. Attempting to
reboot the server in this state makes the shutdown hang forever.
You may want to consider backporting the fix released in zfs 0.8.4
into 20.04: https://github.com/openzfs/zfs/pull/10148
Log sample of panic:
```
Nov 17 16:06:15 hostname kernel: [3385134.716024] PANIC: zfs: accessing past
end of object c1c/2db52f (size=17408 access=7492+16428)
Nov 17 16:06:15 hostname kernel: [3385134.716072] Showing stack for process
3166846
Nov 17 16:06:15 hostname kernel: [3385134.716074] CPU: 25 PID: 3166846 Comm:
node Tainted: P O 5.4.0-48-generic #52-Ubuntu
Nov 17 16:06:15 hostname kernel: [3385134.716075] Hardware name:
Nov 17 16:06:15 hostname kernel: [3385134.716076] Call Trace:
Nov 17 16:06:15 hostname kernel: [3385134.716085] dump_stack+0x6d/0x9a
Nov 17 16:06:15 hostname kernel: [3385134.716097] spl_dumpstack+0x29/0x2b
[spl]
Nov 17 16:06:15 hostname kernel: [3385134.716102] vcmn_err.cold+0x60/0x99
[spl]
Nov 17 16:06:15 hostname kernel: [3385134.716106] ? _cond_resched+0x19/0x30
Nov 17 16:06:15 hostname kernel: [3385134.716108] ?
__kmalloc_node+0x20e/0x330
Nov 17 16:06:15 hostname kernel: [3385134.716113] ?
spl_kmem_alloc_impl+0xa8/0x100 [spl]
Nov 17 16:06:15 hostname kernel: [3385134.716190] ? __list_add+0x17/0x40
[zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716235]
zfs_panic_recover+0x6f/0x90 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716272] ?
dsl_dir_tempreserve_impl.isra.0.constprop.0+0xed/0x330 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716305]
dmu_buf_hold_array_by_dnode+0x3a0/0x490 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716338]
dmu_write_uio_dnode+0x4c/0x140 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716370]
dmu_write_uio_dbuf+0x4f/0x70 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716416] zfs_write+0xa1f/0xd40 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716419] ? d_absolute_path+0x74/0xb0
Nov 17 16:06:15 hostname kernel: [3385134.716421] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716423] ? __switch_to_asm+0x40/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716424] ? __switch_to_asm+0x40/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716425] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716427] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716474]
zpl_write_common_iovec+0xad/0x120 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716567] zpl_iter_write+0x56/0x90
[zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716570] do_iter_write+0x84/0x1a0
Nov 17 16:06:15 hostname kernel: [3385134.716574] ? futex_wake+0x8b/0x180
Nov 17 16:06:15 hostname kernel: [3385134.716577] do_writev+0x71/0x120
Nov 17 16:06:15 hostname kernel: [3385134.716581] do_syscall_64+0x57/0x190
Nov 17 16:06:15 hostname kernel: [3385134.716584] RIP: 0033:0x7fa366eee0cd
Nov 17 16:06:15 hostname kernel: [3385134.716587] RSP: 002b:7fa35e7fbde0
EFLAGS: 0293 ORIG_RAX: 0014
Nov 17 16:06:15 hostname kernel: [3385134.716590] RDX: 000c RSI:
0651c7b0 RDI: 001d
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1904589/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : htt
[Kernel-packages] [Bug 1931475] Re: Ubuntu only stable in safe graphics mode
I've been working with someone at the ubuntu forums also: https://ubuntuforums.org/showthread.php?t=2463365&page=2&p=14042724#post14042724 If I add "i915.aplha_support=1" and "nomodeset" to the line. Ubuntu will boot normally, but in a lower resolution (1024x768). it does remain stable.Im unable to change the resolution. -- 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/1931475 Title: Ubuntu only stable in safe graphics mode Status in linux package in Ubuntu: Incomplete Bug description: Brand new machine, Intel i5, Brand new install of 20.04 ubuntu using 5.11.0-18 kernel. BIOS updated to recent firmware. (5/11/2021 date) Machine will only stay running in safe graphics mode. When booting normal, GUI loads for about 5 seconds then reboots. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 9 14:04:22 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-06-09 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard SK-8115 Bus 001 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 7: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=5e92baa8-faf7-43e0-ab03-c43a1ec8a549 ro recovery nomodeset dis_ucode_ldr text SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2021 dmi.bios.release: 16.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1605 dmi.board.asset.tag: Default string dmi.board.name: PRIME B460-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1605:bd04/07/2021:br16.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB460-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.apport.crashdb.conf: 2021-06-09T13:25:26.012453 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931475/+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 1931576] Re: Cloud kernels meta don't provide kernel-testing--*--modules-extra--preferred
** Also affects: linux-meta-aws (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-meta-aws-5.8 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-meta-gcp (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-meta-gcp-5.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta-gcp (Ubuntu Focal) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: linux-meta-gcp-5.8 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-meta-gcp-5.8 (Ubuntu Focal) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: linux-meta-aws-5.8 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-meta-aws-5.8 (Ubuntu Focal) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: linux-meta-aws (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-meta-aws (Ubuntu Focal) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: linux-meta-gcp (Ubuntu Focal) Importance: Undecided => High ** Description changed: [Impact] ADT sets up the test environment by installing the image and modules-extra package via the virtual provides 'kernel-testing--linux---full--preferred' and 'kernel-testing--linux---modules-extra--preferred'. If those are not available, it falls back to using the real meta names as 'linux-image-' and 'linux-modules-extra-'. The 5.4 cloud kernels in Focal are not providing the virtual packages for 'kernel-testing--linux---modules-extra--preferred'. When the tests falls back to 'linux-modules-extra-', the new 5.8 cloud kernels are pulled for the tests as they are now the default sources. + The oracle kernels in focal don't need fixing as they do not produce a + linux-modules-extra-* package. + ADT log: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/a/acpi-call/20210609_092540_0a7a8@/log.gz [Fix] The meta packages need to be fixed to provide the necessary virtual packages for testing. [Where problems could occur] Adding new virtual meta packages could clash with existing names provided by other sources. However, if they existed ADT would have pulled them. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-aws in Ubuntu. https://bugs.launchpad.net/bugs/1931576 Title: Cloud kernels meta don't provide kernel-testing--*--modules-extra-- preferred Status in linux-meta-aws package in Ubuntu: New Status in linux-meta-aws-5.8 package in Ubuntu: New Status in linux-meta-azure package in Ubuntu: New Status in linux-meta-azure-5.8 package in Ubuntu: New Status in linux-meta-gcp package in Ubuntu: New Status in linux-meta-gcp-5.8 package in Ubuntu: New Status in linux-meta-aws source package in Focal: New Status in linux-meta-aws-5.8 source package in Focal: New Status in linux-meta-azure source package in Focal: New Status in linux-meta-azure-5.8 source package in Focal: New Status in linux-meta-gcp source package in Focal: New Status in linux-meta-gcp-5.8 source package in Focal: New Bug description: [Impact] ADT sets up the test environment by installing the image and modules-extra package via the virtual provides 'kernel-testing--linux---full--preferred' and 'kernel-testing--linux---modules-extra--preferred'. If those are not available, it falls back to using the real meta names as 'linux-image-' and 'linux-modules-extra-'. The 5.4 cloud kernels in Focal are not providing the virtual packages for 'kernel-testing--linux---modules-extra--preferred'. When the tests falls back to 'linux-modules-extra-', the new 5.8 cloud kernels are pulled for the tests as they are now the default sources. The oracle kernels in focal don't need fixing as they do not produce a linux-modules-extra-* package. ADT log: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/a/acpi-call/20210609_092540_0a7a8@/log.gz [Fix] The meta packages need to be fixed to provide the necessary virtual packages for testing. [Where problems could occur] Adding new virtual meta packages could clash with existing names provided by other sources. However, if they existed ADT would have pulled them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-aws/+bug/1931576/+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 1930976] Re: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
*** This bug is a duplicate of bug 1930733 *** https://bugs.launchpad.net/bugs/1930733 ** This bug has been marked a duplicate of bug 1930733 Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930976 Title: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers Status in linux-hwe-5.8 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Kernel: 5.8.0-55 The last kernel destroyed my Ubuntu 20.04.02 installation, something went wrong with some kernel packages. It seems like Ubuntu is unable to find my video card correctly and the device drivers from Nvidia don't seem to work anymore. I had to do a clean installation, but even that doesn't solve the problem. I think this is a serious issue that needs to be looked into. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jun 5 16:50:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation Device [10de:2206] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:403f] InstallationDate: Installed on 2021-06-05 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=4984fe2f-d45f-4734-884c-2426bcf10ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33j dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33j:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1930976/+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 1930794] Re: Ubuntu 20.04 LTS does not start after kernel update
*** This bug is a duplicate of bug 1930733 *** https://bugs.launchpad.net/bugs/1930733 ** This bug is no longer a duplicate of bug 1930976 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers ** This bug has been marked a duplicate of bug 1930733 Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI -- 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/1930794 Title: Ubuntu 20.04 LTS does not start after kernel update Status in linux package in Ubuntu: New Bug description: Hi I got a notification to update my kernel to 5.8.0-55 and when I update and reboot my PC. The desktop does not start and when I downgrade my kernel 5.8.0-53. Again, it does not work either. Finally, I have to reimage my PC from the scratch and I lose all of my local data in this situation. I Hope you can solve this critical problem soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930794/+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 1931568] [NEW] no wifi adpter found: Lenovo E41-25
You have been subscribed to a public bug: I have installed the ubuntu 19.10 and since the installation it says no wifi adpter found but the wifi was working with Windows perfectly but since I switch to ubuntu I am not able to use the wifi. I have tried lots of different methods to fix this issue on the internet and also asked on Ubuntu community for help but none worked for me. It seems there's some bug on the os because during the installation the wifi was working but after the installation has completed the wifi stoped working and says No wifi adapter found. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: anu 2180 F pulseaudio /dev/snd/controlC0: anu 2180 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:31:11 2020 InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lo no wireless extensions. enp0s16u3 no wireless extensions. enp1s0 no wireless extensions. MachineType: LENOVO 81FS ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=9462d35f-9a18-4b4c-8372-6429117b7939 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware 1.183.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7UCN28WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E41-25 dmi.modalias: dmi:bvnLENOVO:bvr7UCN28WW(V2.02):bd11/14/2019:svnLENOVO:pn81FS:pvrLenovoE41-25:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE41-25: dmi.product.family: E41-25 dmi.product.name: 81FS dmi.product.sku: LENOVO_MT_81FS_BU_idea_FM_E41-25 dmi.product.version: Lenovo E41-25 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid -- no wifi adpter found: Lenovo E41-25 https://bugs.launchpad.net/bugs/1931568 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931568] Re: no wifi adpter found: Lenovo E41-25
** Package changed: xubuntu-meta (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/1931568 Title: no wifi adpter found: Lenovo E41-25 Status in linux package in Ubuntu: Invalid Bug description: I have installed the ubuntu 19.10 and since the installation it says no wifi adpter found but the wifi was working with Windows perfectly but since I switch to ubuntu I am not able to use the wifi. I have tried lots of different methods to fix this issue on the internet and also asked on Ubuntu community for help but none worked for me. It seems there's some bug on the os because during the installation the wifi was working but after the installation has completed the wifi stoped working and says No wifi adapter found. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: anu 2180 F pulseaudio /dev/snd/controlC0: anu 2180 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:31:11 2020 InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lo no wireless extensions. enp0s16u3 no wireless extensions. enp1s0 no wireless extensions. MachineType: LENOVO 81FS ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=9462d35f-9a18-4b4c-8372-6429117b7939 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware 1.183.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7UCN28WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E41-25 dmi.modalias: dmi:bvnLENOVO:bvr7UCN28WW(V2.02):bd11/14/2019:svnLENOVO:pn81FS:pvrLenovoE41-25:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE41-25: dmi.product.family: E41-25 dmi.product.name: 81FS dmi.product.sku: LENOVO_MT_81FS_BU_idea_FM_E41-25 dmi.product.version: Lenovo E41-25 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931568/+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 1930794] Re: Ubuntu 20.04 LTS does not start after kernel update
*** This bug is a duplicate of bug 1930733 *** https://bugs.launchpad.net/bugs/1930733 That link is for Ubuntu 20.10 (https://bugs.launchpad.net/ubuntu/+source /nvidia-graphics-drivers-465/+bug/1930733) and my problem is for Ubuntu 20.05 LTS. -- 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/1930794 Title: Ubuntu 20.04 LTS does not start after kernel update Status in linux package in Ubuntu: New Bug description: Hi I got a notification to update my kernel to 5.8.0-55 and when I update and reboot my PC. The desktop does not start and when I downgrade my kernel 5.8.0-53. Again, it does not work either. Finally, I have to reimage my PC from the scratch and I lose all of my local data in this situation. I Hope you can solve this critical problem soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930794/+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 1930527] Re: [SRU][OEM-5.10/H] UBUNTU: SAUCE: Fix backlight control on Samsung 16727 panel
Verified by vendor, brighness can be changed on 5.10.0-1030-oem. ** 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/1930527 Title: [SRU][OEM-5.10/H] UBUNTU: SAUCE: Fix backlight control on Samsung 16727 panel Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: New Bug description: SRU justification: [Impact] Backlight can't be controlled on 5.11- version of kernel. [Fix] The panel needs DPCD to get control of backlight. After 5.12 kernel introduced new Intel HDR backlight control, and it works well on this panel. Add quirk ID to enable DPCD on 5.11- kernel. [Test] Vendor Verified on hardware, with this quirk backlight can be changed on 5.10 and 5.11 kernel. [Where problems could occur] The panel backlight may not be changed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930527/+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 1909814] Re: Keyboard not working
The final patch version is out: https://bugzilla.kernel.org/show_bug.cgi?id=213031#c29 With some luck it'll land in the 5.14 kernel. Thank you all for your information, help and testing! @replydev: Regarding the patches' differences: The patches published by me were for testing for the root cause and overriding it. The patches programmed by Hui Wang do the proper checks (to not always forcibly override the kernel's default behaviour). His final release improved the coding style. -- 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/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460 460.84 is available in impish-proposed, but as dkms only at the moment - not yet available as signed lrm package. It would be nice to know if 460.84 works or not. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-465 package in Ubuntu: Triaged Bug description: I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute Jun 03 16:26:57 willow kernel: Oops: [#1] SMP PTI Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P OE 5.11.0-18-generic #19-Ubuntu Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019 Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09: 8e318220acb8 Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 R12: 0400 Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 R15: 0800 Jun 03 16:26:57 willow kernel: FS: 7f5807f38a40() GS:8e3466dc() knlGS: Jun 03 16:26:57 willow kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 CR4: 003706e0 Jun 03 16:26:57 willow kernel: DR0: DR1: DR2: Jun 03 16:26:57 willow kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jun 03 16:26:57 willow kernel: Call Trace: Jun 03 16:26:57 willow kernel: ? _nv015556rm+0x7fd/0x1020 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv027155rm+0x22c/0x4f0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017787rm+0x303/0x5e0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017789rm+0xe1/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv022829rm+0xed/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv023065rm+0x30/0x60 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv000704rm+0x16da/0x22b0 [nvidia] Jun 03 16:26:57 willow kernel: ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 03 16:26:57 willow kernel: ? nv_open_device+0x122/0x8e0 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_open+0x2b7/0x560 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 03 16:26:57 willow kernel: ? chrdev_open+0xf7/0x220 Jun 03 16:26:57 willow kernel: ? cdev_device_add+0x90/0x90 Jun 03 16:26:57 willow kernel: ? do_dentry_open+0x156/0x370 Jun 03 16:26:57 willow kernel: ? vfs_open+0x2d/0x30 Jun 03 16:26:57 willow kernel: ? do_open+0x1c3/0x340 Jun 03 16:26:57 willow kernel: ? path_openat+0x10a/0x1d0 Jun 03 16:26:57 willow kernel: ? do_filp_open+0x8c/0x130 Jun 03 16:26:57 willow kernel: ? __check_object_size+0x1c/0x20 Jun 03 16:26:57 willow kernel: ? do_sys_openat2+0x9b/0x150 Jun 03 16:26:57 willow kernel: ? __x64_sys_openat+0x56/0x90 Jun 03 16:26:57 willow kernel: ? do_syscall_64+0x38/0x90 Jun 03 16:26:57 willow kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) > Jun 03 16:26:57 willow kernel: sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c> Jun 03 16:26:57 willow kernel: CR2: 0170 Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]--- Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 wil
[Kernel-packages] [Bug 1926330] Re: HWE kernels should enable BTF support to enable eBPF RO.CE support
And for v5.13 kernels even newer dwarves-dfsg is needed. ** Changed in: dwarves-dfsg (Ubuntu Bionic) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Won't Fix ** Changed in: dwarves-dfsg (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: dwarves-dfsg (Ubuntu Hirsute) 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/1926330 Title: HWE kernels should enable BTF support to enable eBPF RO.CE support Status in dwarves-dfsg package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in dwarves-dfsg source package in Bionic: Won't Fix Status in linux source package in Bionic: Won't Fix Status in dwarves-dfsg source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in dwarves-dfsg source package in Groovy: Fix Released Status in linux source package in Groovy: Fix Released Status in dwarves-dfsg source package in Hirsute: New Status in linux source package in Hirsute: New Bug description: I had recent discussion with kernel team regarding support or not BTF in HWE kernels (Bionic and Focal). Having CONFIG_DEBUG_INFO_BTF option enabled for HWE kernels (v4.4 and v.4.8) would allow eBPF based code (powered by libbpf or not) to be RO.CE (https://github.com/rafaeldtinoco/portablebpf for more information). By allowing runtime relocations, using provided BTF, libbpf binaries might end up running, without modifications, in different kernel versions (from Bionic HWE v5.4 kernel to Hirsute v5.11). A good example would be to support tools such as: https://github.com/aquasecurity/tracee/discussions/713#discussioncomment-665641 An ebpf powered backend for a containers security solution. Considering: $ rmadisonb dwarves dwarves | 1.9-1 | precise/universe | amd64 dwarves | 1.10-2 | trusty | amd64 dwarves | 1.10-2.1 | xenial/universe | amd64 dwarves | 1.10-2.1build1 | bionic/universe | amd64 dwarves | 1.15-2 | focal/universe | amd64 dwarves | 1.17-1 | groovy/universe | amd64 dwarves | 1.20-1 | hirsute/universe | amd64 dwarves | 1.20-1 | impish/universe | amd64 And the fact that the 'pahole' binary, from dwarves package, is the one to blame, not to have CONFIG_DEBUG_INFO_BTF available, for this bug to be solved we would have to provide a backport of dwarves (at least 1.17-1) to Bionic and Focal. It could have another name (not to mess with original dwarves package and its dependencies) and it is unclear if it needs to be in [main] or [universe]. Question: Would have dwarves backported in -backports be enough for Bionic and Focal HWE kernels compilation to have CONFIG_DEBUG_INFO_BTF enabled ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1926330/+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 1931435] Re: crash fails to build on ubuntu 20.10 (Groovy) on arm64
Debdiff for G. ** Patch added: "lp1931435_groovy.debdiff" https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931435/+attachment/5503885/+files/lp1931435_groovy.debdiff ** Tags added: sts-sponsor-ddstreet -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1931435 Title: crash fails to build on ubuntu 20.10 (Groovy) on arm64 Status in crash package in Ubuntu: Confirmed Status in crash source package in Groovy: Confirmed Bug description: On arm64, crash fails to build with error "multiple definition of `tdesc_aarch64'" [1]. From upstream git log, seems it can be resolved with commit e770735200c02ac2414c394ea6ec5f7f033efe64 . [1] https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630861 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931435/+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 1904589] Re: zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4
the focal package with this fix is now awaiting approval by the distro
manager; then it will be available in the -proposed pocket for testing.
--
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/1904589
Title:
zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Focal:
In Progress
Status in zfs-linux source package in Groovy:
Fix Released
Status in zfs-linux source package in Hirsute:
Fix Released
Bug description:
[Impact]
zfs_write() doesn't properly account partial copies done by
copy_from_user(), causing accesses past the end of objects and
triggering kernel panics.
[Test case]
The problem seems to be workload specific, there is not a specific
test case to reproduce the problem, but the bug seems to be pretty
well identified by the upstream commit reported below.
[Fix]
Apply upstream commit c9e3efdb3a6111b9795becc6594b3c52ba004522
("Bugfix/fix uio partial copies").
[Regression potential]
Upstream commit that is basically fixing potential out-of-bounds
accesses by properly checking partial copies done by copy_from_user()
and preventing kernel panics. Regression potential is minimal: it
seems unlikely to break other things if this change is applied.
[Original bug report]
Using latest zfs 0.8.3-1ubuntu12.4 on latest Ubuntu 20.04.1, I observe
a rare zfs panics that seem to be workload-specific which render a
server mostly unresponsive besides ssh still working. Attempting to
reboot the server in this state makes the shutdown hang forever.
You may want to consider backporting the fix released in zfs 0.8.4
into 20.04: https://github.com/openzfs/zfs/pull/10148
Log sample of panic:
```
Nov 17 16:06:15 hostname kernel: [3385134.716024] PANIC: zfs: accessing past
end of object c1c/2db52f (size=17408 access=7492+16428)
Nov 17 16:06:15 hostname kernel: [3385134.716072] Showing stack for process
3166846
Nov 17 16:06:15 hostname kernel: [3385134.716074] CPU: 25 PID: 3166846 Comm:
node Tainted: P O 5.4.0-48-generic #52-Ubuntu
Nov 17 16:06:15 hostname kernel: [3385134.716075] Hardware name:
Nov 17 16:06:15 hostname kernel: [3385134.716076] Call Trace:
Nov 17 16:06:15 hostname kernel: [3385134.716085] dump_stack+0x6d/0x9a
Nov 17 16:06:15 hostname kernel: [3385134.716097] spl_dumpstack+0x29/0x2b
[spl]
Nov 17 16:06:15 hostname kernel: [3385134.716102] vcmn_err.cold+0x60/0x99
[spl]
Nov 17 16:06:15 hostname kernel: [3385134.716106] ? _cond_resched+0x19/0x30
Nov 17 16:06:15 hostname kernel: [3385134.716108] ?
__kmalloc_node+0x20e/0x330
Nov 17 16:06:15 hostname kernel: [3385134.716113] ?
spl_kmem_alloc_impl+0xa8/0x100 [spl]
Nov 17 16:06:15 hostname kernel: [3385134.716190] ? __list_add+0x17/0x40
[zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716235]
zfs_panic_recover+0x6f/0x90 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716272] ?
dsl_dir_tempreserve_impl.isra.0.constprop.0+0xed/0x330 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716305]
dmu_buf_hold_array_by_dnode+0x3a0/0x490 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716338]
dmu_write_uio_dnode+0x4c/0x140 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716370]
dmu_write_uio_dbuf+0x4f/0x70 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716416] zfs_write+0xa1f/0xd40 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716419] ? d_absolute_path+0x74/0xb0
Nov 17 16:06:15 hostname kernel: [3385134.716421] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716423] ? __switch_to_asm+0x40/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716424] ? __switch_to_asm+0x40/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716425] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716427] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716474]
zpl_write_common_iovec+0xad/0x120 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716567] zpl_iter_write+0x56/0x90
[zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716570] do_iter_write+0x84/0x1a0
Nov 17 16:06:15 hostname kernel: [3385134.716574] ? futex_wake+0x8b/0x180
Nov 17 16:06:15 hostname kernel: [3385134.716577] do_writev+0x71/0x120
Nov 17 16:06:15 hostname kernel: [3385134.716581] do_syscall_64+0x57/0x190
Nov 17 16:06:15 hostname kernel: [3385134.716584] RIP: 0033:0x7fa366eee0cd
Nov 17 16:06:15 hostname kernel: [3385134.716587] RSP: 002b:7fa35e7fbde0
EFLAGS: 0293 ORIG_RAX: 0014
Nov 17 16:06:15 hostname kernel: [3385134.716590] RDX: 000c RSI:
0651c7b0 RDI: 001d
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1904589/+subscriptions
--
Mailing list: https://launchpad.net/~k
[Kernel-packages] [Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
Keyboard worked with new kernel, however Fn+F4 still doesn't functional. I've also noticed that mouse middle button stopped to work (both scrolling and clicking) on this version. dmesg doesn't show anything on pressing Fn+F4. -- 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/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I found that some of the Lenovo Lenovo Essential Wireless Keyboard Fn keys don't work. First one is Mute mic (Fn+F4), second one is Scissors (Fn+F10, probably hotkey for Windows Snipping Tool for selective screenshot).gnome-control-panel, xev and evtest doesn't react on pressing these buttons. Here what I was able to get via sudo cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"' : For Mute key 00 00 00 FF DC 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 For Scissors 00 00 00 FF DB 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asudak 2085 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 6 22:36:50 2021 InstallationDate: Installed on 2021-04-13 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-18 (17 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+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 1931435] Re: crash fails to build on ubuntu 20.10 (Groovy) on arm64
The attachment "lp1931435_groovy.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1931435 Title: crash fails to build on ubuntu 20.10 (Groovy) on arm64 Status in crash package in Ubuntu: Confirmed Status in crash source package in Groovy: Confirmed Bug description: On arm64, crash fails to build with error "multiple definition of `tdesc_aarch64'" [1]. From upstream git log, seems it can be resolved with commit e770735200c02ac2414c394ea6ec5f7f033efe64 . [1] https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630861 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931435/+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 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
Hello folks, Im also affected by this issue In the meantime, you can try with this PPA: https://launchpad.net/~tuxinvader/+archive/ubuntu/lts-mainline-longterm -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1928535] Re: No disk space, mainline 5.10.37 and 5.11.20, 5.11.21 failed to build
This is still broken on 5.10.43. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.43/ -- 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/1928535 Title: No disk space, mainline 5.10.37 and 5.11.20, 5.11.21 failed to build Status in linux package in Ubuntu: Confirmed Bug description: It looks like the build machine ran out of disk space while building 5.11.20 amd64 and 5.10.36 armhf. From: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11.20/amd64/log ld: final link failed: No space left on device make[2]: *** [/home/kernel/COD/linux/Makefile:1183: vmlinux] Error 1 make[2]: Leaving directory '/home/kernel/COD/linux/debian/build/build-generic' make[1]: *** [Makefile:185: __sub-make] Error 2 make[1]: Leaving directory '/home/kernel/COD/linux' make: *** [debian/rules.d/2-binary-arch.mk:50: /home/kernel/COD/linux/debian/stamps/stamp-build-generic] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 No packages have been built for 5.10.37, 5.11.20, or 5.11.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928535/+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 1927866] Re: Root filesystem becomes readonly frequenty freezing system
I ran into this error again. The system did not go into the console mode with full errors but it was in the login screen with all images replaced by blank icons and I couldn't do anything. There was no immediate reboot before this. I wish we could have a mechanism where the specific scenario that triggers this error could be logged. -- 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/1927866 Title: Root filesystem becomes readonly frequenty freezing system Status in linux package in Ubuntu: Confirmed Bug description: I have a brand new Lenovo Ideapad Flex 5.14 which came with Windows 10 and I have installed Ubuntu 21.04 with dual boot. I am running into this problem where the root filesystem becomes readonly and the system freezes with a screen full of errors shown about unable to write to filesystem. I booted into a live boot usb and did fsck and e2fsck but did not see any errors there. I read online that this could be because of io errors but smartctl and fsck does not show any errors So I was wondering if this could be a bug vs a hardward issue. Please let me know if you need any further information from the system. = = fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: WDC PC SN530 SDBPMPZ-512G-1101 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E8803E28-C4F7-4FA5-9B6D-0F3CAB7027A5 Device StartEnd Sectors Size Type /dev/nvme0n1p1 2048 534527532480 260M EFI System /dev/nvme0n1p2534528 567295 3276816M Microsoft reserved /dev/nvme0n1p3567296 199446527 198879232 94.8G Microsoft basic data /dev/nvme0n1p4 998166528 1000214527 2048000 1000M Windows recovery environmen /dev/nvme0n1p5 199446528 203352063 3905536 1.9G Linux filesystem /dev/nvme0n1p6 203352064 219353087 16001024 7.6G Linux swap /dev/nvme0n1p7 219353088 414664703 195311616 93.1G Linux filesystem /dev/nvme0n1p8 414664704 998166527 583501824 278.2G Microsoft basic data = = smartctl -a /dev/nvme0 smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.0-16-generic] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: WDC PC SN530 SDBPMPZ-512G-1101 Serial Number: 205135806243 Firmware Version: 21160001 PCI Vendor/Subsystem ID:0x15b7 IEEE OUI Identifier:0x001b44 Total NVM Capacity: 512,110,190,592 [512 GB] Unallocated NVM Capacity: 0 Controller ID: 1 NVMe Version: 1.4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64:001b44 8b484daff7 Local Time is: Sun May 9 12:45:05 2021 EDT Firmware Updates (0x14):2 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Maximum Data Transfer Size: 128 Pages Warning Comp. Temp. Threshold: 80 Celsius Critical Comp. Temp. Threshold: 85 Celsius Namespace 1 Features (0x02):NA_Fields Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 3.50W2.10W -0 0 0 00 0 1 + 2.40W1.60W -0 0 0 00 0 2 + 1.90W1.50W -0 0 0 00 0 3 - 0.0250W --3 3 3 3 3900 11000 4 - 0.0050W --4 4 4 4 5000 39000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 2 1 -4096 0 1 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature:35 Celsius Available Spare:100% Available Spare Threshold: 10% Percentage Used:0% Data Units Read:624,535 [319 GB] Data Units Written: 526,042 [26
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
It's a shame that mainline don't build LTS compatible kernels anymore, but what can we do about it? It would be nice if they would build for ubuntu-next *and* previous LTS, but they don't. So new kernels for any Ubuntu release relies on the HWE updates that come with the point releases. The next focal update (20.04.3) should back port the kernel from 21.04 (which is 5.11) and it should arrive in August. The previous HWE kernel was 5.8. What I don't understand with the HWE packages, is that there is both a linux-generic-hwe-20.04 and a linux-generic-hwe-20.04-edge. It feels to me like `edge` should be more like a rolling release between the HWE releases that come with an LTS update, but they're not?? Currently the edge and non-edge versions are exactly the same. $ apt-cache madison linux-generic-hwe-20.04-edge linux-generic-hwe-20.04-edge | 5.8.0.55.62~20.04.39 | http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages $ apt-cache madison linux-generic-hwe-20.04 linux-generic-hwe-20.04 | 5.8.0.55.62~20.04.39 | http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages Strange. -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
ok thanks. On 09/06/2021 17:16, Colin Ian King wrote: > I've uploaded 2.4.6 to debian and this will sync this into Ubuntu Impish > development in the next 24-36 hours. Once that's done I'll backport this > fix to older releases of thermald. Thanks for fixing this. > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system Status in thermald package in Ubuntu: Fix Released Bug description: cpu runs at 100c fan at 3000rpm when in heavy use previous version was ok re: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186 lshw -short is: H/W path Device Class Description == system XPS 8940 (09C5) /0 bus0KV3RP /0/0memory 64KiB BIOS /0/9memory 16GiB System Memory /0/9/0 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/1 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/2 memory Project-Id-Version: lshwRepor /0/9/3 memory Project-Id-Version: lshwRepor /0/35 memory 512KiB L1 cache /0/36 memory 2MiB L2 cache /0/37 memory 16MiB L3 cache /0/38 processor Intel(R) Core(TM) i7-10700 CP /0/100 bridge Intel Corporation /0/100/1bridge Xeon E3-1200 v5/E3-1500 v5/6t /0/100/1/0 displayTU106 [GeForce RTX 2060 Rev. /0/100/1/0.1multimedia TU106 High Definition Audio C /0/100/1/0.2busTU106 USB 3.1 Host Controller /0/100/1/0.2/0 usb3 busxHCI Host Controller /0/100/1/0.2/1 usb4 busxHCI Host Controller /0/100/1/0.3busTU106 USB Type-C UCSI Control /0/100/2displayIntel Corporation /0/100/4genericXeon E3-1200 v5/E3-1500 v5/6t /0/100/8genericXeon E3-1200 v5/v6 / E3-1500 /0/100/12 genericComet Lake PCH Thermal Contro /0/100/14 busComet Lake USB 3.1 xHCI Host /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/4 enx0c5b8f279a64 communication HUAWEI_MOBILE /0/100/14/0/5 input Dell MS116 USB Optical Mouse /0/100/14/0/6 input Dell KB216 Wired Keyboard /0/100/14/0/b genericUSB2.0-CRW /0/100/14/0/c genericUB91C /0/100/14/0/e communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3wlo1 networkWi-Fi 6 AX201 /0/100/15 busComet Lake PCH Serial IO I2C /0/100/16 communication Comet Lake HECI Controller /0/100/17 storageIntel Corporation /0/100/1b bridge Comet Lake PCI Express Root P /0/100/1b/0 storageSamsung Electronics Co Ltd /0/100/1b/0/0 /dev/nvme0 storagePM991 NVMe Samsung 512GB /0/100/1b/0/0/1/dev/nvme0n1 disk 512GB NVMe namespace /0/100/1b/0/0/1/1 volume 149MiB Windows FAT volume /0/100/1b/0/0/1/2 /dev/nvme0n1p2 volume 127MiB reserved partition /0/100/1b/0/0/1/3 /dev/nvme0n1p3 volume 214GiB Windows NTFS volume /0/100/1b/0/0/1/4 /dev/nvme0n1p4 volume 989MiB Windows NTFS volume /0/100/1b/0/0/1/5 /dev/nvme0n1p5 volume 16GiB Windows NTFS volume /0/100/1b/0/0/1/6 /dev/nvme0n1p6 volume 1417MiB Windows NTFS volume /0/100/1b/0/0/1/7 /dev/nvme0n1p7 volume 243GiB EXT4 volume /0/100/1c bridge Intel Corporation /0/100/1c/0enp3s0 networkRealtek Semiconductor Co., Lt /0/100/1f bridge Intel Corporation /0/100/1f.3 multimedia Comet Lake PCH cAVS /0/100/1f.4 busComet Lake PCH SMBus Controll /0/10
[Kernel-packages] [Bug 1929831] Re: cifs: On cifs_reconnect, resolve the hostname again
This bug was fixed in the package linux-azure - 5.4.0-1049.51 --- linux-azure (5.4.0-1049.51) focal; urgency=medium * focal/linux-azure: 5.4.0-1049.51 -proposed tracker (LP: #1930703) * cifs: On cifs_reconnect, resolve the hostname again (LP: #1929831) - cifs: rename reconn_inval_dfs_target() - cifs: Simplify reconnect code when dfs upcall is enabled - cifs: Avoid error pointer dereference - cifs: On cifs_reconnect, resolve the hostname again. -- Tim Gardner Thu, 03 Jun 2021 09:17:13 -0600 ** Changed in: linux-azure (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1929831 Title: cifs: On cifs_reconnect, resolve the hostname again Status in linux package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Focal: New Status in linux-azure source package in Focal: Fix Released Bug description: SRU Justification [Impact] The Microsoft CIFS team is requesting below patch to be backported for 5.4 Azure tuned kernel https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4e456b30f78c429b183db420e23b26cde7e03a78 A customer is encountering the bug fixed by this patch. [Fix] 7d397a034d5c45528c7bdf7fc3752c4793029cce cifs: rename reconn_inval_dfs_target() 7d6535b720421d58886d5590ffc3617d359aa871 cifs: Simplify reconnect code when dfs upcall is enabled 4e456b30f78c429b183db420e23b26cde7e03a78 cifs: On cifs_reconnect, resolve the hostname again. The first 2 patches are scaffolding to make the backport simpler. the 3rd patch is the bug fix. [Test Plan] The test kernel at https://launchpad.net/~timg-tpi/+archive/ubuntu /cifs-reconnect-sf00309672 has been found to fix the issue. [Where problems could occur] This could perturb CIFS connections in new and different ways. [Other Info] https://canonical.my.salesforce.com/5004K05pQNG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930275] Re: [nvidia] System does not wake up after suspend
Since the issue has appeared again on Ubuntu 21.04. Please see attached logs from previous boot. ** Attachment added: "Previous boot logs 06-10-2021" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930275/+attachment/5503893/+files/prevboot.txt.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930275 Title: [nvidia] System does not wake up after suspend Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Ubuntu 20.10 suspend is not working. After suspend it does not wake up. And I have to hard reboot machine. It is happening since last few days. Here is error message I see from logs: "Failed to start Application launched by gnome-session-binary. A start job for unit UNIT has finished with a failure. The job identifier is 368 and the job result is failed. Failed to start LSB: OpenIPMI Driver init script. A start job for unit openipmi.service has finished with a failure. The job identifier is 151 and the job result is failed. " ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.73.01 Thu Apr 1 21:40:36 UTC 2021 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 09:04:06 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.73.01, 5.8.0-50-generic, x86_64: installed nvidia, 460.73.01, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU106 [GeForce RTX 2060 SUPER] [3842:3061] InstallationDate: Installed on 2020-02-15 (471 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=ae47d531-67a5-47ff-ba8c-fd3928cd4cad ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7b:bd09/17/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930275/+subscriptions -- Mailing lis
[Kernel-packages] [Bug 1931574] Re: Lost network connection, seems like an older kernel bug
https://wiki.archlinux.org/title/Dell_XPS_13_(9360)#Ethernet_repeatedly_disconnects /reconnects_with_Dell_USB-C_adapter_(DA200) -- 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/1931574 Title: Lost network connection, seems like an older kernel bug Status in linux package in Ubuntu: New Bug description: I experience what seems the exact copy of the issue here after I have connected my Dell laptop to a Dell Monitor with an embedded Ethernet over USB-C/Thunderbolt (and USB-B High Speed Upstream Cable). Suddenly no network connection and it can not be restored for a long time or until reboot. https://bugzilla.kernel.org/show_bug.cgi?id=95711 [350895.699185] INFO: task kworker/3:1:11823 blocked for more than 120 seconds. [350895.699192] Tainted: G U W OE4.15.0-43-generic #46-Ubuntu [350895.699195] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [350895.699198] kworker/3:1 D0 11823 2 0x8000 [350895.699212] Workqueue: events rtl_work_func_t [r8152] [350895.699215] Call Trace: [350895.699224] __schedule+0x291/0x8a0 [350895.699228] schedule+0x2c/0x80 [350895.699232] rpm_resume+0x108/0x7d0 [350895.699237] ? wait_woken+0x80/0x80 [350895.699240] rpm_resume+0x584/0x7d0 [350895.699245] ? __switch_to_asm+0x34/0x70 [350895.699249] ? __switch_to_asm+0x40/0x70 [350895.699252] ? __switch_to_asm+0x34/0x70 [350895.699256] ? __switch_to_asm+0x40/0x70 [350895.699259] ? __switch_to_asm+0x34/0x70 [350895.699263] __pm_runtime_resume+0x4e/0x80 [350895.699267] usb_autopm_get_interface+0x22/0x60 [350895.699272] rtl_work_func_t+0x70/0x41e [r8152] [350895.699277] process_one_work+0x1de/0x410 [350895.699280] worker_thread+0x32/0x410 [350895.699285] kthread+0x121/0x140 [350895.699288] ? process_one_work+0x410/0x410 [350895.699292] ? kthread_create_worker_on_cpu+0x70/0x70 [350895.699297] ? do_syscall_64+0x73/0x130 [350895.699300] ? SyS_exit+0x17/0x20 [350895.699304] ret_from_fork+0x35/0x40 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 4820 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jun 10 14:49:39 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=adfb1128-00d7-41b1-be85-1d224e4ddd57 InstallationDate: Installed on 2018-12-31 (891 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=0807f9b3-f643-40c3-8e0c-ae2e30161acc ro locale=en_US quiet splash i915.modeset=1 i915.enable_rc6=1 i915.enable_fbc=1 i915.enable_guc_loading=1 i915.enable_guc_submission=1 i915.enable_huc=1 i915.enable_psr=1 i915.disable_power_well=0 i915.semaphores=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.20 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.15.1 dmi.board.name: 0PF86Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.15.1:bd03/09/2021:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931574/+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 1931522] Re: Radeon 7 - [drm] perform_link_training_with_retries: Link training attempt failed
Looks like upgrading to the newest mainline stable(?) kernel 5.12.9-051209-generic from here https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.12.9/ with the proper associated headers made an improvement. Switching TTY's and back to the active gnome session the second display stays awake. -- 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/1931522 Title: Radeon 7 - [drm] perform_link_training_with_retries: Link training attempt failed Status in linux package in Ubuntu: New Bug description: One of two Displayport connected monitors does not properly wake. Ubuntu 20.04.2 LTS - this was when they went to sleep after being locked for a while for power save. Ubuntu 21.04 LTS - Occurred when display when switching to a tty and back to the gnome gui. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: babak 2491 F pulseaudio /dev/snd/controlC2: babak 2491 F pulseaudio /dev/snd/controlC0: babak 2491 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 9 22:12:30 2021 InstallationDate: Installed on 2021-06-09 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Micro-Star International Co., Ltd. MS-7C34 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=3d216401-e070-4d87-8a07-3cc2f5bf2650 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.D0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MEG X570 GODLIKE (MS-7C34) 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.D0:bd05/12/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGX570GODLIKE(MS-7C34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C34 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/1931522/+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 1929870] Re: AMD desktop often fails to resume from deep suspend
The magic key doesn't work, the keyboard appears to not function at all when this happens. -- 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/1929870 Title: AMD desktop often fails to resume from deep suspend Status in linux package in Ubuntu: Confirmed Bug description: Machine setup: Desktop PC Ubuntu 21.04 Linux version 5.11.0-17-generic AMD Ryzen 3900X Asus X590 PRIME PRO motherboard NVIDIA P400 GPU Approximately one in every 4 attempts to resume from a deep suspend fails. When the issue occurs the fans spin up but the monitor displays no output and input devices do not function, the system appears frozen and must be restarted using power or reset buttons. I have tried using different dNVIDIA isplay drivers (proprietary as well as open source) as well as trying an AMD Radeon HD 6450 GPU instead of the NVIDIA GPU. I have tried the following kernel parameters: processor.max_cstate=1 rcu_nocbs=0-23 I have updated the BIOS several times. I had similar problems with Ubuntu 20.10. I have enabled some additional kernel logging with initcall_debug. Fairly consistently the last message printed in the kernel log is from the ethernet driver: May 27 09:19:43 jacob-tm kernel: [ 230.878348] OOM killer enabled. May 27 09:19:43 jacob-tm kernel: [ 230.878349] Restarting tasks ... May 27 09:19:43 jacob-tm kernel: [ 230.879023] usb 5-2.3: USB disconnect, device number 4 May 27 09:19:43 jacob-tm kernel: [ 230.879026] usb 5-2.3.1: USB disconnect, device number 5 May 27 09:19:43 jacob-tm kernel: [ 230.879285] done. May 27 09:19:43 jacob-tm kernel: [ 230.879318] PM: suspend exit May 27 09:19:43 jacob-tm kernel: [ 230.880916] rfkill: input handler enabled May 27 09:19:43 jacob-tm kernel: [ 230.955727] kauditd_printk_skb: 1 callbacks suppressed May 27 09:19:43 jacob-tm kernel: [ 230.955731] audit: type=1400 audit(1622132383.424:64): apparmor="DENIED" operation="capab le" profile="/usr/sbin/cupsd" pid=4418 comm="cupsd" capability=12 capname="net_admin" May 27 09:19:43 jacob-tm kernel: [ 230.966192] audit: type=1400 audit(1622132383.432:65): apparmor="DENIED" operation="capab le" profile="/usr/sbin/cups-browsed" pid=4429 comm="cups-browsed" capability=23 capname="sys_nice" May 27 09:19:43 jacob-tm kernel: [ 231.120385] rfkill: input handler disabled May 27 09:19:43 jacob-tm kernel: [ 231.225924] usb 5-2.3.2: USB disconnect, device number 6 May 27 09:19:43 jacob-tm kernel: [ 231.481893] usb 5-2.3.5: USB disconnect, device number 7 May 27 09:19:47 jacob-tm kernel: [ 235.009576] igb :05:00.0 enp5s0: igb: enp5s0 NIC Link is Up 1000 Mbps Full Duplex, Fl ow Control: RX/TX May 27 09:19:47 jacob-tm kernel: [ 235.009913] IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-17-generic 5.11.0-17.18 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacob 2024 F pulseaudio /dev/snd/controlC0: jacob 2024 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 27 14:12:33 2021 InstallationDate: Installed on 2020-10-28 (211 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp5s0no wireless extensions. docker0 no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=f721d5df-ceec-434a-919a-0680ee380996 ro quiet splash initcall_debug processor.max_cstate=1 rcu_nocbs=0-23 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-17-generic N/A linux-backports-modules-5.11.0-17-generic N/A linux-firmware 1.197 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-14 (13 days ago) dmi.bios.date: 05/08/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3604 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3604:bd05/08/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC
[Kernel-packages] [Bug 1931637] [NEW] Groovy update: upstream stable patchset 2021-06-10
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-06-10 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Groovy) 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/1931637 Title: Groovy update: upstream stable patchset 2021-06-10 Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-06-10 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931637/+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 1931475] Re: Ubuntu only stable in safe graphics mode
So what happens when you use i915.alpha_support=1 without nomodeset? -- 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/1931475 Title: Ubuntu only stable in safe graphics mode Status in linux package in Ubuntu: Incomplete Bug description: Brand new machine, Intel i5, Brand new install of 20.04 ubuntu using 5.11.0-18 kernel. BIOS updated to recent firmware. (5/11/2021 date) Machine will only stay running in safe graphics mode. When booting normal, GUI loads for about 5 seconds then reboots. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 9 14:04:22 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-06-09 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard SK-8115 Bus 001 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 7: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=5e92baa8-faf7-43e0-ab03-c43a1ec8a549 ro recovery nomodeset dis_ucode_ldr text SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2021 dmi.bios.release: 16.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1605 dmi.board.asset.tag: Default string dmi.board.name: PRIME B460-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1605:bd04/07/2021:br16.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB460-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.apport.crashdb.conf: 2021-06-09T13:25:26.012453 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
I posted this on the NVIDIA forums, but thought it might be helpful to cross-post here. --- I just tried the 460 server driver solution. This did not work for me and I still have the display port bug. I have an AMD 3800X, 64 gb ram, rtx 2080 super, fresh install of Ubuntu 20.04 kernel 5.8.0-55, with 3 identical 4K monitors, (1 on HDMI, 2 on DP). The opensource driver continues to work just fine, but we need CUDA for our science to continue. Here are the outputs from nvidia-smi, uname -r, and xrandr. Note that all monitors should have 4K options. ''' (base) x@x:~$ nvidia-smi Wed Jun 9 17:18:16 2021 +-+ | NVIDIA-SMI 460.73.01Driver Version: 460.73.01CUDA Version: 11.2 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 GeForce RTX 208... Off | :0E:00.0 On | N/A | | 0% 45CP517W / 250W |702MiB / 7981MiB | 1% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 918 G /usr/lib/xorg/Xorg198MiB | |0 N/A N/A 1466 G /usr/lib/xorg/Xorg349MiB | |0 N/A N/A 1603 G /usr/bin/gnome-shell 137MiB | |0 N/A N/A 2014 G gnome-control-center2MiB | +-+ (base) x@x:~$ uname -r 5.8.0-55-generic (base) x@x:~$ (base) x@x:~$ xrandr Screen 0: minimum 8 x 8, current 7680 x 2160, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected 1920x1080+3840+0 (normal left inverted right x axis y axis) 1110mm x 620mm 1920x1080 60.00 + 59.9429.97* 23.98 1680x1050 59.95 1440x900 59.89 1360x768 60.02 1280x1024 75.0260.02 1280x960 60.00 1280x800 59.81 1280x720 60.0059.9429.9723.98 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.32 720x480 59.94 640x480 75.0072.8159.9459.93 HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 800mm x 450mm 3840x2160 30.00*+ 59.9429.9723.9823.98 4096x2160 59.9429.9724.0023.98 1920x1080 60.0059.9429.9723.98 1680x1050 59.95 1440x900 59.89 1360x768 60.02 1280x1024 75.0260.02 1280x960 60.00 1280x800 59.81 1280x720 60.0059.9429.9723.98 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.32 720x480 59.94 640x480 75.0072.8159.9459.93 DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 disconnected (normal left inverted right x axis y axis) DP-5 connected 1920x1080+5760+0 (normal left inverted right x axis y axis) 800mm x 450mm 1920x1080 60.00*+ 59.9429.9723.98 1680x1050 59.95 1440x900 59.89 1360x768 60.02 1280x1024 75.0260.02 1280x960 60.00 1280x800 59.81 1280x720 60.0059.9429.9723.98 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.32 720x480 59.94 640x480 75.0072.8159.9459.93 USB-C-0 disconnected (normal left inverted right x axis y axis) ''' I tried the nvidia-driver-460-server solution. Sadly it did not work for me. The display port connected monitor resolutions are not correct with the 460.73.01 driver version showing 1080p when they should be 4K. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel
[Kernel-packages] [Bug 1931637] Re: Groovy update: upstream stable patchset 2021-06-10
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ upstream stable patchset 2021-06-10
+ from git://git.kernel.org/
-upstream stable patchset 2021-06-10
-from git://git.kernel.org/
+ KEYS: trusted: Fix memory leak on object td
+ tpm: fix error return code in tpm2_get_cc_attrs_tbl()
+ tpm, tpm_tis: Extend locality handling to TPM2 in tpm_tis_gen_interrupt()
+ tpm, tpm_tis: Reserve locality in tpm_tis_resume()
+ KVM: x86/mmu: Remove the defunct update_pte() paging hook
+ PM: runtime: Fix unpaired parent child_count for force_resume
+ kvm: Cap halt polling at kvm->max_halt_poll_ns
+ ath11k: fix thermal temperature read
+ fs: dlm: fix debugfs dump
+ tipc: convert dest node's address to network order
+ ASoC: Intel: bytcr_rt5640: Enable jack-detect support on Asus T100TAF
+ net: stmmac: Set FIFO sizes for ipq806x
+ ASoC: rsnd: core: Check convert rate in rsnd_hw_params
+ Bluetooth: Fix incorrect status handling in LE PHY UPDATE event
+ i2c: bail out early when RDWR parameters are wrong
+ ALSA: hdsp: don't disable if not enabled
+ ALSA: hdspm: don't disable if not enabled
+ ALSA: rme9652: don't disable if not enabled
+ ALSA: bebob: enable to deliver MIDI messages for multiple ports
+ Bluetooth: Set CONF_NOT_COMPLETE as l2cap_chan default
+ Bluetooth: initialize skb_queue_head at l2cap_chan_create()
+ net/sched: cls_flower: use ntohs for struct flow_dissector_key_ports
+ net: bridge: when suppression is enabled exclude RARP packets
+ Bluetooth: check for zapped sk before connecting
+ powerpc/32: Statically initialise first emergency context
+ net: hns3: remediate a potential overflow risk of bd_num_list
+ ip6_vti: proper dev_{hold|put} in ndo_[un]init methods
+ ASoC: Intel: bytcr_rt5640: Add quirk for the Chuwi Hi8 tablet
+ ice: handle increasing Tx or Rx ring sizes
+ Bluetooth: btusb: Enable quirk boolean flag for Mediatek Chip.
+ i2c: Add I2C_AQ_NO_REP_START adapter quirk
+ MIPS: Loongson64: Use _CACHE_UNCACHED instead of _CACHE_UNCACHED_ACCELERATED
+ coresight: Do not scan for graph if none is present
+ IB/hfi1: Correct oversized ring allocation
+ mac80211: clear the beacon's CRC after channel switch
+ pinctrl: samsung: use 'int' for register masks in Exynos
+ rtw88: 8822c: add LC calibration for RTL8822C
+ mt76: mt7615: support loading EEPROM for MT7613BE
+ mt76: mt76x0: disable GTK offloading
+ mt76: mt7915: fix txpower init for TSSI off chips
+ virtiofs: fix userns
+ cuse: prevent clone
+ iwlwifi: pcie: make cfg vs. trans_cfg more robust
+ powerpc/mm: Add cond_resched() while removing hpte mappings
+ ASoC: rsnd: call rsnd_ssi_master_clk_start() from rsnd_ssi_init()
+ Revert "iommu/amd: Fix performance counter initialization"
+ iommu/amd: Remove performance counter pre-initialization test
+ drm/amd/display: Force vsync flip when reconfiguring MPCC
+ selftests: Set CC to clang in lib.mk if LLVM is set
+ kconfig: nconf: stop endless search loops
+ ALSA: hda/realtek: Add quirk for Lenovo Ideapad S740
+ ASoC: Intel: sof_sdw: add quirk for new ADL-P Rvp
+ ALSA: hda/hdmi: fix race in handling acomp ELD notification at resume
+ sctp: Fix out-of-bounds warning in sctp_process_asconf_param()
+ flow_dissector: Fix out-of-bounds warning in __skb_flow_bpf_to_target()
+ powerpc/smp: Set numa node before updating mask
+ ASoC: rt286: Generalize support for ALC3263 codec
+ ethtool: ioctl: Fix out-of-bounds warning in store_link_ksettings_for_user()
+ net: sched: tapr: prevent cycle_time == 0 in parse_taprio_schedule
+ samples/bpf: Fix broken tracex1 due to kprobe argument change
+ powerpc/pseries: Stop calling printk in rtas_stop_self()
+ drm/amd/display: fixed divide by zero kernel crash during dsc enablement
+ drm/amd/display: add handling for hdcp2 rx id list validation
+ drm/amdgpu: Add mem syn
[Kernel-packages] [Bug 1910200] Re: aws: network performance regression due to initial TCP receive buffer size change
** Changed in: linux-aws (Ubuntu Groovy)
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/1910200
Title:
aws: network performance regression due to initial TCP receive buffer
size change
Status in linux-aws package in Ubuntu:
New
Status in linux-aws source package in Bionic:
Fix Released
Status in linux-aws source package in Focal:
Fix Released
Status in linux-aws source package in Groovy:
Fix Released
Bug description:
[Impact]
AWS has seen some customers reporting networking performance
degradation after they upgraded their Ubuntu instanceses. This
regression is highly impacting customers who are using MTU=9000 (which
is the default in EC2).
[Test case]
Bug reproduced internally in AWS (no test case provided), but
apparently it is very easy to reproduce simply by measuring networking
performance.
[Fix]
AWS worked internally and found that the regression has been
introduced by:
a337531b942b ("tcp: up initial rmem to 128KB and SYN rwin to around
64KB")
To solve the problem we need to apply the following upstream commit
that explicitly fixes the problem introduced by the commit above:
33ae7b5bb841 ("tcp: select sane initial rcvq_space.space for big
MSS")
[Regression potential]
Upstream fix that is only affecting the initial TCP buffer space and
allows the TCP window size to be dynamically increased, basically
restoring the previous (correct) behavior, so regression potential is
minimal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1910200/+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 1931637] Re: Groovy update: upstream stable patchset 2021-06-10
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1931637
Title:
Groovy update: upstream stable patchset 2021-06-10
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Groovy:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2021-06-10
Ported from the following upstream stable releases:
v5.4.120, v5.10.38
from git://git.kernel.org/
KEYS: trusted: Fix memory leak on object td
tpm: fix error return code in tpm2_get_cc_attrs_tbl()
tpm, tpm_tis: Extend locality handling to TPM2 in tpm_tis_gen_interrupt()
tpm, tpm_tis: Reserve locality in tpm_tis_resume()
KVM: x86/mmu: Remove the defunct update_pte() paging hook
PM: runtime: Fix unpaired parent child_count for force_resume
kvm: Cap halt polling at kvm->max_halt_poll_ns
ath11k: fix thermal temperature read
fs: dlm: fix debugfs dump
tipc: convert dest node's address to network order
ASoC: Intel: bytcr_rt5640: Enable jack-detect support on Asus T100TAF
net: stmmac: Set FIFO sizes for ipq806x
ASoC: rsnd: core: Check convert rate in rsnd_hw_params
Bluetooth: Fix incorrect status handling in LE PHY UPDATE event
i2c: bail out early when RDWR parameters are wrong
ALSA: hdsp: don't disable if not enabled
ALSA: hdspm: don't disable if not enabled
ALSA: rme9652: don't disable if not enabled
ALSA: bebob: enable to deliver MIDI messages for multiple ports
Bluetooth: Set CONF_NOT_COMPLETE as l2cap_chan default
Bluetooth: initialize skb_queue_head at l2cap_chan_create()
net/sched: cls_flower: use ntohs for struct flow_dissector_key_ports
net: bridge: when suppression is enabled exclude RARP packets
Bluetooth: check for zapped sk before connecting
powerpc/32: Statically initialise first emergency context
net: hns3: remediate a potential overflow risk of bd_num_list
ip6_vti: proper dev_{hold|put} in ndo_[un]init methods
ASoC: Intel: bytcr_rt5640: Add quirk for the Chuwi Hi8 tablet
ice: handle increasing Tx or Rx ring sizes
Bluetooth: btusb: Enable quirk boolean flag for Mediatek Chip.
i2c: Add I2C_AQ_NO_REP_START adapter quirk
MIPS: Loongson64: Use _CACHE_UNCACHED instead of _CACHE_UNCACHED_ACCELERATED
coresight: Do not scan for graph if none is present
IB/hfi1: Correct oversized ring allocation
mac80211: clear the beacon's CRC after channel switch
pinctrl: samsung: use 'int' for register masks in Exynos
rtw88: 8822c: add LC calibration for RTL8822C
mt76: mt7615: support loading EEPROM for MT7613BE
mt76: mt76x0: disable GTK offloading
mt76: mt7915: fix txpower init for TSSI off chips
virtiofs: fix userns
cuse: prevent clone
iwlwifi: pcie: make cfg vs. trans_cfg more robust
powerpc/mm: Add cond_resched() while removing hpte mappings
ASoC: rsnd: call rsnd_ssi_master_clk_start() from rsnd_ssi_init()
Revert "iommu/amd: Fix performance counter initialization"
iommu/amd: Remove performance counter pre-initialization test
drm/amd/display: Force vsync flip when reconfiguring MPCC
selftests: Set CC to clang in lib.mk if LLVM is set
kconfig: nconf: stop endless search loops
ALSA: hda/realtek: Add quirk for Lenovo Ideapad S740
ASoC: Intel: sof_sdw: add quirk for new ADL-P Rvp
ALSA: hda/hdmi: fix race in handling acomp ELD notification at resume
sctp: Fix out-of-bounds warning in sctp_process_asconf_param()
flow_dissector: Fix out-of-bounds warning in __skb_flow_bpf_to_target()
powerpc/smp: Set numa node before updating mask
ASoC: rt286: Generalize support for ALC3263 codec
ethtool: ioctl: Fix out-of-bounds warning in store_link_ksettings_for_user()
net: sched: tapr: prevent cycle_time == 0 in parse_taprio_schedule
samples/bpf: Fix broken tracex1 due to kprobe argument change
powerpc/pseries: Stop calling printk in rtas_stop_self()
drm/amd/display: fixed divide by zero kernel crash during dsc enablement
drm/amd/display: add handling for hdcp2 rx id list validation
drm/amdgpu: Add mem sync flag for IB allocated by SA
mt76: mt7615: fix entering driver-own state on mt7663
crypto: ccp: Free SEV device if SEV init fails
wl3501_cs: Fix out-of-bounds warnings in wl3501_send_pkt
wl3501_cs: Fix out-of-bounds warnings in wl3501_mgmt_join
qtnfmac: Fix possible buffer overflow in qtnf_event_handle_external_auth
powerpc/io
[Kernel-packages] [Bug 1921632] Re: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later
I went ahead and tested 5.11.0-19 and 5.11.0.20, neither of them works. 5.11.0-19 does not boot to GUI at all, 5.11.0-20 has no audio and touchpad broken. I'm currently on a self-built 5.11.0-17 where the only change is the two soundwire configs and this works amazing. What has happened to -19 and -20 kernels besides the config change? -- 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/1921632 Title: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later Status in linux package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Status in linux source package in Hirsute: Fix Committed Status in linux-oracle source package in Hirsute: Confirmed Status in linux source package in Impish: Confirmed Status in linux-oracle source package in Impish: Confirmed Bug description: [Impact] Ubuntu users ran the kernel on the Dell soundwire audio machines, the dmesg shows the audio mchine driver is not found, then the audio fails to initialize [Fix] Enable the intel soundwire audio machine driver and some related codec driver. [Test] run fakeroot debian/rules clean updateconfigs, and check the config.common.ubuntu, the content is not changed. Build the kernel with this patch applied, the soundwire audio machine driver is built. [Where problems could occur] This could possibly introduce the building failure, I tested it, so far no failure. See also https://bugzilla.kernel.org/show_bug.cgi?id=212465 Default kernel from https://cdimage.ubuntu.com/kubuntu/daily-live/20210327/ and also upstream kernel https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12-rc4/ tested and both do not work. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-28 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210326) MachineType: HP HP Spectre x360 Convertible 13-aw2xxx Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-11-generic root=/dev/mapper/sys-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-11-generic N/A linux-backports-modules-5.11.0-11-generic N/A linux-firmware 1.195 Tags: hirsute Uname: Linux 5.11.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 15.10 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8709 dmi.board.vendor: HP dmi.board.version: 31.30 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 31.30 dmi.modalias: dmi:bvnAMI:bvrF.10:bd12/08/2020:br15.10:efr31.30:svnHP:pnHPSpectrex360Convertible13-aw2xxx:pvr:rvnHP:rn8709:rvr31.30:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-aw2xxx dmi.product.sku: 2G2D8EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632/+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 1921632] Re: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later
@Herczeg, What is your machine, Dell or HP? If non-audio part is broken with -20 kernel, you could file a new bug against it. -- 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/1921632 Title: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later Status in linux package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Status in linux source package in Hirsute: Fix Committed Status in linux-oracle source package in Hirsute: Confirmed Status in linux source package in Impish: Confirmed Status in linux-oracle source package in Impish: Confirmed Bug description: [Impact] Ubuntu users ran the kernel on the Dell soundwire audio machines, the dmesg shows the audio mchine driver is not found, then the audio fails to initialize [Fix] Enable the intel soundwire audio machine driver and some related codec driver. [Test] run fakeroot debian/rules clean updateconfigs, and check the config.common.ubuntu, the content is not changed. Build the kernel with this patch applied, the soundwire audio machine driver is built. [Where problems could occur] This could possibly introduce the building failure, I tested it, so far no failure. See also https://bugzilla.kernel.org/show_bug.cgi?id=212465 Default kernel from https://cdimage.ubuntu.com/kubuntu/daily-live/20210327/ and also upstream kernel https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12-rc4/ tested and both do not work. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-28 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210326) MachineType: HP HP Spectre x360 Convertible 13-aw2xxx Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-11-generic root=/dev/mapper/sys-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-11-generic N/A linux-backports-modules-5.11.0-11-generic N/A linux-firmware 1.195 Tags: hirsute Uname: Linux 5.11.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 15.10 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8709 dmi.board.vendor: HP dmi.board.version: 31.30 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 31.30 dmi.modalias: dmi:bvnAMI:bvrF.10:bd12/08/2020:br15.10:efr31.30:svnHP:pnHPSpectrex360Convertible13-aw2xxx:pvr:rvnHP:rn8709:rvr31.30:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-aw2xxx dmi.product.sku: 2G2D8EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632/+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 1931649] [NEW] alsa: the output volume can't be adjusted on the Lenovo machines with Bass speaker
Public bug reported: this bug is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-5.6 (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: Triaged ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: High Status: Triaged ** Tags: oem-priority originate-from-1931433 sutton ** Package changed: linux (Ubuntu) => linux-oem-5.6 (Ubuntu) ** Changed in: linux-oem-5.6 (Ubuntu) Importance: Undecided => High ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => Triaged ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => Triaged ** Tags added: oem-priority originate-from-1931433 sutton -- 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/1931649 Title: alsa: the output volume can't be adjusted on the Lenovo machines with Bass speaker Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: Triaged Status in linux-oem-5.6 source package in Focal: Triaged Bug description: this bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931649/+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 1931649] Re: alsa: the output volume can't be adjusted on the Lenovo machines with Bass speaker
** Description changed: - this bug is for tracking purpose. + [Impact] + Users could adjust the speaker's output volume from UI, but the sound + doesn't change with the user's adjustment. + + [Fix] + Backport 2 upstream patches, these patches are merged to 5.8.0-generic + with stable update, but not in 5.6-oem yet. + + [Test] + run amixer contents | grep DAC1, we could see the DAC1 mixer control + is found, adjust the speaker's volume from gnome-sound-setting, then + play some sound, we could hear the sound's volume is changed with our + adjustment. + + + [Where problems could occur] + This could possibly introduce the speaker output doesn't work anymore + on lenovo machines with dual speakers, but this posibility is very low, + I have tested the patches on 3 different lenovo machines with dual + speakers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1931649 Title: alsa: the output volume can't be adjusted on the Lenovo machines with Bass speaker Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: Triaged Status in linux-oem-5.6 source package in Focal: Triaged Bug description: [Impact] Users could adjust the speaker's output volume from UI, but the sound doesn't change with the user's adjustment. [Fix] Backport 2 upstream patches, these patches are merged to 5.8.0-generic with stable update, but not in 5.6-oem yet. [Test] run amixer contents | grep DAC1, we could see the DAC1 mixer control is found, adjust the speaker's volume from gnome-sound-setting, then play some sound, we could hear the sound's volume is changed with our adjustment. [Where problems could occur] This could possibly introduce the speaker output doesn't work anymore on lenovo machines with dual speakers, but this posibility is very low, I have tested the patches on 3 different lenovo machines with dual speakers. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931649/+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 1930976] Re: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
Unmarking as a duplicate of bug 1930733. It doesn't look like the same issue. Bas, please remember to follow the instructions in comment #4. ** This bug is no longer a duplicate of bug 1930733 Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930976 Title: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers Status in linux-hwe-5.8 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Kernel: 5.8.0-55 The last kernel destroyed my Ubuntu 20.04.02 installation, something went wrong with some kernel packages. It seems like Ubuntu is unable to find my video card correctly and the device drivers from Nvidia don't seem to work anymore. I had to do a clean installation, but even that doesn't solve the problem. I think this is a serious issue that needs to be looked into. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jun 5 16:50:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation Device [10de:2206] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:403f] InstallationDate: Installed on 2021-06-05 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=4984fe2f-d45f-4734-884c-2426bcf10ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33j dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33j:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1930976/+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 1931475] Re: Ubuntu only stable in safe graphics mode
Those logs are from kernel 5.10.0-1029-oem so reassigning... ** Package changed: linux (Ubuntu) => linux-oem-5.10 (Ubuntu) ** Summary changed: - Ubuntu only stable in safe graphics mode + [i915] [Comet Lake] Ubuntu only stable in safe graphics mode ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** 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/1931475 Title: [i915] [Comet Lake] Ubuntu only stable in safe graphics mode Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Incomplete Bug description: Brand new machine, Intel i5, Brand new install of 20.04 ubuntu using 5.11.0-18 kernel. BIOS updated to recent firmware. (5/11/2021 date) Machine will only stay running in safe graphics mode. When booting normal, GUI loads for about 5 seconds then reboots. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 9 14:04:22 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-06-09 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard SK-8115 Bus 001 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 7: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=5e92baa8-faf7-43e0-ab03-c43a1ec8a549 ro recovery nomodeset dis_ucode_ldr text SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2021 dmi.bios.release: 16.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1605 dmi.board.asset.tag: Default string dmi.board.name: PRIME B460-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1605:bd04/07/2021:br16.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB460-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.apport.crashdb.conf: 2021-06-09T13:25:26.012453 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931475/+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 1930275] Re: [nvidia] System does not wake up after suspend
Thanks. That indeed just shows a sleeping system. No evidence of waking up. This is probably a driver or kernel issue and since Ubuntu 20.10 is about to reach end-of-life I suggest upgrading to Ubuntu 21.04 which has a very different kernel. Or if you want a release with a long lifecycle then install 20.04 instead. Please let us know if 21.04 or 20.04 has the same bug so as to avoid this bug closing next month. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930275 Title: [nvidia] System does not wake up after suspend Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Ubuntu 20.10 suspend is not working. After suspend it does not wake up. And I have to hard reboot machine. It is happening since last few days. Here is error message I see from logs: "Failed to start Application launched by gnome-session-binary. A start job for unit UNIT has finished with a failure. The job identifier is 368 and the job result is failed. Failed to start LSB: OpenIPMI Driver init script. A start job for unit openipmi.service has finished with a failure. The job identifier is 151 and the job result is failed. " ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.73.01 Thu Apr 1 21:40:36 UTC 2021 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 09:04:06 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.73.01, 5.8.0-50-generic, x86_64: installed nvidia, 460.73.01, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU106 [GeForce RTX 2060 SUPER] [3842:3061] InstallationDate: Installed on 2020-02-15 (471 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=ae47d531-67a5-47ff-ba8c-fd3928cd4cad ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7b:bd09/17/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To
