[Kernel-packages] [Bug 1902613] Re: drm/i915/dp_mst - only read the base capability in DPCD.
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1902613 Title: drm/i915/dp_mst - only read the base capability in DPCD. Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] Currently DRM driver assume the source device caps is higher than the MST device caps. With this commit, the statement would be broken. e.g. the source device only support DP1.2 and the mst device support DP1.4. The source device can't output the video to the external monitor on the docking station. [Fix] Revert the previous patch and only read the base capability from DPCD. [test] With the patch, The machine(DP1.2) connect with the external monitor on docking station(SC) and can output the video to the external monitor on docking station(SC-DP1.4). [Regression Potential] Can't output 4k@60hz on the docking station(SC). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905842] Re: Bluetooth once turned off then it does'nt start agin
The Bluetooth menu item is *designed* to hide if turned off and you hadn't paired anything yet https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1426#note_912033 I'm not sure I agree with that design but it does mean it's not a bug. You will need to either: * Re-enable Bluetooth via Settings; or * Pair a Bluetooth device. ** Package changed: bluez (Ubuntu) => gnome-shell (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #1426 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1426 ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1905842 Title: Bluetooth once turned off then it does'nt start agin Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Bluetooth does'nt start once turned off. It only starts when I restart my system. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 12:43:08 2020 InstallationDate: Installed on 2020-10-29 (28 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=cd634a09-ce20-463b-aa0a-8d92be8e0864 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/05/2013 dmi.bios.release: 15.101 dmi.bios.vendor: Insyde dmi.bios.version: F.65 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.44 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 33.68 dmi.modalias: dmi:bvnInsyde:bvrF.65:bd02/05/2013:br15.101:efr33.68:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.44:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: D7Z60PC#ACJ dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 2C:D0:5A:58:29:47 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:1289 acl:0 sco:0 events:108 errors:0 TX bytes:5027 acl:0 sco:0 commands:87 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905214] Re: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update
Lenovo thinkpad P1 Gen2, AX200, bt 8087:0029 Works. BT headset connected for 9 hours without problems -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905214 Title: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Groovy: In Progress Status in linux-firmware source package in Hirsute: Fix Released Bug description: For H, it already has all patches, this SRU is not needed for H For G, only needs the 0005-xxx.patch and 0010-xxx.patch For F, needs all patches. [Impact] We found 2 issues: Bluetooth headset can't work in hsp/hfp mode, Both AX200 and AX201 have this issue (#1871794) Bluetooth will stop working randomly on the machines with AX200 (OEM bug). [Fix] Update the firmware to the latest version, the above 2 issues could be fixed. [Test] connect a bluetooth headset, after connecting, it is in A2DP mode by default, change it to hsp/hfp mode from gnome-sound-setting, play sound and record sound from headset, all work well. Keep the machine powered on and let it be idle for 1 day, check the bluetooth headset, still could work. [Regression Potential] I could make the Bluetooth function stop working on the machines with AX200 or AX201 module, like can't scan the BT devices, can't connect the BT devices or the BT devices can't work normally. But this possibility is very low, we have tested the SRU on a couple of lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905841] 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/1905841 Title: Touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: I dual booted Ubuntu and the touchpad has not been working from the beginningg, ever since I booted from the USB stick ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: animesh1204 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 00:09:43 2020 InstallationDate: Installed on 2020-11-27 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 062a:4102 MosArt Semiconductor Corp. 2.4G Wireless Mouse Bus 001 Device 002: ID 04f2:b6d9 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=41982936-95b1-4d20-9313-a152b947f662 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN37WW:bd06/24/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905841] [NEW] Touchpad not working
Public bug reported: I dual booted Ubuntu and the touchpad has not been working from the beginningg, ever since I booted from the USB stick ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: animesh1204 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 00:09:43 2020 InstallationDate: Installed on 2020-11-27 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 062a:4102 MosArt Semiconductor Corp. 2.4G Wireless Mouse Bus 001 Device 002: ID 04f2:b6d9 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=41982936-95b1-4d20-9313-a152b947f662 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN37WW:bd06/24/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1905841/+attachment/5438571/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905841 Title: Touchpad not working Status in linux package in Ubuntu: New Bug description: I dual booted Ubuntu and the touchpad has not been working from the beginningg, ever since I booted from the USB stick ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: animesh1204 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 00:09:43 2020 InstallationDate: Installed on 2020-11-27 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 062a:4102 MosArt Semiconductor Corp. 2.4G Wireless Mouse Bus 001 Device 002: ID 04f2:b6d9 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=41982936-95b1-4d20-9313-a152b947f662 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN37WW:bd06/24/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE
[Kernel-packages] [Bug 1905842] [NEW] Bluetooth once turned off then it does'nt start agin
Public bug reported: Bluetooth does'nt start once turned off. It only starts when I restart my system. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 12:43:08 2020 InstallationDate: Installed on 2020-10-29 (28 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=cd634a09-ce20-463b-aa0a-8d92be8e0864 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/05/2013 dmi.bios.release: 15.101 dmi.bios.vendor: Insyde dmi.bios.version: F.65 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.44 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 33.68 dmi.modalias: dmi:bvnInsyde:bvrF.65:bd02/05/2013:br15.101:efr33.68:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.44:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: D7Z60PC#ACJ dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0: Type: Primary Bus: USB BD Address: 2C:D0:5A:58:29:47 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:1289 acl:0 sco:0 events:108 errors:0 TX bytes:5027 acl:0 sco:0 commands:87 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1905842 Title: Bluetooth once turned off then it does'nt start agin Status in bluez package in Ubuntu: New Bug description: Bluetooth does'nt start once turned off. It only starts when I restart my system. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 12:43:08 2020 InstallationDate: Installed on 2020-10-29 (28 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=cd634a09-ce20-463b-aa0a-8d92be8e0864 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/05/2013 dmi.bios.release: 15.101 dmi.bios.vendor: Insyde dmi.bios.version: F.65 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.44 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 33.68 dmi.modalias: dmi:bvnInsyde:bvrF.65:bd02/05/2013:br15.101:efr33.68:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.44:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: D7Z60PC#ACJ dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 2C:D0:5A:58:29:47 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:1289 acl:0 sco:0 events:108 errors:0 TX bytes:5027 acl:0 sco:0 commands:87 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1905842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905214] Re: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update
** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905214 Title: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Groovy: In Progress Status in linux-firmware source package in Hirsute: Fix Released Bug description: For H, it already has all patches, this SRU is not needed for H For G, only needs the 0005-xxx.patch and 0010-xxx.patch For F, needs all patches. [Impact] We found 2 issues: Bluetooth headset can't work in hsp/hfp mode, Both AX200 and AX201 have this issue (#1871794) Bluetooth will stop working randomly on the machines with AX200 (OEM bug). [Fix] Update the firmware to the latest version, the above 2 issues could be fixed. [Test] connect a bluetooth headset, after connecting, it is in A2DP mode by default, change it to hsp/hfp mode from gnome-sound-setting, play sound and record sound from headset, all work well. Keep the machine powered on and let it be idle for 1 day, check the bluetooth headset, still could work. [Regression Potential] I could make the Bluetooth function stop working on the machines with AX200 or AX201 module, like can't scan the BT devices, can't connect the BT devices or the BT devices can't work normally. But this possibility is very low, we have tested the SRU on a couple of lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903397] Re: Groovy 5.8 kernel hangs on boot on CPUs with eLLC
** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903397 Title: Groovy 5.8 kernel hangs on boot on CPUs with eLLC Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.8 package in Ubuntu: New Status in linux-hwe-5.8 source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Bug description: 5.8 kernel hangs on boot on my PC with Intel Core i7-5775C. Bug is already fixed upstream: https://gitlab.freedesktop.org/drm/intel/-/issues/2381 https://bugzilla.kernel.org/show_bug.cgi?id=208737 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.10-rc1=1664ffee760a5d98952318fdd9b198fae396d660 Please backport the fix. Thanks! [Impact] * Bug causes boot failure on common hardware. [Test Case] * Test kernel validated by submitter (see Comment #6). [Regression Potential] * Low: Simple cherry-pick from upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905823] [NEW] task mount blocked - SSD keeps unmounting becoming read-only
Public bug reported: Im running Ubuntu 20.4 on Raspberry Pi 4 running Geth attempting to sync with Eth1 during fast sync i incur a critical error CRIT Failed to store fast sync trie process err="write /mnt/ssd/ethereum/geth/chaindata/80.log: read-only file system when i check the file system i can see the directory and data is there, but after reboot, the SSD does nto mount and on restart and log in Ubuntu repeats the following if unattended Tainted: GCE 5.4.0-1022-raspi #25-Ubuntu Is this a bug or is my SSD damaged? Ive tried re-formatting the SSD, remounting and re-starting sync successfully, but ultimatley end up with the same problem. Please advise ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1905823 Title: task mount blocked - SSD keeps unmounting becoming read-only Status in linux-raspi package in Ubuntu: New Bug description: Im running Ubuntu 20.4 on Raspberry Pi 4 running Geth attempting to sync with Eth1 during fast sync i incur a critical error CRIT Failed to store fast sync trie process err="write /mnt/ssd/ethereum/geth/chaindata/80.log: read-only file system when i check the file system i can see the directory and data is there, but after reboot, the SSD does nto mount and on restart and log in Ubuntu repeats the following if unattended Tainted: GCE 5.4.0-1022-raspi #25-Ubuntu Is this a bug or is my SSD damaged? Ive tried re-formatting the SSD, remounting and re-starting sync successfully, but ultimatley end up with the same problem. Please advise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1905823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837326] Re: platform eisa.0: EISA: Cannot allocate resource for mainboard
Same: uname -a Linux … 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837326 Title: platform eisa.0: EISA: Cannot allocate resource for mainboard Status in linux package in Ubuntu: Confirmed Bug description: dmesg: [0.889531] platform eisa.0: EISA: Cannot allocate resource for mainboard [0.889533] platform eisa.0: Cannot allocate resource for EISA slot 1 [0.889535] platform eisa.0: Cannot allocate resource for EISA slot 2 [0.889536] platform eisa.0: Cannot allocate resource for EISA slot 3 [0.889537] platform eisa.0: Cannot allocate resource for EISA slot 4 [0.889539] platform eisa.0: Cannot allocate resource for EISA slot 5 [0.889540] platform eisa.0: Cannot allocate resource for EISA slot 6 [0.889541] platform eisa.0: Cannot allocate resource for EISA slot 7 [0.889542] platform eisa.0: Cannot allocate resource for EISA slot 8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 3028 F pulseaudio /dev/snd/pcmC0D0p: caravena 3028 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jul 21 12:16:07 2019 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (230 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2018-12-02 (230 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866323] Re: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866323 Title: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Released Bug description: Test failure in fallocate06 was composed by two issues, one is xfs fill_fs test issue addressed in bug 1865967. Another is this one, this is the case 2 of btrfs (fill_fs): tst_test.c:1290: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (2 This issue can be found from X to F X - https://pastebin.ubuntu.com/p/9FfVrZkQN8/ B - https://pastebin.ubuntu.com/p/Zc9TW4sQKF/ D - https://pastebin.ubuntu.com/p/cryTnnn5wF/ E - https://pastebin.ubuntu.com/p/FXTZpsX7Qb/ F - https://pastebin.ubuntu.com/p/FKPJKCS2zr/ Note that the hint printed in the test: HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e093c4be760e It something that will get printed after the test, as it's for XFS so it has nothing to do with this issue here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891421] Re: kci_test_encap_fou() in rtnetlink.sh from kselftests/net failed with "FAIL: can't add fou port 7777, skipping test"
Issue has gone on 5.4.0-1030.32-oracle
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1891421
Title:
kci_test_encap_fou() in rtnetlink.sh from kselftests/net failed with
"FAIL: can't add fou port , skipping test"
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux-oem-osp1 package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux-oem-5.6 source package in Bionic:
Invalid
Status in linux-oem-osp1 source package in Bionic:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Fix Committed
Status in linux-oem-osp1 source package in Focal:
Invalid
Status in linux source package in Groovy:
Fix Committed
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux-oem-osp1 source package in Groovy:
Invalid
Bug description:
== SRU Justification ==
The kci_test_encap_fou() from kci_test_encap() in rtnetlink.sh of
kselftests/net will fail with non-zero return value, and print:
"FAIL: can't add fou port , skipping test"
How to reproduce this:
devdummy="test-dummy0"
testns="testns"
ip netns add "$testns"
ip netns exec "$testns" ip link set lo up
ip netns exec "$testns" ip link add name "$devdummy" type dummy
ip netns exec "$testns" ip link set "$devdummy" up
ip netns exec "$testns" ip fou add port ipproto 47
RTNETLINK answers: No such file or directory
Error talking to the kernel
This test would require the fou module to be loaded before it gets
started.
== Fix
* 26ebd6fed9bb ("selftests: rtnetlink: load fou module for
kci_test_encap_fou() test")
This patch needs to be backported for series after Xenial.
== Test ==
Patch tested directly on the kernel tree, the test will now pass as
expected.
== Regression Potential ==
Low, change limited to the testing tool.
== Original Bug Report ==
The kci_test_encap_fou() from kci_test_encap() in rtnetlink.sh of
kselftests/net will fail with non-zero return value, and print:
"FAIL: can't add fou port , skipping test"
How to reproduce this:
devdummy="test-dummy0"
testns="testns"
ip netns add "$testns"
ip netns exec "$testns" ip link set lo up
ip netns exec "$testns" ip link add name "$devdummy" type dummy
ip netns exec "$testns" ip link set "$devdummy" up
ip netns exec "$testns" ip fou add port ipproto 47
RTNETLINK answers: No such file or directory
Error talking to the kernel
This is not a regression, it's the real test result after bug 1890136
has been fixed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1891421/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
Can you double check that URL? Doesn't seem to be working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905808] Re: alsa/hda: The sound output is abnormal when the balance is on center after switch from the audio speaker to headset on a Dell AIO
** Description changed: - This bug is for tracking purpose + Since this patch is cced to stable kernel, I only send this patch + to oem-5.6 kernel since oem project needs it, other ubuntu kernels + will merge this patch with stable update. + + [Impact] + The sound output is abnormal when the balance is on center after + switch from the audio speaker to headset on a Dell AIO + + [Fix] + Realtek engineer submit a patch to usptream, I backport this patch + to ubuntu oem kernel. + + [Test] + plug a speaker, plug out this speaker, then plug a headset, play some + sound from headset, the sound quality is pretty good. + + [Regression Potential] + This SRU could make some Dell AIO not work well on audio output, like + can't output sound or output poor quality sound. but this posibility is + low since we tested this patch on a couple of dell AIO, all worked well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1905808 Title: alsa/hda: The sound output is abnormal when the balance is on center after switch from the audio speaker to headset on a Dell AIO Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: In Progress Status in linux-oem-5.6 source package in Focal: In Progress Bug description: Since this patch is cced to stable kernel, I only send this patch to oem-5.6 kernel since oem project needs it, other ubuntu kernels will merge this patch with stable update. [Impact] The sound output is abnormal when the balance is on center after switch from the audio speaker to headset on a Dell AIO [Fix] Realtek engineer submit a patch to usptream, I backport this patch to ubuntu oem kernel. [Test] plug a speaker, plug out this speaker, then plug a headset, play some sound from headset, the sound quality is pretty good. [Regression Potential] This SRU could make some Dell AIO not work well on audio output, like can't output sound or output poor quality sound. but this posibility is low since we tested this patch on a couple of dell AIO, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905808] [NEW] alsa/hda: The sound output is abnormal when the balance is on center after switch from the audio speaker to headset on a Dell AIO
Public bug reported: This bug is for tracking purpose ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-5.6 (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: Critical Assignee: Hui Wang (hui.wang) Status: In Progress ** Tags: oem-priority originate-from-1895332 somerville ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => In Progress ** Changed in: linux-oem-5.6 (Ubuntu) Importance: Undecided => Critical ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux-oem-5.6 (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) ** Tags added: oem-priority originate-from-1895332 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1905808 Title: alsa/hda: The sound output is abnormal when the balance is on center after switch from the audio speaker to headset on a Dell AIO Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: In Progress Status in linux-oem-5.6 source package in Focal: In Progress Bug description: This bug is for tracking purpose To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905807] [NEW] insecure W+X mapping
Public bug reported: [ 19.051518] Freeing unused kernel memory: 308K [ 19.062326] [ cut here ] [ 19.066219] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 19.074930] WARNING: CPU: 0 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 19.082806] Modules linked in: [ 19.085825] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.8.0-10-generic #12+21.04.1-Ubuntu [ 19.094007] epc: ffe000208f18 ra : ffe000208f18 sp : ffe1f5b9fb30 [ 19.101104] gp : ffe001728ee0 tp : ffe1f5bedc00 t0 : ffe00173edf8 [ 19.108330] t1 : ffe00173ed90 t2 : 0001feca5000 s0 : ffe1f5b9fb80 [ 19.115536] s1 : ffe1f5b9fe10 a0 : 0053 a1 : 00020020 [ 19.122743] a2 : ffe1f5b9f870 a3 : a4 : ffe0016200f8 [ 19.129949] a5 : ffe0016200f8 a6 : 00c1 a7 : ffe0006f27fe [ 19.137156] s2 : ffdff8001000 s3 : s4 : 0004 [ 19.144376] s5 : s6 : s7 : ffe1f5b9fd20 [ 19.151570] s8 : ffdff8001000 s9 : ffe00172a148 s10: ffdff8002000 [ 19.158775] s11: ffe000c16e20 t3 : 0003ce50 t4 : 0003ce50 [ 19.165980] t5 : t6 : ffe001739462 [ 19.171255] status: 00020120 badaddr: cause: 0003 [ 19.179177] ---[ end trace 72fa85d58b123e2f ]--- [ 19.184544] Checked W+X mappings: failed, 513 W+X pages found [ 19.189561] Run /init as init process Not sure what that means. This is on [0.00] Linux version 5.8.0-10-generic (buildd@riscv64-qemu-lcy01-087) (gcc (Ubuntu 10.2.0-18ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #12+21.04.1-Ubuntu SMP Fri Nov 20 16:26:05 UTC 2020 (Ubuntu 5.8.0-10.12+21.04.1-generic 5.8.17) will try to get full logs. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1905807 Title: insecure W+X mapping Status in linux-riscv package in Ubuntu: New Bug description: [ 19.051518] Freeing unused kernel memory: 308K [ 19.062326] [ cut here ] [ 19.066219] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 19.074930] WARNING: CPU: 0 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 19.082806] Modules linked in: [ 19.085825] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.8.0-10-generic #12+21.04.1-Ubuntu [ 19.094007] epc: ffe000208f18 ra : ffe000208f18 sp : ffe1f5b9fb30 [ 19.101104] gp : ffe001728ee0 tp : ffe1f5bedc00 t0 : ffe00173edf8 [ 19.108330] t1 : ffe00173ed90 t2 : 0001feca5000 s0 : ffe1f5b9fb80 [ 19.115536] s1 : ffe1f5b9fe10 a0 : 0053 a1 : 00020020 [ 19.122743] a2 : ffe1f5b9f870 a3 : a4 : ffe0016200f8 [ 19.129949] a5 : ffe0016200f8 a6 : 00c1 a7 : ffe0006f27fe [ 19.137156] s2 : ffdff8001000 s3 : s4 : 0004 [ 19.144376] s5 : s6 : s7 : ffe1f5b9fd20 [ 19.151570] s8 : ffdff8001000 s9 : ffe00172a148 s10: ffdff8002000 [ 19.158775] s11: ffe000c16e20 t3 : 0003ce50 t4 : 0003ce50 [ 19.165980] t5 : t6 : ffe001739462 [ 19.171255] status: 00020120 badaddr: cause: 0003 [ 19.179177] ---[ end trace 72fa85d58b123e2f ]--- [ 19.184544] Checked W+X mappings: failed, 513 W+X pages found [ 19.189561] Run /init as init process Not sure what that means. This is on [0.00] Linux version 5.8.0-10-generic (buildd@riscv64-qemu-lcy01-087) (gcc (Ubuntu 10.2.0-18ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #12+21.04.1-Ubuntu SMP Fri Nov 20 16:26:05 UTC 2020 (Ubuntu 5.8.0-10.12+21.04.1-generic 5.8.17) will try to get full logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1905807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905214] Re: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update
Verified on focal, installed the 1.187.6 on a lenovo x13 yoga (the bt module 8087:0026), it works well and the bt headset could work in hsp/hfp mode. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905214 Title: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Groovy: In Progress Status in linux-firmware source package in Hirsute: Fix Released Bug description: For H, it already has all patches, this SRU is not needed for H For G, only needs the 0005-xxx.patch and 0010-xxx.patch For F, needs all patches. [Impact] We found 2 issues: Bluetooth headset can't work in hsp/hfp mode, Both AX200 and AX201 have this issue (#1871794) Bluetooth will stop working randomly on the machines with AX200 (OEM bug). [Fix] Update the firmware to the latest version, the above 2 issues could be fixed. [Test] connect a bluetooth headset, after connecting, it is in A2DP mode by default, change it to hsp/hfp mode from gnome-sound-setting, play sound and record sound from headset, all work well. Keep the machine powered on and let it be idle for 1 day, check the bluetooth headset, still could work. [Regression Potential] I could make the Bluetooth function stop working on the machines with AX200 or AX201 module, like can't scan the BT devices, can't connect the BT devices or the BT devices can't work normally. But this possibility is very low, we have tested the SRU on a couple of lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
NAK on the linux patch. I think this is a grub bug. When loading multiple initrds, grub aligns_up each one of them at 4bytes boundary, and allocates pages for that. And it declares and passes ramdisk_image as the total allocated memory. Rather than the true size of the initrds. ** Changed in: grub2 (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Triaged Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
As discussed at https://github.com/lz4/lz4/issues/956 I really think it is grub2 secureboot patches linuxefi bug. WIP thing is here https://github.com/rhboot/grub2/pull/77/files ** Bug watch added: github.com/lz4/lz4/issues #956 https://github.com/lz4/lz4/issues/956 ** Changed in: grub2 (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: grub2 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Triaged Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901215] Re: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel]
*** This bug is a duplicate of bug 1902469 *** https://bugs.launchpad.net/bugs/1902469 ** This bug has been marked a duplicate of bug 1902469 drm/i915/dp_mst - System would hang during the boot up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901215 Title: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel] Status in linux package in Ubuntu: Confirmed Bug description: Dell XPS 9650 with a TB16 thunderbolt dock. 2 external displays through the dock (HDMI and VGA). My system uses graphical boot via plymouth. Dell logo remains on screen while ubuntu loads into gdm3 (when it is booting normally). I'm using LUKS. This is a regression from focal and kernel 5.4. If I boot the laptop with the thunderbolt dock connected, the system will get past the Dell logo, go to a black screen and remain there. The screen is powered up as I can see some light on the edges. It won't boot up or respond to any keys. After force-shutdown via power key long press, on the next boot the grub menu will appear. The system will boot normally then (with the dock still connected). If I boot the system with the dock disconnected, it will correctly go into disk encryption password prompt. If at that point I connect the dock and wait without entering the password, the system will correctly set up the dock: the displays lit up and the mouse and keyboard plugged into it become active. The system boots normally. I'm trying to bisect in which kernel version this happened. I'll put results in a comment. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.25.30 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: luis 3332 F pulseaudio /dev/snd/controlC0: luis 3332 F pulseaudio CasperMD5CheckResult: skip Date: Fri Oct 23 16:27:30 2020 InstallationDate: Installed on 2019-08-17 (432 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=/dev/mapper/vglinux-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-09 (13 days ago) dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881505] Re: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1881505 Title: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Now and then, the notebooks stops producing any sound, and program that try to use sound output freeze for many seconds. There is a repeating sequence on messages in `dmesg`: [116525.402057] sof-audio-pci :00:1f.3: error: ipc timed out for 0x8001 size 120 [116525.402081] sof-audio-pci :00:1f.3: status: fw entered - code 0005 [116525.402338] sof-audio-pci :00:1f.3: error: can't enter idle [116525.402342] sof-audio-pci :00:1f.3: error: trace point 4000 [116525.402346] sof-audio-pci :00:1f.3: error: panic at src/lib/agent.c:50 [116525.402350] sof-audio-pci :00:1f.3: error: DSP Firmware Oops [116525.402356] sof-audio-pci :00:1f.3: EXCCAUSE 0x003f EXCVADDR 0x PS 0x00060925 SAR 0x [116525.402361] sof-audio-pci :00:1f.3: EPC1 0x EPC2 0xbe00d30e EPC3 0x EPC40x [116525.402365] sof-audio-pci :00:1f.3: EPC5 0x EPC6 0x EPC7 0x DEPC0x [116525.402369] sof-audio-pci :00:1f.3: EPS2 0x00060d20 EPS3 0x EPS4 0x EPS50x [116525.402374] sof-audio-pci :00:1f.3: EPS6 0x EPS7 0x INTENABL 0x INTERRU 0x0222 [116525.402378] sof-audio-pci :00:1f.3: stack dump from 0xbe04f5b0 [116525.402385] sof-audio-pci :00:1f.3: 0xbe04f5b0: be00fc00 be04f5e0 be062180 0001 [116525.402391] sof-audio-pci :00:1f.3: 0xbe04f5b4: 0032 [116525.402396] sof-audio-pci :00:1f.3: 0xbe04f5b8: 69cd0100 15655b6c 602aeaf8 93a4 [116525.402401] sof-audio-pci :00:1f.3: 0xbe04f5bc: 93a4 303a3030 [116525.402406] sof-audio-pci :00:1f.3: 0xbe04f5c0: 0078 602aea98 93a4 [116525.402411] sof-audio-pci :00:1f.3: 0xbe04f5c4: 6bdcfb58 93a4 5d006830 93a4 [116525.402416] sof-audio-pci :00:1f.3: 0xbe04f5c8: 6ba37218 93a4 82317aaf bca5 [116525.402421] sof-audio-pci :00:1f.3: 0xbe04f5cc: 6ba37220 93a4 023179f8 bca5 [116525.402446] sof-audio-pci :00:1f.3: error: hda irq intsts 0x intlctl 0xc081 rirb 00 [116525.402450] sof-audio-pci :00:1f.3: error: dsp irq ppsts 0x adspis 0x [116525.402471] sof-audio-pci :00:1f.3: error: host status 0x dsp status 0x mask 0x0003 [116525.402475] sof-audio-pci :00:1f.3: error: waking up any trace sleepers [116525.402481] sof-audio-pci :00:1f.3: error: failed to set dai config for iDisp1 [116525.402486] sof-audio-pci :00:1f.3: ASoC: can't set iDisp1 Pin hw params: -110 [116525.402498] iDisp1: ASoC: hw_params BE failed -110 [116525.402502] HDMI1: ASoC: hw_params BE failed -110 This _might_ be the upstream bug https://github.com/thesofproject/sof/issues/2828 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crosser 42712 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 31 20:40:20 2020 InstallationDate: Installed on 2020-01-02 (149 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) MachineType: LENOVO 20QDCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET50W(1.33):bd05/13/2020:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1
[Kernel-packages] [Bug 1902469] Re: drm/i915/dp_mst - System would hang during the boot up.
I can confirm the kernel in groovy-proposed fixes this issue: # enable proposed cat
[Kernel-packages] [Bug 830915] Re: Error during kernel upgrade: Could not locate dkms.conf file
@Syslog.eu: This simple addition allowed me to stop flailing and zero in on the problem! The "Could not locate dkms.conf file" error wasn't enough. Knowing what it was looking for IMMEDIATELY showed me what the problem was. For whatever reason, the version number reflected in the folder /var/lib/dkms/nvidia/ was *not* the same as the installed driver version. As a result, the contained symlink `source` was also pointed to the wrong version number. Renaming the folder to the installed version and updating the symlink allowed dkms to successfully rebuild the driver. I can only assume the error was a fatfinger on my part as the incorrect version doesn't exist. I hope your simple addition makes it's way upstream so it can be useful to others. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/830915 Title: Error during kernel upgrade: Could not locate dkms.conf file Status in dkms package in Ubuntu: Incomplete Bug description: Настраивается пакет linux-image-3.0.0-9-generic (3.0.0-9.12) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms 3.0.0-9-generic /boot/vmlinuz-3.0.0-9-generic Error! Could not locate dkms.conf file. File: does not exist. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.0.0-9-generic /boot/vmlinuz-3.0.0-9-generic update-initramfs: Generating /boot/initrd.img-3.0.0-9-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.0.0-9-generic /boot/vmlinuz-3.0.0-9-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 3.0.0-9-generic /boot/vmlinuz-3.0.0-9-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.0.0-9-generic /boot/vmlinuz-3.0.0-9-generic Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.0.0-9-generic Found initrd image: /boot/initrd.img-3.0.0-9-generic Found linux image: /boot/vmlinuz-3.0.0-8-generic Found initrd image: /boot/initrd.img-3.0.0-8-generic Found linux image: /boot/vmlinuz-2.6.38-10-generic Found initrd image: /boot/initrd.img-2.6.38-10-generic Found memtest86+ image: /boot/memtest86+.bin Found Ubuntu Natty (development branch) (11.04) on /dev/sdb5 done This, however, doesn't seem to be fatal. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: dkms 2.2.0.2-1 ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1 Uname: Linux 3.0.0-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Aug 22 12:43:31 2011 InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: dkms UpgradeStatus: Upgraded to oneiric on 2011-08-10 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/830915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905787] Re: package linux-firmware 1.187.6 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905787 Title: package linux-firmware 1.187.6 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: Migrating from 18.04.05 to 20.04.1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.6 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ba033462279 F pulseaudio /dev/snd/controlC0: ba033462279 F pulseaudio CasperMD5CheckResult: skip Date: Thu Nov 26 15:29:42 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=bdfb5b60-2f66-45e6-a1fc-7c87d5f3867d InstallationDate: Installed on 2017-08-20 (1194 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=66854b36-6a3e-46f6-930d-2c9ca2f26faf ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware Title: package linux-firmware 1.187.6 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: Default string dmi.board.name: STRIX Z270E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd03/22/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXZ270EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905787] [NEW] package linux-firmware 1.187.6 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: Migrating from 18.04.05 to 20.04.1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.6 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ba033462279 F pulseaudio /dev/snd/controlC0: ba033462279 F pulseaudio CasperMD5CheckResult: skip Date: Thu Nov 26 15:29:42 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=bdfb5b60-2f66-45e6-a1fc-7c87d5f3867d InstallationDate: Installed on 2017-08-20 (1194 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=66854b36-6a3e-46f6-930d-2c9ca2f26faf ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware Title: package linux-firmware 1.187.6 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: Default string dmi.board.name: STRIX Z270E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd03/22/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXZ270EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-from-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905787 Title: package linux-firmware 1.187.6 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: Migrating from 18.04.05 to 20.04.1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.6 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ba033462279 F pulseaudio /dev/snd/controlC0: ba033462279 F pulseaudio CasperMD5CheckResult: skip Date: Thu Nov 26 15:29:42 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=bdfb5b60-2f66-45e6-a1fc-7c87d5f3867d InstallationDate: Installed on 2017-08-20 (1194 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=66854b36-6a3e-46f6-930d-2c9ca2f26faf ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware Title: package linux-firmware 1.187.6 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: Default string dmi.board.name: STRIX Z270E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
The attachment "[PATCH] unlz4: Handle 0-size chunks, discard trailing padding/garbage" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: New Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905786] [NEW] perf_event_open is not restricted to admin by default
Public bug reported: [Impact] perf_event_open is not restricted by default, which means unprivileged users may have access to information they should not have. [Test case] Run as an unprivileged user: perf stat true and check that it fails. [Potential regression] Users who expect to be able to use perf will not be able to do it. The fix might also cause the build to fail, in case it doesn't match enforced config options. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Invalid ** Affects: linux-raspi2 (Ubuntu Bionic) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-raspi2 (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux-raspi2 (Ubuntu Bionic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905786 Title: perf_event_open is not restricted to admin by default Status in linux package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-raspi2 source package in Bionic: In Progress Bug description: [Impact] perf_event_open is not restricted by default, which means unprivileged users may have access to information they should not have. [Test case] Run as an unprivileged user: perf stat true and check that it fails. [Potential regression] Users who expect to be able to use perf will not be able to do it. The fix might also cause the build to fail, in case it doesn't match enforced config options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905761] 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/1905761 Title: "perf record" doesn't have compression enabled Status in linux package in Ubuntu: Confirmed Bug description: "perf record --help" indicates that it should support compression: """ -z, --compression-level[=n] Produce compressed trace using specified level n (default: 1 - fastest compression, 22 - smallest trace) """ However, when trying to use that option, one gets the following error: """ Error: unknown switch `z' Usage: perf record [] [] or: perf record [] -- [] [etc.] """ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-tools-common 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antoine2985 F pulseaudio /dev/snd/controlC1: antoine2985 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Nov 26 18:03:55 2020 InstallationDate: Installed on 2013-04-12 (2784 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130409) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=ed011dc6-f138-4ba8-9e89-bc69c075a0d8 ro quiet splash nomodeset vga=845 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-09-06 (81 days ago) dmi.bios.date: 07/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.50 dmi.board.name: X370 Gaming X 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.50:bd07/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370GamingX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2019-04-25T00:25:35.163654 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905214] Re: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update
I can confirm this fixes the issue for me on the 2020 Dell XPS 13 Dev Edition with Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905214 Title: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Groovy: In Progress Status in linux-firmware source package in Hirsute: Fix Released Bug description: For H, it already has all patches, this SRU is not needed for H For G, only needs the 0005-xxx.patch and 0010-xxx.patch For F, needs all patches. [Impact] We found 2 issues: Bluetooth headset can't work in hsp/hfp mode, Both AX200 and AX201 have this issue (#1871794) Bluetooth will stop working randomly on the machines with AX200 (OEM bug). [Fix] Update the firmware to the latest version, the above 2 issues could be fixed. [Test] connect a bluetooth headset, after connecting, it is in A2DP mode by default, change it to hsp/hfp mode from gnome-sound-setting, play sound and record sound from headset, all work well. Keep the machine powered on and let it be idle for 1 day, check the bluetooth headset, still could work. [Regression Potential] I could make the Bluetooth function stop working on the machines with AX200 or AX201 module, like can't scan the BT devices, can't connect the BT devices or the BT devices can't work normally. But this possibility is very low, we have tested the SRU on a couple of lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905761] Re: "perf record" doesn't have compression enabled
** 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/1905761 Title: "perf record" doesn't have compression enabled Status in linux package in Ubuntu: New Bug description: "perf record --help" indicates that it should support compression: """ -z, --compression-level[=n] Produce compressed trace using specified level n (default: 1 - fastest compression, 22 - smallest trace) """ However, when trying to use that option, one gets the following error: """ Error: unknown switch `z' Usage: perf record [] [] or: perf record [] -- [] [etc.] """ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-tools-common 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antoine2985 F pulseaudio /dev/snd/controlC1: antoine2985 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Nov 26 18:03:55 2020 InstallationDate: Installed on 2013-04-12 (2784 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130409) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=ed011dc6-f138-4ba8-9e89-bc69c075a0d8 ro quiet splash nomodeset vga=845 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-09-06 (81 days ago) dmi.bios.date: 07/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.50 dmi.board.name: X370 Gaming X 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.50:bd07/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370GamingX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2019-04-25T00:25:35.163654 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905761] [NEW] "perf record" doesn't have compression enabled
You have been subscribed to a public bug: "perf record --help" indicates that it should support compression: """ -z, --compression-level[=n] Produce compressed trace using specified level n (default: 1 - fastest compression, 22 - smallest trace) """ However, when trying to use that option, one gets the following error: """ Error: unknown switch `z' Usage: perf record [] [] or: perf record [] -- [] [etc.] """ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-tools-common 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antoine2985 F pulseaudio /dev/snd/controlC1: antoine2985 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Nov 26 18:03:55 2020 InstallationDate: Installed on 2013-04-12 (2784 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130409) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=ed011dc6-f138-4ba8-9e89-bc69c075a0d8 ro quiet splash nomodeset vga=845 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-09-06 (81 days ago) dmi.bios.date: 07/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.50 dmi.board.name: X370 Gaming X 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.50:bd07/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370GamingX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2019-04-25T00:25:35.163654 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- "perf record" doesn't have compression enabled https://bugs.launchpad.net/bugs/1905761 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 1905782] 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/1905782 Title: kernel freeze on USB disconnect after failure to set rts/dts on USB VCP device Status in linux package in Ubuntu: Confirmed Bug description: When plugging in a USB device on Ubuntu 18.04 that offers a virtual modem/com port (typically /dev/ttyACM0) then the "modemmanager" service will try to configure this modem/serial port automatically without user interaction, setting dtr/rts parameters. However sometimes USB modem devices are used as a generic serial interface to hardware internals, without an actual serial line connected. Setting dtr/rts makes no sense in this context, and this feature might be unsupported. This, however, triggers a faulty code path in the linux kernel that on device disconnect causes a kworker process to freeze - blocking the CPU core it is running on indefinitely. This in turn has catastrophic effects on system stability. Some IO calls, that run on other cores, will work without problem, while those scheduled on the same core will never execute. Although no "OOPS" or "PANIC" is generated, the situation is dire, as the system typically can not be shutdown or rebooted, and during tests I ended up with file system corruption in a few cases that could not be fixed by a simple journal recovery To trigger this bug, several side-conditions need to be met: 1. A USB device needs to be plugged in that provides a virtual com port 2. The device must not support setting of DTR/RTS parameters 3. A program must try to set these via ioctls 4. The device must then be disconnected --> Kernel freeze On Ubuntu "3." is always guaranteed, if modemmanager is installed and the service is running Please contact me if you need additional information about how to reproduce this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-124-generic 4.15.0-124.127 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raven 2039 F pulseaudio CurrentDesktop: XFCE Date: Thu Nov 26 20:30:58 2020 EcryptfsInUse: Yes HibernationDevice: #RESUME=UUID=de4646dc-eb1a-4530-b6bc-df659b641728 RESUME=none InstallationDate: Installed on 2017-04-28 (1308 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: FUJITSU LIFEBOOK E736 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-124-generic root=/dev/mapper/ubuntu--vg-root ro "acpi_osi=!Windows 2012" RelatedPackageVersions: linux-restricted-modules-4.15.0-124-generic N/A linux-backports-modules-4.15.0-124-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-06-28 (517 days ago) dmi.bios.date: 12/20/2016 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.22 dmi.board.name: FJNB293 dmi.board.vendor: FUJITSU dmi.board.version: M4 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK E736 dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.22:bd12/20/2016:svnFUJITSU:pnLIFEBOOKE736:pvr10601115935:rvnFUJITSU:rnFJNB293:rvrM4:cvnFUJITSU:ct10:cvrLIFEBOOKE736: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E736 dmi.product.version: 10601115935 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905782] [NEW] kernel freeze on USB disconnect after failure to set rts/dts on USB VCP device
Public bug reported: When plugging in a USB device on Ubuntu 18.04 that offers a virtual modem/com port (typically /dev/ttyACM0) then the "modemmanager" service will try to configure this modem/serial port automatically without user interaction, setting dtr/rts parameters. However sometimes USB modem devices are used as a generic serial interface to hardware internals, without an actual serial line connected. Setting dtr/rts makes no sense in this context, and this feature might be unsupported. This, however, triggers a faulty code path in the linux kernel that on device disconnect causes a kworker process to freeze - blocking the CPU core it is running on indefinitely. This in turn has catastrophic effects on system stability. Some IO calls, that run on other cores, will work without problem, while those scheduled on the same core will never execute. Although no "OOPS" or "PANIC" is generated, the situation is dire, as the system typically can not be shutdown or rebooted, and during tests I ended up with file system corruption in a few cases that could not be fixed by a simple journal recovery To trigger this bug, several side-conditions need to be met: 1. A USB device needs to be plugged in that provides a virtual com port 2. The device must not support setting of DTR/RTS parameters 3. A program must try to set these via ioctls 4. The device must then be disconnected --> Kernel freeze On Ubuntu "3." is always guaranteed, if modemmanager is installed and the service is running Please contact me if you need additional information about how to reproduce this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-124-generic 4.15.0-124.127 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raven 2039 F pulseaudio CurrentDesktop: XFCE Date: Thu Nov 26 20:30:58 2020 EcryptfsInUse: Yes HibernationDevice: #RESUME=UUID=de4646dc-eb1a-4530-b6bc-df659b641728 RESUME=none InstallationDate: Installed on 2017-04-28 (1308 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: FUJITSU LIFEBOOK E736 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-124-generic root=/dev/mapper/ubuntu--vg-root ro "acpi_osi=!Windows 2012" RelatedPackageVersions: linux-restricted-modules-4.15.0-124-generic N/A linux-backports-modules-4.15.0-124-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-06-28 (517 days ago) dmi.bios.date: 12/20/2016 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.22 dmi.board.name: FJNB293 dmi.board.vendor: FUJITSU dmi.board.version: M4 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK E736 dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.22:bd12/20/2016:svnFUJITSU:pnLIFEBOOKE736:pvr10601115935:rvnFUJITSU:rnFJNB293:rvrM4:cvnFUJITSU:ct10:cvrLIFEBOOKE736: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E736 dmi.product.version: 10601115935 dmi.sys.vendor: FUJITSU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Kernel dmesg log of the freeze" https://bugs.launchpad.net/bugs/1905782/+attachment/5438421/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905782 Title: kernel freeze on USB disconnect after failure to set rts/dts on USB VCP device Status in linux package in Ubuntu: New Bug description: When plugging in a USB device on Ubuntu 18.04 that offers a virtual modem/com port (typically /dev/ttyACM0) then the "modemmanager" service will try to configure this modem/serial port automatically without user interaction, setting dtr/rts parameters. However sometimes USB modem devices are used as a generic serial interface to hardware internals, without an actual serial line connected. Setting dtr/rts makes no sense in this context, and this feature might be unsupported. This, however, triggers a faulty code path in the linux kernel that on device disconnect causes a kworker process to freeze - blocking the CPU core it is running on indefinitely. This in turn has catastrophic effects on system stability. Some IO calls, that run on other cores, will work without problem, while those scheduled on the same core will never execute. Although no "OOPS" or "PANIC" is generated, the situation is dire, as the system typically can not be shutdown or rebooted, and during tests I ended up with file system corruption in a few cases that could not be fixed by a simple journal recovery To trigger this bug, several side-conditions need
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: New Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903397] Re: Groovy 5.8 kernel hangs on boot on CPUs with eLLC
The kernel in -proposed solves the problem. Should I change the tag to 'verification-done-groovy'? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903397 Title: Groovy 5.8 kernel hangs on boot on CPUs with eLLC Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.8 package in Ubuntu: New Status in linux-hwe-5.8 source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Bug description: 5.8 kernel hangs on boot on my PC with Intel Core i7-5775C. Bug is already fixed upstream: https://gitlab.freedesktop.org/drm/intel/-/issues/2381 https://bugzilla.kernel.org/show_bug.cgi?id=208737 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.10-rc1=1664ffee760a5d98952318fdd9b198fae396d660 Please backport the fix. Thanks! [Impact] * Bug causes boot failure on common hardware. [Test Case] * Test kernel validated by submitter (see Comment #6). [Regression Potential] * Low: Simple cherry-pick from upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905757] [NEW] Display flickers when computer wakes up
Public bug reported: I am using a 144hz Refresh rate screen The screen flickers once it wakes up from sleep or it is woken up from Screen turn off due to inactivity The possible solution to stop the flickering is to set the refresh to 60 hz and then reverting to the 144hz refresh ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: soumyajyoti 2145 F pulseaudio /dev/snd/controlC0: soumyajyoti 2145 F pulseaudio /dev/snd/controlC1: soumyajyoti 2145 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 26 22:13:34 2020 InstallationDate: Installed on 2020-11-22 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506II_FA566II ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=80cc1579-96aa-4743-aef2-d67dbff067cb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506II.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506II dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.10 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506II.311:bd09/11/2020:br5.16:efr3.10:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506II_FA566II:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506II:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506II dmi.product.name: TUF Gaming FA506II_FA566II dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905757 Title: Display flickers when computer wakes up Status in linux package in Ubuntu: New Bug description: I am using a 144hz Refresh rate screen The screen flickers once it wakes up from sleep or it is woken up from Screen turn off due to inactivity The possible solution to stop the flickering is to set the refresh to 60 hz and then reverting to the 144hz refresh ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: soumyajyoti 2145 F pulseaudio /dev/snd/controlC0: soumyajyoti 2145 F pulseaudio /dev/snd/controlC1: soumyajyoti 2145 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 26 22:13:34 2020 InstallationDate: Installed on 2020-11-22 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506II_FA566II ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=80cc1579-96aa-4743-aef2-d67dbff067cb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506II.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506II dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.10 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506II.311:bd09/11/2020:br5.16:efr3.10:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506II_FA566II:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506II:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506II dmi.product.name: TUF Gaming FA506II_FA566II dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1900809] Re: [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to stable-v1.6
This bug was fixed in the package linux-firmware - 1.192 --- linux-firmware (1.192) hirsute; urgency=medium * [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to stable-v1.6 (LP: #1900809) - SAUCE: sof-firmware: update the sof-firmware to stable-v1.6 - SAUCE: sof-firmware: Replace duplicates with symbolic links -- Juerg Haefliger Thu, 26 Nov 2020 13:23:20 +0100 ** Changed in: linux-firmware (Ubuntu Hirsute) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1900809 Title: [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to stable-v1.6 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Groovy: Triaged Status in linux-firmware source package in Hirsute: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1900809 [Impact] Intel released the sof-firmware v1.6, and in our oem projects, the Dell TGL machines and the machines with soundwire audio need the new firmware, otherwise they will fail to load the firmware or the audio can't work well. [Fix] replace the old sof-firmware-v1.4.2 with sof-firmware-v1.6 [Test] Tested on the Dell cml/tgl soundwire machines, all audio functions worked well, and those audio functions didn't work with old firmware. Tested on Lenovo dimc machines, all audio functions worked as well as before. [Regression Potential] Intel tested the new firmware with the 5.8 and 5.9 kernel, but we need the new firmware to work with 5.4 and 5.6 kernel as well, so there is some possibility that the 5.4/5.6 kernel can't work well with the new sof-firmware. I have tested the new firmware with 5.4/5.6 kernel on some Lenovo machines, so far no issues were found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1900809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905770] Re: package linux-firmware 1.187.5 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905770 Title: package linux-firmware 1.187.5 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: Migration de UBUNTU 18.04.05 (LTS) vers UBUNTU 20.04.01 (LTS) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.5 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 AptOrdering: linux-firmware:amd64: Install xdg-utils:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ba033462280 F pulseaudio /dev/snd/controlC0: ba033462280 F pulseaudio CasperMD5CheckResult: skip Date: Thu Nov 26 13:16:19 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=bdfb5b60-2f66-45e6-a1fc-7c87d5f3867d InstallationDate: Installed on 2017-08-20 (1194 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=66854b36-6a3e-46f6-930d-2c9ca2f26faf ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware Title: package linux-firmware 1.187.5 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: Default string dmi.board.name: STRIX Z270E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd03/22/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXZ270EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905770] [NEW] package linux-firmware 1.187.5 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: Migration de UBUNTU 18.04.05 (LTS) vers UBUNTU 20.04.01 (LTS) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.5 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 AptOrdering: linux-firmware:amd64: Install xdg-utils:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ba033462280 F pulseaudio /dev/snd/controlC0: ba033462280 F pulseaudio CasperMD5CheckResult: skip Date: Thu Nov 26 13:16:19 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=bdfb5b60-2f66-45e6-a1fc-7c87d5f3867d InstallationDate: Installed on 2017-08-20 (1194 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=66854b36-6a3e-46f6-930d-2c9ca2f26faf ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware Title: package linux-firmware 1.187.5 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: Default string dmi.board.name: STRIX Z270E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd03/22/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXZ270EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-from-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905770 Title: package linux-firmware 1.187.5 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: Migration de UBUNTU 18.04.05 (LTS) vers UBUNTU 20.04.01 (LTS) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.5 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 AptOrdering: linux-firmware:amd64: Install xdg-utils:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ba033462280 F pulseaudio /dev/snd/controlC0: ba033462280 F pulseaudio CasperMD5CheckResult: skip Date: Thu Nov 26 13:16:19 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=bdfb5b60-2f66-45e6-a1fc-7c87d5f3867d InstallationDate: Installed on 2017-08-20 (1194 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=66854b36-6a3e-46f6-930d-2c9ca2f26faf ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware Title: package linux-firmware 1.187.5 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: Default string dmi.board.name: STRIX Z270E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC.
[Kernel-packages] [Bug 1842479] Re: timer_create will fail with invalid error code
** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842479 Title: timer_create will fail with invalid error code Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Bug description: [Impact] On some OpenPower systems, RTC does not support set_alarm, and timer_create(CLOCK_REALTIME_ALARM, ...) will fail with ENOTSUPP instead of EOPNOTSUPP. This will break some regression testing that expects the later value. [Test cases] Run LTP syscalls regression testing, which we do before releasing kernels. [Regression potential] This should not break any userspace, as none should be using/expecting ENOTSUPP for any call. In order to do so, they would have to go out of their way as it's not defined on libc headers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905757] 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/1905757 Title: Display flickers when computer wakes up Status in linux package in Ubuntu: Confirmed Bug description: I am using a 144hz Refresh rate screen The screen flickers once it wakes up from sleep or it is woken up from Screen turn off due to inactivity The possible solution to stop the flickering is to set the refresh to 60 hz and then reverting to the 144hz refresh ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: soumyajyoti 2145 F pulseaudio /dev/snd/controlC0: soumyajyoti 2145 F pulseaudio /dev/snd/controlC1: soumyajyoti 2145 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 26 22:13:34 2020 InstallationDate: Installed on 2020-11-22 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506II_FA566II ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=80cc1579-96aa-4743-aef2-d67dbff067cb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506II.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506II dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.10 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506II.311:bd09/11/2020:br5.16:efr3.10:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506II_FA566II:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506II:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506II dmi.product.name: TUF Gaming FA506II_FA566II dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900809] Please test proposed package
Hello Hui, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1900809 Title: [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to stable-v1.6 Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Groovy: Triaged Status in linux-firmware source package in Hirsute: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1900809 [Impact] Intel released the sof-firmware v1.6, and in our oem projects, the Dell TGL machines and the machines with soundwire audio need the new firmware, otherwise they will fail to load the firmware or the audio can't work well. [Fix] replace the old sof-firmware-v1.4.2 with sof-firmware-v1.6 [Test] Tested on the Dell cml/tgl soundwire machines, all audio functions worked well, and those audio functions didn't work with old firmware. Tested on Lenovo dimc machines, all audio functions worked as well as before. [Regression Potential] Intel tested the new firmware with the 5.8 and 5.9 kernel, but we need the new firmware to work with 5.4 and 5.6 kernel as well, so there is some possibility that the 5.4/5.6 kernel can't work well with the new sof-firmware. I have tested the new firmware with 5.4/5.6 kernel on some Lenovo machines, so far no issues were found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1900809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902195] Re: Intel RocketLake graphics support
Hello AceLan, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1902195 Title: Intel RocketLake graphics support Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] Intel RocketLake platform requires a new firmware for its graphics driver. [Fix] Cherry pick from linux-firmware 1b81373b i915: Add DMC firmware 2.02 for RKL Groovy has it already. [Verify] Verified on RKL platforms [Regression Potential] Low, it's a new firmware for a new platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1902195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905214] Please test proposed package
Hello Hui, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905214 Title: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Groovy: In Progress Status in linux-firmware source package in Hirsute: Fix Released Bug description: For H, it already has all patches, this SRU is not needed for H For G, only needs the 0005-xxx.patch and 0010-xxx.patch For F, needs all patches. [Impact] We found 2 issues: Bluetooth headset can't work in hsp/hfp mode, Both AX200 and AX201 have this issue (#1871794) Bluetooth will stop working randomly on the machines with AX200 (OEM bug). [Fix] Update the firmware to the latest version, the above 2 issues could be fixed. [Test] connect a bluetooth headset, after connecting, it is in A2DP mode by default, change it to hsp/hfp mode from gnome-sound-setting, play sound and record sound from headset, all work well. Keep the machine powered on and let it be idle for 1 day, check the bluetooth headset, still could work. [Regression Potential] I could make the Bluetooth function stop working on the machines with AX200 or AX201 module, like can't scan the BT devices, can't connect the BT devices or the BT devices can't work normally. But this possibility is very low, we have tested the SRU on a couple of lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900809] Re: [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to stable-v1.6
Hello Hui, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Focal) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1900809 Title: [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to stable-v1.6 Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Groovy: Triaged Status in linux-firmware source package in Hirsute: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1900809 [Impact] Intel released the sof-firmware v1.6, and in our oem projects, the Dell TGL machines and the machines with soundwire audio need the new firmware, otherwise they will fail to load the firmware or the audio can't work well. [Fix] replace the old sof-firmware-v1.4.2 with sof-firmware-v1.6 [Test] Tested on the Dell cml/tgl soundwire machines, all audio functions worked well, and those audio functions didn't work with old firmware. Tested on Lenovo dimc machines, all audio functions worked as well as before. [Regression Potential] Intel tested the new firmware with the 5.8 and 5.9 kernel, but we need the new firmware to work with 5.4 and 5.6 kernel as well, so there is some possibility that the 5.4/5.6 kernel can't work well with the new sof-firmware. I have tested the new firmware with 5.4/5.6 kernel on some Lenovo machines, so far no issues were found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1900809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905214] Re: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update
Hello Hui, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905214 Title: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Groovy: In Progress Status in linux-firmware source package in Hirsute: Fix Released Bug description: For H, it already has all patches, this SRU is not needed for H For G, only needs the 0005-xxx.patch and 0010-xxx.patch For F, needs all patches. [Impact] We found 2 issues: Bluetooth headset can't work in hsp/hfp mode, Both AX200 and AX201 have this issue (#1871794) Bluetooth will stop working randomly on the machines with AX200 (OEM bug). [Fix] Update the firmware to the latest version, the above 2 issues could be fixed. [Test] connect a bluetooth headset, after connecting, it is in A2DP mode by default, change it to hsp/hfp mode from gnome-sound-setting, play sound and record sound from headset, all work well. Keep the machine powered on and let it be idle for 1 day, check the bluetooth headset, still could work. [Regression Potential] I could make the Bluetooth function stop working on the machines with AX200 or AX201 module, like can't scan the BT devices, can't connect the BT devices or the BT devices can't work normally. But this possibility is very low, we have tested the SRU on a couple of lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894017] Re: Keyboard not working
chassis_type 31 is "Convertible", so we expect the intel-vbtn
SW_TABLET_MODE reporting to work there.
There was one other HP model which had a bit of a weird issue, this was
fixed by:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d823346876a970522ff9e4d2b323c9b734dcc4de
But that workaround got dropped when we switched to ignoring
SW_TABLET_MODE on all devices where the chassis_type is not 31 or 32,
since the model which needed that fix ("HP Pavilion 11 x360") uses a
chassis_type of 10, so that workaround was no longer needed.
So now it seems that we should not have dropped the workaround as
possibly more HP models need it. If you can build your own 5.9.10 kernel
with the linked workaround applied, and test it that would be great.
There should be docs somewhere on how to build an ubuntu kernel with
patches applied yourself. If you do not feel up to doing this yourself,
then please say so, then one of the Ubuntu devs should be able to
provide a test kernel with the patch added for you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894017
Title:
Keyboard not working
Status in linux package in Ubuntu:
Confirmed
Bug description:
The laptop keyboard doesn't work at login or in the de. If I
ctrl+alt+F3 from an external usb keyboard to a terminal the laptop
keyboard works. An external usb keyboard works everywhere. The
laptop's keyboard does work everywhere with the previous kernel
5.4.0.42.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49
ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55
Uname: Linux 5.4.0-45-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Thu Sep 3 03:09:49 2020
InstallationDate: Installed on 2019-08-07 (392 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency
root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-5.4.0-45-lowlatency N/A
linux-backports-modules-5.4.0-45-lowlatency N/A
linux-firmware 1.187.3
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago)
dmi.bios.date: 03/13/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.30
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2209
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.57
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
dmi.product.name: HP Pavilion 11 x360 PC
dmi.product.sku: M0B61EA#ACQ
dmi.product.version: 097710405F00010420180
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905742] Re: Add support for AMD Sienna Cichlid (RX6000)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905742 Title: Add support for AMD Sienna Cichlid (RX6000) Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: Confirmed Status in linux-firmware source package in Groovy: Confirmed Bug description: [Impact] RX6000 series gfx cards do not work on Ubuntu at the moment. They need new firmware recently pushed upstream. [Test case] Install the updates, see that the desktop session is running with the native driver. [Where things could go wrong] ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904848] Re: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module
** Changed in: linux (Ubuntu Bionic) 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/1904848 Title: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] unloading ib_ipoib causes a call trace to be logged in kernel buffer. bisecting the bionic kernel reveals that this issue was discovered by 616e695435e3 workqueue: Try to catch flush_work() without INIT_WORK() in version 4.15.0-59.66 [test case] # modprobe ib_ipoib # modprobe ib_ipoib -r # dmesg [ 306.277717] [ cut here ] [ 306.277738] WARNING: CPU: 10 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.277739] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp llc binfmt_misc intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp rpcrdma rdma_ucm ib_umad ib_uverbs coretemp ib_iser rdma_cm kvm_intel kvm iw_cm irqbypass ib_ipoib(-) libiscsi scsi_transport_iscsi ib_cm joydev input_leds crct10dif_pclmul crc32_pclmul mgag200 ttm drm_kms_helper drm hpilo ghash_clmulni_intel pcbc i2c_algo_bit ipmi_ssif fb_sys_fops syscopyarea sysfillrect sysimgblt aesni_intel aes_x86_64 crypto_simd ioatdma glue_helper shpchp cryptd dca intel_cstate intel_rapl_perf [ 306.277790] serio_raw acpi_power_meter lpc_ich mac_hid ipmi_si ipmi_devintf ipmi_msghandler nfsd auth_rpcgss nfs_acl lockd grace sunrpc sch_fq_codel ip_tables x_tables autofs4 mlx5_ib mlx4_ib mlx4_en ib_core hid_generic psmouse mlx5_core usbhid hid pata_acpi hpsa tg3 mlxfw mlx4_core scsi_transport_sas ptp pps_core devlink [ 306.277817] CPU: 10 PID: 2148 Comm: modprobe Not tainted 4.15.0-124-generic #127-Ubuntu [ 306.277818] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 07/01/2015 [ 306.277823] RIP: 0010:__flush_work+0x1f8/0x210 [ 306.277825] RSP: 0018:bdeb47ecfcd8 EFLAGS: 00010286 [ 306.277827] RAX: 0024 RBX: 993a5c3d8ec8 RCX: 0006 [ 306.277829] RDX: RSI: 99429ef16498 RDI: 99429ef16490 [ 306.277830] RBP: bdeb47ecfd48 R08: 050d R09: 0004 [ 306.277832] R10: e263a058c1c0 R11: 0001 R12: 993a5c3d8ec8 [ 306.277833] R13: 0001 R14: bdeb47ecfd78 R15: b00a9800 [ 306.277835] FS: 7fa1124a9540() GS:99429ef0() knlGS: [ 306.277837] CS: 0010 DS: ES: CR0: 80050033 [ 306.277839] CR2: 55b1c5007bb0 CR3: 000fcf36c002 CR4: 001606e0 [ 306.277840] Call Trace: [ 306.277850] __cancel_work_timer+0x136/0x1b0 [ 306.277881] ? mlx5_core_destroy_qp+0x99/0xd0 [mlx5_core] [ 306.277886] cancel_delayed_work_sync+0x13/0x20 [ 306.277909] mlx5e_detach_netdev+0x83/0x90 [mlx5_core] [ 306.277931] mlx5_rdma_netdev_free+0x30/0x80 [mlx5_core] [ 306.277941] mlx5_ib_free_rdma_netdev+0xe/0x10 [mlx5_ib] [ 306.277948] ipoib_remove_one+0xe4/0x180 [ib_ipoib] [ 306.277965] ib_unregister_client+0x171/0x1e0 [ib_core] [ 306.277972] ipoib_cleanup_module+0x15/0x2f [ib_ipoib] [ 306.277978] SyS_delete_module+0x1ab/0x2d0 [ 306.277983] do_syscall_64+0x73/0x130 [ 306.277989] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 306.277992] RIP: 0033:0x7fa111fc1047 [ 306.277993] RSP: 002b:7ffc0db32298 EFLAGS: 0206 ORIG_RAX: 00b0 [ 306.277996] RAX: ffda RBX: 5614be46cca0 RCX: 7fa111fc1047 [ 306.277997] RDX: RSI: 0800 RDI: 5614be46cd08 [ 306.277999] RBP: 5614be46cca0 R08: 7ffc0db31241 R09: [ 306.278000] R10: 7fa11203dc40 R11: 0206 R12: 5614be46cd08 [ 306.278002] R13: 0001 R14: 5614be46cd08 R15: 7ffc0db33680 [ 306.278004] Code: 24 03 80 c9 f0 e9 5b ff ff ff 48 c7 c7 18 50 0b b1 e8 ed 66 04 00 0f 0b 31 c0 e9 75 ff ff ff 48 c7 c7 18 50 0b b1 e8 d8 66 04 00 <0f> 0b 31 c0 e9 60 ff ff ff e8 5a 35 fe ff 66 2e 0f 1f 84 00 00 [ 306.278035] ---[ end trace 652f7759937172a2 ]--- [ 306.646061] [ cut here ] [ 306.646077] WARNING: CPU: 6 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.646078] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack
[Kernel-packages] [Bug 1886859] Re: memory is leaked when tasks are moved to net_prio
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1886859 Title: memory is leaked when tasks are moved to net_prio Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] In some container scenarios, there will be a memory leak, leading to OOM. [Test case] Run the following: while true ; do mkdir net_prio/a unified/a ; bash -c 'echo $$ > unified/a/cgroup.procs ; echo $$ > net_prio/a/tasks ; ping -c 1 localhost > /dev/null' ; rmdir net_prio/a unified/a ; done Or the attached program cgroup_leak.c, which is faster. A leak would be produced without the fix, while there should be no constant leak with the fix applied. [Potential regression] This patch has also caused breakage with BPF cgroup in the past, when racing with its disabling, when one attachs a process to netprio cgroup. Similar breakage could happen. - When net_prio is used without setting ifpriomap and BFP cgroup is used, memory may be leaked. This was fixed by upstream commit 090e28b229af92dc5b40786ca673999d59e73056, but it had to be reverted to fix LP #1886668. When a real fix for this cgroup BFP crash lands, this patch should be reinstated. Cascardo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886859/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905620] Re: please promote modules from extra to modules for HiFive Unleashed
** Changed in: linux-riscv (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-riscv (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1905620 Title: please promote modules from extra to modules for HiFive Unleashed Status in linux-riscv package in Ubuntu: Triaged Status in linux-riscv source package in Focal: Fix Committed Status in linux-riscv source package in Groovy: Fix Committed Status in linux-riscv source package in Hirsute: Triaged Bug description: please promote modules from extra to modules for HiFive Unleashed The following modules are used by the HiFive Unleashed board from extra Please install them in modules. linux-modules-extra-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/net/phy/mscc.ko linux-modules-extra-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/net/ethernet/cadence/macb.ko linux-modules-extra-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/i2c/busses/i2c-ocores.ko To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1905620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905742] Re: Add support for AMD Sienna Cichlid (RX6000)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu Groovy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905742 Title: Add support for AMD Sienna Cichlid (RX6000) Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: Confirmed Status in linux-firmware source package in Groovy: Confirmed Bug description: [Impact] RX6000 series gfx cards do not work on Ubuntu at the moment. They need new firmware recently pushed upstream. [Test case] Install the updates, see that the desktop session is running with the native driver. [Where things could go wrong] ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905742] Re: Add support for AMD Sienna Cichlid (RX6000)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905742 Title: Add support for AMD Sienna Cichlid (RX6000) Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: Confirmed Status in linux-firmware source package in Groovy: Confirmed Bug description: [Impact] RX6000 series gfx cards do not work on Ubuntu at the moment. They need new firmware recently pushed upstream. [Test case] Install the updates, see that the desktop session is running with the native driver. [Where things could go wrong] ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905618] Re: Focal update: v5.4.78 upstream stable release
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1905618 Title: Focal update: v5.4.78 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: 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.78 upstream stable release from git://git.kernel.org/ drm/i915/gem: Flush coherency domains on first set-domain-ioctl time: Prevent undefined behaviour in timespec64_to_ns() nbd: don't update block size after device is started KVM: arm64: Force PTE mapping on fault resulting in a device mapping PCI: qcom: Make sure PCIe is reset before init for rev 2.1.0 usb: dwc3: gadget: Continue to process pending requests usb: dwc3: gadget: Reclaim extra TRBs after request completion btrfs: tracepoints: output proper root owner for trace_find_free_extent() btrfs: sysfs: init devices outside of the chunk_mutex btrfs: reschedule when cloning lots of extents ASoC: Intel: kbl_rt5663_max98927: Fix kabylake_ssp_fixup function genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY hv_balloon: disable warning when floor reached net: xfrm: fix a race condition during allocing spi ASoC: codecs: wcd9335: Set digital gain range correctly xfs: set xefi_discard when creating a deferred agfl free log intent item netfilter: use actual socket sk rather than skb sk when routing harder netfilter: nf_tables: missing validation from the abort path netfilter: ipset: Update byte and packet counters regardless of whether they match powerpc/eeh_cache: Fix a possible debugfs deadlock perf trace: Fix segfault when trying to trace events by cgroup perf tools: Add missing swap for ino_generation ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link() iommu/vt-d: Fix a bug for PDP check in prq_event_thread afs: Fix warning due to unadvanced marshalling pointer can: rx-offload: don't call kfree_skb() from IRQ context can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ context can: dev: __can_get_echo_skb(): fix real payload length return value for RTR frames can: can_create_echo_skb(): fix echo skb generation: always use skb_clone() can: j1939: swap addr and pgn in the send example can: j1939: j1939_sk_bind(): return failure if netdev is down can: ti_hecc: ti_hecc_probe(): add missed clk_disable_unprepare() in error path can: xilinx_can: handle failure cases of pm_runtime_get_sync can: peak_usb: add range checking in decode operations can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback is on can: flexcan: remove FLEXCAN_QUIRK_DISABLE_MECR quirk for LS1021A can: flexcan: flexcan_remove(): disable wakeup completely xfs: flush new eof page on truncate to avoid post-eof corruption xfs: fix scrub flagging rtinherit even if there is no rt device tpm: efi: Don't create binary_bios_measurements file for an empty log random32: make prandom_u32() output unpredictable KVM: arm64: ARM_SMCCC_ARCH_WORKAROUND_1 doesn't return SMCCC_RET_NOT_REQUIRED KVM: x86: don't expose MSR_IA32_UMWAIT_CONTROL unconditionally ath9k_htc: Use appropriate rs_datalen type ASoC: qcom: sdm845: set driver name correctly ASoC: cs42l51: manage mclk shutdown delay usb: dwc3: pci: add support for the Intel Alder Lake-S opp: Reduce the size of critical section in _opp_table_kref_release() usb: gadget: goku_udc: fix potential crashes in probe selftests/ftrace: check for do_sys_openat2 in user-memory test selftests: pidfd: fix compilation errors due to wait.h ALSA: hda: Separate runtime and system suspend ALSA: hda: Reinstate runtime_allow() for all hda controllers gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free gfs2: Add missing truncate_inode_pages_final for sd_aspace gfs2: check for live vs. read-only file system in gfs2_fitrim scsi: hpsa: Fix memory leak in hpsa_init_one() drm/amdgpu: perform srbm soft reset always on SDMA resume drm/amd/pm: perform SMC reset on suspend/hibernation drm/amd/pm: do not use ixFEATURE_STATUS for checking smc running mac80211: fix use of skb payload instead of header cfg80211: initialize wdev data earlier cfg80211: regulatory: Fix inconsistent format argument tracing: Fix the checking of stackidx in
[Kernel-packages] [Bug 1905742] Re: Add support for AMD Sienna Cichlid (RX6000)
** Description changed: [Impact] - RX6000 does not currently work on Ubuntu. It needs new firmware - currently missing from the package. + RX6000 series gfx cards do not work on Ubuntu at the moment. They need + new firmware recently pushed upstream. [Test case] Install the updates, see that the desktop session is running with the native driver. [Where things could go wrong] ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905742 Title: Add support for AMD Sienna Cichlid (RX6000) Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: Confirmed Status in linux-firmware source package in Groovy: Confirmed Bug description: [Impact] RX6000 series gfx cards do not work on Ubuntu at the moment. They need new firmware recently pushed upstream. [Test case] Install the updates, see that the desktop session is running with the native driver. [Where things could go wrong] ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905742] Re: Add support for AMD Sienna Cichlid (RX6000)
commit 54c797a694d3830ef93f349ec25e1d96d4b88102 Author: Alex Deucher Date: Tue Nov 17 14:32:15 2020 -0500 amdgpu: add sienna cichlid firmware for 20.45 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905742 Title: Add support for AMD Sienna Cichlid (RX6000) Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Groovy: New Bug description: [Impact] RX6000 does not currently work on Ubuntu. It needs new firmware currently missing from the package. [Test case] Install the updates, see that the desktop session is running with the native driver. [Where things could go wrong] ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900360] Re: [Lenovo ThinkPad X230] Input freeze, kernel crash in input_handle_event
Changing dm from lightdm to gdm3 has stopped the crashes for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1900360 Title: [Lenovo ThinkPad X230] Input freeze, kernel crash in input_handle_event Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I think the problem arises from use of a USB switch. However it does not necessarily happen when engaging or disengaging USB hub. Inbuilt trackpad allows use of cursor during freeze, but not usb attatched mouse. aside from that nothing gets a response on the display. Using a Thinkpad X230 kern.log includes crash ``` Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.457323] usb 3-3.1: USB disconnect, device number 4 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.457328] usb 3-3.1.1: USB disconnect, device number 5 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.504690] usb 3-3.1.4: USB disconnect, device number 8 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663393] BUG: unable to handle page fault for address: 1c18 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663396] #PF: supervisor read access in kernel mode Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663398] #PF: error_code(0x) - not-present page Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663399] PGD 0 P4D 0 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663402] Oops: [#1] SMP PTI Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663405] CPU: 2 PID: 25 Comm: kworker/2:0 Not tainted 5.4.0-51-generic #56-Ubuntu Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663406] Hardware name: LENOVO 2324AS7/2324AS7, BIOS G2ETB2WW (2.72 ) 04/11/2018 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663412] Workqueue: usb_hub_wq hub_event Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663417] RIP: 0010:holtek_kbd_input_event+0x4d/0x80 [hid_holtek_kbd] Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663419] Code: 80 10 19 00 00 48 8b 78 40 48 81 ef a0 00 00 00 e8 78 b4 62 d5 48 85 c0 74 2f 48 8b 80 a8 00 00 00 44 89 f1 44 89 ea 44 89 e6 <48> 8b 80 18 1c 00 00 48 8b 78 18 48 8b 87 e0 01 00 00 e8 4c 5c c4 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663420] RSP: 0018:b8018014b7b8 EFLAGS: 00010086 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663422] RAX: RBX: 0011 RCX: Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663424] RDX: RSI: 0011 RDI: 9ea909877000 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663425] RBP: b8018014b7d0 R08: 9ea9138cd800 R09: 0004 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663426] R10: 9ea8c3f2cd9d R11: 9ea9c3f2cd97 R12: 0011 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663427] R13: R14: R15: 0003 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663429] FS: () GS:9ea91648() knlGS: Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663430] CS: 0010 DS: ES: CR0: 80050033 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663431] CR2: 1c18 CR3: 00013580a001 CR4: 001606e0 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663432] Call Trace: Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663439] input_handle_event+0x7f/0x610 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663441] input_inject_event+0x82/0x84 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663445] input_leds_brightness_set+0x27/0x30 [input_leds] Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663449] led_set_brightness_nopm+0x17/0x40 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663450] led_set_brightness+0x28/0x60 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663452] led_trigger_set+0x12c/0x2a0 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663455] ? synchronize_rcu+0x67/0x70 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663457] ? __call_rcu+0x1d0/0x1d0 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663459] led_classdev_unregister.part.0+0x32/0xd0 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663460] led_classdev_unregister+0x1f/0x30 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663462] input_leds_disconnect+0x39/0x70 [input_leds] Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663464] __input_unregister_device+0xb5/0x150 Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.663465]
[Kernel-packages] [Bug 1905614] Re: Focal update: v5.4.77 upstream stable release
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1905614 Title: Focal update: v5.4.77 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: 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.77 upstream stable release from git://git.kernel.org/ Note: This patch set is empty for focal because v5.4.77 contained only one patch: 19f6d91bdad4 powercap: restrict energy meter to root access The contents of which are already present here via: 33837d9fa5b9 powercap: make attributes only readable by root ^^^ (note also that this should have been "UBUNTU: SAUCE:") Linux 5.4.76 UBUNTU: upstream stable to v5.4.76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905612] Re: Focal update: v5.4.76 upstream stable release
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1905612 Title: Focal update: v5.4.76 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: 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.76 upstream stable release from git://git.kernel.org/ drm/i915: Break up error capture compression loops with cond_resched() drm/i915/gt: Delay execlist processing for tgl drm/i915: Drop runtime-pm assert from vgpu io accessors ASoC: Intel: Skylake: Add alternative topology binary name UBUNTU: update dkms package versions linkage: Introduce new macros for assembler symbols arm64: asm: Add new-style position independent function annotations arm64: lib: Use modern annotations for assembly functions arm64: Change .weak to SYM_FUNC_START_WEAK_PI for arch/arm64/lib/mem*.S tipc: fix use-after-free in tipc_bcast_get_mode ptrace: fix task_join_group_stop() for the case when current is traced cadence: force nonlinear buffers to be cloned chelsio/chtls: fix memory leaks caused by a race chelsio/chtls: fix always leaking ctrl_skb gianfar: Replace skb_realloc_headroom with skb_cow_head for PTP gianfar: Account for Tx PTP timestamp in the skb headroom ionic: check port ptr before use ip_tunnel: fix over-mtu packet send fail without TUNNEL_DONT_FRAGMENT flags net: usb: qmi_wwan: add Telit LE910Cx 0x1230 composition powerpc/vnic: Extend "failover pending" window sctp: Fix COMM_LOST/CANT_STR_ASSOC err reporting on big-endian platforms sfp: Fix error handing in sfp_probe() Fonts: Replace discarded const qualifier ALSA: hda/realtek - Fixed HP headset Mic can't be detected ALSA: hda/realtek - Enable headphone for ASUS TM420 ALSA: usb-audio: Add implicit feedback quirk for Zoom UAC-2 ALSA: usb-audio: add usb vendor id as DSD-capable for Khadas devices ALSA: usb-audio: Add implicit feedback quirk for Qu-16 ALSA: usb-audio: Add implicit feedback quirk for MODX mm: mempolicy: fix potential pte_unmap_unlock pte error lib/crc32test: remove extra local_irq_disable/enable kthread_worker: prevent queuing delayed work from timer_fn when it is being canceled mm: always have io_remap_pfn_range() set pgprot_decrypted() gfs2: Wake up when sd_glock_disposal becomes zero ring-buffer: Fix recursion protection transitions between interrupt context mtd: spi-nor: Don't copy self-pointing struct around ftrace: Fix recursion check for NMI test ftrace: Handle tracing when switching between context regulator: defer probe when trying to get voltage from unresolved supply spi: bcm2835: fix gpio cs level inversion tracing: Fix out of bounds write in get_trace_buf futex: Handle transient "ownerless" rtmutex state correctly ARM: dts: sun4i-a10: fix cpu_alert temperature arm64: dts: meson: add missing g12 rng clock x86/kexec: Use up-to-dated screen_info copy to fill boot params of: Fix reserved-memory overlap detection drm/sun4i: frontend: Rework a bit the phase data drm/sun4i: frontend: Reuse the ch0 phase for RGB formats drm/sun4i: frontend: Fix the scaler phase on A33 blk-cgroup: Fix memleak on error path blk-cgroup: Pre-allocate tree node on blkg_conf_prep scsi: core: Don't start concurrent async scan on same host drm/amdgpu: add DID for navi10 blockchain SKU scsi: ibmvscsi: Fix potential race after loss of transport vsock: use ns_capable_noaudit() on socket create nvme-rdma: handle unexpected nvme completion data length nvmet: fix a NULL pointer dereference when tracing the flush command drm/vc4: drv: Add error handding for bind ACPI: NFIT: Fix comparison to '-ENXIO' usb: cdns3: gadget: suspicious implicit sign extension drm/nouveau/nouveau: fix the start/end range for migration drm/nouveau/gem: fix "refcount_t: underflow; use-after-free" arm64/smp: Move rcu_cpu_starting() earlier vt: Disable KD_FONT_OP_COPY fork: fix copy_process(CLONE_PARENT) race with the exiting ->real_parent s390/pkey: fix paes selftest failure with paes and pkey static build serial: 8250_mtk: Fix uart_get_baud_rate warning serial: txx9: add missing platform_driver_unregister() on error in serial_txx9_init USB: serial: cyberjack: fix write-URB completion race USB: serial: option: add Quectel EC200T module support USB: serial: option: add
[Kernel-packages] [Bug 1905742] Re: Add support for AMD Sienna Cichlid (RX6000)
For the kernel it needs 5.9 or up (oem-5.10 will do), Mesa needs to be on 20.2.x or newer (currently in groovy and in focal-proposed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905742 Title: Add support for AMD Sienna Cichlid (RX6000) Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Groovy: New Bug description: [Impact] RX6000 does not currently work on Ubuntu. It needs new firmware currently missing from the package. [Test case] Install the updates, see that the desktop session is running with the native driver. [Where things could go wrong] ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905742] [NEW] Add support for AMD Sienna Cichlid (RX6000)
Public bug reported: [Impact] RX6000 does not currently work on Ubuntu. It needs new firmware currently missing from the package. [Test case] Install the updates, see that the desktop session is running with the native driver. [Where things could go wrong] ... ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Groovy) Importance: Undecided Status: New ** Description changed: [Impact] - RX6000 does not currently work on Ubuntu. + RX6000 does not currently work on Ubuntu. It needs new firmware + currently missing from the package. [Test case] Install the updates, see that the desktop session is running with the native driver. [Where things could go wrong] ... ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1905742 Title: Add support for AMD Sienna Cichlid (RX6000) Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Groovy: New Bug description: [Impact] RX6000 does not currently work on Ubuntu. It needs new firmware currently missing from the package. [Test case] Install the updates, see that the desktop session is running with the native driver. [Where things could go wrong] ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900809] Re: [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to stable-v1.6
** Changed in: linux-firmware (Ubuntu Hirsute) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1900809 Title: [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to stable-v1.6 Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Focal: Triaged Status in linux-firmware source package in Groovy: Triaged Status in linux-firmware source package in Hirsute: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1900809 [Impact] Intel released the sof-firmware v1.6, and in our oem projects, the Dell TGL machines and the machines with soundwire audio need the new firmware, otherwise they will fail to load the firmware or the audio can't work well. [Fix] replace the old sof-firmware-v1.4.2 with sof-firmware-v1.6 [Test] Tested on the Dell cml/tgl soundwire machines, all audio functions worked well, and those audio functions didn't work with old firmware. Tested on Lenovo dimc machines, all audio functions worked as well as before. [Regression Potential] Intel tested the new firmware with the 5.8 and 5.9 kernel, but we need the new firmware to work with 5.4 and 5.6 kernel as well, so there is some possibility that the 5.4/5.6 kernel can't work well with the new sof-firmware. I have tested the new firmware with 5.4/5.6 kernel on some Lenovo machines, so far no issues were found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1900809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903293] Re: Avoid double newline when running insertchanges
This change affects purely the generation of changelogs, so there is nothing a user could verify. ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-groovy verification-needed-xenial ** Tags added: verification-done-bionic verification-done-focal verification-done-groovy verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903293 Title: Avoid double newline when running insertchanges Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: In Progress Bug description: [Impact] When preparing derivative kernels and inserting master kernel changes, if the derivative has not changes on its own, we end up with two empty lines, which is caught up by verify-release-ready. [Test case] Run cranky-close with derivative changes and no derivative changes. [Regression Potential] We could break changelogs, or the kernel preparation altogether. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
I cannot yet explain this, but after bisecting the config, I can repro this with pseries_le_defconfig + CONFIG_RCU_SCALE_TEST=m That's weird to me, and I'll continue to investigate. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: Canonical requests to test the secure boot for the 5.10 kernel but kernel fails to boot with secure boot disabled. The 5.10 kernel can be found in: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap They can be installed by installing the linux-generic-wip package with this PPA enabled. As usual, they are only signed using a key specific to that PPA. This key can be retrieved from the signing tarballs for the kernels, e.g.: http://ppa.launchpad.net/canonical-kernel- team/bootstrap/ubuntu/dists/hirsute/main/signed/linux-5.10-ppc64el/5.10.0-2.3/signed.tar.gz Our tester installed the 5.10 kernel via aptitude. If booting directly from the bootmenu, it stucks at: "kexec_core: Starting new kernel" If booting recovery kernel for 5.10.0, it proceeds farther and after kexec_core, it failed at: " [0.029830] LSM: Security Framework initializing [0.029916] Yama: b " Two attempts with a different scenario; running with 5.8 kernel and boot via commandline for 5.10: kexec -l /boot/vmlinux-5.10.0-0-generic --initrd=/boot/initrd.img-5.10.0-0-generic --append="root=UUID=49d000cb-dba2-4d70-809e-38f2b31d0f09 ro quiet splash" kexec -e Both attempts also failed while rebooting, once with the same error as the error from booting with bootmenu; the other failure occurred a lot earlier. Wondering what new CONFIGs and/or features for the 5.10 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905728] 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 1905728 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/1905728 Title: Found insecure W+X mapping at address on Groovy RISCV Status in linux package in Ubuntu: Incomplete Bug description: Issue found on 5.8.0-10-generic riscv Message reported on boot. [ 13.483103] [ cut here ] [ 13.483711] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 13.484542] WARNING: CPU: 5 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 13.485175] Modules linked in: [ 13.485606] CPU: 5 PID: 1 Comm: swapper/0 Not tainted 5.8.0-10-generic #12-Ubuntu [ 13.486091] epc: ffe000208f18 ra : ffe000208f18 sp : ffe1f5bfbb30 [ 13.486471] gp : ffe001728ee0 tp : ffe1f5bf5080 t0 : ffe00173ed88 [ 13.486850] t1 : ffe00173ed20 t2 : 0001fecbe000 s0 : ffe1f5bfbb80 [ 13.487250] s1 : ffe1f5bfbe10 a0 : 0053 a1 : 0020 [ 13.487633] a2 : ffe1f5bfb870 a3 : a4 : ffe0016200f8 [ 13.488040] a5 : ffe0016200f8 a6 : 00b5 a7 : ffe0006f2806 [ 13.488421] s2 : ffdff8001000 s3 : s4 : 0004 [ 13.488800] s5 : s6 : s7 : ffe1f5bfbd20 [ 13.489322] s8 : ffdff8001000 s9 : ffe00172a148 s10: ffdff8002000 [ 13.489738] s11: ffe000c16e20 t3 : 0003cec0 t4 : 0003cec0 [ 13.490119] t5 : t6 : ffe001739462 [ 13.490406] status: 0120 badaddr: cause: 0003 [ 13.490849] ---[ end trace 607c551edff1ef12 ]--- Please find attachment for the boot dmesg log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905728] Re: Found insecure W+X mapping at address on Groovy RISCV
** Attachment added: "riscv-groovy-dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905728/+attachment/5438245/+files/riscv-groovy-dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905728 Title: Found insecure W+X mapping at address on Groovy RISCV Status in linux package in Ubuntu: New Bug description: Issue found on 5.8.0-10-generic riscv Message reported on boot. [ 13.483103] [ cut here ] [ 13.483711] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 13.484542] WARNING: CPU: 5 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 13.485175] Modules linked in: [ 13.485606] CPU: 5 PID: 1 Comm: swapper/0 Not tainted 5.8.0-10-generic #12-Ubuntu [ 13.486091] epc: ffe000208f18 ra : ffe000208f18 sp : ffe1f5bfbb30 [ 13.486471] gp : ffe001728ee0 tp : ffe1f5bf5080 t0 : ffe00173ed88 [ 13.486850] t1 : ffe00173ed20 t2 : 0001fecbe000 s0 : ffe1f5bfbb80 [ 13.487250] s1 : ffe1f5bfbe10 a0 : 0053 a1 : 0020 [ 13.487633] a2 : ffe1f5bfb870 a3 : a4 : ffe0016200f8 [ 13.488040] a5 : ffe0016200f8 a6 : 00b5 a7 : ffe0006f2806 [ 13.488421] s2 : ffdff8001000 s3 : s4 : 0004 [ 13.488800] s5 : s6 : s7 : ffe1f5bfbd20 [ 13.489322] s8 : ffdff8001000 s9 : ffe00172a148 s10: ffdff8002000 [ 13.489738] s11: ffe000c16e20 t3 : 0003cec0 t4 : 0003cec0 [ 13.490119] t5 : t6 : ffe001739462 [ 13.490406] status: 0120 badaddr: cause: 0003 [ 13.490849] ---[ end trace 607c551edff1ef12 ]--- Please find attachment for the boot dmesg log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905728] [NEW] Found insecure W+X mapping at address on Groovy RISCV
Public bug reported: Issue found on 5.8.0-10-generic riscv Message reported on boot. [ 13.483103] [ cut here ] [ 13.483711] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 13.484542] WARNING: CPU: 5 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 13.485175] Modules linked in: [ 13.485606] CPU: 5 PID: 1 Comm: swapper/0 Not tainted 5.8.0-10-generic #12-Ubuntu [ 13.486091] epc: ffe000208f18 ra : ffe000208f18 sp : ffe1f5bfbb30 [ 13.486471] gp : ffe001728ee0 tp : ffe1f5bf5080 t0 : ffe00173ed88 [ 13.486850] t1 : ffe00173ed20 t2 : 0001fecbe000 s0 : ffe1f5bfbb80 [ 13.487250] s1 : ffe1f5bfbe10 a0 : 0053 a1 : 0020 [ 13.487633] a2 : ffe1f5bfb870 a3 : a4 : ffe0016200f8 [ 13.488040] a5 : ffe0016200f8 a6 : 00b5 a7 : ffe0006f2806 [ 13.488421] s2 : ffdff8001000 s3 : s4 : 0004 [ 13.488800] s5 : s6 : s7 : ffe1f5bfbd20 [ 13.489322] s8 : ffdff8001000 s9 : ffe00172a148 s10: ffdff8002000 [ 13.489738] s11: ffe000c16e20 t3 : 0003cec0 t4 : 0003cec0 [ 13.490119] t5 : t6 : ffe001739462 [ 13.490406] status: 0120 badaddr: cause: 0003 [ 13.490849] ---[ end trace 607c551edff1ef12 ]--- Please find attachment for the boot dmesg log. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 5.8 groovy ** Tags added: groovy ** Tags added: 5.8 ** Description changed: Issue found on 5.8.0-10-generic riscv + + Message reported on boot. [ 13.483103] [ cut here ] [ 13.483711] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 13.484542] WARNING: CPU: 5 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 13.485175] Modules linked in: [ 13.485606] CPU: 5 PID: 1 Comm: swapper/0 Not tainted 5.8.0-10-generic #12-Ubuntu [ 13.486091] epc: ffe000208f18 ra : ffe000208f18 sp : ffe1f5bfbb30 [ 13.486471] gp : ffe001728ee0 tp : ffe1f5bf5080 t0 : ffe00173ed88 [ 13.486850] t1 : ffe00173ed20 t2 : 0001fecbe000 s0 : ffe1f5bfbb80 [ 13.487250] s1 : ffe1f5bfbe10 a0 : 0053 a1 : 0020 [ 13.487633] a2 : ffe1f5bfb870 a3 : a4 : ffe0016200f8 [ 13.488040] a5 : ffe0016200f8 a6 : 00b5 a7 : ffe0006f2806 [ 13.488421] s2 : ffdff8001000 s3 : s4 : 0004 [ 13.488800] s5 : s6 : s7 : ffe1f5bfbd20 [ 13.489322] s8 : ffdff8001000 s9 : ffe00172a148 s10: ffdff8002000 [ 13.489738] s11: ffe000c16e20 t3 : 0003cec0 t4 : 0003cec0 [ 13.490119] t5 : t6 : ffe001739462 [ 13.490406] status: 0120 badaddr: cause: 0003 [ 13.490849] ---[ end trace 607c551edff1ef12 ]--- + + Please find attachment for the boot dmesg log. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905728 Title: Found insecure W+X mapping at address on Groovy RISCV Status in linux package in Ubuntu: New Bug description: Issue found on 5.8.0-10-generic riscv Message reported on boot. [ 13.483103] [ cut here ] [ 13.483711] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 13.484542] WARNING: CPU: 5 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 13.485175] Modules linked in: [ 13.485606] CPU: 5 PID: 1 Comm: swapper/0 Not tainted 5.8.0-10-generic #12-Ubuntu [ 13.486091] epc: ffe000208f18 ra : ffe000208f18 sp : ffe1f5bfbb30 [ 13.486471] gp : ffe001728ee0 tp : ffe1f5bf5080 t0 : ffe00173ed88 [ 13.486850] t1 : ffe00173ed20 t2 : 0001fecbe000 s0 : ffe1f5bfbb80 [ 13.487250] s1 : ffe1f5bfbe10 a0 : 0053 a1 : 0020 [ 13.487633] a2 : ffe1f5bfb870 a3 : a4 : ffe0016200f8 [ 13.488040] a5 : ffe0016200f8 a6 : 00b5 a7 : ffe0006f2806 [ 13.488421] s2 : ffdff8001000 s3 : s4 : 0004 [ 13.488800] s5 : s6 : s7 : ffe1f5bfbd20 [ 13.489322] s8 : ffdff8001000 s9 : ffe00172a148 s10: ffdff8002000 [ 13.489738] s11: ffe000c16e20 t3 : 0003cec0 t4 : 0003cec0 [ 13.490119] t5 : t6 : ffe001739462 [ 13.490406] status: 0120 badaddr: cause: 0003 [
[Kernel-packages] [Bug 1905469] 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 1905469 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: groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905469 Title: USB3.0 lost after 18LTS->20LTS upgrade Status in linux package in Ubuntu: Incomplete Bug description: After upgrade to 20 LTS I've lost all USB3.0 ports. This is a desktop PC, not a laptop, no docking station. This happens on all kernels 5.4 - 5.8 . [1.071876] xhci_hcd :0a:00.0: xHCI Host Controller [1.071884] xhci_hcd :0a:00.0: new USB bus registered, assigned bus number 3 [1.125979] xhci_hcd :0a:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x0008 [1.126207] usb usb3: Manufacturer: Linux 5.8.0-29-generic xhci-hcd [1.126410] xhci_hcd :0a:00.0: xHCI Host Controller [1.126414] xhci_hcd :0a:00.0: new USB bus registered, assigned bus number 4 [1.126416] xhci_hcd :0a:00.0: Host supports USB 3.0 SuperSpeed [1.126450] usb usb4: Manufacturer: Linux 5.8.0-29-generic xhci-hcd [1.126638] xhci_hcd :0b:00.0: xHCI Host Controller [1.126641] xhci_hcd :0b:00.0: new USB bus registered, assigned bus number 5 [1.142664] xhci_hcd :0b:00.0: Host halt failed, -110 [1.142665] xhci_hcd :0b:00.0: can't setup: -110 [1.142697] xhci_hcd :0b:00.0: USB bus 5 deregistered [1.142740] xhci_hcd :0b:00.0: init :0b:00.0 fail, -110 [1.142748] xhci_hcd: probe of :0b:00.0 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.8.0-29-generic 5.8.0-29.31~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-29.31~20.04.1-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 24 23:48:42 2020 Dependencies: SourcePackage: linux-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905469] Re: USB3.0 lost after 18LTS->20LTS upgrade
You have nonfree kernel modules. Could you reproduce this bug with free drivers only? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905469 Title: USB3.0 lost after 18LTS->20LTS upgrade Status in linux package in Ubuntu: Incomplete Bug description: After upgrade to 20 LTS I've lost all USB3.0 ports. This is a desktop PC, not a laptop, no docking station. This happens on all kernels 5.4 - 5.8 . [1.071876] xhci_hcd :0a:00.0: xHCI Host Controller [1.071884] xhci_hcd :0a:00.0: new USB bus registered, assigned bus number 3 [1.125979] xhci_hcd :0a:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x0008 [1.126207] usb usb3: Manufacturer: Linux 5.8.0-29-generic xhci-hcd [1.126410] xhci_hcd :0a:00.0: xHCI Host Controller [1.126414] xhci_hcd :0a:00.0: new USB bus registered, assigned bus number 4 [1.126416] xhci_hcd :0a:00.0: Host supports USB 3.0 SuperSpeed [1.126450] usb usb4: Manufacturer: Linux 5.8.0-29-generic xhci-hcd [1.126638] xhci_hcd :0b:00.0: xHCI Host Controller [1.126641] xhci_hcd :0b:00.0: new USB bus registered, assigned bus number 5 [1.142664] xhci_hcd :0b:00.0: Host halt failed, -110 [1.142665] xhci_hcd :0b:00.0: can't setup: -110 [1.142697] xhci_hcd :0b:00.0: USB bus 5 deregistered [1.142740] xhci_hcd :0b:00.0: init :0b:00.0 fail, -110 [1.142748] xhci_hcd: probe of :0b:00.0 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.8.0-29-generic 5.8.0-29.31~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-29.31~20.04.1-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 24 23:48:42 2020 Dependencies: SourcePackage: linux-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905469] Re: USB3.0 lost after 18LTS->20LTS upgrade
In order to allow additional upstream mainline kernel developers to examine the issue, at your earliest convenience, could you please test the latest mainline kernel? Please keep in mind the following: 1) The one to test is in a folder at the very top of the page (not the daily folder). 2) The release names are irrelevant. 3) The folder time stamps aren't indicative of when the kernel actually was released upstream. 4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . If testing on your main install would be inconvenient, one may: 1) Install Ubuntu to a different partition and then test this there. 2) Backup, or clone the primary install. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the mainline kernel, please comment on which kernel version specifically you tested. If this issue is not reproducible in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the Bug Description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists. If the issue is reproducible with the mainline kernel, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Also, you don't need to apport-collect further unless specifically requested to do so. In addition, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available. Lastly, it is most helpful that after testing of the latest mainline kernel is complete, you mark this report Status Confirmed. Thank you for your help. ** Package changed: linux-hwe-5.8 (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/1905469 Title: USB3.0 lost after 18LTS->20LTS upgrade Status in linux package in Ubuntu: Incomplete Bug description: After upgrade to 20 LTS I've lost all USB3.0 ports. This is a desktop PC, not a laptop, no docking station. This happens on all kernels 5.4 - 5.8 . [1.071876] xhci_hcd :0a:00.0: xHCI Host Controller [1.071884] xhci_hcd :0a:00.0: new USB bus registered, assigned bus number 3 [1.125979] xhci_hcd :0a:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x0008 [1.126207] usb usb3: Manufacturer: Linux 5.8.0-29-generic xhci-hcd [1.126410] xhci_hcd :0a:00.0: xHCI Host Controller [1.126414] xhci_hcd :0a:00.0: new USB bus registered, assigned bus number 4 [1.126416] xhci_hcd :0a:00.0: Host supports USB 3.0 SuperSpeed [1.126450] usb usb4: Manufacturer: Linux 5.8.0-29-generic xhci-hcd [1.126638] xhci_hcd :0b:00.0: xHCI Host Controller [1.126641] xhci_hcd :0b:00.0: new USB bus registered, assigned bus number 5 [1.142664] xhci_hcd :0b:00.0: Host halt failed, -110 [1.142665] xhci_hcd :0b:00.0: can't setup: -110 [1.142697] xhci_hcd :0b:00.0: USB bus 5 deregistered [1.142740] xhci_hcd :0b:00.0: init :0b:00.0 fail, -110 [1.142748] xhci_hcd: probe of :0b:00.0 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.8.0-29-generic 5.8.0-29.31~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-29.31~20.04.1-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 24 23:48:42 2020 Dependencies: SourcePackage: linux-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905469] [NEW] USB3.0 lost after 18LTS->20LTS upgrade
You have been subscribed to a public bug: After upgrade to 20 LTS I've lost all USB3.0 ports. This is a desktop PC, not a laptop, no docking station. This happens on all kernels 5.4 - 5.8 . [1.071876] xhci_hcd :0a:00.0: xHCI Host Controller [1.071884] xhci_hcd :0a:00.0: new USB bus registered, assigned bus number 3 [1.125979] xhci_hcd :0a:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x0008 [1.126207] usb usb3: Manufacturer: Linux 5.8.0-29-generic xhci-hcd [1.126410] xhci_hcd :0a:00.0: xHCI Host Controller [1.126414] xhci_hcd :0a:00.0: new USB bus registered, assigned bus number 4 [1.126416] xhci_hcd :0a:00.0: Host supports USB 3.0 SuperSpeed [1.126450] usb usb4: Manufacturer: Linux 5.8.0-29-generic xhci-hcd [1.126638] xhci_hcd :0b:00.0: xHCI Host Controller [1.126641] xhci_hcd :0b:00.0: new USB bus registered, assigned bus number 5 [1.142664] xhci_hcd :0b:00.0: Host halt failed, -110 [1.142665] xhci_hcd :0b:00.0: can't setup: -110 [1.142697] xhci_hcd :0b:00.0: USB bus 5 deregistered [1.142740] xhci_hcd :0b:00.0: init :0b:00.0 fail, -110 [1.142748] xhci_hcd: probe of :0b:00.0 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.8.0-29-generic 5.8.0-29.31~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-29.31~20.04.1-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 24 23:48:42 2020 Dependencies: SourcePackage: linux-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- USB3.0 lost after 18LTS->20LTS upgrade https://bugs.launchpad.net/bugs/1905469 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 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in
** Also affects: plasma-desktop (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758512 Title: No virtual terminals (CTRL+ALT+F?) when no user logged in Status in gdm3 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: New Bug description: As of today's 18.04 version, on a dell xps-13 (the old i7-4500U one), to reproduce: - boot Ubuntu - Press Ctrl+Alt+F2 (or F3 or...) Expected behaviour: virtual console should appear with login prompt. Actual behaviour: nothing happens. When a user is logged in, Ctrl+Alt+F3 switches to terminal tty3... However, hitting first Ctrl+Alt+F1 and, subsequently, hitting Ctrl+Alt+F3 does not show tty3, and remains at the graphical login screen but keyboard and mouse are unresponsive until either Ctrl+Alt+F1 or Ctrl+Alt+F? are pressed, being ? the virtual terminal the ubuntu session is running at. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 10:11:26 2018 InstallationDate: Installed on 2014-05-05 (1418 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-03-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899586] Re: Fix broken MSI interrupt after HDA controller was suspended
** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1899586 Title: Fix broken MSI interrupt after HDA controller was suspended Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] After HDA controller gets suspended and resumed, no MSI interrupt raised when plugging headset to the audio jack. [Fix] Power up the Realtek codec when HDA controller runtime resumes. [Test] 1) Make sure both codec and HDA controller are runtime suspended. 2) Runtime resume the HDA controller without runtime resume the codec. 3) Plug a headset and see if the system can detect anything. With the fix applied, we can see azx_interrupt() is working again by using ftrace. [Regression Potential] If there's any system that is not affected by this issue, runtime-resume the HDA controller will take a slightly longer time. It's rather unlikely, since _all_ systems with Realtek codec we tested have this issue, regardless of AMD or Intel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905663] Re: Add dpcd backlight control for 0x4c83 0x4f41
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1905663 Title: Add dpcd backlight control for 0x4c83 0x4f41 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] There is a new OLED panel that is required to be listed in the EDID quirk to make its backlight work. [Fix] The commit adds its EDID to the quirk. https://lkml.org/lkml/2020/11/19/1564 [Test] Verified on Dell's platform with this panel. [Where problems could occur] Only if this panel switches to use PWM mode only, and doesn't support DPCD backlight. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904848] Re: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Bionic) Assignee: Kamal Mostafa (kamalmostafa) => Ian (ian-may) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904848 Title: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: [Impact] unloading ib_ipoib causes a call trace to be logged in kernel buffer. bisecting the bionic kernel reveals that this issue was discovered by 616e695435e3 workqueue: Try to catch flush_work() without INIT_WORK() in version 4.15.0-59.66 [test case] # modprobe ib_ipoib # modprobe ib_ipoib -r # dmesg [ 306.277717] [ cut here ] [ 306.277738] WARNING: CPU: 10 PID: 2148 at /build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 __flush_work+0x1f8/0x210 [ 306.277739] Modules linked in: nfsv3 nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp llc binfmt_misc intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp rpcrdma rdma_ucm ib_umad ib_uverbs coretemp ib_iser rdma_cm kvm_intel kvm iw_cm irqbypass ib_ipoib(-) libiscsi scsi_transport_iscsi ib_cm joydev input_leds crct10dif_pclmul crc32_pclmul mgag200 ttm drm_kms_helper drm hpilo ghash_clmulni_intel pcbc i2c_algo_bit ipmi_ssif fb_sys_fops syscopyarea sysfillrect sysimgblt aesni_intel aes_x86_64 crypto_simd ioatdma glue_helper shpchp cryptd dca intel_cstate intel_rapl_perf [ 306.277790] serio_raw acpi_power_meter lpc_ich mac_hid ipmi_si ipmi_devintf ipmi_msghandler nfsd auth_rpcgss nfs_acl lockd grace sunrpc sch_fq_codel ip_tables x_tables autofs4 mlx5_ib mlx4_ib mlx4_en ib_core hid_generic psmouse mlx5_core usbhid hid pata_acpi hpsa tg3 mlxfw mlx4_core scsi_transport_sas ptp pps_core devlink [ 306.277817] CPU: 10 PID: 2148 Comm: modprobe Not tainted 4.15.0-124-generic #127-Ubuntu [ 306.277818] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 07/01/2015 [ 306.277823] RIP: 0010:__flush_work+0x1f8/0x210 [ 306.277825] RSP: 0018:bdeb47ecfcd8 EFLAGS: 00010286 [ 306.277827] RAX: 0024 RBX: 993a5c3d8ec8 RCX: 0006 [ 306.277829] RDX: RSI: 99429ef16498 RDI: 99429ef16490 [ 306.277830] RBP: bdeb47ecfd48 R08: 050d R09: 0004 [ 306.277832] R10: e263a058c1c0 R11: 0001 R12: 993a5c3d8ec8 [ 306.277833] R13: 0001 R14: bdeb47ecfd78 R15: b00a9800 [ 306.277835] FS: 7fa1124a9540() GS:99429ef0() knlGS: [ 306.277837] CS: 0010 DS: ES: CR0: 80050033 [ 306.277839] CR2: 55b1c5007bb0 CR3: 000fcf36c002 CR4: 001606e0 [ 306.277840] Call Trace: [ 306.277850] __cancel_work_timer+0x136/0x1b0 [ 306.277881] ? mlx5_core_destroy_qp+0x99/0xd0 [mlx5_core] [ 306.277886] cancel_delayed_work_sync+0x13/0x20 [ 306.277909] mlx5e_detach_netdev+0x83/0x90 [mlx5_core] [ 306.277931] mlx5_rdma_netdev_free+0x30/0x80 [mlx5_core] [ 306.277941] mlx5_ib_free_rdma_netdev+0xe/0x10 [mlx5_ib] [ 306.277948] ipoib_remove_one+0xe4/0x180 [ib_ipoib] [ 306.277965] ib_unregister_client+0x171/0x1e0 [ib_core] [ 306.277972] ipoib_cleanup_module+0x15/0x2f [ib_ipoib] [ 306.277978] SyS_delete_module+0x1ab/0x2d0 [ 306.277983] do_syscall_64+0x73/0x130 [ 306.277989] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 306.277992] RIP: 0033:0x7fa111fc1047 [ 306.277993] RSP: 002b:7ffc0db32298 EFLAGS: 0206 ORIG_RAX: 00b0 [ 306.277996] RAX: ffda RBX: 5614be46cca0 RCX: 7fa111fc1047 [ 306.277997] RDX: RSI: 0800 RDI: 5614be46cd08 [ 306.277999] RBP: 5614be46cca0 R08: 7ffc0db31241 R09: [ 306.278000] R10: 7fa11203dc40 R11: 0206 R12: 5614be46cd08 [ 306.278002] R13: 0001 R14: 5614be46cd08 R15: 7ffc0db33680 [ 306.278004] Code: 24 03 80 c9 f0 e9 5b ff ff ff 48 c7 c7 18 50 0b b1 e8 ed 66 04 00 0f 0b 31 c0 e9 75 ff ff ff 48 c7 c7 18 50 0b b1 e8 d8 66 04 00 <0f> 0b 31 c0 e9 60 ff ff ff e8 5a 35 fe ff 66 2e 0f 1f 84 00 00 [ 306.278035] ---[ end trace 652f7759937172a2 ]--- [ 306.646061] [ cut here ] [
[Kernel-packages] [Bug 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1
** Tags added: rls-gg-incoming rls-hh-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1905627 Title: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1 Status in bluez package in Ubuntu: New Bug description: Bluetooth stops working after updating to bluez version 5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization timed out". Bluetooth is working again if bluez is reverted to version 5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt. Release: 20.10 bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14 Uname: Linux 5.8.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 16:09:03 2020 ImageMediaBuild: 20200423.1 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 25EE Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: bluez UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1905627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905663] Re: Add dpcd backlight control for 0x4c83 0x4f41
** Tags added: oem-priority originate-from-1902471 somerville ** Description changed: [Impact] There is a new OLED panel that is required to be listed in the EDID quirk to make its backlight work. [Fix] The commit adds its EDID to the quirk. https://lkml.org/lkml/2020/11/19/1564 [Test] Verified on Dell's platform with this panel. [Where problems could occur] - Only if this panel uses PWM mode only, and doesn't support DPCD backlight. + Only if this panel switches to use PWM mode only, and doesn't support DPCD backlight. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1905663 Title: Add dpcd backlight control for 0x4c83 0x4f41 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] There is a new OLED panel that is required to be listed in the EDID quirk to make its backlight work. [Fix] The commit adds its EDID to the quirk. https://lkml.org/lkml/2020/11/19/1564 [Test] Verified on Dell's platform with this panel. [Where problems could occur] Only if this panel switches to use PWM mode only, and doesn't support DPCD backlight. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902957] Re: Update kernel packaging to support forward porting kernels
I have cranked several backport kernels this cycle and I confirm that as expected these patches made no change on the how their versions are constructed. Only the forward-ported kernels in Hirsute should have a visible change. ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-groovy verification-needed-xenial ** Tags added: verification-done-bionic verification-done-focal verification-done-groovy verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902957 Title: Update kernel packaging to support forward porting kernels Status in linux package in Ubuntu: In Progress Status in linux source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: In Progress Bug description: SRU Justification Impact: Our kernel packaging currently has support for backporting kernels to older releases. This includes appending ~BACKPORT_SUFFIX to the version string for the backport kernel, where BACKPORT_SUFFIX is defined in update.conf. We need to start doing similar forward ported kernels, but BACKPORT_SUFFIX should be appended using a + rather than a ~. Our kernel packaging cannot easily determine whether a + or a ~ is appropriate. Fix: Move the leading character into BACKPORT_SUFFIX, and do not insert any leading characters from the kernel packaging scripts. Since the script which generates update.conf has access to information from kernel-series, it can more easily determine whether + or ~ is the appropriate leader. Test Case: Run through the normal steps for updating a backport kernel. The version string generated should have ~SERIES for a backport to an older series, and +SERIES for a backport to a newer series. Regression Potential: Backport kernels could end up with an incorrect version strings. Since all kernel uploads undergo review, any such errors should be caught before uploading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882834] Re: vmxnet3: update to latest ToT
Any updates ? Thanks Yuhua Zou -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882834 Title: vmxnet3: update to latest ToT Status in linux package in Ubuntu: Confirmed Bug description: This request is to port vmxnet3 patches to Ubuntu kernel. Below are the commits in order: vmxnet3: prepare for version 4 changes https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1 vmxnet3: add support to get/set rx flow hash https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d3a8a9e5c3b334d443e97daa59bb95c0b69f4794 vmxnet3: add geneve and vxlan tunnel offload support https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dacce2be33124df3c71f979ac47e3d6354a41125 vmxnet3: update to version 4 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=a31135e36eccd0d16e500d3041f23c3ece62096f vmxnet3: use correct hdr reference when packet is encapsulated https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=36432797641ff0013be9252eecf7ad1ba73171a2 vmxnet3: allow rx flow hash ops only when rss is enabled https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=11e877b2a8cfd282a1b81f9d4c594b900889a5d8 This is a request to bring Ubuntu vmxnet3 driver up to date with ToT Linux kernel. Could you apply these patches to ongoing releases? Also, could you help verify if the below commits are present in vmxnet3 of ubuntu kernel? If not, then please apply these patches before above ones. vmxnet3: set the DMA mask before the first DMA map operation https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=61aeecea40afb2b89933e27cd4adb10fc2e75cfd vmxnet3: use DMA memory barriers where required https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=f3002c1374fb2367c9d8dbb28852791ef90d2bac vmxnet3: turn off lro when rxcsum is disabled https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/drivers/net/vmxnet3?id=3dd7400b419409b1551f7f01764b1f3160feda90 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899586] Re: Fix broken MSI interrupt after HDA controller was suspended
** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: linux-oem-5.6 (Ubuntu Groovy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1899586 Title: Fix broken MSI interrupt after HDA controller was suspended Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] After HDA controller gets suspended and resumed, no MSI interrupt raised when plugging headset to the audio jack. [Fix] Power up the Realtek codec when HDA controller runtime resumes. [Test] 1) Make sure both codec and HDA controller are runtime suspended. 2) Runtime resume the HDA controller without runtime resume the codec. 3) Plug a headset and see if the system can detect anything. With the fix applied, we can see azx_interrupt() is working again by using ftrace. [Regression Potential] If there's any system that is not affected by this issue, runtime-resume the HDA controller will take a slightly longer time. It's rather unlikely, since _all_ systems with Realtek codec we tested have this issue, regardless of AMD or Intel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1
Thank you for your bug report. It's probably an issue we want sorted out before accepting the update in hirsute so let's tag it block-proposed ** Tags added: regression-update ** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Tags added: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1905627 Title: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1 Status in bluez package in Ubuntu: New Bug description: Bluetooth stops working after updating to bluez version 5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization timed out". Bluetooth is working again if bluez is reverted to version 5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt. Release: 20.10 bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14 Uname: Linux 5.8.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 16:09:03 2020 ImageMediaBuild: 20200423.1 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 25EE Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: bluez UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1905627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905103] Re: Unrecoverable random freezes; Ubuntu 20.04; HP Spectre X360
I upgraded to Ubuntu 20.10 kernel 5.8.0-29-generic five days ago and have had no freeze issues since. I believe this issue is resolved with kernel update. Not sure if it is relevant but the new kernel does not log messages of the sort: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 300) which were seen in the old kernel. I did monitor the temperature sensors under both kernels and neither were unusually high. The fan rarely kicked in. Hopefully this will help diagnosis and future development. 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/1905103 Title: Unrecoverable random freezes; Ubuntu 20.04; HP Spectre X360 Status in linux package in Ubuntu: Incomplete Bug description: The system freezes at apparently random times with no warning and no possibility to recover. The system becomes completely unresponsive and has to be hard reset. The mouse cursor does not move and no keyboard input works. In particular, Alt+SysRq+REISUB does not work (confirmed that it is activated and works in normal conditions). Neither does Ctrl+Alt+F2,F3,etc. If a youtube music is playing in the background I hear the audio get stuck in a short repeat loop (stutter) then stop after a while. The freezes have been happening for the past month or so at intervals of about 1-3 days, not long after I installed Ubuntu 20.04 as the first linux distro on this machine. Not sure if it all started after an update. No program seems to crash before the freeze happens, and I have not found any pattern of activity that can reliably trigger the freeze. It has happened while surfing the internet or just viewing files. The kernel logs nothing unusual before the freeze (please see the attached kern.log file; it contains multiple instances of the freeze: look for where the system boots without proper shut down beforehand). I have tried switching between the open-source and the proprietary video drivers. It didn't help. Also uninstalled xserver-xorg-video-intel with no result, so installed it back. Not sure what to try next. Very frustrating as the hard resets can damage important work and data on disks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: farshad1494 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 20 15:11:20 2020 InstallationDate: Installed on 2020-10-10 (41 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201007) MachineType: HP HP Spectre x360 Convertible 15-df1xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=0536b924-b1a1-4ba7-bff4-04df7284b913 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2020 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863F dmi.board.vendor: HP dmi.board.version: 54.23 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd06/01/2020:svnHP:pnHPSpectrex360Convertible15-df1xxx:pvr:rvnHP:rn863F:rvr54.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-df1xxx dmi.product.sku: 7UT64UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
