[Kernel-packages] [Bug 1928838] Re: Fix kernel panic on Intel Bluetooth
This was reverted in stable kernel v5.10.x, v5.13.x per https://lore.kernel.org/linux-bluetooth/8735ryk0o7@baylibre.com/. Further tracking in bug 1948898. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928838 Title: Fix kernel panic on Intel Bluetooth Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Bug description: [Impact] Kernel panic when doing rfkill block on Intel Bluetooth controller. [Fix] Ensure everything is stopped before calling the shutdown callback. [Test] Keep pressing the airplane mode button. High chance that a kernel splat is shown and Bluetooth becomes unusable. [Where problems could occur] The shutdown callback is used by other Bluetooth controller as well. Logically, the patch is doing the correct thing by queiscing the device before calling shutodwn. However, other Bluetooth drivers may depend it to behave correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1928838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947818] Re: The fans are constantly whirring on ThinkPad P14S Gen 2
** Changed in: linux (Ubuntu) Assignee: (unassigned) => AaronMa (mapengyu) ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947818 Title: The fans are constantly whirring on ThinkPad P14S Gen 2 Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Bug description: The fans are constantly whirring despite next to no CPU usage, it's quite loud, on versions 20.04, 21.04 and 21.10 it has the same issues. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1947818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948898] [NEW] Bluetooth HCI reset fail during airplane mode switch stress tests
Public bug reported:
Bug 1928838 fixed possible kernel panic when doing rfkill block on Intel
Bluetooth controller. The fix was also upstreamed in v5.14-rc1 as commit
0ea9fd001a14e ("Bluetooth: Shutdown controller after workqueues are
flushed or cancelled") and was backported to v5.10.51, v5.12.18, and
v5.13.3. However, as indicated in https://lore.kernel.org/linux-
bluetooth/8735ryk0o7@baylibre.com/ , it caused a regression to
mtkbtsdio and was then fixed in upstream commit 0ea53674d07f ("
Bluetooth: Move shutdown callback before flushing tx and rx queue")
since v5.15-rc1 and has been backported to v5.14.3. Current statuses:
* v5.10.x:
* 0ea9fd001a14e: backported(v5.10.51), reverted(v5.10.57)
* 0ea53674d07f: backported(v5.10.65), reverted(v5.10.66)
* v5.11.x: N/A
* v5.12.x:
* 0ea9fd001a14e: backported(v5.12.18)
* v5.13.x:
* 0ea9fd001a14e: backported(v5.13.3), reverted(v5.13.9)
* 0ea53674d07f: backported(v5.13.17), reverted(v5.13.18)
* v5.14.x:
* 0ea9fd001a14e: committed(v5.14-rc1)
* 0ea53674d07f: backported(v5.14.3)
* v5.15.x:
* 0ea53674d07f: committed(v5.15-rc1)
As a result, this affects 5.10/11/13 kernels.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: hwe-bluetooth ihv-intel oem-priority originate-from-1940428 somerville
** Tags added: oem-priority originate-from-1940428 somerville
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1948898
Title:
Bluetooth HCI reset fail during airplane mode switch stress tests
Status in HWE Next:
New
Status in linux package in Ubuntu:
New
Bug description:
Bug 1928838 fixed possible kernel panic when doing rfkill block on
Intel Bluetooth controller. The fix was also upstreamed in v5.14-rc1
as commit 0ea9fd001a14e ("Bluetooth: Shutdown controller after
workqueues are flushed or cancelled") and was backported to v5.10.51,
v5.12.18, and v5.13.3. However, as indicated in
https://lore.kernel.org/linux-bluetooth/8735ryk0o7@baylibre.com/ ,
it caused a regression to mtkbtsdio and was then fixed in upstream
commit 0ea53674d07f (" Bluetooth: Move shutdown callback before
flushing tx and rx queue") since v5.15-rc1 and has been backported to
v5.14.3. Current statuses:
* v5.10.x:
* 0ea9fd001a14e: backported(v5.10.51), reverted(v5.10.57)
* 0ea53674d07f: backported(v5.10.65), reverted(v5.10.66)
* v5.11.x: N/A
* v5.12.x:
* 0ea9fd001a14e: backported(v5.12.18)
* v5.13.x:
* 0ea9fd001a14e: backported(v5.13.3), reverted(v5.13.9)
* 0ea53674d07f: backported(v5.13.17), reverted(v5.13.18)
* v5.14.x:
* 0ea9fd001a14e: committed(v5.14-rc1)
* 0ea53674d07f: backported(v5.14.3)
* v5.15.x:
* 0ea53674d07f: committed(v5.15-rc1)
As a result, this affects 5.10/11/13 kernels.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1948898/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947818] Re: The fans are constantly whirring on ThinkPad P14S Gen 2
** Tags added: oem-priority originate-from-1948896 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947818 Title: The fans are constantly whirring on ThinkPad P14S Gen 2 Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: The fans are constantly whirring despite next to no CPU usage, it's quite loud, on versions 20.04, 21.04 and 21.10 it has the same issues. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1947818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
I had the issue again. so my previous change didn't work. I have changed DefaultTimeoutStopSec=90s timeout to 40s. I tried turning off wifi byt rfkill block all from terminal prior to shutdown, that just ended up in black screen as usual but this time wifi was off, but laptop still on. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919266] Re: kubuntu hirsute daily QA-test install & no background at first login
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1919266 Title: kubuntu hirsute daily QA-test install & no background at first login Status in linux package in Ubuntu: Expired Bug description: This issue is minor. QA-test install on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) (testcase: manual install, equivalent of install alongside) ** description & actual results On first login, there is NO WALLPAPER background. ** expected results I liked the wallpaper I saw behind `ubiquity` , and expected to see that on login (or another wallpaper). ** further notes I logged out, logged in again & this time I had wallpaper. (the wallpaper I saw & loved during install). Maybe this was a one-off fluke, but reporting... Minor issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: kubuntu-settings-desktop 1:21.04.4build1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Mar 16 12:50:44 2021 InstallationDate: Installed on 2021-03-16 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210315) PackageArchitecture: all SourcePackage: kubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942784] Re: makedumpfile falls back to cp on focal with 5.11 kernel
** No longer affects: makedumpfile (Ubuntu Hirsute)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1942784
Title:
makedumpfile falls back to cp on focal with 5.11 kernel
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Focal:
Fix Committed
Bug description:
[IMPACT]
When running Focal with the hwe 5.11 kernel makedumpfile is not working as it
should.
Instead of compressing the dump makedumpfile falls back to cp.
This can create problems on systems with very large RAM and result into
exhausting all storage on the host.
[FIX]
This can be resolved with upstream commit f1197543d1c4 ([PATCH] Retrieve
MAX_PHYSMEM_BITS from vmcoreinfo).
The reason for falling back to cp is that without this patch makedumpfile
calculates wrongly the memory layout.
This happens after the kernel commit 1d50e5d0c505 ("crash_core, vmcoreinfo:
Append 'MAX_PHYSMEM_BITS'to vmcoreinfo").
With this commit applied, reading MAX_PHYSMEM_BITS from vmcoreinfo instead of
inferring lead to correctly detecting the memory layout and creating the dump
file properly.
[TEST CASE]
For testing a machine running focal with the 5.11 kernel is required.
Then trigger a crash.
On the console we can see that makedumpfile fails and `falls back to cp`.
In /var/crash we can see that no dmesg file is created and instead of the
dump file
the uncompressed vmcoreinfo is created.
[WHERE PROBLEMS COULD OCCUR]
Any regression potential would involve the crash dump not being
created after a crash in case kdump is configured.
[OTHER]
Only Focal with 5.11 kernel is affected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946828] Re: ntfsresize hang and call traces in syslog
Hi Dan, In this case, does it able to be reproduced if you resize it using ntfresize in live session (impish)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946828 Title: ntfsresize hang and call traces in syslog Status in linux package in Ubuntu: Confirmed Status in ntfs-3g package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Bug description: Attempting to boot the impish final iso on my kvm VM setup with a windows 10 install on the virtual disk. The install process hangs at the "updates and other software" screen, apparently on a ntfsresize call. Mind you, this is before I have chosen disks to partition - I'm at the step where I can choose a Normal or Minimal installation. While this is not a 100% reproduction rate issue, the rate seems high - above 50% I would guess. If I try to quickly click thru the installer on boot it might be a little more likely. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-19-generic 5.13.0-19.19 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4609 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 13 02:40:56 2021 IwConfig: lono wireless extensions. enp1s0no wireless extensions. LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-5.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.2:sku:cvnQEMU:ct1:cvrpc-q35-5.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-5.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] *** this issue happen with secure boot on and issue gone when secure boot is off*** After the BIOS loading screen, a yellow screen pops up in an instant (< 1 second) and then disappears. Attached a demo video. [Fix] do what intel_color_commit() does to make sure the bottom color state matches whatever out hardware readout produced. Ref. https://patchwork.freedesktop.org/patch/456170/?series=95171=1 [Test] 1. Power on the system 2. Check if any unusual screen shows before and after the system loading screen. 3. No unusual screen shows before and after the system loading screen [Regression Potential] Medium, maintainer still not totally sure what should do about color management features here in general. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945932/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896420] Re: seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4
** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Luke Nowakowski-Krijger (lukenow) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896420 Title: seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: [Impact] Test fails to build in selftests/seccomp/seccomp_bpf.c with 'error: storage size of ‘md’ isn’t known' due to the type struct seccomp_metadata not being defined for B/5.4 kernels. [Test case] Test successfully builds and test cases pass both on Bionic/5.4 and on Focal [Fixes] Unconditionally define struct seccomp_metadata. Remove linux/ptrace.h where a definition of seccomp_metadata is already being defined in Focal. [Potential regression] There could be future build failures if glibc headers get updated to include definitions of struct seccomp_metadata or if linux/ptrace.h gets updated to include needed definitions. --- Issue found on 5.4.0-48.52~18.04.1 Test build failed with: gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf seccomp_bpf.c: In function ‘get_metadata’: seccomp_bpf.c:3028:26: error: storage size of ‘md’ isn’t known struct seccomp_metadata md; ^~ seccomp_bpf.c:3028:26: warning: unused variable ‘md’ [-Wunused-variable] Makefile:12: recipe for target 'seccomp_bpf' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948813] Re: cant connect to second monitor
Thanks for the bug report. The problem appears to be that the nvidia-470 kernel driver loaded and then quickly unloaded two seconds later. I don't know why that would happen... Maybe look in the 'Additional Drivers' app and uninstall the 470 driver, try 460 or 465 instead? ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-470 (Ubuntu) ** Summary changed: - cant connect to second monitor + Nvidia-470 kernel driver loads then unloads during boot on GTX 1050 Mobile. No driver loaded in the end. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1948813 Title: Nvidia-470 kernel driver loads then unloads during boot on GTX 1050 Mobile. No driver loaded in the end. Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: I lost projecting to my second monitor while updating in ubuntu 20 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 07:55:42 2021 DistUpgraded: 2021-10-15 08:30:35,667 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.4.0-89-generic, x86_64: installed nvidia, 470.74, 5.4.0-89-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-88-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-89-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1264] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev ff) (prog-if ff) InstallationDate: Installed on 2021-09-21 (34 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=c4de9279-4774-410d-be28-7e7083e0c939 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-15 (10 days ago) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1948813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948813] [NEW] cant connect to second monitor
You have been subscribed to a public bug: I lost projecting to my second monitor while updating in ubuntu 20 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 07:55:42 2021 DistUpgraded: 2021-10-15 08:30:35,667 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.4.0-89-generic, x86_64: installed nvidia, 470.74, 5.4.0-89-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-88-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-89-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1264] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev ff) (prog-if ff) InstallationDate: Installed on 2021-09-21 (34 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=c4de9279-4774-410d-be28-7e7083e0c939 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-15 (10 days ago) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- cant connect to second monitor https://bugs.launchpad.net/bugs/1948813 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 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 1947859] Re: linux-azure: Updata MANA to 5.15-rc6
This bug is awaiting verification that the linux-azure/5.11.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- 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/1947859 Title: linux-azure: Updata MANA to 5.15-rc6 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Hirsute: Fix Committed Status in linux-azure source package in Impish: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested the addition of MANA EQ-sharing patch set which is essentially everything up through v5.15-rc6. 3 more patches from Haiyang regarding EQ-sharing for Microsoft Azure Network Adapter (MANA). This saves MSI-X interrupts and allows the host to offer more virtual ports (network interfaces) to the VM. With the patches, the MANA driver supports up to 256 virtual ports per VF (it was 16/VF), and support up to 64 queues per vPort (it was 16). [Test Case] Microsoft to test and verify. [Where things might go wrong] More virtual ports may cause issues in older kernels. [Other Info] SF: #00321275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1947859/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
This bug is awaiting verification that the linux-kvm/4.15.0-1102.104 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Bug description: [ Impact ] The bionic 4.15 kernels are failing to boot on r5.metal instances on AWS. The default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-aws(4.15.0-1113-aws) or bionic/linux (4.15.0-160.168) the machine fails to boot the 4.15 kernel. This problem only appears on metal instances, which uses NVME instead of XVDA devices. [ Fix ] It was discovered that after reverting the following two commits from upstream stable the 4.15 kernels can be booted again on the affected AWS metal instance: PCI/MSI: Enforce that MSI-X table entry is masked for update PCI/MSI: Enforce MSI[X] entry updates to be visible [ Test Case ] Deploy a r5.metal instance on AWS with a bionic image, which should boot initially with bionic/linux-aws-5.4. Install bionic/linux or bionic/linux-aws (4.15 based) and reboot the system. [ Where problems could occur ] These two commits are part of a larger patchset fixing PCI/MSI issues which were backported to some upstream stable releases. By reverting only part of the set we might end up with MSI issues that were not present before the whole set was applied. Regression potential can be minimized by testing the kernels with these two reverted patches on all the platforms available. [ Original Description ] When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel- team/2021-September/123963.html With that being said, after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' from mount options and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot after installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
I've been looking for possible fixes regarding the terms "NMI watchdog", "soft lockup", and "hard lockup", and nothing has worked. Does anybody reading this have any ideas? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939966/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1946828] Re: ntfsresize hang and call traces in syslog
This bug is probably a duplicate of bug #1945011 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946828 Title: ntfsresize hang and call traces in syslog Status in linux package in Ubuntu: Confirmed Status in ntfs-3g package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Bug description: Attempting to boot the impish final iso on my kvm VM setup with a windows 10 install on the virtual disk. The install process hangs at the "updates and other software" screen, apparently on a ntfsresize call. Mind you, this is before I have chosen disks to partition - I'm at the step where I can choose a Normal or Minimal installation. While this is not a 100% reproduction rate issue, the rate seems high - above 50% I would guess. If I try to quickly click thru the installer on boot it might be a little more likely. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-19-generic 5.13.0-19.19 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4609 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 13 02:40:56 2021 IwConfig: lono wireless extensions. enp1s0no wireless extensions. LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-5.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.2:sku:cvnQEMU:ct1:cvrpc-q35-5.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-5.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945011] Re: kernel BUG at fs/inode.c:1676! during Live CD ubiquity partman with NTFS partitions
This issue is exactly the same with the final Live CD of Ubuntu Desktop 21.10 (Impish Indri) with full graphics. The process which causes warnings from 'fs/block_dev.c' is ntfsresize. So, this issue is probably the same as bugs #121943 and #1946828 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945011 Title: kernel BUG at fs/inode.c:1676! during Live CD ubiquity partman with NTFS partitions Status in linux package in Ubuntu: Confirmed Bug description: On this computer with ext4, FAT and NTFS partitions : I successfully booted from the Live CD of Ubuntu Desktop 21.10 (Impish Indri) beta with full graphics. I started the ubiquity graphical interface and successfully completed the first screens. But on the 'Updates and other software screen', after clicking on Continue, ubiquity does NOT show the next screen (which on previous versions was Partitioning). ubiquity seems to be blocked inside partman. I attach the partman log file. syslog contains following message : kernel BUG at fs/inode.c:1676! Notably, this kernel bug message is preceeded by 2 warnings : WARNING: CPU: 7 PID: 18634 at fs/block_dev.c:1610 blkdev_put+0x130/0x140 WARNING: CPU: 7 PID: 18634 at fs/block_dev.c:1576 __blkdev_put+0x1dc/0x1f0 Thanks in advance for investigating and correcting this issue. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 6322 F pulseaudio /dev/snd/controlC1: ubuntu 6322 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 24 21:25:08 2021 IwConfig: lono wireless extensions. enp2s0no wireless extensions. LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.200 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:skuSKU:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx: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: SKU 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/1945011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938983] Re: missing modules after 5.11.0-25-generic update
Similar bugs are also reported here: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1922350 https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1939986 It seems that the 5.11 kernel needs newer versions of i915 firmware than those currently available in linux-firmware package. ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1938983 Title: missing modules after 5.11.0-25-generic update Status in initramfs-tools package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: After updating to kernel 5.11.0-25-generic wireless driver failed to recognize WiFi card. Possible reasons/symptoms: $ sudo update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 update-initramfs: Generating /boot/initrd.img-5.8.0-63-generic $ lsb_release -a LSB Version: core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description: July2021 Release: 20.04 Codename: focal Workaround: connected Ethernet. (Inconvenient) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1938983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948873] [NEW] Hirsute update: upstream stable patchset 2021-10-26
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2021-10-26
Ported from the following upstream stable releases:
v5.10.68, v5.14.7
from git://git.kernel.org/
drm/bridge: lt9611: Fix handling of 4k panels
xen: reset legacy rtc flag for PV domU
arm64/sve: Use correct size when reinitialising SVE state
PM: base: power: don't try to use non-existing RTC for storing data
PCI: Add AMD GPU multi-function power dependencies
drm/amd/amdgpu: Increase HWIP_MAX_INSTANCE to 10
drm/etnaviv: return context from etnaviv_iommu_context_get
drm/etnaviv: put submit prev MMU context when it exists
drm/etnaviv: stop abusing mmu_context as FE running marker
drm/etnaviv: keep MMU context across runtime suspend/resume
drm/etnaviv: exec and MMU state is lost when resetting the GPU
drm/etnaviv: fix MMU context leak on GPU reset
drm/etnaviv: reference MMU context when setting up hardware state
drm/etnaviv: add missing MMU context put when reaping MMU mapping
s390/sclp: fix Secure-IPL facility detection
x86/pat: Pass valid address to sanitize_phys()
x86/mm: Fix kern_addr_valid() to cope with existing but not present entries
tipc: fix an use-after-free issue in tipc_recvmsg
ethtool: Fix rxnfc copy to user buffer overflow
net/{mlx5|nfp|bnxt}: Remove unnecessary RTNL lock assert
net-caif: avoid user-triggerable WARN_ON(1)
ptp: dp83640: don't define PAGE0
net/l2tp: Fix reference count leak in l2tp_udp_recv_core
r6040: Restore MDIO clock frequency after MAC reset
tipc: increase timeout in tipc_sk_enqueue()
drm/rockchip: cdn-dp-core: Make cdn_dp_core_resume __maybe_unused
perf machine: Initialize srcline string member in add_location struct
net/mlx5: FWTrace, cancel work on alloc pd error flow
net/mlx5: Fix potential sleeping in atomic context
nvme-tcp: fix io_work priority inversion
events: Reuse value read using READ_ONCE instead of re-reading it
net: ipa: initialize all filter table slots
gen_compile_commands: fix missing 'sys' package
vhost_net: fix OoB on sendmsg() failure.
net/af_unix: fix a data-race in unix_dgram_poll
net: dsa: destroy the phylink instance on any error in dsa_slave_phy_setup
x86/uaccess: Fix 32-bit __get_user_asm_u64() when CC_HAS_ASM_GOTO_OUTPUT=y
tcp: fix tp->undo_retrans accounting in tcp_sacktag_one()
selftest: net: fix typo in altname test
qed: Handle management FW error
udp_tunnel: Fix udp_tunnel_nic work-queue type
dt-bindings: arm: Fix Toradex compatible typo
ibmvnic: check failover_pending in login response
KVM: PPC: Book3S HV: Tolerate treclaim. in fake-suspend mode changing registers
bnxt_en: make bnxt_free_skbs() safe to call after bnxt_free_mem()
net: hns3: pad the short tunnel frame before sending to hardware
net: hns3: change affinity_mask to numa node range
net: hns3: disable mac in flr process
net: hns3: fix the timing issue of VF clearing interrupt sources
dt-bindings: mtd: gpmc: Fix the ECC bytes vs. OOB bytes equation
mfd: db8500-prcmu: Adjust map to reality
PCI: Add ACS quirks for NXP LX2xx0 and LX2xx2 platforms
fuse: fix use after free in fuse_read_interrupt()
PCI: tegra194: Fix handling BME_CHGED event
PCI: tegra194: Fix MSI-X programming
PCI: tegra: Fix OF node reference leak
mfd: Don't use irq_create_mapping() to resolve a mapping
PCI: rcar: Fix runtime PM imbalance in rcar_pcie_ep_probe()
tracing/probes: Reject events which have the same name of existing one
PCI: cadence: Use bitfield for *quirk_retrain_flag* instead of bool
PCI: cadence: Add quirk flag to set minimum delay in LTSSM Detect.Quiet state
PCI: j721e: Add PCIe support for J7200
PCI: j721e: Add PCIe support for AM64
PCI: Add ACS quirks for Cavium multi-function devices
watchdog: Start watchdog in watchdog_set_last_hw_keepalive only if appropriate
octeontx2-af: Add additional register check to rvu_poll_reg()
Set fc_nlinfo in nh_create_ipv4, nh_create_ipv6
net: usb: cdc_mbim: avoid altsetting toggling for Telit LN920
PCI: ibmphp: Fix double unmap of io_mem
ethtool: Fix an error code in cxgb2.c
NTB: Fix an error code in ntb_msit_probe()
NTB: perf: Fix an error code in perf_setup_inbuf()
mfd: axp20x: Update AXP288 volatile ranges
backlight: ktd253: Stabilize backlight
PCI: of: Don't fail devm_pci_alloc_host_bridge() on missing 'ranges'
PCI: iproc: Fix BCMA probe resource handling
netfilter: Fix fall-through warnings for Clang
netfilter: nft_ct: protect nft_ct_pcpu_template_refcnt with mutex
KVM: arm64: Restrict IPA size to maximum 48 bits on 4K and 16K page size
PCI: Fix pci_dev_str_match_path() alloc while atomic bug
mfd: tqmx86: Clear GPIO
[Kernel-packages] [Bug 1943524] Re: [EHL] Intel ishtp VNIC driver
** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1943524 Title: [EHL] Intel ishtp VNIC driver Status in intel: New Status in intel lookout-canyon series: New Status in linux-intel-5.13 package in Ubuntu: New Status in linux-intel-5.13 source package in Focal: Fix Released Bug description: Description The driver enables a virtual network interface for communicating with a dedicated low power chip over ISHTP Hardware: ElkhartLake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.13-yocto-210727T062416Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1943524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: intel/lookout-canyon Status: Fix Committed => Fix Released ** Changed in: intel Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945548 Title: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board Status in intel: Fix Released Status in intel lookout-canyon series: Fix Released Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Released Bug description: [Summary] I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board [Steps to reproduce] 1. Install https://cdimage.ubuntu.com/focal/daily-preinstalled/20210929/ to the system 2. Boot to desktop 3. Check if all Ethernet get IP address [Expected result] All Ethernet Port should up and runing and get the IP address. [Actual result] I225-IT Ethernet (8086:0d9f) does not work and did not get IP address [Failure rate] 100% [Additional information] CID: 202109-29492 SKU: N/A system-manufacturer: AAEON system-product-name: UPN-EHL01 bios-version: UNEHAM0D CPU: Intel Atom(R) x6425RE Processor @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] (rev 01) kernel-version: 5.13.0-1004-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1945548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921403] Re: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels
Hello Ioanna, or anyone else affected, Accepted makedumpfile into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.7-1ubuntu2.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: makedumpfile (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1921403 Title: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Focal: Fix Committed Status in makedumpfile source package in Hirsute: Fix Released Status in makedumpfile package in Debian: Fix Released Bug description: [IMPACT] makedumpfile does not create the dmesg. in /var/crash. This happens only on 5.10+ kernel because 5.10 kernel introduces a new lockless ringbuffer. This issue has been addressed upstream with commits : [1] c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer) [2] 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values) [TEST CASE] For testing a machine running focal with the 5.11 kernel is required. Then trigger a crash. After reboot make sure that dmesg. file is created in /var/crash/ [WHERE PROBLEMS COULD OCCUR] Any problems would involve the dmesg file not created. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/c617ec63339222f3a44d73e36677a9acc8954ccd [2] https://github.com/makedumpfile/makedumpfile/commit/44b073b7ec467aee0d7de381d455b8ace1199184 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1921403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942784] Re: makedumpfile falls back to cp on focal with 5.11 kernel
Hello Ioanna, or anyone else affected,
Accepted makedumpfile into focal-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.7-1ubuntu2.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: makedumpfile (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1942784
Title:
makedumpfile falls back to cp on focal with 5.11 kernel
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Focal:
Fix Committed
Status in makedumpfile source package in Hirsute:
Invalid
Bug description:
[IMPACT]
When running Focal with the hwe 5.11 kernel makedumpfile is not working as it
should.
Instead of compressing the dump makedumpfile falls back to cp.
This can create problems on systems with very large RAM and result into
exhausting all storage on the host.
[FIX]
This can be resolved with upstream commit f1197543d1c4 ([PATCH] Retrieve
MAX_PHYSMEM_BITS from vmcoreinfo).
The reason for falling back to cp is that without this patch makedumpfile
calculates wrongly the memory layout.
This happens after the kernel commit 1d50e5d0c505 ("crash_core, vmcoreinfo:
Append 'MAX_PHYSMEM_BITS'to vmcoreinfo").
With this commit applied, reading MAX_PHYSMEM_BITS from vmcoreinfo instead of
inferring lead to correctly detecting the memory layout and creating the dump
file properly.
[TEST CASE]
For testing a machine running focal with the 5.11 kernel is required.
Then trigger a crash.
On the console we can see that makedumpfile fails and `falls back to cp`.
In /var/crash we can see that no dmesg file is created and instead of the
dump file
the uncompressed vmcoreinfo is created.
[WHERE PROBLEMS COULD OCCUR]
Any regression potential would involve the crash dump not being
created after a crash in case kdump is configured.
[OTHER]
Only Focal with 5.11 kernel is affected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948862] 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 1948862 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/1948862 Title: KVM emulation failure when booting into VM crash kernel with multiple CPUs Status in linux package in Ubuntu: Incomplete Bug description: [Impact] When kexec'ing into a crash kernel with `ncpus` > 1, VMs can raise a KVM emulation failure. This will cause the VM to go into the "paused" state, and prevents it from being restored without a full VM restart. This happens only when there are multiple enabled CPUs in the crash kernel command-line, regardless of whether `nr_cpus` or `maxcpus` is being used. Due to the vCPU MMU state not being cleaned up correctly, the secondary CPUs try to access virtual addresses with a faulty MMU context that will result in the emulation failure. This shows up with a similar spew as below: $ sudo tail -n20 /var/log/libvirt/qemu/focal-vm.log KVM internal error. Suberror: 1 emulation failure EAX=de8f EBX= ECX=008f EDX=0600 ESI= EDI= EBP= ESP=f90c EIP=cdb1 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 000f 9b00 SS =de00 000de000 9300 DS =de00 000de000 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3=290b8001 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=66 83 c4 28 66 5b 66 c3 66 56 66 53 66 52 b1 8f 88 c8 e6 70 71 66 0f b6 f0 66 89 f2 67 88 54 24 03 88 c8 e6 70 66 31 db 88 d8 e6 71 66 56 66 68 1a [Test Plan] 1. Boot an Ubuntu guest VM with e.g. multipass: $ multipass launch daily:focal -c8 -m16g -n focal-vm 2. Configure guest crash kernel command-line with `nr_cpus=8`: ubuntu@focal-vm:~$ grep CMDLINE_APPEND /etc/default/kdump-tools # KDUMP_CMDLINE_APPEND - Additional arguments to append to the command line KDUMP_CMDLINE_APPEND="reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=8 irqpoll nousb ata_piix.prefer_ms_hyperv=0" 3. Crash guest VM and watch for the KVM emulation failure: ubuntu@focal-vm:~$ echo c | sudo tee /proc/sysrq-trigger [Where problems could occur] As we're resetting MMU context on vCPUs, potential regressions would show up in workloads relying on KVM guests. We should properly test the scenario mentioned in the bug to make sure secondary CPUs are being cleaned up properly, and that no other regressions have been introduced when rebooting or kexec'ing into different kernels. Since we're adding an MMU reset at kvm_vcpu_reset(), the overall regression potential should be fairly low and contained to starting/resetting vCPUs (i.e. VM start and reboot). [Other info] This has been fixed by upstream commit: 0aa1837533e5 KVM: x86: Properly reset MMU context at vCPU RESET/INIT And the two follow up commits, which revert the vendor-specific resets: 5d2d7e41e3b8 KVM: SVM: Drop explicit MMU reset at RESET/INIT 61152cd907d5 KVM: VMX: Remove explicit MMU reset in enter_rmode() These commits have been introduced during the upstream 5.14 and 5.15 release candidates, and as such should be backported to previous supported kernels. $ git describe --contains 0aa1837533e5 5d2d7e41e3b8 61152cd907d5 v5.14-rc1~166^2~58 v5.15-rc1~65^2~119 v5.15-rc1~65^2~120 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948862] [NEW] KVM emulation failure when booting into VM crash kernel with multiple CPUs
Public bug reported: [Impact] When kexec'ing into a crash kernel with `ncpus` > 1, VMs can raise a KVM emulation failure. This will cause the VM to go into the "paused" state, and prevents it from being restored without a full VM restart. This happens only when there are multiple enabled CPUs in the crash kernel command-line, regardless of whether `nr_cpus` or `maxcpus` is being used. Due to the vCPU MMU state not being cleaned up correctly, the secondary CPUs try to access virtual addresses with a faulty MMU context that will result in the emulation failure. This shows up with a similar spew as below: $ sudo tail -n20 /var/log/libvirt/qemu/focal-vm.log KVM internal error. Suberror: 1 emulation failure EAX=de8f EBX= ECX=008f EDX=0600 ESI= EDI= EBP= ESP=f90c EIP=cdb1 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 000f 9b00 SS =de00 000de000 9300 DS =de00 000de000 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3=290b8001 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=66 83 c4 28 66 5b 66 c3 66 56 66 53 66 52 b1 8f 88 c8 e6 70 71 66 0f b6 f0 66 89 f2 67 88 54 24 03 88 c8 e6 70 66 31 db 88 d8 e6 71 66 56 66 68 1a [Test Plan] 1. Boot an Ubuntu guest VM with e.g. multipass: $ multipass launch daily:focal -c8 -m16g -n focal-vm 2. Configure guest crash kernel command-line with `nr_cpus=8`: ubuntu@focal-vm:~$ grep CMDLINE_APPEND /etc/default/kdump-tools # KDUMP_CMDLINE_APPEND - Additional arguments to append to the command line KDUMP_CMDLINE_APPEND="reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=8 irqpoll nousb ata_piix.prefer_ms_hyperv=0" 3. Crash guest VM and watch for the KVM emulation failure: ubuntu@focal-vm:~$ echo c | sudo tee /proc/sysrq-trigger [Where problems could occur] As we're resetting MMU context on vCPUs, potential regressions would show up in workloads relying on KVM guests. We should properly test the scenario mentioned in the bug to make sure secondary CPUs are being cleaned up properly, and that no other regressions have been introduced when rebooting or kexec'ing into different kernels. Since we're adding an MMU reset at kvm_vcpu_reset(), the overall regression potential should be fairly low and contained to starting/resetting vCPUs (i.e. VM start and reboot). [Other info] This has been fixed by upstream commit: 0aa1837533e5 KVM: x86: Properly reset MMU context at vCPU RESET/INIT And the two follow up commits, which revert the vendor-specific resets: 5d2d7e41e3b8 KVM: SVM: Drop explicit MMU reset at RESET/INIT 61152cd907d5 KVM: VMX: Remove explicit MMU reset in enter_rmode() These commits have been introduced during the upstream 5.14 and 5.15 release candidates, and as such should be backported to previous supported kernels. $ git describe --contains 0aa1837533e5 5d2d7e41e3b8 61152cd907d5 v5.14-rc1~166^2~58 v5.15-rc1~65^2~119 v5.15-rc1~65^2~120 ** Affects: linux (Ubuntu) Importance: High Assignee: Heitor Alves de Siqueira (halves) Status: New ** Tags: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948862 Title: KVM emulation failure when booting into VM crash kernel with multiple CPUs Status in linux package in Ubuntu: New Bug description: [Impact] When kexec'ing into a crash kernel with `ncpus` > 1, VMs can raise a KVM emulation failure. This will cause the VM to go into the "paused" state, and prevents it from being restored without a full VM restart. This happens only when there are multiple enabled CPUs in the crash kernel command-line, regardless of whether `nr_cpus` or `maxcpus` is being used. Due to the vCPU MMU state not being cleaned up correctly, the secondary CPUs try to access virtual addresses with a faulty MMU context that will result in the emulation failure. This shows up with a similar spew as below: $ sudo tail -n20 /var/log/libvirt/qemu/focal-vm.log KVM internal error. Suberror: 1 emulation failure EAX=de8f EBX= ECX=008f EDX=0600 ESI= EDI= EBP= ESP=f90c EIP=cdb1 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 000f 9b00 SS =de00 000de000 9300 DS =de00 000de000 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT=
[Kernel-packages] [Bug 1574196] Re: Card with chipset BCM4360 [14e4:43a0] (rev 03) doesn't see 5Ghz networks with high channel number.
Same problem with an ASUS PCE-AC68 (chipset BCM4360 [14e4:43a0] (rev 03)) on Kubuntu 20.04. I can not connect to my 5Ghz network. If I type I get this output: iwlist wlp9s0 freq wlp9s032 channels in total; available frequencies : Channel 01 : 2.412 GHz Channel 02 : 2.417 GHz Channel 03 : 2.422 GHz Channel 04 : 2.427 GHz Channel 05 : 2.432 GHz Channel 06 : 2.437 GHz Channel 07 : 2.442 GHz Channel 08 : 2.447 GHz Channel 09 : 2.452 GHz Channel 10 : 2.457 GHz Channel 11 : 2.462 GHz Channel 12 : 2.467 GHz Channel 13 : 2.472 GHz Channel 32 : 5.16 GHz Channel 34 : 5.17 GHz Channel 36 : 5.18 GHz Channel 38 : 5.19 GHz Channel 40 : 5.2 GHz Channel 42 : 5.21 GHz Channel 44 : 5.22 GHz Channel 46 : 5.23 GHz Channel 48 : 5.24 GHz Channel 50 : 5.25 GHz Channel 52 : 5.26 GHz Channel 54 : 5.27 GHz Channel 56 : 5.28 GHz Channel 58 : 5.29 GHz Channel 60 : 5.3 GHz Channel 62 : 5.31 GHz Channel 64 : 5.32 GHz Channel 66 : 5.33 GHz Channel 68 : 5.34 GHz Current Frequency:2.462 GHz (Channel 11) This bug is opened since 2016 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1574196 Title: Card with chipset BCM4360 [14e4:43a0] (rev 03) doesn't see 5Ghz networks with high channel number. Status in bcmwl package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: The card Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03) doesn't see 5Ghz networks with an high channel number, if you change the channel back to a lower one the network will be found again. In my case with channel 104 the network wasn't seen by the card, with channel 40 it works fine wireless-info script result: ## wireless info START ## Report from: 22 Apr 2016 19:23 CEST +0200 Booted last: 22 Apr 2016 18:51 CEST +0200 Script from: 27 Sep 2015 00:34 UTC + # release ### Distributor ID: Ubuntu Description: Ubuntu 14.04.4 LTS Release: 14.04 Codename: trusty # kernel Linux 3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Parameters: ro, quiet, splash, vt.handoff=7 # desktop ### Ubuntu # lspci # 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7758] Kernel driver in use: r8169 04:00.0 Network controller [0280]: Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03) Subsystem: Broadcom Corporation Device [14e4:0619] Kernel driver in use: wl # lsusb # Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 004: ID 1532:0016 Razer USA, Ltd DeathAdder Mouse Bus 001 Device 003: ID 258a:0001 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # PCMCIA card info ## # rfkill 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no # lsmod # wl 6367819 0 mxm_wmi13021 1 nouveau wmi19177 2 mxm_wmi,nouveau cfg80211 496328 1 wl # interfaces auto lo iface lo inet loopback # ifconfig ## eth0 Link encap:Ethernet HWaddr UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) virbr0Link encap:Ethernet HWaddr inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0
[Kernel-packages] [Bug 1942589] Re: Ubuntu 5.4.0-81 stops bnx2x loading hardware
Looks like this might be fixed in 5.4.0-90 with: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942589 Title: Ubuntu 5.4.0-81 stops bnx2x loading hardware Status in linux package in Ubuntu: Confirmed Bug description: Server: HPE BL460c Gen9 Network: HP FlexFabric 10Gb 2-port 536FLB Adapter (Broadcom/Qlogic Net Extreme II 10/20GBE) Using ubuntu 20.04.2 with linux kernel 5.4.0-80 all functionality worked however upon upgrades via apt to 20.04.3 which uses linux kernel 5.4.0-81, ubuntu is unable to load the drivers for the network device. Below is the output for both kernels when the system is booted. ### # Kernel 5.4.0-80 working # ### ubuntu@server:$ dmesg | grep bnx2x [6.648833] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.713.36-0 (2014/02/10) [6.695219] bnx2x :06:00.0: msix capability found [6.719107] bnx2x :06:00.0: part number 0-0-0-0 [7.112390] bnx2x :06:00.0: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [7.112504] bnx2x :06:00.1: msix capability found [7.112889] bnx2x :06:00.1: part number 0-0-0-0 [7.320779] bnx2x :06:00.1: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [7.323549] bnx2x :06:00.0 eno49: renamed from eth0 [7.343281] bnx2x :06:00.1 eno50: renamed from eth1 [ 16.321102] bnx2x :06:00.1 eno50: using MSI-X IRQs: sp 130 fp[0] 132 ... fp[7] 139 [ 16.770833] bnx2x :06:00.1 eno50: NIC Link is Up, 1 Mbps full duplex, Flow control: ON - receive & transmit [ 17.136896] bnx2x :06:00.0 eno49: using MSI-X IRQs: sp 120 fp[0] 122 ... fp[7] 129 [ 17.526831] bnx2x :06:00.0 eno49: NIC Link is Up, 1 Mbps full duplex, Flow control: ON - receive & transmit ubuntu@server:$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno49: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 9e:b2:88:1c:ea:40 brd ff:ff:ff:ff:ff:ff 3: eno50: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 9e:b2:88:1c:ea:40 brd ff:ff:ff:ff:ff:ff 4: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 9e:b2:88:1c:ea:40 brd ff:ff:ff:ff:ff:ff inet 10.0.0.68/24 brd 10.0.0.255 scope global bond0 valid_lft forever preferred_lft forever inet6 fe80::9cb2:88ff:fe1c:ea40/64 scope link valid_lft forever preferred_lft forever ubuntu@server:$ sudo lshw -C network *-network:0 description: Ethernet interface product: BCM57840 NetXtreme II 10/20-Gigabit Ethernet vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:06:00.0 logical name: eno49 version: 11 serial: 9e:b2:88:1c:ea:40 size: 10Gbit/s capacity: 10Gbit/s width: 64 bits clock: 33MHz capabilities: pm vpd msix pciexpress bus_master cap_list rom ethernet physical fibre 1000bt-fd 1bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=bnx2x driverversion=1.713.36-0 storm 7.13.11.0 duplex=full firmware=mbi 7.18.77 bc 7.15.80 latency=0 link=yes multicast=yes port=fibre slave=yes speed=10Gbit/s resources: irq:16 memory:9400-947f memory:9480-94ff memory:9501-9501 memory:92b0-92b7 *-network:1 description: Ethernet interface product: BCM57840 NetXtreme II 10/20-Gigabit Ethernet vendor: Broadcom Inc. and subsidiaries physical id: 0.1 bus info: pci@:06:00.1 logical name: eno50 version: 11 serial: 9e:b2:88:1c:ea:40 size: 10Gbit/s capacity: 10Gbit/s width: 64 bits clock: 33MHz capabilities: pm vpd msix pciexpress bus_master cap_list rom ethernet physical fibre 1000bt-fd 1bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=bnx2x driverversion=1.713.36-0 storm 7.13.11.0 duplex=full firmware=mbi 7.18.77 bc 7.15.80 latency=0 link=yes multicast=yes port=fibre slave=yes speed=10Gbit/s resources: irq:17 memory:9300-937f memory:9380-93ff memory:9500-9500 memory:92b8-92bf *-network description: Ethernet interface physical id: 1 logical name: bond0 serial: 9e:b2:88:1c:ea:40 size: 10Gbit/s
[Kernel-packages] [Bug 1948811] Re: Touchpad not detected when pci=nocrs not specified
** 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/1948811 Title: Touchpad not detected when pci=nocrs not specified Status in linux package in Ubuntu: Confirmed Bug description: Touchpad on Clevo NL41LU2 is not detected with 5.13.0-20-generic kernel unless pci=nocrs is specified. Please find iomem, dmesg and lspci dump attached. Ubuntu details: $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Florent --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: flo 884 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-26 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: PC Specialist LTD NL4x_NL5xLU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p6 pci=nocrs ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201 Tags: wayland-session impish Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/19/2020 dmi.bios.release: 7.2 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.02TPCS dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4XLU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.02TPCS:bd08/19/2020:br7.2:efr7.2:svnPCSpecialistLTD:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnCLEVO:rnNL4XLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948811] Re: Touchpad not detected when pci=nocrs not specified
** Tags added: apport-collected wayland-session ** Description changed: Touchpad on Clevo NL41LU2 is not detected with 5.13.0-20-generic kernel unless pci=nocrs is specified. Please find iomem, dmesg and lspci dump attached. Ubuntu details: $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Florent + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu71 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: flo 884 F pulseaudio + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 21.10 + InstallationDate: Installed on 2021-10-26 (0 days ago) + InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) + MachineType: PC Specialist LTD NL4x_NL5xLU + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p6 pci=nocrs + ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-20-generic N/A + linux-backports-modules-5.13.0-20-generic N/A + linux-firmware 1.201 + Tags: wayland-session impish + Uname: Linux 5.13.0-20-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/19/2020 + dmi.bios.release: 7.2 + dmi.bios.vendor: INSYDE Corp. + dmi.bios.version: 1.07.02TPCS + dmi.board.asset.tag: Tag 12345 + dmi.board.name: NL4XLU + dmi.board.vendor: CLEVO + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: No Enclosure + dmi.chassis.version: N/A + dmi.ec.firmware.release: 7.2 + dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.02TPCS:bd08/19/2020:br7.2:efr7.2:svnPCSpecialistLTD:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnCLEVO:rnNL4XLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: + dmi.product.family: Not Applicable + dmi.product.name: NL4x_NL5xLU + dmi.product.sku: Not Applicable + dmi.product.version: Not Applicable + dmi.sys.vendor: PC Specialist LTD -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948811 Title: Touchpad not detected when pci=nocrs not specified Status in linux package in Ubuntu: Confirmed Bug description: Touchpad on Clevo NL41LU2 is not detected with 5.13.0-20-generic kernel unless pci=nocrs is specified. Please find iomem, dmesg and lspci dump attached. Ubuntu details: $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Florent --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: flo 884 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-26 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: PC Specialist LTD NL4x_NL5xLU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p6 pci=nocrs ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201 Tags: wayland-session impish Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/19/2020 dmi.bios.release: 7.2 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.02TPCS dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4XLU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.02TPCS:bd08/19/2020:br7.2:efr7.2:svnPCSpecialistLTD:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnCLEVO:rnNL4XLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package alsa-ucm-conf - 1.2.4-2ubuntu5 --- alsa-ucm-conf (1.2.4-2ubuntu5) impish; urgency=medium * d/p/0008-HDA-Intel-add-Boost-volume-control-for-Headset-Mic.patch Add Mic Boost in the HDA Intel ucm, after this change, when users adjust input volume, the Mic Boost could be adjusted as well as Capture Volume. (LP: #1930188) -- Hui Wang Tue, 14 Sep 2021 10:54:28 +0800 ** Changed in: alsa-ucm-conf (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Released Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with
[Kernel-packages] [Bug 1938742] Re: 5.8.0-63 Breaks Wifi on RTL8822BE
Hello, I updated to a 5.11 version and it was working ok for a while. I recently updated to 5.11.0-38-generic #42~20.04.1 and wifi is no longer showing up. What can I do to fix this? Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1938742 Title: 5.8.0-63 Breaks Wifi on RTL8822BE Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: After upgrading to 5.8.0-63 the wifi card RTL8822BE can still be seen, but wifi networks cannot be found. If the nvidia driver 470.57 is installed the wifi card is no longer found. lspci | grep -i realtek: 07:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter (rev ff) Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 2 22:37:25 2021 EcryptfsInUse: Yes ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username 2540 F pulseaudio /dev/snd/controlC1: username 2540 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 EcryptfsInUse: Yes MachineType: LENOVO 81LF Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=79951aeb-477e-4f92-a571-ce78702269da ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-63-generic N/A linux-backports-modules-5.8.0-63-generic N/A linux-firmware1.187.15 Tags: wayland-session focal Uname: Linux 5.8.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2020 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: 9VCN22WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion Y7000P-1060 dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvr9VCN22WW:bd11/30/2020:br1.22:efr1.22:svnLENOVO:pn81LF:pvrLenovoLegionY7000P-1060:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoLegionY7000P-1060: dmi.product.family: Legion Y7000P-1060 dmi.product.name: 81LF dmi.product.sku: LENOVO_MT_81LF_BU_idea_FM_Legion Y7000P-1060 dmi.product.version: Lenovo Legion Y7000P-1060 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1938742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945576] Re: Intel I225-IT ethernet controller: igc: probe of 0000:02:00.0 failed with error -1
Already fixed in linux-intel in bug 1945548. ** Changed in: linux-intel (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: linux-intel (Ubuntu Focal) Assignee: You-Sheng Yang (vicamo) => (unassigned) ** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: linux-intel-5.13 (Ubuntu Focal) Assignee: You-Sheng Yang (vicamo) => (unassigned) ** Changed in: linux-intel (Ubuntu Focal) Status: Fix Released => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945576 Title: Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed with error -1 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-intel package in Ubuntu: Invalid Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-intel source package in Focal: Won't Fix Status in linux-intel-5.13 source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-intel source package in Hirsute: Invalid Status in linux-intel-5.13 source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-intel source package in Impish: Invalid Status in linux-intel-5.13 source package in Impish: Invalid Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Environment] Device : Aaeon Up xtreme i11 Platform: Intel TigerLake-UP3 I225-IT NVM version: 1.79 I225-IT Stepping: B3 Ubuntu version: 20.04.3 LTS with kernel 5.11.0-27-generic [Description] It can work under Windows10. But uner Ubuntu, we can't find the interface by ifconfig command and the system dmesg will has the error of igc driver module : igc: probe of :02:00.0 failed with error -1 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831974] Re: turbo boost doesnt work on battery in ubuntu for 8th gen intel core processors , Turbo boost works only when charger is plugged in . This reduces clock speed and ca
** Changed in: debian Status: Incomplete => 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/1831974 Title: turbo boost doesnt work on battery in ubuntu for 8th gen intel core processors , Turbo boost works only when charger is plugged in . This reduces clock speed and causes single core performance to throttle Status in linux package in Ubuntu: Expired Status in Debian: Invalid Bug description: Tried reinstalling and other versions of debian distro like PopOs , on every install turbo boost doesnt seem to work even when power plan is changed to high performance for 8th gen intel laptop cpu. /sys/devices/system/cpu/intel_pstate/no_turbo is set to 1 , and the value cannot be changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948825] [NEW] kernel NULL pointer dereference in iwlmvm when debugfs=off
Public bug reported: When booting 5.11.0-38-generic, dmesg shows this: ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' thermal thermal_zone3: failed to read out thermal zone (-61) BUG: kernel NULL pointer dereference, address: 0017 #PF: supervisor read access in kernel mode #PF: error_code(0x) - not-present page PGD 0 P4D 0 Oops: [#1] SMP PTI CPU: 1 PID: 912 Comm: modprobe Tainted: P O 5.11.0-38-generic #42~20.04.1-Ubuntu Hardware name: System76Lemur/Lemur, BIOS 1.05.25RSA2-1 04/17/2018 RIP: 0010:iwl_mvm_dbgfs_register+0x5db/0x660 [iwlmvm] Code: 48 c7 c7 a8 bb 00 c1 e8 83 15 89 cc 48 89 d9 4c 89 e2 be 80 01 00 00 49 c7 c0 00 51 00 c1 48 c7 c7 b0 bb 00 c1 e8 15 0c 89 cc <49> 8b 4c 24 18 48 c7 c2 b4 bb 00 c1 be 64 00 00 00 48 8d 7d 84 e8 RSP: 0018:a59c40607af0 EFLAGS: 00010206 RAX: RBX: 8ebbc8f91f28 RCX: 8ebbc8f91f28 RDX: RSI: RDI: c100bbb0 RBP: a59c40607b70 R08: 8e46b100 R09: c1005100 R10: 0100 R11: 0013 R12: R13: 000fffe0 R14: 8ebbc8f91f28 R15: 8ebbc8f91f20 FS: 7f6eb9e21540() GS:8ec30ec8() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0017 CR3: 00010aba2002 CR4: 003706e0 Call Trace: ? thermal_zone_device_set_mode+0x8c/0xb0 ? thermal_zone_device_enable+0x13/0x20 ? iwl_mvm_thermal_initialize+0x1ca/0x390 [iwlmvm] iwl_op_mode_mvm_start+0x762/0xa10 [iwlmvm] _iwl_op_mode_start.isra.0+0x47/0x80 [iwlwifi] iwl_opmode_register+0x73/0xe0 [iwlwifi] ? 0xc0aa3000 iwl_mvm_init+0x3a/0x1000 [iwlmvm] ? 0xc0aa3000 do_one_initcall+0x48/0x1d0 ? _cond_resched+0x19/0x30 ? kmem_cache_alloc_trace+0x37a/0x430 ? do_init_module+0x28/0x250 do_init_module+0x62/0x250 load_module+0x11aa/0x1370 ? security_kernel_post_read_file+0x5c/0x70 ? security_kernel_post_read_file+0x5c/0x70 __do_sys_finit_module+0xc2/0x120 ? __do_sys_finit_module+0xc2/0x120 __x64_sys_finit_module+0x1a/0x20 do_syscall_64+0x38/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f6eb9f6689d Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 f5 0c 00 f7 d8 64 89 01 48 RSP: 002b:7ffdbd12deb8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 555dbd8f8a40 RCX: 7f6eb9f6689d RDX: RSI: 555dbcc58358 RDI: 0002 RBP: 0004 R08: R09: R10: 0002 R11: 0246 R12: 555dbcc58358 R13: R14: 555dbd8f8b70 R15: 555dbd8f8a40 Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generi> intel_pch_thermal libahci intel_xhci_usb_role_switch acpi_pad sch_fq_codel nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr ip_tables x_tables autofs4 btrfs blake2b_generic libcrc32c xor raid6_pq dm_crypt hid_generic usbhid hid i915 aesni_intel i2c_algo_bit drm_kms_helper psm> CR2: 0017 ---[ end trace b471419e1ba88be0 ]--- iwlwifi :02:00.0 wlp2s0: renamed from wlan0 RIP: 0010:iwl_mvm_dbgfs_register+0x5db/0x660 [iwlmvm] Code: 48 c7 c7 a8 bb 00 c1 e8 83 15 89 cc 48 89 d9 4c 89 e2 be 80 01 00 00 49 c7 c0 00 51 00 c1 48 c7 c7 b0 bb 00 c1 e8 15 0c 89 cc <49> 8b 4c 24 18 48 c7 c2 b4 bb 00 c1 be 64 00 00 00 48 8d 7d 84 e8 RSP: 0018:a59c40607af0 EFLAGS: 00010206 RAX: RBX: 8ebbc8f91f28 RCX: 8ebbc8f91f28 RDX: RSI: RDI: c100bbb0 RBP: a59c40607b70 R08: 8e46b100 R09: c1005100 R10: 0100 R11: 0013 R12: R13: 000fffe0 R14: 8ebbc8f91f28 R15: 8ebbc8f91f20 FS: 7f6eb9e21540() GS:8ec30ec8() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0017 CR3: 00010aba2002 CR4: 003706e0 ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. FYI, debugfs is disabled by booting with debugfs=off in /proc/cmdline. Additional information: $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 $ apt-cache policy linux-image-5.11.0-38-generic linux-image-5.11.0-38-generic: Installed: 5.11.0-38.42~20.04.1 Candidate: 5.11.0-38.42~20.04.1 Version table: *** 5.11.0-38.42~20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu
[Kernel-packages] [Bug 1887620] Re: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1887620 Title: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: Bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.4.0-40-generic Date: Thu Jul 9 06:16:55 2020 Dependencies: InstallationDate: Installed on 2020-05-28 (47 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 440.100-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-440 Title: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1887620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948349] Re: Ubuntu 21.10 Kernel Panic error.. Unable to boot from Live USB installer
I have managed to solved this problem yesterday with the help of Ubuntu Support system on Telegram.. The problem in my case was the incorrect error in the ISO image that I downloaded from the official repo. This error might have creeped in while I was downloading the iso in parts through IDM. With the help of the Checksum correction I managed to fix the error of the ISO image. I used qtorrent and downloaded the partially incomplete and missing piece of the ISO. I have already installed and I'm currently running Impish Indri with zero problem... Thank you everyone! Impish Indri was a superb release.. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948349 Title: Ubuntu 21.10 Kernel Panic error.. Unable to boot from Live USB installer Status in linux package in Ubuntu: Confirmed Bug description: I tried to install Ubuntu 21.10 stable which was released couple of days ago. I get Kernel panic error on both my ThinkPad and Thinkcenter when trying to boot from the Live usb installer. My ThinkPad x201 processor is Intel 1stGen. My Thinkcenter m93p runs on Intel Core i5- 4430s. I have tried to disable the track point and touchpad from BIOS but with no luck. I tried acpi=off from the unetbootin boot menu and kernel panic doesn't appear but another problem "unable to find a medium containing a live file system" popped up. I don't know how to go past this. Any help will be appreciated. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948811] Re: Touchpad not detected when pci=nocrs not specified
This issue is going to be fixed by this patchset: https://patchwork.kernel.org/project/linux- pci/patch/20211014183943.27717-2-hdego...@redhat.com/ The patchset will be merged to mainline kernel soon, and will be picked by stable kernel and ubuntu kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948811 Title: Touchpad not detected when pci=nocrs not specified Status in linux package in Ubuntu: Incomplete Bug description: Touchpad on Clevo NL41LU2 is not detected with 5.13.0-20-generic kernel unless pci=nocrs is specified. Please find iomem, dmesg and lspci dump attached. Ubuntu details: $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Florent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948811] 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 1948811 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948811 Title: Touchpad not detected when pci=nocrs not specified Status in linux package in Ubuntu: Incomplete Bug description: Touchpad on Clevo NL41LU2 is not detected with 5.13.0-20-generic kernel unless pci=nocrs is specified. Please find iomem, dmesg and lspci dump attached. Ubuntu details: $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Florent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948811] [NEW] Touchpad not detected when pci=nocrs not specified
Public bug reported: Touchpad on Clevo NL41LU2 is not detected with 5.13.0-20-generic kernel unless pci=nocrs is specified. Please find iomem, dmesg and lspci dump attached. Ubuntu details: $ lsb_release -rd Description:Ubuntu 21.10 Release:21.10 Florent ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: impish ** Attachment added: "iomem, dmesg and lspci logs" https://bugs.launchpad.net/bugs/1948811/+attachment/5536249/+files/logs.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948811 Title: Touchpad not detected when pci=nocrs not specified Status in linux package in Ubuntu: Incomplete Bug description: Touchpad on Clevo NL41LU2 is not detected with 5.13.0-20-generic kernel unless pci=nocrs is specified. Please find iomem, dmesg and lspci dump attached. Ubuntu details: $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Florent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948807] [NEW] Boot time from snap in 20/stable increses boot time on 3.5 seconds
Public bug reported: I am seeing what looks as a regression in pi-kernel snap for UC20: there are around 3.5 additional seconds spent in boot time. In the image from cdimage (2021-06-30), I see: [1.856540] random: crng init done [1.871798] loop: module loaded (see https://paste.ubuntu.com/p/CkfWXY5Vgf/) while if I build an image from latest snaps in the 20/stable channel, I get: [1.855481] random: crng init done [5.349491] loop: module loaded (see https://paste.ubuntu.com/p/CNt42gdDcZ/) The pi-kernel snap revision is 353. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1948807 Title: Boot time from snap in 20/stable increses boot time on 3.5 seconds Status in linux-raspi package in Ubuntu: New Bug description: I am seeing what looks as a regression in pi-kernel snap for UC20: there are around 3.5 additional seconds spent in boot time. In the image from cdimage (2021-06-30), I see: [1.856540] random: crng init done [1.871798] loop: module loaded (see https://paste.ubuntu.com/p/CkfWXY5Vgf/) while if I build an image from latest snaps in the 20/stable channel, I get: [1.855481] random: crng init done [5.349491] loop: module loaded (see https://paste.ubuntu.com/p/CNt42gdDcZ/) The pi-kernel snap revision is 353. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package alsa-ucm-conf - 1.2.4-2ubuntu5 --- alsa-ucm-conf (1.2.4-2ubuntu5) impish; urgency=medium * d/p/0008-HDA-Intel-add-Boost-volume-control-for-Headset-Mic.patch Add Mic Boost in the HDA Intel ucm, after this change, when users adjust input volume, the Mic Boost could be adjusted as well as Capture Volume. (LP: #1930188) -- Hui Wang Tue, 14 Sep 2021 10:54:28 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Released Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR
[Kernel-packages] [Bug 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) 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/1867570 Title: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: This issue was extracted from the comment in bug 1812638, since that bug will be specific for i386 This reuseport_bpf_numa in net will fail on PowerPC with: The output on B-5.3 P8 is: # selftests: net: reuseport_bpf_numa # IPv4 UDP # send node 0, receive socket 0 # send node 1, receive socket 7 # ./reuseport_bpf_numa: node id/receive socket mismatch not ok 3 selftests: net: reuseport_bpf_numa # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1867570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853665] Re: Realtek RTL8821CE [10ec:c821] Subsystem [103c:831a] Bluetooth not probed
The issue still persists with kernel 5.13 and the impish driver Why doesn't the maintainers of this driver use some of the code of tomaspinho driver? I read on Linux Mint forum that some people got bluetooth working with that driver. Link to repo: https://github.com/tomaspinho/rtl8821ce/ Link to LM forum thread: https://forums.linuxmint.com/viewtopic.php?t=308215 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1853665 Title: Realtek RTL8821CE [10ec:c821] Subsystem [103c:831a] Bluetooth not probed Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in rtl8821ce package in Ubuntu: Confirmed Bug description: The driver installed just fine and wifi is working but bluetooth does not. I will gladly provide further debugging information. Ubuntu 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 2090 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-17 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G7 Notebook PC Package: rtl8821ce ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/05/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8532 dmi.board.vendor: HP dmi.board.version: 70.22 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.16:bd12/05/2018:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn8532:rvr70.22:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G7 Notebook PC dmi.product.sku: 6MQ54EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 1931 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-17 (231 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP 250 G7 Notebook PC Package: rtl8821ce ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: ashmem_linux Tags: focal staging staging Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-18 (47 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/05/2018 dmi.bios.vendor: Insyde dmi.bios.version:
[Kernel-packages] [Bug 1948767] Re: Fail to detect audio output from external monitor
** Changed in: linux (Ubuntu Hirsute)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Impish)
Status: Incomplete => In Progress
** Tags added: oem-priority originate-from-1946054 somerville
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1948767
Title:
Fail to detect audio output from external monitor
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.13 package in Ubuntu:
New
Status in linux-oem-5.14 package in Ubuntu:
New
Status in linux source package in Focal:
Incomplete
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
In Progress
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Few recent AMD systems shows "snd_hda_intel :00:1f.3: azx_get_response
timeout" and fail to detect the HDMI/DP audio output device when connects to
external monitor. It will work magically when re-loading the driver.
[Fix]
Backport the upstream fix c0f1886de7e1 ("Allow repeatedly probing on codec
configuration errors) from 5.15.0 rc. It adds the capability for retrying the
probe upon codec probe errors on the certain AMD platforms.
[Test]
1. Connect the external monitor to particular affected AMD systems with HDMI
or DisplayPort.
2. Go to Audio Settings to check if the HDMI/DP audio output device exist or
not.
[Where problems could occur]
Should be low risk, it adds the chance for retrying codec probe and won't
affect machines which used to work.
== Original Bug Description ==
Can not detect DP audio output
[Steps to reproduce]
1) install dell-bto-focal-fossa-grimer-rkl-X72-20210929-8.iso and boot into OS
2) switch to on-demand mode
3) connect an external monitor via DP Port
4) check sound setting --> Output Device
5) switch to performance mode
6) check sound setting --> Output Device
[Expected result]
System can detect DP audio output when external monitor connected
[Actual result]
Can not detect DP audio output
This issue can be reproduce in on-demand and performance mode.
[Failure rate]
1/1
[Additional information]
CID: 202101-28624
SKU: PRH-DVT-C6
Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-grimer-rkl+X72
system-manufacturer: Dell Inc.
system-product-name: OptiPlex 5490 AIO
bios-version: 1.4.1
CPU: 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16x)
GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:4c8a] (rev 04)
01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f99] (rev a1)
kernel-version: 5.14.0-2006-oem
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1948767/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948377] Re: [SRU][F] USB: serial: pl2303: add support for PL2303HXN
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => AaronMa (mapengyu) ** Changed in: linux (Ubuntu) Assignee: AaronMa (mapengyu) => (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/1948377 Title: [SRU][F] USB: serial: pl2303: add support for PL2303HXN Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: [Impact] PL2303HXN is not supported by 5.4 kernel. 5.5 kernel starts to support it. so only SRU for focal 5.4 kernel. [Fix] Clean cherry-pick upstream commits. Add support for PL2303HXN. [Test] Verified on hardware, use minicom to test serial port, it works fine. [Where problems could occur] It may break the pl2303 ttyUSBx. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1948377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948434] Re: Check if secure boot is enabled with development keys
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Shravan Kumar Ramani (sramani) ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1948434 Title: Check if secure boot is enabled with development keys Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: In Progress Bug description: SRU Justification: [Impact] Currently, there is no indication from mlx-bootctl when the user reads the lifecycle_state sysfs as to whether secure boot is enabled with development keys or production keys. In order to make this clear to the user, add a check in the driver. [Fix] Check the secure boot development mode status bit. If secure boot is enabled with the development key, then print it to the output buffer when lifecycle_state_show() is invoked. [Test Case] On a system in secure state, if it has been programmed with development keys, then reading the lifecycle_state sysfs entry in the mlx-bootctl driver should print a message that indicates the same. Similarly, a secure system which has been programmed with production keys must print the appropriate message when the lifecycle_state sysfs is read. [Regression Potential] Can be considered minimum. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1948434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948767] 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 1948767
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 Focal)
Status: New => Incomplete
** Changed in: linux (Ubuntu Hirsute)
Status: New => Incomplete
** Changed in: linux (Ubuntu Impish)
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/1948767
Title:
Fail to detect audio output from external monitor
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.13 package in Ubuntu:
New
Status in linux-oem-5.14 package in Ubuntu:
New
Status in linux source package in Focal:
Incomplete
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
In Progress
Status in linux source package in Hirsute:
Incomplete
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Incomplete
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Few recent AMD systems shows "snd_hda_intel :00:1f.3: azx_get_response
timeout" and fail to detect the HDMI/DP audio output device when connects to
external monitor. It will work magically when re-loading the driver.
[Fix]
Backport the upstream fix c0f1886de7e1 ("Allow repeatedly probing on codec
configuration errors) from 5.15.0 rc. It adds the capability for retrying the
probe upon codec probe errors on the certain AMD platforms.
[Test]
1. Connect the external monitor to particular affected AMD systems with HDMI
or DisplayPort.
2. Go to Audio Settings to check if the HDMI/DP audio output device exist or
not.
[Where problems could occur]
Should be low risk, it adds the chance for retrying codec probe and won't
affect machines which used to work.
== Original Bug Description ==
Can not detect DP audio output
[Steps to reproduce]
1) install dell-bto-focal-fossa-grimer-rkl-X72-20210929-8.iso and boot into OS
2) switch to on-demand mode
3) connect an external monitor via DP Port
4) check sound setting --> Output Device
5) switch to performance mode
6) check sound setting --> Output Device
[Expected result]
System can detect DP audio output when external monitor connected
[Actual result]
Can not detect DP audio output
This issue can be reproduce in on-demand and performance mode.
[Failure rate]
1/1
[Additional information]
CID: 202101-28624
SKU: PRH-DVT-C6
Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-grimer-rkl+X72
system-manufacturer: Dell Inc.
system-product-name: OptiPlex 5490 AIO
bios-version: 1.4.1
CPU: 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16x)
GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:4c8a] (rev 04)
01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f99] (rev a1)
kernel-version: 5.14.0-2006-oem
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948767/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948767] [NEW] Fail to detect audio output from external monitor
Public bug reported:
[SRU Justification]
[Impact]
Few recent AMD systems shows "snd_hda_intel :00:1f.3: azx_get_response
timeout" and fail to detect the HDMI/DP audio output device when connects to
external monitor. It will work magically when re-loading the driver.
[Fix]
Backport the upstream fix c0f1886de7e1 ("Allow repeatedly probing on codec
configuration errors) from 5.15.0 rc. It adds the capability for retrying the
probe upon codec probe errors on the certain AMD platforms.
[Test]
1. Connect the external monitor to particular affected AMD systems with HDMI or
DisplayPort.
2. Go to Audio Settings to check if the HDMI/DP audio output device exist or
not.
[Where problems could occur]
Should be low risk, it adds the chance for retrying codec probe and won't
affect machines which used to work.
== Original Bug Description ==
Can not detect DP audio output
[Steps to reproduce]
1) install dell-bto-focal-fossa-grimer-rkl-X72-20210929-8.iso and boot into OS
2) switch to on-demand mode
3) connect an external monitor via DP Port
4) check sound setting --> Output Device
5) switch to performance mode
6) check sound setting --> Output Device
[Expected result]
System can detect DP audio output when external monitor connected
[Actual result]
Can not detect DP audio output
This issue can be reproduce in on-demand and performance mode.
[Failure rate]
1/1
[Additional information]
CID: 202101-28624
SKU: PRH-DVT-C6
Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-grimer-rkl+X72
system-manufacturer: Dell Inc.
system-product-name: OptiPlex 5490 AIO
bios-version: 1.4.1
CPU: 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16x)
GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:4c8a] (rev 04)
01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f99] (rev a1)
kernel-version: 5.14.0-2006-oem
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: linux-oem-5.13 (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Status: Incomplete
** Affects: linux-oem-5.13 (Ubuntu Focal)
Importance: Undecided
Status: In Progress
** Affects: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided
Status: In Progress
** Affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: Incomplete
** Affects: linux-oem-5.13 (Ubuntu Hirsute)
Importance: Undecided
Status: Invalid
** Affects: linux-oem-5.14 (Ubuntu Hirsute)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Impish)
Importance: Undecided
Status: Incomplete
** Affects: linux-oem-5.13 (Ubuntu Impish)
Importance: Undecided
Status: Invalid
** Affects: linux-oem-5.14 (Ubuntu Impish)
Importance: Undecided
Status: Invalid
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.13 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.13 (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: linux-oem-5.13 (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux-oem-5.14 (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: linux-oem-5.14 (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1948767
Title:
Fail to detect audio output from external monitor
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.13 package in Ubuntu:
New
Status in linux-oem-5.14 package in Ubuntu:
New
Status in linux source package in Focal:
Incomplete
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
In Progress
Status in linux source package in Hirsute:
Incomplete
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Incomplete
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Few recent AMD systems shows "snd_hda_intel :00:1f.3: azx_get_response
timeout" and fail to detect the HDMI/DP audio output device when
[Kernel-packages] [Bug 1940759] 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/1940759 Title: [Qualcomm Atheros QCA9565 / AR9565] Bluetooth settings have a delay between on and off modes Status in linux package in Ubuntu: Confirmed Bug description: When I switch bluetooth on or off in Control Center, it has a delay (5-30s) between the switch icon and the actual screen output, some times I need to switch between options on the side bar or even close the Control Center. outputs: >>>lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Aug 22 00:46:45 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2021-04-20 (123 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-06-08 (75 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: junior 1611 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-20 (126 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 1bcf:2c81 Sunplus Innovation Technology Inc. HD WebCam Bus 001 Device 031: ID 04ca:3014 Lite-On Technology Corp. Qualcomm Atheros Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-574 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=6767043c-143f-4c3a-976f-1c786765d862 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-06-08 (78 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/04/2016 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Zoro_SL dmi.board.vendor: Acer dmi.board.version: V1.14 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.14:bd03/04/2016:br0.0:efr2.70:svnAcer:pnAspireE5-574:pvrV1.14:rvnAcer:rnZoro_SL:rvrV1.14:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: SKL dmi.product.name: Aspire E5-574 dmi.product.sku: Aspire E5-574_100C_1.14 dmi.product.version: V1.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
