[Kernel-packages] [Bug 1835340] Re: [HMEM] kmem: clear poison reported via mce or ACPI patrol scrub notifications
** Description changed: Description: During run-time, the kernel can be notified of new/latent errors in two different ways: If an application trips over a latent/unknown error, and if the system has machine check recovery, then we will be notified via the mce handler, and the app will be killed. In this case, the kernel should take the chance to go clear-errors for that page, and re-online it so it can be used again in the future. If the 'patrol scrubber' discovers an error on a yet-to-be-accessed location, it can send an ACPI notification to the nfit driver. In this case, the kernel should go clear the error if the page is not in use. If it is in use, the application that has it mapped may need to killed as in case 1 above. This additional run-time handling of errors will augment (and be complimentary to) the init-time handling in userspace, and having both will give us the best possible coverage for media errors. - Target Release: 20.10 + Target Release: 21.04 Target Kernel: TBD ** Tags removed: intel-kernel-20.10 ** Tags added: intel-kernel-21.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835340 Title: [HMEM] kmem: clear poison reported via mce or ACPI patrol scrub notifications Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: During run-time, the kernel can be notified of new/latent errors in two different ways: If an application trips over a latent/unknown error, and if the system has machine check recovery, then we will be notified via the mce handler, and the app will be killed. In this case, the kernel should take the chance to go clear-errors for that page, and re-online it so it can be used again in the future. If the 'patrol scrubber' discovers an error on a yet-to-be-accessed location, it can send an ACPI notification to the nfit driver. In this case, the kernel should go clear the error if the page is not in use. If it is in use, the application that has it mapped may need to killed as in case 1 above. This additional run-time handling of errors will augment (and be complimentary to) the init-time handling in userspace, and having both will give us the best possible coverage for media errors. Target Release: 21.04 Target Kernel: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904391] [NEW] Touchpad and Keyboard not detectable in the new kernel
Public bug reported: Hello! I had to abruptly shutdown my pc while update for new groovy was on. Upon rebooting, the touchpad and keyboard is not detectable in the new kernel. They're working fine in older kernel which I had to select in boot options. Please kindly resolve this issue. Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niraj 6806 F pulseaudio /dev/snd/pcmC0D0p: niraj 6806 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 16 14:14:33 2020 InstallationDate: Installed on 2018-09-09 (798 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 005: ID 04ca:3018 Lite-On Technology Corp. Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X556URK ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-28-generic root=UUID=a268e846-0346-4124-855c-4a0a45bd4c8e ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.8.0-28-generic N/A linux-backports-modules-5.8.0-28-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2016 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556URK.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556URK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556URK.302:bd10/24/2016:br5.12:svnASUSTeKCOMPUTERINC.:pnX556URK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556URK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556URK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Summary changed: - Touchpad not detectable in the new kernel + Touchpad and Keyboard not detectable in the new kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904391 Title: Touchpad and Keyboard not detectable in the new kernel Status in linux package in Ubuntu: New Bug description: Hello! I had to abruptly shutdown my pc while update for new groovy was on. Upon rebooting, the touchpad and keyboard is not detectable in the new kernel. They're working fine in older kernel which I had to select in boot options. Please kindly resolve this issue. Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niraj 6806 F pulseaudio /dev/snd/pcmC0D0p: niraj 6806 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 16 14:14:33 2020 InstallationDate: Installed on 2018-09-09 (798 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 005: ID 04ca:3018 Lite-On Technology Corp. Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X556URK ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-28-generic root=UUID=a268e846-0346-4124-855c-4a0a45bd4c8e ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.8.0-28-generic N/A linux-backports-modules-5.8.0-28-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2016 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556URK.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556URK dmi.board.vendor: ASUSTeK COMPUTER INC.
[Kernel-packages] [Bug 1904186] Re: Linux kernel 5.8 is now EOL on kernel.org
Please refer to https://ubuntu.com/about/release-cycle for life cycles of Ubuntu kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904186 Title: Linux kernel 5.8 is now EOL on kernel.org Status in linux package in Ubuntu: Incomplete Bug description: According to kernel.org, the 5.8 branch of the Linux kernel is now End-Of-Life (EOL). This mean it will not be supported as much as the 5.9 branch will. It should be better to switch Groovy and Hisute to 5.9 branch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904186] Re: Linux kernel 5.8 is now EOL on kernel.org
Ubuntu Groovy will support kernel 5.8 for 9 month, and Hisute will move to newer kernel later for certain. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904186 Title: Linux kernel 5.8 is now EOL on kernel.org Status in linux package in Ubuntu: Incomplete Bug description: According to kernel.org, the 5.8 branch of the Linux kernel is now End-Of-Life (EOL). This mean it will not be supported as much as the 5.9 branch will. It should be better to switch Groovy and Hisute to 5.9 branch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903964] Re: The installer encountered an unrecoverable error
*** This bug is a duplicate of bug 1903378 *** https://bugs.launchpad.net/bugs/1903378 ** This bug has been marked a duplicate of bug 1903378 installation failed, but wasn't started (live boot only) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1903964 Title: The installer encountered an unrecoverable error Status in linux-meta package in Ubuntu: New Bug description: Attempting to install Kubuntu Hirsute daily ISO http://cdimage.ubuntu.com/kubuntu/daily-live/20201112/hirsute-desktop-amd64.iso the installer failed with the following error message: The installer encountered an unrecoverable error.A desktop session will now be run so that you may investgate the problem or try installing again. This error occurred immediately after booting and the running of the file checks before entering the installer. The machine invlved were : 1. Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 b/g/N, Bluetooth 4.0, 500 GB hd) This machine was in UEFI+secure boot mode. 2. InWin BL641 i5-10400,32GB,Intel UHD Graphics 630,Ethernet,Intel 660p 512GB M.2 NVMe hd - this install was in a VIrtualBox machine in BIOS mode. Attached is the dmesg log file from the USB media that booted the Dell Inspirion machine (#1 above ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1903964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903596] Re: stack trace in kernel
Thanks for the log! Three more questions here: 1. Does your wifi still working even with this warning message present? 2. Is it easy to reproduce this issue? How to reproduce it? 3. Can you give this x-4.15 kernel a try? https://people.canonical.com/~phlin/kernel/lp-1903596-napi-warnon/X/x-hwe/ Kernel in step 3 contains this commit https://github.com/torvalds/linux/commit/427d5838e99632e9218eae752009c873cade89ac Which is expected to print the warning message in a different format (if the same issue can be triggered again). Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903596 Title: stack trace in kernel Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: This appears to be a problem in the ath10k module. I am not sure what it is exactly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-122-generic 4.15.0-122.124~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.26 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 9 13:35:54 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904391] 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/1904391 Title: Touchpad and Keyboard not detectable in the new kernel Status in linux package in Ubuntu: Confirmed Bug description: Hello! I had to abruptly shutdown my pc while update for new groovy was on. Upon rebooting, the touchpad and keyboard is not detectable in the new kernel. They're working fine in older kernel which I had to select in boot options. Please kindly resolve this issue. Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niraj 6806 F pulseaudio /dev/snd/pcmC0D0p: niraj 6806 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 16 14:14:33 2020 InstallationDate: Installed on 2018-09-09 (798 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 005: ID 04ca:3018 Lite-On Technology Corp. Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X556URK ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-28-generic root=UUID=a268e846-0346-4124-855c-4a0a45bd4c8e ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.8.0-28-generic N/A linux-backports-modules-5.8.0-28-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2016 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556URK.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556URK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556URK.302:bd10/24/2016:br5.12:svnASUSTeKCOMPUTERINC.:pnX556URK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556URK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556URK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904391/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
This bug was fixed in the package zfs-linux - 0.8.4-1ubuntu14
---
zfs-linux (0.8.4-1ubuntu14) hirsute; urgency=medium
[ Didier Roche ]
[ Jean-Baptiste Lallement ]
* Generate clone uuid without dd which is flagged as having an executable
stack. Thanks Usarin Heininga for the patch (LP: #1894329)
-- Jean-Baptiste Lallement Mon,
09 Nov 2020 10:25:57 +0100
** Changed in: zfs-linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
Fix Released
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Triaged
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Triaged
Bug description:
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903770] Re: middle mouse button does not work Logitech M185
haha. nevermind, I think it's the mouse https://cstcnj-blog- blog.tumblr.com/post/83240793790/how-to-fix-logitech-m185-middle-mouse- button ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903770 Title: middle mouse button does not work Logitech M185 Status in linux package in Ubuntu: Invalid Bug description: My mouse works ok with movement, left and right click and scrolling. However, the middle mouse click, ie pressing down on the scroll wheel does not work. I am positive this has worked with previous ubuntu versions with this mouse on this laptop. I'll attach the output from evtest - but I'm not sure how helpful that is, it shows all events that work, but shows nothing when I press the middle button. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 861 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 22:01:13 2020 InstallationDate: Installed on 2020-10-13 (27 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) MachineType: HP HP Pavilion x2 Detachable ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=aad7498f-7086-4036-b6dd-8bceef953d46 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2016 dmi.bios.release: 15.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8181 dmi.board.vendor: HP dmi.board.version: 42.25 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.25 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd03/14/2016:br15.13:efr42.25:svnHP:pnHPPavilionx2Detachable:pvr:rvnHP:rn8181:rvr42.25:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Pavilion x2 Detachable dmi.product.sku: T9R01EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
I have tested the new package on Hirsute. Everything is working now.
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
Fix Released
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Triaged
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Triaged
Bug description:
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904343] Re: WiFi Working, Wired connection not.
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 1904343 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. sounds also more likely a kernel issue than a network manager service one ** Package changed: network-manager (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/1904343 Title: WiFi Working, Wired connection not. Status in linux package in Ubuntu: Incomplete Bug description: Yesterday I wanted to move from Windows 10 to Linux (again) but I had bad luck I guess with the network-manager and its current version. My WiFi is working without any problems but the Ethernet (wired connection) is not working. Tried (installed and fully updated) Pop OS 20.10, Kubuntu 20.10, KDE Neon based on 20.04 same problem on all of them. Not working from Live USB too. Went back to Windows 10 - everything works without any problems. Tried some debugging: taking out the cable and plugging it back. No luck. Restarting the laptop - not working. Laptop model Acer ES1-512 if it matters. acer.com/ac/en/US/content/support-product/5611;-;Aspire%20ES1-512 On network, I have Broadcom and Atheros - not sure which one is for the ethernet. P.S: Whine Kubuntu was loading (the text window) I saw with red Failed - network manager online or something like that, can't really remember the whole thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
Thanks for the confirmation :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
Fix Released
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Triaged
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Triaged
Bug description:
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904343] [NEW] WiFi Working, Wired connection not.
You have been subscribed to a public bug: Yesterday I wanted to move from Windows 10 to Linux (again) but I had bad luck I guess with the network-manager and its current version. My WiFi is working without any problems but the Ethernet (wired connection) is not working. Tried (installed and fully updated) Pop OS 20.10, Kubuntu 20.10, KDE Neon based on 20.04 same problem on all of them. Not working from Live USB too. Went back to Windows 10 - everything works without any problems. Tried some debugging: taking out the cable and plugging it back. No luck. Restarting the laptop - not working. Laptop model Acer ES1-512 if it matters. acer.com/ac/en/US/content/support-product/5611;-;Aspire%20ES1-512 On network, I have Broadcom and Atheros - not sure which one is for the ethernet. P.S: Whine Kubuntu was loading (the text window) I saw with red Failed - network manager online or something like that, can't really remember the whole thing. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: connection ethernet network network-manager wired -- WiFi Working, Wired connection not. https://bugs.launchpad.net/bugs/1904343 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 1891773] Re: kcompactd0 and btrfs-transaction keep deadlocking with each other
I had the problem with Ubuntu 18.04 for months. It didn't occur after that I switched to HWE kernels. No problem since the migration to Ubuntu 20.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891773 Title: kcompactd0 and btrfs-transaction keep deadlocking with each other Status in linux package in Ubuntu: Confirmed Bug description: Example 1: [346911.187920] INFO: task kcompactd0:53 blocked for more than 120 seconds. [346911.187938] Not tainted 4.15.0-112-generic #113-Ubuntu [346911.187951] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [346911.187968] kcompactd0 D053 2 0x8000 [346911.187969] Call Trace: [346911.187973] __schedule+0x24e/0x880 [346911.187986] ? btree_releasepage+0x42/0x50 [btrfs] [346911.187987] schedule+0x2c/0x80 [346911.187988] io_schedule+0x16/0x40 [346911.187989] __lock_page+0xff/0x140 [346911.187990] ? page_cache_tree_insert+0xe0/0xe0 [346911.187992] migrate_pages+0x91f/0xb80 [346911.187993] ? __ClearPageMovable+0x10/0x10 [346911.187994] ? isolate_freepages_block+0x3b0/0x3b0 [346911.187995] compact_zone+0x681/0x950 [346911.187995] kcompactd_do_work+0xfe/0x2a0 [346911.187996] ? __switch_to_asm+0x35/0x70 [346911.187997] ? __switch_to_asm+0x41/0x70 [346911.187998] kcompactd+0x86/0x1c0 [346911.187999] ? kcompactd+0x86/0x1c0 [346911.188001] ? wait_woken+0x80/0x80 [346911.188002] kthread+0x121/0x140 [346911.188003] ? kcompactd_do_work+0x2a0/0x2a0 [346911.188003] ? kthread_create_worker_on_cpu+0x70/0x70 [346911.188004] ret_from_fork+0x35/0x40 [346911.188015] INFO: task btrfs-transacti:858 blocked for more than 120 seconds. [346911.188031] Not tainted 4.15.0-112-generic #113-Ubuntu [346911.188043] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [346911.188060] btrfs-transacti D0 858 2 0x8000 [346911.188061] Call Trace: [346911.188062] __schedule+0x24e/0x880 [346911.188063] ? bit_wait+0x60/0x60 [346911.188063] schedule+0x2c/0x80 [346911.188064] io_schedule+0x16/0x40 [346911.188065] bit_wait_io+0x11/0x60 [346911.188066] __wait_on_bit+0x4c/0x90 [346911.188066] ? bit_wait+0x60/0x60 [346911.188067] out_of_line_wait_on_bit+0x90/0xb0 [346911.188068] ? bit_waitqueue+0x40/0x40 [346911.188080] lock_extent_buffer_for_io+0x100/0x2a0 [btrfs] [346911.188090] btree_write_cache_pages+0x1b8/0x420 [btrfs] [346911.188092] ? native_sched_clock_from_tsc+0x30/0x70 [346911.188092] ? update_load_avg+0x423/0x780 [346911.188101] btree_writepages+0x5d/0x70 [btrfs] [346911.188102] do_writepages+0x4b/0xe0 [346911.188102] ? enqueue_task_fair+0xb6/0x300 [346911.188111] ? merge_state.part.47+0x44/0x130 [btrfs] [346911.188112] __filemap_fdatawrite_range+0xcf/0x100 [346911.188113] ? __filemap_fdatawrite_range+0xcf/0x100 [346911.188114] filemap_fdatawrite_range+0x13/0x20 [346911.188122] btrfs_write_marked_extents+0x68/0x140 [btrfs] [346911.188129] btrfs_write_and_wait_marked_extents.constprop.20+0x4f/0x90 [btrfs] [346911.188136] btrfs_commit_transaction+0x696/0x910 [btrfs] [346911.188143] ? btrfs_commit_transaction+0x696/0x910 [btrfs] [346911.188144] ? wait_woken+0x80/0x80 [346911.188151] transaction_kthread+0x18d/0x1b0 [btrfs] [346911.188152] kthread+0x121/0x140 [346911.188158] ? btrfs_cleanup_transaction+0x570/0x570 [btrfs] [346911.188159] ? kthread_create_worker_on_cpu+0x70/0x70 [346911.188160] ret_from_fork+0x35/0x40 Example 2: 2020-08-11T20:23:03.533+01:00 kernel: INFO: task kcompactd0:53 blocked for more than 120 seconds. 2020-08-11T20:23:03.533+01:00 kernel: Not tainted 4.15.0-112-generic #113-Ubuntu 2020-08-11T20:23:03.533+01:00 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2020-08-11T20:23:03.533+01:00 kernel: kcompactd0 D053 2 0x8000 2020-08-11T20:23:03.533+01:00 kernel: Call Trace: 2020-08-11T20:23:03.533+01:00 kernel: __schedule+0x24e/0x880 2020-08-11T20:23:03.533+01:00 kernel: ? btree_releasepage+0x42/0x50 [btrfs] 2020-08-11T20:23:03.533+01:00 kernel: schedule+0x2c/0x80 2020-08-11T20:23:03.533+01:00 kernel: io_schedule+0x16/0x40 2020-08-11T20:23:03.533+01:00 kernel: __lock_page+0xff/0x140 2020-08-11T20:23:03.533+01:00 kernel: ? page_cache_tree_insert+0xe0/0xe0 2020-08-11T20:23:03.533+01:00 kernel: migrate_pages+0x91f/0xb80 2020-08-11T20:23:03.533+01:00 kernel: ? __ClearPageMovable+0x10/0x10 2020-08-11T20:23:03.533+01:00 kernel: ? isolate_freepages_block+0x3b0/0x3b0 2020-08-11T20:23:03.533+01:00 kernel: compact_zone+0x681/0x950 2020-08-11T20:23:03.533+01:00 kernel: kcompactd_do_work+0xfe/0x2a0 2020-08-11T20:23:03.533+01:00 kernel: ? __switch_to_asm+0x35/0x70
[Kernel-packages] [Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL
The following two commits commit 1b65b23b4398 and 0472b5ea5c97 do not apply
cleanly to:
s390-tools | 2.12.0-0ubuntu3.1
and some of the conflicts don't seem to be obvious to solve.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in s390-tools source package in Focal:
New
Status in linux source package in Groovy:
Fix Committed
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
In Progress
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
arch/s390/kernel/ipl.c and arch/s390/boot/ipl_parm.c).
[Other]
* The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
"s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
proven to work with groovy.
* New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
parameters".
* The entire set of commits/patches is only new for focal.
* The SRU for SRUing "s390/ipl: support NVMe IPL kernel parameters" to
groovy/20.10 was handled by a separate request.
_
SRU Justification: (groovy)
==
[Impact]
* The basics for being able to IPL (boot) from NVMe devices on s390x
were introduced with kernel 5.8.
* This was tested and is proven to work with groovy.
* Now a patch was requested to be added to groovy that introduces
support for NVMe IPL kernel parameters.
[Fix]
* d9f12e48d08ec08ace574050a838e001e442ee38 d9f12e48d08e "s390/ipl:
support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Just check if NVMe kernel parameters can be passed over.
* Due to the lack of hardware this test needs to be done by IBM.
[Regression Potential]
* There is a certain regression risk with this patch, since:
* The
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
We will backport your patch to previous releases soon.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
Fix Released
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Triaged
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Triaged
Bug description:
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904343] 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 1904343 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/1904343 Title: WiFi Working, Wired connection not. Status in linux package in Ubuntu: Incomplete Bug description: Yesterday I wanted to move from Windows 10 to Linux (again) but I had bad luck I guess with the network-manager and its current version. My WiFi is working without any problems but the Ethernet (wired connection) is not working. Tried (installed and fully updated) Pop OS 20.10, Kubuntu 20.10, KDE Neon based on 20.04 same problem on all of them. Not working from Live USB too. Went back to Windows 10 - everything works without any problems. Tried some debugging: taking out the cable and plugging it back. No luck. Restarting the laptop - not working. Laptop model Acer ES1-512 if it matters. acer.com/ac/en/US/content/support-product/5611;-;Aspire%20ES1-512 On network, I have Broadcom and Atheros - not sure which one is for the ethernet. P.S: Whine Kubuntu was loading (the text window) I saw with red Failed - network manager online or something like that, can't really remember the whole thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904294] Re: package linux-firmware 1.157.23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Here are the error messages from the log files: Setting up linux-firmware (1.157.23) ... update-initramfs: Generating /boot/initrd.img-3.13.0-170-generic E: amd64-microcode: unsupported kernel version! E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1. update-initramfs: failed for /boot/initrd.img-3.13.0-170-generic with 1. dpkg: error processing package linux-firmware (--configure): subprocess installed post-installation script returned error exit status 1 The problem isn't with linux-firmware, it happens because the linux- firmware upgrade triggers building a new initrd and scripts installed by some other packages cause that to fail. It's very unusual that you are running a 3.13 kernel with 16.04, and this is not a supported kernel for that release. This could be at least part of the problem, as one of the error messages complains about it being an unsupported kernel version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1904294 Title: package linux-firmware 1.157.23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: I have this update on updating my Ubuntu version from 14.04 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.23 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.27 Architecture: amd64 Date: Sat Nov 14 22:08:05 2020 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2020-08-12 (94 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: linux-firmware Title: package linux-firmware 1.157.23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2020-11-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1904294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894893] Re: [linux-azure][hibernation] GPU device no longer working after resume from hibernation in NV6 VM size
For Groovy, the proposed fix has already been applied to the generic groovy/linux kernel as part of "Groovy update: v5.8.17 upstream stable release" (bug 1902137). Therefore, the patch applied to the linux-azure branch went away during the rebase so it's missing the BugLink to this bug report, due to that this bug will not be closed automatically when the package is released. -- 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/1894893 Title: [linux-azure][hibernation] GPU device no longer working after resume from hibernation in NV6 VM size Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Groovy: Fix Committed Bug description: [Impact] There are failed logs after resume from hibernation in NV6 (GPU passthrough size) VM in Azure: [ 1432.153730] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() failed: 0x5 [ 1432.167910] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() failed: 0x5 This happens to the latest stable release of the linux-azure 5.4.0-1023.23 kernel and the latest mainline linux kernel. [Test Case] How reproducible: 100% Steps to Reproduce: 1. Start a Standard_NV6 VM in Azure and enable hibernation properly (please refer to https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/comments/14 ) E.g. here I create a Generation-1 Ubuntu 20.04 Standard NV6_Promo (6 vcpus, 56 GiB memory) VM in East US 2. 2. Make sure the in-kernel open-source nouveau driver is loaded, or blacklist the nouveau driver and install the official Nvidia GPU driver (please follow https://docs.microsoft.com/en-us/azure/virtual- machines/linux/n-series-driver-setup : "Install GRID drivers on NV or NVv3-series VMs" -- the most important step to run the "./NVIDIA- Linux-x86_64-grid.run".) 3. Run hibernation from serial console # systemctl hibernate 4. After hibernation finishes, start VM and check dmesg # dmesg|grep fail Actual results: [ 1432.153730] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() failed: 0x5 [ 1432.167910] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() failed: 0x5 And /proc/interrupts shows that the GPU interrupts are no longer happening. Expected results: No failed logs, and the GPU interrupt should still happen after hibernation. [Regression Potential] The fix touches the pci-hyperv and can compromise the hyper-v guest drivers. However the change is focuses on the execution path used for hibernation that is still not officially supported. [Other info] BUG FIX: I made a fix here: https://lkml.org/lkml/2020/9/4/1268. Without the patch, we see the error "hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() failed: 0x5" during hibernation when the VM has the Nvidia GPU driver loaded, and after hibernation the GPU driver can no longer receive any MSI/MSI-X interrupts when we check /proc/interrupts. With the patch, we should no longer see the error, and the GPU driver should still receive interrupts after hibernation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1894893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903288] Re: Power guest secure boot with static keys: kernel portion
To confirm, this bug only requires that commit 61f879d97ce4
("powerpc/pseries: Detect secure and trusted boot state of the system.")
lands in hirsute. Is that correct, or are other patches also required?
** Changed in: ubuntu-power-systems
Status: Confirmed => Incomplete
** 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/1903288
Title:
Power guest secure boot with static keys: kernel portion
Status in The Ubuntu-power-systems project:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
== Comment: #2 - Daniel John Axtens - 2020-11-05
20:15:10 ==
This is the kernel side of changes needed for LPAR/guest secure boot.
Because Ubuntu keeps its kernels so wonderfully up to date, I don't
think there are any extra patches you need to pick up. (I'll double-
check against the 21.04 tree once my git pulls finish!)
However, we potentially need some configuration changes to make sure
kexec-ing into a crashdump kernel still works.
Because Lockdown requires that kexec kernels are signed by a key
trusted by IMA, the public key for used for signing the kdump kernel
needs to be in the IMA keyring or the platform keyring. For host
secure boot (and in the UEFI case), it's loaded into the platform
keyring. But in the case of guest secure boot with static keys, it's
not loaded into the platform keyring so it needs to be loaded into the
IMA keyring.
This is easy enough to do. Firstly, load the Secure Boot CA into the
.primary_trusted_keys keyring via the CONFIG_SYSTEM_TRUSTED_KEYS
property. We assume the key used to sign the kernel is signed by this
CA.
Then, enable IMA_LOAD_X509, which allows certificates signed by a key on the
.primary_trusted_keys keyring to be loaded into the IMA keyring. Then set
IMA_X509_PATH to provide a path to the signing key on installed file system.
(It may also be possible to do this step in userspace, so long as the CA is
trusted by the kernel.)
Then that key will be loaded into the .ima keyring at boot and be used to
appraise the kexec kernel for crashdumps.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902093] Re: Introduce the new NVIDIA 455 series
This bug was fixed in the package linux-restricted-modules - 4.15.0-124.127 --- linux-restricted-modules (4.15.0-124.127) bionic; urgency=medium * Master version: 4.15.0-124.127 * Packaging resync (LP: #1786013) - [Packaging] Auto-sync build environment * Introduce the new NVIDIA 455 series (LP: #1902093) - [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package - [Packaging] NVIDIA -- Add the 455 driver * Miscellaneous Ubuntu changes - debian/dkms-versions -- update from master -- Stefan Bader Fri, 06 Nov 2020 11:07:08 +0100 -- 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/1902093 Title: Introduce the new NVIDIA 455 series Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-455 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Released Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Added support for the following GPUs: GeForce RTX 3070 - Added support for using an NVIDIA-driven display as a PRIME Display Offload sink with a PRIME Display Offload source driven by the xf86-video-intel driver. - Fixed a bug in a Vulkan barrier optimization that allowed some back-to-back copies to run unordered. - Fixed a performance regression in the NVIDIA X driver which affected some X11 RENDER extension use cases. - Added AMD Secure Memory Encryption compatibility. * debian/templates/control.in: - Set support level to NFB instead of Beta. - Add support for CUDA 11. Note: this will be the initial release for Bionic and Focal. Changelog entries for the linux-restricted-modules: UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package Make all the NVIDIA drivers, except for 390, provide the nvidia-prebuilt-kernel virtual package. This allows adding a generic dependency on the signed modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904391] Re: Touchpad and Keyboard not detectable in the new kernel
Problem solved! I installed new latest kernel and did a reboot. ** Information type changed from Public to Private Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904391 Title: Touchpad and Keyboard not detectable in the new kernel Status in linux package in Ubuntu: Confirmed Bug description: Hello! I had to abruptly shutdown my pc while update for new groovy was on. Upon rebooting, the touchpad and keyboard is not detectable in the new kernel. They're working fine in older kernel which I had to select in boot options. Please kindly resolve this issue. Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niraj 6806 F pulseaudio /dev/snd/pcmC0D0p: niraj 6806 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 16 14:14:33 2020 InstallationDate: Installed on 2018-09-09 (798 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 005: ID 04ca:3018 Lite-On Technology Corp. Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X556URK ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-28-generic root=UUID=a268e846-0346-4124-855c-4a0a45bd4c8e ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.8.0-28-generic N/A linux-backports-modules-5.8.0-28-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2016 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556URK.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556URK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556URK.302:bd10/24/2016:br5.12:svnASUSTeKCOMPUTERINC.:pnX556URK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556URK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556URK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904391/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902093] Update Released
The verification of the Stable Release Update for nvidia-graphics- drivers-455 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1902093 Title: Introduce the new NVIDIA 455 series Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-455 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Released Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Added support for the following GPUs: GeForce RTX 3070 - Added support for using an NVIDIA-driven display as a PRIME Display Offload sink with a PRIME Display Offload source driven by the xf86-video-intel driver. - Fixed a bug in a Vulkan barrier optimization that allowed some back-to-back copies to run unordered. - Fixed a performance regression in the NVIDIA X driver which affected some X11 RENDER extension use cases. - Added AMD Secure Memory Encryption compatibility. * debian/templates/control.in: - Set support level to NFB instead of Beta. - Add support for CUDA 11. Note: this will be the initial release for Bionic and Focal. Changelog entries for the linux-restricted-modules: UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package Make all the NVIDIA drivers, except for 390, provide the nvidia-prebuilt-kernel virtual package. This allows adding a generic dependency on the signed modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902093] Re: Introduce the new NVIDIA 455 series
This bug was fixed in the package linux - 4.15.0-124.127 --- linux (4.15.0-124.127) bionic; urgency=medium * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the new NVIDIA 455 series (LP: #1902093) - [Packaging] NVIDIA -- Add the NVIDIA 455 driver -- Stefan Bader Thu, 05 Nov 2020 18:43:42 +0100 ** Changed in: nvidia-graphics-drivers-455 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1902093 Title: Introduce the new NVIDIA 455 series Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-455 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Released Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Added support for the following GPUs: GeForce RTX 3070 - Added support for using an NVIDIA-driven display as a PRIME Display Offload sink with a PRIME Display Offload source driven by the xf86-video-intel driver. - Fixed a bug in a Vulkan barrier optimization that allowed some back-to-back copies to run unordered. - Fixed a performance regression in the NVIDIA X driver which affected some X11 RENDER extension use cases. - Added AMD Secure Memory Encryption compatibility. * debian/templates/control.in: - Set support level to NFB instead of Beta. - Add support for CUDA 11. Note: this will be the initial release for Bionic and Focal. Changelog entries for the linux-restricted-modules: UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package Make all the NVIDIA drivers, except for 390, provide the nvidia-prebuilt-kernel virtual package. This allows adding a generic dependency on the signed modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902093] Re: Introduce the new NVIDIA 455 series
This bug was fixed in the package linux-restricted-modules - 5.4.0-54.60 --- linux-restricted-modules (5.4.0-54.60) focal; urgency=medium * Master version: 5.4.0-54.60 * Introduce the new NVIDIA 455 series (LP: #1902093) - [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package - [Packaging] NVIDIA -- Add the 455 driver * Miscellaneous Ubuntu changes - debian/dkms-versions -- update from master -- Stefan Bader Thu, 05 Nov 2020 19:01:15 +0100 ** Changed in: nvidia-graphics-drivers-455 (Ubuntu Groovy) Status: Fix Committed => Fix Released -- 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/1902093 Title: Introduce the new NVIDIA 455 series Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-455 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Released Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Added support for the following GPUs: GeForce RTX 3070 - Added support for using an NVIDIA-driven display as a PRIME Display Offload sink with a PRIME Display Offload source driven by the xf86-video-intel driver. - Fixed a bug in a Vulkan barrier optimization that allowed some back-to-back copies to run unordered. - Fixed a performance regression in the NVIDIA X driver which affected some X11 RENDER extension use cases. - Added AMD Secure Memory Encryption compatibility. * debian/templates/control.in: - Set support level to NFB instead of Beta. - Add support for CUDA 11. Note: this will be the initial release for Bionic and Focal. Changelog entries for the linux-restricted-modules: UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package Make all the NVIDIA drivers, except for 390, provide the nvidia-prebuilt-kernel virtual package. This allows adding a generic dependency on the signed modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902093] Re: Introduce the new NVIDIA 455 series
This bug was fixed in the package linux-restricted-modules - 5.8.0-29.31 --- linux-restricted-modules (5.8.0-29.31) groovy; urgency=medium * Master version: 5.8.0-29.31 * Introduce the new NVIDIA 455 series (LP: #1902093) - [Packaging] Migrate nvidia-435 users to updated nvidia-455 - [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package * Miscellaneous Ubuntu changes - debian/dkms-versions -- update from master -- Stefan Bader Fri, 06 Nov 2020 12:54:17 +0100 ** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1902093 Title: Introduce the new NVIDIA 455 series Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-455 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Released Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Added support for the following GPUs: GeForce RTX 3070 - Added support for using an NVIDIA-driven display as a PRIME Display Offload sink with a PRIME Display Offload source driven by the xf86-video-intel driver. - Fixed a bug in a Vulkan barrier optimization that allowed some back-to-back copies to run unordered. - Fixed a performance regression in the NVIDIA X driver which affected some X11 RENDER extension use cases. - Added AMD Secure Memory Encryption compatibility. * debian/templates/control.in: - Set support level to NFB instead of Beta. - Add support for CUDA 11. Note: this will be the initial release for Bionic and Focal. Changelog entries for the linux-restricted-modules: UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package Make all the NVIDIA drivers, except for 390, provide the nvidia-prebuilt-kernel virtual package. This allows adding a generic dependency on the signed modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902093] Re: Introduce the new NVIDIA 455 series
This bug was fixed in the package nvidia-graphics-drivers-455 - 455.38-0ubuntu0.20.04.1 --- nvidia-graphics-drivers-455 (455.38-0ubuntu0.20.04.1) focal; urgency=medium * Initial release (LP: #1902093). Replaces the 435 series. -- Alberto Milone Thu, 29 Oct 2020 17:01:27 +0100 ** Changed in: linux-restricted-modules (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1902093 Title: Introduce the new NVIDIA 455 series Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-455 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Released Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Added support for the following GPUs: GeForce RTX 3070 - Added support for using an NVIDIA-driven display as a PRIME Display Offload sink with a PRIME Display Offload source driven by the xf86-video-intel driver. - Fixed a bug in a Vulkan barrier optimization that allowed some back-to-back copies to run unordered. - Fixed a performance regression in the NVIDIA X driver which affected some X11 RENDER extension use cases. - Added AMD Secure Memory Encryption compatibility. * debian/templates/control.in: - Set support level to NFB instead of Beta. - Add support for CUDA 11. Note: this will be the initial release for Bionic and Focal. Changelog entries for the linux-restricted-modules: UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package Make all the NVIDIA drivers, except for 390, provide the nvidia-prebuilt-kernel virtual package. This allows adding a generic dependency on the signed modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902093] Re: Introduce the new NVIDIA 455 series
This bug was fixed in the package nvidia-graphics-drivers-455 - 455.38-0ubuntu0.20.10.1 --- nvidia-graphics-drivers-455 (455.38-0ubuntu0.20.10.1) groovy; urgency=medium * New upstream release (LP: #1902093): - Added support for the following GPUs: GeForce RTX 3070 - Added support for using an NVIDIA-driven display as a PRIME Display Offload sink with a PRIME Display Offload source driven by the xf86-video-intel driver. - Fixed a bug in a Vulkan barrier optimization that allowed some back-to-back copies to run unordered. - Fixed a performance regression in the NVIDIA X driver which affected some X11 RENDER extension use cases. - Added AMD Secure Memory Encryption compatibility. * debian/templates/control.in: - Set support level to NFB instead of Beta. - Add support for CUDA 11. - Add transitional packages for the 435 series. -- Alberto Milone Thu, 29 Oct 2020 16:31:36 +0100 ** Changed in: nvidia-graphics-drivers-455 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1902093 Title: Introduce the new NVIDIA 455 series Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-455 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Released Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Added support for the following GPUs: GeForce RTX 3070 - Added support for using an NVIDIA-driven display as a PRIME Display Offload sink with a PRIME Display Offload source driven by the xf86-video-intel driver. - Fixed a bug in a Vulkan barrier optimization that allowed some back-to-back copies to run unordered. - Fixed a performance regression in the NVIDIA X driver which affected some X11 RENDER extension use cases. - Added AMD Secure Memory Encryption compatibility. * debian/templates/control.in: - Set support level to NFB instead of Beta. - Add support for CUDA 11. Note: this will be the initial release for Bionic and Focal. Changelog entries for the linux-restricted-modules: UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package Make all the NVIDIA drivers, except for 390, provide the nvidia-prebuilt-kernel virtual package. This allows adding a generic dependency on the signed modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902093] Re: Introduce the new NVIDIA 455 series
This bug was fixed in the package nvidia-graphics-drivers-455 - 455.38-0ubuntu0.18.04.1 --- nvidia-graphics-drivers-455 (455.38-0ubuntu0.18.04.1) bionic; urgency=medium * Initial release (LP: #1902093). Replaces the 435 series. -- Alberto Milone Thu, 29 Oct 2020 17:07:19 +0100 ** Changed in: linux-restricted-modules (Ubuntu Groovy) Status: Fix Committed => Fix Released -- 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/1902093 Title: Introduce the new NVIDIA 455 series Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-455 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Released Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Added support for the following GPUs: GeForce RTX 3070 - Added support for using an NVIDIA-driven display as a PRIME Display Offload sink with a PRIME Display Offload source driven by the xf86-video-intel driver. - Fixed a bug in a Vulkan barrier optimization that allowed some back-to-back copies to run unordered. - Fixed a performance regression in the NVIDIA X driver which affected some X11 RENDER extension use cases. - Added AMD Secure Memory Encryption compatibility. * debian/templates/control.in: - Set support level to NFB instead of Beta. - Add support for CUDA 11. Note: this will be the initial release for Bionic and Focal. Changelog entries for the linux-restricted-modules: UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package Make all the NVIDIA drivers, except for 390, provide the nvidia-prebuilt-kernel virtual package. This allows adding a generic dependency on the signed modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902093] Re: Introduce the new NVIDIA 455 series
This bug was fixed in the package linux - 5.4.0-54.60 --- linux (5.4.0-54.60) focal; urgency=medium * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the new NVIDIA 455 series (LP: #1902093) - [Packaging] NVIDIA -- Add the NVIDIA 455 driver -- Stefan Bader Thu, 05 Nov 2020 18:03:49 +0100 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: linux-restricted-modules (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1902093 Title: Introduce the new NVIDIA 455 series Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-455 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Released Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Added support for the following GPUs: GeForce RTX 3070 - Added support for using an NVIDIA-driven display as a PRIME Display Offload sink with a PRIME Display Offload source driven by the xf86-video-intel driver. - Fixed a bug in a Vulkan barrier optimization that allowed some back-to-back copies to run unordered. - Fixed a performance regression in the NVIDIA X driver which affected some X11 RENDER extension use cases. - Added AMD Secure Memory Encryption compatibility. * debian/templates/control.in: - Set support level to NFB instead of Beta. - Add support for CUDA 11. Note: this will be the initial release for Bionic and Focal. Changelog entries for the linux-restricted-modules: UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package Make all the NVIDIA drivers, except for 390, provide the nvidia-prebuilt-kernel virtual package. This allows adding a generic dependency on the signed modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900809] Re: [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to v1.6
This update would also fix at least bug #1881505. Basically, my audio on Lenovo T14 was working very unreliably and jammed with a DSP panic quite often with the 1.4.2 version, but seems to work just fine with 1.6. It would be great to get this update included soon, since it's very inconvenient to reboot the laptop about 1-2 times a day, because that seems to be the only way to get audio working after the DSP paic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1900809 Title: [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to v1.6 Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Focal: Triaged Status in linux-firmware source package in Groovy: Triaged Bug description: BugLink: https://bugs.launchpad.net/bugs/1900809 [Impact] Intel released the sof-firmware v1.6, and in our oem projects, the Dell TGL machines and the machines with soundwire audio need the new firmware, otherwise they will fail to load the firmware or the audio can't work well. [Fix] replace the old sof-firmware-v1.4.2 with sof-firmware-v1.6 [Test] Tested on the Dell cml/tgl soundwire machines, all audio functions worked well, and those audio functions didn't work with old firmware. Tested on Lenovo dimc machines, all audio functions worked as well as before. [Regression Potential] Intel tested the new firmware with the 5.8 and 5.9 kernel, but we need the new firmware to work with 5.4 and 5.6 kernel as well, so there is some possibility that the 5.4/5.6 kernel can't work well with the new sof-firmware. I have tested the new firmware with 5.4/5.6 kernel on some Lenovo machines, so far no issues were found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1900809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902179] Comment bridged from LTC Bugzilla
--- Comment From jan.hoepp...@de.ibm.com 2020-11-16 11:16 EDT---
Canonical,
are there public s390-tools repositories with the Ubuntu versions available
that we can mirror internally and which we could then use for potential
backport work (such as this feature seems to require)?
Please let me know so that we can provide you with backport patches
that apply cleanly on your version of s390-tools (v2.12.0).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in s390-tools source package in Focal:
New
Status in linux source package in Groovy:
Fix Committed
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
In Progress
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
arch/s390/kernel/ipl.c and arch/s390/boot/ipl_parm.c).
[Other]
* The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
"s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
proven to work with groovy.
* New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
parameters".
* The entire set of commits/patches is only new for focal.
* The SRU for SRUing "s390/ipl: support NVMe IPL kernel parameters" to
groovy/20.10 was handled by a separate request.
_
SRU Justification: (groovy)
==
[Impact]
* The basics for being able to IPL (boot) from NVMe devices on s390x
were introduced with kernel 5.8.
* This was tested and is proven to work with groovy.
* Now a patch was requested to be added to groovy that introduces
support for NVMe IPL kernel parameters.
[Fix]
* d9f12e48d08ec08ace574050a838e001e442ee38 d9f12e48d08e "s390/ipl:
support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to
[Kernel-packages] [Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL
Hi Jan, yes (almost) all Ubuntu packages are hosted nowadays at our Launchpad
git (at least all packages in main, incl. s390-tools).
Please see: https://code.launchpad.net/ubuntu/+source/s390-tools
If you are logged in with a Launchpad account, you will directly see at the top
a comd-line that allows to clone the package sources, like:
" Get this repository:
git clone https://git.launchpad.net/ubuntu/+source/s390-tools "
If not logged in you'll see a more generic page, but again listing the URLs
that can be used for cloning, here:
git://git.launchpad.net/ubuntu/+source/s390-tools
git+ssh://git.launchpad.net/ubuntu/+source/s390-tools
https://git.launchpad.net/ubuntu/+source/s390-tools
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in s390-tools source package in Focal:
New
Status in linux source package in Groovy:
Fix Committed
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
In Progress
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
arch/s390/kernel/ipl.c and arch/s390/boot/ipl_parm.c).
[Other]
* The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
"s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
proven to work with groovy.
* New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
parameters".
* The entire set of commits/patches is only new for focal.
* The SRU for SRUing "s390/ipl: support NVMe IPL kernel parameters" to
groovy/20.10 was handled by a separate request.
_
SRU Justification: (groovy)
==
[Impact]
* The basics for being able to IPL (boot) from NVMe devices on s390x
were introduced with kernel 5.8.
* This was tested and is proven to work with groovy.
* Now a patch was requested to be added
[Kernel-packages] [Bug 1904445] [NEW] Focal update: v5.4.74 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.74 upstream stable release from git://git.kernel.org/ netfilter: nftables_offload: KASAN slab-out-of-bounds Read in nft_flow_rule_create socket: don't clear SOCK_TSTAMP_NEW when SO_TIMESTAMPNS is disabled objtool: Support Clang non-section symbols in ORC generation scripts/setlocalversion: make git describe output more reliable arm64: Run ARCH_WORKAROUND_1 enabling code on all CPUs arm64: Run ARCH_WORKAROUND_2 enabling code on all CPUs arm64: link with -z norelro regardless of CONFIG_RELOCATABLE x86/PCI: Fix intel_mid_pci.c build error when ACPI is not enabled bnxt_en: Check abort error state in bnxt_open_nic(). bnxt_en: Send HWRM_FUNC_RESET fw command unconditionally. chelsio/chtls: fix deadlock issue chelsio/chtls: fix memory leaks in CPL handlers chelsio/chtls: fix tls record info to user cxgb4: set up filter action after rewrites gtp: fix an use-before-init in gtp_newlink() ibmvnic: fix ibmvnic_set_mac mlxsw: core: Fix memory leak on module removal netem: fix zero division in tabledist net/sched: act_mpls: Add softdep on mpls_gso.ko r8169: fix issue with forced threading in combination with shared interrupts ravb: Fix bit fields checking in ravb_hwtstamp_get() tcp: Prevent low rmem stalls with SO_RCVLOWAT. tipc: fix memory leak caused by tipc_buf_append() net: hns3: Clear the CMDQ registers before unmapping BAR region bnxt_en: Re-write PCI BARs after PCI fatal error. bnxt_en: Fix regression in workqueue cleanup logic in bnxt_remove_one(). bnxt_en: Invoke cancel_delayed_work_sync() for PFs also. erofs: avoid duplicated permission check for "trusted." xattrs arch/x86/amd/ibs: Fix re-arming IBS Fetch x86/xen: disable Firmware First mode for correctable memory errors ata: ahci: mvebu: Make SATA PHY optional for Armada 3720 fuse: fix page dereference after free bpf: Fix comment for helper bpf_current_task_under_cgroup() evm: Check size of security.evm before using it p54: avoid accessing the data mapped to streaming DMA cxl: Rework error message for incompatible slots RDMA/addr: Fix race with netevent_callback()/rdma_addr_cancel() mtd: lpddr: Fix bad logic in print_drs_error serial: qcom_geni_serial: To correct QUP Version detection logic serial: pl011: Fix lockdep splat when handling magic-sysrq interrupt PM: runtime: Fix timer_expires data type on 32-bit arches ata: sata_rcar: Fix DMA boundary mask xen/gntdev.c: Mark pages as dirty crypto: x86/crc32c - fix building with clang ias openrisc: Fix issue with get_user for 64-bit values misc: rtsx: do not setting OC_POWER_DOWN reg in rtsx_pci_init_ocp() phy: marvell: comphy: Convert internal SMCC firmware return codes to errno Linux 5.4.74 UBUNTU: upstream stable to v5.4.74 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided 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) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** 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.74 upstream stable release + from git://git.kernel.org/ -v5.4.74 upstream stable release -from git://git.kernel.org/ + netfilter: nftables_offload: KASAN slab-out-of-bounds Read in nft_flow_rule_create + socket: don't clear
[Kernel-packages] [Bug 1904430] [NEW] Fix AMD GFX where no HDMI audio when hotplugging different monitors
Public bug reported: [Impact] Hotplugging different monitors on different ports makes HDMI audio disappears. [Fix] Make sure new EDID is added. [Test case] Boot up with a HDMI monitor with audio output, unplug the monitor and plug another monitor without speaker and without audio jack. Then plug back the original monitor. With the patch applied, there's still HDMI audio output from the original monitor. [Where problems could occur] If the EDID is valid, the driver does the correct thing. If the EDID is invalid, then the driver spends a bit more time setting up EDID, without doing any harm. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Tags: oem-priority originate-from-1896207 sutton ** Package changed: linux (Ubuntu) => linux-oem-5.6 (Ubuntu) ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided => Medium ** Tags added: oem-priority originate-from-1896207 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904430 Title: Fix AMD GFX where no HDMI audio when hotplugging different monitors Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: Confirmed Bug description: [Impact] Hotplugging different monitors on different ports makes HDMI audio disappears. [Fix] Make sure new EDID is added. [Test case] Boot up with a HDMI monitor with audio output, unplug the monitor and plug another monitor without speaker and without audio jack. Then plug back the original monitor. With the patch applied, there's still HDMI audio output from the original monitor. [Where problems could occur] If the EDID is valid, the driver does the correct thing. If the EDID is invalid, then the driver spends a bit more time setting up EDID, without doing any harm. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1904430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847628] Re: When using swap in ZFS, system stops when you start using swap
Is there any hope that a swap on zvol with sync=standard at least doesn't hang/deadlock? Like: zfs create rpool/swap -V 2G -b $(getconf PAGESIZE) -o logbias=throughput -o sync=always -o primarycache=metadata -o secondarycache=none In my testing this didn't hang when swap got hit. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1847628 Title: When using swap in ZFS, system stops when you start using swap Status in Release Notes for Ubuntu: Fix Released Status in Native ZFS for Linux: New Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Won't Fix Bug description: # Problem When using swap in ZFS, system stops when you start using swap. > stress --vm 100 if you doing swapoff will only occur OOM and the system will not stop. # Environment jehos@MacBuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan jehos@MacBuntu:~$ dpkg -l | grep zfs ii libzfs2linux 0.8.1-1ubuntu13 amd64OpenZFS filesystem library for Linux ii zfs-initramfs 0.8.1-1ubuntu13 amd64OpenZFS root filesystem capabilities for Linux - initramfs ii zfs-zed0.8.1-1ubuntu13 amd64OpenZFS Event Daemon ii zfsutils-linux 0.8.1-1ubuntu13 amd64command-line tools to manage OpenZFS filesystems jehos@MacBuntu:~$ uname -a Linux MacBuntu 5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux jehos@MacBuntu:~$ zpool list NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT bpool 1.88G 66.1M 1.81G- - - 3% 1.00xONLINE - rpool 230G 124G 106G- - 9%53% 1.00xONLINE - jehos@MacBuntu:~$ zfs get all rpool/swap NAMEPROPERTY VALUESOURCE rpool/swap type volume - rpool/swap creation 목 10월 10 15:56 2019 - rpool/swap used 2.13G- rpool/swap available 98.9G- rpool/swap referenced72K - rpool/swap compressratio 1.11x- rpool/swap reservation none default rpool/swap volsize 2G local rpool/swap volblocksize 4K - rpool/swap checksum on default rpool/swap compression zle local rpool/swap readonly off default rpool/swap createtxg 34 - rpool/swap copies1default rpool/swap refreservation2.13Glocal rpool/swap guid 18209330213704683244 - rpool/swap primarycache metadata local rpool/swap secondarycachenone local rpool/swap usedbysnapshots 0B - rpool/swap usedbydataset 72K - rpool/swap usedbychildren0B - rpool/swap usedbyrefreservation 2.13G- rpool/swap logbias throughput local rpool/swap objsetid 393 - rpool/swap dedup off default rpool/swap mlslabel none default rpool/swap sync always local rpool/swap refcompressratio 1.11x- rpool/swap written 72K - rpool/swap logicalused 40K - rpool/swap logicalreferenced 40K - rpool/swap volmode default default rpool/swap snapshot_limitnone default rpool/swap snapshot_countnone default rpool/swap snapdev hidden default rpool/swap context none default rpool/swap fscontext none default rpool/swap defcontextnone default rpool/swap rootcontext none default rpool/swap redundant_metadataall default rpool/swap encryptionoff default rpool/swap keylocation
[Kernel-packages] [Bug 1858463] Re: Desktop freezing while SSD under heavy load
What can it be, then? What should I test, to find out? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858463 Title: Desktop freezing while SSD under heavy load Status in linux package in Ubuntu: Incomplete Bug description: Every time my SSD is under heavy writing load (e.g. copying large files from a USB stick, or downloading an ISO from a fast website), the entire Ubuntu (Gnome) desktop, including mouse pointer, freezes. My computer is an Asus UX410UAK with a Micron 1100 SSD. guillaume@massada:~$ sudo dmidecode | grep -i UX Version: UX410UAK.308 Product Name: UX410UAK Family: UX Product Name: UX410UAK guillaume@massada:~$ cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: Micron_1100_MTFD Rev: A020 Type: Direct-AccessANSI SCSI revision: 05 This is a recurring problem, and has always been with this machine (including previous kernel and Ubuntu versions, at least for the past 2 years). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 6 18:20:01 2020 InstallationDate: Installed on 2018-07-28 (526 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1685 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam 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: ASUSTeK COMPUTER INC. UX410UAK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 Tags: focal wayland-session Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1423 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (208 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam 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: ASUSTeK COMPUTER INC. UX410UAK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=
[Kernel-packages] [Bug 1904484] Re: iMac with AMD Radeon Mobility GPU Suffers from Pink Screen Artefacts Following Waking from Suspension
** Description changed: - The bug is in the text file uploaded. Thank you so much for your - help + The bug is in the text file uploaded titled Launchpad.txt. Thank you so + much for your help ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ali 781 F pulseaudio - ali 808 F pipewire-media- - /dev/snd/seq:ali 780 F pipewire + USERPID ACCESS COMMAND + /dev/snd/controlC0: ali 781 F pulseaudio + ali 808 F pipewire-media- + /dev/snd/seq:ali 780 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 16 20:13:25 2020 InstallationDate: Installed on 2020-11-16 (0 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Apple Inc. iMac8,1 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=a5cc462d-49e8-4b4a-92af-d249eefa326a ro noapic noacpi nosplash irqpoll RelatedPackageVersions: - linux-restricted-modules-5.8.0-29-generic N/A - linux-backports-modules-5.8.0-29-generic N/A - linux-firmware1.190 + linux-restricted-modules-5.8.0-29-generic N/A + linux-backports-modules-5.8.0-29-generic N/A + linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/08 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM81.88Z.00C1.B00.0802091538 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F226BEC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F226BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrIM81.88Z.00C1.B00.0802091538:bd02/09/08:br0.1:svnAppleInc.:pniMac8,1:pvr1.0:rvnAppleInc.:rnMac-F226BEC8:rvrPVT:cvnAppleInc.:ct13:cvrMac-F226BEC8: dmi.product.family: Mac dmi.product.name: iMac8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904484 Title: iMac with AMD Radeon Mobility GPU Suffers from Pink Screen Artefacts Following Waking from Suspension Status in linux package in Ubuntu: New Bug description: The bug is in the text file uploaded titled Launchpad.txt. Thank you so much for your help ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ali 781 F pulseaudio ali 808 F pipewire-media- /dev/snd/seq:ali 780 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 16 20:13:25 2020 InstallationDate: Installed on 2020-11-16 (0 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Apple Inc. iMac8,1 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=a5cc462d-49e8-4b4a-92af-d249eefa326a ro noapic noacpi nosplash irqpoll RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/08 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM81.88Z.00C1.B00.0802091538 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F226BEC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F226BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrIM81.88Z.00C1.B00.0802091538:bd02/09/08:br0.1:svnAppleInc.:pniMac8,1:pvr1.0:rvnAppleInc.:rnMac-F226BEC8:rvrPVT:cvnAppleInc.:ct13:cvrMac-F226BEC8: dmi.product.family: Mac dmi.product.name: iMac8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904484/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1904463] [NEW] [linux-azure] Fix hibernation in case interrupts are not re-created
Public bug reported: Microsoft would like to request the following commit in all supported releases that run on Azure: 915cff7f38c5 (“PCI: hv: Fix hibernation in case interrupts are not re-created”) Commit details: pci_restore_msi_state() directly writes the MSI/MSI-X related registers via MMIO. On a physical machine, this works perfectly; for a Linux VM running on a hypervisor, which typically enables IOMMU interrupt remapping, the hypervisor usually should trap and emulate the MMIO accesses in order to re-create the necessary interrupt remapping table entries in the IOMMU, otherwise the interrupts can not work in the VM after hibernation. Hyper-V is different from other hypervisors in that it does not trap and emulate the MMIO accesses, and instead it uses a para-virtualized method, which requires the VM to call hv_compose_msi_msg() to notify the hypervisor of the info that would be passed to the hypervisor in the case of the trap-and-emulate method. This is not an issue to a lot of PCI device drivers, which destroy and re-create the interrupts across hibernation, so hv_compose_msi_msg() is called automatically. However, some PCI device drivers (e.g. the in-tree GPU driver nouveau and the out-of-tree Nvidia proprietary GPU driver) do not destroy and re-create MSI/MSI-X interrupts across hibernation, so hv_pci_resume() has to call hv_compose_msi_msg(), otherwise the PCI device drivers can no longer receive interrupts after the VM resumes from hibernation. Hyper-V is also different in that chip->irq_unmask() may fail in a Linux VM running on Hyper-V (on a physical machine, chip->irq_unmask() can not fail because unmasking an MSI/MSI-X register just means an MMIO write): during hibernation, when a CPU is offlined, the kernel tries to move the interrupt to the remaining CPUs that haven't been offlined yet. In this case, hv_irq_unmask() -> hv_do_hypercall() always fails because the vmbus channel has been closed: here the early "return" in hv_irq_unmask() means the pci_msi_unmask_irq() is not called, i.e. the desc->masked remains "true", so later after hibernation, the MSI interrupt always remains masked, which is incorrect. Refer to cpu_disable_common() -> fixup_irqs() -> irq_migrate_all_off_this_cpu() -> migrate_one_irq(): ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Fix hibernation in case interrupts are not re-created + [linux-azure] Fix hibernation in case interrupts are not re-created -- 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/1904463 Title: [linux-azure] Fix hibernation in case interrupts are not re-created Status in linux-azure package in Ubuntu: New Bug description: Microsoft would like to request the following commit in all supported releases that run on Azure: 915cff7f38c5 (“PCI: hv: Fix hibernation in case interrupts are not re-created”) Commit details: pci_restore_msi_state() directly writes the MSI/MSI-X related registers via MMIO. On a physical machine, this works perfectly; for a Linux VM running on a hypervisor, which typically enables IOMMU interrupt remapping, the hypervisor usually should trap and emulate the MMIO accesses in order to re-create the necessary interrupt remapping table entries in the IOMMU, otherwise the interrupts can not work in the VM after hibernation. Hyper-V is different from other hypervisors in that it does not trap and emulate the MMIO accesses, and instead it uses a para-virtualized method, which requires the VM to call hv_compose_msi_msg() to notify the hypervisor of the info that would be passed to the hypervisor in the case of the trap-and-emulate method. This is not an issue to a lot of PCI device drivers, which destroy and re-create the interrupts across hibernation, so hv_compose_msi_msg() is called automatically. However, some PCI device drivers (e.g. the in-tree GPU driver nouveau and the out-of-tree Nvidia proprietary GPU driver) do not destroy and re-create MSI/MSI-X interrupts across hibernation, so hv_pci_resume() has to call hv_compose_msi_msg(), otherwise the PCI device drivers can no longer receive interrupts after the VM resumes from hibernation. Hyper-V is also different in that chip->irq_unmask() may fail in a Linux VM running on Hyper-V (on a physical machine, chip->irq_unmask() can not fail because unmasking an MSI/MSI-X register just means an MMIO write): during hibernation, when a CPU is offlined, the kernel tries to move the interrupt to the remaining CPUs that haven't been offlined yet. In this case, hv_irq_unmask() -> hv_do_hypercall() always fails because the vmbus channel has been
[Kernel-packages] [Bug 1904484] 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/1904484 Title: iMac with AMD Radeon Mobility GPU Suffers from Pink Screen Artefacts Following Waking from Suspension Status in linux package in Ubuntu: Confirmed Bug description: The bug is in the text file uploaded titled Launchpad.txt. Thank you so much for your help ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ali 781 F pulseaudio ali 808 F pipewire-media- /dev/snd/seq:ali 780 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 16 20:13:25 2020 InstallationDate: Installed on 2020-11-16 (0 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Apple Inc. iMac8,1 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=a5cc462d-49e8-4b4a-92af-d249eefa326a ro noapic noacpi nosplash irqpoll RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/08 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM81.88Z.00C1.B00.0802091538 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F226BEC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F226BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrIM81.88Z.00C1.B00.0802091538:bd02/09/08:br0.1:svnAppleInc.:pniMac8,1:pvr1.0:rvnAppleInc.:rnMac-F226BEC8:rvrPVT:cvnAppleInc.:ct13:cvrMac-F226BEC8: dmi.product.family: Mac dmi.product.name: iMac8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)
** Also affects: apport (Ubuntu Hirsute) Importance: High Assignee: Brian Murray (brian-murray) Status: Fix Released ** Also affects: bluez (Ubuntu Hirsute) Importance: Undecided Status: Invalid -- 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/1870060 Title: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services) Status in apport package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Invalid Status in apport source package in Focal: Triaged Status in bluez source package in Focal: Invalid Status in apport source package in Groovy: Triaged Status in bluez source package in Groovy: Invalid Status in apport source package in Hirsute: Fix Released Status in bluez source package in Hirsute: Invalid Bug description: [Impact] apport is not creating crash files for multiple system services that use ProtectSystem since Ubuntu 20.04 LTS. [Test Case] On an Ubuntu desktop system perform the following step 1) sudo pkill -11 upowerd With the current version of apport there will not be a crash file for upowerd in /var/crash/. With the version of apport in -proposed there will be a crash file for upowerd in /var/crash/. [Regression Potential] In the event that the changes to /usr/share/apport/apport are bad then apport itself would crash thereby preventing us from getting any crash reports. So in addition to killing upowerd we should also test a regular application like xeyes. [Original Description] bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot
Mainline kernel version 5.8.0-050800-generic boots up without any issues. Mainline kernel version *5.8.18-050818-generic* doesn't (GPF and kernel panics). I'll work backwards from 5.8.18-050818-generic to see when the GPFs and kernel panics go away. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904054 Title: kernel 5.8 general protection fault at boot Status in linux package in Ubuntu: Triaged Bug description: Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26) crashes at boot with many general protection faults, on my Intel NUC 10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benp 2912 F pulseaudio /dev/snd/controlC1: benp 2912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 11:51:07 2020 InstallationDate: Installed on 2020-10-08 (35 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC10i7FNH 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=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago) dmi.bios.date: 08/17/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0045.2020.0817.1709 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904484] [NEW] iMac with AMD Radeon Mobility GPU Suffers from Pink Screen Artefacts Following Waking from Suspension
Public bug reported: The bug is in the text file uploaded. Thank you so much for your help ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ali 781 F pulseaudio ali 808 F pipewire-media- /dev/snd/seq:ali 780 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 16 20:13:25 2020 InstallationDate: Installed on 2020-11-16 (0 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Apple Inc. iMac8,1 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=a5cc462d-49e8-4b4a-92af-d249eefa326a ro noapic noacpi nosplash irqpoll RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/08 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM81.88Z.00C1.B00.0802091538 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F226BEC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F226BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrIM81.88Z.00C1.B00.0802091538:bd02/09/08:br0.1:svnAppleInc.:pniMac8,1:pvr1.0:rvnAppleInc.:rnMac-F226BEC8:rvrPVT:cvnAppleInc.:ct13:cvrMac-F226BEC8: dmi.product.family: Mac dmi.product.name: iMac8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "Launchpad.txt" https://bugs.launchpad.net/bugs/1904484/+attachment/5434936/+files/Launchpad.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/1904484 Title: iMac with AMD Radeon Mobility GPU Suffers from Pink Screen Artefacts Following Waking from Suspension Status in linux package in Ubuntu: New Bug description: The bug is in the text file uploaded. Thank you so much for your help ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ali 781 F pulseaudio ali 808 F pipewire-media- /dev/snd/seq:ali 780 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 16 20:13:25 2020 InstallationDate: Installed on 2020-11-16 (0 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Apple Inc. iMac8,1 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=a5cc462d-49e8-4b4a-92af-d249eefa326a ro noapic noacpi nosplash irqpoll RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/08 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM81.88Z.00C1.B00.0802091538 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F226BEC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F226BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrIM81.88Z.00C1.B00.0802091538:bd02/09/08:br0.1:svnAppleInc.:pniMac8,1:pvr1.0:rvnAppleInc.:rnMac-F226BEC8:rvrPVT:cvnAppleInc.:ct13:cvrMac-F226BEC8: dmi.product.family: Mac dmi.product.name: iMac8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
The patch had also been posted to LKML: https://lkml.org/lkml/2020/11/16/1438 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
Please take a look at the following patch as it might be relevant to the issue at hand. ** Patch added: "[PATCH] unlz4: Handle 0-size chunks, discard trailing padding/garbage" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+attachment/5434929/+files/0001-unlz4-Handle-0-size-chunks-discard-trailing-padding-.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805670] Re: 18.04 LTS - ACPI parsing errors in ZBook G5 Mobile Workstation: issues ex. suspend, touchpad
This happens for me as well with 20.04 and HP ZBook G5. But after turning of almost everything in the BIOS and discovering that it actually booted (without acpi=off), I eventually discovered that it works if I disable... the microphone(!). There are some errors, but it boots and is stable afterwards. Erik -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805670 Title: 18.04 LTS - ACPI parsing errors in ZBook G5 Mobile Workstation: issues ex. suspend, touchpad Status in linux package in Ubuntu: Confirmed Bug description: Some background information: I have a new Ubuntu 18.04 installation that did not go too well. The Live-USB installation would hang with ACPi related errors. I finally installed (barring a GRUB install error) using the acpi=off kernel flag. I also tested with acpi=force and no acpi settings (only worked after the last kernel update). I report here with - no changes in the kernel parameters - no changes in BIOS except of graphics set to hybrid (Nvidia + Intel) otherwise I could not get it to work I am following the indications here: https://wiki.ubuntu.com/DebuggingACPI So here is the initial information I have (kernel version, kernel parameters, ACPI errors): .. uname -a Linux gandalf 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=82d8b6b9-1f12-4651--3639a6b76683 ro quiet splash vt.handoff=1 dmesg | grep -i acpi | grep -i error [0.00] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload-210) [0.00] ACPI Error: 1 table load failures, 19 successful (20170831/tbxfload-246) [0.164845] ACPI Error: Field [CAP1] at bit offset/length 64/32 exceeds size of target Buffer (64 bits) (20170831/dsopcode-235) [0.164874] ACPI Error: Method parse/execution failed \_SB._OSC, AE_AML_BUFFER_LIMIT (20170831/psparse-550) [3.528032] ACPI Error: Method parse/execution failed \_SB.PCI0.SPI1.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/psparse-550) [3.528042] ACPI Error: Method execution failed \_SB.PCI0.SPI1.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/uteval-103) [3.529831] ACPI Error: Method parse/execution failed \_SB.PCI0.SPI2.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/psparse-550) [3.529840] ACPI Error: Method execution failed \_SB.PCI0.SPI2.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/uteval-103) [4.610629] ACPI Error: Method parse/execution failed \_TZ.GETP, AE_AML_PACKAGE_LIMIT (20170831/psparse-550) [4.610635] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, AE_AML_PACKAGE_LIMIT (20170831/psparse-550) [4.611513] ACPI Error: Method parse/execution failed \_TZ.GETP, AE_AML_PACKAGE_LIMIT (20170831/psparse-550) [4.611518] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, AE_AML_PACKAGE_LIMIT (20170831/psparse-550) [8.206279] ACPI Error: Needed [Buffer/String/Package], found [Integer] 85bce4f4 (20170831/exresop-593) [8.206309] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, AE_AML_OPERAND_TYPE (20170831/psparse-550) [8.206315] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_TYPE (20170831/psparse-550) [8.210629] ACPI Error: Needed [Buffer/String/Package], found [Integer] 352a9487 (20170831/exresop-593) [8.210660] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, AE_AML_OPERAND_TYPE (20170831/psparse-550) [8.210666] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_TYPE (20170831/psparse-550) [8.214527] ACPI Error: Needed [Buffer/String/Package], found [Integer] 88ce12bb (20170831/exresop-593) [8.214555] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, AE_AML_OPERAND_TYPE (20170831/psparse-550) [8.214562] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_TYPE (20170831/psparse-550) [8.231122] ACPI Error: Attempt to CreateField of length zero (20170831/dsopcode-168) [8.231147] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPI, AE_AML_OPERAND_VALUE (20170831/psparse-550) [8.231154] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_VALUE (20170831/psparse-550) .. I have also added the following outputs: sudo lspci -vvnn >> report.txt sudo dmidecode > dmidecode.txt The kern.log after a suspend and resume. Some weird behavior I have noticed: . The Live-USB pendrive allowed me to use the touchpad when testing and installing Ubuntu . The current kernel does not allow me to use the touchpad . After I resume, the touchpad
[Kernel-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1870060 Title: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services) Status in apport package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Invalid Status in apport source package in Focal: Triaged Status in bluez source package in Focal: Invalid Status in apport source package in Groovy: Triaged Status in bluez source package in Groovy: Invalid Bug description: [Impact] apport is not creating crash files for multiple system services that use ProtectSystem since Ubuntu 20.04 LTS. [Test Case] On an Ubuntu desktop system perform the following step 1) sudo pkill -11 upowerd With the current version of apport there will not be a crash file for upowerd in /var/crash/. With the version of apport in -proposed there will be a crash file for upowerd in /var/crash/. [Regression Potential] In the event that the changes to /usr/share/apport/apport are bad then apport itself would crash thereby preventing us from getting any crash reports. So in addition to killing upowerd we should also test a regular application like xeyes. [Original Description] bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904243] Re: 21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI disk
I was not able to reproduce this: ubuntu@fginther-hirsute:~$ lsb_release -c Codename: hirsute ubuntu@fginther-hirsute:~$ uname -a Linux fginther-hirsute 5.10.0-4-generic #5-Ubuntu SMP Mon Nov 16 09:45:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ubuntu@fginther-hirsute:~$ cat /etc/cloud/build.info build_name: minimal serial: 20201114 I booted a minimal hirsute image by mistake, but it should be close. Also, the kernel was up to 5.10.0-4 when I tested. There could still be some compatibility issue in play here. Let's see how the next round of testing goes. ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Francis Ginther (fginther) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904243 Title: 21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI disk Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: Incomplete Bug description: This was caught while testing a few runs in the google cloud. Steps to reproduce: 1.) deploy 21.04 in the cloud (n1-standard-1 instance type) 2.) install 5.10.0-3.4 from the canonical-kernel-team bootstrap ppa 2a.) sudo add-apt-repository ppa:canonical-kernel-team/bootstrap 3.) sudo apt install linux-generic-wip Full startup logs attached: looks to be grub related, I have not looked into this any further. 1.410153] VFS: Cannot open root device "PARTUUID=02631d3d-a298-4349-b157-aa86d82843b5" or unknown-block(0,0): error -6 [1.411882] Please append a correct "root=" boot option; here are the available partitions: [1.413203] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [1.414356] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.0-3-generic #4-Ubuntu [1.415702] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [1.417180] Call Trace: [1.417710] show_stack+0x52/0x58 [1.418263] dump_stack+0x70/0x8b [1.418738] panic+0x101/0x2e3 [1.419209] mount_block_root+0x21e/0x298 [1.419778] mount_root+0x38/0x3a [1.420243] prepare_namespace+0x13f/0x18d [1.420840] kernel_init_freeable+0x156/0x17d [1.421574] ? rest_init+0xba/0xba [1.422135] kernel_init+0xe/0x116 [1.422708] ret_from_fork+0x22/0x30 [1.423858] Kernel Offset: 0x10c0 from 0x8100 (relocation range: 0x8000-0xbfff) [1.425374] ACPI MEMORY or I/O RESET_REG. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot
Thanks Ben, that's much appreciated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904054 Title: kernel 5.8 general protection fault at boot Status in linux package in Ubuntu: Triaged Bug description: Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26) crashes at boot with many general protection faults, on my Intel NUC 10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benp 2912 F pulseaudio /dev/snd/controlC1: benp 2912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 11:51:07 2020 InstallationDate: Installed on 2020-10-08 (35 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC10i7FNH 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=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago) dmi.bios.date: 08/17/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0045.2020.0817.1709 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot
OK, after a lot of kernel package installs and rebooting... Mainline kernel version 5.8.5-050805 boots and runs successfully. But the *next* version (5.8.6-050806) generally fails to boot, exhibiting the pattern of GPFs and occasional kernel panics. Once it booted up all the way, but the system hung shortly after booting up. Ubuntu kernel version 5.4.0.52-generic continues to be very reliable on this system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904054 Title: kernel 5.8 general protection fault at boot Status in linux package in Ubuntu: Triaged Bug description: Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26) crashes at boot with many general protection faults, on my Intel NUC 10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benp 2912 F pulseaudio /dev/snd/controlC1: benp 2912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 11:51:07 2020 InstallationDate: Installed on 2020-10-08 (35 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC10i7FNH 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=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago) dmi.bios.date: 08/17/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0045.2020.0817.1709 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391407] Re: package firmware-b43-installer 1:018-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: b43-fwcutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/1391407 Title: package firmware-b43-installer 1:018-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4 Status in b43-fwcutter package in Ubuntu: Confirmed Bug description: dpkg: error processing package firmware-b43-installer (--configure): subprocess installed post-installation script returned error exit status 4 Errors were encountered while processing: firmware-b43-installer E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 14.04 Package: firmware-b43-installer 1:018-2 ProcVersionSignature: Ubuntu 3.13.0-40.68-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.6 AptOrdering: b43-fwcutter: Install firmware-b43-installer: Install b43-fwcutter: Configure firmware-b43-installer: Configure Architecture: i386 Date: Tue Nov 11 08:48:16 2014 DuplicateSignature: package:firmware-b43-installer:1:018-2:subprocess installed post-installation script returned error exit status 4 ErrorMessage: subprocess installed post-installation script returned error exit status 4 InstallationDate: Installed on 2014-05-01 (193 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) PackageArchitecture: all SourcePackage: b43-fwcutter Title: package firmware-b43-installer 1:018-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1391407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902156] Re: [ASUS VivoBook X541UJ] Keyboard and touchpad don't work on kernel 5.8.0.28, but 5.4 or 5.8.16 work
Also doesn't work on ASUS UX360U. Neither in kernel 5.8.0.29 kernel. Works fine on kernel 5.8.18 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902156 Title: [ASUS VivoBook X541UJ] Keyboard and touchpad don't work on kernel 5.8.0.28, but 5.4 or 5.8.16 work Status in linux package in Ubuntu: Confirmed Bug description: when I updated my system to ubuntu 20.10, the keyboard and mouse no longer worked after a little investigation, I found out the kernel causes this problem, downgrading to linux 5.4 or upgrading to linux kernel 5.8.11 solved this issue, I also found that this problem is present on other ASUS laptop models ( my laptop is ASUS) so you may want to investigate this issue to update your default 20.10 Linux kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joseph 1979 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-03 (515 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. X541UJ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=1298f5d0-e6c0-4aa3-9c5a-fbe0ebf0fc02 ro quiet splash pci=noaer mds=full,nosmt vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/18/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541UJ.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541UJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541UJ.310:bd04/18/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnX541UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X541UJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902156/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests
Still visible in Xenial 4.4.0-1118.132 AWS c5.metal ** Tags added: sru-20201109 -- 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/1821394 Title: vmx tests fail in kvm_unit_tests Status in ubuntu-kernel-tests: Confirmed Status in linux-aws package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Bug description: Reproducible: Yes, every time. Series: cosmic Kernel: "linux-aws 4.18.0-1012.14" Steps: 1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git gcc-multilib 2.) git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 3.) cd kvm-unit-tests; ./configure; make 4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* -vmx_vmcs_shadow_test" PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails INFO: Processor supports accessed and dirty flag PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails FAIL:
[Kernel-packages] [Bug 1748103] Re: apic test in kvm-unit-test failed with timeout
Still visible in Xenial 4.4.0-1118.132 AWS c5.metal ** Tags added: sru-20201109 -- 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/1748103 Title: apic test in kvm-unit-test failed with timeout Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux-azure-edge package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux-azure-edge source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux-azure-edge source package in Bionic: New Bug description: With Joshua's comment in bug 1719524: "Nested KVM can only be tried on instance sizes with nested Hypervisor support: Ev3 and Dv3.", although the instance name is E4v3 here but I can start a KVM on it. Test apic will timeout on it. Steps: 1. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 2. cd kvm-unit-tests; ./configure; make 3. Run the apic test as root: # TESTNAME=apic TIMEOUT=30 ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.onXtr5JVp7 enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 apic version: 1050014 PASS: apic existence PASS: xapic id matches cpuid PASS: writeable xapic id PASS: non-writeable x2apic id PASS: sane x2apic id FAIL: x2apic id matches cpuid PASS: correct xapic id after reset PASS: apic_disable: Local apic enabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: Local apic disabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear PASS: apic_disable: Local apic enabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set x2apic enabled PASS: x2apic enabled to invalid state PASS: x2apic enabled to apic enabled PASS: disabled to invalid state PASS: disabled to x2apic enabled PASS: apic enabled to invalid state PASS: apicbase: relocate apic PASS: apicbase: reserved physaddr bits PASS: apicbase: reserved low bits PASS: self ipi starting broadcast (x2apic) PASS: APIC physical broadcast address PASS: APIC physical broadcast shorthand PASS: nmi-after-sti qemu-system-x86_64: terminating on signal 15 from pid 7246 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4 ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14 Uname: Linux 4.14.0-1004-azure-edge x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Feb 8 06:00:55 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-azure-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DistroRelease: Ubuntu 16.04 Package: linux-azure-edge PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 4.13.0-1009.12-username 4.13.13 Tags: xenial uec-images Uname: Linux 4.13.0-1009-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy libvirtd lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1593056] Re: backport hibernate fix for recent kernels
** Package changed: gnome-shell (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/1593056 Title: backport hibernate fix for recent kernels Status in linux package in Ubuntu: Incomplete Bug description: Hibernate has been broken in Kernel that ships with Ubuntu. Recently upstream has fixed the problem with hibernation which appears to be a long standing bug. https://bugzilla.kernel.org/show_bug.cgi?id=104771 Can this bug fix be backported to Ubuntu 16.04 ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1593056] 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 1593056 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/1593056 Title: backport hibernate fix for recent kernels Status in linux package in Ubuntu: Incomplete Bug description: Hibernate has been broken in Kernel that ships with Ubuntu. Recently upstream has fixed the problem with hibernation which appears to be a long standing bug. https://bugzilla.kernel.org/show_bug.cgi?id=104771 Can this bug fix be backported to Ubuntu 16.04 ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904509] 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 1904509 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-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1904509 Title: Intel(R) Wi-Fi 6 AX201 160MHz [8086:a0f0] subsystem [8086:4070] fails to register device: can not clear persistence bit Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Bug description: [Summary] The Wi-Fi interface is missing on Gnome Settings, even through ifconfig command. See below message from syslog for more details. Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.336194] iwlwifi :00:14.3: enabling device ( -> 0002) Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.416938] WARNING: CPU: 7 PID: 411 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2088 iwl_trans_pcie_grab_nic_access+0x1bd/0x1f0 [iwlwifi] Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.416938] Modules linked in: snd_seq_device dell_smbios snd_timer dcdbas input_leds(+) intel_cstate(+) serio_raw snd dell_wmi_descriptor fjes(-) wmi_bmof iwlwifi(+) soundcore hid_sensor_gyro_3d mei_me cfg80211 hid_multitouch(+) mei hid_sensor_accel_3d hid_sensor_als hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common industrialio processor_thermal_device ucsi_acpi typec_ucsi intel_rapl_common cros_ec_ishtp intel_soc_dts_iosf cros_ec typec int3403_thermal int340x_thermal_zone soc_button_array mac_hid intel_hid int3400_thermal acpi_thermal_rel acpi_pad sparse_keymap acpi_tad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor usbhid raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log hid_sensor_custom hid_sensor_hub intel_ishtp_loader intel_ishtp_hid hid_generic i915 rtsx_pci_sdmmc i2c_algo_bit Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417001] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1bd/0x1f0 [iwlwifi] Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417027] iwl_pci_probe+0xf2/0x6d0 [iwlwifi] Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417062] iwl_pci_register_driver+0x25/0x40 [iwlwifi] Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417074] iwl_drv_init+0x83/0x1000 [iwlwifi] Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417112] iwlwifi :00:14.3: iwlwifi transaction failed, dumping registers Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417113] iwlwifi :00:14.3: iwlwifi device config registers: Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417610] iwlwifi :00:14.3: : a0f08086 00100400 02800020 0080 5319c004 0060 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417612] iwlwifi :00:14.3: 0020: 40708086 00c8 01ff Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417613] iwlwifi :00:14.3: 0040: 00928010 1ec0 00100c10 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417615] iwlwifi :00:14.3: 0060: 00080812 0405 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417616] iwlwifi :00:14.3: 0080: 800f0011 2000 3000 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417618] iwlwifi :00:14.3: 00a0: Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417620] iwlwifi :00:14.3: 00c0: c823d001 0d08 00804005 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417621] iwlwifi :00:14.3: 00e0: Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417623] iwlwifi :00:14.3: 0100: 16410018 00462031 2000 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417624] iwlwifi :00:14.3: 0120: Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417626] iwlwifi :00:14.3: 0140: 14c0 ff00 00ff 0001001e 00481e1f Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417627] iwlwifi
[Kernel-packages] [Bug 1904512] 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/1904512 Title: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 Status in linux package in Ubuntu: Confirmed Bug description: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-95-generic 3.13.0-95.142 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student2551 F pulseaudio Date: Mon Nov 16 22:28:47 2020 DuplicateSignature: package:linux-image-3.13.0-95-generic:3.13.0-95.142:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=3d4ab9a1-2d6d-4b35-87a7-2d89117768f0 InstallationDate: Installed on 2016-09-12 (1526 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 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 MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=4202df25-0bff-4b12-9bc1-a3b8e2bb9925 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: Upgraded to trusty on 2020-11-17 (0 days ago) dmi.bios.date: 02/27/2020 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.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904521] [NEW] Intel Tiger Lake IDs supplement
Public bug reported: [Impact] [Fix] [Test] [Regression potential] ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Groovy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** No longer affects: linux (Ubuntu Focal) ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => In Progress ** No longer affects: linux-oem-5.6 (Ubuntu Groovy) ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.6 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904521 Title: Intel Tiger Lake IDs supplement Status in linux package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: [Impact] [Fix] [Test] [Regression potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904513] [NEW] package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17
*** This bug is a duplicate of bug 1904512 *** https://bugs.launchpad.net/bugs/1904512 Public bug reported: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-95-generic 3.13.0-95.142 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student2551 F pulseaudio Date: Mon Nov 16 22:28:47 2020 DuplicateSignature: package:linux-image-3.13.0-95-generic:3.13.0-95.142:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=3d4ab9a1-2d6d-4b35-87a7-2d89117768f0 InstallationDate: Installed on 2016-09-12 (1526 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 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 MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=4202df25-0bff-4b12-9bc1-a3b8e2bb9925 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: Upgraded to trusty on 2020-11-17 (0 days ago) dmi.bios.date: 02/27/2020 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.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904513 Title: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 Status in linux package in Ubuntu: New Bug description: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-95-generic 3.13.0-95.142 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student2551 F pulseaudio Date: Mon Nov 16 22:28:47 2020 DuplicateSignature: package:linux-image-3.13.0-95-generic:3.13.0-95.142:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=3d4ab9a1-2d6d-4b35-87a7-2d89117768f0 InstallationDate: Installed on 2016-09-12 (1526 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 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 MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=4202df25-0bff-4b12-9bc1-a3b8e2bb9925 ro quiet splash
[Kernel-packages] [Bug 1904512] Re: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17
** 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/1904512 Title: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 Status in linux package in Ubuntu: New Bug description: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-95-generic 3.13.0-95.142 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student2551 F pulseaudio Date: Mon Nov 16 22:28:47 2020 DuplicateSignature: package:linux-image-3.13.0-95-generic:3.13.0-95.142:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=3d4ab9a1-2d6d-4b35-87a7-2d89117768f0 InstallationDate: Installed on 2016-09-12 (1526 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 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 MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=4202df25-0bff-4b12-9bc1-a3b8e2bb9925 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: Upgraded to trusty on 2020-11-17 (0 days ago) dmi.bios.date: 02/27/2020 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.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904511] [NEW] package linux-image-3.13.0-96-generic 3.13.0-96.143 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17
Public bug reported: package linux image generic installation error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-96-generic 3.13.0-96.143 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student2551 F pulseaudio Date: Mon Nov 16 22:28:47 2020 DuplicateSignature: package:linux-image-3.13.0-96-generic:3.13.0-96.143:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=3d4ab9a1-2d6d-4b35-87a7-2d89117768f0 InstallationDate: Installed on 2016-09-12 (1526 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 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 MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=4202df25-0bff-4b12-9bc1-a3b8e2bb9925 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.13.0-96-generic 3.13.0-96.143 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: Upgraded to trusty on 2020-11-17 (0 days ago) dmi.bios.date: 02/27/2020 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.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904511 Title: package linux-image-3.13.0-96-generic 3.13.0-96.143 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 Status in linux package in Ubuntu: New Bug description: package linux image generic installation error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-96-generic 3.13.0-96.143 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student2551 F pulseaudio Date: Mon Nov 16 22:28:47 2020 DuplicateSignature: package:linux-image-3.13.0-96-generic:3.13.0-96.143:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=3d4ab9a1-2d6d-4b35-87a7-2d89117768f0 InstallationDate: Installed on 2016-09-12 (1526 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 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 MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=4202df25-0bff-4b12-9bc1-a3b8e2bb9925 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package
[Kernel-packages] [Bug 1904512] [NEW] package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17
Public bug reported: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-95-generic 3.13.0-95.142 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student2551 F pulseaudio Date: Mon Nov 16 22:28:47 2020 DuplicateSignature: package:linux-image-3.13.0-95-generic:3.13.0-95.142:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=3d4ab9a1-2d6d-4b35-87a7-2d89117768f0 InstallationDate: Installed on 2016-09-12 (1526 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 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 MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=4202df25-0bff-4b12-9bc1-a3b8e2bb9925 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: Upgraded to trusty on 2020-11-17 (0 days ago) dmi.bios.date: 02/27/2020 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.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904512 Title: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 Status in linux package in Ubuntu: New Bug description: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-95-generic 3.13.0-95.142 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student2551 F pulseaudio Date: Mon Nov 16 22:28:47 2020 DuplicateSignature: package:linux-image-3.13.0-95-generic:3.13.0-95.142:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=3d4ab9a1-2d6d-4b35-87a7-2d89117768f0 InstallationDate: Installed on 2016-09-12 (1526 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 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 MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=4202df25-0bff-4b12-9bc1-a3b8e2bb9925 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon
[Kernel-packages] [Bug 1904091] Re: Linux, Ubuntu, 20.04, X40CI, S_P: Monitor connect Salomon Dock has no display(FR:100%)
** Attachment added: "sosreport-tt-Precision-5750-100554.008-2020-11-17-hpqsnsu.tar.xz" https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1904091/+attachment/5435071/+files/sosreport-tt-Precision-5750-100554.008-2020-11-17-hpqsnsu.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1904091 Title: Linux,Ubuntu,20.04,X40CI,S_P: Monitor connect Salomon Dock has no display(FR:100%) Status in linux-oem package in Ubuntu: New Bug description: [Result] Expected Result Boot to SUT to Ubutnu OS, plugging in the external Display/Monitor video cable to the Salomon dock, SUT& monitor has not problem(s) or issue(s). Actual Result Boot to SUT to Ubutnu OS, plugging in the external Display/Monitor video cable to the Salomon dock, SUT can recognize monitor, but monitor no display. [Additional Information] 1. Test Vault ID: 61923.008 2. SKU: Precision All SKU 3. BIOS Version: 1.4.0 4. ImageManifest: Ubuntu 20.04.1 LTS (fossa-bronn X40) 5. Product Name: Precision 5750 6. Kernel Version:5.6.0-2029-oem 7. CPU: Intel(R) Core(TM) i7-10850H @ 2.70GHz12 8. GPU: Mesa Intel(R) UHD Graphics (CML GT2) 9.VP DC/SC/TBT FWA03 & FWA04 Dock 10.VP all types of Monitors & Monitors ports 11.VNP Ubuntu 18.04 Failure rate Precision-SKU5-6 10/10 times Precision-SKUP2-3 10/10times [Reproduce Steps] 1. Flash Latest BIOS, Install Ubuntu OS 20.04.1. 2. Do Ubuntu update. 3. Plugging in the external Display/Monitor video cable to the Salomon dock, SUT can recognize monitor, but monitor no display.>problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1904091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904508] [NEW] package firmware-b43legacy-installer 1:019-4 failed to install/upgrade: el subproceso instalado paquete firmware-b43legacy-installer script post-installation devo
Public bug reported: intento hacer que funcione el wifi en mi laptop lenovo idepad 330 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: firmware-b43legacy-installer 1:019-4 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 AptOrdering: firmware-b43legacy-installer:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 16 23:41:28 2020 ErrorMessage: el subproceso instalado paquete firmware-b43legacy-installer script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2020-11-13 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: b43-fwcutter Title: package firmware-b43legacy-installer 1:019-4 failed to install/upgrade: el subproceso instalado paquete firmware-b43legacy-installer script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: b43-fwcutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/1904508 Title: package firmware-b43legacy-installer 1:019-4 failed to install/upgrade: el subproceso instalado paquete firmware-b43legacy- installer script post-installation devolvió el código de salida de error 1 Status in b43-fwcutter package in Ubuntu: New Bug description: intento hacer que funcione el wifi en mi laptop lenovo idepad 330 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: firmware-b43legacy-installer 1:019-4 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 AptOrdering: firmware-b43legacy-installer:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 16 23:41:28 2020 ErrorMessage: el subproceso instalado paquete firmware-b43legacy-installer script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2020-11-13 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: b43-fwcutter Title: package firmware-b43legacy-installer 1:019-4 failed to install/upgrade: el subproceso instalado paquete firmware-b43legacy-installer script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1904508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822308] Re: vmx_hlt_with_rvi_test in kvm_unit_tests fails
Still visible in Xenial 4.4.0-1118.132 AWS c5.metal ** Tags added: sru-20201109 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1822308 Title: vmx_hlt_with_rvi_test in kvm_unit_tests fails Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Bug description: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_hlt_with_rvi_test' BUILD_HEAD=e2c275c4 timeout -k 1s --foreground 10 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.Jo9XTMTiTj -smp 1 -cpu host,+vmx -append vmx_hlt_with_rvi_test # -initrd /tmp/tmp.Y9HtqW5t9P enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_hlt_with_rvi_test qemu-system-x86_64: terminating on signal 15 from pid 24517 FAIL vmx_hlt_with_rvi_test (timeout; duration=10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822309] Re: vmx_apic_passthrough_thread in kvm_unit_tests failed with 1 unexpected failures
Still visible in Xenial 4.4.0-1118.132 AWS c5.metal ** Tags added: sru-20201109 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1822309 Title: vmx_apic_passthrough_thread in kvm_unit_tests failed with 1 unexpected failures Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-kvm source package in Xenial: New Status in linux-aws source package in Bionic: New Status in linux-kvm source package in Bionic: New Status in linux-oracle source package in Bionic: New Bug description: TESTNAME=vmx_apic_passthrough_thread TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 2 -cpu host,+vmx -m 2048 -append vmx_apic_passthrough_thread_test FAIL vmx_apic_passthrough_thread (5 tests, 1 unexpected failures) Detailed report will be appended later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822309/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821906] Re: debug in ubuntu_kvm_unit_test failed on 3.13 / 4.4
Still visible in Xenial 4.4.0-1118.132 AWS c5.metal ** Tags added: sru-20201109 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821906 Title: debug in ubuntu_kvm_unit_test failed on 3.13 / 4.4 Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Status in linux source package in Xenial: Confirmed Bug description: This test has failed on: * T-3.13: - FAIL debug (11 tests, 6 unexpected failures) * T-4.4 / X-4.4: - FAIL debug (11 tests, 1 unexpected failures) root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests# TESTNAME=debug TIMEOUT=90s ACCEL= ./x86/run x86/debug.flat -smp 1 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/debug.flat -smp 1 # -initrd /tmp/tmp.WOQmQkB7bo enabling apic PASS: #BP PASS: hw breakpoint (test that dr6.BS is not set) PASS: hw breakpoint (test that dr6.BS is not cleared) PASS: single step FAIL: single step emulated instructions PASS: hw watchpoint (test that dr6.BS is not cleared) PASS: hw watchpoint (test that dr6.BS is not set) PASS: icebp PASS: MOV SS + watchpoint + ICEBP PASS: MOV SS + watchpoint + int $1 PASS: MOV SS + watchpoint + INT3 SUMMARY: 11 tests, 1 unexpected failures ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-143-generic 4.4.0-143.169~14.04.2 ProcVersionSignature: User Name 4.4.0-143.169~14.04.2-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Wed Mar 27 11:15:05 2019 SourcePackage: linux-signed-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821906/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827866] Re: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X/B-KVM X-azure
Still visible in Xenial 4.4.0-1118.132 AWS c5.metal ** Tags added: sru-20201109 ** Summary changed: - vmx_apicv_test in ubuntu_kvm_unit_tests failed on X/B-KVM X-azure + vmx_apicv_test in ubuntu_kvm_unit_tests failed on X/B-KVM X-azure / X-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827866 Title: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X/B-KVM X-azure / X-aws Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Xenial: New Status in linux-kvm source package in Xenial: New Status in linux-oracle source package in Xenial: New Status in linux-azure source package in Bionic: New Status in linux-kvm source package in Bionic: New Status in linux-oracle source package in Bionic: New Bug description: vmx_apicv_test from ubuntu_kvm_unit_tests failed on X-KVM: FAIL vmx_apicv_test (timeout; duration=10) the test was terminated with return code 124: # TESTNAME=vmx_apicv_test TIMEOUT=10 ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "apic_reg_virt_test virt_x2apic_mode_test" timeout -k 1s --foreground 10 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu host,+vmx -append apic_reg_virt_test virt_x2apic_mode_test # -initrd /tmp/tmp.K6b7rjmgp8 enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: apic_reg_virt_test --- Virtualize APIC accesses test --- PASS: xapic - reading 0x000: got APIC access exit @ page offset 0x000, want 0x000 PASS: xapic - writing 0x12345678 to 0x000: got APIC access exit @ page offset 0x000, want 0x000 PASS: xapic - reading 0x010: got APIC access exit @ page offset 0x010, want 0x010 PASS: xapic - writing 0x12345678 to 0x010: got APIC access exit @ page offset 0x010, want 0x010 PASS: xapic - reading 0x020: got APIC access exit @ page offset 0x020, want 0x020 PASS: xapic - writing 0x12345678 to 0x020: got APIC access exit @ page offset 0x020, want 0x020 PASS: xapic - reading 0x030: got APIC access exit @ page offset 0x030, want 0x030 PASS: xapic - writing 0x12345678 to 0x380: non-virtualized write; val is 0x12345678, want 0x12345678 PASS: xapic - reading 0x390: read 0x12345678, expected 0x12345678. PASS: xapic - writing 0x12345678 to 0x390: non-virtualized writqemu-system-x86_64: terminating on signal 15 from pid 1327 # echo $? 124 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1044-kvm 4.4.0-1044.50 ProcVersionSignature: Ubuntu 4.4.0-1044.50-kvm 4.4.177 Uname: Linux 4.4.0-1044-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon May 6 10:47:17 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720438] Re: brightness control broken nvidia
** Tags removed: gnome-17.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia Status in gnome-power: Confirmed Status in gnome-power-manager package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 beta 2 Nvidia 310M, 340.x official driver installed with Additional Drivers program The brightness control built into the laptop (Dell Vostro 3300) isn't changing the brightness. Normally I can use Fn + Up/Down arrow keys to change the brightness. The brightness control works fine in Ubuntu 16.04 with the same driver series. I don't know if this is a GNOME 3.26 bug but it's likely as I'm having the exact same problem with Fedora 26 on this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1720438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904511] 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/1904511 Title: package linux-image-3.13.0-96-generic 3.13.0-96.143 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 Status in linux package in Ubuntu: Confirmed Bug description: package linux image generic installation error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-96-generic 3.13.0-96.143 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student2551 F pulseaudio Date: Mon Nov 16 22:28:47 2020 DuplicateSignature: package:linux-image-3.13.0-96-generic:3.13.0-96.143:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=3d4ab9a1-2d6d-4b35-87a7-2d89117768f0 InstallationDate: Installed on 2016-09-12 (1526 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 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 MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=4202df25-0bff-4b12-9bc1-a3b8e2bb9925 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.13.0-96-generic 3.13.0-96.143 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: Upgraded to trusty on 2020-11-17 (0 days ago) dmi.bios.date: 02/27/2020 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.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904511/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904509] [NEW] Intel(R) Wi-Fi 6 AX201 160MHz [8086:a0f0] subsystem [8086:4070] fails to register device: can not clear persistence bit
Public bug reported: [Summary] The Wi-Fi interface is missing on Gnome Settings, even through ifconfig command. See below message from syslog for more details. Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.336194] iwlwifi :00:14.3: enabling device ( -> 0002) Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.416938] WARNING: CPU: 7 PID: 411 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2088 iwl_trans_pcie_grab_nic_access+0x1bd/0x1f0 [iwlwifi] Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.416938] Modules linked in: snd_seq_device dell_smbios snd_timer dcdbas input_leds(+) intel_cstate(+) serio_raw snd dell_wmi_descriptor fjes(-) wmi_bmof iwlwifi(+) soundcore hid_sensor_gyro_3d mei_me cfg80211 hid_multitouch(+) mei hid_sensor_accel_3d hid_sensor_als hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common industrialio processor_thermal_device ucsi_acpi typec_ucsi intel_rapl_common cros_ec_ishtp intel_soc_dts_iosf cros_ec typec int3403_thermal int340x_thermal_zone soc_button_array mac_hid intel_hid int3400_thermal acpi_thermal_rel acpi_pad sparse_keymap acpi_tad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor usbhid raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log hid_sensor_custom hid_sensor_hub intel_ishtp_loader intel_ishtp_hid hid_generic i915 rtsx_pci_sdmmc i2c_algo_bit Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417001] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1bd/0x1f0 [iwlwifi] Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417027] iwl_pci_probe+0xf2/0x6d0 [iwlwifi] Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417062] iwl_pci_register_driver+0x25/0x40 [iwlwifi] Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417074] iwl_drv_init+0x83/0x1000 [iwlwifi] Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417112] iwlwifi :00:14.3: iwlwifi transaction failed, dumping registers Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417113] iwlwifi :00:14.3: iwlwifi device config registers: Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417610] iwlwifi :00:14.3: : a0f08086 00100400 02800020 0080 5319c004 0060 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417612] iwlwifi :00:14.3: 0020: 40708086 00c8 01ff Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417613] iwlwifi :00:14.3: 0040: 00928010 1ec0 00100c10 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417615] iwlwifi :00:14.3: 0060: 00080812 0405 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417616] iwlwifi :00:14.3: 0080: 800f0011 2000 3000 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417618] iwlwifi :00:14.3: 00a0: Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417620] iwlwifi :00:14.3: 00c0: c823d001 0d08 00804005 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417621] iwlwifi :00:14.3: 00e0: Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417623] iwlwifi :00:14.3: 0100: 16410018 00462031 2000 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417624] iwlwifi :00:14.3: 0120: Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417626] iwlwifi :00:14.3: 0140: 14c0 ff00 00ff 0001001e 00481e1f Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417627] iwlwifi :00:14.3: iwlwifi device memory mapped registers: Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417884] iwlwifi :00:14.3: : Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417886] iwlwifi :00:14.3: 0020: Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.418247] iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-52.ucode failed with error -2 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.418270] iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-51.ucode failed with error -2 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.418284] iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.418299] iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.419744] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ
[Kernel-packages] [Bug 1904509] Re: Intel(R) Wi-Fi 6 AX201 160MHz [8086:a0f0] subsystem [8086:4070] fails to register device: can not clear persistence bit
** Tags added: oem-priority originate-from-1904092 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1904509 Title: Intel(R) Wi-Fi 6 AX201 160MHz [8086:a0f0] subsystem [8086:4070] fails to register device: can not clear persistence bit Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Bug description: [Summary] The Wi-Fi interface is missing on Gnome Settings, even through ifconfig command. See below message from syslog for more details. Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.336194] iwlwifi :00:14.3: enabling device ( -> 0002) Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.416938] WARNING: CPU: 7 PID: 411 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2088 iwl_trans_pcie_grab_nic_access+0x1bd/0x1f0 [iwlwifi] Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.416938] Modules linked in: snd_seq_device dell_smbios snd_timer dcdbas input_leds(+) intel_cstate(+) serio_raw snd dell_wmi_descriptor fjes(-) wmi_bmof iwlwifi(+) soundcore hid_sensor_gyro_3d mei_me cfg80211 hid_multitouch(+) mei hid_sensor_accel_3d hid_sensor_als hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common industrialio processor_thermal_device ucsi_acpi typec_ucsi intel_rapl_common cros_ec_ishtp intel_soc_dts_iosf cros_ec typec int3403_thermal int340x_thermal_zone soc_button_array mac_hid intel_hid int3400_thermal acpi_thermal_rel acpi_pad sparse_keymap acpi_tad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor usbhid raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log hid_sensor_custom hid_sensor_hub intel_ishtp_loader intel_ishtp_hid hid_generic i915 rtsx_pci_sdmmc i2c_algo_bit Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417001] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1bd/0x1f0 [iwlwifi] Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417027] iwl_pci_probe+0xf2/0x6d0 [iwlwifi] Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417062] iwl_pci_register_driver+0x25/0x40 [iwlwifi] Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417074] iwl_drv_init+0x83/0x1000 [iwlwifi] Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417112] iwlwifi :00:14.3: iwlwifi transaction failed, dumping registers Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417113] iwlwifi :00:14.3: iwlwifi device config registers: Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417610] iwlwifi :00:14.3: : a0f08086 00100400 02800020 0080 5319c004 0060 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417612] iwlwifi :00:14.3: 0020: 40708086 00c8 01ff Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417613] iwlwifi :00:14.3: 0040: 00928010 1ec0 00100c10 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417615] iwlwifi :00:14.3: 0060: 00080812 0405 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417616] iwlwifi :00:14.3: 0080: 800f0011 2000 3000 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417618] iwlwifi :00:14.3: 00a0: Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417620] iwlwifi :00:14.3: 00c0: c823d001 0d08 00804005 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417621] iwlwifi :00:14.3: 00e0: Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417623] iwlwifi :00:14.3: 0100: 16410018 00462031 2000 Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417624] iwlwifi :00:14.3: 0120: Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417626] iwlwifi :00:14.3: 0140: 14c0 ff00 00ff 0001001e 00481e1f Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417627] iwlwifi :00:14.3: iwlwifi device memory mapped registers: Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417884] iwlwifi :00:14.3: : Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.417886] iwlwifi :00:14.3: 0020: Nov 12 05:01:05 u-Latitude-9520 kernel: [ 4.418247] iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-52.ucode failed with error -2 Nov 12
[Kernel-packages] [Bug 1904521] Re: Intel Tiger Lake IDs supplement
** Description changed: [Impact] + Intel Tiger Lake-H platform requires new pin settings and IDs to enable. [Fix] + Intel provides us a list of TGL-H commits on 5.8 and 5.9, we need all of the commits to enable TGL-H platforms completely. [Test] + Verified those commits on Intel TGL-H SDP [Regression potential] + Low, all of those commits are adding new IDs for TGL-H platform. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904521 Title: Intel Tiger Lake IDs supplement Status in linux package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: [Impact] Intel Tiger Lake-H platform requires new pin settings and IDs to enable. [Fix] Intel provides us a list of TGL-H commits on 5.8 and 5.9, we need all of the commits to enable TGL-H platforms completely. [Test] Verified those commits on Intel TGL-H SDP [Regression potential] Low, all of those commits are adding new IDs for TGL-H platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Also affects: linux-oem-5.6 (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/1903969 Title: failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: New Status in linux-oem-5.6 source package in Groovy: New Status in linux source package in Hirsute: In Progress Status in linux-oem-5.6 source package in Hirsute: New Bug description: [Summary] When the monitor ONLY is connected to the WD19 (DP port) and WD19 is connected to the type c port than boot the machine, the monitor shows no video output after loaded i915. [Reproduce Steps] 1. connect power cable of WD19 2. connect DP cable from monitor to WD19 3. connect power cable to target system. 4. connect type c cable from WD19 to target system 5. boot up [Results] Expected: video output as there is only one monitor connected. Actual: No video output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35 ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 Uname: Linux 5.6.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 12 05:11:11 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40 InstallationDate: Installed on 2020-11-03 (9 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-signed-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900951] Re: ptrace10 from ubuntu_ltp_syscalls failed on X/B
Spotted on AWS 4.4.0-1118.132 ** Summary changed: - ptrace10 from ubuntu_ltp_syscalls failed on B + ptrace10 from ubuntu_ltp_syscalls failed on X/B ** Tags added: 4.4 aws ** Tags added: sru-20201109 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1900951 Title: ptrace10 from ubuntu_ltp_syscalls failed on X/B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: Issue found on B-AWS 4.15.0-1087.92 This is a new test case added a week ago [1]. Test failed with: startup='Wed Oct 21 13:10:37 2020' tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s ptrace10.c:60: TFAIL: The rd0 wasn't set on second PTRACE_POKEUSER HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd14406b78e6 Summary: passed 0 failed 1 skipped 0 warnings 0 tag=ptrace10 stime=1603285837 dur=0 exit=exited stat=1 core=no cu=0 cs=0 [1] https://github.com/linux-test- project/ltp/blob/master/testcases/kernel/syscalls/ptrace/ptrace10.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902934] Re: dmesg is not restricted in linux-raspi kernel
** Changed in: linux-raspi (Ubuntu Groovy) Status: Triaged => Fix Committed ** No longer affects: linux-raspi (Ubuntu Hirsute) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1902934 Title: dmesg is not restricted in linux-raspi kernel Status in linux-raspi package in Ubuntu: Triaged Status in linux-raspi source package in Groovy: Fix Committed Bug description: [Impact] The CONFIG_SECURITY_DMESG_RESTRICT option is not set on the Ubuntu Pi kernels, resulting in dmesg being accessible to ordinary users. This is in contrast to PC installs, where dmesg is now restricted to the "root" user in 20.10 onwards. The following messages from the ubuntu-devel list cover the original proposal (which proposed limiting dmesg to root:adm), and earlier discussion from 2011 (which proposed limiting dmesg to root alone, which is what was implemented in groovy): https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html https://lists.ubuntu.com/archives/ubuntu-devel/2011-May/033240.html [Test Case] $ dmesg > /dev/null $ echo $? 0 Should be: $ dmesg dmesg: read kernel buffer failed: Operation not permitted [Regression Potential] Ordinary users might still be able to execute dmesg and read the kernel logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1902934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866323] Re: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
Still visible in Xenial 4.4.0-1118.132 AWS c5.metal ** Tags added: sru-20201109 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866323 Title: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Test failure in fallocate06 was composed by two issues, one is xfs fill_fs test issue addressed in bug 1865967. Another is this one, this is the case 2 of btrfs (fill_fs): tst_test.c:1290: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (2 This issue can be found from X to F X - https://pastebin.ubuntu.com/p/9FfVrZkQN8/ B - https://pastebin.ubuntu.com/p/Zc9TW4sQKF/ D - https://pastebin.ubuntu.com/p/cryTnnn5wF/ E - https://pastebin.ubuntu.com/p/FXTZpsX7Qb/ F - https://pastebin.ubuntu.com/p/FKPJKCS2zr/ Note that the hint printed in the test: HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e093c4be760e It something that will get printed after the test, as it's for XFS so it has nothing to do with this issue here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1593056] [NEW] backport hibernate fix for recent kernels
You have been subscribed to a public bug: Hibernate has been broken in Kernel that ships with Ubuntu. Recently upstream has fixed the problem with hibernation which appears to be a long standing bug. https://bugzilla.kernel.org/show_bug.cgi?id=104771 Can this bug fix be backported to Ubuntu 16.04 ? ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- backport hibernate fix for recent kernels https://bugs.launchpad.net/bugs/1593056 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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@ #47 Creative Labs BT-W3 supports mSBC (https://sg.creative.com/p/speakers/creative-bt-w3). I had checked with them before buying one. Tried pairing it with Jabra Talk 15, as well as Avantree Clipper Pro, and I can confirm that it works. Tried plotting the spectrum of the recorded audio using Audacity to confirm. Affirmative. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
Still visible in Xenial 4.4.0-1118.132 AWS c5.metal
** Tags added: sru-20201109
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802454
Title:
fanotify10 in ubuntu_ltp_syscalls failed
Status in ubuntu-kernel-tests:
Confirmed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
New
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux source package in Focal:
Fix Released
Bug description:
== Justification ==
Commit 92183a42898d ("fsnotify: fix ignore mask logic in
send_to_group()") acknowledges the use case of ignoring an event on
an inode mark, because of an ignore mask on a mount mark of the same
group (i.e. I want to get all events on this file, except for the events
that came from that mount).
This change depends on correctly merging the inode marks and mount marks
group lists, so that the mount mark ignore mask would be tested in
send_to_group(). Alas, the merging of the lists did not take into
account the case where event in question is not in the mask of any of
the mount marks.
To fix this, completely remove the tests for inode and mount event masks
from the lists merging code.
== Fix ==
9bdda4e9 (fsnotify: fix ignore mask logic in fsnotify())
Test kernels for Bionic can be found here:
http://people.canonical.com/~phlin/kernel/lp-1802454-fanotify10/bionic/
It seems that T/X poses with the same issue and we might be able to backport
it with the same logic, but I think we should target Bionic as it's a fix for
for 92183a42898d which was only applied to Bionic.
== Regression Potential ==
Low.
The backport work is required as it's missing commit 47d9c7cc457 in Bionic,
which generalizes the iteration of marks for inode_mark and vfsmount_mark,
from:
iter_info.inode_mark
to:
iter_info.marks[FSNOTIFY_OBJ_TYPE_INODE]
But the patch can still be backported with the same logic without this
commit.
The test with the syscalls test in LTP test suite shows no sign of
regression.
== Test Case ==
Run the fanotify10 test in ubuntu_ltp_syscalls test suite. And it will pass
with the patched kernel.
Full LTP syscalls test with 4.15.0-42 in -proposed:
http://paste.ubuntu.com/p/Wm8nQ932g6/
Full LTP syscalls test with patched 4.15.0-42:
http://paste.ubuntu.com/p/nv4jW6shpJ/
-
This is a new test case that landed 7 days ago.
<<>>
tag=fanotify10 stime=1541744937
cmdline="fanotify10"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop1'
tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
mke2fs 1.44.1 (24-Mar-2018)
tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
fanotify10.c:199: INFO: Test #0: ignore mount events created on a specific
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:264: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:199: INFO: Test #1: don't ignore mount events created on another
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:199: INFO: Test #2: ignore inode events created on a specific
mount point
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:258: FAIL: group 0 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT
[Kernel-packages] [Bug 1833028] Re: fanotify06 from ubuntu_ltp_syscalls failed
Still visible in Xenial 4.4.0-1118.132 AWS c5.metal ** Tags added: sru-20201109 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833028 Title: fanotify06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Status in linux source package in Disco: Fix Released Bug description: == SRU Justification == fanotify06 test from ubuntu_ltp_syscalls reported that test #1 for overlayfs has received more than one expected event: <<>> tag=fanotify06 stime=1560747299 cmdline="fanotify06" contacts="" analysis=exit <<>> incrementing stop tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2' tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15 fanotify06.c:230: PASS: group 8 got no event fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark fanotify06.c:208: FAIL: group 0 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 1 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 2 got more than one event (48 > 24) fanotify06.c:220: FAIL: group 3 got event fanotify06.c:220: FAIL: group 4 got event fanotify06.c:220: FAIL: group 5 got event fanotify06.c:220: FAIL: group 6 got event fanotify06.c:220: FAIL: group 7 got event fanotify06.c:220: FAIL: group 8 got event Summary: passed 9 failed 9 skipped 0 warnings 0 This duplicated event was generated with operations on files with "fake" path. == Fix == * d9899030 (ovl: do not generate duplicate fsnotify events for "fake" path) This patch can be cherry-picked into Disco. Older kernels are not affected by this issue (without commit d1d04ef8) == Test == Test kernel could be found here: https://people.canonical.com/~phlin/kernel/lp-1833028-fanotify06-ovl/ Verified on a KVM node, the fanotify06 test will pass with this patched disco kernel: fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=5997 fd=30 fanotify06.c:147: PASS: group 1 got event: mask 2 pid=5997 fd=30 fanotify06.c:147: PASS: group 2 got event: mask 2 pid=5997 fd=30 fanotify06.c:230: PASS: group 3 got no event fanotify06.c:230: PASS: group 4 got no event fanotify06.c:230: PASS: group 5 got no event fanotify06.c:230: PASS: group 6 got no event fanotify06.c:230: PASS: group 7 got no event fanotify06.c:230: PASS: group 8 got no event == Regression Potential == Low, fix limited to the overlayfs and just corrects the flag behaviour with "fake" path. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: User Name 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 17 04:37 seq crw-rw 1 root audio 116, 33 Jun 17 04:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 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: Mon Jun 17 04:40:18 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-5.0.0-16-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 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:
[Kernel-packages] [Bug 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D
Still visible in Xenial 4.4.0-1118.132 AWS c5.metal ** Tags added: sru-20201109 ** Tags added: aws -- 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/1831043 Title: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-azure source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Bug description: This is a new test case landed 8 days ago, but we already have the patch in B, and it looks like this is not failing across all the nodes: move_pages12.c:114: FAIL: move_pages failed: ENOMEM <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> 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 30 09:29 seq crw-rw 1 root audio 116, 33 May 30 09:29 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: Date: Thu May 30 09:42:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 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/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895276] Re: shmctl04 from ubuntu_ltp_syscalls failed with 4.15
Still visible in Xenial 4.4.0-1118.132 AWS c5.metal ** Tags added: sru-20201109 ** Summary changed: - shmctl04 from ubuntu_ltp_syscalls failed with 4.15 + shmctl04 from ubuntu_ltp_syscalls failed with X-aws / 4.15 ** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895276 Title: shmctl04 from ubuntu_ltp_syscalls failed with X-aws / 4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue spotted with 4.15.0-1054.58~16.04.1-oracle The test case got re-wrote in the upstream https://github.com/linux-test-project/ltp/commit/234b8f200cd80556a4784a3a6b4b073061128c16#diff-c2b2d6e89ea2cd9831c395fbe1bef9f3 Test failed with: startup='Fri Sep 11 07:28:24 2020' tst_test.c:1250: INFO: Timeout per run is 0h 05m 00s shmctl04.c:115: FAIL: SHM_INFO haven't returned a valid index: SUCCESS (0) shmctl04.c:131: FAIL: Counted used = 0, used_ids = 4 shmctl04.c:72: PASS: used_ids = 4 shmctl04.c:79: PASS: shm_rss = 6 shmctl04.c:86: PASS: shm_swp = 0 shmctl04.c:93: PASS: shm_tot = 7 Summary: passed 4 failed 2 skipped 0 warnings 0 tag=shmctl04 stime=1599809304 dur=0 exit=exited stat=1 core=no cu=0 cs=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1895276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904513] Re: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17
*** This bug is a duplicate of bug 1904512 *** https://bugs.launchpad.net/bugs/1904512 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1904512, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1904512 package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904513 Title: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 Status in linux package in Ubuntu: New Bug description: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-95-generic 3.13.0-95.142 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student2551 F pulseaudio Date: Mon Nov 16 22:28:47 2020 DuplicateSignature: package:linux-image-3.13.0-95-generic:3.13.0-95.142:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=3d4ab9a1-2d6d-4b35-87a7-2d89117768f0 InstallationDate: Installed on 2016-09-12 (1526 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 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 MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=4202df25-0bff-4b12-9bc1-a3b8e2bb9925 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.13.0-95-generic 3.13.0-95.142 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: Upgraded to trusty on 2020-11-17 (0 days ago) dmi.bios.date: 02/27/2020 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.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904511] Re: package linux-image-3.13.0-96-generic 3.13.0-96.143 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17
** 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/1904511 Title: package linux-image-3.13.0-96-generic 3.13.0-96.143 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 Status in linux package in Ubuntu: New Bug description: package linux image generic installation error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-96-generic 3.13.0-96.143 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student2551 F pulseaudio Date: Mon Nov 16 22:28:47 2020 DuplicateSignature: package:linux-image-3.13.0-96-generic:3.13.0-96.143:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=3d4ab9a1-2d6d-4b35-87a7-2d89117768f0 InstallationDate: Installed on 2016-09-12 (1526 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 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 MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=4202df25-0bff-4b12-9bc1-a3b8e2bb9925 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.13.0-96-generic 3.13.0-96.143 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: Upgraded to trusty on 2020-11-17 (0 days ago) dmi.bios.date: 02/27/2020 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.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904511/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902179] Comment bridged from LTC Bugzilla
--- Comment From jjhe...@us.ibm.com 2020-11-16 14:19 EDT---
(In reply to comment #60)
> Hi Jan, yes (almost) all Ubuntu packages are hosted nowadays at our
> Launchpad git (at least all packages in main, incl. s390-tools).
> Please see: https://code.launchpad.net/ubuntu/+source/s390-tools
> If you are logged in with a Launchpad account, you will directly see at the
> top a comd-line that allows to clone the package sources, like:
> " Get this repository:
> git clone https://git.launchpad.net/ubuntu/+source/s390-tools "
> If not logged in you'll see a more generic page, but again listing the URLs
> that can be used for cloning, here:
> git://git.launchpad.net/ubuntu/+source/s390-tools
> git+ssh://git.launchpad.net/ubuntu/+source/s390-tools
> https://git.launchpad.net/ubuntu/+source/s390-tools
I've cloned the repo. Which branch should I re-base the patches on? I
was able to find the following likely candidates:
origin/ubuntu/focal
origin/ubuntu/focal-devel
origin/ubuntu/focal-proposed
origin/ubuntu/focal-updates
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in s390-tools source package in Focal:
New
Status in linux source package in Groovy:
Fix Committed
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
In Progress
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
arch/s390/kernel/ipl.c and arch/s390/boot/ipl_parm.c).
[Other]
* The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
"s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
proven to work with groovy.
* New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
parameters".
* The entire set of commits/patches is only new for focal.
* The SRU for SRUing "s390/ipl: support NVMe IPL kernel parameters" to
groovy/20.10
[Kernel-packages] [Bug 1904456] [NEW] [ ASUS Notebook: X556UQK] KB / touch pad do not work
Public bug reported: Simmlar to Bug #1902156 but I have different hardware than the one listed. When I upgraded to 20.10 my keyboard and touchpad no longer work. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thecrazygm 3043 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 16 14:47:10 2020 InstallationDate: Installed on 2020-07-29 (109 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. X556UQK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=34723fa7-8d98-4a00-8500-6aa879b461e2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-13 (3 days ago) dmi.bios.date: 02/10/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UQK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UQK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UQK.308:bd02/10/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX556UQK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UQK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556UQK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1904456 Title: [ ASUS Notebook: X556UQK] KB / touch pad do not work Status in linux package in Ubuntu: Confirmed Bug description: Simmlar to Bug #1902156 but I have different hardware than the one listed. When I upgraded to 20.10 my keyboard and touchpad no longer work. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thecrazygm 3043 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 16 14:47:10 2020 InstallationDate: Installed on 2020-07-29 (109 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. X556UQK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=34723fa7-8d98-4a00-8500-6aa879b461e2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-13 (3 days ago) dmi.bios.date: 02/10/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UQK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UQK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UQK.308:bd02/10/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX556UQK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UQK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556UQK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904456/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904458] [NEW] [linux-azure] Batch hibernate and resume IO requests
Public bug reported:
Microsoft would like to request the following upstream commit in all
releases supported on Azure. This commit improves a signification delay
in hibernation/resume:
55c4478a8f0e("PM: hibernate: Batch hibernate and resume IO requests")
Details of this commit:
Hibernate and resume process submits individual IO requests for each page of
the data, so use blk_plug to improve the batching of these requests.
Testing this change with hibernate and resumes consistently shows
merging of the IO requests and more than an order of magnitude
improvement in hibernate and resume speed is observed.
One hibernate and resume cycle for 16GB RAM out of 32GB in use takes
around 21 minutes before the change, and 1 minutes after the change on a
system with limited storage IOPS.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1904458
Title:
[linux-azure] Batch hibernate and resume IO requests
Status in linux-azure package in Ubuntu:
New
Bug description:
Microsoft would like to request the following upstream commit in all
releases supported on Azure. This commit improves a signification
delay in hibernation/resume:
55c4478a8f0e("PM: hibernate: Batch hibernate and resume IO requests")
Details of this commit:
Hibernate and resume process submits individual IO requests for each page of
the data, so use blk_plug to improve the batching of these requests.
Testing this change with hibernate and resumes consistently shows
merging of the IO requests and more than an order of magnitude
improvement in hibernate and resume speed is observed.
One hibernate and resume cycle for 16GB RAM out of 32GB in use takes
around 21 minutes before the change, and 1 minutes after the change on
a system with limited storage IOPS.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1904458/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
*** This bug is a duplicate of bug 1872159 *** https://bugs.launchpad.net/bugs/1872159 I did it! I have connected AOC both with HDMI and D-SUB VGA cables. Monitor AOC has PIP (picture in picture) option. So, my notebook think that two monitors are connected. And boots ok! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904456] 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/1904456 Title: [ ASUS Notebook: X556UQK] KB / touch pad do not work Status in linux package in Ubuntu: Confirmed Bug description: Simmlar to Bug #1902156 but I have different hardware than the one listed. When I upgraded to 20.10 my keyboard and touchpad no longer work. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thecrazygm 3043 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 16 14:47:10 2020 InstallationDate: Installed on 2020-07-29 (109 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. X556UQK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=34723fa7-8d98-4a00-8500-6aa879b461e2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-13 (3 days ago) dmi.bios.date: 02/10/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UQK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UQK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UQK.308:bd02/10/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX556UQK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UQK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556UQK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904456/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904450] [NEW] Focal update: v5.4.75 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.75 upstream stable release from git://git.kernel.org/ xen/events: avoid removing an event channel while handling it xen/events: add a proper barrier to 2-level uevent unmasking xen/events: fix race in evtchn_fifo_unmask() xen/events: add a new "late EOI" evtchn framework xen/blkback: use lateeoi irq binding xen/netback: use lateeoi irq binding xen/scsiback: use lateeoi irq binding xen/pvcallsback: use lateeoi irq binding xen/pciback: use lateeoi irq binding xen/events: switch user event channels to lateeoi model xen/events: use a common cpu hotplug hook for event channels xen/events: defer eoi in case of excessive number of events xen/events: block rogue events for some time firmware: arm_scmi: Fix ARCH_COLD_RESET firmware: arm_scmi: Add missing Rx size re-initialisation x86/unwind/orc: Fix inactive tasks with stack pointer in %sp on GCC 10 compiled kernels mlxsw: core: Fix use-after-free in mlxsw_emad_trans_finish() RDMA/qedr: Fix memory leak in iWARP CM ata: sata_nv: Fix retrieving of active qcs futex: Fix incorrect should_fail_futex() handling powerpc/powernv/smp: Fix spurious DBG() warning mm: fix exec activate_mm vs TLB shootdown and lazy tlb switching race powerpc: select ARCH_WANT_IRQS_OFF_ACTIVATE_MM sparc64: remove mm_cpumask clearing to fix kthread_use_mm race f2fs: add trace exit in exception path f2fs: fix uninit-value in f2fs_lookup f2fs: fix to check segment boundary during SIT page readahead s390/startup: avoid save_area_sync overflow um: change sigio_spinlock to a mutex f2fs: handle errors of f2fs_get_meta_page_nofail ARM: 8997/2: hw_breakpoint: Handle inexact watchpoint addresses NFS4: Fix oops when copy_file_range is attempted with NFS4.0 source power: supply: bq27xxx: report "not charging" on all types xfs: fix realtime bitmap/summary file truncation when growing rt volume video: fbdev: pvr2fb: initialize variables ath10k: start recovery process when payload length exceeds max htc length for sdio ath10k: fix VHT NSS calculation when STBC is enabled drm/brige/megachips: Add checking if ge_b850v3_lvds_init() is working correctly selftests/x86/fsgsbase: Reap a forgotten child media: videodev2.h: RGB BT2020 and HSV are always full range media: platform: Improve queue set up flow for bug fixing usb: typec: tcpm: During PR_SWAP, source caps should be sent only after tSwapSourceStart media: tw5864: check status of tw5864_frameinterval_get media: imx274: fix frame interval handling mmc: via-sdmmc: Fix data race bug drm/bridge/synopsys: dsi: add support for non-continuous HS clock arm64: topology: Stop using MPIDR for topology information printk: reduce LOG_BUF_SHIFT range for H8300 ia64: kprobes: Use generic kretprobe trampoline handler kgdb: Make "kgdbcon" work properly with "kgdb_earlycon" bpf: Permit map_ptr arithmetic with opcode add and offset 0 media: uvcvideo: Fix dereference of out-of-bound list iterator selftests/bpf: Define string const as global for test_sysctl_prog.c samples/bpf: Fix possible deadlock in xdpsock riscv: Define AT_VECTOR_SIZE_ARCH for ARCH_DLINFO cpufreq: sti-cpufreq: add stih418 support USB: adutux: fix debugging uio: free uio id after uio file node is freed usb: xhci: omit duplicate actions when suspending a runtime suspended host. SUNRPC: Mitigate cond_resched() in xprt_transmit() arm64/mm: return cpu_all_mask when node is NUMA_NO_NODE can: flexcan: disable clocks during stop mode xfs: don't free rt blocks when we're doing a REMAP bunmapi call ACPI: Add out of bounds and numa_off protections to pxm_to_node() brcmfmac: Fix warning message after dongle setup failed drivers/net/wan/hdlc_fr: Correctly handle special skb->protocol values bus/fsl_mc: Do not rely on caller to provide non NULL mc_io ACPI: HMAT: Fix handling of changes from ACPI 6.2 to ACPI 6.3 power: supply: test_power: add missing newlines when printing parameters by sysfs drm/amd/display: HDMI remote sink need mode validation for Linux ARC: [dts] fix the errors detected by dtbs_check btrfs: fix replace of seed device md/bitmap: md_bitmap_get_counter returns wrong blocks bnxt_en: Log unknown link speed appropriately. rpmsg: glink: Use complete_all for open states clk: ti: clockdomain: fix static checker warning net: 9p: initialize sun_server.sun_path to have addr's value only when addr is valid drivers: watchdog: rdc321x_wdt: Fix race condition bugs ext4: Detect already used quota file early KVM: PPC: Book3S HV: Do not allocate HPT for a nested guest gfs2: use-after-free in sysfs deregistration gfs2: add validation
[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
*** This bug is a duplicate of bug 1872159 *** https://bugs.launchpad.net/bugs/1872159 Have made some tests. And have found that this bug does not exists with ViewSonic VP191s monitor connected to HDMI. If I connect AOC Style U2879VF to HDMI, then my notebook stay with black screen and can't boot. Else if I connect both monitors (ViewSonic to VGA SUB, AOC to HDMI), the notebook boot ok. Does this mean the problem is in a monitor, not in 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
