[Kernel-packages] [Bug 1933938] Re: Missing CNVi firmware for Intel AX211/AX201 on ADL
Moved PPA in comment #2 to https://launchpad.net/~vicamo/+archive/ubuntu/linux-staging to have a single origin containing all planned fixes. -- 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/1933938 Title: Missing CNVi firmware for Intel AX211/AX201 on ADL Status in HWE Next: New Status in intel: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Incomplete Status in linux-oem-5.13 source package in Focal: Incomplete Status in linux source package in Impish: Incomplete Status in linux-firmware source package in Impish: Incomplete Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.sfi * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: ??? To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930980] Re: Hang on loading initial ramdisk on kernels 5.4.0-72+, 5.11.0-16+ with nvidia drivers 440+
Additional data: * laptop with i7-8750H and GP104M (GeForce GTX 1070 Mobile) * kernel 5.4.0-77 and nvidia 460 worked * upgraded to kernel 5.4.0-80 and nvidia 470 * kernel 5.4.0-80 and nvidia 470 failed to load ramdisk * booted back to kernel 5.4.0-77 and nvidia 470 * kernel 5.4.0-77 and nvidia 470 loaded ramdisk but no gdm * used command line to downgrade to nvidia 460 * kernel 5.4.0-80 and nvidia 460 working -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930980 Title: Hang on loading initial ramdisk on kernels 5.4.0-72+, 5.11.0-16+ with nvidia drivers 440+ Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-465 package in Ubuntu: Confirmed Bug description: Affected Ubuntu Versions: Release: 20.04 Kernel: 5.4.0-73,74 Nvidia Driver: 440,450,460,465 Kernel: 5.4.0-72 Nvidia Driver: 460, 465 Release: 21.04 Kernel: 5.11.0-16,18 Nvidia Driver: 440, 450, 460, 465 For 21.04 with all kernels, driver 390 works correctly Issue occurs during bootup where after starting to load the initial ramdisk, the system hangs indefinitely with no output. Booting in recovery mode and examining the logs, there is a series of bug messages. Updating motherboard bios to latest had no effect. Note: This exact hardware setup worked as recently as June 2, 2021 on ubuntu 20.04. After applying the latest set of OS updates and rebooting, the issue began occurring. Trace follows: Jun 4 21:51:06 ultra kernel: [7.262411] BUG: kernel NULL pointer dereference, address: Jun 4 21:51:06 ultra kernel: [7.262412] #PF: supervisor write access in kernel mode Jun 4 21:51:06 ultra kernel: [7.262413] #PF: error_code(0x0002) - not-present page Jun 4 21:51:06 ultra kernel: [7.262414] PGD 0 P4D 0 Jun 4 21:51:06 ultra kernel: [7.262415] Oops: 0002 [#1] SMP NOPTI Jun 4 21:51:06 ultra kernel: [7.262416] CPU: 3 PID: 998 Comm: Xorg Tainted: P IO 5.11.0-18-generic #19-Ubuntu Jun 4 21:51:06 ultra kernel: [7.262417] Hardware name: ASUS System Product Name/PRIME Z390-A, BIOS 1802 12/01/2020 Jun 4 21:51:06 ultra kernel: [7.262418] RIP: 0010:_nv008453rm+0xa8/0x5f0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.262673] Code: 8b 84 24 60 04 00 00 ba 01 00 00 00 4c 89 e6 48 89 df 4d 89 e5 e8 c8 64 c4 e0 41 89 c6 45 85 f6 0f 84 3c 02 00 00 48 8b 45 08 <4c> 89 28 5b 44 89 f0 41 5c 41 5d 41 5e 41 5f 48 83 c5 40 c3 0f 1f Jun 4 21:51:06 ultra kernel: [7.262675] RSP: 0018:be91018bf8c8 EFLAGS: 00010282 Jun 4 21:51:06 ultra kernel: [7.262676] RAX: RBX: a08c06e14008 RCX: Jun 4 21:51:06 ultra kernel: [7.262676] RDX: 0020 RSI: d9a4 RDI: a08c06e14008 Jun 4 21:51:06 ultra kernel: [7.262677] RBP: a08c0a0c5db0 R08: 0025 R09: a08c0a0c5d18 Jun 4 21:51:06 ultra kernel: [7.262678] R10: a08c06e14008 R11: a08c06e150a0 R12: a08c07440008 Jun 4 21:51:06 ultra kernel: [7.262678] R13: a08c07440010 R14: R15: a08c0a0c5de0 Jun 4 21:51:06 ultra kernel: [7.262679] FS: 7f7d29194a40() GS:a09b2dac() knlGS: Jun 4 21:51:06 ultra kernel: [7.262680] CS: 0010 DS: ES: CR0: 80050033 Jun 4 21:51:06 ultra kernel: [7.262680] CR2: CR3: 00010f6fe006 CR4: 003706e0 Jun 4 21:51:06 ultra kernel: [7.262681] DR0: DR1: DR2: Jun 4 21:51:06 ultra kernel: [7.262681] DR3: DR6: fffe0ff0 DR7: 0400 Jun 4 21:51:06 ultra kernel: [7.262682] Call Trace: Jun 4 21:51:06 ultra kernel: [7.262684] ? _nv032332rm+0x10c/0x280 [nvidia] Jun 4 21:51:06 ultra kernel: [7.262884] ? _nv032330rm+0x145/0x180 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263075] ? _nv014647rm+0x213/0x300 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263255] ? _nv014704rm+0x6dd/0xf80 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263435] ? _nv026937rm+0x226/0x4e0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263616] ? _nv016954rm+0x4a8/0x5e0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.263819] ? _nv016956rm+0xdd/0x230 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264009] ? _nv09rm+0xcd/0x1d0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264256] ? _nv022467rm+0x30/0x60 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264394] ? _nv000701rm+0x143f/0x2100 [nvidia] Jun 4 21:51:06 ultra kernel: [7.264552] ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 4 21:51:06 ultra kernel: [7.2647
[Kernel-packages] [Bug 1934647] Re: [HP Pavilion Gaming Laptop 15-dk0xxx] Black screen at login using 5.8.0-59, but 5.8.0-43 and 5.12.14 work fine
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1934647 Title: [HP Pavilion Gaming Laptop 15-dk0xxx] Black screen at login using 5.8.0-59, but 5.8.0-43 and 5.12.14 work fine Status in linux package in Ubuntu: Confirmed Bug description: If I choose nvidia driver, then the screen is black and I cannot log in. To log in, I need to delete all nvidia files. After that, the xorg is selected and I can log in. But I cannot edit brightness. I can hardly see anything on the screen. The battery is draining very badly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936452] Re: [SRU][F/H/I] Add MT7921 wifi fw
SRU: * https://lists.ubuntu.com/archives/kernel-team/2021-July/122569.html (linux-firmware, F) * https://lists.ubuntu.com/archives/kernel-team/2021-July/122570.html (linux-firmware, H) * https://lists.ubuntu.com/archives/kernel-team/2021-July/122571.html (linux-firmware, I) -- 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/1936452 Title: [SRU][F/H/I] Add MT7921 wifi fw Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Hirsute: New Status in linux-firmware source package in Impish: New Bug description: SRU justification: [Impact] No support for MT7921 wifi card. [Fix] MT7921 needs both driver and firmware, driver is almost ready, add firmware first, then get driver bug fixed later. [Test] Verified on hardware, cold boot system wifi works fine. Reboot make it fail, but I will fix it in SRU of kernel patch. After that, it works fine. [Where problems could occur] The MT7921 wifi may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924685] Re: No sound output/input available after installing 21.04
I'm not seeing any of the sof-audio errors from bug 1935850 in dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924685 Title: No sound output/input available after installing 21.04 Status in OEM Priority Project: Won't Fix Status in Release Notes for Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Image: Hirsute 21.04 (20210415 daily build) Device: Dell Precision 5750 After installing 21.04, the sound card is unavailable. In Sound Settings, there is only one choice: "Dummy Output" . The only way to hear sound is to connect a Bluetooth speaker. Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel: https://certification.ubuntu.com/hardware/202002-27726 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1561 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 15:10:05 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Precision 5750 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937056] [NEW] Touchpad not working with ASUS TUF F15
Public bug reported: I am using Kubuntu 21.10 on my ASUS TUF F15 FX506HM_FX566HM. The touchpad isn't detected in Settings and neither in xinput, nor in cat /proc/bus/input/devices. Laptop model: ASUS TUF F15 FX506HM_FX566HM. Manufacturer of the Touchpad: Touchpad not detected When the symptom first appeared: From beginning Output of lsb_release -rd Description:Ubuntu Impish Indri (development branch) Release:21.10 Using kernel version 5.13.2. Also tried 5.13.1, 5.12.15, 5.11 Output of xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Asus Wireless Radio Control id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=11 [slave keyboard (3)] ↳ Intel HID events id=12 [slave keyboard (3)] ↳ Intel HID 5 button array id=13 [slave keyboard (3)] ↳ Asus WMI hotkeys id=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)] Output of lspci :00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 05) :00:01.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #1 (rev 05) :00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) :00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 05) :00:06.0 System peripheral: Intel Corporation Device 09ab :00:07.0 PCI bridge: Intel Corporation Tiger Lake-H Thunderbolt 4 PCI Express Root Port #0 (rev 05) :00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 05) :00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01) :00:0d.0 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 USB Controller (rev 05) :00:0d.2 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 NHI #0 (rev 05) :00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller :00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11) :00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11) :00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H Serial IO I2C Controller #0 (rev 11) :00:16.0 Communication controller: Intel Corporation Tiger Lake-H Management Engine Interface (rev 11) :00:1c.0 PCI bridge: Intel Corporation Device 43bf (rev 11) :00:1d.0 PCI bridge: Intel Corporation Device 43b6 (rev 11) :00:1f.0 ISA bridge: Intel Corporation Tiger Lake-H LPC/eSPI Controller (rev 11) :00:1f.3 Audio device: Intel Corporation Tiger Lake-H HD Audio Controller (rev 11) :00:1f.4 SMBus: Intel Corporation Tiger Lake-H SMBus Controller (rev 11) :00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H SPI Controller (rev 11) :01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1) :01:00.1 Audio device: NVIDIA Corporation Device 228e (rev a1) :2d:00.0 Network controller: MEDIATEK Corp. Device 7961 :2e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 1:e0:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #0 (rev 05) 1:e1:00.0 Non-Volatile memory controller: SK hynix Device 174a ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Output of cat /proc/bus/input/devices" https://bugs.launchpad.net/bugs/1937056/+attachment/5512448/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937056 Title: Touchpad not working with ASUS TUF F15 Status in linux package in Ubuntu: New Bug description: I am using Kubuntu 21.10 on my ASUS TUF F15 FX506HM_FX566HM. The touchpad isn't detected in Settings and neither in xinput, nor in cat /proc/bus/input/devices. Laptop model: ASUS TUF F15 FX506HM_FX566HM. Manufacturer of the Touchpad: Touchpad not detected When the symptom first appeared: From beginning Output of lsb_release -rd Description:Ubuntu Impish Indri
[Kernel-packages] [Bug 1935951] Re: [nvidia] HomeOffice & Un-/Docking: X11 crash on resume when docked to multi monitor
Is there anything I can do, to make the "INCOMPLETE" bug in COMPLETE
state?
The problem is, that X11 is not crashing or leaving any crash files. It just
restarts. From user view it is a crash.
IN case of KDE, there are at least some KDE crash files.
The post in NVIDIA forum also has been created, see my older comment #7
Are there more commands I should execute?
The three bugs seem to be related to Intel Video according to lspci.txt,
and mine is NVIDIA originated X11 restart.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1935951
Title:
[nvidia] HomeOffice & Un-/Docking: X11 crash on resume when docked to
multi monitor
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Incomplete
Bug description:
X11 crashes on resume and my current desktop is lost and the login
manager appears.
I posted a bugreported here
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1197
with configu details.
But it seems to be nvidia, but may be a workaround is possible in Ubuntu?
This bug prevents me to use Linux for daily docking /undocking cycles for
HomeOffice (works fine with Windows).
[ 1272.639] (II) NVIDIA(0): Setting mode "DP-4: nvidia-auto-select
@1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[ 1272.639] (WW) NVIDIA(0): Failed to set the display configuration
[ 1272.639] (WW) NVIDIA(0): - Setting a mode on head 1 failed: Invalid
surface parameters
[ 1272.639] (WW) NVIDIA(0): were specified
[ 1272.639] (EE) NVIDIA(0): Failed to enter VT (mode initialization failed)
[ 1272.639] (EE)
Fatal server error:
[ 1272.639] (EE) EnterVT failed for screen 0
[ 1272.639] (EE)
[ 1272.639] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 1272.639] (EE) Please also check the log file at "/var/log/Xorg.0.log" for
additional information.
[ 1272.639] (EE)
[ 1274.034] (EE) Server terminated with error (1). Closing log file.
I found something similar which could handle the EnterVT failed issue:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/
but I am not sure if it is already in Ubuntu 20.04 LTS
Hardware:
Hardware used:
Dell Precision 15" 7540, Xeon E-2286M@2.4GHz, 128 GB ECC RAM, NVIDIA Quadro
RTX 5000 16GB VRAM
Dockingstations at Home and Offices: WD19DC (240W)
Monitors used for Linux migration Office1: 2x 4K U4320Q, 42.5" @ 96dpi font /
No scaling a
Monitors used for Linux migration Office2: 2xU3818DW, 37.5"
Monitors used for Linux migration at home: 3x FullHD Dell monitors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1935951/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935951] Re: [nvidia] HomeOffice & Un-/Docking: X11 crash on resume when docked to multi monitor
It is a crash but also Xorg tries to catch its own crashes which creates
this headache for maintainers whereby you often lose all trace of where
it crashed. Often but not always, so we do get plenty of proper crash
reports from Xorg. In my experience it just takes more attempts and
eventually one will leave a file in /var/crash/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1935951
Title:
[nvidia] HomeOffice & Un-/Docking: X11 crash on resume when docked to
multi monitor
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Incomplete
Bug description:
X11 crashes on resume and my current desktop is lost and the login
manager appears.
I posted a bugreported here
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1197
with configu details.
But it seems to be nvidia, but may be a workaround is possible in Ubuntu?
This bug prevents me to use Linux for daily docking /undocking cycles for
HomeOffice (works fine with Windows).
[ 1272.639] (II) NVIDIA(0): Setting mode "DP-4: nvidia-auto-select
@1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[ 1272.639] (WW) NVIDIA(0): Failed to set the display configuration
[ 1272.639] (WW) NVIDIA(0): - Setting a mode on head 1 failed: Invalid
surface parameters
[ 1272.639] (WW) NVIDIA(0): were specified
[ 1272.639] (EE) NVIDIA(0): Failed to enter VT (mode initialization failed)
[ 1272.639] (EE)
Fatal server error:
[ 1272.639] (EE) EnterVT failed for screen 0
[ 1272.639] (EE)
[ 1272.639] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 1272.639] (EE) Please also check the log file at "/var/log/Xorg.0.log" for
additional information.
[ 1272.639] (EE)
[ 1274.034] (EE) Server terminated with error (1). Closing log file.
I found something similar which could handle the EnterVT failed issue:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/
but I am not sure if it is already in Ubuntu 20.04 LTS
Hardware:
Hardware used:
Dell Precision 15" 7540, Xeon E-2286M@2.4GHz, 128 GB ECC RAM, NVIDIA Quadro
RTX 5000 16GB VRAM
Dockingstations at Home and Offices: WD19DC (240W)
Monitors used for Linux migration Office1: 2x 4K U4320Q, 42.5" @ 96dpi font /
No scaling a
Monitors used for Linux migration Office2: 2xU3818DW, 37.5"
Monitors used for Linux migration at home: 3x FullHD Dell monitors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1935951/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936577] Re: Introduce the 470-server series
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1936577 Title: Introduce the 470-server series Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-460-server source package in Bionic: In Progress Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-460-server source package in Focal: In Progress Status in linux-restricted-modules source package in Hirsute: Triaged Status in nvidia-graphics-drivers-460-server source package in Hirsute: In Progress Bug description: Introduce the 470 NVIDIA ERD (-server) series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.57.02 (470-server) == * Initial release (LP: #1936577). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1936577/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
In Progress
Status in fabric-manager-460 source package in Bionic:
In Progress
Status in libnvidia-nscq-450 source package in Bionic:
In Progress
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
In Progress
Status in fabric-manager-450 source package in Focal:
In Progress
Status in fabric-manager-460 source package in Focal:
In Progress
Status in libnvidia-nscq-450 source package in Focal:
In Progress
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
In Progress
Status in fabric-manager-450 source package in Groovy:
In Progress
Status in fabric-manager-460 source package in Groovy:
In Progress
Status in libnvidia-nscq-450 source package in Groovy:
In Progress
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
In Progress
Status in fabric-manager-450 source package in Hirsute:
In Progress
Status in fabric-manager-460 source package in Hirsute:
In Progress
Status in libnvidia-nscq-450 source package in Hirsute:
In Progress
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
In Progress
Bug description:
As per the subject, the update includes fixes for the following CVEs:
CVE-2021-1093
CVE-2021-1094
CVE-2021-1095
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1933980/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@
[Kernel-packages] [Bug 1936785] Re: Add support for AMD BCL DID
** Description changed: [Impact] AMD BCL APU shares same code as CZN/RN, but has another DID to be added to kernel. [Fix] Below commit adds the ID. https://lists.freedesktop.org/archives/amd-gfx/2021-July/066502.html [Test] + We didn't receive h/w yet, just told by AMD that the new ID is required. [Where problems could occur] + Adding a new ID should be pretty safe. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936785 Title: Add support for AMD BCL DID Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] AMD BCL APU shares same code as CZN/RN, but has another DID to be added to kernel. [Fix] Below commit adds the ID. https://lists.freedesktop.org/archives/amd-gfx/2021-July/066502.html [Test] We didn't receive h/w yet, just told by AMD that the new ID is required. [Where problems could occur] Adding a new ID should be pretty safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936998] Re: e1000e blocks the boot process when it tried to write checksum to its NVM
** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936998 Title: e1000e blocks the boot process when it tried to write checksum to its NVM Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress 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 source package in Hirsute: In Progress 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 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 Bug description: [Impact] While probing e1000e, it checks its NVM checksum, and write correct checksum back if the checksum is not correct. But for recent GBE update for security, its NVM could be written once for MAC address during production, so write checksum during driver probing is not allowed and would block the boot process. [Fix] Intel provides a fix for it. https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20210718041031.3619696-1-sasha.nef...@intel.com/ [Test] Verified on a Dell machine which has wrong NVM checksum. [Where problems could occur] From what Intel told us, the checksum isn't correct is not a big deal, we could ignore it and it won't lead to any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937068] [NEW] "BUG: non-zero pgtables_bytes on freeing mm: 16384" errors during boot on bionic/linux s390x
Public bug reported: [Impact] When booting bionic/linux 4.15.0-152.159 on a s390x machine there's a lot of the following error message on the kernel log: BUG: non-zero pgtables_bytes on freeing mm: 16384 This error doesn't seem to happen on every boot. I could trace this happening as far back as 4.15.0-143.147, but this could be older as I don't have test results for older releases. This is similar to bug 1840046, which was supposedly fixed by an upstream stable patch around Sep/2019. [Test case] Boot bionic/linux on a s390x system. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Tags: 4.15 bionic s390x sru-20210719 ubuntu-boot ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Tags added: 4.15 bionic s390x sru-20210719 ** Tags added: ubuntu-boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937068 Title: "BUG: non-zero pgtables_bytes on freeing mm: 16384" errors during boot on bionic/linux s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: [Impact] When booting bionic/linux 4.15.0-152.159 on a s390x machine there's a lot of the following error message on the kernel log: BUG: non-zero pgtables_bytes on freeing mm: 16384 This error doesn't seem to happen on every boot. I could trace this happening as far back as 4.15.0-143.147, but this could be older as I don't have test results for older releases. This is similar to bug 1840046, which was supposedly fixed by an upstream stable patch around Sep/2019. [Test case] Boot bionic/linux on a s390x system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937068/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936785] Re: Add support for AMD BCL DID
** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936785 Title: Add support for AMD BCL DID Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] AMD BCL APU shares same code as CZN/RN, but has another DID to be added to kernel. [Fix] Below commit adds the ID. https://lists.freedesktop.org/archives/amd-gfx/2021-July/066502.html [Test] We didn't receive h/w yet, just told by AMD that the new ID is required. [Where problems could occur] Adding a new ID should be pretty safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936921] Re: While screen while vt switching with AMD W5700 or W5500
** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) -- 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/1936921 Title: While screen while vt switching with AMD W5700 or W5500 Status in HWE Next: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Bug description: [Impact] Ubuntu-oem-5.10-5.10.0-1027.28 includes some amdgpu patches to support s2idle feature, but it leads to the white screen while vt switching during booting up. [Fix] After bisect the kernel, we need below commit to fix this issue. 0b08c54bb7a37 drm/amd/display: Fix the display corruption issue on Navi10 [Test] Verified on Dell machine with AMD W5700 graphics card. [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936577] Re: Introduce the 470-server series
Unembargoed into -proposed. Please test as an SRU and set tags appropriately. ** Tags added: verification-needed-bionic verification-needed-focal verification-needed-hirsute ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu) Status: In Progress => Fix Committed ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1936577 Title: Introduce the 470-server series Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Committed Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in linux-restricted-modules source package in Hirsute: Triaged Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Bug description: Introduce the 470 NVIDIA ERD (-server) series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.57.02 (470-server) == * Initial release (LP: #1936577). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1936577/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package fabric-manager-450 -
450.142.00-0ubuntu0.21.04.1
---
fabric-manager-450 (450.142.00-0ubuntu0.21.04.1) hirsute; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
16:05:25 +0200
** Changed in: fabric-manager-450 (Ubuntu Hirsute)
Status: In Progress => Fix Released
** Changed in: fabric-manager-450 (Ubuntu Groovy)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings s
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package fabric-manager-450 -
450.142.00-0ubuntu0.18.04.1
---
fabric-manager-450 (450.142.00-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
16:20:07 +0200
** Changed in: fabric-manager-460 (Ubuntu Hirsute)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update inc
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package fabric-manager-450 -
450.142.00-0ubuntu0.20.04.1
---
fabric-manager-450 (450.142.00-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
16:09:08 +0200
** Changed in: fabric-manager-450 (Ubuntu Bionic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update inclu
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package fabric-manager-460 -
460.91.03-0ubuntu0.21.04.1
---
fabric-manager-460 (460.91.03-0ubuntu0.21.04.1) hirsute; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
16:25:57 +0200
** Changed in: fabric-manager-460 (Ubuntu Groovy)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update inclu
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package fabric-manager-450 -
450.142.00-0ubuntu0.20.10.1
---
fabric-manager-450 (450.142.00-0ubuntu0.20.10.1) groovy; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
16:06:28 +0200
** Changed in: fabric-manager-450 (Ubuntu Focal)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update inclu
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package fabric-manager-460 -
460.91.03-0ubuntu0.20.10.1
---
fabric-manager-460 (460.91.03-0ubuntu0.20.10.1) groovy; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
16:30:03 +0200
** Changed in: fabric-manager-460 (Ubuntu Focal)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update include
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package libnvidia-nscq-450 -
450.142.00-0ubuntu0.21.04.1
---
libnvidia-nscq-450 (450.142.00-0ubuntu0.21.04.1) hirsute; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
16:58:11 +0200
** Changed in: libnvidia-nscq-450 (Ubuntu Groovy)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update inc
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package fabric-manager-460 -
460.91.03-0ubuntu0.20.04.1
---
fabric-manager-460 (460.91.03-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
16:30:58 +0200
** Changed in: fabric-manager-460 (Ubuntu Bionic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update include
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package libnvidia-nscq-450 -
450.142.00-0ubuntu0.20.04.1
---
libnvidia-nscq-450 (450.142.00-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
16:59:52 +0200
** Changed in: libnvidia-nscq-450 (Ubuntu Bionic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update inclu
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package nvidia-settings -
470.57.01-0ubuntu0.21.04.1
---
nvidia-settings (470.57.01-0ubuntu0.21.04.1) hirsute; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Mon, 12 Jul 2021
16:22:06 +0200
** Changed in: nvidia-settings (Ubuntu Groovy)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update includes fixes
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package libnvidia-nscq-450 -
450.142.00-0ubuntu0.20.10.1
---
libnvidia-nscq-450 (450.142.00-0ubuntu0.20.10.1) groovy; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
16:59:10 +0200
** Changed in: libnvidia-nscq-450 (Ubuntu Focal)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update inclu
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package fabric-manager-460 -
460.91.03-0ubuntu0.18.04.1
---
fabric-manager-460 (460.91.03-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
16:32:02 +0200
** Changed in: libnvidia-nscq-450 (Ubuntu Hirsute)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update inclu
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package nvidia-settings -
470.57.01-0ubuntu0.20.10.1
---
nvidia-settings (470.57.01-0ubuntu0.20.10.1) groovy; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Mon, 12 Jul 2021
16:23:25 +0200
** Changed in: nvidia-settings (Ubuntu Focal)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update includes fixes f
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package nvidia-settings -
470.57.01-0ubuntu0.18.04.1
---
nvidia-settings (470.57.01-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Mon, 12 Jul 2021
16:52:10 +0200
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update includes fixes for the following CVEs:
CVE-2021-1093
CVE-2021-1094
CVE-2021-1095
To manage notific
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package libnvidia-nscq-450 -
450.142.00-0ubuntu0.18.04.1
---
libnvidia-nscq-450 (450.142.00-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
17:00:52 +0200
** Changed in: nvidia-settings (Ubuntu Hirsute)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update includ
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package nvidia-settings -
470.57.01-0ubuntu0.20.04.1
---
nvidia-settings (470.57.01-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Mon, 12 Jul 2021
16:46:55 +0200
** Changed in: nvidia-settings (Ubuntu Bionic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
In Progress
Status in libnvidia-nscq-450 package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update includes fixes f
[Kernel-packages] [Bug 1931131] Re: Update the 465 and the 460 NVIDIA driver series
This bug was fixed in the package nvidia-settings - 470.57.01-0ubuntu0.21.04.1 --- nvidia-settings (470.57.01-0ubuntu0.21.04.1) hirsute; urgency=medium * New upstream release (LP: #1933980). -- Alberto Milone Mon, 12 Jul 2021 16:22:06 +0200 ** Changed in: nvidia-settings (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: nvidia-settings (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1931131 Title: Update the 465 and the 460 NVIDIA driver series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: New Status in nvidia-graphics-drivers-465 package in Ubuntu: In Progress Status in nvidia-settings package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Released Status in linux source package in Hirsute: In Progress Status in nvidia-graphics-drivers-390 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Released Bug description: Update the 465 and the 460 NVIDIA driver series, and add support for Linux 5.13 to all the driver series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460.84 == * New upstream release (LP: #1931131): - Added support for the following GPUs: GeForce RTX 3080 Ti * debian/additional_card_ids: - Drop the additional IDs. * debian/rules: - Skip lines that start with "#"
[Kernel-packages] [Bug 1931131] Re: Update the 465 and the 460 NVIDIA driver series
This bug was fixed in the package nvidia-settings - 470.57.01-0ubuntu0.20.10.1 --- nvidia-settings (470.57.01-0ubuntu0.20.10.1) groovy; urgency=medium * New upstream release (LP: #1933980). -- Alberto Milone Mon, 12 Jul 2021 16:23:25 +0200 ** Changed in: nvidia-settings (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1931131 Title: Update the 465 and the 460 NVIDIA driver series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: New Status in nvidia-graphics-drivers-465 package in Ubuntu: In Progress Status in nvidia-settings package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Released Status in linux source package in Hirsute: In Progress Status in nvidia-graphics-drivers-390 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Released Bug description: Update the 465 and the 460 NVIDIA driver series, and add support for Linux 5.13 to all the driver series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460.84 == * New upstream release (LP: #1931131): - Added support for the following GPUs: GeForce RTX 3080 Ti * debian/additional_card_ids: - Drop the additional IDs. * debian/rules: - Skip lines that start with "#" in debian/additional_card_ids. * debian/templates/dkms_nvidia.conf.in: - Drop b
[Kernel-packages] [Bug 1931131] Re: Update the 465 and the 460 NVIDIA driver series
This bug was fixed in the package nvidia-settings - 470.57.01-0ubuntu0.20.04.1 --- nvidia-settings (470.57.01-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1933980). -- Alberto Milone Mon, 12 Jul 2021 16:46:55 +0200 ** Changed in: nvidia-settings (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1931131 Title: Update the 465 and the 460 NVIDIA driver series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: New Status in nvidia-graphics-drivers-465 package in Ubuntu: In Progress Status in nvidia-settings package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Released Status in linux source package in Hirsute: In Progress Status in nvidia-graphics-drivers-390 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Released Bug description: Update the 465 and the 460 NVIDIA driver series, and add support for Linux 5.13 to all the driver series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460.84 == * New upstream release (LP: #1931131): - Added support for the following GPUs: GeForce RTX 3080 Ti * debian/additional_card_ids: - Drop the additional IDs. * debian/rules: - Skip lines that start with "#" in debian/additional_card_ids. * debian/templates/dkms_nvidia.conf.in: - Drop b
[Kernel-packages] [Bug 1931131] Re: Update the 465 and the 460 NVIDIA driver series
This bug was fixed in the package nvidia-settings - 470.57.01-0ubuntu0.18.04.1 --- nvidia-settings (470.57.01-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (LP: #1933980). -- Alberto Milone Mon, 12 Jul 2021 16:52:10 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1931131 Title: Update the 465 and the 460 NVIDIA driver series Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: New Status in nvidia-graphics-drivers-465 package in Ubuntu: In Progress Status in nvidia-settings package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Released Status in linux source package in Hirsute: In Progress Status in nvidia-graphics-drivers-390 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Released Bug description: Update the 465 and the 460 NVIDIA driver series, and add support for Linux 5.13 to all the driver series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460.84 == * New upstream release (LP: #1931131): - Added support for the following GPUs: GeForce RTX 3080 Ti * debian/additional_card_ids: - Drop the additional IDs. * debian/rules: - Skip lines that start with "#" in debian/additional_card_ids. * debian/templates/dkms_nvidia.conf.in: - Drop buildfix_kernel_5.13.patch. == 465.31 == * New upstream release (LP: #1931131):
[Kernel-packages] [Bug 1936921] Re: While screen while vt switching with AMD W5700 or W5500
** Description changed: [Impact] Ubuntu-oem-5.10-5.10.0-1027.28 includes some amdgpu patches to support s2idle feature, but it leads to the white screen while vt switching during booting up. [Fix] After bisect the kernel, we need below commit to fix this issue. 0b08c54bb7a37 drm/amd/display: Fix the display corruption issue on Navi10 [Test] Verified on Dell machine with AMD W5700 graphics card. [Where problems could occur] + Hard to evaluate, but there is no further code modification on this part since 10/20/2020, and no "Fixes:" on this commit, so it should be stable. -- 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/1936921 Title: While screen while vt switching with AMD W5700 or W5500 Status in HWE Next: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Bug description: [Impact] Ubuntu-oem-5.10-5.10.0-1027.28 includes some amdgpu patches to support s2idle feature, but it leads to the white screen while vt switching during booting up. [Fix] After bisect the kernel, we need below commit to fix this issue. 0b08c54bb7a37 drm/amd/display: Fix the display corruption issue on Navi10 [Test] Verified on Dell machine with AMD W5700 graphics card. [Where problems could occur] Hard to evaluate, but there is no further code modification on this part since 10/20/2020, and no "Fixes:" on this commit, so it should be stable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] [NEW] GPF in rtl2832
You have been subscribed to a public bug: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- GPF in rtl2832 https://bugs.launchpad.net/bugs/1937031 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] Re: GPF in rtl2832
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1937031 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. (package changed to linux as "kernel fault" is mentioned; probably should be gnuradio) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] Re: GPF in rtl2832
apport information ** Tags added: apport-collected focal ** Description changed: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.18 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 + InstallationDate: Installed on 2018-06-09 (1137 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + MachineType: System manufacturer System Product Name + NonfreeKernelModules: wl nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + SHELL=/bin/bash + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-77-generic N/A + linux-backports-modules-5.4.0-77-generic N/A + linux-firmware1.187.15 + Tags: focal + Uname: Linux 5.4.0-77-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/14/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 3801 + dmi.board.asset.tag: Default string + dmi.board.name: Z170-DELUXE + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: System Product Name + dmi.product.sku: SKU + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512494/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add
[Kernel-packages] [Bug 1937031] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512500/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512496/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512502/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512503/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512497/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512499/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512501/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512495/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512504/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512498/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512509/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] Re: GPF in rtl2832
I don't believe that this is a problem with GnuRadio, as the kernel stack trace shows a device driver or similar.. plus the computer is unusable after the problem occurs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512512/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512510/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512508/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512506/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512507/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512505/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937031] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1937031/+attachment/5512511/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937031 Title: GPF in rtl2832 Status in linux package in Ubuntu: New Bug description: I'm using a nooelec "nesdr smart" and GnuRadio - however every time i try to run the gnuradio program, i get a kernel fault. the computer then seems to be unusable. it doesn't crash, but it becomes unstable - various programs don't work correctly, can't edit files... the only way to resolve this is to reboot. The problem appears reliably every time. I get a an error reported, which i can see with dmesg. I can't save the error to a file - as saving files doesn't seem to work correctly after this error (e.g. vi error.txt, then save will hang) I'll add some details about the error here, and attach a screenshot. (this is me transcribing the screenshot, so hopefully accurate!) general protection fault: [#1] SMP PTI CPU: 3: PID: 866 Comm: kworker/3:3 Tainted: P Workqueue: events rtl2832_i2c_gate_work [rtl2832] call trace: ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_xtra+0x1ae/0x5e0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x2e/0x40 regmap_lock_mutex+0xe/0x10 regmap_update_bits_base+0x3b/0x90 rtl2832_i2c_gate_work+0x31/0x70 [rtl2832] process_one_work+0x1eb/0x3b0 RIP: 0010:__mutex_lock.isra.0+0x78/0x4f0 uname -a Linux beasty 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Memory: 65678960K/67040508K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 1361548K reserved, 0K cma-reserved) CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3) happy to supply further information if required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=a3775e3e-a429-449e-b37a-bcd420ca62e8 InstallationDate: Installed on 2018-06-09 (1137 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name NonfreeKernelModules: wl nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-77-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 RelatedPackageVersions: linux-restricted-modules-5.4.0-77-generic N/A linux-backports-modules-5.4.0-77-generic N/A linux-firmware1.187.15 Tags: focal Uname: Linux 5.4.0-77-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-11 (222 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1936678] Re: Samsung Laptop support module doesn't load
Alex, Does https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040557 still apply? I’m running under UEFI, not BIOS, and I don’t want to brick this machine. Sent from my iPhone > On Jul 19, 2021, at 3:30 AM, Alex Hung <1936...@bugs.launchpad.net> wrote: > > Please run "sudo modprobe samsung-laptop -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936678 Title: Samsung Laptop support module doesn't load Status in linux package in Ubuntu: New Bug description: This is identical to bug # 1170885, which was filed 2013-04-20. The last comment on that bug was by Kai-Heng Feng (kaihengfeng), who requested a new bug report. This is a Samsung laptop NP730QCJ. $ sudo modprobe samsung-laptop modprobe: ERROR: could not insert 'samsung_laptop': No such device About my system: $ sudo dmidecode | grep -A 2 -i 'base board' Base Board Information Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: NP730QCJ-K01US $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS" $ cat /proc/version_signature Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 $ file /sys/firmware/efi/ /sys/firmware/efi/: directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928921] Re: LRMv5: switch primary version handling to kernel-versions data set
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1928921 Title: LRMv5: switch primary version handling to kernel-versions data set Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: In Progress Bug description: Switch fetching dkms-versions data for these packages to the kernel- versions dataset. Currently the primary dkms-versions data is committed directly to the primary kernel packages. This allows this information to cascade reliably to all derivatives and their associated LRM packages. But once the primaries are closed it is increasingly hard to change this data. This makes performing an LRM-only respin very difficult as it differs in handling from a primary spin. We move the primary version dataset out of the kernel packages into a shared external "kernel-versions" dataset. Each package which needs this data then obtains the information it needs directly, with it committed locally to that package at update time. This renders preparation of am initial (-1) spin and a later LRM-only respin identicle. We simply update the shared dataset and perform a no-change rebuild (./update-versions) on them and they will automatically get the updated version information. We will want to update update-dkms-versions in all primary main packages, and introduce same into all LRM packages. As we already run update-dkms-versions in the primary main packages, and are introducing update-dkms-versions handling to update-versions in LRM this should not change kernel crank proceedure. The cycle proceedure will need a new step to update the shared kernel-versions dataset before cranking commences. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937078] [NEW] Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
Public bug reported:
SRU Justification
[Impact]
Customers have degraded network performance on Hyper-V/Azure
This is a request to pick up a patch from the upstream, the patch fixes
an issue with Ubuntu as a hyper-v and Azure guest. This patch need to
get picked up for 20.04, 18.04. The link to the upstream patch follows:
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-
fixes&id=7c9ff3d61b253715dcf968a6307af148c9b2
Description of issue and solution:
The vmbus module uses a rotational algorithm to assign target CPUs to
a device's channels. Depending on the timing of different device's channel
offers, different channels of a device may be assigned to the same CPU.
For example on a VM with 2 CPUs, if NIC A and B's channels are offered
in the following order, NIC A will have both channels on CPU0, and
NIC B will have both channels on CPU1 -- see below. This kind of
assignment causes RSS load that is spreading across different channels
to end up on the same CPU.
Timing of channel offers:
NIC A channel 0
NIC B channel 0
NIC A channel 1
NIC B channel 1
VMBUS ID 14: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {cab064cd-1f31-47d5-a8b4-9d57e320cccd}
Sysfs path: /sys/bus/vmbus/devices/cab064cd-1f31-47d5-a8b4-9d57e320cccd
Rel_ID=14, target_cpu=0
Rel_ID=17, target_cpu=0
VMBUS ID 16: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {244225ca-743e-4020-a17d-d7baa13d6cea}
Sysfs path: /sys/bus/vmbus/devices/244225ca-743e-4020-a17d-d7baa13d6cea
Rel_ID=16, target_cpu=1
Rel_ID=18, target_cpu=1
Update the vmbus CPU assignment algorithm to avoid duplicate CPU
assignments within a device.
The new algorithm iterates num_online_cpus + 1 times.
The existing rotational algorithm to find "next NUMA & CPU" is still here.
But if the resulting CPU is already used by the same device, it will try
the next CPU.
In the last iteration, it assigns the channel to the next available CPU
like the existing algorithm. This is not normally expected, because
during device probe, we limit the number of channels of a device to
be <= number of online CPUs.
[Test Plan]
This could be tough to test as the patch fixes a race condition.
[Where problems could occur]
Network performance issues could persist.
[Other Info]
SF:#00315347
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1937078
Title:
Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
Status in linux package in Ubuntu:
New
Bug description:
SRU Justification
[Impact]
Customers have degraded network performance on Hyper-V/Azure
This is a request to pick up a patch from the upstream, the patch
fixes an issue with Ubuntu as a hyper-v and Azure guest. This patch
need to get picked up for 20.04, 18.04. The link to the upstream patch
follows:
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-
fixes&id=7c9ff3d61b253715dcf968a6307af148c9b2
Description of issue and solution:
The vmbus module uses a rotational algorithm to assign target CPUs to
a device's channels. Depending on the timing of different device's channel
offers, different channels of a device may be assigned to the same CPU.
For example on a VM with 2 CPUs, if NIC A and B's channels are offered
in the following order, NIC A will have both channels on CPU0, and
NIC B will have both channels on CPU1 -- see below. This kind of
assignment causes RSS load that is spreading across different channels
to end up on the same CPU.
Timing of channel offers:
NIC A channel 0
NIC B channel 0
NIC A channel 1
NIC B channel 1
VMBUS ID 14: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {cab064cd-1f31-47d5-a8b4-9d57e320cccd}
Sysfs path: /sys/bus/vmbus/devices/cab064cd-1f31-47d5-a8b4-9d57e320cccd
Rel_ID=14, target_cpu=0
Rel_ID=17, target_cpu=0
VMBUS ID 16: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {244225ca-743e-4020-a17d-d7baa13d6cea}
Sysfs path: /sys/bus/vmbus/devices/244225ca-743e-4020-a17d-d7baa13d6cea
Rel_ID=16, target_cpu=1
Rel_ID=18, target_cpu=1
Update the vmbus CPU assignment algorithm to avoid duplicate CPU
assignments within a device.
The new algorithm iterates num_online_cpus + 1 times.
The existing rotational algorithm to find "next NUMA & CPU" is still here.
But if the resulting CPU is already used by the same device, it will try
the next CPU.
In the last iteration, it assigns the channel to the next available CPU
like the existing algorithm. This is not normally expected, because
during device probe, we limit the number of channels of a device to
be <= number of online CPUs.
[Tes
[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
Thanks. This is now fixed for me with the 470.57.02 and the 460.91.03. drivers from the normal repositories in 21.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-465 package in Ubuntu: Triaged Bug description: I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute Jun 03 16:26:57 willow kernel: Oops: [#1] SMP PTI Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P OE 5.11.0-18-generic #19-Ubuntu Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019 Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09: 8e318220acb8 Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 R12: 0400 Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 R15: 0800 Jun 03 16:26:57 willow kernel: FS: 7f5807f38a40() GS:8e3466dc() knlGS: Jun 03 16:26:57 willow kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 CR4: 003706e0 Jun 03 16:26:57 willow kernel: DR0: DR1: DR2: Jun 03 16:26:57 willow kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jun 03 16:26:57 willow kernel: Call Trace: Jun 03 16:26:57 willow kernel: ? _nv015556rm+0x7fd/0x1020 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv027155rm+0x22c/0x4f0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017787rm+0x303/0x5e0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017789rm+0xe1/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv022829rm+0xed/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv023065rm+0x30/0x60 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv000704rm+0x16da/0x22b0 [nvidia] Jun 03 16:26:57 willow kernel: ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 03 16:26:57 willow kernel: ? nv_open_device+0x122/0x8e0 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_open+0x2b7/0x560 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 03 16:26:57 willow kernel: ? chrdev_open+0xf7/0x220 Jun 03 16:26:57 willow kernel: ? cdev_device_add+0x90/0x90 Jun 03 16:26:57 willow kernel: ? do_dentry_open+0x156/0x370 Jun 03 16:26:57 willow kernel: ? vfs_open+0x2d/0x30 Jun 03 16:26:57 willow kernel: ? do_open+0x1c3/0x340 Jun 03 16:26:57 willow kernel: ? path_openat+0x10a/0x1d0 Jun 03 16:26:57 willow kernel: ? do_filp_open+0x8c/0x130 Jun 03 16:26:57 willow kernel: ? __check_object_size+0x1c/0x20 Jun 03 16:26:57 willow kernel: ? do_sys_openat2+0x9b/0x150 Jun 03 16:26:57 willow kernel: ? __x64_sys_openat+0x56/0x90 Jun 03 16:26:57 willow kernel: ? do_syscall_64+0x38/0x90 Jun 03 16:26:57 willow kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) > Jun 03 16:26:57 willow kernel: sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c> Jun 03 16:26:57 willow kernel: CR2: 0170 Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]--- Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel:
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package fabric-manager-460 -
460.91.03-0ubuntu1
---
fabric-manager-460 (460.91.03-0ubuntu1) impish; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
16:25:04 +0200
** Changed in: fabric-manager-460 (Ubuntu)
Status: In Progress => Fix Released
** Changed in: libnvidia-nscq-450 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package libnvidia-nscq-450 -
450.142.00-0ubuntu1
---
libnvidia-nscq-450 (450.142.00-0ubuntu1) impish; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
16:56:59 +0200
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-460 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update includes fixes for the following CVEs:
CVE-2021-1093
CVE-2021-1094
CVE-2021-1095
To manage notifications
[Kernel-packages] [Bug 1926062] Please test proposed package
Hello Jatin, or anyone else affected, Accepted gnome-settings-daemon into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-settings- daemon/3.36.1-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in gnome-settings-daemon source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Released Status in gnome-settings-daemon source package in Hirsute: Fix Committed Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06
[Kernel-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Hello Jatin, or anyone else affected, Accepted gnome-settings-daemon into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-settings- daemon/3.38.1-3ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-settings-daemon (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute ** Changed in: gnome-settings-daemon (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in gnome-settings-daemon source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Released Status in gnome-settings-daemon source package in Hirsute: Fix Committed Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvr
[Kernel-packages] [Bug 1906418] Re: igc driver for Comet Lake onboard 15f3 NIC drops all igmp packets
Same here. Tiger Canyon Intel NUC 11 Pro NUC11TNKi5 Ethernet Controller i225-LM 20.04.2 LTS (Focal Fossa) 5.4.0-77-generic #86-Ubuntu *-network description: Ethernet interface product: Intel Corporation vendor: Intel Corporation physical id: 0 bus info: pci@:58:00.0 logical name: enp88s0 version: 03 serial: size: 1Gbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=igc driverversion=0.0.1-k duplex=full ip=192.168.2.156 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s resources: irq:17 memory:6a20-6a2f memory:6a30-6a303fff cat /sys/devices/pci:00/:00:1d.0/:58:00.0/net/enp88s0/statistics/multicast 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906418 Title: igc driver for Comet Lake onboard 15f3 NIC drops all igmp packets Status in linux package in Ubuntu: Confirmed Bug description: This is occurring on Ubuntu 20.04 with kernel 5.4.0-56-generic. To demonstrate, run $ sudo tcpdump -nv -ienp4s0 igmp (adjusting the interface name appropriately). The result will be 0 packets captured, even though all other Ubuntu systems on the same ethernet lan are reporting igmp queries from the router and responding with reports every minute or so. One consequence of this is that a CUPS server using the Comet Lake onboard ethernet controller cannot be detected by any clients, except within the first 120 seconds after restarting the avahi-daemon. Since the Comet Lake server does not receive the igmp queries, it does not respond with a report and so the router unsubscribes the interface from the multicast group that is used by avahi and bonjour. This makes the CUPS server disappear. The output of ubuntu-bug linux is attached. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: culler 2071 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-17 (13 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. Z490I AORUS ULTRA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=bdba1f28-6903-467f-abfa-10c6bee47cd7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-56-generic N/A linux-backports-modules-5.4.0-56-generic N/A linux-firmware1.187.4 Tags: focal Uname: Linux 5.4.0-56-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/03/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6b dmi.board.asset.tag: Default string dmi.board.name: Z490I AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6b:bd11/03/2020:svnGigabyteTechnologyCo.,Ltd.:pnZ490IAORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnZ490IAORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Z490 MB dmi.product.name: Z490I AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934878] Re: Mute/mic LEDs no function on some HP platfroms
This bug is awaiting verification that the 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-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1934878 Title: Mute/mic LEDs no function on some HP platfroms 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 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 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 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 Bug description: [Impact] The mic mute/audio mute LEDS are not work on 1) HP ProBook 630 G8 Notebook PC 2) HP ProBook 445 G8 Notebook PC 3) HP ProBook 450 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934239] Re: mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC
This bug is awaiting verification that the 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-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1934239 Title: mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook 830 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package nvidia-settings - 470.57.01-0ubuntu1
---
nvidia-settings (470.57.01-0ubuntu1) impish; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Mon, 12 Jul 2021
16:13:23 +0200
** Changed in: nvidia-settings (Ubuntu)
Status: In Progress => Fix Released
** Changed in: fabric-manager-450 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
Fix Released
Status in fabric-manager-460 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Release
[Kernel-packages] [Bug 1934293] Re: Add l2tp.sh in net from ubuntu_kernel_selftests back
This bug is awaiting verification that the 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 ** Tags added: verification-needed-focal -- 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/1934293 Title: Add l2tp.sh in net from ubuntu_kernel_selftests back Status in ubuntu-kernel-tests: In Progress 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 source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.13 source package in Groovy: Invalid 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 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 Bug description: [Impact] We have this test disabled intentionally in the past because of the lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" in our kernels. The way we disable it is to override the executable bit with our autotest-client-tests suite [1], but this makes the test suite complain about script is not executable. Henceforth we further disable it by removing it from the Makefile in the patch "UBUNTU: SAUCE: selftests/net -- disable timeout" Now with commit 27d53323664c54 landed and l2tp.sh test re-enabled in our test suite [2], we still need to revert that SAUCE patch to get it tested. [1] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=05d7eebf32c6872ebce6c9e5275b1ff9d91ecd16 [2] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d [Fix] Revert "UBUNTU: SAUCE: selftests/net -- disable timeout" This test only exists in our tree since Focal. [Test] Run the net test suite in kselftest with patched source tree: sudo make -C linux/tools/testing/selftests TARGETS=net run_tests The l2tp.sh test will be executed. [Where problems could occur] This is only for testing tools, however if commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" didn't land properly we might crash our testing node like in bug 1854968. Also, we might see new failures caused by this test in the test report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
This bug was fixed in the package fabric-manager-450 -
450.142.00-0ubuntu1
---
fabric-manager-450 (450.142.00-0ubuntu1) impish; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
15:51:12 +0200
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
Fix Released
Status in fabric-manager-460 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Triaged
Status in linux-restricted-modules source package in Groovy:
Triaged
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
In Progress
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update includes fixes for the following CVEs:
CVE-2021-1093
CVE-2021-1094
CVE-2021-1095
To manage notificatio
[Kernel-packages] [Bug 1934293] Re: Add l2tp.sh in net from ubuntu_kernel_selftests back
This bug is awaiting verification that the 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- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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! -- 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/1934293 Title: Add l2tp.sh in net from ubuntu_kernel_selftests back Status in ubuntu-kernel-tests: In Progress 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 source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.13 source package in Groovy: Invalid 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 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 Bug description: [Impact] We have this test disabled intentionally in the past because of the lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" in our kernels. The way we disable it is to override the executable bit with our autotest-client-tests suite [1], but this makes the test suite complain about script is not executable. Henceforth we further disable it by removing it from the Makefile in the patch "UBUNTU: SAUCE: selftests/net -- disable timeout" Now with commit 27d53323664c54 landed and l2tp.sh test re-enabled in our test suite [2], we still need to revert that SAUCE patch to get it tested. [1] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=05d7eebf32c6872ebce6c9e5275b1ff9d91ecd16 [2] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d [Fix] Revert "UBUNTU: SAUCE: selftests/net -- disable timeout" This test only exists in our tree since Focal. [Test] Run the net test suite in kselftest with patched source tree: sudo make -C linux/tools/testing/selftests TARGETS=net run_tests The l2tp.sh test will be executed. [Where problems could occur] This is only for testing tools, however if commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" didn't land properly we might crash our testing node like in bug 1854968. Also, we might see new failures caused by this test in the test report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934864] Re: [SRU][OEM-5.10/H] Fix HDMI output issue on Intel TGL GPU
This bug is awaiting verification that the 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-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1934864 Title: [SRU][OEM-5.10/H] Fix HDMI output issue on Intel TGL GPU Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: Fix Committed Bug description: SRU justification: [Impact] When plugin HDMI cable, no HDMI output, kernel reported error: [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port [Fix] Legacy LSPCON chip from MCA and Parade is only used for platforms, Limit the support between GEN9 and GEN10. The commit is already in 5.13, so only SRU for oem-5.10 and hirsute. [Test] Verified on hardware, HDMI output works fine. [Where problems could occur] The HDMI output may break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1934864/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934110] Re: ubuntu-host driver lacks lseek ops
This bug is awaiting verification that the 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1934110
Title:
ubuntu-host driver lacks lseek ops
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Bug description:
[ SRU Justification ][GROOVY][HIRSUTE][IMPISH]
== Impact ==
The ubuntu-host driver lacks procfs lseek ops and lseeking on the
procfs esm-token file will jump to a NULL address causing the
following splat:
942.470568] BUG: kernel NULL pointer dereference, address:
[ 942.471157] #PF: supervisor instruction fetch in kernel mode
[ 942.471724] #PF: error_code(0x0010) - not-present page
[ 942.472297] PGD 0 P4D 0
[ 942.472867] Oops: 0010 [#1] SMP PTI
[ 942.473435] CPU: 2 PID: 5661 Comm: stress-ng Not tainted 5.13.0-9-generic
#9
[ 942.474012] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0
02/06/2015
[ 942.474599] RIP: 0010:0x0
[ 942.475194] Code: Unable to access opcode bytes at RIP 0xffd6.
[ 942.475792] RSP: 0018:aacf80ff7eb8 EFLAGS: 00010246
[ 942.476383] RAX: RBX: 9eaa8a175240 RCX:
0001
[ 942.476986] RDX: RSI: RDI:
9eaa838d5800
[ 942.477600] RBP: aacf80ff7ed0 R08: 4000 R09:
0004
[ 942.478203] R10: 0002 R11: R12:
[ 942.478800] R13: R14: ffea R15:
9eaa838d5800
[ 942.479399] FS: 7f998d487f00() GS:9eaaffc8()
knlGS:
[ 942.480006] CS: 0010 DS: ES: CR0: 80050033
[ 942.480607] CR2: ffd6 CR3: 00010a774002 CR4:
00370ee0
[ 942.481219] DR0: DR1: DR2:
[ 942.481855] DR3: DR6: fffe0ff0 DR7:
0400
[ 942.482458] Call Trace:
[ 942.483052] proc_reg_llseek+0x4e/0x80
[ 942.483646] ? __fdget_pos+0x43/0x50
[ 942.484234] ksys_lseek+0x84/0xc0
[ 942.484815] __x64_sys_lseek+0x1a/0x20
[ 942.485412] do_syscall_64+0x61/0xb0
[ 942.485966] ? asm_exc_page_fault+0x8/0x30
[ 942.486476] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 942.486994] RIP: 0033:0x7f998d5c1cdb
[ 942.487512] Code: ff ff c3 0f 1f 40 00 48 8b 15 89 81 0d 00 f7 d8 64 89 02
48 c7 c0 ff ff ff ff eb ba 0f 1f 00 f3 0f 1e fa b8 08 00 00 00 0f 05 <48> 3d 00
f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 59 81 0d 00 f7 d8
[ 942.488593] RSP: 002b:7ffdf61c5328 EFLAGS: 0246 ORIG_RAX:
0008
[ 942.489148] RAX: ffda RBX: RCX:
7f998d5c1cdb
[ 942.489710] RDX: RSI: RDI:
0004
[ 942.490252] RBP: 0004 R08: 01785e4740dd R09:
562dbebb9e50
[ 942.490801] R10: 7ffdf61c5300 R11: 0246 R12:
7ffdf61c63f0
[ 942.491354] R13: 7ffdf61c53f0 R14: 0003 R15:
01e9
== Fix ==
Add the default_llseek ops:
diff --git a/ubuntu/ubuntu-host/ubuntu-host.c
b/ubuntu/ubuntu-host/ubuntu-host.c
index 1abd402..a4c0636 100644
--- a/ubuntu/ubuntu-host/ubuntu-host.c
+++ b/ubuntu/ubuntu-host/ubuntu-host.c
@@ -38,6 +38,8 @@ static ssize_t esm_token_write(struct file *f, const char
__user *buf,
static const struct proc_ops esm_token_fops = {
.proc_read = esm_token_read,
.proc_write = esm_token_write,
+ .proc_lseek = default_llseek,
+
};
== Test plan ==
modrobe ubuntu-host
stress-ng --procfs 0 -t 60
without the fix we hit the splat. With the fix it's OK.
== Where problems could occur ==
This one liner adds the missing proc_lseek op. It is hard to see where
it can cause a regression since it affects the driver no other way. I
doubt any code is relying on the current semantics of lseek not
working.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934110/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://l
[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H
This bug is awaiting verification that the 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 ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1880645 Title: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released 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.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.13 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid 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.6 source package in Hirsute: Invalid Bug description: [Impact] The IPv6: mtu exception plus redirect test in icmp_redirect.sh test from kselftest/net is expected to fail due to a known bug in the IPv6 logic. When trying to run this test you will see this sub test fail with: TEST: IPv6: mtu exception plus redirect [FAIL] and thus causing non-zero return value for this script. [Fix] * 0a36a75c681880 selftests: icmp_redirect: support expected failures This fix can be cherry-picked into all affected series. And it has already landed on Unstable, test passed with Impish 5.13. Although we have this script in Focal kernel as well, but it's not being executed at all. This is another issue that will be dealt in a different bug report. [Test] Run the patched icmp_redirect.sh test manually in tools/testing/selftests/net, this sub-test will be marked as XFAIL and the return value of this script will be 0: $ sudo ./icmp_redirect.sh # Routing with nexthop objects and VRF # TEST: IPv6: mtu exception plus redirect [XFAIL] Tests passed: 36 Tests failed: 0 Tests xfailed: 4 $ echo $? 0 [Where problems could occur] Change limited to testing tool, not affecting actual kernel functionality. The only possible issue that I can think of is that as this script is no longer complaining about this failure, people might forgot there is such an issue exist in ipv6. [Original Bug Report] Issue found on Focal 5.6.0-1011.11-oem ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./icmp_redirect.sh ### Legacy routing ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ]
[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H
This bug is awaiting verification that the 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- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1880645 Title: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released 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.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.13 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid 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.6 source package in Hirsute: Invalid Bug description: [Impact] The IPv6: mtu exception plus redirect test in icmp_redirect.sh test from kselftest/net is expected to fail due to a known bug in the IPv6 logic. When trying to run this test you will see this sub test fail with: TEST: IPv6: mtu exception plus redirect [FAIL] and thus causing non-zero return value for this script. [Fix] * 0a36a75c681880 selftests: icmp_redirect: support expected failures This fix can be cherry-picked into all affected series. And it has already landed on Unstable, test passed with Impish 5.13. Although we have this script in Focal kernel as well, but it's not being executed at all. This is another issue that will be dealt in a different bug report. [Test] Run the patched icmp_redirect.sh test manually in tools/testing/selftests/net, this sub-test will be marked as XFAIL and the return value of this script will be 0: $ sudo ./icmp_redirect.sh # Routing with nexthop objects and VRF # TEST: IPv6: mtu exception plus redirect [XFAIL] Tests passed: 36 Tests failed: 0 Tests xfailed: 4 $ echo $? 0 [Where problems could occur] Change limited to testing tool, not affecting actual kernel functionality. The only possible issue that I can think of is that as this script is no longer complaining about this failure, people might forgot there is such an issue exist in ipv6. [Original Bug Report] Issue found on Focal 5.6.0-1011.11-oem ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./icmp_redirect.sh ### Legacy routing ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirec
[Kernel-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
This bug is awaiting verification that the 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 in Ubuntu. https://bugs.launchpad.net/bugs/1925057 Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound Status in linux package in Ubuntu: Fix Released Bug description: Hello, I'm using Ubuntu together with Windows on my laptop. If I boot in Ubuntu after Windows sound doesn't work well (instead of system sounds I can hear only shot noise). To fix the issue I need to completely shut down the system (call Power Off via Ubuntu GUI) and then boot again in Ubuntu. Please note, that reboot (called via Ubuntu GUI) doesn't help to fix the issue. Expected result: sound works well regardless of boot history. Actual result: every time I boot in Ubuntu after Windows sound doesn't work. Issue occurrence: 100%. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thank you in advance! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1640 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 19:37:56 2021 InstallationDate: Installed on 2021-03-06 (43 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 'module-null-sink' was still loaded! кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected
This bug is awaiting verification that the 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- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918427 Title: curtin: install flash-kernel in arm64 UEFI unexpected Status in cloud-images: Confirmed Status in curtin package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in curtin source package in Focal: New Status in linux source package in Focal: Fix Committed Status in curtin source package in Hirsute: New Status in linux source package in Hirsute: Fix Released Bug description: [Impact (linux)] The only package that currently satisfies the bootloader Recommends relationship on ARM systems is flash-kernel. This ignores EFI-based systems, which will instead require GRUB. Our installers know to install GRUB anyway - but flash-kernel also gets installed. Normally flash-kernel realizes it is not needed and just exits - so the impact is limited to wasting space and CPU cycles on each kernel update. However, there can be cases where calling flash-kernel can cause problems. The original report here describes one where flash-kernel thinks it recognizes the system and tries to run anyway, when in fact GRUB is the correct boot loader. [Test Case (linux)] On an arm64 system, confirm that grub-efi-arm64 is an option in the Recommends field: $ apt show linux-image-unsigned-5.4.0-78-generic | grep Recommends WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Recommends: flash-kernel | grub-efi-arm64, initramfs-tools | linux- initramfs-tool [What Could Go Wrong (linux)] First let me describe the mitigations against something going wrong. The proposed patch was already in the hirsute kernel at the time of hirsute GA, so it's had some real world testing, including in our installers. In addition, the patch still leaves flash-kernel as the *default* bootloader Recommends (first in the |'d list) - it only adds grub-efi-arm64 as a secondary option, preventing the installation of flash-kernel if GRUB is already there. So, the only scenario where I can see a problem might be if something depends on flash-kernel getting installed due to a Recommends even though GRUB is already present. = Original Report Follows = I used APM Mustang which flash-kernel supported in u-boot mode. But I used it with UEFI environment. It will cause fatal error when I used ARM64 ubuntu live server ISO to install system. In code[1], this will not install `flash-kernel` for APM Mustang because of UEFI. So that means code[2] will not disable `flash-kernel` in target system, only disable `update-initramfs`. When curtin execute to `install_kernel` stage, code[3,4] will not install `flash-kernel` either. But in code[5], it will install `linux-generic`. `linux-generic` has a long dependency tree and it will get `flash-kernel` in Recommended field. Apt by default will install Recommended package before kernel is installed.[6] So it will still execute `zz-flash-kernel` and `flash-kernel` when installing kernel. But system didn't create any `initrd.img` ever because curtin disable `update-initramfs` in code[2]. This will cause that `flash-kernel` cannot find `initrd.img.` and fail when installing it. This issue didn't effect all ARM64 UEFI platform because `flash-kernel` didn't support them and skip.[7] I'm not sure which is best solution for this. But I think we should apply PR-27 in `flash-kernel`[8] for enhancement and fix curtin process with this patch both. If we only apply PR-27, it should work fine as well because it will be skipped when detecting UEFI and install `flash-kernel` before `disable_update_initranfs` in ARM platform without UEFI.[9] [Patch-1,2,3] might have side effect. Picking one patch for curtin should be enough. But I need your advice for this to determine which one is better for curtin. There are two categories 1. avoid installing flash-kernel if no need, [Patch1,2] 2. always install flash-kernel in arm/arm64 and make sure it be installed before code[2] [Patch3] (I will attach patch in reply.) Thanks a lot Regards, Date [1] https://github.com/canonical/curtin/blob/master/curtin/deps/__init__.py#L57-L58 [2] https://github.com/canonical/curtin/bl
[Kernel-packages] [Bug 1933268] Re: net kselftest failures in the tls bidir test case
This bug is awaiting verification that the 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 in Ubuntu. https://bugs.launchpad.net/bugs/1933268 Title: net kselftest failures in the tls bidir test case Status in linux package in Ubuntu: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] The tls bidir test from the network kselftests fails with the ChaCha cipher: # RUN tls.12_chacha.bidir ... # tls.c:845:bidir:Expected ret (-1) == 0 (0) # bidir: Test terminated by assertion # FAIL tls.12_chacha.bidir This is a problem with the test. The test fixture setup configures tls in one direction on the test socket pair according to the cipher being tested. The test case configures tls in the other direction, however it always configures for GCM regardless of the cipher being tested. When the test cipher is ChaCha the setsockopt() calls fail as the cipher is required to be the same in both directions. [Test Plan] Run the tls test from the net kselftests and confirm that the bidir test now passes when the test cipher is ChaCha. [Where problems could occur] This is a fix for a test case and should have no user impact. A serious problem in the test case might cause passing test cases to fail or prevent subsequent test cases from running. Any such issues should be caught during testing in -proposed before releasing kernels to users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933518] Re: Update SmartPQI driver
This bug is awaiting verification that the 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 in Ubuntu. https://bugs.launchpad.net/bugs/1933518 Title: Update SmartPQI driver Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] Improves support in SmartPQI for most recent controllers [Fixes] All are in mainline currently and cleanly cherry pick into Hirsute. c64aab41c5e1 scsi: smartpqi: Remove unused functions 5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static checker issue 667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045 75fbeacca3ad scsi: smartpqi: Add new PCI IDs 43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from hibernation d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs 18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets 55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and target_port_protocols ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf() 3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues 66f1c2b40270 scsi: smartpqi: Update device scan operations 2790cd4d3f6a scsi: smartpqi: Update OFA management 5be9db069d3f scsi: smartpqi: Update RAID bypass handling 9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown 37f3318199ce scsi: smartpqi: Synchronize device resets with mutex 4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA 06b41e0d1800 scsi: smartpqi: Update event handler 7a84a821f194 scsi: smartpqi: Add support for wwid ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds 99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks 5be746d7d74b scsi: smartpqi: Add host level stream detection enable c7ffedb3a774 scsi: smartpqi: Add stream detection 583891c9e509 scsi: smartpqi: Align code with oob driver 598bef8d7942 scsi: smartpqi: Add support for long firmware version f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and feature bits 7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes 6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes 1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code 281a817f232e scsi: smartpqi: Refactor aio submission code 2708a25643ab scsi: smartpqi: Add support for new product ids b622a601a13a scsi: smartpqi: Correct request leakage during reset operations c6d3ee209b9e scsi: smartpqi: Use host-wide tag space The patches they provided only apply the hunk that applies to the SmartPQI driver. This commit was a much wider commit that removes references to MODULE_SUPPORTED_DEVICE in many drivers across the kernel. 6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE [Testing] On machines equipped with SmartPQI SCSI controller: 1. reboot tests 2. insmod/rmmod tests 3. fio testing: no performance regressions [Regression Risk] Patchset changes only smartpqi driver so regression is limited to systems equipped with this SCSI device. On such SmartPQI-equipped systems the patchset can cause data corruption, data loss or unavailability of SCSI storage and boot failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933508] Re: mute/micmute LEDs no function on HP EliteBook x360 830 G8
This bug is awaiting verification that the 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-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1933508 Title: mute/micmute LEDs no function on HP EliteBook x360 830 G8 Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook x360 830 G8 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 is awaiting verification that the 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 in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: New Bug description: Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)
This bug is awaiting verification that the 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-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928889 Title: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range) Status in ubuntu-kernel-tests: In Progress 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 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 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 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 Bug description: [Impact] If there is no devlink device available, the devlink_port_split.py in kselftest/net will fail with: # selftests: net: devlink_port_split.py # Traceback (most recent call last): # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in # main() # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main # dev = list(devs.keys())[0] # IndexError: list index out of range not ok 43 selftests: net: devlink_port_split.py # exit=1 [Fix] * 25173dd4093a24 selftests: net: devlink_port_split.py: skip the test if no devlink device This test only exist in our source tree since Hirsute, this patch can be cherry-picked into all affected kernels. [Test Plan] Run this test manually from the patched source tree, the test will be skipped when there is no devlink device: # selftests: net: devlink_port_split.py # no devlink device was found, test skipped ok 7 selftests: net: devlink_port_split.py # SKIP [Where problems could occur] Change limited to testing tool, if this change is incorrect it might cause false-negative result in our test report. [Original Bug Report] This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz 17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:39:37 DEBUG| [stdout] # Traceback (most recent call last): 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in 17:39:37 DEBUG| [stdout] # main() 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main 17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0] 17:39:37 DEBUG| [stdout] # IndexError: list index out of range 17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1928889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-package
[Kernel-packages] [Bug 1932367] Re: Pixel format change broken for Elgato Cam Link 4K
This bug is awaiting verification that the 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 in Ubuntu. https://bugs.launchpad.net/bugs/1932367 Title: Pixel format change broken for Elgato Cam Link 4K Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Triaged Bug description: [Impact] The Elgato Cam Link 4K HDMI video capture card reports to support three different pixel formats, where the first format depends on the connected HDMI device. ``` $ v4l2-ctl -d /dev/video0 --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [1]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [2]: 'YU12' (Planar YUV 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) ``` Changing the pixel format to anything besides the first pixel format does not work: ``` $ v4l2-ctl -d /dev/video0 --try-fmt-video pixelformat=YU12 Format Video Capture: Width/Height : 3840/2160 Pixel Format : 'NV12' (Y/CbCr 4:2:0) Field : None Bytes per Line: 3840 Size Image: 12441600 Colorspace: sRGB Transfer Function : Rec. 709 YCbCr/HSV Encoding: Rec. 709 Quantization : Default (maps to Limited Range) Flags : ``` User space applications like VLC might show an error message on the terminal in that case: ``` libv4l2: error set_fmt gave us a different result than try_fmt! ``` Depending on the error handling of the user space applications, they might display a distorted video, because they use the wrong pixel format for decoding the stream. [Fix] The Elgato Cam Link 4K responds to the USB video probe VS_PROBE_CONTROL/VS_COMMIT_CONTROL with a malformed data structure: The second byte contains bFormatIndex (instead of being the second byte of bmHint). The first byte is always zero. The third byte is always 1. The firmware bug was reported to Elgato on 2020-12-01 and it was forwarded by the support team to the developers as feature request. There is no firmware update available since then. The latest firmware for Elgato Cam Link 4K as of 2021-03-23 has MCU 20.02.19 and FPGA 67. Therefore correct the malformed data structure for this device. The change was successfully tested with VLC, OBS, and Chromium using different pixel formats (YUYV, NV12, YU12), resolutions (3840x2160, 1920x1080), and frame rates (29.970 and 59.940 fps). [Test Case] Connect an input device to the Cam Link 4K and try all three pixel formats with VLC: vlc v4l2:///dev/video0 --v4l2-chroma=NV12 vlc v4l2:///dev/video0 --v4l2-chroma=YU12 [Other Info] The fix was reviewed and accepted by the subsystem maintainer and will be included upstream: https://git.linuxtv.org/media_stage.git/commit/?id=4c6e0976295add7f0ed94d276c04a3d6f1ea8f83 Attached a backported patch for Ubuntu. I successfully tested it with Linux 5.11 on Ubuntu 21.04 and Linux 5.8 on Ubuntu 20.10. It should work on older kernel versions as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927749] Re: ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8
This bug is awaiting verification that the 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 in Ubuntu. https://bugs.launchpad.net/bugs/1927749 Title: ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-aws source package in Focal: New Status in linux source package in Groovy: Fix Committed Status in linux-aws source package in Groovy: New Status in linux source package in Hirsute: Fix Committed Status in linux-aws source package in Hirsute: New Status in linux source package in Impish: In Progress Status in linux-aws source package in Impish: New Bug description: [Impact] arm64 only focal/aws 5.8.0-1031.33~20.04.1-aws and 5.8.0-1032.34~20.04.1-aws - regression. Works fine on previous Focal cycle (5.8.0-1028.30~20.04.3-aws) and current Groovy 5.8. 12. 05/06 07:01:39 DEBUG| utils:0153| [stdout] TAP version 13 13. 05/06 07:01:39 DEBUG| utils:0153| [stdout] 1..1 14. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 15. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 16. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 17. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 18. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 19. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check [PASS] 20. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 21. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 22. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 23. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct functions against tracers [UNRESOLVED] 24. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] 25. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - add/remove kprobe events [PASS] 26. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - add/remove synthetic events [PASS] 27. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event - selective clear (compatibility) [PASS] 28. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event - generic clear event [PASS] 29. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with event level files [PASS] 30. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [15] event tracing - restricts events based on pid notrace filtering [FAIL] 31. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [16] event tracing - restricts events based on pid [PASS] 32. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [17] event tracing - enable/disable with subsystem level files [PASS] 33. 05/06 07:01:46 DEBUG| utils:0153| [stdout] # [18] event tracing - enable/disable with top level files [PASS] [Test Plan] * Run ftrace test from kernel selftests. [Where problems could occur] * Only kernel selftests should be affected. * ftrace test can have false positives or negatives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934759] Re: Enable fib-onlink-tests.sh and msg_zerocopy.sh in kselftests/net on Bionic
This bug is awaiting verification that the 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/1934759 Title: Enable fib-onlink-tests.sh and msg_zerocopy.sh in kselftests/net on Bionic Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Found this issue while debugging missing tests with bug 1934282. On Bionic there are 3 scripts that are not in the Makefile of the kselftests/net: $ for file in $(ls *.sh); do grep -q $file Makefile || echo $file; done fib-onlink-tests.sh in_netns.sh msg_zerocopy.sh [Fix] * 830669e691464c selftests/net: enable msg_zerocopy test * 1751eb42ddb56b selftests: net: use TEST_PROGS_EXTENDED * a52b839752aab7 selftests: Add fib-onlink-tests.sh to TEST_PROGS * Set fib-onlink-tests.sh as executable They all need to be backported to Bionic. For the in_netns.sh it's not causing any issue to us when being called by run_afpackettests, but I think it's no harm to fix it to reduce confusions. Commit 1751eb42ddb56b will replace the change in 9faedd64 selftests: net: add in_netns.sh TEST_GEN_PROGS_EXTENDED [1] and 5ff9c1a3 selftests: net: add in_netns.sh to TEST_PROGS [2], and since we need to backport it there is no need to work on these two. [1] https://github.com/torvalds/linux/commit/9faedd643fd9 [2] https://github.com/torvalds/linux/commit/5ff9c1a3dd92 [Test] Run the "net" test suite in the kselftest directory from a patched source tree. fib-onlink-tests.sh and msg_zerocopy.sh tests will be executed. [Where problems could occur] This change will bring in more test for our SRU, we might see new failures because of these test in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934709] Re: btrfs: Automatic balance returns -EUCLEAN and leads to forced readonly filesystem
This bug is awaiting verification that the 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/1934709
Title:
btrfs: Automatic balance returns -EUCLEAN and leads to forced readonly
filesystem
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
BugLink: https://bugs.launchpad.net/bugs/1934709
[Impact]
During an automatic balance, users may encounter an error when writing
the transaction log to disk, when the log tree is being parsed, which
forces the filesystem to be remounted read-only and outputs the
following kernel oops:
BTRFS: error (device dm-14) in balance_level:1962: errno=-117 unknown
BTRFS info (device dm-14): forced readonly
BTRFS: Transaction aborted (error -117)
WARNING: CPU: 7 PID: 10818 at
/build/linux-99Rib2/linux-4.15.0/fs/btrfs/tree-log.c:2908
btrfs_sync_log+0xa28/0xbc0 [btrfs]
CPU: 7 PID: 10818 Comm: qemu-system-s39 Tainted: G OE
4.15.0-136-generic #140-Ubuntu
Hardware name: IBM 3907 LR1 A00 (LPAR)
Krnl PSW : 76bc1d64 9cc65255 (btrfs_sync_log+0xa28/0xbc0
[btrfs])
R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3
Krnl GPRS: 007899a6 0006 0027 0007
03ff801fdd8c 0002394c 0053650a7000 ff8b
00536b7f6000 0053ff8b 0053650a3800 005385935000
00532054de01 005385935290 03ff801fdd8c 004eebb1fae0
Krnl Code: 03ff801fdd80: c022a032 larl%r2,03ff80251de4
03ff801fdd86: c0e5fffb2181 brasl %r14,03ff80162088
#03ff801fdd8c: a7f40001 brc 15,03ff801fdd8e
>03ff801fdd90: e3a0f0a80004 lg %r10,168(%r15)
03ff801fdd96: b9040057 lgr %r5,%r7
03ff801fdd9a: a7490b5c lghi%r4,2908
03ff801fdd9e: b904002a lgr %r2,%r10
03ff801fdda2: c032604f larl%r3,03ff80249e40
Call Trace:
([<03ff801fdd8c>] btrfs_sync_log+0xa24/0xbc0 [btrfs])
[<03ff801c74e2>] btrfs_sync_file+0x3e2/0x550 [btrfs]
[<003ce6ce>] do_fsync+0x5e/0x90
[<003ce9ca>] SyS_fdatasync+0x32/0x48
[<008ffe5c>] system_call+0xd8/0x2c8
Last Breaking-Event-Address:
[<03ff801fdd8c>] btrfs_sync_log+0xa24/0xbc0 [btrfs]
BTRFS: error (device dm-14) in btrfs_sync_log:2908: errno=-117 unknown
BTRFS error (device dm-14): pending csums is 269639680
This bug appears to be linked to bug 1933172, but is different and has
a different root cause. Again, I believe that this is a regression
introduced in the fixing of CVE-2019-19036, from 4.15.0-109-generic.
[Fix]
Analysis of the kernel oops is as follows:
The first thing we see is that BTRFS entered ERROR state with the
reason:
in balance_level:1962: errno=-117 unknown
Now errno -117 is:
100 #define EUCLEAN 117 /* Structure needs cleaning */
btrfs treats -EUCLEAN as if corruption has happened. Let's see where
this is returned from.
If we start at fs/btrfs/ctree.c in balance_level(), line 1962:
1917 static noinline int balance_level(struct btrfs_trans_handle *trans,
1918 struct btrfs_root *root,
1919 struct btrfs_path *path, int level)
1920 {
...
1958 /* promote the child to a root */
1959 child = read_node_slot(fs_info, mid, 0);
1960 if (IS_ERR(child)) {
1961 ret = PTR_ERR(child);
1962 btrfs_handle_fs_error(fs_info, ret, NULL);
1963 goto enospc;
1964 }
...
2136 }
We are in the middle of a balancing operation, and if you happen to be
familiar with how b-tree data structures work, we are promoting a
child node to a topmost root node.
The error most likely happens in read_node_slot(), with the lines
after it printing that an error has happened.
1887 static noinline struct extent_buffer *
1888 read_node_slot(struct btrfs_fs_info *fs_info, struct extent_buffer
*parent,
1889int slot)
1890 {
...
1900 btrfs_node_key_to_cpu(parent, &first_key, slot);
1901 eb = read
[Kernel-packages] [Bug 1934282] Re: Some test in kselftest/net on focal source tree were not tested at all
This bug is awaiting verification that the 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- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934282 Title: Some test in kselftest/net on focal source tree were not tested at all Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: [Impact] Found this issue while debugging devlink_port_split.py test issue in bug 1928889. There are some tests like icmp_redirect.sh, ip6_gre_headroom.sh and etc are not in the Makefile of the net directory, thus they are not tested at all. [Fix] * 919a23e9d6ccf8 selftests/net: add missing tests to Makefile Backport needed for Focal as we only have these tests unadded: $ for file in $(ls *.sh); do grep -q $file Makefile || echo $file; done fib_nexthop_multiprefix.sh fib_nexthops.sh icmp_redirect.sh ip6_gre_headroom.sh route_localnet.sh [Test] Run the "net" test suite in the kselftest directory from a patched source tree. These tests will be executed. [Where problems could occur] This change will bring in more tests for our SRU, we might see new failures because of these test in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933172] Re: btrfs: Attempting to balance a nearly full filesystem with relocated root nodes fails
This bug is awaiting verification that the 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/1933172 Title: btrfs: Attempting to balance a nearly full filesystem with relocated root nodes fails Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1933172 [Impact] If you attempt to balance a btrfs filesystem that is nearly full, and this filesystem has had a lot of small, medium and large files created and deleted, such that the b-tree needs to be rotated, when the balance fails due to not having enough free space, the kernel oops, and the btrfs filesystem hangs. It doesn't appear to cause any filesystem corruption, and is reproducible every time on affected filesystems. The following oops is generated: general protection fault: [#1] SMP PTI CPU: 0 PID: 18440 Comm: btrfs Not tainted 4.15.0-136-generic #140-Ubuntu Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 RIP: 0010:btrfs_set_root_node+0x5/0x60 [btrfs] RSP: 0018:b3db890a79e0 EFLAGS: 00010282 RAX: 8d7f73861ad0 RBX: 8d7f78455708 RCX: 8d7f6d9a5390 RDX: 8d7f73861ad0 RSI: a023775cfc0348a3 RDI: 8d7f6d9a5028 RBP: b3db890a7a78 R08: 0044 R09: 0228 R10: 8d7f6d9a5000 R11: 0010 R12: b3db890a7a08 R13: 8d7f6d9a5000 R14: 8d7f6d9a5028 R15: 8d7f7456 FS: 7f48d84498c0() GS:8d7f7fc0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fe4fbc1f000 CR3: 0001799fc001 CR4: 00160ef0 Call Trace: ? commit_fs_roots+0x130/0x1b0 [btrfs] ? btrfs_run_delayed_refs.part.70+0x80/0x190 [btrfs] btrfs_commit_transaction+0x42c/0x910 [btrfs] ? start_transaction+0x191/0x430 [btrfs] relocate_block_group+0x1e7/0x640 [btrfs] btrfs_relocate_block_group+0x18f/0x280 [btrfs] btrfs_relocate_chunk+0x38/0xd0 [btrfs] __btrfs_balance+0x972/0xcd0 [btrfs] ? insert_balance_item.isra.35+0x391/0x3c0 [btrfs] btrfs_balance+0x32c/0x5a0 [btrfs] btrfs_ioctl_balance+0x320/0x390 [btrfs] btrfs_ioctl+0x5a6/0x2490 [btrfs] ? lru_cache_add_active_or_unevictable+0x36/0xb0 ? __handle_mm_fault+0x9fd/0x1290 do_vfs_ioctl+0xa8/0x630 ? btrfs_ioctl_get_supported_features+0x30/0x30 [btrfs] ? do_vfs_ioctl+0xa8/0x630 ? __do_page_fault+0x2a1/0x4b0 SyS_ioctl+0x79/0x90 do_syscall_64+0x73/0x130 entry_SYSCALL_64_after_hwframe+0x41/0xa6 RIP: 0033:0x7f48d7228317 RSP: 002b:7ffd76d03e38 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 0001 RCX: 7f48d7228317 RDX: 7ffd76d03ec8 RSI: c4009420 RDI: 0003 RBP: 7ffd76d03ec8 R08: 0078 R09: R10: 562086e7f010 R11: 0246 R12: 0003 R13: 7ffd76d057cb R14: 0002 R15: Code: 4d 85 e4 0f 84 56 fe ff ff 4d 89 04 24 41 c6 44 24 08 84 4d 89 4c 24 09 e9 42 fe ff ff 0f 0b e8 02 24 5e e0 66 90 0f 1f 44 00 00 <48> 8b 06 48 8b 0d c9 d4 99 e1 48 8b 15 d2 d4 99 e1 55 48 89 87 RIP: btrfs_set_root_node+0x5/0x60 [btrfs] RSP: b3db890a79e0 I don't see this behaviour on any upstream kernel, and the first kernel to show this behaviour is 4.15.0-109-generic. The current 4.15.0-145-generic is still affected. I believe that this is a regression introduced in the fixing of CVE-2019-19036. [Testcase] I haven't reliably been able to create a script which places a btrfs filesystem into the state necessary to reproduce this issue, so I have just provided my qcow2 image with my btrfs filesystem which reproduces the issue 100% of the time. Download the image from here (warning size is 8.0gb): https://people.canonical.com/~mruffell/sf311164/ubuntu18.04-server-2.qcow2 Make a Ubuntu 18.04 VM. Attach the ubuntu18.04-server-2.qcow2 image to a new virtio disk. Note, ubuntu18.04-server-2.qcow2 does not have an operating system, it is just a data only volume. Mount the volume: $ sudo mount /dev/vdb /mnt Attempt to balance: $ sudo btrfs filesystem balance start --full-balance /mnt Segmentation fault (core
[Kernel-packages] [Bug 1933074] Re: large_dir in ext4 broken
This bug is awaiting verification that the 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 ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933074 Title: large_dir in ext4 broken Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Triaged Bug description: == SRU, Bionic, Focal, Groovy, Hirsute, Impish == [Impact] Creating millions of files on ext4 partition with large_dir support by touching them will eventually trip an ext4 leaf node issue in the index hash. This occurs more frequently when also using smaller block sizes and ends up either with a EXIST or EUCLEAN failure. This occurs on the restart condition when performing do_split. [ Fix ] The fix protects do_split() from the restart condition, making it safe from both current and future ordering of goto statements in earlier sections of the code. The fix is from a patch sent upstream and cc'd to Ted Tso but didn't appear on the ext4 mailing list presumably because it got marked as SPAM. [ Test Case ] Without the fix touching tens of thousands of empty files will trip the issue. It seems to occur more frequently with memory pressure and smaller block sizes, e.g.: sudo mkdir -p /mnt/tmpfs /mnt/storage sudo mount -t tmpfs -o size=9000M tmpfs /mnt/tmpfs sudo dd if=/dev/urandom of=/mnt/tmpfs/ext4.img bs=1M sudo mkfs.ext4 -O large_dir -N 2100 -O dir_index /mnt/tmpfs/ext4.img -b 1024 -F sudo mount /mnt/tmpfs/ext4.img /mnt/storage and compile and run the attached C program (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933074/+attachment/5509402/+files/touch.c) that quickly populates /mnt/storage with empty files. Without the fix this will terminate with an -EEXIST or -EUCLEAN error on the file creation after several tens of thousands of files. [Where problems could occur] This changes the behaviour of the directory indexing hashing so there is a regression potential that this may introduce subsequent index hashing issues when needed (or not) to do a split. This patch seems to cover all the necessary cases, so I believe this risk is relatively low. I have also tested this on all the kernel series in the SRU with 21,000,000 files so I am confident we have enough test coverage to show the fix is OK. -- I believe, I found a bug in ext4 in recent kernel versions. I stumbled across this while I was trying to restore a backup to a new VM. How to reproduce this bug: 1. Use a virtual/physical machine with "Ubuntu 18.04.5 LTS" and kernel version 4.15.0-144-generic. 2. add a secondary disk to hold the test files. 3. prepare and mount the filesystem with enabled 'large_dir' flag: mkfs.ext4 -m0 /dev/sdb1; tune2fs -O large_dir /dev/sdb1; mkdir /mnt/storage; mount /dev/sdb1 /mnt/storage; 4. change to directory and create approx. 16 mio files cd /mnt/storage; i=0; while (( $i < 2000 )); do i=$(( $i + 1 )); (( $i % 1000 == 0 )) && echo $i; touch file_$i.dat || break; done Expected behaviour: - 20 mio files shoud be created without error What happened instead: - The loop aborts with an error message: # 16263100 # touch: cannot touch 'file_16263173.dat': Structure needs cleaning - dmesg gives a little more details: # [Mon Jun 21 03:15:18 2021] EXT4-fs error (device sdb): dx_probe:855: inode #2: block 146221: comm touch: directory leaf block found instead of index block Additional notes: - This occurs on kernel version 4.15.0-144-generic - Not sure, but I believe one test was run on 4.15.0-143-generic and failed too. - Did not check against 4.15.0-142-generic - On 4.15.0-141-generic, the problem does not exist. Behaviour is as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933074/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscr
[Kernel-packages] [Bug 1933074] Re: large_dir in ext4 broken
This bug is awaiting verification that the 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! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933074 Title: large_dir in ext4 broken Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Triaged Bug description: == SRU, Bionic, Focal, Groovy, Hirsute, Impish == [Impact] Creating millions of files on ext4 partition with large_dir support by touching them will eventually trip an ext4 leaf node issue in the index hash. This occurs more frequently when also using smaller block sizes and ends up either with a EXIST or EUCLEAN failure. This occurs on the restart condition when performing do_split. [ Fix ] The fix protects do_split() from the restart condition, making it safe from both current and future ordering of goto statements in earlier sections of the code. The fix is from a patch sent upstream and cc'd to Ted Tso but didn't appear on the ext4 mailing list presumably because it got marked as SPAM. [ Test Case ] Without the fix touching tens of thousands of empty files will trip the issue. It seems to occur more frequently with memory pressure and smaller block sizes, e.g.: sudo mkdir -p /mnt/tmpfs /mnt/storage sudo mount -t tmpfs -o size=9000M tmpfs /mnt/tmpfs sudo dd if=/dev/urandom of=/mnt/tmpfs/ext4.img bs=1M sudo mkfs.ext4 -O large_dir -N 2100 -O dir_index /mnt/tmpfs/ext4.img -b 1024 -F sudo mount /mnt/tmpfs/ext4.img /mnt/storage and compile and run the attached C program (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933074/+attachment/5509402/+files/touch.c) that quickly populates /mnt/storage with empty files. Without the fix this will terminate with an -EEXIST or -EUCLEAN error on the file creation after several tens of thousands of files. [Where problems could occur] This changes the behaviour of the directory indexing hashing so there is a regression potential that this may introduce subsequent index hashing issues when needed (or not) to do a split. This patch seems to cover all the necessary cases, so I believe this risk is relatively low. I have also tested this on all the kernel series in the SRU with 21,000,000 files so I am confident we have enough test coverage to show the fix is OK. -- I believe, I found a bug in ext4 in recent kernel versions. I stumbled across this while I was trying to restore a backup to a new VM. How to reproduce this bug: 1. Use a virtual/physical machine with "Ubuntu 18.04.5 LTS" and kernel version 4.15.0-144-generic. 2. add a secondary disk to hold the test files. 3. prepare and mount the filesystem with enabled 'large_dir' flag: mkfs.ext4 -m0 /dev/sdb1; tune2fs -O large_dir /dev/sdb1; mkdir /mnt/storage; mount /dev/sdb1 /mnt/storage; 4. change to directory and create approx. 16 mio files cd /mnt/storage; i=0; while (( $i < 2000 )); do i=$(( $i + 1 )); (( $i % 1000 == 0 )) && echo $i; touch file_$i.dat || break; done Expected behaviour: - 20 mio files shoud be created without error What happened instead: - The loop aborts with an error message: # 16263100 # touch: cannot touch 'file_16263173.dat': Structure needs cleaning - dmesg gives a little more details: # [Mon Jun 21 03:15:18 2021] EXT4-fs error (device sdb): dx_probe:855: inode #2: block 146221: comm touch: directory leaf block found instead of index block Additional notes: - This occurs on kernel version 4.15.0-144-generic - Not sure, but I believe one test was run on 4.15.0-143-generic and failed too. - Did not check against 4.15.0-142-generic - On 4.15.0-141-generic, the problem does not exist. Behaviour is as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933074/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListH
[Kernel-packages] [Bug 1887661] Re: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message
This bug is awaiting verification that the 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- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1887661 Title: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.6 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 Status in linux-oem-5.6 source package in Impish: Invalid Bug description: [Impact] The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed even there is no obvious failure message from the test: $ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions [ OK ] vxlan4 not supported TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] vxlan4 not supported TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] geneve4 not supported TEST: IPv4 over geneve4: PMTU exceptions [SKIP] geneve4 not supported TEST: IPv6 over geneve4: PMTU exceptions [SKIP] TEST: IPv4 over geneve6: PMTU exceptions [ OK ] TEST: IPv6 over geneve6: PMTU exceptions [ OK ] TEST: IPv4 over fou4: PMTU exceptions [ OK ] TEST: IPv6 over fou4: PMTU exceptions [ OK ] TEST: IPv4 over fou6: PMTU exceptions [ OK ] TEST: IPv6 over fou6: PMTU exceptions [ OK ] TEST: IPv4 over gue4: PMTU exceptions [ OK ] TEST: IPv6 over gue4: PMTU exceptions [ OK ] TEST: IPv4 over gue6: PMTU exceptions [ OK ] TEST: IPv6 over gue6: PMTU exceptions [ OK ] TEST: vti6: PMTU exceptions [ OK ] TEST: vti4: PMTU exceptions [ OK ] TEST: vti4: default MTU assignment [ OK ] TEST: vti6: default MTU assignment [ OK ] TEST: vti4: MTU setting on link creation [ OK ] TEST: vti6: MTU setting on link creation [ OK ] TEST: vti6: MTU changes on link changes [ OK ] vxlan4 not supported TEST: ipv4: cleanup of cached exceptions [SKIP] TEST: ipv6: cleanup of cached exceptions [ OK ] TEST: ipv4: list and flush cached exceptions [ OK ] TEST: ipv6: list and flush cached exceptions [ OK ] $ echo $? 1 This is because the test script treats all non-zero return code as a failure, thus it will be marked as FAILED when some sub-test got skipped. [Fix] * ef1220a7d4bbdb selftests: pmtu.sh: use $ksft_skip for skipped return code * 2a9d3716b810a4 selftests: pmtu.sh: improve the test result processing This patchset will: 1. Use the kselftest framework skip code $ksft_skip to replace the hardcoded SKIP return code. 2. Improve the result processing, the test will be marked as PASSED if nothing goes wrong and not all the tests were skipped. These have already landed in newer releases and this test does not exist in B, thus we just need this for F/F-OEM-5.6/F-OEM-5.10/G. The first patch needs to be backported (except on F-OEM-5.10) as some test cases were not added yet. The second one can be cherry-picked. [Test] Run this test directly on a patched kernel. The skipped test will cause failure to this test. [Where problems could occur] Changes limited to testing tools, it's unlikely to cause any problem to kernel functions. [Original Bug Report] Issue found on B-5.4 oracle 5.4.0-1021.21~18.04.1 The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed even there is no obvious failure message from the test: $ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions [
[Kernel-packages] [Bug 1929831] Re: cifs: On cifs_reconnect, resolve the hostname again
This bug is awaiting verification that the 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- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1929831 Title: cifs: On cifs_reconnect, resolve the hostname again Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-azure source package in Groovy: In Progress Bug description: SRU Justification [Impact] The Microsoft CIFS team is requesting below patch to be backported for 5.4 Azure tuned kernel https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4e456b30f78c429b183db420e23b26cde7e03a78 A customer is encountering the bug fixed by this patch. [Fix] 7d397a034d5c45528c7bdf7fc3752c4793029cce cifs: rename reconn_inval_dfs_target() 7d6535b720421d58886d5590ffc3617d359aa871 cifs: Simplify reconnect code when dfs upcall is enabled 4e456b30f78c429b183db420e23b26cde7e03a78 cifs: On cifs_reconnect, resolve the hostname again. The first 2 patches are scaffolding to make the backport simpler. the 3rd patch is the bug fix. [Test Plan] The test kernel at https://launchpad.net/~timg- tpi/+archive/ubuntu/cifs-reconnect-sf00309672 has been found to fix the issue. [Where problems could occur] This could perturb CIFS connections in new and different ways. [Other Info] https://canonical.my.salesforce.com/5004K05pQNG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933074] Re: large_dir in ext4 broken
This bug is awaiting verification that the 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- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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/1933074 Title: large_dir in ext4 broken Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Triaged Bug description: == SRU, Bionic, Focal, Groovy, Hirsute, Impish == [Impact] Creating millions of files on ext4 partition with large_dir support by touching them will eventually trip an ext4 leaf node issue in the index hash. This occurs more frequently when also using smaller block sizes and ends up either with a EXIST or EUCLEAN failure. This occurs on the restart condition when performing do_split. [ Fix ] The fix protects do_split() from the restart condition, making it safe from both current and future ordering of goto statements in earlier sections of the code. The fix is from a patch sent upstream and cc'd to Ted Tso but didn't appear on the ext4 mailing list presumably because it got marked as SPAM. [ Test Case ] Without the fix touching tens of thousands of empty files will trip the issue. It seems to occur more frequently with memory pressure and smaller block sizes, e.g.: sudo mkdir -p /mnt/tmpfs /mnt/storage sudo mount -t tmpfs -o size=9000M tmpfs /mnt/tmpfs sudo dd if=/dev/urandom of=/mnt/tmpfs/ext4.img bs=1M sudo mkfs.ext4 -O large_dir -N 2100 -O dir_index /mnt/tmpfs/ext4.img -b 1024 -F sudo mount /mnt/tmpfs/ext4.img /mnt/storage and compile and run the attached C program (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933074/+attachment/5509402/+files/touch.c) that quickly populates /mnt/storage with empty files. Without the fix this will terminate with an -EEXIST or -EUCLEAN error on the file creation after several tens of thousands of files. [Where problems could occur] This changes the behaviour of the directory indexing hashing so there is a regression potential that this may introduce subsequent index hashing issues when needed (or not) to do a split. This patch seems to cover all the necessary cases, so I believe this risk is relatively low. I have also tested this on all the kernel series in the SRU with 21,000,000 files so I am confident we have enough test coverage to show the fix is OK. -- I believe, I found a bug in ext4 in recent kernel versions. I stumbled across this while I was trying to restore a backup to a new VM. How to reproduce this bug: 1. Use a virtual/physical machine with "Ubuntu 18.04.5 LTS" and kernel version 4.15.0-144-generic. 2. add a secondary disk to hold the test files. 3. prepare and mount the filesystem with enabled 'large_dir' flag: mkfs.ext4 -m0 /dev/sdb1; tune2fs -O large_dir /dev/sdb1; mkdir /mnt/storage; mount /dev/sdb1 /mnt/storage; 4. change to directory and create approx. 16 mio files cd /mnt/storage; i=0; while (( $i < 2000 )); do i=$(( $i + 1 )); (( $i % 1000 == 0 )) && echo $i; touch file_$i.dat || break; done Expected behaviour: - 20 mio files shoud be created without error What happened instead: - The loop aborts with an error message: # 16263100 # touch: cannot touch 'file_16263173.dat': Structure needs cleaning - dmesg gives a little more details: # [Mon Jun 21 03:15:18 2021] EXT4-fs error (device sdb): dx_probe:855: inode #2: block 146221: comm touch: directory leaf block found instead of index block Additional notes: - This occurs on kernel version 4.15.0-144-generic - Not sure, but I believe one test was run on 4.15.0-143-generic and failed too. - Did not check against 4.15.0-142-generic - On 4.15.0-141-generic, the problem does not exist. Behaviour is as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933074/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More he
[Kernel-packages] [Bug 1932367] Re: Pixel format change broken for Elgato Cam Link 4K
This bug is awaiting verification that the 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/1932367 Title: Pixel format change broken for Elgato Cam Link 4K Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Triaged Bug description: [Impact] The Elgato Cam Link 4K HDMI video capture card reports to support three different pixel formats, where the first format depends on the connected HDMI device. ``` $ v4l2-ctl -d /dev/video0 --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [1]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [2]: 'YU12' (Planar YUV 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) ``` Changing the pixel format to anything besides the first pixel format does not work: ``` $ v4l2-ctl -d /dev/video0 --try-fmt-video pixelformat=YU12 Format Video Capture: Width/Height : 3840/2160 Pixel Format : 'NV12' (Y/CbCr 4:2:0) Field : None Bytes per Line: 3840 Size Image: 12441600 Colorspace: sRGB Transfer Function : Rec. 709 YCbCr/HSV Encoding: Rec. 709 Quantization : Default (maps to Limited Range) Flags : ``` User space applications like VLC might show an error message on the terminal in that case: ``` libv4l2: error set_fmt gave us a different result than try_fmt! ``` Depending on the error handling of the user space applications, they might display a distorted video, because they use the wrong pixel format for decoding the stream. [Fix] The Elgato Cam Link 4K responds to the USB video probe VS_PROBE_CONTROL/VS_COMMIT_CONTROL with a malformed data structure: The second byte contains bFormatIndex (instead of being the second byte of bmHint). The first byte is always zero. The third byte is always 1. The firmware bug was reported to Elgato on 2020-12-01 and it was forwarded by the support team to the developers as feature request. There is no firmware update available since then. The latest firmware for Elgato Cam Link 4K as of 2021-03-23 has MCU 20.02.19 and FPGA 67. Therefore correct the malformed data structure for this device. The change was successfully tested with VLC, OBS, and Chromium using different pixel formats (YUYV, NV12, YU12), resolutions (3840x2160, 1920x1080), and frame rates (29.970 and 59.940 fps). [Test Case] Connect an input device to the Cam Link 4K and try all three pixel formats with VLC: vlc v4l2:///dev/video0 --v4l2-chroma=NV12 vlc v4l2:///dev/video0 --v4l2-chroma=YU12 [Other Info] The fix was reviewed and accepted by the subsystem maintainer and will be included upstream: https://git.linuxtv.org/media_stage.git/commit/?id=4c6e0976295add7f0ed94d276c04a3d6f1ea8f83 Attached a backported patch for Ubuntu. I successfully tested it with Linux 5.11 on Ubuntu 21.04 and Linux 5.8 on Ubuntu 20.10. It should work on older kernel versions as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934175] Re: Kernel oops due to uninitialized list on kernfs (kernfs_kill_sb)
This bug is awaiting verification that the 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/1934175
Title:
Kernel oops due to uninitialized list on kernfs (kernfs_kill_sb)
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
* We had a recent report of a kernel crash due to a NULL pointer dereference
in a Bionic 4.15 derivative kernel, as per the following log collected:
[...]
[537105.767348] SLUB: Unable to allocate memory on node -1,
gfp=0x14000c0(GFP_KERNEL)
[...]
[537105.767368] BUG: unable to handle kernel NULL pointer dereference at
0008
[537105.11] IP: kernfs_kill_sb+0x31/0x70
[537105.783582] PGD 0 P4D 0
[537105.787844] Oops: 0002 [#1] SMP PTI
[...]
RIP: 0010:kernfs_kill_sb+0x31/0x70
RSP: 0018:b90aec1afd00 EFLAGS: 00010286
RAX: RBX: 9fdbd567d900 RCX: a0143885ae01
RDX: RSI: a0143885ae00 RDI: a2937c40
RBP: b90aec1afd10 R08: a0150b581510 R09: 0001814d
R10: b90aec1afcd8 R11: 0100 R12: a01436e43000
R13: a01436e43000 R14: R15: 9fdbd567d900
FS: 7fe41a615b80() GS:a01afea4() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: 0008 CR3: 007dfe3cc003 CR4: 003606e0
DR0: DR1: DR2:
DR3: DR6: fffe0ff0 DR7: 0400
Call Trace:
sysfs_kill_sb+0x1f/0x40
deactivate_locked_super+0x48/0x80
kernfs_mount_ns+0x1eb/0x230
sysfs_mount+0x66/0xc0
mount_fs+0x37/0x160
? alloc_vfsmnt+0x1b3/0x230
vfs_kern_mount.part.24+0x5d/0x110
do_mount+0x5ed/0xce0
[...]
* The following detailed call stack plus the disassembly help to
understand the cause of the issue:
mount_fs()
--sysfs_mount()
kernfs_mount_ns()
--deactivate_locked_super()
sysfs_kill_sb()
--kernfs_kill_sb()
The below disassembly of kernfs_kill_sb() clarifies exactly the issue:
812f46e0 :
[ ... prologue ...]
48 8b 9f 08 04 00 00mov0x408(%rdi),%rbx # %rbx = kernfs_super_info
*info = sb->s_fs_info
49 89 fcmov%rdi,%r12 # %r12 = super_block *sb
48 c7 c7 40 7c 53 82mov$0x82537c40,%rdi # %rdi =
&kernfs_mutex (global)
812f46f9: R_X86_64_32S kernfs_mutex
e8 ee da 67 00 callq 819721f0 #
mutex_lock(&kernfs_mutex);
[...]
48 8b 53 18 mov0x18(%rbx),%rdx # %rdx = info->node
48 8b 43 20 mov0x20(%rbx),%rax # based on splat, RAX == 0x0
[info->head.prev]
48 89 42 08 mov%rax,0x8(%rdx) # <- OOPS [tried to assign
next->prev = prev, see __list_del()]
48 89 10mov%rdx,(%rax)
48 b8 00 01 00 00 00movabs $0xdead0100,%rax # node->next =
LIST_POISON1
[...]
* The fix for this issue comes from upstream commit 82382acec0c9
("kernfs: deal with kernfs_fill_super() failures"); this commit is a
very trivial fix that adds an INIT_LIST_HEAD(&info->node) in
kernfs_mount_ns(), making the list prev/next pointers valid since the
beginning. Unfortunately this commit wasn't CCed to stable email when
sent, so it wasn't automatically picked up by Ubuntu kernel; now it
was properly submitted to stable list [0].
* Along with this fix, we found another commit (7b745a4e4051) which is
a small/simple fix to correlated code, that also should have been sent
to 4.14.y stable branch, but for some reason wasn't. Since both
commits were accepted in linux-stable, we are hereby proposing the
backport for Ubuntu kernel 4.15.
[0]
https://lore.kernel.org/stable/20210622210622.9925-1-gpicc...@canonical.com/
[Test Case]
* We don't have a real test case, although low-memory condition or an
artificial kprobe reproducer could easily trigger the issue.
* We booted a qemu virtual machine with a kernel containing both
patches with no issues.
[Where problems could occur]
* The likelihood of issues are low, specially due to the fact both patches
are very simple and they are on upstream kernel for more than 3 years (and w
[Kernel-packages] [Bug 1932165] Re: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Changelog entries in the #3 debdiff are in the wrong order. The 2.12.2-1ubuntu1~20.04* entreis should be just above the other 2.12.2 entries. Such that when build is done with -v2.12.5-1ubuntu1~20.04.2 all changelog entries since 2.12.2 are included, i.e. all the v2.12.5 from impish and etc. Will redo this before the upload. -- 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/1932165 Title: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in lttng-modules package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in lttng-modules source package in Focal: Confirmed Bug description: This is a scripted bug report about ADT failures while running lttng- modules tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lttng-modules/20210611_205859_b8295@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210612_123048_fc99b@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210611_210510_27086@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210611_210134_272f4@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932163] Re: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
evdi debdiff is good, but it must go into other series too. https://autopkgtest.ubuntu.com/packages/evdi Looks like that change is needed in impish, hirsute and focal. One cannot introduce brand new change in a focal SRU with a version number higher than all future series. ** Changed in: evdi (Ubuntu Hirsute) Status: Fix Committed => Confirmed ** Changed in: evdi (Ubuntu) Status: Fix Released => Confirmed -- 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/1932163 Title: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in evdi package in Ubuntu: Confirmed Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in evdi source package in Focal: Confirmed Status in linux-hwe-5.11 source package in Focal: Confirmed Status in evdi source package in Hirsute: Confirmed Status in linux-hwe-5.11 source package in Hirsute: Confirmed Bug description: [Impact] focal users running latest hwe kernel, version 5.11, won't be able to use evdi-dkms. [Test case] Built evdi dkms and loaded the evdi module on 5.4, 5.8 and 5.11 kernels. [Potential regression] DisplayLink devices will stop working. -- This is a scripted bug report about ADT failures while running evdi tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/e/evdi/20210611_210228_7f0da@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/e/evdi/20210612_122245_bd52e@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/e/evdi/20210611_210028_038f3@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/e/evdi/20210611_205902_3dc65@/log.gz [Other] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
