[Kernel-packages] [Bug 1910763] Re: Steam Proton fails with Kernel 5.8.0-36 Ubuntu 20.04.1
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910763 Title: Steam Proton fails with Kernel 5.8.0-36 Ubuntu 20.04.1 Status in linux package in Ubuntu: Expired Bug description: Yesterday, I updated my Ubuntu 20.04.1 LTS and obtained the new official kernel (with the update) 5.8.0-36. With this kernel I have got a lot of problems with some games with Steam Proton. For example, with the Kernel 5.4.0-59 all works well, I could play Cyberpunk 2077 and Far Cry 5 without problems. Now, with the kernel 5.8.0-36 I can't play Cyberpunk 2077 and I have got low fps in some areas with Far Cry 5, obtaining for example 7-8 fps in the cinematic scene of faith. Some games doesn't start with the new kernel. Some people need this new kernel due to they have got new hardware pieces which are supported with this new kernel. Regards and thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 8 15:35:36 2021 InstallationDate: Installed on 2020-04-24 (258 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912947] Re: bluetooth: hci0: failed to restart LE scan: status 31
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912947 Title: bluetooth: hci0: failed to restart LE scan: status 31 Status in linux package in Ubuntu: Expired Bug description: Sometimes Redmi AirDots headphones hang bluetooth connection without any chance to restore it: [ 93.521009] input: Redmi AirDots_R (AVRCP) as /devices/virtual/input/input23 [ 182.566859] Bluetooth: hci0: failed to restart LE scan: status 31 [ 182.566863] Bluetooth: hci0: command 0x200c tx timeout [ 184.582786] Bluetooth: hci0: command 0x200c tx timeout [ 184.582804] Bluetooth: hci0: failed to disable LE scan: status 0x1f [ 186.598690] Bluetooth: hci0: command 0x200c tx timeout [ 230.006140] Bluetooth: hci0: link tx timeout [ 230.006151] Bluetooth: hci0: killing stalled connection 1c:52:16:9c:b2:62 [ 232.037806] Bluetooth: hci0: command 0x0406 tx timeout [ 234.053788] Bluetooth: hci0: command 0x0402 tx timeout [ 234.053795] Bluetooth: hci0: No way to reset. Ignoring and continuing [ 236.069748] Bluetooth: hci0: command 0x200c tx timeout [ 236.069752] Bluetooth: hci0: No way to reset. Ignoring and continuing [ 239.521344] Bluetooth: hci0: link tx timeout [ 239.521352] Bluetooth: hci0: killing stalled connection 1c:52:16:9c:b2:62 [ 239.998701] Bluetooth: hci0: link tx timeout [ 239.998707] Bluetooth: hci0: killing stalled connection 1c:52:16:9c:b2:62 [ 242.001218] Bluetooth: hci0: link tx timeout [ 242.001226] Bluetooth: hci0: killing stalled connection 1c:52:16:9c:b2:62 [ 242.001276] Bluetooth: hci0: link tx timeout [ 242.001284] Bluetooth: hci0: killing stalled connection 1c:52:16:9c:b2:62 [ 244.005643] Bluetooth: hci0: command 0x0405 tx timeout [ 244.005650] Bluetooth: hci0: No way to reset. Ignoring and continuing [ 246.021612] Bluetooth: hci0: command 0x0408 tx timeout [ 246.021620] Bluetooth: hci0: No way to reset. Ignoring and continuing [ 248.037630] Bluetooth: hci0: command 0x0408 tx timeout [ 248.037637] Bluetooth: hci0: No way to reset. Ignoring and continuing [ 250.053611] Bluetooth: hci0: command 0x0408 tx timeout [ 250.053618] Bluetooth: hci0: No way to reset. Ignoring and continuing [ 344.027978] Bluetooth: hci0: link tx timeout [ 344.027989] Bluetooth: hci0: killing stalled connection 1c:52:16:9c:b2:62 [ 346.053017] Bluetooth: hci0: command 0x0408 tx timeout [ 346.053025] Bluetooth: hci0: No way to reset. Ignoring and continuing [ 367.684879] Bluetooth: hci0: link tx timeout [ 367.684887] Bluetooth: hci0: killing stalled connection 1c:52:16:9c:b2:62 [ 369.700803] Bluetooth: hci0: command 0x0408 tx timeout [ 369.700811] Bluetooth: hci0: No way to reset. Ignoring and continuing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913028] Re: Green pixels on all black screens with Kernel update 5.4.0-64.72
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1913028 Title: Green pixels on all black screens with Kernel update 5.4.0-64.72 Status in linux package in Ubuntu: Expired Bug description: After a kernel update, I noticed that the Linux Mint Ulyssa startup screen was almost completely green instead of black. Then my desktop wallpaper looked normal. However, whenever I would open a black page in a browser or a document on my desktop, it would be filled up with green pixels and horizontal green lines with large portions of the black screen colored in green. White pages would have vertical pink lines. I thought the screen connector was faulty. However, after checking the History of Updates, I noticed that a Kernel update (5.4.0-64.72) happened just when the screen issue started to occur. I therefore tried and install the previous Kernel (5.4.0-62.70) to see if this would solve the problem. And it did! No more green pixels on black screens, nor vertical pink lines on white screens. Release of Ubuntu used: Linux Mint 20.1 Cinnamon v 4.8.6 Kernel: 5.4.0-64-generic Processor: Intel© Core™ i3 CPU M 380 @ 2.53GHz × 2 Memory: 7.6 GiB Graphic Cards: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] (prog-if 00 [VGA controller]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921411] Re: linux-azure: Install PMEM modules by default
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/1921411 Title: linux-azure: Install PMEM modules by default Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-azure source package in Groovy: Fix Committed Status in linux-azure-4.15 source package in Groovy: Invalid Bug description: [Impact] Some workloads, for example SQL Server, require PMEM support from different modules for performance reasons. Most of this modules are included in the linux-modules-extra package but linux-azure doesn't install it by default. Move these modules to the linux-modules package so they are installed by default: nd_blk.ko, nd_pmem.ko, device_dax.ko, dax_hmem.ko, kmem.ko, dax_pmem.ko, dax_pmem_compat.ko, virtio_pmem.ko , nd_virtio.ko. (Some modules are not available depending on the kernel version) [Test Plan] The modules listed below should be included in the linux-modules package instead of in the linux-modules-extra package. [Where problems could occur] The additional modules shouldn't cause any troubles and in case of problem they can be blacklisted or removed from linux-modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1921411/+subscriptions -- Mailing list: https://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 1919408] Re: General protection fault, kernel panics on ASUS M5A99FX PRO R2.0
And this is the second full crash Today. On Fri, Mar 26, 2021 at 6:25 PM K. M. Ravandi wrote: > GUI Freezed again. > Attached here several journalctl file results today > memtest86: new ram I did not get any errors. > > On Fri, Mar 26, 2021 at 5:25 PM K. M. Ravandi > wrote: > >> Crashed again... >> Attached here several journalctl file results today >> memtest86: new ram I did notget any errors. >> >> On Tue, Mar 23, 2021 at 12:53 PM K. M. Ravandi >> wrote: >> >>> Here you go with the memtest86 result. >>> >>> it shows massive errors on Ram. I installed a new one to double check if >>> it is not also a Motherboard issue; since last night memtest 86 did not >>> show any error. >>> >>> I will wait until this weekend to be sure there are no issues and get >>> back to you with an update. >>> >>> On Sun, Mar 21, 2021 at 10:28 PM K. M. Ravandi >>> wrote: >>> I already started it to run this morning, I am going to check later, and let you know. On Sun, Mar 21, 2021 at 10:25 PM Daniel van Vugt < 1919...@bugs.launchpad.net> wrote: > A full memory test takes hours or even days, but running it overnight > should be enough time usually. Please try the tools mentioned in > comment > #7. > > -- > You received this bug notification because you are subscribed to the > bug > report. > https://bugs.launchpad.net/bugs/1919408 > > Title: > General protection fault, kernel panics on ASUS M5A99FX PRO R2.0 > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > After copied (dd copy) old disk /home to bigger one then reboot > xorg start to freeze it seems kernel crash rather than only Xorg, because > all input devices (keyboard, mouse) turned off completely. only option is > hard reboot. > I upgrade distro from 20.04 to 20.10, the situation remain the same > after every login to desktop the system freeze completely and need it to > do > hard reboot. > > ProblemType: Bug > DistroRelease: Ubuntu 20.10 > Package: xorg 1:7.7+19ubuntu15 > ProcVersionSignature: Ubuntu 5.8.0-45.51-lowlatency 5.8.18 > Uname: Linux 5.8.0-45-lowlatency x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > .tmp.unity_support_test.0: > > ApportVersion: 2.20.11-0ubuntu50.5 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompizPlugins: > [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] > CompositorRunning: None > CurrentDesktop: MATE > Date: Wed Mar 17 01:11:19 2021 > DistUpgraded: 2021-03-15 02:52:49,427 INFO cache.commit() > DistroCodename: groovy > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GconfCompiz: >/apps/compiz-1/general: > /apps/compiz-1/general/screen0: > /apps/compiz-1/general/screen0/options: >active_plugins = > [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] > GpuHangFrequency: Continuously > GpuHangReproducibility: Occurs more often under certain circumstances > GpuHangStarted: Within the last week or two > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX > 470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA > controller]) > Subsystem: XFX Pine Group Inc. Radeon RX 570 [1682:c570] > InstallationDate: Installed on 2018-05-05 (1046 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > MachineType: To be filled by O.E.M. To be filled by O.E.M. > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-lowlatency > root=UUID=17faa721-1006-4426-b460-57b94bfebefa ro threadirqs > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=512M-:192M > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: Upgraded to groovy on 2021-03-15 (1 days ago) > dmi.bios.date: 04/10/2013 > dmi.bios.release: 4.6 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 1708 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: M5A99FX PRO R2.0 > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev 1.xx > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type:
Re: [Kernel-packages] [Bug 1919408] Re: General protection fault, kernel panics on ASUS M5A99FX PRO R2.0
GUI Freezed again. Attached here several journalctl file results today memtest86: new ram I did not get any errors. On Fri, Mar 26, 2021 at 5:25 PM K. M. Ravandi wrote: > Crashed again... > Attached here several journalctl file results today > memtest86: new ram I did notget any errors. > > On Tue, Mar 23, 2021 at 12:53 PM K. M. Ravandi > wrote: > >> Here you go with the memtest86 result. >> >> it shows massive errors on Ram. I installed a new one to double check if >> it is not also a Motherboard issue; since last night memtest 86 did not >> show any error. >> >> I will wait until this weekend to be sure there are no issues and get >> back to you with an update. >> >> On Sun, Mar 21, 2021 at 10:28 PM K. M. Ravandi >> wrote: >> >>> I already started it to run this morning, I am going to check later, and >>> let you know. >>> >>> On Sun, Mar 21, 2021 at 10:25 PM Daniel van Vugt < >>> 1919...@bugs.launchpad.net> wrote: >>> A full memory test takes hours or even days, but running it overnight should be enough time usually. Please try the tools mentioned in comment #7. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1919408 Title: General protection fault, kernel panics on ASUS M5A99FX PRO R2.0 Status in linux package in Ubuntu: Incomplete Bug description: After copied (dd copy) old disk /home to bigger one then reboot xorg start to freeze it seems kernel crash rather than only Xorg, because all input devices (keyboard, mouse) turned off completely. only option is hard reboot. I upgrade distro from 20.04 to 20.10, the situation remain the same after every login to desktop the system freeze completely and need it to do hard reboot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-45.51-lowlatency 5.8.18 Uname: Linux 5.8.0-45-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: MATE Date: Wed Mar 17 01:11:19 2021 DistUpgraded: 2021-03-15 02:52:49,427 INFO cache.commit() DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 570 [1682:c570] InstallationDate: Installed on 2018-05-05 (1046 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-lowlatency root=UUID=17faa721-1006-4426-b460-57b94bfebefa ro threadirqs crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=512M-:192M SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to groovy on 2021-03-15 (1 days ago) dmi.bios.date: 04/10/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1708 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99FX PRO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Kernel-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
** Changed in: alsa-lib (Ubuntu Focal) Importance: Undecided => Low ** Changed in: alsa-lib (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: alsa-lib (Ubuntu Hirsute) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: In Progress Status in alsa-lib package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Groovy: In Progress Status in alsa-lib source package in Hirsute: In Progress Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] This fix limits to the Cmedia Audio only, other devices are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1171582] Re: [highbank] hvc0 getty causes random hangs
** Changed in: linux (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/1171582 Title: [highbank] hvc0 getty causes random hangs Status in finish-install package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in finish-install source package in Raring: Fix Released Status in linux source package in Raring: Won't Fix Status in finish-install source package in Saucy: Fix Released Status in linux source package in Saucy: Won't Fix Bug description: After doing a fresh install of raring, I've observed several issues across multiple systems, and they all seem to be correlated with the hvc0 upstart job (hvc0 getty) running. One symptom I've seen on both machines is that the network goes unresponsive for several seconds before recovering. If I run a ping, I see a pattern of 84-85s of responses, followed by about 41s of failures. The khvcd process consumes a lot of CPU - often 100% of a processor. Processes seem to randomly hang and are seemingly unrecoverable. I ran an apt-get install that never emitted any output, but remained hung until I rebooted the system. When I try to kill the hvc0 upstart job (sudo stop hvc0 - or a kill -9), the process does not die. One one of the two hosts, I observed the console getty (ttyAMA0) successfully starting, but never providing a login prompt to the console. Restarting this process didn't help solve the problem. Disabling the hvc0 upstart job and rebooting reliably makes these problems go away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/finish-install/+bug/1171582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1063895] Re: arm64 support to generate linux-source for crosstool bulds
** Changed in: linux (Ubuntu Linaro Evaluation Build) Status: New => 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/1063895 Title: arm64 support to generate linux-source for crosstool bulds Status in linux package in Ubuntu: Fix Released Status in linux package in Ubuntu Linaro Evaluation Build: Fix Released Bug description: [Not sure If I've filed this aginst the right package. It should be linux-3.5.0, but that doesn't exist according to launchpad. ] Attached is a first-cut patch adding arm64 support to the linux-3.5.0 package so that it builds linux-source packages which can be used to build cross tools against. The arm64 support is just the core stuff so isn't much use for making binaries. It's also an unholy backport of 3.6/3.7 vintage stuff to 3.5 so it probably bust in important ways. However that's not relevant for the primiary purpose here of building cross-tools, which just needs a correct set of headers in linux-libc- dev, and arch/package machinery in linux-source. I'm not expecting this to be uploaded but wanted to put it somewhere public for anyone else to build with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1063895] Re: arm64 support to generate linux-source for crosstool bulds
** Changed in: linux (Ubuntu Linaro Evaluation Build) Assignee: (unassigned) => christopher wayne hess (hess8519) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1063895 Title: arm64 support to generate linux-source for crosstool bulds Status in linux package in Ubuntu: Fix Released Status in linux package in Ubuntu Linaro Evaluation Build: Fix Released Bug description: [Not sure If I've filed this aginst the right package. It should be linux-3.5.0, but that doesn't exist according to launchpad. ] Attached is a first-cut patch adding arm64 support to the linux-3.5.0 package so that it builds linux-source packages which can be used to build cross tools against. The arm64 support is just the core stuff so isn't much use for making binaries. It's also an unholy backport of 3.6/3.7 vintage stuff to 3.5 so it probably bust in important ways. However that's not relevant for the primiary purpose here of building cross-tools, which just needs a correct set of headers in linux-libc- dev, and arch/package machinery in linux-source. I'm not expecting this to be uploaded but wanted to put it somewhere public for anyone else to build with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 I'm experiencing this issue as well. On the HSP/HFP profile, the audio output comes through crystal clear, but the microphone is lost. On the A2DP profile, I get the microphone back, but the sound quality on the headphones becomes terrible... sounds like I'm on a copper phone line or bad cell signal. - Kernel: 5.8.0-48-generic - OS: Ubuntu 20.04.2 LTS - Machine: Lenovo ThinkPad T-490 - Headset: Bose QuietComfort 35 II -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] [NEW] "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
Public bug reported: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New -- 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/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux-restricted-modules package in Ubuntu: New Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 95940] Re: No way to reset ALSA state from GUI
** Changed in: gnome-applets (Ubuntu) Status: Triaged => 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/95940 Title: No way to reset ALSA state from GUI Status in GNOME Applets: Won't Fix Status in KDE Multimedia: New Status in gnome-applets package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-source-2.6.20 package in Ubuntu: Won't Fix Status in gnome-applets source package in Hardy: Won't Fix Status in linux source package in Hardy: Invalid Status in linux-source-2.6.20 source package in Hardy: Won't Fix Bug description: There is no way to reset the ALSA state from the mixer applet. Several users have found that they lose sound, and that the problem turns out to be an asound.state file which does not work for their hardware. It has not been established how the file came to be corrupt or whether the problem was caused by upgrades to newer versions which did not handle the file as written by the previous version. It has not been established what aspect of the asound.state files caused the problem. But several approaches can fix the problem: 1. Removing the ALSA modules, deleting the asound.state file, and reloading the modules. This is difficult to do for non-expert users, because applications such as the Gnome mixer and volume control can be using the modules, preventing their unloading. 2. Removing the ALSA modules, and editing the asound.state to an ultra-minimal state that reflects only the primary card, and reloading the modules. 3. Invoking the alsa-utils "reset" option. On Ubuntu, typing this fixes the problem for Intel sound cards: /etc/init.d/alsa-utils reset Intel The latter option is thought to be best, because it doesn't require unloading and reloading modules. It would be very useful to be able to invoke that "reset" command from the GUI Gnome mixer applet, which is why this bug has been filed on that. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-applets/+bug/95940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] Re: Garbage window on external 4k display
I was mistaken the issue is still there, it is most easily reproduced if you run youtube.com using Firefox on the external display moving the mouse over videos displays the window with garbage quite easily. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Confirmed Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia 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.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow
Kernel SRU request submitted for groovy and focal: https://lists.ubuntu.com/archives/kernel-team/2021-March/thread.html#118559 changing status to 'In Progress' for both entries (G and F). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921104 Title: net/mlx5e: Add missing capability check for uplink follow Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification: == [Impact] * Since older firmware may not support the uplink state setting, this can lead to problems. * Now expose firmware indication that it supports setting eswitch uplink state to follow the physical link. * If a kernel without the backport is used on an adapter which does not have the latest adapter firmware, the adapter silently drops outgoing traffic. * This is a regression which was introduced with kernel 5.4.0-48. [Fix] * upstream fix (as in 5.11): 9c9be85f6b59d80efe4705109c0396df18d4e11d 9c9be85f6b59 "net/mlx5e: Add missing capability check for uplink follow" * backport for focal: https://launchpadlibrarian.net/529543695/0001 -Backport-net-mlx5e-Add-missing-capability-check-for-.patch * backport for groovy: https://launchpadlibrarian.net/529775887/0001 -Backport-groovy-net-mlx5e-Add-missing-capability-che.patch [Test Case] * Two IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04 or 20.10 on LPAR, are needed. * Each with RoCE Express 2.x adapters (Mellanox ConnectX4/5) attached and firmware 16.29.1006 or earlier. * Assign an IP address to the adapters on both systems and try to ping one node from the other. * The ping will just fail with the stock Ubuntu kernels (not having the patch), but will succeed with kernels that incl. the patches (like the test builds from the PPA mentioned below). * Due to the lack of hardware this needs to be verified by IBM. [Regression Potential] * Undesired / erroneous behavior in case the modified if condition is assembled in a wrong way. * Again wrong behavior in case the modification of the capability bits in mlx5_ifc_cmd_hca_cap_bits are wrong. * All modification are limited to the mlx5 driver only. * The changes are relatively limited with effectively two lines removed and 4 added (three of them adjustments of the capability bits only). * The modifications were done and tested by IBM and reviewed by Mellanox (see LP comments), based on a PPA test build. [Other] * The above patch/commit was upstream accepted with kernel 5.11. * Hence the patch is not needed for hirsute, just needs to be SRUed for groovy and focal. * The commit couldn't be cleanly cherry-picked, mainly due to changed context, hence the backport(s). __ Expose firmware indication that it supports setting eswitch uplink state to follow (follow the physical link). Condition setting the eswitch uplink admin-state with this capability bit. Older FW may not support the uplink state setting. Available fix with kernel 5.11. https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d Now required for Ubuntu 20.04 via backport patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow
Kernel SRU request submitted for groovy and focal: https://lists.ubuntu.com/archives/kernel-team/2021-March/thread.html#118548 changing status to 'In Progress' for both entries (G and F). ** Changed in: linux (Ubuntu Groovy) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: ubuntu-z-systems Status: Triaged => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => High ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921104 Title: net/mlx5e: Add missing capability check for uplink follow Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification: == [Impact] * Since older firmware may not support the uplink state setting, this can lead to problems. * Now expose firmware indication that it supports setting eswitch uplink state to follow the physical link. * If a kernel without the backport is used on an adapter which does not have the latest adapter firmware, the adapter silently drops outgoing traffic. * This is a regression which was introduced with kernel 5.4.0-48. [Fix] * upstream fix (as in 5.11): 9c9be85f6b59d80efe4705109c0396df18d4e11d 9c9be85f6b59 "net/mlx5e: Add missing capability check for uplink follow" * backport for focal: https://launchpadlibrarian.net/529543695/0001 -Backport-net-mlx5e-Add-missing-capability-check-for-.patch * backport for groovy: https://launchpadlibrarian.net/529775887/0001 -Backport-groovy-net-mlx5e-Add-missing-capability-che.patch [Test Case] * Two IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04 or 20.10 on LPAR, are needed. * Each with RoCE Express 2.x adapters (Mellanox ConnectX4/5) attached and firmware 16.29.1006 or earlier. * Assign an IP address to the adapters on both systems and try to ping one node from the other. * The ping will just fail with the stock Ubuntu kernels (not having the patch), but will succeed with kernels that incl. the patches (like the test builds from the PPA mentioned below). * Due to the lack of hardware this needs to be verified by IBM. [Regression Potential] * Undesired / erroneous behavior in case the modified if condition is assembled in a wrong way. * Again wrong behavior in case the modification of the capability bits in mlx5_ifc_cmd_hca_cap_bits are wrong. * All modification are limited to the mlx5 driver only. * The changes are relatively limited with effectively two lines removed and 4 added (three of them adjustments of the capability bits only). * The modifications were done and tested by IBM and reviewed by Mellanox (see LP comments), based on a PPA test build. [Other] * The above patch/commit was upstream accepted with kernel 5.11. * Hence the patch is not needed for hirsute, just needs to be SRUed for groovy and focal. * The commit couldn't be cleanly cherry-picked, mainly due to changed context, hence the backport(s). __ Expose firmware indication that it supports setting eswitch uplink state to follow (follow the physical link). Condition setting the eswitch uplink admin-state with this capability bit. Older FW may not support the uplink state setting. Available fix with kernel 5.11. https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d Now required for Ubuntu 20.04 via backport patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918228] Re: Fix missing HDMI/DP audio on NVidia card after S3
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918228 Title: Fix missing HDMI/DP audio on NVidia card after S3 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: [Impact] NVidia DP/HDMI aduio disappears after S3. This is a regression introduced by LP: #1867704. [Fix] Update ELD properly so jack status is correctly reported. [Test] Perform S3 and open Sound Settings. With the fix applied, the DP/HDMI audio is always present after S3. [Where problems could occur] This series changes how ELD gets update. So if device depends on the original behavior, jack status could be wrong after this fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1918228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow
** Summary changed: - net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04 + net/mlx5e: Add missing capability check for uplink follow -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921104 Title: net/mlx5e: Add missing capability check for uplink follow Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification: == [Impact] * Since older firmware may not support the uplink state setting, this can lead to problems. * Now expose firmware indication that it supports setting eswitch uplink state to follow the physical link. * If a kernel without the backport is used on an adapter which does not have the latest adapter firmware, the adapter silently drops outgoing traffic. * This is a regression which was introduced with kernel 5.4.0-48. [Fix] * upstream fix (as in 5.11): 9c9be85f6b59d80efe4705109c0396df18d4e11d 9c9be85f6b59 "net/mlx5e: Add missing capability check for uplink follow" * backport for focal: https://launchpadlibrarian.net/529543695/0001 -Backport-net-mlx5e-Add-missing-capability-check-for-.patch * backport for groovy: https://launchpadlibrarian.net/529775887/0001 -Backport-groovy-net-mlx5e-Add-missing-capability-che.patch [Test Case] * Two IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04 or 20.10 on LPAR, are needed. * Each with RoCE Express 2.x adapters (Mellanox ConnectX4/5) attached and firmware 16.29.1006 or earlier. * Assign an IP address to the adapters on both systems and try to ping one node from the other. * The ping will just fail with the stock Ubuntu kernels (not having the patch), but will succeed with kernels that incl. the patches (like the test builds from the PPA mentioned below). * Due to the lack of hardware this needs to be verified by IBM. [Regression Potential] * Undesired / erroneous behavior in case the modified if condition is assembled in a wrong way. * Again wrong behavior in case the modification of the capability bits in mlx5_ifc_cmd_hca_cap_bits are wrong. * All modification are limited to the mlx5 driver only. * The changes are relatively limited with effectively two lines removed and 4 added (three of them adjustments of the capability bits only). * The modifications were done and tested by IBM and reviewed by Mellanox (see LP comments), based on a PPA test build. [Other] * The above patch/commit was upstream accepted with kernel 5.11. * Hence the patch is not needed for hirsute, just needs to be SRUed for groovy and focal. * The commit couldn't be cleanly cherry-picked, mainly due to changed context, hence the backport(s). __ Expose firmware indication that it supports setting eswitch uplink state to follow (follow the physical link). Condition setting the eswitch uplink admin-state with this capability bit. Older FW may not support the uplink state setting. Available fix with kernel 5.11. https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d Now required for Ubuntu 20.04 via backport patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921385] Re: Crashes in i915 on Intel GM965
User solved initial problem by installing newer version of Ubuntu. Now user is asking for support for wireless chip. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/linux/+question/696265 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921385 Title: Crashes in i915 on Intel GM965 Status in linux package in Ubuntu: Invalid Bug description: The boot program is very slow. An error dialog pops up simply stating there is a problem with the system. If I open the details a long long list of data is shown, way above my technical knowledge. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-140.144~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-140-generic i686 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Mar 25 08:22:18 2021 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-139-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-140-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Inspiron 1525 [1028:022f] Subsystem: Dell Inspiron 1525 [1028:022f] InstallationDate: Installed on 2021-03-17 (7 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: Dell Inc. Inspiron 1525 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-140-generic root=UUID=b85df775-5de2-47b0-843b-d2f8b1f71d5e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1921504/+attachment/5481163/+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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpc07271228 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-43-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: 10/27/2009 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1921504/+attachment/5481162/+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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpc07271228 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-43-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: 10/27/2009 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1921504/+attachment/5481164/+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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpc07271228 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-43-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: 10/27/2009 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1921504/+attachment/5481161/+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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpc07271228 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-43-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: 10/27/2009 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1921504/+attachment/5481160/+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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpc07271228 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-43-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: 10/27/2009 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1921504/+attachment/5481159/+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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpc07271228 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-43-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: 10/27/2009 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1921504/+attachment/5481155/+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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpc07271228 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-43-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: 10/27/2009 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1921504/+attachment/5481153/+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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpc07271228 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-43-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: 10/27/2009 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1921504/+attachment/5481157/+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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpc07271228 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-43-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: 10/27/2009 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1921504/+attachment/5481158/+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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpc07271228 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-43-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: 10/27/2009 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1921504/+attachment/5481154/+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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpc07271228 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-43-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: 10/27/2009 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1921504/+attachment/5481150/+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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpc07271228 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-43-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: 10/27/2009 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1921504/+attachment/5481152/+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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpc07271228 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-43-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: 10/27/2009 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1921504/+attachment/5481156/+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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpc07271228 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-43-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: 10/27/2009 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1921504/+attachment/5481151/+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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpc07271228 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-43-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: 10/27/2009 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] Re: Ubuntu 20.04 Install
apport information ** Tags added: apport-collected ** Description changed: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: jpc07271228 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-03-26 (0 days ago) + InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) + IwConfig: + lono wireless extensions. + + enp9s0no wireless extensions. + MachineType: Dell Inc. Inspiron 1525 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-43-generic N/A + linux-backports-modules-5.8.0-43-generic N/A + linux-firmware1.187.9 + RfKill: + + Tags: focal + Uname: Linux 5.8.0-43-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: 10/27/2009 + dmi.bios.release: 1.7 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A17 + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.ec.firmware.release: 1.7 + dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: + dmi.product.name: Inspiron 1525 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1921504/+attachment/5481149/+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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpc07271228 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=8b3b451d-a458-4ba6-b9a6-55f9e2a9d259 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.8.0-43-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: 10/27/2009 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:br1.7:efr1.7:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04
Hi Frank, thank you very much! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921104 Title: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Triaged Status in linux source package in Groovy: Triaged Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification: == [Impact] * Since older firmware may not support the uplink state setting, this can lead to problems. * Now expose firmware indication that it supports setting eswitch uplink state to follow the physical link. * If a kernel without the backport is used on an adapter which does not have the latest adapter firmware, the adapter silently drops outgoing traffic. * This is a regression which was introduced with kernel 5.4.0-48. [Fix] * upstream fix (as in 5.11): 9c9be85f6b59d80efe4705109c0396df18d4e11d 9c9be85f6b59 "net/mlx5e: Add missing capability check for uplink follow" * backport for focal: https://launchpadlibrarian.net/529543695/0001 -Backport-net-mlx5e-Add-missing-capability-check-for-.patch * backport for groovy: https://launchpadlibrarian.net/529775887/0001 -Backport-groovy-net-mlx5e-Add-missing-capability-che.patch [Test Case] * Two IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04 or 20.10 on LPAR, are needed. * Each with RoCE Express 2.x adapters (Mellanox ConnectX4/5) attached and firmware 16.29.1006 or earlier. * Assign an IP address to the adapters on both systems and try to ping one node from the other. * The ping will just fail with the stock Ubuntu kernels (not having the patch), but will succeed with kernels that incl. the patches (like the test builds from the PPA mentioned below). * Due to the lack of hardware this needs to be verified by IBM. [Regression Potential] * Undesired / erroneous behavior in case the modified if condition is assembled in a wrong way. * Again wrong behavior in case the modification of the capability bits in mlx5_ifc_cmd_hca_cap_bits are wrong. * All modification are limited to the mlx5 driver only. * The changes are relatively limited with effectively two lines removed and 4 added (three of them adjustments of the capability bits only). * The modifications were done and tested by IBM and reviewed by Mellanox (see LP comments), based on a PPA test build. [Other] * The above patch/commit was upstream accepted with kernel 5.11. * Hence the patch is not needed for hirsute, just needs to be SRUed for groovy and focal. * The commit couldn't be cleanly cherry-picked, mainly due to changed context, hence the backport(s). __ Expose firmware indication that it supports setting eswitch uplink state to follow (follow the physical link). Condition setting the eswitch uplink admin-state with this capability bit. Older FW may not support the uplink state setting. Available fix with kernel 5.11. https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d Now required for Ubuntu 20.04 via backport patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900438] Re: Bcache bypasse writeback on caching device with fragmentation
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Assignee: dongdong tao (taodd)
Status: 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/1900438
Title:
Bcache bypasse writeback on caching device with fragmentation
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Status in linux source package in Hirsute:
Confirmed
Bug description:
SRU Justification:
[Impact]
This bug in bcache affects I/O performance on all versions of the kernel
[correct versions affected]. It is particularly negative on ceph if used with
bcache.
Write I/O latency would suddenly go to around 1 second from around 10
ms when hitting this issue and would easily be stuck there for hours
or even days, especially bad for ceph on bcache architecture. This
would make ceph extremely slow and make the entire cloud almost
unusable.
The root cause is that the dirty bucket had reached the 70 percent
threshold, thus causing all writes to go direct to the backing HDD
device. It might be fine if it actually had a lot of dirty data, but
this happens when dirty data has not even reached over 10 percent, due
to having high memory fragmentation. What makes it worse is that the
writeback rate might be still at minimum value (8) due to the
writeback percent not reached, so it takes ages for bcache to really
reclaim enough dirty buckets to get itself out of this situation.
[Fix]
* 71dda2a5625f31bc3410cb69c3d31376a2b66f28 “bcache: consider the
fragmentation when update the writeback rate”
The current way to calculate the writeback rate only considered the dirty
sectors.
This usually works fine when memory fragmentation is not high, but it will
give us an unreasonably low writeback rate when we are in the situation that a
few dirty sectors have consumed a lot of dirty buckets. In some cases, the
dirty buckets reached CUTOFF_WRITEBACK_SYNC (i.e., stopped writeback) while
the dirty data (sectors) had not even reached the writeback_percent threshold
(i.e., started writeback). In that situation, the writeback rate will still be
the minimum value (8*512 = 4KB/s), thus it will cause all the writes to bestuck
in a non-writeback mode because of the slow writeback.
We accelerate the rate in 3 stages with different aggressiveness:
the first stage starts when dirty buckets percent reach above
BCH_WRITEBACK_FRAGMENT_THRESHOLD_LOW (50),
the second is BCH_WRITEBACK_FRAGMENT_THRESHOLD_MID (57),
the third is BCH_WRITEBACK_FRAGMENT_THRESHOLD_HIGH (64).
By default the first stage tries to writeback the amount of dirty data
in one bucket (on average) in (1 / (dirty_buckets_percent - 50)) seconds,
the second stage tries to writeback the amount of dirty data in one bucket
in (1 / (dirty_buckets_percent - 57)) * 100 milliseconds, the third
stage tries to writeback the amount of dirty data in one bucket in
(1 / (dirty_buckets_percent - 64)) milliseconds.
The initial rate at each stage can be controlled by 3 configurable
parameters:
writeback_rate_fp_term_{low|mid|high}
They are by default 1, 10, 1000, chosen based on testing and
production data, detailed below.
A. When it comes to the low stage, it is still far from the 70%
threshold, so we only want to give it a little bit push by setting the
term to 1, it means the initial rate will be 170 if the fragment is 6,
it is calculated by bucket_size/fragment, this rate is very small,
but still much more reasonable than the minimum 8.
For a production bcache with non-heavy workload, if the cache device
is bigger than 1 TB, it may take hours to consume 1% buckets,
so it is very possible to reclaim enough dirty buckets in this stage,
thus to avoid entering the next stage.
B. If the dirty buckets ratio didn’t turn around during the first stage,
it comes to the mid stage, then it is necessary for mid stage
to be more aggressive than low stage, so the initial rate is chosen
to be 10 times more than the low stage, which means 1700 as the initial
rate if the fragment is 6. This is a normal rate
we usually see for a normal workload when writeback happens
because of writeback_percent.
C. If the dirty buckets ratio didn't turn around during the low and mid
stages, it comes to the third stage, and it is the last chance that
we can turn around to avoid the horrible cutoff writeback sync issue,
then we choose 100 times more aggressive than the mid stage, that
means 17 as the initial rate if the fragment is 6. This is also
inferred from a production bcache, I've got one week's writeback rate
data from a production bcache which has quite
[Kernel-packages] [Bug 1905591] Re: no brightness control in {455, 460} after update from 450
Same problem with Legion 5 pro, 5800H+3070. Tried config
https://www.reddit.com/r/GamingLaptops/comments/ls9k5r/legion_5_pro_other_info_64gb_ram_upgrade_linux/
This guy claims that after 'upgrading to Kernel 5.10', 'Blacklisting
noveau drivers', 'changing the .conf file' and 'adding modules in
initramfs', brightness control works. https://www.notion.so/Legion-5
-Pro-Regolith-Important-Steps-2c468d1b33cc481dbd92d5ea59a6b74b
Will try this later. So far I have tried changing .conf and adding
modules in initramfs and it didn't work.
--
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/1905591
Title:
no brightness control in {455,460} after update from 450
Status in OEM Priority Project:
New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Confirmed
Bug description:
On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce
GTX 1050 Ti Mobile]:
WORKS FINE:
nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1
NO BRIGHTNESS CONTROL:
nvidia-driver-455: 455.38-0ubuntu0.18.04.1
nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1
nvidia-driver-460: 460.39-0ubuntu0.18.04.1
*WORKAROUND: See comment #11 (add nvidia drivers to initramfs).
*Note that 460 fixes it for a 20.04 ThinkPad P73 per comment #6, but
not for my 18.04.5 Lenovo ThinkPad X1 per comment #5.
Updating to nvidia-driver-455 (or -460) results in loss of brightness
control. On boot, the laptop display brightness is somewhat less than
fully bright and cannot be changed. The brightness up/down keys do
pop up the gnome gui brightness widget, and
/sys/class/backlight/nvidia_0/* values do change, but the actual
display's brightness does not.
Problem occurs with either version of nvidia-driver-455 (the archive
or the ~graphics-drivers/PPA) or any version of -460.
Normal functionality returns if I downgrade to any version of nvidia-
driver-450.
Also observed: 455 and 460 temporarily display some pixel garbage
while mode-switching during the graphic login sequence. Only a minor
glitch, but note that 450 does not exhibit that issue either.
Note also that manually applying this to
/lib/systemd/system/nvidia-persistenced.service has no effect on the problem:
https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic
kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1905591/+subscriptions
--
Mailing list: https://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 1921504] Missing required logs.
I cannot perform this for I do not have an internet connection. On Fri, Mar 26, 2021 at 9:05 AM Ubuntu Kernel Bot <1921...@bugs.launchpad.net> wrote: > > This bug is missing log files that will aid in diagnosing the problem. > While running an Ubuntu kernel (not a mainline or third-party kernel) > please enter the following command in a terminal window: > > apport-collect 1921504 > > and then change the status of the bug to 'Confirmed'. > > If, due to the nature of the issue you have encountered, you are unable > to run this command, please add a comment stating that fact and change > the bug status to 'Confirmed'. > > This change has been made by an automated script, maintained by the > Ubuntu Kernel Team. > > ** Changed in: linux (Ubuntu) >Status: New => Incomplete > > ** Tags added: focal > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1921504 > > Title: > Ubuntu 20.04 Install > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I installed Ubuntu 20.04. > Previous version on Dell Inspiron 1525 was version 16, the wireless > connection was working. > Now with the new install 20.04, I am getting the message No Wi-Fi Adapter > Found? > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://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 1835660] Re: initramfs unpacking failed
Works well, thank you for the update. On Fri, Mar 26, 2021, 7:31 AM Armandoobnaiala <1835...@bugs.launchpad.net> wrote: > update-initramfs: Generating /boot/initrd.img-5.8.0-45-generic > /usr/sbin/mkinitramfs: 177: COMPRESS: parameter not set > update-initramfs: failed for /boot/initrd.img-5.8.0-45-generic with 2. > > > ** Changed in: initramfs-tools (Ubuntu Focal) > Assignee: (unassigned) => Armandoobnaiala (armando1986) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1835660 > > Title: > initramfs unpacking failed > > Status in OEM Priority Project: > New > Status in grub2 package in Ubuntu: > Invalid > Status in initramfs-tools package in Ubuntu: > Invalid > Status in linux package in Ubuntu: > Fix Released > Status in grub2 source package in Focal: > Invalid > Status in initramfs-tools source package in Focal: > Invalid > Status in linux source package in Focal: > Fix Released > Status in grub2 source package in Groovy: > Invalid > Status in initramfs-tools source package in Groovy: > Invalid > Status in linux source package in Groovy: > Fix Released > Status in grub2 source package in Hirsute: > Invalid > Status in initramfs-tools source package in Hirsute: > Invalid > Status in linux source package in Hirsute: > Fix Released > > Bug description: > "initramfs unpacking failed: Decoding failed", message appears on > boot up. > > If I "update-initramfs" using gzip instead of lz, then boot up passes > without decoding failed message. > > --- > > However, we currently believe that the decoding error reported in > dmesg is actually harmless and has no impact on usability on the > system. > > Switching from lz4 to gzip compression, simply papers over the > warning, without any benefits, and slows down boot. > > Kernel should be fixed to correctly parse lz4 compressed initrds, or > at least lower the warning, to not be user visible as an error. > > [Impact] > >* Decoding failure messages in dmsg with a single lz4 initrd > >* Multiple lz4 compressed initrds cannot be decompressed by kernel, > when loaded by grub > >* Multiple lz4 compressed initrds cannot be decompressed by kernel, > when there is padding between them > > [Test Case] > >* Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 > >* Create an lz4 compressed initrd with a single test-file in it with > some content. I.e. echo "second-initrd" > test-file, and then pack > that with cpio hewc owned by root & lz4 -l. > >* Create a combined padded initrd of stock initrd, pad4, and the > test-marker initrd created above. > >* Boot above with "break=top" kernel command line. > >* With broken kernels, there should be dmesg error message that > decoding failed, and one will observe that /test-file does not exist > in the shell. > >* With fixed kernel, /test-file in the initrd shell should exist, and > should have the expected content "second-initrd". > >* The alignment and padding in the above test case depends on the > size of the first initrd => if a given padded initrd does not > reproduce the problem, try varying the size of the first initrd or > that of the padding between 0..4. > > > [Where problems could occur] > >* This changes compatible lz4 decompressor in the kernel, which can > also be used by other kernel modules such as cryptography, squashfs, > zram, f2fs, comprssed kernel image, pstore. For example, previously > rejected files with "bogus" length and extra padding may now be > accepted, whereas they were previously getting rejected by the > decompressor. > >* Ideally kernel should switch to the stable lz4 format which has > better specification of end of stream. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Released Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Released Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Fix Released Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip
[Kernel-packages] [Bug 1921504] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1921504 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921504] [NEW] Ubuntu 20.04 Install
Public bug reported: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: 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/1921504 Title: Ubuntu 20.04 Install Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04. Previous version on Dell Inspiron 1525 was version 16, the wireless connection was working. Now with the new install 20.04, I am getting the message No Wi-Fi Adapter Found? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921504/+subscriptions -- Mailing list: https://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 1921385] Re: Xorg freeze
Hello Daniel. I need your help. I installed Ubuntu 20.04 and it installed ok, but now I cannot get my wireless network connection. The previous install wireless connection worked now it is not working. Can you help? On Thu, Mar 25, 2021 at 10:25 PM Daniel van Vugt <1921...@bugs.launchpad.net> wrote: > > Thanks for the bug report. > > I can see some recurring crashes in your 'i915' kernel graphics driver > so will move this bug to the kernel. > > Also, Ubuntu 16.04 is 5 years old and not supported as well as newer > releases. We encourage you to install Ubuntu 20.04.2.0 instead: > https://ubuntu.com/download/desktop > > ** Summary changed: > > - Xorg freeze > + Crashes in i915 on Intel GM965 > > ** Package changed: xorg (Ubuntu) => linux (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1921385 > > Title: > Crashes in i915 on Intel GM965 > > Status in linux package in Ubuntu: > New > > Bug description: > The boot program is very slow. > An error dialog pops up simply stating there is a problem with the system. > If I open the details a long long list of data is shown, way above my > technical knowledge. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: xorg 1:7.7+13ubuntu3.1 > ProcVersionSignature: Ubuntu 4.15.0-140.144~16.04.1-generic 4.15.18 > Uname: Linux 4.15.0-140-generic i686 > NonfreeKernelModules: wl > .tmp.unity_support_test.0: > > ApportVersion: 2.20.1-0ubuntu2.30 > Architecture: i386 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CurrentDesktop: Unity > Date: Thu Mar 25 08:22:18 2021 > DistUpgraded: Fresh install > DistroCodename: xenial > DistroVariant: ubuntu > DkmsStatus: >bcmwl, 6.30.223.271+bdcom, 4.15.0-139-generic, i686: installed >bcmwl, 6.30.223.271+bdcom, 4.15.0-140-generic, i686: installed > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller > (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) > Subsystem: Dell Inspiron 1525 [1028:022f] > Subsystem: Dell Inspiron 1525 [1028:022f] > InstallationDate: Installed on 2021-03-17 (7 days ago) > InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 > (20190227.1) > MachineType: Dell Inc. Inspiron 1525 > ProcEnviron: >LANGUAGE=en_US >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-140-generic > root=UUID=b85df775-5de2-47b0-843b-d2f8b1f71d5e ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/27/2009 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A17 > dmi.board.vendor: Dell Inc. > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: > dmi.product.name: Inspiron 1525 > dmi.sys.vendor: Dell Inc. > version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 > version.libdrm2: libdrm2 2.4.91-2~16.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 > version.xserver-xorg-core: xserver-xorg-core N/A > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921385/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921385 Title: Crashes in i915 on Intel GM965 Status in linux package in Ubuntu: Confirmed Bug description: The boot program is very slow. An error dialog pops up simply stating there is a problem with the system. If I open the details a long long list of data is shown, way above my technical knowledge. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-140.144~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-140-generic i686 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
[Kernel-packages] [Bug 1920179] Re: System freezes when using Wacom tablet after upgrading to linux-image-5.8.0-45-generic
*** This bug is a duplicate of bug 1920632 *** https://bugs.launchpad.net/bugs/1920632 ** This bug has been marked a duplicate of bug 1920632 use of Wacom stylus causes immediate system hang with kernel 5.8.0-45, but 5.8.0-44 works -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920179 Title: System freezes when using Wacom tablet after upgrading to linux- image-5.8.0-45-generic Status in linux package in Ubuntu: Confirmed Bug description: I have an Lenovo Thinkpad Yoga 260 with a built-in Wacom digitizer. After the latest Kernel update my system freezes as soon as I put the pen on the screen. Nothing else but a forced power-off is possible. Reverting back to 5.8.0-44 is a work-around, so this seems to be a regression. The relevant entry from /var/log/apt/history.log: Start-Date: 2021-03-17 11:37:43 Commandline: apt dist-upgrade Install: linux-image-5.8.0-45-generic:amd64 (5.8.0-45.51, automatic), linux-headers-5.8.0-45:amd64 (5.8.0-45.51, automatic), linux-modules-extra-5.8.0-45-generic:amd64 (5.8.0-45.51, automatic), linux-headers-5.8.0-45-generic:amd64 (5.8.0-45.51, automatic), linux-modules-5.8.0-45-generic:amd64 (5.8.0-45.51, automatic), dctrl-tools:amd64 (2.24-3, automatic) Upgrade: update-manager-core:amd64 (1:20.10.4, 1:20.10.5), linux-headers-generic:amd64 (5.8.0.44.49, 5.8.0.45.50), linux-libc-dev:amd64 (5.8.0-44.50, 5.8.0-45.51), linux-image-generic:amd64 (5.8.0.44.49, 5.8.0.45.50), update-manager:amd64 (1:20.10.4, 1:20.10.5), dkms:amd64 (2.8.3-4, 2.8.3-4ubuntu0.1), python3-update-manager:amd64 (1:20.10.4, 1:20.10.5), libglib2.0-bin:amd64 (2.66.1-2ubuntu0.1, 2.66.1-2ubuntu0.2), libglib2.0-data:amd64 (2.66.1-2ubuntu0.1, 2.66.1-2ubuntu0.2), linux-generic:amd64 (5.8.0.44.49, 5.8.0.45.50), libglib2.0-0:amd64 (2.66.1-2ubuntu0.1, 2.66.1-2ubuntu0.2), libglib2.0-0:i386 (2.66.1-2ubuntu0.1, 2.66.1-2ubuntu0.2) End-Date: 2021-03-17 11:38:44 Apport is enabled but no crash report is generated. BTW, I found a similar bug report for Manjaro: https://forum.manjaro.org/t/system-freezes-when-using-wacom-tablet-on-5-10/50339 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.14 [origin: unknown] ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Fri Mar 19 12:41:12 2021 InstallationDate: Installed on 2020-04-14 (338 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-11-12 (127 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921498] Re: [UBUNUT 21.04] s390/vtime: fix increased steal time accounting
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Status: New => Triaged
** Changed in: linux (Ubuntu Hirsute)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Frank Heimes
(fheimes)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1921498
Title:
[UBUNUT 21.04] s390/vtime: fix increased steal time accounting
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
New
Status in linux source package in Focal:
New
Status in linux source package in Groovy:
New
Status in linux source package in Hirsute:
New
Bug description:
Description: s390/vtime: fix increased steal time accounting
Symptom: Increased steal time values.
Problem: Commit 152e9b8676c6e ("s390/vtime: steal time exponential
moving average") inadvertently changed the input value for
account_steal_time() from "cputime_to_nsecs(steal)" to just
"steal", resulting in broken increased steal time accounting.
Solution: Fix this by changing it back to "cputime_to_nsecs(steal)".
Reproduction: -
Upstream-ID: d54cb7d54877d529bc1e0e1f47a3dd082f73add3
Stable tagged : kernel 5.1.
Therefore only to be applyable for focal, groovy, hirsuite.
Due to stable tag integration , only for integration checking..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921498/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921498] [NEW] [UBUNUT 21.04] s390/vtime: fix increased steal time accounting
Public bug reported:
Description: s390/vtime: fix increased steal time accounting
Symptom: Increased steal time values.
Problem: Commit 152e9b8676c6e ("s390/vtime: steal time exponential
moving average") inadvertently changed the input value for
account_steal_time() from "cputime_to_nsecs(steal)" to just
"steal", resulting in broken increased steal time accounting.
Solution: Fix this by changing it back to "cputime_to_nsecs(steal)".
Reproduction: -
Upstream-ID: d54cb7d54877d529bc1e0e1f47a3dd082f73add3
Stable tagged : kernel 5.1.
Therefore only to be applyable for focal, groovy, hirsuite.
Due to stable tag integration , only for integration checking..
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-192225 severity-high
targetmilestone-inin2104
** Tags added: architecture-s39064 bugnameltc-192225 severity-high
targetmilestone-inin2104
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** 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/1921498
Title:
[UBUNUT 21.04] s390/vtime: fix increased steal time accounting
Status in linux package in Ubuntu:
New
Bug description:
Description: s390/vtime: fix increased steal time accounting
Symptom: Increased steal time values.
Problem: Commit 152e9b8676c6e ("s390/vtime: steal time exponential
moving average") inadvertently changed the input value for
account_steal_time() from "cputime_to_nsecs(steal)" to just
"steal", resulting in broken increased steal time accounting.
Solution: Fix this by changing it back to "cputime_to_nsecs(steal)".
Reproduction: -
Upstream-ID: d54cb7d54877d529bc1e0e1f47a3dd082f73add3
Stable tagged : kernel 5.1.
Therefore only to be applyable for focal, groovy, hirsuite.
Due to stable tag integration , only for integration checking..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921498/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
update-initramfs: Generating /boot/initrd.img-5.8.0-45-generic /usr/sbin/mkinitramfs: 177: COMPRESS: parameter not set update-initramfs: failed for /boot/initrd.img-5.8.0-45-generic with 2. ** Changed in: initramfs-tools (Ubuntu Focal) Assignee: (unassigned) => Armandoobnaiala (armando1986) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Released Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Released Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Fix Released Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
# An empty value - compcache isn't used, or added to the initramfs at all. # An integer and K (e.g. 65536 K) - use a number of kilobytes. # An integer and M (e.g. 256 M) - use a number of megabytes. # An integer and G (e.g. 1 G) - use a number of gigabytes. # An integer and % (e.g. 50 %) - use a percentage of the amount of RAM. # # You can optionally install the compcache package to configure this setting # via debconf and have userspace scripts to load and unload compcache. # COMPCACHE_SIZE="" # # COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | xz ] # stuck here -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Released Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Released Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Fix Released Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921498] [NEW] [UBUNUT 21.04] s390/vtime: fix increased steal time accounting
You have been subscribed to a public bug:
Description: s390/vtime: fix increased steal time accounting
Symptom: Increased steal time values.
Problem: Commit 152e9b8676c6e ("s390/vtime: steal time exponential
moving average") inadvertently changed the input value for
account_steal_time() from "cputime_to_nsecs(steal)" to just
"steal", resulting in broken increased steal time accounting.
Solution: Fix this by changing it back to "cputime_to_nsecs(steal)".
Reproduction: -
Upstream-ID: d54cb7d54877d529bc1e0e1f47a3dd082f73add3
Stable tagged : kernel 5.1.
Therefore only to be applyable for focal, groovy, hirsuite.
Due to stable tag integration , only for integration checking..
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-192225 severity-high
targetmilestone-inin2104
--
[UBUNUT 21.04] s390/vtime: fix increased steal time accounting
https://bugs.launchpad.net/bugs/1921498
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 1920179] Re: System freezes when using Wacom tablet after upgrading to linux-image-5.8.0-45-generic
The problem persists with linux-image-5.8.0-48. In order to keep the working version 5.8.0-44 installed, I issued 'sudo apt-mark hold linux-image-5.8.0-44-generic' for the moment. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920179 Title: System freezes when using Wacom tablet after upgrading to linux- image-5.8.0-45-generic Status in linux package in Ubuntu: Confirmed Bug description: I have an Lenovo Thinkpad Yoga 260 with a built-in Wacom digitizer. After the latest Kernel update my system freezes as soon as I put the pen on the screen. Nothing else but a forced power-off is possible. Reverting back to 5.8.0-44 is a work-around, so this seems to be a regression. The relevant entry from /var/log/apt/history.log: Start-Date: 2021-03-17 11:37:43 Commandline: apt dist-upgrade Install: linux-image-5.8.0-45-generic:amd64 (5.8.0-45.51, automatic), linux-headers-5.8.0-45:amd64 (5.8.0-45.51, automatic), linux-modules-extra-5.8.0-45-generic:amd64 (5.8.0-45.51, automatic), linux-headers-5.8.0-45-generic:amd64 (5.8.0-45.51, automatic), linux-modules-5.8.0-45-generic:amd64 (5.8.0-45.51, automatic), dctrl-tools:amd64 (2.24-3, automatic) Upgrade: update-manager-core:amd64 (1:20.10.4, 1:20.10.5), linux-headers-generic:amd64 (5.8.0.44.49, 5.8.0.45.50), linux-libc-dev:amd64 (5.8.0-44.50, 5.8.0-45.51), linux-image-generic:amd64 (5.8.0.44.49, 5.8.0.45.50), update-manager:amd64 (1:20.10.4, 1:20.10.5), dkms:amd64 (2.8.3-4, 2.8.3-4ubuntu0.1), python3-update-manager:amd64 (1:20.10.4, 1:20.10.5), libglib2.0-bin:amd64 (2.66.1-2ubuntu0.1, 2.66.1-2ubuntu0.2), libglib2.0-data:amd64 (2.66.1-2ubuntu0.1, 2.66.1-2ubuntu0.2), linux-generic:amd64 (5.8.0.44.49, 5.8.0.45.50), libglib2.0-0:amd64 (2.66.1-2ubuntu0.1, 2.66.1-2ubuntu0.2), libglib2.0-0:i386 (2.66.1-2ubuntu0.1, 2.66.1-2ubuntu0.2) End-Date: 2021-03-17 11:38:44 Apport is enabled but no crash report is generated. BTW, I found a similar bug report for Manjaro: https://forum.manjaro.org/t/system-freezes-when-using-wacom-tablet-on-5-10/50339 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.14 [origin: unknown] ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Fri Mar 19 12:41:12 2021 InstallationDate: Installed on 2020-04-14 (338 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-11-12 (127 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04
Thx Alex, that allowed me to fill the gaps and I have consolidated the SRU Justification and added it to the bug description. ** Description changed: SRU Justification: == [Impact] * Since older firmware may not support the uplink state setting, this can lead to problems. * Now expose firmware indication that it supports setting eswitch uplink state to follow the physical link. * If a kernel without the backport is used on an adapter which does not have the latest adapter firmware, the adapter silently drops outgoing traffic. * This is a regression which was introduced with kernel 5.4.0-48. [Fix] * upstream fix (as in 5.11): - 9c9be85f6b59d80efe4705109c0396df18d4e11d 9c9be85f6b59 "net/mlx5e: Add missing capability check for uplink follow" + 9c9be85f6b59d80efe4705109c0396df18d4e11d 9c9be85f6b59 "net/mlx5e: Add missing capability check for uplink follow" * backport for focal: https://launchpadlibrarian.net/529543695/0001 -Backport-net-mlx5e-Add-missing-capability-check-for-.patch * backport for groovy: https://launchpadlibrarian.net/529775887/0001 -Backport-groovy-net-mlx5e-Add-missing-capability-che.patch [Test Case] - * It requires an IBM Z or LinuxONE system, with groovy/focal installed - in LPAR and RoCE Express 2.x adapters attached. + * Two IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04 or + 20.10 on LPAR, are needed. - * ... + * Each with RoCE Express 2.x adapters (Mellanox ConnectX4/5) attached + and firmware 16.29.1006 or earlier. + + * Assign an IP address to the adapters on both systems and try to ping + one node from the other. + + * The ping will just fail with the stock Ubuntu kernels (not having the + patch), but will succeed with kernels that incl. the patches (like the + test builds from the PPA mentioned below). * Due to the lack of hardware this needs to be verified by IBM. [Regression Potential] * Undesired / erroneous behavior in case the modified if condition is assembled in a wrong way. * Again wrong behavior in case the modification of the capability bits in mlx5_ifc_cmd_hca_cap_bits are wrong. * All modification are limited to the mlx5 driver only. * The changes are relatively limited with effectively two lines removed and 4 added (three of them adjustments of the capability bits only). * The modifications were done and tested by IBM and reviewed by Mellanox (see LP comments), based on a PPA test build. [Other] * The above patch/commit was upstream accepted with kernel 5.11. * Hence the patch is not needed for hirsute, just needs to be SRUed for groovy and focal. * The commit couldn't be cleanly cherry-picked, mainly due to changed context, hence the backport(s). __ Expose firmware indication that it supports setting eswitch uplink state to follow (follow the physical link). Condition setting the eswitch uplink admin-state with this capability bit. Older FW may not support the uplink state setting. Available fix with kernel 5.11. https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d Now required for Ubuntu 20.04 via backport patch. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921104 Title: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Triaged Status in linux source package in Groovy: Triaged Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification: == [Impact] * Since older firmware may not support the uplink state setting, this can lead to problems. * Now expose firmware indication that it supports setting eswitch uplink state to follow the physical link. * If a kernel without the backport is used on an adapter which does not have the latest adapter firmware, the adapter silently drops outgoing traffic. * This is a regression which was introduced with kernel 5.4.0-48. [Fix] * upstream fix (as in 5.11): 9c9be85f6b59d80efe4705109c0396df18d4e11d 9c9be85f6b59 "net/mlx5e: Add missing capability check for uplink follow" * backport for focal: https://launchpadlibrarian.net/529543695/0001 -Backport-net-mlx5e-Add-missing-capability-check-for-.patch * backport for groovy: https://launchpadlibrarian.net/529775887/0001 -Backport-groovy-net-mlx5e-Add-missing-capability-che.patch [Test Case] * Two IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04 or 20.10 on LPAR, are needed. * Each with RoCE Express 2.x adapters (Mellanox ConnectX4/5) attached and firmware 16.29.1006 or earlier. * Assign an IP address to the adapters on both systems and try
[Kernel-packages] [Bug 1916950] Re: [amdgpu] Screen fails to wake up after sleep using 5.4.0-66, but 5.4.0-65 works
I installed the HWE kernel using : $ sudo apt-get install linux-generic-hwe-20.04 What is the recommended way to remove it and go back to the regular kernel again? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1916950 Title: [amdgpu] Screen fails to wake up after sleep using 5.4.0-66, but 5.4.0-65 works Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Status in linux-meta-hwe-5.8 package in Ubuntu: Fix Released Bug description: It looks an awful lot like this issue : https://gitlab.freedesktop.org/drm/amd/-/issues/1427. I'm hitting these: [11596.268677] [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR* dce112_get_pix_clk_dividers: Invalid parameters!! [11596.269781] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring old state failed with -22 Switching to tty2 wakes it up and allows me to switch back and recover my xorg session. Should this be filed against the kernel, xorg, or amd drivers? I'm not sure.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu Feb 25 21:07:28 2021 DistUpgraded: 2020-04-22 17:41:41,681 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-64-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed zfs, 0.8.3, 5.4.0-65-generic, x86_64: installed zfs, 0.8.3, 5.4.0-66-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701] InstallationDate: Installed on 2019-08-15 (560 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-66-generic root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash amd_iommu=on iommu=pt video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset usbhid.quirks=0x1b1c:0x1b44:0x2408 usbcore.quirks=1b1c:1b44:gn crashkernel=384M vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-22 (309 days ago) dmi.bios.date: 02/17/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33c:bd02/17/2021:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
[Kernel-packages] [Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04
** Description changed: + SRU Justification: + == + + [Impact] + + * Since older firmware may not support the uplink state setting, this + can lead to problems. + + * Now expose firmware indication that it supports setting eswitch uplink + state to follow the physical link. + + * If a kernel without the backport is used on an adapter which does not + have the latest adapter firmware, the adapter silently drops outgoing + traffic. + + * This is a regression which was introduced with kernel 5.4.0-48. + + [Fix] + + * upstream fix (as in 5.11): + 9c9be85f6b59d80efe4705109c0396df18d4e11d 9c9be85f6b59 "net/mlx5e: Add missing capability check for uplink follow" + + * backport for focal: https://launchpadlibrarian.net/529543695/0001 + -Backport-net-mlx5e-Add-missing-capability-check-for-.patch + + * backport for groovy: https://launchpadlibrarian.net/529775887/0001 + -Backport-groovy-net-mlx5e-Add-missing-capability-che.patch + + [Test Case] + + * It requires an IBM Z or LinuxONE system, with groovy/focal installed + in LPAR and RoCE Express 2.x adapters attached. + + * ... + + * Due to the lack of hardware this needs to be verified by IBM. + + [Regression Potential] + + * Undesired / erroneous behavior in case the modified if condition is + assembled in a wrong way. + + * Again wrong behavior in case the modification of the capability bits + in mlx5_ifc_cmd_hca_cap_bits are wrong. + + * All modification are limited to the mlx5 driver only. + + * The changes are relatively limited with effectively two lines removed + and 4 added (three of them adjustments of the capability bits only). + + * The modifications were done and tested by IBM and reviewed by Mellanox + (see LP comments), based on a PPA test build. + + [Other] + + * The above patch/commit was upstream accepted with kernel 5.11. + + * Hence the patch is not needed for hirsute, just needs to be SRUed for + groovy and focal. + + * The commit couldn't be cleanly cherry-picked, mainly due to changed + context, hence the backport(s). + + __ + Expose firmware indication that it supports setting eswitch uplink state to follow (follow the physical link). Condition setting the eswitch uplink admin-state with this capability bit. Older FW may not support the uplink state setting. Available fix with kernel 5.11. https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d Now required for Ubuntu 20.04 via backport patch. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921104 Title: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Triaged Status in linux source package in Groovy: Triaged Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification: == [Impact] * Since older firmware may not support the uplink state setting, this can lead to problems. * Now expose firmware indication that it supports setting eswitch uplink state to follow the physical link. * If a kernel without the backport is used on an adapter which does not have the latest adapter firmware, the adapter silently drops outgoing traffic. * This is a regression which was introduced with kernel 5.4.0-48. [Fix] * upstream fix (as in 5.11): 9c9be85f6b59d80efe4705109c0396df18d4e11d 9c9be85f6b59 "net/mlx5e: Add missing capability check for uplink follow" * backport for focal: https://launchpadlibrarian.net/529543695/0001 -Backport-net-mlx5e-Add-missing-capability-check-for-.patch * backport for groovy: https://launchpadlibrarian.net/529775887/0001 -Backport-groovy-net-mlx5e-Add-missing-capability-che.patch [Test Case] * It requires an IBM Z or LinuxONE system, with groovy/focal installed in LPAR and RoCE Express 2.x adapters attached. * ... * Due to the lack of hardware this needs to be verified by IBM. [Regression Potential] * Undesired / erroneous behavior in case the modified if condition is assembled in a wrong way. * Again wrong behavior in case the modification of the capability bits in mlx5_ifc_cmd_hca_cap_bits are wrong. * All modification are limited to the mlx5 driver only. * The changes are relatively limited with effectively two lines removed and 4 added (three of them adjustments of the capability bits only). * The modifications were done and tested by IBM and reviewed by Mellanox (see LP comments), based on a PPA test build. [Other] * The above patch/commit was upstream accepted with kernel 5.11. * Hence the patch is not needed for hirsute, just needs to be SRUed for groovy and focal. * The commit couldn't be cleanly cherry-picked, mainly due to changed context,
[Kernel-packages] [Bug 1921104] Comment bridged from LTC Bugzilla
--- Comment From alexs...@de.ibm.com 2021-03-26 06:23 EDT--- Additions for the Impact statement: [Impact] * Since older firmware may not support the uplink state setting, this can lead to problems. * Now expose firmware indication that it supports setting eswitch uplink state to follow the physical link. * If a kernel without the backport is used on an adapter which does not have the latest adapter firmware, the adapter silently drops outgoing traffic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921104 Title: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Triaged Status in linux source package in Groovy: Triaged Status in linux source package in Hirsute: Fix Released Bug description: Expose firmware indication that it supports setting eswitch uplink state to follow (follow the physical link). Condition setting the eswitch uplink admin-state with this capability bit. Older FW may not support the uplink state setting. Available fix with kernel 5.11. https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d Now required for Ubuntu 20.04 via backport patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921477] Re: After suspend CUDA is not working any more
It looks like following is working also. Create a file /etc/modules- load.d/nvidia.conf with contents below and restart. options nvidia NVreg_PreserveVideoMemoryAllocations=1 options nvidia NVreg_TemporaryFilePath=/run -- 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/1921477 Title: After suspend CUDA is not working any more Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: After suspend the CUDA library can not get a connection to the GPU any more. There is following workaround possible: sudo rmmod nvidia_uvm sudo modprobe nvidia_uvm This could be automated in an event script however it is not helping if there are applications running already which depend on CUDA connection. The module will be refused to unload due to its usage then. System environment: Description:Ubuntu 20.04.2 LTS Release:20.04 +-+ | NVIDIA-SMI 460.32.03Driver Version: 460.32.03CUDA Version: 11.2 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 GeForce GTX 1650On | :01:00.0 Off | N/A | | N/A 53CP5 9W / N/A | 2015MiB / 3911MiB | 5% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 2924 G /usr/lib/xorg/Xorg768MiB | |0 N/A N/A 5018 G xfwm4 2MiB | |0 N/A N/A 8227 G /opt/idea/jbr/bin/java 2MiB | |0 N/A N/A255790 G ...A= --shared-files 66MiB | |0 N/A N/A267569C+G jdks/openjdk-15/bin/java 1168MiB | +-+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1921477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921104] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-03-26 05:16 EDT--- SRU Justification: [Impact] * Since older firmware may not support the uplink state setting, this can lead to problems. * Now expose firmware indication that it supports setting eswitch uplink state to follow the physical link. * <... some more details are needed on how things fail today, w/o the patch> [Fix] * upstream fix (as in 5.11): 9c9be85f6b59d80efe4705109c0396df18d4e11d 9c9be85f6b59 "net/mlx5e: Add missing capability check for uplink follow" https://launchpadlibrarian.net/529543695/0001-Backport-net-mlx5e-Add- missing-capability-check-for-.patch * backport for groovy: https://launchpadlibrarian.net/529775887/0001-Backport-groovy-net-mlx5e-Add-missing-capability-che.patch [Test Case] * It requires an IBM Z or LinuxONE system, with groovy/focal installed in LPAR and RoCE Express 2.x adapters attached. * Due to the lack of hardware this needs to be verifid by IBM. [Regression Potential] * This backport fixes a regression which was introduced with the kernel 5.4.0-48 update for Ubuntu 20.04. [Other] * The above patch/commit was upstream accepted with kernel 5.11. * Hence the patch is not needed for hirsute, just SRUs for groovy and focal are needed. * But the commit couldn't be cleanly cherry-picked, due to changed context, hence the backport(s). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921104 Title: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Triaged Status in linux source package in Groovy: Triaged Status in linux source package in Hirsute: Fix Released Bug description: Expose firmware indication that it supports setting eswitch uplink state to follow (follow the physical link). Condition setting the eswitch uplink admin-state with this capability bit. Older FW may not support the uplink state setting. Available fix with kernel 5.11. https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d Now required for Ubuntu 20.04 via backport patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921477] [NEW] After suspend CUDA is not working any more
Public bug reported: After suspend the CUDA library can not get a connection to the GPU any more. There is following workaround possible: sudo rmmod nvidia_uvm sudo modprobe nvidia_uvm This could be automated in an event script however it is not helping if there are applications running already which depend on CUDA connection. The module will be refused to unload due to its usage then. System environment: Description:Ubuntu 20.04.2 LTS Release:20.04 +-+ | NVIDIA-SMI 460.32.03Driver Version: 460.32.03CUDA Version: 11.2 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 GeForce GTX 1650On | :01:00.0 Off | N/A | | N/A 53CP5 9W / N/A | 2015MiB / 3911MiB | 5% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 2924 G /usr/lib/xorg/Xorg768MiB | |0 N/A N/A 5018 G xfwm4 2MiB | |0 N/A N/A 8227 G /opt/idea/jbr/bin/java 2MiB | |0 N/A N/A255790 G ...A= --shared-files 66MiB | |0 N/A N/A267569C+G jdks/openjdk-15/bin/java 1168MiB | +-+ ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1921477 Title: After suspend CUDA is not working any more Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: After suspend the CUDA library can not get a connection to the GPU any more. There is following workaround possible: sudo rmmod nvidia_uvm sudo modprobe nvidia_uvm This could be automated in an event script however it is not helping if there are applications running already which depend on CUDA connection. The module will be refused to unload due to its usage then. System environment: Description:Ubuntu 20.04.2 LTS Release:20.04 +-+ | NVIDIA-SMI 460.32.03Driver Version: 460.32.03CUDA Version: 11.2 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 GeForce GTX 1650On | :01:00.0 Off | N/A | | N/A 53CP5 9W / N/A | 2015MiB / 3911MiB | 5% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 2924 G /usr/lib/xorg/Xorg768MiB | |0 N/A N/A 5018 G xfwm4 2MiB | |0 N/A N/A 8227 G /opt/idea/jbr/bin/java 2MiB | |0 N/A N/A255790 G ...A= --shared-files 66MiB | |0 N/A N/A267569C+G
[Kernel-packages] [Bug 1900438] Re: Bcache bypasse writeback on caching device with fragmentation
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => dongdong tao (taodd)
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1900438
Title:
Bcache bypasse writeback on caching device with fragmentation
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
[Impact]
This bug in bcache affects I/O performance on all versions of the kernel
[correct versions affected]. It is particularly negative on ceph if used with
bcache.
Write I/O latency would suddenly go to around 1 second from around 10
ms when hitting this issue and would easily be stuck there for hours
or even days, especially bad for ceph on bcache architecture. This
would make ceph extremely slow and make the entire cloud almost
unusable.
The root cause is that the dirty bucket had reached the 70 percent
threshold, thus causing all writes to go direct to the backing HDD
device. It might be fine if it actually had a lot of dirty data, but
this happens when dirty data has not even reached over 10 percent, due
to having high memory fragmentation. What makes it worse is that the
writeback rate might be still at minimum value (8) due to the
writeback percent not reached, so it takes ages for bcache to really
reclaim enough dirty buckets to get itself out of this situation.
[Fix]
* 71dda2a5625f31bc3410cb69c3d31376a2b66f28 “bcache: consider the
fragmentation when update the writeback rate”
The current way to calculate the writeback rate only considered the dirty
sectors.
This usually works fine when memory fragmentation is not high, but it will
give us an unreasonably low writeback rate when we are in the situation that a
few dirty sectors have consumed a lot of dirty buckets. In some cases, the
dirty buckets reached CUTOFF_WRITEBACK_SYNC (i.e., stopped writeback) while
the dirty data (sectors) had not even reached the writeback_percent threshold
(i.e., started writeback). In that situation, the writeback rate will still be
the minimum value (8*512 = 4KB/s), thus it will cause all the writes to bestuck
in a non-writeback mode because of the slow writeback.
We accelerate the rate in 3 stages with different aggressiveness:
the first stage starts when dirty buckets percent reach above
BCH_WRITEBACK_FRAGMENT_THRESHOLD_LOW (50),
the second is BCH_WRITEBACK_FRAGMENT_THRESHOLD_MID (57),
the third is BCH_WRITEBACK_FRAGMENT_THRESHOLD_HIGH (64).
By default the first stage tries to writeback the amount of dirty data
in one bucket (on average) in (1 / (dirty_buckets_percent - 50)) seconds,
the second stage tries to writeback the amount of dirty data in one bucket
in (1 / (dirty_buckets_percent - 57)) * 100 milliseconds, the third
stage tries to writeback the amount of dirty data in one bucket in
(1 / (dirty_buckets_percent - 64)) milliseconds.
The initial rate at each stage can be controlled by 3 configurable
parameters:
writeback_rate_fp_term_{low|mid|high}
They are by default 1, 10, 1000, chosen based on testing and
production data, detailed below.
A. When it comes to the low stage, it is still far from the 70%
threshold, so we only want to give it a little bit push by setting the
term to 1, it means the initial rate will be 170 if the fragment is 6,
it is calculated by bucket_size/fragment, this rate is very small,
but still much more reasonable than the minimum 8.
For a production bcache with non-heavy workload, if the cache device
is bigger than 1 TB, it may take hours to consume 1% buckets,
so it is very possible to reclaim enough dirty buckets in this stage,
thus to avoid entering the next stage.
B. If the dirty buckets ratio didn’t turn around during the first stage,
it comes to the mid stage, then it is necessary for mid stage
to be more aggressive than low stage, so the initial rate is chosen
to be 10 times more than the low stage, which means 1700 as the initial
rate if the fragment is 6. This is a normal rate
we usually see for a normal workload when writeback happens
because of writeback_percent.
C. If the dirty buckets ratio didn't turn around during the low
[Kernel-packages] [Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04
Additional comment for the SRU description: this backport fixes a regression which was introduced with the kernel 5.4.0-48 update for Ubuntu 20.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921104 Title: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Triaged Status in linux source package in Groovy: Triaged Status in linux source package in Hirsute: Fix Released Bug description: Expose firmware indication that it supports setting eswitch uplink state to follow (follow the physical link). Condition setting the eswitch uplink admin-state with this capability bit. Older FW may not support the uplink state setting. Available fix with kernel 5.11. https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d Now required for Ubuntu 20.04 via backport patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900438] Re: Bcache bypasse writeback on caching device with fragmentation
** Description changed:
SRU Justification:
[Impact]
- This bug in bcache [insert correct area] affects I/O performance on all
versions of the kernel [correct versions affected]. It is particularly negative
on ceph if used with bcache.
+ This bug in bcache affects I/O performance on all versions of the kernel
[correct versions affected]. It is particularly negative on ceph if used with
bcache.
Write I/O latency would suddenly go to around 1 second from around 10 ms
when hitting this issue and would easily be stuck there for hours or
even days, especially bad for ceph on bcache architecture. This would
make ceph extremely slow and make the entire cloud almost unusable.
The root cause is that the dirty bucket had reached the 70 percent
threshold, thus causing all writes to go direct to the backing HDD
device. It might be fine if it actually had a lot of dirty data, but
this happens when dirty data has not even reached over 10 percent, due
to having high memory fragmentation. What makes it worse is that the
writeback rate might be still at minimum value (8) due to the writeback
percent not reached, so it takes ages for bcache to really reclaim
enough dirty buckets to get itself out of this situation.
[Fix]
* 71dda2a5625f31bc3410cb69c3d31376a2b66f28 “bcache: consider the
fragmentation when update the writeback rate”
- The current way to calculate the writeback rate only considered the dirty
sectors.
+ The current way to calculate the writeback rate only considered the dirty
sectors.
This usually works fine when memory fragmentation is not high, but it will
give us an unreasonably low writeback rate when we are in the situation that a
few dirty sectors have consumed a lot of dirty buckets. In some cases, the
dirty buckets reached CUTOFF_WRITEBACK_SYNC (i.e., stopped writeback) while
the dirty data (sectors) had not even reached the writeback_percent threshold
(i.e., started writeback). In that situation, the writeback rate will still be
the minimum value (8*512 = 4KB/s), thus it will cause all the writes to bestuck
in a non-writeback mode because of the slow writeback.
We accelerate the rate in 3 stages with different aggressiveness:
- the first stage starts when dirty buckets percent reach above
BCH_WRITEBACK_FRAGMENT_THRESHOLD_LOW (50),
+ the first stage starts when dirty buckets percent reach above
BCH_WRITEBACK_FRAGMENT_THRESHOLD_LOW (50),
the second is BCH_WRITEBACK_FRAGMENT_THRESHOLD_MID (57),
- the third is BCH_WRITEBACK_FRAGMENT_THRESHOLD_HIGH (64).
+ the third is BCH_WRITEBACK_FRAGMENT_THRESHOLD_HIGH (64).
By default the first stage tries to writeback the amount of dirty data
in one bucket (on average) in (1 / (dirty_buckets_percent - 50)) seconds,
the second stage tries to writeback the amount of dirty data in one bucket
in (1 / (dirty_buckets_percent - 57)) * 100 milliseconds, the third
stage tries to writeback the amount of dirty data in one bucket in
(1 / (dirty_buckets_percent - 64)) milliseconds.
The initial rate at each stage can be controlled by 3 configurable
- parameters:
+ parameters:
writeback_rate_fp_term_{low|mid|high}
They are by default 1, 10, 1000, chosen based on testing and production
data, detailed below.
A. When it comes to the low stage, it is still far from the 70%
-threshold, so we only want to give it a little bit push by setting the
-term to 1, it means the initial rate will be 170 if the fragment is 6,
-it is calculated by bucket_size/fragment, this rate is very small,
-but still much more reasonable than the minimum 8.
-For a production bcache with non-heavy workload, if the cache device
-is bigger than 1 TB, it may take hours to consume 1% buckets,
-so it is very possible to reclaim enough dirty buckets in this stage,
-thus to avoid entering the next stage.
+ threshold, so we only want to give it a little bit push by setting the
+ term to 1, it means the initial rate will be 170 if the fragment is 6,
+ it is calculated by bucket_size/fragment, this rate is very small,
+ but still much more reasonable than the minimum 8.
+ For a production bcache with non-heavy workload, if the cache device
+ is bigger than 1 TB, it may take hours to consume 1% buckets,
+ so it is very possible to reclaim enough dirty buckets in this stage,
+ thus to avoid entering the next stage.
B. If the dirty buckets ratio didn’t turn around during the first stage,
-it comes to the mid stage, then it is necessary for mid stage
-to be more aggressive than low stage, so the initial rate is chosen
-to be 10 times more than the low stage, which means 1700 as the initial
-rate if the fragment is 6. This is a normal rate
-we usually see for a normal workload when writeback happens
-because of writeback_percent.
+ it comes to the mid stage, then it is necessary for mid stage
+ to be more aggressive than
[Kernel-packages] [Bug 1914668] Re: Exploitable vulnerabilities in AF_VSOCK implementation
** Changed in: linux-hwe-5.8 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1914668
Title:
Exploitable vulnerabilities in AF_VSOCK implementation
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.8 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Fix Released
Status in linux-riscv package in Ubuntu:
Fix Released
Status in linux-hwe-5.8 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Committed
Bug description:
https://www.openwall.com/lists/oss-security/2021/02/04/5
The following mainline patch is required for all kernels >= v5.8:
{focal hwe-5.8, groovy, hirsute}:
[linux] c518adafa39f vsock: fix the race conditions in multi-transport
support
or [linux-5.10-y] 55d900415b81 vsock: fix the race conditions in
multi-transport support
[Impact]
* Patches an exploitable vulnerability.
[Test Case]
* See disclosure article.
[Regression Potential]
* Low: straightforward race condition fix; upstream cherry-pick.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914668/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
The link of Nvidia SRU testing results are following, no regressions were found. 460.56: https://docs.google.com/spreadsheets/d/13fPRPMELE6Fal2xNE- dTDZFJXJ0djH7W3tq0dJa0nB0/edit?usp=sharing 450.102.04: https://docs.google.com/spreadsheets/d /17BZZANxJgWXXX0B6OnNY37NI7zMU6F-qTOQybA7Izbk/edit?usp=sharing 390.141: https://docs.google.com/spreadsheets/d/1c8ITvWs2zyBttt9m- dLmHHYzpfQMbRoHxx0Re8-6Fzw/edit?usp=sharing -- 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/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [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 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cuda-11.2-1. == 460-server == * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in,
[Kernel-packages] [Bug 1908677] Re: Dell Latitude 9510 capture volume is too low
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1908677 Title: Dell Latitude 9510 capture volume is too low Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Bug description: [Impact] * The internal mic default volume is too low A upstream commit correct the init configuration [Test Case] * Using gnome-sound-recoder to record audio without tweak capture volume The volume is very low * Try to update the init.conf mentioned by https://github.com/alsa-project/alsa-ucm-conf/commit/263bd26b1216c933db3d216197a78678d0f8610e $ alsactl init $ amixer cget name='rt715 ADC 07 Capture Volume' numid=14,iface=MIXER,name='rt715 ADC 07 Capture Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0 : values=58,58 | dBscale-min=-17.25dB,step=0.75dB,mute=0 * Using gnome-sound-recorder to record again The volume is significantly improved [Where problems could occur] * The change only apply to the hardware with rt715 codec. * [racb] Is there any other hardware that isn't being tested that uses this codec? * The change adjust the volume only, but not change other control, the worst case is the change doesn't take effect. [Other Info] * The change has been verified on Latitude 9510. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1908677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919930] Re: power off stress test will hang on the TGL machines
tested on the lenovo machine, stress poweroff not hang ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1919930 Title: power off stress test will hang on the TGL machines Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: In Progress Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: Intel suggested that we do 2 actions to fix this problem, the 1st is merging 5 kernel patches, this only applies to H and OEM-5.10 since there is no tgl.c in the groovy kernel yet. the 2nd is change a kernel config, this change applies to H, G and OEM-5.10. https://github.com/thesofproject/linux/issues/2781 [Impact] When we run poweroff/on stress test on some lenovo TGL laptop, the system will randomly hang, and when this issue happens, the dmesg shows the sof audio driver fails. [Fix] Intel recommend that we backport 5 kernel patches and change a kernel config. [Test] After applying the changes, and test on TGL/cml/whl machines, the audio function works as good as before, and the poweroff stress test didn't hang anymore. [Where problems could occur] The kernel patches probably could introduce issues when system powre off or reboot on TGL machines, but this possibility is low since we have tested these patches on different TGL machines. the kernel option change could introduce power consumption regression, but it only affects power saving and package_cstate values when any capture stream is active, while no impact if all capture streams are inactive. that is to say, in theory it will not impact the power consumption in short idle or long idle. And I checked the system cound enter package_c10 after this change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1919930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908677] Re: Dell Latitude 9510 capture volume is too low
Test on Latitude 9510 with 5.10.0-1020-oem kernel, BIOS: 1.4.2 with, codename: focal 1. enable proposed channel 2. $ sudo apt install alsa-ucm-conf 3. $ alsactl init 4. $ amixer cget name='rt715 ADC 07 Capture Volume' numid=14,iface=MIXER,name='rt715 ADC 07 Capture Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0 : values=58,58 | dBscale-min=-17.25dB,step=0.75dB,mute=0 And capture volume is improved. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1908677 Title: Dell Latitude 9510 capture volume is too low Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Bug description: [Impact] * The internal mic default volume is too low A upstream commit correct the init configuration [Test Case] * Using gnome-sound-recoder to record audio without tweak capture volume The volume is very low * Try to update the init.conf mentioned by https://github.com/alsa-project/alsa-ucm-conf/commit/263bd26b1216c933db3d216197a78678d0f8610e $ alsactl init $ amixer cget name='rt715 ADC 07 Capture Volume' numid=14,iface=MIXER,name='rt715 ADC 07 Capture Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0 : values=58,58 | dBscale-min=-17.25dB,step=0.75dB,mute=0 * Using gnome-sound-recorder to record again The volume is significantly improved [Where problems could occur] * The change only apply to the hardware with rt715 codec. * [racb] Is there any other hardware that isn't being tested that uses this codec? * The change adjust the volume only, but not change other control, the worst case is the change doesn't take effect. [Other Info] * The change has been verified on Latitude 9510. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1908677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913259] Re: Intel AX201 Wi-Fi [8086:43f0] subsystem [1a56:1652]: Direct firmware load for (efault)128.ucode failed with error -2
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/1913259 Title: Intel AX201 Wi-Fi [8086:43f0] subsystem [1a56:1652]: Direct firmware load for (efault)128.ucode failed with error -2 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 source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: Won't Fix Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: 00:14.3 Network controller [0280]: Intel Corporation Device [8086:43f0] Subsystem: Bigfoot Networks, Inc. Device [1a56:1652] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: iwlwifi In dmesg: [ 4.146811] Intel(R) Wireless WiFi driver for Linux [ 4.146866] iwlwifi :00:14.3: enabling device ( -> 0002) [ 4.155371] iwlwifi :00:14.3: Direct firmware load for (efault)128.ucode failed with error -2 [ 4.155388] iwlwifi :00:14.3: Direct firmware load for (efault)127.ucode failed with error -2 [ 4.155486] iwlwifi :00:14.3: Direct firmware load for (efault)126.ucode failed with error -2 [ 4.155585] iwlwifi :00:14.3: Direct firmware load for (efault)125.ucode failed with error -2 [ 4.155596] iwlwifi :00:14.3: Direct firmware load for (efault)124.ucode failed with error -2 [ 4.155606] iwlwifi :00:14.3: Direct firmware load for (efault)123.ucode failed with error -2 [ 4.155617] iwlwifi :00:14.3: Direct firmware load for (efault)122.ucode failed with error -2 [ 4.155628] iwlwifi :00:14.3: Direct firmware load for (efault)121.ucode failed with error -2 [ 4.155639] iwlwifi :00:14.3: Direct firmware load for (efault)120.ucode failed with error -2 [ 4.155649] iwlwifi :00:14.3: Direct firmware load for (efault)119.ucode failed with error -2 [ 4.155660] iwlwifi :00:14.3: Direct firmware load for (efault)118.ucode failed with error -2 [ 4.155670] iwlwifi :00:14.3: Direct firmware load for (efault)117.ucode failed with error -2 [ 4.155683] iwlwifi :00:14.3: Direct firmware load for (efault)116.ucode failed with error -2 [ 4.155693] iwlwifi :00:14.3: Direct firmware load for (efault)115.ucode failed with error -2 [ 4.155704] iwlwifi :00:14.3: Direct firmware load for (efault)114.ucode failed with error -2 [ 4.155716] iwlwifi :00:14.3: Direct firmware load for (efault)113.ucode failed with error -2 [ 4.155727] iwlwifi :00:14.3: Direct firmware load for (efault)112.ucode failed with error -2 [ 4.155817] iwlwifi :00:14.3: Direct firmware load for (efault)111.ucode failed with error -2 [ 4.155829] iwlwifi :00:14.3: Direct firmware load for (efault)110.ucode failed with error -2 [ 4.155840] iwlwifi :00:14.3: Direct firmware load for (efault)109.ucode failed with error -2 [ 4.155851] iwlwifi :00:14.3: Direct firmware load for (efault)108.ucode failed with error -2 [ 4.155863] iwlwifi :00:14.3: Direct firmware load for (efault)107.ucode failed with error -2 [ 4.155874] iwlwifi :00:14.3: Direct firmware load for (efault)106.ucode failed with error -2 [ 4.155884] iwlwifi :00:14.3: Direct firmware load for (efault)105.ucode failed with error -2 [ 4.155895] iwlwifi :00:14.3: Direct firmware load for (efault)104.ucode failed with error -2 [ 4.155907] iwlwifi :00:14.3: Direct firmware load for (efault)103.ucode failed with error -2 [ 4.155919] iwlwifi :00:14.3: Direct firmware load for (efault)102.ucode failed with error -2 [ 4.155930] iwlwifi :00:14.3: Direct firmware load for (efault)101.ucode failed with error -2 [ 4.155941] iwlwifi :00:14.3: Direct firmware load for (efault)100.ucode failed with error -2 [ 4.155953] iwlwifi :00:14.3: Direct firmware load for (efault)99.ucode failed with error -2 [ 4.155964] iwlwifi :00:14.3: Direct firmware load for
[Kernel-packages] [Bug 1919930] Re: power off stress test will hang on the TGL machines
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/1919930 Title: power off stress test will hang on the TGL machines Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: In Progress Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: Intel suggested that we do 2 actions to fix this problem, the 1st is merging 5 kernel patches, this only applies to H and OEM-5.10 since there is no tgl.c in the groovy kernel yet. the 2nd is change a kernel config, this change applies to H, G and OEM-5.10. https://github.com/thesofproject/linux/issues/2781 [Impact] When we run poweroff/on stress test on some lenovo TGL laptop, the system will randomly hang, and when this issue happens, the dmesg shows the sof audio driver fails. [Fix] Intel recommend that we backport 5 kernel patches and change a kernel config. [Test] After applying the changes, and test on TGL/cml/whl machines, the audio function works as good as before, and the poweroff stress test didn't hang anymore. [Where problems could occur] The kernel patches probably could introduce issues when system powre off or reboot on TGL machines, but this possibility is low since we have tested these patches on different TGL machines. the kernel option change could introduce power consumption regression, but it only affects power saving and package_cstate values when any capture stream is active, while no impact if all capture streams are inactive. that is to say, in theory it will not impact the power consumption in short idle or long idle. And I checked the system cound enter package_c10 after this change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1919930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919123] Re: Dell Precision 5550 takes up to 10 seconds to respond when coming out of sleep
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/1919123 Title: Dell Precision 5550 takes up to 10 seconds to respond when coming out of sleep Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] On some platforms, the EC doesn't support the register reading sequence for sentelic[1], and then make the EC can't respond commands for a while when probing. It leads to the keyboard is non-responsive for around 10 seconds while waking up from s2idle. [ 44.304488] i8042: [9804] d4 -> i8042 (command) [ 44.304634] i8042: [9804] f3 -> i8042 (parameter) [ 44.304787] i8042: [9804] fa <- i8042 (interrupt, 1, 12) [ 44.304855] i8042: [9804] d4 -> i8042 (command) [ 44.304938] i8042: [9804] 66 -> i8042 (parameter) [ 44.337698] i8042: [9813] d4 -> i8042 (command) [ 44.905695] i8042: [9942] 88 -> i8042 (parameter) [ 45.497478] i8042: [10102] d4 -> i8042 (command) [ 46.098041] i8042: [10253] f3 -> i8042 (parameter) [ 46.098070] i8042: [10253] fe <- i8042 (interrupt, 1, 12) [ 46.718154] i8042: [10386] d4 -> i8042 (command) [ 47.309915] i8042: [10386] f4 -> i8042 (parameter) [ 47.918961] i8042: [10556] d4 -> i8042 (command) [ 48.402624] i8042: [10556] f6 -> i8042 (parameter) [Fix] A DMI quirk to mark this platform doesn't have aux device could avoid those commands to be sent. And the system could still using i2c interface to communicate with the touchpad. https://lkml.org/lkml/2021/3/15/126 [Test] Verified on Dell Precision 5550 [Where problem could occur] The quirk only affects the listed platform, there is no regression could occur. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1919123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916554] Re: Cirrus Audio Codec CS8409/CS42L42 support
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/1916554 Title: Cirrus Audio Codec CS8409/CS42L42 support 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 source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] No driver for Cirrus CS8409 HDA bridge/CS42L42 codec, no playback/capture device available. [Fix] Patchset https://lore.kernel.org/alsa-devel/20210306111934.4832-1-vita...@opensource.cirrus.com/ currently in https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git branch for-next. [Test Case] On platform with Cirrus CS8409 HDA bridge: /sys/class/sound/card0/device/$ cat hdaudioC0D0/vendor_* 0x10138409 Cirrus Logic /sys/class/sound/card0/device/$ cat hdaudioC0D0/chip_name Generic Its chip_name should be updated with correct model name and sound system should be working: /sys/class/sound/card0/device/$ cat hdaudioC0D0/chip_name CS8409/CS42L42 APLAY and ARECORD should also list new audio devices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CS8409/CS42L42 Analog [CS8409/CS42L42 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CS8409/CS42L42 Analog [CS8409/CS42L42 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 [Where problems could occur] New device driver landing, may bring in new issues bound to new driver/device configuration such as suspend/resume issues. == original bug description == $ sudo dmesg|grep hda [ 19.253994] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [ 19.254515] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 19.317386] snd_hda_codec_generic hdaudioC0D0: autoconfig for Generic: line_outs=1 (0x2c/0x0/0x0/0x0/0x0) type:speaker [ 19.317390] snd_hda_codec_generic hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 19.317392] snd_hda_codec_generic hdaudioC0D0:hp_outs=1 (0x24/0x0/0x0/0x0/0x0) [ 19.317393] snd_hda_codec_generic hdaudioC0D0:mono: mono_out=0x0 [ 19.317395] snd_hda_codec_generic hdaudioC0D0:inputs: [ 19.317397] snd_hda_codec_generic hdaudioC0D0: Internal Mic=0x44 [ 19.317399] snd_hda_codec_generic hdaudioC0D0: Mic=0x34 Vendor driver in progress: https://github.com/CirrusLogic/product-support/tree/cs8409_hda Upstream submission: https://patchwork.kernel.org/project/alsa-devel/list/?series=441331 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1013-oem 5.10.0-1013.14 ProcVersionSignature: Ubuntu 5.10.0-1013.14-oem 5.10.6 Uname: Linux 5.10.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 22 22:13:32 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-beric-icl+X44 InstallationDate: Installed on 2021-02-04 (18 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.10 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1673 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
[Kernel-packages] [Bug 1918134] Re: LRMv4: switch to signing nvidia modules via the Ubuntu Modules signing key
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-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1918134 Title: LRMv4: switch to signing nvidia modules via the Ubuntu Modules signing key Status in linux package in Ubuntu: In Progress Status in linux-restricted-modules package in Ubuntu: Fix Released Bug description: To allow decoupling of nvidia-graphics-drivers- streams and versions from the underlying kernel versions we wish to be able to sign new kernel modules into an existing kernel after the fact. Under bug #1898716 we added support for an Ubuntu Modules signing key certificate. Rebuild the LRM package to make use of this new signature. This involves splitting the LRM package into three. linux-restricted- modules first builds the nvidia-graphics-drivers-* we require signed. linux-restricted-generate then consumes the .o's produced in that build and forms a signing custom binary upload for this. linux- restricted-signatures then consumes the signing result from the LRG upload and expresses clean redistributible signatures which are consumed by LRM at installation time. LRG must be embargoed as it (necessarily) generates fully formed .ko files for signing. Additional process is added to the kernel build life-cycle to handle the privacy requirements of the LRG/LRS interaction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918378] Re: Cirrus Audio Codec CS8409/CS42L42: Input Device does not switch to headset Mic when a headset is inserted
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/1918378 Title: Cirrus Audio Codec CS8409/CS42L42: Input Device does not switch to headset Mic when a headset is inserted 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 source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [SRU Justfication] BugLink: https://bugs.launchpad.net/bugs/1918378 [Impact] With headset/mic injected, GNOME Settings does not update record volume control option to the headset one automatically. [Fix] https://github.com/CirrusLogic/product- support/blob/82915ae88a02781b173c83568426722789d74f37/dell/hda/5.10.7/0001 -ALSA-hda-cirrus-Fix-Headset-Mic-volume-control-name.patch [Test Case] Tested on affected platform. With the patch, both playback and record volume control will be updated simultaneously. [Where problems could occur] Control object name string update only. [Other Info] This is a follow-up for patchset https://lists.ubuntu.com/archives/kernel-team/2021-March/117814.html titled "Cirrus CS8409 HDA bridge/CS42L42 codec support". == original bug description == Steps: 1. With the latest test kernel from Vicamo's PPA as of 3/8 2. Plug in a headset Expected behavior: Input Device should switch to Headset Microphone - Built-in Audio Actual behavior: Input Device remains at Microphone - Built-in Audio and users need to manually switch to correct Input Device for the audio recording via headset to work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1918378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920030] Re: Mute/Mic-mute LEDs are not work on HP 850/840/440 G8 Laptops
This bug 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/1920030 Title: Mute/Mic-mute LEDs are not work on HP 850/840/440 G8 Laptops Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 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 source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: New Bug description: [Impact] The Mute/Mic-mute LEDs are not work when muting audio-output/microphone on HP 850/840/440 G8 laptops. [Fix] Add three realtek quirks for them. [Test] After applying the quirks, the LEDs are functioned on HP 850/840/440 G8 laptops. [Where problems could occur] If HP ships the different system boards design with the same subsystem IDs of audio codec which are using different GPIO pins (different layout), then the quirks will not work (LEDs will not function when muting audio-output or microphone. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920874] Re: [Regression] Partition not removed after removing the memory cards from card reader since kernel 5.9.0-rc3+
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/1920874 Title: [Regression] Partition not removed after removing the memory cards from card reader since kernel 5.9.0-rc3+ 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 source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] Memory card removal event can not be reflected via uevent on some card readers Ex. Realtek card readers 0bda:0328 and 0bda:0158. Thus the file browser still see the ghost disk even it's already removed. [Fix] Found the commit 6540fbf6b643 in 5.9.0-rc3 introduce this regression. Fix it by making sure the partition scan will never be skipped for each vfs_open until the partition scan is really done [Test] Verified on the Realtek card reader 0bda:0328 on Dell Precision 7820 and the external Realtek usb interface card reader 0bda:0158. Insert the SD card in the card reader $ udevadm monitor Remove the SD card and check the udevadm monitor output KERNEL[188.377042] change /devices/pci:00/:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) UDEV [188.383261] remove /devices/pci:00/:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) KERNEL[188.390887] change /devices/pci:00/:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) UDEV [188.396012] remove /devices/pci:00/:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) The remove event should be observed from the output messages. On the affected card reader, only change event would be observed. [Where problem could occur] These kind of card readers doesn't send remove event of scsi_disk and scsi_device like others so they only depend on the block subsystem to detect the media change and relect the removal event by partition scan. The behavior related to media removal is changed after 5.9.0-rc3. The remove event is not able to be correcly reflected since then, the device node of the media will remain there until next card insertion. == Original Bug Description == Ubuntu version: 20.10 Kernel: 5.10.0-1013-oem Card reader: Realtek Card Reader (0bda:0328 and 0bda:0158) Summary === After upgrading to kernel 5.9.0-rc3 or later, the device node for the partitions on the memory cards will not disappear after removing the memory cards. This is confusing to the user level applications like File Browser since the partition label will remain there for a long time. Steps to reproduce == 1. Upgrade to kernel later than 5.9.0-rc3 2. Plug the external card reader and insert the formatted memory card 3. Verify if the memory card mounted and visible on File Browser 4. Remove the memory card from the card reader 5. Verify if the mounted memory card removed from the File Browser Expected results The mounted memory card identifier should be disappear after remove the memory card Actual results == The partition label of the memory card exists for a long time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dev1443 F pulseaudio /dev/snd/controlC0: dev1443 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-03-22 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. ZenBook UX434IQ_UX434IQ Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=ac0e9628-3402-4892-84ab-a1dfb21be15a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions:
[Kernel-packages] [Bug 1921345] Re: Support MIPI camera through Intel IPU6
SRU: https://lists.ubuntu.com/archives/kernel- team/2021-March/118514.html (firmware, focal only) -- 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/1921345 Title: Support MIPI camera through Intel IPU6 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-firmware source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] There are new platforms with MIPI camera based on Intel IPU6(Imaging Processing Unit version 6) currently unsupported in Ubuntu. [Fix] Intel IPU6 can be enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc This patchset took kernel patches from intel/ipu6-drivers. [Test Case] With kernel/firmware properly installed, the hardware should be ready for further development: $ dmesg | grep ipu intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 There should be nearly 24 video4linux devices created under /dev. [Where problems could occur] MIPI camera through Intel IPU6 takes also firmware blobs loaded in runtime from user space, addtional softwares are also required to fully enable it for oridinary use. The exposed video devices are hidden from general users and a relay daemon+v4l2loopback is used to enable use from existing applications. >From kernel's point of view, there is still a known issue that it takes root priviledge to access these devices. [Other Info] So far Intel has no plan to commit this driver to upstream yet, so it's only nominated for oem-5.10. It will only be nominated to generic kernels when the plan/requirements have changed. The original driver Kconfig would disable VIDEO_IPU3_CIO2, but that's reverted to avoid unnecessary changes to existing users. == original bug description == The Intel imaging processing unit version 6, found in Intel SoCs and used for capturing images and video from a camera sensor is enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc With all components properly installed, the hardware should be ready for further development: intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 This one equips an OV01A1S sensor, and HM11B1 is also supported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64
[Kernel-packages] [Bug 1921345] Re: Support MIPI camera through Intel IPU6
SRU: https://lists.ubuntu.com/archives/kernel- team/2021-March/118504.html (oem-5.10) ** Description changed: - The Intel imaging processing unit version 6, found in Intel SoCs and - used for capturing images and video from a camera sensor is enabled by - integration of following kernel driver, firmware, userspace HAL - libraries as well as a GStreamer source element: + [SRU Justification] + + [Impact] + + There are new platforms with MIPI camera based on Intel IPU6(Imaging + Processing Unit version 6) currently unsupported in Ubuntu. + + [Fix] + + Intel IPU6 can be enabled by integration of following kernel driver, + firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc - With all components properly installed, the hardware should be ready for + This patchset took kernel patches from intel/ipu6-drivers. + + [Test Case] + + With kernel/firmware properly installed, the hardware should be ready for further development: + $ dmesg | grep ipu intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 - intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 + intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 + port is 1 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 + + There should be nearly 24 video4linux devices created under /dev. + + [Where problems could occur] + + MIPI camera through Intel IPU6 takes also firmware blobs loaded in + runtime from user space, addtional softwares are also required to + fully enable it for oridinary use. The exposed video devices are hidden + from general users and a relay daemon+v4l2loopback is used to enable + use from existing applications. + + >From kernel's point of view, there is still a known issue that it takes + root priviledge to access these devices. + + [Other Info] + + So far Intel has no plan to commit this driver to upstream yet, so it's + only nominated for oem-5.10. It will only be nominated to generic + kernels when the plan/requirements have changed. + + The original driver Kconfig would disable VIDEO_IPU3_CIO2, but that's + reverted to avoid unnecessary changes to existing users. + + == original bug description == + + The Intel imaging processing unit version 6, found in Intel SoCs and + used for capturing images and video from a camera sensor is enabled by + integration of following kernel driver, firmware, userspace HAL + libraries as well as a GStreamer source element: + + * https://github.com/intel/ipu6-drivers + * https://github.com/intel/ipu6-camera-bins + * https://github.com/intel/ipu6-camera-hal + * https://github.com/intel/icamerasrc + + With all components properly installed, the hardware should be ready for + further development: + + intel-ipu6 intel-ipu: enabling device ( -> 0002) + intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) + intel-ipu6 intel-ipu: physical base address 0x605400 + intel-ipu6 intel-ipu: mapped as: 0x97793328 + intel-ipu6 intel-ipu: IPU in secure mode + intel-ipu6 intel-ipu: IPC reset done + intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin + intel-ipu6 intel-ipu: FW version: 20201222 + intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE + intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE + intel-ipu6 intel-ipu: CSE authenticate_run done + intel-ipu6 intel-ipu: IPU driver version 1.0 + intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 + intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 + intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 + intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. + intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 This one equips an OV01A1S sensor, and HM11B1 is also supported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1721 F pulseaudio CasperMD5CheckResult: skip Dependencies:
[Kernel-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
** Description changed: - [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- - Audio.pcm.iec958_device - - Just for tracking now. - [Impact] + On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] + Disable IEC958 (SPDIF) through ALSA UCM. - [Test Case] + [Test] + With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. - [Where problems could occur] + [Regression Potential] + This fix limits to the Cmedia Audio only, other devices are unaffected. ** Description changed: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. - [Regression Potential] + [Where problems will occur] This fix limits to the Cmedia Audio only, other devices are unaffected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: In Progress Status in alsa-lib package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Groovy: In Progress Status in alsa-lib source package in Hirsute: In Progress Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] This fix limits to the Cmedia Audio only, other devices are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
This is the debdiff for Focal, thanks. ** Patch added: "alsa-lib_1.2.2-2.1ubuntu2.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1921452/+attachment/5481044/+files/alsa-lib_1.2.2-2.1ubuntu2.4.debdiff ** Changed in: alsa-lib (Ubuntu Focal) Assignee: (unassigned) => Shengyao Xue (xueshengyao) ** No longer affects: alsa-lib ** Tags added: oem-priority originate-from-1916751 somerville ** Tags added: originate-from-1916753 ** Changed in: oem-priority Assignee: (unassigned) => Shengyao Xue (xueshengyao) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => In Progress ** Changed in: alsa-lib (Ubuntu Focal) Status: New => In Progress ** Changed in: alsa-lib (Ubuntu Groovy) Status: New => In Progress ** Changed in: alsa-lib (Ubuntu Hirsute) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: In Progress Status in alsa-lib package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Groovy: In Progress Status in alsa-lib source package in Hirsute: In Progress Bug description: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Just for tracking now. [Impact] [Fix] [Test Case] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
This is the debdiff for Groovy, thanks. ** Patch added: "alsa-lib_1.2.3.2-1ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1921452/+attachment/5481035/+files/alsa-lib_1.2.3.2-1ubuntu4.debdiff ** Changed in: alsa-lib (Ubuntu Groovy) Assignee: (unassigned) => Shengyao Xue (xueshengyao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in ALSA Libraries: New Status in alsa-lib package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-lib source package in Hirsute: New Bug description: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Just for tracking now. [Impact] [Fix] [Test Case] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-lib/+bug/1921452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
