[Kernel-packages] [Bug 1949050] Re: Fix Screen freeze after resume from suspend with iGPU [1002:6987]
** Tags removed: verification-needed-hirsute verification-needed-impish ** Tags added: verification-done-hirsute verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1949050 Title: Fix Screen freeze after resume from suspend with iGPU [1002:6987] Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Incomplete Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] Screen freeze after resume from suspend [Fix] Perform proper cleanups on UVD/VCE suspend: powergate enablement, clockgating enablement and dpm disablement. This can fix some hangs observed on suspending when UVD/VCE still using(e.g. issue "pm-suspend" when video is still playing). [Test] 1. Plug AMD RX640/Radeon 540 into the system 2. Connect with DP monitor to iGPU 3. Power on 4. Suspend the system 5. Resume from suspend 6. Do something for a while (terminal, nautilus, gnome-control-center, etc). 7. System could resume normally [Regression Potential] Low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
Kernel works ok. So as it stands, new 5.15.3 has no "CONFIG_UBSAN_TRAP" in config. So for new kernels you can probably close this bug off as long as they don't reintroduce it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot Status in linux package in Ubuntu: Confirmed Bug description: I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to boot with either one. However, I am able to boot just fine with 5.14.0-rc7. journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-04 (62 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: wayland-session hirsute Uname: Linux 5.14.0-051400rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
@skucharski77 nope, mine was less than 1% before freeze. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912052] Re: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset)
Hello! Thanks for the bug report, can you give these test kernels (bionic 4.15, Focal 5.4, Hirsute 5.11, Impish 5.13, Jammy 5.15) a try: https://people.canonical.com/~phlin/kernel/lp-1912052-acer-SP513-mic/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset) Status in Linux: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
Looks like they may have removed "CONFIG_UBSAN_TRAP" from the kernel config of 5.15.3! Only this is in the config... ``` # CONFIG_UBSAN is not set ``` I'm building it now to see if it is ok and works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot Status in linux package in Ubuntu: Confirmed Bug description: I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to boot with either one. However, I am able to boot just fine with 5.14.0-rc7. journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-04 (62 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: wayland-session hirsute Uname: Linux 5.14.0-051400rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912052] Re: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset)
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset) Status in Linux: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912052] Re: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset)
** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset) Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Status in linux source package in Hirsute: New Status in linux source package in Impish: New Status in linux source package in Jammy: Confirmed Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944071] Re: [Nvidia GeForce GT 710] Low resolution, missing /dev/dri/card0
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1944071 Title: [Nvidia GeForce GT 710] Low resolution, missing /dev/dri/card0 Status in linux package in Ubuntu: Expired Bug description: my system has low resolution , strange size in icons , cannot upgrade and update Ubuntu 18.04 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Sep 19 13:09:38 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-33-generic, i686: installed bbswitch, 0.8, 4.15.0-43-generic, i686: installed bbswitch, 0.8, 4.15.0-96-generic, i686: installed bbswitch, 0.8, 4.4.0-134-generic, i686: installed nvidia, 390.116: added DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK208B [GeForce GT 710] [1458:36f8] InstallationDate: Installed on 2014-05-05 (2693 days ago) InstallationMedia: MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=a29545ea-f853-49eb-ab0d-862d65642632 ro quiet splash Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-S2PV REV 2.2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S2PVREV2.2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Sep 19 12:23:48 2021 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
** Tags added: displaylink evdi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950087] Re: ubuntu 21.10 live usb does not recognize Razer Blade 15 (2021) nvme drive (possible kernel bug)
I am also having the exact same issue, though WiFI and Nvidia drivers worked as expected for me (with a tiny hiccup due to some intel wifi firmware blob being bad: iwlwifi-ty-a0-gf-a0.pnvm sha1sum: 0fca9ea9041f65585fcc860f3949832a69360a6f). I currently have a 'usable' 21.10 install that I upgraded to from 20.04 LTS. I can only use the system when using kernel version 5.11.0-38-generic. When doing an lshw on the 21.10 Live image, I can see that the 'NVMe SSD Controller PM9A1/PM9A3/980PRO' section is highlighted as unknown. Attempting to modprobe the nvme driver didn't seem to help if I recall. I'll be happy to test any potential fix as I believe I have the same hardware as the original reported. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950087 Title: ubuntu 21.10 live usb does not recognize Razer Blade 15 (2021) nvme drive (possible kernel bug) Status in linux package in Ubuntu: Confirmed Bug description: I am attempting to install Ubuntu on to a new Razer Blade 15 Advanced (mid-2021) laptop. However, there seems to be some issues with kernel compatibility. When installing 20.04 LTS I have many issues with hardware not being detected (especially the intel AX210 wifi card). Running the 21.10 release from a live usb happily detected all of my hardware out of the box, with one show-stopping exception.. the internal nvme drive is not visible at all. I have tried every combination of bios options imaginable, as well as multiple Ubuntu-based distros such as Kubuntu, Pop!OS and Ubuntu Studio - all with the same results: 20.04 LTS detects the internal nvme and will install, but lacks important hardware support - while 21.10 (running in live mode) is compatible with all the essential hardware out of the box, but does not "see" the internal nvme. My short-term solution has been to install a 20.04 release using a wired internet connection, followed by upgrading to 21.04. This configuration then works, however if I upgrade again to 21.10 the internal drive again becomes undetectable, making it impossible to boot the OS. This seems to be an emerging issue.. see: https://askubuntu.com/questions/1370379/21-10-does-not-see-windows- nvme-drive/1374079?noredirect=1#comment2364713_1374079 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
Hi. Can you retry with, in terminal running iostat -mx 2 . Is this similar to mine? I have large %iowait value before the freeze. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950086 ** Attachment added: "IMG_2024_225936.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+attachment/5541889/+files/IMG_2024_225936.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
Hi. Can you retry with, in terminal running iostat -mxz 2 . Is this similar to mine? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950086 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
@arighi i completely agree with manolo above and have also stated it before above, this bug has to be considered critical for the installer (all the *buntu installers) because on installer launch you just get a total kernel lockup/crash with no possibility to proceed. in fact i still don't understand why a total kernel crash with stack corruption on certain hardware is not classed as critical in itself (ie this bug itself should have importance critical). as manolo rightly says, an ugly crash on install attempt means any prospective new user trying any *buntu installer on any hardware with this trackpad will quite likely simply give up on *buntu, which is hardly what *buntu as a whole should want. imho there definitely needs to be new installer iso point releases at some stage before 22.04 once the working kernel is officially released. at the very least all ubuntu flavours need to amend their release/install notes with a new "Known issues" item for "Installer and live session" that details this kernel crash, which should be updated (on fixed kernel release) with the work-around (disable trackpad/trackpoint, install, upgrade kernel, re-enable trackpad/trackpoint) to get the system installed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Status in linux source package in Jammy: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!
Launchpad has imported 65 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=177311. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-10-12T20:59:43+00:00 ck+kernelbugzilla wrote: I've noticed, when I do enable CONFIG_SENSORS_JC42 as a module or build into my kernel, this causes a very high rate of interrupts on i801_smbus - about 6000-8000 per second according to /proc/interrupts. After 20 minutes, there were about 5 million interrupts generated on i801_smbus. When I do unload the module jc42, the interrupts do not stop, until I do a complete reboot. Mainboard: Supermicro A1SRM-2758F Kernel: Gentoo-Sources 4.8.1 (Happens also with Vanilla 4.8.1 and older kernel versions) dmesg: [8.319900] i801_smbus :00:1f.3: enabling device (0140 -> 0143) [8.321864] i801_smbus :00:1f.3: SMBus using PCI interrupt [8.326098] ismt_smbus :00:13.0: enabling device (0140 -> 0142) lspci: 00:1f.3 SMBus: Intel Corporation Atom processor C2000 PCU SMBus (rev 02) When the module is loaded, I am also getting this errors: [ 73.934901] ismt_smbus :00:13.0: completion wait timed out [ 74.974970] ismt_smbus :00:13.0: completion wait timed out [ 76.014949] ismt_smbus :00:13.0: completion wait timed out [ 77.054903] ismt_smbus :00:13.0: completion wait timed out [ 78.094961] ismt_smbus :00:13.0: completion wait timed out [ 79.134982] ismt_smbus :00:13.0: completion wait timed out [ 80.175116] ismt_smbus :00:13.0: completion wait timed out [ 81.215057] ismt_smbus :00:13.0: completion wait timed out Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- hwe-5.11/+bug/1931001/comments/0 On 2016-10-12T21:00:53+00:00 ck+kernelbugzilla wrote: The jc42 module seems to work, as lm_sensors do find the sensors, after loading it: Galactica ~ # sensors jc42-i2c-1-19 Adapter: SMBus I801 adapter at e000 temp1:+30.8°C (low = +0.0°C) ALARM (HIGH, CRIT) (high = +0.0°C, hyst = +0.0°C) (crit = +0.0°C, hyst = +0.0°C) jc42-i2c-1-1a Adapter: SMBus I801 adapter at e000 temp1:+29.5°C (low = +0.0°C) ALARM (HIGH, CRIT) (high = +0.0°C, hyst = +0.0°C) (crit = +0.0°C, hyst = +0.0°C) jc42-i2c-1-18 Adapter: SMBus I801 adapter at e000 temp1:+27.2°C (low = +0.0°C) ALARM (HIGH, CRIT) (high = +0.0°C, hyst = +0.0°C) (crit = +0.0°C, hyst = +0.0°C) jc42-i2c-1-1b Adapter: SMBus I801 adapter at e000 temp1:+28.2°C (low = +0.0°C) ALARM (HIGH, CRIT) (high = +0.0°C, hyst = +0.0°C) (crit = +0.0°C, hyst = +0.0°C) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- hwe-5.11/+bug/1931001/comments/1 On 2016-11-28T15:19:42+00:00 linux wrote: You need to set the temperature limits correctly. Without limits, the chips will persistently generate alarms which is the likely cause of the interrupts. That won't solve the completion interrupt timeouts, though. That may be another problem. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- hwe-5.11/+bug/1931001/comments/2 On 2016-11-28T16:10:21+00:00 ck+kernelbugzilla wrote: (In reply to Guenter Roeck from comment #2) > You need to set the temperature limits correctly. Without limits, the chips > will persistently generate alarms which is the likely cause of the > interrupts. > > That won't solve the completion interrupt timeouts, though. That may be > another problem. Hi! Thanks for your answer. I've gave a try and set those limits, so sensors does not show any more ALARM. Seems not to be the cause, because after settings, the interrupts are still generated massivley.. jc42-i2c-1-1b Adapter: SMBus I801 adapter at e000 RAM: +30.0°C (low = +0.0°C) (high = +80.0°C, hyst = +80.0°C) (crit = +80.0°C, hyst = +80.0°C) jc42-i2c-1-19 Adapter: SMBus I801 adapter at e000 RAM: +32.0°C (low = +0.0°C) (high = +80.0°C, hyst = +80.0°C) (crit = +80.0°C, hyst = +80.0°C) jc42-i2c-1-1a Adapter: SMBus I801 adapter at e000 RAM: +31.0°C (low = +0.0°C) (high = +80.0°C, hyst = +80.0°C) (crit = +80.0°C, hyst = +80.0°C) jc42-i2c-1-18 Adapter: SMBus I801 adapter at e000 RAM:
[Kernel-packages] [Bug 1951470] Proposed Fix
Default Comment by Bridge ** Attachment added: "Proposed Fix" https://bugs.launchpad.net/bugs/1951470/+attachment/5541882/+files/webkit-IBMZ-fix.patch ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** 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/1951470 Title: webkit javascript segmentation fault Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Andreas Krebbel - 2021-11-15 09:29:44 == ---Problem Description--- Segmentation fault from WebKit Javascript engine Contact Information = andreas.kreb...@de.ibm.com ---uname output--- Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM Z ---Debugger--- A debugger is not configured ---Steps to Reproduce--- index.html: min.js: var i = Math.max wkhtmltopdf index.html test.pdf QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Loading page (1/2) Segmentation fault (core dumped) ] 17% Userspace tool common name: wkhtmltopdf The userspace tool has the following bit modes: 64 Userspace rpm: libqt5webkit5 Userspace tool obtained from project website: na *Additional Instructions for andreas.kreb...@de.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #1 - Andreas Krebbel - 2021-11-15 09:44:04 == In CodeBlock.cpp the code preparing the operands of op_get_from_scope writes the property offset as pointer size (hence 64 bit) value: 2141: instructions[i + 6].u.pointer = reinterpret_cast(op.operand); while the same slot is accessed later by the jitted code as 32 bit integer: macro getProperty(slow) loadisFromInstruction(6, t1) This fails on big endian targets since the integer access takes the higher part of the 64 bit value. Changing: macro getProperty(slow) loadisFromInstruction(6, t1) to macro getProperty(slow) loadpFromInstruction(6, t1) in llint/LowLevelInterpreter64.asm fixes the problem for me. I could not reproduce the problem on Ubuntu 20.10. In upstream webkit the problem got fixed as a side effect of a larger change but in the end quite similar to the change I'm proposing. The value resides somewhere else now but it is accessed as 64 bit value in getProperty: macro getProperty() loadp OpGetFromScope::Metadata::m_operand[t5], t1 If you have the jsc binary from the webkit package available the problem can be reproduced with just 'jsc -e "i=Math.min"' == Comment: #2 - Andreas Krebbel - 2021-11-15 09:49:55 == To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951470] [NEW] webkit javascript segmentation fault
You have been subscribed to a public bug: == Comment: #0 - Andreas Krebbel - 2021-11-15 09:29:44 == ---Problem Description--- Segmentation fault from WebKit Javascript engine Contact Information = andreas.kreb...@de.ibm.com ---uname output--- Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM Z ---Debugger--- A debugger is not configured ---Steps to Reproduce--- index.html: min.js: var i = Math.max wkhtmltopdf index.html test.pdf QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Loading page (1/2) Segmentation fault (core dumped) ] 17% Userspace tool common name: wkhtmltopdf The userspace tool has the following bit modes: 64 Userspace rpm: libqt5webkit5 Userspace tool obtained from project website: na *Additional Instructions for andreas.kreb...@de.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #1 - Andreas Krebbel - 2021-11-15 09:44:04 == In CodeBlock.cpp the code preparing the operands of op_get_from_scope writes the property offset as pointer size (hence 64 bit) value: 2141: instructions[i + 6].u.pointer = reinterpret_cast(op.operand); while the same slot is accessed later by the jitted code as 32 bit integer: macro getProperty(slow) loadisFromInstruction(6, t1) This fails on big endian targets since the integer access takes the higher part of the 64 bit value. Changing: macro getProperty(slow) loadisFromInstruction(6, t1) to macro getProperty(slow) loadpFromInstruction(6, t1) in llint/LowLevelInterpreter64.asm fixes the problem for me. I could not reproduce the problem on Ubuntu 20.10. In upstream webkit the problem got fixed as a side effect of a larger change but in the end quite similar to the change I'm proposing. The value resides somewhere else now but it is accessed as 64 bit value in getProperty: macro getProperty() loadp OpGetFromScope::Metadata::m_operand[t5], t1 If you have the jsc binary from the webkit package available the problem can be reproduced with just 'jsc -e "i=Math.min"' == Comment: #2 - Andreas Krebbel - 2021-11-15 09:49:55 == ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-195436 severity-high targetmilestone-inin--- -- webkit javascript segmentation fault https://bugs.launchpad.net/bugs/1951470 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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
Bumped into this bug after upgrading to 21.10. Laptop with nVidia 2080, DisplayPort to external screen. Adding LIBGL_DRI3_DISABLE=true to /etc/environment fixed my issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!
My Lenovo Ideapad Duet 3i with Ubuntu 22.04 (Kernel 5.13) is also affected (Current workaround disable_features=0x10). ** Bug watch added: Linux Kernel Bug Tracker #177311 https://bugzilla.kernel.org/show_bug.cgi?id=177311 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=177311 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! Status in Linux: Unknown Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in Fedora: Confirmed Bug description: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0] jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [lxd:3975] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] root@alumne-1-58:~# --- Usually if you reboot everything works fine but it's very annoying when happens. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1931001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951460] Re: Impish update: upstream stable patchset 2021-11-18
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2021-11-18 -upstream stable patchset 2021-11-18 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v5.10.73, v5.14.12 + + from git://git.kernel.org/ + + Partially revert "usb: Kconfig: using select for USB_COMMON dependency" + usb: chipidea: ci_hdrc_imx: Also search for 'phys' phandle + USB: cdc-acm: fix racy tty buffer accesses + USB: cdc-acm: fix break reporting + usb: typec: tcpm: handle SRC_STARTUP state if cc changes + drm/nouveau/kms/tu102-: delay enabling cursor until after assign_windows + xen/privcmd: fix error handling in mmap-resource processing + mmc: meson-gx: do not use memcpy_to/fromio for dram-access-quirk + mmc: sdhci-of-at91: wait for calibration done before proceed + mmc: sdhci-of-at91: replace while loop with read_poll_timeout + ovl: fix missing negative dentry check in ovl_rename() + ovl: fix IOCB_DIRECT if underlying fs doesn't support direct IO + nfsd: fix error handling of register_pernet_subsys() in init_nfsd() + nfsd4: Handle the NFSv4 READDIR 'dircount' hint being zero + SUNRPC: fix sign error causing rpcsec_gss drops + xen/balloon: fix cancelled balloon action + ARM: dts: omap3430-sdp: Fix NAND device node + ARM: dts: imx6dl-yapp4: Fix lp5562 LED driver probe + ARM: dts: qcom: apq8064: use compatible which contains chipid + riscv: Flush current cpu icache before other cpus + bus: ti-sysc: Add break in switch statement in sysc_init_soc() + soc: qcom: socinfo: Fixed argument passed to platform_set_data() + ARM: dts: qcom: apq8064: Use 27MHz PXO clock as DSI PLL reference + ARM: at91: pm: do not panic if ram controllers are not enabled + soc: qcom: mdt_loader: Drop PT_LOAD check on hash segment + ARM: dts: imx: Add missing pinctrl-names for panel on M53Menlo + ARM: dts: imx: Fix USB host power regulator polarity on M53Menlo + ARM: dts: imx6qdl-pico: Fix Ethernet support + PCI: hv: Fix sleep while in non-sleep context when removing child devices from the bus + ath5k: fix building with LEDS=m + arm64: dts: qcom: pm8150: use qcom,pm8998-pon binding + xtensa: use CONFIG_USE_OF instead of CONFIG_OF + xtensa: call irqchip_init only when CONFIG_USE_OF is selected + iwlwifi: pcie: add configuration of a Wi-Fi adapter on Dell XPS 15 + bpf, arm: Fix register clobbering in div/mod implementation + soc: ti: omap-prm: Fix external abort for am335x pruss + bpf: Fix integer overflow in prealloc_elems_and_freelist() + net/mlx5e: IPSEC RX, enable checksum complete + net/mlx5: E-Switch, Fix double allocation of acl flow counter + phy: mdio: fix memory leak + net_sched: fix NULL deref in fifo_set_limit() + powerpc/fsl/dts: Fix phy-connection-type for fm1mac3 + ptp_pch: Load module automatically if ID matches + dt-bindings: drm/bridge: ti-sn65dsi86: Fix reg value + ARM: imx6: disable the GIC CPU interface before calling stby-poweroff sequence + net: bridge: use nla_total_size_64bit() in br_get_linkxstats_size() + net: bridge: fix under estimation in br_get_linkxstats_size() + net/sched: sch_taprio: properly cancel timer from taprio_destroy() + net: sfp: Fix typo in state machine debug string + netlink: annotate data races around nlk->bound + bus: ti-sysc: Use CLKDM_NOAUTO for dra7 dcan1 for errata i893 + drm/sun4i: dw-hdmi: Fix HDMI PHY clock setup + video: fbdev: gbefb: Only instantiate device when built for IP32 + drm/nouveau: avoid a use-after-free when BO init fails + drm/nouveau/kms/nv50-: fix file release memory leak + drm/nouveau/debugfs: fix file release memory leak + gve: Correct available tx qpl check + gve: Avoid freeing NULL pointer + rtnetlink: fix if_nlmsg_stats_size() under estimation + gve: fix gve_get_stats() + gve: report 64bit tx_bytes counter from gve_handle_report_stats() + i40e: fix endless loop under rtnl + i40e: Fix freeing of uninitialized misc IRQ vector + net: prefer socket bound to interface when not in VRF + powerpc/iommu: Report the correct most efficient DMA mask for PCI devices + i2c: acpi: fix
[Kernel-packages] [Bug 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed
** Tags added: sru-20211108 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1837543 Title: crypto_user02 in crypto from ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: Confirmed Bug description: This is a new test, test will fail with: <<>> tag=crypto_user02 stime=1563881396 cmdline="crypto_user02" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s crypto_user02.c:59: INFO: Starting crypto_user larval deletion test. May crash buggy kernels. crypto_user02.c:91: BROK: unexpected error from tst_crypto_del_alg(): EBUSY Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Nothing interesting in syslog: Jul 23 11:29:20 amaura systemd[1]: Started Session 1 of user ubuntu. Jul 23 11:29:56 amaura kernel: [ 619.646330] LTP: starting crypto_user02 Jul 23 11:30:23 amaura kernel: [ 646.554403] cfg80211: Loading compiled-in X.509 certificates for regulatory database Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "crypto_user02 crypto_user02" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 23 11:19 seq crw-rw 1 root audio 116, 33 Jul 23 11:19 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 23 11:30:15 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951460] [NEW] Impish update: upstream stable patchset 2021-11-18
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-11-18 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Impish) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => Invalid ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Impish) Status: Invalid => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951460 Title: Impish update: upstream stable patchset 2021-11-18 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: In Progress 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: upstream stable patchset 2021-11-18 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951460/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946486] Re: Unable to reboot ARM64 node with 5.11.0-27-realtime
** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946486 Title: Unable to reboot ARM64 node with 5.11.0-27-realtime Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: Confirmed Bug description: It looks like this issue is affecting some ARM64 bare metal node: * helo-kernel 2 failed out of 2 attempts * kuzzle 11 failed out of 13 attempts (as far as I can recall 2 deployments failed early, the system was not deployed at all, so probably we can call it 9 failed) The boot test will fail, the system was unable to reboot with the 5.11.0-27-realtime kernel, here is the steps (integrated with the deployment script) 1. Deploy this node with Hirsute 2. Install the 5.11.0-27-realtime kernel and set to boot with this kernel by using the boot-kernel-simple in ckct. Reboot 3. System can boot with 5.11.0-27-realtime, reboot again to make sure it's OK It seem the system will stuck at the last reboot attempt in step 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1946486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861053] Re: fatrace doesn't trace on zfs filesystems
$ https://github.com/openzfs/zfs $ cd zfs/ $ git grep -n fsnotify shows that notification was never implemented. So this works as designed. Closing as "invalid". Best regards Heinrich ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: fatrace (Ubuntu) Status: New => 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/1861053 Title: fatrace doesn't trace on zfs filesystems Status in fatrace package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: Hello, fatrace in focal doesn't seem to work for me in focal. Start fatrace in one terminal, and perform file operations in another terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc. sarnold@millbarge:~$ sudo fatrace [sudo] password for sarnold: ^Csarnold@millbarge:~$ sudo strace -yy fatrace execve("/usr/sbin/fatrace", ["fatrace"], 0x7ffcc89ad9c8 /* 15 vars */) = 0 brk(NULL) = 0x55c9a1947000 arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd18dbde80) = -1 EINVAL (Invalid argument) access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 fstat(3, {st_mode=S_IFREG|0644, st_size=71040, ...}) = 0 mmap(NULL, 71040, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f3539b15000 close(3) = 0 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360r\2\0\0\0\0\0"..., 832) = 832 lseek(3, 64, SEEK_SET) = 64 read(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784 lseek(3, 848, SEEK_SET) = 848 read(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32 lseek(3, 880, SEEK_SET) = 880 read(3, "\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"..., 68) = 68 fstat(3, {st_mode=S_IFREG|0755, st_size=2025032, ...}) = 0 mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f3539b13000 lseek(3, 64, SEEK_SET) = 64 read(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784 lseek(3, 848, SEEK_SET) = 848 read(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32 lseek(3, 880, SEEK_SET) = 880 read(3, "\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"..., 68) = 68 mmap(NULL, 2032984, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f3539922000 mmap(0x7f3539947000, 1540096, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x25000) = 0x7f3539947000 mmap(0x7f3539abf000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x19d000) = 0x7f3539abf000 mmap(0x7f3539b09000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e6000) = 0x7f3539b09000 mmap(0x7f3539b0f000, 13656, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3539b0f000 close(3) = 0 arch_prctl(ARCH_SET_FS, 0x7f3539b14580) = 0 mprotect(0x7f3539b09000, 12288, PROT_READ) = 0 mprotect(0x55c99fee8000, 4096, PROT_READ) = 0 mprotect(0x7f3539b53000, 4096, PROT_READ) = 0 munmap(0x7f3539b15000, 71040) = 0 getpid()= 120700 fanotify_init(FAN_CLASS_NOTIF, O_RDONLY|O_LARGEFILE) = 3 brk(NULL) = 0x55c9a1947000 brk(0x55c9a1968000) = 0x55c9a1968000 openat(AT_FDCWD, "/proc/self/mounts", O_RDONLY|O_CLOEXEC) = 4 fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 read(4, "sysfs /sys sysfs rw,nosuid,nodev"..., 1024) = 1024 access("sysfs", F_OK) = -1 ENOENT (No such file or directory) access("proc", F_OK)= -1 ENOENT (No such file or directory) access("udev", F_OK)= -1 ENOENT (No such file or directory) access("devpts", F_OK) = -1 ENOENT (No such file or directory) access("tmpfs", F_OK) = -1 ENOENT (No such file or directory) access("rpool/ROOT/ubuntu", F_OK) = -1 ENOENT (No such file or directory) access("securityfs", F_OK) = -1 ENOENT (No such file or directory) access("tmpfs", F_OK) = -1 ENOENT (No such file or directory) access("tmpfs", F_OK) = -1 ENOENT (No such file or directory) access("tmpfs", F_OK) = -1 ENOENT (No such file or directory) access("cgroup2", F_OK) = -1 ENOENT (No such file or directory) access("cgroup", F_OK) = -1 ENOENT (No such file or directory) access("pstore", F_OK) = -1 ENOENT (No such file or directory) access("efivarfs", F_OK)= -1 ENOENT (No such file or directory) read(4, "de=700 0 0\ncgroup /sys/fs/cgroup"..., 1024)
[Kernel-packages] [Bug 1951159] Re: Hirsute update: upstream stable patchset 2021-11-16
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951159 Title: Hirsute update: upstream stable patchset 2021-11-16 Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: 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: upstream stable patchset 2021-11-16 Ported from the following upstream stable releases: v5.10.72, v5.14.11 from git://git.kernel.org/ spi: rockchip: handle zero length transfers without timing out platform/x86: touchscreen_dmi: Add info for the Chuwi HiBook (CWI514) tablet platform/x86: touchscreen_dmi: Update info for the Chuwi Hi10 Plus (CWI527) tablet nfsd: back channel stuck in SEQ4_STATUS_CB_PATH_DOWN btrfs: replace BUG_ON() in btrfs_csum_one_bio() with proper error handling btrfs: fix mount failure due to past and transient device flush error net: mdio: introduce a shutdown method to mdio device drivers xen-netback: correct success/error reporting for the SKB-with-fraglist case sparc64: fix pci_iounmap() when CONFIG_PCI is not set ext2: fix sleeping in atomic bugs on error scsi: sd: Free scsi_disk device via put_device() usb: testusb: Fix for showing the connection speed usb: dwc2: check return value after calling platform_get_resource() habanalabs/gaudi: fix LBW RR configuration selftests: be sure to make khdr before other targets selftests:kvm: fix get_warnings_count() ignoring fscanf() return warn nvme-fc: update hardware queues before using them nvme-fc: avoid race between time out and tear down thermal/drivers/tsens: Fix wrong check for tzd in irq handlers scsi: ses: Retry failed Send/Receive Diagnostic commands irqchip/gic: Work around broken Renesas integration smb3: correct smb3 ACL security descriptor tools/vm/page-types: remove dependency on opt_file for idle page tracking selftests: KVM: Align SMCCC call with the spec in steal_time KVM: do not shrink halt_poll_ns below grow_start kvm: x86: Add AMD PMU MSRs to msrs_to_save_all[] KVM: x86: nSVM: restore int_vector in svm_clear_vintr perf/x86: Reset destroy callback on event init failure libata: Add ATA_HORKAGE_NO_NCQ_ON_ATI for Samsung 860 and 870 SSD. afs: Add missing vnode validation checks habanalabs/gaudi: use direct MSI in single mode habanalabs: fail collective wait when not supported block: don't call rq_qos_ops->done_bio if the bio isn't tracked kasan: always respect CONFIG_KASAN_STACK UBUNTU: upstream stable to v5.10.72, v5.14.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi-5.4/5.4.0.1047.50)
All autopkgtests for the newly accepted linux-meta-raspi-5.4 (5.4.0.1047.50) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lime-forensics/unknown (arm64) xtables-addons/unknown (arm64) lttng-modules/unknown (arm64) west-chamber/unknown (arm64) lxd/unknown (arm64) dm-writeboost/unknown (arm64) nat-rtsp/unknown (arm64) ddcci-driver-linux/unknown (arm64) systemd/unknown (arm64) langford/unknown (arm64) fwts/unknown (arm64) linux-raspi-5.4/unknown (arm64) bbswitch/0.8-4ubuntu1 (arm64) acpi-call/1.1.0-4 (arm64) ktap/unknown (arm64) rtl8812au/unknown (arm64) dpdk/unknown (arm64) glibc/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-raspi-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951440] Re: Enable INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON on jammy 5.15
** Description changed: - Starting with the following commit, upstream kernel is enabling Intel IOMMU related options by default: - - 792fb43ce2c9 ("iommu/vt-d: Enable Intel IOMMU scalable mode by default") - - We should follow upstream direction enabling INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON. - - A downside is that this change may introduce boot regressions on old systems (especially those with buggy firmware). + Starting with the following commit, upstream kernel is enabling Intel + IOMMU related options by default: + + 792fb43ce2c9 ("iommu/vt-d: Enable Intel IOMMU scalable mode by + default") + + We should follow upstream direction enabling + CONFIG_INTEL_IOMMU_DEFAULT_ON and + CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON. + + A downside is that this change may introduce boot regressions on old + systems (especially those with buggy firmware). ** Summary changed: - Enable INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON on jammy 5.15 + Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON on jammy 5.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951440 Title: Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON on jammy 5.15 Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Starting with the following commit, upstream kernel is enabling Intel IOMMU related options by default: 792fb43ce2c9 ("iommu/vt-d: Enable Intel IOMMU scalable mode by default") We should follow upstream direction enabling CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON. A downside is that this change may introduce boot regressions on old systems (especially those with buggy firmware). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951440] 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 1951440 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: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951440 Title: Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON on jammy 5.15 Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Starting with the following commit, upstream kernel is enabling Intel IOMMU related options by default: 792fb43ce2c9 ("iommu/vt-d: Enable Intel IOMMU scalable mode by default") We should follow upstream direction enabling CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON. A downside is that this change may introduce boot regressions on old systems (especially those with buggy firmware). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951440] [NEW] Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON on jammy 5.15
Public bug reported: Starting with the following commit, upstream kernel is enabling Intel IOMMU related options by default: 792fb43ce2c9 ("iommu/vt-d: Enable Intel IOMMU scalable mode by default") We should follow upstream direction enabling CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON. A downside is that this change may introduce boot regressions on old systems (especially those with buggy firmware). ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Tags: jammy ** Also affects: linux (Ubuntu Jammy) 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/1951440 Title: Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON on jammy 5.15 Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Starting with the following commit, upstream kernel is enabling Intel IOMMU related options by default: 792fb43ce2c9 ("iommu/vt-d: Enable Intel IOMMU scalable mode by default") We should follow upstream direction enabling CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON. A downside is that this change may introduce boot regressions on old systems (especially those with buggy firmware). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915
** Changed in: linux-firmware (Ubuntu Focal) Status: Confirmed => 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/1939986 Title: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Bug description: [ Impact ] The i915 driver in Focal HWE kernels (currently 5.11 and 5.13) needs new firmware blobs. Without them, some users reported display/audio issues when installing said kernel. [ Test Case ] 1) Install linux-generic-hwe-20.04 2) echo 'i915' >> /etc/initramfs-tools/modules 3) update-initramfs -u Which leads to multiple warnings: W: Possible missing firmware for module i915 [Fix ] Add missing firmware blobs from upstream linux-firmware. [ Where Problems Could Occur ] New closed-source firmware binaries, would could possibly go wrong? No display with i915, kernel crashes. [ Original Description ] Dear all, I can see that the linux-firmware is missing firmware files, in Ubuntu 20.04.1 LTS, for initramfs, when it loads i915. Package: linux-firmware 1.187.15 It contains the following files, for the module i915: i915/tgl_dmc_ver2_04.bin 2019-09-13 installed i915/tgl_dmc_ver2_06.bin 2020-03-04 installed i915/tgl_dmc_ver2_08.bin 2020-08-13 installed i915/tgl_guc_35.2.0.bin 2019-11-06 installed i915/tgl_huc_7.0.12.bin 2020-03-04 installed i915/tgl_huc_7.0.3.bin2019-11-06 installed Package: linux-firmware MUST at least contain the following files, for the module i915: i915/tgl_huc_7.5.0.bin2020-08-13 i915: Add HuC firwmare v7.5.0 for TGL as the module asks for it, during 'update-initramfs', to avoid: W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 But it COULD also contain : i915/tgl_dmc_ver2_12.bin 2021-07-28 i915: Add v2.12 DMC for TGL i915/tgl_guc_49.0.1.bin 2020-11-24 i915: Add GuC firmware v49.0.1 for all platforms i915/tgl_guc_62.0.0.bin 2021-06-29 firmware/i915/guc: Add GuC v62.0.0 for all platforms i915/tgl_huc_7.9.3.bin2021-06-29 firmware/i915/guc: Add HuC v7.9.3 for TGL & DG1 Source: $ modprobe --show-depends --ignore-install i915 ... insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko $ modinfo -F firmware /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko ... i915/tgl_dmc_ver2_08.bin i915/tgl_guc_35.2.0.bin i915/tgl_huc_7.5.0.bin Actual result: $ sudo update-initramfs -u W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 Expected result: No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915 Info : INTEL Repository of firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.15 ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46 Uname: Linux 5.10.0-1038-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1699 F pulseaudio /dev/snd/pcmC0D0p: chris 1699 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Aug 15 14:46:47 2021 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 InstallationDate: Installed on 2021-08-12 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.10.0-1038-oem N/A linux-backports-modules-5.10.0-1038-oem N/A linux-firmware 1.187.15 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2021 dmi.bios.release: 3.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.0.4 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1950968] Re: v5.15 RT kernel fails to boot on some arm64 instances
** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Jammy) 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/1950968 Title: v5.15 RT kernel fails to boot on some arm64 instances Status in linux package in Ubuntu: Triaged Status in linux source package in Jammy: Triaged Bug description: d2021.10.26/jammy/linux-realtime/5.15.0-1002.2 failed to boot on helo- kernel.arm64 without any logs. - Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-1002-realtime Found initrd image: /boot/initrd.img-5.15.0-1002-realtime Found linux image: /boot/vmlinuz-5.13.0-21-generic Found initrd image: /boot/initrd.img-5.13.0-21-generic done . Rebooting for installed Kernel meta package Traceback (most recent call last): File "/home/maas/ckct/sut-prep", line 187, in exit(app.main(args)) File "/home/maas/ckct/sut-prep", line 74, in main if instance.provision(): File "/home/maas/ckct/lib/target.py", line 1301, in provision s.reboot(progress=reboot) File "/home/maas/ckct/lib/target.py", line 621, in reboot s.wait_for_target() File "/home/maas/ckct/lib/target.py", line 173, in wait_for_target raise WaitForTarget(message) lib.target.WaitForTarget: The specified timeout (30 minutes) was reached while waiting for the target system (10.229.83.183) to come back up. WARNING - [2021-11-15 10:42:43.270713] ssh command (return): uname -vr (0) 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 09:01:50 UTC 2021 - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949357] Re: linux-azure: make mana.ko built-in
Microsoft tested. ** Tags removed: verification-needed-hirsute verification-needed-impish ** Tags added: verification-done-hirsute verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1949357 Title: linux-azure: make mana.ko built-in Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Hirsute: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] The new networking module mana.ko is not included with linux-modules, rather it is packaged in linux-modules-extra. Instance types that have mana.ko as a boot dependency will not work since Azure images are not created using linux-image-extra. [Test Plan] Download linux-modules and check for mana.ko [Where problems could occur] mana.ko could go missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1949357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947027] Re: hirsute/linux-azure: Backport CIFS patches
Microsoft tested. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1947027 Title: hirsute/linux-azure: Backport CIFS patches Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Hirsute: Fix Committed Bug description: [SRU Justification] [Impact] Microsoft has asked to backport cifs patches up through v5.15-rc3 from git://git.samba.org/sfrench/cifs-2.6.git 5.11-backport [Test Case] Connect to a SAMBA server [Where things might go wrong] Connections may fail, or have poor performance. [Other Info] SF: #00316229 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1947027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951424] 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/1951424 Title: No audio after install ubuntu 21.10 on Acer swift 3 Status in linux package in Ubuntu: Confirmed Bug description: dmesg shows below errors: (see intel-sdw lines) [3.428920] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device [3.461588] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [3.482055] sof-audio-pci-intel-tgl :00:1f.3: No SoundWire machine driver found [3.482059] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 5 [3.482061] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.482066] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [3.584389] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 1:6:0-18fab [3.584392] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:18:0 [3.586144] intel-sdw intel-sdw.0: Bus clash for control word [3.586147] intel-sdw intel-sdw.0: Bus clash for data word [3.586169] intel-sdw intel-sdw.1: Bus clash for control word [3.586171] intel-sdw intel-sdw.1: Bus clash for data word [3.586227] intel-sdw intel-sdw.0: Bus clash for control word [3.586230] intel-sdw intel-sdw.1: Bus clash for control word [3.586275] intel-sdw intel-sdw.0: Bus clash for control word [3.586279] intel-sdw intel-sdw.1: Bus clash for control word [3.586342] intel-sdw intel-sdw.0: Bus clash for control word [3.586346] intel-sdw intel-sdw.1: Bus clash for control word [3.586395] intel-sdw intel-sdw.0: Bus clash for control word [3.586398] intel-sdw intel-sdw.1: Bus clash for control word [3.593087] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:18:0 [3.610615] sof-audio-pci-intel-tgl :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred [3.640221] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.640226] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.640228] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.640229] snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 [3.640230] snd_hda_codec_realtek ehdaudio0D0:inputs: [3.688338] snd_hda_codec_realtek ehdaudio0D0: ASoC: sink widget AIF1TX overwritten [3.688344] snd_hda_codec_realtek ehdaudio0D0: ASoC: source widget AIF1RX overwritten [3.688440] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi3 overwritten [3.688444] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi2 overwritten [3.688447] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi1 overwritten [3.688450] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Codec Output Pin1 overwritten [3.688452] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Codec Input Pin1 overwritten [3.688456] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Analog Codec Playback overwritten [3.688460] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Digital Codec Playback overwritten [3.688463] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Alt Analog Codec Playback overwritten [3.688468] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Analog Codec Capture overwritten [3.688471] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Digital Codec Capture overwritten [3.688475] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Alt Analog Codec Capture overwritten [3.688482] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 3 [3.688483] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 4 [3.688484] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 5 [3.688485] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 6 [3.688486] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 7 [3.688487] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 8 [3.707637] input: sof-hda-dsp Front Headphone as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input17 [3.707683] input: sof-hda-dsp HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input18
[Kernel-packages] [Bug 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915
In my case, GuC isn’t enabled. You’re right, before Gen 11 GuC and HuC firmware aren’t loading by default, a kernel parameter need to be added. https://01.org/linuxgraphics/downloads/firmware https://wiki.gentoo.org/wiki/Intel#Feature_support Maybe news GuC/HuC firmware blobs aren’t useful for the majority? -- 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/1939986 Title: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Confirmed Bug description: [ Impact ] The i915 driver in Focal HWE kernels (currently 5.11 and 5.13) needs new firmware blobs. Without them, some users reported display/audio issues when installing said kernel. [ Test Case ] 1) Install linux-generic-hwe-20.04 2) echo 'i915' >> /etc/initramfs-tools/modules 3) update-initramfs -u Which leads to multiple warnings: W: Possible missing firmware for module i915 [Fix ] Add missing firmware blobs from upstream linux-firmware. [ Where Problems Could Occur ] New closed-source firmware binaries, would could possibly go wrong? No display with i915, kernel crashes. [ Original Description ] Dear all, I can see that the linux-firmware is missing firmware files, in Ubuntu 20.04.1 LTS, for initramfs, when it loads i915. Package: linux-firmware 1.187.15 It contains the following files, for the module i915: i915/tgl_dmc_ver2_04.bin 2019-09-13 installed i915/tgl_dmc_ver2_06.bin 2020-03-04 installed i915/tgl_dmc_ver2_08.bin 2020-08-13 installed i915/tgl_guc_35.2.0.bin 2019-11-06 installed i915/tgl_huc_7.0.12.bin 2020-03-04 installed i915/tgl_huc_7.0.3.bin2019-11-06 installed Package: linux-firmware MUST at least contain the following files, for the module i915: i915/tgl_huc_7.5.0.bin2020-08-13 i915: Add HuC firwmare v7.5.0 for TGL as the module asks for it, during 'update-initramfs', to avoid: W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 But it COULD also contain : i915/tgl_dmc_ver2_12.bin 2021-07-28 i915: Add v2.12 DMC for TGL i915/tgl_guc_49.0.1.bin 2020-11-24 i915: Add GuC firmware v49.0.1 for all platforms i915/tgl_guc_62.0.0.bin 2021-06-29 firmware/i915/guc: Add GuC v62.0.0 for all platforms i915/tgl_huc_7.9.3.bin2021-06-29 firmware/i915/guc: Add HuC v7.9.3 for TGL & DG1 Source: $ modprobe --show-depends --ignore-install i915 ... insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko $ modinfo -F firmware /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko ... i915/tgl_dmc_ver2_08.bin i915/tgl_guc_35.2.0.bin i915/tgl_huc_7.5.0.bin Actual result: $ sudo update-initramfs -u W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 Expected result: No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915 Info : INTEL Repository of firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.15 ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46 Uname: Linux 5.10.0-1038-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1699 F pulseaudio /dev/snd/pcmC0D0p: chris 1699 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Aug 15 14:46:47 2021 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 InstallationDate: Installed on 2021-08-12 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.10.0-1038-oem N/A linux-backports-modules-5.10.0-1038-oem N/A linux-firmware 1.187.15 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2021 dmi.bios.release: 3.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.0.4 dmi.board.name: 08607K dmi.board.vendor:
[Kernel-packages] [Bug 1951424] [NEW] No audio after install ubuntu 21.10 on Acer swift 3
Public bug reported: dmesg shows below errors: (see intel-sdw lines) [3.428920] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device [3.461588] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [3.482055] sof-audio-pci-intel-tgl :00:1f.3: No SoundWire machine driver found [3.482059] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 5 [3.482061] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.482066] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [3.584389] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 1:6:0-18fab [3.584392] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:18:0 [3.586144] intel-sdw intel-sdw.0: Bus clash for control word [3.586147] intel-sdw intel-sdw.0: Bus clash for data word [3.586169] intel-sdw intel-sdw.1: Bus clash for control word [3.586171] intel-sdw intel-sdw.1: Bus clash for data word [3.586227] intel-sdw intel-sdw.0: Bus clash for control word [3.586230] intel-sdw intel-sdw.1: Bus clash for control word [3.586275] intel-sdw intel-sdw.0: Bus clash for control word [3.586279] intel-sdw intel-sdw.1: Bus clash for control word [3.586342] intel-sdw intel-sdw.0: Bus clash for control word [3.586346] intel-sdw intel-sdw.1: Bus clash for control word [3.586395] intel-sdw intel-sdw.0: Bus clash for control word [3.586398] intel-sdw intel-sdw.1: Bus clash for control word [3.593087] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:18:0 [3.610615] sof-audio-pci-intel-tgl :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred [3.640221] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.640226] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.640228] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.640229] snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 [3.640230] snd_hda_codec_realtek ehdaudio0D0:inputs: [3.688338] snd_hda_codec_realtek ehdaudio0D0: ASoC: sink widget AIF1TX overwritten [3.688344] snd_hda_codec_realtek ehdaudio0D0: ASoC: source widget AIF1RX overwritten [3.688440] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi3 overwritten [3.688444] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi2 overwritten [3.688447] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi1 overwritten [3.688450] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Codec Output Pin1 overwritten [3.688452] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Codec Input Pin1 overwritten [3.688456] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Analog Codec Playback overwritten [3.688460] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Digital Codec Playback overwritten [3.688463] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Alt Analog Codec Playback overwritten [3.688468] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Analog Codec Capture overwritten [3.688471] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Digital Codec Capture overwritten [3.688475] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Alt Analog Codec Capture overwritten [3.688482] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 3 [3.688483] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 4 [3.688484] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 5 [3.688485] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 6 [3.688486] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 7 [3.688487] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 8 [3.707637] input: sof-hda-dsp Front Headphone as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input17 [3.707683] input: sof-hda-dsp HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input18 [3.707715] input: sof-hda-dsp HDMI/DP,pcm=4 as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input19 [3.707769] input: sof-hda-dsp HDMI/DP,pcm=5 as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input20 [4.195918] Bluetooth: hci0: Waiting for firmware download to complete [4.197511] Bluetooth: hci0: Firmware loaded in 1706912 usecs [4.197548] Bluetooth: hci0: Waiting for device to boot [4.212520] Bluetooth:
[Kernel-packages] [Bug 1951422] [NEW] Ucore kernel snap size: netronome smartnic fw
Public bug reported: The size of the pi-kernel snap for UC20 is 254Mbytes (compressed) and 794Mbytes (uncompressed). 569Mbyte of this is caused by FW 140Mbyte -> Netronome SmartNIC Removing unreferenced FW and/or reducing number of drivers & their FW has exponential reduction of disk space usage. Additionally, downloaded image will be smaller; and storing 3x kernel snaps for upgrades will be smaller. Even more, snap seeding will be faster, so boot time will be faster. So it will be a nice gain in multiple aspects: download image, boot image, upgrade image, reboot image, start using image. stulluk ~/tmp $ ls -lah pi-kernel_353.snap -rw--- 1 stulluk stulluk 254M Kas 8 13:57 pi-kernel_353.snap stulluk ~/tmp $ cd pikern/ stulluk ~/tmp/pikern $ du -sh 794M. stulluk ~/tmp/pikern $ cd firmware/ stulluk ~/tmp/pikern/firmware $ du --block-size=MiB --max-depth=1 . | sort -rn 569MiB . 140MiB ./netronome 40MiB ./amdgpu 34MiB ./intel 25MiB ./liquidio 24MiB ./qcom 20MiB ./qed 19MiB ./brcm 12MiB ./mellanox 12MiB ./dpaa2 12MiB ./ath10k ... ** 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/1951422 Title: Ucore kernel snap size: netronome smartnic fw Status in linux-raspi package in Ubuntu: New Bug description: The size of the pi-kernel snap for UC20 is 254Mbytes (compressed) and 794Mbytes (uncompressed). 569Mbyte of this is caused by FW 140Mbyte -> Netronome SmartNIC Removing unreferenced FW and/or reducing number of drivers & their FW has exponential reduction of disk space usage. Additionally, downloaded image will be smaller; and storing 3x kernel snaps for upgrades will be smaller. Even more, snap seeding will be faster, so boot time will be faster. So it will be a nice gain in multiple aspects: download image, boot image, upgrade image, reboot image, start using image. stulluk ~/tmp $ ls -lah pi-kernel_353.snap -rw--- 1 stulluk stulluk 254M Kas 8 13:57 pi-kernel_353.snap stulluk ~/tmp $ cd pikern/ stulluk ~/tmp/pikern $ du -sh 794M . stulluk ~/tmp/pikern $ cd firmware/ stulluk ~/tmp/pikern/firmware $ du --block-size=MiB --max-depth=1 . | sort -rn 569MiB. 140MiB./netronome 40MiB ./amdgpu 34MiB ./intel 25MiB ./liquidio 24MiB ./qcom 20MiB ./qed 19MiB ./brcm 12MiB ./mellanox 12MiB ./dpaa2 12MiB ./ath10k ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1951422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951423] [NEW] Ucore kernel snap size: amd gpu fw
Public bug reported: The size of the kernel snap for UC20 is 254Mbytes (compressed) and 794Mbytes (uncompressed). 569Mbyte of this is caused by FW 40Mbyte -> amdgpu IMO, removing unreferenced FW and/or reducing number of drivers & their FW has exponential reduction of disk space usage. Additionally, downloaded image will be smaller; and storing 3x kernel snaps for upgrades will be smaller. Even more, snap seeding will be faster, so boot time will be faster. So it will be a nice gain in multiple aspects: download image, boot image, upgrade image, reboot image, start using image. stulluk ~/tmp $ ls -lah pi-kernel_353.snap -rw--- 1 stulluk stulluk 254M Kas 8 13:57 pi-kernel_353.snap stulluk ~/tmp $ cd pikern/ stulluk ~/tmp/pikern $ du -sh 794M. stulluk ~/tmp/pikern $ cd firmware/ stulluk ~/tmp/pikern/firmware $ du --block-size=MiB --max-depth=1 . | sort -rn 569MiB . 140MiB ./netronome 40MiB ./amdgpu 34MiB ./intel 25MiB ./liquidio 24MiB ./qcom 20MiB ./qed 19MiB ./brcm 12MiB ./mellanox 12MiB ./dpaa2 12MiB ./ath10k ... ** 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/1951423 Title: Ucore kernel snap size: amd gpu fw Status in linux-raspi package in Ubuntu: New Bug description: The size of the kernel snap for UC20 is 254Mbytes (compressed) and 794Mbytes (uncompressed). 569Mbyte of this is caused by FW 40Mbyte -> amdgpu IMO, removing unreferenced FW and/or reducing number of drivers & their FW has exponential reduction of disk space usage. Additionally, downloaded image will be smaller; and storing 3x kernel snaps for upgrades will be smaller. Even more, snap seeding will be faster, so boot time will be faster. So it will be a nice gain in multiple aspects: download image, boot image, upgrade image, reboot image, start using image. stulluk ~/tmp $ ls -lah pi-kernel_353.snap -rw--- 1 stulluk stulluk 254M Kas 8 13:57 pi-kernel_353.snap stulluk ~/tmp $ cd pikern/ stulluk ~/tmp/pikern $ du -sh 794M . stulluk ~/tmp/pikern $ cd firmware/ stulluk ~/tmp/pikern/firmware $ du --block-size=MiB --max-depth=1 . | sort -rn 569MiB. 140MiB./netronome 40MiB ./amdgpu 34MiB ./intel 25MiB ./liquidio 24MiB ./qcom 20MiB ./qed 19MiB ./brcm 12MiB ./mellanox 12MiB ./dpaa2 12MiB ./ath10k ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1951423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
I have the same issue on: Dell E5495 AMD Ryzen 7 PRO 2700U w/ Radeon Vega Mobile Gfx 16Gb RAM Linux Mint 19.3 (Ubuntu 18.04) Kernel 5.15.2 Linux Firmware 1.173.20 -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913188] Re: linux-hwe 4.15.0-133.137~16.04.1 ADT test failure with linux-hwe ubuntu_qrt_kernel_panic
** Tags added: bionic sru-20211108 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1913188 Title: linux-hwe 4.15.0-133.137~16.04.1 ADT test failure with linux-hwe ubuntu_qrt_kernel_panic Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in linux-hwe package in Ubuntu: New Bug description: Happened at least once before on 4.15.0-126.129~16.04.1 Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux-hwe/20210123_133436_7de7b@/log.gz 09:19:41 INFO | Test suite HEAD SHA1: 7ccda2e 09:19:43 INFO | GOODubuntu_qrt_kernel_panic.setup ubuntu_qrt_kernel_panic.setup timestamp=1611393583localtime=Jan 23 09:19:43 completed successfully 09:19:43 INFO | END GOODubuntu_qrt_kernel_panic.setup ubuntu_qrt_kernel_panic.setup timestamp=1611393583localtime=Jan 23 09:19:43 09:19:43 DEBUG| Persistent state client._record_indent now set to 1 09:19:43 DEBUG| Persistent state client.unexpected_reboot deleted 09:19:43 DEBUG| Test has timeout: 1200 sec. 09:19:43 INFO | START ubuntu_qrt_kernel_panic.test-kernel-panic.py ubuntu_qrt_kernel_panic.test-kernel-panic.pytimestamp=1611393583 timeout=1200localtime=Jan 23 09:19:43 09:19:43 DEBUG| Persistent state client._record_indent now set to 2 09:19:43 DEBUG| Persistent state client.unexpected_reboot now set to ('ubuntu_qrt_kernel_panic.test-kernel-panic.py', 'ubuntu_qrt_kernel_panic.test-kernel-panic.py') 09:19:43 DEBUG| Waiting for pid 4648 for 1200 seconds 09:19:43 DEBUG| Running 'python2 ./test-kernel-panic.py -v' 09:19:43 DEBUG| [stdout] Running test: './test-kernel-panic.py' distro: 'Ubuntu 16.04' kernel: '4.15.0-133.137~16.04.1 (Ubuntu 4.15.0-133.137~16.04.1-generic 4.15.18)' arch: 'i386' uid: 0/0 SUDO_USER: 'ubuntu') 09:19:43 ERROR| [stderr] test_cve_2013_2094 (__main__.KernelPanicTest) 09:19:43 DEBUG| [stdout] Skipping private tests 09:19:43 ERROR| [stderr] test linux kernel perf out-of-bounds access (CVE-2013-2094) ... (skipped: test works on amd64 only) ok 09:19:43 ERROR| [stderr] test_cve_2015_7550 (__main__.KernelPanicTest) 09:19:43 DEBUG| [stdout] 09:39:45 INFO | Timer expired (1200 sec.), nuking pid 4648 09:39:46 INFO | ERROR ubuntu_qrt_kernel_panic.test-kernel-panic.py ubuntu_qrt_kernel_panic.test-kernel-panic.pytimestamp=1611394786 localtime=Jan 23 09:39:46 Test timeout expired, rc=15 09:39:46 INFO | END ERROR ubuntu_qrt_kernel_panic.test-kernel-panic.py ubuntu_qrt_kernel_panic.test-kernel-panic.pytimestamp=1611394786 localtime=Jan 23 09:39:46 09:39:46 DEBUG| Persistent state client._record_indent now set to 1 09:39:46 DEBUG| Persistent state client.unexpected_reboot deleted 09:39:46 INFO | END GOOD timestamp=1611394786 localtime=Jan 23 09:39:46 To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1913188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951390] Re: update iproute2 in jammy
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1951390 Title: update iproute2 in jammy Status in iproute2 package in Ubuntu: New Status in iproute2 source package in Jammy: New Bug description: [Impact] Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6 In-situ OAM (IOAM6). [Test case] This lack of support is triggering the following kernel selftest failure: # selftests: net: ioam6.sh # SKIP: iproute2 too old, missing ioam command not ok 1 selftests: net: ioam6.sh # exit=1 [Fix] We're still using iproute2 v5.10 in jammy. It'd be nice to update to the latest upstream version (v5.15) to properly support this new kernel feature (and more). [Regression potential] We may introduce networking regressions with this change, because we are jumping from iproute2 5.10 to 5.15. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Thanks @arighi Having the ISO updated is just for other people's user experience. If they try and appears a black screen and then it reboots.. they may go back to Windows. I don't know how difficult is to show an error message (like the one that appears in recovery mode but without previous verbose) in those cases recommending to try other version. In my case, I deal with the problem working with 20.04 with 5.13.0-1010-oem kernel (the only drawback is that Virtualbox is not compatible, so I have to wait till the fixed kernel is supported by them). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Status in linux source package in Jammy: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951109] Re: [UBUNTU 20.04] kvm: floating interrupts may get stuck
--- Comment From boris.m...@de.ibm.com 2021-11-18 06:36 EDT--- Patch is included in v5.4.146 upstream stable release-updates which was already rolled out for focal. Therefore closing the bug. IBM status update: CLOSED ** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin2004 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951109 Title: [UBUNTU 20.04] kvm: floating interrupts may get stuck Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Description: kvm: floating interrupts may get stuck Symptom: Most prominently guest stuck in IPL. Problem: When trying to pick an idle cpu to process the interrupts we can end up messing up, and picking, for example a stopped vcpu, because we first look up an index form the kvm->arch.idle_mask and then use it to obtain a cpu using kvm_get_vcpu() The trouble is, we made kvm->arch.idle_mask to be indexed with cpu_id, while kvm_get_vcpu() expects a vcpu_idx. Hereby vcpu_id is an identifier that comes from userspace, while vcpu_idx'es are given away at vcpu creation FCFS. In practice QEMU does currently the creation of vcpus so that the two end up having the same value. That is why we did not notice this problem for years. Reproduction: Make sure you cpu_id's and cpu_idx'es aren't the same, and try to IPL a guest. Solution: Make kvm->arch.idle_mask cpu_idx based. Upstream-ID: a3e03bc1368c1bc16e19b001fc96dc7430573cc8 Date: 2021-09-09 Author:Halil Pasic Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1951109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951390] Re: update iproute2 in jammy
debdiff against Debian iproute2 5.15.0-1 (re-applied Ubuntu Fan driver). v2: added this tracking bug to the changelog entry. ** Patch added: "iproute2-update-to-5.15-v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+attachment/5541717/+files/iproute2-update-to-5.15-v2.debdiff ** Description changed: + [Impact] + Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6 - In-situ OAM (IOAM6). This lack of support is also triggering the - following kernel selftest failure: + In-situ OAM (IOAM6). - # selftests: net: ioam6.sh - # SKIP: iproute2 too old, missing ioam command - not ok 1 selftests: net: ioam6.sh # exit=1 + [Test case] + + This lack of support is triggering the following kernel selftest + failure: + + # selftests: net: ioam6.sh + # SKIP: iproute2 too old, missing ioam command + not ok 1 selftests: net: ioam6.sh # exit=1 + + [Fix] We're still using iproute2 v5.10 in jammy. It'd be nice to update to the latest upstream version (v5.15) to properly support this new kernel feature (and more). + + [Regression potential] + + We may introduce networking regressions with this change, because we are + jumping from iproute2 5.10 to 5.15. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1951390 Title: update iproute2 in jammy Status in iproute2 package in Ubuntu: New Status in iproute2 source package in Jammy: New Bug description: [Impact] Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6 In-situ OAM (IOAM6). [Test case] This lack of support is triggering the following kernel selftest failure: # selftests: net: ioam6.sh # SKIP: iproute2 too old, missing ioam command not ok 1 selftests: net: ioam6.sh # exit=1 [Fix] We're still using iproute2 v5.10 in jammy. It'd be nice to update to the latest upstream version (v5.15) to properly support this new kernel feature (and more). [Regression potential] We may introduce networking regressions with this change, because we are jumping from iproute2 5.10 to 5.15. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951390] Re: update iproute2 in jammy
** Patch added: "iproute2-update-to-5.15.debdiff" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+attachment/5541716/+files/iproute2-update-to-5.15.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1951390 Title: update iproute2 in jammy Status in iproute2 package in Ubuntu: New Status in iproute2 source package in Jammy: New Bug description: [Impact] Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6 In-situ OAM (IOAM6). [Test case] This lack of support is triggering the following kernel selftest failure: # selftests: net: ioam6.sh # SKIP: iproute2 too old, missing ioam command not ok 1 selftests: net: ioam6.sh # exit=1 [Fix] We're still using iproute2 v5.10 in jammy. It'd be nice to update to the latest upstream version (v5.15) to properly support this new kernel feature (and more). [Regression potential] We may introduce networking regressions with this change, because we are jumping from iproute2 5.10 to 5.15. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951390] Re: update iproute2 in jammy
** Also affects: iproute2 (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1951390 Title: update iproute2 in jammy Status in iproute2 package in Ubuntu: New Status in iproute2 source package in Jammy: New Bug description: Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6 In-situ OAM (IOAM6). This lack of support is also triggering the following kernel selftest failure: # selftests: net: ioam6.sh # SKIP: iproute2 too old, missing ioam command not ok 1 selftests: net: ioam6.sh # exit=1 We're still using iproute2 v5.10 in jammy. It'd be nice to update to the latest upstream version (v5.15) to properly support this new kernel feature (and more). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915
Are you all enabling GuC manually? It's not used by default on any currently shipping GPU. Having them around is harmless though, because while they get loaded (fixing the warning), they are not actually used. -- 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/1939986 Title: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Confirmed Bug description: [ Impact ] The i915 driver in Focal HWE kernels (currently 5.11 and 5.13) needs new firmware blobs. Without them, some users reported display/audio issues when installing said kernel. [ Test Case ] 1) Install linux-generic-hwe-20.04 2) echo 'i915' >> /etc/initramfs-tools/modules 3) update-initramfs -u Which leads to multiple warnings: W: Possible missing firmware for module i915 [Fix ] Add missing firmware blobs from upstream linux-firmware. [ Where Problems Could Occur ] New closed-source firmware binaries, would could possibly go wrong? No display with i915, kernel crashes. [ Original Description ] Dear all, I can see that the linux-firmware is missing firmware files, in Ubuntu 20.04.1 LTS, for initramfs, when it loads i915. Package: linux-firmware 1.187.15 It contains the following files, for the module i915: i915/tgl_dmc_ver2_04.bin 2019-09-13 installed i915/tgl_dmc_ver2_06.bin 2020-03-04 installed i915/tgl_dmc_ver2_08.bin 2020-08-13 installed i915/tgl_guc_35.2.0.bin 2019-11-06 installed i915/tgl_huc_7.0.12.bin 2020-03-04 installed i915/tgl_huc_7.0.3.bin2019-11-06 installed Package: linux-firmware MUST at least contain the following files, for the module i915: i915/tgl_huc_7.5.0.bin2020-08-13 i915: Add HuC firwmare v7.5.0 for TGL as the module asks for it, during 'update-initramfs', to avoid: W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 But it COULD also contain : i915/tgl_dmc_ver2_12.bin 2021-07-28 i915: Add v2.12 DMC for TGL i915/tgl_guc_49.0.1.bin 2020-11-24 i915: Add GuC firmware v49.0.1 for all platforms i915/tgl_guc_62.0.0.bin 2021-06-29 firmware/i915/guc: Add GuC v62.0.0 for all platforms i915/tgl_huc_7.9.3.bin2021-06-29 firmware/i915/guc: Add HuC v7.9.3 for TGL & DG1 Source: $ modprobe --show-depends --ignore-install i915 ... insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko $ modinfo -F firmware /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko ... i915/tgl_dmc_ver2_08.bin i915/tgl_guc_35.2.0.bin i915/tgl_huc_7.5.0.bin Actual result: $ sudo update-initramfs -u W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 Expected result: No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915 Info : INTEL Repository of firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.15 ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46 Uname: Linux 5.10.0-1038-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1699 F pulseaudio /dev/snd/pcmC0D0p: chris 1699 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Aug 15 14:46:47 2021 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 InstallationDate: Installed on 2021-08-12 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.10.0-1038-oem N/A linux-backports-modules-5.10.0-1038-oem N/A linux-firmware 1.187.15 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2021 dmi.bios.release: 3.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.0.4 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc.
[Kernel-packages] [Bug 1690085]
Thanks for sharing your wealthy information. This is one of the excellent posts. It is great to have the opportunity to read a good quality article with useful information. https://technologycounter.com/hr-software/india -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups:
[Kernel-packages] [Bug 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915
** Description changed: + [ Impact ] + + The i915 driver in Focal HWE kernels (currently 5.11 and 5.13) needs new + firmware blobs. Without them, some users reported display/audio issues + when installing said kernel. + + + [ Test Case ] + + 1) Install linux-generic-hwe-20.04 + 2) echo 'i915' >> /etc/initramfs-tools/modules + 3) update-initramfs -u + + Which leads to multiple warnings: + W: Possible missing firmware for module i915 + + + [Fix ] + + Add missing firmware blobs from upstream linux-firmware. + + + [ Where Problems Could Occur ] + + New closed-source firmware binaries, would could possibly go wrong? No + display with i915, kernel crashes. + + + [ Original Description ] Dear all, I can see that the linux-firmware is missing firmware files, in Ubuntu 20.04.1 LTS, for initramfs, when it loads i915. Package: linux-firmware 1.187.15 It contains the following files, for the module i915: i915/tgl_dmc_ver2_04.bin 2019-09-13 installed i915/tgl_dmc_ver2_06.bin 2020-03-04 installed i915/tgl_dmc_ver2_08.bin 2020-08-13 installed i915/tgl_guc_35.2.0.bin 2019-11-06 installed i915/tgl_huc_7.0.12.bin 2020-03-04 installed i915/tgl_huc_7.0.3.bin2019-11-06 installed Package: linux-firmware MUST at least contain the following files, for the module i915: i915/tgl_huc_7.5.0.bin2020-08-13 i915: Add HuC firwmare v7.5.0 for TGL as the module asks for it, during 'update-initramfs', to avoid: W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 - But it COULD also contain : + But it COULD also contain : i915/tgl_dmc_ver2_12.bin 2021-07-28 i915: Add v2.12 DMC for TGL i915/tgl_guc_49.0.1.bin 2020-11-24 i915: Add GuC firmware v49.0.1 for all platforms i915/tgl_guc_62.0.0.bin 2021-06-29 firmware/i915/guc: Add GuC v62.0.0 for all platforms i915/tgl_huc_7.9.3.bin2021-06-29 firmware/i915/guc: Add HuC v7.9.3 for TGL & DG1 - Source: + Source: $ modprobe --show-depends --ignore-install i915 ... - insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko + insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko $ modinfo -F firmware /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko ... i915/tgl_dmc_ver2_08.bin i915/tgl_guc_35.2.0.bin i915/tgl_huc_7.5.0.bin Actual result: $ sudo update-initramfs -u W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 - Expected result: No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915 - Info : INTEL Repository of firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.15 ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46 Uname: Linux 5.10.0-1038-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: chris 1699 F pulseaudio - /dev/snd/pcmC0D0p: chris 1699 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: chris 1699 F pulseaudio + /dev/snd/pcmC0D0p: chris 1699 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Aug 15 14:46:47 2021 Dependencies: - + DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 InstallationDate: Installed on 2021-08-12 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.10.0-1038-oem N/A - linux-backports-modules-5.10.0-1038-oem N/A - linux-firmware 1.187.15 + linux-restricted-modules-5.10.0-1038-oem N/A + linux-backports-modules-5.10.0-1038-oem N/A + linux-firmware 1.187.15 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: - + dmi.bios.date: 07/16/2021 dmi.bios.release: 3.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.0.4 dmi.board.name: 08607K
[Kernel-packages] [Bug 1859592] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541691/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541698/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541695/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541692/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541684/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541693/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541683/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541687/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541694/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541690/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541685/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541701/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541688/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541696/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541689/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541699/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541700/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541697/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5541686/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gad1821 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:64d2 Microdia Integrated Webcam Bus 001 Device 002: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E5570 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=fc8f615e-1d7e-4e0a-a8ce-a0655746f51c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-40-generic N/A linux-backports-modules-5.11.0-40-generic N/A linux-firmware 1.197.3 Tags: wayland-session hirsute Uname: Linux 5.11.0-40-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-07-16 (124 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/02/2019 dmi.bios.release: 1.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.6 dmi.board.name: 0N98Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.6:bd10/02/2019:br1.21:svnDellInc.:pnLatitudeE5570:pvr:sku06DF:rvnDellInc.:rn0N98Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E5570 dmi.product.sku: 06DF dmi.sys.vendor: Dell Inc. ** Tags added: hirsute wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951390] [NEW] update iproute2 in jammy
Public bug reported: Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6 In-situ OAM (IOAM6). This lack of support is also triggering the following kernel selftest failure: # selftests: net: ioam6.sh # SKIP: iproute2 too old, missing ioam command not ok 1 selftests: net: ioam6.sh # exit=1 We're still using iproute2 v5.10 in jammy. It'd be nice to update to the latest upstream version (v5.15) to properly support this new kernel feature (and more). ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1951390 Title: update iproute2 in jammy Status in iproute2 package in Ubuntu: New Bug description: Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6 In-situ OAM (IOAM6). This lack of support is also triggering the following kernel selftest failure: # selftests: net: ioam6.sh # SKIP: iproute2 too old, missing ioam command not ok 1 selftests: net: ioam6.sh # exit=1 We're still using iproute2 v5.10 in jammy. It'd be nice to update to the latest upstream version (v5.15) to properly support this new kernel feature (and more). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp