[Kernel-packages] [Bug 1924717] Re: Internal speaker doesn't work after plug in a headset
Let us disable the "Auto-Mute" first, then redo the test. Simple mixer control 'Auto-Mute Mode',0 Capabilities: enum Items: 'Disabled' 'Enabled' Item0: 'Enabled' -- 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/1924717 Title: Internal speaker doesn't work after plug in a headset Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: [Summary] Internal speaker doesn't work after plug in a headset. In the meantime, audio for HDMI/Buletooth headset/wired headset are working fine. Only Internal speaker doesn't work. But internal speaker working well if not plug wired headset in. CID:202010-28313 https://certification.canonical.com/hardware/202010-28313/ 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 1512 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 05:07:59 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Latitude 5520 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.11.0-14-generic root=UUID=8bcd3f6a-d6e8-494d-93fa-6f720bf6e582 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: 01/13/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: 1132343535 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/13/2021:br1.2:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5520 dmi.product.sku: 0A21 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1924717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907212] Re: Power consumption regression after upgrade to 20.10 5.8.0-31-generic
Turns out this is going to be really hard. It requires change in both PCI and HDA, and potentially in nouveau and proprietary nvidia driver. I'll revisit this once upstream devs have a concrete plan. ** Changed in: linux (Ubuntu) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- 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/1907212 Title: Power consumption regression after upgrade to 20.10 5.8.0-31-generic Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 20.10 which ships kernel 5.8.0-31-generic, battery life is considerably less and power consumption is about 10 watts more idle, (idling at 14-15 watts) using integrated graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and based on past experiences a possible cause is not powering off the dedicated GPU completely while using the integrated. Running sudo powertop --auto-tune doesn't eliminate the issue. $ cat /sys/bus/pci/devices/:01:00.0/power/runtime_status suspended $ cat /sys/bus/pci/devices/:01:00.0/power/runtime_suspended_time 1815948 $ cat /sys/bus/pci/devices/:01:00.1/power/runtime_status active $ cat /sys/bus/pci/devices/:01:00.1/power/runtime_suspended_time 3827 Device "01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller" appears active, does this mean that the audio subsystem of dGPU keeps it enabled, causing the 10-watt consumption? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54
Adding a new module parameter to select different algorithms shouldn't be too hard, anyone up to the task? -- 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/1861554 Title: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54 Status in linux package in Ubuntu: Confirmed Bug description: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic. This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin, MX and so on. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. here is a video: https://youtu.be/9Rez7s0V6iA here is another user with same problem: https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922293] Re: Snaps appear broken on 21.04 Beta with ZFS
Just an update, I still see this in the beta after a reboot. Workaround still functions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1922293 Title: Snaps appear broken on 21.04 Beta with ZFS Status in snapd package in Ubuntu: In Progress Status in zfs-linux package in Ubuntu: Fix Released Bug description: I've attempted to use two different userland snaps (qownnotes and keepassxc) neither function. When attempting to launch I get the following error: ``` chalbersma@abdos:~$ qownnotes cannot perform operation: mount --rbind /dev /tmp/snap.rootfs_t3kehe//dev: No such file or directory ``` Additionally the snaps installed "by default" have a note of "broken" next to them : ``` chalbersma@abdos:~$ sudo snap list Name Version RevTracking Publisher Notes core18 1997 latest/stablecanonical✓ broken gnome-3-34-1804 66 latest/stable/… canonical✓ broken gtk-common-themes 1514 latest/stable/… canonical✓ broken qownnotes 21.3.9 8183 latest/stablepbek- snap-store 518latest/stable/… canonical✓ broken snapd 11402 latest/stablecanonical✓ broken ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1922293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924763] Re: Problems with brcmsmac driver and Broadcom BCM4360
It doesn't seem to supports BCM4360... ** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist -- 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/1924763 Title: Problems with brcmsmac driver and Broadcom BCM4360 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I am trying to make it work this device with the driver brcmsmac, since seems is the only one that supports AP mode (and this is mandatory in our case; all other drivers for this devices, including proprietary one, does not support this mode). When I issue sudo modprobe brcmsmac, this is what I get in logs: cfg80211: Loading compiled-in X.509 certificates for regulatory database cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' bcma-pci-bridge :06:00.0: bus0: Found chip with id 0x4360, rev 0x03 and package 0x01 bcma-pci-bridge :06:00.0: bus0: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x2B, class 0x0) bcma-pci-bridge :06:00.0: bus0: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x2A, class 0x0) bcma-pci-bridge :06:00.0: bus0: Core 2 found: ARM CR4 (manuf 0x4BF, id 0x83E, rev 0x02, class 0x0) bcma-pci-bridge :06:00.0: bus0: Core 3 found: PCIe Gen2 (manuf 0x4BF, id 0x83C, rev 0x01, class 0x0) bcma-pci-bridge :06:00.0: bus0: Core 4 found: USB 2.0 Device (manuf 0x4BF, id 0x81A, rev 0x11, class 0x0) bcma: Unsupported SPROM revision: 11 bcma-pci-bridge :06:00.0: bus0: Invalid SPROM read from the PCIe card, trying to use fallback SPROM bcma-pci-bridge :06:00.0: bus0: Using fallback SPROM failed (err -2) bcma-pci-bridge :06:00.0: bus0: No SPROM available bcma-pci-bridge :06:00.0: bus0: Bus registered Currently this PC is running Ubuntu 20.04 with kernel 5.8.0-50-generic (using linux-image-generic-hwe-20.04-edge). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: KDE neon 20.04 IwConfig: lono wireless extensions. enp8s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. A320M-S2H V2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=d79c1263-3eed-43a8-acd5-3ea79e3ae084 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/02/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H V2-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd12/02/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2HV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2HV2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H V2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925415] [NEW] Enable mute/micmute LEDs and limit mic boost on EliteBook 845 G8
Public bug reported: [Impact] Mute/micmute LEDs don't work. In addition, the internal mic can only capture lots of noises. [Fix] Use Realtek specific coef to enable LEDs and limit mic boost on the platform. [Test] With the patch applied, the both LEDs start to work, and audio recording becomes crystal clear. [Where problems could occur] It's a trivial change to a brand new device, so no existing device is affected. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Hirsute) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1923711 originate-from-1923712 stella ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Tags added: oem-priority originate-from-1923711 stella ** Tags added: originate-from-1923712 -- 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/1925415 Title: Enable mute/micmute LEDs and limit mic boost on EliteBook 845 G8 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: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] Mute/micmute LEDs don't work. In addition, the internal mic can only capture lots of noises. [Fix] Use Realtek specific coef to enable LEDs and limit mic boost on the platform. [Test] With the patch applied, the both LEDs start to work, and audio recording becomes crystal clear. [Where problems could occur] It's a trivial change to a brand new device, so no existing device is affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1925415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923062] Re: NVIDIA CVE-2021-1076 CVE-2021-1077
Also tested linux-modules-nvidia-460-server-generic-hwe-18.04 on bionic and linux-modules-nvidia-460-server-generic-hwe-20.04 on focal. They look good now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1923062 Title: NVIDIA CVE-2021-1076 CVE-2021-1077 Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: In Progress Status in nvidia-graphics-drivers-418-server source package in Bionic: In Progress Status in nvidia-graphics-drivers-450 source package in Bionic: In Progress Status in nvidia-graphics-drivers-450-server source package in Bionic: In Progress Status in nvidia-graphics-drivers-460 source package in Bionic: In Progress Status in nvidia-graphics-drivers-460-server source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: In Progress Status in nvidia-graphics-drivers-450 source package in Focal: In Progress Status in nvidia-graphics-drivers-450-server source package in Focal: In Progress Status in nvidia-graphics-drivers-460 source package in Focal: In Progress Status in nvidia-graphics-drivers-460-server source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: In Progress Status in nvidia-graphics-drivers-418-server source package in Groovy: In Progress Status in nvidia-graphics-drivers-450 source package in Groovy: In Progress Status in nvidia-graphics-drivers-450-server source package in Groovy: In Progress Status in nvidia-graphics-drivers-460 source package in Groovy: In Progress Status in nvidia-graphics-drivers-460-server source package in Groovy: In Progress Bug description: Here is the list of the affected drivers: 418-server - CVE-2021-1076 460, 450, 460-server, 450-server - CVE-2021-1076 CVE-2021-1077 390 - CVE-2021-1076 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1923062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
A cross reference on F-5.8 RISCV: $ uname -a Linux riscv64-focal 5.8.0-23-generic #25~20.04.1-Ubuntu SMP Tue Apr 20 12:51:20 UTC 2021 riscv64 riscv64 riscv64 GNU/Linux $ grep AUFS /boot/config-5.8.0-23-generic CONFIG_AUFS_FS=m CONFIG_AUFS_BRANCH_MAX_127=y # CONFIG_AUFS_BRANCH_MAX_511 is not set # CONFIG_AUFS_BRANCH_MAX_1023 is not set # CONFIG_AUFS_BRANCH_MAX_32767 is not set CONFIG_AUFS_SBILIST=y # CONFIG_AUFS_HNOTIFY is not set CONFIG_AUFS_EXPORT=y CONFIG_AUFS_INO_T_64=y CONFIG_AUFS_XATTR=y # CONFIG_AUFS_FHSM is not set # CONFIG_AUFS_RDU is not set CONFIG_AUFS_DIRREN=y # CONFIG_AUFS_SHWH is not set # CONFIG_AUFS_BR_RAMFS is not set # CONFIG_AUFS_BR_FUSE is not set CONFIG_AUFS_BR_HFSPLUS=y CONFIG_AUFS_BDEV_LOOP=y # CONFIG_AUFS_DEBUG is not set ** Description changed: 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 + 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 + 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. ** Also affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-riscv (Ubuntu Hirsute) Importance: Undecided Status: New -- 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 Status in ubuntu-kernel-tests: New Status in linux-riscv package in Ubuntu: New Status in linux-riscv source package in Hirsute: New 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 1924624] Re: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable
Downgrade to kernel 48 and works. Please update to 51 release asap. -- 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/1924624 Title: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-5.8 package in Ubuntu: Confirmed Bug description: After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was suddenly extremely glitchy. Icons from the desktop flash through the browser, windows top bar gets distorted, all sort of glitches appear, parts of characters are missing in terminal, scrolling is inconsistent and the whole desktop becomes unusable. Under wayland the graphics are a bit more stable, but lots of glitches appear anyway, video reproduction in browser is stuttering and wobbly. Booting with previous kernel 5.8.0-48 seems to fix the issues. 5.8.0-50 is broken as well. this is the result of 'sudo lshw -c video' on my hp Elitebook 8470: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:d400-d43f memory:c000-cfff ioport:4000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923506] Re: linux-source-5.11.0 spuriously "suggests" kernel-package
Confirming with no log, since this is not a runtime issue. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923506 Title: linux-source-5.11.0 spuriously "suggests" kernel-package Status in linux package in Ubuntu: Confirmed Bug description: The linux-source-5.11.0 package should not suggest kernel-package. kernel-package is not available. Per Debian bug #960377, kernel- package is discontinued. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923506/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925386] Re: Upgrade from 460.32.03-0ubuntu2 to 460.73.01-0ubuntu1 fails
I was able to replicate this with focal 5.4.0-72-generic on DGX2 steps I took to reproduce sudo apt install nvidia-dkms-460-server enable proposed apt update sudo apt install nvidia-dkms-460-server The upgrade does work correctly if I instead use 'nvidia-driver-460-server' -- 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/1925386 Title: Upgrade from 460.32.03-0ubuntu2 to 460.73.01-0ubuntu1 fails Status in nvidia-graphics-drivers-460-server package in Ubuntu: New 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-25896:~$ ls /var/lib/dkms/nvidia-srv/460.73.01/build/ dkms.conf patches ubuntu@dgx-1-exotic-skunk-201710-25896:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1925386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923062] Re: NVIDIA CVE-2021-1076 CVE-2021-1077
Testing of the server drivers is also complete. All drivers were able to install as both dkms and l-r-m with no issues. A cuda workload and nvidia-smi was also tested for each. Note: no upgrade testing was attempted. Drivers were fully purged before testing the next driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1923062 Title: NVIDIA CVE-2021-1076 CVE-2021-1077 Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: In Progress Status in nvidia-graphics-drivers-418-server source package in Bionic: In Progress Status in nvidia-graphics-drivers-450 source package in Bionic: In Progress Status in nvidia-graphics-drivers-450-server source package in Bionic: In Progress Status in nvidia-graphics-drivers-460 source package in Bionic: In Progress Status in nvidia-graphics-drivers-460-server source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: In Progress Status in nvidia-graphics-drivers-450 source package in Focal: In Progress Status in nvidia-graphics-drivers-450-server source package in Focal: In Progress Status in nvidia-graphics-drivers-460 source package in Focal: In Progress Status in nvidia-graphics-drivers-460-server source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: In Progress Status in nvidia-graphics-drivers-418-server source package in Groovy: In Progress Status in nvidia-graphics-drivers-450 source package in Groovy: In Progress Status in nvidia-graphics-drivers-450-server source package in Groovy: In Progress Status in nvidia-graphics-drivers-460 source package in Groovy: In Progress Status in nvidia-graphics-drivers-460-server source package in Groovy: In Progress Bug description: Here is the list of the affected drivers: 418-server - CVE-2021-1076 460, 450, 460-server, 450-server - CVE-2021-1076 CVE-2021-1077 390 - CVE-2021-1076 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1923062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922599] Re: fails to create a new context
This appears to no longer be an issue with the 460.73.01 driver:
$ sudo ./foo
cuCtxCreate returned 0
$
--
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/1922599
Title:
fails to create a new context
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
New
Bug description:
With the 460 driver on a 5.11 kernel, I'm unable to initialize a new
context.
ubuntu@blanka:~$ cat foo.c
#include
#include
#include
int main(){
int ret;
assert (cuInit(0) == 0);
CUcontext ctx;
CUdevice device;
assert(cuDeviceGet(,0) == 0 );
ret = cuCtxCreate(, 0, device);
printf("cuCtxCreate returned %d\n", ret);
return 0;
}
$ sudo ./foo
cuCtxCreate returned 1
This works fine with the 450 driver.
$ cat /proc/version
Linux version 5.11.0-13-generic (buildd@lgw01-amd64-035) (gcc (Ubuntu
10.2.1-23ubuntu1) 10.2.1 20210312, GNU ld (GNU Binutils for Ubuntu) 2.36.1)
#14-Ubuntu SMP Fri Mar 19 16:55:27 UTC 2021
$ dpkg -l | grep nvidia-cuda-dev
ii nvidia-cuda-dev:amd64 11.2.1-2
amd64NVIDIA CUDA
development files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1922599/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490780/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490783/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490779/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490774/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490772/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490775/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490784/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490777/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490782/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490781/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490778/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490768/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490776/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490773/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490771/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490770/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490769/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490767/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490766/+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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490765/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] Re: Boot stuck in UEFI after enrolling keys for drivers
Hello Dan, Thank you very much for your comments! I played with graphics card settings and found out that when I use only Intel graphics everything works well and I can boot without stuck. I performed the following steps. 1. Originally I used NVidia graphics via NVidia driver. 2. First I switched on Nouveau driver and it didn't help. 3. Then I switched again on NVidia recommended driver (nvidia-driver-460) and it didn't help. 4. Eventually I switched on Intel graphics via nvidia-settings (prime selection) and it helped. Thanks! ** Tags added: apport-collected wayland-session ** Description changed: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu65 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: gluttton 1602 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2021-03-06 (46 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + MachineType: LENOVO 82A1 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 + RelatedPackageVersions: + linux-restricted-modules-5.11.0-16-generic N/A + linux-backports-modules-5.11.0-16-generic N/A + linux-firmware 1.197 + Tags: hirsute wayland-session + Uname: Linux 5.11.0-16-generic x86_64 + UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) + UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/14/2021 + dmi.bios.release: 1.31 + dmi.bios.vendor: LENOVO + dmi.bios.version: DHCN31WW + dmi.board.asset.tag: ��� + dmi.board.name: LNVNB161216 + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40688 WIN + dmi.chassis.asset.tag: ��� + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Yoga Slim 7 14IIL05 + dmi.ec.firmware.release: 1.29 + dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: + dmi.product.family: Yoga Slim 7 14IIL05 + dmi.product.name: 82A1 + dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 + dmi.product.version: Yoga Slim 7 14IIL05 + dmi.sys.vendor: LENOVO -- 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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during
[Kernel-packages] [Bug 1925386] Re: Upgrade from 460.32.03-0ubuntu2 to 460.73.01-0ubuntu1 fails
It works fine if I remove the old version before installing the new: ubuntu@dgx-1-exotic-skunk-201710-25896:~$ sudo apt autoremove nvidia-dkms-460-server Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: dctrl-tools dkms libpciaccess0 nvidia-dkms-460-server nvidia-kernel-common-460-server nvidia-kernel-source-460-server 0 upgraded, 0 newly installed, 6 to remove and 36 not upgraded. 1 not fully installed or removed. After this operation, 49.5 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 87066 files and directories currently installed.) Removing nvidia-dkms-460-server (460.73.01-0ubuntu1) ... Removing all DKMS Modules Done. update-initramfs: deferring update (trigger activated) Removing dkms (2.8.4-4) ... Removing dctrl-tools (2.24-3) ... Removing nvidia-kernel-common-460-server (460.73.01-0ubuntu1) ... update-initramfs: deferring update (trigger activated) Removing libpciaccess0:amd64 (0.16-1build2) ... Removing nvidia-kernel-source-460-server (460.32.03-0ubuntu2) ... Processing triggers for libc-bin (2.33-0ubuntu5) ... 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 Scanning processes... Scanning processor microcode... Scanning linux images... Running kernel seems to be up-to-date. The processor microcode seems to be up-to-date. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. 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 nvidia-utils-460-server is already the newest version (460.73.01-0ubuntu1). The following additional packages will be installed: dctrl-tools dkms libpciaccess0 nvidia-kernel-common-460-server nvidia-kernel-source-460-server Suggested packages: debtags menu The following NEW packages will be installed: dctrl-tools dkms libpciaccess0 nvidia-dkms-460-server nvidia-kernel-common-460-server nvidia-kernel-source-460-server 0 upgraded, 6 newly installed, 0 to remove and 36 not upgraded. Need to get 24.6 MB/24.7 MB of archives. After this operation, 49.6 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu hirsute/main amd64 dctrl-tools amd64 2.24-3 [61.5 kB] Get:2 http://archive.ubuntu.com/ubuntu hirsute/main amd64 dkms all 2.8.4-4 [68.3 kB] Get:3 http://archive.ubuntu.com/ubuntu hirsute/main amd64 libpciaccess0 amd64 0.16-1build2 [18.0 kB] Get:4 http://archive.ubuntu.com/ubuntu hirsute-proposed/restricted amd64 nvidia-kernel-source-460-server amd64 460.73.01-0ubuntu1 [24.5 MB] Fetched 24.6 MB in 5s (5246 kB/s) Selecting previously unselected package dctrl-tools. (Reading database ... 86584 files and directories currently installed.) Preparing to unpack .../0-dctrl-tools_2.24-3_amd64.deb ... Unpacking dctrl-tools (2.24-3) ... Selecting previously unselected package dkms. Preparing to unpack .../1-dkms_2.8.4-4_all.deb ... Unpacking dkms (2.8.4-4) ... Selecting previously unselected package libpciaccess0:amd64. Preparing to unpack .../2-libpciaccess0_0.16-1build2_amd64.deb ... Unpacking libpciaccess0:amd64 (0.16-1build2) ... Selecting previously unselected package nvidia-kernel-source-460-server. Preparing to unpack .../3-nvidia-kernel-source-460-server_460.73.01-0ubuntu1_amd 64.deb ... Unpacking nvidia-kernel-source-460-server (460.73.01-0ubuntu1) ... Selecting previously unselected package nvidia-kernel-common-460-server. Preparing to unpack .../4-nvidia-kernel-common-460-server_460.73.01-0ubuntu1_amd 64.deb ... Unpacking nvidia-kernel-common-460-server (460.73.01-0ubuntu1) ... Selecting previously unselected package nvidia-dkms-460-server. Preparing to unpack .../5-nvidia-dkms-460-server_460.73.01-0ubuntu1_amd64.deb .. . Unpacking nvidia-dkms-460-server (460.73.01-0ubuntu1) ... Setting up libpciaccess0:amd64 (0.16-1build2) ... Setting up nvidia-kernel-common-460-server (460.73.01-0ubuntu1) ... update-initramfs: deferring update (trigger activated) Setting up nvidia-kernel-source-460-server (460.73.01-0ubuntu1) ... Setting up dctrl-tools (2.24-3) ... Setting up dkms (2.8.4-4) ... 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 Secure Boot not enabled on this system.
[Kernel-packages] [Bug 1925386] Re: Upgrade from 460.32.03-0ubuntu2 to 460.73.01-0ubuntu1 fails
** Attachment added: "sosreport-dgx-1-exotic-skunk-201710-25896-2021-04-21-gqdnfmi.tar.xz" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1925386/+attachment/5490762/+files/sosreport-dgx-1-exotic-skunk-201710-25896-2021-04-21-gqdnfmi.tar.xz -- 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/1925386 Title: Upgrade from 460.32.03-0ubuntu2 to 460.73.01-0ubuntu1 fails Status in nvidia-graphics-drivers-460-server package in Ubuntu: New 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-25896:~$ ls /var/lib/dkms/nvidia-srv/460.73.01/build/ dkms.conf patches ubuntu@dgx-1-exotic-skunk-201710-25896:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1925386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925386] [NEW] Upgrade from 460.32.03-0ubuntu2 to 460.73.01-0ubuntu1 fails
Public bug reported: 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-25896:~$ ls /var/lib/dkms/nvidia-srv/460.73.01/build/ dkms.conf patches ubuntu@dgx-1-exotic-skunk-201710-25896:~$ ** Affects: nvidia-graphics-drivers-460-server (Ubuntu) Importance: Undecided Status: New -- 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/1925386 Title: Upgrade from 460.32.03-0ubuntu2 to 460.73.01-0ubuntu1 fails Status in nvidia-graphics-drivers-460-server package in Ubuntu: New 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) ...
[Kernel-packages] [Bug 1910562] 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 1910562 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/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Invalid Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885862] Re: Add in-tree Realtek 8821CE wireless module support
Just wondering. I am still using rtl8821ce-dkms on Ubuntu 20.04. This is
not needed anymore now and 5 Ghz Wifi DFS protetcted channels are now
available?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1885862
Title:
Add in-tree Realtek 8821CE wireless module support
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-firmware source package in Focal:
Fix Released
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Status in linux source package in Groovy:
Won't Fix
Status in linux-firmware source package in Groovy:
Invalid
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification]
[Impact]
RTL8821CE RFE Type 2 PCIE module is not supported by new rtw88 driver
in kernel version v5.11 or older. Dmesg gives:
rtw_8821ce :01:00.0: enabling device ( -> 0003)
rtw_8821ce :01:00.0: Firmware version 24.8.0, H2C version 12
rtw_8821ce :01:00.0: rfe 2 isn't supported
rtw_8821ce :01:00.0: failed to setup chip efuse info
rtw_8821ce :01:00.0: failed to setup chip information
Such modules are previosly covered by rtl8821ce-dkms.
[Fix]
Patch set
https://lore.kernel.org/linux-wireless/20210202055012.8296-1-pks...@realtek.com/
landed in v5.12-rc1, as well as WLAN firmware updates in commit
c5e3240eff0f ("rtw88: RTL8821C: Update firmware to v24.8"), which is
already available in Hirsute version 1.195. Bluetooth firmware should
have been the latest 0x829a_7644 in both Focal/Hirsute.
[Test Case]
With patched kernel, wlan interface should be up and running:
rtw_8821ce :01:00.0: enabling device ( -> 0003)
rtw_8821ce :01:00.0: Firmware version 24.8.0, H2C version 12
rtw_8821ce :01:00.0 wlp1s0: renamed from wlan0
[Where problems could occur]
Previously this hardware piece can only be driven by external DKMS
modules, so with this driver patched, users can now use in-tree driver,
but may experience the difference between them in power consumption or
feature supportness.
[Other Info]
While Bionic/Focal LTS is still using rtl8821ce-dkms for RFE Type 2
cards, there is no plan to introduce such change to them. So they'll be
upgraded only at the next point release with kernel >= 5.11.
== original bug description ==
8821ce is being upstreamed in https://lore.kernel.org/linux-
wireless/20200603094218.19942-1-yhchu...@realtek.com/ . To backport it
to ubuntu kernel so that we may obsolete the usage of rtl8821ce-dkms
from https://bugs.launchpad.net/ubuntu/+source/rtl8821ce .
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1885862/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-signed-hwe-5.8 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Invalid Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924957] Re: AACRAID not exposing drives in Protect mode
Hi, thanks for the bug report. Can you please try in 18.04 with both kernels 4.15 and 5.4? The 4.15 series is the GA series for Ubuntu 18.04, meaning it is the kernel version available since the release of 18.04. Now, through HWE process[0] we get more recent kernels to older releases, so kernel 5.4 is available to Bionic - which is the version on Ubuntu 20.04. With that experiment, we could narrow it down to a kernel change vs. userspace. Thanks in advance, Guilherme [0] https://wiki.ubuntu.com/Kernel/LTSEnablementStack -- 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/1924957 Title: AACRAID not exposing drives in Protect mode Status in linux package in Ubuntu: Confirmed Bug description: In 18.04 LTS - Drives behind an array were exposed as /dev/sg[12345...] when expose_externals was set to -1(default) In 20.04 LTS - This is no longer happening unless you force expose_externals to 1. This is undesirable as it also exposes the disks as /dev/sd[abc] as well as /dev/sg[123] No hardware/firmware/bios changes between 18.04 and 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925369] Re: pacote linux-image-generic 4.4.0.210.216 falha ao instalar / atualizar: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-
So, it seems there was an issue installing the kernel package, right? Are you using an out-of-tree driver / DKMS? Based on the attached dmesg, seems intel_hid taints the kernel. This made me suspect you're facing an issue dkms-building some module in 4.4.0-210. Can you please try: apt-get --reinstall install linux- image-4.4.0-210-generic linux-modules-4.4.0-210-generic linux-modules- extra-4.4.0-210-generic linux-headers-4.4.0-210-generic Please provide the full output of the command execution. Thanks, Guilherme -- 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/1925369 Title: pacote linux-image-generic 4.4.0.210.216 falha ao instalar / atualizar: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in linux package in Ubuntu: Confirmed Bug description: Computador avisa constantemente que há um problema no pacote/sistema, e quando vou relatar ou amparar o erro nunca é possível. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.210.216 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: evelyn 2483 F pulseaudio Date: Wed Apr 21 12:10:01 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. HibernationDevice: RESUME=UUID=99aa7395-fd5b-45c8-8844-246bf083aade InstallationDate: Installed on 2019-04-12 (739 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-210-generic root=UUID=876349e3-7565-4791-b02a-2a8164cead91 ro alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-generic 4.4.0.210.216 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.8.0 dmi.board.name: 01PXGP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.8.0:bd12/05/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn01PXGP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925369] Re: pacote linux-image-generic 4.4.0.210.216 falha ao instalar / atualizar: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-
Pt-Br: Oi Evelyn, obrigado pelo report! A comunicação no Lauchpad usualmente é feita em inglês, podemos proceder em inglês? Hi Evelyn, thanks for the report. Can we proceed in english? -- 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/1925369 Title: pacote linux-image-generic 4.4.0.210.216 falha ao instalar / atualizar: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in linux package in Ubuntu: Confirmed Bug description: Computador avisa constantemente que há um problema no pacote/sistema, e quando vou relatar ou amparar o erro nunca é possível. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.210.216 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: evelyn 2483 F pulseaudio Date: Wed Apr 21 12:10:01 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. HibernationDevice: RESUME=UUID=99aa7395-fd5b-45c8-8844-246bf083aade InstallationDate: Installed on 2019-04-12 (739 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-210-generic root=UUID=876349e3-7565-4791-b02a-2a8164cead91 ro alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-generic 4.4.0.210.216 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.8.0 dmi.board.name: 01PXGP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.8.0:bd12/05/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn01PXGP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895132] Re: s390x broken with unknown syscall number on kernels < 5.8
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Description changed:
SRU Justification
+
+ Note: I marked this as affecting bionic as well, as discovered in bug
+ 1916485.
Impact: On kernels prior to 5.8 when a task is in traced state (due to
audit, ptrace, or seccomp) s390x and a syscall is issued that the kernel
doesn't know about s390x will not return ENOSYS in r2 but instead will
return the syscall number. This breaks userspace all over the place. The
following program compiled on s390x will output 500 instead of -ENOSYS:
root@test:~# cat test.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
static inline int dummy_inline_asm(void)
{
register long r1 asm("r1") = 500;
register long r2 asm("r2") = -1;
register long r3 asm("r3") = -1;
register long r4 asm("r4") = -1;
register long r5 asm("r5") = -1;
register long __res_r2 asm("r2");
asm volatile(
"svc 0\n\t"
: "=d"(__res_r2)
: "d"(r1), "0"(r2), "d"(r3), "d"(r4), "d"(r5)
: "memory");
return (int) __res_r2;
}
static inline int dummy_syscall(void)
{
return syscall(500, -1, -1, -1, -1);
}
int main(int argc, char *argv[])
{
printf("Uhm: %d\n", dummy_inline_asm());
printf("Uhm: %d\n", dummy_syscall());
exit(EXIT_SUCCESS);
}
This breaks LXD on s390x currently completely as well as strace.
Fix: Backport
commit cd29fa798001075a554b978df3a64e6656c25794
Author: Sven Schnelle
Date: Fri Mar 6 13:18:31 2020 +0100
s390/ptrace: return -ENOSYS when invalid syscall is supplied
The current code returns the syscall number which an invalid
syscall number is supplied and tracing is enabled. This makes
the strace testsuite fail.
Signed-off-by: Sven Schnelle
Signed-off-by: Vasily Gorbik
which got released with 5.8. The commit missed to Cc stable and although
I've asked Sven to include it in stable I'm not sure when or if it will
show up there.
Regression Potential: Limited to s390x.
Test Case: The reproducer given above needs to output -ENOSYS instead of
500.
--
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/1895132
Title:
s390x broken with unknown syscall number on kernels < 5.8
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
New
Status in linux source package in Focal:
Fix Released
Bug description:
SRU Justification
Note: I marked this as affecting bionic as well, as discovered in bug
1916485.
Impact: On kernels prior to 5.8 when a task is in traced state (due to
audit, ptrace, or seccomp) s390x and a syscall is issued that the
kernel doesn't know about s390x will not return ENOSYS in r2 but
instead will return the syscall number. This breaks userspace all over
the place. The following program compiled on s390x will output 500
instead of -ENOSYS:
root@test:~# cat test.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
static inline int dummy_inline_asm(void)
{
register long r1 asm("r1") = 500;
register long r2 asm("r2") = -1;
register long r3 asm("r3") = -1;
register long r4 asm("r4") = -1;
register long r5 asm("r5") = -1;
register long __res_r2 asm("r2");
asm volatile(
"svc 0\n\t"
: "=d"(__res_r2)
: "d"(r1), "0"(r2), "d"(r3), "d"(r4), "d"(r5)
: "memory");
return (int) __res_r2;
}
static inline int dummy_syscall(void)
{
return syscall(500, -1, -1, -1, -1);
}
int main(int argc, char *argv[])
{
printf("Uhm: %d\n", dummy_inline_asm());
printf("Uhm: %d\n", dummy_syscall());
exit(EXIT_SUCCESS);
}
This breaks LXD on s390x currently completely as well as strace.
Fix: Backport
commit cd29fa798001075a554b978df3a64e6656c25794
Author: Sven Schnelle
Date: Fri Mar 6 13:18:31 2020 +0100
s390/ptrace: return -ENOSYS when invalid syscall is supplied
The current code returns the syscall number which an invalid
syscall number is supplied and tracing is enabled. This makes
the strace testsuite fail.
Signed-off-by: Sven Schnelle
Signed-off-by: Vasily Gorbik
which got released with 5.8. The commit missed to Cc stable and
although I've asked Sven to include it in stable I'm not sure when or
if it will show up
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
Olaf - Can you paste your whole command line ? -- 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: In Progress Status in linux source package in Groovy: Fix Released Status in linux-kvm source package in Groovy: In Progress Status in linux source package in Hirsute: Fix Released Status in linux-kvm source package in Hirsute: In Progress Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923162] Re: riscv64 images fail to boot in qemu
This bug was fixed in the package u-boot - 2021.01+dfsg-3ubuntu8 --- u-boot (2021.01+dfsg-3ubuntu8) hirsute; urgency=medium * Skip processing fdtdir on qemu-riscv64_smode target, as it crashes the riscv qemu VM. LP: #1925267 LP: #1923162 -- Dimitri John Ledkov Wed, 21 Apr 2021 01:25:13 +0100 ** Changed in: u-boot (Ubuntu Hirsute) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Fix Released Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: Fix Released Status in u-boot-menu source package in Hirsute: Fix Released Bug description: When booting v5.11 based riscv unmatched image in qemu with uboot, it fails to boot. When booting v5.11 based riscv unmatched kernel+initrd directly, it boots fine. Somehow, it seems that u-boot fails to correctly load & start v5.11 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913186] Re: Backport the adaptive engine from v2.4.1 upstream
I've soak tested focal thermald 1.9.1-1ubuntu0.4 for 4.5 hours with a laptop that is cycled through CPU loading and idle states with the air vents blocked to try to trip thermal overrun. Debug mode was enabled and also it was run with valgrind to check for memory leaks. thermald was able to passively change CPU state to avoid thermal overrun. thermald had no long term memory leakage. Looks good to me. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1913186 Title: Backport the adaptive engine from v2.4.1 upstream Status in thermald package in Ubuntu: New Status in thermald source package in Focal: Fix Committed Status in thermald source package in Groovy: Fix Committed Bug description: Impact: DPTM provides an adaptive power policy that allows for improved integration between the platform and the OS. Firmware can provide a set of complex conditions to the OS, and an OS agent (in this case thermal_daemon) is responsible for evaluating them, potentially making use of information that is easily available to the OS and not the firmware. The agent evaluates each set of conditions in turn, and once the first evaluates completely it triggers a set of actions. Fix: Backport the adaptive engine (and all its dependencies) from upstream v.2.4.1 Regression potential: Both Focal and Groovy backports are substantial (Focal in particular is pretty large), so there's definitely a regression potential. On the other hand, the entire patchset is a clean backport, taking no shortcut or trying to adapt any patch, but rather picking up all the necessary dependencies to make the entire stack apply cleanly. -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] Re: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded
Wow, I did not realise apport submitted so many messages. Anyway, the system wanted a reboot for a kernel update so I proceeded to reboot after making sure I did a `sudo apt update && sudo apt upgrade` to ensure everything is up to date as of this comment. I've then went ahead to run the replace again, and the behaviour still exists. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Confirmed Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
SRU request sent reverting these commits:
https://lists.ubuntu.com/archives/kernel-team/2021-April/119419.html
** Changed in: linux (Ubuntu Groovy)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
Incomplete
Status in linux source package in Groovy:
In Progress
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 1925284] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490756/+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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490755/+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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490754/+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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490752/+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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490753/+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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490751/+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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490750/+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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490749/+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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490748/+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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490747/+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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490746/+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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490745/+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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490744/+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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490743/+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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490741/+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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490742/+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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490740/+files/AudioDevicesInUse.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/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-18 (2 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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 RfKill: Tags: hirsute Uname: Linux 5.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925284] Re: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded
apport information ** Tags added: apport-collected hirsute ** Description changed: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value increases: Data,single: Size:107.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 107.00GiB ... several minutes later as btrfs replace continues to run ... Data,single: Size:177.00GiB, Used:5.25MiB (0.00%) /dev/sdb1 177.00GiB I have also posted this on the Btrfs kernel mailing list here for more details and output from commands: https://lore.kernel.org/linux- btrfs/cafmvigfq+xotjo_578lvsvycd3sblcv_ap6a+b0u+ybapu2...@mail.gmail.com/T/#t It's speculated this could be an Ubuntu specific issue. What is certain is I've done this process three times with this array on Ubuntu 21.04 and it happens every time, so I can reproduce it 100%. I believe this is a bug with the Ubuntu kernel, but I suppose it could be related to btrfs-progs. What is certain is the btrfs replace triggers the issue. I'm happy to provide any more additional details as best I can. Thanks, -Jonah + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu65 + Architecture: amd64 + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2021-04-18 (2 days ago) + InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en_CA:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_CA.UTF-8 + SHELL=/bin/bash + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=b34e7cba-e2cd-440e-ac70-479267e84867 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RebootRequiredPkgs: + linux-image-5.11.0-16-generic + linux-base + 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 + RfKill: + + Tags: hirsute + Uname: Linux 5.11.0-14-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 06/04/2020 + dmi.bios.release: 5.14 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P3.40 + dmi.board.name: B450 Steel Legend + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd06/04/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450SteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: To Be Filled By O.E.M. + dmi.product.sku: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1925284/+attachment/5490739/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded Status in linux package in Ubuntu: Incomplete Bug description: I experience this with Ubuntu 21.04. I've not tested on older releases. I have a btrfs RAID1 array and simulated a failed disk and then replaced it with the `btrfs replace` feature part of btrfs-progs after mounting the remaining disk with the degraded,noatime mount options. For clarity: The disk that is being used in btrfs replace is sda1, sdb1 is the existing disk with the data that is mounted degraded. Unfortunately, when you begin the replacement, btrfs begins slowly allocating new empty single chunks on the disk that was mounted degraded (sdb1) as soon as the btrfs replace begins, seemingly equal to the amount of raid1 chunks that were already allocated + 1. As the replace continues, this value
[Kernel-packages] [Bug 1923162] Re: riscv64 images fail to boot in qemu
** Tags removed: block-proposed block-proposed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: New Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: New Status in u-boot-menu source package in Hirsute: Fix Released Bug description: When booting v5.11 based riscv unmatched image in qemu with uboot, it fails to boot. When booting v5.11 based riscv unmatched kernel+initrd directly, it boots fine. Somehow, it seems that u-boot fails to correctly load & start v5.11 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925290] Re: hangup01 from pty in ubuntu_ltp_stable failed on G-5.8
** Description changed:
[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
+ hangup011 TFAIL : hangup01.c:132: unexpected message 3
+ tag=hangup01 stime=1618856629 dur=1 exit=exited stat=1
--
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:
Incomplete
Status in linux source package in Groovy:
Confirmed
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 1925290] Re: hangup01 from pty in ubuntu_ltp_stable failed on G-5.8
** Description changed: - Issue found on Groovy 5.8.0-51.57 with P8 node "dryden" and ARM64 node - "helo-kernel" and AMD64 node "onibi" + [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 + + [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 -- 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: Incomplete Status in linux source package in Groovy: Confirmed 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 [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 1919177] Re: Azure: issues with accelerated networking on Hirsute
** Description changed:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
- enabled, sometimes the SSH key is not setup properly and the user cannot
- log into the VM.
+ enabled, sometimes part of the cloud-init configuration is not applied.
+
+ Especially, in those cases, the SSH key is not setup properly and the
+ user cannot log into the VM.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
- To be able to connect into the VM to debug, run:
+ To be able to connect into the VM, run:
- ```
+
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
- "publicKeys": [
- {
-"keyData": "",
-"path": "/home/ubuntu/.ssh/authorized_keys"
- }
- ],
+ "publicKeys": [
+ {
+ "keyData": "",
+ "path": "/home/ubuntu/.ssh/authorized_keys"
+ }
+ ],
```
as expected.
+
+ [workaround]
+
+ As mentioned, Azure allows the user to run command into the VM without
+ SSH connection. To do so, one can use the Azure CLI:
+
+
+ az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
+
+ This example uses "ssh-import-id" but it's also possible to just echo a
+ given public key into /home/ubuntu/.ssh/authorized_keys
+
+ NOTE: this will only solves the SSH issue, I do not know if this bug
+ affects other things. If so the user would have to apply those things
+ manually.
** Description changed:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not applied.
- Especially, in those cases, the SSH key is not setup properly and the
- user cannot log into the VM.
+ Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM, run:
-
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
[workaround]
As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:
-
- az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
+ az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
+ RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
This example uses "ssh-import-id" but it's also possible to just echo a
given public key into /home/ubuntu/.ssh/authorized_keys
NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.
--
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/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
New
Status in linux-azure package in Ubuntu:
New
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not
applied.
Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be
[Kernel-packages] [Bug 1925369] 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/1925369 Title: pacote linux-image-generic 4.4.0.210.216 falha ao instalar / atualizar: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in linux package in Ubuntu: Confirmed Bug description: Computador avisa constantemente que há um problema no pacote/sistema, e quando vou relatar ou amparar o erro nunca é possível. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.210.216 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: evelyn 2483 F pulseaudio Date: Wed Apr 21 12:10:01 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. HibernationDevice: RESUME=UUID=99aa7395-fd5b-45c8-8844-246bf083aade InstallationDate: Installed on 2019-04-12 (739 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-210-generic root=UUID=876349e3-7565-4791-b02a-2a8164cead91 ro alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-generic 4.4.0.210.216 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.8.0 dmi.board.name: 01PXGP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.8.0:bd12/05/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn01PXGP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Well for memory hotplug the -m paramter is important. Here is how i started the VM: qemu -name myfancyvm -m 1024,slots=255,maxmem=256G... -- 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: In Progress Status in linux source package in Groovy: Fix Released Status in linux-kvm source package in Groovy: In Progress Status in linux source package in Hirsute: Fix Released Status in linux-kvm source package in Hirsute: In Progress Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
The issue is fixed by reverting the following two patches: commit b7bfa1af145a6aa3868894a4be82f7b2034c564a Author: Linus Torvalds Date: Tue Jan 19 10:49:19 2021 -0800 tty: implement read_iter BugLink: https://bugs.launchpad.net/bugs/1921960 [ Upstream commit dd78b0c483e33225e0e0782b0ed887129b00f956 ] commit 4b71b60ef2cb9f930b8056049a1d8de170be42bc Author: Linus Torvalds Date: Mon Jan 18 13:31:30 2021 -0800 tty: convert tty_ldisc_ops 'read()' function to take a kernel pointer BugLink: https://bugs.launchpad.net/bugs/1921960 [ Upstream commit 3b830a9c34d5897be07176ce4e6f2d75e2c8cfd7 ] -- 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: Incomplete Status in linux source package in Groovy: Confirmed Bug 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 1922403] Re: hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI
The daily iso no longer has this issue. -- 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/1922403 Title: hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI 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: Invalid Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: I've tried to boot the Ubuntu 21.04 desktop beta Live CD (AMD64; http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso) inside a Hyper-V Gen 2 Virtual Machine with UEFI enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925369] [NEW] pacote linux-image-generic 4.4.0.210.216 falha ao instalar / atualizar: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configur
Public bug reported: Computador avisa constantemente que há um problema no pacote/sistema, e quando vou relatar ou amparar o erro nunca é possível. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.210.216 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: evelyn 2483 F pulseaudio Date: Wed Apr 21 12:10:01 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. HibernationDevice: RESUME=UUID=99aa7395-fd5b-45c8-8844-246bf083aade InstallationDate: Installed on 2019-04-12 (739 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-210-generic root=UUID=876349e3-7565-4791-b02a-2a8164cead91 ro alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-generic 4.4.0.210.216 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.8.0 dmi.board.name: 01PXGP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.8.0:bd12/05/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn01PXGP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial ** Summary changed: - package linux-image-generic 4.4.0.210.216 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. + pacote linux-image-generic 4.4.0.210.216 falha ao instalar / atualizar: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. -- 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/1925369 Title: pacote linux-image-generic 4.4.0.210.216 falha ao instalar / atualizar: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in linux package in Ubuntu: New Bug description: Computador avisa constantemente que há um problema no pacote/sistema, e quando vou relatar ou amparar o erro nunca é possível. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.210.216 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: evelyn 2483 F pulseaudio Date: Wed Apr 21 12:10:01 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. HibernationDevice: RESUME=UUID=99aa7395-fd5b-45c8-8844-246bf083aade InstallationDate: Installed on 2019-04-12 (739 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-210-generic root=UUID=876349e3-7565-4791-b02a-2a8164cead91 ro alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-generic 4.4.0.210.216 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.8.0 dmi.board.name: 01PXGP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc.
[Kernel-packages] [Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow
Another customer has provided positive feedback that it fixes the issue on Focal: 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:39:42 UTC 2021 -- 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 Committed Status in linux source package in Groovy: Fix Committed 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 1925261] Re: memory leak on AWS kernels when using docker
Kleber, I am not sure exactly which commit fixes the issue we are experiencing. I will put some time into bisecting the commits introduced in v5.9-rc4 and building/testing kernels with that code to see if I can narrow down the exact commit that introduced the fix. Thanks, Paul -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1925261 Title: memory leak on AWS kernels when using docker Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Focal: New Bug description: Ever since the "ubuntu-bionic-18.04-amd64-server-20200729" EC2 Ubuntu AMI was released which has the "5.3.0-1032-aws" kernel we have been hitting a 100% repro memory leak that causes our app that is running under docker to be OOM killed. The scenario is that we have an app running in a docker container and it occasionally catches a crash happening within itself and when that happens it creates another process which triggers a gdb dump of that parent app. Normally this works fine but under these specific kernels it causes the memory usage to grow and grow until it hits the maximum allowed memory for the container at which point the container is killed. I have tested using several of the latest available Ubuntu AMIs including the latest "ubuntu-bionic-18.04-amd64-server-20210415" which has the "5.4.0-1045-aws" kernel and the bug still exists. I also tested a bunch of the mainline kernels and found the fix was introduced for this memory leak in the v5.9-rc4 kernel (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9-rc4/CHANGES). Do you all have any idea if or when that set of changes will be backported into a supported kernel for Ubuntu 18.04 or 20.04? Release we are running: root@:~# lsb_release -rd Description: Ubuntu 18.04.5 LTS Release: 18.04 Docker / containerd.io versions: - containerd.io: 1.4.4-1 - docker-ce: 5:20.10.5~3-0~ubuntu-bionic Latest supported kernel I tried which still sees the memory leak: root@hostname:~# apt-cache policy linux-aws linux-aws: Installed: 5.4.0.1045.27 Candidate: 5.4.0.1045.27 Version table: *** 5.4.0.1045.27 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1007.7 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Thanks, Paul To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1925261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute
The issue probably* started between these two serials: 20210215 and
20210304.
*I say "probably" because while I'm sure I can reproduce the issue with
20210304, the fact I didn't manage to reproduce it with 20210215 (in ~15
tries) doesn't **absolutely prove** that the issue wasn't there.
--
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/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
New
Status in linux-azure package in Ubuntu:
New
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes the SSH key is not setup properly and the user
cannot log into the VM.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM to debug, run:
```
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] 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 1925055 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925055] Re: Boot stuck in UEFI after enrolling keys for drivers
> But after I install some drivers (NVidia you appear to have 2 separate graphics cards: [4.893710] nvidia :30:00.0: enabling device (0006 -> 0007) [6.034799] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device my guess would be you're having problems with the kernel choosing the correct graphics device to use, and/or some problem with the driver not correctly updating the screen. I also noticed this: [5.535665] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 however you said disabling secure boot doesn't help, so that's probably not related. Have you tried uninstalling the nvidia driver package to see if that is what's causing the problem? > Return to the original console by Alt+Fn+F1 Just a note, since you're booting with vt.handoff=7 the active VT should be 7, i.e. Ctrl+Alt+F7 You might also want to try booting with all the possibly relevant params removed, i.e. remove 'quiet splash vt.handoff=7' You could also try adding 'nomodeset' to the kernel boot params to see if that helps. In any case, this certainly looks like a kernel issue, not systemd. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925344] Re: Session not started after reboot (black screen) - requires switching tty back and forth
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1925344 ** Tags added: iso-testing -- 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/1925344 Title: Session not started after reboot (black screen) - requires switching tty back and forth Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in nvidia-prime package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: After installation, the first boot works as expected - the system boots into a graphical shell login screen. However all subsequent reboots end up with a black screen with a blinking cursor in the top- left corner of the screen. To get to the login screen, one has to switch to a different tty (like tty2 with ctrl+alt+f2) and then to tty1. Running `prime-select query` shows `nvidia`. Interesting enough, when I change the nvidia-prime settings at least once, like to on-demand via `prime-select on-demand` - then everything starts working as expected. Even when I switch back to `nvidia`. Not sure which package I should fill this under. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xserver-xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.67 Thu Mar 11 00:11:45 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 21 15:20:15 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:09e1] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:09e1] InstallationDate: Installed on 2021-04-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. G3 3500 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=5b38428b-60e8-4741-8b7f-0e60094a80f7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 06ND9G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd12/04/2020:br1.7:svnDellInc.:pnG33500:pvr:rvnDellInc.:rn06ND9G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3500 dmi.product.sku: 09E1 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1925344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925344] [NEW] Session not started after reboot (black screen) - requires switching tty back and forth
Public bug reported: After installation, the first boot works as expected - the system boots into a graphical shell login screen. However all subsequent reboots end up with a black screen with a blinking cursor in the top-left corner of the screen. To get to the login screen, one has to switch to a different tty (like tty2 with ctrl+alt+f2) and then to tty1. Running `prime-select query` shows `nvidia`. Interesting enough, when I change the nvidia-prime settings at least once, like to on-demand via `prime-select on-demand` - then everything starts working as expected. Even when I switch back to `nvidia`. Not sure which package I should fill this under. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xserver-xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.67 Thu Mar 11 00:11:45 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 21 15:20:15 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:09e1] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:09e1] InstallationDate: Installed on 2021-04-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. G3 3500 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=5b38428b-60e8-4741-8b7f-0e60094a80f7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 06ND9G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd12/04/2020:br1.7:svnDellInc.:pnG33500:pvr:rvnDellInc.:rn06ND9G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3500 dmi.product.sku: 09E1 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu ** Also affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New -- 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/1925344 Title: Session not started after reboot (black screen) - requires switching tty back and forth Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in nvidia-prime package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: After installation, the first boot works as expected - the system boots into a graphical shell login screen. However all subsequent reboots end up with a black screen with a blinking cursor in the top- left corner of the screen. To get to the login screen, one has to switch to a different tty (like tty2 with ctrl+alt+f2) and then to
[Kernel-packages] [Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow
Thank you Alex, adjusting the tags accordingly ... ** Tags removed: verification-needed-focal verification-needed-groovy ** Tags added: verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 Committed Status in linux source package in Groovy: Fix Committed 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 1923162] Re: riscv64 images fail to boot in qemu
** Merge proposal linked: https://code.launchpad.net/~xnox/ubuntu/+source/u-boot/+git/u-boot/+merge/401545 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: New Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: New Status in u-boot-menu source package in Hirsute: Fix Released Bug description: When booting v5.11 based riscv unmatched image in qemu with uboot, it fails to boot. When booting v5.11 based riscv unmatched kernel+initrd directly, it boots fine. Somehow, it seems that u-boot fails to correctly load & start v5.11 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921104] Comment bridged from LTC Bugzilla
--- Comment From alexs...@de.ibm.com 2021-04-21 08:50 EDT--- I verified the fix successfully on 5.4.0-73. -- 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 Committed Status in linux source package in Groovy: Fix Committed 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 1921960] Re: Groovy update: upstream stable patchset 2021-03-30
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Groovy) Status: New => In Progress -- 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 Committed Status in linux-gcp source package in Groovy: In Progress 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 device reference before return Bluetooth: Put HCI device if inquiry procedure interrupts memory: ti-aemif: Drop child node when jumping out loop ARM: dts: Configure missing thermal interrupt for 4430 usb: dwc2: Do not update data length if it is 0 on inbound transfers usb: dwc2: Abort transaction after errors with unknown reason usb: dwc2: Make "trimming xfer length" a debug message staging: rtl8723bs: wifi_regd.c: Fix incorrect number of regulatory rules ARM: dts: armada388-helios4: assign pinctrl to LEDs ARM: dts: armada388-helios4: assign pinctrl to each fan arm64: dts:
[Kernel-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
** Description changed: + SRU Justification + + [Impact] + + Hot removal of disks under kvm on s390 does not result in the kernel + removing the block device, which can lead to hung tasks and other + issues. + + [Test Plan] + + See steps to reproduce the bug in the original description below. To + test, execute these steps and confirm that the block device gets removed + as expected. + + [Where problems could occur] + + The fix is a revert of the changes which introduced this regression. The + original commit was a removal of supposedly unused code, but it seems a + mistake was made in the logic around unregistering of disks. Reverting + the changes could have potential to introduce bugs related to other virt + devices, especially if it interacts badly with subsequent driver + changes. However, the patch reverted cleanly, and reverting restores the + code to the state which has been working well in previous kernels and + seems like the lowest risk option until a proper fix is available + upstream. + + --- + Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc - From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! - --- + --- 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-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: - + Lspci-vt: -[:00]- 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: Package: udev PackageArchitecture: s390x PciMultimedia: - + ProcFB: - + ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: - linux-restricted-modules-5.11.0-14-generic N/A - linux-backports-modules-5.11.0-14-generic N/A - linux-firmware N/A + linux-restricted-modules-5.11.0-14-generic N/A + linux-backports-modules-5.11.0-14-generic N/A + linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: -- 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/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged
[Kernel-packages] [Bug 1913186] Re: Backport the adaptive engine from v2.4.1 upstream
I've soak tested groovy thermald 2.3-4ubuntu1 for 2.5 hours with a laptop that is cycled through CPU loading and idle states with the air vents blocked to try to trip thermal overrun. Debug mode was enabled and also it was run with valgrind to check for memory leaks. thermald was able to passively change CPU state to avoid thermal overrun. thermald had no long term memory leakage. Looks good to me. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1913186 Title: Backport the adaptive engine from v2.4.1 upstream Status in thermald package in Ubuntu: New Status in thermald source package in Focal: Fix Committed Status in thermald source package in Groovy: Fix Committed Bug description: Impact: DPTM provides an adaptive power policy that allows for improved integration between the platform and the OS. Firmware can provide a set of complex conditions to the OS, and an OS agent (in this case thermal_daemon) is responsible for evaluating them, potentially making use of information that is easily available to the OS and not the firmware. The agent evaluates each set of conditions in turn, and once the first evaluates completely it triggers a set of actions. Fix: Backport the adaptive engine (and all its dependencies) from upstream v.2.4.1 Regression potential: Both Focal and Groovy backports are substantial (Focal in particular is pretty large), so there's definitely a regression potential. On the other hand, the entire patchset is a clean backport, taking no shortcut or trying to adapt any patch, but rather picking up all the necessary dependencies to make the entire stack apply cleanly. -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
The condition for css_sch_device_unregister(sch) also caught my eye, calling it unconditionally is probably closer to right because it was called in the !cdev case before, and in the attached patch it would no longer be called in this case. However I think in the short term the revert is the safest option, since the code will match what we already know was working in the groovy kernel. Once a fix is committed upstream, we can trade out the revert for that 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/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Status in linux source package in Hirsute: Triaged Status in systemd source package in Hirsute: Invalid Status in udev source package in Hirsute: Invalid Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- 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-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- 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: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925318] Re: bluetooth just turning off and on and also disconnecting
** Package changed: ubuntu => bluez (Ubuntu) -- 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/1925318 Title: bluetooth just turning off and on and also disconnecting Status in bluez package in Ubuntu: New Bug description: bluetooth just turning off and on and also disconnecting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 21 14:53:05 2021 InstallationDate: Installed on 2020-12-22 (119 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 3521 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=e7fbb5e3-519a-41d2-94fd-6b2a0305a65d ro text SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0JYTX5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd10/25/2013:efr1.1:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn0JYTX5:rvrA00:cvnDellInc.:ct8:cvrA12: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3521 dmi.product.sku: Inspiron 3521 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. hciconfig: rfkill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1925318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925318] [NEW] bluetooth just turning off and on and also disconnecting
You have been subscribed to a public bug: bluetooth just turning off and on and also disconnecting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 21 14:53:05 2021 InstallationDate: Installed on 2020-12-22 (119 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 3521 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=e7fbb5e3-519a-41d2-94fd-6b2a0305a65d ro text SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0JYTX5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd10/25/2013:efr1.1:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn0JYTX5:rvrA00:cvnDellInc.:ct8:cvrA12: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3521 dmi.product.sku: Inspiron 3521 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. hciconfig: rfkill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- bluetooth just turning off and on and also disconnecting https://bugs.launchpad.net/bugs/1925318 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez 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 1919177] Re: Azure: issues with accelerated networking on Hirsute
Hi,
Ok thanks. I am now trying to find at which time the issue was first
introduced. So far I tested an image from 20201222 and confirm that I
cannot reproduce the issue with this image.
Then by modifying the image (always before first boot) I was able to find that:
- upgrading cloud-init from 20.4-0ubuntu1 to 21.1-19-gbad84ad4-0ubuntu2 I
still cannot reproduce the issue
- upgrading systemd from 246.6-5ubuntu1 to 247.3-1ubuntu4 I couldn't reproduce
the issue
- upgrading BOTH cloud-init and systemd at the same time I was able to
reproduce the issue
I am now trying to test newer images to understand what is the first
image that introduces the issue.
--
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/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
New
Status in linux-azure package in Ubuntu:
New
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes the SSH key is not setup properly and the user
cannot log into the VM.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM to debug, run:
```
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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
I used the same steps to verify it and can conconfirm it's succeeded
fio --name=test1 --filename /dev/bcache0 --direct 1 --rw=randrw
--bs=32k,4k --ioengine=libaio --iodepth=1
Then I monitoring the cache_available_percent and writeback rate.
I no longer see the cache_available_percent dropped to 30 and writeback rate
stucked at 4k.
I can see the rate got accelerated while the dirty buckets hit the
writeback_rate_*_fp_term, which is expected
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix 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 buckets ratio didn’t turn around during the first stage,
it comes to the mid stage, then it is necessary for mid stage
to be more aggressive than low stage, so the initial rate is chosen
to be 10 times more than the low stage, which means 1700 as the initial
rate if the fragment is 6. This is a normal rate
we usually see for a normal workload when writeback happens
because of writeback_percent.
C. If the dirty buckets ratio didn't turn around during the low and mid
[Kernel-packages] [Bug 1925290] Re: hangup01 from pty in ubuntu_ltp_stable failed on G-5.8
** Changed in: linux (Ubuntu Groovy) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Incomplete Status in linux source package in Groovy: Confirmed Bug 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 1925290] 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 1925290 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 ** Changed in: linux (Ubuntu Groovy) 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/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: Incomplete Status in linux source package in Groovy: Incomplete Bug 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 1925290] Re: hangup01 from pty in ubuntu_ltp_stable failed on G-5.8
Found on AMD64 node "onibi" as well, bug description updated. ** Summary changed: - hangup01 from pty in ubuntu_ltp_stable failed on G-5.8 P8/arm64 + hangup01 from pty in ubuntu_ltp_stable failed on G-5.8 ** Description changed: Issue found on Groovy 5.8.0-51.57 with P8 node "dryden" and ARM64 node - "helo-kernel" + "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 + hangup011 TFAIL : hangup01.c:132: unexpected message 3 + tag=hangup01 stime=1618856629 dur=1 exit=exited stat=1 ** Tags added: amd64 -- 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: New Status in linux source package in Groovy: New Bug 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 1925290] Re: hangup01 from pty in ubuntu_ltp_stable failed on G-5.8 P8/arm64
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: New Status in linux source package in Groovy: New Bug 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 1925261] Re: memory leak on AWS kernels when using docker
Thank you Paul for the bug report. Just as an additional information, the 5.3.0 series kernels are not supported anymore. If you want to continue using Ubuntu 18.04 with the additional security and bug fixes you will need to eventually upgrade to a 5.4.0-based AWS kernel. Are you able to point at which commit exactly from v5.9-rc4 fixes the memory leak you are experiencing? Most of the commits mentioning "leak" in their titles has already been applied to the 5.4 kernels, so if you can still reproduce the issue with the latest 5.4 AWS kernel we are probably missing another fix. Thank you. ** Also affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1925261 Title: memory leak on AWS kernels when using docker Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Focal: New Bug description: Ever since the "ubuntu-bionic-18.04-amd64-server-20200729" EC2 Ubuntu AMI was released which has the "5.3.0-1032-aws" kernel we have been hitting a 100% repro memory leak that causes our app that is running under docker to be OOM killed. The scenario is that we have an app running in a docker container and it occasionally catches a crash happening within itself and when that happens it creates another process which triggers a gdb dump of that parent app. Normally this works fine but under these specific kernels it causes the memory usage to grow and grow until it hits the maximum allowed memory for the container at which point the container is killed. I have tested using several of the latest available Ubuntu AMIs including the latest "ubuntu-bionic-18.04-amd64-server-20210415" which has the "5.4.0-1045-aws" kernel and the bug still exists. I also tested a bunch of the mainline kernels and found the fix was introduced for this memory leak in the v5.9-rc4 kernel (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9-rc4/CHANGES). Do you all have any idea if or when that set of changes will be backported into a supported kernel for Ubuntu 18.04 or 20.04? Release we are running: root@:~# lsb_release -rd Description: Ubuntu 18.04.5 LTS Release: 18.04 Docker / containerd.io versions: - containerd.io: 1.4.4-1 - docker-ce: 5:20.10.5~3-0~ubuntu-bionic Latest supported kernel I tried which still sees the memory leak: root@hostname:~# apt-cache policy linux-aws linux-aws: Installed: 5.4.0.1045.27 Candidate: 5.4.0.1045.27 Version table: *** 5.4.0.1045.27 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1007.7 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Thanks, Paul To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1925261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924624] Re: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable
Using 5.8.0-51 has fixed the problem for me. My PC : - Dell Inc. Inspiron 3847/088DT1, BIOS A11 05/07/2019 - EFI v2.31 by American Megatrends - Secure boot disable - CPU : Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz - GPU : Intel HD Graphics 4400 - A single screen connected via HDMI. Resolution: 1920x1080 - RAM : 16 GB DDR3 My Ubuntu 20.10 : - X11 - GNOME 3.38.2 - French language -- 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/1924624 Title: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-5.8 package in Ubuntu: Confirmed Bug description: After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was suddenly extremely glitchy. Icons from the desktop flash through the browser, windows top bar gets distorted, all sort of glitches appear, parts of characters are missing in terminal, scrolling is inconsistent and the whole desktop becomes unusable. Under wayland the graphics are a bit more stable, but lots of glitches appear anyway, video reproduction in browser is stuttering and wobbly. Booting with previous kernel 5.8.0-48 seems to fix the issues. 5.8.0-50 is broken as well. this is the result of 'sudo lshw -c video' on my hp Elitebook 8470: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:d400-d43f memory:c000-cfff ioport:4000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
