[Kernel-packages] [Bug 1955644] 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 1955644 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/1955644 Title: AMD GPU driver warning found in log after crash Status in linux package in Ubuntu: Incomplete Bug description: With new Kubuntu 21.10 installation I experienced instabilities of my work system (when letting the system run over night, at morning the system had rebooted by itself and asks for disk encryption password). I had a look into the kernel log and I found an incident that may be related to the instability. Anyway there seems to be something going wrong. I have attached the log snippet as a text file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956373] [NEW] Fix for rare (~1%) s0ix failures o AMD systems
Public bug reported: [Impact] A rare (~1%) failure has been reported in the community for a period of time on Renoir platforms with s0ix. This failure was also corroborated once by a Cezanne user. [Fix] In the s0ix entry need retain gfx in the gfxoff state, so skipping setting gfx cgpg in the S0ix suspend-resume process. The fix was cherry-picked from 5.16-rc8. [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD systems that support s0ix. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Assignee: Alex Hung (alexhung) Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-1956259 ** Information type changed from Proprietary to Public ** Changed in: amd Assignee: (unassigned) => Alex Hung (alexhung) ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: amd ** Changed in: linux-oem-5.14 (Ubuntu) Assignee: (unassigned) => Alex Hung (alexhung) ** Tags added: amd oem-priority originate-from-1956259 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956373 Title: Fix for rare (~1%) s0ix failures o AMD systems Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] A rare (~1%) failure has been reported in the community for a period of time on Renoir platforms with s0ix. This failure was also corroborated once by a Cezanne user. [Fix] In the s0ix entry need retain gfx in the gfxoff state, so skipping setting gfx cgpg in the S0ix suspend-resume process. The fix was cherry-picked from 5.16-rc8. [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD systems that support s0ix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551154/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551150/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551143/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551153/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551140/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551149/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551145/+files/PaInfo.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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551142/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551148/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551144/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551141/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551147/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551146/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551138/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI
apport information ** Tags added: apport-collected ** Description changed: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V - I've updated the BIOS to latest version 1.12 already, with no better - result. What is the problem here, and how can I fix it? + I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu71 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: thomas 945 F pulseaudio + CasperMD5CheckResult: pass + CurrentDesktop: KDE + DistroRelease: Ubuntu 21.10 + InstallationDate: Installed on 2021-12-31 (4 days ago) + InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) + MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-22-generic N/A + linux-backports-modules-5.13.0-22-generic N/A + linux-firmware 1.201.3 + Tags: impish + Uname: Linux 5.13.0-22-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: 09/22/2021 + dmi.bios.release: 1.12 + dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED + dmi.bios.version: Version 1.12 + dmi.board.name: FJNBB6D + dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED + dmi.board.version: EQAB073106 + dmi.chassis.type: 10 + dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED + dmi.ec.firmware.release: 1.9 + dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: + dmi.product.family: LIFEBOOK-FTS + dmi.product.name: LIFEBOOK A3510 + dmi.product.sku: SK00 + dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551136/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably
[Kernel-packages] [Bug 1956177] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551151/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551152/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551155/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551139/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] 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 1956383 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: impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Incomplete Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938964] Re: icmp_redirect from selftests fails on F/kvm (unary operator expected)
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938964 Title: icmp_redirect from selftests fails on F/kvm (unary operator expected) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] If any sub-test in this icmp_redirect.sh is failing but not expected to fail. The script will complain: ./icmp_redirect.sh: line 72: [: 1: unary operator expected This is because when the sub-test is not expected to fail, we won't pass any value for the xfail local variable in log_test() and thus it's empty. Fix this by passing 0 as the 4th variable to log_test() for non-xfail cases. This issue can be found on our KVM kernel with SRU tests, they're failing because of missing some kernel configs. [Fix] * 39d8622c72 "selftests: icmp_redirect: pass xfail=0 to log_test()" This patch can be cherry-picked into all of the affected kernels. [Test Plan] Run the patched icmp_redirect.sh script with a KVM kernel (e.g. F/kvm), and this "unary operator expected" error message should no longer exist. [Where problems could occur] Change limited to test script, it won't have any impact to real kernel function. And this issue is most likely specific to KVM kernels. == Original Bug Report == icmp_redirect from selftect is failing on F/kvm 5.4.0-1045.47 # selftests: net: icmp_redirect.sh # # ### # Legacy routing # ### # # TEST: IPv4: redirect exception [ OK ] # TEST: IPv6: redirect exception [ OK ] # TEST: IPv4: redirect exception plus mtu [ OK ] # TEST: IPv6: redirect exception plus mtu [ OK ] # TEST: IPv4: routing reset [ OK ] # TEST: IPv6: routing reset [ OK ] # TEST: IPv4: mtu exception [ OK ] # TEST: IPv6: mtu exception [ OK ] # TEST: IPv4: mtu exception plus redirect [ OK ] # TEST: IPv6: mtu exception plus redirect [XFAIL] # # ### # Legacy routing with VRF # ### # # Error: Unknown device type. # Cannot find device "red" # Error: argument "red" is wrong: Invalid VRF # # Error: argument "red" is wrong: Invalid VRF # # Cannot find device "red" # Cannot find device "red" # Error: argument "red" is wrong: Not a valid VRF name # # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: redirect exception [FAIL] # Error: argument "red" is wrong: Invalid VRF # # TEST: IPv6: redirect exception [XFAIL] # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: redirect exception plus mtu [FAIL] # Error: argument "red" is wrong: Invalid VRF # # TEST: IPv6: redirect exception plus mtu [XFAIL] # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: routing reset [FAIL] # Error: argument "red" is wrong: Invalid VRF # # TEST: IPv6: routing reset [XFAIL] # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: mtu exception [FAIL] # Error: argument "red" is wrong: Invalid VRF # # TEST: IPv6: mtu exception [XFAIL] # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: mtu exception plus redirect
[Kernel-packages] [Bug 1956177] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1956177/+attachment/5551137/+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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955686] Re: alsa/sdw: fix the audio sdw codec parsing logic in the acpi table
** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955686 Title: alsa/sdw: fix the audio sdw codec parsing logic in the acpi table Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] we have a couple of Dell ADL laptops which have sdw audio, after upgrading the BIOS to 0.1.4 or above, the sdw audio can't work anymore, the driver can't parse the codec layout from ACPI table anymore. [Fix] Backport two patches from upstream. [Test] Boot the patched kernel on those machines both with old bios and new bios, all work well, the sdw audio could initialize and the audio function work well. [Where problems could occur] If it could introduce regression, it will be on the acpi sdw codec parsing, so some sdw audio machines could fail to find the codec, then the whole audio function fails. But this possibility is very low, we already tested the patches on both old bios and new bios. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1955686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956382] [NEW] package linux-modules-5.13.0-23-generic (not installed) failed to install/upgrade: »/lib/modules/5.13.0-23-generic/kernel/zfs/zfs.ko.dpkg-new« kann nicht geöffnet
Public bug reported: happened while update Linux kernel ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-modules-5.13.0-23-generic (not installed) ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tmk 19949 F pulseaudio /dev/snd/pcmC1D0p: tmk 19949 F...m pulseaudio CasperMD5CheckResult: unknown Date: Tue Jan 4 21:03:40 2022 DpkgHistoryLog: Start-Date: 2022-01-04 21:03:32 Commandline: aptdaemon role='role-commit-packages' sender=':1.1656' Install: linux-modules-extra-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-image-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-modules-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23:amd64 (5.13.0-23.23, automatic) Upgrade: linux-headers-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-image-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-libc-dev:amd64 (5.13.0-22.22, 5.13.0-23.23) DpkgTerminalLog: Vorbereitung zum Entpacken von .../0-linux-modules-5.13.0-23-generic_5.13.0-23.23_amd64.deb ... Entpacken von linux-modules-5.13.0-23-generic (5.13.0-23.23) ... dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-ie5ayf/0-linux-modules-5.13.0-23-generic_5.13.0-23.23_amd64.deb (--unpack): »/lib/modules/5.13.0-23-generic/kernel/zfs/zfs.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig ErrorMessage: »/lib/modules/5.13.0-23-generic/kernel/zfs/zfs.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig HibernationDevice: RESUME=UUID=2b4f4686-beea-42f6-bda8-1cc70f6f2f6d InstallationDate: Installed on 2019-09-27 (830 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E5450 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu47 SourcePackage: linux Title: package linux-modules-5.13.0-23-generic (not installed) failed to install/upgrade: »/lib/modules/5.13.0-23-generic/kernel/zfs/zfs.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 65.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd11/25/2019:br65.23:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr:sku062B: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956382 Title: package linux-modules-5.13.0-23-generic (not installed) failed to install/upgrade: »/lib/modules/5.13.0-23-generic/kernel/zfs/zfs.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig Status in linux package in Ubuntu: New Bug description: happened while update Linux kernel ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-modules-5.13.0-23-generic (not installed) ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tmk 19949 F pulseaudio /dev/snd/pcmC1D0p: tmk 19949 F...m pulseaudio CasperMD5CheckResult: unknown Date: Tue Jan 4 21:03:40 2022 DpkgHistoryLog: Start-Date: 2022-01-04 21:03:32 Commandline: aptdaemon role='role-commit-packages' sender=':1.1656' Install: linux-modules-extra-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-image-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-modules-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23:amd64 (5.13.0-23.23, automatic) Upgrade: linux-headers-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-image-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-libc-dev:amd64 (5.13.0-22.22, 5.13.0-23.23) DpkgTerminalLog: Vorbereitung zum
[Kernel-packages] [Bug 1956382] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956382 Title: package linux-modules-5.13.0-23-generic (not installed) failed to install/upgrade: »/lib/modules/5.13.0-23-generic/kernel/zfs/zfs.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig Status in linux package in Ubuntu: Confirmed Bug description: happened while update Linux kernel ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-modules-5.13.0-23-generic (not installed) ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tmk 19949 F pulseaudio /dev/snd/pcmC1D0p: tmk 19949 F...m pulseaudio CasperMD5CheckResult: unknown Date: Tue Jan 4 21:03:40 2022 DpkgHistoryLog: Start-Date: 2022-01-04 21:03:32 Commandline: aptdaemon role='role-commit-packages' sender=':1.1656' Install: linux-modules-extra-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-image-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-modules-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23:amd64 (5.13.0-23.23, automatic) Upgrade: linux-headers-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-image-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-libc-dev:amd64 (5.13.0-22.22, 5.13.0-23.23) DpkgTerminalLog: Vorbereitung zum Entpacken von .../0-linux-modules-5.13.0-23-generic_5.13.0-23.23_amd64.deb ... Entpacken von linux-modules-5.13.0-23-generic (5.13.0-23.23) ... dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-ie5ayf/0-linux-modules-5.13.0-23-generic_5.13.0-23.23_amd64.deb (--unpack): »/lib/modules/5.13.0-23-generic/kernel/zfs/zfs.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig ErrorMessage: »/lib/modules/5.13.0-23-generic/kernel/zfs/zfs.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig HibernationDevice: RESUME=UUID=2b4f4686-beea-42f6-bda8-1cc70f6f2f6d InstallationDate: Installed on 2019-09-27 (830 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E5450 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu47 SourcePackage: linux Title: package linux-modules-5.13.0-23-generic (not installed) failed to install/upgrade: »/lib/modules/5.13.0-23-generic/kernel/zfs/zfs.ko.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 65.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd11/25/2019:br65.23:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr:sku062B: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
In /etc/default/grub, I added the following kernel parameter: GRUB_CMDLINE_LINUX_DEFAULT="i915.enable_dc=0" Then run sudo update-grub and restart your computer. This disables GPU power management. It still freezes for a while, but then it is released and it seems to work. CPU usage seems to be at 100% when it does let go. I can now at least use my laptop without the dock or using the kernel recovery mode trick. You can also try limiting the CPU sleep states by adding: intel_idle.max_cstate=1 Try and see if one or both of those fixes it for you. I haven't had my laptop running for longer periods yet, so I don't know if this just delays the freezes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956381] [NEW] Focal update: v5.4.164 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.164 upstream stable release from git://git.kernel.org/ NFSv42: Fix pagecache invalidation after COPY/CLONE of: clk: Make self-contained arm64: dts: mcbin: support 2W SFP modules can: j1939: j1939_tp_cmd_recv(): check the dst address of TP.CM_BAM gfs2: Fix length of holes reported at end-of-file drm/sun4i: fix unmet dependency on RESET_CONTROLLER for PHY_SUN6I_MIPI_DPHY mac80211: do not access the IV when it was stripped net/smc: Transfer remaining wait queue entries during fallback atlantic: Fix OOB read and write in hw_atl_utils_fw_rpc_wait net: return correct error code platform/x86: thinkpad_acpi: Fix WWAN device disabled issue after S3 deep s390/setup: avoid using memblock_enforce_memory_limit btrfs: check-integrity: fix a warning on write caching disabled disk thermal: core: Reset previous low and high trip during thermal zone init scsi: iscsi: Unblock session then wake up error handler ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of bound net: ethernet: dec: tulip: de4x5: fix possible array overflows in type3_infoblock() perf hist: Fix memory leak of a perf_hpp_fmt perf report: Fix memory leaks around perf_tip() net/smc: Avoid warning of possible recursive locking vrf: Reset IPCB/IP6CB when processing outbound pkts in vrf dev xmit kprobes: Limit max data_size of the kretprobe instances rt2x00: do not mark device gone on EPROTO errors during start cpufreq: Fix get_cpu_device() failure in add_cpu_dev_symlink() s390/pci: move pseudo-MMIO to prevent MIO overlap fget: check that the fd still exists after getting a ref to it sata_fsl: fix UAF in sata_fsl_port_stop when rmmod sata_fsl sata_fsl: fix warning in remove_proc_entry when rmmod sata_fsl i2c: stm32f7: flush TX FIFO upon transfer errors i2c: stm32f7: recover the bus on access timeout i2c: stm32f7: stop dma transfer in case of NACK i2c: cbus-gpio: set atomic transfer callback natsemi: xtensa: fix section mismatch warnings net: qlogic: qlcnic: Fix a NULL pointer dereference in qlcnic_83xx_add_rings() net: mpls: Fix notifications when deleting a device siphash: use _unaligned version by default net/mlx4_en: Fix an use-after-free bug in mlx4_en_try_alloc_resources() selftests: net: Correct case name rxrpc: Fix rxrpc_local leak in rxrpc_lookup_peer() net: usb: lan78xx: lan78xx_phy_init(): use PHY_POLL instead of "0" if no IRQ is available net: marvell: mvpp2: Fix the computation of shared CPUs net: annotate data-races on txq->xmit_lock_owner ipv4: convert fib_num_tclassid_users to atomic_t net/rds: correct socket tunable error in rds_tcp_tune() net/smc: Keep smc_close_final rc during active close drm/msm: Do hw_init() before capturing GPU state ipv6: fix memory leak in fib6_rule_suppress KVM: x86/pmu: Fix reserved bits for AMD PerfEvtSeln register sched/uclamp: Fix rq->uclamp_max not set on first enqueue parisc: Fix KBUILD_IMAGE for self-extracting kernel parisc: Fix "make install" on newer debian releases vgacon: Propagate console boot parameters before calling `vc_resize' xhci: Fix commad ring abort, write all 64 bits to CRCR register. USB: NO_LPM quirk Lenovo Powered USB-C Travel Hub usb: typec: tcpm: Wait in SNK_DEBOUNCED until disconnect x86/tsc: Add a timer to make sure TSC_adjust is always checked x86/tsc: Disable clocksource watchdog for TSC on qualified platorms x86/64/mm: Map all kernel memory into trampoline_pgd tty: serial: msm_serial: Deactivate RX DMA for polling support serial: pl011: Add ACPI SBSA UART match id serial: core: fix transmit-buffer reset and memleak serial: 8250_pci: Fix ACCES entries in pci_serial_quirks array serial: 8250_pci: rewrite pericom_do_set_divisor() iwlwifi: mvm: retry init flow if failed parisc: Mark cr16 CPU clocksource unstable on all SMP machines net/tls: Fix authentication failure in CCM mode Linux 5.4.164 UBUNTU: upstream stable to v5.4.164 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In
[Kernel-packages] [Bug 1955717] 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 1955717 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/1955717 Title: BUG: unsupported FP instruction in kernel mode FPEXC == 0x4700 at the end of a btrfs balance to RAID1 Status in linux package in Ubuntu: Incomplete Bug description: Hello there, on my Raspberry Pi 4 I needed to convert a volume to RAID1, so I added a disk and launched btrfs balance: #> sudo btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/mountpoint The volume was 5 Tb worth of data, and after a couple of days the process looked terminated correctly, in "sudo btrfs filesystem show" everything looked ok: Label: 'mountpoint' uuid: 15d2c29b-dc20-48a9-910d-e1af8948ed08 Total devices 2 FS bytes used 4.38TiB devid1 size 5.45TiB used 5.16TiB path /dev/mapper/dev-sdb1 devid2 size 8.65TiB used 5.16TiB path /dev/mapper/dev-sda3 The total size is less than the single devices size because during the process I managed to free up 1 Tb of data. Anyway, I looked at the screen containing the balance command and it actually terminated with a segfault, and dmesg was reporting this: [ven dic 24 13:04:06 2021] BTRFS info (device dm-5): relocating block group 2177892352 flags data [ven dic 24 13:04:43 2021] BTRFS info (device dm-5): found 462 extents, stage: move data extents [ven dic 24 13:04:44 2021] BTRFS info (device dm-5): found 462 extents, stage: update data pointers [ven dic 24 13:04:44 2021] BTRFS info (device dm-5): relocating block group 1104150528 flags data [ven dic 24 13:05:22 2021] BTRFS info (device dm-5): found 2625 extents, stage: move data extents [ven dic 24 13:05:23 2021] BTRFS info (device dm-5): found 2625 extents, stage: update data pointers [ven dic 24 13:05:24 2021] BTRFS info (device dm-5): relocating block group 30408704 flags metadata|dup [ven dic 24 13:05:56 2021] BTRFS info (device dm-5): found 2412 extents, stage: move data extents [ven dic 24 13:06:00 2021] BTRFS info (device dm-5): relocating block group 22020096 flags system|dup [ven dic 24 13:06:01 2021] BTRFS info (device dm-5): balance: ended with status: 0 [ven dic 24 13:06:01 2021] BUG: unsupported FP instruction in kernel mode [ven dic 24 13:06:01 2021] FPEXC == 0x4700 [ven dic 24 13:06:01 2021] Internal error: Oops - undefined instruction: 0 [#1] SMP ARM [ven dic 24 13:06:01 2021] Modules linked in: rpcsec_gss_krb5 veth cdc_acm aes_arm_bs crypto_simd cryptd dm_crypt dm_mod fuse xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc overlay sg sch_fq_codel nfsd ip_tables x_tables ipv6 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq raid1 raid0 linear md_mod hid_logitech_hidpp joydev hid_logitech_dj brcmfmac brcmutil vc4 sha256_generic v3d cec gpu_sched drm_kms_helper cfg80211 bcm2835_codec(C) raspberrypi_hwmon rfkill bcm2835_v4l2(C) bcm2835_isp(C) bcm2835_mmal_vchiq(C) v4l2_mem2mem videobuf2_vmalloc videobuf2_dma_contig videobuf2_memops drm videobuf2_v4l2 videobuf2_common vc_sm_cma(C) videodev snd_bcm2835(C) mc drm_panel_orientation_quirks snd_soc_core rpivid_mem snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd syscopyarea sysfillrect [ven dic 24 13:06:01 2021] sysimgblt fb_sys_fops backlight uio_pdrv_genirq nvmem_rmem uio [last unloaded: cdc_acm] [ven dic 24 13:06:01 2021] CPU: 3 PID: 9141 Comm: btrfs Tainted: G C 5.10.63-v7l+ #1459 [ven dic 24 13:06:01 2021] Hardware name: BCM2711 [ven dic 24 13:06:01 2021] PC is at vfp_reload_hw+0x30/0x44 [ven dic 24 13:06:01 2021] LR is at __und_usr_fault_32+0x0/0x8 [ven dic 24 13:06:01 2021] pc : []lr : []psr: a0070013 [ven dic 24 13:06:01 2021] sp : ca0adfb0 ip : ca0adf30 fp : 0003 [ven dic 24 13:06:01 2021] r10: ca0ac1f8 r9 : c0201024 r8 : c1205048 [ven dic 24 13:06:01 2021] r7 : 0001 r6 : r5 : c0288068 r4 : c88f60f8 [ven dic 24 13:06:01 2021] r3 : c135607c r2 : b6cfeb8c r1 : ae24b2ce r0 : f421070d [ven dic 24 13:06:01 2021] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ven dic 24 13:06:01
[Kernel-packages] [Bug 1952234] Re: linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver
** Tags removed: verification-needed-bionic verification-needed-focal
verification-needed-hirsute verification-needed-impish
** Tags added: verification-done-bionic verification-done-focal
verification-done-hirsute verification-done-impish
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure-4.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1952234
Title:
linux-azure: add Icelake servers support in no-HWP mode to
cpufreq/intel_pstate driver
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-4.15 package in Ubuntu:
Invalid
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
Fix Committed
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-azure-4.15 source package in Focal:
Invalid
Status in linux-azure source package in Hirsute:
Fix Committed
Status in linux-azure-4.15 source package in Hirsute:
Invalid
Status in linux-azure source package in Impish:
Fix Committed
Status in linux-azure-4.15 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Starting with the AH2020 Azure host build, Hyper-V is virtualizing
some registers that provide information about the CPU frequency. The
registers are read-only in a guest VM, so the guest can see the
frequency, but cannot make any modifications.
This feature also requires that the VM Configuration Version be 9.2 or
later, which means it needs to be a new VM type, such as the just
introduced Dv5/Ev5 series, and the new M832v2 VMs.
Within the Linux VM, the presence of the feature is indicated by the
“aperfmperf” flag in the “lscpu” flags output (or in the flags field
in /proc/cpuinfo).
It turns out there is a Linux kernel limitation when running on the
new Intel IceLake processors used for the Dv5/Ev5 series. Upstream
commit fbdc21e9b038 was added to provide IceLake support in the 5.14
kernel.
Microsoft has asked to backport fbdc21e9b038 commit to all supported
kernels.
[Test Plan]
Run Intel IceLake based VM and check the "aperfmperf" flag in the
"lscpu" flags output.
Without the patch the intel_pstate directory is missing from
/sys/devices/system/cpu/ and /sys/devices/system/cpu/cpufreq/ is
empty.
[Where problems could occur]
* intel_pstate driver is always used on Intel IceLake based VMs
without checking for presence of "aperfmperf" CPU flag.
* In earlier (5.4 and 4.15) linux-azure kernels when intel_pstate
driver is used it is in "active" mode instead of "passive" one (as
reported by "cat /sys/devices/system/cpu/intel_pstate/status", also
"cat /sys/devices/system/cpu/cpufreq/policy0/scaling_driver" returns
"intel_pstate" instead of "intel_cpufreq" which is the expected
behavior when in "active" mode).
If a consistent behavior across all kernel versions is desired commit
33aa46f252c7 ("cpufreq: intel_pstate: Use passive mode by default
without HWP") from the upstream should probably also be backported.
* /sys/devices/system/cpu/cpufreq/policy*/scaling_{min,max}_freq files
can be modified and the values reported by kernel will no longer match
the values used by hardware.
[Other Info]
None.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1952234/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
Still the same with v5.16-rc8. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot Status in linux package in Ubuntu: Confirmed Bug description: I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to boot with either one. However, I am able to boot just fine with 5.14.0-rc7. journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-04 (62 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: wayland-session hirsute Uname: Linux 5.14.0-051400rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
** Changed in: linux (Ubuntu Impish) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1927808 Title: rtw88_8821ce causes freeze Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: Fix Committed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1927808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950144] Re: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm)
** Changed in: ubuntu-z-systems Status: Fix Committed => 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/1950144 Title: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm) Status in Ubuntu on IBM z Systems: Fix Released 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 Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * The kernel is unable to read partitions on virtio-block DASD (on KVM). That's a severe situation, since it prevents Ubuntu from starting, if installed on a DASD. This issue can either occur after a fresh installation or after an upgrade. * The virtio specification virtio-v1.1-cs01 states: "Transitional devices MUST detect Legacy drivers by detecting that VIRTIO_F_VERSION_1 has not been acknowledged by the driver." And this is what QEMU as of 6.1 has done relying solely on VIRTIO_F_VERSION_1 for detecting that. * But the specification also says: "... the driver MAY read (but MUST NOT write) the device-specific configuration fields to check that it can support the device ..." before setting FEATURES_OK. * In this case, any transitional device relying solely on VIRTIO_F_VERSION_1 for detecting legacy drivers will return data in legacy format. In particular, this implies that it's in big endian format for big endian guests. This naturally confuses the driver that expects little endian in the modern mode. * VIRTIO_F_VERSION_1 can only be relied on after the feature negotiation is done. * 'verify' is called before virtio_finalize_features(), so a transitional s390 virtio device still serves native endian (i.e. big endian) config space, while the driver knows that it is going to accept VERSION_1, so when reading the config space, it assumes it got little endian, and byteswaps. * For QEMU, we can work around the issue by writing out the feature bits with VIRTIO_F_VERSION_1 bit set. We (ab)use the finalize_features config op for this. This isn't enough to address all vhost devices since these do not get the features until FEATURES_OK, however it looks like the affected devices actually never handled the endianness for legacy mode correctly, so at least that's not a regression. [Fix] * 2f9a174f918e29608564c7a4e8329893ab604fb4 2f9a174f918e "virtio: write back F_VERSION_1 before validate" [Test Case] * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server 20.04 as KVM host. * This Ubuntu KVM host can either be installed on FCP or DASD storage, but at least one DASD disk need to be reserved for a KVM guest. * Now hand over the reserved DASD disk (low-level formatted using dasdfmt and partitioned using fdasd) using 'virtio-block' to a KVM virtual machine (e.g. using a virsh VM config). * Try to install an Ubuntu KVM virtual machine using this DASD disk, that includes the check and read of the partition table. [Where problems could occur] * First of all requested commit contains one additional if statement; and is due tothat relatively traceable. * But the change is in /drivers/virtio/virtio.c, means in common code! * This issue obviously affects big endian systems only. * But if done wrong, it may effect in worst-case little endian systems, too! * But the if statement explicitly checks for '!virtio_legacy_is_little_endian()'. * Only virtio net and virtio blk devices seem to be affected. * And the commit/solutions was in-depth discussed upstream here: https://lore.kernel.org/all/20211011053921.1198936-1-pa...@linux.ibm.com/t/#u [Other] * Patches are upstream accepted with since 5.15-rc6 and tagged for upstream stable #v4.11. Hence jammy is not affected. * Request was to add the patches to focal / 20.04, but to avoid potential regressions on upgrades, the patches need to be added to impish and hirsute, too. * Fortunately cherry-picking the commit works cleanly from all the affected Ubuntu releases. __ Description: kernel: unable to read partitions on virtio-block dasd (kvm) Symptom: unable to read partitions on virtio-block dasd (kvm) Problem: verify is called before virtio_finalize_features() , so a transitional s390 virtio device still serves native endian (i.e. big endian) config space, while the driver knows that it is going to accept VERSION_1, so when reading the config space, it assumes it got little endian, and byteswaps. Solution: For QEMU, we can work around the issue by
[Kernel-packages] [Bug 1955691] Re: audio mute/ mic mute are not working on a HP machine
** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux (Ubuntu Impish) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955691 Title: audio mute/ mic mute are not working on a HP machine Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not working on a HP platform [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1955691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955644] Re: AMD GPU driver warning found in log after crash
** 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/1955644 Title: AMD GPU driver warning found in log after crash Status in linux package in Ubuntu: New Bug description: With new Kubuntu 21.10 installation I experienced instabilities of my work system (when letting the system run over night, at morning the system had rebooted by itself and asks for disk encryption password). I had a look into the kernel log and I found an incident that may be related to the instability. Anyway there seems to be something going wrong. I have attached the log snippet as a text file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955717] Re: BUG: unsupported FP instruction in kernel mode FPEXC == 0x40000700 at the end of a btrfs balance to RAID1
** Package changed: apport (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/1955717 Title: BUG: unsupported FP instruction in kernel mode FPEXC == 0x4700 at the end of a btrfs balance to RAID1 Status in linux package in Ubuntu: New Bug description: Hello there, on my Raspberry Pi 4 I needed to convert a volume to RAID1, so I added a disk and launched btrfs balance: #> sudo btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/mountpoint The volume was 5 Tb worth of data, and after a couple of days the process looked terminated correctly, in "sudo btrfs filesystem show" everything looked ok: Label: 'mountpoint' uuid: 15d2c29b-dc20-48a9-910d-e1af8948ed08 Total devices 2 FS bytes used 4.38TiB devid1 size 5.45TiB used 5.16TiB path /dev/mapper/dev-sdb1 devid2 size 8.65TiB used 5.16TiB path /dev/mapper/dev-sda3 The total size is less than the single devices size because during the process I managed to free up 1 Tb of data. Anyway, I looked at the screen containing the balance command and it actually terminated with a segfault, and dmesg was reporting this: [ven dic 24 13:04:06 2021] BTRFS info (device dm-5): relocating block group 2177892352 flags data [ven dic 24 13:04:43 2021] BTRFS info (device dm-5): found 462 extents, stage: move data extents [ven dic 24 13:04:44 2021] BTRFS info (device dm-5): found 462 extents, stage: update data pointers [ven dic 24 13:04:44 2021] BTRFS info (device dm-5): relocating block group 1104150528 flags data [ven dic 24 13:05:22 2021] BTRFS info (device dm-5): found 2625 extents, stage: move data extents [ven dic 24 13:05:23 2021] BTRFS info (device dm-5): found 2625 extents, stage: update data pointers [ven dic 24 13:05:24 2021] BTRFS info (device dm-5): relocating block group 30408704 flags metadata|dup [ven dic 24 13:05:56 2021] BTRFS info (device dm-5): found 2412 extents, stage: move data extents [ven dic 24 13:06:00 2021] BTRFS info (device dm-5): relocating block group 22020096 flags system|dup [ven dic 24 13:06:01 2021] BTRFS info (device dm-5): balance: ended with status: 0 [ven dic 24 13:06:01 2021] BUG: unsupported FP instruction in kernel mode [ven dic 24 13:06:01 2021] FPEXC == 0x4700 [ven dic 24 13:06:01 2021] Internal error: Oops - undefined instruction: 0 [#1] SMP ARM [ven dic 24 13:06:01 2021] Modules linked in: rpcsec_gss_krb5 veth cdc_acm aes_arm_bs crypto_simd cryptd dm_crypt dm_mod fuse xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc overlay sg sch_fq_codel nfsd ip_tables x_tables ipv6 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq raid1 raid0 linear md_mod hid_logitech_hidpp joydev hid_logitech_dj brcmfmac brcmutil vc4 sha256_generic v3d cec gpu_sched drm_kms_helper cfg80211 bcm2835_codec(C) raspberrypi_hwmon rfkill bcm2835_v4l2(C) bcm2835_isp(C) bcm2835_mmal_vchiq(C) v4l2_mem2mem videobuf2_vmalloc videobuf2_dma_contig videobuf2_memops drm videobuf2_v4l2 videobuf2_common vc_sm_cma(C) videodev snd_bcm2835(C) mc drm_panel_orientation_quirks snd_soc_core rpivid_mem snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd syscopyarea sysfillrect [ven dic 24 13:06:01 2021] sysimgblt fb_sys_fops backlight uio_pdrv_genirq nvmem_rmem uio [last unloaded: cdc_acm] [ven dic 24 13:06:01 2021] CPU: 3 PID: 9141 Comm: btrfs Tainted: G C 5.10.63-v7l+ #1459 [ven dic 24 13:06:01 2021] Hardware name: BCM2711 [ven dic 24 13:06:01 2021] PC is at vfp_reload_hw+0x30/0x44 [ven dic 24 13:06:01 2021] LR is at __und_usr_fault_32+0x0/0x8 [ven dic 24 13:06:01 2021] pc : []lr : []psr: a0070013 [ven dic 24 13:06:01 2021] sp : ca0adfb0 ip : ca0adf30 fp : 0003 [ven dic 24 13:06:01 2021] r10: ca0ac1f8 r9 : c0201024 r8 : c1205048 [ven dic 24 13:06:01 2021] r7 : 0001 r6 : r5 : c0288068 r4 : c88f60f8 [ven dic 24 13:06:01 2021] r3 : c135607c r2 : b6cfeb8c r1 : ae24b2ce r0 : f421070d [ven dic 24 13:06:01 2021] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ven dic 24 13:06:01 2021] Control: 30c5383d Table: 0335dd80 DAC: [ven dic 24 13:06:01 2021] Process btrfs (pid: 9141, stack limit = 0x7d756e7e) [ven dic 24 13:06:01 2021] Stack: (0xca0adfb0 to 0xca0ae000) [ven dic 24 13:06:01 2021] dfa0: 00ad81d2 00491e87 0008 002c [ven dic 24 13:06:01 2021] dfc0: 0008 b6d95d28 00491e8f 00491e87 b6cef66d b6d95e4c [ven dic 24 13:06:01 2021] dfe0: 00ad81d2 be903718 b6cfa6d5 b6cfeb8c 80070010 [ven dic 24 13:06:01 2021]
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
I have installed 5.13.0-23, and doesn't seem the fix is there, or it
just doesn't work for my model. Does anyone know Which version was going
to have the fix?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Confirmed
Bug description:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
I installed the Ubuntu 21.10 beta and as soon as I boot I get the
kernel panic that I am attaching.
I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
5.13 kernel I get the same problem, disabling the trackpad and
trackpoint in the bios the problem disappears.
Everything works with the 5.11 kernel.
I remain available for further details and sorry for my lack of experience.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-16-generic 5.13.0-16.16
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pietro 1810 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 30 10:26:10 2021
InstallationDate: Installed on 2021-09-29 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20TA0033IX
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
dmi.bios.date: 09/02/2021
dmi.bios.release: 1.43
dmi.bios.vendor: LENOVO
dmi.bios.version: R1EET43W(1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TA0033IX
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.43
dmi.modalias:
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E14 Gen 2
dmi.product.name: 20TA0033IX
dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
dmi.product.version: ThinkPad E14 Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952674] Re: Kernel 5.13 fails to work with lots of hardware (HP Zbook)
Update: the 4700U graphics crash problem persists with the new 5.13.0-23 HWE kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1952674 Title: Kernel 5.13 fails to work with lots of hardware (HP Zbook) Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: The Internal display does not work. External monitors connected via Thunderbolt down continue to work. The trackpad does not work. The keyboard does work. The Ethernet on the Thunderbolt dock does not work. Booting the 5.11 kernel allows everything to work. I'm not sure how useful the automatically-attached files are since I had to boot with 5.11 in order to get the network working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-22-generic 5.13.0-22.22~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 30 10:37:03 2021 InstallationDate: Installed on 2021-08-30 (91 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 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.13/+bug/1952674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956380] [NEW] Focal update: v5.4.163 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.163 upstream stable release from git://git.kernel.org/ USB: serial: option: add Telit LE910S1 0x9200 composition USB: serial: option: add Fibocom FM101-GL variants usb: dwc2: gadget: Fix ISOC flow for elapsed frames usb: dwc2: hcd_queue: Fix use of floating point literal net: nexthop: fix null pointer dereference when IPv6 is not enabled usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts usb: hub: Fix usb enumeration issue due to address0 race usb: hub: Fix locking issues with address0_mutex binder: fix test regression due to sender_euid change ALSA: ctxfi: Fix out-of-range access media: cec: copy sequence field for the reply HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts staging/fbtft: Fix backlight staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect() xen: don't continue xenstore initialization in case of errors xen: detect uninitialized xenbus in xenbus_init KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB tracing/uprobe: Fix uprobe_perf_open probes iteration tracing: Fix pid filtering when triggers are attached mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB mdio: aspeed: Fix "Link is Down" issue PCI: aardvark: Deduplicate code in advk_pcie_rd_conf() PCI: aardvark: Wait for endpoint to be ready before training link PCI: aardvark: Fix big endian support PCI: aardvark: Train link immediately after enabling training PCI: aardvark: Improve link training PCI: aardvark: Issue PERST via GPIO PCI: aardvark: Replace custom macros by standard linux/pci_regs.h macros PCI: aardvark: Don't touch PCIe registers if no card connected PCI: aardvark: Fix compilation on s390 PCI: aardvark: Move PCIe reset card code to advk_pcie_train_link() PCI: aardvark: Update comment about disabling link training PCI: pci-bridge-emul: Fix array overruns, improve safety PCI: aardvark: Configure PCIe resources from 'ranges' DT property PCI: aardvark: Fix PCIe Max Payload Size setting PCI: aardvark: Implement re-issuing config requests on CRS response PCI: aardvark: Simplify initialization of rootcap on virtual bridge PCI: aardvark: Fix link training PCI: aardvark: Fix support for bus mastering and PCI_COMMAND on emulated bridge PCI: aardvark: Set PCI Bridge Class Code to PCI Bridge PCI: aardvark: Fix support for PCI_BRIDGE_CTL_BUS_RESET on emulated bridge pinctrl: armada-37xx: Correct PWM pins definitions arm64: dts: marvell: armada-37xx: Set pcie_reset_pin to gpio function proc/vmcore: fix clearing user buffer by properly using clear_user() netfilter: ipvs: Fix reuse connection if RS weight is 0 ARM: dts: BCM5301X: Fix I2C controller interrupt ARM: dts: BCM5301X: Add interrupt properties to GPIO node ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer ASoC: topology: Add missing rwsem around snd_ctl_remove() calls net: ieee802154: handle iftypes as u32 firmware: arm_scmi: pm: Propagate return value to caller NFSv42: Don't fail clone() unless the OP_CLONE operation failed ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE scsi: mpt3sas: Fix kernel panic during drive powercycle test drm/vc4: fix error code in vc4_create_object() iavf: Prevent changing static ITR values if adaptive moderation is on ipv6: fix typos in __ip6_finish_output() nfp: checking parameter process for rx-usecs/tx-usecs is invalid net: ipv6: add fib6_nh_release_dsts stub net: nexthop: release IPv6 per-cpu dsts when replacing a nexthop group scsi: core: sysfs: Fix setting device state to SDEV_RUNNING net/smc: Ensure the active closing peer first closes clcsock nvmet-tcp: fix incomplete data digest send net/ncsi : Add payload to be 32-bit aligned to fix dropped packets PM: hibernate: use correct mode for swsusp_close() tcp_cubic: fix spurious Hystart ACK train detections for not-cwnd-limited flows nvmet: use IOCB_NOWAIT only if the filesystem supports it igb: fix netpoll exit with traffic MIPS: use 3-level pgtable for 64KB page size on MIPS_VA_BITS_48 net: vlan: fix underflow for the real_dev refcnt net/smc: Don't call clcsock shutdown twice when smc shutdown net: hns3: fix VF RSS failed problem after PF enable multi-TCs net: mscc: ocelot: don't downgrade timestamping RX filters in SIOCSHWTSTAMP net: mscc: ocelot: correctly report the timestamping RX filters in ethtool f2fs: set SBI_NEED_FSCK flag when inconsistent node block found smb3: do not error on fsync when readonly vhost/vsock: fix incorrect used length reported to the guest tracing: Check pid filtering when creating events s390/mm: validate VMA in PGSTE
[Kernel-packages] [Bug 1942377] Re: Linux 5.16/5.15/5.14/4.13.14 fails to boot
>v5.16-rc8 Still fails to boot. It seems maintainers to be doing some kind of experiments known only to them. ** Summary changed: - Linux 5.15/5.14/4.13.14 fails to boot + Linux 5.16/5.15/5.14/4.13.14 fails to boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942377 Title: Linux 5.16/5.15/5.14/4.13.14 fails to boot Status in linux package in Ubuntu: Confirmed Bug description: Downloaded and installed packages of 5.14 from https://kernel.ubuntu.com/~kernel-ppa/mainline/ I found it is not able to boot. Please, look in attachment. Motherboard: Asus P5Q3 CPU: Intel(R) Xeon(R) CPU X5482 OS: Kubuntu 21.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2019-04-13 (872 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) Package: linux (not installed) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash Tags: hirsute Uname: Linux 5.13.13-051313-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to hirsute on 2021-01-06 (238 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene 1270 F pulseaudio /dev/snd/pcmC0D0p: eugene 1270 F...m pulseaudio /dev/snd/controlC2: eugene 1270 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (872 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.11.0-31-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 RfKill: Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-01-06 (238 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd06/11/2010:br11.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955717] [NEW] BUG: unsupported FP instruction in kernel mode FPEXC == 0x40000700 at the end of a btrfs balance to RAID1
You have been subscribed to a public bug: Hello there, on my Raspberry Pi 4 I needed to convert a volume to RAID1, so I added a disk and launched btrfs balance: #> sudo btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/mountpoint The volume was 5 Tb worth of data, and after a couple of days the process looked terminated correctly, in "sudo btrfs filesystem show" everything looked ok: Label: 'mountpoint' uuid: 15d2c29b-dc20-48a9-910d-e1af8948ed08 Total devices 2 FS bytes used 4.38TiB devid1 size 5.45TiB used 5.16TiB path /dev/mapper/dev-sdb1 devid2 size 8.65TiB used 5.16TiB path /dev/mapper/dev-sda3 The total size is less than the single devices size because during the process I managed to free up 1 Tb of data. Anyway, I looked at the screen containing the balance command and it actually terminated with a segfault, and dmesg was reporting this: [ven dic 24 13:04:06 2021] BTRFS info (device dm-5): relocating block group 2177892352 flags data [ven dic 24 13:04:43 2021] BTRFS info (device dm-5): found 462 extents, stage: move data extents [ven dic 24 13:04:44 2021] BTRFS info (device dm-5): found 462 extents, stage: update data pointers [ven dic 24 13:04:44 2021] BTRFS info (device dm-5): relocating block group 1104150528 flags data [ven dic 24 13:05:22 2021] BTRFS info (device dm-5): found 2625 extents, stage: move data extents [ven dic 24 13:05:23 2021] BTRFS info (device dm-5): found 2625 extents, stage: update data pointers [ven dic 24 13:05:24 2021] BTRFS info (device dm-5): relocating block group 30408704 flags metadata|dup [ven dic 24 13:05:56 2021] BTRFS info (device dm-5): found 2412 extents, stage: move data extents [ven dic 24 13:06:00 2021] BTRFS info (device dm-5): relocating block group 22020096 flags system|dup [ven dic 24 13:06:01 2021] BTRFS info (device dm-5): balance: ended with status: 0 [ven dic 24 13:06:01 2021] BUG: unsupported FP instruction in kernel mode [ven dic 24 13:06:01 2021] FPEXC == 0x4700 [ven dic 24 13:06:01 2021] Internal error: Oops - undefined instruction: 0 [#1] SMP ARM [ven dic 24 13:06:01 2021] Modules linked in: rpcsec_gss_krb5 veth cdc_acm aes_arm_bs crypto_simd cryptd dm_crypt dm_mod fuse xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc overlay sg sch_fq_codel nfsd ip_tables x_tables ipv6 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq raid1 raid0 linear md_mod hid_logitech_hidpp joydev hid_logitech_dj brcmfmac brcmutil vc4 sha256_generic v3d cec gpu_sched drm_kms_helper cfg80211 bcm2835_codec(C) raspberrypi_hwmon rfkill bcm2835_v4l2(C) bcm2835_isp(C) bcm2835_mmal_vchiq(C) v4l2_mem2mem videobuf2_vmalloc videobuf2_dma_contig videobuf2_memops drm videobuf2_v4l2 videobuf2_common vc_sm_cma(C) videodev snd_bcm2835(C) mc drm_panel_orientation_quirks snd_soc_core rpivid_mem snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd syscopyarea sysfillrect [ven dic 24 13:06:01 2021] sysimgblt fb_sys_fops backlight uio_pdrv_genirq nvmem_rmem uio [last unloaded: cdc_acm] [ven dic 24 13:06:01 2021] CPU: 3 PID: 9141 Comm: btrfs Tainted: G C 5.10.63-v7l+ #1459 [ven dic 24 13:06:01 2021] Hardware name: BCM2711 [ven dic 24 13:06:01 2021] PC is at vfp_reload_hw+0x30/0x44 [ven dic 24 13:06:01 2021] LR is at __und_usr_fault_32+0x0/0x8 [ven dic 24 13:06:01 2021] pc : []lr : []psr: a0070013 [ven dic 24 13:06:01 2021] sp : ca0adfb0 ip : ca0adf30 fp : 0003 [ven dic 24 13:06:01 2021] r10: ca0ac1f8 r9 : c0201024 r8 : c1205048 [ven dic 24 13:06:01 2021] r7 : 0001 r6 : r5 : c0288068 r4 : c88f60f8 [ven dic 24 13:06:01 2021] r3 : c135607c r2 : b6cfeb8c r1 : ae24b2ce r0 : f421070d [ven dic 24 13:06:01 2021] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ven dic 24 13:06:01 2021] Control: 30c5383d Table: 0335dd80 DAC: [ven dic 24 13:06:01 2021] Process btrfs (pid: 9141, stack limit = 0x7d756e7e) [ven dic 24 13:06:01 2021] Stack: (0xca0adfb0 to 0xca0ae000) [ven dic 24 13:06:01 2021] dfa0: 00ad81d2 00491e87 0008 002c [ven dic 24 13:06:01 2021] dfc0: 0008 b6d95d28 00491e8f 00491e87 b6cef66d b6d95e4c [ven dic 24 13:06:01 2021] dfe0: 00ad81d2 be903718 b6cfa6d5 b6cfeb8c 80070010 [ven dic 24 13:06:01 2021] Backtrace: invalid frame pointer 0x0003 [ven dic 24 13:06:01 2021] Code: 128aa080 e89a0162 e3110102 0a03 (eee96a10) [ven dic 24 13:06:01 2021] ---[ end trace b013d23166ad7965 ]--- I'm running Ubuntu 20.04 32 bit with kernel 5.10.63-v7l+ and btrfs- progs/btrfs-tools at these versions: ii btrfs-progs5.4.1-2armhfChecksumming Copy on Write Filesystem utilities ii btrfs-tools4.15.1-1build1 armhftransitional
[Kernel-packages] [Bug 1955644] [NEW] AMD GPU driver warning found in log after crash
You have been subscribed to a public bug: With new Kubuntu 21.10 installation I experienced instabilities of my work system (when letting the system run over night, at morning the system had rebooted by itself and asks for disk encryption password). I had a look into the kernel log and I found an incident that may be related to the instability. Anyway there seems to be something going wrong. I have attached the log snippet as a text file. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- AMD GPU driver warning found in log after crash https://bugs.launchpad.net/bugs/1955644 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 1948701] Re: Hard system lock under 5.* kernel on standard laptop
Bump. This bug is still open AFAICT. And I just realized that the real cost to me on this machine (which otherwise runs great with the old 4.* kernel) is that I cannot launch Docker containers any more. Which stinks. Machine otherwise happy and stable under 21.10 *provided I run the ancient kernel*. If there is something I could or should test, please let me know and I will. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948701 Title: Hard system lock under 5.* kernel on standard laptop Status in linux package in Ubuntu: Confirmed Bug description: This issue appeared first under 21.04, and I (wrongly) suspected a bug in the window manager or graphics stack. I posted on askubuntu at https://askubuntu.com/questions/1346317/ubuntu-21-04-and-21-10-lock- hard-with-basic-gui-redrawing-using-standard-intel-g and even offered a bounty but no luck. I then hopen 21.10 may solve it, but alas, no. At issue is a fairly immediate system lock as soon as I use Chrome or Slack and switch desktops. It typically locks the machine with minutes of a reboot -- making it unuseable under GUI. On the other hand, I kept it running 'headless' (just ssh'ed in from byobu running on my desktop) for a month so I had some reason to believe the hard ware was not at fault. Now, more recently, I realized that I had not tried an older kernel, and indeed under 4.13.0-46-generic, still installed from an older relese, everything runs fine! I would be happy to help debug if you pointers or test builds. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16 Uname: Linux 4.13.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edd2005 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Oct 25 13:04:38 2021 HibernationDevice: RESUME=UUID=97ca6744-22ea-45bd-bf19-38197b40062c InstallationDate: Installed on 2016-08-08 (1904 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20FCCTO1WW ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-46-generic root=UUID=5f3d6606-96bb-422c-9918-62d7cf6850fb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-46-generic N/A linux-backports-modules-4.13.0-46-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-14 (11 days ago) dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FCCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FCCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 4th dmi.product.name: 20FCCTO1WW dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956373] [NEW] Fix for rare (~1%) s0ix failures o AMD systems
You have been subscribed to a public bug: [Impact] A rare (~1%) failure has been reported in the community for a period of time on Renoir platforms with s0ix. This failure was also corroborated once by a Cezanne user. [Fix] In the s0ix entry need retain gfx in the gfxoff state, so skipping setting gfx cgpg in the S0ix suspend-resume process. The fix was cherry-picked from 5.16-rc8. [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD systems that support s0ix. ** Affects: amd Importance: Undecided Assignee: Alex Hung (alexhung) Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New -- Fix for rare (~1%) s0ix failures o AMD systems https://bugs.launchpad.net/bugs/1956373 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 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 1956383] [NEW] Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot
Public bug reported: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Incomplete Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952621] Re: Bionic/linux-azure: Call trace on Ubuntu 18.04 VM with Standard NV24
This bug was fixed in the package linux-azure-5.4 - 5.4.0-1065.68~18.04.1 --- linux-azure-5.4 (5.4.0-1065.68~18.04.1) bionic; urgency=medium * bionic/linux-azure-5.4: 5.4.0-1065.68~18.04.1 -proposed tracker (LP: #1952289) [ Ubuntu: 5.4.0-1065.68 ] * focal/linux-azure: 5.4.0-1065.68 -proposed tracker (LP: #1952290) * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632) - [Config] azure: enable CONFIG_DEBUG_INFO_BTF * Support builtin revoked certificates (LP: #1932029) - [Config] azure: set CONFIG_SYSTEM_REVOCATION_KEYS * Bionic/linux-azure: Call trace on Ubuntu 18.04 VM with Standard NV24 (LP: #1952621) - PCI/sysfs: Convert "config" to static attribute * linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver (LP: #1952234) - cpufreq: intel_pstate: Add Icelake servers support in no-HWP mode * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - debian/dkms-versions -- update from kernel-versions (main/2021.11.29) * CVE-2021-4002 - tlb: mmu_gather: add tlb_flush_*_range APIs - hugetlbfs: flush TLBs correctly after huge_pmd_unshare * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632) - [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462) - KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again - jump_label: Fix usage in module __init * Support builtin revoked certificates (LP: #1932029) - Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about cert lists that aren't present." - integrity: Move import of MokListRT certs to a separate routine - integrity: Load certs from the EFI MOK config table - certs: Add ability to preload revocation certs - integrity: Load mokx variables into the blacklist keyring - certs: add 'x509_revocation_list' to gitignore - SAUCE: Dump stack when X.509 certificates cannot be loaded - [Packaging] build canonical-revoked-certs.pem from branch/arch certs - [Packaging] Revoke 2012 UEFI signing certificate as built-in - [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys * Support importing mokx keys into revocation list from the mok table (LP: #1928679) - efi: Support for MOK variable config table - efi: mokvar-table: fix some issues in new code - efi: mokvar: add missing include of asm/early_ioremap.h - efi/mokvar: Reserve the table only if it is in boot services data - SAUCE: integrity: add informational messages when revoking certs * Support importing mokx keys into revocation list from the mok table (LP: #1928679) // CVE-2020-26541 when certificates are revoked via MokListXRT. - SAUCE: integrity: Load mokx certs from the EFI MOK config table * Focal update: v5.4.157 upstream stable release (LP: #1951883) - ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned - ARM: 9134/1: remove duplicate memcpy() definition - ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype - ARM: 9141/1: only warn about XIP address when not compile testing - ipv6: use siphash in rt6_exception_hash() - ipv4: use siphash instead of Jenkins in fnhe_hashfun() - usbnet: sanity check for maxpacket - usbnet: fix error return code in usbnet_probe() - Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" - ata: sata_mv: Fix the error handling of mv_chip_id() - nfc: port100: fix using -ERRNO as command type mask - net/tls: Fix flipped sign in tls_err_abort() calls - mmc: vub300: fix control-message timeouts - mmc: cqhci: clear HALT state after CQE enable - mmc: dw_mmc: exynos: fix the finding clock sample value - mmc: sdhci: Map more voltage level to SDHCI_POWER_330 - mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit - cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() - net: lan78xx: fix division by zero in send path - tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function - IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields - IB/hfi1: Fix abba locking issue with sc_disable() - nvmet-tcp: fix data digest pointer calculation - nvme-tcp: fix data digest pointer calculation - RDMA/mlx5: Set user priority for DCT - arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node - regmap: Fix possible double-free in regcache_rbtree_exit() - net: batman-adv: fix error handling - net: Prevent infinite while loop in skb_tx_hash() - RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string - nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST - net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume fails - net: ethernet: microchip:
[Kernel-packages] [Bug 1952621] Re: Bionic/linux-azure: Call trace on Ubuntu 18.04 VM with Standard NV24
This bug was fixed in the package linux-azure - 5.4.0-1065.68 --- linux-azure (5.4.0-1065.68) focal; urgency=medium * focal/linux-azure: 5.4.0-1065.68 -proposed tracker (LP: #1952290) * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632) - [Config] azure: enable CONFIG_DEBUG_INFO_BTF * Support builtin revoked certificates (LP: #1932029) - [Config] azure: set CONFIG_SYSTEM_REVOCATION_KEYS * Bionic/linux-azure: Call trace on Ubuntu 18.04 VM with Standard NV24 (LP: #1952621) - PCI/sysfs: Convert "config" to static attribute * linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver (LP: #1952234) - cpufreq: intel_pstate: Add Icelake servers support in no-HWP mode [ Ubuntu: 5.4.0-92.103 ] * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - debian/dkms-versions -- update from kernel-versions (main/2021.11.29) * CVE-2021-4002 - tlb: mmu_gather: add tlb_flush_*_range APIs - hugetlbfs: flush TLBs correctly after huge_pmd_unshare * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632) - [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462) - KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again - jump_label: Fix usage in module __init * Support builtin revoked certificates (LP: #1932029) - Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about cert lists that aren't present." - integrity: Move import of MokListRT certs to a separate routine - integrity: Load certs from the EFI MOK config table - certs: Add ability to preload revocation certs - integrity: Load mokx variables into the blacklist keyring - certs: add 'x509_revocation_list' to gitignore - SAUCE: Dump stack when X.509 certificates cannot be loaded - [Packaging] build canonical-revoked-certs.pem from branch/arch certs - [Packaging] Revoke 2012 UEFI signing certificate as built-in - [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys * Support importing mokx keys into revocation list from the mok table (LP: #1928679) - efi: Support for MOK variable config table - efi: mokvar-table: fix some issues in new code - efi: mokvar: add missing include of asm/early_ioremap.h - efi/mokvar: Reserve the table only if it is in boot services data - SAUCE: integrity: add informational messages when revoking certs * Support importing mokx keys into revocation list from the mok table (LP: #1928679) // CVE-2020-26541 when certificates are revoked via MokListXRT. - SAUCE: integrity: Load mokx certs from the EFI MOK config table * Focal update: v5.4.157 upstream stable release (LP: #1951883) - ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned - ARM: 9134/1: remove duplicate memcpy() definition - ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype - ARM: 9141/1: only warn about XIP address when not compile testing - ipv6: use siphash in rt6_exception_hash() - ipv4: use siphash instead of Jenkins in fnhe_hashfun() - usbnet: sanity check for maxpacket - usbnet: fix error return code in usbnet_probe() - Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" - ata: sata_mv: Fix the error handling of mv_chip_id() - nfc: port100: fix using -ERRNO as command type mask - net/tls: Fix flipped sign in tls_err_abort() calls - mmc: vub300: fix control-message timeouts - mmc: cqhci: clear HALT state after CQE enable - mmc: dw_mmc: exynos: fix the finding clock sample value - mmc: sdhci: Map more voltage level to SDHCI_POWER_330 - mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit - cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() - net: lan78xx: fix division by zero in send path - tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function - IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields - IB/hfi1: Fix abba locking issue with sc_disable() - nvmet-tcp: fix data digest pointer calculation - nvme-tcp: fix data digest pointer calculation - RDMA/mlx5: Set user priority for DCT - arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node - regmap: Fix possible double-free in regcache_rbtree_exit() - net: batman-adv: fix error handling - net: Prevent infinite while loop in skb_tx_hash() - RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string - nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST - net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume fails - net: ethernet: microchip: lan743x: Fix dma allocation failure by using dma_set_mask_and_coherent - net: nxp: lpc_eth.c: avoid
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time
Same Errors and behavior here with Ubuntu Budgie 21.10 after upgrade to 5.13.0-23 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-33-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time
Additional Info: AMD Ryzen 5 3400G with AMDGPU -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-33-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955932] Re: ps5 controller no longer working
This was probably a regression in either a kernel update or a Xorg update. Both happened in mid-to-late December. ** Package changed: xorg-server (Ubuntu) => linux-hwe-5.11 (Ubuntu) ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags added: regression-update -- 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/1955932 Title: ps5 controller no longer working Status in linux-hwe-5.11 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hello! Up until today, my playstation 5 controller worked great with ubuntu + steam both over bluetooth and wired. Now, I can get the controller connected via bluetooth, and I can use `jstest /dev/input/js0` to read input from the controller in my terminal, but Steam no longer recognizes the controller. This bug only just started happening today. When I check in my journalctl logs when connecting the controller, I see the following, which indicates that perhaps something is going wrong... ``` Dez 28 23:43:13 zagreus kernel: hid-generic 0005:054C:0CE6.0023: unknown main item tag 0x0 Dez 28 23:43:13 zagreus kernel: input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:8/0005:054C:0CE6.0023/input/input65 Dez 28 23:43:13 zagreus kernel: hid-generic 0005:054C:0CE6.0023: input,hidraw8: BLUETOOTH HID v1.00 Gamepad [Wireless Controller] on 9c:b6:d0:ef:fd:7c Dez 28 23:43:13 zagreus systemd-udevd[14721]: js0: Process '/usr/bin/jscal-restore /dev/input/js0' failed with exit code 1. Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) config/udev: Adding input device Wireless Controller (/dev/input/js0) Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) No input driver specified, ignoring this device. Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) This device may have been added with another device file. Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) config/udev: Adding input device Wireless Controller (/dev/input/event30) Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) No input driver specified, ignoring this device. Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) This device may have been added with another device file. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 28 23:49:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:082a] InstallationDate: Installed on 2020-10-25 (429 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-43-generic root=/dev/mapper/vgubuntu-root ro ipv6.disable=1 quiet splash ipv6.disable=1 vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2019 dmi.bios.release: 2.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 0TPN17 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:br2.11:svnDellInc.:pnXPS139360:pvr:sku082A:rvnDellInc.:rn0TPN17:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 082A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-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/1955932/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1952234] Re: linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver
This bug was fixed in the package linux-azure - 5.11.0-1023.24 --- linux-azure (5.11.0-1023.24) hirsute; urgency=medium * hirsute/linux-azure: 5.11.0-1023.24 -proposed tracker (LP: #1952268) * Enable arm64 for Hyper-V guests (LP: #1949770) - Drivers: hv: vmbus: Move Hyper-V page allocator to arch neutral code - x86/hyper-v: Move hv_message_type to architecture neutral module - Drivers: hv: Redo Hyper-V synthetic MSR get/set functions - Drivers: hv: vmbus: Move hyperv_report_panic_msg to arch neutral code - Drivers: hv: vmbus: Handle auto EOI quirk inline - Drivers: hv: vmbus: Move handling of VMbus interrupts - clocksource/drivers/hyper-v: Handle vDSO differences inline - clocksource/drivers/hyper-v: Handle sched_clock differences inline - asm-generic/hyperv: change HV_CPU_POWER_MANAGEMENT to HV_CPU_MANAGEMENT - x86/hyperv: detect if Linux is the root partition - clocksource/hyperv: use MSR-based access if running as root - clocksource/drivers/hyper-v: Set clocksource rating based on Hyper-V feature - clocksource/drivers/hyper-v: Move handling of STIMER0 interrupts - drivers: hv: Fix whitespace errors - x86/Hyper-V: Support for free page reporting - x86/hyperv: Move hv_do_rep_hypercall to asm-generic - drivers: hv: Create a consistent pattern for checking Hyper-V hypercall status - arm64: smccc: Add support for SMCCCv1.2 extended input/output registers - Drivers: hv: Move Hyper-V extended capability check to arch neutral code - asm-generic/hyperv: Add missing #include of nmi.h - arm64: hyperv: Add Hyper-V hypercall and register access utilities - arm64: hyperv: Add panic handler - arm64: hyperv: Initialize hypervisor on boot - arm64: efi: Export screen_info - Drivers: hv: Enable Hyper-V code to be built on ARM64 - [Packaging] linux-azure: Add basic packaging support for arm64 - [Config] linux-azure: Extending existing annotations to arm64 - [Config] linux-azure: Generate initial config for arm64 - [Packaging] linux-azure: Ignore initial arm64 ABI - Drivers: hv: Make portions of Hyper-V init code be arch neutral - Drivers: hv: Add arch independent default functions for some Hyper-V handlers - Drivers: hv: Move Hyper-V misc functionality to arch-neutral code - drivers: hv: Decouple Hyper-V clock/timer code from VMbus drivers - PCI: Introduce domain_nr in pci_host_bridge - PCI: Support populating MSI domains of root buses via bridges - arm64: PCI: Restructure pcibios_root_bridge_prepare() - arm64: PCI: Support root bridge preparation for Hyper-V - PCI: hv: Generify PCI probing - PCI: hv: Set ->domain_nr of pci_host_bridge at probing time - PCI: hv: Turn on the host bridge probing on ARM64 - PCI: hv: Set up MSI domain at bridge probing time - [Config] azure: COMMON_CLK_XLNX_CLKWZRD=m - PCI: hv: Support for create interrupt v3 - SAUCE: PCI: hv: Make the code arch neutral by adding arch specific interfaces - SAUCE: arm64: PCI: hv: Add support for Hyper-V vPCI - [Packaging] Update CONFIG_PCI_HYPERV policy for arm64 - PCI: hv: Drop msi_controller structure - clocksource/drivers/hyper-v: Re-enable VDSO_CLOCKMODE_HVCLOCK on X86 * linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver (LP: #1952234) - cpufreq: intel_pstate: Add Icelake servers support in no-HWP mode * hirsute/linux-azure: Backport more CIFS patches (LP: #1950336) - cifs: To match file servers, make sure the server hostname matches - cifs: add mount parameter tcpnodelay [ Ubuntu: 5.11.0-42.46 ] * hirsute/linux: 5.11.0-42.46 -proposed tracker (LP: #1952278) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - debian/dkms-versions -- update from kernel-versions (main/2021.11.29) * CVE-2021-4002 - hugetlbfs: flush TLBs correctly after huge_pmd_unshare * CVE-2021-43267 - tipc: fix size validations for the MSG_CRYPTO type * Hirsute update: upstream stable patchset 2021-11-24 (LP: #1952136) - ext4: check and update i_disksize properly - ext4: correct the error path of ext4_write_inline_data_end() - ASoC: Intel: sof_sdw: tag SoundWire BEs as non-atomic - HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS - netfilter: ip6_tables: zero-initialize fragment offset - HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs - ASoC: SOF: loader: release_firmware() on load failure to avoid batching - netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic - netfilter: nf_nat_masquerade: defer conntrack walk to work queue - mac80211: Drop frames from invalid MAC address in ad-hoc mode - m68k: Handle arrivals of multiple signals correctly - hwmon: (ltc2947) Properly handle errors when looking for the external clock - net:
[Kernel-packages] [Bug 1950644] Re: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels
This bug was fixed in the package linux-azure - 5.11.0-1023.24 --- linux-azure (5.11.0-1023.24) hirsute; urgency=medium * hirsute/linux-azure: 5.11.0-1023.24 -proposed tracker (LP: #1952268) * Enable arm64 for Hyper-V guests (LP: #1949770) - Drivers: hv: vmbus: Move Hyper-V page allocator to arch neutral code - x86/hyper-v: Move hv_message_type to architecture neutral module - Drivers: hv: Redo Hyper-V synthetic MSR get/set functions - Drivers: hv: vmbus: Move hyperv_report_panic_msg to arch neutral code - Drivers: hv: vmbus: Handle auto EOI quirk inline - Drivers: hv: vmbus: Move handling of VMbus interrupts - clocksource/drivers/hyper-v: Handle vDSO differences inline - clocksource/drivers/hyper-v: Handle sched_clock differences inline - asm-generic/hyperv: change HV_CPU_POWER_MANAGEMENT to HV_CPU_MANAGEMENT - x86/hyperv: detect if Linux is the root partition - clocksource/hyperv: use MSR-based access if running as root - clocksource/drivers/hyper-v: Set clocksource rating based on Hyper-V feature - clocksource/drivers/hyper-v: Move handling of STIMER0 interrupts - drivers: hv: Fix whitespace errors - x86/Hyper-V: Support for free page reporting - x86/hyperv: Move hv_do_rep_hypercall to asm-generic - drivers: hv: Create a consistent pattern for checking Hyper-V hypercall status - arm64: smccc: Add support for SMCCCv1.2 extended input/output registers - Drivers: hv: Move Hyper-V extended capability check to arch neutral code - asm-generic/hyperv: Add missing #include of nmi.h - arm64: hyperv: Add Hyper-V hypercall and register access utilities - arm64: hyperv: Add panic handler - arm64: hyperv: Initialize hypervisor on boot - arm64: efi: Export screen_info - Drivers: hv: Enable Hyper-V code to be built on ARM64 - [Packaging] linux-azure: Add basic packaging support for arm64 - [Config] linux-azure: Extending existing annotations to arm64 - [Config] linux-azure: Generate initial config for arm64 - [Packaging] linux-azure: Ignore initial arm64 ABI - Drivers: hv: Make portions of Hyper-V init code be arch neutral - Drivers: hv: Add arch independent default functions for some Hyper-V handlers - Drivers: hv: Move Hyper-V misc functionality to arch-neutral code - drivers: hv: Decouple Hyper-V clock/timer code from VMbus drivers - PCI: Introduce domain_nr in pci_host_bridge - PCI: Support populating MSI domains of root buses via bridges - arm64: PCI: Restructure pcibios_root_bridge_prepare() - arm64: PCI: Support root bridge preparation for Hyper-V - PCI: hv: Generify PCI probing - PCI: hv: Set ->domain_nr of pci_host_bridge at probing time - PCI: hv: Turn on the host bridge probing on ARM64 - PCI: hv: Set up MSI domain at bridge probing time - [Config] azure: COMMON_CLK_XLNX_CLKWZRD=m - PCI: hv: Support for create interrupt v3 - SAUCE: PCI: hv: Make the code arch neutral by adding arch specific interfaces - SAUCE: arm64: PCI: hv: Add support for Hyper-V vPCI - [Packaging] Update CONFIG_PCI_HYPERV policy for arm64 - PCI: hv: Drop msi_controller structure - clocksource/drivers/hyper-v: Re-enable VDSO_CLOCKMODE_HVCLOCK on X86 * linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver (LP: #1952234) - cpufreq: intel_pstate: Add Icelake servers support in no-HWP mode * hirsute/linux-azure: Backport more CIFS patches (LP: #1950336) - cifs: To match file servers, make sure the server hostname matches - cifs: add mount parameter tcpnodelay [ Ubuntu: 5.11.0-42.46 ] * hirsute/linux: 5.11.0-42.46 -proposed tracker (LP: #1952278) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - debian/dkms-versions -- update from kernel-versions (main/2021.11.29) * CVE-2021-4002 - hugetlbfs: flush TLBs correctly after huge_pmd_unshare * CVE-2021-43267 - tipc: fix size validations for the MSG_CRYPTO type * Hirsute update: upstream stable patchset 2021-11-24 (LP: #1952136) - ext4: check and update i_disksize properly - ext4: correct the error path of ext4_write_inline_data_end() - ASoC: Intel: sof_sdw: tag SoundWire BEs as non-atomic - HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS - netfilter: ip6_tables: zero-initialize fragment offset - HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs - ASoC: SOF: loader: release_firmware() on load failure to avoid batching - netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic - netfilter: nf_nat_masquerade: defer conntrack walk to work queue - mac80211: Drop frames from invalid MAC address in ad-hoc mode - m68k: Handle arrivals of multiple signals correctly - hwmon: (ltc2947) Properly handle errors when looking for the external clock - net:
[Kernel-packages] [Bug 1950644] Re: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels
This bug was fixed in the package linux-azure - 5.13.0-1009.10 --- linux-azure (5.13.0-1009.10) impish; urgency=medium * impish/linux-azure: 5.13.0-1009.10 -proposed tracker (LP: #1952257) * linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver (LP: #1952234) - cpufreq: intel_pstate: Add Icelake servers support in no-HWP mode [ Ubuntu: 5.13.0-23.23 ] * impish/linux: 5.13.0-23.23 -proposed tracker (LP: #1952263) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - debian/dkms-versions -- update from kernel-versions (main/2021.11.29) * CVE-2021-4002 - hugetlbfs: flush TLBs correctly after huge_pmd_unshare * [SRU][I/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks (LP: #1951767) - net: usb: r8152: Add MAC passthrough support for more Lenovo Docks * Fix non-working e1000e device after resume (LP: #1951861) - SAUCE: Revert "e1000e: Additional PHY power saving in S0ix" - SAUCE: Revert "e1000e: Add polling mechanism to indicate CSME DPG exit" - SAUCE: Revert "e1000e: Add handshake with the CSME to support S0ix" * CVE-2021-43267 - tipc: fix size validations for the MSG_CRYPTO type * Impish update: upstream stable patchset 2021-11-22 (LP: #1951880) - ext4: check and update i_disksize properly - ext4: correct the error path of ext4_write_inline_data_end() - ASoC: Intel: sof_sdw: tag SoundWire BEs as non-atomic - HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS - netfilter: ip6_tables: zero-initialize fragment offset - HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs - ASoC: SOF: loader: release_firmware() on load failure to avoid batching - netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic - netfilter: nf_nat_masquerade: defer conntrack walk to work queue - mac80211: Drop frames from invalid MAC address in ad-hoc mode - m68k: Handle arrivals of multiple signals correctly - hwmon: (ltc2947) Properly handle errors when looking for the external clock - net: prevent user from passing illegal stab size - mac80211: check return value of rhashtable_init - vboxfs: fix broken legacy mount signature checking - net: sun: SUNVNET_COMMON should depend on INET - drm/amdgpu: fix gart.bo pin_count leak - scsi: ses: Fix unsigned comparison with less than zero - scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported" - perf/core: fix userpage->time_enabled of inactive events - sched: Always inline is_percpu_thread() - hwmon: (pmbus/ibm-cffps) max_power_out swap changes - ALSA: usb-audio: Unify mixer resume and reset_resume procedure - KVM: arm64: nvhe: Fix missing FORCE for hyp-reloc.S build rule - pinctrl: qcom: sc7280: Add PM suspend callbacks - net: bgmac-platform: handle mac-address deferral - scsi: qla2xxx: Fix excessive messages during device logout - io_uring: kill fasync - upstream stable to v5.10.74, v5.14.13 - ALSA: usb-audio: Add quirk for VF0770 - ALSA: pcm: Workaround for a wrong offset in SYNC_PTR compat ioctl - ALSA: seq: Fix a potential UAF by wrong private_free call order - ALSA: hda/realtek: Enable 4-speaker output for Dell Precision 5560 laptop - ALSA: hda - Enable headphone mic on Dell Latitude laptops with ALC3254 - ALSA: hda/realtek: Complete partial device name to avoid ambiguity - ALSA: hda/realtek: Add quirk for Clevo X170KM-G - ALSA: hda/realtek - ALC236 headset MIC recording issue - ALSA: hda/realtek: Add quirk for TongFang PHxTxX1 - ALSA: hda/realtek: Fix the mic type detection issue for ASUS G551JW - nds32/ftrace: Fix Error: invalid operands (*UND* and *UND* sections) for `^' - s390: fix strrchr() implementation - clk: socfpga: agilex: fix duplicate s2f_user0_clk - csky: don't let sigreturn play with priveleged bits of status register - csky: Fixup regs.sr broken in ptrace - arm64/hugetlb: fix CMA gigantic page order for non-4K PAGE_SIZE - drm/msm: Avoid potential overflow in timeout_to_jiffies() - btrfs: unlock newly allocated extent buffer after error - btrfs: deal with errors when replaying dir entry during log replay - btrfs: deal with errors when adding inode reference during log replay - btrfs: check for error when looking up inode during dir entry replay - btrfs: update refs for any root except tree log roots - btrfs: fix abort logic in btrfs_replace_file_extents - x86/resctrl: Free the ctrlval arrays when domain_setup_mon_state() fails - mei: me: add Ice Lake-N device id. - USB: xhci: dbc: fix tty registration race - xhci: guard accesses to ep_state in xhci_endpoint_reset() - xhci: Fix command ring pointer corruption while aborting a command - xhci: Enable trust tx length quirk for Fresco FL11 USB controller - cb710: avoid
[Kernel-packages] [Bug 1956383] Re: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot
Please note that the kernel currently running (5.13.0-22) is NOT the one with the reported problem. Linux kernel 5.13.0-23.23 is the one that has no video after reboot, when the graphic login (greeter?) should have appeared. Ctrl-Alt-F1 to F7 are not working, but I see a flicker (for a fraction of a second the monitor is going completely black, like unpowered, then returns to blank with backlighting visible). By the way, are Ctrl-Alt-F1 to F7 supposed to still work? Don't know if anything changed in this respect the last few years (Wayland instead of X11). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
Here is some additional information that may be helpful. 1. Prior to upgrade with kernel 5.14.0-1011-oem, KDE Control Center > Bluetooth configuration shows full control over Bluetooth 2. After update to 5.14.0-1013-oem KDE Control Center > Bluetooth configuration shows message similar to 'No Bluetooth Device Found' 3. Reverting to kernel 5.14-0-1011-oem restores the expected capability 4. The following show differences between kernels: 4.1 `systemctl status bluetooth` shows more endpoints with 5.14.0-1011-oem 4.2 `lsusb` shows an Intel device with 5.14.0-1011-oem 4.3 `dmesg | egrep -i 'blue|firm'` shows more output with 5.14.0-1011-oem 5. We have reproduced on three systems, all with Intel AX201 Wifi Cards 5.1 First system: #> 00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi #> Subsystem: Intel Corporation Wi-Fi 6 AX201 160MHz ... 5.2 Second System: #> 00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20) #> Subsystem: Intel Corporation Device 0074 #> Updated Packages: apt-rollback --last 2 #> 1: 2022-01-04 13:09:02 - Upgrade of libsystemd0:amd64 libsystemd0:i386 udev:amd64 libudev1:amd64 libudev1:i386 systemd-timesyncd:amd64 libudev-dev:amd64 systemd-sysv:amd64 libpam-systemd:amd64 systemd:amd64 libnss-systemd:amd64 #> 2: 2022-01-04 08:51:30 - Upgrade of linux-image-oem-20.04d:amd64 linux-libc-dev:amd64 libnvidia-compute-470:amd64 libnvidia-compute-470:i386 libnvidia-encode-470:amd64 libnvidia-encode-470:i386 nvidia-kernel-common-470:amd64 xserver-xorg-video-nvidia-470:amd64 libnvidia-gl-470:amd64 libnvidia-gl-470:i386 azure-cli:amd64 libnvidia-fbc1-470:amd64 libnvidia-fbc1-470:i386 libnvidia-decode-470:amd64 libnvidia-decode-470:i386 linux-headers-oem-20.04d:amd64 libnvidia-cfg1-470:amd64 nvidia-utils-470:amd64 nvidia-dkms-470:amd64 linux-tools-oem-20.04d:amd64 nvidia-compute-utils-470:amd64 libnvidia-ifr1-470:amd64 libnvidia-ifr1-470:i386 nvidia-driver-470:amd64 libnvidia-common-470:amd64 linux-firmware:amd64 linux-tools-common:amd64 linux-oem-20.04d:amd64 libnvidia-extra-470:amd64 nvidia-kernel-source-470:amd64 systemctl status bluetooth # with 5.14.0-1013-oem kernel #> ● bluetooth.service - Bluetooth service #> Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) #> Active: active (running) since Tue 2022-01-04 13:26:24 PST; 10min ago #>Docs: man:bluetoothd(8) #>Main PID: 17644 (bluetoothd) #> Status: "Running" #> Tasks: 1 (limit: 38132) #> Memory: 504.0K #> CGroup: /system.slice/bluetooth.service #> └─17644 /usr/lib/bluetooth/bluetoothd #> #> Jan 04 13:26:24 kfocus systemd[1]: Starting Bluetooth service... #> Jan 04 13:26:24 kfocus bluetoothd[17644]: Bluetooth daemon 5.53 #> Jan 04 13:26:24 kfocus systemd[1]: Started Bluetooth service. #> Jan 04 13:26:24 kfocus bluetoothd[17644]: Starting SDP server #> Jan 04 13:26:24 kfocus bluetoothd[17644]: Bluetooth management interface 1.21 initialized systemctl status bluetooth # with 5.14.0-1011-oem kernel #> ● bluetooth.service - Bluetooth service #> Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) #> Active: active (running) since Tue 2022-01-04 13:47:16 PST; 20min ago #>Docs: man:bluetoothd(8) #>Main PID: 2482 (bluetoothd) #> Status: "Running" #> Tasks: 1 (limit: 38132) #> Memory: 2.8M #> CGroup: /system.slice/bluetooth.service #> └─2482 /usr/lib/bluetooth/bluetoothd #> #> Jan 04 13:47:16 kfocus bluetoothd[2482]: Bluetooth daemon 5.53 #> Jan 04 13:47:16 kfocus systemd[1]: Started Bluetooth service. #> Jan 04 13:47:16 kfocus bluetoothd[2482]: Starting SDP server #> Jan 04 13:47:16 kfocus bluetoothd[2482]: Bluetooth management interface 1.21 initialized #> Jan 04 13:47:17 kfocus bluetoothd[2482]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/sbc #> Jan 04 13:47:17 kfocus bluetoothd[2482]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/sbc #> Jan 04 13:47:21 kfocus bluetoothd[2482]: Endpoint unregistered: sender=:1.45 path=/MediaEndpoint/A2DPSink/sbc #> Jan 04 13:47:21 kfocus bluetoothd[2482]: Endpoint unregistered: sender=:1.45 path=/MediaEndpoint/A2DPSource/sbc #> Jan 04 13:47:22 kfocus bluetoothd[2482]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink/sbc #> Jan 04 13:47:22 kfocus bluetoothd[2482]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/sbc lsusb # 5.14.0-1011-oem kernel #> Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub #> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub #> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub #> Bus 001 Device 003: ID 5986:9102 Acer, Inc BisonCam,NB Pro #> Bus 001 Device 005: ID 8087:0026 Intel Corp. #> Bus 001 Device 004: ID 06cb:00c7 Synaptics, Inc. #> Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver #> Bus 001 Device 001: ID
[Kernel-packages] [Bug 1956396] 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 1956396 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: hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956396 Title: kernel 5.13.0-23 extremely slow boot on AMD proc/graphics Status in linux package in Ubuntu: Incomplete Bug description: 5.13.0-23 HWE kernel on Linux Mint 20.2 Xfce (Ubuntu 20.04.3) Had been using the 5.13 HWE kernel for months with no problems. Today the kernel and linux-firmware updated. 5.13.0-23 kernel now takes about 2 minutes to boot to the login screen. Normal boot time is 8 seconds. During that time the pc is frozen with only a _ underline cursor that doesn't flash. Can't change terminals with Ctrl+Alt+F1, etc. Problem does not occur when booting 5.11.0-44 or 5.4.0-92 so I'm pretty sure the problem is in the kernel and not linux-firmware. System information (while using 5.11 kernel) CPU: Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP arch: Zen+ rev: 1 L2 cache: 2048 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 59089 Speed: 1259 MHz min/max: 1400/3700 MHz boost: enabled Core speeds (MHz): 1: 1258 2: 1258 3: 1258 4: 1258 5: 1257 6: 1260 7: 1267 8: 1330 Graphics: Device-1: AMD Picasso vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 0c:00.0 chip ID: 1002:15d8 Display: x11 server: X.Org 1.20.13 driver: amdgpu resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.40.0 5.11.0-44-generic LLVM 12.0.0) v: 4.6 Mesa 21.0.3 direct render: Yes Forums threads about it: https://ubuntuforums.org/showthread.php?t=2470574 https://forums.linuxmint.com/viewtopic.php?f=46=364729 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950644] Re: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels
This bug was fixed in the package linux-azure - 5.4.0-1065.68 --- linux-azure (5.4.0-1065.68) focal; urgency=medium * focal/linux-azure: 5.4.0-1065.68 -proposed tracker (LP: #1952290) * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632) - [Config] azure: enable CONFIG_DEBUG_INFO_BTF * Support builtin revoked certificates (LP: #1932029) - [Config] azure: set CONFIG_SYSTEM_REVOCATION_KEYS * Bionic/linux-azure: Call trace on Ubuntu 18.04 VM with Standard NV24 (LP: #1952621) - PCI/sysfs: Convert "config" to static attribute * linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver (LP: #1952234) - cpufreq: intel_pstate: Add Icelake servers support in no-HWP mode [ Ubuntu: 5.4.0-92.103 ] * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - debian/dkms-versions -- update from kernel-versions (main/2021.11.29) * CVE-2021-4002 - tlb: mmu_gather: add tlb_flush_*_range APIs - hugetlbfs: flush TLBs correctly after huge_pmd_unshare * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632) - [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462) - KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again - jump_label: Fix usage in module __init * Support builtin revoked certificates (LP: #1932029) - Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about cert lists that aren't present." - integrity: Move import of MokListRT certs to a separate routine - integrity: Load certs from the EFI MOK config table - certs: Add ability to preload revocation certs - integrity: Load mokx variables into the blacklist keyring - certs: add 'x509_revocation_list' to gitignore - SAUCE: Dump stack when X.509 certificates cannot be loaded - [Packaging] build canonical-revoked-certs.pem from branch/arch certs - [Packaging] Revoke 2012 UEFI signing certificate as built-in - [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys * Support importing mokx keys into revocation list from the mok table (LP: #1928679) - efi: Support for MOK variable config table - efi: mokvar-table: fix some issues in new code - efi: mokvar: add missing include of asm/early_ioremap.h - efi/mokvar: Reserve the table only if it is in boot services data - SAUCE: integrity: add informational messages when revoking certs * Support importing mokx keys into revocation list from the mok table (LP: #1928679) // CVE-2020-26541 when certificates are revoked via MokListXRT. - SAUCE: integrity: Load mokx certs from the EFI MOK config table * Focal update: v5.4.157 upstream stable release (LP: #1951883) - ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned - ARM: 9134/1: remove duplicate memcpy() definition - ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype - ARM: 9141/1: only warn about XIP address when not compile testing - ipv6: use siphash in rt6_exception_hash() - ipv4: use siphash instead of Jenkins in fnhe_hashfun() - usbnet: sanity check for maxpacket - usbnet: fix error return code in usbnet_probe() - Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" - ata: sata_mv: Fix the error handling of mv_chip_id() - nfc: port100: fix using -ERRNO as command type mask - net/tls: Fix flipped sign in tls_err_abort() calls - mmc: vub300: fix control-message timeouts - mmc: cqhci: clear HALT state after CQE enable - mmc: dw_mmc: exynos: fix the finding clock sample value - mmc: sdhci: Map more voltage level to SDHCI_POWER_330 - mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit - cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() - net: lan78xx: fix division by zero in send path - tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function - IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields - IB/hfi1: Fix abba locking issue with sc_disable() - nvmet-tcp: fix data digest pointer calculation - nvme-tcp: fix data digest pointer calculation - RDMA/mlx5: Set user priority for DCT - arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node - regmap: Fix possible double-free in regcache_rbtree_exit() - net: batman-adv: fix error handling - net: Prevent infinite while loop in skb_tx_hash() - RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string - nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST - net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume fails - net: ethernet: microchip: lan743x: Fix dma allocation failure by using dma_set_mask_and_coherent - net: nxp: lpc_eth.c: avoid
[Kernel-packages] [Bug 1952234] Re: linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver
This bug was fixed in the package linux-azure - 5.4.0-1065.68 --- linux-azure (5.4.0-1065.68) focal; urgency=medium * focal/linux-azure: 5.4.0-1065.68 -proposed tracker (LP: #1952290) * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632) - [Config] azure: enable CONFIG_DEBUG_INFO_BTF * Support builtin revoked certificates (LP: #1932029) - [Config] azure: set CONFIG_SYSTEM_REVOCATION_KEYS * Bionic/linux-azure: Call trace on Ubuntu 18.04 VM with Standard NV24 (LP: #1952621) - PCI/sysfs: Convert "config" to static attribute * linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver (LP: #1952234) - cpufreq: intel_pstate: Add Icelake servers support in no-HWP mode [ Ubuntu: 5.4.0-92.103 ] * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - debian/dkms-versions -- update from kernel-versions (main/2021.11.29) * CVE-2021-4002 - tlb: mmu_gather: add tlb_flush_*_range APIs - hugetlbfs: flush TLBs correctly after huge_pmd_unshare * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632) - [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462) - KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again - jump_label: Fix usage in module __init * Support builtin revoked certificates (LP: #1932029) - Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about cert lists that aren't present." - integrity: Move import of MokListRT certs to a separate routine - integrity: Load certs from the EFI MOK config table - certs: Add ability to preload revocation certs - integrity: Load mokx variables into the blacklist keyring - certs: add 'x509_revocation_list' to gitignore - SAUCE: Dump stack when X.509 certificates cannot be loaded - [Packaging] build canonical-revoked-certs.pem from branch/arch certs - [Packaging] Revoke 2012 UEFI signing certificate as built-in - [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys * Support importing mokx keys into revocation list from the mok table (LP: #1928679) - efi: Support for MOK variable config table - efi: mokvar-table: fix some issues in new code - efi: mokvar: add missing include of asm/early_ioremap.h - efi/mokvar: Reserve the table only if it is in boot services data - SAUCE: integrity: add informational messages when revoking certs * Support importing mokx keys into revocation list from the mok table (LP: #1928679) // CVE-2020-26541 when certificates are revoked via MokListXRT. - SAUCE: integrity: Load mokx certs from the EFI MOK config table * Focal update: v5.4.157 upstream stable release (LP: #1951883) - ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned - ARM: 9134/1: remove duplicate memcpy() definition - ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype - ARM: 9141/1: only warn about XIP address when not compile testing - ipv6: use siphash in rt6_exception_hash() - ipv4: use siphash instead of Jenkins in fnhe_hashfun() - usbnet: sanity check for maxpacket - usbnet: fix error return code in usbnet_probe() - Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" - ata: sata_mv: Fix the error handling of mv_chip_id() - nfc: port100: fix using -ERRNO as command type mask - net/tls: Fix flipped sign in tls_err_abort() calls - mmc: vub300: fix control-message timeouts - mmc: cqhci: clear HALT state after CQE enable - mmc: dw_mmc: exynos: fix the finding clock sample value - mmc: sdhci: Map more voltage level to SDHCI_POWER_330 - mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit - cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() - net: lan78xx: fix division by zero in send path - tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function - IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields - IB/hfi1: Fix abba locking issue with sc_disable() - nvmet-tcp: fix data digest pointer calculation - nvme-tcp: fix data digest pointer calculation - RDMA/mlx5: Set user priority for DCT - arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node - regmap: Fix possible double-free in regcache_rbtree_exit() - net: batman-adv: fix error handling - net: Prevent infinite while loop in skb_tx_hash() - RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string - nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST - net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume fails - net: ethernet: microchip: lan743x: Fix dma allocation failure by using dma_set_mask_and_coherent - net: nxp: lpc_eth.c: avoid
[Kernel-packages] [Bug 1952234] Re: linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver
This bug was fixed in the package linux-azure - 5.13.0-1009.10 --- linux-azure (5.13.0-1009.10) impish; urgency=medium * impish/linux-azure: 5.13.0-1009.10 -proposed tracker (LP: #1952257) * linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver (LP: #1952234) - cpufreq: intel_pstate: Add Icelake servers support in no-HWP mode [ Ubuntu: 5.13.0-23.23 ] * impish/linux: 5.13.0-23.23 -proposed tracker (LP: #1952263) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - debian/dkms-versions -- update from kernel-versions (main/2021.11.29) * CVE-2021-4002 - hugetlbfs: flush TLBs correctly after huge_pmd_unshare * [SRU][I/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks (LP: #1951767) - net: usb: r8152: Add MAC passthrough support for more Lenovo Docks * Fix non-working e1000e device after resume (LP: #1951861) - SAUCE: Revert "e1000e: Additional PHY power saving in S0ix" - SAUCE: Revert "e1000e: Add polling mechanism to indicate CSME DPG exit" - SAUCE: Revert "e1000e: Add handshake with the CSME to support S0ix" * CVE-2021-43267 - tipc: fix size validations for the MSG_CRYPTO type * Impish update: upstream stable patchset 2021-11-22 (LP: #1951880) - ext4: check and update i_disksize properly - ext4: correct the error path of ext4_write_inline_data_end() - ASoC: Intel: sof_sdw: tag SoundWire BEs as non-atomic - HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS - netfilter: ip6_tables: zero-initialize fragment offset - HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs - ASoC: SOF: loader: release_firmware() on load failure to avoid batching - netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic - netfilter: nf_nat_masquerade: defer conntrack walk to work queue - mac80211: Drop frames from invalid MAC address in ad-hoc mode - m68k: Handle arrivals of multiple signals correctly - hwmon: (ltc2947) Properly handle errors when looking for the external clock - net: prevent user from passing illegal stab size - mac80211: check return value of rhashtable_init - vboxfs: fix broken legacy mount signature checking - net: sun: SUNVNET_COMMON should depend on INET - drm/amdgpu: fix gart.bo pin_count leak - scsi: ses: Fix unsigned comparison with less than zero - scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported" - perf/core: fix userpage->time_enabled of inactive events - sched: Always inline is_percpu_thread() - hwmon: (pmbus/ibm-cffps) max_power_out swap changes - ALSA: usb-audio: Unify mixer resume and reset_resume procedure - KVM: arm64: nvhe: Fix missing FORCE for hyp-reloc.S build rule - pinctrl: qcom: sc7280: Add PM suspend callbacks - net: bgmac-platform: handle mac-address deferral - scsi: qla2xxx: Fix excessive messages during device logout - io_uring: kill fasync - upstream stable to v5.10.74, v5.14.13 - ALSA: usb-audio: Add quirk for VF0770 - ALSA: pcm: Workaround for a wrong offset in SYNC_PTR compat ioctl - ALSA: seq: Fix a potential UAF by wrong private_free call order - ALSA: hda/realtek: Enable 4-speaker output for Dell Precision 5560 laptop - ALSA: hda - Enable headphone mic on Dell Latitude laptops with ALC3254 - ALSA: hda/realtek: Complete partial device name to avoid ambiguity - ALSA: hda/realtek: Add quirk for Clevo X170KM-G - ALSA: hda/realtek - ALC236 headset MIC recording issue - ALSA: hda/realtek: Add quirk for TongFang PHxTxX1 - ALSA: hda/realtek: Fix the mic type detection issue for ASUS G551JW - nds32/ftrace: Fix Error: invalid operands (*UND* and *UND* sections) for `^' - s390: fix strrchr() implementation - clk: socfpga: agilex: fix duplicate s2f_user0_clk - csky: don't let sigreturn play with priveleged bits of status register - csky: Fixup regs.sr broken in ptrace - arm64/hugetlb: fix CMA gigantic page order for non-4K PAGE_SIZE - drm/msm: Avoid potential overflow in timeout_to_jiffies() - btrfs: unlock newly allocated extent buffer after error - btrfs: deal with errors when replaying dir entry during log replay - btrfs: deal with errors when adding inode reference during log replay - btrfs: check for error when looking up inode during dir entry replay - btrfs: update refs for any root except tree log roots - btrfs: fix abort logic in btrfs_replace_file_extents - x86/resctrl: Free the ctrlval arrays when domain_setup_mon_state() fails - mei: me: add Ice Lake-N device id. - USB: xhci: dbc: fix tty registration race - xhci: guard accesses to ep_state in xhci_endpoint_reset() - xhci: Fix command ring pointer corruption while aborting a command - xhci: Enable trust tx length quirk for Fresco FL11 USB controller - cb710: avoid
[Kernel-packages] [Bug 1952234] Re: linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver
This bug was fixed in the package linux-azure-4.15 - 4.15.0-1129.142 --- linux-azure-4.15 (4.15.0-1129.142) bionic; urgency=medium * bionic/linux-azure-4.15: 4.15.0-1129.142 -proposed tracker (LP: #1953649) [ Ubuntu: 4.15.0-166.174 ] * bionic/linux: 4.15.0-166.174 -proposed tracker (LP: #1953667) * Ubuntu version macros overflow with high ABI numbers (LP: #1953522) - SAUCE: Revert "stable: clamp SUBLEVEL in 4.14" * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and variants (LP: #1953287) - SAUCE: Revert "bpf: add also cbpf long jump test cases with heavy expansion" * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and variants (LP: #1953287) // CVE-2018-25020 - bpf: fix truncated jump targets on heavy expansions linux-azure-4.15 (4.15.0-1128.141) bionic; urgency=medium * bionic/linux-azure-4.15: 4.15.0-1128.141 -proposed tracker (LP: #1952330) * linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver (LP: #1952234) - cpufreq: intel_pstate: Add Icelake servers support in no-HWP mode [ Ubuntu: 4.15.0-165.173 ] * bionic/linux: 4.15.0-165.173 -proposed tracker (LP: #1952780) * Support builtin revoked certificates (LP: #1932029) - certs: Add EFI_CERT_X509_GUID support for dbx entries - certs: Move load_system_certificate_list to a common function - integrity: Move import of MokListRT certs to a separate routine - integrity: Load certs from the EFI MOK config table - certs: Add ability to preload revocation certs - certs: add 'x509_revocation_list' to gitignore - SAUCE: Dump stack when X.509 certificates cannot be loaded - [Packaging] build canonical-revoked-certs.pem from branch/arch certs - [Packaging] Revoke 2012 UEFI signing certificate as built-in - [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys * Support importing mokx keys into revocation list from the mok table (LP: #1928679) - efi: Support for MOK variable config table - efi: mokvar-table: fix some issues in new code - efi: mokvar: add missing include of asm/early_ioremap.h - efi/mokvar: Reserve the table only if it is in boot services data - SAUCE: integrity: Load mokx certs from the EFI MOK config table - SAUCE: integrity: add informational messages when revoking certs * CVE-2021-4002 - arm64: tlb: Provide forward declaration of tlb_flush() before including tlb.h - mm: mmu_notifier fix for tlb_end_vma - hugetlbfs: flush TLBs correctly after huge_pmd_unshare [ Ubuntu: 4.15.0-164.172 ] * bionic/linux: 4.15.0-164.172 -proposed tracker (LP: #1952348) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - debian/dkms-versions -- update from kernel-versions (main/2021.11.29) * Bionic update: upstream stable patchset 2021-11-23 (LP: #1951997) - btrfs: always wait on ordered extents at fsync time - ARM: dts: at91: sama5d2_som1_ek: disable ISC node by default - xtensa: xtfpga: use CONFIG_USE_OF instead of CONFIG_OF - xtensa: xtfpga: Try software restart before simulating CPU reset - NFSD: Keep existing listeners on portlist error - netfilter: ipvs: make global sysctl readonly in non-init netns - NIOS2: irqflags: rename a redefined register name - can: rcar_can: fix suspend/resume - can: peak_usb: pcan_usb_fd_decode_status(): fix back to ERROR_ACTIVE state notification - can: peak_pci: peak_pci_remove(): fix UAF - ocfs2: fix data corruption after conversion from inline format - ocfs2: mount fails with buffer overflow in strlen - elfcore: correct reference to CONFIG_UML - ALSA: usb-audio: Provide quirk for Sennheiser GSP670 Headset - ASoC: DAPM: Fix missing kctl change notifications - nfc: nci: fix the UAF of rf_conn_info object - isdn: cpai: check ctr->cnr to avoid array index out of bound - netfilter: Kconfig: use 'default y' instead of 'm' for bool config option - btrfs: deal with errors when checking if a dir entry exists during log replay - net: stmmac: add support for dwmac 3.40a - ARM: dts: spear3xx: Fix gmac node - isdn: mISDN: Fix sleeping function called from invalid context - platform/x86: intel_scu_ipc: Update timeout value in comment - ALSA: hda: avoid write to STATESTS if controller is in reset - tracing: Have all levels of checks prevent recursion - ARM: 9122/1: select HAVE_FUTEX_CMPXCHG - dma-debug: fix sg checks in debug_dma_map_sg() - ASoC: wm8960: Fix clock configuration on slave mode - lan78xx: select CRC32 - net: hns3: add limit ets dwrr bandwidth cannot be 0 - net: hns3: disable sriov before unload hclge layer - ALSA: hda/realtek: Add quirk for Clevo PC50HS - mm, slub: fix mismatch between reconstructed freelist depth and cnt - gcc-plugins/structleak: add makefile var for disabling structleak *
[Kernel-packages] [Bug 1956396] [NEW] kernel 5.13.0-23 extremely slow boot on AMD proc/graphics
Public bug reported: 5.13.0-23 HWE kernel on Linux Mint 20.2 Xfce (Ubuntu 20.04.3) Had been using the 5.13 HWE kernel for months with no problems. Today the kernel and linux-firmware updated. 5.13.0-23 kernel now takes about 2 minutes to boot to the login screen. Normal boot time is 8 seconds. During that time the pc is frozen with only a _ underline cursor that doesn't flash. Can't change terminals with Ctrl+Alt+F1, etc. Problem does not occur when booting 5.11.0-44 or 5.4.0-92 so I'm pretty sure the problem is in the kernel and not linux-firmware. System information (while using 5.11 kernel) CPU: Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP arch: Zen+ rev: 1 L2 cache: 2048 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 59089 Speed: 1259 MHz min/max: 1400/3700 MHz boost: enabled Core speeds (MHz): 1: 1258 2: 1258 3: 1258 4: 1258 5: 1257 6: 1260 7: 1267 8: 1330 Graphics: Device-1: AMD Picasso vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 0c:00.0 chip ID: 1002:15d8 Display: x11 server: X.Org 1.20.13 driver: amdgpu resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.40.0 5.11.0-44-generic LLVM 12.0.0) v: 4.6 Mesa 21.0.3 direct render: Yes Forums threads about it: https://ubuntuforums.org/showthread.php?t=2470574 https://forums.linuxmint.com/viewtopic.php?f=46=364729 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: hirsute ** Description changed: 5.13.0-23 HWE kernel on Linux Mint 20.2 Xfce (Ubuntu 20.04.3) Had been using the 5.13 HWE kernel for months with no problems. Today the kernel and linux-firmware updated. 5.13.0-23 kernel now takes about 2 minutes to boot to the login screen. Normal boot time is 8 seconds. During that time the pc is frozen with only a _ underline cursor that doesn't flash. Can't change terminals with Ctrl+Alt+F1, etc. Problem does not occur when booting 5.11.0-44 or 5.4.0-92 so I'm pretty sure the problem is in the kernel and not linux-firmware. - CPU: Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP -arch: Zen+ rev: 1 L2 cache: 2048 KiB -flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 59089 -Speed: 1259 MHz min/max: 1400/3700 MHz boost: enabled Core speeds (MHz): 1: 1258 2: 1258 -3: 1258 4: 1258 5: 1257 6: 1260 7: 1267 8: 1330 + System information (while using 5.11 kernel) + CPU: Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP + arch: Zen+ rev: 1 L2 cache: 2048 KiB + flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 59089 + Speed: 1259 MHz min/max: 1400/3700 MHz boost: enabled Core speeds (MHz): 1: 1258 2: 1258 + 3: 1258 4: 1258 5: 1257 6: 1260 7: 1267 8: 1330 - Graphics: Device-1: AMD Picasso vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 0c:00.0 -chip ID: 1002:15d8 -Display: x11 server: X.Org 1.20.13 driver: amdgpu resolution: 1920x1080~60Hz -OpenGL: -renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.40.0 5.11.0-44-generic LLVM 12.0.0) -v: 4.6 Mesa 21.0.3 direct render: Yes + Graphics: Device-1: AMD Picasso vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 0c:00.0 + chip ID: 1002:15d8 + Display: x11 server: X.Org 1.20.13 driver: amdgpu resolution: 1920x1080~60Hz + OpenGL: + renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.40.0 5.11.0-44-generic LLVM 12.0.0) + v: 4.6 Mesa 21.0.3 direct render: Yes ** Description changed: 5.13.0-23 HWE kernel on Linux Mint 20.2 Xfce (Ubuntu 20.04.3) Had been using the 5.13 HWE kernel for months with no problems. Today the kernel and linux-firmware updated. 5.13.0-23 kernel now takes about 2 minutes to boot to the login screen. Normal boot time is 8 seconds. During that time the pc is frozen with only a _ underline cursor that doesn't flash. Can't change terminals with Ctrl+Alt+F1, etc. Problem does not occur when booting 5.11.0-44 or 5.4.0-92 so I'm pretty sure the problem is in the kernel and not linux-firmware. System information (while using 5.11 kernel) CPU: Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP arch: Zen+ rev: 1 L2 cache: 2048 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 59089 Speed: 1259 MHz min/max: 1400/3700 MHz boost: enabled Core speeds (MHz): 1: 1258 2: 1258 3: 1258 4: 1258 5: 1257 6: 1260 7: 1267 8: 1330 Graphics: Device-1: AMD
[Kernel-packages] [Bug 1956399] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956399 Title: Regression: kernel does not init graphics (?) on AMD Ryzen 5 3400G Status in linux package in Ubuntu: Confirmed Bug description: After latest upgrade of linux-image to 5.13.0.23.34 system seem to boot, but it looks like graphics does not initialize correctly. After showing initial init logging, at the moment when X should init and graphics login should appear, monitor just goes to sleep and provides diagnostic message that there is no signal on selected input. apt upgrade log: Start-Date: 2022-01-04 23:21:11 Commandline: apt upgrade Requested-By: xx (1000) Install: linux-modules-extra-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-image-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-modules-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23:amd64 (5.13.0-23.23, automatic) Upgrade: linux-headers-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), google-chrome-stable:amd64 (96.0.4664.110-1, 97.0.4692.71-1), linux-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-image-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-libc-dev:amd64 (5.13.0-22.22, 5.13.0-23.23) End-Date: 2022-01-04 23:22:39 Currently working around this issues by booting previous version of the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-generic 5.13.0.23.34 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 2532 F pulseaudio /dev/snd/pcmC1D0p: alexei 2532 F...m pulseaudio /dev/snd/controlC0: alexei 2532 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 01:02:53 2022 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (2190 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp8s0no wireless extensions. lxcbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-05 (91 days ago) dmi.bios.date: 05/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.00 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd05/10/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956401] [NEW] amdgpu hangs for 90 seconds at a time
Public bug reported: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-33-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry ** Affects: linux-hwe-5.13 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time Status in linux-hwe-5.13 package in Ubuntu: New Bug description: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-33-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time
** Attachment added: "Some kernel log showing amdgpu errors and others resulting from it" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+attachment/5551255/+files/wow.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time Status in linux-hwe-5.13 package in Ubuntu: New Bug description: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-33-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe-5.13 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-33-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950462] Re: Focal linux-azure: Vm crash on Dv5/Ev5
This bug was fixed in the package linux-azure - 5.4.0-1065.68 --- linux-azure (5.4.0-1065.68) focal; urgency=medium * focal/linux-azure: 5.4.0-1065.68 -proposed tracker (LP: #1952290) * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632) - [Config] azure: enable CONFIG_DEBUG_INFO_BTF * Support builtin revoked certificates (LP: #1932029) - [Config] azure: set CONFIG_SYSTEM_REVOCATION_KEYS * Bionic/linux-azure: Call trace on Ubuntu 18.04 VM with Standard NV24 (LP: #1952621) - PCI/sysfs: Convert "config" to static attribute * linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver (LP: #1952234) - cpufreq: intel_pstate: Add Icelake servers support in no-HWP mode [ Ubuntu: 5.4.0-92.103 ] * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - debian/dkms-versions -- update from kernel-versions (main/2021.11.29) * CVE-2021-4002 - tlb: mmu_gather: add tlb_flush_*_range APIs - hugetlbfs: flush TLBs correctly after huge_pmd_unshare * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632) - [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462) - KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again - jump_label: Fix usage in module __init * Support builtin revoked certificates (LP: #1932029) - Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about cert lists that aren't present." - integrity: Move import of MokListRT certs to a separate routine - integrity: Load certs from the EFI MOK config table - certs: Add ability to preload revocation certs - integrity: Load mokx variables into the blacklist keyring - certs: add 'x509_revocation_list' to gitignore - SAUCE: Dump stack when X.509 certificates cannot be loaded - [Packaging] build canonical-revoked-certs.pem from branch/arch certs - [Packaging] Revoke 2012 UEFI signing certificate as built-in - [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys * Support importing mokx keys into revocation list from the mok table (LP: #1928679) - efi: Support for MOK variable config table - efi: mokvar-table: fix some issues in new code - efi: mokvar: add missing include of asm/early_ioremap.h - efi/mokvar: Reserve the table only if it is in boot services data - SAUCE: integrity: add informational messages when revoking certs * Support importing mokx keys into revocation list from the mok table (LP: #1928679) // CVE-2020-26541 when certificates are revoked via MokListXRT. - SAUCE: integrity: Load mokx certs from the EFI MOK config table * Focal update: v5.4.157 upstream stable release (LP: #1951883) - ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned - ARM: 9134/1: remove duplicate memcpy() definition - ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype - ARM: 9141/1: only warn about XIP address when not compile testing - ipv6: use siphash in rt6_exception_hash() - ipv4: use siphash instead of Jenkins in fnhe_hashfun() - usbnet: sanity check for maxpacket - usbnet: fix error return code in usbnet_probe() - Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" - ata: sata_mv: Fix the error handling of mv_chip_id() - nfc: port100: fix using -ERRNO as command type mask - net/tls: Fix flipped sign in tls_err_abort() calls - mmc: vub300: fix control-message timeouts - mmc: cqhci: clear HALT state after CQE enable - mmc: dw_mmc: exynos: fix the finding clock sample value - mmc: sdhci: Map more voltage level to SDHCI_POWER_330 - mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit - cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() - net: lan78xx: fix division by zero in send path - tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function - IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields - IB/hfi1: Fix abba locking issue with sc_disable() - nvmet-tcp: fix data digest pointer calculation - nvme-tcp: fix data digest pointer calculation - RDMA/mlx5: Set user priority for DCT - arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node - regmap: Fix possible double-free in regcache_rbtree_exit() - net: batman-adv: fix error handling - net: Prevent infinite while loop in skb_tx_hash() - RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string - nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST - net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume fails - net: ethernet: microchip: lan743x: Fix dma allocation failure by using dma_set_mask_and_coherent - net: nxp: lpc_eth.c: avoid
[Kernel-packages] [Bug 1956393] [NEW] Bluetooth no longer recognized after update to 5.14.0-1013
Public bug reported: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem-5.14 (Ubuntu) Importance: Critical Status: Confirmed ** Tags: amd64 apport-bug focal oem-priority ** Changed in: linux-signed-oem-5.14 (Ubuntu) Status: New => Confirmed ** Changed in: linux-signed-oem-5.14 (Ubuntu) Importance: Undecided => Critical ** Description changed: - On Kubuntu Focus computers with the recent update to the OEM 5.13.0-1013 + On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-signed-oem-5.14 package in Ubuntu: Confirmed Bug description: On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu Focus 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1956393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956396] Re: kernel 5.13.0-23 extremely slow boot on AMD proc/graphics
Unable to run apport-collect 1956396. ** 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/1956396 Title: kernel 5.13.0-23 extremely slow boot on AMD proc/graphics Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-23 HWE kernel on Linux Mint 20.2 Xfce (Ubuntu 20.04.3) Had been using the 5.13 HWE kernel for months with no problems. Today the kernel and linux-firmware updated. 5.13.0-23 kernel now takes about 2 minutes to boot to the login screen. Normal boot time is 8 seconds. During that time the pc is frozen with only a _ underline cursor that doesn't flash. Can't change terminals with Ctrl+Alt+F1, etc. Problem does not occur when booting 5.11.0-44 or 5.4.0-92 so I'm pretty sure the problem is in the kernel and not linux-firmware. System information (while using 5.11 kernel) CPU: Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP arch: Zen+ rev: 1 L2 cache: 2048 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 59089 Speed: 1259 MHz min/max: 1400/3700 MHz boost: enabled Core speeds (MHz): 1: 1258 2: 1258 3: 1258 4: 1258 5: 1257 6: 1260 7: 1267 8: 1330 Graphics: Device-1: AMD Picasso vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 0c:00.0 chip ID: 1002:15d8 Display: x11 server: X.Org 1.20.13 driver: amdgpu resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.40.0 5.11.0-44-generic LLVM 12.0.0) v: 4.6 Mesa 21.0.3 direct render: Yes Forums threads about it: https://ubuntuforums.org/showthread.php?t=2470574 https://forums.linuxmint.com/viewtopic.php?f=46=364729 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955916] Re: Bluetooth dongle rtl8761b
The problem is that the USB ID for this chip is not in the btusb module. Many people report the same problem elsewhere, though it seems most want to try and use a strange module from a random BT dongle manufacturers website, which is just crazy. The proper thing to do is to add the USB ID to drivers/bluetooth/btusb.c. However, I am a bit lazy, so instead I just modified the driver in place, writing over the ID of another realtek chip with this one (0x2550 0x8761), then strip the module to remove the signature: sudo -s cp /lib/modules/`uname -r`/kernel/drivers/bluetooth/btusb.ko btusb.ko.orig xxd /lib/modules/`uname -r`/kernel/drivers/bluetooth/btusb.ko | sed 's/ca04 0540/5025 6187/g' | xxd -r > btusb.ko.mod strip --strip-debug btusb.ko.mod mv btusb.ko.mod /lib/modules/`uname -r`/kernel/drivers/bluetooth/btusb.ko Don't forget to also download firmware: wget -O /lib/firmware/rtl_bt/rtl8761b_config.bin https://raw.githubusercontent.com/Realtek-OpenSource/android_hardware_realtek/rtk1395/bt/rtkbt/Firmware/BT/rtl8761b_config wget -O /lib/firmware/rtl_bt/rtl8761b_fw.bin https://raw.githubusercontent.com/Realtek-OpenSource/android_hardware_realtek/rtk1395/bt/rtkbt/Firmware/BT/rtl8761b_fw You have to disable secure boot to load the modified module, if you didn't have it disabled already, and reboot. If already disabled you can probably just do: modprobe -r btusb && modprobe btusb You also need at least kernel 5.8 I believe. Hopefully the USB ID will be added to the kernel soon, as it's pretty silly having to do this! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1955916 Title: Bluetooth dongle rtl8761b Status in linux package in Ubuntu: Incomplete Bug description: Package: linux-firmware Architecture: all Version: 1.187 The device is recognized, hciconfig -a shows a device, no errors at all. It can scan do whatever. The only thing it doesn't do is find anything. hci0: Type: Primary Bus: USB BD Address: 00:E0:4C:19:xx:xx ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING RX bytes:1706 acl:0 sco:0 events:225 errors:0 TX bytes:6122 acl:0 sco:0 commands:201 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'hostname' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0xb LMP Version: 5.1 (0xa) Subversion: 0x8761 Manufacturer: Realtek Semiconductor Corporation (93) #included on request Ubuntu 5.13.0-23.23~20.04.2-generic 5.13.19 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:191f] (rev 07) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [1458:5000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 07) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31) (prog-if 30 [XHCI]) Subsystem: Gigabyte Technology Co., Ltd 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [1458:5007] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31) Subsystem: Gigabyte Technology Co., Ltd 100 Series/C230 Series Chipset Family MEI Controller [1458:1c3a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: mei_me Kernel modules: mei_me 00:17.0 RAID bus controller [0104]: Intel Corporation SATA
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time
Additional note, I did notice one "un-regression" -- I have a build of rocm where I've tried enabling "GFX902" support for my card, this is an unsupported configuration so I don't know if I have it 100% functional but rocminfo (which as the name suggests dumps info about the rocm install and any video or compute cards it detects that can use. ) With the 5.4.0-91-generic kernel I can run rocminfo and it dumps some info about the card. On 5.13.0-22 it prints: hsa api call failure at: /home/hwertz/ROCm/rocminfo/rocminfo.cc:1143 Call returned HSA_STATUS_ERROR_OUT_OF_RESOURCES: The runtime failed to allocate the necessary resources. This error may also occur when the core runtime library needs to spawn threads or create internal OS-specific events. On 5.13.0-23, although opengl is hosed the rocminfo didn't pause and printed the rocm-related information. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time Status in linux-hwe-5.13 package in Ubuntu: New Bug description: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-33-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950336] Re: hirsute/linux-azure: Backport more CIFS patches
This bug was fixed in the package linux-azure - 5.11.0-1023.24 --- linux-azure (5.11.0-1023.24) hirsute; urgency=medium * hirsute/linux-azure: 5.11.0-1023.24 -proposed tracker (LP: #1952268) * Enable arm64 for Hyper-V guests (LP: #1949770) - Drivers: hv: vmbus: Move Hyper-V page allocator to arch neutral code - x86/hyper-v: Move hv_message_type to architecture neutral module - Drivers: hv: Redo Hyper-V synthetic MSR get/set functions - Drivers: hv: vmbus: Move hyperv_report_panic_msg to arch neutral code - Drivers: hv: vmbus: Handle auto EOI quirk inline - Drivers: hv: vmbus: Move handling of VMbus interrupts - clocksource/drivers/hyper-v: Handle vDSO differences inline - clocksource/drivers/hyper-v: Handle sched_clock differences inline - asm-generic/hyperv: change HV_CPU_POWER_MANAGEMENT to HV_CPU_MANAGEMENT - x86/hyperv: detect if Linux is the root partition - clocksource/hyperv: use MSR-based access if running as root - clocksource/drivers/hyper-v: Set clocksource rating based on Hyper-V feature - clocksource/drivers/hyper-v: Move handling of STIMER0 interrupts - drivers: hv: Fix whitespace errors - x86/Hyper-V: Support for free page reporting - x86/hyperv: Move hv_do_rep_hypercall to asm-generic - drivers: hv: Create a consistent pattern for checking Hyper-V hypercall status - arm64: smccc: Add support for SMCCCv1.2 extended input/output registers - Drivers: hv: Move Hyper-V extended capability check to arch neutral code - asm-generic/hyperv: Add missing #include of nmi.h - arm64: hyperv: Add Hyper-V hypercall and register access utilities - arm64: hyperv: Add panic handler - arm64: hyperv: Initialize hypervisor on boot - arm64: efi: Export screen_info - Drivers: hv: Enable Hyper-V code to be built on ARM64 - [Packaging] linux-azure: Add basic packaging support for arm64 - [Config] linux-azure: Extending existing annotations to arm64 - [Config] linux-azure: Generate initial config for arm64 - [Packaging] linux-azure: Ignore initial arm64 ABI - Drivers: hv: Make portions of Hyper-V init code be arch neutral - Drivers: hv: Add arch independent default functions for some Hyper-V handlers - Drivers: hv: Move Hyper-V misc functionality to arch-neutral code - drivers: hv: Decouple Hyper-V clock/timer code from VMbus drivers - PCI: Introduce domain_nr in pci_host_bridge - PCI: Support populating MSI domains of root buses via bridges - arm64: PCI: Restructure pcibios_root_bridge_prepare() - arm64: PCI: Support root bridge preparation for Hyper-V - PCI: hv: Generify PCI probing - PCI: hv: Set ->domain_nr of pci_host_bridge at probing time - PCI: hv: Turn on the host bridge probing on ARM64 - PCI: hv: Set up MSI domain at bridge probing time - [Config] azure: COMMON_CLK_XLNX_CLKWZRD=m - PCI: hv: Support for create interrupt v3 - SAUCE: PCI: hv: Make the code arch neutral by adding arch specific interfaces - SAUCE: arm64: PCI: hv: Add support for Hyper-V vPCI - [Packaging] Update CONFIG_PCI_HYPERV policy for arm64 - PCI: hv: Drop msi_controller structure - clocksource/drivers/hyper-v: Re-enable VDSO_CLOCKMODE_HVCLOCK on X86 * linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver (LP: #1952234) - cpufreq: intel_pstate: Add Icelake servers support in no-HWP mode * hirsute/linux-azure: Backport more CIFS patches (LP: #1950336) - cifs: To match file servers, make sure the server hostname matches - cifs: add mount parameter tcpnodelay [ Ubuntu: 5.11.0-42.46 ] * hirsute/linux: 5.11.0-42.46 -proposed tracker (LP: #1952278) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - debian/dkms-versions -- update from kernel-versions (main/2021.11.29) * CVE-2021-4002 - hugetlbfs: flush TLBs correctly after huge_pmd_unshare * CVE-2021-43267 - tipc: fix size validations for the MSG_CRYPTO type * Hirsute update: upstream stable patchset 2021-11-24 (LP: #1952136) - ext4: check and update i_disksize properly - ext4: correct the error path of ext4_write_inline_data_end() - ASoC: Intel: sof_sdw: tag SoundWire BEs as non-atomic - HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS - netfilter: ip6_tables: zero-initialize fragment offset - HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs - ASoC: SOF: loader: release_firmware() on load failure to avoid batching - netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic - netfilter: nf_nat_masquerade: defer conntrack walk to work queue - mac80211: Drop frames from invalid MAC address in ad-hoc mode - m68k: Handle arrivals of multiple signals correctly - hwmon: (ltc2947) Properly handle errors when looking for the external clock - net:
[Kernel-packages] [Bug 1949770] Re: Enable arm64 for Hyper-V guests
This bug was fixed in the package linux-azure - 5.11.0-1023.24 --- linux-azure (5.11.0-1023.24) hirsute; urgency=medium * hirsute/linux-azure: 5.11.0-1023.24 -proposed tracker (LP: #1952268) * Enable arm64 for Hyper-V guests (LP: #1949770) - Drivers: hv: vmbus: Move Hyper-V page allocator to arch neutral code - x86/hyper-v: Move hv_message_type to architecture neutral module - Drivers: hv: Redo Hyper-V synthetic MSR get/set functions - Drivers: hv: vmbus: Move hyperv_report_panic_msg to arch neutral code - Drivers: hv: vmbus: Handle auto EOI quirk inline - Drivers: hv: vmbus: Move handling of VMbus interrupts - clocksource/drivers/hyper-v: Handle vDSO differences inline - clocksource/drivers/hyper-v: Handle sched_clock differences inline - asm-generic/hyperv: change HV_CPU_POWER_MANAGEMENT to HV_CPU_MANAGEMENT - x86/hyperv: detect if Linux is the root partition - clocksource/hyperv: use MSR-based access if running as root - clocksource/drivers/hyper-v: Set clocksource rating based on Hyper-V feature - clocksource/drivers/hyper-v: Move handling of STIMER0 interrupts - drivers: hv: Fix whitespace errors - x86/Hyper-V: Support for free page reporting - x86/hyperv: Move hv_do_rep_hypercall to asm-generic - drivers: hv: Create a consistent pattern for checking Hyper-V hypercall status - arm64: smccc: Add support for SMCCCv1.2 extended input/output registers - Drivers: hv: Move Hyper-V extended capability check to arch neutral code - asm-generic/hyperv: Add missing #include of nmi.h - arm64: hyperv: Add Hyper-V hypercall and register access utilities - arm64: hyperv: Add panic handler - arm64: hyperv: Initialize hypervisor on boot - arm64: efi: Export screen_info - Drivers: hv: Enable Hyper-V code to be built on ARM64 - [Packaging] linux-azure: Add basic packaging support for arm64 - [Config] linux-azure: Extending existing annotations to arm64 - [Config] linux-azure: Generate initial config for arm64 - [Packaging] linux-azure: Ignore initial arm64 ABI - Drivers: hv: Make portions of Hyper-V init code be arch neutral - Drivers: hv: Add arch independent default functions for some Hyper-V handlers - Drivers: hv: Move Hyper-V misc functionality to arch-neutral code - drivers: hv: Decouple Hyper-V clock/timer code from VMbus drivers - PCI: Introduce domain_nr in pci_host_bridge - PCI: Support populating MSI domains of root buses via bridges - arm64: PCI: Restructure pcibios_root_bridge_prepare() - arm64: PCI: Support root bridge preparation for Hyper-V - PCI: hv: Generify PCI probing - PCI: hv: Set ->domain_nr of pci_host_bridge at probing time - PCI: hv: Turn on the host bridge probing on ARM64 - PCI: hv: Set up MSI domain at bridge probing time - [Config] azure: COMMON_CLK_XLNX_CLKWZRD=m - PCI: hv: Support for create interrupt v3 - SAUCE: PCI: hv: Make the code arch neutral by adding arch specific interfaces - SAUCE: arm64: PCI: hv: Add support for Hyper-V vPCI - [Packaging] Update CONFIG_PCI_HYPERV policy for arm64 - PCI: hv: Drop msi_controller structure - clocksource/drivers/hyper-v: Re-enable VDSO_CLOCKMODE_HVCLOCK on X86 * linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver (LP: #1952234) - cpufreq: intel_pstate: Add Icelake servers support in no-HWP mode * hirsute/linux-azure: Backport more CIFS patches (LP: #1950336) - cifs: To match file servers, make sure the server hostname matches - cifs: add mount parameter tcpnodelay [ Ubuntu: 5.11.0-42.46 ] * hirsute/linux: 5.11.0-42.46 -proposed tracker (LP: #1952278) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - debian/dkms-versions -- update from kernel-versions (main/2021.11.29) * CVE-2021-4002 - hugetlbfs: flush TLBs correctly after huge_pmd_unshare * CVE-2021-43267 - tipc: fix size validations for the MSG_CRYPTO type * Hirsute update: upstream stable patchset 2021-11-24 (LP: #1952136) - ext4: check and update i_disksize properly - ext4: correct the error path of ext4_write_inline_data_end() - ASoC: Intel: sof_sdw: tag SoundWire BEs as non-atomic - HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS - netfilter: ip6_tables: zero-initialize fragment offset - HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs - ASoC: SOF: loader: release_firmware() on load failure to avoid batching - netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic - netfilter: nf_nat_masquerade: defer conntrack walk to work queue - mac80211: Drop frames from invalid MAC address in ad-hoc mode - m68k: Handle arrivals of multiple signals correctly - hwmon: (ltc2947) Properly handle errors when looking for the external clock - net:
[Kernel-packages] [Bug 1956383] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551223/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551221/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551227/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551231/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551224/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551225/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551226/+files/PaInfo.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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551222/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551234/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551232/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
well if it is another bogus change to "fix released" why does this keep
happening?
and since it is at least "fix committed" how about an update on what
kernel version the fix is in and when it will be released?
@arighi any update? thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Confirmed
Bug description:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
I installed the Ubuntu 21.10 beta and as soon as I boot I get the
kernel panic that I am attaching.
I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
5.13 kernel I get the same problem, disabling the trackpad and
trackpoint in the bios the problem disappears.
Everything works with the 5.11 kernel.
I remain available for further details and sorry for my lack of experience.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-16-generic 5.13.0-16.16
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pietro 1810 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 30 10:26:10 2021
InstallationDate: Installed on 2021-09-29 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20TA0033IX
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
dmi.bios.date: 09/02/2021
dmi.bios.release: 1.43
dmi.bios.vendor: LENOVO
dmi.bios.version: R1EET43W(1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TA0033IX
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.43
dmi.modalias:
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E14 Gen 2
dmi.product.name: 20TA0033IX
dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
dmi.product.version: ThinkPad E14 Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551230/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551233/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551220/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551219/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551228/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] Re: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot
apport information ** Tags added: apport-collected ** Description changed: 5.13.0-22 worked acceptably well before the update and still works now. - Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the - older kernel, not the latest one with the problem being reported. + Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu71 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: an 1849 F pulseaudio + /dev/snd/controlC0: an 1849 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: MATE + DistroRelease: Ubuntu 21.10 + InstallationDate: Installed on 2019-10-14 (813 days ago) + InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) + IwConfig: + lono wireless extensions. + + enp4s0no wireless extensions. + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro + ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-22-generic N/A + linux-backports-modules-5.13.0-22-generic N/A + linux-firmware 1.201.3 + RfKill: + + Tags: impish + Uname: Linux 5.13.0-22-generic x86_64 + UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) + UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/31/2019 + dmi.bios.release: 5.14 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P2.60 + dmi.board.name: B450M Steel Legend + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: To Be Filled By O.E.M. + dmi.product.sku: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551218/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Kernel-packages] [Bug 1956383] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551229/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956383] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1956383/+attachment/5551235/+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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955932] [NEW] ps5 controller no longer working
You have been subscribed to a public bug: Hello! Up until today, my playstation 5 controller worked great with ubuntu + steam both over bluetooth and wired. Now, I can get the controller connected via bluetooth, and I can use `jstest /dev/input/js0` to read input from the controller in my terminal, but Steam no longer recognizes the controller. This bug only just started happening today. When I check in my journalctl logs when connecting the controller, I see the following, which indicates that perhaps something is going wrong... ``` Dez 28 23:43:13 zagreus kernel: hid-generic 0005:054C:0CE6.0023: unknown main item tag 0x0 Dez 28 23:43:13 zagreus kernel: input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:8/0005:054C:0CE6.0023/input/input65 Dez 28 23:43:13 zagreus kernel: hid-generic 0005:054C:0CE6.0023: input,hidraw8: BLUETOOTH HID v1.00 Gamepad [Wireless Controller] on 9c:b6:d0:ef:fd:7c Dez 28 23:43:13 zagreus systemd-udevd[14721]: js0: Process '/usr/bin/jscal-restore /dev/input/js0' failed with exit code 1. Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) config/udev: Adding input device Wireless Controller (/dev/input/js0) Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) No input driver specified, ignoring this device. Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) This device may have been added with another device file. Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) config/udev: Adding input device Wireless Controller (/dev/input/event30) Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) No input driver specified, ignoring this device. Dez 28 23:43:13 zagreus /usr/lib/gdm3/gdm-x-session[1946]: (II) This device may have been added with another device file. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 28 23:49:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:082a] InstallationDate: Installed on 2020-10-25 (429 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-43-generic root=/dev/mapper/vgubuntu-root ro ipv6.disable=1 quiet splash ipv6.disable=1 vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2019 dmi.bios.release: 2.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 0TPN17 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:br2.11:svnDellInc.:pnXPS139360:pvr:sku082A:rvnDellInc.:rn0TPN17:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 082A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-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: New ** Tags: amd64 apport-bug focal ubuntu -- ps5 controller no longer working https://bugs.launchpad.net/bugs/1955932 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 1956399] [NEW] Regression: kernel does not init graphics (?) on AMD Ryzen 5 3400G
Public bug reported: After latest upgrade of linux-image to 5.13.0.23.34 system seem to boot, but it looks like graphics does not initialize correctly. After showing initial init logging, at the moment when X should init and graphics login should appear, monitor just goes to sleep and provides diagnostic message that there is no signal on selected input. apt upgrade log: Start-Date: 2022-01-04 23:21:11 Commandline: apt upgrade Requested-By: xx (1000) Install: linux-modules-extra-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-image-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-modules-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23:amd64 (5.13.0-23.23, automatic) Upgrade: linux-headers-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), google-chrome-stable:amd64 (96.0.4664.110-1, 97.0.4692.71-1), linux-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-image-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-libc-dev:amd64 (5.13.0-22.22, 5.13.0-23.23) End-Date: 2022-01-04 23:22:39 Currently working around this issues by booting previous version of the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-generic 5.13.0.23.34 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 2532 F pulseaudio /dev/snd/pcmC1D0p: alexei 2532 F...m pulseaudio /dev/snd/controlC0: alexei 2532 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 01:02:53 2022 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (2190 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp8s0no wireless extensions. lxcbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-05 (91 days ago) dmi.bios.date: 05/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.00 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd05/10/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956399 Title: Regression: kernel does not init graphics (?) on AMD Ryzen 5 3400G Status in linux package in Ubuntu: Confirmed Bug description: After latest upgrade of linux-image to 5.13.0.23.34 system seem to boot, but it looks like graphics does not initialize correctly. After showing initial init logging, at the moment when X should init and graphics login should appear, monitor just goes to sleep and provides diagnostic message that there is no signal on selected input. apt upgrade log: Start-Date: 2022-01-04 23:21:11 Commandline: apt upgrade Requested-By: xx (1000) Install: linux-modules-extra-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-image-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-modules-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23:amd64 (5.13.0-23.23, automatic) Upgrade: linux-headers-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), google-chrome-stable:amd64 (96.0.4664.110-1, 97.0.4692.71-1), linux-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-image-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-libc-dev:amd64 (5.13.0-22.22, 5.13.0-23.23) End-Date: 2022-01-04 23:22:39 Currently working around this issues by booting previous version of the kernel. ProblemType: Bug
[Kernel-packages] [Bug 1956416] [NEW] logitech k400 wiresless keyboard/trackpad not recognized as trackpad
Public bug reported: in earlier installs of ubuntu 21.10 i didn't have this problem, but this time in settings/mouse & touchpad, my touchpad does not show up. it works fine as a mouse + two finger scroll, but i cannot tap to click, which i need. in /var/log/syslog: Jan 4 00:15:03 flister-desktop kernel: [1.961613] usb 1-7: Manufacturer: Logitech Jan 4 00:15:03 flister-desktop kernel: [2.035091] input: Logitech USB Receiver as /devices/pci:00/:00:02.1/:01:00.0/usb1/1-7/1-7:1.0/0003:046D:C52B.0001/input/input3 Jan 4 00:15:03 flister-desktop kernel: [2.093490] hid-generic 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-:01:00.0-7/input0 Jan 4 00:15:03 flister-desktop kernel: [2.093621] input: Logitech USB Receiver Mouse as /devices/pci:00/:00:02.1/:01:00.0/usb1/1-7/1-7:1.1/0003:046D:C52B.0002/input/input4 Jan 4 00:15:03 flister-desktop kernel: [2.093690] input: Logitech USB Receiver Consumer Control as /devices/pci:00/:00:02.1/:01:00.0/usb1/1-7/1-7:1.1/0003:046D:C52B.0002/input/input5 Jan 4 00:15:03 flister-desktop kernel: [2.153465] input: Logitech USB Receiver System Control as /devices/pci:00/:00:02.1/:01:00.0/usb1/1-7/1-7:1.1/0003:046D:C52B.0002/input/input6 Jan 4 00:15:03 flister-desktop kernel: [2.153539] hid-generic 0003:046D:C52B.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-:01:00.0-7/input1 Jan 4 00:15:03 flister-desktop kernel: [2.153638] hid-generic 0003:046D:C52B.0003: hiddev1,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-:01:00.0-7/input2 Jan 4 00:15:03 flister-desktop kernel: [2.301661] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-:01:00.0-7/input2 Jan 4 00:15:03 flister-desktop kernel: [2.424572] input: Logitech Wireless Device PID:4024 Keyboard as /devices/pci:00/:00:02.1/:01:00.0/usb1/1-7/1-7:1.2/0003:046D:C52B.0003/0003:046D:4024.0004/input/input8 Jan 4 00:15:03 flister-desktop kernel: [2.424603] input: Logitech Wireless Device PID:4024 Mouse as /devices/pci:00/:00:02.1/:01:00.0/usb1/1-7/1-7:1.2/0003:046D:C52B.0003/0003:046D:4024.0004/input/input9 Jan 4 00:15:03 flister-desktop kernel: [2.424640] hid-generic 0003:046D:4024.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech Wireless Device PID:4024] on usb-:01:00.0-7/input2:1 Jan 4 00:15:03 flister-desktop kernel: [2.648586] input: Logitech K400 as /devices/pci:00/:00:02.1/:01:00.0/usb1/1-7/1-7:1.2/0003:046D:C52B.0003/0003:046D:4024.0004/input/input13 Jan 4 00:15:03 flister-desktop kernel: [2.648675] logitech-hidpp-device 0003:046D:4024.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech K400] on usb-:01:00.0-7/input2:1 Jan 4 00:15:09 flister-desktop kernel: [ 12.006131] logitech-hidpp-device 0003:046D:4024.0004: HID++ 2.0 device connected. Jan 4 00:18:30 flister-desktop gnome-shell[1093]: libinput error: event3 - Logitech K400: client bug: event processing lagging behind by 12ms, your system is too slow Jan 4 00:19:47 flister-desktop kernel: [2.082504] usb 1-7: Manufacturer: Logitech Jan 4 00:19:47 flister-desktop kernel: [2.154905] input: Logitech USB Receiver as /devices/pci:00/:00:02.1/:01:00.0/usb1/1-7/1-7:1.0/0003:046D:C52B.0001/input/input3 Jan 4 00:19:47 flister-desktop kernel: [2.212491] hid-generic 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-:01:00.0-7/input0 Jan 4 00:19:47 flister-desktop kernel: [2.212618] input: Logitech USB Receiver Mouse as /devices/pci:00/:00:02.1/:01:00.0/usb1/1-7/1-7:1.1/0003:046D:C52B.0002/input/input4 Jan 4 00:19:47 flister-desktop kernel: [2.212691] input: Logitech USB Receiver Consumer Control as /devices/pci:00/:00:02.1/:01:00.0/usb1/1-7/1-7:1.1/0003:046D:C52B.0002/input/input5 Jan 4 00:19:47 flister-desktop kernel: [2.272465] input: Logitech USB Receiver System Control as /devices/pci:00/:00:02.1/:01:00.0/usb1/1-7/1-7:1.1/0003:046D:C52B.0002/input/input6 Jan 4 00:19:47 flister-desktop kernel: [2.272537] hid-generic 0003:046D:C52B.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-:01:00.0-7/input1 Jan 4 00:19:47 flister-desktop kernel: [2.272636] hid-generic 0003:046D:C52B.0003: hiddev1,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-:01:00.0-7/input2 Jan 4 00:19:47 flister-desktop kernel: [2.416682] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-:01:00.0-7/input2 Jan 4 00:19:47 flister-desktop kernel: [2.539445] input: Logitech Wireless Device PID:4024 Keyboard as
[Kernel-packages] [Bug 1955916] Re: Bluetooth dongle rtl8761b
What's the output of the following? sudo modprobe -r btusb sudo modprobe btusb sha256sum /lib/modules/`uname -r`/kernel/drivers/bluetooth/btusb.ko xxd /lib/modules/`uname -r`/kernel/drivers/bluetooth/btusb.ko | grep "ca04 0540" xxd /lib/modules/`uname -r`/kernel/drivers/bluetooth/btusb.ko | grep "5025 6187" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1955916 Title: Bluetooth dongle rtl8761b Status in linux package in Ubuntu: Incomplete Bug description: Package: linux-firmware Architecture: all Version: 1.187 The device is recognized, hciconfig -a shows a device, no errors at all. It can scan do whatever. The only thing it doesn't do is find anything. hci0: Type: Primary Bus: USB BD Address: 00:E0:4C:19:xx:xx ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING RX bytes:1706 acl:0 sco:0 events:225 errors:0 TX bytes:6122 acl:0 sco:0 commands:201 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'hostname' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0xb LMP Version: 5.1 (0xa) Subversion: 0x8761 Manufacturer: Realtek Semiconductor Corporation (93) #included on request Ubuntu 5.13.0-23.23~20.04.2-generic 5.13.19 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:191f] (rev 07) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [1458:5000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 07) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31) (prog-if 30 [XHCI]) Subsystem: Gigabyte Technology Co., Ltd 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [1458:5007] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31) Subsystem: Gigabyte Technology Co., Ltd 100 Series/C230 Series Chipset Family MEI Controller [1458:1c3a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: mei_me Kernel modules: mei_me 00:17.0 RAID bus controller [0104]: Intel Corporation SATA Controller [RAID mode] [8086:2822] (rev 31) Subsystem: Gigabyte Technology Co., Ltd SATA Controller [RAID mode] [1458:b005] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ahci Kernel modules: ahci 00:1b.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17 [8086:a167] (rev f1) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1b.2 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #19 [8086:a169] (rev f1) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
[Kernel-packages] [Bug 1956422] [NEW] Linux Kernel 5.13.0-23 Suspend Modus
Public bug reported: Hi there, after updating to kernel 5.13.0-23 the suspend modus is not working anymore. I tried it with a Dell inspiron 5415 with AMD processor and a MacBook with a Intel processor. I have to start with Kernel 5.13.0-22 and then it works fine. When is suspend modus the computer doesn't wake up again. Thanx in advance. Dietmar ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-23-generic 5.13.0-23.23 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dietmar1227 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 08:06:59 2022 InstallationDate: Installed on 2021-10-21 (75 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Apple Inc. MacBook5,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=dfd4fa6d-1d92-4d20-b916-8d9ed9588566 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/09 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB51.88Z.007D.B03.0904271443 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F42D89C8 dmi.board.vendor: Apple Inc. dmi.board.version: Proto dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42D89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:br0.1:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:skuSystemSKU#: dmi.product.family: MacBook dmi.product.name: MacBook5,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956422 Title: Linux Kernel 5.13.0-23 Suspend Modus Status in linux package in Ubuntu: New Bug description: Hi there, after updating to kernel 5.13.0-23 the suspend modus is not working anymore. I tried it with a Dell inspiron 5415 with AMD processor and a MacBook with a Intel processor. I have to start with Kernel 5.13.0-22 and then it works fine. When is suspend modus the computer doesn't wake up again. Thanx in advance. Dietmar ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-23-generic 5.13.0-23.23 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dietmar1227 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 08:06:59 2022 InstallationDate: Installed on 2021-10-21 (75 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Apple Inc. MacBook5,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=dfd4fa6d-1d92-4d20-b916-8d9ed9588566 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/09 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB51.88Z.007D.B03.0904271443 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F42D89C8 dmi.board.vendor: Apple Inc. dmi.board.version: Proto dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42D89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:br0.1:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:skuSystemSKU#: dmi.product.family: MacBook dmi.product.name: MacBook5,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1927808 Title: rtw88_8821ce causes freeze Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1927808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955613] Re: Add basic Wifi support for Qualcomm WCN6856
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955613 Title: Add basic Wifi support for Qualcomm WCN6856 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Confirmed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Confirmed Status in linux-firmware source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Qualcomm WCN6856 doens't work. [Fix] Backport missing bits to make Wifi 5 work. Wifi 6 support is not in the scope of this SRU. [Test] The system can connect to Wifi. Wifi still works after several rounds of suspend/resume cycles. [Where problems could occur] The change is limited to ath11k, which is also the only user of mhi bus, so the scope of risk is limited. Let alone it never worked before, so there's not much room to go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956413] Re: Intel EHL: Two of the on-board ethernet ports don't work
** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956413 Title: Intel EHL: Two of the on-board ethernet ports don't work Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Triaged Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: == Impact == Only one of the three on-board ethernet ports works. The other two can't get IP addresses. == Fix == commit 884d2b845477cd0a18302444dc20fe2d9a01743e Author: David Wu Date: Mon Dec 13 19:15:15 2021 +0800 net: stmmac: Add GFP_DMA32 for rx buffers if no 64 capability Use page_pool_alloc_pages instead of page_pool_dev_alloc_pages, which can give the gfp parameter, in the case of not supporting 64-bit width, using 32-bit address memory can reduce a copy from swiotlb. Signed-off-by: David Wu Signed-off-by: David S. Miller == Risk of Regression == Low. The commit changes gfp parameter only when there's no 64-bit capability, and it is already in mainline. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
