[Kernel-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop
This impacts all arm64 installs, not just raspberry pi. The MIR for qrtr and protection-domain-mapper [0] was requested late in the Mantic cycle and was only approved by Security since it was promised to only be used for x13s hardware enablement. Hopefully Qualcomm IPC is only enabled for x13s kernels. As noted in the qrtr MIR: > We should be cautious of IPC routers running root permissions. Similar code > has > enabled vendor backdoors [1]. Furthermore, qrtr has nearly no documentation and has no inline code comments [2]. Please remove this from the mantic and noble's ubuntu-meta package. [0] https://bugs.launchpad.net/ubuntu/+source/qrtr/+bug/2038942 [1] https://redmine.replicant.us/projects/replicant/wiki/samsunggalaxybackdoor [2] https://github.com/linux-msm/qrtr -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063308] Re: lenovo p1g5 suspend issues with docking stations
Can we get the system config details please - CPU, GPU in particular. Also confirm if WWAN is enabled Which dock is being used? Can you confirm if AMT is enabled or not in the BIOS? We've seen issues with AMT enabled with the TBT dock, especially with networking. Will look to reproduce the issue with high power numbers after the ME FW update - agreed that looks like a FW issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2063308 Title: lenovo p1g5 suspend issues with docking stations Status in linux package in Ubuntu: Triaged Bug description: Lenovo Docking Station Issue with Ubuntu 22.04 Sleep mode Recovery Hello, We are having trouble with our lenovo p1 laptops docking stations. When waking from suspend on Ubuntu with a docking station is an issue for some users even with Intel AMT disabled in BIOS. The exact steps to reproduce are as follows: 1) Suspend/sleep the laptop 2) Plug the docking station into the laptop 3) Wake the laptop The sleep settings in BIOS are set to Linux S3. Docking station issues, such as Ethernet not working after waking, do not occur with Windows/Linux sleep settings, but the laptop doesn't properly suspend processes in Windows/Linux sleep mode and will overheat the laptop when in an enclosed space such as a bag. Linux S3 is the only way we've found laptops to not overheat after suspending, but we that makes the dock inoperable after waking from suspend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1231178] Re: Altec Lansing speakers remote control not working
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1231178 Title: Altec Lansing speakers remote control not working Status in linux package in Ubuntu: Confirmed Bug description: This has been ongoing since 2010 ... I initially thought that it was a hardware (Altec-Lansing speakers and/or Altec-Lansing remote control) issue, but noting the timing of linux header updates (remote intermittently working: range ~20 minutes to a couple of weeks or more working, interspaced with prolonged periods - up to 6+ months NOT working), I believe it is linux (Ubuntu) problem. == From: Altec Lansing Customer Service Subject: Request received: Wireless remote not workling (VS 4221 speakers) (ticket #1630) Date: Fri, 4 Nov 2011 19:46:44 + Request received: Wireless remote not workling (VS 4221 speakers) (ticket #1630) Hi - Your request (#1630) has been received, and is being reviewed by our support staff. -- Hello: I have the VS 4221 speakers and two of the wireless remotes; neither of the remotes works, even with new button batteries. I cannot change the treble/bass, etc. Restarting my computer has no effect, nor doe unplugging the speakers (electrical outlet), then plugging them back in again. == - Original Message(s): - Date: 2010 Apr 24 (Sat) 14:02 From: "Altec Lansing Support" Subject: Altec Lansing vs4221 remote does not work [Incident: 100425-06] Your question has been received. You should expect a response from us within 72 hours. To access your question from our support site, click the following link or paste it into your web browser. http://alteclansing.custhelp.com/cgi- bin/alteclansing.cfg/php/enduser/acct_login.php?p_next_page=myq_upd.php_iid=477391_created=1272142931 Question Reference #100425-06 Summary: Altec Lansing VS4221 remote does not work Product Level 1: Powered Audio Product Level 2: Satellite Speaker System Date Created: 04/24/2010 02:02 PM Last Updated: 04/24/2010 02:02 PM Status: Unresolved Date of Purchase: 11/13/2009 First Name : Victoria Region: Canada Discussion Thread: Customer (Victoria S) - 04/24/2010 02:02 PM April 24, 2010 Hi: I purchased these speakers (VS4221) in Nov. 2009. This week, the remote suddenly stopped working; I thought it was the battery, but a fresh (new) battery did nothing: the remote still fails to work, at all. I cannot use the standby function,or more importantly adjust bass / treble. Please advise. Thanks, Victoria === ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-53-generic 3.2.0-53.81 ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50 Uname: Linux 3.2.0-53-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: victoria 2169 F pulseaudio /dev/snd/controlC0: victoria 2169 F pulseaudio /dev/snd/pcmC0D0p: victoria 2169 F...m pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xeb22 irq 48' Mixer name : 'SigmaTel STAC9271D' Components : 'HDA:83847627,80863001,00100201' Controls : 44 Simple ctrls : 25 Card1.Amixer.info: Card hw:1 'U0x46d0x825'/'USB Device 0x46d:0x825 at usb-:00:1a.7-6.1, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:0825' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 6144 Mono: Capture 4608 [75%] [24.00dB] [on] Date: Wed Sep 25 15:49:08 2013 HibernationDevice: RESUME=UUID=91c758d2-001a-4a17-baba-f49fb267dd6f InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) IwConfig: lono wireless extensions. eth0 no wireless extensions. MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-53-generic root=UUID=7dfce011-0edb-4c59-af1c-88e4f3b85c0e ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.2.0-53-generic N/A linux-backports-modules-3.2.0-53-generic N/A linux-firmware1.79.6 RfKill: SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2008
[Kernel-packages] [Bug 1884207] Re: Wifi Enterprice Login Page does not appear at connect
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884207 Title: Wifi Enterprice Login Page does not appear at connect Status in linux package in Ubuntu: Confirmed Bug description: Wifi Enterprice Login Page does not appear at connect. Therefore I cannot log in into my enterprice. Our Enterprice has a wifi where employees can login , after connect to the SID a loginpage should appear somewhere , or at least at the first request in a browser. Does not workin in Firefox (newest) and not in Chrome (newest) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 4416 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 09:51:01 2020 InstallationDate: Installed on 2019-05-16 (399 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=d4e13886-b582-4019-bf6a-200113126da3 ro mem_sleep_default=deep nouveau.modeset=0 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-03 (15 days ago) dmi.bios.date: 04/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.2 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.2:bd04/21/2020:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 927225] Re: Yukon Optima 88E8059 fails to come up as a network interface when system is powered on without AC or network cable
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/927225 Title: Yukon Optima 88E8059 fails to come up as a network interface when system is powered on without AC or network cable Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Bug description: I'm sure I've seen a bug report regarding this before, but I've searched and have been unable to find it, and it has occurred in both Oneiric and now Precise. On my laptop, an HP ProBook 6555b, using a Yukon Optima 88E8059, if I do not have the charger or a network cable plugged in when I power the machine on, I am unable to use the wired network port; I have to shut down the machine and plug AC or a network cable in before powering it up again. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-12-generic 3.2.0-12.21 ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 Uname: Linux 3.2.0-12-generic x86_64 NonfreeKernelModules: wl fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.91-0ubuntu1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dave 2152 F pulseaudio /dev/snd/controlC0: dave 2152 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xd650 irq 16' Mixer name : 'IDT 92HD75B3X5' Components : 'HDA:111d7603,103c1457,00100202 HDA:11c11040,103c3066,00100200' Controls : 18 Simple ctrls : 9 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd641 irq 19' Mixer name : 'ATI RS690/780 HDMI' Components : 'HDA:1002791a,00791a00,0010' Controls : 4 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Sun Feb 5 17:07:09 2012 HibernationDevice: RESUME=UUID=08571619-07bd-4539-aaa1-abf52c468bbe InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426) MachineType: Hewlett-Packard HP ProBook 6555b ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-12-generic root=/dev/mapper/sda1_crypt ro quiet splash acpi_os_name=Linux vt.handoff=7 PulseSinks: Error: command ['pacmd', 'list-sinks'] failed with exit code 1: Home directory /home/dave not ours. No PulseAudio daemon running, or not running as session daemon. PulseSources: Error: command ['pacmd', 'list-sources'] failed with exit code 1: Home directory /home/dave not ours. No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.2.0-12-generic N/A linux-backports-modules-3.2.0-12-generic N/A linux-firmware1.68 SourcePackage: linux UpgradeStatus: Upgraded to precise on 2012-02-05 (0 days ago) dmi.bios.date: 01/26/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68DTM Ver. F.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1455 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 75.11 dmi.chassis.asset.tag: CNU1072YY7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68DTMVer.F.07:bd01/26/2011:svnHewlett-Packard:pnHPProBook6555b:pvr:rvnHewlett-Packard:rn1455:rvrKBCVersion75.11:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6555b dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/927225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696859] Re: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696859 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: ... ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnnybegood 1415 F pulseaudio /dev/snd/controlC1: johnnybegood 1415 F pulseaudio Date: Wed Jun 7 06:52:02 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=8e8fcdb0-767f-4fa7-a8e3-e06bf12ae742 InstallationDate: Installed on 2017-04-15 (53 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=9056280d-1b43-47b6-b5ed-5b796780a968 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M77 Ver. 01.14 dmi.board.name: 2271 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.50 dmi.chassis.asset.tag: 5CG5517PNY dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM77Ver.01.14:bd09/26/2016:svnHewlett-Packard:pnHPEliteBookFolio1020G1:pvrA3009FD18303:rvnHewlett-Packard:rn2271:rvrKBCVersion91.50:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook Folio 1020 G1 dmi.product.version: A3009FD18303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696859/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919150] Re: My keyboard stop working
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1919150 Title: My keyboard stop working Status in linux package in Ubuntu: Confirmed Bug description: I am using UBUNTU 18. My keyboard and mouse do not work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-136-generic 4.15.0-136.140 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: elham 1797 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Mar 15 13:24:06 2021 HibernationDevice: RESUME=UUID=0cd3cd69-2564-4117-a21b-1c28c2a83019 InstallationDate: Installed on 2018-11-15 (850 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20L8S02D00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-136-generic root=UUID=17a0324e-ead9-4861-bdd0-60ece73973f5 ro quiet splash atkbd.reset vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-136-generic N/A linux-backports-modules-4.15.0-136-generic N/A linux-firmware 1.173.18 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET48W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET48W(1.25):bd07/18/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904391] Re: Touchpad and Keyboard not detectable in the new kernel
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904391 Title: Touchpad and Keyboard not detectable in the new kernel Status in linux package in Ubuntu: Confirmed Bug description: Hello! I had to abruptly shutdown my pc while update for new groovy was on. Upon rebooting, the touchpad and keyboard is not detectable in the new kernel. They're working fine in older kernel which I had to select in boot options. Please kindly resolve this issue. Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niraj 6806 F pulseaudio /dev/snd/pcmC0D0p: niraj 6806 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 16 14:14:33 2020 InstallationDate: Installed on 2018-09-09 (798 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04ca:3018 Lite-On Technology Corp. Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X556URK ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-28-generic root=UUID=a268e846-0346-4124-855c-4a0a45bd4c8e ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.8.0-28-generic N/A linux-backports-modules-5.8.0-28-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2016 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556URK.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556URK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556URK.302:bd10/24/2016:br5.12:svnASUSTeKCOMPUTERINC.:pnX556URK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556URK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556URK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904391/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045931] Re: ps3 sixasis controller request pin to connect to bt
Regardless of how the bluetooth device works, enabling unbonded devices in BlueZ makes a computer vulnerable to CVE-2023-45866. It won't be enabled by the security team. Perhaps GNOME or other desktops could become more aware of gaming controllers with these issues to make pairing easier, without needing to open a terminal. If there are feature requests for this, please link them in this bug for others. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Won't Fix Bug description: [ Workaround ] 1. Set ClassicBondedOnly=false in /etc/bluetooth/input.conf 2. Run: systemctl restart bluetooth # or reboot [ Original Description ] Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049242] Re: CIFS Mounts Keep Load Average at n+1
This issue is fixed in the mainline kernel, 6.5.10 and higher. Re Possible bug report kernel 6.5.06.5.1 high load when CIFS share is mounted (cifsd-cfid-laundromat inD state) https://lore.kernel.org/lkml/cao+kfxqgxosx6u+xlkgje0kdifsragstspnrwxjqf6udgz5...@mail.gmail.com/T/ The relevant patches: "smb3: allow controlling length of time directory entries are cached with dir leases" https://github.com/torvalds/linux/commit/238b351d0935 "smb3: allow controlling maximum number of cached directories" https://github.com/torvalds/linux/commit/6a50d71d0fff "smb3: do not start laundromat thread when dir leases disabled" https://github.com/torvalds/linux/commit/2da338ff752a "smb: client: make laundromat a delayed worker" https://github.com/torvalds/linux/commit/e95f3f744650 "smb: client: prevent new fids from being removed by laundromat" https://github.com/torvalds/linux/commit/81ba10959970 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049242 Title: CIFS Mounts Keep Load Average at n+1 Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Today I noticed that my two primary Ubuntu boxes were running at high load. After investigation, I discovered at that unmounting their CIFS shares alleviating the high load. I rebooted to the previous kernel, linux-modules-6.2.0-39-generic, and saw that the load was low after everything had settled after startup. I rebooted to the current kernel, linux-modules-6.5.0-14-generic, and again saw the high load. The load appears to be n+1, where n is the number of CIFS mounts. (Based on a sample of two boxes.) I confirmed that the default mount options (e.g. the ones not specified in fstab) are the same between the two kernels. This *might* also be slowing down external (USB disk access. I'm still investigating that. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 19:47:25 2024 InstallationDate: Installed on 2020-10-01 (1198 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2023-01-01 (376 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2049242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
Well, I have the same problem as the original post except I am running, but I can't get rid of the trying to install loop. It fails to reinstall when updating other packages. zfs version zfs-2.1.5-1ubuntu6~22.04.2 zfs-kmod-2.2.0-0ubuntu1~23.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To recreate: - Install Ubuntu 22.04.3. - Update to current. - Install package 'zfs-dkms' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046116] Re: bluetooth device connected but not recognised as output device
hi @werdem o/ What bluetooth device are you using? Your version of BlueZ has a security patch for vulnerability CVE-2023-45866 which disables support for certain legacy bluetooth devices. If your device does not support Classic Bonding, you can re-enable it by setting `ClassicBondedOnly=false` in `/etc/bluetooth/input.conf`, and then running `systemctl restart bluetooth`. More info in https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/comments/6 Please let me know if that enables your device. Keep in mind that enabling legacy devices enables the exploit. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45866 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2046116 Title: bluetooth device connected but not recognised as output device Status in bluez package in Ubuntu: New Bug description: bluetooth device connected but not recognised as output device ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 15:28:00 2023 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 81EK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=6f698382-a806-46af-9a4b-472e96795c6f ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2018 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: 7QCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 530-14IKB dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvr7QCN28WW:bd08/02/2018:br1.28:efr1.28:svnLENOVO:pn81EK:pvrLenovoYOGA530-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA530-14IKB:skuLENOVO_MT_81EK_BU_idea_FM_YOGA530-14IKB: dmi.product.family: YOGA 530-14IKB dmi.product.name: 81EK dmi.product.sku: LENOVO_MT_81EK_BU_idea_FM_YOGA 530-14IKB dmi.product.version: Lenovo YOGA 530-14IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 0C:54:15:91:FA:4F ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:83770 acl:295 sco:0 events:4208 errors:0 TX bytes:879445 acl:1667 sco:0 commands:1184 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2046116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045931] Re: ps3 sixasis controller request pin to connect to bt
Hello all o/ This is intentional. And easy to reverse. The patch for CVE-2023-45866 works as intended and is not a regression. https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/profiles/input?id=25a471a83e02e1effb15d5a488b3f0085eaeb675 If ClassicBondedOnly is not enforced, a nearby attacker can create a HID (like a keyboard and mouse) on the victims PC when bluetooth is discoverable. An HID can be used as a keyloggers or, of course, give direct control of the session. The CVE reporter has discussed this further on https://github.com/skysafe/reblog/tree/main/cve-2023-45866 And a talk and PoC release is forthcoming. Fortunately, it is easy to enable legacy devices by setting `ClassicBondedOnly=false` in `/etc/bluetooth/input.conf`, and then running `systemctl restart bluetooth`. I ver ified that a PS3 controller works well after this :) All other distros *should* be fixing this CVE. I would love it if bloggers in the Linux gaming sphere could raise awareness about this CVE and share how to enable legacy bluetooth device support. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45866 ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: bluez (Ubuntu) Assignee: Nishit Majithia (0xnishit) => Mark Esler (eslerm) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Won't Fix Bug description: Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045855] Re: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt
hi @yudamjoo o/
Please check the end of your `DpkgTerminalLog.txt` file.
To fix CVE-2023-45866 [0] a configuration file
(`/etc/bluetooth/input.conf`) was changed. If there had been edits made
to this file before updating BlueZ, apt will ask what you want to do
with the configuration file. "Y" is likely the right option if you do
not intend to have custom changes in `/etc/bluetooth/input.conf`.
Here's an example of me asking apt to show the config differences ("D") before
accepting the new changes ("Y"):
```
$ sudo apt install bluez
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
bluez
1 upgraded, 0 newly installed, 0 to remove and 157 not upgraded.
Need to get 1,106 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://redacted.launchpadcontent.net/ubuntu-security/ppa/ubuntu
jammy/main amd64 bluez amd64 5.64-0ubuntu1.1 [1,106 kB]
Fetched 1,106 kB in 1s (884 kB/s)
(Reading database ... 161840 files and directories currently installed.)
Preparing to unpack .../bluez_5.64-0ubuntu1.1_amd64.deb ...
Unpacking bluez (5.64-0ubuntu1.1) over (5.64-0ubuntu1) ...
Setting up bluez (5.64-0ubuntu1.1) ...
Configuration file '/etc/bluetooth/input.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** input.conf (Y/I/N/O/D/Z) [default=N] ? D
--- /etc/bluetooth/input.conf 2023-03-21 08:04:20.023928226 -0500
+++ /etc/bluetooth/input.conf.dpkg-new 2023-11-29 05:31:28.0 -0600
@@ -17,8 +17,8 @@
# platforms may want to make sure that input connections only come from bonded
# device connections. Several older mice have been known for not supporting
# pairing/encryption.
-# Defaults to false to maximize device compatibility.
-ClassicBondedOnly=true
+# Defaults to true for security.
+#ClassicBondedOnly=true
# LE upgrade security
# Enables upgrades of security automatically if required.
Configuration file '/etc/bluetooth/input.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** input.conf (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/bluetooth/input.conf ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for dbus (1.12.20-2ubuntu4.1) ...
```
[0] https://ubuntu.com/security/notices/USN-6540-1
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45866
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2045855
Title:
package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file
on stdin at conffile prompt
Status in bluez package in Ubuntu:
New
Bug description:
I did not recognized the error.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1.1
ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
bluez:amd64: Install
NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Dec 7 15:44:57 2023
ErrorMessage: end of file on stdin at conffile prompt
InstallationDate: Installed on 2021-01-30 (1040 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. OptiPlex 7010
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic
root=UUID=1aa27b2f-8d22-4b4e-931f-bd8e304ed0d4 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.10, Python 3.10.12, unpackaged
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.21.1ubuntu2.2
apt 2.4.11
SourcePackage: bluez
Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file
on stdin at conffile prompt
UpgradeStatus: Upgraded to jammy on 2023-03-28 (253 days ago)
dmi.bios.date: 03/25/2013
dmi.bios.release: 4.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 0GY6Y8
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
[Kernel-packages] [Bug 2038942] Re: [MIR] protection-domain-mapper & qrtr
I reviewed protection-domain-mapper as checked into mantic. This shouldn't be considered a full audit but rather a quick gauge of maintainability. pd-mapper: [no upstream description] - CVE History: - no CVE history - possible security issues in commit messages - no security policy - upstream may not be reporting security issues - this is a maintenance issue - Build-Depends? - qrtr - pre/post inst/rm scripts? - postinst configures and starts pd-mapper.service - prerm stops pd-mapper.service - postrm runs daemon-reload and purges pd-mapper.service - init scripts? - none - systemd units? - ./lib/systemd/system/pd-mapper.service - spartan documentation - starts pd-mapper - dbus services? - none - setuid binaries? - none - binaries in PATH? - ./usr/bin/pd-mapper - sudo fragments? - none - polkit files? - none - udev rules? - none - unit tests / autopkgtests? - tests, hardware tests, are needed - cron jobs? - none - Build logs: - no-manual-page - Processes spawned? - none - Memory management? - owning team has agreed to fix issues - File IO? - pd_enumerate_jsons looks dangerous - statically opens /sys/class/remoteproc/ - only root should own these files - if continues, without consequence - /lib/firmware/ also set - interprets json - Logging? - minimal, mostly stderr - Environment variable usage? - none - Use of privileged functions? - none - Use of cryptography / random number sources etc? - none - Use of temp files? - none - Use of networking? - through qrtr - Use of WebKit? - none - Use of PolicyKit? - none - Any significant cppcheck results? - none - Any significant Coverity results? - high density for only ~1k loc - owning team agreed to address all positive results - Any significant shellcheck results? - none - Any significant bandit results? - none This deserves fuzzing and a deeper review. Hardware enablement is a priority and urgent. slyon's recommendations are great! There is no release or changelog history. Commit messages are the only context Possibly zero in-line comments. No documentation. This project does not even have a description. This is a major maintenance issue. Thank you for adding a hardened systemd profile in -proposed for promotion \o/ http://launchpadlibrarian.net/691288606/protection-domain-mapper_1.0-4ubuntu1_1.0-4ubuntu2.diff.gz Security team ACK for promoting protection-domain-mapper to main. ** Attachment added: "coverity-protection-domain-mapper.txt" https://bugs.launchpad.net/ubuntu/+source/qrtr/+bug/2038942/+attachment/5708388/+files/coverity-protection-domain-mapper.txt ** Changed in: protection-domain-mapper (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) ** Changed in: qrtr (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) ** Changed in: protection-domain-mapper (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: qrtr (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2038942 Title: [MIR] protection-domain-mapper & qrtr Status in protection-domain-mapper package in Ubuntu: Fix Committed Status in qrtr package in Ubuntu: Fix Committed Bug description: [Availability] The package protection-domain-mapper is already in Ubuntu universe. The package protection-domain-mapper build for the architectures it is designed to work on. It currently builds and works for architectures: any, verified as working on arm64 Link to package https://launchpad.net/ubuntu/+source/protection-domain-mapper [Rationale] - The package protection-domain-mapper is required in Ubuntu main for ubuntu-desktop on ARM64, as it enables power-indicator (among other things) on most Windows on Arm laptops (qcom based laptops ~7 SKUs and more coming). There is no other way to implement this. - protection-domain-mapper depends on qrtr for library and a systemd service it provides. - There is no other/better way to solve this that is already in main or should go universe->main instead of this. As this is the only implementation of talking to the qcom hardware. - The package protection-domain-mapper is required in Ubuntu main no later than today due to Mantic release, if we want to have the best impression of Ubuntu Desktop in the live session on x13s. - If that fails, having it fixed as SRU is the next best option. [Security] - No CVEs/security issues in this software in the past. This is a reference open source implementation of these tools, which otherwise are used on qcom Android devices - no `suid` or `sgid` binaries no executables in `/sbin` and `/usr/sbin` - Package does install services: pd-mapper.service & qrtr-ns.service which allow runtime access to the qcom hardware which
[Kernel-packages] [Bug 2038942] Re: [MIR] protection-domain-mapper & qrtr
I reviewed qrtr 1.0-2 as checked into mantic. This shouldn't be considered a full audit but rather a quick gauge of maintainability. qrtr: Userspace reference for net/qrtr in the Linux kernel - CVE History: - no CVE history - no security policy - CVE-2019-19079 and CVE-2021-29647 affect kernel implementation - Build-Depends? - no explicit dependencies in d/control - pre/post inst/rm scripts? - postinst configures and starts qrtr-ns.service - prerm stops qrtr-ns.service - postrm runs daemon-reload and purges qrtr-ns.service - init scripts? - init - systemd units? - ./lib/systemd/system/qrtr-ns.service - spartan documentation - starts qrtr-ns - dbus services? - none - setuid binaries? - none - binaries in PATH? - ./usr/bin/qrtr-cfg - ./usr/bin/qrtr-lookup - ./usr/bin/qrtr-ns - sudo fragments? - none - polkit files? - none - udev rules? - none - unit tests / autopkgtests? - tests, hardware tests, are needed - cron jobs? - none - Build logs: - mostly clean - see -proposed - Processes spawned? - none - Memory management? - memory use appears safe - if values are confidential, memset_s should be used - File IO? - only sockets - Logging? - yes, see PLOGE - string use looks safe - Environment variable usage? - none - Use of privileged functions? - none - Use of cryptography / random number sources etc? - none - Use of temp files? - none - Use of networking? - heavy, most of codebase - nothing obviously concerning - Use of WebKit? - none - Use of PolicyKit? - none - Any significant cppcheck results? - none - Any significant Coverity results? - rc appears to be false positive - src/ns.c:796:2 appears to be an infinite loop - Any significant shellcheck results? - none - Any significant bandit results? - none - ./qrtr.py is python2.7 We should be cautious of IPC routers running root permissions. Similar code has enabled vendor backdoors [0]. Qualcomm IPC will only be enabled in kernels which require it, such as for the x13s. Some mitigations exist to prevent spoofing and non-local observers. Fuzzing seems worthwhile. Possibly zero in-line comments. No documentation. This is a major maintenance issue. slyon's recommendations are great! Thank you for adding a hardened systemd profile to -proposed for promotion \o/ http://launchpadlibrarian.net/691288509/qrtr_1.0-2_1.0-2ubuntu1.diff.gz Security team ACK for promoting qrtr to main. [0] https://redmine.replicant.us/projects/replicant/wiki/samsunggalaxybackdoor ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-19079 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-29647 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2038942 Title: [MIR] protection-domain-mapper & qrtr Status in protection-domain-mapper package in Ubuntu: Fix Committed Status in qrtr package in Ubuntu: Fix Committed Bug description: [Availability] The package protection-domain-mapper is already in Ubuntu universe. The package protection-domain-mapper build for the architectures it is designed to work on. It currently builds and works for architectures: any, verified as working on arm64 Link to package https://launchpad.net/ubuntu/+source/protection-domain-mapper [Rationale] - The package protection-domain-mapper is required in Ubuntu main for ubuntu-desktop on ARM64, as it enables power-indicator (among other things) on most Windows on Arm laptops (qcom based laptops ~7 SKUs and more coming). There is no other way to implement this. - protection-domain-mapper depends on qrtr for library and a systemd service it provides. - There is no other/better way to solve this that is already in main or should go universe->main instead of this. As this is the only implementation of talking to the qcom hardware. - The package protection-domain-mapper is required in Ubuntu main no later than today due to Mantic release, if we want to have the best impression of Ubuntu Desktop in the live session on x13s. - If that fails, having it fixed as SRU is the next best option. [Security] - No CVEs/security issues in this software in the past. This is a reference open source implementation of these tools, which otherwise are used on qcom Android devices - no `suid` or `sgid` binaries no executables in `/sbin` and `/usr/sbin` - Package does install services: pd-mapper.service & qrtr-ns.service which allow runtime access to the qcom hardware which are run as root - Security has been kept in mind and common isolation/risk-mitigation patterns are in place utilizing the following features: - Packages does not open privileged ports (ports < 1024). - Package does not expose any external endpoints - Packages does not contain extensions to security-sensitive software (filters,
[Kernel-packages] [Bug 2024500] Re: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration.
** Description changed: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes - No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 - --- + + + + --- ProblemType: Bug AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Jun 20 21:15 seq - crw-rw 1 root audio 116, 33 Jun 20 21:15 timer + total 0 + crw-rw 1 root audio 116, 1 Jun 20 21:15 seq + crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: - + ProcEnviron: - TERM=screen-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=screen-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: - linux-restricted-modules-5.15.0-75-generic N/A - linux-backports-modules-5.15.0-75-generic N/A - linux-firmware 1.187.39 + linux-restricted-modules-5.15.0-75-generic N/A + linux-backports-modules-5.15.0-75-generic N/A + linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux-hwe-5.15 package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip
[Kernel-packages] [Bug 2024500] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681058/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681056/+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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681052/+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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681057/+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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681050/+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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681055/+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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681051/+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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681054/+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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681053/+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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681049/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681048/+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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681046/+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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681047/+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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] Re: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration.
apport information ** Tags added: apport-collected focal ** Description changed: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jun 20 21:15 seq + crw-rw 1 root audio 116, 33 Jun 20 21:15 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.27 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + MachineType: Supermicro AS -2124BT-HNTR + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 astdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 + ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-75-generic N/A + linux-backports-modules-5.15.0-75-generic N/A + linux-firmware 1.187.39 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal + Uname: Linux 5.15.0-75-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 09/23/2022 + dmi.bios.release: 5.22 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2.5 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: H12DST-B + dmi.board.vendor: Supermicro + dmi.board.version: 1.00A + dmi.chassis.asset.tag: To be filled by O.E.M. + dmi.chassis.type: 1 + dmi.chassis.vendor: Supermicro + dmi.chassis.version: 0123456789 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: AS -2124BT-HNTR + dmi.product.sku: To be filled by O.E.M. + dmi.product.version: 0123456789 + dmi.sys.vendor: Supermicro ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2024500/+attachment/5681045/+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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color
[Kernel-packages] [Bug 2024500] Re: KVM: after upgrading the kernel to 5.15.0-75, Guest hangs after migration.
compute37 apport ** Attachment added: "compute37 apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+attachment/5681032/+files/compute37-apport.txt ** Description changed: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes - Not seeing the issue using the following kernels: + No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Incomplete Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] Re: KVM: after upgrading the kernel to 5.15.0-75, Guest hangs after migration.
libvirt version (nova-libvirt)[root@compute81 /]# dpkg -l | grep libvirt ii libvirt-clients 6.0.0-0ubuntu8.16 amd64Programs for the libvirt library ii libvirt-daemon 6.0.0-0ubuntu8.16 amd64Virtualization daemon ii libvirt-daemon-driver-qemu 6.0.0-0ubuntu8.16 amd64Virtualization daemon QEMU connection driver ii libvirt-daemon-system6.0.0-0ubuntu8.16 amd64Libvirt daemon configuration files ii libvirt-daemon-system-systemd6.0.0-0ubuntu8.16 amd64Libvirt daemon configuration files (systemd) ii libvirt0:amd64 6.0.0-0ubuntu8.16 amd64library for interfacing with different virtualization systems qemu version (nova-libvirt)[root@compute81 /]# dpkg -l | grep qemu ii ipxe-qemu1.0.0+git-20190109.133f4c4-0ubuntu3.2 all PXE boot firmware - ROM images for qemu ii ipxe-qemu-256k-compat-efi-roms 1.0.0+git-20150424.a25a16d-0ubuntu4 all PXE boot firmware - Compat EFI ROM images for qemu ii libvirt-daemon-driver-qemu 6.0.0-0ubuntu8.16 amd64Virtualization daemon QEMU connection driver ii qemu-block-extra:amd64 1:4.2-3ubuntu6.24 amd64extra block backend modules for qemu-system and qemu-utils ii qemu-kvm 1:4.2-3ubuntu6.24 amd64QEMU Full virtualization on x86 hardware ii qemu-slof20191209+dfsg-1 all Slimline Open Firmware -- QEMU PowerPC version ii qemu-system 1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries ii qemu-system-arm 1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries (arm) ii qemu-system-common 1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries (common files) ii qemu-system-data 1:4.2-3ubuntu6.24 all QEMU full system emulation (data files) ii qemu-system-mips 1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries (mips) ii qemu-system-misc 1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries (miscellaneous) ii qemu-system-ppc 1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries (ppc) ii qemu-system-s390x1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries (s390x) ii qemu-system-sparc1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries (sparc) ii qemu-system-x86 1:4.2-3ubuntu6.24 amd64QEMU full system emulation binaries (x86) ** Summary changed: - KVM: after upgrading the kernel to 5.15.0-75, Guest hangs after migration. + KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Incomplete Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] Re: KVM: after upgrading the kernel to 5.15.0-75, Guest hangs after migration.
compute81 apport ** Description changed: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. - First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux - When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes - No issue using the following kernels: + Not seeing the issue using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 ** Attachment added: "compute81-apport.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+attachment/5681031/+files/compute81-apport.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/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux package in Ubuntu: Incomplete Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024500] [NEW] KVM: after upgrading the kernel to 5.15.0-75, Guest hangs after migration.
Public bug reported: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes Not seeing the issue using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, Guest hangs after migration. Status in linux package in Ubuntu: New Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM freezes Not seeing the issue using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874241] Re: iwlwifi intel ax201 crashing on intel nuc10i7fnh
activity. still an issue -- 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/1874241 Title: iwlwifi intel ax201 crashing on intel nuc10i7fnh Status in linux-firmware package in Ubuntu: Expired Bug description: The intel iwlwifi firmware will crash when you insert a device into the thunderbolt3 port, and this will be trigger probabilistically. wifi card model:Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354 Firmware version: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 Linux-firmware version: 1.187 thunderbolt3 chip model: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06) dmesg output: [ 103.777908] pcieport :00:1c.0: PME: Spurious native interrupt! [ 103.777918] pcieport :00:1c.0: PME: Spurious native interrupt! [ 104.118148] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 104.147184] usb 4-1: New USB device found, idVendor=05e3, idProduct=0749, bcdDevice=15.32 [ 104.147190] usb 4-1: New USB device strings: Mfr=3, Product=4, SerialNumber=2 [ 104.147194] usb 4-1: Product: USB3.0 Card Reader [ 104.147197] usb 4-1: Manufacturer: Generic [ 104.147199] usb 4-1: SerialNumber: 1532 [ 104.183374] usb-storage 4-1:1.0: USB Mass Storage device detected [ 104.183952] scsi host3: usb-storage 4-1:1.0 [ 104.184172] usbcore: registered new interface driver usb-storage [ 104.187897] usbcore: registered new interface driver uas [ 105.217035] scsi 3:0:0:0: Direct-Access Generic STORAGE DEVICE 1532 PQ: 0 ANSI: 6 [ 105.217792] sd 3:0:0:0: Attached scsi generic sg1 type 0 [ 105.233978] sd 3:0:0:0: [sdb] Attached SCSI removable disk [ 109.998995] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 109.999102] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 109.999111] iwlwifi :00:14.3: Status: 0x0040, count: 6 [ 109.999119] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0 [ 109.999128] iwlwifi :00:14.3: 0x4435 | ADVANCED_SYSASSERT [ 109.999135] iwlwifi :00:14.3: 0x008026F4 | trm_hw_status0 [ 109.999142] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 109.999148] iwlwifi :00:14.3: 0x004CA228 | branchlink2 [ 109.999154] iwlwifi :00:14.3: 0x0E26 | interruptlink1 [ 109.999161] iwlwifi :00:14.3: 0x0E26 | interruptlink2 [ 109.999168] iwlwifi :00:14.3: 0x000161A0 | data1 [ 109.999174] iwlwifi :00:14.3: 0xDEADBEEF | data2 [ 109.999180] iwlwifi :00:14.3: 0xDEADBEEF | data3 [ 109.999186] iwlwifi :00:14.3: 0xF90167B5 | beacon time [ 109.999192] iwlwifi :00:14.3: 0x51938809 | tsf low [ 109.999199] iwlwifi :00:14.3: 0x0010 | tsf hi [ 109.999205] iwlwifi :00:14.3: 0x | time gp1 [ 109.999211] iwlwifi :00:14.3: 0x064A1430 | time gp2 [ 109.999217] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 109.999224] iwlwifi :00:14.3: 0x0030 | uCode version major [ 109.999231] iwlwifi :00:14.3: 0x4FA0041F | uCode version minor [ 109.999239] iwlwifi :00:14.3: 0x0351 | hw version [ 109.999245] iwlwifi :00:14.3: 0x00C89004 | board version [ 109.999252] iwlwifi :00:14.3: 0x069E001C | hcmd [ 109.999259] iwlwifi :00:14.3: 0x8002 | isr0 [ 109.999265] iwlwifi :00:14.3: 0x0100 | isr1 [ 109.999271] iwlwifi :00:14.3: 0x08F2 | isr2 [ 109.999278] iwlwifi :00:14.3: 0x04C1FFCC | isr3 [ 109.999284] iwlwifi :00:14.3: 0x | isr4 [ 109.999290] iwlwifi :00:14.3: 0x069D001C | last cmd Id [ 109.999297] iwlwifi :00:14.3: 0x8B70 | wait_event [ 109.999304] iwlwifi :00:14.3: 0x4208 | l2p_control [ 109.999310] iwlwifi :00:14.3: 0x2020 | l2p_duration [ 109.999317] iwlwifi :00:14.3: 0x033F | l2p_mhvalid [ 109.999324] iwlwifi :00:14.3: 0x00E6 | l2p_addr_match [ 109.999331] iwlwifi :00:14.3: 0x0009 | lmpm_pmg_sel [ 109.999337] iwlwifi :00:14.3: 0x | timestamp [ 109.999344] iwlwifi :00:14.3: 0xB8DC | flow_handler [ 109.999391] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 109.999398] iwlwifi :00:14.3: Status: 0x0040, count: 7 [ 109.999406] iwlwifi :00:14.3: 0x2070 | NMI_INTERRUPT_LMAC_FATAL [ 109.999413] iwlwifi :00:14.3: 0x | umac branchlink1 [ 109.999420] iwlwifi :00:14.3: 0xC008D49C | umac branchlink2 [ 109.999427] iwlwifi :00:14.3: 0x8048DBD2 | umac interruptlink1 [ 109.999434] iwlwifi :00:14.3: 0x8048DBD2 | umac interruptlink2 [ 109.999441] iwlwifi :00:14.3: 0x0400 | umac data1 [ 109.999447] iwlwifi :00:14.3: 0x8048DBD2 | umac data2 [ 109.999454] iwlwifi :00:14.3: 0x | umac data3 [ 109.999461] iwlwifi :00:14.3: 0x0030 | umac major [
[Kernel-packages] [Bug 2017227] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Un
I was able to boot lunar even though this package installation failed, because there was still a 5.xy kernel left from kinetic, which booted just fine. Removing the evdi dkms and `apt upgrade` finished the installation of this package. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017227 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück Status in linux package in Ubuntu: Invalid Bug description: I got an error message during updating from Ubuntu 22.10 to 23.04 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaeger 2885 F wireplumber /dev/snd/seq:jaeger 2882 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Fri Apr 21 11:52:56 2023 ErrorMessage: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2022-12-06 (135 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Latitude 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 03/17/2023 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0C6CYC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd03/17/2023:br1.12:svnDellInc.:pnLatitude5530:pvr:rvnDellInc.:rn0C6CYC:rvrA00:cvnDellInc.:ct10:cvr:sku0B06: dmi.product.family: Latitude dmi.product.name: Latitude 5530 dmi.product.sku: 0B06 dmi.sys.vendor: Dell Inc. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018431] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess
Public bug reported: During upgrade from kinetic to lunar ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1639 F wireplumber /dev/snd/controlC1: mark 1639 F wireplumber /dev/snd/seq:mark 1636 F pipewire CRDA: N/A CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-common-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-source-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-utils-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/xserver-xorg-video-nvidia-515_515.76+really.515.65.01-0ubuntu1_amd64.deb CasperMD5CheckResult: fail Date: Wed May 3 21:56:24 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-01 (183 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: SYSTEM_MANUFACTURER HX90 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=887b3140-4d95-48d5-aec2-39d52a18cd30 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-03 (0 days ago) dmi.bios.date: 10/11/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.19 dmi.board.asset.tag: Default string dmi.board.name: HX90 dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.19:bd10/11/2021:br5.19:svnSYSTEM_MANUFACTURER:pnHX90:pvrDefaultstring:rvnDefaultstring:rnHX90:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: HX90 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: SYSTEM_MANUFACTURER ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018431 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: During upgrade from kinetic to lunar ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1639 F wireplumber /dev/snd/controlC1: mark 1639 F wireplumber /dev/snd/seq: mark 1636 F pipewire CRDA: N/A CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-common-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-source-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-utils-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/xserver-xorg-video-nvidia-515_515.76+really.515.65.01-0ubuntu1_amd64.deb CasperMD5CheckResult: fail Date: Wed May 3 21:56:24 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-01 (183 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: SYSTEM_MANUFACTURER HX90 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=887b3140-4d95-48d5-aec2-39d52a18
[Kernel-packages] [Bug 1998338] [NEW] linux-modules-5.15.0-1022-gcp is missing nf_conntrack.ko
Public bug reported: linux-modules-5.15.0-1022-gcp is missing nf_conntrack.ko file. The file exists in linux- modules-5.15.0-1022-aws_5.15.0-1022.26~20.04.1_amd64.deb. ** Affects: linux-gcp-5.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1998338 Title: linux-modules-5.15.0-1022-gcp is missing nf_conntrack.ko Status in linux-gcp-5.15 package in Ubuntu: New Bug description: linux-modules-5.15.0-1022-gcp is missing nf_conntrack.ko file. The file exists in linux- modules-5.15.0-1022-aws_5.15.0-1022.26~20.04.1_amd64.deb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp-5.15/+bug/1998338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990690] Re: Users belonging to video group may trigger a deadlock WARN
I don't know if this is where you track it, but the problem described
here appears to have made it into Ubuntu Advantage 16.04-ESM as well,
specifically across the 4.15.0-189.200~16.04.1 -> 4.15.0-193.204~16.04.1
upgrade. (Just based on changelog text this fix was not in
4.15.0-194.205~16.04.1 but I haven't dug far enough to track more
closely.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990690
Title:
Users belonging to video group may trigger a deadlock WARN
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
One of the fixing commits for CVE-2021-33655, commit 159a96b199b4
("fbcon: Prevent that screen size is smaller than font size") introduced
an extraneous lock_fb_info line into the ioctl flow in fbmem.c.
This line only exists in bionic tree.
Users belonging to video group may trigger a deadlock and potentially
lock the system.
WARNING: possible recursive locking detected
4.15.0-195-generic #206 Not tainted
refresh/1248 is trying to acquire lock:
(_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
but task is already holding lock:
(_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
lock(_info->lock);
lock(_info->lock);
*** DEADLOCK ***
May be due to missing lock nesting notation
2 locks held by refresh/1248:
#0: (console_lock){+.+.}, at: [<8000aa2b>] do_fb_ioctl+0x435/0x5e0
#1: (_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
stack backtrace:
CPU: 0 PID: 1248 Comm: refresh Not tainted 4.15.0-195-generic #206
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
Call Trace:
dump_stack+0x98/0xd2
__lock_acquire+0x736/0x1480
? sched_clock_local+0x17/0x90
? sched_clock+0x9/0x10
? sched_clock_local+0x17/0x90
lock_acquire+0xa3/0x1e0
? lock_acquire+0xa3/0x1e0
? lock_fb_info+0x1d/0x40
? lock_fb_info+0x1d/0x40
__mutex_lock+0x65/0x970
? lock_fb_info+0x1d/0x40
? sched_clock_local+0x17/0x90
? lock_acquire+0xa3/0x1e0
mutex_lock_nested+0x1b/0x20
? mutex_lock_nested+0x1b/0x20
lock_fb_info+0x1d/0x40
do_fb_ioctl+0x57a/0x5e0
? __fd_install+0x5/0x250
fb_ioctl+0x33/0x40
? fb_ioctl+0x33/0x40
do_vfs_ioctl+0xa9/0x6d0
? putname+0x4c/0x60
? do_sys_open+0x13d/0x370
SyS_ioctl+0x79/0x90
do_syscall_64+0x7b/0x1e0
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f22acca7217
RSP: 002b:7ffe2a930b48 EFLAGS: 0213 ORIG_RAX: 0010
RAX: ffda RBX: RCX: 7f22acca7217
RDX: 7ffe2a930c30 RSI: 4601 RDI: 0003
RBP: 7ffe2a930d40 R08: R09:
R10: R11: 0213 R12: 5624ac8fc7c0
R13: 7ffe2a930e20 R14: R15:
[Test case]
Run a sample framebuffer userspace test to call FBIOPUT_VSCREENINFO
and verified with LOCKDEP.
[Potential regressions]
There are no new potential regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990690/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968631] Re: regression in jammy kernel 5.15 for module ath9k
Is this the same bug? [ 85.432958] UBSAN: invalid-load in /build/linux-kQ6jNR/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:488:16 [ 85.432965] load of value 255 is not a valid value for type '_Bool' [ 85.432969] CPU: 1 PID: 182 Comm: kworker/u8:5 Not tainted 5.15.0-48-generic #54-Ubuntu [ 85.432974] Hardware name: TOSHIBA Satellite L300/Portable PC, BIOS 1.80 03/20/2009 [ 85.432978] Workqueue: phy0 ieee80211_reconfig_filter [mac80211] [ 85.433146] Call Trace: [ 85.433149] [ 85.433154] show_stack+0x52/0x5c [ 85.433161] dump_stack_lvl+0x4a/0x63 [ 85.433170] dump_stack+0x10/0x16 [ 85.433174] ubsan_epilogue+0x9/0x49 [ 85.433178] __ubsan_handle_load_invalid_value.cold+0x44/0x49 [ 85.433184] ath5k_vif_iter.cold+0x13/0x70 [ath5k] [ 85.433200] ? update_load_avg+0x82/0x620 [ 85.433206] __iterate_interfaces+0xa2/0x100 [mac80211] [ 85.433289] ? ath5k_tasklet_ani+0x40/0x40 [ath5k] [ 85.433302] ieee80211_iterate_active_interfaces_atomic+0x11/0x20 [mac80211] [ 85.433384] ath5k_configure_filter+0x114/0x190 [ath5k] [ 85.433397] ieee80211_configure_filter+0x175/0x2d0 [mac80211] [ 85.433462] ieee80211_reconfig_filter+0x15/0x20 [mac80211] [ 85.433524] process_one_work+0x22b/0x3d0 [ 85.433530] worker_thread+0x53/0x420 [ 85.433533] ? process_one_work+0x3d0/0x3d0 [ 85.433537] kthread+0x12a/0x150 [ 85.433542] ? set_kthread_struct+0x50/0x50 [ 85.433547] ret_from_fork+0x22/0x30 [ 85.433554] [ 85.433582] [ 87.313291] loop6: detected capacity change from 0 to 8 [ 89.340540] wlan0: authenticate with c0:06:c3:7e:af:ca [ 89.340562] wlan0: No basic rates, using min rate instead [ 89.344817] wlan0: send auth to c0:06:c3:7e:af:ca (try 1/3) [ 89.345272] wlan0: authenticated [ 89.347154] wlan0: associate with c0:06:c3:7e:af:ca (try 1/3) [ 89.355603] wlan0: RX AssocResp from c0:06:c3:7e:af:ca (capab=0x1811 status=0 aid=7) [ 89.355727] wlan0: associated [ 89.955165] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 94.135131] audit: type=1400 audit(1665309268.790:45): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/snap/snapd/17029/usr/lib/snapd/snap-confine" pid=1020 comm="apparmor_parser" [ 94.151682] audit: type=1400 audit(1665309268.806:46): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/snap/snapd/17029/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=1020 comm="apparmor_parser" [ 95.601560] audit: type=1400 audit(1665309270.254:47): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.firefox" pid=1022 comm="apparmor_parser" [ 95.661079] audit: type=1400 audit(1665309270.314:48): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.firefox.firefox" pid=1041 comm="apparmor_parser" [ 95.711682] audit: type=1400 audit(1665309270.366:49): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.firefox.geckodriver" pid=1042 comm="apparmor_parser" [ 95.733492] audit: type=1400 audit(1665309270.386:50): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.firefox.hook.configure" pid=1043 comm="apparmor_parser" [ 95.748191] audit: type=1400 audit(1665309270.402:51): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.firefox.hook.connect-plug-host-hunspell" pid=1044 comm="apparmor_parser" [ 95.762985] audit: type=1400 audit(1665309270.418:52): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.firefox.hook.disconnect-plug-host-hunspell" pid=1045 comm="apparmor_parser" [ 95.782132] audit: type=1400 audit(1665309270.434:53): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.firefox.hook.post-refresh" pid=1046 comm="apparmor_parser" [ 96.022549] audit: type=1400 audit(1665309270.674:54): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=837 comm="cupsd" capability=12 capname="net_admin" [ 98.742137] [ 98.742150] UBSAN: array-index-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20 [ 98.742157] index 4 is out of range for type 'ieee80211_tx_rate [4]' [ 98.742161] CPU: 0 PID: 880 Comm: snapd Not tainted 5.15.0-48-generic #54-Ubuntu [ 98.742166] Hardware name: TOSHIBA Satellite L300/Portable PC, BIOS 1.80 03/20/2009 [ 98.742169] Call Trace: [ 98.742173] [ 98.742178] show_stack+0x52/0x5c [ 98.742186]
[Kernel-packages] [Bug 1990997] [NEW] en_ZA locale not correct in applications
Public bug reported: In all Ubuntu based distributions I have found that in applications such as LibreOffice Calc where I need to see formats applicable to my locale en_ZA (South Africa) the decimal place is denoted by , in the application even though the file /usr/share/i18n/locales/en_ZA is correct in specifying the decimal place as denoted by a . This is the same for monetary values where it is showing , in applications instead of the . as specified in the locale file. The comma was deprecated in South Africa in the 1990s and the generally accepted decimal is . This makes it extremely difficult to transfer Windows Excel files that have decimal points to a Linux distro that strictly enforces recognising a decimal with a comma and hence renders the Windows Excel file useless in Linux. The Windows feature of customising locales in terms of date, time, decimal place and digit grouping within the GUI is sorely missing from all desktops in Linux and so this cannot be fixed by the end-user. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: africa currency decimal locale south za -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990997 Title: en_ZA locale not correct in applications Status in linux package in Ubuntu: New Bug description: In all Ubuntu based distributions I have found that in applications such as LibreOffice Calc where I need to see formats applicable to my locale en_ZA (South Africa) the decimal place is denoted by , in the application even though the file /usr/share/i18n/locales/en_ZA is correct in specifying the decimal place as denoted by a . This is the same for monetary values where it is showing , in applications instead of the . as specified in the locale file. The comma was deprecated in South Africa in the 1990s and the generally accepted decimal is . This makes it extremely difficult to transfer Windows Excel files that have decimal points to a Linux distro that strictly enforces recognising a decimal with a comma and hence renders the Windows Excel file useless in Linux. The Windows feature of customising locales in terms of date, time, decimal place and digit grouping within the GUI is sorely missing from all desktops in Linux and so this cannot be fixed by the end-user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)
Juerg, yes. The Breaks line of comment 15 used the most recently available version (<< 20220711.gitdfa29317-0~). -- 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/1983409 Title: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free) Status in amd64-microcode package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Committed Bug description: Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2 to 3.20220411.1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)
\o/ woo! Thanks everyone who helped get this into Kinetic before feature freeze! -- 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/1983409 Title: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free) Status in amd64-microcode package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Committed Bug description: Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2 to 3.20220411.1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)
The current version of linux-firmware (20220819.git8413c63c-0ubuntu1) contains a Breaks line with: `amd64-microcode (<= 3.20220411.1ubuntu1)`. The linux-firmware patch proposed in comment 16 contains a Breaks line with: `amd64-microcode (<< 3.20220411.1~)`. The patch in comment 16 works. Using the Breaks line `amd64-microcode (<< 3.20220411.1~)` in the current version of linux-firmware (20220819.git8413c63c-0ubuntu1) I was able to install both linux-firmware and amd64-microcode in a fresh kinetic VM with: sudo apt install linux-firmware sudo apt --fix-broken install sudo apt install linux-firmware eslerm@sec-kinetic-amd64:~$ apt-cache policy linux-firmware linux-firmware: Installed: 20220819.git8413c63c-0ubuntu3 Candidate: 20220819.git8413c63c-0ubuntu3 Version table: *** 20220819.git8413c63c-0ubuntu3 500 500 http://192.168.122.1/debs/testing kinetic/ Packages 100 /var/lib/dpkg/status 20220819.git8413c63c-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main i386 Packages 20220711.gitdfa29317-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu kinetic/main i386 Packages eslerm@sec-kinetic-amd64:~$ apt-cache policy amd64-microcode amd64-microcode: Installed: 3.20220411.1ubuntu2 Candidate: 3.20220411.1ubuntu2 Version table: *** 3.20220411.1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.20191218.1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages ** Changed in: amd64-microcode (Ubuntu) Importance: Medium => Critical ** Changed in: linux-firmware (Ubuntu) Importance: Medium => Critical -- 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/1983409 Title: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free) Status in amd64-microcode package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Committed Bug description: Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2 to 3.20220411.1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)
@juergh, the amd64-microcode in kinetic proposed could be fixed by using the control file in https://launchpad.net/~eslerm/+archive/ubuntu/share3/+sourcepub/13868029/+listing- archive-extra -- 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/1983409 Title: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free) Status in amd64-microcode package in Ubuntu: Fix Committed Status in linux-firmware package in Ubuntu: Fix Committed Bug description: Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2 to 3.20220411.1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986796] Re: amd64-microcode conflicts with linux-firmware
The conflicts are resolved with patches for amd64-microcode and linux- firmware here: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409 -- 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/1986796 Title: amd64-microcode conflicts with linux-firmware Status in amd64-microcode package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Triaged Bug description: Occurs on kubuntu, gnome and xfce versions of kinetic proposed -- most recent updates ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: amd64-microcode 3.20191218.1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Aug 17 08:07:09 2022 InstallationDate: Installed on 2022-06-10 (67 days ago) InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220610) SourcePackage: amd64-microcode UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1986796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)
I am setting this to confirmed and assigning owning teams per https://wiki.ubuntu.com/UbuntuDevelopment/Merging Please let me know if I assigned teams incorrectly or if I can do more work for this merge. ** Changed in: amd64-microcode (Ubuntu) Status: In Progress => Confirmed ** Changed in: linux-firmware (Ubuntu) Status: In Progress => Confirmed ** Changed in: amd64-microcode (Ubuntu) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: linux-firmware (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- 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/1983409 Title: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free) Status in amd64-microcode package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2 to 3.20220411.1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)
** Changed in: amd64-microcode (Ubuntu) Assignee: Mark Esler (eslerm) => (unassigned) ** Changed in: linux-firmware (Ubuntu) Assignee: Mark Esler (eslerm) => (unassigned) -- 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/1983409 Title: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free) Status in amd64-microcode package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: In Progress Bug description: Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2 to 3.20220411.1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)
Please see the proposed diff for the next linux-firmware update: https://launchpad.net/~eslerm/+archive/ubuntu/share/+sourcepub/13868068/+listing-archive-extra I was not able to specify [amd64] in the Breaks line, since that broke build: "error: the Breaks field ... 'linux-firmware' is architecture all" -- 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/1983409 Title: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free) Status in amd64-microcode package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: In Progress Bug description: Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2 to 3.20220411.1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)
@vorlon suggested to use "linux-firmware (<< 20220711.gitdfa29317-0~)" to make this SRU-proof for the future. d/control now contains: ``` Breaks: intel-microcode (<< 2), linux-firmware (<< 20220711.gitdfa29317-0~) Replaces: linux-firmware (<< 20220711.gitdfa29317-0~) ``` Please see the latest proposed merge: https://launchpad.net/~eslerm/+archive/ubuntu/share3/+sourcepub/13868029/+listing-archive-extra -- 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/1983409 Title: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free) Status in amd64-microcode package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: In Progress Bug description: Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2 to 3.20220411.1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)
An updated merge is ready for review.
https://launchpad.net/~eslerm/+archive/ubuntu/share2/+sourcepub/13867943/+listing-archive-extra
This package has a d/control with:
```
Source: amd64-microcode
Section: non-free/admin
Priority: standard
Maintainer: Ubuntu Developers
XSBC-Original-Maintainer: Henrique de Moraes Holschuh
Uploaders: Giacomo Catenazzi
Build-Depends: debhelper (>= 9)
Standards-Version: 3.9.8
Vcs-Git: https://salsa.debian.org/hmh/amd64-microcode.git
Vcs-Browser: https://salsa.debian.org/hmh/amd64-microcode
XS-Autobuild: yes
Package: amd64-microcode
Architecture: i386 amd64 x32
Recommends: initramfs-tools (>= 0.113~) | dracut (>= 044) | tiny-initramfs
Depends: ${misc:Depends}
Breaks: intel-microcode (<< 2), linux-firmware (<=
20220711.gitdfa29317-0ubuntu1)
Replaces: linux-firmware (<= 20220711.gitdfa29317-0ubuntu1)
Description: Processor microcode firmware for AMD CPUs
This package contains microcode patches for all AMD AMD64
processors. AMD releases microcode patches to correct
processor behavior as documented in the respective processor
revision guides. This package includes both AMD CPU microcode
patches and AMD SEV firmware updates.
.
For Intel processors, please refer to the intel-microcode package.
```
--
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/1983409
Title:
Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable
(non-free)
Status in amd64-microcode package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
In Progress
Bug description:
Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2
to 3.20220411.1ubuntu1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)
In the above comment I did not apply rule 9 to linux-firmware properly. Since the next linux-firmware version number is unknown, the amd64-microcode relationship to linux-firmware will use earlier or equal to (<=) the current linux-firmware version https://www.debian.org/doc/debian-policy/ch-relationships.html So linux-firmware needs: Breaks: amd64-microcode (<< 3.20220411.1ubuntu1) [amd64] and amd64-microcode needs: Breaks: linux-firmware (<= 20220711.gitdfa29317-0ubuntu1) Replaces: linux-firmware (<= 20220711.gitdfa29317-0ubuntu1) Keeping replaces feels odd. -- 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/1983409 Title: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free) Status in amd64-microcode package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: In Progress Bug description: Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2 to 3.20220411.1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)
Thank you @superm1 and @juergh! I have not made packages outside of security patches and I immensely appreciate the advice. Since not everyone who needs linux-firmware wants amd64-micocode, I believe it should be #9: "Reorg: A and B existed; move some files from A to B; new A does not require new B". So linux-firmware needs: Depends: amd64-microcode (
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Just updated to 22.04 and seems like the 5.15.0-27-generic is working
well with the touchpad.
Thank you all for your hard work
--
You 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:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
I installed the Ubuntu 21.10 beta and as soon as I boot I get the
kernel panic that I am attaching.
I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
5.13 kernel I get the same problem, disabling the trackpad and
trackpoint in the bios the problem disappears.
Everything works with the 5.11 kernel.
I remain available for further details and sorry for my lack of experience.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-16-generic 5.13.0-16.16
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pietro 1810 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 30 10:26:10 2021
InstallationDate: Installed on 2021-09-29 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20TA0033IX
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
dmi.bios.date: 09/02/2021
dmi.bios.release: 1.43
dmi.bios.vendor: LENOVO
dmi.bios.version: R1EET43W(1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TA0033IX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.43
dmi.modalias:
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E14 Gen 2
dmi.product.name: 20TA0033IX
dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
dmi.product.version: ThinkPad E14 Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load
Christopher,
Thank-you for the work you have put into researching this. It is really
appreciated.
The system I originally used to reproduce this bug has since been updated to:
linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1
I have just attempted to reproduce the issue and I have been unable to.
That is consistent with your findings.
I have also reviewed the git commit you identified and I agree that it
is very likely that that commit fixed the bur reported here.
I am going to update the error message reported by Apache Tomcat to
update to the OS to a version that uses kernel 5.10 or greater.
I would close this issue as fixed but I don't appear to have the
necessary karma to do that.
Thanks again for your extremely helpful research.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1924298
Title:
accept returns duplicate endpoints under load
Status in Linux:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
When accepting client connections under load, duplicate endpoints may
be returned. These endpoints will have different (usually sequential)
file descriptors but will refer to the same connection (same server
IP, same server port, same client IP, same client port). Both copies
of the endpoint appear to be functional.
Reproduction requires:
- compilation of the attached server.c program
- wrk (https://github.com/wg/wrk) to generate load
The steps to reproduce are:
- run 'server' application in one console window
- run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency
--timeout 1s http://localhost:/post; done' in a second console window
- run the same command in a third window to generate concurrent load
You may need to run additional instance of the wrk command in multiple
windows to trigger the issue.
When the problem occurs the server executable will exit and print some
debugging info. e.g.:
accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient
= 232
This indicates that the sockets with file descriptors 233 and 232 are
duplicates.
The issue has been reproduced on fully patched versions of Ubuntu
20.04 and 18.04. Other versions have not been tested.
This issue was originally observed in Java and was reported against the
Spring Framework:
https://github.com/spring-projects/spring-framework/issues/26434
Investigation from the Spring team and the Apache Tomcat team identified that
it appeared to be a JDK issue:
https://bugs.openjdk.java.net/browse/JDK-8263243
Further research from the JDK team determined that the issue was at
the OS level. Hence this report.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-71-generic 5.4.0-71.79
ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
Uname: Linux 5.4.0-71-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 15 12:52:53 2021
HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
InstallationDate: Installed on 2017-02-02 (1532 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig:
lono wireless extensions.
docker0 no wireless extensions.
eno1 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. Default string
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic
root=/dev/mapper/ubuntu--vg-root ro text
RelatedPackageVersions:
linux-restricted-modules-5.4.0-71-generic N/A
linux-backports-modules-5.4.0-71-generic N/A
linux-firmware1.187.10
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
dmi.bios.date: 06/13/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F22
dmi.board.asset.tag: Default string
dmi.board.name: X99-SLI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1924298/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :
[Kernel-packages] [Bug 1967820] Re: Touchpad incorrectly detected as PS/2 mouse in 'Galago Pro 5' after the kernel upgrade.
In /proc/bus/input/devices, the correct info is: I: Bus=0018 Vendor=2808 Product=0101 Version=0100 N: Name="PNP0C50:00 2808:0101 Touchpad" P: Phys=i2c-PNP0C50:00 S: Sysfs=/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-PNP0C50:00/0018:2808:0101.0001/input/input16 U: Uniq= H: Handlers=mouse1 event11 B: PROP=5 B: EV=1b B: KEY=e520 1 0 0 0 0 B: ABS=2e08003 B: MSC=20 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967820 Title: Touchpad incorrectly detected as PS/2 mouse in 'Galago Pro 5' after the kernel upgrade. Status in linux package in Ubuntu: Confirmed Bug description: Computer model 'galp5'. The issue started after updating everything, including the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1360 F pulseaudio CurrentDesktop: KDE Date: Mon Apr 4 20:24:07 2022 InstallationDate: Installed on 2022-04-03 (1 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:9102 Acer, Inc BisonCam,NB Pro Bus 001 Device 005: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Galago Pro ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-39-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-39-generic N/A linux-backports-modules-5.13.0-39-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2021 dmi.bios.release: 4.13 dmi.bios.vendor: coreboot dmi.bios.version: 2021-07-20_93c2809 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp5 dmi.chassis.type: 9 dmi.chassis.vendor: System76 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr2021-07-20_93c2809:bd07/20/2021:br4.13:efr0.0:svnSystem76:pnGalagoPro:pvrgalp5:rvnSystem76:rnGalagoPro:rvrgalp5:cvnSystem76:ct9:cvr:sku: dmi.product.name: Galago Pro dmi.product.version: galp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967820] Re: Touchpad incorrectly detected as PS/2 mouse in 'Galago Pro 5' after the kernel upgrade.
I completely reinstalled Kubuntu, then ran: sudo apt update sudo apt upgrade sudo apt install neofetch I rebooted, and the Touchpad is still detected, ran neofetch: `.:/osssso/:. mark@mark-Galago-Pro .:oyyo:` -oyyyodMMso- OS: Kubuntu 21.10 x86_64 -syydMMyodmMMys- Host: Galago Pro galp5 oyyysdMysdMyyyo Kernel: 5.13.0-39-generic `odysyysoodyo`Uptime: 6 mins oyydsdMMysyyyoPackages: 1969 (dpkg) -dMysyysdMysyyy- Shell: bash 5.1.8 osoodMyyydysyyyo Resolution: 1920x1080 yyysdMyyysos DE: Plasma 5.22.5 yyysdMyy WM: KWin oysosdyyydysyyyo Theme: Breeze Light [Plasma], Breeze [GTK2/3] -dMysyysdMysyyy- Icons: breeze [Plasma], breeze [GTK2/3] oyydMMMysyyysdMMyoyyyoyyyoTerminal: konsole `odMMMysyyyoodyoo CPU: 11th Gen Intel i5-1135G7 (8) @ 4.200GHz oyyysyyosdMMMo GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics] -sydMMMysyyydMMMyss- Memory: 1584MiB / 39969MiB -oyyydMMyyysoso- ./oyyo/. `.:/oossso/:.` Thus I do not know how to reproduce the error. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967820 Title: Touchpad incorrectly detected as PS/2 mouse in 'Galago Pro 5' after the kernel upgrade. Status in linux package in Ubuntu: Confirmed Bug description: Computer model 'galp5'. The issue started after updating everything, including the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1360 F pulseaudio CurrentDesktop: KDE Date: Mon Apr 4 20:24:07 2022 InstallationDate: Installed on 2022-04-03 (1 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:9102 Acer, Inc BisonCam,NB Pro Bus 001 Device 005: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Galago Pro ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-39-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-39-generic N/A linux-backports-modules-5.13.0-39-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2021 dmi.bios.release: 4.13 dmi.bios.vendor: coreboot dmi.bios.version: 2021-07-20_93c2809 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp5 dmi.chassis.type: 9 dmi.chassis.vendor: System76 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr2021-07-20_93c2809:bd07/20/2021:br4.13:efr0.0:svnSystem76:pnGalagoPro:pvrgalp5:rvnSystem76:rnGalagoPro:rvrgalp5:cvnSystem76:ct9:cvr:sku: dmi.product.name: Galago Pro dmi.product.version: galp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967820] [NEW] Touchpad incorrectly detected as PS/2 mouse in 'Galago Pro 5' after the kernel upgrade.
Public bug reported: Computer model 'galp5'. The issue started after updating everything, including the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1360 F pulseaudio CurrentDesktop: KDE Date: Mon Apr 4 20:24:07 2022 InstallationDate: Installed on 2022-04-03 (1 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:9102 Acer, Inc BisonCam,NB Pro Bus 001 Device 005: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Galago Pro ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-39-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-39-generic N/A linux-backports-modules-5.13.0-39-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2021 dmi.bios.release: 4.13 dmi.bios.vendor: coreboot dmi.bios.version: 2021-07-20_93c2809 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp5 dmi.chassis.type: 9 dmi.chassis.vendor: System76 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr2021-07-20_93c2809:bd07/20/2021:br4.13:efr0.0:svnSystem76:pnGalagoPro:pvrgalp5:rvnSystem76:rnGalagoPro:rvrgalp5:cvnSystem76:ct9:cvr:sku: dmi.product.name: Galago Pro dmi.product.version: galp5 dmi.sys.vendor: System76 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish wayland-session ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1967820/+attachment/5577121/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967820 Title: Touchpad incorrectly detected as PS/2 mouse in 'Galago Pro 5' after the kernel upgrade. Status in linux package in Ubuntu: Confirmed Bug description: Computer model 'galp5'. The issue started after updating everything, including the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1360 F pulseaudio CurrentDesktop: KDE Date: Mon Apr 4 20:24:07 2022 InstallationDate: Installed on 2022-04-03 (1 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:9102 Acer, Inc BisonCam,NB Pro Bus 001 Device 005: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Galago Pro ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-39-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-39-generic N/A linux-backports-modules-5.13.0-39-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2021 dmi.bios.release: 4.13 dmi.bios.vendor: coreboot dmi.bios.version: 2021-07-20_93c2809 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp5 dmi.chassis.type: 9 dmi.chassis.vendor: System76 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr2021-07-20_93c2809:bd07/20/2021:br4.13:efr0.0:svnSystem76:pnGalagoPro:pvrgalp5:rvnSystem76:rnGalagoPro:rvrgalp5:cvnSystem76:ct9:cvr:sku: dmi.product.name: Galago Pro dmi.product.version: galp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] Re: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend
Tried with a live medium of Ubuntu Jammy Beta. Also reproducable here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576321/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576320/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] Re: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend
Tested on the current Kubuntu Jammy Beta. Same problem. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576319/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576309/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576310/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576312/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576313/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576311/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576318/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576317/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576314/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576307/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576315/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576316/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576305/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576308/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576306/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576304/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-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: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] Re: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend
apport information ** Tags added: apport-collected jammy staging ** Description changed: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. - What is the difference to the formerly known bugs: It is possible to get - the Trackpoint working by sending the system into suspend and waking it - up again. After this the Trackpoint works without a problem. So the - problem might have something to do with the driver not correctly loaded - at boot, but this is done correctly when the system wakes up from - suspend. + What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu79 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: kubuntu3913 F pulseaudio + CasperMD5CheckResult: pass + CasperVersion: 1.468 + CurrentDesktop: KDE + DistroRelease: Ubuntu 22.04 + LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) + Lsusb: + Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface + Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: LENOVO 20JBCTO1WW + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- + ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-23-generic N/A + linux-backports-modules-5.15.0-23-generic N/A + linux-firmware 20220314.gitcd01f857-0ubuntu2 + StagingDrivers: ipu3_imgu + Tags: jammy staging + Uname: Linux 5.15.0-23-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: 11/29/2021 + dmi.bios.release: 1.43 + dmi.bios.vendor: LENOVO + dmi.bios.version: N1OET58W (1.43 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20JBCTO1WW + dmi.board.vendor: LENOVO + dmi.board.version: SDK0K17763 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 32 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.ec.firmware.release: 1.23 + dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: + dmi.product.family: ThinkPad + dmi.product.name: 20JBCTO1WW + dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad + dmi.product.version: ThinkPad X1 Tablet Gen 2 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1967188/+attachment/5576303/+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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse:
[Kernel-packages] [Bug 1967188] [NEW] Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend
Public bug reported: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: lenovo systemd-boot thinkpad trackpoint ** Tags added: lenovo systemd-boot thinkpad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: New Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964626] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1964626/+attachment/5568063/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964626 Title: Unable to launch 5.15.0-22-generic kernel (or its recovery mode) Status in linux package in Ubuntu: Confirmed Bug description: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daisy 1635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964626] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1964626/+attachment/5568057/+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/1964626 Title: Unable to launch 5.15.0-22-generic kernel (or its recovery mode) Status in linux package in Ubuntu: Confirmed Bug description: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daisy 1635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964626] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1964626/+attachment/5568062/+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/1964626 Title: Unable to launch 5.15.0-22-generic kernel (or its recovery mode) Status in linux package in Ubuntu: Confirmed Bug description: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daisy 1635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964626] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1964626/+attachment/5568058/+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/1964626 Title: Unable to launch 5.15.0-22-generic kernel (or its recovery mode) Status in linux package in Ubuntu: Confirmed Bug description: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daisy 1635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964626] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1964626/+attachment/5568059/+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/1964626 Title: Unable to launch 5.15.0-22-generic kernel (or its recovery mode) Status in linux package in Ubuntu: Confirmed Bug description: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daisy 1635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964626] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1964626/+attachment/5568060/+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/1964626 Title: Unable to launch 5.15.0-22-generic kernel (or its recovery mode) Status in linux package in Ubuntu: Confirmed Bug description: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daisy 1635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964626] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1964626/+attachment/5568056/+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/1964626 Title: Unable to launch 5.15.0-22-generic kernel (or its recovery mode) Status in linux package in Ubuntu: Confirmed Bug description: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daisy 1635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964626] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1964626/+attachment/5568061/+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/1964626 Title: Unable to launch 5.15.0-22-generic kernel (or its recovery mode) Status in linux package in Ubuntu: Confirmed Bug description: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daisy 1635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964626] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1964626/+attachment/5568055/+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/1964626 Title: Unable to launch 5.15.0-22-generic kernel (or its recovery mode) Status in linux package in Ubuntu: Confirmed Bug description: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daisy 1635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964626] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1964626/+attachment/5568051/+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/1964626 Title: Unable to launch 5.15.0-22-generic kernel (or its recovery mode) Status in linux package in Ubuntu: Confirmed Bug description: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daisy 1635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964626] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1964626/+attachment/5568054/+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/1964626 Title: Unable to launch 5.15.0-22-generic kernel (or its recovery mode) Status in linux package in Ubuntu: Confirmed Bug description: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daisy 1635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964626] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1964626/+attachment/5568052/+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/1964626 Title: Unable to launch 5.15.0-22-generic kernel (or its recovery mode) Status in linux package in Ubuntu: Confirmed Bug description: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daisy 1635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964626] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1964626/+attachment/5568053/+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/1964626 Title: Unable to launch 5.15.0-22-generic kernel (or its recovery mode) Status in linux package in Ubuntu: Confirmed Bug description: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daisy 1635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964626] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1964626/+attachment/5568050/+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/1964626 Title: Unable to launch 5.15.0-22-generic kernel (or its recovery mode) Status in linux package in Ubuntu: Confirmed Bug description: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daisy 1635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964626] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1964626/+attachment/5568049/+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/1964626 Title: Unable to launch 5.15.0-22-generic kernel (or its recovery mode) Status in linux package in Ubuntu: Confirmed Bug description: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daisy 1635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 RfKill: Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964626] Re: Unable to launch 5.15.0-22-generic kernel (or its recovery mode)
apport information ** Tags added: apport-collected ** Description changed: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu78 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: daisy 1635 F pulseaudio + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-02-26 (13 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) + IwConfig: + lono wireless extensions. + + enp0s3no wireless extensions. + Lsusb: + Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Lsusb-t: + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M + MachineType: innotek GmbH VirtualBox + Package: linux (not installed) + ProcFB: 0 svgadrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash + ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-18-generic N/A + linux-backports-modules-5.15.0-18-generic N/A + linux-firmware 20220302.gitee0667aa-0ubuntu1 + RfKill: + + Tags: wayland-session jammy + Uname: Linux 5.15.0-18-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf + _MarkForUpload: True + dmi.bios.date: 12/01/2006 + dmi.bios.vendor: innotek GmbH + dmi.bios.version: VirtualBox + dmi.board.name: VirtualBox + dmi.board.vendor: Oracle Corporation + dmi.board.version: 1.2 + dmi.chassis.type: 1 + dmi.chassis.vendor: Oracle Corporation + dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: + dmi.product.family: Virtual Machine + dmi.product.name: VirtualBox + dmi.product.version: 1.2 + dmi.sys.vendor: innotek GmbH ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1964626/+attachment/5568048/+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/1964626 Title: Unable to launch 5.15.0-22-generic kernel (or its recovery mode) Status in linux package in Ubuntu: Confirmed Bug description: I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple of weeks and just updating and upgrading using apt. When restarting the VM (VirtualBox), I get the screen in the screenshot below. The same thing happens if I select the 5.15.0-22-generic options - normal or recovery mode - from the grub list in advanced options. I can boot into 5.15.0-18-generic with no issues. I have attempted to run upgrade-grub to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 11 18:17:17 2022 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daisy 1635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-26 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish"
[Kernel-packages] [Bug 1908090] Re: ubuntu 20.04 kdump fails
Yes, me too. The same fix fixed it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1908090 Title: ubuntu 20.04 kdump fails Status in kexec-tools package in Ubuntu: Confirmed Bug description: When linux-crashdump (5.4.0.58.61) is enabled on Ubuntu 20.04 LTS, everything appears to be in good working order, according to "systemctl status kdump-tools" and "kdump-config status". However, upon an actual crash, the system hangs, and no crash files are produced. I've investigated and have learned that the capture kernel does indeed start, but it is unable to unpack the rootfs/initrd, and thus fails and hangs. [1.070469] Trying to unpack rootfs image as initramfs... [1.333182] swapper/0 invoked oom-killer: gfp_mask=0x100cc2(GFP_HIGHUSER), order=0, oom_score_adj=0 [1.335074] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-26-generic #30-Ubuntu [1.336396] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [1.336396] Call Trace: [1.336396] dump_stack+0x6d/0x9a [1.336396] dump_header+0x4f/0x1eb [1.336396] out_of_memory.part.0.cold+0x39/0x83 [1.336396] out_of_memory+0x6d/0xd0 ... [1.413202] ---[ end Kernel panic - not syncing: System is deadlocked on memory ]--- On this system with 8G of memory, the crash memory as specified on the kernel command line is "crashkernel=512M-:192M". I changed the 192M to 256M, and now kdump works. Not sure how the 192M value is chosen, but it does not work. I think this used value used to work for 16.04 and maybe 18.04 (I didn't try), but is no longer useful for 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1908090/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962053] [NEW] Modules missing from package install
Public bug reported: Sorry I'm new to Ubuntu but I have been trying to get microK8s to work on my Raspi Pi4/8Gb for a while now - the instructions are simple enough and I have K8s and Docker running and working on other OS so... But no matter what I try I can't get a stable set of services running. Having investigated this I think the problem could be something to do with this: The microk8s inspect command reports iptables/1.8.7 Failed to initialize nft: Protocol not supported ERROR: Couldn't determine iptables version Following various threads on the internet people suggest checking if iptables is part of the kernel or a module ubuntu@aitu20pi42:~$ grep -i iptables /boot/config-$(uname -r) CONFIG_IP_NF_IPTABLES=m CONFIG_IP6_NF_IPTABLES=m # iptables trigger is under Netfilter config (LED target) So checking if the iptables module is installed / present ubuntu@aitu20pi42:~$ modinfo ip_tables modinfo: ERROR: Module ip_tables not found. ubuntu@aitu20pi42:~$ modprobe ip_tables modprobe: FATAL: Module ip_tables not found in directory /lib/modules/5.13.0-1017-raspi >From the package file list and what I have read I would expect to find a file /lib/modules/5.13.0-1017-raspi/kernel/net/ipv4/netfilter/ip_tables.ko But in fact there are only these two modules in /net/ipv4 ubuntu@aitu20pi42:~$ ls /lib/modules/5.13.0-1017-raspi/kernel/net/ipv4 gre.ko udp_tunnel.ko there is no netfilter directory in either /ipv4 or /ipv6 or /bridge ubuntu@aitu20pi42:~$ ls /lib/modules/5.13.0-1017-raspi/kernel/net/ipv6 ip6_tunnel.ko ip6_udp_tunnel.ko tunnel6.ko. While trying to resolve my problem I came across suggestions that said to try reinstalling the linux-modules package (because that's where they are?) so I've tried with linux-modules-5.13.0-1016-raspi and I've just upgraded to linux- modules-5.13.0-1017-raspi to no avail. I also came across this Bug #1942691 https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1942691 and while I appreciate they are missing a different module; rpi-poe-fan, some of what they describe; "I can['t] even find it under the relevant path in /lib/modules." and "If I do not put the module in /etc/initramfs-tools/modules the module will not be there after a reboot (e.g. remove from the filesystem). And this is so for a lot of the other modules. I am booting from iSCSI and even the NFS modules are gone. As far as I know this wasn't the case in previous version." So I'm wondering if these issues are related and my problem is perhaps part of a wider problem? I know my problem originally manifested itself as an issue with microk8s and I'm not convinced that it is solely down to a missing ip_tables modules but I don't think its just a microk8s problem because if I try to do anything with the firewall for example ubuntu@aitu20pi42:~$ sudo ufw status ERROR: Couldn't determine iptables version or ubuntu@aitu20pi42:~$ sudo iptables -P FORWARD ACCEPT iptables/1.8.7 Failed to initialize nft: Protocol not supported I get the same problem but ufw is just a wrapper around iptables and since ufw is installed it seems reasonable to expect that its dependencies are installed also. I'm obviously not a linux expert but I'm not alone in thinking that I should be able to find a whole bunch of *.ko files beneath /lib/modules/**/ or more than I can presently. If you need any more information from me, to investigate this further, then please let me know what commands to run and I'll report back what I find. System info below. Welcome to Ubuntu 21.10 (GNU/Linux 5.13.0-1017-raspi aarch64) System load: 1.13 Temperature: 37.0 C Usage of /: 4.7% of 223.19GB Processes: 142 Memory usage: 2% Users logged in: 0 Swap usage: 0% IPv4 address for eth0: 192.168.1.58 ubuntu@aitu20pi42:~$ lsb_release -rd Description:Ubuntu 21.10 Release:21.10 ** 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/1962053 Title: Modules missing from package install Status in linux-raspi package in Ubuntu: New Bug description: Sorry I'm new to Ubuntu but I have been trying to get microK8s to work on my Raspi Pi4/8Gb for a while now - the instructions are simple enough and I have K8s and Docker running and working on other OS so... But no matter what I try I can't get a stable set of services running. Having investigated this I think the problem could be something to do with this: The microk8s inspect command reports iptables/1.8.7 Failed to initialize nft: Protocol not supported ERROR: Couldn't determine iptables version Following various threads on the internet people suggest checking if iptables is part of the kernel or a module ubuntu@aitu20pi42:~$ grep -i
[Kernel-packages] [Bug 1939210] Re: When using HWE, zfs-kmod and zfs user tools versions must match
I see a lot of people somehow subscribed to this bug. But only 17 registered as this bug affects them. Could i politely ask more people to vote for this issue. So it might be noticed before 22.04. Since we need a fix before then or we will live with this for 2 more years in the new LTS. Best regards, Darkyere -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939210 Title: When using HWE, zfs-kmod and zfs user tools versions must match Status in zfs-linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.2 LTS I ran into a problem recently (https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177) due to mismatched versions when HWE upgraded the kernel from 5.8 to 5.11 where the userspace tools don't match the zfs-kmod version. After the update the system ended up with zfs-0.8.3-1ubuntu12.12 and zfs- kmod-2.0.2-1ubuntu5 My understanding from asking in the OpenZFS github is that the two versions must match. This bug is to figure out what to do for those of us who use HWE and zfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
