[Kernel-packages] [Bug 1924238] Re: Fix no picture from HDMI when it's plugged after boot
Hi, [Focal, Thinkpad T480s, 8550u/intel igpu] Unfortunately I suspect this: * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port in *-1024 OEM 5.10 kernel, that I do use in Focal, did break HDMI hotplug after GNOME is loaded. HDMI works if plugged when at GDM login screen and then in GNOME itself. Additionally, my laptop's sleep seems to be broken (I don't remember if this happens when HDMI is working or not). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924238 Title: Fix no picture from HDMI when it's plugged after boot Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] On Intel CML desktop, there's no HDMI output when the cable is not connected pre-boot. [Fix] Properly handle lane polarity so the driver can write different values to the register to enable the port. [Test] 1. Boot with DP display. 2. Connect HDMI under GNOME desktop. 3. No picture on HDMI monitor. With the fix applied, the issue is resolved. [Where problems could occur] If the BIOS VBT table is not correct, which did happen in the pase, this fix may break those ports. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924624] Re: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable
Is there a plan, roadmap, or experience values for when to expect -51 for focal without using the above mentioned – not recommended – PPA? It’s not that I want to complain; it would be simply helpful for my own planning. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924624 Title: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-5.8 package in Ubuntu: Confirmed Bug description: After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was suddenly extremely glitchy. Icons from the desktop flash through the browser, windows top bar gets distorted, all sort of glitches appear, parts of characters are missing in terminal, scrolling is inconsistent and the whole desktop becomes unusable. Under wayland the graphics are a bit more stable, but lots of glitches appear anyway, video reproduction in browser is stuttering and wobbly. Booting with previous kernel 5.8.0-48 seems to fix the issues. 5.8.0-50 is broken as well. this is the result of 'sudo lshw -c video' on my hp Elitebook 8470: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:d400-d43f memory:c000-cfff ioport:4000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation
There are no entries in the journal for those particular boots I'm afraid. That is, the journal is empty if I boot without "nomodeset" or without "amdgpu.ip_block_mask=0xfdff". There are some very quick boot messages appearing on the screen before it turns all black, but nothing in the log. I rebooted several times to make sure it is not a random behaviour. I even tried "verbose debug" kernel boot parameters with no success. I packed all the logs from that particular date in case I analysed the situation wrong. What can I do now? ** Attachment added: "journal_AMD_A8-7680.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+attachment/5493224/+files/journal_AMD_A8-7680.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/1920674 Title: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation Status in linux package in Ubuntu: Incomplete Bug description: Dear developers, please let me thank you for all your hard work first of all, I'm a big fan of yours! On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which seem to be connected to the amdgpu kernel module: 1. Amdgpu kernel module loads correctly during boot, but VESA Xorg module is loaded instead of AMDGPU Xorg module during X startup. This results in non-accelerated X and high CPU load. - This situation is always reproducible. - I'm experiencing it with all kernel versions in between 5.4.0-47-generic and 5.4.0-67-generic inclusive. - The situation escalates more with newer kernel version. For 5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and I just get black screen. - I have found a workaround after many days of googling and testing. AMDGPU Xorg module is loaded correctly if and only if I disable AMD ACP by means of the following kernel boot parameter: amdgpu.ip_block_mask=0xfdff - Acceleration is ok with kernels where AMD ACP is disabled by default (linux-image-linuxlite-5.6.0 for example) 2. The 2nd problem I'm facing is with non functioning hibernation after I "fixed" the X acceleration. Hibernation image does not seem to get created, screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by means of "nomodeset" and go just with VESA module. - always reproducible but tested only with 5.4.0-67-generic Thank you and best regards, Radek ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-67-generic 5.4.0-67.75 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radek 1513 F pulseaudio /dev/snd/controlC0: radek 1513 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Mar 21 15:22:29 2021 HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff no_console_suspend RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.20 dmi.board.name: FM2A68M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922651] Re: r8152 tx status -71
Maybe the Lenovo USB3.1 Hub device would benefit from having the 'k' parameter? I'll try. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922651 Title: r8152 tx status -71 Status in linux package in Ubuntu: Confirmed Bug description: I've bought ThinkPad T14s with a USB-based docking station. Everything is working marvelously, but from time to time the ethernet port on the docking station won't connect. I've discovered the following messages in my dmesg: [ 400.597506] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 401.164370] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 463.168412] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 465.314415] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 529.409871] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 533.718163] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 591.168537] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 594.335383] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 Rebooting the machine doesn't seem to work, turning the ethernet connection off and on doesn't seem to work. I have a dualboot Linux+Windows (one wants to play games from time to time :-p ) and it could be that rebooting from Win to Lin causes this issue, but this needs to be confirmed yet. I will try to power off the computer and/or the docking station, to see whether that would help. I've found numerous bug reports, but they are rather old or may not apply to this situation, therefore I figured it's best to open a new bug report. Thank you so much for your hard work! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-48-generic 5.8.0-48.54 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 10:00:29 2021 InstallationDate: Installed on 2021-03-24 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UH001QMX ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic root=UUID=14a0-0947-4e58-ade1-ad9963053d85 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-48-generic N/A linux-backports-modules-5.8.0-48-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2020 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET61W(1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UH001QMX dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnLENOVO:bvrR1CET61W(1.30):bd12/21/2020:br1.30:efr1.30:svnLENOVO:pn20UH001QMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001QMX:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UH001QMX dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922651/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922651] Re: r8152 tx status -71
Hold on please, it looks like the bug is back - upon a boot I'm randomly getting [ 271.935097] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 272.959356] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 273.983324] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 even though I have the kernel parameter usbcore.quirks=17ef:a387:k . Now I'm running Ubuntu 21.04 using kernel 5.11.0-16-generic. lsusb now identifies the device correctly: Bus 005 Device 003: ID 17ef:a387 Lenovo USB-C Dock Ethernet So, the k option, while improving the situation, doesn't seem to solve it fully. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922651 Title: r8152 tx status -71 Status in linux package in Ubuntu: Confirmed Bug description: I've bought ThinkPad T14s with a USB-based docking station. Everything is working marvelously, but from time to time the ethernet port on the docking station won't connect. I've discovered the following messages in my dmesg: [ 400.597506] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 401.164370] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 463.168412] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 465.314415] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 529.409871] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 533.718163] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 591.168537] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 594.335383] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 Rebooting the machine doesn't seem to work, turning the ethernet connection off and on doesn't seem to work. I have a dualboot Linux+Windows (one wants to play games from time to time :-p ) and it could be that rebooting from Win to Lin causes this issue, but this needs to be confirmed yet. I will try to power off the computer and/or the docking station, to see whether that would help. I've found numerous bug reports, but they are rather old or may not apply to this situation, therefore I figured it's best to open a new bug report. Thank you so much for your hard work! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-48-generic 5.8.0-48.54 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 10:00:29 2021 InstallationDate: Installed on 2021-03-24 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UH001QMX ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic root=UUID=14a0-0947-4e58-ade1-ad9963053d85 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-48-generic N/A linux-backports-modules-5.8.0-48-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2020 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET61W(1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UH001QMX dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnLENOVO:bvrR1CET61W(1.30):bd12/21/2020:br1.30:efr1.30:svnLENOVO:pn20UH001QMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001QMX:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UH001QMX dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922651/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926517] Re: mpt3sas: only one vSES is handy even IOC has multi vSES
I have built a test kernel. https://people.canonical.com/~mreed/lp1926517/ ** Summary changed: - mpt3sas: only one vSES is handy even IOC has multi vSES + [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926517 Title: [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Whenever the driver is adding a vSES to virtual-phys list it is reinitializing the list head. Hence those vSES devices which were added previously are lost. [FIXES] Stop reinitializing the list every time a new vSES device is added. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=4c51f9569651 CommitID: 4c51f956965120b3441cdd39c358b87daba13e19 [TESTING] [REGRESSION RISK] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] 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 1926527 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Incomplete Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] Re: "Power off" dialog appears when any three keyboard keys are pressed quickly
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1926527 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: 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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: New Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] [NEW] "Power off" dialog appears when any three keyboard keys are pressed quickly
You have been subscribed to a public bug: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- "Power off" dialog appears when any three keyboard keys are pressed quickly https://bugs.launchpad.net/bugs/1926527 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 1926184] Re: locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
** Changed in: linux-aws (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1926184
Title:
locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
Status in linux package in Ubuntu:
In Progress
Status in linux-aws package in Ubuntu:
In Progress
Status in linux source package in Bionic:
New
Status in linux-aws source package in Bionic:
Fix Committed
Status in linux source package in Focal:
New
Status in linux-aws source package in Focal:
Fix Committed
Status in linux source package in Groovy:
New
Status in linux-aws source package in Groovy:
New
Status in linux source package in Hirsute:
New
Status in linux-aws source package in Hirsute:
New
Bug description:
[Impact]
* Out of order reads can fetch a NULL pointer causing a kernel crash. Affects
kernels from v4.15 to v5.11.
[Fix]
* commit 84a24bf8c52e ("locking/qrwlock: Fix ordering in
queued_write_lock_slowpath()")
* For Bionic, we also require an additional patch: commit fcfdfe30e324
("locking/barriers: Introduce smp_cond_load_relaxed() and
atomic_cond_read_relaxed()")
[Where problems could occur]
* This is quite a subtle bug. It is more prevalent on arm64. Regression
possibility seems quite low. The worst impact could be a minor performance
degradation.
* Kernels 4.15 / 5.4 / 5.8 / 5.11 were successfully built and booted
with this patch. Also, by using ftrace we could see that the changed
function was executed with success multiple times.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926184/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926517] 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 1926517 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926517 Title: mpt3sas: only one vSES is handy even IOC has multi vSES Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Whenever the driver is adding a vSES to virtual-phys list it is reinitializing the list head. Hence those vSES devices which were added previously are lost. [FIXES] Stop reinitializing the list every time a new vSES device is added. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=4c51f9569651 CommitID: 4c51f956965120b3441cdd39c358b87daba13e19 [TESTING] [REGRESSION RISK] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926517] [NEW] mpt3sas: only one vSES is handy even IOC has multi vSES
Public bug reported: [Impact] Whenever the driver is adding a vSES to virtual-phys list it is reinitializing the list head. Hence those vSES devices which were added previously are lost. [FIXES] Stop reinitializing the list every time a new vSES device is added. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=4c51f9569651 CommitID: 4c51f956965120b3441cdd39c358b87daba13e19 [TESTING] [REGRESSION RISK] ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926517 Title: mpt3sas: only one vSES is handy even IOC has multi vSES Status in linux package in Ubuntu: New Bug description: [Impact] Whenever the driver is adding a vSES to virtual-phys list it is reinitializing the list head. Hence those vSES devices which were added previously are lost. [FIXES] Stop reinitializing the list every time a new vSES device is added. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=4c51f9569651 CommitID: 4c51f956965120b3441cdd39c358b87daba13e19 [TESTING] [REGRESSION RISK] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926501] Re: ADT/hint: Multiple DKMS modules fail to build in linux-kvm due to lack of Kconfigs set
lttng-dkms is also failing to build in Bionic/kvm due to lack of a config option: https://bugs.launchpad.net/ubuntu/+source/lttng- modules/+bug/1905989 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1926501 Title: ADT/hint: Multiple DKMS modules fail to build in linux-kvm due to lack of Kconfigs set Status in linux-kvm package in Ubuntu: Confirmed Bug description: This a catch-all Launchpad report regarding the build failures of some DKMS modules (like Nvidia drivers, virtualbox-hwe, ...) in linux-kvm. The goal of linux-kvm kernel is to be a *very* minimal kernel for virtualized environments (guests), with the bare minimum of Kconfigs enabled, in order to have it booting really fast and with a reduced attack surface. Given that, some DKMS may not work, like virtualbox- hwe (which requires CONFIG_DRM_*). The objective of this LP is to report such failures and use this information "database" to help us mark Autopackage testing (ADT) failures as _expected_, or else in every kernel cycle we will face the same issues that show up as regressions, when they are in fact incompatibilities between the test and the minimal linux-kvm kernel. We could use the comments to report individual failures / attach logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1926501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926501] Re: ADT/hint: Multiple DKMS modules fail to build in linux-kvm due to lack of Kconfigs set
We noticed that recent Nvidia modules (all series, like -450, -460, etc) are failing to build on linux-kvm, due to the lack of CONFIG_PM option, which is not set in linux-kvm. Logs attached for Bionic/Focal. ** Attachment added: "nvidia-460-bionic,focal.tgz" https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1926501/+attachment/5493162/+files/nvidia-460-bionic%2Cfocal.tgz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1926501 Title: ADT/hint: Multiple DKMS modules fail to build in linux-kvm due to lack of Kconfigs set Status in linux-kvm package in Ubuntu: Confirmed Bug description: This a catch-all Launchpad report regarding the build failures of some DKMS modules (like Nvidia drivers, virtualbox-hwe, ...) in linux-kvm. The goal of linux-kvm kernel is to be a *very* minimal kernel for virtualized environments (guests), with the bare minimum of Kconfigs enabled, in order to have it booting really fast and with a reduced attack surface. Given that, some DKMS may not work, like virtualbox- hwe (which requires CONFIG_DRM_*). The objective of this LP is to report such failures and use this information "database" to help us mark Autopackage testing (ADT) failures as _expected_, or else in every kernel cycle we will face the same issues that show up as regressions, when they are in fact incompatibilities between the test and the minimal linux-kvm kernel. We could use the comments to report individual failures / attach logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1926501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924624] Re: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable
Same problem in two ThinkPad E430 (Intel HD Graphics 4000; driver i915) when upgrading to -49 or -50 Additionally, with -50 I can't login (Ubuntu 20.04): cursor appears fine but login screen (e.g., logo, username, password box) does not appear. However I can still open non-graphical consoles (e.g., tty3) Everything works fine booting into -48-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924624 Title: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-5.8 package in Ubuntu: Confirmed Bug description: After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was suddenly extremely glitchy. Icons from the desktop flash through the browser, windows top bar gets distorted, all sort of glitches appear, parts of characters are missing in terminal, scrolling is inconsistent and the whole desktop becomes unusable. Under wayland the graphics are a bit more stable, but lots of glitches appear anyway, video reproduction in browser is stuttering and wobbly. Booting with previous kernel 5.8.0-48 seems to fix the issues. 5.8.0-50 is broken as well. this is the result of 'sudo lshw -c video' on my hp Elitebook 8470: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:d400-d43f memory:c000-cfff ioport:4000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed
** Tags removed: ibm-gt -- 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/1829849 Title: proc01 in fs from ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: Triaged Status in linux-azure package in Ubuntu: Triaged Status in linux-oracle-5.0 package in Ubuntu: Confirmed Bug description: proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only. proc01 0 TINFO : /proc/sys/net/ipv6/conf/all/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/default/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/ens6/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/lo/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable proc01 0 TINFO : /proc/sysrq-trigger: is write-only. proc01 0 TINFO : /proc/self/task/8782/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/task/8782/clear_refs: is write-only. proc01 0 TINFO : /proc/self/task/8782/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/task/8782/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 1 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 2 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 3 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 4 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 5 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 6 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 7 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 8 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 9 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/clear_refs: is write-only. proc01 0 TINFO : /proc/self/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 10 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 11 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 12 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 13 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 14 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 15 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 16 TFAIL : proc01.c:397: read failed: /proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 17 TFAIL : proc01.c:397: read failed: /proc/self/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01
[Kernel-packages] [Bug 1829983] Re: memcg_stat from controllers test suite in LTP failed
** Tags removed: ibm-gt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829983 Title: memcg_stat from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: memcg_stat_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_stat_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 1 TINFO: Running memcg_process --shm -k 3 -s 135168 memcg_stat_test 1 TINFO: Warming up pid: 31352 memcg_stat_test 1 TINFO: Process is still here after warm up: 31352 memcg_stat_test 1 TPASS: cache is 135168 as expected memcg_stat_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_stat_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 2 TINFO: Running memcg_process --mmap-file -s 135168 memcg_stat_test 2 TINFO: Warming up pid: 31380 memcg_stat_test 2 TINFO: Process is still here after warm up: 31380 memcg_stat_test 2 TPASS: mapped_file is 135168 as expected memcg_stat_test 3 TINFO: Starting test 3 sh: echo: I/O error memcg_stat_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 3 TINFO: Running memcg_process --mmap-lock1 -s 4096 memcg_stat_test 3 TINFO: Warming up pid: 31409 memcg_stat_test 3 TINFO: Process is still here after warm up: 31409 memcg_stat_test 3 TPASS: unevictable is 4096 as expected memcg_stat_test 4 TINFO: Starting test 4 sh: echo: I/O error memcg_stat_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 4 TINFO: Running memcg_process --mmap-lock2 -s 4096 memcg_stat_test 4 TINFO: Warming up pid: 31434 memcg_stat_test 4 TINFO: Process is still here after warm up: 31434 memcg_stat_test 4 TPASS: unevictable is 4096 as expected memcg_stat_test 5 TINFO: Starting test 5 sh: echo: I/O error memcg_stat_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 5 TPASS: hierarchical_memory_limit is 4096 as expected memcg_stat_test 6 TINFO: Starting test 6 sh: echo: I/O error memcg_stat_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed sh: echo: I/O error memcg_stat_test 6 TFAIL: hierarchical_memory_limit is 4096, 8192 expected memcg_stat_test 7 TINFO: Starting test 7 sh: echo: I/O error memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 7 TCONF: mem+swap is not enabled memcg_stat_test 7 TINFO: Starting test 8 sh: echo: I/O error memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 7 TCONF: mem+swap is not enabled tag=memcg_stat stime=1558504742 dur=4 exit=exited stat=33 core=no cu=16 cs=10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:17:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i4
[Kernel-packages] [Bug 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed
** Tags removed: ibm-gt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829984 Title: memcg_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: startup='Wed May 22 05:59:09 2019' memcg_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689 memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689 memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 expected memcg_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no cu=5 cs=3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:17:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829989] Re: memcg_use_hierarchy from controllers test suite in LTP failed
** Tags removed: ibm-gt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829989 Title: memcg_use_hierarchy from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: startup='Wed May 22 05:59:07 2019' memcg_use_hierarchy_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_use_hierarchy_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_use_hierarchy_test 1 TPASS: process 31577 is killed memcg_use_hierarchy_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_use_hierarchy_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_use_hierarchy_test 2 TFAIL: echo 1 > memory.use_hierarchy passed unexpectedly memcg_use_hierarchy_test 3 TINFO: Starting test 3 sh: echo: I/O error memcg_use_hierarchy_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_use_hierarchy_test 3 TPASS: echo 0 > subgroup/memory.use_hierarchy failed as expected tag=memcg_use_hierarchy stime=1558504747 dur=1 exit=exited stat=1 core=no cu=5 cs=5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:33:33 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829995] Re: getaddrinfo_01 from ipv6_lib test suite in LTP failed
** Tags removed: ibm-gt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1829995
Title:
getaddrinfo_01 from ipv6_lib test suite in LTP failed
Status in ubuntu-kernel-tests:
Triaged
Status in linux package in Ubuntu:
Incomplete
Status in linux-aws package in Ubuntu:
New
Status in linux source package in Bionic:
Incomplete
Status in linux-aws source package in Bionic:
New
Status in linux source package in Eoan:
New
Status in linux-aws source package in Eoan:
New
Bug description:
startup='Wed May 22 08:02:52 2019'
getaddrinfo_011 TPASS : getaddrinfo IPv4 basic lookup
getaddrinfo_012 TFAIL : getaddrinfo_01.c:140: getaddrinfo IPv4
canonical name ("curly.maas") doesn't match hostname ("curly")
getaddrinfo_013 TFAIL : getaddrinfo_01.c:578: getaddrinfo IPv6 basic
lookup ("curly") returns -5 ("No address associated with hostname")
tag=getaddrinfo_01 stime=1558512172 dur=1 exit=exited stat=1 core=no cu=0 cs=0
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-50-generic 4.15.0-50.54
ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 22 02:57 seq
crw-rw 1 root audio 116, 33 May 22 02:57 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Wed May 22 08:04:30 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
RelatedPackageVersions:
linux-restricted-modules-4.15.0-50-generic N/A
linux-backports-modules-4.15.0-50-generic N/A
linux-firmware 1.173.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias:
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829995/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed
** Tags removed: ibm-gt -- 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/1834006 Title: cpuset_hotplug from controllers in ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux source package in Focal: New Status in linux-aws source package in Focal: New Status in linux-azure source package in Focal: New Bug description: Issue found on node amaura: <<>> tag=cpuset_hotplug stime=1561372131 cmdline="cpuset_hotplug_test.sh" contacts="" analysis=exit <<>> incrementing stop cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15, Expect: 0-7). cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded. <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=19 cstime=81 <<>> Test script: https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-22-generic 4.18.0-22.23 ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 24 10:25 seq crw-rw 1 root audio 116, 33 Jun 24 10:25 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jun 24 10:30:59 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed
** Tags removed: ibm-gt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1837543 Title: crypto_user02 in crypto from ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: Confirmed Bug description: This is a new test, test will fail with: <<>> tag=crypto_user02 stime=1563881396 cmdline="crypto_user02" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s crypto_user02.c:59: INFO: Starting crypto_user larval deletion test. May crash buggy kernels. crypto_user02.c:91: BROK: unexpected error from tst_crypto_del_alg(): EBUSY Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Nothing interesting in syslog: Jul 23 11:29:20 amaura systemd[1]: Started Session 1 of user ubuntu. Jul 23 11:29:56 amaura kernel: [ 619.646330] LTP: starting crypto_user02 Jul 23 11:30:23 amaura kernel: [ 646.554403] cfg80211: Loading compiled-in X.509 certificates for regulatory database Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "crypto_user02 crypto_user02" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 23 11:19 seq crw-rw 1 root audio 116, 33 Jul 23 11:19 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 23 11:30:15 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926501] Re: ADT/hint: Multiple DKMS modules fail to build in linux-kvm due to lack of Kconfigs set
Nvidia DKMS drivers fail to build in linux-kvm kernels > 5.8, as reported here: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1922800 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1926501 Title: ADT/hint: Multiple DKMS modules fail to build in linux-kvm due to lack of Kconfigs set Status in linux-kvm package in Ubuntu: Confirmed Bug description: This a catch-all Launchpad report regarding the build failures of some DKMS modules (like Nvidia drivers, virtualbox-hwe, ...) in linux-kvm. The goal of linux-kvm kernel is to be a *very* minimal kernel for virtualized environments (guests), with the bare minimum of Kconfigs enabled, in order to have it booting really fast and with a reduced attack surface. Given that, some DKMS may not work, like virtualbox- hwe (which requires CONFIG_DRM_*). The objective of this LP is to report such failures and use this information "database" to help us mark Autopackage testing (ADT) failures as _expected_, or else in every kernel cycle we will face the same issues that show up as regressions, when they are in fact incompatibilities between the test and the minimal linux-kvm kernel. We could use the comments to report individual failures / attach logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1926501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922800] Re: Nvidia proprietary DKMS drivers cannot build in linux-kvm 5.8 and subsequent versions
A more generic LP about ADT failures, that encompass multiple DKMS failures due to lack of Kconfigs set in linux-kvm: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1926501 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1922800 Title: Nvidia proprietary DKMS drivers cannot build in linux-kvm 5.8 and subsequent versions Status in linux-kvm package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in linux-kvm source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: New Bug description: After an ADT/DKMS modification (see https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1915051) binary DKMS packages without -dkms in the name started to get tested on ADT run. This exposed a problem in the Nvidia proprietary DKMS modules for linux-kvm build: if we don't have CONFIG_X86_PAT set, the Nvidia drivers (all versions) set NV_ENABLE_BUILTIN_PAT_SUPPORT to 1 and attempt to build the file nvidia/nv-pat.c - two functions there make use of __flush_tlb() exported symbol. But, after kernel v5.8, this symbol is not exported anymore [0][1], not even flush_tlb_local() is available. For the time being, we ADT-hinted linux-kvm package, but the driver requires modifications, in order to fix that. [0] http://git.kernel.org/linus/2faf153bb734 [1] http://git.kernel.org/linus/bfe3d8f6313d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1922800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926501] Re: ADT/hint: Multiple DKMS modules fail to build in linux-kvm due to lack of Kconfigs set
Virtualbox-hwe is expected to fail in linux-kvm, as reported here: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1922397 We will hint its ADT test accordingly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1926501 Title: ADT/hint: Multiple DKMS modules fail to build in linux-kvm due to lack of Kconfigs set Status in linux-kvm package in Ubuntu: Confirmed Bug description: This a catch-all Launchpad report regarding the build failures of some DKMS modules (like Nvidia drivers, virtualbox-hwe, ...) in linux-kvm. The goal of linux-kvm kernel is to be a *very* minimal kernel for virtualized environments (guests), with the bare minimum of Kconfigs enabled, in order to have it booting really fast and with a reduced attack surface. Given that, some DKMS may not work, like virtualbox- hwe (which requires CONFIG_DRM_*). The objective of this LP is to report such failures and use this information "database" to help us mark Autopackage testing (ADT) failures as _expected_, or else in every kernel cycle we will face the same issues that show up as regressions, when they are in fact incompatibilities between the test and the minimal linux-kvm kernel. We could use the comments to report individual failures / attach logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1926501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922397] Re: ADT test failure in proposed kernel 5.4.0-1037.38: virtualbox-guest-dkms-hwe is not building
A more generic LP about ADT failures, that encompass multiple DKMS failures due to lack of Kconfigs set in linux-kvm: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1926501 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1922397 Title: ADT test failure in proposed kernel 5.4.0-1037.38: virtualbox-guest- dkms-hwe is not building Status in linux-kvm package in Ubuntu: Fix Released Bug description: This is the failure report: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/v/virtualbox- hwe/20210402_001931_2bea9@/log.gz By trying to reproduce in a VM with linux-kvm, the logs are explicit about the failure reason: DKMS make.log for virtualbox-guest-6.1.16 for kernel 5.4.0-1037-kvm (x86_64) Fri Apr 2 21:25:41 UTC 2021 make: Entering directory '/usr/src/linux-headers-5.4.0-1037-kvm' CC [M] /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxguest/VBoxGuest-linux.o CC [M] /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxguest/VBoxGuest.o [...] CC [M] /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vbox_hgsmi.o LD [M] /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.o AR /var/lib/dkms/virtualbox-guest/6.1.16/build/built-in.a Building modules, stage 2. MODPOST 3 modules ERROR: "drm_gem_prime_export" [/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined! ERROR: "drm_release" [/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined! ERROR: "ttm_bo_eviction_valuable" [/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined! ERROR: "ttm_tt_fini" [/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined! ERROR: "drm_crtc_helper_set_config" [/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined! ERROR: "drm_dev_register" [/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined! [...] linux-kvm has "CONFIG_DRM" unset, so..it's expected to fail! The odd part here is that this seems to be the first failure; checking the ADT results in last kernel before current cycle (-1034), we can see the DKMS built never happened; I suspect this is related with the ADT command-line change between -1034 and -1037 - I'll attach both lines. For reference, this is the full log from the ADT test in -1034: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/v/virtualbox- hwe/20210225_192413_d067f@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1922397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926501] [NEW] ADT/hint: Multiple DKMS modules fail to build in linux-kvm due to lack of Kconfigs set
Public bug reported: This a catch-all Launchpad report regarding the build failures of some DKMS modules (like Nvidia drivers, virtualbox-hwe, ...) in linux-kvm. The goal of linux-kvm kernel is to be a *very* minimal kernel for virtualized environments (guests), with the bare minimum of Kconfigs enabled, in order to have it booting really fast and with a reduced attack surface. Given that, some DKMS may not work, like virtualbox-hwe (which requires CONFIG_DRM_*). The objective of this LP is to report such failures and use this information "database" to help us mark Autopackage testing (ADT) failures as _expected_, or else in every kernel cycle we will face the same issues that show up as regressions, when they are in fact incompatibilities between the test and the minimal linux-kvm kernel. We could use the comments to report individual failures / attach logs. ** Affects: linux-kvm (Ubuntu) Importance: Medium Assignee: Guilherme G. Piccoli (gpiccoli) Status: Confirmed ** Tags: bionic focal groovy hirsute kvm linux-kvm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1926501 Title: ADT/hint: Multiple DKMS modules fail to build in linux-kvm due to lack of Kconfigs set Status in linux-kvm package in Ubuntu: Confirmed Bug description: This a catch-all Launchpad report regarding the build failures of some DKMS modules (like Nvidia drivers, virtualbox-hwe, ...) in linux-kvm. The goal of linux-kvm kernel is to be a *very* minimal kernel for virtualized environments (guests), with the bare minimum of Kconfigs enabled, in order to have it booting really fast and with a reduced attack surface. Given that, some DKMS may not work, like virtualbox- hwe (which requires CONFIG_DRM_*). The objective of this LP is to report such failures and use this information "database" to help us mark Autopackage testing (ADT) failures as _expected_, or else in every kernel cycle we will face the same issues that show up as regressions, when they are in fact incompatibilities between the test and the minimal linux-kvm kernel. We could use the comments to report individual failures / attach logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1926501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926493] [NEW] Focal update: v5.4.114 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.114 upstream stable release
from git://git.kernel.org/
Revert "scsi: qla2xxx: Retry PLOGI on FC-NVMe PRLI failure"
Revert "scsi: qla2xxx: Fix stuck login session using prli_pend_timer"
scsi: qla2xxx: Dual FCP-NVMe target port support
scsi: qla2xxx: Fix device connect issues in P2P configuration
scsi: qla2xxx: Retry PLOGI on FC-NVMe PRLI failure
scsi: qla2xxx: Add a shadow variable to hold disc_state history of fcport
scsi: qla2xxx: Fix stuck login session using prli_pend_timer
scsi: qla2xxx: Fix fabric scan hang
net/sctp: fix race condition in sctp_destroy_sock
Input: nspire-keypad - enable interrupts only when opened
gpio: sysfs: Obey valid_mask
dmaengine: dw: Make it dependent to HAS_IOMEM
ARM: dts: Drop duplicate sha2md5_fck to fix clk_disable race
ARM: dts: Fix moving mmc devices with aliases for omap4 & 5
lockdep: Add a missing initialization hint to the "INFO: Trying to register
non-static key" message
arc: kernel: Return -EFAULT if copy_to_user() fails
ASoC: max98373: Added 30ms turn on/off time delay
neighbour: Disregard DEAD dst in neigh_update
ARM: keystone: fix integer overflow warning
ARM: omap1: fix building with clang IAS
drm/msm: Fix a5xx/a6xx timestamps
ASoC: fsl_esai: Fix TDM slot setup for I2S mode
scsi: scsi_transport_srp: Don't block target in SRP_PORT_LOST state
net: ieee802154: stop dump llsec keys for monitors
net: ieee802154: forbid monitor for add llsec key
net: ieee802154: forbid monitor for del llsec key
net: ieee802154: stop dump llsec devs for monitors
net: ieee802154: forbid monitor for add llsec dev
net: ieee802154: forbid monitor for del llsec dev
net: ieee802154: stop dump llsec devkeys for monitors
net: ieee802154: forbid monitor for add llsec devkey
net: ieee802154: forbid monitor for del llsec devkey
net: ieee802154: stop dump llsec seclevels for monitors
net: ieee802154: forbid monitor for add llsec seclevel
pcnet32: Use pci_resource_len to validate PCI resource
mac80211: clear sta->fast_rx when STA removed from 4-addr VLAN
virt_wifi: Return micros for BSS TSF values
Input: s6sy761 - fix coordinate read bit shift
Input: i8042 - fix Pegatron C15B ID entry
HID: wacom: set EV_KEY and EV_ABS only for non-HID_GENERIC type of devices
dm verity fec: fix misaligned RS roots IO
readdir: make sure to verify directory entry for legacy interfaces too
arm64: fix inline asm in load_unaligned_zeropad()
arm64: alternatives: Move length validation in alternative_{insn, endif}
vfio/pci: Add missing range check in vfio_pci_mmap
riscv: Fix spelling mistake "SPARSEMEM" to "SPARSMEM"
scsi: libsas: Reset num_scatter if libata marks qc as NODATA
netfilter: conntrack: do not print icmpv6 as unknown via /proc
libnvdimm/region: Fix nvdimm_has_flush() to handle ND_REGION_ASYNC
netfilter: bridge: add pre_exit hooks for ebtable unregistration
netfilter: arp_tables: add pre_exit hook for table unregister
net: macb: fix the restore of cmp registers
netfilter: nft_limit: avoid possible divide error in nft_limit_init
net: davicom: Fix regulator not turned off on failed probe
net: sit: Unregister catch-all devices
net: ip6_tunnel: Unregister catch-all devices
i40e: fix the panic when running bpf in xdpdrv mode
ibmvnic: avoid calling napi_disable() twice
ibmvnic: remove duplicate napi_schedule call in do_reset function
ibmvnic: remove duplicate napi_schedule call in open function
gro: ensure frag0 meets IP header alignment
ARM: footbridge: fix PCI interrupt mapping
arm64: dts: allwinner: Fix SD card CD GPIO for SOPine systems
r8169: remove fiddling with the PCIe max read request size
r8169: simplify setting PCI_EXP_DEVCTL_NOSNOOP_EN
r8169: fix performance regression related to PCIe max read request size
r8169: improve rtl_jumbo_config
r8169: tweak max read request size for newer chips also in jumbo mtu mode
r8169: don't advertise pause in jumbo mode
ARM: 9071/1: uprobes: Don't hook on thumb instructions
net: phy: marvell: fix detection of PHY on Topaz switches
Linux 5.4.114
UBUNTU: upstream stable to v5.4.114
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in:
[Kernel-packages] [Bug 1926489] [NEW] Focal update: v5.4.112 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.112 upstream stable release
from git://git.kernel.org/
counter: stm32-timer-cnt: fix ceiling miss-alignment with reload register
ALSA: aloop: Fix initialization of controls
ALSA: hda/realtek: Fix speaker amp setup on Acer Aspire E1
ASoC: intel: atom: Stop advertising non working S24LE support
nfc: fix refcount leak in llcp_sock_bind()
nfc: fix refcount leak in llcp_sock_connect()
nfc: fix memory leak in llcp_sock_connect()
nfc: Avoid endless loops caused by repeated llcp_sock_connect()
xen/evtchn: Change irq_info lock to raw_spinlock_t
net: ipv6: check for validity before dereferencing cfg->fc_nlinfo.nlh
net: dsa: lantiq_gswip: Let GSWIP automatically set the xMII clock
drm/i915: Fix invalid access to ACPI _DSM objects
gcov: re-fix clang-11+ support
ia64: fix user_stack_pointer() for ptrace()
nds32: flush_dcache_page: use page_mapping_file to avoid races with swapoff
ocfs2: fix deadlock between setattr and dio_end_io_write
fs: direct-io: fix missing sdio->boundary
parisc: parisc-agp requires SBA IOMMU driver
parisc: avoid a warning on u8 cast for cmpxchg on u8 pointers
ARM: dts: turris-omnia: configure LED[2]/INTn pin as interrupt pin
batman-adv: initialize "struct batadv_tvlv_tt_vlan_data"->reserved field
ice: Increase control queue timeout
ice: Fix for dereference of NULL pointer
ice: Cleanup fltr list in case of allocation issues
net: hso: fix null-ptr-deref during tty device unregistration
ethernet/netronome/nfp: Fix a use after free in nfp_bpf_ctrl_msg_rx
bpf, sockmap: Fix sk->prot unhash op reset
net: ensure mac header is set in virtio_net_hdr_to_skb()
i40e: Fix sparse warning: missing error code 'err'
i40e: Fix sparse error: 'vsi->netdev' could be null
net: sched: sch_teql: fix null-pointer dereference
mac80211: fix TXQ AC confusion
net: hsr: Reset MAC header for Tx path
net-ipv6: bugfix - raw & sctp - switch to ipv6_can_nonlocal_bind()
net: let skb_orphan_partial wake-up waiters.
usbip: add sysfs_lock to synchronize sysfs code paths
usbip: stub-dev synchronize sysfs code paths
usbip: vudc synchronize sysfs code paths
usbip: synchronize event handler with sysfs code paths
i2c: turn recovery error on init to debug
virtio_net: Add XDP meta data support
net: dsa: lantiq_gswip: Don't use PHY auto polling
net: dsa: lantiq_gswip: Configure all remaining GSWIP_MII_CFG bits
xfrm: interface: fix ipv4 pmtu check to honor ip header df
regulator: bd9571mwv: Fix AVS and DVFS voltage range
net: xfrm: Localize sequence counter per network namespace
esp: delete NETIF_F_SCTP_CRC bit from features for esp offload
ASoC: SOF: Intel: hda: remove unnecessary parentheses
ASoC: SOF: Intel: HDA: fix core status verification
ASoC: wm8960: Fix wrong bclk and lrclk with pll enabled for some chips
xfrm: Fix NULL pointer dereference on policy lookup
i40e: Added Asym_Pause to supported link modes
i40e: Fix kernel oops when i40e driver removes VF's
hostfs: Use kasprintf() instead of fixed buffer formatting
hostfs: fix memory handling in follow_link()
amd-xgbe: Update DMA coherency values
sch_red: fix off-by-one checks in red_check_params()
arm64: dts: imx8mm/q: Fix pad control of SD1_DATA0
can: bcm/raw: fix msg_namelen values depending on CAN_REQUIRED_SIZE
gianfar: Handle error code at MAC address change
cxgb4: avoid collecting SGE_QBASE regs during traffic
net:tipc: Fix a double free in tipc_sk_mcast_rcv
ARM: dts: imx6: pbab01: Set vmmc supply for both SD interfaces
net/ncsi: Avoid channel_monitor hrtimer deadlock
nfp: flower: ignore duplicate merge hints from FW
net: phy: broadcom: Only advertise EEE for supported modes
ASoC: sunxi: sun4i-codec: fill ASoC card owner
net/mlx5e: Fix ethtool indication of connector type
net/mlx5: Don't request more than supported EQs
net/rds: Fix a use after free in rds_message_map_pages
soc/fsl: qbman: fix conflicting alignment attributes
i40e: Fix display statistics for veb_tc
drm/msm: Set drvdata to NULL when msm_drm_init() fails
net: udp: Add support for getsockopt(..., ..., UDP_GRO, ..., ...);
scsi: ufs: Fix irq return code
scsi: ufs: Avoid busy-waiting by eliminating tag conflicts
scsi: ufs: Use blk_{get,put}_request() to allocate and free TMFs
scsi: ufs: core: Fix task management request completion timeout
scsi: ufs: core: Fix wrong Task Tag used in task management request UPIUs
net: macb: restore cmp registers on resume path
clk: fix invalid usage of list cursor in register
clk: fix invalid usage of list cursor in unregister
workqueue: Move the position of debug_work_activate() in __queue_work()
s390/cpcmd: fix
[Kernel-packages] [Bug 1926490] [NEW] Focal update: v5.4.113 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.113 upstream stable release from git://git.kernel.org/ interconnect: core: fix error return code of icc_link_destroy() KVM: arm64: Hide system instruction access to Trace registers KVM: arm64: Disable guest access to trace filter controls drm/imx: imx-ldb: fix out of bounds array access warning gfs2: report "already frozen/thawed" errors drm/tegra: dc: Don't set PLL clock to 0Hz block: only update parent bi_status when bio fail radix tree test suite: Register the main thread with the RCU library idr test suite: Take RCU read lock in idr_find_test_1 idr test suite: Create anchor before launching throbber riscv,entry: fix misaligned base for excp_vect_table block: don't ignore REQ_NOWAIT for direct IO netfilter: x_tables: fix compat match/target pad out-of-bound write driver core: Fix locking bug in deferred_probe_timeout_work_func() perf tools: Use %define api.pure full instead of %pure-parser perf tools: Use %zd for size_t printf formats on 32-bit perf map: Tighten snprintf() string precision to pass gcc check on some 32-bit arches xen/events: fix setting irq affinity Linux 5.4.113 UBUNTU: upstream stable to v5.4.113 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.113 upstream stable release + from git://git.kernel.org/ -v5.4.113 upstream stable release -from git://git.kernel.org/ + interconnect: core: fix error return code of icc_link_destroy() + KVM: arm64: Hide system instruction access to Trace registers + KVM: arm64: Disable guest access to trace filter controls + drm/imx: imx-ldb: fix out of bounds array access warning + gfs2: report "already frozen/thawed" errors + drm/tegra: dc: Don't set PLL clock to 0Hz + block: only update parent bi_status when bio fail + radix tree test suite: Register the main thread with the RCU library + idr test suite: Take RCU read lock in idr_find_test_1 + idr test suite: Create anchor before launching throbber + riscv,entry: fix misaligned base for excp_vect_table + block: don't ignore REQ_NOWAIT for direct IO + netfilter: x_tables: fix compat match/target pad out-of-bound write + driver core: Fix locking bug in deferred_probe_timeout_work_func() + perf tools: Use %define api.pure full instead of %pure-parser + perf tools: Use %zd for size_t printf formats on 32-bit + perf map: Tighten snprintf() string precision to pass gcc check on some 32-bit arches + xen/events: fix setting irq affinity + Linux 5.4.113 + UBUNTU: upstream stable to v5.4.113 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926490 Title: Focal update: v5.4.113 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The up
[Kernel-packages] [Bug 1926481] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1926481/+attachment/5493127/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926481 Title: lockf returns false-positive EDEADLK in multiprocess multithreaded environment Status in linux package in Ubuntu: Confirmed Bug description: As a developer, I found a counter-intuitive behavior in lockf function provided by glibc and Linux kernel that is likely a bug. In glibc, lockf function is implemented on top of fcntl system call: https://github.com/lattera/glibc/blob/master/io/lockf.c man page says that lockf can sometimes detect deadlock: http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html Same with fcntl(F_SETLKW), on top of which lockf is implemented: http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html Deadlock detection algorithm (https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because it can easily give false positives. Suppose we have two processes A and B, process A has threads 1 and 2, process B has threads 3 and 4. When this processes execute concurrently, following sequence of actions is possible: 1. processA thread1 gets lockI 2. processB thread2 gets lockII 3. processA thread3 tries to get lockII, starts to wait 4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is returned from lockf function Steps to reproduce this scenario (see attached file): 1. gcc -o edeadlk ./edeadlk.c -lpthread 2. Launch "./edeadlk a b" in first terminal window. 3. Launch "./edeadlk a b" in second terminal window. What I expected to happen: two instances of the program is steadily working. What happened instead: Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, errno:35 . Error:: Resource deadlock avoided Aborted (core dumped) Surely, this behavior is kind of "right". lockf file locks belongs to process, so on the process level it seems that deadlock is just about to happen: process A holds lockI and waits for lockII, process B holds lockII and is going to wait for lockI. However, algorithm in kernel doesn't take threads into account. In fact, deadlock is not gonna happen here if thread scheduler will give control to some thread holding a lock. I think there's a problem with deadlock detection algorithm because it's overly pessimistic, which in turn creates problems -- lockf errors in applications. # lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 # uname -a Linux test-x64-ub20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 ноя 12 09:53 seq crw-rw 1 root audio 116, 33 ноя 12 09:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-22 (280 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0a89:0030 Aktiv Rutoken ECP Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M |__ Port 1: Dev 4, If 0, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1d0fe562-8128-4922-836e-b0a384fc5054 ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' T
[Kernel-packages] [Bug 1926481] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1926481/+attachment/5493126/+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/1926481 Title: lockf returns false-positive EDEADLK in multiprocess multithreaded environment Status in linux package in Ubuntu: Confirmed Bug description: As a developer, I found a counter-intuitive behavior in lockf function provided by glibc and Linux kernel that is likely a bug. In glibc, lockf function is implemented on top of fcntl system call: https://github.com/lattera/glibc/blob/master/io/lockf.c man page says that lockf can sometimes detect deadlock: http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html Same with fcntl(F_SETLKW), on top of which lockf is implemented: http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html Deadlock detection algorithm (https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because it can easily give false positives. Suppose we have two processes A and B, process A has threads 1 and 2, process B has threads 3 and 4. When this processes execute concurrently, following sequence of actions is possible: 1. processA thread1 gets lockI 2. processB thread2 gets lockII 3. processA thread3 tries to get lockII, starts to wait 4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is returned from lockf function Steps to reproduce this scenario (see attached file): 1. gcc -o edeadlk ./edeadlk.c -lpthread 2. Launch "./edeadlk a b" in first terminal window. 3. Launch "./edeadlk a b" in second terminal window. What I expected to happen: two instances of the program is steadily working. What happened instead: Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, errno:35 . Error:: Resource deadlock avoided Aborted (core dumped) Surely, this behavior is kind of "right". lockf file locks belongs to process, so on the process level it seems that deadlock is just about to happen: process A holds lockI and waits for lockII, process B holds lockII and is going to wait for lockI. However, algorithm in kernel doesn't take threads into account. In fact, deadlock is not gonna happen here if thread scheduler will give control to some thread holding a lock. I think there's a problem with deadlock detection algorithm because it's overly pessimistic, which in turn creates problems -- lockf errors in applications. # lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 # uname -a Linux test-x64-ub20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 ноя 12 09:53 seq crw-rw 1 root audio 116, 33 ноя 12 09:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-22 (280 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0a89:0030 Aktiv Rutoken ECP Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M |__ Port 1: Dev 4, If 0, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1d0fe562-8128-4922-836e-b0a384fc5054 ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus:
[Kernel-packages] [Bug 1926481] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1926481/+attachment/5493125/+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/1926481 Title: lockf returns false-positive EDEADLK in multiprocess multithreaded environment Status in linux package in Ubuntu: Confirmed Bug description: As a developer, I found a counter-intuitive behavior in lockf function provided by glibc and Linux kernel that is likely a bug. In glibc, lockf function is implemented on top of fcntl system call: https://github.com/lattera/glibc/blob/master/io/lockf.c man page says that lockf can sometimes detect deadlock: http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html Same with fcntl(F_SETLKW), on top of which lockf is implemented: http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html Deadlock detection algorithm (https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because it can easily give false positives. Suppose we have two processes A and B, process A has threads 1 and 2, process B has threads 3 and 4. When this processes execute concurrently, following sequence of actions is possible: 1. processA thread1 gets lockI 2. processB thread2 gets lockII 3. processA thread3 tries to get lockII, starts to wait 4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is returned from lockf function Steps to reproduce this scenario (see attached file): 1. gcc -o edeadlk ./edeadlk.c -lpthread 2. Launch "./edeadlk a b" in first terminal window. 3. Launch "./edeadlk a b" in second terminal window. What I expected to happen: two instances of the program is steadily working. What happened instead: Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, errno:35 . Error:: Resource deadlock avoided Aborted (core dumped) Surely, this behavior is kind of "right". lockf file locks belongs to process, so on the process level it seems that deadlock is just about to happen: process A holds lockI and waits for lockII, process B holds lockII and is going to wait for lockI. However, algorithm in kernel doesn't take threads into account. In fact, deadlock is not gonna happen here if thread scheduler will give control to some thread holding a lock. I think there's a problem with deadlock detection algorithm because it's overly pessimistic, which in turn creates problems -- lockf errors in applications. # lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 # uname -a Linux test-x64-ub20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 ноя 12 09:53 seq crw-rw 1 root audio 116, 33 ноя 12 09:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-22 (280 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0a89:0030 Aktiv Rutoken ECP Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M |__ Port 1: Dev 4, If 0, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1d0fe562-8128-4922-836e-b0a384fc5054 ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-42-generic x86_64 Upgr
[Kernel-packages] [Bug 1926481] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1926481/+attachment/5493124/+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/1926481 Title: lockf returns false-positive EDEADLK in multiprocess multithreaded environment Status in linux package in Ubuntu: Confirmed Bug description: As a developer, I found a counter-intuitive behavior in lockf function provided by glibc and Linux kernel that is likely a bug. In glibc, lockf function is implemented on top of fcntl system call: https://github.com/lattera/glibc/blob/master/io/lockf.c man page says that lockf can sometimes detect deadlock: http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html Same with fcntl(F_SETLKW), on top of which lockf is implemented: http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html Deadlock detection algorithm (https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because it can easily give false positives. Suppose we have two processes A and B, process A has threads 1 and 2, process B has threads 3 and 4. When this processes execute concurrently, following sequence of actions is possible: 1. processA thread1 gets lockI 2. processB thread2 gets lockII 3. processA thread3 tries to get lockII, starts to wait 4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is returned from lockf function Steps to reproduce this scenario (see attached file): 1. gcc -o edeadlk ./edeadlk.c -lpthread 2. Launch "./edeadlk a b" in first terminal window. 3. Launch "./edeadlk a b" in second terminal window. What I expected to happen: two instances of the program is steadily working. What happened instead: Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, errno:35 . Error:: Resource deadlock avoided Aborted (core dumped) Surely, this behavior is kind of "right". lockf file locks belongs to process, so on the process level it seems that deadlock is just about to happen: process A holds lockI and waits for lockII, process B holds lockII and is going to wait for lockI. However, algorithm in kernel doesn't take threads into account. In fact, deadlock is not gonna happen here if thread scheduler will give control to some thread holding a lock. I think there's a problem with deadlock detection algorithm because it's overly pessimistic, which in turn creates problems -- lockf errors in applications. # lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 # uname -a Linux test-x64-ub20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 ноя 12 09:53 seq crw-rw 1 root audio 116, 33 ноя 12 09:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-22 (280 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0a89:0030 Aktiv Rutoken ECP Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M |__ Port 1: Dev 4, If 0, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1d0fe562-8128-4922-836e-b0a384fc5054 ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-42-generic x86_64
[Kernel-packages] [Bug 1926481] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1926481/+attachment/5493123/+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/1926481 Title: lockf returns false-positive EDEADLK in multiprocess multithreaded environment Status in linux package in Ubuntu: Confirmed Bug description: As a developer, I found a counter-intuitive behavior in lockf function provided by glibc and Linux kernel that is likely a bug. In glibc, lockf function is implemented on top of fcntl system call: https://github.com/lattera/glibc/blob/master/io/lockf.c man page says that lockf can sometimes detect deadlock: http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html Same with fcntl(F_SETLKW), on top of which lockf is implemented: http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html Deadlock detection algorithm (https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because it can easily give false positives. Suppose we have two processes A and B, process A has threads 1 and 2, process B has threads 3 and 4. When this processes execute concurrently, following sequence of actions is possible: 1. processA thread1 gets lockI 2. processB thread2 gets lockII 3. processA thread3 tries to get lockII, starts to wait 4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is returned from lockf function Steps to reproduce this scenario (see attached file): 1. gcc -o edeadlk ./edeadlk.c -lpthread 2. Launch "./edeadlk a b" in first terminal window. 3. Launch "./edeadlk a b" in second terminal window. What I expected to happen: two instances of the program is steadily working. What happened instead: Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, errno:35 . Error:: Resource deadlock avoided Aborted (core dumped) Surely, this behavior is kind of "right". lockf file locks belongs to process, so on the process level it seems that deadlock is just about to happen: process A holds lockI and waits for lockII, process B holds lockII and is going to wait for lockI. However, algorithm in kernel doesn't take threads into account. In fact, deadlock is not gonna happen here if thread scheduler will give control to some thread holding a lock. I think there's a problem with deadlock detection algorithm because it's overly pessimistic, which in turn creates problems -- lockf errors in applications. # lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 # uname -a Linux test-x64-ub20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 ноя 12 09:53 seq crw-rw 1 root audio 116, 33 ноя 12 09:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-22 (280 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0a89:0030 Aktiv Rutoken ECP Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M |__ Port 1: Dev 4, If 0, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1d0fe562-8128-4922-836e-b0a384fc5054 ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-42-generic
[Kernel-packages] [Bug 1926481] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1926481/+attachment/5493122/+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/1926481 Title: lockf returns false-positive EDEADLK in multiprocess multithreaded environment Status in linux package in Ubuntu: Confirmed Bug description: As a developer, I found a counter-intuitive behavior in lockf function provided by glibc and Linux kernel that is likely a bug. In glibc, lockf function is implemented on top of fcntl system call: https://github.com/lattera/glibc/blob/master/io/lockf.c man page says that lockf can sometimes detect deadlock: http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html Same with fcntl(F_SETLKW), on top of which lockf is implemented: http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html Deadlock detection algorithm (https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because it can easily give false positives. Suppose we have two processes A and B, process A has threads 1 and 2, process B has threads 3 and 4. When this processes execute concurrently, following sequence of actions is possible: 1. processA thread1 gets lockI 2. processB thread2 gets lockII 3. processA thread3 tries to get lockII, starts to wait 4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is returned from lockf function Steps to reproduce this scenario (see attached file): 1. gcc -o edeadlk ./edeadlk.c -lpthread 2. Launch "./edeadlk a b" in first terminal window. 3. Launch "./edeadlk a b" in second terminal window. What I expected to happen: two instances of the program is steadily working. What happened instead: Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, errno:35 . Error:: Resource deadlock avoided Aborted (core dumped) Surely, this behavior is kind of "right". lockf file locks belongs to process, so on the process level it seems that deadlock is just about to happen: process A holds lockI and waits for lockII, process B holds lockII and is going to wait for lockI. However, algorithm in kernel doesn't take threads into account. In fact, deadlock is not gonna happen here if thread scheduler will give control to some thread holding a lock. I think there's a problem with deadlock detection algorithm because it's overly pessimistic, which in turn creates problems -- lockf errors in applications. # lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 # uname -a Linux test-x64-ub20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 ноя 12 09:53 seq crw-rw 1 root audio 116, 33 ноя 12 09:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-22 (280 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0a89:0030 Aktiv Rutoken ECP Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M |__ Port 1: Dev 4, If 0, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1d0fe562-8128-4922-836e-b0a384fc5054 ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-42-generic x86_64 Upgr
[Kernel-packages] [Bug 1926481] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1926481/+attachment/5493121/+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/1926481 Title: lockf returns false-positive EDEADLK in multiprocess multithreaded environment Status in linux package in Ubuntu: Confirmed Bug description: As a developer, I found a counter-intuitive behavior in lockf function provided by glibc and Linux kernel that is likely a bug. In glibc, lockf function is implemented on top of fcntl system call: https://github.com/lattera/glibc/blob/master/io/lockf.c man page says that lockf can sometimes detect deadlock: http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html Same with fcntl(F_SETLKW), on top of which lockf is implemented: http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html Deadlock detection algorithm (https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because it can easily give false positives. Suppose we have two processes A and B, process A has threads 1 and 2, process B has threads 3 and 4. When this processes execute concurrently, following sequence of actions is possible: 1. processA thread1 gets lockI 2. processB thread2 gets lockII 3. processA thread3 tries to get lockII, starts to wait 4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is returned from lockf function Steps to reproduce this scenario (see attached file): 1. gcc -o edeadlk ./edeadlk.c -lpthread 2. Launch "./edeadlk a b" in first terminal window. 3. Launch "./edeadlk a b" in second terminal window. What I expected to happen: two instances of the program is steadily working. What happened instead: Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, errno:35 . Error:: Resource deadlock avoided Aborted (core dumped) Surely, this behavior is kind of "right". lockf file locks belongs to process, so on the process level it seems that deadlock is just about to happen: process A holds lockI and waits for lockII, process B holds lockII and is going to wait for lockI. However, algorithm in kernel doesn't take threads into account. In fact, deadlock is not gonna happen here if thread scheduler will give control to some thread holding a lock. I think there's a problem with deadlock detection algorithm because it's overly pessimistic, which in turn creates problems -- lockf errors in applications. # lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 # uname -a Linux test-x64-ub20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 ноя 12 09:53 seq crw-rw 1 root audio 116, 33 ноя 12 09:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-22 (280 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0a89:0030 Aktiv Rutoken ECP Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M |__ Port 1: Dev 4, If 0, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1d0fe562-8128-4922-836e-b0a384fc5054 ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatu
[Kernel-packages] [Bug 1926481] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1926481/+attachment/5493120/+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/1926481 Title: lockf returns false-positive EDEADLK in multiprocess multithreaded environment Status in linux package in Ubuntu: Confirmed Bug description: As a developer, I found a counter-intuitive behavior in lockf function provided by glibc and Linux kernel that is likely a bug. In glibc, lockf function is implemented on top of fcntl system call: https://github.com/lattera/glibc/blob/master/io/lockf.c man page says that lockf can sometimes detect deadlock: http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html Same with fcntl(F_SETLKW), on top of which lockf is implemented: http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html Deadlock detection algorithm (https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because it can easily give false positives. Suppose we have two processes A and B, process A has threads 1 and 2, process B has threads 3 and 4. When this processes execute concurrently, following sequence of actions is possible: 1. processA thread1 gets lockI 2. processB thread2 gets lockII 3. processA thread3 tries to get lockII, starts to wait 4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is returned from lockf function Steps to reproduce this scenario (see attached file): 1. gcc -o edeadlk ./edeadlk.c -lpthread 2. Launch "./edeadlk a b" in first terminal window. 3. Launch "./edeadlk a b" in second terminal window. What I expected to happen: two instances of the program is steadily working. What happened instead: Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, errno:35 . Error:: Resource deadlock avoided Aborted (core dumped) Surely, this behavior is kind of "right". lockf file locks belongs to process, so on the process level it seems that deadlock is just about to happen: process A holds lockI and waits for lockII, process B holds lockII and is going to wait for lockI. However, algorithm in kernel doesn't take threads into account. In fact, deadlock is not gonna happen here if thread scheduler will give control to some thread holding a lock. I think there's a problem with deadlock detection algorithm because it's overly pessimistic, which in turn creates problems -- lockf errors in applications. # lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 # uname -a Linux test-x64-ub20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 ноя 12 09:53 seq crw-rw 1 root audio 116, 33 ноя 12 09:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-22 (280 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0a89:0030 Aktiv Rutoken ECP Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M |__ Port 1: Dev 4, If 0, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1d0fe562-8128-4922-836e-b0a384fc5054 ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-42-generic x86_64 UpgradeSta
[Kernel-packages] [Bug 1926481] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1926481/+attachment/5493119/+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/1926481 Title: lockf returns false-positive EDEADLK in multiprocess multithreaded environment Status in linux package in Ubuntu: Confirmed Bug description: As a developer, I found a counter-intuitive behavior in lockf function provided by glibc and Linux kernel that is likely a bug. In glibc, lockf function is implemented on top of fcntl system call: https://github.com/lattera/glibc/blob/master/io/lockf.c man page says that lockf can sometimes detect deadlock: http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html Same with fcntl(F_SETLKW), on top of which lockf is implemented: http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html Deadlock detection algorithm (https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because it can easily give false positives. Suppose we have two processes A and B, process A has threads 1 and 2, process B has threads 3 and 4. When this processes execute concurrently, following sequence of actions is possible: 1. processA thread1 gets lockI 2. processB thread2 gets lockII 3. processA thread3 tries to get lockII, starts to wait 4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is returned from lockf function Steps to reproduce this scenario (see attached file): 1. gcc -o edeadlk ./edeadlk.c -lpthread 2. Launch "./edeadlk a b" in first terminal window. 3. Launch "./edeadlk a b" in second terminal window. What I expected to happen: two instances of the program is steadily working. What happened instead: Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, errno:35 . Error:: Resource deadlock avoided Aborted (core dumped) Surely, this behavior is kind of "right". lockf file locks belongs to process, so on the process level it seems that deadlock is just about to happen: process A holds lockI and waits for lockII, process B holds lockII and is going to wait for lockI. However, algorithm in kernel doesn't take threads into account. In fact, deadlock is not gonna happen here if thread scheduler will give control to some thread holding a lock. I think there's a problem with deadlock detection algorithm because it's overly pessimistic, which in turn creates problems -- lockf errors in applications. # lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 # uname -a Linux test-x64-ub20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 ноя 12 09:53 seq crw-rw 1 root audio 116, 33 ноя 12 09:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-22 (280 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0a89:0030 Aktiv Rutoken ECP Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M |__ Port 1: Dev 4, If 0, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1d0fe562-8128-4922-836e-b0a384fc5054 ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No
[Kernel-packages] [Bug 1926481] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1926481/+attachment/5493118/+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/1926481 Title: lockf returns false-positive EDEADLK in multiprocess multithreaded environment Status in linux package in Ubuntu: Confirmed Bug description: As a developer, I found a counter-intuitive behavior in lockf function provided by glibc and Linux kernel that is likely a bug. In glibc, lockf function is implemented on top of fcntl system call: https://github.com/lattera/glibc/blob/master/io/lockf.c man page says that lockf can sometimes detect deadlock: http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html Same with fcntl(F_SETLKW), on top of which lockf is implemented: http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html Deadlock detection algorithm (https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because it can easily give false positives. Suppose we have two processes A and B, process A has threads 1 and 2, process B has threads 3 and 4. When this processes execute concurrently, following sequence of actions is possible: 1. processA thread1 gets lockI 2. processB thread2 gets lockII 3. processA thread3 tries to get lockII, starts to wait 4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is returned from lockf function Steps to reproduce this scenario (see attached file): 1. gcc -o edeadlk ./edeadlk.c -lpthread 2. Launch "./edeadlk a b" in first terminal window. 3. Launch "./edeadlk a b" in second terminal window. What I expected to happen: two instances of the program is steadily working. What happened instead: Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, errno:35 . Error:: Resource deadlock avoided Aborted (core dumped) Surely, this behavior is kind of "right". lockf file locks belongs to process, so on the process level it seems that deadlock is just about to happen: process A holds lockI and waits for lockII, process B holds lockII and is going to wait for lockI. However, algorithm in kernel doesn't take threads into account. In fact, deadlock is not gonna happen here if thread scheduler will give control to some thread holding a lock. I think there's a problem with deadlock detection algorithm because it's overly pessimistic, which in turn creates problems -- lockf errors in applications. # lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 # uname -a Linux test-x64-ub20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 ноя 12 09:53 seq crw-rw 1 root audio 116, 33 ноя 12 09:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-22 (280 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0a89:0030 Aktiv Rutoken ECP Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M |__ Port 1: Dev 4, If 0, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1d0fe562-8128-4922-836e-b0a384fc5054 ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-42-generic x86_64 Up
[Kernel-packages] [Bug 1926481] Re: lockf returns false-positive EDEADLK in multiprocess multithreaded environment
apport information ** Tags added: apport-collected uec-images ** Description changed: As a developer, I found a counter-intuitive behavior in lockf function provided by glibc and Linux kernel that is likely a bug. In glibc, lockf function is implemented on top of fcntl system call: https://github.com/lattera/glibc/blob/master/io/lockf.c man page says that lockf can sometimes detect deadlock: http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html Same with fcntl(F_SETLKW), on top of which lockf is implemented: http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html Deadlock detection algorithm (https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because it can easily give false positives. Suppose we have two processes A and B, process A has threads 1 and 2, process B has threads 3 and 4. When this processes execute concurrently, following sequence of actions is possible: 1. processA thread1 gets lockI 2. processB thread2 gets lockII 3. processA thread3 tries to get lockII, starts to wait 4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is returned from lockf function Steps to reproduce this scenario (see attached file): 1. gcc -o edeadlk ./edeadlk.c -lpthread 2. Launch "./edeadlk a b" in first terminal window. 3. Launch "./edeadlk a b" in second terminal window. What I expected to happen: two instances of the program is steadily working. What happened instead: Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, errno:35 . Error:: Resource deadlock avoided Aborted (core dumped) Surely, this behavior is kind of "right". lockf file locks belongs to process, so on the process level it seems that deadlock is just about to happen: process A holds lockI and waits for lockII, process B holds lockII and is going to wait for lockI. However, algorithm in kernel doesn't take threads into account. In fact, deadlock is not gonna happen here if thread scheduler will give control to some thread holding a lock. I think there's a problem with deadlock detection algorithm because it's overly pessimistic, which in turn creates problems -- lockf errors in applications. # lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 # uname -a Linux test-x64-ub20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 ноя 12 09:53 seq + crw-rw 1 root audio 116, 33 ноя 12 09:53 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.4 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-07-22 (280 days ago) + InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 004: ID 0a89:0030 Aktiv Rutoken ECP + Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub + Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Lsusb-t: + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M + |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M + |__ Port 1: Dev 4, If 0, Class=Chip/SmartCard, Driver=, 12M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M + MachineType: VMware, Inc. VMware Virtual Platform + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=ru_RU.UTF-8 + SHELL=/bin/bash + ProcFB: 0 svgadrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1d0fe562-8128-4922-836e-b0a384fc5054 ro maybe-ubiquity + ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-42-generic N/A + linux-backports-modules-5.4.0-42-generic N/A + linux-firmware1.187.2 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal uec-images + Uname: Linux 5.4.0-42-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 09/21/2015 + dmi.bios.vendor: Phoenix Technologies LTD + dmi.bios.version: 6.00 + dmi.board.name: 440BX Desktop Reference Platform + dmi.board.vendor: Intel Corporation + dmi.board.version: None + dmi.chassis.asset.tag: No Asset Tag + dmi.chass
[Kernel-packages] [Bug 1924685] Re: No sound output/input available after installing 21.04
** Changed in: ubuntu-release-notes 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/1924685 Title: No sound output/input available after installing 21.04 Status in OEM Priority Project: Won't Fix Status in Release Notes for Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Image: Hirsute 21.04 (20210415 daily build) Device: Dell Precision 5750 After installing 21.04, the sound card is unavailable. In Sound Settings, there is only one choice: "Dummy Output" . The only way to hear sound is to connect a Bluetooth speaker. Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel: https://certification.ubuntu.com/hardware/202002-27726 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1561 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 15:10:05 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Precision 5750 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924717] Re: Internal speaker doesn't work after plug in a headset
** Changed in: ubuntu-release-notes Status: New => Fix Released ** Also affects: linux (Ubuntu Impish) Importance: Undecided 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/1924717 Title: Internal speaker doesn't work after plug in a headset Status in Release Notes for Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: [Summary] Internal speaker doesn't work after plug in a headset. In the meantime, audio for HDMI/Buletooth headset/wired headset are working fine. Only Internal speaker doesn't work. But internal speaker working well if not plug wired headset in. CID:202010-28313 https://certification.canonical.com/hardware/202010-28313/ ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1512 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 05:07:59 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Latitude 5520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=8bcd3f6a-d6e8-494d-93fa-6f720bf6e582 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: 1132343535 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/13/2021:br1.2:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5520 dmi.product.sku: 0A21 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1924717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926481] 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 1926481 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/1926481 Title: lockf returns false-positive EDEADLK in multiprocess multithreaded environment Status in linux package in Ubuntu: Incomplete Bug description: As a developer, I found a counter-intuitive behavior in lockf function provided by glibc and Linux kernel that is likely a bug. In glibc, lockf function is implemented on top of fcntl system call: https://github.com/lattera/glibc/blob/master/io/lockf.c man page says that lockf can sometimes detect deadlock: http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html Same with fcntl(F_SETLKW), on top of which lockf is implemented: http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html Deadlock detection algorithm (https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because it can easily give false positives. Suppose we have two processes A and B, process A has threads 1 and 2, process B has threads 3 and 4. When this processes execute concurrently, following sequence of actions is possible: 1. processA thread1 gets lockI 2. processB thread2 gets lockII 3. processA thread3 tries to get lockII, starts to wait 4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is returned from lockf function Steps to reproduce this scenario (see attached file): 1. gcc -o edeadlk ./edeadlk.c -lpthread 2. Launch "./edeadlk a b" in first terminal window. 3. Launch "./edeadlk a b" in second terminal window. What I expected to happen: two instances of the program is steadily working. What happened instead: Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, errno:35 . Error:: Resource deadlock avoided Aborted (core dumped) Surely, this behavior is kind of "right". lockf file locks belongs to process, so on the process level it seems that deadlock is just about to happen: process A holds lockI and waits for lockII, process B holds lockII and is going to wait for lockI. However, algorithm in kernel doesn't take threads into account. In fact, deadlock is not gonna happen here if thread scheduler will give control to some thread holding a lock. I think there's a problem with deadlock detection algorithm because it's overly pessimistic, which in turn creates problems -- lockf errors in applications. # lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 # uname -a Linux test-x64-ub20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 ноя 12 09:53 seq crw-rw 1 root audio 116, 33 ноя 12 09:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-22 (280 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0a89:0030 Aktiv Rutoken ECP Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M |__ Port 1: Dev 4, If 0, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdL
[Kernel-packages] [Bug 1926482] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926482 Title: package linux-image-5.8.0-50-generic 5.8.0-50.56 failed to install/upgrade: triggers looping, abandoned Status in linux package in Ubuntu: Confirmed Bug description: Attempted to upgrade to groovy gorilla. Install could not be completed and the above mentioned package could not be installed. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: b2 2891 F pulseaudio /dev/snd/controlC0: b2 2891 F pulseaudio CasperMD5CheckResult: skip Date: Wed Apr 28 11:36:04 2021 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2020-06-21 (311 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=544a21e7-2da8-49c5-b981-472ed89091e7 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu35.6 SourcePackage: linux Title: package linux-image-5.8.0-50-generic 5.8.0-50.56 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to groovy on 2021-04-28 (0 days ago) dmi.bios.date: 11/19/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922759] Re: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10
ubuntu 5.11 kernel will also be tested tomorrow -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922759 Title: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10 Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: The Clevo NH55RZQ and Intel NUC10 need SND_PCI_QUIRKs to fix wrong pin setup and enable microphones to work correctly when using via the audio jacks. Patches that are fixing these problems have already been accepted to current Linux stable releases: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48698c973e6b4dde94d87cd1ded56d9436e9c97d https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=73e7161eab5dee98114987239ec9c87fe8034ddb Commit-hash: 48698c973e6b4dde94d87cd1ded56d9436e9c97d 73e7161eab5dee98114987239ec9c87fe8034ddb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922759] Re: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10
My colleague tested the Clevo NH55RZQ However the 5.8.0-51.57 kernel is borked for some reason: Audio setting is only showing a Dummy device, which is worse then unpatched kernel. However the mainline 5.12 kernel which uses the exact same quirk works just fine: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/pci/hda/patch_realtek.c?h=v5.12#n8186 NUC10 will be tested tomorrow -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922759 Title: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10 Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: The Clevo NH55RZQ and Intel NUC10 need SND_PCI_QUIRKs to fix wrong pin setup and enable microphones to work correctly when using via the audio jacks. Patches that are fixing these problems have already been accepted to current Linux stable releases: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48698c973e6b4dde94d87cd1ded56d9436e9c97d https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=73e7161eab5dee98114987239ec9c87fe8034ddb Commit-hash: 48698c973e6b4dde94d87cd1ded56d9436e9c97d 73e7161eab5dee98114987239ec9c87fe8034ddb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926482] Re: package linux-image-5.8.0-50-generic 5.8.0-50.56 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926482 Title: package linux-image-5.8.0-50-generic 5.8.0-50.56 failed to install/upgrade: triggers looping, abandoned Status in linux package in Ubuntu: New Bug description: Attempted to upgrade to groovy gorilla. Install could not be completed and the above mentioned package could not be installed. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: b2 2891 F pulseaudio /dev/snd/controlC0: b2 2891 F pulseaudio CasperMD5CheckResult: skip Date: Wed Apr 28 11:36:04 2021 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2020-06-21 (311 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=544a21e7-2da8-49c5-b981-472ed89091e7 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu35.6 SourcePackage: linux Title: package linux-image-5.8.0-50-generic 5.8.0-50.56 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to groovy on 2021-04-28 (0 days ago) dmi.bios.date: 11/19/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926482] [NEW] package linux-image-5.8.0-50-generic 5.8.0-50.56 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Attempted to upgrade to groovy gorilla. Install could not be completed and the above mentioned package could not be installed. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: b2 2891 F pulseaudio /dev/snd/controlC0: b2 2891 F pulseaudio CasperMD5CheckResult: skip Date: Wed Apr 28 11:36:04 2021 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2020-06-21 (311 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=544a21e7-2da8-49c5-b981-472ed89091e7 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu35.6 SourcePackage: linux Title: package linux-image-5.8.0-50-generic 5.8.0-50.56 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to groovy on 2021-04-28 (0 days ago) dmi.bios.date: 11/19/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926482 Title: package linux-image-5.8.0-50-generic 5.8.0-50.56 failed to install/upgrade: triggers looping, abandoned Status in linux package in Ubuntu: New Bug description: Attempted to upgrade to groovy gorilla. Install could not be completed and the above mentioned package could not be installed. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: b2 2891 F pulseaudio /dev/snd/controlC0: b2 2891 F pulseaudio CasperMD5CheckResult: skip Date: Wed Apr 28 11:36:04 2021 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2020-06-21 (311 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=544a21e7-2da8-49c5-b981-472ed89091e7 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu35.6 SourcePackage: linux Title: package linux-image-5.8.0-50-generic 5.8.0-50.56 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to groovy on 2021-04-28 (0 days ago) dmi.bios.date: 11/19/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.
[Kernel-packages] [Bug 1926481] [NEW] lockf returns false-positive EDEADLK in multiprocess multithreaded environment
Public bug reported: As a developer, I found a counter-intuitive behavior in lockf function provided by glibc and Linux kernel that is likely a bug. In glibc, lockf function is implemented on top of fcntl system call: https://github.com/lattera/glibc/blob/master/io/lockf.c man page says that lockf can sometimes detect deadlock: http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html Same with fcntl(F_SETLKW), on top of which lockf is implemented: http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html Deadlock detection algorithm (https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because it can easily give false positives. Suppose we have two processes A and B, process A has threads 1 and 2, process B has threads 3 and 4. When this processes execute concurrently, following sequence of actions is possible: 1. processA thread1 gets lockI 2. processB thread2 gets lockII 3. processA thread3 tries to get lockII, starts to wait 4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is returned from lockf function Steps to reproduce this scenario (see attached file): 1. gcc -o edeadlk ./edeadlk.c -lpthread 2. Launch "./edeadlk a b" in first terminal window. 3. Launch "./edeadlk a b" in second terminal window. What I expected to happen: two instances of the program is steadily working. What happened instead: Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, errno:35 . Error:: Resource deadlock avoided Aborted (core dumped) Surely, this behavior is kind of "right". lockf file locks belongs to process, so on the process level it seems that deadlock is just about to happen: process A holds lockI and waits for lockII, process B holds lockII and is going to wait for lockI. However, algorithm in kernel doesn't take threads into account. In fact, deadlock is not gonna happen here if thread scheduler will give control to some thread holding a lock. I think there's a problem with deadlock detection algorithm because it's overly pessimistic, which in turn creates problems -- lockf errors in applications. # lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 # uname -a Linux test-x64-ub20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "test to reproduce the problem" https://bugs.launchpad.net/bugs/1926481/+attachment/5493082/+files/edeadlk.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926481 Title: lockf returns false-positive EDEADLK in multiprocess multithreaded environment Status in linux package in Ubuntu: New Bug description: As a developer, I found a counter-intuitive behavior in lockf function provided by glibc and Linux kernel that is likely a bug. In glibc, lockf function is implemented on top of fcntl system call: https://github.com/lattera/glibc/blob/master/io/lockf.c man page says that lockf can sometimes detect deadlock: http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html Same with fcntl(F_SETLKW), on top of which lockf is implemented: http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html Deadlock detection algorithm (https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because it can easily give false positives. Suppose we have two processes A and B, process A has threads 1 and 2, process B has threads 3 and 4. When this processes execute concurrently, following sequence of actions is possible: 1. processA thread1 gets lockI 2. processB thread2 gets lockII 3. processA thread3 tries to get lockII, starts to wait 4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is returned from lockf function Steps to reproduce this scenario (see attached file): 1. gcc -o edeadlk ./edeadlk.c -lpthread 2. Launch "./edeadlk a b" in first terminal window. 3. Launch "./edeadlk a b" in second terminal window. What I expected to happen: two instances of the program is steadily working. What happened instead: Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, errno:35 . Error:: Resource deadlock avoided Aborted (core dumped) Surely, this behavior is kind of "right". lockf file locks belongs to process, so on the process level it seems that deadlock is just about to happen: process A holds lockI and waits for lockII, process B holds lockII and is going to wait for lockI. However, algorithm in kernel doesn't take threads into account. In fact, deadlock is not gonna happen here if thread scheduler will give control to some thread holding a lock. I think there's a problem with deadlock detection algorithm because it's overly pessimistic, which in turn creates problems -- lockf errors in applications. #
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
Hi all. I am also affected by this bug. Just to be clear, Ubuntu 20.04 works with a previous version of Linux Kernel right ( <= 4.15)? I can use a downgraded version of the kernel for now if thats the only thing that can be done atm. Regards, Akash -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). WORKAROUND: I installed the 4.15 kernel, so at the moment I can work with this. Higher than 4.15 the second monitor doesn't work. Tested until 5.8 and without good results. Just with 4.15. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvi
[Kernel-packages] [Bug 1924685] Re: No sound output/input available after installing 21.04
Yes, my bluetooth headset mic is detected (Escape 500 ANC) but no sound is received. Also when I try HSP/HPF output the sound is Dalek-y, high- fidelity is fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924685 Title: No sound output/input available after installing 21.04 Status in OEM Priority Project: Won't Fix Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Image: Hirsute 21.04 (20210415 daily build) Device: Dell Precision 5750 After installing 21.04, the sound card is unavailable. In Sound Settings, there is only one choice: "Dummy Output" . The only way to hear sound is to connect a Bluetooth speaker. Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel: https://certification.ubuntu.com/hardware/202002-27726 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1561 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 15:10:05 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Precision 5750 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
Andrew - It was suggested that there are a couple more patches relevant
to this issue:
mm: fix oom_kill event handling
mem_cgroup: make sure moving_account, move_lock_task and stat_cpu in the same
cacheline
mm: memcg: make sure memory.events is uptodate when waking pollers
mm: memcontrol: fix NR_WRITEBACK leak in memcg and system stats
Please test the kernel at
https://kernel.ubuntu.com/~rtg/LP%231926081/4.15.0-144.148~LP1926081.2/amd64/
to make sure it still solves your issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1926081
Title:
nr_writeback memory leak in kernel 4.15.0-137+
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
SRU Justification
[Impact]
Ubuntu 18.04.5 4.15.0 LTS kernels at version 4.15.0-137 and above
contain a memory leak due to the inclusion of patch from the upstream
kernel, but not the fix for that patch which was released later.
Bad patch in bionic:linux 2c17fa778db85644458b52a7df8eacc402cbc1ef mm:
memcontrol: fix excessive complexity in memory.stat reporting
This issue manifests itself as an increasing amount of memory used by
the writeback queue, which never returns to zero. This can been seen
either as the value of `nr_writeback` in /proc/vmstat, or the value of
`Writeback` in /proc/meminfo.
Ordinarily these values should be at or around zero, but on our
servers we observe the `nr_writeback` value increasing to over 8
million, (32GB of memory), at which point it isn't long before the
system IO slows to a crawl (tens of Kb/s). Our servers have 256GB of
memory, and are performing many CI related activities - this issue
appears to be related to concurrent writing to disk, and can be
demonstrated with a simple testcase (see later).
On our heavily used systems this memory leak can result in an unstable
server after 2-3 days, requiring a reboot to fix it.
After much investigation the issue appears to be because the patch
"mm: memcontrol: fix excessive complexity in memory.stat reporting"
was brought in to the 4.15.0-137 Ubuntu kernel (see
https://launchpad.net/ubuntu/+source/linux/4.15.0-137.141) as part of
" Bionic update: upstream stable patchset 2021-01-25 (LP: #1913214)",
however in the mainline kernel there was a follow up patch because
this initial patch introduced concurrency issues. The patch "mm:
memcontrol: fix NR_WRITEBACK leak in memcg and system stats" is
required, and should be brought into the Ubuntu packaged kernel to fix
the issues reported.
The required patch is here:
https://github.com/torvalds/linux/commit/c3cc39118c3610eb6ab4711bc624af7fc48a35fe
and was committed a few weeks after the original (broken) patch:
https://github.com/torvalds/linux/commit/a983b5ebee57209c99f68c8327072f25e0e6e3da
I have checked the release notes for Ubuntu versions -137 to -143, and
none include this second patch that should fix the issue. (I checked
https://people.canonical.com/~kernel/info/kernel-version-map.html for
all the kernel versions, and then visited each changelog page in turn,
e.g. https://launchpad.net/ubuntu/+source/linux/4.15.0-143.147 looking
for "mm: memcontrol: fix NR_WRITEBACK leak in memcg and system
stats").
We do not observe this on the 5.4.0 kernel (supported HWE kernel on
18.05.5), which includes this second patch. That kernel may also
include other patches, so we do not know if any other fixes are also
required, but the one we have linked above seems to definitely be
needed, and seems to match our symptoms.
[Test Plan]
Testcase:
The following is enough to permanently increase the value of
`nr_writeback` on our systems (by about 2000 during most executions):
```
date
grep nr_writeback /proc/vmstat
mkdir -p /docker/testfiles/{1..5}
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/1/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/2/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/3/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/4/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/5/file.% bs=4k count=10 status=none' &
wait $(jobs -p)
grep nr_writeback /proc/vmstat
date
```
Subsequent iterations of the test raise it further, and on a system
doing a lot of writing from a lot of different processes, it can rise
quickly.
System details:
lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Affected kernel: 4.15.0-137 onwards (current latest version tried was
4.15.0-142)
e.g.
apt-cache policy linux-
[Kernel-packages] [Bug 1924685] Re: No sound output/input available after installing 21.04
Thanks Herczeg Zsolt. I was able to compile latest kernel with those settings and it works for my Dell XPS 9700. Except for the headset microphone. Does anyone else have problems with headset microphone? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924685 Title: No sound output/input available after installing 21.04 Status in OEM Priority Project: Won't Fix Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Image: Hirsute 21.04 (20210415 daily build) Device: Dell Precision 5750 After installing 21.04, the sound card is unavailable. In Sound Settings, there is only one choice: "Dummy Output" . The only way to hear sound is to connect a Bluetooth speaker. Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel: https://certification.ubuntu.com/hardware/202002-27726 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1561 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 15:10:05 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Precision 5750 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
The kernel installation via debs always created the link. Just the installkernel command which is not part or the kernel packages had the issue of only moving around the kernel links but not the initrd ones. The case which I was working on was having a system which only had kernels install via .debs and then would run installkernel (with the new postinst.d hook installed). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More he
[Kernel-packages] [Bug 1922759] Re: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10
links to wring repo but same in groovy repo: https://kernel.ubuntu.com/git/ubuntu/ubuntu- groovy.git/tree/sound/pci/hda/patch_realtek.c?h=master- prep&id=0f3c49138f90cb367c96f94d68cdbf530869f971#n8155 https://kernel.ubuntu.com/git/ubuntu/ubuntu- groovy.git/tree/sound/pci/hda/patch_realtek.c?h=master- prep&id=0f3c49138f90cb367c96f94d68cdbf530869f971#n8250 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922759 Title: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10 Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: The Clevo NH55RZQ and Intel NUC10 need SND_PCI_QUIRKs to fix wrong pin setup and enable microphones to work correctly when using via the audio jacks. Patches that are fixing these problems have already been accepted to current Linux stable releases: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48698c973e6b4dde94d87cd1ded56d9436e9c97d https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=73e7161eab5dee98114987239ec9c87fe8034ddb Commit-hash: 48698c973e6b4dde94d87cd1ded56d9436e9c97d 73e7161eab5dee98114987239ec9c87fe8034ddb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922759] Re: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10
Loking in the code of 5.8.0-51.57 the fixes are there: https://kernel.ubuntu.com/git/ubuntu/ubuntu- focal.git/tree/sound/pci/hda/patch_realtek.c?h=hwe-5.8&id=37a31d9d4344b1438a49f8afaabdac3c834364a7#n8155 https://kernel.ubuntu.com/git/ubuntu/ubuntu- focal.git/tree/sound/pci/hda/patch_realtek.c?h=hwe-5.8&id=37a31d9d4344b1438a49f8afaabdac3c834364a7#n8250 I currently don't have the devices at hand (homeoffice), but I will let a colleague know so that he can test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922759 Title: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10 Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: The Clevo NH55RZQ and Intel NUC10 need SND_PCI_QUIRKs to fix wrong pin setup and enable microphones to work correctly when using via the audio jacks. Patches that are fixing these problems have already been accepted to current Linux stable releases: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48698c973e6b4dde94d87cd1ded56d9436e9c97d https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=73e7161eab5dee98114987239ec9c87fe8034ddb Commit-hash: 48698c973e6b4dde94d87cd1ded56d9436e9c97d 73e7161eab5dee98114987239ec9c87fe8034ddb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926453] [NEW] Migrate the NVIDIA UDA 450 series to the 460 series
Public bug reported: Migrate the NVIDIA UDA 450 series to the 460 series ** Affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: High Assignee: Alberto Milone (albertomilone) Status: Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1926453 Title: Migrate the NVIDIA UDA 450 series to the 460 series Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Bug description: Migrate the NVIDIA UDA 450 series to the 460 series To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1926453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921498] Re: [Ubuntu 21.04] s390/vtime: fix increased steal time accounting
Thx for the verifications, I've adjusted the tags accordingly.
** Tags removed: verification-needed-focal verification-needed-groovy
** Tags added: verification-done-focal verification-done-groovy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1921498
Title:
[Ubuntu 21.04] s390/vtime: fix increased steal time accounting
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* The reported steal time on s390x is erroneously increasing and
therefore broken.
* This problem got introduced with commit 152e9b8676c6e
("s390/vtime: steal time exponential moving average") - upstream with v5.1
[Fix]
* d54cb7d54877d529bc1e0e1f47a3dd082f73add3 d54cb7d54877 "s390/vtime:
fix increased steal time accounting"
[Test Case]
* An IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04,
20.10 and 21.04 on LPAR, are needed.
* The system needs to be configured as KVM host with one or more KVM
guests.
* Now put significant workload on the guest(s), so that the hypervisor starts
to 'steal time'.
This can be best forced by having only very limited CPU resources for the
hypervisor itself.
* Start monitoring the steal time, that is reported at /proc/stat,
but can be more easily verified with tools like vmstat or even top.
* If the steal time starts ever growing (exponentially), the situation
is broken.
* In case the steal time stays relatively constant,
or grows only very limited after a ramp up phase of some minutes,
or just oscillates around a certain value, a fixed/patched kernel is in use.
[Regression Potential]
* The patch only changes the single line that calculates:
account_steal_time
* In case the account_steal_time calculation is still broken after the
modification,
the steal time is just again not reported correctly on s390x,
but maybe in a different way (rather than exponentially growing).
* But it will not further harm virtualization on s390x systems.
* The modification is very limited with that one line change.
* The commit got upstream accepted with 5.12-rc4.
[Other]
* Since the patch is needed for kernel higher than 5.1 and got upstream
accepted with 5.12-rc4,
hirsute, groovy and focal are affected.
* The upstream commit can be cleanly cherry-picked from all three affected
Ubuntu releases.
__
Description: s390/vtime: fix increased steal time accounting
Symptom: Increased steal time values.
Problem: Commit 152e9b8676c6e ("s390/vtime: steal time exponential
moving average") inadvertently changed the input value for
account_steal_time() from "cputime_to_nsecs(steal)" to just
"steal", resulting in broken increased steal time accounting.
Solution: Fix this by changing it back to "cputime_to_nsecs(steal)".
Reproduction: -
Upstream-ID: d54cb7d54877d529bc1e0e1f47a3dd082f73add3
Stable tagged : kernel 5.1.
Therefore only to be applyable for focal, groovy, hirsuite.
Due to stable tag integration , only for integration checking..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921498/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921498] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-04-28 09:21 EDT---
Verified by IBM for focal and groovy...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1921498
Title:
[Ubuntu 21.04] s390/vtime: fix increased steal time accounting
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* The reported steal time on s390x is erroneously increasing and
therefore broken.
* This problem got introduced with commit 152e9b8676c6e
("s390/vtime: steal time exponential moving average") - upstream with v5.1
[Fix]
* d54cb7d54877d529bc1e0e1f47a3dd082f73add3 d54cb7d54877 "s390/vtime:
fix increased steal time accounting"
[Test Case]
* An IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04,
20.10 and 21.04 on LPAR, are needed.
* The system needs to be configured as KVM host with one or more KVM
guests.
* Now put significant workload on the guest(s), so that the hypervisor starts
to 'steal time'.
This can be best forced by having only very limited CPU resources for the
hypervisor itself.
* Start monitoring the steal time, that is reported at /proc/stat,
but can be more easily verified with tools like vmstat or even top.
* If the steal time starts ever growing (exponentially), the situation
is broken.
* In case the steal time stays relatively constant,
or grows only very limited after a ramp up phase of some minutes,
or just oscillates around a certain value, a fixed/patched kernel is in use.
[Regression Potential]
* The patch only changes the single line that calculates:
account_steal_time
* In case the account_steal_time calculation is still broken after the
modification,
the steal time is just again not reported correctly on s390x,
but maybe in a different way (rather than exponentially growing).
* But it will not further harm virtualization on s390x systems.
* The modification is very limited with that one line change.
* The commit got upstream accepted with 5.12-rc4.
[Other]
* Since the patch is needed for kernel higher than 5.1 and got upstream
accepted with 5.12-rc4,
hirsute, groovy and focal are affected.
* The upstream commit can be cleanly cherry-picked from all three affected
Ubuntu releases.
__
Description: s390/vtime: fix increased steal time accounting
Symptom: Increased steal time values.
Problem: Commit 152e9b8676c6e ("s390/vtime: steal time exponential
moving average") inadvertently changed the input value for
account_steal_time() from "cputime_to_nsecs(steal)" to just
"steal", resulting in broken increased steal time accounting.
Solution: Fix this by changing it back to "cputime_to_nsecs(steal)".
Reproduction: -
Upstream-ID: d54cb7d54877d529bc1e0e1f47a3dd082f73add3
Stable tagged : kernel 5.1.
Therefore only to be applyable for focal, groovy, hirsuite.
Due to stable tag integration , only for integration checking..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921498/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814003] Re: kernel BUG at fs/ext4/inode.c:2679!
I've been seeing this problem for several years, with different Ubuntu verisons, and still can repro on 20.04, kernel 5.4.0-72-generic. I think this one is related: https://lkml.org/lkml/2019/3/8/806 ** Attachment added: "kern.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814003/+attachment/5493060/+files/kern.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/1814003 Title: kernel BUG at fs/ext4/inode.c:2679! Status in linux package in Ubuntu: Confirmed Bug description: I started seeing this bug in Ubuntu 18.04 running VMWare Workstation Pro 14. After upgrading to Ubuntu 18.10 and VMware Workstation 15 the bug still appears. I started to ask questions on the VMware Community, https://communities.vmware.com/thread/604705. Because I had some additional time to troubleshoot I am also noticing that this bug is being reported on other Linux Distributions notably: https://bugzilla.redhat.com/show_bug.cgi?id=1662314 Conditions to reproduce. Laptop is running 2 NVMe drives with Cryptfs on each drive (unsure if this is related). Running Vmware Workstation Pro 15 with a Windows 10 Guest upon shutting down the Windows Guest a kernel stack strace appears in both dmesg -w and /var/log/syslog. The VM does not gracefully stop. Stack Trace is Below: Jan 30 17:10:02 system-box kernel: [13117.565550] [ cut here ] Jan 30 17:10:02 system-box kernel: [13116.565552] kernel BUG at fs/ext4/inode.c:2679! Jan 30 17:10:02 system-box kernel: [13117.565558] invalid opcode: [#1] SMP PTI Jan 30 17:10:02 system-box kernel: [13117.565561] CPU: 0 PID: 18820 Comm: kworker/u8:0 Tainted: GW OE 4.18.0-13-generic #14-Ubuntu Jan 30 17:10:02 system-box kernel: [13117.565562] Hardware name: LENOVO 20HES35Q00/20HES35Q00, BIOS N1QET79W (1.54 ) 11/16/2018 Jan 30 17:10:02 system-box kernel: [13117.565566] Workqueue: writeback wb_workfn (flush-253:3) Jan 30 17:10:02 system-box kernel: [13117.565569] RIP: 0010:mpage_prepare_extent_to_map+0x2bc/0x2f0 Jan 30 17:10:02 system-box kernel: [13117.565570] Code: 86 0a fe ff ff 31 c0 eb a4 4c 89 ef e8 4d b3 e9 ff e9 91 fe ff ff be 0e 00 00 00 4c 89 ef e8 5b bb e9 ff e9 e4 fe ff ff 0f 0b <0f> 0b 48 8d bd 50 ff ff ff 89 85 40 ff ff ff e8 50 1a eb ff 8b 85 Jan 30 17:10:02 system-box kernel: [13117.565589] RSP: 0018:99674b78b930 EFLAGS: 00010246 ...skipping... Jan 30 17:10:02 system-box kernel: [13117.565633] ? ext4_mark_inode_dirty+0x1d0/0x1d0 Jan 30 17:10:02 system-box kernel: [13117.565635] ? do_writepages+0x41/0xd0 Jan 30 17:10:02 system-box kernel: [13117.565638] ? check_preempt_wakeup+0x11f/0x250 Jan 30 17:10:02 system-box kernel: [13117.565641] __writeback_single_inode+0x40/0x360 Jan 30 17:10:02 system-box kernel: [13117.565643] writeback_sb_inodes+0x211/0x520 Jan 30 17:10:02 system-box kernel: [13117.565646] __writeback_inodes_wb+0x67/0xb0 Jan 30 17:10:02 system-box kernel: [13117.565648] wb_writeback+0x25f/0x2f0 Jan 30 17:10:02 system-box kernel: [13117.565651] ? get_nr_dirty_inodes+0x46/0x70 Jan 30 17:10:02 system-box kernel: [13117.565654] wb_workfn+0x32c/0x3f0 Jan 30 17:10:02 system-box kernel: [13117.565656] ? __switch_to_asm+0x34/0x70 Jan 30 17:10:02 system-box kernel: [13117.565660] process_one_work+0x20f/0x3c0 Jan 30 17:10:02 system-box kernel: [13117.565662] worker_thread+0x34/0x400 Jan 30 17:10:02 system-box kernel: [13117.565664] kthread+0x120/0x140 Jan 30 17:10:02 system-box kernel: [13117.565667] ? pwq_unbound_release_workfn+0xd0/0xd0 Jan 30 17:10:02 system-box kernel: [13117.565668] ? kthread_bind+0x40/0x40 Jan 30 17:10:02 system-box kernel: [13117.565670] ret_from_fork+0x35/0x40 Jan 30 17:10:02 system-box kernel: [13117.565671] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 vmnet(OE) parport_pc vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) thunderbolt rfcomm veth xt_nat nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox msr ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 cmac nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc devlink pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) ip6table_filter ip6_tables vboxdrv(OE) iptable_filter bpfilter aufs overlay bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common btusb btrtl videodev btbcm Jan 30 17:10:02 system-box kernel: [13117.565701] media btintel bluetooth ecdh_generic binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_
[Kernel-packages] [Bug 1921498] Re: [Ubuntu 21.04] s390/vtime: fix increased steal time accounting
** Summary changed:
- [UBUNUT 21.04] s390/vtime: fix increased steal time accounting
+ [Ubuntu 21.04] s390/vtime: fix increased steal time accounting
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1921498
Title:
[Ubuntu 21.04] s390/vtime: fix increased steal time accounting
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* The reported steal time on s390x is erroneously increasing and
therefore broken.
* This problem got introduced with commit 152e9b8676c6e
("s390/vtime: steal time exponential moving average") - upstream with v5.1
[Fix]
* d54cb7d54877d529bc1e0e1f47a3dd082f73add3 d54cb7d54877 "s390/vtime:
fix increased steal time accounting"
[Test Case]
* An IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04,
20.10 and 21.04 on LPAR, are needed.
* The system needs to be configured as KVM host with one or more KVM
guests.
* Now put significant workload on the guest(s), so that the hypervisor starts
to 'steal time'.
This can be best forced by having only very limited CPU resources for the
hypervisor itself.
* Start monitoring the steal time, that is reported at /proc/stat,
but can be more easily verified with tools like vmstat or even top.
* If the steal time starts ever growing (exponentially), the situation
is broken.
* In case the steal time stays relatively constant,
or grows only very limited after a ramp up phase of some minutes,
or just oscillates around a certain value, a fixed/patched kernel is in use.
[Regression Potential]
* The patch only changes the single line that calculates:
account_steal_time
* In case the account_steal_time calculation is still broken after the
modification,
the steal time is just again not reported correctly on s390x,
but maybe in a different way (rather than exponentially growing).
* But it will not further harm virtualization on s390x systems.
* The modification is very limited with that one line change.
* The commit got upstream accepted with 5.12-rc4.
[Other]
* Since the patch is needed for kernel higher than 5.1 and got upstream
accepted with 5.12-rc4,
hirsute, groovy and focal are affected.
* The upstream commit can be cleanly cherry-picked from all three affected
Ubuntu releases.
__
Description: s390/vtime: fix increased steal time accounting
Symptom: Increased steal time values.
Problem: Commit 152e9b8676c6e ("s390/vtime: steal time exponential
moving average") inadvertently changed the input value for
account_steal_time() from "cputime_to_nsecs(steal)" to just
"steal", resulting in broken increased steal time accounting.
Solution: Fix this by changing it back to "cputime_to_nsecs(steal)".
Reproduction: -
Upstream-ID: d54cb7d54877d529bc1e0e1f47a3dd082f73add3
Stable tagged : kernel 5.1.
Therefore only to be applyable for focal, groovy, hirsuite.
Due to stable tag integration , only for integration checking..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921498/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922759] Re: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10
Hello Werner, Could you please verify if the latest 20.10 Groovy kernel in -proposed fixes the issue reported? As of now the version of the latest kernel is 5.8.0-51.57. Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922759 Title: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10 Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: The Clevo NH55RZQ and Intel NUC10 need SND_PCI_QUIRKs to fix wrong pin setup and enable microphones to work correctly when using via the audio jacks. Patches that are fixing these problems have already been accepted to current Linux stable releases: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48698c973e6b4dde94d87cd1ded56d9436e9c97d https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=73e7161eab5dee98114987239ec9c87fe8034ddb Commit-hash: 48698c973e6b4dde94d87cd1ded56d9436e9c97d 73e7161eab5dee98114987239ec9c87fe8034ddb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926439] Re: Dependencies conflicts breaks upgrade process
Last version without this problem: ~# apt show linux-modules-nvidia-460-5.4.0-70-generic Package: linux-modules-nvidia-460-5.4.0-70-generic Version: 5.4.0-70.78 Priority: optional Section: restricted/kernel Source: linux-restricted-modules Origin: Ubuntu Maintainer: Canonical Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 45.3 MB Depends: debconf (>= 0.5) | debconf-2.0, binutils, linux-image-5.4.0-70-generic | linux-image-unsigned-5.4.0-70-generic Download-Size: 24.2 MB APT-Sources: http://archive.pls.pbank.com.ua/ubuntu-current focal-updates/restricted amd64 Packages Description: Linux kernel nvidia modules for version 5.4.0-70 -- 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/1926439 Title: Dependencies conflicts breaks upgrade process Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: Latest updates of linux-restricted-modules breaks upgrade process, updates cannot be installed without removing nvidia modules for previous kernel version, unattended-upgrade cannot do that, as result we have broken system without nvidia driver ~# apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: linux-modules-nvidia-460-5.4.0-71-generic The following NEW packages will be installed: linux-modules-nvidia-460-5.4.0-72-generic linux-objects-nvidia-460-5.4.0-72-generic linux-signatures-nvidia-5.4.0-72-generic The following packages will be upgraded: libnvidia-cfg1-460 libnvidia-compute-460 libnvidia-compute-460:i386 libnvidia-decode-460 libnvidia-decode-460:i386 libnvidia-encode-460 libnvidia-encode-460:i386 libnvidia-extra-460 libnvidia-fbc1-460 libnvidia-fbc1-460:i386 libnvidia-gl-460 libnvidia-gl-460:i386 libnvidia-ifr1-460 libnvidia-ifr1-460:i386 linux-modules-nvidia-460-generic nvidia-compute-utils-460 nvidia-driver-460 nvidia-kernel-common-460 nvidia-kernel-source-460 nvidia-utils-460 xserver-xorg-video-nvidia-460 21 upgraded, 3 newly installed, 1 to remove and 0 not upgraded. Need to get 199 MB of archives. After this operation, 45.6 MB of additional disk space will be used. Do you want to continue? [Y/n] ~# apt show linux-modules-nvidia-460-5.4.0-71-generic Package: linux-modules-nvidia-460-5.4.0-71-generic Version: 5.4.0-71.79+1 Priority: optional Section: restricted/kernel Source: linux-restricted-modules Origin: Ubuntu Maintainer: Canonical Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 32.8 kB Depends: debconf (>= 0.5) | debconf-2.0, linux-image-5.4.0-71-generic | linux-image-unsigned-5.4.0-71-generic, linux-signatures-nvidia-5.4.0-71-generic (= 5.4.0-71.79+1), linux-objects-nvidia-460-5.4.0-71-generic (= 5.4.0-71.79+1), nvidia-kernel-common-460 (<= 460.56-1), nvidia-kernel-common-460 (>= 460.56) Download-Size: 7136 B APT-Manual-Installed: no APT-Sources: http://archive.pls.pbank.com.ua/ubuntu-current focal-updates/restricted amd64 Packages Description: Linux kernel nvidia modules for version 5.4.0-71 This dependencies should be removed to fix this problem: nvidia-kernel-common-460 (<= 460.56-1), nvidia-kernel-common-460 (>= 460.56) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1926439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926439] Re: Dependencies conflicts breaks upgrade process
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-restricted-modules (Ubuntu) Status: New => Confirmed -- 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/1926439 Title: Dependencies conflicts breaks upgrade process Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: Latest updates of linux-restricted-modules breaks upgrade process, updates cannot be installed without removing nvidia modules for previous kernel version, unattended-upgrade cannot do that, as result we have broken system without nvidia driver ~# apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: linux-modules-nvidia-460-5.4.0-71-generic The following NEW packages will be installed: linux-modules-nvidia-460-5.4.0-72-generic linux-objects-nvidia-460-5.4.0-72-generic linux-signatures-nvidia-5.4.0-72-generic The following packages will be upgraded: libnvidia-cfg1-460 libnvidia-compute-460 libnvidia-compute-460:i386 libnvidia-decode-460 libnvidia-decode-460:i386 libnvidia-encode-460 libnvidia-encode-460:i386 libnvidia-extra-460 libnvidia-fbc1-460 libnvidia-fbc1-460:i386 libnvidia-gl-460 libnvidia-gl-460:i386 libnvidia-ifr1-460 libnvidia-ifr1-460:i386 linux-modules-nvidia-460-generic nvidia-compute-utils-460 nvidia-driver-460 nvidia-kernel-common-460 nvidia-kernel-source-460 nvidia-utils-460 xserver-xorg-video-nvidia-460 21 upgraded, 3 newly installed, 1 to remove and 0 not upgraded. Need to get 199 MB of archives. After this operation, 45.6 MB of additional disk space will be used. Do you want to continue? [Y/n] ~# apt show linux-modules-nvidia-460-5.4.0-71-generic Package: linux-modules-nvidia-460-5.4.0-71-generic Version: 5.4.0-71.79+1 Priority: optional Section: restricted/kernel Source: linux-restricted-modules Origin: Ubuntu Maintainer: Canonical Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 32.8 kB Depends: debconf (>= 0.5) | debconf-2.0, linux-image-5.4.0-71-generic | linux-image-unsigned-5.4.0-71-generic, linux-signatures-nvidia-5.4.0-71-generic (= 5.4.0-71.79+1), linux-objects-nvidia-460-5.4.0-71-generic (= 5.4.0-71.79+1), nvidia-kernel-common-460 (<= 460.56-1), nvidia-kernel-common-460 (>= 460.56) Download-Size: 7136 B APT-Manual-Installed: no APT-Sources: http://archive.pls.pbank.com.ua/ubuntu-current focal-updates/restricted amd64 Packages Description: Linux kernel nvidia modules for version 5.4.0-71 This dependencies should be removed to fix this problem: nvidia-kernel-common-460 (<= 460.56-1), nvidia-kernel-common-460 (>= 460.56) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1926439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926439] Re: Dependencies conflicts breaks upgrade process
** Attachment added: "Знімок екрану з 2021-04-28 15-48-35.png" https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1926439/+attachment/5493056/+files/%D0%97%D0%BD%D1%96%D0%BC%D0%BE%D0%BA%20%D0%B5%D0%BA%D1%80%D0%B0%D0%BD%D1%83%20%D0%B7%202021-04-28%2015-48-35.png -- 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/1926439 Title: Dependencies conflicts breaks upgrade process Status in linux-restricted-modules package in Ubuntu: New Bug description: Latest updates of linux-restricted-modules breaks upgrade process, updates cannot be installed without removing nvidia modules for previous kernel version, unattended-upgrade cannot do that, as result we have broken system without nvidia driver ~# apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: linux-modules-nvidia-460-5.4.0-71-generic The following NEW packages will be installed: linux-modules-nvidia-460-5.4.0-72-generic linux-objects-nvidia-460-5.4.0-72-generic linux-signatures-nvidia-5.4.0-72-generic The following packages will be upgraded: libnvidia-cfg1-460 libnvidia-compute-460 libnvidia-compute-460:i386 libnvidia-decode-460 libnvidia-decode-460:i386 libnvidia-encode-460 libnvidia-encode-460:i386 libnvidia-extra-460 libnvidia-fbc1-460 libnvidia-fbc1-460:i386 libnvidia-gl-460 libnvidia-gl-460:i386 libnvidia-ifr1-460 libnvidia-ifr1-460:i386 linux-modules-nvidia-460-generic nvidia-compute-utils-460 nvidia-driver-460 nvidia-kernel-common-460 nvidia-kernel-source-460 nvidia-utils-460 xserver-xorg-video-nvidia-460 21 upgraded, 3 newly installed, 1 to remove and 0 not upgraded. Need to get 199 MB of archives. After this operation, 45.6 MB of additional disk space will be used. Do you want to continue? [Y/n] ~# apt show linux-modules-nvidia-460-5.4.0-71-generic Package: linux-modules-nvidia-460-5.4.0-71-generic Version: 5.4.0-71.79+1 Priority: optional Section: restricted/kernel Source: linux-restricted-modules Origin: Ubuntu Maintainer: Canonical Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 32.8 kB Depends: debconf (>= 0.5) | debconf-2.0, linux-image-5.4.0-71-generic | linux-image-unsigned-5.4.0-71-generic, linux-signatures-nvidia-5.4.0-71-generic (= 5.4.0-71.79+1), linux-objects-nvidia-460-5.4.0-71-generic (= 5.4.0-71.79+1), nvidia-kernel-common-460 (<= 460.56-1), nvidia-kernel-common-460 (>= 460.56) Download-Size: 7136 B APT-Manual-Installed: no APT-Sources: http://archive.pls.pbank.com.ua/ubuntu-current focal-updates/restricted amd64 Packages Description: Linux kernel nvidia modules for version 5.4.0-71 This dependencies should be removed to fix this problem: nvidia-kernel-common-460 (<= 460.56-1), nvidia-kernel-common-460 (>= 460.56) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1926439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926439] [NEW] Dependencies conflicts breaks upgrade process
Public bug reported: Latest updates of linux-restricted-modules breaks upgrade process, updates cannot be installed without removing nvidia modules for previous kernel version, unattended-upgrade cannot do that, as result we have broken system without nvidia driver ~# apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: linux-modules-nvidia-460-5.4.0-71-generic The following NEW packages will be installed: linux-modules-nvidia-460-5.4.0-72-generic linux-objects-nvidia-460-5.4.0-72-generic linux-signatures-nvidia-5.4.0-72-generic The following packages will be upgraded: libnvidia-cfg1-460 libnvidia-compute-460 libnvidia-compute-460:i386 libnvidia-decode-460 libnvidia-decode-460:i386 libnvidia-encode-460 libnvidia-encode-460:i386 libnvidia-extra-460 libnvidia-fbc1-460 libnvidia-fbc1-460:i386 libnvidia-gl-460 libnvidia-gl-460:i386 libnvidia-ifr1-460 libnvidia-ifr1-460:i386 linux-modules-nvidia-460-generic nvidia-compute-utils-460 nvidia-driver-460 nvidia-kernel-common-460 nvidia-kernel-source-460 nvidia-utils-460 xserver-xorg-video-nvidia-460 21 upgraded, 3 newly installed, 1 to remove and 0 not upgraded. Need to get 199 MB of archives. After this operation, 45.6 MB of additional disk space will be used. Do you want to continue? [Y/n] ~# apt show linux-modules-nvidia-460-5.4.0-71-generic Package: linux-modules-nvidia-460-5.4.0-71-generic Version: 5.4.0-71.79+1 Priority: optional Section: restricted/kernel Source: linux-restricted-modules Origin: Ubuntu Maintainer: Canonical Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 32.8 kB Depends: debconf (>= 0.5) | debconf-2.0, linux-image-5.4.0-71-generic | linux-image-unsigned-5.4.0-71-generic, linux-signatures-nvidia-5.4.0-71-generic (= 5.4.0-71.79+1), linux-objects-nvidia-460-5.4.0-71-generic (= 5.4.0-71.79+1), nvidia-kernel-common-460 (<= 460.56-1), nvidia-kernel-common-460 (>= 460.56) Download-Size: 7136 B APT-Manual-Installed: no APT-Sources: http://archive.pls.pbank.com.ua/ubuntu-current focal-updates/restricted amd64 Packages Description: Linux kernel nvidia modules for version 5.4.0-71 This dependencies should be removed to fix this problem: nvidia-kernel-common-460 (<= 460.56-1), nvidia-kernel-common-460 (>= 460.56) ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Tags: focal regression-update ** Attachment added: "Знімок екрану з 2021-04-28 15-44-30.png" https://bugs.launchpad.net/bugs/1926439/+attachment/5493055/+files/%D0%97%D0%BD%D1%96%D0%BC%D0%BE%D0%BA%20%D0%B5%D0%BA%D1%80%D0%B0%D0%BD%D1%83%20%D0%B7%202021-04-28%2015-44-30.png -- 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/1926439 Title: Dependencies conflicts breaks upgrade process Status in linux-restricted-modules package in Ubuntu: New Bug description: Latest updates of linux-restricted-modules breaks upgrade process, updates cannot be installed without removing nvidia modules for previous kernel version, unattended-upgrade cannot do that, as result we have broken system without nvidia driver ~# apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: linux-modules-nvidia-460-5.4.0-71-generic The following NEW packages will be installed: linux-modules-nvidia-460-5.4.0-72-generic linux-objects-nvidia-460-5.4.0-72-generic linux-signatures-nvidia-5.4.0-72-generic The following packages will be upgraded: libnvidia-cfg1-460 libnvidia-compute-460 libnvidia-compute-460:i386 libnvidia-decode-460 libnvidia-decode-460:i386 libnvidia-encode-460 libnvidia-encode-460:i386 libnvidia-extra-460 libnvidia-fbc1-460 libnvidia-fbc1-460:i386 libnvidia-gl-460 libnvidia-gl-460:i386 libnvidia-ifr1-460 libnvidia-ifr1-460:i386 linux-modules-nvidia-460-generic nvidia-compute-utils-460 nvidia-driver-460 nvidia-kernel-common-460 nvidia-kernel-source-460 nvidia-utils-460 xserver-xorg-video-nvidia-460 21 upgraded, 3 newly installed, 1 to remove and 0 not upgraded. Need to get 199 MB of archives. After this operation, 45.6 MB of additional disk space will be used. Do you want to continue? [Y/n] ~# apt show linux-modules-nvidia-460-5.4.0-71-generic Package: linux-modules-nvidia-460-5.4.0-71-generic Version: 5.4.0-71.79+1 Priority: optional Section: restricted/kernel Source: linux-restricted-modules Origin: Ubuntu Maintainer: Canonical Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 32.8 kB Depends: debconf (>= 0.5) | debconf-2.0, linux-image-5.4.0-71-generic | linux-image-unsigned-5.4.0-71-generic, linux-signatures-nvidia-5.4
[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 edit says tried also with same Problem - Kernel 5.3.0-55-generic - Kernel 5.4.0-70-generic - Kernel 5.4.0-71-generic -- 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 1926421] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926421 Title: wifi starts disconnecting randomly; processes hang; machine shutdown takes several minutes with black screen Status in linux package in Ubuntu: Confirmed Bug description: dmesg -l output: Wed Apr 28 14:09:48 2021] pcieport :04:00.0: can't change power state from D3cold to D0 (config space inaccessible ) [Wed Apr 28 14:10:39 2021] xhci_hcd :39:00.0: can't change power state from D3cold to D0 (config space inaccessible ) [Wed Apr 28 14:10:39 2021] xhci_hcd :39:00.0: can't change power state from D3hot to D0 (config space inaccessible) [Wed Apr 28 14:10:39 2021] xhci_hcd :39:00.0: PCI post-resume error -19! [Wed Apr 28 14:10:39 2021] xhci_hcd :39:00.0: HC died; cleaning up [Wed Apr 28 14:10:44 2021] pcieport :04:00.0: can't change power state from D3cold to D0 (config space inaccessible ) [Wed Apr 28 15:09:07 2021] check: Corrupted low memory at 45b936ab (8068 phys) = 1f0 [Wed Apr 28 15:09:07 2021] Memory corruption detected in low memory [Wed Apr 28 15:11:50 2021] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun [Wed Apr 28 15:13:38 2021] ath10k_pci :02:00.0: failed to receive initialized event from target: [Wed Apr 28 15:13:41 2021] ath10k_pci :02:00.0: failed to receive initialized event from target: [Wed Apr 28 15:16:11 2021] INFO: task kworker/2:2:140 blocked for more than 120 seconds. [Wed Apr 28 15:16:11 2021] Tainted: GW 5.8.0-50-generic #56~20.04.1-Ubuntu [Wed Apr 28 15:16:11 2021] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Wed Apr 28 15:16:11 2021] INFO: task wpa_supplicant:1272 blocked for more than 120 seconds. [Wed Apr 28 15:16:11 2021] Tainted: GW 5.8.0-50-generic #56~20.04.1-Ubuntu ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-72-generic 5.4.0-72.80 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shubham1247 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 16:09:02 2021 HibernationDevice: RESUME=UUID=302d1afd-f0c8-4b57-a80c-f5f7b6f6023a InstallationDate: Installed on 2018-11-26 (884 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 27c6:5385 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=UUID=2f792b16-8928-4e91-9c2c-6d520f887ed1 ro quiet splash pcie_aspm=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-72-generic N/A linux-backports-modules-5.4.0-72-generic N/A linux-firmware1.187.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd07/08/2020:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926421] Re: wifi starts disconnecting randomly; processes hang; machine shutdown takes several minutes with black screen
** 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/1926421 Title: wifi starts disconnecting randomly; processes hang; machine shutdown takes several minutes with black screen Status in linux package in Ubuntu: New Bug description: dmesg -l output: Wed Apr 28 14:09:48 2021] pcieport :04:00.0: can't change power state from D3cold to D0 (config space inaccessible ) [Wed Apr 28 14:10:39 2021] xhci_hcd :39:00.0: can't change power state from D3cold to D0 (config space inaccessible ) [Wed Apr 28 14:10:39 2021] xhci_hcd :39:00.0: can't change power state from D3hot to D0 (config space inaccessible) [Wed Apr 28 14:10:39 2021] xhci_hcd :39:00.0: PCI post-resume error -19! [Wed Apr 28 14:10:39 2021] xhci_hcd :39:00.0: HC died; cleaning up [Wed Apr 28 14:10:44 2021] pcieport :04:00.0: can't change power state from D3cold to D0 (config space inaccessible ) [Wed Apr 28 15:09:07 2021] check: Corrupted low memory at 45b936ab (8068 phys) = 1f0 [Wed Apr 28 15:09:07 2021] Memory corruption detected in low memory [Wed Apr 28 15:11:50 2021] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun [Wed Apr 28 15:13:38 2021] ath10k_pci :02:00.0: failed to receive initialized event from target: [Wed Apr 28 15:13:41 2021] ath10k_pci :02:00.0: failed to receive initialized event from target: [Wed Apr 28 15:16:11 2021] INFO: task kworker/2:2:140 blocked for more than 120 seconds. [Wed Apr 28 15:16:11 2021] Tainted: GW 5.8.0-50-generic #56~20.04.1-Ubuntu [Wed Apr 28 15:16:11 2021] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Wed Apr 28 15:16:11 2021] INFO: task wpa_supplicant:1272 blocked for more than 120 seconds. [Wed Apr 28 15:16:11 2021] Tainted: GW 5.8.0-50-generic #56~20.04.1-Ubuntu ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-72-generic 5.4.0-72.80 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shubham1247 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 16:09:02 2021 HibernationDevice: RESUME=UUID=302d1afd-f0c8-4b57-a80c-f5f7b6f6023a InstallationDate: Installed on 2018-11-26 (884 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 27c6:5385 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=UUID=2f792b16-8928-4e91-9c2c-6d520f887ed1 ro quiet splash pcie_aspm=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-72-generic N/A linux-backports-modules-5.4.0-72-generic N/A linux-firmware1.187.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd07/08/2020:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1926081
Title:
nr_writeback memory leak in kernel 4.15.0-137+
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
SRU Justification
[Impact]
Ubuntu 18.04.5 4.15.0 LTS kernels at version 4.15.0-137 and above
contain a memory leak due to the inclusion of patch from the upstream
kernel, but not the fix for that patch which was released later.
Bad patch in bionic:linux 2c17fa778db85644458b52a7df8eacc402cbc1ef mm:
memcontrol: fix excessive complexity in memory.stat reporting
This issue manifests itself as an increasing amount of memory used by
the writeback queue, which never returns to zero. This can been seen
either as the value of `nr_writeback` in /proc/vmstat, or the value of
`Writeback` in /proc/meminfo.
Ordinarily these values should be at or around zero, but on our
servers we observe the `nr_writeback` value increasing to over 8
million, (32GB of memory), at which point it isn't long before the
system IO slows to a crawl (tens of Kb/s). Our servers have 256GB of
memory, and are performing many CI related activities - this issue
appears to be related to concurrent writing to disk, and can be
demonstrated with a simple testcase (see later).
On our heavily used systems this memory leak can result in an unstable
server after 2-3 days, requiring a reboot to fix it.
After much investigation the issue appears to be because the patch
"mm: memcontrol: fix excessive complexity in memory.stat reporting"
was brought in to the 4.15.0-137 Ubuntu kernel (see
https://launchpad.net/ubuntu/+source/linux/4.15.0-137.141) as part of
" Bionic update: upstream stable patchset 2021-01-25 (LP: #1913214)",
however in the mainline kernel there was a follow up patch because
this initial patch introduced concurrency issues. The patch "mm:
memcontrol: fix NR_WRITEBACK leak in memcg and system stats" is
required, and should be brought into the Ubuntu packaged kernel to fix
the issues reported.
The required patch is here:
https://github.com/torvalds/linux/commit/c3cc39118c3610eb6ab4711bc624af7fc48a35fe
and was committed a few weeks after the original (broken) patch:
https://github.com/torvalds/linux/commit/a983b5ebee57209c99f68c8327072f25e0e6e3da
I have checked the release notes for Ubuntu versions -137 to -143, and
none include this second patch that should fix the issue. (I checked
https://people.canonical.com/~kernel/info/kernel-version-map.html for
all the kernel versions, and then visited each changelog page in turn,
e.g. https://launchpad.net/ubuntu/+source/linux/4.15.0-143.147 looking
for "mm: memcontrol: fix NR_WRITEBACK leak in memcg and system
stats").
We do not observe this on the 5.4.0 kernel (supported HWE kernel on
18.05.5), which includes this second patch. That kernel may also
include other patches, so we do not know if any other fixes are also
required, but the one we have linked above seems to definitely be
needed, and seems to match our symptoms.
[Test Plan]
Testcase:
The following is enough to permanently increase the value of
`nr_writeback` on our systems (by about 2000 during most executions):
```
date
grep nr_writeback /proc/vmstat
mkdir -p /docker/testfiles/{1..5}
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/1/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/2/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/3/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/4/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/5/file.% bs=4k count=10 status=none' &
wait $(jobs -p)
grep nr_writeback /proc/vmstat
date
```
Subsequent iterations of the test raise it further, and on a system
doing a lot of writing from a lot of different processes, it can rise
quickly.
System details:
lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Affected kernel: 4.15.0-137 onwards (current latest version tried was
4.15.0-142)
e.g.
apt-cache policy linux-image-4.15.0-141-generic
linux-image-4.15.0-141-generic:
Installed: 4.15.0-141.145
Candidate: 4.15.0-141.145
Version table:
*** 4.15.0-141.145 500
500 http://mirrors.service.networklayer.com/ubuntu
bionic-updates/main amd64 Packag
[Kernel-packages] [Bug 1926421] [NEW] wifi starts disconnecting randomly; processes hang; machine shutdown takes several minutes with black screen
You have been subscribed to a public bug: dmesg -l output: Wed Apr 28 14:09:48 2021] pcieport :04:00.0: can't change power state from D3cold to D0 (config space inaccessible ) [Wed Apr 28 14:10:39 2021] xhci_hcd :39:00.0: can't change power state from D3cold to D0 (config space inaccessible ) [Wed Apr 28 14:10:39 2021] xhci_hcd :39:00.0: can't change power state from D3hot to D0 (config space inaccessible) [Wed Apr 28 14:10:39 2021] xhci_hcd :39:00.0: PCI post-resume error -19! [Wed Apr 28 14:10:39 2021] xhci_hcd :39:00.0: HC died; cleaning up [Wed Apr 28 14:10:44 2021] pcieport :04:00.0: can't change power state from D3cold to D0 (config space inaccessible ) [Wed Apr 28 15:09:07 2021] check: Corrupted low memory at 45b936ab (8068 phys) = 1f0 [Wed Apr 28 15:09:07 2021] Memory corruption detected in low memory [Wed Apr 28 15:11:50 2021] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun [Wed Apr 28 15:13:38 2021] ath10k_pci :02:00.0: failed to receive initialized event from target: [Wed Apr 28 15:13:41 2021] ath10k_pci :02:00.0: failed to receive initialized event from target: [Wed Apr 28 15:16:11 2021] INFO: task kworker/2:2:140 blocked for more than 120 seconds. [Wed Apr 28 15:16:11 2021] Tainted: GW 5.8.0-50-generic #56~20.04.1-Ubuntu [Wed Apr 28 15:16:11 2021] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Wed Apr 28 15:16:11 2021] INFO: task wpa_supplicant:1272 blocked for more than 120 seconds. [Wed Apr 28 15:16:11 2021] Tainted: GW 5.8.0-50-generic #56~20.04.1-Ubuntu ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-72-generic 5.4.0-72.80 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shubham1247 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 16:09:02 2021 HibernationDevice: RESUME=UUID=302d1afd-f0c8-4b57-a80c-f5f7b6f6023a InstallationDate: Installed on 2018-11-26 (884 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 27c6:5385 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=UUID=2f792b16-8928-4e91-9c2c-6d520f887ed1 ro quiet splash pcie_aspm=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-72-generic N/A linux-backports-modules-5.4.0-72-generic N/A linux-firmware1.187.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd07/08/2020:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- wifi starts disconnecting randomly; processes hang; machine shutdown takes several minutes with black screen https://bugs.launchpad.net/bugs/1926421 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 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
Patches sent: https://lists.ubuntu.com/archives/kernel-
team/2021-April/119627.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1926081
Title:
nr_writeback memory leak in kernel 4.15.0-137+
Status in linux package in Ubuntu:
In Progress
Bug description:
SRU Justification
[Impact]
Ubuntu 18.04.5 4.15.0 LTS kernels at version 4.15.0-137 and above
contain a memory leak due to the inclusion of patch from the upstream
kernel, but not the fix for that patch which was released later.
Bad patch in bionic:linux 2c17fa778db85644458b52a7df8eacc402cbc1ef mm:
memcontrol: fix excessive complexity in memory.stat reporting
This issue manifests itself as an increasing amount of memory used by
the writeback queue, which never returns to zero. This can been seen
either as the value of `nr_writeback` in /proc/vmstat, or the value of
`Writeback` in /proc/meminfo.
Ordinarily these values should be at or around zero, but on our
servers we observe the `nr_writeback` value increasing to over 8
million, (32GB of memory), at which point it isn't long before the
system IO slows to a crawl (tens of Kb/s). Our servers have 256GB of
memory, and are performing many CI related activities - this issue
appears to be related to concurrent writing to disk, and can be
demonstrated with a simple testcase (see later).
On our heavily used systems this memory leak can result in an unstable
server after 2-3 days, requiring a reboot to fix it.
After much investigation the issue appears to be because the patch
"mm: memcontrol: fix excessive complexity in memory.stat reporting"
was brought in to the 4.15.0-137 Ubuntu kernel (see
https://launchpad.net/ubuntu/+source/linux/4.15.0-137.141) as part of
" Bionic update: upstream stable patchset 2021-01-25 (LP: #1913214)",
however in the mainline kernel there was a follow up patch because
this initial patch introduced concurrency issues. The patch "mm:
memcontrol: fix NR_WRITEBACK leak in memcg and system stats" is
required, and should be brought into the Ubuntu packaged kernel to fix
the issues reported.
The required patch is here:
https://github.com/torvalds/linux/commit/c3cc39118c3610eb6ab4711bc624af7fc48a35fe
and was committed a few weeks after the original (broken) patch:
https://github.com/torvalds/linux/commit/a983b5ebee57209c99f68c8327072f25e0e6e3da
I have checked the release notes for Ubuntu versions -137 to -143, and
none include this second patch that should fix the issue. (I checked
https://people.canonical.com/~kernel/info/kernel-version-map.html for
all the kernel versions, and then visited each changelog page in turn,
e.g. https://launchpad.net/ubuntu/+source/linux/4.15.0-143.147 looking
for "mm: memcontrol: fix NR_WRITEBACK leak in memcg and system
stats").
We do not observe this on the 5.4.0 kernel (supported HWE kernel on
18.05.5), which includes this second patch. That kernel may also
include other patches, so we do not know if any other fixes are also
required, but the one we have linked above seems to definitely be
needed, and seems to match our symptoms.
[Test Plan]
Testcase:
The following is enough to permanently increase the value of
`nr_writeback` on our systems (by about 2000 during most executions):
```
date
grep nr_writeback /proc/vmstat
mkdir -p /docker/testfiles/{1..5}
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/1/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/2/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/3/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/4/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/5/file.% bs=4k count=10 status=none' &
wait $(jobs -p)
grep nr_writeback /proc/vmstat
date
```
Subsequent iterations of the test raise it further, and on a system
doing a lot of writing from a lot of different processes, it can rise
quickly.
System details:
lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Affected kernel: 4.15.0-137 onwards (current latest version tried was
4.15.0-142)
e.g.
apt-cache policy linux-image-4.15.0-141-generic
linux-image-4.15.0-141-generic:
Installed: 4.15.0-141.145
Candidate: 4.15.0-141.145
Version table:
*** 4.15.0-141.145 500
500 http://mirrors.service.networklayer.com/ubuntu
bionic-updates/main amd64 Packages
500 http://mirrors.service.networklayer.com/ubuntu
bionic-security/main amd64 Packages
100 /var/lib/dpkg/status
According to https://wiki.ubuntu.com/KernelTeam/KernelTeamBug
[Kernel-packages] [Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
** Description changed:
+ SRU Justification
- Ubuntu 18.04.5 4.15.0 LTS kernels at version 4.15.0-137 and above contain a
memory leak due to the inclusion of patch from the upstream kernel, but not the
fix for that patch which was released later.
+ [Impact]
+
+ Ubuntu 18.04.5 4.15.0 LTS kernels at version 4.15.0-137 and above
+ contain a memory leak due to the inclusion of patch from the upstream
+ kernel, but not the fix for that patch which was released later.
+
+ Bad patch in bionic:linux 2c17fa778db85644458b52a7df8eacc402cbc1ef mm:
+ memcontrol: fix excessive complexity in memory.stat reporting
This issue manifests itself as an increasing amount of memory used by
the writeback queue, which never returns to zero. This can been seen
either as the value of `nr_writeback` in /proc/vmstat, or the value of
`Writeback` in /proc/meminfo.
Ordinarily these values should be at or around zero, but on our servers
we observe the `nr_writeback` value increasing to over 8 million, (32GB
of memory), at which point it isn't long before the system IO slows to a
crawl (tens of Kb/s). Our servers have 256GB of memory, and are
performing many CI related activities - this issue appears to be related
to concurrent writing to disk, and can be demonstrated with a simple
testcase (see later).
On our heavily used systems this memory leak can result in an unstable
server after 2-3 days, requiring a reboot to fix it.
After much investigation the issue appears to be because the patch "mm:
memcontrol: fix excessive complexity in memory.stat reporting" was
brought in to the 4.15.0-137 Ubuntu kernel (see
https://launchpad.net/ubuntu/+source/linux/4.15.0-137.141) as part of "
Bionic update: upstream stable patchset 2021-01-25 (LP: #1913214)",
however in the mainline kernel there was a follow up patch because this
initial patch introduced concurrency issues. The patch "mm: memcontrol:
fix NR_WRITEBACK leak in memcg and system stats" is required, and should
be brought into the Ubuntu packaged kernel to fix the issues reported.
The required patch is here:
https://github.com/torvalds/linux/commit/c3cc39118c3610eb6ab4711bc624af7fc48a35fe
and was committed a few weeks after the original (broken) patch:
https://github.com/torvalds/linux/commit/a983b5ebee57209c99f68c8327072f25e0e6e3da
I have checked the release notes for Ubuntu versions -137 to -143, and
none include this second patch that should fix the issue. (I checked
https://people.canonical.com/~kernel/info/kernel-version-map.html for
all the kernel versions, and then visited each changelog page in turn,
e.g. https://launchpad.net/ubuntu/+source/linux/4.15.0-143.147 looking
for "mm: memcontrol: fix NR_WRITEBACK leak in memcg and system stats").
We do not observe this on the 5.4.0 kernel (supported HWE kernel on
18.05.5), which includes this second patch. That kernel may also include
other patches, so we do not know if any other fixes are also required,
but the one we have linked above seems to definitely be needed, and
seems to match our symptoms.
+ [Test Plan]
+
Testcase:
The following is enough to permanently increase the value of
`nr_writeback` on our systems (by about 2000 during most executions):
```
date
grep nr_writeback /proc/vmstat
mkdir -p /docker/testfiles/{1..5}
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/1/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/2/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/3/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/4/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/5/file.% bs=4k count=10 status=none' &
wait $(jobs -p)
grep nr_writeback /proc/vmstat
date
```
Subsequent iterations of the test raise it further, and on a system
doing a lot of writing from a lot of different processes, it can rise
quickly.
System details:
lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Affected kernel: 4.15.0-137 onwards (current latest version tried was
4.15.0-142)
e.g.
apt-cache policy linux-image-4.15.0-141-generic
linux-image-4.15.0-141-generic:
- Installed: 4.15.0-141.145
- Candidate: 4.15.0-141.145
- Version table:
- *** 4.15.0-141.145 500
- 500 http://mirrors.service.networklayer.com/ubuntu
bionic-updates/main amd64 Packages
- 500 http://mirrors.service.networklayer.com/ubuntu
bionic-security/main amd64 Packages
- 100 /var/lib/dpkg/status
+ Installed: 4.15.0-141.145
+ Candidate: 4.15.0-141.145
+ Version table:
+ *** 4.15.0-141.145 500
+ 500 http://mirrors.service.networklayer.com/ubuntu
b
[Kernel-packages] [Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2021-04-28 06:44 EDT--- (In reply to comment #36) > The second attempt seems to have been made without undoing the files and > links created by the old setup. The cases to handle with that mix get rather > hard to handle. So if possible I would rather ask for to check whether the > updated script works in a clean environment forward before marking this as > failed. I'll redo the test with a prestine (despite update to Focal Proposed) system, it should be noted though that at least the initrd.img symlink at the second attempt was created by the normal kernel update. What other links/files should I look into? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd
[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 Same problem for me - Kernel: 5.4.0-72-generic - OS: Ubuntu 20.04.02 LTS focal - BT Speaker: Hama AquaJam -- 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 1926184] Re: locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1926184
Title:
locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
Status in linux package in Ubuntu:
In Progress
Status in linux-aws package in Ubuntu:
In Progress
Status in linux source package in Bionic:
New
Status in linux-aws source package in Bionic:
Fix Committed
Status in linux source package in Focal:
New
Status in linux-aws source package in Focal:
New
Status in linux source package in Groovy:
New
Status in linux-aws source package in Groovy:
New
Status in linux source package in Hirsute:
New
Status in linux-aws source package in Hirsute:
New
Bug description:
[Impact]
* Out of order reads can fetch a NULL pointer causing a kernel crash. Affects
kernels from v4.15 to v5.11.
[Fix]
* commit 84a24bf8c52e ("locking/qrwlock: Fix ordering in
queued_write_lock_slowpath()")
* For Bionic, we also require an additional patch: commit fcfdfe30e324
("locking/barriers: Introduce smp_cond_load_relaxed() and
atomic_cond_read_relaxed()")
[Where problems could occur]
* This is quite a subtle bug. It is more prevalent on arm64. Regression
possibility seems quite low. The worst impact could be a minor performance
degradation.
* Kernels 4.15 / 5.4 / 5.8 / 5.11 were successfully built and booted
with this patch. Also, by using ftrace we could see that the changed
function was executed with success multiple times.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926184/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922754] Re: Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output
The proposed fix is currently 68eb3ae3c63708f823aeeb63bb15197c727bd9bf in linux-next, so Impish would for now be affected as well (even being based on v5.12). ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922754 Title: Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: SRU Justification: Impact: On some setups, while the monitor and the gpu support display modes with pixel clocks of up to 600MHz, the link encoder might not. This prevents YCbCr444 and RGB encoding for 4k60Hz, but YCbCr420 encoding might still be possible. However, which color mode is used is decided before the link encoder capabilities are checked, causing the check to fail and discarding 4k60Hz from the list of possible display modes. Fix: This patch fixes the problem by retrying to find a display mode with YCbCr420 enforced and using it, if it is valid. Testcase: Tested on an Clevo NL50RU. General: Find a PC with a current AMD Radeon GPU, but only a hdmi 1.4 output (e.g. current Clevo laptops with AMD APU's). Connect a 4k@60Hz display supporting YCbCr420 encoding to the hdmi port. Without the patch the maximum that can be set via xrandr is 3840 × 2160 30Hz. With the Patch 3840 × 2160 60Hz can be selected which will use YCbCr420 automatically. Patch already got accepted upstream for linux-next: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=14e4a095b29fd290a9b80f6e553adcfcf01672d1 and applies without modifications to ubuntu-focal/hwe-5.8 Commit-hash: 14e4a095b29fd290a9b80f6e553adcfcf01672d1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 2903 F pulseaudio /dev/snd/controlC0: test 2903 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 20.04 MachineType: TUXEDO TUXEDO Aura 15 Gen1 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=59a028a1-0764-418a-951d-515f1839bd7f ro ignore_loglevel quiet splash i8042.reset i8042.nomux i8042.nopnp i8042.noloop xhci_hcd.quirks=1073741824 vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-48-generic N/A linux-backports-modules-5.8.0-48-generic N/A linux-firmware1.187.9 Tags: focal Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: AURA1501 dmi.board.vendor: TUXEDO Computers dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR2:bd11/13/2020:br7.3:svnTUXEDO:pnTUXEDOAura15Gen1:pvrNotApplicable:rvnTUXEDOComputers:rnAURA1501:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO Aura 15 Gen1 dmi.product.sku: AURA1501 dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
The second attempt seems to have been made without undoing the files and links created by the old setup. The cases to handle with that mix get rather hard to handle. So if possible I would rather ask for to check whether the updated script works in a clean environment forward before marking this as failed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922754] Re: Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output
** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922754 Title: Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: New Status in linux source package in Hirsute: New Bug description: SRU Justification: Impact: On some setups, while the monitor and the gpu support display modes with pixel clocks of up to 600MHz, the link encoder might not. This prevents YCbCr444 and RGB encoding for 4k60Hz, but YCbCr420 encoding might still be possible. However, which color mode is used is decided before the link encoder capabilities are checked, causing the check to fail and discarding 4k60Hz from the list of possible display modes. Fix: This patch fixes the problem by retrying to find a display mode with YCbCr420 enforced and using it, if it is valid. Testcase: Tested on an Clevo NL50RU. General: Find a PC with a current AMD Radeon GPU, but only a hdmi 1.4 output (e.g. current Clevo laptops with AMD APU's). Connect a 4k@60Hz display supporting YCbCr420 encoding to the hdmi port. Without the patch the maximum that can be set via xrandr is 3840 × 2160 30Hz. With the Patch 3840 × 2160 60Hz can be selected which will use YCbCr420 automatically. Patch already got accepted upstream for linux-next: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=14e4a095b29fd290a9b80f6e553adcfcf01672d1 and applies without modifications to ubuntu-focal/hwe-5.8 Commit-hash: 14e4a095b29fd290a9b80f6e553adcfcf01672d1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 2903 F pulseaudio /dev/snd/controlC0: test 2903 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 20.04 MachineType: TUXEDO TUXEDO Aura 15 Gen1 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=59a028a1-0764-418a-951d-515f1839bd7f ro ignore_loglevel quiet splash i8042.reset i8042.nomux i8042.nopnp i8042.noloop xhci_hcd.quirks=1073741824 vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-48-generic N/A linux-backports-modules-5.8.0-48-generic N/A linux-firmware1.187.9 Tags: focal Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: AURA1501 dmi.board.vendor: TUXEDO Computers dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR2:bd11/13/2020:br7.3:svnTUXEDO:pnTUXEDOAura15Gen1:pvrNotApplicable:rvnTUXEDOComputers:rnAURA1501:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO Aura 15 Gen1 dmi.product.sku: AURA1501 dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
** Tags added: verification-failed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926257] Re: Keys not working on laptop
Did you also observe the same issue on Ubuntu 21.04 as well? ** Summary changed: - Keys not working on laptop + Keys not working on Lenovo ideapad 530S -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926257 Title: Keys not working on Lenovo ideapad 530S Status in linux package in Ubuntu: Confirmed Bug description: Some keys are not working in this version ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shivanshu 1994 F pulseaudio /dev/snd/pcmC0D0c: shivanshu 1994 F...m pulseaudio /dev/snd/pcmC0D0p: shivanshu 1994 F...m pulseaudio /dev/snd/controlC1: shivanshu 1994 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 27 12:26:35 2021 InstallationDate: Installed on 2020-06-10 (320 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 0bda:b023 Realtek Semiconductor Corp. RTL8822BE Bluetooth 4.2 Adapter Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81EU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=86104863-1f3c-40e9-9432-c6edade6d000 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.4 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-27 (181 days ago) dmi.bios.date: 11/26/2020 dmi.bios.release: 1.46 dmi.bios.vendor: LENOVO dmi.bios.version: 7PCN46WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14IKB dmi.ec.firmware.release: 1.46 dmi.modalias: dmi:bvnLENOVO:bvr7PCN46WW:bd11/26/2020:br1.46:efr1.46:svnLENOVO:pn81EU:pvrLenovoideapad530S-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14IKB: dmi.product.family: ideapad 530S-14IKB dmi.product.name: 81EU dmi.product.sku: LENOVO_MT_81EU_BU_idea_FM_ideapad 530S-14IKB dmi.product.version: Lenovo ideapad 530S-14IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926257] Re: Keys not working on laptop
Please be more specific what some keys are -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926257 Title: Keys not working on Lenovo ideapad 530S Status in linux package in Ubuntu: Confirmed Bug description: Some keys are not working in this version ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shivanshu 1994 F pulseaudio /dev/snd/pcmC0D0c: shivanshu 1994 F...m pulseaudio /dev/snd/pcmC0D0p: shivanshu 1994 F...m pulseaudio /dev/snd/controlC1: shivanshu 1994 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 27 12:26:35 2021 InstallationDate: Installed on 2020-06-10 (320 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 0bda:b023 Realtek Semiconductor Corp. RTL8822BE Bluetooth 4.2 Adapter Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81EU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=86104863-1f3c-40e9-9432-c6edade6d000 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.4 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-27 (181 days ago) dmi.bios.date: 11/26/2020 dmi.bios.release: 1.46 dmi.bios.vendor: LENOVO dmi.bios.version: 7PCN46WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14IKB dmi.ec.firmware.release: 1.46 dmi.modalias: dmi:bvnLENOVO:bvr7PCN46WW:bd11/26/2020:br1.46:efr1.46:svnLENOVO:pn81EU:pvrLenovoideapad530S-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14IKB: dmi.product.family: ideapad 530S-14IKB dmi.product.name: 81EU dmi.product.sku: LENOVO_MT_81EU_BU_idea_FM_ideapad 530S-14IKB dmi.product.version: Lenovo ideapad 530S-14IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
