[Kernel-packages] [Bug 1942633] Re: Can not boot impish in Cavium ThunderX
5.14.0-9.9 exhibits kernel stack corruption on boot. ** Attachment added: "phanpy.bootlog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+attachment/5524292/+files/phanpy.bootlog -- 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/1942633 Title: Can not boot impish in Cavium ThunderX Status in linux package in Ubuntu: Confirmed Bug description: Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic 5.11.7) in arm64 description: Computer product: Cavium ThunderX CN88XX board width: 64 bits I tried 2 releases: - 20210817 ( https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/ga-21.10/ ) - 20210830 ( https://images.maas.io/ephemeral-v3/candidate/impish/arm64/20210830/ ) 20210817: Ends the deploy successfully but fails to boot from disk: ``` [0.00] Booting Linux on physical CPU 0x00 [0x431f0a11] [0.00] Linux version 5.13.0-14-generic (buildd@bos02-arm64-018) (gcc (Ubuntu 10.3.0-6ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #14-Ubuntu SMP Mon Aug 2 12:40:58 UTC 2021 (Ubuntu 5.13.0-14.14-generic 5.13.1) [0.00] Machine model: Cavium ThunderX CN88XX board [ 139.896752] raid6: xor() 1224 MB/s, rmw enabled [ 139.957046] raid6: using neon recovery algorithm [ 140.020937] xor: measuring software checksum speed [ 140.085571]8regs : 2432 MB/sec [ 140.149834]32regs : 2687 MB/sec [ 140.212202]arm64_neon : 4390 MB/sec [ 140.271985] xor: using function: arm64_neon (4390 MB/sec) [ 140.335013] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 140.569847] Btrfs loaded, crc32c=crc32c-generic, zoned=yes Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. ``` 20210830 Fails the network boot: ``` [ 140.351066] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... cloud-initramfs-dyn-netconf: did no find a nic with 1c:1b:0d:0d:52:7c done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Waiting up to 180 secs for BOOTIF to become available ... Failure: Interface BOOTIF did not appear in time done. ipconfig: BOOTIF: SIOCGIFINDEX: No such device ipconfig: no devices to configure ``` I will attach full logs of each try. JFYI, this is the same machine as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942427] Re: [Lenovo Thunderbolt 3 Dock] Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915
What was the last working kernel version? ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1942427 Title: [Lenovo Thunderbolt 3 Dock] Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915 Status in linux package in Ubuntu: Incomplete Bug description: upgrading to latest packages, my setup with 3 displays (internal plus 2 external, plugged into Lenovo USB-c base station) no longer works. the Settings -> Displays app does find all displays, but the system only displays on the internal one. Attempting to enable all displays fails, the third disappears from view in the Displays app just before it presents the "Keep settings" dialog. However no output appears on any of the external displays other than the display's own firmware messages. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Thu Sep 2 10:54:09 2021 DistUpgraded: 2021-06-14 13:24:54,764 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-08-13 (384 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20L6S30S00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-14 (79 days ago) dmi.bios.date: 08/10/2020 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET60W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S30S00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN24ET60W(1.35):bd08/10/2020:br1.35:efr1.20:svnLENOVO:pn20L6S30S00:pvrThinkPadT480:rvnLENOVO:rn20L6S30S00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S30S00 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943079] Re: Installing latest linux-firmware (1.187.16) causes wifi interface to disappear
So it's Intel AX210. Can you please also attach dmesg here? Thanks! -- 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/1943079 Title: Installing latest linux-firmware (1.187.16) causes wifi interface to disappear Status in linux-firmware package in Ubuntu: New Bug description: Summary === Installing linux-firmware 1.187.16, which became available on 17th Aug 2021, caused my wifi interface to disappear after reboot. My machine: Lenovo T15 Gen2 CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 I tried force installing previous version 1.187.15, but that version isn't available! So, in the end, I rebooted into a live CD and re-installed the OS! In the newly installed OS, I just made sure to NOT select linux- firmware package in the list of available upgrades, and I will stick with version 1.187.15 till I have confidence there is better and working version. NOTE: On an older machine, with an older chipset, I did NOT experience this issue. Older machine: Lenovo x230 CPU: Intel(R) Core(TM) i5-3210M CPU Wifi: Centrino Advanced-N 6205 System == I'm running Linux Mint Edge, based on Ubuntu 20.04, but with upgraded kernel (5.11.0.34): lsb_release -rd Description: Linux Mint 20.2 Release: 20.2 Package === apt-cache policy linux-firmware linux-firmware: Installed: 1.187.16 Candidate: 1.187.16 Version table: *** 1.187.16 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages Expected Upgrade to linux-firmware=1.187.16 Reboot. Wifi network Interface must continue to be available and functioning. What Happened = Upgrade to linux-firmware=1.187.16 Reboot. Wifi network interface disappeared. Therefore, cannot use wifi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1943079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942427] Re: [Lenovo Thunderbolt 3 Dock] Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915
I would urge you to reconsider the importance of this bug. This change broke a working setup, with no apparent user-visible workaround available. -- 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/1942427 Title: [Lenovo Thunderbolt 3 Dock] Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915 Status in linux package in Ubuntu: Confirmed Bug description: upgrading to latest packages, my setup with 3 displays (internal plus 2 external, plugged into Lenovo USB-c base station) no longer works. the Settings -> Displays app does find all displays, but the system only displays on the internal one. Attempting to enable all displays fails, the third disappears from view in the Displays app just before it presents the "Keep settings" dialog. However no output appears on any of the external displays other than the display's own firmware messages. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Thu Sep 2 10:54:09 2021 DistUpgraded: 2021-06-14 13:24:54,764 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-08-13 (384 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20L6S30S00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-14 (79 days ago) dmi.bios.date: 08/10/2020 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET60W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S30S00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN24ET60W(1.35):bd08/10/2020:br1.35:efr1.20:svnLENOVO:pn20L6S30S00:pvrThinkPadT480:rvnLENOVO:rn20L6S30S00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S30S00 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921643] Re: Thunderbolt docking station drops USB
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB Status in linux package in Ubuntu: Expired Bug description: My Lenovo Thunderbolt Dock Gen2 randomly drops the USB controller, resulting in no USB at all. It sometimes happens after a few seconds of being plugged in to the notebook, but sometimes it works for hours. The display connected to the dock stays active and working. I tried to blacklist the driver (r8152) for the usb3-ethernet controller, as suggested in a few forums, but it does not solve the issue. dmesg is full of the following messages: [ 1001.028336] xhci_hcd :08:00.0: WARN Event TRB for slot 11 ep 1 with no TDs queued? [ 1001.029304] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1 comp_code 1 [ 1001.029324] xhci_hcd :08:00.0: Looking for event-dma 00087785b460 trb-start 00087785b540 trb-end 00087785b540 seg-start 00087785b000 seg-end 00087785bff0 I'm running ubuntu 20.10, but it also happened under 20.04. Everything is up to date as of writing this bugreport. The dock is running the latest firmware, but the issue was present with earlier version of the firmware too. I also tried both thunderbolt ports on the notebook (MSI Prestige 15), the issue happens on both. The dock works flawlessly under windows 10. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.8.0-48-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: viktor 1021 F pulseaudio /dev/snd/controlC0: viktor 1021 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-06-05 (306 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-48-generic N/A linux-backports-modules-5.8.0-48-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2019 dmi.bios.release: 1.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16S3IMS.108 dmi.board.asset.tag: Default string dmi.board.name: MS-16S3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: Prestige dmi.product.name: Prestige 15 A10SC dmi.product.sku: 16S3.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939528] Re: Need support of Qualcomm WCN6856
** Tags added: originate-from-1936917 stella
--
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/1939528
Title:
Need support of Qualcomm WCN6856
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-firmware package in Ubuntu:
New
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-firmware source package in Focal:
Incomplete
Status in linux-oem-5.13 source package in Focal:
Incomplete
Status in linux source package in Hirsute:
Won't Fix
Status in linux-firmware source package in Hirsute:
New
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Incomplete
Status in linux-firmware source package in Impish:
New
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Qualcomm WCN6856 not supported yet.
[Fix]
Upstream fixes in thread
https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/
has been merged in mainline starting from commit 755b1f73173e ("ath11k:
add hw reg support for WCN6855").
[Test Case]
TBD.
[Where problems could occur]
While this introduces a new hardware, it might need further polishments.
== original bug report ==
Wireless Driver support: PCI\VEN_17CB&DEV_1103&SUBSYS_E0B8105B&REV_01
BT driver support: USB\VID_0489&PID_E0C9&REV_0001
Wireless Driver support: PCI\VEN_17CB&DEV_1103&REV_01
BT driver support: USB\VID_0489&PID_E0CC&REV_0001
https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/
Already landed to mainline kernel v5.14-rc1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1939528/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943154] Re: My resolution has changed to 800x600 , it was in higher than 1000 I dont know the exact no
Thanks for the bug report. The attached Xorg logs appear to be from before the bug as they show a resolution of 1600x900. But I can also see that your current resolution is 800x600 in Xrandr.txt. It seems Xorg now can't even tell what kind of monitor connection it is. Please try booting an older kernel by accessing the grub menu (press Esc at startup). Do you find older kernel versions avoid the problem? Please also try unplugging and reconnecting the monitor. ** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu) ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Incomplete ** Summary changed: - My resolution has changed to 800x600 , it was in higher than 1000 I dont know the exact no + [i915] My resolution has changed to 800x600, it was 1600x900 before -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943154 Title: [i915] My resolution has changed to 800x600, it was 1600x900 before Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: My resolution has suddenly changed from a higher resolution from to low resolution to 800x600 and it is now showing only one resolution option ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 20:32:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2042] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=78d7ef17-370f-42ec-839a-ad90938c65fb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: HOH6110H.86A.0010.2012.0424.1632 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61HO dmi.board.vendor: Intel Corporation dmi.board.version: AAG62445-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrHOH6110H.86A.0010.2012.0424.1632:bd04/24/2012:svn:pn:pvr:sku:rvnIntelCorporation:rnDH61HO:rvrAAG62445-102:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943154] [NEW] My resolution has changed to 800x600 , it was in higher than 1000 I dont know the exact no
You have been subscribed to a public bug: My resolution has suddenly changed from a higher resolution from to low resolution to 800x600 and it is now showing only one resolution option ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 20:32:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2042] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=78d7ef17-370f-42ec-839a-ad90938c65fb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: HOH6110H.86A.0010.2012.0424.1632 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61HO dmi.board.vendor: Intel Corporation dmi.board.version: AAG62445-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrHOH6110H.86A.0010.2012.0424.1632:bd04/24/2012:svn:pn:pvr:sku:rvnIntelCorporation:rnDH61HO:rvrAAG62445-102:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal ubuntu -- My resolution has changed to 800x600 , it was in higher than 1000 I dont know the exact no https://bugs.launchpad.net/bugs/1943154 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 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 1943197] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524235/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524240/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524246/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524236/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524243/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524237/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524244/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524245/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524232/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524234/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524239/+files/ProcEnviron.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/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524241/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524242/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] Re: Ubuntu unusable with new kernel. pciehp: Failed to check link status
Sorry, I have run the command apport-collect 1943197 under the working BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic and not the unusable vmlinuz-5.4.0-84-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524238/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524233/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524231/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] Re: Ubuntu unusable with new kernel. pciehp: Failed to check link status
apport information ** Tags added: apport-collected ** Description changed: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present - I have Ubuntu 20.04.3 LTS. The relevant package might be linux- - image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux- - modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules- - extra-5.4.0-84-generic (5.4.0-84.94). + I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.18 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: a 2004 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader + Bus 001 Device 003: ID 8087:0a2b Intel Corp. + Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: HP HP ProBook 450 G5 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-81-generic N/A + linux-backports-modules-5.4.0-81-generic N/A + linux-firmware1.187.16 + Tags: focal + Uname: Linux 5.4.0-81-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark + _MarkForUpload: True + dmi.bios.date: 05/23/2018 + dmi.bios.vendor: HP + dmi.bios.version: Q85 Ver. 01.02.07 + dmi.board.name: 837D + dmi.board.vendor: HP + dmi.board.version: KBC Version 02.2A.00 + dmi.chassis.type: 10 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: + dmi.product.family: HP ProBook + dmi.product.name: HP ProBook 450 G5 + dmi.product.sku: 3KY96EA#ABD + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524229/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bi
[Kernel-packages] [Bug 1943197] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1943197/+attachment/5524230/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Confirmed Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943130] Re: Nvidia drivers info
Please collect logs from the failed boots of the 470 driver by running: journalctl -b-1 > prevboot-1.txt journalctl -b-2 > prevboot-2.txt journalctl -b-3 > prevboot-3.txt journalctl -b-4 > prevboot-4.txt journalctl -b-5 > prevboot-5.txt and attach the resulting text files here. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-470 (Ubuntu) ** Also affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Nvidia drivers info + PC doesn't send signal to the second monitor ** Summary changed: - PC doesn't send signal to the second monitor + [nvidia] PC doesn't send signal to the second monitor ** Tags added: nvidia ** Summary changed: - [nvidia] PC doesn't send signal to the second monitor + [nvidia] PC doesn't send signal to the second monitor using nvidia-470 (but nvidia-460 works) ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1943130 Title: [nvidia] PC doesn't send signal to the second monitor using nvidia-470 (but nvidia-460 works) Status in linux-hwe-5.11 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: After turn on mu PC, it doesn't send signal to the second monitor. (with driver "nvidia-driver-470(proprietary tested)" After change it to: "nvidia-driver-460(proprietary)" problem solved. Looks like new kernel update have conflict with nvidia - 470 driver. (because yesterday it was fine but today is broken, and made me to change the driver) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..2b.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 15:15:39 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.91.03, 5.11.0-34-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:2208] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8803] InstallationDate: Installed on 2021-08-31 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Micro-Star International Co., Ltd. MS-7C91 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=1bb75479-3578-4389-a29e-40823860bbbc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 05/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG B550 TOMAHAWK (MS-7C91) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.60:bd05/12/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C91:pvr2.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMAGB550TOMAHAWK(MS-7C91):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C91 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx
[Kernel-packages] [Bug 1943130] [NEW] Nvidia drivers info
You have been subscribed to a public bug: After turn on mu PC, it doesn't send signal to the second monitor. (with driver "nvidia-driver-470(proprietary tested)" After change it to: "nvidia-driver-460(proprietary)" problem solved. Looks like new kernel update have conflict with nvidia - 470 driver. (because yesterday it was fine but today is broken, and made me to change the driver) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..2b.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 15:15:39 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.91.03, 5.11.0-34-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:2208] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8803] InstallationDate: Installed on 2021-08-31 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Micro-Star International Co., Ltd. MS-7C91 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=1bb75479-3578-4389-a29e-40823860bbbc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 05/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG B550 TOMAHAWK (MS-7C91) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.60:bd05/12/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C91:pvr2.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMAGB550TOMAHAWK(MS-7C91):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C91 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Nvidia drivers info https://bugs.launchpad.net/bugs/1943130 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] 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 1943197 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Incomplete Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] Re: Ubuntu unusable with new kernel. pciehp: Failed to check link status
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 1943197 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943197 Title: Ubuntu unusable with new kernel. pciehp: Failed to check link status Status in linux package in Ubuntu: Incomplete Bug description: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux-image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux-modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules-extra-5.4.0-84-generic (5.4.0-84.94). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2004 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-10 (1126 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 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b5ee Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=40b1c187-6c37-4f0e-9d28-bae411740f85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: focal Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.02.07 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.02.07:bd05/23/2018:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr: dmi.product.family: HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 3KY96EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943197] [NEW] Ubuntu unusable with new kernel. pciehp: Failed to check link status
You have been subscribed to a public bug: Up to linux-image-5.4.0-81-generic Ubuntu was working normally. With the new image linux-image-5.4.0-84-generic Ubuntu starts very slow, with very high GPU use and the gnome login window actually never comes up. (The colored screen comes up after some time, but stays without name etc.) If I switch to the console, this is inundated by the message: pcieport :00:1d.3: pciehp: Failed to check link status This makes the console unusable too. In the kernel log I find two more lines which might be relevant: pcieport :00:1d.3: Data Link Layer Link Active not set in 1000 msec pcieport :00:1d.3: pciehp: Failed to check link status pcieport :00:1d.3: pciehp: Slot(11): Card present I have Ubuntu 20.04.3 LTS. The relevant package might be linux- image-5.4.0-84-generic (5.4.0-84.94), but it could also be linux- modules-5.4.0-84-generic (5.4.0-84.94) or linux-modules- extra-5.4.0-84-generic (5.4.0-84.94). ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Ubuntu unusable with new kernel. pciehp: Failed to check link status https://bugs.launchpad.net/bugs/1943197 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 1941955] Re: New upstream release 2021.08.28
$ dpkg-query -W wireless-regdb wireless-regdb 2021.08.28-0ubuntu1~18.04.1 $ iw reg get global country 00: DFS-UNSET (2402 - 2472 @ 40), (6, 20), (N/A) (2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) $ sudo iw reg set US $ iw reg get global country US: DFS-FCC (2400 - 2472 @ 40), (N/A, 30), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN (57240 - 71000 @ 2160), (N/A, 40), (N/A) ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1941955 Title: New upstream release 2021.08.28 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Hirsute: Fix Committed Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941955] Re: New upstream release 2021.08.28
$ dpkg-query -W wireless-regdb wireless-regdb 2021.08.28-0ubuntu1~20.04.1 $ iw reg get global country 00: DFS-UNSET (2402 - 2472 @ 40), (6, 20), (N/A) (2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) $ sudo iw reg set US $ iw reg get global country US: DFS-FCC (2400 - 2472 @ 40), (N/A, 30), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN (57240 - 71000 @ 2160), (N/A, 40), (N/A) ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1941955 Title: New upstream release 2021.08.28 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Hirsute: Fix Committed Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941955] Re: New upstream release 2021.08.28
$ dpkg-query -W wireless-regdb wireless-regdb 2021.08.28-0ubuntu1~21.04.1 $ iw reg get global country 00: DFS-UNSET (2402 - 2472 @ 40), (6, 20), (N/A) (2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) $ sudo iw reg set US $ iw reg get global country US: DFS-FCC (2400 - 2472 @ 40), (N/A, 30), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN (57240 - 71000 @ 2160), (N/A, 40), (N/A) ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1941955 Title: New upstream release 2021.08.28 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Hirsute: Fix Committed Status in wireless-regdb source package in Impish: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942952] Re: Kernel Call Trace on Secure Boot
I disabled Secure Boot and same problem. Seems to happen reliably on cold boots. ** Attachment added: "dmesg with Secure Boot disabled" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942952/+attachment/5524215/+files/dmesg.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/1942952 Title: Kernel Call Trace on Secure Boot Status in linux package in Ubuntu: Confirmed Bug description: Could the call traces in dmesg be related to UEFI secure boot? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js1 948 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Sep 7 21:05:54 2021 InstallationDate: Installed on 2021-09-06 (1 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M |__ Port 8: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-34-generic root=/dev/mapper/vgkubuntu-root ro ipv6.disable=1 elevator=deadline splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 15.63 dmi.bios.vendor: Insyde dmi.bios.version: F.63 dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 76.32 dmi.modalias: dmi:bvnInsyde:bvrF.63:bd03/25/2021:br15.63:efr76.32:svnHP:pn:pvr:sku:rvnHP:rn84B6:rvrKBCVersion76.32:cvnHP:ct10:cvrChassisVersion: dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943185] Re: Fix AMD GPIO-based power button
** Description changed: [Impact] - Power button or other wake up sources connected to GPIO may not wake up + Power button or other wake up sources connected to GPIO may not wake up idle AMD systems. [Fix] - Enable and disable power management wakeup mode, which is disabled by - default, accordingly + Enable and disable power management wakeup mode, which is disabled by + default, accordingly. + + The patch series can be found @ https://lore.kernel.org/linux- + gpio/20210831120613.1514899-1-basavaraj.nati...@amd.com/ [Test] - This is requested by AMD. + This is requested by AMD. [Where problems could occur] - Only AMD systems that require GPIOs as wake sources will be affected, + Only AMD systems that require GPIOs as wake sources will be affected, i.e. amd_gpio_irq_set_wake with "on != 0", but this is intended - behaviours. + behaviour. -- 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/1943185 Title: Fix AMD GPIO-based power button Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Power button or other wake up sources connected to GPIO may not wake up idle AMD systems. [Fix] Enable and disable power management wakeup mode, which is disabled by default, accordingly. The patch series can be found @ https://lore.kernel.org/linux- gpio/20210831120613.1514899-1-basavaraj.nati...@amd.com/ [Test] This is requested by AMD. [Where problems could occur] Only AMD systems that require GPIOs as wake sources will be affected, i.e. amd_gpio_irq_set_wake with "on != 0", but this is intended behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1943185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943185] Re: Fix AMD GPIO-based power button
** Tags added: amd oem-priority originate-from-1942219 -- 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/1943185 Title: Fix AMD GPIO-based power button Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Power button or other wake up sources connected to GPIO may not wake up idle AMD systems. [Fix] Enable and disable power management wakeup mode, which is disabled by default, accordingly. The patch series can be found @ https://lore.kernel.org/linux- gpio/20210831120613.1514899-1-basavaraj.nati...@amd.com/ [Test] This is requested by AMD. [Where problems could occur] Only AMD systems that require GPIOs as wake sources will be affected, i.e. amd_gpio_irq_set_wake with "on != 0", but this is intended behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1943185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943185] 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 1943185 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/1943185 Title: Fix AMD GPIO-based power button Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Power button or other wake up sources connected to GPIO may not wake up idle AMD systems. [Fix] Enable and disable power management wakeup mode, which is disabled by default, accordingly [Test] This is requested by AMD. [Where problems could occur] Only AMD systems that require GPIOs as wake sources will be affected, i.e. amd_gpio_irq_set_wake with "on != 0", but this is intended behaviours. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1943185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943185] [NEW] Fix AMD GPIO-based power button
Public bug reported: [Impact] Power button or other wake up sources connected to GPIO may not wake up idle AMD systems. [Fix] Enable and disable power management wakeup mode, which is disabled by default, accordingly [Test] This is requested by AMD. [Where problems could occur] Only AMD systems that require GPIOs as wake sources will be affected, i.e. amd_gpio_irq_set_wake with "on != 0", but this is intended behaviours. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Alex Hung (alexhung) Status: Incomplete ** Tags: amd oem-priority originate-from-1942219 ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alex Hung (alexhung) -- 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/1943185 Title: Fix AMD GPIO-based power button Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Power button or other wake up sources connected to GPIO may not wake up idle AMD systems. [Fix] Enable and disable power management wakeup mode, which is disabled by default, accordingly [Test] This is requested by AMD. [Where problems could occur] Only AMD systems that require GPIOs as wake sources will be affected, i.e. amd_gpio_irq_set_wake with "on != 0", but this is intended behaviours. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1943185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870975] Re: [Dell Inspiron 5570] No audio devices appear except "Dummy Output" after I close my laptop lid while audio is playing and then open it back up.
** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5361003/+files/WifiSyslog.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360989/+files/CRDA.txt ** Information type changed from Public to Private ** Attachment removed: "Image of Audio Settings Menu" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5347299/+files/Screenshot%20from%202020-04-05%2014-51-31.png ** Attachment removed: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5349980/+files/journalctl.log ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Invalid => Confirmed ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5347300/+files/Dependencies.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5347301/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360990/+files/CurrentDmesg.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360999/+files/ProcModules.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5361000/+files/PulseList.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360992/+files/IwConfig.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5361002/+files/UdevDb.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360991/+files/Dependencies.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360988/+files/AlsaInfo.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5361001/+files/RfKill.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360998/+files/ProcInterrupts.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360993/+files/Lspci.txt ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Attachment removed: "Lspci-vt.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360994/+files/Lspci-vt.txt ** Attachment removed: "Lsusb-v.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360996/+files/Lsusb-v.txt ** Attachment removed: "Lsusb-t.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360995/+files/Lsusb-t.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360997/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870975 Title: [Dell Inspiron 5570] No audio devices appear except "Dummy Output" after I close my laptop lid while audio is playing and then open it back up. Status in alsa-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: When I closed my laptop lid while sound was playing in Audacity and then opened the lid back up, the device woke up from sleep. However, my headphones were plugged in at the time, and Ubuntu acted as if the audio resumed. However, I was not hearing audio. So I went to the Audio section of Settings and found there was only one sound device: Dummy Device, instead of seeing the speakers built into the laptop and the headphones. Description: Ubuntu 18.04.4 LTS Release: 18.04 I am forced to reboot my machine as a workaround. gnome-control-center: Installed: 1:3.28.2-0ubuntu0.18.04.6 Candidate: 1:3.28.2-0ubuntu0.18.04.6 Version table: *** 1:3.28.2-0ubuntu0.18.04.6 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.28.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2
[Kernel-packages] [Bug 1847340] Re: ext4 journal recovery fails w/ data=journal + mmap
Patches posted for SRU. [B/F][PATCH 0/5] ext4/jbd2: data=journal: write-protect pages on transaction commit https://lists.ubuntu.com/archives/kernel-team/2021-September/123963.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847340 Title: ext4 journal recovery fails w/ data=journal + mmap Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Bug description: [Impact] With mmap()ed files on ext4's data journaling it's possible to change a mapped page's buffers contents during their jbd2 transaction commit (as currently nothing prevents/blocks the write access at that time.) This might happen between the buffers checksum calculation and actual write to journal, so the (old) checksum is invalid for the (new) data. If the system crashes after that, but before such journal entry makes it to the filesystem, the journal replay on the next mount just fails, and the filesystem now requires fsck. (apparently curtin might set up /etc/fstab with passno=0, requiring manual intervention.) [39751.096455] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! [39751.114435] JBD2: Invalid checksum recovering block 87305 in log [39751.146133] JBD2: Invalid checksum recovering block 88039 in log [39751.195950] JBD2: Invalid checksum recovering block 49633 in log [39751.265158] JBD2: recovery failed [39751.265163] EXT4-fs (vdc): error loading journal [Fix] The fix is to write-protect the pages during journal transaction commit, so that writes to mapped pages hit a page fault, then ext4's page_mkwrite hook can block until the commit finishes and the buffers can be modified. In order to do that, add jbd2 journal callbacks that the filesystems can customize, called before/after the critical region in transaction commit, then have ext4 in data journaling mode to write-protect the pages whose buffers are being committed (and handle cases that need pages redirtied.) The changes are restricted to the data journaling mode and page_mkwrite hook, and other modes/paths use the same code/behavior in the callbacks. [Test Case] Set up an ext4 filesystem in data journaling mode, and run stress-ng's mmap file test on it, then crash the system after a bit; check whether the filesystem can mount again or not (i.e., with jbd2 checksum errors.) # mkfs.ext4 $DEV # mount -o data=journal $DEV $DIR # cd $DIR # stress-ng --mmap $((4*$(nproc))) --mmap-file & # sleep 60 # echo c >/proc/sysrq-trigger ... # mount -o data=journal $DEV $DIR # PASS/FAIL. # dmesg | tail [Regression Potential] Regressions would likely manifest in ext4 data journaling mode (which is not the default mode, 'ordered') with memory mapped access, as the other modes/paths are largely unaffected by the changes/same behavior. This has been tested with (x)fstests, that showed no regressions on data=ordered and data=journal on both Bionic and Focal (with kernel versions 4.15.0-156-generic and 5.4.0-84-generic) w/in 10 runs each. And the stress-ng test-case as well. (Numbers/details in the LP bug.) [Other info] The patchset is applied on 5.10, so Hirsute (5.11) is already fixed; only Focal and Bionic need it. There are little changes in the patches between Focal and Bionic (mostly minor backport adjustments, mainly due to no vm_fault_t) but unfortunately that needs separate versions for most patches. ... [Original Bug Description] [Impact] In the event of a loss of power, ext4 filesystems mounted w/ data=journal,journal_checksum are subject to a corruption issue that requires a fsck to recover. This is exacerbated by installations by curtin that set passno=0 in /etc/fstab, preventing fsck from running automatically and thus requiring a manual recovery. And *that* is further exacerbated because initramfs-tools is smart enough to not include fsck.ext4 when passno=0 is detected in /etc/fstab, requiring the user to boot from recovery media. [Test Case] Forcibly power cycle a system running 'stress-ng --dir 0'. I've created a package to automate the reproduction: https://git.launchpad.net/~dannf/+git/dgx2-ext4-csum-repro?h=master [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://he
[Kernel-packages] [Bug 1855628] Re: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep
** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310885/+files/Dependencies.txt ** Attachment removed: "NetDevice.enp4s0.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310888/+files/NetDevice.enp4s0.txt ** Attachment removed: "NetDevice.lo.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310889/+files/NetDevice.lo.txt ** Attachment removed: "NetDevice.wlp3s0.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310890/+files/NetDevice.wlp3s0.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310893/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350595/+files/AlsaInfo.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350597/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350598/+files/Dependencies.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350600/+files/IwConfig.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350601/+files/Lspci.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350612/+files/UdevDb.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350611/+files/RfKill.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350610/+files/PulseList.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350609/+files/ProcModules.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350608/+files/ProcInterrupts.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350607/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "NetDevice.wlp2s0.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350604/+files/NetDevice.wlp2s0.txt ** Attachment removed: "NetDevice.lo.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350603/+files/NetDevice.lo.txt ** Attachment removed: "NetDevice.enp1s0.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350602/+files/NetDevice.enp1s0.txt ** Description changed: - Whenever I wake the computer up from sleep, the computer no longer - connects to the Internet without my having to go into Settings and turn - Wi-Fi off and then back on again. - - Please address this issue. - - Thank you! - - network-manager: - Installed: 1.10.6-2ubuntu1.2 - Candidate: 1.10.6-2ubuntu1.2 - Version table: - *** 1.10.6-2ubuntu1.2 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1.10.6-2ubuntu1.1 500 - 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages - 1.10.6-2ubuntu1 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - - Description: Ubuntu 18.04.3 LTS - Release: 18.04 - - ProblemType: Bug - DistroRelease: Ubuntu 18.04 - Package: network-manager 1.10.6-2ubuntu1.2 - ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 - Uname: Linux 5.0.0-37-generic x86_64 - ApportVersion: 2.20.9-0ubuntu7.9 - Architecture: amd64 - CurrentDesktop: ubuntu:GNOME - Date: Sun Dec 8 19:51:31 2019 - IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback - IpRoute: - default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 - 169.254.0.0/16 dev wlp3s0 scope link metric 1000 - 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 - NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash - RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no - SourcePackage: network-manager - UpgradeStatus: No upgrade log present (probably fresh install) - nmcli-con: - NAMEUUID TYPE TIM
[Kernel-packages] [Bug 1847340] Re: ext4 journal recovery fails w/ data=journal + mmap
** Summary changed: - ext4 journal recovery fails w/ data=journal + journal_checksum + mmap + ext4 journal recovery fails w/ data=journal + mmap -- 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/1847340 Title: ext4 journal recovery fails w/ data=journal + mmap Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Bug description: [Impact] With mmap()ed files on ext4's data journaling it's possible to change a mapped page's buffers contents during their jbd2 transaction commit (as currently nothing prevents/blocks the write access at that time.) This might happen between the buffers checksum calculation and actual write to journal, so the (old) checksum is invalid for the (new) data. If the system crashes after that, but before such journal entry makes it to the filesystem, the journal replay on the next mount just fails, and the filesystem now requires fsck. (apparently curtin might set up /etc/fstab with passno=0, requiring manual intervention.) [39751.096455] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! [39751.114435] JBD2: Invalid checksum recovering block 87305 in log [39751.146133] JBD2: Invalid checksum recovering block 88039 in log [39751.195950] JBD2: Invalid checksum recovering block 49633 in log [39751.265158] JBD2: recovery failed [39751.265163] EXT4-fs (vdc): error loading journal [Fix] The fix is to write-protect the pages during journal transaction commit, so that writes to mapped pages hit a page fault, then ext4's page_mkwrite hook can block until the commit finishes and the buffers can be modified. In order to do that, add jbd2 journal callbacks that the filesystems can customize, called before/after the critical region in transaction commit, then have ext4 in data journaling mode to write-protect the pages whose buffers are being committed (and handle cases that need pages redirtied.) The changes are restricted to the data journaling mode and page_mkwrite hook, and other modes/paths use the same code/behavior in the callbacks. [Test Case] Set up an ext4 filesystem in data journaling mode, and run stress-ng's mmap file test on it, then crash the system after a bit; check whether the filesystem can mount again or not (i.e., with jbd2 checksum errors.) # mkfs.ext4 $DEV # mount -o data=journal $DEV $DIR # cd $DIR # stress-ng --mmap $((4*$(nproc))) --mmap-file & # sleep 60 # echo c >/proc/sysrq-trigger ... # mount -o data=journal $DEV $DIR # PASS/FAIL. # dmesg | tail [Regression Potential] Regressions would likely manifest in ext4 data journaling mode (which is not the default mode, 'ordered') with memory mapped access, as the other modes/paths are largely unaffected by the changes/same behavior. This has been tested with (x)fstests, that showed no regressions on data=ordered and data=journal on both Bionic and Focal (with kernel versions 4.15.0-156-generic and 5.4.0-84-generic) w/in 10 runs each. And the stress-ng test-case as well. (Numbers/details in the LP bug.) [Other info] The patchset is applied on 5.10, so Hirsute (5.11) is already fixed; only Focal and Bionic need it. There are little changes in the patches between Focal and Bionic (mostly minor backport adjustments, mainly due to no vm_fault_t) but unfortunately that needs separate versions for most patches. ... [Original Bug Description] [Impact] In the event of a loss of power, ext4 filesystems mounted w/ data=journal,journal_checksum are subject to a corruption issue that requires a fsck to recover. This is exacerbated by installations by curtin that set passno=0 in /etc/fstab, preventing fsck from running automatically and thus requiring a manual recovery. And *that* is further exacerbated because initramfs-tools is smart enough to not include fsck.ext4 when passno=0 is detected in /etc/fstab, requiring the user to boot from recovery media. [Test Case] Forcibly power cycle a system running 'stress-ng --dir 0'. I've created a package to automate the reproduction: https://git.launchpad.net/~dannf/+git/dgx2-ext4-csum-repro?h=master [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847340] Re: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap
** Attachment added: "test-loop.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+attachment/5524208/+files/test-loop.sh -- 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/1847340 Title: ext4 journal recovery fails w/ data=journal + mmap Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Bug description: [Impact] With mmap()ed files on ext4's data journaling it's possible to change a mapped page's buffers contents during their jbd2 transaction commit (as currently nothing prevents/blocks the write access at that time.) This might happen between the buffers checksum calculation and actual write to journal, so the (old) checksum is invalid for the (new) data. If the system crashes after that, but before such journal entry makes it to the filesystem, the journal replay on the next mount just fails, and the filesystem now requires fsck. (apparently curtin might set up /etc/fstab with passno=0, requiring manual intervention.) [39751.096455] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! [39751.114435] JBD2: Invalid checksum recovering block 87305 in log [39751.146133] JBD2: Invalid checksum recovering block 88039 in log [39751.195950] JBD2: Invalid checksum recovering block 49633 in log [39751.265158] JBD2: recovery failed [39751.265163] EXT4-fs (vdc): error loading journal [Fix] The fix is to write-protect the pages during journal transaction commit, so that writes to mapped pages hit a page fault, then ext4's page_mkwrite hook can block until the commit finishes and the buffers can be modified. In order to do that, add jbd2 journal callbacks that the filesystems can customize, called before/after the critical region in transaction commit, then have ext4 in data journaling mode to write-protect the pages whose buffers are being committed (and handle cases that need pages redirtied.) The changes are restricted to the data journaling mode and page_mkwrite hook, and other modes/paths use the same code/behavior in the callbacks. [Test Case] Set up an ext4 filesystem in data journaling mode, and run stress-ng's mmap file test on it, then crash the system after a bit; check whether the filesystem can mount again or not (i.e., with jbd2 checksum errors.) # mkfs.ext4 $DEV # mount -o data=journal $DEV $DIR # cd $DIR # stress-ng --mmap $((4*$(nproc))) --mmap-file & # sleep 60 # echo c >/proc/sysrq-trigger ... # mount -o data=journal $DEV $DIR # PASS/FAIL. # dmesg | tail [Regression Potential] Regressions would likely manifest in ext4 data journaling mode (which is not the default mode, 'ordered') with memory mapped access, as the other modes/paths are largely unaffected by the changes/same behavior. This has been tested with (x)fstests, that showed no regressions on data=ordered and data=journal on both Bionic and Focal (with kernel versions 4.15.0-156-generic and 5.4.0-84-generic) w/in 10 runs each. And the stress-ng test-case as well. (Numbers/details in the LP bug.) [Other info] The patchset is applied on 5.10, so Hirsute (5.11) is already fixed; only Focal and Bionic need it. There are little changes in the patches between Focal and Bionic (mostly minor backport adjustments, mainly due to no vm_fault_t) but unfortunately that needs separate versions for most patches. ... [Original Bug Description] [Impact] In the event of a loss of power, ext4 filesystems mounted w/ data=journal,journal_checksum are subject to a corruption issue that requires a fsck to recover. This is exacerbated by installations by curtin that set passno=0 in /etc/fstab, preventing fsck from running automatically and thus requiring a manual recovery. And *that* is further exacerbated because initramfs-tools is smart enough to not include fsck.ext4 when passno=0 is detected in /etc/fstab, requiring the user to boot from recovery media. [Test Case] Forcibly power cycle a system running 'stress-ng --dir 0'. I've created a package to automate the reproduction: https://git.launchpad.net/~dannf/+git/dgx2-ext4-csum-repro?h=master [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847340] Re: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap
** Attachment added: "fstests-check-logs.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+attachment/5524207/+files/fstests-check-logs.sh -- 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/1847340 Title: ext4 journal recovery fails w/ data=journal + mmap Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Bug description: [Impact] With mmap()ed files on ext4's data journaling it's possible to change a mapped page's buffers contents during their jbd2 transaction commit (as currently nothing prevents/blocks the write access at that time.) This might happen between the buffers checksum calculation and actual write to journal, so the (old) checksum is invalid for the (new) data. If the system crashes after that, but before such journal entry makes it to the filesystem, the journal replay on the next mount just fails, and the filesystem now requires fsck. (apparently curtin might set up /etc/fstab with passno=0, requiring manual intervention.) [39751.096455] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! [39751.114435] JBD2: Invalid checksum recovering block 87305 in log [39751.146133] JBD2: Invalid checksum recovering block 88039 in log [39751.195950] JBD2: Invalid checksum recovering block 49633 in log [39751.265158] JBD2: recovery failed [39751.265163] EXT4-fs (vdc): error loading journal [Fix] The fix is to write-protect the pages during journal transaction commit, so that writes to mapped pages hit a page fault, then ext4's page_mkwrite hook can block until the commit finishes and the buffers can be modified. In order to do that, add jbd2 journal callbacks that the filesystems can customize, called before/after the critical region in transaction commit, then have ext4 in data journaling mode to write-protect the pages whose buffers are being committed (and handle cases that need pages redirtied.) The changes are restricted to the data journaling mode and page_mkwrite hook, and other modes/paths use the same code/behavior in the callbacks. [Test Case] Set up an ext4 filesystem in data journaling mode, and run stress-ng's mmap file test on it, then crash the system after a bit; check whether the filesystem can mount again or not (i.e., with jbd2 checksum errors.) # mkfs.ext4 $DEV # mount -o data=journal $DEV $DIR # cd $DIR # stress-ng --mmap $((4*$(nproc))) --mmap-file & # sleep 60 # echo c >/proc/sysrq-trigger ... # mount -o data=journal $DEV $DIR # PASS/FAIL. # dmesg | tail [Regression Potential] Regressions would likely manifest in ext4 data journaling mode (which is not the default mode, 'ordered') with memory mapped access, as the other modes/paths are largely unaffected by the changes/same behavior. This has been tested with (x)fstests, that showed no regressions on data=ordered and data=journal on both Bionic and Focal (with kernel versions 4.15.0-156-generic and 5.4.0-84-generic) w/in 10 runs each. And the stress-ng test-case as well. (Numbers/details in the LP bug.) [Other info] The patchset is applied on 5.10, so Hirsute (5.11) is already fixed; only Focal and Bionic need it. There are little changes in the patches between Focal and Bionic (mostly minor backport adjustments, mainly due to no vm_fault_t) but unfortunately that needs separate versions for most patches. ... [Original Bug Description] [Impact] In the event of a loss of power, ext4 filesystems mounted w/ data=journal,journal_checksum are subject to a corruption issue that requires a fsck to recover. This is exacerbated by installations by curtin that set passno=0 in /etc/fstab, preventing fsck from running automatically and thus requiring a manual recovery. And *that* is further exacerbated because initramfs-tools is smart enough to not include fsck.ext4 when passno=0 is detected in /etc/fstab, requiring the user to boot from recovery media. [Test Case] Forcibly power cycle a system running 'stress-ng --dir 0'. I've created a package to automate the reproduction: https://git.launchpad.net/~dannf/+git/dgx2-ext4-csum-repro?h=master [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHel
[Kernel-packages] [Bug 1847340] Re: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap
Attaching the scripts used for testing (run/check xfstests, and run stress-ng) -- 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/1847340 Title: ext4 journal recovery fails w/ data=journal + mmap Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Bug description: [Impact] With mmap()ed files on ext4's data journaling it's possible to change a mapped page's buffers contents during their jbd2 transaction commit (as currently nothing prevents/blocks the write access at that time.) This might happen between the buffers checksum calculation and actual write to journal, so the (old) checksum is invalid for the (new) data. If the system crashes after that, but before such journal entry makes it to the filesystem, the journal replay on the next mount just fails, and the filesystem now requires fsck. (apparently curtin might set up /etc/fstab with passno=0, requiring manual intervention.) [39751.096455] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! [39751.114435] JBD2: Invalid checksum recovering block 87305 in log [39751.146133] JBD2: Invalid checksum recovering block 88039 in log [39751.195950] JBD2: Invalid checksum recovering block 49633 in log [39751.265158] JBD2: recovery failed [39751.265163] EXT4-fs (vdc): error loading journal [Fix] The fix is to write-protect the pages during journal transaction commit, so that writes to mapped pages hit a page fault, then ext4's page_mkwrite hook can block until the commit finishes and the buffers can be modified. In order to do that, add jbd2 journal callbacks that the filesystems can customize, called before/after the critical region in transaction commit, then have ext4 in data journaling mode to write-protect the pages whose buffers are being committed (and handle cases that need pages redirtied.) The changes are restricted to the data journaling mode and page_mkwrite hook, and other modes/paths use the same code/behavior in the callbacks. [Test Case] Set up an ext4 filesystem in data journaling mode, and run stress-ng's mmap file test on it, then crash the system after a bit; check whether the filesystem can mount again or not (i.e., with jbd2 checksum errors.) # mkfs.ext4 $DEV # mount -o data=journal $DEV $DIR # cd $DIR # stress-ng --mmap $((4*$(nproc))) --mmap-file & # sleep 60 # echo c >/proc/sysrq-trigger ... # mount -o data=journal $DEV $DIR # PASS/FAIL. # dmesg | tail [Regression Potential] Regressions would likely manifest in ext4 data journaling mode (which is not the default mode, 'ordered') with memory mapped access, as the other modes/paths are largely unaffected by the changes/same behavior. This has been tested with (x)fstests, that showed no regressions on data=ordered and data=journal on both Bionic and Focal (with kernel versions 4.15.0-156-generic and 5.4.0-84-generic) w/in 10 runs each. And the stress-ng test-case as well. (Numbers/details in the LP bug.) [Other info] The patchset is applied on 5.10, so Hirsute (5.11) is already fixed; only Focal and Bionic need it. There are little changes in the patches between Focal and Bionic (mostly minor backport adjustments, mainly due to no vm_fault_t) but unfortunately that needs separate versions for most patches. ... [Original Bug Description] [Impact] In the event of a loss of power, ext4 filesystems mounted w/ data=journal,journal_checksum are subject to a corruption issue that requires a fsck to recover. This is exacerbated by installations by curtin that set passno=0 in /etc/fstab, preventing fsck from running automatically and thus requiring a manual recovery. And *that* is further exacerbated because initramfs-tools is smart enough to not include fsck.ext4 when passno=0 is detected in /etc/fstab, requiring the user to boot from recovery media. [Test Case] Forcibly power cycle a system running 'stress-ng --dir 0'. I've created a package to automate the reproduction: https://git.launchpad.net/~dannf/+git/dgx2-ext4-csum-repro?h=master [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847340] Re: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap
** Attachment added: "fstests-run.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+attachment/5524206/+files/fstests-run.sh -- 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/1847340 Title: ext4 journal recovery fails w/ data=journal + mmap Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Bug description: [Impact] With mmap()ed files on ext4's data journaling it's possible to change a mapped page's buffers contents during their jbd2 transaction commit (as currently nothing prevents/blocks the write access at that time.) This might happen between the buffers checksum calculation and actual write to journal, so the (old) checksum is invalid for the (new) data. If the system crashes after that, but before such journal entry makes it to the filesystem, the journal replay on the next mount just fails, and the filesystem now requires fsck. (apparently curtin might set up /etc/fstab with passno=0, requiring manual intervention.) [39751.096455] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! [39751.114435] JBD2: Invalid checksum recovering block 87305 in log [39751.146133] JBD2: Invalid checksum recovering block 88039 in log [39751.195950] JBD2: Invalid checksum recovering block 49633 in log [39751.265158] JBD2: recovery failed [39751.265163] EXT4-fs (vdc): error loading journal [Fix] The fix is to write-protect the pages during journal transaction commit, so that writes to mapped pages hit a page fault, then ext4's page_mkwrite hook can block until the commit finishes and the buffers can be modified. In order to do that, add jbd2 journal callbacks that the filesystems can customize, called before/after the critical region in transaction commit, then have ext4 in data journaling mode to write-protect the pages whose buffers are being committed (and handle cases that need pages redirtied.) The changes are restricted to the data journaling mode and page_mkwrite hook, and other modes/paths use the same code/behavior in the callbacks. [Test Case] Set up an ext4 filesystem in data journaling mode, and run stress-ng's mmap file test on it, then crash the system after a bit; check whether the filesystem can mount again or not (i.e., with jbd2 checksum errors.) # mkfs.ext4 $DEV # mount -o data=journal $DEV $DIR # cd $DIR # stress-ng --mmap $((4*$(nproc))) --mmap-file & # sleep 60 # echo c >/proc/sysrq-trigger ... # mount -o data=journal $DEV $DIR # PASS/FAIL. # dmesg | tail [Regression Potential] Regressions would likely manifest in ext4 data journaling mode (which is not the default mode, 'ordered') with memory mapped access, as the other modes/paths are largely unaffected by the changes/same behavior. This has been tested with (x)fstests, that showed no regressions on data=ordered and data=journal on both Bionic and Focal (with kernel versions 4.15.0-156-generic and 5.4.0-84-generic) w/in 10 runs each. And the stress-ng test-case as well. (Numbers/details in the LP bug.) [Other info] The patchset is applied on 5.10, so Hirsute (5.11) is already fixed; only Focal and Bionic need it. There are little changes in the patches between Focal and Bionic (mostly minor backport adjustments, mainly due to no vm_fault_t) but unfortunately that needs separate versions for most patches. ... [Original Bug Description] [Impact] In the event of a loss of power, ext4 filesystems mounted w/ data=journal,journal_checksum are subject to a corruption issue that requires a fsck to recover. This is exacerbated by installations by curtin that set passno=0 in /etc/fstab, preventing fsck from running automatically and thus requiring a manual recovery. And *that* is further exacerbated because initramfs-tools is smart enough to not include fsck.ext4 when passno=0 is detected in /etc/fstab, requiring the user to boot from recovery media. [Test Case] Forcibly power cycle a system running 'stress-ng --dir 0'. I've created a package to automate the reproduction: https://git.launchpad.net/~dannf/+git/dgx2-ext4-csum-repro?h=master [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847340] Re: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap
Test results with stress-ng. The original kernels hit the issue (very often on Bionic, less often on Focal.) The modified kernels don't (in 2x the number of runs on both Bionic and Focal.) Number of tests (stress-ng + crash + mount) that mount PASSED or FAILED (ie, problem was hit.) --- Bionic / Original: ubuntu@mfo-sf250123-b:~$ grep -e ^FAILED -e ^PASSED /test.log | cut -d' ' -f1 | sort | uniq -c 189 FAILED 573 PASSED Bionic / Modified: ubuntu@mfo-sf250123-b2:~$ grep -e ^FAILED -e ^PASSED /test.log | cut -d' ' -f1 | sort | uniq -c 1362 PASSED Focal / Original: ubuntu@mfo-sf250123-f:~$ grep -e ^FAILED -e ^PASSED /test.log | cut -d' ' -f1 | sort | uniq -c 1 FAILED 693 PASSED Focal / Modified: ubuntu@mfo-sf250123-f2:~$ grep -e ^FAILED -e ^PASSED /test.log | cut -d' ' -f1 | sort | uniq -c 1354 PASSED -- 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/1847340 Title: ext4 journal recovery fails w/ data=journal + mmap Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Bug description: [Impact] With mmap()ed files on ext4's data journaling it's possible to change a mapped page's buffers contents during their jbd2 transaction commit (as currently nothing prevents/blocks the write access at that time.) This might happen between the buffers checksum calculation and actual write to journal, so the (old) checksum is invalid for the (new) data. If the system crashes after that, but before such journal entry makes it to the filesystem, the journal replay on the next mount just fails, and the filesystem now requires fsck. (apparently curtin might set up /etc/fstab with passno=0, requiring manual intervention.) [39751.096455] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! [39751.114435] JBD2: Invalid checksum recovering block 87305 in log [39751.146133] JBD2: Invalid checksum recovering block 88039 in log [39751.195950] JBD2: Invalid checksum recovering block 49633 in log [39751.265158] JBD2: recovery failed [39751.265163] EXT4-fs (vdc): error loading journal [Fix] The fix is to write-protect the pages during journal transaction commit, so that writes to mapped pages hit a page fault, then ext4's page_mkwrite hook can block until the commit finishes and the buffers can be modified. In order to do that, add jbd2 journal callbacks that the filesystems can customize, called before/after the critical region in transaction commit, then have ext4 in data journaling mode to write-protect the pages whose buffers are being committed (and handle cases that need pages redirtied.) The changes are restricted to the data journaling mode and page_mkwrite hook, and other modes/paths use the same code/behavior in the callbacks. [Test Case] Set up an ext4 filesystem in data journaling mode, and run stress-ng's mmap file test on it, then crash the system after a bit; check whether the filesystem can mount again or not (i.e., with jbd2 checksum errors.) # mkfs.ext4 $DEV # mount -o data=journal $DEV $DIR # cd $DIR # stress-ng --mmap $((4*$(nproc))) --mmap-file & # sleep 60 # echo c >/proc/sysrq-trigger ... # mount -o data=journal $DEV $DIR # PASS/FAIL. # dmesg | tail [Regression Potential] Regressions would likely manifest in ext4 data journaling mode (which is not the default mode, 'ordered') with memory mapped access, as the other modes/paths are largely unaffected by the changes/same behavior. This has been tested with (x)fstests, that showed no regressions on data=ordered and data=journal on both Bionic and Focal (with kernel versions 4.15.0-156-generic and 5.4.0-84-generic) w/in 10 runs each. And the stress-ng test-case as well. (Numbers/details in the LP bug.) [Other info] The patchset is applied on 5.10, so Hirsute (5.11) is already fixed; only Focal and Bionic need it. There are little changes in the patches between Focal and Bionic (mostly minor backport adjustments, mainly due to no vm_fault_t) but unfortunately that needs separate versions for most patches. ... [Original Bug Description] [Impact] In the event of a loss of power, ext4 filesystems mounted w/ data=journal,journal_checksum are subject to a corruption issue that requires a fsck to recover. This is exacerbated by installations by curtin that set passno=0 in /etc/fstab, preventing fsck from running automatically and thus requiring a manual recovery. And *that* is further exacerbated because initramfs-tools i
[Kernel-packages] [Bug 1855628] Re: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep
** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350596/+files/CRDA.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310884/+files/CRDA.txt ** Attachment removed: "PciNetwork.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350606/+files/PciNetwork.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/1855628 Title: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: Whenever I wake the computer up from sleep, the computer no longer connects to the Internet without my having to go into Settings and turn Wi-Fi off and then back on again. Please address this issue. Thank you! network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 19:51:31 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575852612 Sun 08 Dec 2019 07:50:12 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575852610 Sun 08 Dec 2019 07:50:10 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/1 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: seija 1560 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-04 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev
[Kernel-packages] [Bug 1943070] Re: linux-aws: Missing check for CONFIG_SUSPEND in amdgpu_acpi.c
** Changed in: linux-aws (Ubuntu Hirsute) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1943070 Title: linux-aws: Missing check for CONFIG_SUSPEND in amdgpu_acpi.c Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Hirsute: Fix Committed Bug description: SRU Justification [Impact] A missing check in drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c causes a link error when CONFIG_SUSPEND=n ERROR: modpost: "pm_suspend_target_state" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined! This issue was introduced by an upstream stable update (commit 5706cb3c910cc8283f344bc37a889a8d523a2c6d upstream). [Test Plan] Successfully build and link. [Where problems could occur] This is a build time issue. No run time regression is possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1943070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847340] Re: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap
Regression test results with (x)fstests. Focal, data=ordered: no regression. Original: --- $ ./fstests-check-logs.sh orig-ordered/xfstests.log* Kernel version: 5.4.0-84-generic #94-Ubuntu - Number of Runs: 10 - Always fail (failed every time) 10 ext4/024 10 ext4/034 10 ext4/045 10 generic/044 10 generic/045 10 generic/046 10 generic/082 10 generic/219 10 generic/230 10 generic/231 10 generic/232 10 generic/233 10 generic/235 10 generic/270 10 generic/381 10 generic/382 10 generic/397 10 generic/398 10 generic/399 10 generic/419 10 generic/421 10 generic/429 10 generic/435 10 generic/440 10 generic/484 10 generic/548 10 generic/549 10 generic/550 10 generic/566 10 generic/587 10 generic/600 - Flaky (failed, but not every time) 4 generic/388 Modified: --- $ ./fstests-check-logs.sh mod-ordered/xfstests.log* Kernel version: 5.4.0-84-generic #94+test20210906b1 - Number of Runs: 10 - Always fail (failed every time) 10 ext4/024 10 ext4/034 10 ext4/045 10 generic/044 10 generic/045 10 generic/046 10 generic/082 10 generic/219 10 generic/230 10 generic/231 10 generic/232 10 generic/233 10 generic/235 10 generic/270 10 generic/381 10 generic/382 10 generic/397 10 generic/398 10 generic/399 10 generic/419 10 generic/421 10 generic/429 10 generic/435 10 generic/440 10 generic/484 10 generic/548 10 generic/549 10 generic/550 10 generic/566 10 generic/587 10 generic/600 - Flaky (failed, but not every time) 6 generic/388 -- 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/1847340 Title: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Bug description: [Impact] With mmap()ed files on ext4's data journaling it's possible to change a mapped page's buffers contents during their jbd2 transaction commit (as currently nothing prevents/blocks the write access at that time.) This might happen between the buffers checksum calculation and actual write to journal, so the (old) checksum is invalid for the (new) data. If the system crashes after that, but before such journal entry makes it to the filesystem, the journal replay on the next mount just fails, and the filesystem now requires fsck. (apparently curtin might set up /etc/fstab with passno=0, requiring manual intervention.) [39751.096455] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! [39751.114435] JBD2: Invalid checksum recovering block 87305 in log [39751.146133] JBD2: Invalid checksum recovering block 88039 in log [39751.195950] JBD2: Invalid checksum recovering block 49633 in log [39751.265158] JBD2: recovery failed [39751.265163] EXT4-fs (vdc): error loading journal [Fix] The fix is to write-protect the pages during journal transaction commit, so that writes to mapped pages hit a page fault, then ext4's page_mkwrite hook can block until the commit finishes and the buffers can be modified. In order to do that, add jbd2 journal callbacks that the filesystems can customize, called before/after the critical region in transaction commit, then have ext4 in data journaling mode to write-protect the pages whose buffers are being committed (and handle cases that need pages redirtied.) The changes are restricted to the data journaling mode and page_mkwrite hook, and other modes/paths use the same code/behavior in the callbacks. [Test Case] Set up an ext4 filesystem in data journaling mode, and run stress-ng's mmap file test on it, then crash the system after a bit; check whether the filesystem can mount again or not (i.e., with jbd2 checksum errors.) # mkfs.ext4 $DEV # mount -o data=journal $DEV $DIR # cd $DIR # stress-ng --mmap $((4*$(nproc))) --mmap-file & # sleep 60 # echo c >/proc/sysrq-trigger ... # mount -o data=journal $DEV $DIR # PASS/FAIL. # dmesg | tail [Regression Potential] Regressions would likely manifest in ext4 data journaling mode (which is not the default mode, 'ordered') with memory mapped access, as the other modes/paths are largely unaffected by the changes/same behavior. This has been tested with (x)fstests, that showed no regressions on data=ordered and data=journal on both B
[Kernel-packages] [Bug 1847340] Re: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap
Regression test results with (x)fstests. Bionic, data=journal: no regression. Original: --- $ ./fstests-check-logs.sh orig-journal/xfstests.log* Kernel version: 5.4.0-84-generic #94-Ubuntu - Number of Runs: 10 - Always fail (failed every time) 10 ext4/024 10 ext4/034 10 ext4/045 10 generic/082 10 generic/219 10 generic/223 10 generic/230 10 generic/231 10 generic/232 10 generic/233 10 generic/235 10 generic/270 10 generic/381 10 generic/382 10 generic/397 10 generic/398 10 generic/399 10 generic/419 10 generic/421 10 generic/429 10 generic/435 10 generic/440 10 generic/441 10 generic/537 10 generic/548 10 generic/549 10 generic/550 10 generic/566 10 generic/600 - Flaky (failed, but not every time) 2 generic/388 2 generic/475 9 generic/347 Modified: --- $ ./fstests-check-logs.sh mod-journal/xfstests.log* Kernel version: 5.4.0-84-generic #94+test20210906b1 - Number of Runs: 10 - Always fail (failed every time) 10 ext4/024 10 ext4/034 10 ext4/045 10 generic/082 10 generic/219 10 generic/223 10 generic/230 10 generic/231 10 generic/232 10 generic/233 10 generic/235 10 generic/270 10 generic/381 10 generic/382 10 generic/397 10 generic/398 10 generic/399 10 generic/419 10 generic/421 10 generic/429 10 generic/435 10 generic/440 10 generic/441 10 generic/537 10 generic/548 10 generic/549 10 generic/550 10 generic/566 10 generic/600 - Flaky (failed, but not every time) 1 generic/388 6 generic/484 * 9 generic/347 * This test has been confirmed to fail on the original kernel too, with a larger sample size (more runs w/ only the generic/484 test.) Even though it takes more than a few hundred runs to manifest a few times, it demonstrates that the problematic behavior is also there, and might be just a timing change that made it happen more often now (but it's still flaky, doesn't fail every single time.) $ ls -1 xfstests.log* | wc -l 518 $ grep -h ^Failures: xfstests.log* | sort | uniq -c 6 Failures: generic/484 -- 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/1847340 Title: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Bug description: [Impact] With mmap()ed files on ext4's data journaling it's possible to change a mapped page's buffers contents during their jbd2 transaction commit (as currently nothing prevents/blocks the write access at that time.) This might happen between the buffers checksum calculation and actual write to journal, so the (old) checksum is invalid for the (new) data. If the system crashes after that, but before such journal entry makes it to the filesystem, the journal replay on the next mount just fails, and the filesystem now requires fsck. (apparently curtin might set up /etc/fstab with passno=0, requiring manual intervention.) [39751.096455] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! [39751.114435] JBD2: Invalid checksum recovering block 87305 in log [39751.146133] JBD2: Invalid checksum recovering block 88039 in log [39751.195950] JBD2: Invalid checksum recovering block 49633 in log [39751.265158] JBD2: recovery failed [39751.265163] EXT4-fs (vdc): error loading journal [Fix] The fix is to write-protect the pages during journal transaction commit, so that writes to mapped pages hit a page fault, then ext4's page_mkwrite hook can block until the commit finishes and the buffers can be modified. In order to do that, add jbd2 journal callbacks that the filesystems can customize, called before/after the critical region in transaction commit, then have ext4 in data journaling mode to write-protect the pages whose buffers are being committed (and handle cases that need pages redirtied.) The changes are restricted to the data journaling mode and page_mkwrite hook, and other modes/paths use the same code/behavior in the callbacks. [Test Case] Set up an ext4 filesystem in data journaling mode, and run stress-ng's mmap file test on it, then crash the system after a bit; check whether the filesystem can mount again or not (i.e., with jbd2 checksum errors.) # mkfs.ext4 $DEV # mount -o data=journal $DEV $DIR # cd $DIR # stress-ng --mmap $((4*$
[Kernel-packages] [Bug 1847340] Re: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap
Regression test results with (x)fstests. Bionic, data=journal: no regression. Original: --- $ ./fstests-check-logs.sh orig-journal/xfstests.log* Kernel version: 4.15.0-156-generic #163-Ubuntu - Number of Runs: 10 - Always fail (failed every time) 10 ext4/045 10 generic/082 10 generic/219 10 generic/223 10 generic/230 10 generic/231 10 generic/232 10 generic/233 10 generic/235 10 generic/270 10 generic/347 10 generic/371 10 generic/381 10 generic/382 10 generic/441 10 generic/491 10 generic/553 10 generic/554 10 generic/555 10 generic/565 10 generic/566 10 generic/569 10 generic/598 10 generic/600 10 generic/623 10 generic/629 10 shared/298 - Flaky (failed, but not every time) 3 generic/475 6 generic/388 Modified: --- $ ./fstests-check-logs.sh mod-journal/xfstests.log* Kernel version: 4.15.0-156-generic #163+test20210906b1 - Number of Runs: 10 - Always fail (failed every time) 10 ext4/045 10 generic/082 10 generic/219 10 generic/223 10 generic/230 10 generic/231 10 generic/232 10 generic/233 10 generic/235 10 generic/270 10 generic/381 10 generic/382 10 generic/441 10 generic/491 10 generic/553 10 generic/554 10 generic/555 10 generic/565 10 generic/566 10 generic/569 10 generic/598 10 generic/600 10 generic/623 10 generic/629 10 shared/298 - Flaky (failed, but not every time) 6 generic/347 (improved from orig, now flaky, prev always) 6 generic/388 9 generic/371 (improved from orig, now flaky, prev always) -- 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/1847340 Title: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Bug description: [Impact] With mmap()ed files on ext4's data journaling it's possible to change a mapped page's buffers contents during their jbd2 transaction commit (as currently nothing prevents/blocks the write access at that time.) This might happen between the buffers checksum calculation and actual write to journal, so the (old) checksum is invalid for the (new) data. If the system crashes after that, but before such journal entry makes it to the filesystem, the journal replay on the next mount just fails, and the filesystem now requires fsck. (apparently curtin might set up /etc/fstab with passno=0, requiring manual intervention.) [39751.096455] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! [39751.114435] JBD2: Invalid checksum recovering block 87305 in log [39751.146133] JBD2: Invalid checksum recovering block 88039 in log [39751.195950] JBD2: Invalid checksum recovering block 49633 in log [39751.265158] JBD2: recovery failed [39751.265163] EXT4-fs (vdc): error loading journal [Fix] The fix is to write-protect the pages during journal transaction commit, so that writes to mapped pages hit a page fault, then ext4's page_mkwrite hook can block until the commit finishes and the buffers can be modified. In order to do that, add jbd2 journal callbacks that the filesystems can customize, called before/after the critical region in transaction commit, then have ext4 in data journaling mode to write-protect the pages whose buffers are being committed (and handle cases that need pages redirtied.) The changes are restricted to the data journaling mode and page_mkwrite hook, and other modes/paths use the same code/behavior in the callbacks. [Test Case] Set up an ext4 filesystem in data journaling mode, and run stress-ng's mmap file test on it, then crash the system after a bit; check whether the filesystem can mount again or not (i.e., with jbd2 checksum errors.) # mkfs.ext4 $DEV # mount -o data=journal $DEV $DIR # cd $DIR # stress-ng --mmap $((4*$(nproc))) --mmap-file & # sleep 60 # echo c >/proc/sysrq-trigger ... # mount -o data=journal $DEV $DIR # PASS/FAIL. # dmesg | tail [Regression Potential] Regressions would likely manifest in ext4 data journaling mode (which is not the default mode, 'ordered') with memory mapped access, as the other modes/paths are largely unaffected by the changes/same behavior. This has been tested with (x)fstests, that showed no regressions on data=ordered and data=journal on both Bionic and Focal (with kernel ve
[Kernel-packages] [Bug 1847340] Re: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap
Regression test results with (x)fstests. Bionic, data=ordered: no regression. Original: --- $ ./fstests-check-logs.sh orig-ordered/xfstests.log* Kernel version: 4.15.0-156-generic #163-Ubuntu - Number of Runs: 10 - Always fail (failed every time) 10 ext4/045 10 generic/044 10 generic/045 10 generic/046 10 generic/082 10 generic/095 10 generic/219 10 generic/230 10 generic/231 10 generic/232 10 generic/233 10 generic/235 10 generic/270 10 generic/299 10 generic/300 10 generic/381 10 generic/382 10 generic/491 10 generic/553 10 generic/554 10 generic/555 10 generic/565 10 generic/566 10 generic/569 10 generic/587 10 generic/598 10 generic/600 10 generic/623 10 generic/629 10 shared/298 - Flaky (failed, but not every time) 6 generic/388 Modified: --- $ ./fstests-check-logs.sh mod-ordered/xfstests.log* Kernel version: 4.15.0-156-generic #163+test20210906b1 - Number of Runs: 10 - Always fail (failed every time) 10 ext4/045 10 generic/044 10 generic/045 10 generic/046 10 generic/082 10 generic/095 10 generic/219 10 generic/230 10 generic/231 10 generic/232 10 generic/233 10 generic/235 10 generic/270 10 generic/299 10 generic/300 10 generic/381 10 generic/382 10 generic/491 10 generic/553 10 generic/554 10 generic/555 10 generic/565 10 generic/566 10 generic/569 10 generic/587 10 generic/598 10 generic/600 10 generic/623 10 generic/629 10 shared/298 - Flaky (failed, but not every time) 9 generic/388 -- 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/1847340 Title: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Bug description: [Impact] With mmap()ed files on ext4's data journaling it's possible to change a mapped page's buffers contents during their jbd2 transaction commit (as currently nothing prevents/blocks the write access at that time.) This might happen between the buffers checksum calculation and actual write to journal, so the (old) checksum is invalid for the (new) data. If the system crashes after that, but before such journal entry makes it to the filesystem, the journal replay on the next mount just fails, and the filesystem now requires fsck. (apparently curtin might set up /etc/fstab with passno=0, requiring manual intervention.) [39751.096455] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! [39751.114435] JBD2: Invalid checksum recovering block 87305 in log [39751.146133] JBD2: Invalid checksum recovering block 88039 in log [39751.195950] JBD2: Invalid checksum recovering block 49633 in log [39751.265158] JBD2: recovery failed [39751.265163] EXT4-fs (vdc): error loading journal [Fix] The fix is to write-protect the pages during journal transaction commit, so that writes to mapped pages hit a page fault, then ext4's page_mkwrite hook can block until the commit finishes and the buffers can be modified. In order to do that, add jbd2 journal callbacks that the filesystems can customize, called before/after the critical region in transaction commit, then have ext4 in data journaling mode to write-protect the pages whose buffers are being committed (and handle cases that need pages redirtied.) The changes are restricted to the data journaling mode and page_mkwrite hook, and other modes/paths use the same code/behavior in the callbacks. [Test Case] Set up an ext4 filesystem in data journaling mode, and run stress-ng's mmap file test on it, then crash the system after a bit; check whether the filesystem can mount again or not (i.e., with jbd2 checksum errors.) # mkfs.ext4 $DEV # mount -o data=journal $DEV $DIR # cd $DIR # stress-ng --mmap $((4*$(nproc))) --mmap-file & # sleep 60 # echo c >/proc/sysrq-trigger ... # mount -o data=journal $DEV $DIR # PASS/FAIL. # dmesg | tail [Regression Potential] Regressions would likely manifest in ext4 data journaling mode (which is not the default mode, 'ordered') with memory mapped access, as the other modes/paths are largely unaffected by the changes/same behavior. This has been tested with (x)fstests, that showed no regressions on data=ordered and data=journal on both Bionic and Focal (with k
[Kernel-packages] [Bug 1847340] Re: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap
** Description changed: + [Impact] + + With mmap()ed files on ext4's data journaling it's possible to change + a mapped page's buffers contents during their jbd2 transaction commit + (as currently nothing prevents/blocks the write access at that time.) + + This might happen between the buffers checksum calculation and actual + write to journal, so the (old) checksum is invalid for the (new) data. + + If the system crashes after that, but before such journal entry makes + it to the filesystem, the journal replay on the next mount just fails, + and the filesystem now requires fsck. (apparently curtin might set up + /etc/fstab with passno=0, requiring manual intervention.) + + [39751.096455] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! + [39751.114435] JBD2: Invalid checksum recovering block 87305 in log + [39751.146133] JBD2: Invalid checksum recovering block 88039 in log + [39751.195950] JBD2: Invalid checksum recovering block 49633 in log + [39751.265158] JBD2: recovery failed + [39751.265163] EXT4-fs (vdc): error loading journal + + [Fix] + + The fix is to write-protect the pages during journal transaction commit, + so that writes to mapped pages hit a page fault, then ext4's page_mkwrite + hook can block until the commit finishes and the buffers can be modified. + + In order to do that, add jbd2 journal callbacks that the filesystems can + customize, called before/after the critical region in transaction commit, + then have ext4 in data journaling mode to write-protect the pages whose + buffers are being committed (and handle cases that need pages redirtied.) + + The changes are restricted to the data journaling mode and page_mkwrite + hook, and other modes/paths use the same code/behavior in the callbacks. + + [Test Case] + + Set up an ext4 filesystem in data journaling mode, and run stress-ng's + mmap file test on it, then crash the system after a bit; check whether + the filesystem can mount again or not (i.e., with jbd2 checksum errors.) + + # mkfs.ext4 $DEV + # mount -o data=journal $DEV $DIR + # cd $DIR + # stress-ng --mmap $((4*$(nproc))) --mmap-file & + # sleep 60 + # echo c >/proc/sysrq-trigger + ... + # mount -o data=journal $DEV $DIR # PASS/FAIL. + # dmesg | tail + + [Regression Potential] + + Regressions would likely manifest in ext4 data journaling mode (which + is not the default mode, 'ordered') with memory mapped access, as the + other modes/paths are largely unaffected by the changes/same behavior. + + This has been tested with (x)fstests, that showed no regressions on + data=ordered and data=journal on both Bionic and Focal (with kernel + versions 4.15.0-156-generic and 5.4.0-84-generic) w/in 10 runs each. + And the stress-ng test-case as well. (Numbers/details in the LP bug.) + + [Other info] + + The patchset is applied on 5.10, so Hirsute (5.11) is already fixed; + only Focal and Bionic need it. + + There are little changes in the patches between Focal and Bionic + (mostly minor backport adjustments, mainly due to no vm_fault_t) + but unfortunately that needs separate versions for most patches. + + ... + + + [Original Bug Description] + [Impact] In the event of a loss of power, ext4 filesystems mounted w/ data=journal,journal_checksum are subject to a corruption issue that requires a fsck to recover. This is exacerbated by installations by curtin that set passno=0 in /etc/fstab, preventing fsck from running automatically and thus requiring a manual recovery. And *that* is further exacerbated because initramfs-tools is smart enough to not include fsck.ext4 when passno=0 is detected in /etc/fstab, requiring the user to boot from recovery media. [Test Case] Forcibly power cycle a system running 'stress-ng --dir 0'. I've created a package to automate the reproduction: https://git.launchpad.net/~dannf/+git/dgx2-ext4-csum-repro?h=master [Fix] [Regression Risk] -- 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/1847340 Title: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Bug description: [Impact] With mmap()ed files on ext4's data journaling it's possible to change a mapped page's buffers contents during their jbd2 transaction commit (as currently nothing prevents/blocks the write access at that time.) This might happen between the buffers checksum calculation and actual write to journal, so the (old) checksum is invalid for the (new) data. If the system crashes after
[Kernel-packages] [Bug 1349252] Re: crypt(3) lacks Blowfish support
FWIW, in Ubuntu 20.04 a bcrypt hash generated with -B in the provided
htpasswd (that uses their own implementation), can be used by crypt(3):
$ perl -e 'print crypt("cvspassword",
"\$2y\$05\$xGcVN3jyU43rgH/jtc0mG.wMEYmvXBjdZtBc5R1jFYD83aaOTWiqa"), "\n"'
$2y$05$xGcVN3jyU43rgH/jtc0mG.wMEYmvXBjdZtBc5R1jFYD83aaOTWiqa
--
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/1349252
Title:
crypt(3) lacks Blowfish support
Status in glibc package in Ubuntu:
Won't Fix
Status in linux package in Ubuntu:
Invalid
Bug description:
crypt(3) bundled with Ubuntu's GNU C Library supports MD5, DES, SHA256
and SHA512 hashing methods, but lacks support for Blowfish (aka
bcrypt).
There is a patch available from Openwall:
http://www.openwall.com/crypt/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1349252/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847340] Re: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap
** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Changed in: linux (Ubuntu Hirsute) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847340 Title: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Bug description: [Impact] In the event of a loss of power, ext4 filesystems mounted w/ data=journal,journal_checksum are subject to a corruption issue that requires a fsck to recover. This is exacerbated by installations by curtin that set passno=0 in /etc/fstab, preventing fsck from running automatically and thus requiring a manual recovery. And *that* is further exacerbated because initramfs-tools is smart enough to not include fsck.ext4 when passno=0 is detected in /etc/fstab, requiring the user to boot from recovery media. [Test Case] Forcibly power cycle a system running 'stress-ng --dir 0'. I've created a package to automate the reproduction: https://git.launchpad.net/~dannf/+git/dgx2-ext4-csum-repro?h=master [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855628] Re: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep
** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310894/+files/WifiSyslog.txt ** Attachment removed: "IpAddr.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310886/+files/IpAddr.txt ** Attachment removed: "PciNetwork.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310892/+files/PciNetwork.txt ** Attachment removed: "NetworkManager.conf.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310891/+files/NetworkManager.conf.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310887/+files/IwConfig.txt ** Attachment removed: "NetworkManager.conf.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350605/+files/NetworkManager.conf.txt ** Attachment removed: "IpAddr.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350599/+files/IpAddr.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350613/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855628 Title: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: Whenever I wake the computer up from sleep, the computer no longer connects to the Internet without my having to go into Settings and turn Wi-Fi off and then back on again. Please address this issue. Thank you! network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 19:51:31 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575852612 Sun 08 Dec 2019 07:50:12 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575852610 Sun 08 Dec 2019 07:50:10 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/1 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devic
[Kernel-packages] [Bug 1943097] Re: Kernel 5.13 broke my Ubuntu 21.10 on RPI4 8Gb
** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu) Status: New => Confirmed -- 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/1943097 Title: Kernel 5.13 broke my Ubuntu 21.10 on RPI4 8Gb Status in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Bug description: Hello all, Ubuntu 21.10 on RPI4 and Kernel 5.13 broke my system when I use a USB SSD install. Lets see all steps: I downloaded Ubuntu 21.10 desktop img from ubuntu daily builds and installed it on a USB SSD (about a month ago). Every things were all wright an for me it was better than 21.04. I was very happy. Until last week, when Update manager came with a kernel 5.13 version. As usual I applied all updates and rebooted. Reboot took a long time and terminated in a character screen and was written Busybox. initram... Type help for... For what??? I simply didn't know how to deal with that info. Than I decide to install Ubuntu 21.04, but firefox latest version was 90 and I would be in trouble to recover firefox (90.0.2) data files form 21.10 and use it. So I decide to give ubuntu 21.10 another try, and installed it on a SDcard. set up finished lets update it all and reboot. Reboot successfully and than I copied SDcard to my USB SSD using SD Card Copy from Raspberry PI OS. Reboot took a long time and terminated in a character screen and was written Busybox. initram... Type help for... Oh my God, expending a weekend to have a 21.10 working New try... Installed 21.10 again on RPI4 on USB SSD but... but in update manager UNMARKed all kernel 5.13 updates. Now I am running Ubuntu 21.10 for 3 days but Kernel installed is 5.11. I Hope this report could be useful for someone. And waiting for a fix. Thanks, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1943097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] Re: DVD-Drive opens randomly on Kernel 5.4.0-84
** 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/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Invalid Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524174/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524180/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524185/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524181/+files/ProcEnviron.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/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524179/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524183/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524187/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524176/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524182/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524184/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524186/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524175/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524177/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524178/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524173/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524172/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] Re: DVD-Drive opens randomly on Kernel 5.4.0-84
apport information ** Tags added: apport-collected uma ** Description changed: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.18 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: malthael 1255 F pulseaudio + /dev/snd/controlC0: malthael 1255 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 20.2 + InstallationDate: Installed on 2021-09-06 (2 days ago) + InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 + IwConfig: + lono wireless extensions. + + enp4s0no wireless extensions. + MachineType: Dell Inc. Studio XPS 8100 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash + ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-81-generic N/A + linux-backports-modules-5.4.0-81-generic N/A + linux-firmware1.187.16 + RfKill: + + Tags: uma + Uname: Linux 5.4.0-81-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/08/2010 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A05 + dmi.board.name: 0T568R + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 3 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: + dmi.product.name: Studio XPS 8100 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1943174/+attachment/5524171/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] 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 1943174 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/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Confirmed Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: malthael 1255 F pulseaudio /dev/snd/controlC0: malthael 1255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-09-06 (2 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Studio XPS 8100 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=268cd9b3-6f51-4f5d-b567-51b769303ee5 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 RfKill: Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943174] [NEW] DVD-Drive opens randomly on Kernel 5.4.0-84
Public bug reported: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: kernel-bug -- 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/1943174 Title: DVD-Drive opens randomly on Kernel 5.4.0-84 Status in linux package in Ubuntu: Incomplete Bug description: With up-to-date Linux Mint. After switching back to Kernel 5.4.0-81 this problem is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933359] Re: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933359 Title: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request Status in linux package in Ubuntu: Confirmed Bug description: Broadcom is coming up with next generation high performance Storage IO and RAID controllers. For details, follow: https://www.spinics.net/lists/linux-scsi/msg147868.html This family of controllers is managed by "mpi3mr" Linux device driver(written from scratch). First patchset of the driver is accepted by Linux upstream. The driver is available in git branch - 5.14/scsi-staging of Linux SCSI tree: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git The driver will be part of 5.14 mainline Linux kernel release. Here is the list of commit ids: 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints 74e1f30a2868 scsi: mpi3mr: Add EEDP DIF DIX support 28cbe2f420d3 scsi: mpi3mr: Add support for DSN secure firmware check 2f9c4d520aa6 scsi: mpi3mr: Add support for PM suspend and resume 44dc724f5eec scsi: mpi3mr: Wait for pending I/O completions upon detection of VD I/O timeout 71e80106d059 scsi: mpi3mr: Print pending host I/Os for debugging f061178e0762 scsi: mpi3mr: Complete support for soft reset 463429f8dd5c scsi: mpi3mr: Add support for threaded ISR 392bbeb85b2a scsi: mpi3mr: Hardware workaround for UNMAP commands to NVMe drives 82141ddba90a scsi: mpi3mr: Allow certain commands during pci-remove hook 0ea177343f1f scsi: mpi3mr: Add change queue depth support e844adb1fbdc scsi: mpi3mr: Implement SCSI error handler hooks 8f9c6173ca46 scsi: mpi3mr: Add bios_param SCSI host template hook ff9561e910fc scsi: mpi3mr: Print IOC info for debugging 54dfcffb4191 scsi: mpi3mr: Add support for timestamp sync with firmware fb9b04574f14 scsi: mpi3mr: Add support for recovering controller e36710dc06e3 scsi: mpi3mr: Additional event handling 8e653455547a scsi: mpi3mr: Add support for PCIe device event handling 13ef29ea4aa0 scsi: mpi3mr: Add support for device add/remove event handling 672ae26c8216 scsi: mpi3mr: Add support for internal watchdog thread 023ab2a9b4ed scsi: mpi3mr: Add support for queue command processing c9566231cfaf scsi: mpi3mr: Create operational request and reply queue pair 824a156633df scsi: mpi3mr: Base driver code c4f7ac64616e scsi: mpi3mr: Add mpi30 Rev-R headers and Kconfig Please include this driver in Ubuntu 21.10 release. Let me know for any questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers
This bug was fixed in the package nvidia-graphics-drivers-470 - 470.63.01-0ubuntu0.20.04.2 --- nvidia-graphics-drivers-470 (470.63.01-0ubuntu0.20.04.2) focal; urgency=medium * debian/nvidia_supported, debian/rules: debian/pm-aliases-gen - Include the actual changes that were only mentioned in the changelog for the previous release (LP: #1939673). nvidia-graphics-drivers-470 (470.63.01-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1939673): - Added support for the following GPUs: NVIDIA RTX A2000 - Fixed a Vulkan performance regression that affected rFactor2. * debian/nvidia_supported, debian/rules: - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. -- Alberto Milone Tue, 31 Aug 2021 11:26:03 +0200 ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1939673 Title: Update the 470 and the 470-server NVIDIA drivers Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Released Bug description: Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.57.02 (470-server) == * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. == 470.63.01 (470) == * New upstream release (LP: #1939673): - Added support for the following GPUs: NVIDIA RTX A2000 - Fixed a Vulkan performance regression that affected rFactor2. * debian/nvidia_supported, debian/rules: - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers
This bug was fixed in the package nvidia-graphics-drivers-470 - 470.63.01-0ubuntu0.18.04.2 --- nvidia-graphics-drivers-470 (470.63.01-0ubuntu0.18.04.2) bionic; urgency=medium * debian/nvidia_supported, debian/rules: debian/pm-aliases-gen - Include the actual changes that were only mentioned in the changelog for the previous release (LP: #1939673). nvidia-graphics-drivers-470 (470.63.01-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (LP: #1939673): - Added support for the following GPUs: NVIDIA RTX A2000 - Fixed a Vulkan performance regression that affected rFactor2. * debian/nvidia_supported, debian/rules: - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. -- Alberto Milone Tue, 31 Aug 2021 11:35:34 +0200 ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1939673 Title: Update the 470 and the 470-server NVIDIA drivers Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Released Bug description: Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.57.02 (470-server) == * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. == 470.63.01 (470) == * New upstream release (LP: #1939673): - Added support for the following GPUs: NVIDIA RTX A2000 - Fixed a Vulkan performance regression that affected rFactor2. * debian/nvidia_supported, debian/rules: - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers
This bug was fixed in the package nvidia-graphics-drivers-470-server - 470.57.02-0ubuntu0.18.04.4 --- nvidia-graphics-drivers-470-server (470.57.02-0ubuntu0.18.04.4) bionic; urgency=medium * debian/nvidia_supported: - Ignore subsystem vendor and id when generating modaliases, so that we don't exclude devices that are actually supported (LP: #1939673). nvidia-graphics-drivers-470-server (470.57.02-0ubuntu0.18.04.3) bionic; urgency=medium * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. -- Alberto Milone Tue, 31 Aug 2021 17:18:03 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1939673 Title: Update the 470 and the 470-server NVIDIA drivers Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Released Bug description: Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.57.02 (470-server) == * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. == 470.63.01 (470) == * New upstream release (LP: #1939673): - Added support for the following GPUs: NVIDIA RTX A2000 - Fixed a Vulkan performance regression that affected rFactor2. * debian/nvidia_supported, debian/rules: - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers
This bug was fixed in the package nvidia-graphics-drivers-470-server - 470.57.02-0ubuntu0.20.04.4 --- nvidia-graphics-drivers-470-server (470.57.02-0ubuntu0.20.04.4) focal; urgency=medium * debian/nvidia_supported: - Ignore subsystem vendor and id when generating modaliases, so that we don't exclude devices that are actually supported (LP: #1939673). nvidia-graphics-drivers-470-server (470.57.02-0ubuntu0.20.04.3) focal; urgency=medium * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. -- Alberto Milone Tue, 31 Aug 2021 17:16:14 +0200 ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1939673 Title: Update the 470 and the 470-server NVIDIA drivers Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Released Bug description: Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.57.02 (470-server) == * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. == 470.63.01 (470) == * New upstream release (LP: #1939673): - Added support for the following GPUs: NVIDIA RTX A2000 - Fixed a Vulkan performance regression that affected rFactor2. * debian/nvidia_supported, debian/rules: - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers
This bug was fixed in the package nvidia-graphics-drivers-470-server - 470.57.02-0ubuntu0.21.04.4 --- nvidia-graphics-drivers-470-server (470.57.02-0ubuntu0.21.04.4) hirsute; urgency=medium * debian/nvidia_supported: - Ignore subsystem vendor and id when generating modaliases, so that we don't exclude devices that are actually supported (LP: #1939673). nvidia-graphics-drivers-470-server (470.57.02-0ubuntu0.21.04.3) hirsute; urgency=medium * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. -- Alberto Milone Tue, 31 Aug 2021 17:03:11 +0200 ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1939673 Title: Update the 470 and the 470-server NVIDIA drivers Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Released Bug description: Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.57.02 (470-server) == * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. == 470.63.01 (470) == * New upstream release (LP: #1939673): - Added support for the following GPUs: NVIDIA RTX A2000 - Fixed a Vulkan performance regression that affected rFactor2. * debian/nvidia_supported, debian/rules: - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers
This bug was fixed in the package nvidia-graphics-drivers-470 - 470.63.01-0ubuntu0.21.04.2 --- nvidia-graphics-drivers-470 (470.63.01-0ubuntu0.21.04.2) hirsute; urgency=medium * debian/nvidia_supported, debian/rules: debian/pm-aliases-gen - Include the actual changes that were only mentioned in the changelog for the previous release (LP: #1939673). nvidia-graphics-drivers-470 (470.63.01-0ubuntu0.21.04.1) hirsute; urgency=medium * New upstream release (LP: #1939673): - Added support for the following GPUs: NVIDIA RTX A2000 - Fixed a Vulkan performance regression that affected rFactor2. * debian/nvidia_supported, debian/rules: - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. -- Alberto Milone Mon, 30 Aug 2021 16:17:11 +0200 ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1939673 Title: Update the 470 and the 470-server NVIDIA drivers Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Released Bug description: Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.57.02 (470-server) == * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. == 470.63.01 (470) == * New upstream release (LP: #1939673): - Added support for the following GPUs: NVIDIA RTX A2000 - Fixed a Vulkan performance regression that affected rFactor2. * debian/nvidia_supported, debian/rules: - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers
** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-bionic verification-done-focal verification-done-hirsute ** Tags removed: verification-done-bionic verification-done-focal verification-done-hirsute verification-needed ** Tags added: verification-done verification-needed-bionic verification-needed-focal verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1939673 Title: Update the 470 and the 470-server NVIDIA drivers Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Released Bug description: Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.57.02 (470-server) == * debian/nvidia_supported, debian/rules (LP: #1939673): - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. == 470.63.01 (470) == * New upstream release (LP: #1939673): - Added support for the following GPUs: NVIDIA RTX A2000 - Fixed a Vulkan performance regression that affected rFactor2. * debian/nvidia_supported, debian/rules: - Use the json database file to generate the modaliases. - Fix aliases generation. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. * debian/pm-aliases-gen: - Fix aliases generation for runtimepm. We were not matching some of the aliases because of some missing zeroes in the subdevice and subvendor ids. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943086] Re: linux-modules-nvidia-470-generic-hwe-20.04 dependency cant be installed
I can confirm this problem, just updated the system and Xorg session wasn't starting, I was able to install the latest drivers using another tty and enabling the graphics drivers ppa, but, yes, I restarted the computer and saw just a black screen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943086 Title: linux-modules-nvidia-470-generic-hwe-20.04 dependency cant be installed Status in linux-restricted-modules-hwe-5.11 package in Ubuntu: Confirmed Bug description: linux-modules-nvidia-470-generic-hwe-20.04=5.11.0-34.36~20.04.1 depends on nvidia-kernel-common-470 (>= 470.63.01) but that version is not published, the latest one available today is 470.57.02-0ubuntu0.20.04.1 That means that installing latest hwe kernel for 20.04 breaks nvidia driver. This is problematic in distros like Elementary OS 6 as they dont expose the grub menu, so you have the latest kernel version installed only, which will not be able to boot on the graphical interface because there is no driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.11/+bug/1943086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942008] Re: Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs, won't wake from sleep
** Description changed: Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake from sleep worked fine. Updates for 20.04.2 caused issues where it wouldn't wake from sleep, rebooting hangs, and never actually shutdowns for the reboot, and shutdown causes an audible hardware clicking noise (somewhere to the left side of the computer underneath the keyboard) and corrupts the BIOS. The corrupted BIOS causes the computer to not boot at all and I have to do a BIOS reset via CMOS (Hold the power button for 2-3 sec while pressing the WIN+v keys until it begins to boot). This gets more difficult each time it's done, where I have to wait longer before trying it and it seems to take longer to work. I have tried - shutdown from the GUI menu, from the log-out menu, from Konsole, and - from a TTY (CTRL+ALT+F2). + shutdown from the GUI menu, from the log-out menu, Konsole, and a TTY + (CTRL+ALT+F2). I also have tried reinstalling a couple of times. + + Edit (also posted below): I made a post on a support site here: + https://ubuntuforums.org/showthread.php?t=2466821. Even though this is + clearly a bug in the 5.8+ kernels, updating to 5.11 and 20.04.3 still + has this bug. The "solution" was to downgrade the kernel to 5.4, which + is not a long-term solution. Hopefully, this bug will be resolved in + future updates to the kernel. Computer specs: Host: HP Pavilion dv7-2180us Notebook PC Rev 1 Kernel: 5.8.0-59-generic Resolution: 1600x900 CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz GPU: AMD ATI Mobility Radeon HD 4650/5165 Memory: 6 GB --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kah1382 F pulseaudio /dev/snd/controlC1: kah1382 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (13 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.16 Tags: focal Uname: Linux 5.11.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2009 dmi.bios.release: 15.51 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.33 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3624 dmi.board.vendor: Quanta dmi.board.version: 18.42 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.ec.firmware.release: 24.66 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.sku: NV022UA#ABA dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard -- 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/1942008 Title: Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs, won't wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake from sleep worked fine. Updates for 20.04.2 caused issues where it wouldn't wake from sleep, rebooting hangs, and never actually shutdowns for the reboot, and shutdown causes an audible hardware clicking noise (somewhere to the left side of the computer underneath the keyboard) and corrupts the BIOS. The corrupted BIOS causes the computer to not boot at all and I have to do a BIOS reset via CMOS (Hold the power button for 2-3 sec while pressing the WIN+v keys until it begins to boot). This gets more difficult each time it's done, where I have to wait longer before trying it and it seems to take longer to work. I have tried shutdown from the GUI menu, from the log- out menu, Konsole, and a TTY (CTRL+ALT+F2). I also have tried reinstalling a couple of times. Edit (also posted below): I made a post on a support site here: https://ubuntuforums.org/showthread.php?t=2466821. Even though this is clearly a bug in the 5.8+ kernels, updating to 5.11 and 20.04.3 still has this bug. The "solution" was to downgrade the kernel to 5.4, which is not a long-term sol
[Kernel-packages] [Bug 1943160] Re: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running.
This is the debdiff for Impish, Thanks.
** Changed in: nvidia-settings (Ubuntu)
Status: New => In Progress
** Patch added:
"nvidia-settings_470.57.01-0ubuntu1.dsc-to-nvidia-settings_470.57.01-0ubuntu2.dsc.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1943160/+attachment/5524162/+files/nvidia-settings_470.57.01-0ubuntu1.dsc-to-nvidia-settings_470.57.01-0ubuntu2.dsc.debdiff
** Tags added: oem-priority originate-from-1928911 sutton
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1943160
Title:
[SRU] It will take about 90+ seconds to open the 'Nvidia settings' app
when 'Power Saving mode' running.
Status in OEM Priority Project:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Bug description:
[Impact]
On some I+N configs, It will take about 90+ seconds to open the 'Nvidia
settings' window when 'Power Saving mode' running.
[Fix]
do not read config file if Nvidia driver did not loaded:
change nvidia-settings/src/nvidia-settings.c
if (!op->no_load) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, &conf, &systems);
to
if (!op->no_load && systems.n != 0) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, &conf, &systems);
[Test]
1. Install Ubuntu image.
2. Boot and login the system.
3. Open 'Nvidia Settings' app
4. Select the prime is 'Power saving' mode
5. Reboot system and login
6. Open 'Nvidia Settings' app
7. Verify the result
[Where problems will occur]
the "systems.n" gets from
NvCtrlConnectToSystem(op->ctrl_display, &systems);
If there is a possibility that systems.n is zero and we still need to read
nvidia config file, then it will be a problem. I tried and cannot find a
situation like that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943160/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942498] Re: can_bcm01 from can in ubuntu_ltp_stable crash system on F-OEM-5.13
Test passed with 5.13.0-1012.16 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609 ** Changed in: linux-signed-oem-5.13 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-signed-oem-5.13 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942498 Title: can_bcm01 from can in ubuntu_ltp_stable crash system on F-OEM-5.13 Status in ubuntu-kernel-tests: New Status in linux-signed-oem-5.13 package in Ubuntu: Invalid Status in linux-signed-oem-5.13 source package in Focal: Fix Committed Bug description: It looks like this is a test case for CVE-2021-3609 This issue does not exist in the last cycle for OEM 5.13.0-1010 as this test case does not exist back then. can_bcm01 test in ubuntu_ltp_stable/can will trigger the following error on 5.13.0-1011-oem and crash the system: Sep 3 04:30:20 spitfire kernel: [ 324.458389] LTP: starting can_bcm01 Sep 3 04:30:20 spitfire kernel: [ 324.474313] vcan: Virtual CAN interface driver Sep 3 04:30:20 spitfire systemd-networkd[1967]: ltp_vcan0: Link UP Sep 3 04:30:20 spitfire networkd-dispatcher[2025]: WARNING:Unknown index 4 seen, reloading interface list Sep 3 04:30:20 spitfire systemd-networkd[1967]: ltp_vcan0: Gained carrier Sep 3 04:30:20 spitfire systemd-udevd[4596]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Sep 3 04:30:20 spitfire systemd-udevd[4596]: Using default interface naming scheme 'v245'. Sep 3 04:30:20 spitfire kernel: [ 324.483778] can: controller area network core Sep 3 04:30:20 spitfire kernel: [ 324.483819] NET: Registered protocol family 29 Sep 3 04:30:20 spitfire kernel: [ 324.491947] can: broadcast manager protocol Sep 3 04:30:20 spitfire kernel: [ 324.515859] [ cut here ] Sep 3 04:30:20 spitfire kernel: [ 324.515863] WARNING: CPU: 7 PID: 4591 at lib/timerqueue.c:55 timerqueue_del+0x43/0x50 Sep 3 04:30:20 spitfire kernel: [ 324.515877] Modules linked in: can_bcm can vcan nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr intel_rapl_common i10nm_edac nfit x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ipmi_ssif rapl joydev input_leds efi_pstore isst_if_mbox_pci isst_if_mmio isst_if_common mei_me intel_pch_thermal mei ioatdma acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad mac_hid sch_fq_codel msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crct10dif_pclmul ast crc32_pclmul drm_vram_helper i2c_algo_bit drm_ttm_helper ttm ghash_clmulni_intel drm_kms_helper aesni_intel syscopyarea ixgbe sysfillrect sysimgblt fb_sys_fops crypto_simd cec xfrm_algo rc_core cryptd dca drm mdio ahci i2c_i801 xhci_pci i2c_smbus xhci_pci_renesas intel_pmt libahci wmi Sep 3 04:30:20 spitfire kernel: [ 324.515953] CPU: 7 PID: 4591 Comm: can_bcm01 Not tainted 5.13.0-1011-oem #15-Ubuntu Sep 3 04:30:20 spitfire kernel: [ 324.515957] Hardware name: Intel Corporation M50CYP2SB2U/M50CYP2SB2U, BIOS SE5C6200.86B.0021.D40.2101090208 01/09/2021 Sep 3 04:30:20 spitfire kernel: [ 324.515959] RIP: 0010:timerqueue_del+0x43/0x50 Sep 3 04:30:20 spitfire kernel: [ 324.515965] Code: 48 89 df e8 ef c5 ff ff 49 89 44 24 08 4c 89 e6 48 89 df e8 9f be ff ff 48 89 1b 49 8b 04 24 5b 41 5c 48 85 c0 5d 0f 95 c0 c3 <0f> 0b eb cb cc cc cc cc cc cc cc cc cc 48 8b 07 45 31 c0 48 83 c0 Sep 3 04:30:20 spitfire kernel: [ 324.515968] RSP: 0018:ff46f753c8917d40 EFLAGS: 00010046 Sep 3 04:30:20 spitfire kernel: [ 324.515972] RAX: 0001 RBX: ff3a23c5110cae50 RCX: Sep 3 04:30:20 spitfire kernel: [ 324.515974] RDX: RSI: ff3a23c5110cae50 RDI: ff3a23cc5f85f260 Sep 3 04:30:20 spitfire kernel: [ 324.515975] RBP: ff46f753c8917d50 R08: a3ce6048 R09: ff3a23c51bc84e40 Sep 3 04:30:20 spitfire kernel: [ 324.515977] R10: 0008 R11: ff3a23c54ea21a10 R12: ff3a23cc5f85f260 Sep 3 04:30:20 spitfire kernel: [ 324.515979] R13: R14: ff3a23cc5f85f100 R15: ff3a23c54ea2df10 Sep 3 04:30:20 spitfire kernel: [ 324.515980] FS: 7f196de15740() GS:ff3a23cc5f3c() knlGS: Sep 3 04:30:20 spitfire kernel: [ 324.515983] CS: 0010 DS: ES: CR0: 80050033 Sep 3 04:30:20 spitfire kernel: [ 324.515984] CR2: 7f196e008fec CR3: 00010ea66003 CR4: 00771ee0 Sep 3 04:30:20 spitfire kernel: [ 324.515986] DR0: DR1: DR2: Sep 3 04:30:20 spitfire kernel: [ 324.515988] DR3: DR6: fffe0ff0 DR7: 00
[Kernel-packages] [Bug 1943160] Re: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running.
This is the debdiff for Hirsute, Thanks.
** Patch added:
"nvidia-settings_470.57.01-0ubuntu0.21.04.1.dsc-to-nvidia-settings_470.57.01-0ubuntu1.21.04.1.dsc.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1943160/+attachment/5524152/+files/nvidia-settings_470.57.01-0ubuntu0.21.04.1.dsc-to-nvidia-settings_470.57.01-0ubuntu1.21.04.1.dsc.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1943160
Title:
[SRU] It will take about 90+ seconds to open the 'Nvidia settings' app
when 'Power Saving mode' running.
Status in OEM Priority Project:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Bug description:
[Impact]
On some I+N configs, It will take about 90+ seconds to open the 'Nvidia
settings' window when 'Power Saving mode' running.
[Fix]
do not read config file if Nvidia driver did not loaded:
change nvidia-settings/src/nvidia-settings.c
if (!op->no_load) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, &conf, &systems);
to
if (!op->no_load && systems.n != 0) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, &conf, &systems);
[Test]
1. Install Ubuntu image.
2. Boot and login the system.
3. Open 'Nvidia Settings' app
4. Select the prime is 'Power saving' mode
5. Reboot system and login
6. Open 'Nvidia Settings' app
7. Verify the result
[Where problems will occur]
the "systems.n" gets from
NvCtrlConnectToSystem(op->ctrl_display, &systems);
If there is a possibility that systems.n is zero and we still need to read
nvidia config file, then it will be a problem. I tried and cannot find a
situation like that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943160/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943160] Re: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running.
The attachment "nvidia-
settings_470.57.01-0ubuntu0.20.04.1-to-470.57.01-0ubuntu1.20.04.1.debdiff"
seems to be a debdiff. The ubuntu-sponsors team has been subscribed to
the bug report so that they can review and hopefully sponsor the
debdiff. If the attachment isn't a patch, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are member
of the ~ubuntu-sponsors, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1943160
Title:
[SRU] It will take about 90+ seconds to open the 'Nvidia settings' app
when 'Power Saving mode' running.
Status in OEM Priority Project:
In Progress
Status in nvidia-settings package in Ubuntu:
New
Bug description:
[Impact]
On some I+N configs, It will take about 90+ seconds to open the 'Nvidia
settings' window when 'Power Saving mode' running.
[Fix]
do not read config file if Nvidia driver did not loaded:
change nvidia-settings/src/nvidia-settings.c
if (!op->no_load) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, &conf, &systems);
to
if (!op->no_load && systems.n != 0) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, &conf, &systems);
[Test]
1. Install Ubuntu image.
2. Boot and login the system.
3. Open 'Nvidia Settings' app
4. Select the prime is 'Power saving' mode
5. Reboot system and login
6. Open 'Nvidia Settings' app
7. Verify the result
[Where problems will occur]
the "systems.n" gets from
NvCtrlConnectToSystem(op->ctrl_display, &systems);
If there is a possibility that systems.n is zero and we still need to read
nvidia config file, then it will be a problem. I tried and cannot find a
situation like that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943160/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943160] Re: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running.
This is the debdiff for Focal, Thanks.
** Patch added:
"nvidia-settings_470.57.01-0ubuntu0.20.04.1-to-470.57.01-0ubuntu1.20.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1943160/+attachment/5524144/+files/nvidia-settings_470.57.01-0ubuntu0.20.04.1-to-470.57.01-0ubuntu1.20.04.1.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1943160
Title:
[SRU] It will take about 90+ seconds to open the 'Nvidia settings' app
when 'Power Saving mode' running.
Status in OEM Priority Project:
In Progress
Status in nvidia-settings package in Ubuntu:
New
Bug description:
[Impact]
On some I+N configs, It will take about 90+ seconds to open the 'Nvidia
settings' window when 'Power Saving mode' running.
[Fix]
do not read config file if Nvidia driver did not loaded:
change nvidia-settings/src/nvidia-settings.c
if (!op->no_load) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, &conf, &systems);
to
if (!op->no_load && systems.n != 0) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, &conf, &systems);
[Test]
1. Install Ubuntu image.
2. Boot and login the system.
3. Open 'Nvidia Settings' app
4. Select the prime is 'Power saving' mode
5. Reboot system and login
6. Open 'Nvidia Settings' app
7. Verify the result
[Where problems will occur]
the "systems.n" gets from
NvCtrlConnectToSystem(op->ctrl_display, &systems);
If there is a possibility that systems.n is zero and we still need to read
nvidia config file, then it will be a problem. I tried and cannot find a
situation like that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943160/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943164] Re: touchpad not working
attached output when i try running cat /proc/bus/input/devices ** Attachment added: "devices" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1943164/+attachment/5524143/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943164 Title: touchpad not working Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: touchpad not working and i cant find touchpad when i try to run cat /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 10 00:14:00 2021 InstallationDate: Installed on 2021-09-09 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1943164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942902] Re: Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split corruption"
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
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/1942902
Title:
Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split
corruption"
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
New
Status in linux source package in Hirsute:
New
Bug description:
In order to address https://bugs.launchpad.net/bugs/1933074 the following
SAUCE patch was introduced.
Colin Ian King (1):
UBUNTU: SAUCE: ext4: fix directory index node split corruption
fs/ext4/namei.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
Meanwhile the issue addressed by this patch was fixed upstream with
commit 877ba3f729fd ("ext4: fix potential htree corruption when
growing large_dir directories").
The upstream patch was already cherry-picked to hirsute with "upstream
stable patchset 2021-08-30" [1] commit ffcc845ec245) and focal with
"v5.4.140 upstream stable release" [2] (commit 93ad4c3f59c6).
[1] BugLink: https://bugs.launchpad.net/bugs/1942123
[2] BugLink: https://bugs.launchpad.net/bugs/1941798
Therefore the SAUCE patch is obsolete and can be either dropped or
reverted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942902/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943164] [NEW] touchpad not working
Public bug reported: touchpad not working and i cant find touchpad when i try to run cat /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 10 00:14:00 2021 InstallationDate: Installed on 2021-09-09 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943164 Title: touchpad not working Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: touchpad not working and i cant find touchpad when i try to run cat /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 10 00:14:00 2021 InstallationDate: Installed on 2021-09-09 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1943164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
I tested kernel side of fix in ubuntu officially updated 5.11.0-34-generic. I think all 3 fixes are working fine headphones input/output unplugged by default, auto switch to internal/headphones on plug in/plug out and headphone microphone input. So, I have removed all temp fixes and started using the new drivers now very glad to finally receive the fix officially. Patiently waiting for pulseaudio fix to separate volume. I did notice one small issue, I think I forgot to test this before and not sure if I need to file a new bug report for it now. - When headphones are plugged in and if I restart/shutdown-turn on the laptop and log in it does not detect headphones microphone at all and internal microphone is selected. - For output device headphones are plugged in but left/right channel is merged into both channels - To fix this need to re-plug the headphones/earphones and the issue goes away or during first boot only plug in only after logging in. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943160] [NEW] [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running.
Public bug reported:
[Impact]
On some I+N configs, It will take about 90+ seconds to open the 'Nvidia
settings' window when 'Power Saving mode' running.
[Fix]
do not read config file if Nvidia driver did not loaded:
change nvidia-settings/src/nvidia-settings.c
if (!op->no_load) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, &conf, &systems);
to
if (!op->no_load && systems.n != 0) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, &conf, &systems);
[Test]
1. Install Ubuntu image.
2. Boot and login the system.
3. Open 'Nvidia Settings' app
4. Select the prime is 'Power saving' mode
5. Reboot system and login
6. Open 'Nvidia Settings' app
7. Verify the result
[Where problems will occur]
the "systems.n" gets from
NvCtrlConnectToSystem(op->ctrl_display, &systems);
If there is a possibility that systems.n is zero and we still need to read
nvidia config file, then it will be a problem. I tried and cannot find a
situation like that.
** Affects: oem-priority
Importance: Critical
Assignee: Shengyao Xue (xueshengyao)
Status: In Progress
** Affects: nvidia-settings (Ubuntu)
Importance: Undecided
Status: New
** Changed in: oem-priority
Status: New => In Progress
** Also affects: nvidia-settings (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1943160
Title:
[SRU] It will take about 90+ seconds to open the 'Nvidia settings' app
when 'Power Saving mode' running.
Status in OEM Priority Project:
In Progress
Status in nvidia-settings package in Ubuntu:
New
Bug description:
[Impact]
On some I+N configs, It will take about 90+ seconds to open the 'Nvidia
settings' window when 'Power Saving mode' running.
[Fix]
do not read config file if Nvidia driver did not loaded:
change nvidia-settings/src/nvidia-settings.c
if (!op->no_load) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, &conf, &systems);
to
if (!op->no_load && systems.n != 0) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, &conf, &systems);
[Test]
1. Install Ubuntu image.
2. Boot and login the system.
3. Open 'Nvidia Settings' app
4. Select the prime is 'Power saving' mode
5. Reboot system and login
6. Open 'Nvidia Settings' app
7. Verify the result
[Where problems will occur]
the "systems.n" gets from
NvCtrlConnectToSystem(op->ctrl_display, &systems);
If there is a possibility that systems.n is zero and we still need to read
nvidia config file, then it will be a problem. I tried and cannot find a
situation like that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943160/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
