[Kernel-packages] [Bug 1920699] Re: package nvidia-dkms-460-server (not installed) failed to install/upgrade: installed nvidia-dkms-460-server package post-installation script subprocess returned erro
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1920699 Title: package nvidia-dkms-460-server (not installed) failed to install/upgrade: installed nvidia-dkms-460-server package post- installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-460-server package in Ubuntu: Confirmed Bug description: I'm currently trying to fix my NVIDIA drivers and can't seem to do it as it crashes when I tried to run it. I already tried reinstalling the drivers, but I can't fix it ;( ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460-server (not installed) ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Mar 21 22:23:02 2021 ErrorMessage: installed nvidia-dkms-460-server package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-03-20 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-460-server Title: package nvidia-dkms-460-server (not installed) failed to install/upgrade: installed nvidia-dkms-460-server package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1920699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Well, I found, for my computer, the bus nuber is different : numpad light on : sudo i2ctransfer -f -y 14 w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07 0x00 0x0d 0x14 0x03 0x01 0xa Numpad light off sudo i2ctransfer -f -y 14 w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07 0x00 0x0d 0x14 0x03 0x00 0xad But, is there a way to integrate this in the script to enable backlight when activating the numpad and switch it off when deactivating ? I can understand that this is difficult to do it universally because it seems that we have different bus numbers for the light, but can I integrate this in the script, and if yes, where in the script ? Anyway, many thanks for this super job. Fred -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926579] Re: On TGL platforms screen shows garbage when browsing website by scrolling mouse
** 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/1926579 Title: On TGL platforms screen shows garbage when browsing website by scrolling mouse Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact] On Dell TGL platforms screen shows garbage when browsing website by scrolling mouse [Fix] This patch fixes the issue https://patchwork.freedesktop.org/patch/430153/?series=89348&rev=1 [Test] Verified on Dell TGL-H platforms. [Where problems could occur] It disable PSR2 on A0 and B0 TGL-H platforms, should introduce no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927067] Re: Add s2idle support on AMD Renoir and Cezanne
** Changed in: linux-oem-5.10 (Ubuntu Focal) 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/1927067 Title: Add s2idle support on AMD Renoir and Cezanne Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux 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: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] S2idle doesn't work on AMD Renoir and Cezanne. [Fix] Backport AMD PMC driver and pull many new patches let AMDGPU support s2idle. [Test] Suspend the laptop and the system freezes. With the patch applied, suspend works but with some caveats: 1) Keyboard sometimes can't wake up the laptop. 2) Touchpad sometimes can wake up the laptop. 3) RTC can't wake up the laptop. (Hardware Limitation) [Where problems could occur] Most changes are limited to logic of suspend/resume, and specific to Renoir GFX. However, there are some refactoring patches may cause unintended results, so AMDGPU may break for sleep/hibernation/runtime suspend on non-Renoir GFXs. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1927067/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926030] Re: IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Groovy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1926030
Title:
IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Groovy:
Confirmed
Bug description:
[Impact]
Patch:
* media: rc: fix timeout handling after switch to microsecond durations
* media: rc: ite-cir: fix min_timeout calculation
Were applied to Groovy with our stable update process (bug 1918516)
User reported that IR Remote key press will be repeated for multiple times
with these patches applied.
Commit 528222d853f92 ("media: rc: harmonize infrared durations to
microseconds") that needs to be fixed by these two does not exist in
5.8 kernel. The patch author Matthias Reichl also state these are for
5.10 and onward.
[Fix]
Revert these two patches for groovy.
[Test]
Test kernels for G-5.8 / F-5.8 can be found here:
https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/
User Ted L confirmed that F-5.8 test kernel can fix the problem.
[Where problems could occur]
The chance to cause regression can be considered as low since the original
patch that need to be fix by these two patches does not exist in 5.8 at all.
[Original Bug Report]
I use an IR remote with the ir-keytable package. Everything was working fine
until kernel 5.8.0-49 was automatically installed by Software Updater on Ubuntu
20.04.2. When any key is pressed on the remote, the key is repeated about 500
times. The kernel is now 5.8.0-50, and the problem persists.
Other users on the MythTV mailing list are reporting the issue, and it
appears that the problem is related to changes in the following files:
drivers/media/rc/ir-mce_kbd-decoder.c
drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c
drivers/media/rc/serial_ir.c
It has been reported that reverting the ir-mce_kbd-decoder.c and rc-
main.c files to the older versions fixes the problem.
/proc/version_signature > version.log:
Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
lspci -vnvn:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core
Processor Host Bridge/DRAM Registers [8086:590f] (rev 06)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host
Bridge/DRAM Registers [1043:8694]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-
Kernel driver in use: skl_uncore
ir-keytable -V:
IR keytable control version 1.18.0
lsb_release -rd:
Description: Ubuntu 20.04.2 LTS
Release: 20.04
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ted1020 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-09-19 (217 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IwConfig:
lono wireless extensions.
enp3s0no wireless extensions.
enp0s31f6 no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic
root=UUID=529cae8e-19cd-4732-80d5-b3dca123afc6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
RelatedPackageVersions:
linux-restricted-modules-5.8.0-50-generic N/A
linux-backports-modules-5.8.0-50-generic N/A
linux-firmware1.187.11
RfKill:
Tags: focal
Uname: Linux 5.8.0-50-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd mythtv plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/05/2017
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3405
dmi.board.asset.tag: Default string
dmi.board.name: H110T
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.:bvr3405:bd07/05/2017:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110T:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name:
[Kernel-packages] [Bug 1770845] Re: Make vfio-pci built-in or xhci_hcd optional
** Changed in: linux-kvm (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux (Ubuntu Cosmic) Status: Opinion => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1770845 Title: Make vfio-pci built-in or xhci_hcd optional Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: New Status in linux source package in Cosmic: Invalid Status in linux-kvm source package in Cosmic: Invalid Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: In Progress Bug description: [Impact] This allows vfio-pci to be bound to certain devices during boot, preventing other drivers from binding them. In particular, USB host drivers, like xhci_hcd, are hard to unbind, as USB devices may end up being used by applications. [Test case] Boot the system with vfio-pci.ids=8086:1e31 or other device ID. [Regression potential] Check that VFIO does not bind to any other device. -- Because of nazar-pc@nazar-pc ~> cat '/boot/config-4.15.0-21-generic' | grep CONFIG_USB_XHCI_HCD CONFIG_USB_XHCI_HCD=y Following doesn't work: nazar-pc@nazar-pc ~> cat /etc/modprobe.d/gpu-passthrough.conf options vfio-pci ids=10de:1b06,10de:10ef,1b21:2142 softdep nouveau pre: vfio-pci softdep xhci_hcd pre: vfio-pci GPU is fine (first 2 IDs), but USB controller is always occupied by xhci_hcd and I can't change that while xhci_hcd is built-in. I'd like you to resolve this issue by either embedding vfio-pci module too (prefered solution) or making xhci_hcd optional. There are some discussions withot clean solution online like this: https://www.reddit.com/r/VFIO/comments/4o6wla/cant_get_vfiopci_to_bind_to_usb_30_card_at_boot/ ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-21-generic 4.15.0-21.22 ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 Uname: Linux 4.15.0-21-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-21-generic. ApportVersion: 2.20.10-0ubuntu2 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: S51 [SB Omni Surround 5.1], device 0: USB Audio [USB Audio] Subdevices: 0/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: nazar-pc 2226 F...m pulseaudio /dev/snd/pcmC1D0p: nazar-pc 2226 F...m pulseaudio /dev/snd/controlC1: nazar-pc 2226 F pulseaudio nazar-pc 2267 F volumeicon Card1.Amixer.info: Card hw:1 'S51'/'Creative Technology Ltd SB Omni Surround 5.1 at usb-:00:14.0-9.2, full spee' Mixer name : 'USB Mixer' Components : 'USB041e:322c' Controls : 12 Simple ctrls : 5 CurrentDesktop: Custom Date: Sat May 12 16:44:11 2018 IwConfig: Error: [Errno 2] Немає такого файла або каталогу: 'iwconfig': 'iwconfig' MachineType: Micro-Star International Co., Ltd. MS-7B45 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/root/boot/vmlinuz-4.15.0-21-generic root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root nosplash intel_pstate=disable scsi_mod.use_blk_mq=1 intel_iommu=on RelatedPackageVersions: linux-restricted-modules-4.15.0-21-generic N/A linux-backports-modules-4.15.0-21-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] Немає такого файла або каталогу: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.51 dmi.board.asset.tag: Default string dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.51:bd03/29/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7B45 dmi.product.version: 2.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/1770845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Hello, Running fine on my asus UX363EA. Numpad working great, but I did not find a way to activate the backlight of the numpad. Did I miss something ? Anyway thanks for this great job. Fred -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 just had another freeze but unlike in the past I was still in the desktop and did not go into the terminal view. I was able to switch to the terminal but I was not able to run any commands like 'cat /var/log/dmesg' or 'dmesg'. I have seen this in the past where all the icons including the icons in the notification area and favorites become blank icons but I have not been able to do anything. I tried to run ubuntu-bug from the terminal but it didn't start and showed io error. Is there any command I should have run when I run into this scenario? I rebooted into a live usb and ran fsck and badblock. No errors. sudo badblocks -nsv /dev/nvme0n1p7 Checking for bad blocks in non-destructive read-write mode >From block 0 to 97655807 Checking for bad blocks (non-destructive read-write test) Testing with random pattern: done Pass completed, 0 bad blocks found. (0/0/0 errors) sudo e2fsck -fcck /dev/nvme0n1p7 e2fsck 1.45.7 (28-Jan-2021) Checking for bad blocks (non-destructive read-write test) Testing with random pattern: done /dev/nvme0n1p7: Updating bad block inode. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/nvme0n1p7: * FILE SYSTEM WAS MODIFIED * /dev/nvme0n1p7: 248682/6111232 files (1.4% non-contiguous), 4843265/24413952 blocks -- 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
[Kernel-packages] [Bug 1918794] Re: Kernel panic on HP m400 cartridge when deploying Groovy
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918794 Title: Kernel panic on HP m400 cartridge when deploying Groovy Status in linux package in Ubuntu: Expired Bug description: hostname ms10-35-mcdivittB0-kernel IP-Config: no response after 2 secs - giving up IP-Config: enp1s0 hardware address 14:58:d0:58:c3:c2 mtu 1500 DHCP RARP hostname ms10-35-mcdivittB0-kernel hostname ms10-35-mcdivittB0-kernel IP-Config: enp1s0 complete (dhcp from 10.229.32.21): address: 10.229.65.135broadcast: 10.229.255.255 netmask: 255.[ 112.101878] random: crng init done 255.0.0 gateway: 10.229.0.1 dns0 : 10.229.32.21[ 112.182113] Unable to handle kernel read from unreadable memory at virtual address 0068 dns1 : 10.229.32.21 domain : maas [ 112.357410] Mem abort info: rootserver: 10.229.[ 112.457556] ESR = 0x9604 32.21 rootpath: filename : lpxelinux.0 :: root=squash:http:[ 112.560827] EC = 0x25: DABT (current EL), IL = 32 bits //10.229.32.21:5248/images/ubuntu/arm64/xgene-uboot/groovy/stabl[ 112.691226] SET = 0, FnV = 0 e/squashfs :: mount_squash downloading http://10.229.32.21:5248[ 112.794511] EA = 0, S1PTW = 0 /images/ubuntu/arm64/xgene-uboot/groovy/stable/squashfs to /root[ 112.898829] Data abort info: .tmp.img Connecting to 10.229.32.21:5248 (10.229.32.21:5248) [ 113.19] ISV = 0, ISS = 0x0004 root.tmp.img 1% || 354[ 113.112681] CM = 0, WnR = 0 root.tmp.img [ 113.214909] user pgtable: 4k pages, 48-bit VAs, pgdp=004f97498000 4% [ 113.330702] [0068] pgd=, p4d= |* | 14.6M 0:00:43 ETA[ 113.417300] Internal error: Oops: 9604 [#1] SMP [ 113.530986] Modules linked in: raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx4_ib ib_uverbs ib_core mlx4_en gpio_keys_polled mlx4_core ahci_xgene gpio_dwapb crct10dif_ce gpio_xgene_sb aes_neon_bs aes_neon_blk crypto_simd cryptd [ 113.869103] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.8.0-44-generic #50-Ubuntu [ 113.958919] Hardware name: HP ProLiant m400 Server Cartridge (DT) [ 114.031945] pstate: 6045 (nZCv daif +PAN -UAO BTYPE=--) [ 114.098717] pc : mlx4_en_poll_rx_cq+0xac/0x180 [mlx4_en] [ 114.162459] lr : mlx4_en_poll_rx_cq+0x7c/0x180 [mlx4_en] [ 114.226193] sp : 800010003dc0 [ 114.265834] x29: 800010003dc0 x28: 800012182f80 [ 114.329470] x27: 800011c09088 x26: 000ff7eae300 [ 114.393104] x25: 800012176000 x24: 000f95ea0900 [ 114.456740] x23: 000fa87b8d08 x22: 000fa87b8c00 [ 114.520376] x21: 000f95ea x20: 0040 [ 114.584011] x19: 0040 x18: [ 114.647645] x17: x16: 0003 [ 114.711280] x15: 0030 x14: [ 114.774916] x13: 800090003b07 x12: 0006 [ 114.838551] x11: 0040 x10: 0040 [ 114.902187] x9 : 89072448 x8 : 000f95fa [ 114.965822] x7 : x6 : 004fec96c000 [ 115.029457] x5 : 00c896ec4f00 x4 : 00020a20 [ 115.093093] x3 : 0001 x2 : [ 115.156728] x1 : x0 : [ 115.220364] Call trace: [ 115.249578] mlx4_en_poll_rx_cq+0xac/0x180 [mlx4_en] [ 115.309144] napi_poll+0xc4/0x264 [ 115.348887] net_rx_action+0xd4/0x26c [ 115.392702] __do_softirq+0x128/0x364 [ 115.436621] irq_exit+0xac/0x100 [ 115.475219] __handle_domain_irq+0x8c/0xf0 [ 115.524247] gic_handle_irq+0x60/0xc0 [ 115.568062] el1_irq+0x104/0x1c0 [ 115.606662] arch_cpu_idle+0x40/0x1e0 [ 115.650477] cpuidle_idle_call+0x184/0x230 [ 115.699506] do_idle+0xb0/0x100 [ 115.737060] cpu_startup_entry+0x30/0xb0 [ 115.784006] rest_init+0xc4/0xd4 [ 115.822605] arch_call_rest_init+0x1c/0x28 [ 115.952142] start_kernel+0x474/0x4ac [ 115.995961] Code: f9415ac0 715f 1100fc41 1a82b021 (f9403400) [ 116.069094] ---[ end trace 04b92c50255aaf57 ]--- [ 116.124486] Kernel panic - not syncing: Fatal exception in interrupt [ 116.200641] SMP: stopping secondary CPUs [ 116.247692] Kernel Offset: 0x8 from 0x80001000 [ 116.313512] PHYS_OFFSET: 0x40 [ 116.357328] CPU features: 0x24,20802000 [ 116.407400] Memory Limit: none [ 116.443917] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]--- To m
[Kernel-packages] [Bug 1651500] Re: [ASUS X441SA] [8086:2284] No sound at all
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651500 Title: [ASUS X441SA] [8086:2284] No sound at all Status in linux package in Ubuntu: Expired Bug description: 1. Release of ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 2. version of the package AlsaMixer v1.1.0 3. I expect to hear sound from speaker 4. I can not any sound from speaker ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamda 1627 F pulseaudio CurrentDesktop: Unity Date: Tue Dec 20 22:51:08 2016 InstallationDate: Installed on 2016-12-15 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamda 1627 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X441SA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X441SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX441SA.301:bd08/08/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X441SA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904339] Re: kernel 5.4.0-53 (amd64) won't shut down
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904339 Title: kernel 5.4.0-53 (amd64) won't shut down Status in linux package in Ubuntu: Expired Bug description: Whenever using the "Shutdown" button in Linux Mint 20 Cinnamon, laptop GUI disappears until only a white cursor on black background appears. Cursor does not blink. No other messages or text. Same when using "shutdown" in terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928138] Re: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached]
No, I made it for myself (using another patch (https://bugs.freedesktop.org/show_bug.cgi?id=91393#c31) as a reference for adding i915 module parameter). Not sure if upstream would accept it. This patch doesn't fix root issue but provides ability to disable DRRS power-saving feature which causes it (I didn't find any other way to do that). By the way, Intel® Graphics Command Center on Windows also has an option to enable/disable "Dynamic Refresh Rate Switching" (https://www.intel.com/content/www/us/en/support/articles/57188/graphics.html). ** Bug watch added: freedesktop.org Bugzilla #91393 https://bugs.freedesktop.org/show_bug.cgi?id=91393 -- 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/1928138 Title: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached] Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) has a pretty serious issue with flickering Symptoms: 1) If I leave mouse cursor for a few seconds, then start moving it, there's a slight flicker (like display brightness changes a bit). There's also some flickering even without user interactions. 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M dmesg shows constant refresh rate changes (even if it's set to 40HZ) [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz nomodeset boot option eliminates flickering Turns out Display Refresh Rate Switching (DRRS) feature doesn't work correctly here. It was implemented on kernels 4.0...4.1 but on a particular machine flickering started with 4.1. As a workaround I'm attaching a patch which disables DRRS by default and adds module parameter "enable_drrs" to activate it. It's made for kernel 5.12 and should work for older versions as well (tested with 5.11). Until this issue is resolved, please consider adding parameter to disable DRRS. Windows has such option on Intel® Graphics Command Center. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1928138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928138] Re: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached]
Is the patch in upstream Linux? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1928138 Title: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached] Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) has a pretty serious issue with flickering Symptoms: 1) If I leave mouse cursor for a few seconds, then start moving it, there's a slight flicker (like display brightness changes a bit). There's also some flickering even without user interactions. 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M dmesg shows constant refresh rate changes (even if it's set to 40HZ) [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz nomodeset boot option eliminates flickering Turns out Display Refresh Rate Switching (DRRS) feature doesn't work correctly here. It was implemented on kernels 4.0...4.1 but on a particular machine flickering started with 4.1. As a workaround I'm attaching a patch which disables DRRS by default and adds module parameter "enable_drrs" to activate it. It's made for kernel 5.12 and should work for older versions as well (tested with 5.11). Until this issue is resolved, please consider adding parameter to disable DRRS. Windows has such option on Intel® Graphics Command Center. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1928138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917194] Re: [Dell G5 5590] lspci freezes computer on Ubuntu 20.04
** Changed in: linux (Ubuntu) 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/1917194 Title: [Dell G5 5590] lspci freezes computer on Ubuntu 20.04 Status in linux package in Ubuntu: Fix Committed Bug description: After upgrading from Ubuntu 18.04 to 20.04 my computer started to freeze when running lspci. I ended up noticing that it happened when trying to query device '1f:00.0' a USB port. After some kernel and bios updates the problem got worse. Now the computer freezes ~5 seconds after booting up. I tried: 1) Running in recovery mode, also freezes 2) Running an older kernel version (5.4.0-66-generic), also freezes 3) Removing nvidia drivers (just in case), also freezes 4) Running all combinations nodemodeset, acpi=off an nouveau blacklisting 5) Updating all drivers The computer freezes for ever, I can't switch TTYs, move the mouse, anything, the only way to leave was to force shutdown. On the last cases after switching to a tty I could see this messages before the freeze ocurred: kernel: xhci_hcd :1f:00.0: PCI post-resume error -19! kernel: xhci_hcd :1f:00.0: HC died; cleaning up Running Ubuntu 20.04 from a USB sticks works fine, as well as doing a fresh install. All logs were obtained by chrooting to the faulty partition from a fresh install, if there are any more logs that would be helpful, let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
@markb, ok thanks ** Changed in: linux (Ubuntu) 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/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: Fix Committed Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 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 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928138] Re: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached]
** Tags added: patch -- 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/1928138 Title: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached] Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) has a pretty serious issue with flickering Symptoms: 1) If I leave mouse cursor for a few seconds, then start moving it, there's a slight flicker (like display brightness changes a bit). There's also some flickering even without user interactions. 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M dmesg shows constant refresh rate changes (even if it's set to 40HZ) [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz nomodeset boot option eliminates flickering Turns out Display Refresh Rate Switching (DRRS) feature doesn't work correctly here. It was implemented on kernels 4.0...4.1 but on a particular machine flickering started with 4.1. As a workaround I'm attaching a patch which disables DRRS by default and adds module parameter "enable_drrs" to activate it. It's made for kernel 5.12 and should work for older versions as well (tested with 5.11). Until this issue is resolved, please consider adding parameter to disable DRRS. Windows has such option on Intel® Graphics Command Center. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1928138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927409] Re: Race between isotp_bind and isotp_setsockopt
** Summary changed:
- Race between two functions
+ Race between isotp_bind and isotp_setsockopt
--
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/1927409
Title:
Race between isotp_bind and isotp_setsockopt
Status in linux package in Ubuntu:
Fix Released
Bug description:
A race condition in the CAN ISOTP networking protocol was discovered
which allows forbidden changing of socket members after binding
the socket.
In particular, the lack of locking behavior in isotp_setsockopt()
makes it feasible to assign the flag CAN_ISOTP_SF_BROADCAST to the
socket, despite having previously registered a can receiver. After
closing the isotp socket, the can receiver will still be registered
and use-after-free's can be triggered in isotp_rcv() on the freed
isotp_sock structure. This leads to arbitrary kernel execution by
overwriting the sk_error_report()pointer, which can be misused in
order to execute a user-controlled ROP chain to gain root privileges.
The vulnerability was introduced with the introduction of SF_BROADCAST
support in commit 921ca574cd38 ("can: isotp: add SF_BROADCAST support
for functional addressing") in 5.11-rc1. In fact, commit 323a391a220c
("can: isotp: isotp_setsockopt(): block setsockopt on bound sockets")
did not effectively prevent isotp_setsockopt() from modifying socket
members before isotp_bind().
Credits: Norbert Slusarek
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927409/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On Hours: 76 Unsafe Shutdowns
[Kernel-packages] [Bug 1927866] Re: Root filesystem becomes readonly frequenty freezing system
Thanks for looking into this issue Chris. Thanks for pointing about ubuntu-bug and apport and the bug reporting guidelines. Will do so in the future. -- 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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20
[Kernel-packages] [Bug 1927866] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496491/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power O
[Kernel-packages] [Bug 1927866] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496487/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power
[Kernel-packages] [Bug 1927866] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496492/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On Ho
[Kernel-packages] [Bug 1927866] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496482/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On Hour
[Kernel-packages] [Bug 1927866] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496484/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power
[Kernel-packages] [Bug 1927866] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496479/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On Ho
[Kernel-packages] [Bug 1927866] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496488/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On
[Kernel-packages] [Bug 1927866] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496481/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On Hour
[Kernel-packages] [Bug 1927866] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496478/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On Hours:
[Kernel-packages] [Bug 1927866] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496489/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On Hours:
[Kernel-packages] [Bug 1927866] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496486/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20
[Kernel-packages] [Bug 1927866] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496490/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On Hours:
[Kernel-packages] [Bug 1927866] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496483/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On Hours:
[Kernel-packages] [Bug 1927866] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496485/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles:
[Kernel-packages] [Bug 1927866] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496476/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Pow
[Kernel-packages] [Bug 1927866] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496477/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On Ho
[Kernel-packages] [Bug 1927866] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496480/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On Hours:
[Kernel-packages] [Bug 1927866] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1927866/+attachment/5496475/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On Hours:
[Kernel-packages] [Bug 1927866] Re: Root filesystem becomes readonly frequenty freezing system
apport information ** Tags added: apport-collected hirsute wayland-session ** Description changed: 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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On Hours: 76 Unsafe Shutdowns: 9 Media and Data Integrity Errors:0 Error Information Log Entries: 1 Warning Comp. Temperature Time:0 Critical Comp. Temperature Time:0 Error Information (NVMe Log 0x01, 16 of 256 entries) No Errors Logged ==
[Kernel-packages] [Bug 1927866] Re: Root filesystem becomes readonly frequenty freezing system
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1927866 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927866 Title: Root filesystem becomes readonly frequenty freezing system Status in linux package in Ubuntu: New 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:
[Kernel-packages] [Bug 1927866] Re: Root filesystem becomes readonly frequenty freezing system
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 ** Package changed: 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/1927866 Title: Root filesystem becomes readonly frequenty freezing system Status in linux package in Ubuntu: New 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:
[Kernel-packages] [Bug 1927866] [NEW] Root filesystem becomes readonly frequenty freezing system
You have been subscribed to a public bug: 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 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On Hours: 76 Unsafe Shutdowns: 9 Media and Data Integrity Errors:0 Error Information Log Entries: 1 Warning Comp. Temperature Time:0 Critical Comp. Temperature Time:0 Error Information (NVMe Log 0x01, 16 of 256 entries) No Errors Logged = = cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be us
[Kernel-packages] [Bug 1928146] Re: Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73
** Description changed:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe >= 460.73 and nvidia-settings >= 460.73.
This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be synchronized to match the
other versions provided in this and all future nvidia-drivers-*
metapackages? This should resolve the issue forever going forward.
+
+
+ Debdiffs:
+
+ Hirsute: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
+ /nvidia-
+ settings_460.56-0ubuntu2_460.73.01-0ubuntu1~ubuntu21.04.1~ppa1.diff.gz
+
+ Groovy: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
+ /nvidia-
+ settings_440.82-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.10.1~ppa1.diff.gz
+
+ Focal:
+
https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files/nvidia-settings_440.64-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.04.1~ppa1.diff.gz
** Changed in: nvidia-modprobe (Ubuntu Hirsute)
Importance: Undecided => High
** Changed in: nvidia-modprobe (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: nvidia-modprobe (Ubuntu Focal)
Importance: Undecided => High
** Changed in: nvidia-settings (Ubuntu Focal)
Importance: Undecided => High
** Changed in: nvidia-settings (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: nvidia-settings (Ubuntu Hirsute)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1928146
Title:
Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73
Status in nvidia-modprobe package in Ubuntu:
Fix Released
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in nvidia-modprobe source package in Focal:
New
Status in nvidia-settings source package in Focal:
New
Status in nvidia-modprobe source package in Groovy:
New
Status in nvidia-settings source package in Groovy:
New
Status in nvidia-modprobe source package in Hirsute:
New
Status in nvidia-settings source package in Hirsute:
New
Status in nvidia-modprobe source package in Impish:
Fix Released
Status in nvidia-settings source package in Impish:
Fix Released
Bug description:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe >= 460.73 and nvidia-settings >= 460.73.
This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo
[Kernel-packages] [Bug 1927409] Re: Race between two functions
** Information type changed from Private Security to Public Security
--
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/1927409
Title:
Race between two functions
Status in linux package in Ubuntu:
Fix Released
Bug description:
A race condition in the CAN ISOTP networking protocol was discovered
which allows forbidden changing of socket members after binding
the socket.
In particular, the lack of locking behavior in isotp_setsockopt()
makes it feasible to assign the flag CAN_ISOTP_SF_BROADCAST to the
socket, despite having previously registered a can receiver. After
closing the isotp socket, the can receiver will still be registered
and use-after-free's can be triggered in isotp_rcv() on the freed
isotp_sock structure. This leads to arbitrary kernel execution by
overwriting the sk_error_report()pointer, which can be misused in
order to execute a user-controlled ROP chain to gain root privileges.
The vulnerability was introduced with the introduction of SF_BROADCAST
support in commit 921ca574cd38 ("can: isotp: add SF_BROADCAST support
for functional addressing") in 5.11-rc1. In fact, commit 323a391a220c
("can: isotp: isotp_setsockopt(): block setsockopt on bound sockets")
did not effectively prevent isotp_setsockopt() from modifying socket
members before isotp_bind().
Credits: Norbert Slusarek
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927409/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928146] Re: Please SRU nvidia-modprobe and nvidia-settings 460.73
This bug was fixed in the package nvidia-modprobe - 465.24.02-1
---
nvidia-modprobe (465.24.02-1) experimental; urgency=medium
* New upstream release. (Closes: #987744)
-- Luca Boccassi Thu, 29 Apr 2021 11:48:45 +0100
** Description changed:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe 460.73 and nvidia-settings 460.73.
- This is impacting data scientists and AI learning customers, which are
- target customers of the Kubuntu Focus laptops produced by
- MindShareManagement
+ This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be synchronized to match the
other versions provided in this and all future nvidia-drivers-*
metapackages? This should resolve the issue forever going forward.
** Changed in: nvidia-modprobe (Ubuntu)
Status: New => Fix Released
** Summary changed:
- Please SRU nvidia-modprobe and nvidia-settings 460.73
+ Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73
** Description changed:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
- dependency on nvidia-modprobe 460.73 and nvidia-settings 460.73.
+ dependency on nvidia-modprobe >= 460.73 and nvidia-settings >= 460.73.
This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be s
[Kernel-packages] [Bug 1928146] Re: Please SRU nvidia-modprobe and nvidia-settings 460.73
** Changed in: nvidia-modprobe (Ubuntu Impish)
Status: Fix Released => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1928146
Title:
Please SRU nvidia-modprobe and nvidia-settings 460.73
Status in nvidia-modprobe package in Ubuntu:
Fix Released
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in nvidia-modprobe source package in Focal:
New
Status in nvidia-settings source package in Focal:
New
Status in nvidia-modprobe source package in Groovy:
New
Status in nvidia-settings source package in Groovy:
New
Status in nvidia-modprobe source package in Hirsute:
New
Status in nvidia-settings source package in Hirsute:
New
Status in nvidia-modprobe source package in Impish:
Fix Released
Status in nvidia-settings source package in Impish:
Fix Released
Bug description:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe 460.73 and nvidia-settings 460.73.
This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show
below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be synchronized to match the
other versions provided in this and all future nvidia-drivers-*
metapackages? This should resolve the issue forever going forward.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-modprobe/+bug/1928146/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928146] [NEW] Please SRU nvidia-modprobe and nvidia-settings 460.73
Public bug reported:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe 460.73 and nvidia-settings 460.73.
This is impacting data scientists and AI learning customers, which are
target customers of the Kubuntu Focus laptops produced by
MindShareManagement
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be synchronized to match the
other versions provided in this and all future nvidia-drivers-*
metapackages? This should resolve the issue forever going forward.
** Affects: nvidia-modprobe (Ubuntu)
Importance: Undecided
Status: New
** Affects: nvidia-settings (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: nvidia-modprobe (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: nvidia-settings (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: nvidia-modprobe (Ubuntu Groovy)
Importance: Undecided
Status: New
** Affects: nvidia-settings (Ubuntu Groovy)
Importance: Undecided
Status: New
** Affects: nvidia-modprobe (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Affects: nvidia-settings (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Affects: nvidia-modprobe (Ubuntu Impish)
Importance: Undecided
Status: New
** Affects: nvidia-settings (Ubuntu Impish)
Importance: Undecided
Status: Fix Released
** Tags: oem-priority
** Also affects: nvidia-settings (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-settings (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nvidia-modprobe (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nvidia-settings (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: nvidia-modprobe (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: nvidia-settings (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: nvidia-modprobe (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: nvidia-settings (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: nvidia-modprobe (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: nvidia-settings (Ubuntu Impish)
Status: New => Fix Released
** Changed in: nvidia-modprobe (Ubuntu Impish)
Status: New => Fix Released
** Description changed:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe 460.73 and nvidia-settings 460.73.
This is impacting data scientists and AI learning customers, which are
target customers of the Kubuntu Focus laptops produced by
MindShareManagement
-
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
-
* Ensure nvidia and
[Kernel-packages] [Bug 1925522] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-460 into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-460/460.80-0ubuntu0.21.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: In Progress Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: In Progress Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: In Progress Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: In Progress Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 series to the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 450-server == * New upstream release (LP: #1925522). - Fixed an issue with the NSCQ library that caused clients such as DCGM to fail to load the library. Since the NSCQ library version needs to match the driver version, the user would encounter a version mismatch issue when using DCGM. - Fixed an ECC policy that caused a CUDA malloc failure after encountering a single uncorrectable error. == 460 == * debian/templ
[Kernel-packages] [Bug 1925386] Re: Upgrade from 460.32.03-0ubuntu2 to 460.73.01-0ubuntu1 fails
Hello dann, or anyone else affected, Accepted nvidia-graphics-drivers-460 into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-460/460.80-0ubuntu0.21.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Hirsute) Status: New => Fix Committed -- 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/1925386 Title: Upgrade from 460.32.03-0ubuntu2 to 460.73.01-0ubuntu1 fails Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Committed Bug description: ubuntu@dgx-1-exotic-skunk-201710-25896:~$ sudo apt install nvidia-dkms-460-server nvidia-utils-460-server Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: nvidia-kernel-common-460-server Suggested packages: nvidia-driver-460-server The following packages will be upgraded: nvidia-dkms-460-server nvidia-kernel-common-460-server nvidia-utils-460-server 3 upgraded, 0 newly installed, 0 to remove and 37 not upgraded. Need to get 424 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu hirsute-proposed/restricted amd64 nvidia-dkms-460-server amd64 460.73.01-0ubuntu1 [42.8 kB] Get:2 http://archive.ubuntu.com/ubuntu hirsute-proposed/restricted amd64 nvidia-kernel-common-460-server amd64 460.73.01-0ubuntu1 [18.4 kB] Get:3 http://archive.ubuntu.com/ubuntu hirsute-proposed/restricted amd64 nvidia-utils-460-server amd64 460.73.01-0ubuntu1 [363 kB] Fetched 424 kB in 2s (220 kB/s) (Reading database ... 87065 files and directories currently installed.) Preparing to unpack .../nvidia-dkms-460-server_460.73.01-0ubuntu1_amd64.deb ... Removing all DKMS Modules Done. Unpacking nvidia-dkms-460-server (460.73.01-0ubuntu1) over (460.32.03-0ubuntu2) ... Preparing to unpack .../nvidia-kernel-common-460-server_460.73.01-0ubuntu1_amd64 .deb ... Unpacking nvidia-kernel-common-460-server (460.73.01-0ubuntu1) over (460.32.03-0 ubuntu2) ... Preparing to unpack .../nvidia-utils-460-server_460.73.01-0ubuntu1_amd64.deb ... Unpacking nvidia-utils-460-server (460.73.01-0ubuntu1) over (460.32.03-0ubuntu2) ... Setting up nvidia-kernel-common-460-server (460.73.01-0ubuntu1) ... update-initramfs: deferring update (trigger activated) Setting up nvidia-utils-460-server (460.73.01-0ubuntu1) ... Setting up nvidia-dkms-460-server (460.73.01-0ubuntu1) ... update-initramfs: deferring update (trigger activated) Loading new nvidia-srv-460.73.01 DKMS files... Building for 5.11.0-16-generic Building for architecture x86_64 Building initial module for 5.11.0-16-generic Error! Application of patch disable_fstack-clash-protection_fcf-protection.patch failed. Check /var/lib/dkms/nvidia-srv/460.73.01/build/ for more information. dpkg: error processing package nvidia-dkms-460-server (--configure): installed nvidia-dkms-460-server package post-installation script subprocess re turned error exit status 6 Processing triggers for man-db (2.9.4-2) ... Processing triggers for initramfs-tools (0.139ubuntu3) ... update-initramfs: Generating /boot/initrd.img-5.11.0-16-generic W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast Errors were encountered while processing: nvidia-dkms-460-server needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) ubuntu@dgx-1-exotic-skunk-201710-25
[Kernel-packages] [Bug 1881015] Re: Fn Lock light does not come on to indicate when Fn Lock is enabled
The relevant patch was upstreamed in the following kernel versions: * 5.12-rc5 * 5.11.13 * 5.10.29 * 5.4.111 * 4.19.186 * 4.14.230 I recently got an email from an ubuntu user having this issue, and it's a shame to see that the patch hasn't been picked up by ubuntu yet, even in its new 21.04 release or its HWE kernels. Could it be added? For reference, the patch in question is: https://lore.kernel.org/platform-driver-x86/20210315195823.23212-1-esteve.var...@gmail.com/ -- 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/1881015 Title: Fn Lock light does not come on to indicate when Fn Lock is enabled Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo E595 running Ubuntu 20.04. The "Fn Lock" feature on the keyboard works in terms of how it modifies subsequent presses of the F1-F12 keys, but the little light on the Esc key doesn't show the current state. Example: 1. I press F5 a few times, and the screen brightness is adjusted. 2. I press Fn+Esc, and "Fn Lock" is now on, but the light hasn't changed. 3. I press F5 again, or several times, and it acts as a normal F5 (ie my browser might refresh the page). 4. I press Fn+Esc again, and "Fn Lock" is now off, but again the light hasn't changed. So, "Fn Lock" works in the sense that it modifies what keypresses do, but the little light on the Esc key doesn't come on. Under Windows the light does toggle, to show the current status. The behaviour is the same on Xorg and Wayland. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.31.36 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: paul 2138 F pulseaudio /dev/snd/controlC0: paul 2138 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 27 21:37:47 2020 InstallationDate: Installed on 2020-05-13 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NFCTO1WW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=f7c34228-ee6f-4043-931c-f4752ad503c8 ro quiet splash nomodeset vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET36W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E595 dmi.product.name: 20NFCTO1WW dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595 dmi.product.version: ThinkPad E595 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928138] Re: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bissected and workaround attached]
** Tags removed: patch ** Summary changed: - Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bissected and workaround attached] + Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached] -- 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/1928138 Title: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached] Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) has a pretty serious issue with flickering Symptoms: 1) If I leave mouse cursor for a few seconds, then start moving it, there's a slight flicker (like display brightness changes a bit). There's also some flickering even without user interactions. 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M dmesg shows constant refresh rate changes (even if it's set to 40HZ) [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz nomodeset boot option eliminates flickering Turns out Display Refresh Rate Switching (DRRS) feature doesn't work correctly here. It was implemented on kernels 4.0...4.1 but on a particular machine flickering started with 4.1. As a workaround I'm attaching a patch which disables DRRS by default and adds module parameter "enable_drrs" to activate it. It's made for kernel 5.12 and should work for older versions as well (tested with 5.11). Until this issue is resolved, please consider adding parameter to disable DRRS. Windows has such option on Intel® Graphics Command Center. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1928138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928138] Re: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bissected and workaround attached]
** Description changed: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) - has a pretty issue with flickering + has a pretty serious issue with flickering Symptoms: - 1) If I leave mouse cursor for a few seconds, then start moving it, there's slight flicker (like display brightness changes a bit) + 1) If I leave mouse cursor for a few seconds, then start moving it, there's a slight flicker (like display brightness changes a bit). There's also some flickering even without user interactions. 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M + dmesg shows constant refresh rate changes (even if it's set to 40HZ) - dmesg shows constant refresh rate changes (even if it's set to 40HZ) + [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz nomodeset boot option eliminates flickering Turns out Display Refresh Rate Switching (DRRS) feature doesn't work correctly here. It was implemented on kernels 4.0...4.1 but on a particular machine flickering started with 4.1. As a workaround I'm attaching a patch which disables DRRS by default and adds module parameter "enable_drrs" to activate it. It's made for kernel 5.12 and should work for older versions as well (tested with 5.11). Until this issue is resolved, please consider adding parameter to disable DRRS. Windows has such option on Intel® Graphics Command Center. -- 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/1928138 Title: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached] Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) has a pretty serious issue with flickering Symptoms: 1) If I leave mouse cursor for a few seconds, then start moving it, there's a slight flicker (like display brightness changes a bit). There's also some flickering even without user interactions. 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M dmesg shows constant refresh rate changes (even if it's set to 40HZ) [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz nomodeset boot option eliminates flickering Turns out Display Refresh Rate Switching (DRRS) feature doesn't work correctly here. It was implemented on kernels 4.0...4.1 but on a particular machine flickering started with 4.1. As a workaround I'm attaching a patch which disables DRRS by default and adds module parameter "enable_drrs" to activate it. It's made for kernel 5.12 and should work for older versions as well (tested with 5.11). Until this issue is resolved, please consider adding parameter to disable DRRS. Windows has such option on Intel® Graphics Command Center. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1928138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928138] Re: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bissected and workaround attached]
** Tags added: patch -- 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/1928138 Title: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached] Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) has a pretty serious issue with flickering Symptoms: 1) If I leave mouse cursor for a few seconds, then start moving it, there's a slight flicker (like display brightness changes a bit). There's also some flickering even without user interactions. 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M dmesg shows constant refresh rate changes (even if it's set to 40HZ) [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz nomodeset boot option eliminates flickering Turns out Display Refresh Rate Switching (DRRS) feature doesn't work correctly here. It was implemented on kernels 4.0...4.1 but on a particular machine flickering started with 4.1. As a workaround I'm attaching a patch which disables DRRS by default and adds module parameter "enable_drrs" to activate it. It's made for kernel 5.12 and should work for older versions as well (tested with 5.11). Until this issue is resolved, please consider adding parameter to disable DRRS. Windows has such option on Intel® Graphics Command Center. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1928138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928138] Re: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bissected and workaround attached]
** Attachment added: "Demonstration of the issue" https://bugs.launchpad.net/linux/+bug/1928138/+attachment/5496450/+files/VID_20190526_162622.mp4 -- 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/1928138 Title: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bissected and workaround attached] Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) has a pretty issue with flickering Symptoms: 1) If I leave mouse cursor for a few seconds, then start moving it, there's slight flicker (like display brightness changes a bit) 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M dmesg shows constant refresh rate changes (even if it's set to 40HZ) [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz nomodeset boot option eliminates flickering Turns out Display Refresh Rate Switching (DRRS) feature doesn't work correctly here. It was implemented on kernels 4.0...4.1 but on a particular machine flickering started with 4.1. As a workaround I'm attaching a patch which disables DRRS by default and adds module parameter "enable_drrs" to activate it. It's made for kernel 5.12 and should work for older versions as well (tested with 5.11). Until this issue is resolved, please consider adding parameter to disable DRRS. Windows has such option on Intel® Graphics Command Center. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1928138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928138] [NEW] Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bissected and workaround attached]
Public bug reported: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) has a pretty issue with flickering Symptoms: 1) If I leave mouse cursor for a few seconds, then start moving it, there's slight flicker (like display brightness changes a bit) 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M dmesg shows constant refresh rate changes (even if it's set to 40HZ) [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz nomodeset boot option eliminates flickering Turns out Display Refresh Rate Switching (DRRS) feature doesn't work correctly here. It was implemented on kernels 4.0...4.1 but on a particular machine flickering started with 4.1. As a workaround I'm attaching a patch which disables DRRS by default and adds module parameter "enable_drrs" to activate it. It's made for kernel 5.12 and should work for older versions as well (tested with 5.11). Until this issue is resolved, please consider adding parameter to disable DRRS. Windows has such option on Intel® Graphics Command Center. ** Affects: linux Importance: Unknown Status: Unknown ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 1040 flickering folio g1 hp i915 ** Patch added: "Patch to disable DRRS by default with parameter to enable it" https://bugs.launchpad.net/bugs/1928138/+attachment/5496449/+files/disable_drrs_by_default_5-12.patch ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #3441 https://gitlab.freedesktop.org/drm/intel/-/issues/3441 ** Also affects: linux via https://gitlab.freedesktop.org/drm/intel/-/issues/3441 Importance: Unknown Status: Unknown ** Description changed: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) has a pretty issue with flickering Symptoms: 1) If I leave mouse cursor for a few seconds, then start moving it, there's slight flicker (like display brightness changes a bit) 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M + dmesg shows constant refresh rate changes (even if it's set to 40HZ) [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz nomodeset boot option eliminates flickering Turns out Display Refresh Rate Switching (DRRS) feature doesn't work correctly here. It was implemented on kernels 4.0...4.1 but on a particular machine flickering started with 4.1. As a workaround I'm attaching a patch which disables DRRS by default and adds module parameter "enable_drrs" to activate it. It's made for kernel 5.12 and should work for older versions as well (tested with 5.11). Until this issue is resolved, please consider adding parameter to disable DRRS. Windows has such option on Intel® Graphics Command Center. -- 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/1928138 Title: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bissected and workaround attached] Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) has a pretty issue with flickering Symptoms: 1) If I leave mouse cursor for a few seconds, then start moving it, there's slight flicker (like display brightness changes a bit) 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M dmesg shows constant refresh rate changes (even if it's set to 40HZ) [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60H
[Kernel-packages] [Bug 1909814] Re: Keyboard not working
Okay people, thank you for your reportings, I'm with openSUSE, but have the same problem. MEDION 15651 / M15T with TigerLake chipset and 11th Gen Intel Core i5-1135G7. I've now posted a BUG report @bugzilla.kernel.org: https://bugzilla.kernel.org/show_bug.cgi?id=213031 Please help with information I might have missed to mention. Best regards, Manuel ** Bug watch added: Linux Kernel Bug Tracker #213031 https://bugzilla.kernel.org/show_bug.cgi?id=213031 -- 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: Confirmed 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 1925008] Re: no memory hot-plugging in cloud-images
This bug was fixed in the package linux-kvm - 5.11.0-1007.7 --- linux-kvm (5.11.0-1007.7) hirsute; urgency=medium * no memory hot-plugging in cloud-images (LP: #1925008) - [Config] kvm: CONFIG_ACPI_HOTPLUG_MEMORY=y [ Ubuntu: 5.11.0-17.18 ] * Race between isotp_bind and isotp_setsockopt (LP: #1927409) - SAUCE: Revert "can: isotp: add SF_BROADCAST support for functional addressing" * CVE-2021-3491 - io_uring: fix overflows checks in provide buffers - SAUCE: proc: Avoid mixing integer types in mem_rw() - SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide buffers * CVE-2021-3490 - SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops * CVE-2021-3489 - SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf - SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages -- Stefan Bader Thu, 06 May 2021 21:28:51 +0200 ** Changed in: linux-kvm (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Status in linux-kvm source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux-kvm source package in Hirsute: Fix Released Bug description: SRU Justification [Impact] Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU [Test Plan] Boot a kernel with CONFIG_ACPI_HOTPLUG_MEMORY enabled. Check that requested memory has been added. [Where problems could occur] Adding memory could fail, or cause other configurations issues. Regressions seem unlikely since this config option is enabled in all cloud kernels except linux-azure. To manage notifications about this bug go to: https://b
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
Nice work and very timely, @tuxinvader. Perhaps leave an answer on askubuntu for future reference. -- 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 1925407] Re: ubuntu_aufs_smoke_test failed on Hirsute RISCV (CONFIG_AUFS_FS is not set)
This is resolved in autotest-client-tests 5b2d46bf401e50a13be5c0641e0157d58c2a7669 ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux-riscv (Ubuntu) Status: New => Won't Fix ** Changed in: linux-riscv (Ubuntu Hirsute) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1925407 Title: ubuntu_aufs_smoke_test failed on Hirsute RISCV (CONFIG_AUFS_FS is not set) Status in ubuntu-kernel-tests: Fix Released Status in linux-riscv package in Ubuntu: Won't Fix Status in linux-riscv source package in Hirsute: Won't Fix Bug description: Issue found on 5.11.0-1005.5 RISCV kernel Test failed with: Running '/home/ubuntu/autotest/client/tests/ubuntu_aufs_smoke_test/ubuntu_aufs_smoke_test.sh' mount: /tmp/aufs/aufs-root: unknown filesystem type 'aufs'. aufs: mount: FAILED: ret=32 It looks like this is simply because the kernel configs were not enabled: ubuntu@riscv64-hirsute:~$ grep AUFS /boot/config-5.11.0-1005-generic # CONFIG_AUFS_FS is not set I think it's more like a decision making here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1925407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921104 Title: net/mlx5e: Add missing capability check for uplink follow Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification: == [Impact] * Since older firmware may not support the uplink state setting, this can lead to problems. * Now expose firmware indication that it supports setting eswitch uplink state to follow the physical link. * If a kernel without the backport is used on an adapter which does not have the latest adapter firmware, the adapter silently drops outgoing traffic. * This is a regression which was introduced with kernel 5.4.0-48. [Fix] * upstream fix (as in 5.11): 9c9be85f6b59d80efe4705109c0396df18d4e11d 9c9be85f6b59 "net/mlx5e: Add missing capability check for uplink follow" * backport for focal: https://launchpadlibrarian.net/529543695/0001 -Backport-net-mlx5e-Add-missing-capability-check-for-.patch * backport for groovy: https://launchpadlibrarian.net/529775887/0001 -Backport-groovy-net-mlx5e-Add-missing-capability-che.patch [Test Case] * Two IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04 or 20.10 on LPAR, are needed. * Each with RoCE Express 2.x adapters (Mellanox ConnectX4/5) attached and firmware 16.29.1006 or earlier. * Assign an IP address to the adapters on both systems and try to ping one node from the other. * The ping will just fail with the stock Ubuntu kernels (not having the patch), but will succeed with kernels that incl. the patches (like the test builds from the PPA mentioned below). * Due to the lack of hardware this needs to be verified by IBM. [Regression Potential] * Undesired / erroneous behavior in case the modified if condition is assembled in a wrong way. * Again wrong behavior in case the modification of the capability bits in mlx5_ifc_cmd_hca_cap_bits are wrong. * All modification are limited to the mlx5 driver only. * The changes are relatively limited with effectively two lines removed and 4 added (three of them adjustments of the capability bits only). * The modifications were done and tested by IBM and reviewed by Mellanox (see LP comments), based on a PPA test build. [Other] * The above patch/commit was upstream accepted with kernel 5.11. * Hence the patch is not needed for hirsute, just needs to be SRUed for groovy and focal. * The commit couldn't be cleanly cherry-picked, mainly due to changed context, hence the backport(s). __ Expose firmware indication that it supports setting eswitch uplink state to follow (follow the physical link). Condition setting the eswitch uplink admin-state with this capability bit. Older FW may not support the uplink state setting. Available fix with kernel 5.11. https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d Now required for Ubuntu 20.04 via backport patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921498] Re: [Ubuntu 21.04] s390/vtime: fix increased steal time accounting
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1921498
Title:
[Ubuntu 21.04] s390/vtime: fix increased steal time accounting
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* The reported steal time on s390x is erroneously increasing and
therefore broken.
* This problem got introduced with commit 152e9b8676c6e
("s390/vtime: steal time exponential moving average") - upstream with v5.1
[Fix]
* d54cb7d54877d529bc1e0e1f47a3dd082f73add3 d54cb7d54877 "s390/vtime:
fix increased steal time accounting"
[Test Case]
* An IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04,
20.10 and 21.04 on LPAR, are needed.
* The system needs to be configured as KVM host with one or more KVM
guests.
* Now put significant workload on the guest(s), so that the hypervisor starts
to 'steal time'.
This can be best forced by having only very limited CPU resources for the
hypervisor itself.
* Start monitoring the steal time, that is reported at /proc/stat,
but can be more easily verified with tools like vmstat or even top.
* If the steal time starts ever growing (exponentially), the situation
is broken.
* In case the steal time stays relatively constant,
or grows only very limited after a ramp up phase of some minutes,
or just oscillates around a certain value, a fixed/patched kernel is in use.
[Regression Potential]
* The patch only changes the single line that calculates:
account_steal_time
* In case the account_steal_time calculation is still broken after the
modification,
the steal time is just again not reported correctly on s390x,
but maybe in a different way (rather than exponentially growing).
* But it will not further harm virtualization on s390x systems.
* The modification is very limited with that one line change.
* The commit got upstream accepted with 5.12-rc4.
[Other]
* Since the patch is needed for kernel higher than 5.1 and got upstream
accepted with 5.12-rc4,
hirsute, groovy and focal are affected.
* The upstream commit can be cleanly cherry-picked from all three affected
Ubuntu releases.
__
Description: s390/vtime: fix increased steal time accounting
Symptom: Increased steal time values.
Problem: Commit 152e9b8676c6e ("s390/vtime: steal time exponential
moving average") inadvertently changed the input value for
account_steal_time() from "cputime_to_nsecs(steal)" to just
"steal", resulting in broken increased steal time accounting.
Solution: Fix this by changing it back to "cputime_to_nsecs(steal)".
Reproduction: -
Upstream-ID: d54cb7d54877d529bc1e0e1f47a3dd082f73add3
Stable tagged : kernel 5.1.
Therefore only to be applyable for focal, groovy, hirsuite.
Due to stable tag integration , only for integration checking..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921498/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908264] Re: Disable Atari partition support for cloud kernels
This bug was fixed in the package linux-gcp - 5.8.0-1031.32 --- linux-gcp (5.8.0-1031.32) groovy; urgency=medium [ Ubuntu: 5.8.0-53.60 ] * CVE-2021-3491 - io_uring: fix provide_buffers sign extension - io_uring: fix overflows checks in provide buffers - SAUCE: proc: Avoid mixing integer types in mem_rw() - SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide buffers * CVE-2021-3490 - bpf: Fix a verifier failure with xor - SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops * CVE-2021-3489 - SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf - SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages -- Stefan Bader Thu, 06 May 2021 10:32:39 +0200 ** Changed in: linux-gcp (Ubuntu Groovy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491 ** Changed in: linux-oracle (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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1908264 Title: Disable Atari partition support for cloud kernels Status in linux-aws package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-aws source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-aws source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Fix Committed Status in linux-oracle source package in Bionic: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-gcp source package in Focal: Fix Released Status in linux-gke source package in Focal: Fix Released Status in linux-gkeop source package in Focal: Fix Released Status in linux-oracle source package in Focal: Fix Released Status in linux-aws source package in Groovy: Fix Committed Status in linux-azure source package in Groovy: Fix Released Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux-gcp source package in Groovy: Fix Released Status in linux-oracle source package in Groovy: Fix Released Status in linux-aws source package in Hirsute: In Progress Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-4.15 source package in Hirsute: Invalid Status in linux-gcp source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Atari partition tables have very broad specifications, and can spontaneously show up on uncleared disks with "garbage" data. There have been reports of misinterpreted AHDI partition tables before (see [0] and [1]), usually as an unintended side-effect of using non-zeroed disks. Users of this specific partition scheme are unlikely to be on AWS instances, so we should disable them. [0] https://lore.kernel.org/linux-block/1467736712-11825-1-git-send-email-kris...@linux.vnet.ibm.com/ [1] https://mail-index.netbsd.org/port-atari/1995/11/19/0001.html [Test Case] Ensure that CONFIG_ATARI_PARTITION is not set in /boot/config-$(uname -r) [Fix] Unset CONFIG_ATARI_PARTITION in debian.aws/config/config.common.ubuntu [Regression Potential] There could be unexpected dependencies on Atari partitions that are impacted by this change. Considering Atari hardware hasn't been produced in a long time, and is unlikely to be used in AWS instances, the regression potential should be very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908264] Re: Disable Atari partition support for cloud kernels
This bug was fixed in the package linux-oracle - 5.8.0-1029.30 --- linux-oracle (5.8.0-1029.30) groovy; urgency=medium [ Ubuntu: 5.8.0-53.60 ] * CVE-2021-3491 - io_uring: fix provide_buffers sign extension - io_uring: fix overflows checks in provide buffers - SAUCE: proc: Avoid mixing integer types in mem_rw() - SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide buffers * CVE-2021-3490 - bpf: Fix a verifier failure with xor - SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops * CVE-2021-3489 - SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf - SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages -- Stefan Bader Thu, 06 May 2021 11:26:55 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1908264 Title: Disable Atari partition support for cloud kernels Status in linux-aws package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-aws source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-aws source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Fix Committed Status in linux-oracle source package in Bionic: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-gcp source package in Focal: Fix Released Status in linux-gke source package in Focal: Fix Released Status in linux-gkeop source package in Focal: Fix Released Status in linux-oracle source package in Focal: Fix Released Status in linux-aws source package in Groovy: Fix Committed Status in linux-azure source package in Groovy: Fix Released Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux-gcp source package in Groovy: Fix Released Status in linux-oracle source package in Groovy: Fix Released Status in linux-aws source package in Hirsute: In Progress Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-4.15 source package in Hirsute: Invalid Status in linux-gcp source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Atari partition tables have very broad specifications, and can spontaneously show up on uncleared disks with "garbage" data. There have been reports of misinterpreted AHDI partition tables before (see [0] and [1]), usually as an unintended side-effect of using non-zeroed disks. Users of this specific partition scheme are unlikely to be on AWS instances, so we should disable them. [0] https://lore.kernel.org/linux-block/1467736712-11825-1-git-send-email-kris...@linux.vnet.ibm.com/ [1] https://mail-index.netbsd.org/port-atari/1995/11/19/0001.html [Test Case] Ensure that CONFIG_ATARI_PARTITION is not set in /boot/config-$(uname -r) [Fix] Unset CONFIG_ATARI_PARTITION in debian.aws/config/config.common.ubuntu [Regression Potential] There could be unexpected dependencies on Atari partitions that are impacted by this change. Considering Atari hardware hasn't been produced in a long time, and is unlikely to be used in AWS instances, the regression potential should be very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921960] Re: Groovy update: upstream stable patchset 2021-03-30
This bug was fixed in the package linux-gcp - 5.8.0-1031.32 --- linux-gcp (5.8.0-1031.32) groovy; urgency=medium [ Ubuntu: 5.8.0-53.60 ] * CVE-2021-3491 - io_uring: fix provide_buffers sign extension - io_uring: fix overflows checks in provide buffers - SAUCE: proc: Avoid mixing integer types in mem_rw() - SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide buffers * CVE-2021-3490 - bpf: Fix a verifier failure with xor - SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops * CVE-2021-3489 - SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf - SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages -- Stefan Bader Thu, 06 May 2021 10:32:39 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1921960 Title: Groovy update: upstream stable patchset 2021-03-30 Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux source package in Groovy: Fix Released Status in linux-gcp source package in Groovy: Fix Released 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-03-30 Ported from the following upstream stable releases: v5.4.102, v5.10.20 from git://git.kernel.org/ vmlinux.lds.h: add DWARF v5 sections debugfs: be more robust at handling improper input in debugfs_lookup() debugfs: do not attempt to create a new file before the filesystem is initalized scsi: libsas: docs: Remove notify_ha_event() scsi: qla2xxx: Fix mailbox Ch erroneous error kdb: Make memory allocations more robust PCI: qcom: Use PHY_REFCLK_USE_PAD only for ipq8064 PCI: Decline to resize resources if boot config must be preserved virt: vbox: Do not use wait_event_interruptible when called from kernel context bfq: Avoid false bfq queue merging ALSA: usb-audio: Fix PCM buffer allocation in non-vmalloc mode MIPS: vmlinux.lds.S: add missing PAGE_ALIGNED_DATA() section random: fix the RNDRESEEDCRNG ioctl ALSA: pcm: Call sync_stop at disconnection ALSA: pcm: Assure sync with the pending stop operation at suspend ALSA: pcm: Don't call sync_stop if it hasn't been stopped drm/i915/gt: One more flush for Baytrail clear residuals ath10k: Fix error handling in case of CE pipe init failure Bluetooth: btqcomsmd: Fix a resource leak in error handling paths in the probe function Bluetooth: hci_uart: Fix a race for write_work scheduling Bluetooth: Fix initializing response id after clearing struct ARM: dts: exynos: correct PMIC interrupt trigger level on Artik 5 ARM: dts: exynos: correct PMIC interrupt trigger level on Monk ARM: dts: exynos: correct PMIC interrupt trigger level on Rinato ARM: dts: exynos: correct PMIC interrupt trigger level on Spring ARM: dts: exynos: correct PMIC interrupt trigger level on Arndale Octa ARM: dts: exynos: correct PMIC interrupt trigger level on Odroid XU3 family arm64: dts: exynos: correct PMIC interrupt trigger level on TM2 arm64: dts: exynos: correct PMIC interrupt trigger level on Espresso memory: mtk-smi: Fix PM usage counter unbalance in mtk_smi ops Bluetooth: hci_qca: Fix memleak in qca_controller_memdump arm64: dts: qcom: msm8916-samsung-a5u: Fix iris compatible net: stmmac: dwmac-meson8b: fix enabling the timing-adjustment clock bpf: Add bpf_patch_call_args prototype to include/linux/bpf.h bpf: Avoid warning when re-casting __bpf_call_base into __bpf_call_base_args arm64: dts: allwinner: A64: properly connect USB PHY to port 0 arm64: dts: allwinner: H6: properly connect USB PHY to port 0 arm64: dts: allwinner: Drop non-removable from SoPine/LTS SD card arm64: dts: allwinner: H6: Allow up to 150 MHz MMC bus frequency arm64: dts: allwinner: A64: Limit MMC2 bus frequency to 150 MHz cpufreq: brcmstb-avs-cpufreq: Free resources in error path cpufreq: brcmstb-avs-cpufreq: Fix resource leaks in ->remove() arm64: dts: rockchip: rk3328: Add clock_in_out property to gmac2phy node ACPICA: Fix exception code class checks usb: gadget: u_audio: Free requests only after callback arm64: dts: qcom: sdm845-db845c: Fix reset-pin of ov8856 node soc: ti: pm33xx: Fix some resource leak in the error handling paths of the probe function staging: media: atomisp: Fix size_t format specifier in hmm_alloc() debug statemenet Bluetooth: drop HCI d
[Kernel-packages] [Bug 1921960] Re: Groovy update: upstream stable patchset 2021-03-30
This bug was fixed in the package linux - 5.8.0-53.60 --- linux (5.8.0-53.60) groovy; urgency=medium * CVE-2021-3491 - io_uring: fix provide_buffers sign extension - io_uring: fix overflows checks in provide buffers - SAUCE: proc: Avoid mixing integer types in mem_rw() - SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide buffers * CVE-2021-3490 - bpf: Fix a verifier failure with xor - SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops * CVE-2021-3489 - SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf - SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages -- Stefan Bader Thu, 06 May 2021 07:43:20 +0200 ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491 ** Changed in: linux-gcp (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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1921960 Title: Groovy update: upstream stable patchset 2021-03-30 Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux source package in Groovy: Fix Released Status in linux-gcp source package in Groovy: Fix Released 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-03-30 Ported from the following upstream stable releases: v5.4.102, v5.10.20 from git://git.kernel.org/ vmlinux.lds.h: add DWARF v5 sections debugfs: be more robust at handling improper input in debugfs_lookup() debugfs: do not attempt to create a new file before the filesystem is initalized scsi: libsas: docs: Remove notify_ha_event() scsi: qla2xxx: Fix mailbox Ch erroneous error kdb: Make memory allocations more robust PCI: qcom: Use PHY_REFCLK_USE_PAD only for ipq8064 PCI: Decline to resize resources if boot config must be preserved virt: vbox: Do not use wait_event_interruptible when called from kernel context bfq: Avoid false bfq queue merging ALSA: usb-audio: Fix PCM buffer allocation in non-vmalloc mode MIPS: vmlinux.lds.S: add missing PAGE_ALIGNED_DATA() section random: fix the RNDRESEEDCRNG ioctl ALSA: pcm: Call sync_stop at disconnection ALSA: pcm: Assure sync with the pending stop operation at suspend ALSA: pcm: Don't call sync_stop if it hasn't been stopped drm/i915/gt: One more flush for Baytrail clear residuals ath10k: Fix error handling in case of CE pipe init failure Bluetooth: btqcomsmd: Fix a resource leak in error handling paths in the probe function Bluetooth: hci_uart: Fix a race for write_work scheduling Bluetooth: Fix initializing response id after clearing struct ARM: dts: exynos: correct PMIC interrupt trigger level on Artik 5 ARM: dts: exynos: correct PMIC interrupt trigger level on Monk ARM: dts: exynos: correct PMIC interrupt trigger level on Rinato ARM: dts: exynos: correct PMIC interrupt trigger level on Spring ARM: dts: exynos: correct PMIC interrupt trigger level on Arndale Octa ARM: dts: exynos: correct PMIC interrupt trigger level on Odroid XU3 family arm64: dts: exynos: correct PMIC interrupt trigger level on TM2 arm64: dts: exynos: correct PMIC interrupt trigger level on Espresso memory: mtk-smi: Fix PM usage counter unbalance in mtk_smi ops Bluetooth: hci_qca: Fix memleak in qca_controller_memdump arm64: dts: qcom: msm8916-samsung-a5u: Fix iris compatible net: stmmac: dwmac-meson8b: fix enabling the timing-adjustment clock bpf: Add bpf_patch_call_args prototype to include/linux/bpf.h bpf: Avoid warning when re-casting __bpf_call_base into __bpf_call_base_args arm64: dts: allwinner: A64: properly connect USB PHY to port 0 arm64: dts: allwinner: H6: properly connect USB PHY to port 0 arm64: dts: allwinner: Drop non-removable from SoPine/LTS SD card arm64: dts: allwinner: H6: Allow up to 150 MHz MMC bus frequency arm64: dts: allwinner: A64: Limit MMC2 bus frequency to 150 MHz cpufreq: brcmstb-avs-cpufreq: Free resources in error path cpufreq: brcmstb-avs-cpufreq: Fix resource leaks in ->remove() arm64: dts: rockchip: rk3328: Add clock_in_out property to gmac2phy node ACPICA: Fix excep
[Kernel-packages] [Bug 1925241] Re: Disable CONFIG_DELL_SMBIOS_SMM, CONFIG_DELL_UART_BACKLIGHT, CONFIG_I2C_AMD_MP2
This bug was fixed in the package linux-gcp - 5.8.0-1031.32 --- linux-gcp (5.8.0-1031.32) groovy; urgency=medium [ Ubuntu: 5.8.0-53.60 ] * CVE-2021-3491 - io_uring: fix provide_buffers sign extension - io_uring: fix overflows checks in provide buffers - SAUCE: proc: Avoid mixing integer types in mem_rw() - SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide buffers * CVE-2021-3490 - bpf: Fix a verifier failure with xor - SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops * CVE-2021-3489 - SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf - SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages -- Stefan Bader Thu, 06 May 2021 10:32:39 +0200 ** Changed in: linux-gcp (Ubuntu Groovy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1925241 Title: Disable CONFIG_DELL_SMBIOS_SMM, CONFIG_DELL_UART_BACKLIGHT, CONFIG_I2C_AMD_MP2 Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp-5.8 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-gcp source package in Focal: Invalid Status in linux-gcp-5.8 source package in Focal: In Progress Status in linux source package in Groovy: Invalid Status in linux-gcp source package in Groovy: Fix Released Status in linux-gcp-5.8 source package in Groovy: Invalid Status in linux source package in Hirsute: Invalid Status in linux-gcp source package in Hirsute: In Progress Status in linux-gcp-5.8 source package in Hirsute: Invalid Bug description: SRU Justification: Enforcement annotations indicate that these config options should never have been set. [Impact] Disable these options for hardware that does not exist in the Google cloud fabric. There should be no impact to existing users. [Fix] CONFIG_DELL_SMBIOS_SMM=n CONFIG_DELL_UART_BACKLIGHT=n CONFIG_I2C_AMD_MP2=n [Test Plan] Boot a GCP instance and ensure there are no new kernel log errors. [Where problems could occur] Regression potential should be low since this HW does not exists in a GCP guest instance. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927874] Re: package bcmwl-kernel-source (not installed) failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit
The installation of bcmwl-kernel-source package failed during the upgrade from 19.10 to 20.04, but it was successful after installing gcc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1927874 Title: package bcmwl-kernel-source (not installed) failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: New Bug description: ~$ uname -r 5.4.0-72-generic ~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal *-network UNCLAIMED description: Network controller product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:03:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: latency=0 resources: memory:c050-c0503fff ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source (not installed) ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 AptOrdering: bcmwl-kernel-source:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 9 22:24:40 2021 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-08-11 (637 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: bcmwl Title: package bcmwl-kernel-source (not installed) failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to focal on 2021-05-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1927874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900438] Re: Bcache bypasse writeback on caching device with fragmentation
This bug was fixed in the package linux - 5.8.0-53.60
---
linux (5.8.0-53.60) groovy; urgency=medium
* CVE-2021-3491
- io_uring: fix provide_buffers sign extension
- io_uring: fix overflows checks in provide buffers
- SAUCE: proc: Avoid mixing integer types in mem_rw()
- SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide
buffers
* CVE-2021-3490
- bpf: Fix a verifier failure with xor
- SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops
* CVE-2021-3489
- SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf
- SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages
-- Stefan Bader Thu, 06 May 2021 07:43:20
+0200
** Changed in: linux (Ubuntu Groovy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491
--
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/1900438
Title:
Bcache bypasse writeback on caching device with fragmentation
Status in linux package in Ubuntu:
Fix Released
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
Status in linux source package in Hirsute:
Fix Released
Bug description:
SRU Justification:
[Impact]
This bug in bcache affects I/O performance on all versions of the kernel
[correct versions affected]. It is particularly negative on ceph if used with
bcache.
Write I/O latency would suddenly go to around 1 second from around 10
ms when hitting this issue and would easily be stuck there for hours
or even days, especially bad for ceph on bcache architecture. This
would make ceph extremely slow and make the entire cloud almost
unusable.
The root cause is that the dirty bucket had reached the 70 percent
threshold, thus causing all writes to go direct to the backing HDD
device. It might be fine if it actually had a lot of dirty data, but
this happens when dirty data has not even reached over 10 percent, due
to having high memory fragmentation. What makes it worse is that the
writeback rate might be still at minimum value (8) due to the
writeback percent not reached, so it takes ages for bcache to really
reclaim enough dirty buckets to get itself out of this situation.
[Fix]
* 71dda2a5625f31bc3410cb69c3d31376a2b66f28 “bcache: consider the
fragmentation when update the writeback rate”
The current way to calculate the writeback rate only considered the dirty
sectors.
This usually works fine when memory fragmentation is not high, but it will
give us an unreasonably low writeback rate when we are in the situation that a
few dirty sectors have consumed a lot of dirty buckets. In some cases, the
dirty buckets reached CUTOFF_WRITEBACK_SYNC (i.e., stopped writeback) while
the dirty data (sectors) had not even reached the writeback_percent threshold
(i.e., started writeback). In that situation, the writeback rate will still be
the minimum value (8*512 = 4KB/s), thus it will cause all the writes to bestuck
in a non-writeback mode because of the slow writeback.
We accelerate the rate in 3 stages with different aggressiveness:
the first stage starts when dirty buckets percent reach above
BCH_WRITEBACK_FRAGMENT_THRESHOLD_LOW (50),
the second is BCH_WRITEBACK_FRAGMENT_THRESHOLD_MID (57),
the third is BCH_WRITEBACK_FRAGMENT_THRESHOLD_HIGH (64).
By default the first stage tries to writeback the amount of dirty data
in one bucket (on average) in (1 / (dirty_buckets_percent - 50)) seconds,
the second stage tries to writeback the amount of dirty data in one bucket
in (1 / (dirty_buckets_percent - 57)) * 100 milliseconds, the third
stage tries to writeback the amount of dirty data in one bucket in
(1 / (dirty_buckets_percent - 64)) milliseconds.
The initial rate at each stage can be controlled by 3 configurable
parameters:
writeback_rate_fp_term_{low|mid|high}
They are by default 1, 10, 1000, chosen based on testing and
production data, detailed below.
A. When it comes to the low stage, it is still far from the 70%
threshold, so we only want to give it a little bit push by setting the
term to 1, it means the initial rate will be 170 if the fragment is 6,
it is calculated by bucket_size/fragment, this rate is very small,
but still much more reasonable than the minimum 8.
For a production bcache with non-heavy workload, if the cache device
is bigger than 1 TB, it may take hours to consume 1% buckets,
so it is very possible to reclaim enough dirty buckets in this stage,
thus to avoid entering the next stage.
B. If the dirty
[Kernel-packages] [Bug 1918134] Re: LRMv4: switch to signing nvidia modules via the Ubuntu Modules signing key
This bug was fixed in the package linux - 5.8.0-53.60 --- linux (5.8.0-53.60) groovy; urgency=medium * CVE-2021-3491 - io_uring: fix provide_buffers sign extension - io_uring: fix overflows checks in provide buffers - SAUCE: proc: Avoid mixing integer types in mem_rw() - SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide buffers * CVE-2021-3490 - bpf: Fix a verifier failure with xor - SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops * CVE-2021-3489 - SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf - SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages -- Stefan Bader Thu, 06 May 2021 07:43:20 +0200 ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1918134 Title: LRMv4: switch to signing nvidia modules via the Ubuntu Modules signing key Status in linux package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-restricted-modules source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-restricted-modules source package in Hirsute: Fix Released Bug description: To allow decoupling of nvidia-graphics-drivers- streams and versions from the underlying kernel versions we wish to be able to sign new kernel modules into an existing kernel after the fact. Under bug #1898716 we added support for an Ubuntu Modules signing key certificate. Rebuild the LRM package to make use of this new signature. This involves splitting the LRM package into three. linux-restricted- modules first builds the nvidia-graphics-drivers-* we require signed. linux-restricted-generate then consumes the .o's produced in that build and forms a signing custom binary upload for this. linux- restricted-signatures then consumes the signing result from the LRG upload and expresses clean redistributible signatures which are consumed by LRM at installation time. LRG must be embargoed as it (necessarily) generates fully formed .ko files for signing. Additional process is added to the kernel build life-cycle to handle the privacy requirements of the LRG/LRS interaction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918987] Re: Groovy update: upstream stable patchset 2021-03-12
This bug was fixed in the package linux - 5.8.0-53.60
---
linux (5.8.0-53.60) groovy; urgency=medium
* CVE-2021-3491
- io_uring: fix provide_buffers sign extension
- io_uring: fix overflows checks in provide buffers
- SAUCE: proc: Avoid mixing integer types in mem_rw()
- SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide
buffers
* CVE-2021-3490
- bpf: Fix a verifier failure with xor
- SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops
* CVE-2021-3489
- SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf
- SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages
-- Stefan Bader Thu, 06 May 2021 07:43:20
+0200
** Changed in: linux (Ubuntu Groovy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491
--
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/1918987
Title:
Groovy update: upstream stable patchset 2021-03-12
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Groovy:
Fix Released
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-03-12
Ported from the following upstream stable releases:
v5.4.96, v5.10.14,
v5.4.97, v5.10.15
from git://git.kernel.org/
net: fec: put child node on error path
net: octeontx2: Make sure the buffer is 128 byte aligned
stmmac: intel: Configure EHL PSE0 GbE and PSE1 GbE to 32 bits DMA addressing
net: dsa: bcm_sf2: put device node before return
net: switchdev: don't set port_obj_info->handled true when -EOPNOTSUPP
ibmvnic: Ensure that CRQ entry read are correctly ordered
iommu/io-pgtable-arm: Support coherency for Mali LPAE
drm/panfrost: Support cache-coherent integrations
arm64: dts: meson: Describe G12b GPU as coherent
arm64: Fix kernel address detection of __is_lm_address()
arm64: Do not pass tagged addresses to __is_lm_address()
ARM: 9025/1: Kconfig: CPU_BIG_ENDIAN depends on !LD_IS_LLD
iommu/vt-d: Do not use flush-queue when caching-mode is on
phy: cpcap-usb: Fix warning for missing regulator_disable
tools/power/x86/intel-speed-select: Set scaling_max_freq to base_frequency
tools/power/x86/intel-speed-select: Set higher of cpuinfo_max_freq or
base_frequency
platform/x86: touchscreen_dmi: Add swap-x-y quirk for Goodix touchscreen on
Estar Beauty HD tablet
platform/x86: intel-vbtn: Support for tablet mode on Dell Inspiron 7352
locking/lockdep: Avoid noinstr warning for DEBUG_LOCKDEP
x86: __always_inline __{rd,wr}msr()
scsi: scsi_transport_srp: Don't block target in failfast state
scsi: libfc: Avoid invoking response handler twice if ep is already completed
scsi: fnic: Fix memleak in vnic_dev_init_devcmd2
ALSA: hda - add Intel DG1 PCI and HDMI ids
ALSA: hda: Add Alderlake-S PCI ID and HDMI codec vid
ALSA: hda: Add AlderLake-P PCI ID and HDMI codec vid
objtool: Don't add empty symbols to the rbtree
mac80211: fix incorrect strlen of .write in debugfs
mac80211: fix fast-rx encryption check
scsi: ibmvfc: Set default timeout to avoid crash during migration
i2c: tegra: Create i2c_writesl_vi() to use with VI I2C for filling TX FIFO
udf: fix the problem that the disc content is not displayed
nvme: check the PRINFO bit before deciding the host buffer length
nvme-rdma: avoid request double completion for concurrent nvme_rdma_timeout
nvme-tcp: avoid request double completion for concurrent nvme_tcp_timeout
nvme-pci: allow use of cmb on v1.4 controllers
nvmet: set right status on error in id-ns handler
platform/x86: thinkpad_acpi: Add P53/73 firmware to fan_quirk_table for dual
fan control
selftests/powerpc: Only test lwm/stmw on big endian
drm/amd/display: Update dram_clock_change_latency for DCN2.1
drm/amd/display: Change function decide_dp_link_settings to avoid infinite
looping
drm/amd/display: Use hardware sequencer functions for PG control
objtool: Don't fail the kernel build on fatal errors
x86/cpu: Add Lakefield, Alder Lake and Rocket Lake models to the to Intel CPU
family
x86/cpu: Add another Alder Lake CPU to the Intel family
kthread: Extract KTHREAD_IS_PER_CPU
workqueue: Restrict
[Kernel-packages] [Bug 1909428] Re: eeh-basic.sh from powerpc in ubuntu_kernel_selftests failed with unexpected operator on F-5.8
This bug was fixed in the package linux - 5.8.0-53.60
---
linux (5.8.0-53.60) groovy; urgency=medium
* CVE-2021-3491
- io_uring: fix provide_buffers sign extension
- io_uring: fix overflows checks in provide buffers
- SAUCE: proc: Avoid mixing integer types in mem_rw()
- SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide
buffers
* CVE-2021-3490
- bpf: Fix a verifier failure with xor
- SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops
* CVE-2021-3489
- SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf
- SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages
-- Stefan Bader Thu, 06 May 2021 07:43:20
+0200
** Changed in: linux (Ubuntu Groovy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491
--
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/1909428
Title:
eeh-basic.sh from powerpc in ubuntu_kernel_selftests failed with
unexpected operator on F-5.8
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Committed
Bug description:
[Impact]
The fail check in the end of powerpc/eeh/eeh-basic.sh script will complain
about "unexpected operator"
This is caused by the following line in the script:
$ test "$failed" == 0
/bin/sh: 4: test: 0: unexpected operator
[Fix]
* 3db380570af705 ("selftests/powerpc: Make the test check in eeh-basic.sh
posix compliant")
This is affecting F/G/H and can be cherry-picked for all of them.
[Test case]
Run the eeh-basic.sh script in tools/testing/selftests/powerpc/eeh/
This error message should be gone.
[Where problems could occur]
This fix is limited to PowerPC testing tool, it's unlike to cause any issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1909428/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920571] Re: Groovy update: upstream stable patchset 2021-03-19
This bug was fixed in the package linux - 5.8.0-53.60 --- linux (5.8.0-53.60) groovy; urgency=medium * CVE-2021-3491 - io_uring: fix provide_buffers sign extension - io_uring: fix overflows checks in provide buffers - SAUCE: proc: Avoid mixing integer types in mem_rw() - SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide buffers * CVE-2021-3490 - bpf: Fix a verifier failure with xor - SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops * CVE-2021-3489 - SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf - SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages -- Stefan Bader Thu, 06 May 2021 07:43:20 +0200 ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491 -- 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/1920571 Title: Groovy update: upstream stable patchset 2021-03-19 Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: Fix Released 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-03-19 Ported from the following upstream stable releases: v5.4.98, v5.10.16, v5.4.99, v5.10.17, v5.4.100, v5.10.18, v5.4.101, v5.10.19 from git://git.kernel.org/ af_key: relax availability checks for skb size calculation regulator: core: avoid regulator_resolve_supply() race condition ASoC: wm_adsp: Fix control name parsing for multi-fw mac80211: 160MHz with extended NSS BW in CSA ASoC: Intel: Skylake: Zero snd_ctl_elem_value chtls: Fix potential resource leak pNFS/NFSv4: Try to return invalid layout in pnfs_layout_process() pNFS/NFSv4: Improve rejection of out-of-order layouts ALSA: hda: intel-dsp-config: add PCI id for TGL-H ASoC: ak4458: correct reset polarity ASoC: Intel: sof_sdw: set proper flags for Dell TGL-H SKU 0A5E iwlwifi: mvm: skip power command when unbinding vif during CSA iwlwifi: mvm: take mutex for calling iwl_mvm_get_sync_time() iwlwifi: pcie: add a NULL check in iwl_pcie_txq_unmap iwlwifi: pcie: fix context info memory leak iwlwifi: mvm: invalidate IDs of internal stations at mvm start iwlwifi: pcie: add rules to match Qu with Hr2 iwlwifi: mvm: guard against device removal in reprobe SUNRPC: Move simple_get_bytes and simple_get_netobj into private header SUNRPC: Handle 0 length opaque XDR object data properly i2c: mediatek: Move suspend and resume handling to NOIRQ phase blk-cgroup: Use cond_resched() when destroy blkgs regulator: Fix lockdep warning resolving supplies bpf: Fix verifier jmp32 pruning decision logic bpf: Fix 32 bit src register truncation on div/mod bpf: Fix verifier jsgt branch analysis on max bound drm/i915: Fix ICL MG PHY vswing handling drm/i915: Skip vswing programming for TBT nilfs2: make splice write available again squashfs: avoid out of bounds writes in decompressors squashfs: add more sanity checks in id lookup squashfs: add more sanity checks in inode lookup squashfs: add more sanity checks in xattr id lookup UBUNTU: upstream stable to v5.4.98, v5.10.16 gpio: mxs: GPIO_MXS should not default to y unconditionally gpio: ep93xx: fix BUG_ON port F usage gpio: ep93xx: Fix single irqchip with multi gpiochips tracing: Do not count ftrace events in top level enable output tracing: Check length before giving out the filter buffer drm/i915: Fix overlay frontbuffer tracking arm/xen: Don't probe xenbus as part of an early initcall cgroup: fix psi monitor for root cgroup drm/i915/tgl+: Make sure TypeC FIA is powered up when initializing it drm/dp_mst: Don't report ports connected if nothing is attached to them dmaengine: move channel device_node deletion to driver soc: ti: omap-prm: Fix boot time errors for rst_map_012 bits 0 and 1 arm64: dts: rockchip: Fix PCIe DT properties on rk3399 arm64: dts: qcom: sdm845: Reserve LPASS clocks in gcc ARM: OMAP2+: Fix suspcious RCU usage splats for omap_enter_idle_coupled arm64: dts: rockchip: remove interrupt-names property from rk3399 vdec node platfor
[Kernel-packages] [Bug 1910323] Re: Fix implicit declaration warnings for kselftests/memfd test on newer releases
This bug was fixed in the package linux - 5.8.0-53.60
---
linux (5.8.0-53.60) groovy; urgency=medium
* CVE-2021-3491
- io_uring: fix provide_buffers sign extension
- io_uring: fix overflows checks in provide buffers
- SAUCE: proc: Avoid mixing integer types in mem_rw()
- SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide
buffers
* CVE-2021-3490
- bpf: Fix a verifier failure with xor
- SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops
* CVE-2021-3489
- SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf
- SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages
-- Stefan Bader Thu, 06 May 2021 07:43:20
+0200
** Changed in: linux (Ubuntu Groovy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491
--
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/1910323
Title:
Fix implicit declaration warnings for kselftests/memfd test on newer
releases
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.6 package in Ubuntu:
New
Status in linux source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Bug description:
[Impact]
While debugging bug 1910277, I found that the test compilation will
print some warnings:
memfd_test.c:64:7: warning: implicit declaration of function ‘open’;
memfd_test.c:90:6: warning: implicit declaration of function ‘fcntl’
memfd_test.c:397:6: warning: implicit declaration of function ‘fallocate’;
fuse_test.c:67:6: warning: implicit declaration of function ‘fcntl’
fuse_test.c:261:7: warning: implicit declaration of function ‘open’;
It's harmless but fixing this we can make the test report easier to
read.
[Fix]
* 1c49e3783f8899 ("selftests/memfd: Fix implicit declaration warnings")
This fix can be cherry-picked into F/F-oem-5.6/G and compiled without
any problem. Older kernel does not have this issue since they're
missing some other commits.
[Test Case]
Build the memfd test in tools/testing/selftests/ with:
sudo make TARGETS=memfd
With this fix, these warnings will be gone.
[Where problems could occur]
This fix is just for fixing the test case compilation, so it's not
affecting real kernel functionality.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910323/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919930] Re: power off stress test will hang on the TGL machines
This bug was fixed in the package linux - 5.8.0-53.60 --- linux (5.8.0-53.60) groovy; urgency=medium * CVE-2021-3491 - io_uring: fix provide_buffers sign extension - io_uring: fix overflows checks in provide buffers - SAUCE: proc: Avoid mixing integer types in mem_rw() - SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide buffers * CVE-2021-3490 - bpf: Fix a verifier failure with xor - SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops * CVE-2021-3489 - SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf - SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages -- Stefan Bader Thu, 06 May 2021 07:43:20 +0200 ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491 -- 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/1919930 Title: power off stress test will hang on the TGL machines 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-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: Intel suggested that we do 2 actions to fix this problem, the 1st is merging 5 kernel patches, this only applies to H and OEM-5.10 since there is no tgl.c in the groovy kernel yet. the 2nd is change a kernel config, this change applies to H, G and OEM-5.10. https://github.com/thesofproject/linux/issues/2781 [Impact] When we run poweroff/on stress test on some lenovo TGL laptop, the system will randomly hang, and when this issue happens, the dmesg shows the sof audio driver fails. [Fix] Intel recommend that we backport 5 kernel patches and change a kernel config. [Test] After applying the changes, and test on TGL/cml/whl machines, the audio function works as good as before, and the poweroff stress test didn't hang anymore. [Where problems could occur] The kernel patches probably could introduce issues when system powre off or reboot on TGL machines, but this possibility is low since we have tested these patches on different TGL machines. the kernel option change could introduce power consumption regression, but it only affects power saving and package_cstate values when any capture stream is active, while no impact if all capture streams are inactive. that is to say, in theory it will not impact the power consumption in short idle or long idle. And I checked the system cound enter package_c10 after this change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1919930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920030] Re: Mute/Mic-mute LEDs are not work on HP 850/840/440 G8 Laptops
This bug was fixed in the package linux - 5.8.0-53.60 --- linux (5.8.0-53.60) groovy; urgency=medium * CVE-2021-3491 - io_uring: fix provide_buffers sign extension - io_uring: fix overflows checks in provide buffers - SAUCE: proc: Avoid mixing integer types in mem_rw() - SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide buffers * CVE-2021-3490 - bpf: Fix a verifier failure with xor - SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops * CVE-2021-3489 - SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf - SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages -- Stefan Bader Thu, 06 May 2021 07:43:20 +0200 ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491 -- 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/1920030 Title: Mute/Mic-mute LEDs are not work on HP 850/840/440 G8 Laptops Status in OEM Priority Project: Fix Released 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: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] The Mute/Mic-mute LEDs are not work when muting audio-output/microphone on HP 850/840/440 G8 laptops. [Fix] Add three realtek quirks for them. [Test] After applying the quirks, the LEDs are functioned on HP 850/840/440 G8 laptops. [Where problems could occur] If HP ships the different system boards design with the same subsystem IDs of audio codec which are using different GPIO pins (different layout), then the quirks will not work (LEDs will not function when muting audio-output or microphone. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow
This bug was fixed in the package linux - 5.8.0-53.60 --- linux (5.8.0-53.60) groovy; urgency=medium * CVE-2021-3491 - io_uring: fix provide_buffers sign extension - io_uring: fix overflows checks in provide buffers - SAUCE: proc: Avoid mixing integer types in mem_rw() - SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide buffers * CVE-2021-3490 - bpf: Fix a verifier failure with xor - SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops * CVE-2021-3489 - SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf - SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages -- Stefan Bader Thu, 06 May 2021 07:43:20 +0200 ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491 -- 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/1921104 Title: net/mlx5e: Add missing capability check for uplink follow Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification: == [Impact] * Since older firmware may not support the uplink state setting, this can lead to problems. * Now expose firmware indication that it supports setting eswitch uplink state to follow the physical link. * If a kernel without the backport is used on an adapter which does not have the latest adapter firmware, the adapter silently drops outgoing traffic. * This is a regression which was introduced with kernel 5.4.0-48. [Fix] * upstream fix (as in 5.11): 9c9be85f6b59d80efe4705109c0396df18d4e11d 9c9be85f6b59 "net/mlx5e: Add missing capability check for uplink follow" * backport for focal: https://launchpadlibrarian.net/529543695/0001 -Backport-net-mlx5e-Add-missing-capability-check-for-.patch * backport for groovy: https://launchpadlibrarian.net/529775887/0001 -Backport-groovy-net-mlx5e-Add-missing-capability-che.patch [Test Case] * Two IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04 or 20.10 on LPAR, are needed. * Each with RoCE Express 2.x adapters (Mellanox ConnectX4/5) attached and firmware 16.29.1006 or earlier. * Assign an IP address to the adapters on both systems and try to ping one node from the other. * The ping will just fail with the stock Ubuntu kernels (not having the patch), but will succeed with kernels that incl. the patches (like the test builds from the PPA mentioned below). * Due to the lack of hardware this needs to be verified by IBM. [Regression Potential] * Undesired / erroneous behavior in case the modified if condition is assembled in a wrong way. * Again wrong behavior in case the modification of the capability bits in mlx5_ifc_cmd_hca_cap_bits are wrong. * All modification are limited to the mlx5 driver only. * The changes are relatively limited with effectively two lines removed and 4 added (three of them adjustments of the capability bits only). * The modifications were done and tested by IBM and reviewed by Mellanox (see LP comments), based on a PPA test build. [Other] * The above patch/commit was upstream accepted with kernel 5.11. * Hence the patch is not needed for hirsute, just needs to be SRUed for groovy and focal. * The commit couldn't be cleanly cherry-picked, mainly due to changed context, hence the backport(s). __ Expose firmware indication that it supports setting eswitch uplink state to follow (follow the physical link). Condition setting the eswitch uplink admin-state with this capability bit. Older FW may not support the uplink state setting. Available fix with kernel 5.11. https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d Now required for Ubuntu 20.04 via backport patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921498] Re: [Ubuntu 21.04] s390/vtime: fix increased steal time accounting
This bug was fixed in the package linux - 5.8.0-53.60
---
linux (5.8.0-53.60) groovy; urgency=medium
* CVE-2021-3491
- io_uring: fix provide_buffers sign extension
- io_uring: fix overflows checks in provide buffers
- SAUCE: proc: Avoid mixing integer types in mem_rw()
- SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide
buffers
* CVE-2021-3490
- bpf: Fix a verifier failure with xor
- SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops
* CVE-2021-3489
- SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf
- SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages
-- Stefan Bader Thu, 06 May 2021 07:43:20
+0200
** Changed in: linux (Ubuntu Groovy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491
--
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/1921498
Title:
[Ubuntu 21.04] s390/vtime: fix increased steal time accounting
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* The reported steal time on s390x is erroneously increasing and
therefore broken.
* This problem got introduced with commit 152e9b8676c6e
("s390/vtime: steal time exponential moving average") - upstream with v5.1
[Fix]
* d54cb7d54877d529bc1e0e1f47a3dd082f73add3 d54cb7d54877 "s390/vtime:
fix increased steal time accounting"
[Test Case]
* An IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04,
20.10 and 21.04 on LPAR, are needed.
* The system needs to be configured as KVM host with one or more KVM
guests.
* Now put significant workload on the guest(s), so that the hypervisor starts
to 'steal time'.
This can be best forced by having only very limited CPU resources for the
hypervisor itself.
* Start monitoring the steal time, that is reported at /proc/stat,
but can be more easily verified with tools like vmstat or even top.
* If the steal time starts ever growing (exponentially), the situation
is broken.
* In case the steal time stays relatively constant,
or grows only very limited after a ramp up phase of some minutes,
or just oscillates around a certain value, a fixed/patched kernel is in use.
[Regression Potential]
* The patch only changes the single line that calculates:
account_steal_time
* In case the account_steal_time calculation is still broken after the
modification,
the steal time is just again not reported correctly on s390x,
but maybe in a different way (rather than exponentially growing).
* But it will not further harm virtualization on s390x systems.
* The modification is very limited with that one line change.
* The commit got upstream accepted with 5.12-rc4.
[Other]
* Since the patch is needed for kernel higher than 5.1 and got upstream
accepted with 5.12-rc4,
hirsute, groovy and focal are affected.
* The upstream commit can be cleanly cherry-picked from all three affected
Ubuntu releases.
__
Description: s390/vtime: fix increased steal time accounting
Symptom: Increased steal time values.
Problem: Commit 152e9b8676c6e ("s390/vtime: steal time exponential
moving average") inadvertently changed the input value for
account_steal_time() from "cputime_to_nsecs(steal)" to just
"steal", resulting in broken increased steal time accounting.
Solution: Fix this by changing it back to "cputime_to_nsecs(steal)".
Reproduction: -
Upstream-ID: d54cb7d54877d529bc1e0e1f47a3dd082f73add3
Stable tagged : kernel 5.1.
Therefore only to be applyable for focal, groovy, hirsuite.
Due to stable tag integration , only for integration checking..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921498/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922582] Re: linux-azure: Enable CONFIG_FPGA_MGR_XILINX_SPI for Azure cloud kernel
This bug was fixed in the package linux-azure - 5.8.0-1032.34 --- linux-azure (5.8.0-1032.34) groovy; urgency=medium [ Ubuntu: 5.8.0-53.60 ] * CVE-2021-3491 - io_uring: fix provide_buffers sign extension - io_uring: fix overflows checks in provide buffers - SAUCE: proc: Avoid mixing integer types in mem_rw() - SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide buffers * CVE-2021-3490 - bpf: Fix a verifier failure with xor - SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops * CVE-2021-3489 - SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf - SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages -- Stefan Bader Thu, 06 May 2021 10:06:14 +0200 ** Changed in: linux-azure (Ubuntu Groovy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491 -- 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/1922582 Title: linux-azure: Enable CONFIG_FPGA_MGR_XILINX_SPI for Azure cloud kernel Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-azure source package in Groovy: Fix Released Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-4.15 source package in Hirsute: Invalid Bug description: [SRU Justification] Microsoft Azure clouds support the use of a Xilinx FPGA to accelerate machine learning and other high performance tasks. The master kernels have had this option since the beginning. The lack of this option for Azure appears to have been an oversight. [Fix] Enable CONFIG_FPGA=m and CONFIG_FPGA_MGR_XILINX_SPI=m. Add these modules to the inclusion list. [Test Plan] modprobe xilinx-spi [Where problems could occur] The chances for regression are minimal as all additions are modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1922582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922759] Re: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10
This bug was fixed in the package linux - 5.8.0-53.60 --- linux (5.8.0-53.60) groovy; urgency=medium * CVE-2021-3491 - io_uring: fix provide_buffers sign extension - io_uring: fix overflows checks in provide buffers - SAUCE: proc: Avoid mixing integer types in mem_rw() - SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide buffers * CVE-2021-3490 - bpf: Fix a verifier failure with xor - SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops * CVE-2021-3489 - SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf - SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages -- Stefan Bader Thu, 06 May 2021 07:43:20 +0200 ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491 -- 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/1922759 Title: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10 Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: The Clevo NH55RZQ and Intel NUC10 need SND_PCI_QUIRKs to fix wrong pin setup and enable microphones to work correctly when using via the audio jacks. Patches that are fixing these problems have already been accepted to current Linux stable releases: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48698c973e6b4dde94d87cd1ded56d9436e9c97d https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=73e7161eab5dee98114987239ec9c87fe8034ddb Commit-hash: 48698c973e6b4dde94d87cd1ded56d9436e9c97d 73e7161eab5dee98114987239ec9c87fe8034ddb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923859] Re: Remove an unused file
This bug was fixed in the package linux-aws - 5.8.0-1033.35 --- linux-aws (5.8.0-1033.35) groovy; urgency=medium [ Ubuntu: 5.8.0-53.60 ] * CVE-2021-3491 - io_uring: fix provide_buffers sign extension - io_uring: fix overflows checks in provide buffers - SAUCE: proc: Avoid mixing integer types in mem_rw() - SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide buffers * CVE-2021-3490 - bpf: Fix a verifier failure with xor - SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops * CVE-2021-3489 - SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf - SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages -- Stefan Bader Thu, 06 May 2021 09:54:52 +0200 ** Changed in: linux-aws (Ubuntu Groovy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491 -- 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/1923859 Title: Remove an unused file Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-aws source package in Focal: Fix Committed Status in linux source package in Groovy: Invalid Status in linux-aws source package in Groovy: Fix Released Bug description: [Impact] debian.aws-20.10/scripts/helpers/copy-files is unused and can be confusing, especially for derivatives. The eye of Sauron (in the form of apw) has cast its baleful glare on this bit of cruft. [Test Plan] Perform a successful build [Where problems could occur] Any regressions will be noted at build time. [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923859/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925290] Re: hangup01 from pty in ubuntu_ltp_stable failed on G-5.8
This bug was fixed in the package linux - 5.8.0-53.60
---
linux (5.8.0-53.60) groovy; urgency=medium
* CVE-2021-3491
- io_uring: fix provide_buffers sign extension
- io_uring: fix overflows checks in provide buffers
- SAUCE: proc: Avoid mixing integer types in mem_rw()
- SAUCE: io_uring: truncate lengths larger than MAX_RW_COUNT on provide
buffers
* CVE-2021-3490
- bpf: Fix a verifier failure with xor
- SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops
* CVE-2021-3489
- SAUCE: bpf: ringbuf: deny reserve of buffers larger than ringbuf
- SAUCE: bpf: prevent writable memory-mapping of read-only ringbuf pages
-- Stefan Bader Thu, 06 May 2021 07:43:20
+0200
** Changed in: linux (Ubuntu Groovy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3489
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3490
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3491
--
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/1925290
Title:
hangup01 from pty in ubuntu_ltp_stable failed on G-5.8
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Groovy:
Fix Released
Bug description:
[Impact]
Testcase hangup01 from ubuntu_ltp_stable.pty is failing on Groovy 5.8.0-51.57.
Test case failed with:
hangup011 TFAIL : hangup01.c:132: unexpected message 3
tag=hangup01 stime=1618856629 dur=1 exit=exited stat=1
It was found that the regression was introduced by the following
commits applied via stable uddates:
dd78b0c483e3 tty: implement read_iter
3b830a9c34d5 tty: convert tty_ldisc_ops 'read()' function to take a kernel
pointer
These patches were applied via bug 1921960 ("Groovy update: upstream
stable patchset 2021-03-30").
[Fix]
Revert the patches mentioned above until a fix can be found.
[Test case]
Run the pty testsuite from ubuntu_ltp_stable.
[Where problems could occur]
If reverting these two patches is not enough to bring the code to the
behavior of the tty driver before 5.8.0-51.57 then remaining issues could still
be present on the tty code. Those issues should be caught by the ltp testcases
though.
[Original Description]
Issue found on Groovy 5.8.0-51.57 with P8 node "dryden" and ARM64 node
"helo-kernel" and AMD64 node "onibi"
Test case failed with:
hangup011 TFAIL : hangup01.c:132: unexpected message 3
tag=hangup01 stime=1618856629 dur=1 exit=exited stat=1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1925290/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928026] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1928026 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1928026 Title: Cannot suspend after the first suspend Status in linux package in Ubuntu: Incomplete Bug description: The suspend fail, it wakes up after 4 or 5 seconds from suspending. This issue is very similar to Elementary OS's problem which I discovered. The only difference is that in Ubuntu, it can suspend for the first time after the restart or turned on, after waking up, it wont be able to suspend again until restart. Ubuntu 20.04.2 LTS Macbook Air 13" Mid 2013 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928026] Re: Cannot suspend after the first suspend
** Tags added: focal ** Package changed: 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/1928026 Title: Cannot suspend after the first suspend Status in linux package in Ubuntu: Incomplete Bug description: The suspend fail, it wakes up after 4 or 5 seconds from suspending. This issue is very similar to Elementary OS's problem which I discovered. The only difference is that in Ubuntu, it can suspend for the first time after the restart or turned on, after waking up, it wont be able to suspend again until restart. Ubuntu 20.04.2 LTS Macbook Air 13" Mid 2013 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928026] [NEW] Cannot suspend after the first suspend
You have been subscribed to a public bug: The suspend fail, it wakes up after 4 or 5 seconds from suspending. This issue is very similar to Elementary OS's problem which I discovered. The only difference is that in Ubuntu, it can suspend for the first time after the restart or turned on, after waking up, it wont be able to suspend again until restart. Ubuntu 20.04.2 LTS Macbook Air 13" Mid 2013 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment focal suspend-resume -- Cannot suspend after the first suspend https://bugs.launchpad.net/bugs/1928026 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 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
** Tags added: architecture-ppc64le bugnameltc-192677 severity-high targetmilestone-inin--- -- 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/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Incomplete Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
This bug was fixed in the package bluez - 5.53-0ubuntu3.1 --- bluez (5.53-0ubuntu3.1) focal; urgency=medium * Add support for the pi 400 (LP: #1903048) -- William 'jawn-smith' Wilson Mon, 15 Mar 2021 19:25:22 + ** Changed in: bluez (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Fix Released Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770845] Re: Make vfio-pci built-in or xhci_hcd optional
** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-kvm (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1770845 Title: Make vfio-pci built-in or xhci_hcd optional Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: New Status in linux source package in Cosmic: Opinion Status in linux-kvm source package in Cosmic: New Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: In Progress Bug description: [Impact] This allows vfio-pci to be bound to certain devices during boot, preventing other drivers from binding them. In particular, USB host drivers, like xhci_hcd, are hard to unbind, as USB devices may end up being used by applications. [Test case] Boot the system with vfio-pci.ids=8086:1e31 or other device ID. [Regression potential] Check that VFIO does not bind to any other device. -- Because of nazar-pc@nazar-pc ~> cat '/boot/config-4.15.0-21-generic' | grep CONFIG_USB_XHCI_HCD CONFIG_USB_XHCI_HCD=y Following doesn't work: nazar-pc@nazar-pc ~> cat /etc/modprobe.d/gpu-passthrough.conf options vfio-pci ids=10de:1b06,10de:10ef,1b21:2142 softdep nouveau pre: vfio-pci softdep xhci_hcd pre: vfio-pci GPU is fine (first 2 IDs), but USB controller is always occupied by xhci_hcd and I can't change that while xhci_hcd is built-in. I'd like you to resolve this issue by either embedding vfio-pci module too (prefered solution) or making xhci_hcd optional. There are some discussions withot clean solution online like this: https://www.reddit.com/r/VFIO/comments/4o6wla/cant_get_vfiopci_to_bind_to_usb_30_card_at_boot/ ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-21-generic 4.15.0-21.22 ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 Uname: Linux 4.15.0-21-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-21-generic. ApportVersion: 2.20.10-0ubuntu2 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: S51 [SB Omni Surround 5.1], device 0: USB Audio [USB Audio] Subdevices: 0/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: nazar-pc 2226 F...m pulseaudio /dev/snd/pcmC1D0p: nazar-pc 2226 F...m pulseaudio /dev/snd/controlC1: nazar-pc 2226 F pulseaudio nazar-pc 2267 F volumeicon Card1.Amixer.info: Card hw:1 'S51'/'Creative Technology Ltd SB Omni Surround 5.1 at usb-:00:14.0-9.2, full spee' Mixer name : 'USB Mixer' Components : 'USB041e:322c' Controls : 12 Simple ctrls : 5 CurrentDesktop: Custom Date: Sat May 12 16:44:11 2018 IwConfig: Error: [Errno 2] Немає такого файла або каталогу: 'iwconfig': 'iwconfig' MachineType: Micro-Star International Co., Ltd. MS-7B45 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/root/boot/vmlinuz-4.15.0-21-generic root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root nosplash intel_pstate=disable scsi_mod.use_blk_mq=1 intel_iommu=on RelatedPackageVersions: linux-restricted-modules-4.15.0-21-generic N/A linux-backports-modules-4.15.0-21-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] Немає такого файла або каталогу: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.51 dmi.board.asset.tag: Default string dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.51:bd03/29/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7B45 dmi.product.version: 2.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/1770845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924685] Re: No sound output/input available after installing 21.04
A release date would be great, I have to boot back (insert other OS here) to use my mic+speakers -- 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/1924685 Title: No sound output/input available after installing 21.04 Status in OEM Priority Project: Won't Fix Status in Release Notes for Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Image: Hirsute 21.04 (20210415 daily build) Device: Dell Precision 5750 After installing 21.04, the sound card is unavailable. In Sound Settings, there is only one choice: "Dummy Output" . The only way to hear sound is to connect a Bluetooth speaker. Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel: https://certification.ubuntu.com/hardware/202002-27726 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1561 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 15:10:05 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Precision 5750 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924685] Re: No sound output/input available after installing 21.04
When do you plan on releasing the fixed kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924685 Title: No sound output/input available after installing 21.04 Status in OEM Priority Project: Won't Fix Status in Release Notes for Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Image: Hirsute 21.04 (20210415 daily build) Device: Dell Precision 5750 After installing 21.04, the sound card is unavailable. In Sound Settings, there is only one choice: "Dummy Output" . The only way to hear sound is to connect a Bluetooth speaker. Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel: https://certification.ubuntu.com/hardware/202002-27726 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1561 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 15:10:05 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Precision 5750 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
I'll upload the latest 5.11.x kernel to a lts-mainline-previous PPA, and longterm 5.10.x kernels to lts-mainline-longterm. 5.10.35 will be available here: https://launchpad.net/~tuxinvader/+archive/ubuntu/lts-mainline-longterm 5.11.19 will be available here: https://launchpad.net/~tuxinvader/+archive/ubuntu/lts-mainline-previous cheers :-) :wq -- 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 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA
@Koba, I have tried kernel 5.10.0-1025lpv1912057g. After boot cat /sys/bus/pci/devices/\:58\:00.0/d3cold_allowed showed "0". After suspend/resume the power consumption is higher. ASPM is disabled for Nvme. I have attached dmesg. ** Attachment added: "dmesg-koba-5.10.0-1025lpv1912057g.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5496367/+files/dmesg-koba-5.10.0-1025lpv1912057g.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/1912057 Title: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA Status in linux package in Ubuntu: Incomplete Bug description: After boot the idle power consumption is around 2.3 W but after suspend it is 4.7 W. The measurement is 5-10 min after boot/resume - looking at "top" to see system was idle. This is consistent - I have tried more that 10 times. BIOS is updated to latest version. I have checked power consumption with external meter - and confirmed that it is higher. I have attached output of: sudo powertop -t 60 -r --html=before.html (and after) I have noticed that Package C-state 6 is reached before suspend but not after. I expect that idle power consumption after suspend should be the same as before. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-38-generic 5.8.0-38.43 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hjh1448 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 15:49:32 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-01-03 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425JA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425JA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425JA_UX425JA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835340] Re: [HMEM] kmem: clear poison reported via mce or ACPI patrol scrub notifications
** Description changed: Description: During run-time, the kernel can be notified of new/latent errors in two different ways: If an application trips over a latent/unknown error, and if the system has machine check recovery, then we will be notified via the mce handler, and the app will be killed. In this case, the kernel should take the chance to go clear-errors for that page, and re-online it so it can be used again in the future. If the 'patrol scrubber' discovers an error on a yet-to-be-accessed location, it can send an ACPI notification to the nfit driver. In this case, the kernel should go clear the error if the page is not in use. If it is in use, the application that has it mapped may need to killed as in case 1 above. This additional run-time handling of errors will augment (and be complimentary to) the init-time handling in userspace, and having both will give us the best possible coverage for media errors. - Target Release: 21.04 + Target Release: 21.10 Target Kernel: TBD ** Tags removed: intel-kernel-21.04 ** Tags added: intel-kernel-21.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835340 Title: [HMEM] kmem: clear poison reported via mce or ACPI patrol scrub notifications Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: During run-time, the kernel can be notified of new/latent errors in two different ways: If an application trips over a latent/unknown error, and if the system has machine check recovery, then we will be notified via the mce handler, and the app will be killed. In this case, the kernel should take the chance to go clear-errors for that page, and re-online it so it can be used again in the future. If the 'patrol scrubber' discovers an error on a yet-to-be-accessed location, it can send an ACPI notification to the nfit driver. In this case, the kernel should go clear the error if the page is not in use. If it is in use, the application that has it mapped may need to killed as in case 1 above. This additional run-time handling of errors will augment (and be complimentary to) the init-time handling in userspace, and having both will give us the best possible coverage for media errors. Target Release: 21.10 Target Kernel: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
There is/was also some discussion on https://askubuntu.com/questions/1334633/mainline-kernel-now-depends-on- libc6-2-33-non-installable-in-focal -- I'm also interested in 5.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1889342] Re: Thunderbolt Dock Loses Monitors
@koba, sorry I use Arch, not Ubuntu/Debian. -- 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/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 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 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Even 5.10 series is affected. I'm on 20.04 and was installing 5.10 series. Now I'm stuck on 5.10.32 because 5.10.33 requires new version of libc6. -- 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 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA
@Henrik, Sorry for causing your inconvenience. don't be in a hurry and if you have free time, please help to try this test kernel remove irrelevant codes. https://drive.google.com/drive/folders/1wRGJNPU0LmmyJMkVLZvG7xLKqinsOZU0?usp=sharing -- 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/1912057 Title: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA Status in linux package in Ubuntu: Incomplete Bug description: After boot the idle power consumption is around 2.3 W but after suspend it is 4.7 W. The measurement is 5-10 min after boot/resume - looking at "top" to see system was idle. This is consistent - I have tried more that 10 times. BIOS is updated to latest version. I have checked power consumption with external meter - and confirmed that it is higher. I have attached output of: sudo powertop -t 60 -r --html=before.html (and after) I have noticed that Package C-state 6 is reached before suspend but not after. I expect that idle power consumption after suspend should be the same as before. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-38-generic 5.8.0-38.43 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hjh1448 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 15:49:32 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-01-03 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425JA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425JA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425JA_UX425JA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926030] Re: IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
Thanks for the quick test, I have submitted a SRU request for this:
https://lists.ubuntu.com/archives/kernel-team/2021-May/120150.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1926030
Title:
IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Groovy:
New
Bug description:
[Impact]
Patch:
* media: rc: fix timeout handling after switch to microsecond durations
* media: rc: ite-cir: fix min_timeout calculation
Were applied to Groovy with our stable update process (bug 1918516)
User reported that IR Remote key press will be repeated for multiple times
with these patches applied.
Commit 528222d853f92 ("media: rc: harmonize infrared durations to
microseconds") that needs to be fixed by these two does not exist in
5.8 kernel. The patch author Matthias Reichl also state these are for
5.10 and onward.
[Fix]
Revert these two patches for groovy.
[Test]
Test kernels for G-5.8 / F-5.8 can be found here:
https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/
User Ted L confirmed that F-5.8 test kernel can fix the problem.
[Where problems could occur]
The chance to cause regression can be considered as low since the original
patch that need to be fix by these two patches does not exist in 5.8 at all.
[Original Bug Report]
I use an IR remote with the ir-keytable package. Everything was working fine
until kernel 5.8.0-49 was automatically installed by Software Updater on Ubuntu
20.04.2. When any key is pressed on the remote, the key is repeated about 500
times. The kernel is now 5.8.0-50, and the problem persists.
Other users on the MythTV mailing list are reporting the issue, and it
appears that the problem is related to changes in the following files:
drivers/media/rc/ir-mce_kbd-decoder.c
drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c
drivers/media/rc/serial_ir.c
It has been reported that reverting the ir-mce_kbd-decoder.c and rc-
main.c files to the older versions fixes the problem.
/proc/version_signature > version.log:
Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
lspci -vnvn:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core
Processor Host Bridge/DRAM Registers [8086:590f] (rev 06)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host
Bridge/DRAM Registers [1043:8694]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-
Kernel driver in use: skl_uncore
ir-keytable -V:
IR keytable control version 1.18.0
lsb_release -rd:
Description: Ubuntu 20.04.2 LTS
Release: 20.04
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ted1020 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-09-19 (217 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IwConfig:
lono wireless extensions.
enp3s0no wireless extensions.
enp0s31f6 no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic
root=UUID=529cae8e-19cd-4732-80d5-b3dca123afc6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
RelatedPackageVersions:
linux-restricted-modules-5.8.0-50-generic N/A
linux-backports-modules-5.8.0-50-generic N/A
linux-firmware1.187.11
RfKill:
Tags: focal
Uname: Linux 5.8.0-50-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd mythtv plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/05/2017
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3405
dmi.board.asset.tag: Default string
dmi.board.name: H110T
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.:bvr3405:bd07/05/2017:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110T:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Pro
[Kernel-packages] [Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA
@Koba, Thanks for your help. I have tried the kernel from #55. sudo cat /sys/bus/pci/devices/\:58\:00.0/d3cold_allowed showed "0". The suspend & resume did end up in a freeze. I have attached dmesg (journalctl -k -b -1 on next boot). Just as a note I saw the power consumption during suspend was around 1.0W compared to 0.5W using the 5.10-oem-1025 and "echo 0 | sudo tee" from #51. This was using an external AC power meter - so it includes the power loss in the AC adapter. ** Attachment added: "dmesg-koba-5.10.0-1025lpv1912057f.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5496322/+files/dmesg-koba-5.10.0-1025lpv1912057f.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/1912057 Title: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA Status in linux package in Ubuntu: Incomplete Bug description: After boot the idle power consumption is around 2.3 W but after suspend it is 4.7 W. The measurement is 5-10 min after boot/resume - looking at "top" to see system was idle. This is consistent - I have tried more that 10 times. BIOS is updated to latest version. I have checked power consumption with external meter - and confirmed that it is higher. I have attached output of: sudo powertop -t 60 -r --html=before.html (and after) I have noticed that Package C-state 6 is reached before suspend but not after. I expect that idle power consumption after suspend should be the same as before. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-38-generic 5.8.0-38.43 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hjh1448 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 15:49:32 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-01-03 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425JA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425JA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425JA_UX425JA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926030] Re: IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
** Description changed:
- I use an IR remote with the ir-keytable package. Everything was working
- fine until kernel 5.8.0-49 was automatically installed by Software
- Updater on Ubuntu 20.04.2. When any key is pressed on the remote, the
- key is repeated about 500 times. The kernel is now 5.8.0-50, and the
- problem persists.
+ [Impact]
+ Patch:
+ * media: rc: fix timeout handling after switch to microsecond durations
+ * media: rc: ite-cir: fix min_timeout calculation
+
+ Were applied to Groovy with our stable update process (bug 1918516)
+
+ User reported that IR Remote key press will be repeated for multiple times
+ with these patches applied.
+
+ Commit 528222d853f92 ("media: rc: harmonize infrared durations to
+ microseconds") that needs to be fixed by these two does not exist in 5.8
+ kernel. The patch author Matthias Reichl also state these are for 5.10
+ and onward.
+
+ [Fix]
+ Revert these two patches for groovy.
+
+ [Test]
+ Test kernels for G-5.8 / F-5.8 can be found here:
+ https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/
+
+ User Ted L confirmed that F-5.8 test kernel can fix the problem.
+
+ [Where problems could occur]
+ The chance to cause regression can be considered as low since the original
patch that need to be fix by these two patches does not exist in 5.8 at all.
+
+
+ [Original Bug Report]
+ I use an IR remote with the ir-keytable package. Everything was working fine
until kernel 5.8.0-49 was automatically installed by Software Updater on Ubuntu
20.04.2. When any key is pressed on the remote, the key is repeated about 500
times. The kernel is now 5.8.0-50, and the problem persists.
Other users on the MythTV mailing list are reporting the issue, and it
appears that the problem is related to changes in the following files:
drivers/media/rc/ir-mce_kbd-decoder.c
drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c
drivers/media/rc/serial_ir.c
It has been reported that reverting the ir-mce_kbd-decoder.c and rc-
main.c files to the older versions fixes the problem.
/proc/version_signature > version.log:
Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
lspci -vnvn:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core
Processor Host Bridge/DRAM Registers [8086:590f] (rev 06)
- Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor
Host Bridge/DRAM Registers [1043:8694]
- Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-
- Kernel driver in use: skl_uncore
+ Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host
Bridge/DRAM Registers [1043:8694]
+ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-
+ Kernel driver in use: skl_uncore
ir-keytable -V:
IR keytable control version 1.18.0
lsb_release -rd:
Description: Ubuntu 20.04.2 LTS
Release: 20.04
- ---
+ ---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: ted1020 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: ted1020 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-09-19 (217 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IwConfig:
- lono wireless extensions.
-
- enp3s0no wireless extensions.
-
- enp0s31f6 no wireless extensions.
+ lono wireless extensions.
+
+ enp3s0no wireless extensions.
+
+ enp0s31f6 no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcEnviron:
- TERM=xterm-256color
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic
root=UUID=529cae8e-19cd-4732-80d5-b3dca123afc6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
RelatedPackageVersions:
- linux-restricted-modules-5.8.0-50-generic N/A
- linux-backports-modules-5.8.0-50-generic N/A
- linux-firmware1.187.11
+ linux-restricted-modules-5.8.0-50-generic N/A
+ linux-backports-modules-5.8.0-50-generic N/A
+ linux-firmware1.187.11
RfKill:
-
+
Tags: focal
Uname: Linux 5.8.0-50-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd mythtv plugdev sambash
[Kernel-packages] [Bug 1910323] Re: Fix implicit declaration warnings for kselftests/memfd test on newer releases
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1056.60
---
linux-oem-5.6 (5.6.0-1056.60) focal; urgency=medium
* focal/linux-oem-5.6: 5.6.0-1056.60 -proposed tracker (LP: #1923783)
* CVE-2021-29646
- tipc: better validate user input in tipc_nl_retrieve_key()
* CVE-2021-28375
- misc: fastrpc: restrict user apps from sending kernel RPC messages
* CVE-2020-35519
- net/x25: prevent a couple of overflows
* CVE-2021-30002
- media: v4l: ioctl: Fix memory leak in video_usercopy
* SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10 (LP: #1922759)
- ALSA: hda/realtek: Add quirk for Intel NUC 10
- ALSA: hda/realtek: Add quirk for Clevo NH55RZQ
* CVE-2021-29650
- netfilter: x_tables: Use correct memory barriers.
* Fix implicit declaration warnings for kselftests/memfd test on newer
releases (LP: #1910323)
- selftests/memfd: Fix implicit declaration warnings
-- Chia-Lin Kao (AceLan) Tue, 04 May 2021
11:46:25 +0800
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-35519
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-28375
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-29646
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-30002
--
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/1910323
Title:
Fix implicit declaration warnings for kselftests/memfd test on newer
releases
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.6 package in Ubuntu:
New
Status in linux source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Released
Bug description:
[Impact]
While debugging bug 1910277, I found that the test compilation will
print some warnings:
memfd_test.c:64:7: warning: implicit declaration of function ‘open’;
memfd_test.c:90:6: warning: implicit declaration of function ‘fcntl’
memfd_test.c:397:6: warning: implicit declaration of function ‘fallocate’;
fuse_test.c:67:6: warning: implicit declaration of function ‘fcntl’
fuse_test.c:261:7: warning: implicit declaration of function ‘open’;
It's harmless but fixing this we can make the test report easier to
read.
[Fix]
* 1c49e3783f8899 ("selftests/memfd: Fix implicit declaration warnings")
This fix can be cherry-picked into F/F-oem-5.6/G and compiled without
any problem. Older kernel does not have this issue since they're
missing some other commits.
[Test Case]
Build the memfd test in tools/testing/selftests/ with:
sudo make TARGETS=memfd
With this fix, these warnings will be gone.
[Where problems could occur]
This fix is just for fixing the test case compilation, so it's not
affecting real kernel functionality.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910323/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922759] Re: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1056.60 --- linux-oem-5.6 (5.6.0-1056.60) focal; urgency=medium * focal/linux-oem-5.6: 5.6.0-1056.60 -proposed tracker (LP: #1923783) * CVE-2021-29646 - tipc: better validate user input in tipc_nl_retrieve_key() * CVE-2021-28375 - misc: fastrpc: restrict user apps from sending kernel RPC messages * CVE-2020-35519 - net/x25: prevent a couple of overflows * CVE-2021-30002 - media: v4l: ioctl: Fix memory leak in video_usercopy * SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10 (LP: #1922759) - ALSA: hda/realtek: Add quirk for Intel NUC 10 - ALSA: hda/realtek: Add quirk for Clevo NH55RZQ * CVE-2021-29650 - netfilter: x_tables: Use correct memory barriers. * Fix implicit declaration warnings for kselftests/memfd test on newer releases (LP: #1910323) - selftests/memfd: Fix implicit declaration warnings -- Chia-Lin Kao (AceLan) Tue, 04 May 2021 11:46:25 +0800 ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-35519 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-28375 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-29646 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-29650 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-30002 -- 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/1922759 Title: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10 Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: The Clevo NH55RZQ and Intel NUC10 need SND_PCI_QUIRKs to fix wrong pin setup and enable microphones to work correctly when using via the audio jacks. Patches that are fixing these problems have already been accepted to current Linux stable releases: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48698c973e6b4dde94d87cd1ded56d9436e9c97d https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=73e7161eab5dee98114987239ec9c87fe8034ddb Commit-hash: 48698c973e6b4dde94d87cd1ded56d9436e9c97d 73e7161eab5dee98114987239ec9c87fe8034ddb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
