[Kernel-packages] [Bug 2056666] Re: [RTL8822CE] i could not able to connect my bluetooth headphone or for context any headphone to my ubuntu machine
After some updates on friday, this morning, I was able to connect my headset. -- 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/205 Title: [RTL8822CE] i could not able to connect my bluetooth headphone or for context any headphone to my ubuntu machine Status in bluez package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Bug description: headphone is not showing up in my ubuntu bluetooth so i cant connect my headphone to my computer ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 14:10:46 2024 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 82C7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-25-generic root=UUID=bed00b3d-206b-4607-8c0b-63d4f55998ef ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-ADA dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnLENOVO:bvrE8CN38WW:bd12/05/2022:br1.38:efr1.38:svnLENOVO:pn82C7:pvrLenovoV15-ADA:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoV15-ADA:skuLENOVO_MT_82C7_BU_idea_FM_V15-ADA: dmi.product.family: V15-ADA dmi.product.name: 82C7 dmi.product.sku: LENOVO_MT_82C7_BU_idea_FM_V15-ADA dmi.product.version: Lenovo V15-ADA dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 28:CD:C4:D1:98:3A ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:35089 acl:0 sco:0 events:1074 errors:0 TX bytes:48329 acl:0 sco:0 commands:549 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/205/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056666] Re: [RTL8822CE] i could not able to connect my bluetooth headphone or for context any headphone to my ubuntu machine
Hi! Since this morning, I'm not able to plug my bluetooth headset. The bluetooth remains off, even after trying to activate it from the settings. I already did a reboot, but nothing changed. My laptop is a Lenovo P15s. Ubuntu 22.04.4 6.2.0-31-generic -- 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/205 Title: [RTL8822CE] i could not able to connect my bluetooth headphone or for context any headphone to my ubuntu machine Status in bluez package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Bug description: headphone is not showing up in my ubuntu bluetooth so i cant connect my headphone to my computer ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 14:10:46 2024 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 82C7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-25-generic root=UUID=bed00b3d-206b-4607-8c0b-63d4f55998ef ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-ADA dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnLENOVO:bvrE8CN38WW:bd12/05/2022:br1.38:efr1.38:svnLENOVO:pn82C7:pvrLenovoV15-ADA:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoV15-ADA:skuLENOVO_MT_82C7_BU_idea_FM_V15-ADA: dmi.product.family: V15-ADA dmi.product.name: 82C7 dmi.product.sku: LENOVO_MT_82C7_BU_idea_FM_V15-ADA dmi.product.version: Lenovo V15-ADA dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 28:CD:C4:D1:98:3A ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:35089 acl:0 sco:0 events:1074 errors:0 TX bytes:48329 acl:0 sco:0 commands:549 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/205/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
I can confirm this! Some games do crash because of a to low VM_max_map_count. This change will improve the gaming experience on Ubuntu and thus would be a nice one to have in the next LTS release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2057792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055248] [NEW] snap pc-kernel missing bluetooth firmware for dell latptops
Public bug reported: Hello, The snap packages pc-kernel from ubuntu 22 to 24 are missing firmware for bluetooth to work properly on dell laptops. The firmware are available on linux-firmware apt package meaning that both distribution medium are not aligned. pc-kernel is required to get tpm full disk encryption so no easy workaround exists. dmesg | grep firmware [ 9.281169] bluetooth hci0: Direct firmware load for mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failed with error -2 [ 9.281179] Bluetooth: hci0: Failed to load firmware file (-2) [ 9.281422] Bluetooth: hci0: Failed to set up firmware (-2) ls /usr/lib/firmware/mediatek BT_RAM_CODE_MT7961_1_2_hdr.bin mt7615_cr4.bin mt7622pr2h.bin mt7663_n9_v3.bin mt7668pr2h.bin mt7915_wm.bin mt7916_wm.bin WIFI_RAM_CODE_MT7922_1.bin mt7610e.bin mt7615_n9.bin mt7650e.bin mt7663pr2h.bin mt7915_rom_patch.bin mt7916_rom_patch.bin WIFI_MT7922_patch_mcu_1_1_hdr.bin WIFI_RAM_CODE_MT7961_1.bin mt7610u.bin mt7615_rom_patch.bin mt7663_n9_rebb.bin mt7663pr2h_rebb.bin mt7915_wa.bin mt7916_wa.bin WIFI_MT7961_patch_mcu_1_2_hdr.bin mount | grep /usr/lib/firmware /run/mnt/data/var/lib/snapd/snaps/pc-kernel_1627.snap on /usr/lib/firmware type squashfs (ro,relatime,errors=continue,threads=single) /run/mnt/data/var/lib/snapd/snaps/pc-kernel_1627.snap on /run/mnt/data/usr/lib/firmware type squashfs (ro,relatime,errors=continue,threads=single) ** 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/2055248 Title: snap pc-kernel missing bluetooth firmware for dell latptops Status in linux package in Ubuntu: New Bug description: Hello, The snap packages pc-kernel from ubuntu 22 to 24 are missing firmware for bluetooth to work properly on dell laptops. The firmware are available on linux-firmware apt package meaning that both distribution medium are not aligned. pc-kernel is required to get tpm full disk encryption so no easy workaround exists. dmesg | grep firmware [ 9.281169] bluetooth hci0: Direct firmware load for mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failed with error -2 [ 9.281179] Bluetooth: hci0: Failed to load firmware file (-2) [ 9.281422] Bluetooth: hci0: Failed to set up firmware (-2) ls /usr/lib/firmware/mediatek BT_RAM_CODE_MT7961_1_2_hdr.bin mt7615_cr4.bin mt7622pr2h.bin mt7663_n9_v3.bin mt7668pr2h.bin mt7915_wm.bin mt7916_wm.bin WIFI_RAM_CODE_MT7922_1.bin mt7610e.bin mt7615_n9.bin mt7650e.bin mt7663pr2h.bin mt7915_rom_patch.bin mt7916_rom_patch.bin WIFI_MT7922_patch_mcu_1_1_hdr.bin WIFI_RAM_CODE_MT7961_1.bin mt7610u.bin mt7615_rom_patch.bin mt7663_n9_rebb.bin mt7663pr2h_rebb.bin mt7915_wa.bin mt7916_wa.bin WIFI_MT7961_patch_mcu_1_2_hdr.bin mount | grep /usr/lib/firmware /run/mnt/data/var/lib/snapd/snaps/pc-kernel_1627.snap on /usr/lib/firmware type squashfs (ro,relatime,errors=continue,threads=single) /run/mnt/data/var/lib/snapd/snaps/pc-kernel_1627.snap on /run/mnt/data/usr/lib/firmware type squashfs (ro,relatime,errors=continue,threads=single) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048105] [NEW] Connecting second bluetooth device fails
Public bug reported: System: Ubuntu 22.04 bluez version 5.64 Devices: 2x Playstation 5 DualSense Controllers Problem description: Connecting either of the controllers individually works without a problem. But when trying to connect both of them, the second fails. Following sequence is typical and shows that there is no problem with the controllers itself: 1) connect controller #1 > succeeds 2) connect controller #2 > fails 3) disconnect controller #1 4) connect controller #2 > succeeds 5) connect controller #1 > fails SOMETIMES it works though and I didn't found out what was different. Connecting both of the controllers immediately after boot+logon works most of the times! When connecting a controller fails, there is _nothing_ in syslog. Both controllers have been paired successfully and marked as trusted devices. The failing connect attempt of the second controller first shows the system notification "connected", followed by a "disconnected" approximately 10-20 seconds later. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- 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/2048105 Title: Connecting second bluetooth device fails Status in bluez package in Ubuntu: New Bug description: System: Ubuntu 22.04 bluez version 5.64 Devices: 2x Playstation 5 DualSense Controllers Problem description: Connecting either of the controllers individually works without a problem. But when trying to connect both of them, the second fails. Following sequence is typical and shows that there is no problem with the controllers itself: 1) connect controller #1 > succeeds 2) connect controller #2 > fails 3) disconnect controller #1 4) connect controller #2 > succeeds 5) connect controller #1 > fails SOMETIMES it works though and I didn't found out what was different. Connecting both of the controllers immediately after boot+logon works most of the times! When connecting a controller fails, there is _nothing_ in syslog. Both controllers have been paired successfully and marked as trusted devices. The failing connect attempt of the second controller first shows the system notification "connected", followed by a "disconnected" approximately 10-20 seconds later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2048105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642112] Re: Can’t connect to the second BT device successfully
@Daniel van Vugt ok -- 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/1642112 Title: Can’t connect to the second BT device successfully Status in bluez package in Ubuntu: New Bug description: OS: 14.04 bluez version: 4.x After first bt device(eg. mouse) connected, try to connect second device(eg. keyboard), found it has no function when connected, and sometimes it fails to connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1642112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642112] Re: Can’t connect to the second BT device successfully
Same problem for me. System: Ubuntu 22.04 bluez version 5.64 Devices: 2x Playstation 5 DualSense Controllers Problem description: Connecting either of the controllers individually works without a problem. But when trying to connect both of them, the second fails. SOMETIMES it works though and I didn't found out what was different. Can someome tell, if this is fixed in newer versions? If yes, I will try a system upgrade out of the LTS sequence. -- 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/1642112 Title: Can’t connect to the second BT device successfully Status in bluez package in Ubuntu: New Bug description: OS: 14.04 bluez version: 4.x After first bt device(eg. mouse) connected, try to connect second device(eg. keyboard), found it has no function when connected, and sometimes it fails to connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1642112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024187] Re: xfrm: packets sent trough a raw socket don't match ipsec policies with proto selector
For the record, the patch has been backported in Lunar/Jammy/Focal:
https://lists.ubuntu.com/archives/kernel-team/2023-August/141562.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2024187
Title:
xfrm: packets sent trough a raw socket don't match ipsec policies with
proto selector
Status in linux package in Ubuntu:
Expired
Bug description:
[Impact]
When a userland application sends packets through an IPv4 or IPv6 raw
socket, these packets don't match ipsec policies that are configured
with a protocol selector.
The problem has been fixed in linux v6.4 with commit 3632679d9e4f
("ipv{4,6}/raw: fix output xfrm lookup wrt protocol").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3632679d9e4f
This commit has been backported in linux 5.15.115:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=395d846c61c5
[Test Case]
Configure an ipsec policy with a protocol selector and send ip packets
that match this policy through an IP raw socket.
Example to match the proto icmp:
ip xfrm policy add src 10.100.0.0/24 dst 10.200.0.0/24 proto icmp dir out
tmpl src 10.125.0.1 dst 10.125.0.2 proto esp mode tunnel reqid 1
[Regression Potential]
The patch introduces a new API to fix this problem, thus the
regression potential is low for existing applications.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024187/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036456] [NEW] linux-firmware mantic missing intel/ibt-{19, 20}*
Public bug reported:
linux-firmware on mantic (20230915.gitdfa11466-0ubuntu1) is missing
/intel/ibt-{19,20}-*
firmwares. When booting I get the following error message:
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Bootloader revision 0.1
build 0 week 30 2018
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Device revision is 2
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Secure boot is enabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: OTP lock is enabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: API lock is enabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Debug lock is disabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Minimum firmware build 1
week 10 2014
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Failed to load Intel
firmware file intel/ibt-19-0-1.sfi (-2)
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Reading supported features
failed (-56)
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Error reading debug
features
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Failed to read MSFT
supported features (-56)
Hardware used is:
ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2036456
Title:
linux-firmware mantic missing intel/ibt-{19,20}*
Status in linux-firmware package in Ubuntu:
New
Bug description:
linux-firmware on mantic (20230915.gitdfa11466-0ubuntu1) is missing
/intel/ibt-{19,20}-*
firmwares. When booting I get the following error message:
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Bootloader revision 0.1
build 0 week 30 2018
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Device revision is 2
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Secure boot is enabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: OTP lock is enabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: API lock is enabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Debug lock is disabled
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Minimum firmware build 1
week 10 2014
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Failed to load Intel
firmware file intel/ibt-19-0-1.sfi (-2)
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Reading supported
features failed (-56)
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Error reading debug
features
Sep 18 13:01:18 rubberducky kernel: Bluetooth: hci0: Failed to read MSFT
supported features (-56)
Hardware used is:
ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036456/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035398] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700689/+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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device
[Kernel-packages] [Bug 2035398] Re: PM: hibernation: Image mismatch: architecture specific data
Sorry, I am not sure whether I was supposed to change the status of this to "confirmed". Changed it back to "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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp.
[Kernel-packages] [Bug 2035398] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700688/+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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID
[Kernel-packages] [Bug 2035398] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700690/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => 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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux
[Kernel-packages] [Bug 2035398] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700686/+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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device
[Kernel-packages] [Bug 2035398] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700687/+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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID
[Kernel-packages] [Bug 2035398] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700685/+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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001
[Kernel-packages] [Bug 2035398] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700684/+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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera
[Kernel-packages] [Bug 2035398] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700682/+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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID
[Kernel-packages] [Bug 2035398] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700683/+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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device
[Kernel-packages] [Bug 2035398] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700681/+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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID
[Kernel-packages] [Bug 2035398] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700678/+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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID
[Kernel-packages] [Bug 2035398] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700680/+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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID
[Kernel-packages] [Bug 2035398] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700679/+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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003:
[Kernel-packages] [Bug 2035398] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700677/+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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003:
[Kernel-packages] [Bug 2035398] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700676/+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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001
[Kernel-packages] [Bug 2035398] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2035398/+attachment/5700675/+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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: Confirmed Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nbock 7015 F wireplumber /dev/snd/seq:nbock 6996 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2020-04-17 (1244 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 003: ID
[Kernel-packages] [Bug 2035398] Re: PM: hibernation: Image mismatch: architecture specific data
apport information
** Tags added: apport-collected mantic wayland-session
** Description changed:
Using
ii linux-headers-6.5.0-56.5.0-5.5all Header
files related to Linux kernel version 6.5.0
ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux
kernel headers for version 6.5.0 on 64 bit x86 SMP
ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed
kernel image generic
ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux
kernel extra modules for version 6.5.0 on 64 bit x86 SMP
ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux
kernel extra modules for version 6.5.0 on 64 bit x86 SMP
Resuming from hibernation fails with the following error messages:
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0x-0x0fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0x000a-0x000f]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0x99a0a000-0x99a1bfff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0x99a1d000-0x99a1]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0x99a22000-0x99a22fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0x99a24000-0x]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5d44c000-0xa5d44dfff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5d457000-0xa5d457fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5d469000-0xa5d469fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5d46c000-0xa5d4bafff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5d9ac000-0xa5d9acfff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e0f9000-0xa5e0fafff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e11e000-0xa5e125fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e1ea000-0xa5e1edfff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e1fd000-0xa5e205fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e20b000-0xa5e32afff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e33a000-0xa5e33cfff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e33e000-0xa5e33efff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e345000-0xa5e34dfff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e366000-0xa5e369fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e36f000-0xa5e3a1fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e3b7000-0xa5e3bbfff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e3c-0xa5e3d0fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages:
[mem 0xa5e3e-0xa5e3e1fff]
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps
created
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch:
architecture specific data
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in
0.01 seconds (1614130.00 MB/s)
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image,
recovering.
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps
freed
Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1)
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.27.0-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: nbock 7015 F wireplumber
+ /dev/snd/seq:nbock 6996 F pipewire
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 23.10
+ InstallationDate: Installed on 2020-04-17 (1244 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
+ Lsusb:
+ Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+ Bus 001 Device 002: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0
Camera
+ Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson
Peak (JfP)
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
+ NonfreeKernelModules: zfs
+ Package: linux (not installed)
+ ProcEnviron:
+ LANG=en_US.UTF-8
+ PATH=(custom, no user)
+
[Kernel-packages] [Bug 2035398] [NEW] PM: hibernation: Image mismatch: architecture specific data
Public bug reported: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x000a-0x000f] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a0a000-0x99a1bfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a1d000-0x99a1] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a22000-0x99a22fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0x99a24000-0x] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d44c000-0xa5d44dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d457000-0xa5d457fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d469000-0xa5d469fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d46c000-0xa5d4bafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5d9ac000-0xa5d9acfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e0f9000-0xa5e0fafff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e11e000-0xa5e125fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1ea000-0xa5e1edfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e1fd000-0xa5e205fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e20b000-0xa5e32afff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33a000-0xa5e33cfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e33e000-0xa5e33efff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e345000-0xa5e34dfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e366000-0xa5e369fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e36f000-0xa5e3a1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3b7000-0xa5e3bbfff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3c-0xa5e3d0fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Marking nosave pages: [mem 0xa5e3e-0xa5e3e1fff] Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps created Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Image mismatch: architecture specific data Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Read 16141300 kbytes in 0.01 seconds (1614130.00 MB/s) Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Failed to load image, recovering. Sep 13 13:54:29 rubberducky kernel: PM: hibernation: Basic memory bitmaps freed Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume failed (-1) ** 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/2035398 Title: PM: hibernation: Image mismatch: architecture specific data Status in linux package in Ubuntu: New Bug description: Using ii linux-headers-6.5.0-56.5.0-5.5all Header files related to Linux kernel version 6.5.0 ii linux-headers-6.5.0-5-generic6.5.0-5.5amd64Linux kernel headers for version 6.5.0 on 64 bit x86 SMP ii linux-image-6.5.0-5-generic 6.5.0-5.5amd64Signed kernel image generic ii linux-modules-6.5.0-5-generic6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-5-generic 6.5.0-5.5amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP Resuming from hibernation fails with the following error messages: Sep 13 13:54:29 rubberducky kernel: PM: hibernation: resume from hibernation Sep 13 13:54:29
Re: [Kernel-packages] [Bug 2028366] Re: Kernel header installation fails for incompatible DKMS modules
Hi Andreas, Anbox dkms module is incomptible with kernel 6.2.0-27-generic. Solution applied: 1- Anbox removed 2- Command applied: $ dkms remove anbox-ashmem/1 --all $ dkms remove anbox-binder/1 --all System is now ok. apt update : ok without error apt upgrade : ok without error Restart ok with the last kernel (6.2.0-31-generic) installed by the last update. Thanks a lot for your help. [https://d36urhup7zbd7q.cloudfront.net/a/5bfbaff9-9d34-4d3d-832c-070e4a3ea4f8.png#logo] Nicolas L'huillier Brasserie La Cavalière Occitane 0608889301 | <http://www.brasserielacavalièreoccitane.fr> www.brasserielacavaliereoccitane.fr<http://www.brasserielacavaliereoccitane.fr> <mailto:contact@brasserielacavalièreoccitane.fr>cont...@brasserielacavaliereoccitane.fr<mailto:cont...@brasserielacavaliereoccitane.fr><mailto:contact@brasserielacavalièreoccitane.fr> 311 route de devant la Save 31230 Anan<https://www.google.fr/maps/place/Brasserie+La+Cavali%C3%A8re+Occitane/@43.3542943,0.821968,17z/data=!3m1!4b1!4m6!3m5!1s0x12a91168d8f11c93:0x341191ec8c4e5c2f!8m2!3d43.3542904!4d0.8245429!16s%2Fg%2F11rsg5ys2b> <https://maps.google.com/?q=311%20route%20de%20devant%20la%20Save%2031230%20Anan> Ouverture brasserie : sur rendez-vous De : nore...@launchpad.net de la part de Andreas Hasenack <2028...@bugs.launchpad.net> Envoyé : jeudi 31 août 2023 15:11:12 À : Brasserie La Cavalière Occitane Objet : [Bug 2028366] Re: Kernel header installation fails for incompatible DKMS modules I suppose it's possible that the particular dkms module that failed to build is essential for booting the system, so the new approach that hides this build failure could render the system unbootable without the user realizing it. A bit less catastrophic, but still very serious, would be for the machine to lose network access (wifi driver), which could pose a chicken an egg problem (need network to fix the problem). So what we have here is a balance between a system with an interrupted release-upgrade, requiring a lot of apt-foo to fix, or a system where dkms rebuilds might have failed, but otherwise upgraded successfully. Both cases could result in an unbootable system, but I tend to agree that the first one (interrupted release-upgrade) is more likely to be much harder to recover (been there). I would like some sort of commitment on the follow-up work for the release upgrader to check the status of dkms builds after the upgrade. Can we get an LP bug for it please? -- You received this bug notification because you are subscribed to a duplicate bug report (2033408). https://bugs.launchpad.net/bugs/2028366 Title: Kernel header installation fails for incompatible DKMS modules Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Jammy: Confirmed Status in dkms source package in Lunar: Fix Released Status in dkms source package in Mantic: Fix Released Bug description: [ Impact ] If a new kernel is installed, all installed DKMS modules are built for that new kernel. There might be incompatible modules that won't compile for the new kernel which results in a kernel header package installation failure. That's bad and not really correct, the incompatible DKMS module is the problem and not the new kernel. In this case, DKMS module build failures should be ignored so that the kernel installation completes. This is especially acute during release-upgrades, as dkms modules are upgraded out of order, and major kernel version are upgraded out of order. Majority of the time there is a new dkms available, which should attempt build & load. However, many modules are often remain broken, no longer needed, or need user to fetch updated versions themselves. [ Test Plan ] * Install jammy * Add module that support v5.15 kernel, but fails to compile with any newer kernels (one can find examples of such dkms modules in the archive, or out of the archive) * Perform release upgrade with patched dkms pre-installed * Release upgrade should succeed, despite unable to compile all dkms modules [ Where problems could occur ] * This is an improvement to the current situation of aborting release upgrade half way through. It doesn't quite resolve the UX to notify the user which dkms modules did not manage to compile, or to ask user to uninstall or to update them. Further UX / hooks might be needed in the release upgrade to complete the story of asking the user what they want to do with regressed dkms modules. [ Other Info ] * See lots and lots of upgrade bugs, failing on dkms module installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2028366/+subscriptions ** Attachment added: "=?Windows-1252?Q?Capture_d=92=E9cran_du_2023-08-31_18-56-37.png?=" https://bugs.launchpad.net/bugs/2028366/+att
Re: [Kernel-packages] [Bug 2033408] Re: package linux-headers-generic 6.2.0.31.29 failed to install/upgrade: problèmes de dépendances - laissé non configuré
*** This bug is a duplicate of bug 2028366 *** https://bugs.launchpad.net/bugs/2028366 Thanks a lot. It's done. Bug solved. Best regards. [https://d36urhup7zbd7q.cloudfront.net/a/5bfbaff9-9d34-4d3d-832c-070e4a3ea4f8.png#logo] Nicolas L'huillier Brasserie La Cavalière Occitane 0608889301 | <http://www.brasserielacavalièreoccitane.fr> www.brasserielacavaliereoccitane.fr<http://www.brasserielacavaliereoccitane.fr> <mailto:contact@brasserielacavalièreoccitane.fr>cont...@brasserielacavaliereoccitane.fr<mailto:cont...@brasserielacavaliereoccitane.fr><mailto:contact@brasserielacavalièreoccitane.fr> 311 route de devant la Save 31230 Anan<https://www.google.fr/maps/place/Brasserie+La+Cavali%C3%A8re+Occitane/@43.3542943,0.821968,17z/data=!3m1!4b1!4m6!3m5!1s0x12a91168d8f11c93:0x341191ec8c4e5c2f!8m2!3d43.3542904!4d0.8245429!16s%2Fg%2F11rsg5ys2b> <https://maps.google.com/?q=311%20route%20de%20devant%20la%20Save%2031230%20Anan> Ouverture brasserie : sur rendez-vous De : nore...@launchpad.net de la part de Juerg Haefliger <2033...@bugs.launchpad.net> Envoyé : mercredi 30 août 2023 08:33:35 À : Brasserie La Cavalière Occitane Objet : [Bug 2033408] Re: package linux-headers-generic 6.2.0.31.29 failed to install/upgrade: problèmes de dépendances - laissé non configuré *** This bug is a duplicate of bug 2028366 *** https://bugs.launchpad.net/bugs/2028366 Unsupported DKMS modules. Please remove them: $ dkms remove anbox-ashmem/1 --all $ dkms remove anbox-binder/1 -all ** This bug has been marked a duplicate of bug 2028366 Kernel header installation fails for incompatible DKMS modules -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/2033408 Title: package linux-headers-generic 6.2.0.31.29 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in linux package in Ubuntu: Confirmed Bug description: Kernel panic after restart. Black screen frozen. Grub option's, restart ok with kernel 6.2.0-26-generic. Thanks a lot for your support. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-generic 6.2.0.31.29 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lco1232 F wireplumber /dev/snd/seq:lco1228 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Aug 29 16:09:30 2023 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2022-08-16 (378 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20GGS02600 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=4c3b7fe7-bf13-4fa9-b982-5265a2accd33 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3 RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-generic 6.2.0.31.29 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: Upgraded to lunar on 2023-05-09 (111 days ago) dmi.bios.date: 08/20/2021 dmi.bios.release: 1.92 dmi.bios.vendor: LENOVO dmi.bios.version: N1LET92W (1.92 ) dmi.board.asset.tag: Not Available dmi.board.name: 20GGS02600 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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:bvrN1LET92W(1.92):bd08/20/2021:br1.92:efr1.23:svnLENOVO:pn20GGS02600:pvrThinkPadX1Tablet:rvnLENOVO:rn20GGS02600:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20GG_BU_Think_FM_ThinkPadX1Tablet: dmi.product.family: ThinkPad X1 Tablet dmi.product.name: 20GGS02600 dmi.product.sku: LENOVO_MT_20GG_BU_Think_FM_ThinkPad X1 Tablet dmi.product.version: ThinkPad X1 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033408/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033408 Title: package linux-headers-generic 6.2.0.31.29 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in linux package in Ubuntu: Confirmed Bug description: Kernel panic after restart. Black screen frozen. Grub option's, restart ok with kernel 6.2.0-26-generic. Thanks a lot for your support. ProblemType: Package Di
[Kernel-packages] [Bug 2033408] Re: package linux-headers-generic 6.2.0.31.29 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Log Terminal in attachment ** Attachment added: "Log Terminal" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033408/+attachment/5696126/+files/term.log.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/2033408 Title: package linux-headers-generic 6.2.0.31.29 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in linux package in Ubuntu: Confirmed Bug description: Kernel panic after restart. Black screen frozen. Grub option's, restart ok with kernel 6.2.0-26-generic. Thanks a lot for your support. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-generic 6.2.0.31.29 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lco1232 F wireplumber /dev/snd/seq:lco1228 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Aug 29 16:09:30 2023 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2022-08-16 (378 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20GGS02600 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=4c3b7fe7-bf13-4fa9-b982-5265a2accd33 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3 RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-generic 6.2.0.31.29 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: Upgraded to lunar on 2023-05-09 (111 days ago) dmi.bios.date: 08/20/2021 dmi.bios.release: 1.92 dmi.bios.vendor: LENOVO dmi.bios.version: N1LET92W (1.92 ) dmi.board.asset.tag: Not Available dmi.board.name: 20GGS02600 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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:bvrN1LET92W(1.92):bd08/20/2021:br1.92:efr1.23:svnLENOVO:pn20GGS02600:pvrThinkPadX1Tablet:rvnLENOVO:rn20GGS02600:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20GG_BU_Think_FM_ThinkPadX1Tablet: dmi.product.family: ThinkPad X1 Tablet dmi.product.name: 20GGS02600 dmi.product.sku: LENOVO_MT_20GG_BU_Think_FM_ThinkPad X1 Tablet dmi.product.version: ThinkPad X1 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033409] [NEW] package linux-headers-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: le sous-processus paquet linux-headers-6.2.0-27-generic script post-installation ins
Public bug reported: linked to bug #2033408. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lco1232 F wireplumber /dev/snd/seq:lco1228 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Aug 29 16:09:21 2023 ErrorMessage: le sous-processus paquet linux-headers-6.2.0-27-generic script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2022-08-16 (378 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20GGS02600 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=4c3b7fe7-bf13-4fa9-b982-5265a2accd33 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3 RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: le sous-processus paquet linux-headers-6.2.0-27-generic script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: Upgraded to lunar on 2023-05-09 (111 days ago) dmi.bios.date: 08/20/2021 dmi.bios.release: 1.92 dmi.bios.vendor: LENOVO dmi.bios.version: N1LET92W (1.92 ) dmi.board.asset.tag: Not Available dmi.board.name: 20GGS02600 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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:bvrN1LET92W(1.92):bd08/20/2021:br1.92:efr1.23:svnLENOVO:pn20GGS02600:pvrThinkPadX1Tablet:rvnLENOVO:rn20GGS02600:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20GG_BU_Think_FM_ThinkPadX1Tablet: dmi.product.family: ThinkPad X1 Tablet dmi.product.name: 20GGS02600 dmi.product.sku: LENOVO_MT_20GG_BU_Think_FM_ThinkPad X1 Tablet dmi.product.version: ThinkPad X1 Tablet dmi.sys.vendor: LENOVO ** 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/2033409 Title: package linux-headers-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: le sous-processus paquet linux- headers-6.2.0-27-generic script post-installation installé a renvoyé un état de sortie d'erreur 1 Status in linux package in Ubuntu: New Bug description: linked to bug #2033408. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lco1232 F wireplumber /dev/snd/seq:lco1228 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Aug 29 16:09:21 2023 ErrorMessage: le sous-processus paquet linux-headers-6.2.0-27-generic script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2022-08-16 (378 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20GGS02600 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=4c3b7fe7-bf13-4fa9-b982-5265a2accd33 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3 RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: le sous-processus paquet linux-headers-6.2.0-27-generic script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: Upgraded to lunar on 2023-05-09 (111 days ago) dmi.bios.date: 08/20/2021 dmi.bios.release: 1.92 dmi.bios.vendor: LENOVO dmi.bios.version: N1LET92W (1.92 ) dmi.board.asset.tag: Not Available dmi.board.name: 20GGS02600 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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:bvrN1LET92W(1.92):bd08/20/2021:br1.92:efr1.23:svnLENOVO:pn20GGS02600:pvrThinkPadX1Tablet:rvnLENOVO:rn20GGS02600:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20GG_BU_Think_FM_ThinkPadX1Tablet:
[Kernel-packages] [Bug 2033408] Re: package linux-headers-generic 6.2.0.31.29 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Hi, Same problem with Kernel 6.2.0-27-generic. Best regards. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033408 Title: package linux-headers-generic 6.2.0.31.29 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in linux package in Ubuntu: Confirmed Bug description: Kernel panic after restart. Black screen frozen. Grub option's, restart ok with kernel 6.2.0-26-generic. Thanks a lot for your support. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-generic 6.2.0.31.29 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lco1232 F wireplumber /dev/snd/seq:lco1228 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Aug 29 16:09:30 2023 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2022-08-16 (378 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20GGS02600 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=4c3b7fe7-bf13-4fa9-b982-5265a2accd33 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3 RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-generic 6.2.0.31.29 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: Upgraded to lunar on 2023-05-09 (111 days ago) dmi.bios.date: 08/20/2021 dmi.bios.release: 1.92 dmi.bios.vendor: LENOVO dmi.bios.version: N1LET92W (1.92 ) dmi.board.asset.tag: Not Available dmi.board.name: 20GGS02600 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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:bvrN1LET92W(1.92):bd08/20/2021:br1.92:efr1.23:svnLENOVO:pn20GGS02600:pvrThinkPadX1Tablet:rvnLENOVO:rn20GGS02600:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20GG_BU_Think_FM_ThinkPadX1Tablet: dmi.product.family: ThinkPad X1 Tablet dmi.product.name: 20GGS02600 dmi.product.sku: LENOVO_MT_20GG_BU_Think_FM_ThinkPad X1 Tablet dmi.product.version: ThinkPad X1 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033408] [NEW] package linux-headers-generic 6.2.0.31.29 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Public bug reported: Kernel panic after restart. Black screen frozen. Grub option's, restart ok with kernel 6.2.0-26-generic. Thanks a lot for your support. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-generic 6.2.0.31.29 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lco1232 F wireplumber /dev/snd/seq:lco1228 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Aug 29 16:09:30 2023 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2022-08-16 (378 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20GGS02600 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=4c3b7fe7-bf13-4fa9-b982-5265a2accd33 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3 RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-generic 6.2.0.31.29 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: Upgraded to lunar on 2023-05-09 (111 days ago) dmi.bios.date: 08/20/2021 dmi.bios.release: 1.92 dmi.bios.vendor: LENOVO dmi.bios.version: N1LET92W (1.92 ) dmi.board.asset.tag: Not Available dmi.board.name: 20GGS02600 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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:bvrN1LET92W(1.92):bd08/20/2021:br1.92:efr1.23:svnLENOVO:pn20GGS02600:pvrThinkPadX1Tablet:rvnLENOVO:rn20GGS02600:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20GG_BU_Think_FM_ThinkPadX1Tablet: dmi.product.family: ThinkPad X1 Tablet dmi.product.name: 20GGS02600 dmi.product.sku: LENOVO_MT_20GG_BU_Think_FM_ThinkPad X1 Tablet dmi.product.version: ThinkPad X1 Tablet dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/2033408 Title: package linux-headers-generic 6.2.0.31.29 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in linux package in Ubuntu: Confirmed Bug description: Kernel panic after restart. Black screen frozen. Grub option's, restart ok with kernel 6.2.0-26-generic. Thanks a lot for your support. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-generic 6.2.0.31.29 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lco1232 F wireplumber /dev/snd/seq:lco1228 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Aug 29 16:09:30 2023 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2022-08-16 (378 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20GGS02600 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=4c3b7fe7-bf13-4fa9-b982-5265a2accd33 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3 RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-generic 6.2.0.31.29 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: Upgraded to lunar on 2023-05-09 (111 days ago) dmi.bios.date: 08/20/2021 dmi.bios.release: 1.92 dmi.bios.vendor: LENOVO dmi.bios.version: N1LET92W (1.92 ) dmi.board.asset.tag: Not Available dmi.board.name: 20GGS02600 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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:bvrN1LET92W(1.92):bd08/20/2021:br1.92:efr1.23:svnLENOVO:pn20GGS02600:pvrThinkPadX1Tablet:rvnLENOVO:rn20GGS02600:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20GG_BU_Think_FM_ThinkPadX1Tablet: dmi.product.family: ThinkPad X1 Tablet dmi.product.name: 20GGS02600 dmi.product.sku: LENOVO_MT_20GG_BU_Think_FM_ThinkPad X1 Tablet dmi.product.version: ThinkPad X1 Tablet dmi.sys.vendor: LENOVO To manage
[Kernel-packages] [Bug 2024187] Re: xfrm: packets sent trough a raw socket don't match ipsec policies with proto selector
Any news?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2024187
Title:
xfrm: packets sent trough a raw socket don't match ipsec policies with
proto selector
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
When a userland application sends packets through an IPv4 or IPv6 raw
socket, these packets don't match ipsec policies that are configured
with a protocol selector.
The problem has been fixed in linux v6.4 with commit 3632679d9e4f
("ipv{4,6}/raw: fix output xfrm lookup wrt protocol").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3632679d9e4f
This commit has been backported in linux 5.15.115:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=395d846c61c5
[Test Case]
Configure an ipsec policy with a protocol selector and send ip packets
that match this policy through an IP raw socket.
Example to match the proto icmp:
ip xfrm policy add src 10.100.0.0/24 dst 10.200.0.0/24 proto icmp dir out
tmpl src 10.125.0.1 dst 10.125.0.2 proto esp mode tunnel reqid 1
[Regression Potential]
The patch introduces a new API to fix this problem, thus the
regression potential is low for existing applications.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024187/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008583] Re: VMware nested under KVM stopped working on 5.19 kernel on Ryzen: Invalid VMCB.
Sorry for the noob question but how do I compile the custom kernel? What is the fix please? Any help would be greatly appreciated. Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008583 Title: VMware nested under KVM stopped working on 5.19 kernel on Ryzen: Invalid VMCB. Status in linux package in Ubuntu: Confirmed Bug description: My setup: Host: Ubuntu Linux 22.04.1, kernel 5.15, Ryzen 5900x Hypervisor: KVM Windows VM with VMware Workstation 16 Running nested VMs in VMware works ok. It fails if Linux host kernel is updated to 5.19 (22.04.2) with MONITOR PANIC: Invalid VMCB. VMware Workstation unrecoverable error: (vcpu-0) vcpu-0:Invalid VMCB. If I update to Workstation 17 it fails with 2023-02-24T15:21:35.112Z In(05) vmx The following features are required for SVM support in VMware Workstation; however, these features are not available on this host: 2023-02-24T15:21:35.112Z In(05) vmxFlush by ASID. This host supports AMD-V, but the AMD-V implementation is incompatible with VMware Workstation. VMware Workstation does not support the user level monitor on this host. Module 'MonitorMode' power on failed. The same VM works ok on 5.19 kernel on my Intel PC. So it has to do with updated Linux kernel and AMD virtualization and VMware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008583] Re: VMware nested under KVM stopped working on 5.19 kernel on Ryzen: Invalid VMCB.
Hi, I’ve got the exact same problem on an AMD Epyc 7763. Can do a nested ESXi 7.0+ (and start VMs on top of it) with kernel 5.15. No longer works with kernel 6.2 (haven’t tried with 5.19). Can’t even virtualize ESXi 8.0: this host supports AMD-V, but the AMD-V implementation is incompatible I was also able to reproduce the issue with Debian 11 and 12. Any help would be greatly appreciated, thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008583 Title: VMware nested under KVM stopped working on 5.19 kernel on Ryzen: Invalid VMCB. Status in linux package in Ubuntu: Confirmed Bug description: My setup: Host: Ubuntu Linux 22.04.1, kernel 5.15, Ryzen 5900x Hypervisor: KVM Windows VM with VMware Workstation 16 Running nested VMs in VMware works ok. It fails if Linux host kernel is updated to 5.19 (22.04.2) with MONITOR PANIC: Invalid VMCB. VMware Workstation unrecoverable error: (vcpu-0) vcpu-0:Invalid VMCB. If I update to Workstation 17 it fails with 2023-02-24T15:21:35.112Z In(05) vmx The following features are required for SVM support in VMware Workstation; however, these features are not available on this host: 2023-02-24T15:21:35.112Z In(05) vmxFlush by ASID. This host supports AMD-V, but the AMD-V implementation is incompatible with VMware Workstation. VMware Workstation does not support the user level monitor on this host. Module 'MonitorMode' power on failed. The same VM works ok on 5.19 kernel on my Intel PC. So it has to do with updated Linux kernel and AMD virtualization and VMware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016269] Re: conntrack mark is not advertised via netlink
Tests with linux-image-unsigned-5.15.0-1033-intel-iotg are ok.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2016269
Title:
conntrack mark is not advertised via netlink
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Bug description:
SRU justification sent to ML:
[Impact]
There was a commit 95fcb42e5f20
("netfilter: ctnetlink: fix compilation warning after data race fixes in ct
mark")
that introduces a regression where the "mark" variable is no longer
dumped in netlink netfilter conntrack messages, which userspace tools use
to mark and track connections.
[Fix]
Introduce the upstream fix 9f7dd42f0db1
("netfilter: ctnetlink: revert to dumping mark regardless of event type")
that always dumps the 'mark' variable for conntrack entries.
This fix has also landed in 5.15 upstream stable.
[Test]
Run 'conntrack -E' and check the output of connection entries.
The 'mark' variable should now be present in connection entries after
the fix.
before fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
after fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] mark=0 use=1
[Where problems could occur]
The fixes are pretty straight forward so regression potential should be
minimal.
[Impact]
The last merge of the v5.15 stable (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
introduced a bug on netlink netfilter conntrack messages.
The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix
compilation warning after data race fixes in ct mark"):
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20
This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter:
ctnetlink: revert to dumping mark regardless of event type"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1
which has been backported in v5.15.103:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c
[Test Case]
Run 'conntrack -E' and check the output.
Before the problematic commit:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED]
mark=0 use=1
'mark=' is seen on connrtack event
after:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
=> 'mark=' is not seen.
[Regression Potential]
The patch is quite simple. It has been backported in the official 5.15
stable. The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016269/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024187] [NEW] xfrm: packets sent trough a raw socket don't match ipsec policies with proto selector
Public bug reported:
[Impact]
When a userland application sends packets through an IPv4 or IPv6 raw
socket, these packets don't match ipsec policies that are configured
with a protocol selector.
The problem has been fixed in linux v6.4 with commit 3632679d9e4f
("ipv{4,6}/raw: fix output xfrm lookup wrt protocol").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3632679d9e4f
This commit has been backported in linux 5.15.115:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=395d846c61c5
[Test Case]
Configure an ipsec policy with a protocol selector and send ip packets
that match this policy through an IP raw socket.
Example to match the proto icmp:
ip xfrm policy add src 10.100.0.0/24 dst 10.200.0.0/24 proto icmp dir out tmpl
src 10.125.0.1 dst 10.125.0.2 proto esp mode tunnel reqid 1
[Regression Potential]
The patch introduces a new API to fix this problem, thus the regression
potential is low for existing applications.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2024187
Title:
xfrm: packets sent trough a raw socket don't match ipsec policies with
proto selector
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
When a userland application sends packets through an IPv4 or IPv6 raw
socket, these packets don't match ipsec policies that are configured
with a protocol selector.
The problem has been fixed in linux v6.4 with commit 3632679d9e4f
("ipv{4,6}/raw: fix output xfrm lookup wrt protocol").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3632679d9e4f
This commit has been backported in linux 5.15.115:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=395d846c61c5
[Test Case]
Configure an ipsec policy with a protocol selector and send ip packets
that match this policy through an IP raw socket.
Example to match the proto icmp:
ip xfrm policy add src 10.100.0.0/24 dst 10.200.0.0/24 proto icmp dir out
tmpl src 10.125.0.1 dst 10.125.0.2 proto esp mode tunnel reqid 1
[Regression Potential]
The patch introduces a new API to fix this problem, thus the
regression potential is low for existing applications.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024187/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016269] Re: conntrack mark is not advertised via netlink
Test with linux-nvidia-5.19/5.19.0-1014.14 are ok.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2016269
Title:
conntrack mark is not advertised via netlink
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Bug description:
SRU justification sent to ML:
[Impact]
There was a commit 95fcb42e5f20
("netfilter: ctnetlink: fix compilation warning after data race fixes in ct
mark")
that introduces a regression where the "mark" variable is no longer
dumped in netlink netfilter conntrack messages, which userspace tools use
to mark and track connections.
[Fix]
Introduce the upstream fix 9f7dd42f0db1
("netfilter: ctnetlink: revert to dumping mark regardless of event type")
that always dumps the 'mark' variable for conntrack entries.
This fix has also landed in 5.15 upstream stable.
[Test]
Run 'conntrack -E' and check the output of connection entries.
The 'mark' variable should now be present in connection entries after
the fix.
before fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
after fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] mark=0 use=1
[Where problems could occur]
The fixes are pretty straight forward so regression potential should be
minimal.
[Impact]
The last merge of the v5.15 stable (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
introduced a bug on netlink netfilter conntrack messages.
The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix
compilation warning after data race fixes in ct mark"):
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20
This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter:
ctnetlink: revert to dumping mark regardless of event type"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1
which has been backported in v5.15.103:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c
[Test Case]
Run 'conntrack -E' and check the output.
Before the problematic commit:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED]
mark=0 use=1
'mark=' is seen on connrtack event
after:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
=> 'mark=' is not seen.
[Regression Potential]
The patch is quite simple. It has been backported in the official 5.15
stable. The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016269/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019543] Re: crypto / qat: unable to init GEN4 device
In fact, those patches are not enough, a lot more are needed:
- ba79a32acfde ("crypto: qat - replace deprecated MSI API")
- 0e64dcd7c94b ("crypto: qat - remove unmatched CPU affinity to cluster IRQ")
- 9832fdc917de ("crypto: qat - free irqs only if allocated")
- 70fead3adb4e ("crypto: qat - free irq in case of failure")
- 40da865381ad ("crypto: qat - remove unneeded packed attribute")
- ca605f97dae4 ("crypto: qat - power up 4xxx device")
- 9b768e8a3909 ("crypto: qat - detect PFVF collision after ACK")
- 18fcba469ba5 ("crypto: qat - disregard spurious PFVF interrupts")
- e17f49bb244a ("crypto: qat - remove unnecessary collision prevention step in
PFVF")
- 993161d36ab5 ("crypto: qat - fix handling of VF to PF interrupts")
- b79c7532dc33 ("crypto: qat - remove duplicated logic across GEN2 drivers")
- c3878a786be0 ("crypto: qat - use hweight for bit counting")
- 6e680f94bc31 ("crypto: qat - make pfvf send message direction agnostic")
- 21db65edb6a5 ("crypto: qat - move pfvf collision detection values")
- 71b5f2ab5e52 ("crypto: qat - rename pfvf collision constants")
- 7a73c4622aaa ("crypto: qat - add VF and PF wrappers to common send function")
- aa3c68634df8 ("crypto: qat - extract send and wait from
adf_vf2pf_request_version()")
- 32dfef6f92dd ("crypto: qat - share adf_enable_pf2vf_comms() from
adf_pf2vf_msg.c")
- 8f5c335e34b5 ("crypto: qat - simplify adf_enable_aer()")
- c79391c696da ("crypto: qat - do not handle PFVF sources for qat_4xxx")
- 5002200b4fed ("crypto: qat - fix undetected PFVF timeout in ACK loop")
- 95b4d40ed256 ("crypto: qat - refactor PF top half for PFVF")
- 08ea97f48883 ("crypto: qat - move vf2pf interrupt helpers")
- b7c13ee46ceb ("crypto: qat - move VF message handler to adf_vf2pf_msg.c")
- 720aa72a77f4 ("crypto: qat - move interrupt code out of the PFVF handler")
- 956125e21f46 ("crypto: qat - change PFVF ACK behaviour")
- 04cf47872c7e ("crypto: qat - re-enable interrupts for legacy PFVF messages")
- bd59b769ddac ("crypto: qat - split PFVF message decoding from handling")
- 1d6133123fb2 ("crypto: qat - handle retries due to collisions in
adf_iov_putmsg()")
- b85bd9457dc3 ("crypto: qat - relocate PFVF PF related logic")
- 7e00fb3f162c ("crypto: qat - relocate PFVF VF related logic")
- 6f2e28015bac ("crypto: qat - relocate PFVF disabled function")
- bc63dabe5254 ("crypto: qat - add pfvf_ops")
- 9baf2de7ee4e ("crypto: qat - differentiate between pf2vf and vf2pf offset")
- 49c43538ce05 ("crypto: qat - abstract PFVF send function")
- 1ea7c2beca5b ("crypto: qat - abstract PFVF receive logic")
- 09ce899a592f ("crypto: qat - reorganize PFVF code")
- f6aff914989e ("crypto: qat - reorganize PFVF protocol definitions")
- 1d4fde6c4e80 ("crypto: qat - use enums for PFVF protocol codes")
- 25110fd2e346 ("crypto: qat - pass the PF2VF responses back to the callers")
- c35c76c6919e ("crypto: qat - refactor pfvf version request messages")
- e669b4dedd89 ("crypto: qat - do not rely on min version")
- 1d9a915fafab ("crypto: qat - fix VF IDs in PFVF log messages")
- 8616b628ef69 ("crypto: qat - improve logging of PFVF messages")
- e0441e2be155 ("crypto: qat - get compression extended capabilities")
- 547bde7bd4ec ("crypto: qat - set CIPHER capability for QAT GEN2")
- cfe4894eccdc ("crypto: qat - set COMPRESSION capability for QAT GEN2")
- 4b44d28c715d ("crypto: qat - extend crypto capability detection for 4xxx")
- 03125541ca29 ("crypto: qat - support the reset of ring pairs on PF")
- 448588adcdf4 ("crypto: qat - add the adf_get_pmisc_base() helper function")
- 6ed942ed3c47 ("crypto: qat - make PFVF message construction direction
agnostic")
- 028042856802 ("crypto: qat - make PFVF send and receive direction agnostic")
- 0aeda694f187 ("crypto: qat - set PFVF_MSGORIGIN just before sending")
- db1c034801c4 ("crypto: qat - abstract PFVF messages with struct
pfvf_message")
- 952f4e812741 ("crypto: qat - leverage bitfield.h utils for PFVF messages")
- 1c94d8035905 ("crypto: qat - leverage read_poll_timeout in PFVF send")
- 6f87979129d1 ("crypto: qat - improve the ACK timings in PFVF send")
- 4d03135faa05 ("crypto: qat - store the PFVF protocol version of the
endpoints")
- 3a5b2a088328 ("crypto: qat - store the ring-to-service mapping")
- 673184a2a58f ("crypto: qat - introduce support for PFVF block messages")
- 851ed498dba1 ("crypto: qat - exchange device capabilities over PFVF")
- 73ef8f3382d1 ("crypto: qat - support fast ACKs in the PFVF protocol")
- e1b176af3d7e ("crypto: qat - exchange ring-to-service mappings over PFVF")
- 925b3069cf6e ("crypto: qat - config VFs based on ring-to-svc mapping")
- a9dc0d966605 ("crypto: qat - add PFVF support to the GEN4 host driver")
- 0bba03ce9739 ("crypto: qat - add PFVF support to enable the reset of ring
pairs")
- beb1e6d71f0e ("crypto: qat - allow detection of dc capabilities for 4xxx")
- 0cec19c761e5 ("crypto: qat - add support for compression for 4xxx")
- 4cab5dfd15b7 ("crypto: qat - fix
[Kernel-packages] [Bug 2016269] Re: conntrack mark is not advertised via netlink
Tests are ok.
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2016269
Title:
conntrack mark is not advertised via netlink
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Bug description:
SRU justification sent to ML:
[Impact]
There was a commit 95fcb42e5f20
("netfilter: ctnetlink: fix compilation warning after data race fixes in ct
mark")
that introduces a regression where the "mark" variable is no longer
dumped in netlink netfilter conntrack messages, which userspace tools use
to mark and track connections.
[Fix]
Introduce the upstream fix 9f7dd42f0db1
("netfilter: ctnetlink: revert to dumping mark regardless of event type")
that always dumps the 'mark' variable for conntrack entries.
This fix has also landed in 5.15 upstream stable.
[Test]
Run 'conntrack -E' and check the output of connection entries.
The 'mark' variable should now be present in connection entries after
the fix.
before fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
after fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] mark=0 use=1
[Where problems could occur]
The fixes are pretty straight forward so regression potential should be
minimal.
[Impact]
The last merge of the v5.15 stable (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
introduced a bug on netlink netfilter conntrack messages.
The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix
compilation warning after data race fixes in ct mark"):
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20
This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter:
ctnetlink: revert to dumping mark regardless of event type"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1
which has been backported in v5.15.103:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c
[Test Case]
Run 'conntrack -E' and check the output.
Before the problematic commit:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED]
mark=0 use=1
'mark=' is seen on connrtack event
after:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
=> 'mark=' is not seen.
[Regression Potential]
The patch is quite simple. It has been backported in the official 5.15
stable. The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016269/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016269] Re: conntrack mark is not advertised via netlink
Tests are ok.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2016269
Title:
conntrack mark is not advertised via netlink
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Bug description:
SRU justification sent to ML:
[Impact]
There was a commit 95fcb42e5f20
("netfilter: ctnetlink: fix compilation warning after data race fixes in ct
mark")
that introduces a regression where the "mark" variable is no longer
dumped in netlink netfilter conntrack messages, which userspace tools use
to mark and track connections.
[Fix]
Introduce the upstream fix 9f7dd42f0db1
("netfilter: ctnetlink: revert to dumping mark regardless of event type")
that always dumps the 'mark' variable for conntrack entries.
This fix has also landed in 5.15 upstream stable.
[Test]
Run 'conntrack -E' and check the output of connection entries.
The 'mark' variable should now be present in connection entries after
the fix.
before fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
after fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] mark=0 use=1
[Where problems could occur]
The fixes are pretty straight forward so regression potential should be
minimal.
[Impact]
The last merge of the v5.15 stable (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
introduced a bug on netlink netfilter conntrack messages.
The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix
compilation warning after data race fixes in ct mark"):
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20
This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter:
ctnetlink: revert to dumping mark regardless of event type"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1
which has been backported in v5.15.103:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c
[Test Case]
Run 'conntrack -E' and check the output.
Before the problematic commit:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED]
mark=0 use=1
'mark=' is seen on connrtack event
after:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
=> 'mark=' is not seen.
[Regression Potential]
The patch is quite simple. It has been backported in the official 5.15
stable. The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016269/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019543] [NEW] crypto / qat: unable to init GEN4 device
Public bug reported:
[Target]
Jammy kernel.
[Impact]
The PCI device cannot be initialized.
This has been fixed in linux v5.18 with the below commits:
- a9dc0d966605 ("crypto: qat - add PFVF support to the GEN4 host driver")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a9dc0d966605
- 642a7d49c249 ("crypto: qat - fix access to PFVF interrupt registers for
GEN4")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=642a7d49c249
[Test Case]
Boot a machine with this device.
Before the patches, the following errors are logged:
> EAL: Probe PCI driver: qat (8086:4941) device: :00:08.0 (socket -1)
> qat_pf2vf_exch_msg(): ACK not received from remote
[Regression Potential]
The patches enable new code for this kind of device only.
It is living in linux for more than 1 years.
The potential regressions are low.
** 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/2019543
Title:
crypto / qat: unable to init GEN4 device
Status in linux package in Ubuntu:
New
Bug description:
[Target]
Jammy kernel.
[Impact]
The PCI device cannot be initialized.
This has been fixed in linux v5.18 with the below commits:
- a9dc0d966605 ("crypto: qat - add PFVF support to the GEN4 host driver")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a9dc0d966605
- 642a7d49c249 ("crypto: qat - fix access to PFVF interrupt registers for
GEN4")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=642a7d49c249
[Test Case]
Boot a machine with this device.
Before the patches, the following errors are logged:
> EAL: Probe PCI driver: qat (8086:4941) device: :00:08.0 (socket -1)
> qat_pf2vf_exch_msg(): ACK not received from remote
[Regression Potential]
The patches enable new code for this kind of device only.
It is living in linux for more than 1 years.
The potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019543/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016269] Re: conntrack mark is not advertised via netlink
** Description changed:
[Impact]
- after the last merge of the v5.15 stable (see
+ The last merge of the v5.15 stable (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
introduced a bug on netlink netfilter conntrack messages.
The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix
compilation warning after data race fixes in ct mark"):
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20
This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter:
ctnetlink: revert to dumping mark regardless of event type"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1
which has been backported in v5.15.103:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c
[Test Case]
Run 'conntrack -E' and check the output.
Before the problematic commit:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED]
mark=0 use=1
'mark=' is seen on connrtack event
after:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
=> 'mark=' is not seen.
[Regression Potential]
The patch is quite simple. It has been backported in the official 5.15
stable. The risk of regression should be contained.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2016269
Title:
conntrack mark is not advertised via netlink
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
The last merge of the v5.15 stable (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
introduced a bug on netlink netfilter conntrack messages.
The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix
compilation warning after data race fixes in ct mark"):
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20
This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter:
ctnetlink: revert to dumping mark regardless of event type"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1
which has been backported in v5.15.103:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c
[Test Case]
Run 'conntrack -E' and check the output.
Before the problematic commit:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED]
mark=0 use=1
'mark=' is seen on connrtack event
after:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
=> 'mark=' is not seen.
[Regression Potential]
The patch is quite simple. It has been backported in the official 5.15
stable. The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016269/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016269] [NEW] conntrack mark is not advertised via netlink
Public bug reported:
[Impact]
The last merge of the v5.15 stable (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
introduced a bug on netlink netfilter conntrack messages.
The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix compilation
warning after data race fixes in ct mark"):
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20
This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter: ctnetlink:
revert to dumping mark regardless of event type"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1
which has been backported in v5.15.103:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c
[Test Case]
Run 'conntrack -E' and check the output.
Before the problematic commit:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
> src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] mark=0 use=1
'mark=' is seen on connrtack event
after:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
> src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
=> 'mark=' is not seen.
[Regression Potential]
The patch is quite simple. It has been backported in the official 5.15
stable. The risk of regression should be contained.
** 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/2016269
Title:
conntrack mark is not advertised via netlink
Status in linux package in Ubuntu:
New
Bug description:
[Impact]
The last merge of the v5.15 stable (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
introduced a bug on netlink netfilter conntrack messages.
The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix
compilation warning after data race fixes in ct mark"):
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20
This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter:
ctnetlink: revert to dumping mark regardless of event type"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1
which has been backported in v5.15.103:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c
[Test Case]
Run 'conntrack -E' and check the output.
Before the problematic commit:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED]
mark=0 use=1
'mark=' is seen on connrtack event
after:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
=> 'mark=' is not seen.
[Regression Potential]
The patch is quite simple. It has been backported in the official 5.15
stable. The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016269/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007173] Re: i915: loss of the screen connected in DP to my dockstation
** 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/2007173 Title: i915: loss of the screen connected in DP to my dockstation Status in linux package in Ubuntu: Confirmed Bug description: Since a few versions of the kernel I'm losing the screen connected to my dockstation thinkpad using displayport. My running laptop is a thinkpad T14s I'm currently running "Linux laptop 5.19.0-28-generic #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 15 12:05:40 UTC 2 x86_64 x86_64 x86_64 GNU/Linux" but I had the same issue while running "linux-image-5.15.0-60-generic" and I think with "linux-image-5.15.0-58-generic" too. When losing the screen, I'm getting "i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful" from the kernel. During the last screen loss, I tried to connect the DisplayPort to another screen to eliminate the possibility that it could be a issue with it. Not only did the other screen not work either, but I got the following stacktrace: 17957.541801] CPU: 3 PID: 30705 Comm: kworker/3:1 Tainted: G U 5.19.0-28-generic #29~22.04.1-Ubuntu [17957.541811] Hardware name: LENOVO 20T1S62300/20T1S62300, BIOS N2YET34W (1.23 ) 12/31/2021 [17957.541816] Workqueue: events i915_hotplug_work_func [i915] [17957.542099] RIP: 0010:intel_dp_prep_link_retrain+0x1b0/0x1d0 [i915] [17957.542378] Code: d2 74 32 48 89 55 a8 4c 89 4d b0 e8 1a 86 f3 f5 48 8b 55 a8 48 c7 c1 50 7c b0 c0 48 c7 c7 e6 00 ae c0 48 89 c6 e8 87 5a 41 f6 <0f> 0b 4c 8b 4d b0 e9 36 ff ff ff 48 8b 17 eb c9 e8 ab bc 4d f6 e9 [17957.542385] RSP: 0018:b27bc6677cb0 EFLAGS: 00010246 [17957.542393] RAX: RBX: 9d6da9ef26c0 RCX: [17957.542398] RDX: RSI: RDI: [17957.542401] RBP: b27bc6677d08 R08: R09: [17957.542405] R10: R11: R12: 9d6c99894170 [17957.542409] R13: b27bc6677d27 R14: b27bc6677d70 R15: 9d6ca032c800 [17957.542414] FS: () GS:9d73ad6c() knlGS: [17957.542420] CS: 0010 DS: ES: CR0: 80050033 [17957.542425] CR2: 170804379000 CR3: 000792010005 CR4: 003706e0 [17957.542431] DR0: DR1: DR2: [17957.542434] DR3: DR6: fffe0ff0 DR7: 0400 [17957.542439] Call Trace: [17957.542443] [17957.542453] intel_dp_retrain_link+0xee/0x2f0 [i915] [17957.542773] intel_ddi_hotplug+0xc6/0x1f0 [i915] [17957.543049] i915_hotplug_work_func+0x1f3/0x320 [i915] [17957.543316] process_one_work+0x222/0x400 [17957.543327] worker_thread+0x50/0x3e0 [17957.543334] ? rescuer_thread+0x3c0/0x3c0 [17957.543340] kthread+0xe6/0x110 [17957.543349] ? kthread_complete_and_exit+0x20/0x20 [17957.543359] ret_from_fork+0x1f/0x30 [17957.543374] [17957.543377] ---[ end trace ]--- [17985.975481] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [17991.187501] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful Distrib is : "lsb_release -rd Description: Linux Mint 21 Release: 21" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007173] [NEW] i915: loss of the screen connected in DP to my dockstation
Public bug reported: Since a few versions of the kernel I'm losing the screen connected to my dockstation thinkpad using displayport. My running laptop is a thinkpad T14s I'm currently running "Linux laptop 5.19.0-28-generic #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 15 12:05:40 UTC 2 x86_64 x86_64 x86_64 GNU/Linux" but I had the same issue while running "linux-image-5.15.0-60-generic" and I think with "linux-image-5.15.0-58-generic" too. When losing the screen, I'm getting "i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful" from the kernel. During the last screen loss, I tried to connect the DisplayPort to another screen to eliminate the possibility that it could be a issue with it. Not only did the other screen not work either, but I got the following stacktrace: 17957.541801] CPU: 3 PID: 30705 Comm: kworker/3:1 Tainted: G U 5.19.0-28-generic #29~22.04.1-Ubuntu [17957.541811] Hardware name: LENOVO 20T1S62300/20T1S62300, BIOS N2YET34W (1.23 ) 12/31/2021 [17957.541816] Workqueue: events i915_hotplug_work_func [i915] [17957.542099] RIP: 0010:intel_dp_prep_link_retrain+0x1b0/0x1d0 [i915] [17957.542378] Code: d2 74 32 48 89 55 a8 4c 89 4d b0 e8 1a 86 f3 f5 48 8b 55 a8 48 c7 c1 50 7c b0 c0 48 c7 c7 e6 00 ae c0 48 89 c6 e8 87 5a 41 f6 <0f> 0b 4c 8b 4d b0 e9 36 ff ff ff 48 8b 17 eb c9 e8 ab bc 4d f6 e9 [17957.542385] RSP: 0018:b27bc6677cb0 EFLAGS: 00010246 [17957.542393] RAX: RBX: 9d6da9ef26c0 RCX: [17957.542398] RDX: RSI: RDI: [17957.542401] RBP: b27bc6677d08 R08: R09: [17957.542405] R10: R11: R12: 9d6c99894170 [17957.542409] R13: b27bc6677d27 R14: b27bc6677d70 R15: 9d6ca032c800 [17957.542414] FS: () GS:9d73ad6c() knlGS: [17957.542420] CS: 0010 DS: ES: CR0: 80050033 [17957.542425] CR2: 170804379000 CR3: 000792010005 CR4: 003706e0 [17957.542431] DR0: DR1: DR2: [17957.542434] DR3: DR6: fffe0ff0 DR7: 0400 [17957.542439] Call Trace: [17957.542443] [17957.542453] intel_dp_retrain_link+0xee/0x2f0 [i915] [17957.542773] intel_ddi_hotplug+0xc6/0x1f0 [i915] [17957.543049] i915_hotplug_work_func+0x1f3/0x320 [i915] [17957.543316] process_one_work+0x222/0x400 [17957.543327] worker_thread+0x50/0x3e0 [17957.543334] ? rescuer_thread+0x3c0/0x3c0 [17957.543340] kthread+0xe6/0x110 [17957.543349] ? kthread_complete_and_exit+0x20/0x20 [17957.543359] ret_from_fork+0x1f/0x30 [17957.543374] [17957.543377] ---[ end trace ]--- [17985.975481] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [17991.187501] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful Distrib is : "lsb_release -rd Description:Linux Mint 21 Release:21" ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007173 Title: i915: loss of the screen connected in DP to my dockstation Status in linux package in Ubuntu: Incomplete Bug description: Since a few versions of the kernel I'm losing the screen connected to my dockstation thinkpad using displayport. My running laptop is a thinkpad T14s I'm currently running "Linux laptop 5.19.0-28-generic #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 15 12:05:40 UTC 2 x86_64 x86_64 x86_64 GNU/Linux" but I had the same issue while running "linux-image-5.15.0-60-generic" and I think with "linux-image-5.15.0-58-generic" too. When losing the screen, I'm getting "i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful" from the kernel. During the last screen loss, I tried to connect the DisplayPort to another screen to eliminate the possibility that it could be a issue with it. Not only did the other screen not work either, but I got the following stacktrace: 17957.541801] CPU: 3 PID: 30705 Comm: kworker/3:1 Tainted: G U 5.19.0-28-generic #29~22.04.1-Ubuntu [17957.541811] Hardware name: LENOVO 20T1S62300/20T1S62300, BIOS N2YET34W (1.23 ) 12/31/2021 [17957.541816] Workqueue: events i915_hotplug_work_func [i915] [17957.542099] RIP: 0010:intel_dp_prep_link_retrain+0x1b0/0x1d0 [i915] [17957.542378] Code: d2 74 32 48 89 55 a8 4c 89 4d b0 e8 1a 86 f3 f5 48 8b 55 a8 48 c7 c1 50 7c b0 c0 48 c7 c7 e6 00 ae c0 48 89 c6 e8 87 5a 41 f6 <0f> 0b 4c 8b 4d b0 e9 36 ff ff ff 48 8b 17 eb c9 e8 ab bc 4d f6 e9 [17957.542385] RSP: 0018:b27bc6677cb0 EFLAGS: 00010246 [17957.542393] RAX: RBX: 9d6da9ef26c0 RCX: [17957.542398] RDX: RSI: RDI:
[Kernel-packages] [Bug 1988809] Re: ip/nexthop: fix default address selection for connected nexthop
I cannot test this kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988809
Title:
ip/nexthop: fix default address selection for connected nexthop
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
Packets sent by userland apps are rejected/dropped if the source
address is not specified and the corresponding route is using a
connected nexthop object.
This bug exists since linux v5.3 and has been fixed in v5.19 by the following
upstream commits:
- 747c14307214 ("ip: fix dflt addr selection for connected nexthop")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214
- cd72e61bad14 ("selftests/net: test nexthop without gw")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14
- eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd
The last commit (v6.0) fixes a regression introduced by the first
commit.
[Test Case]
A detailed test case is explained in the first commit and a self-test
is added in the second commit.
[Regression Potential]
The patch modifies some internal routing states. It has been living in the
upstream trees for 2 months and the reported regression about icmp redirects
has been fixed.
The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988809/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988584] Re: cgroup: all controllers mounted when using 'cgroup_no_v1='
** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988584 Title: cgroup: all controllers mounted when using 'cgroup_no_v1=' Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: [Impact] When mounting a cgroup hierarchy with disabled controller in cgroup v1, all available controllers will be attached. For example, boot with cgroup_no_v1=cpu or cgroup_disable=cpu, and then mount with "mount -t cgroup -ocpu cpu /sys/fs/cgroup/cpu", then all enabled controllers will be attached except cpu. This exists since linux v5.1 and fixed in linux v5.11 with this commit: 61e960b07b63 cgroup-v1: add disabled controller check in cgroup1_parse_param() https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=61e960b07b637 [Test Case] root@dut-vm:~# kexec -l /boot/vmlinuz-5.4.0-122-generic --initrd=/boot/initrd.img-5.4.0-122-generic --command-line="$(cat /proc/cmdline) cgroup_no_v1=net_prio,net_cls" root@dut-vm:~# systemctl kexec root@dut-vm:~# mount | grep cgroup tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,cpu,cpuacct,blkio,memory,devices,freezer,perf_event,hugetlb,pids,rdma) => All controllers are associated to /sys/fs/cgroup/net_cls,net_prio. Note that several reboots may be needed to reproduce the problem (it fails only when systemd tries to mount 'net_cls,net_prio' first, but the order is random). [Regression Potential] The patch is located in cgroup1_parse_param(), the potential regressions are low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988809] Re: ip/nexthop: fix default address selection for connected nexthop
Before the update:
++
root@ubuntu2004:~/linux# uname -a
Linux ubuntu2004 5.4.0-124-generic #140-Ubuntu SMP Thu Aug 4 02:23:37 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu2004:~/linux# tools/testing/selftests/net/fib_nexthop_nongw.sh
TEST: nexthop: get route with nexthop without gw[FAIL]
TEST: nexthop: ping through nexthop without gw [FAIL]
With the new focal kernel:
++
root@ubuntu2004:~/linux# uname -a
Linux ubuntu2004 5.4.0-128-generic #144-Ubuntu SMP Tue Sep 20 11:00:04 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu2004:~/linux# tools/testing/selftests/net/fib_nexthop_nongw.sh
TEST: nexthop: get route with nexthop without gw[ OK ]
TEST: nexthop: ping through nexthop without gw [ OK ]
With the new jammy kernel:
++
root@ubuntu2004:~/linux# uname -a
Linux ubuntu2004 5.15.0-50-generic #56-Ubuntu SMP Tue Sep 20 13:23:26 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu2004:~/linux# tools/testing/selftests/net/fib_nexthop_nongw.sh
TEST: nexthop: get route with nexthop without gw[ OK ]
TEST: nexthop: ping through nexthop without gw [ OK ]
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988809
Title:
ip/nexthop: fix default address selection for connected nexthop
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Bug description:
[Impact]
Packets sent by userland apps are rejected/dropped if the source
address is not specified and the corresponding route is using a
connected nexthop object.
This bug exists since linux v5.3 and has been fixed in v5.19 by the following
upstream commits:
- 747c14307214 ("ip: fix dflt addr selection for connected nexthop")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214
- cd72e61bad14 ("selftests/net: test nexthop without gw")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14
- eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd
The last commit (v6.0) fixes a regression introduced by the first
commit.
[Test Case]
A detailed test case is explained in the first commit and a self-test
is added in the second commit.
[Regression Potential]
The patch modifies some internal routing states. It has been living in the
upstream trees for 2 months and the reported regression about icmp redirects
has been fixed.
The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988809/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988809] Re: ip/nexthop: fix default address selection for connected nexthop
** Tags added: verification-done-focal verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988809
Title:
ip/nexthop: fix default address selection for connected nexthop
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Bug description:
[Impact]
Packets sent by userland apps are rejected/dropped if the source
address is not specified and the corresponding route is using a
connected nexthop object.
This bug exists since linux v5.3 and has been fixed in v5.19 by the following
upstream commits:
- 747c14307214 ("ip: fix dflt addr selection for connected nexthop")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214
- cd72e61bad14 ("selftests/net: test nexthop without gw")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14
- eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd
The last commit (v6.0) fixes a regression introduced by the first
commit.
[Test Case]
A detailed test case is explained in the first commit and a self-test
is added in the second commit.
[Regression Potential]
The patch modifies some internal routing states. It has been living in the
upstream trees for 2 months and the reported regression about icmp redirects
has been fixed.
The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988809/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988809] [NEW] ip/nexthop: fix default address selection for connected nexthop
Public bug reported:
[Impact]
Packets sent by userland apps are rejected/dropped if the source address
is not specified and the corresponding route is using a connected
nexthop object.
This bug exists since linux v5.3 and has been fixed in v5.19 by the following
upstream commits:
- 747c14307214 ("ip: fix dflt addr selection for connected nexthop")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214
- cd72e61bad14 ("selftests/net: test nexthop without gw")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14
- eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd
The last commit (v6.0) fixes a regression introduced by the first
commit.
[Test Case]
A detailed test case is explained in the first commit and a self-test is
added in the second commit.
[Regression Potential]
The patch modifies some internal routing states. It has been living in the
upstream trees for 2 months and the reported regression about icmp redirects
has been fixed.
The risk of regression should be contained.
** 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/1988809
Title:
ip/nexthop: fix default address selection for connected nexthop
Status in linux package in Ubuntu:
New
Bug description:
[Impact]
Packets sent by userland apps are rejected/dropped if the source
address is not specified and the corresponding route is using a
connected nexthop object.
This bug exists since linux v5.3 and has been fixed in v5.19 by the following
upstream commits:
- 747c14307214 ("ip: fix dflt addr selection for connected nexthop")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214
- cd72e61bad14 ("selftests/net: test nexthop without gw")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14
- eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd
The last commit (v6.0) fixes a regression introduced by the first
commit.
[Test Case]
A detailed test case is explained in the first commit and a self-test
is added in the second commit.
[Regression Potential]
The patch modifies some internal routing states. It has been living in the
upstream trees for 2 months and the reported regression about icmp redirects
has been fixed.
The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988809/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988584] Re: cgroup: all controllers mounted when using 'cgroup_no_v1='
** Summary changed: - cgroup: all controller mounted when using 'cgroup_no_v1=' + cgroup: all controllers mounted when using 'cgroup_no_v1=' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988584 Title: cgroup: all controllers mounted when using 'cgroup_no_v1=' Status in linux package in Ubuntu: Incomplete Bug description: [Impact] When mounting a cgroup hierarchy with disabled controller in cgroup v1, all available controllers will be attached. For example, boot with cgroup_no_v1=cpu or cgroup_disable=cpu, and then mount with "mount -t cgroup -ocpu cpu /sys/fs/cgroup/cpu", then all enabled controllers will be attached except cpu. This exists since linux v5.1 and fixed in linux v5.11 with this commit: 61e960b07b63 cgroup-v1: add disabled controller check in cgroup1_parse_param() https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=61e960b07b637 [Test Case] root@dut-vm:~# kexec -l /boot/vmlinuz-5.4.0-122-generic --initrd=/boot/initrd.img-5.4.0-122-generic --command-line="$(cat /proc/cmdline) cgroup_no_v1=net_prio,net_cls" root@dut-vm:~# systemctl kexec root@dut-vm:~# mount | grep cgroup tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,cpu,cpuacct,blkio,memory,devices,freezer,perf_event,hugetlb,pids,rdma) => All controllers are associated to /sys/fs/cgroup/net_cls,net_prio. Note that several reboots may be needed to reproduce the problem (it fails only when systemd tries to mount 'net_cls,net_prio' first, but the order is random). [Regression Potential] The patch is located in cgroup1_parse_param(), the potential regressions are low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988584] [NEW] cgroup: all controller mounted when using 'cgroup_no_v1='
Public bug reported: [Impact] When mounting a cgroup hierarchy with disabled controller in cgroup v1, all available controllers will be attached. For example, boot with cgroup_no_v1=cpu or cgroup_disable=cpu, and then mount with "mount -t cgroup -ocpu cpu /sys/fs/cgroup/cpu", then all enabled controllers will be attached except cpu. This exists since linux v5.1 and fixed in linux v5.11 with this commit: 61e960b07b63 cgroup-v1: add disabled controller check in cgroup1_parse_param() https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=61e960b07b637 [Test Case] root@dut-vm:~# kexec -l /boot/vmlinuz-5.4.0-122-generic --initrd=/boot/initrd.img-5.4.0-122-generic --command-line="$(cat /proc/cmdline) cgroup_no_v1=net_prio,net_cls" root@dut-vm:~# systemctl kexec root@dut-vm:~# mount | grep cgroup tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,cpu,cpuacct,blkio,memory,devices,freezer,perf_event,hugetlb,pids,rdma) => All controllers are associated to /sys/fs/cgroup/net_cls,net_prio. Note that several reboots may be needed to reproduce the problem (it fails only when systemd tries to mount 'net_cls,net_prio' first, but the order is random). [Regression Potential] The patch is located in cgroup1_parse_param(), the potential regressions are low. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988584 Title: cgroup: all controller mounted when using 'cgroup_no_v1=' Status in linux package in Ubuntu: Incomplete Bug description: [Impact] When mounting a cgroup hierarchy with disabled controller in cgroup v1, all available controllers will be attached. For example, boot with cgroup_no_v1=cpu or cgroup_disable=cpu, and then mount with "mount -t cgroup -ocpu cpu /sys/fs/cgroup/cpu", then all enabled controllers will be attached except cpu. This exists since linux v5.1 and fixed in linux v5.11 with this commit: 61e960b07b63 cgroup-v1: add disabled controller check in cgroup1_parse_param() https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=61e960b07b637 [Test Case] root@dut-vm:~# kexec -l /boot/vmlinuz-5.4.0-122-generic --initrd=/boot/initrd.img-5.4.0-122-generic --command-line="$(cat /proc/cmdline) cgroup_no_v1=net_prio,net_cls" root@dut-vm:~# systemctl kexec root@dut-vm:~# mount | grep cgroup tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,cpu,cpuacct,blkio,memory,devices,freezer,perf_event,hugetlb,pids,rdma) => All controllers are associated to /sys/fs/cgroup/net_cls,net_prio. Note that several reboots may be needed to reproduce the problem (it fails only when systemd tries to mount 'net_cls,net_prio' first, but the order is random). [Regression Potential] The patch is located in cgroup1_parse_param(), the potential regressions are low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971567] Re: TPM breaks resume from suspend
Have the same behaviour on my Lenovo Thinkpad T460s (20FAS0FD07) running
5.15.0-33-generic:
1. laptop can't get out of suspend
2. boot is longer than with 21.10 due to the time out of TPM
[0.027286] ACPI: Reserving TPM2 table memory at [mem 0xcfff8000-0xcfff8033]
[5.122778] tpm tpm0: Operation Timed out
[ 11.946910] tpm tpm0: Operation Timed out
[ 11.946942] tpm_crb: probe of MSFT0101:00 failed with error -62
[ 12.023475] ima: No TPM chip found, activating TPM-bypass!
(^^ extract of "demsg | grep -i tpm")
Thanks,
Nicolas
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1971567
Title:
TPM breaks resume from suspend
Status in linux package in Ubuntu:
Confirmed
Bug description:
After upgrading Lenovo Thinkpad X260 from 21.10 to 22.04, following
error shows at boot:
[4.830657] tpm tpm0: Operation Timed out
[ 11.654699] tpm tpm0: Operation Timed out
[ 11.654718] tpm_crb: probe of MSFT0101:00 failed with error -62
Notable consequence is that the laptop will not resume from suspend
any more, even with the power button pressed.
After disabling TPM ("Security Chip" in Lenovo BIOS) completely,
everything works normal.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-27-generic 5.15.0-27.28
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin 2147 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 4 13:15:17 2022
InstallationDate: Installed on 2022-03-06 (59 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20F5S0V400
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-27-generic N/A
linux-backports-modules-5.15.0-27-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-04-24 (10 days ago)
dmi.bios.date: 02/23/2022
dmi.bios.release: 1.49
dmi.bios.vendor: LENOVO
dmi.bios.version: R02ET76W (1.49 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20F5S0V400
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.16
dmi.modalias:
dmi:bvnLENOVO:bvrR02ET76W(1.49):bd02/23/2022:br1.49:efr1.16:svnLENOVO:pn20F5S0V400:pvrThinkPadX260:rvnLENOVO:rn20F5S0V400:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F5_BU_Think_FM_ThinkPadX260:
dmi.product.family: ThinkPad X260
dmi.product.name: 20F5S0V400
dmi.product.sku: LENOVO_MT_20F5_BU_Think_FM_ThinkPad X260
dmi.product.version: ThinkPad X260
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971567/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967721] Re: Laptop never resuming from standby
Adding more hardware: I have the same problem with a Thinkpad T460s on 22.04. Ubuntu 21.10 worked fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967721 Title: Laptop never resuming from standby Status in linux package in Ubuntu: Confirmed Bug description: On a Lenovo Thinkpad X260 with 22.04 and 5.15.0-23-generic kernel, after suspending the laptop, it's never possible to wake it up. Neither keyboard nor power button work, only way is to long-press to force poweroff and restart. This did not happen with 21.10. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 4 08:30:52 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW 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.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968591] Re: xfrm interface cannot be changed anymore
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968591 Title: xfrm interface cannot be changed anymore Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 It has been fixed upstream by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo root@dut-vm:~# ip link change foo type xfrm if_id 5678 dev lo Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968591] Re: xfrm interface cannot be changed anymore
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968591 Title: xfrm interface cannot be changed anymore Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 It has been fixed upstream by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo root@dut-vm:~# ip link change foo type xfrm if_id 5678 dev lo Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968591] Re: xfrm interface cannot be changed anymore
** Description changed: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 It has been fixed upstream by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo - root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1 + root@dut-vm:~# ip link change foo type xfrm if_id 5678 dev lo Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968591 Title: xfrm interface cannot be changed anymore Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 It has been fixed upstream by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo root@dut-vm:~# ip link change foo type xfrm if_id 5678 dev lo Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968591] [NEW] xfrm interface cannot be changed anymore
Public bug reported: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 It has been fixed upstream by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1 Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 + + It has been fixed upstream by this commit: + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1 Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968591 Title: xfrm interface cannot be changed anymore Status in linux package in Ubuntu: New Bug description: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 It has been fixed upstream by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1 Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951606] Re: bonding: arp monitoring is failing with tuntap interfaces
The patch has been merged in ubuntu focal:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=fa748ace5184
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1951606
Title:
bonding: arp monitoring is failing with tuntap interfaces
Status in linux package in Ubuntu:
Expired
Bug description:
[Impact]
When tuntap interfaces are slaves of a bonding interface, arp
monitoring is unusable.
This is fixed upstream with commit a31d27fbed5d ("tun: fix bonding
active backup with arp monitoring"). It will be included in linux
v5.16.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a31d27fbed5d
[Test Case]
Create a bonding with two tuntap interfaces and arp monitoring
configured. Before the patch, slave interfaces are flapping
continuously.
Example:
Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:28 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:31 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:31 dut-vm kernel: bond0: now running without any active
interface!
Nov 19 16:12:32 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:32 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:32 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:35 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:35 dut-vm kernel: bond0: now running without any active
interface!
Nov 19 16:12:36 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:36 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:36 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:37 dut-vm kernel: bond0: (slave ntfp3): link status definitely up
Nov 19 16:12:39 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:39 dut-vm kernel: bond0: (slave ntfp3): making interface the new
active one
[Regression Potential]
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951606/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951606] Re: bonding: arp monitoring is failing with tuntap interfaces
This patch has been backported in the official linux stable 5.4:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=01a7ecd36d1e
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1951606
Title:
bonding: arp monitoring is failing with tuntap interfaces
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
When tuntap interfaces are slaves of a bonding interface, arp
monitoring is unusable.
This is fixed upstream with commit a31d27fbed5d ("tun: fix bonding
active backup with arp monitoring"). It will be included in linux
v5.16.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a31d27fbed5d
[Test Case]
Create a bonding with two tuntap interfaces and arp monitoring
configured. Before the patch, slave interfaces are flapping
continuously.
Example:
Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:28 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:31 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:31 dut-vm kernel: bond0: now running without any active
interface!
Nov 19 16:12:32 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:32 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:32 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:35 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:35 dut-vm kernel: bond0: now running without any active
interface!
Nov 19 16:12:36 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:36 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:36 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:37 dut-vm kernel: bond0: (slave ntfp3): link status definitely up
Nov 19 16:12:39 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:39 dut-vm kernel: bond0: (slave ntfp3): making interface the new
active one
[Regression Potential]
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951606/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958032] PulseList.txt
3B:1C:2F:49:4C:9E:F2:D2:19:FC:F4:77:96: 7F:AC:4B:B7:47:BD:37:A4:2D:06:2C:8B:0D:36:E6:D2:AC:D8:FF:67: 84:C4:62:84:68:95:D6:1C:8D:1F:41:2C:2E:41:1C:D7:24:82:B1:72: 2F:DE:08:81:68:B3:51:39:DE:BB:B4:82:A6:D9:48:5C:06:E3:38:E3: 95:95:D8:F5:DF:E8:4E:C1:BA:D6:F6:A7:19:DC:A4:E4:3C:B4:14:64: D6:4D:84:3E:3B:D2:13:35:47:CD:3D:76:48:97:4D:AC:1A:52:28:B3: 0F:A8:05:69:82:AB:51:EC:5D:3C:AB:EA:98:8E:90:1A:4E:70:76:AE: 6E:A2:DD:77:24:E1:83:81:4B:C7:54:9F:17:21:C5:E4:DE:52:54:55: B0:3C:FC:2A:54:E6:B4:9D:E6:01:04:2E:53:EB:4A:0B:47:B5:16:B0: A8:25:A1:1F:E6:41:67:58:48:0D:E2:54:8B:08:35:41:F7:7A:CB:E5: 20:E8:41:70:9C:74:4E:D3:63:99:B7:AE:FF:2C:F6:B1:3D:13:DD:DB: DE:26:59:ED:E0:DB:3B:77:C3:7C:44:49 parm: max_vfs:Maximum number of virtual functions to allocate per physical function (uint) parm: debug:Debug level (0=none,...,16=all) (int) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1233 F pulseaudio /dev/snd/pcmC0D0p: nicolas1233 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-08 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Shuttle Inc. SH570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=a2970c17-9a05-4c1c-9a6d-1e824048d839 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-46-generic N/A linux-backports-modules-5.11.0-46-generic N/A linux-firmware 1.187.24 RfKill: Tags: focal Uname: Linux 5.11.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.05 dmi.board.asset.tag: To Be Filled By O.E.M dmi.board.name: SH570 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M dmi.chassis.version: To Be Filled By O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.05:bd11/04/2021:br5.19:svnShuttleInc.:pnSH570:pvr1.0:skuToBeFilledByO.E.M:rvnShuttleInc.:rnSH570:rvr1.0:cvnToBeFilledByO.E.M:ct3:cvrToBeFilledByO.E.M: dmi.product.family: To Be Filled By O.E.M dmi.product.name: SH570 dmi.product.sku: To Be Filled By O.E.M dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958032] UdevDb.txt
:D2:19:FC:F4:77:96: 7F:AC:4B:B7:47:BD:37:A4:2D:06:2C:8B:0D:36:E6:D2:AC:D8:FF:67: 84:C4:62:84:68:95:D6:1C:8D:1F:41:2C:2E:41:1C:D7:24:82:B1:72: 2F:DE:08:81:68:B3:51:39:DE:BB:B4:82:A6:D9:48:5C:06:E3:38:E3: 95:95:D8:F5:DF:E8:4E:C1:BA:D6:F6:A7:19:DC:A4:E4:3C:B4:14:64: D6:4D:84:3E:3B:D2:13:35:47:CD:3D:76:48:97:4D:AC:1A:52:28:B3: 0F:A8:05:69:82:AB:51:EC:5D:3C:AB:EA:98:8E:90:1A:4E:70:76:AE: 6E:A2:DD:77:24:E1:83:81:4B:C7:54:9F:17:21:C5:E4:DE:52:54:55: B0:3C:FC:2A:54:E6:B4:9D:E6:01:04:2E:53:EB:4A:0B:47:B5:16:B0: A8:25:A1:1F:E6:41:67:58:48:0D:E2:54:8B:08:35:41:F7:7A:CB:E5: 20:E8:41:70:9C:74:4E:D3:63:99:B7:AE:FF:2C:F6:B1:3D:13:DD:DB: DE:26:59:ED:E0:DB:3B:77:C3:7C:44:49 parm: max_vfs:Maximum number of virtual functions to allocate per physical function (uint) parm: debug:Debug level (0=none,...,16=all) (int) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1233 F pulseaudio /dev/snd/pcmC0D0p: nicolas1233 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-08 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Shuttle Inc. SH570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=a2970c17-9a05-4c1c-9a6d-1e824048d839 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-46-generic N/A linux-backports-modules-5.11.0-46-generic N/A linux-firmware 1.187.24 RfKill: Tags: focal Uname: Linux 5.11.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.05 dmi.board.asset.tag: To Be Filled By O.E.M dmi.board.name: SH570 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M dmi.chassis.version: To Be Filled By O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.05:bd11/04/2021:br5.19:svnShuttleInc.:pnSH570:pvr1.0:skuToBeFilledByO.E.M:rvnShuttleInc.:rnSH570:rvr1.0:cvnToBeFilledByO.E.M:ct3:cvrToBeFilledByO.E.M: dmi.product.family: To Be Filled By O.E.M dmi.product.name: SH570 dmi.product.sku: To Be Filled By O.E.M dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958032] WifiSyslog.txt
3B:1C:2F:49:4C:9E:F2:D2:19:FC:F4:77:96: 7F:AC:4B:B7:47:BD:37:A4:2D:06:2C:8B:0D:36:E6:D2:AC:D8:FF:67: 84:C4:62:84:68:95:D6:1C:8D:1F:41:2C:2E:41:1C:D7:24:82:B1:72: 2F:DE:08:81:68:B3:51:39:DE:BB:B4:82:A6:D9:48:5C:06:E3:38:E3: 95:95:D8:F5:DF:E8:4E:C1:BA:D6:F6:A7:19:DC:A4:E4:3C:B4:14:64: D6:4D:84:3E:3B:D2:13:35:47:CD:3D:76:48:97:4D:AC:1A:52:28:B3: 0F:A8:05:69:82:AB:51:EC:5D:3C:AB:EA:98:8E:90:1A:4E:70:76:AE: 6E:A2:DD:77:24:E1:83:81:4B:C7:54:9F:17:21:C5:E4:DE:52:54:55: B0:3C:FC:2A:54:E6:B4:9D:E6:01:04:2E:53:EB:4A:0B:47:B5:16:B0: A8:25:A1:1F:E6:41:67:58:48:0D:E2:54:8B:08:35:41:F7:7A:CB:E5: 20:E8:41:70:9C:74:4E:D3:63:99:B7:AE:FF:2C:F6:B1:3D:13:DD:DB: DE:26:59:ED:E0:DB:3B:77:C3:7C:44:49 parm: max_vfs:Maximum number of virtual functions to allocate per physical function (uint) parm: debug:Debug level (0=none,...,16=all) (int) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1233 F pulseaudio /dev/snd/pcmC0D0p: nicolas1233 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-08 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Shuttle Inc. SH570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=a2970c17-9a05-4c1c-9a6d-1e824048d839 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-46-generic N/A linux-backports-modules-5.11.0-46-generic N/A linux-firmware 1.187.24 RfKill: Tags: focal Uname: Linux 5.11.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.05 dmi.board.asset.tag: To Be Filled By O.E.M dmi.board.name: SH570 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M dmi.chassis.version: To Be Filled By O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.05:bd11/04/2021:br5.19:svnShuttleInc.:pnSH570:pvr1.0:skuToBeFilledByO.E.M:rvnShuttleInc.:rnSH570:rvr1.0:cvnToBeFilledByO.E.M:ct3:cvrToBeFilledByO.E.M: dmi.product.family: To Be Filled By O.E.M dmi.product.name: SH570 dmi.product.sku: To Be Filled By O.E.M dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958032] acpidump.txt
:1B:5E:09:74:14:75: AC:32:64:8E:FB:B0:A7:3B:1C:2F:49:4C:9E:F2:D2:19:FC:F4:77:96: 7F:AC:4B:B7:47:BD:37:A4:2D:06:2C:8B:0D:36:E6:D2:AC:D8:FF:67: 84:C4:62:84:68:95:D6:1C:8D:1F:41:2C:2E:41:1C:D7:24:82:B1:72: 2F:DE:08:81:68:B3:51:39:DE:BB:B4:82:A6:D9:48:5C:06:E3:38:E3: 95:95:D8:F5:DF:E8:4E:C1:BA:D6:F6:A7:19:DC:A4:E4:3C:B4:14:64: D6:4D:84:3E:3B:D2:13:35:47:CD:3D:76:48:97:4D:AC:1A:52:28:B3: 0F:A8:05:69:82:AB:51:EC:5D:3C:AB:EA:98:8E:90:1A:4E:70:76:AE: 6E:A2:DD:77:24:E1:83:81:4B:C7:54:9F:17:21:C5:E4:DE:52:54:55: B0:3C:FC:2A:54:E6:B4:9D:E6:01:04:2E:53:EB:4A:0B:47:B5:16:B0: A8:25:A1:1F:E6:41:67:58:48:0D:E2:54:8B:08:35:41:F7:7A:CB:E5: 20:E8:41:70:9C:74:4E:D3:63:99:B7:AE:FF:2C:F6:B1:3D:13:DD:DB: DE:26:59:ED:E0:DB:3B:77:C3:7C:44:49 parm: max_vfs:Maximum number of virtual functions to allocate per physical function (uint) parm: debug:Debug level (0=none,...,16=all) (int) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1233 F pulseaudio /dev/snd/pcmC0D0p: nicolas1233 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-08 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Shuttle Inc. SH570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=a2970c17-9a05-4c1c-9a6d-1e824048d839 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-46-generic N/A linux-backports-modules-5.11.0-46-generic N/A linux-firmware 1.187.24 RfKill: Tags: focal Uname: Linux 5.11.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.05 dmi.board.asset.tag: To Be Filled By O.E.M dmi.board.name: SH570 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M dmi.chassis.version: To Be Filled By O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.05:bd11/04/2021:br5.19:svnShuttleInc.:pnSH570:pvr1.0:skuToBeFilledByO.E.M:rvnShuttleInc.:rnSH570:rvr1.0:cvnToBeFilledByO.E.M:ct3:cvrToBeFilledByO.E.M: dmi.product.family: To Be Filled By O.E.M dmi.product.name: SH570 dmi.product.sku: To Be Filled By O.E.M dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958032] CurrentDmesg.txt
3B:1C:2F:49:4C:9E:F2:D2:19:FC:F4:77:96: 7F:AC:4B:B7:47:BD:37:A4:2D:06:2C:8B:0D:36:E6:D2:AC:D8:FF:67: 84:C4:62:84:68:95:D6:1C:8D:1F:41:2C:2E:41:1C:D7:24:82:B1:72: 2F:DE:08:81:68:B3:51:39:DE:BB:B4:82:A6:D9:48:5C:06:E3:38:E3: 95:95:D8:F5:DF:E8:4E:C1:BA:D6:F6:A7:19:DC:A4:E4:3C:B4:14:64: D6:4D:84:3E:3B:D2:13:35:47:CD:3D:76:48:97:4D:AC:1A:52:28:B3: 0F:A8:05:69:82:AB:51:EC:5D:3C:AB:EA:98:8E:90:1A:4E:70:76:AE: 6E:A2:DD:77:24:E1:83:81:4B:C7:54:9F:17:21:C5:E4:DE:52:54:55: B0:3C:FC:2A:54:E6:B4:9D:E6:01:04:2E:53:EB:4A:0B:47:B5:16:B0: A8:25:A1:1F:E6:41:67:58:48:0D:E2:54:8B:08:35:41:F7:7A:CB:E5: 20:E8:41:70:9C:74:4E:D3:63:99:B7:AE:FF:2C:F6:B1:3D:13:DD:DB: DE:26:59:ED:E0:DB:3B:77:C3:7C:44:49 parm: max_vfs:Maximum number of virtual functions to allocate per physical function (uint) parm: debug:Debug level (0=none,...,16=all) (int) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1233 F pulseaudio /dev/snd/pcmC0D0p: nicolas1233 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-08 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Shuttle Inc. SH570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=a2970c17-9a05-4c1c-9a6d-1e824048d839 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-46-generic N/A linux-backports-modules-5.11.0-46-generic N/A linux-firmware 1.187.24 RfKill: Tags: focal Uname: Linux 5.11.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.05 dmi.board.asset.tag: To Be Filled By O.E.M dmi.board.name: SH570 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M dmi.chassis.version: To Be Filled By O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.05:bd11/04/2021:br5.19:svnShuttleInc.:pnSH570:pvr1.0:skuToBeFilledByO.E.M:rvnShuttleInc.:rnSH570:rvr1.0:cvnToBeFilledByO.E.M:ct3:cvrToBeFilledByO.E.M: dmi.product.family: To Be Filled By O.E.M dmi.product.name: SH570 dmi.product.sku: To Be Filled By O.E.M dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958032] Lspci-vt.txt
3B:1C:2F:49:4C:9E:F2:D2:19:FC:F4:77:96: 7F:AC:4B:B7:47:BD:37:A4:2D:06:2C:8B:0D:36:E6:D2:AC:D8:FF:67: 84:C4:62:84:68:95:D6:1C:8D:1F:41:2C:2E:41:1C:D7:24:82:B1:72: 2F:DE:08:81:68:B3:51:39:DE:BB:B4:82:A6:D9:48:5C:06:E3:38:E3: 95:95:D8:F5:DF:E8:4E:C1:BA:D6:F6:A7:19:DC:A4:E4:3C:B4:14:64: D6:4D:84:3E:3B:D2:13:35:47:CD:3D:76:48:97:4D:AC:1A:52:28:B3: 0F:A8:05:69:82:AB:51:EC:5D:3C:AB:EA:98:8E:90:1A:4E:70:76:AE: 6E:A2:DD:77:24:E1:83:81:4B:C7:54:9F:17:21:C5:E4:DE:52:54:55: B0:3C:FC:2A:54:E6:B4:9D:E6:01:04:2E:53:EB:4A:0B:47:B5:16:B0: A8:25:A1:1F:E6:41:67:58:48:0D:E2:54:8B:08:35:41:F7:7A:CB:E5: 20:E8:41:70:9C:74:4E:D3:63:99:B7:AE:FF:2C:F6:B1:3D:13:DD:DB: DE:26:59:ED:E0:DB:3B:77:C3:7C:44:49 parm: max_vfs:Maximum number of virtual functions to allocate per physical function (uint) parm: debug:Debug level (0=none,...,16=all) (int) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1233 F pulseaudio /dev/snd/pcmC0D0p: nicolas1233 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-08 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Shuttle Inc. SH570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=a2970c17-9a05-4c1c-9a6d-1e824048d839 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-46-generic N/A linux-backports-modules-5.11.0-46-generic N/A linux-firmware 1.187.24 RfKill: Tags: focal Uname: Linux 5.11.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.05 dmi.board.asset.tag: To Be Filled By O.E.M dmi.board.name: SH570 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M dmi.chassis.version: To Be Filled By O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.05:bd11/04/2021:br5.19:svnShuttleInc.:pnSH570:pvr1.0:skuToBeFilledByO.E.M:rvnShuttleInc.:rnSH570:rvr1.0:cvnToBeFilledByO.E.M:ct3:cvrToBeFilledByO.E.M: dmi.product.family: To Be Filled By O.E.M dmi.product.name: SH570 dmi.product.sku: To Be Filled By O.E.M dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958032] Lspci.txt
:19:FC:F4:77:96: 7F:AC:4B:B7:47:BD:37:A4:2D:06:2C:8B:0D:36:E6:D2:AC:D8:FF:67: 84:C4:62:84:68:95:D6:1C:8D:1F:41:2C:2E:41:1C:D7:24:82:B1:72: 2F:DE:08:81:68:B3:51:39:DE:BB:B4:82:A6:D9:48:5C:06:E3:38:E3: 95:95:D8:F5:DF:E8:4E:C1:BA:D6:F6:A7:19:DC:A4:E4:3C:B4:14:64: D6:4D:84:3E:3B:D2:13:35:47:CD:3D:76:48:97:4D:AC:1A:52:28:B3: 0F:A8:05:69:82:AB:51:EC:5D:3C:AB:EA:98:8E:90:1A:4E:70:76:AE: 6E:A2:DD:77:24:E1:83:81:4B:C7:54:9F:17:21:C5:E4:DE:52:54:55: B0:3C:FC:2A:54:E6:B4:9D:E6:01:04:2E:53:EB:4A:0B:47:B5:16:B0: A8:25:A1:1F:E6:41:67:58:48:0D:E2:54:8B:08:35:41:F7:7A:CB:E5: 20:E8:41:70:9C:74:4E:D3:63:99:B7:AE:FF:2C:F6:B1:3D:13:DD:DB: DE:26:59:ED:E0:DB:3B:77:C3:7C:44:49 parm: max_vfs:Maximum number of virtual functions to allocate per physical function (uint) parm: debug:Debug level (0=none,...,16=all) (int) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1233 F pulseaudio /dev/snd/pcmC0D0p: nicolas1233 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-08 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Shuttle Inc. SH570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=a2970c17-9a05-4c1c-9a6d-1e824048d839 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-46-generic N/A linux-backports-modules-5.11.0-46-generic N/A linux-firmware 1.187.24 RfKill: Tags: focal Uname: Linux 5.11.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.05 dmi.board.asset.tag: To Be Filled By O.E.M dmi.board.name: SH570 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M dmi.chassis.version: To Be Filled By O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.05:bd11/04/2021:br5.19:svnShuttleInc.:pnSH570:pvr1.0:skuToBeFilledByO.E.M:rvnShuttleInc.:rnSH570:rvr1.0:cvnToBeFilledByO.E.M:ct3:cvrToBeFilledByO.E.M: dmi.product.family: To Be Filled By O.E.M dmi.product.name: SH570 dmi.product.sku: To Be Filled By O.E.M dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958032] ProcInterrupts.txt
3B:1C:2F:49:4C:9E:F2:D2:19:FC:F4:77:96: 7F:AC:4B:B7:47:BD:37:A4:2D:06:2C:8B:0D:36:E6:D2:AC:D8:FF:67: 84:C4:62:84:68:95:D6:1C:8D:1F:41:2C:2E:41:1C:D7:24:82:B1:72: 2F:DE:08:81:68:B3:51:39:DE:BB:B4:82:A6:D9:48:5C:06:E3:38:E3: 95:95:D8:F5:DF:E8:4E:C1:BA:D6:F6:A7:19:DC:A4:E4:3C:B4:14:64: D6:4D:84:3E:3B:D2:13:35:47:CD:3D:76:48:97:4D:AC:1A:52:28:B3: 0F:A8:05:69:82:AB:51:EC:5D:3C:AB:EA:98:8E:90:1A:4E:70:76:AE: 6E:A2:DD:77:24:E1:83:81:4B:C7:54:9F:17:21:C5:E4:DE:52:54:55: B0:3C:FC:2A:54:E6:B4:9D:E6:01:04:2E:53:EB:4A:0B:47:B5:16:B0: A8:25:A1:1F:E6:41:67:58:48:0D:E2:54:8B:08:35:41:F7:7A:CB:E5: 20:E8:41:70:9C:74:4E:D3:63:99:B7:AE:FF:2C:F6:B1:3D:13:DD:DB: DE:26:59:ED:E0:DB:3B:77:C3:7C:44:49 parm: max_vfs:Maximum number of virtual functions to allocate per physical function (uint) parm: debug:Debug level (0=none,...,16=all) (int) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1233 F pulseaudio /dev/snd/pcmC0D0p: nicolas1233 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-08 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Shuttle Inc. SH570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=a2970c17-9a05-4c1c-9a6d-1e824048d839 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-46-generic N/A linux-backports-modules-5.11.0-46-generic N/A linux-firmware 1.187.24 RfKill: Tags: focal Uname: Linux 5.11.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.05 dmi.board.asset.tag: To Be Filled By O.E.M dmi.board.name: SH570 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M dmi.chassis.version: To Be Filled By O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.05:bd11/04/2021:br5.19:svnShuttleInc.:pnSH570:pvr1.0:skuToBeFilledByO.E.M:rvnShuttleInc.:rnSH570:rvr1.0:cvnToBeFilledByO.E.M:ct3:cvrToBeFilledByO.E.M: dmi.product.family: To Be Filled By O.E.M dmi.product.name: SH570 dmi.product.sku: To Be Filled By O.E.M dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958032] ProcCpuinfoMinimal.txt
A7:3B:1C:2F:49:4C:9E:F2:D2:19:FC:F4:77:96: 7F:AC:4B:B7:47:BD:37:A4:2D:06:2C:8B:0D:36:E6:D2:AC:D8:FF:67: 84:C4:62:84:68:95:D6:1C:8D:1F:41:2C:2E:41:1C:D7:24:82:B1:72: 2F:DE:08:81:68:B3:51:39:DE:BB:B4:82:A6:D9:48:5C:06:E3:38:E3: 95:95:D8:F5:DF:E8:4E:C1:BA:D6:F6:A7:19:DC:A4:E4:3C:B4:14:64: D6:4D:84:3E:3B:D2:13:35:47:CD:3D:76:48:97:4D:AC:1A:52:28:B3: 0F:A8:05:69:82:AB:51:EC:5D:3C:AB:EA:98:8E:90:1A:4E:70:76:AE: 6E:A2:DD:77:24:E1:83:81:4B:C7:54:9F:17:21:C5:E4:DE:52:54:55: B0:3C:FC:2A:54:E6:B4:9D:E6:01:04:2E:53:EB:4A:0B:47:B5:16:B0: A8:25:A1:1F:E6:41:67:58:48:0D:E2:54:8B:08:35:41:F7:7A:CB:E5: 20:E8:41:70:9C:74:4E:D3:63:99:B7:AE:FF:2C:F6:B1:3D:13:DD:DB: DE:26:59:ED:E0:DB:3B:77:C3:7C:44:49 parm: max_vfs:Maximum number of virtual functions to allocate per physical function (uint) parm: debug:Debug level (0=none,...,16=all) (int) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1233 F pulseaudio /dev/snd/pcmC0D0p: nicolas1233 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-08 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Shuttle Inc. SH570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=a2970c17-9a05-4c1c-9a6d-1e824048d839 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-46-generic N/A linux-backports-modules-5.11.0-46-generic N/A linux-firmware 1.187.24 RfKill: Tags: focal Uname: Linux 5.11.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.05 dmi.board.asset.tag: To Be Filled By O.E.M dmi.board.name: SH570 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M dmi.chassis.version: To Be Filled By O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.05:bd11/04/2021:br5.19:svnShuttleInc.:pnSH570:pvr1.0:skuToBeFilledByO.E.M:rvnShuttleInc.:rnSH570:rvr1.0:cvnToBeFilledByO.E.M:ct3:cvrToBeFilledByO.E.M: dmi.product.family: To Be Filled By O.E.M dmi.product.name: SH570 dmi.product.sku: To Be Filled By O.E.M dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958032] CRDA.txt
:FC:F4:77:96: 7F:AC:4B:B7:47:BD:37:A4:2D:06:2C:8B:0D:36:E6:D2:AC:D8:FF:67: 84:C4:62:84:68:95:D6:1C:8D:1F:41:2C:2E:41:1C:D7:24:82:B1:72: 2F:DE:08:81:68:B3:51:39:DE:BB:B4:82:A6:D9:48:5C:06:E3:38:E3: 95:95:D8:F5:DF:E8:4E:C1:BA:D6:F6:A7:19:DC:A4:E4:3C:B4:14:64: D6:4D:84:3E:3B:D2:13:35:47:CD:3D:76:48:97:4D:AC:1A:52:28:B3: 0F:A8:05:69:82:AB:51:EC:5D:3C:AB:EA:98:8E:90:1A:4E:70:76:AE: 6E:A2:DD:77:24:E1:83:81:4B:C7:54:9F:17:21:C5:E4:DE:52:54:55: B0:3C:FC:2A:54:E6:B4:9D:E6:01:04:2E:53:EB:4A:0B:47:B5:16:B0: A8:25:A1:1F:E6:41:67:58:48:0D:E2:54:8B:08:35:41:F7:7A:CB:E5: 20:E8:41:70:9C:74:4E:D3:63:99:B7:AE:FF:2C:F6:B1:3D:13:DD:DB: DE:26:59:ED:E0:DB:3B:77:C3:7C:44:49 parm: max_vfs:Maximum number of virtual functions to allocate per physical function (uint) parm: debug:Debug level (0=none,...,16=all) (int) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1233 F pulseaudio /dev/snd/pcmC0D0p: nicolas1233 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-08 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Shuttle Inc. SH570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=a2970c17-9a05-4c1c-9a6d-1e824048d839 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-46-generic N/A linux-backports-modules-5.11.0-46-generic N/A linux-firmware 1.187.24 RfKill: Tags: focal Uname: Linux 5.11.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.05 dmi.board.asset.tag: To Be Filled By O.E.M dmi.board.name: SH570 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M dmi.chassis.version: To Be Filled By O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.05:bd11/04/2021:br5.19:svnShuttleInc.:pnSH570:pvr1.0:skuToBeFilledByO.E.M:rvnShuttleInc.:rnSH570:rvr1.0:cvnToBeFilledByO.E.M:ct3:cvrToBeFilledByO.E.M: dmi.product.family: To Be Filled By O.E.M dmi.product.name: SH570 dmi.product.sku: To Be Filled By O.E.M dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958032] IwConfig.txt
3B:1C:2F:49:4C:9E:F2:D2:19:FC:F4:77:96: 7F:AC:4B:B7:47:BD:37:A4:2D:06:2C:8B:0D:36:E6:D2:AC:D8:FF:67: 84:C4:62:84:68:95:D6:1C:8D:1F:41:2C:2E:41:1C:D7:24:82:B1:72: 2F:DE:08:81:68:B3:51:39:DE:BB:B4:82:A6:D9:48:5C:06:E3:38:E3: 95:95:D8:F5:DF:E8:4E:C1:BA:D6:F6:A7:19:DC:A4:E4:3C:B4:14:64: D6:4D:84:3E:3B:D2:13:35:47:CD:3D:76:48:97:4D:AC:1A:52:28:B3: 0F:A8:05:69:82:AB:51:EC:5D:3C:AB:EA:98:8E:90:1A:4E:70:76:AE: 6E:A2:DD:77:24:E1:83:81:4B:C7:54:9F:17:21:C5:E4:DE:52:54:55: B0:3C:FC:2A:54:E6:B4:9D:E6:01:04:2E:53:EB:4A:0B:47:B5:16:B0: A8:25:A1:1F:E6:41:67:58:48:0D:E2:54:8B:08:35:41:F7:7A:CB:E5: 20:E8:41:70:9C:74:4E:D3:63:99:B7:AE:FF:2C:F6:B1:3D:13:DD:DB: DE:26:59:ED:E0:DB:3B:77:C3:7C:44:49 parm: max_vfs:Maximum number of virtual functions to allocate per physical function (uint) parm: debug:Debug level (0=none,...,16=all) (int) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1233 F pulseaudio /dev/snd/pcmC0D0p: nicolas1233 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-08 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Shuttle Inc. SH570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=a2970c17-9a05-4c1c-9a6d-1e824048d839 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-46-generic N/A linux-backports-modules-5.11.0-46-generic N/A linux-firmware 1.187.24 RfKill: Tags: focal Uname: Linux 5.11.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.05 dmi.board.asset.tag: To Be Filled By O.E.M dmi.board.name: SH570 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M dmi.chassis.version: To Be Filled By O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.05:bd11/04/2021:br5.19:svnShuttleInc.:pnSH570:pvr1.0:skuToBeFilledByO.E.M:rvnShuttleInc.:rnSH570:rvr1.0:cvnToBeFilledByO.E.M:ct3:cvrToBeFilledByO.E.M: dmi.product.family: To Be Filled By O.E.M dmi.product.name: SH570 dmi.product.sku: To Be Filled By O.E.M dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958032] ProcCpuinfo.txt
3B:1C:2F:49:4C:9E:F2:D2:19:FC:F4:77:96: 7F:AC:4B:B7:47:BD:37:A4:2D:06:2C:8B:0D:36:E6:D2:AC:D8:FF:67: 84:C4:62:84:68:95:D6:1C:8D:1F:41:2C:2E:41:1C:D7:24:82:B1:72: 2F:DE:08:81:68:B3:51:39:DE:BB:B4:82:A6:D9:48:5C:06:E3:38:E3: 95:95:D8:F5:DF:E8:4E:C1:BA:D6:F6:A7:19:DC:A4:E4:3C:B4:14:64: D6:4D:84:3E:3B:D2:13:35:47:CD:3D:76:48:97:4D:AC:1A:52:28:B3: 0F:A8:05:69:82:AB:51:EC:5D:3C:AB:EA:98:8E:90:1A:4E:70:76:AE: 6E:A2:DD:77:24:E1:83:81:4B:C7:54:9F:17:21:C5:E4:DE:52:54:55: B0:3C:FC:2A:54:E6:B4:9D:E6:01:04:2E:53:EB:4A:0B:47:B5:16:B0: A8:25:A1:1F:E6:41:67:58:48:0D:E2:54:8B:08:35:41:F7:7A:CB:E5: 20:E8:41:70:9C:74:4E:D3:63:99:B7:AE:FF:2C:F6:B1:3D:13:DD:DB: DE:26:59:ED:E0:DB:3B:77:C3:7C:44:49 parm: max_vfs:Maximum number of virtual functions to allocate per physical function (uint) parm: debug:Debug level (0=none,...,16=all) (int) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1233 F pulseaudio /dev/snd/pcmC0D0p: nicolas1233 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-08 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Shuttle Inc. SH570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=a2970c17-9a05-4c1c-9a6d-1e824048d839 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-46-generic N/A linux-backports-modules-5.11.0-46-generic N/A linux-firmware 1.187.24 RfKill: Tags: focal Uname: Linux 5.11.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.05 dmi.board.asset.tag: To Be Filled By O.E.M dmi.board.name: SH570 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M dmi.chassis.version: To Be Filled By O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.05:bd11/04/2021:br5.19:svnShuttleInc.:pnSH570:pvr1.0:skuToBeFilledByO.E.M:rvnShuttleInc.:rnSH570:rvr1.0:cvnToBeFilledByO.E.M:ct3:cvrToBeFilledByO.E.M: dmi.product.family: To Be Filled By O.E.M dmi.product.name: SH570 dmi.product.sku: To Be Filled By O.E.M dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958032] ProcModules.txt
3B:1C:2F:49:4C:9E:F2:D2:19:FC:F4:77:96: 7F:AC:4B:B7:47:BD:37:A4:2D:06:2C:8B:0D:36:E6:D2:AC:D8:FF:67: 84:C4:62:84:68:95:D6:1C:8D:1F:41:2C:2E:41:1C:D7:24:82:B1:72: 2F:DE:08:81:68:B3:51:39:DE:BB:B4:82:A6:D9:48:5C:06:E3:38:E3: 95:95:D8:F5:DF:E8:4E:C1:BA:D6:F6:A7:19:DC:A4:E4:3C:B4:14:64: D6:4D:84:3E:3B:D2:13:35:47:CD:3D:76:48:97:4D:AC:1A:52:28:B3: 0F:A8:05:69:82:AB:51:EC:5D:3C:AB:EA:98:8E:90:1A:4E:70:76:AE: 6E:A2:DD:77:24:E1:83:81:4B:C7:54:9F:17:21:C5:E4:DE:52:54:55: B0:3C:FC:2A:54:E6:B4:9D:E6:01:04:2E:53:EB:4A:0B:47:B5:16:B0: A8:25:A1:1F:E6:41:67:58:48:0D:E2:54:8B:08:35:41:F7:7A:CB:E5: 20:E8:41:70:9C:74:4E:D3:63:99:B7:AE:FF:2C:F6:B1:3D:13:DD:DB: DE:26:59:ED:E0:DB:3B:77:C3:7C:44:49 parm: max_vfs:Maximum number of virtual functions to allocate per physical function (uint) parm: debug:Debug level (0=none,...,16=all) (int) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1233 F pulseaudio /dev/snd/pcmC0D0p: nicolas1233 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-08 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Shuttle Inc. SH570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=a2970c17-9a05-4c1c-9a6d-1e824048d839 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-46-generic N/A linux-backports-modules-5.11.0-46-generic N/A linux-firmware 1.187.24 RfKill: Tags: focal Uname: Linux 5.11.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.05 dmi.board.asset.tag: To Be Filled By O.E.M dmi.board.name: SH570 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M dmi.chassis.version: To Be Filled By O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.05:bd11/04/2021:br5.19:svnShuttleInc.:pnSH570:pvr1.0:skuToBeFilledByO.E.M:rvnShuttleInc.:rnSH570:rvr1.0:cvnToBeFilledByO.E.M:ct3:cvrToBeFilledByO.E.M: dmi.product.family: To Be Filled By O.E.M dmi.product.name: SH570 dmi.product.sku: To Be Filled By O.E.M dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958032] Lsusb-v.txt
3B:1C:2F:49:4C:9E:F2:D2:19:FC:F4:77:96: 7F:AC:4B:B7:47:BD:37:A4:2D:06:2C:8B:0D:36:E6:D2:AC:D8:FF:67: 84:C4:62:84:68:95:D6:1C:8D:1F:41:2C:2E:41:1C:D7:24:82:B1:72: 2F:DE:08:81:68:B3:51:39:DE:BB:B4:82:A6:D9:48:5C:06:E3:38:E3: 95:95:D8:F5:DF:E8:4E:C1:BA:D6:F6:A7:19:DC:A4:E4:3C:B4:14:64: D6:4D:84:3E:3B:D2:13:35:47:CD:3D:76:48:97:4D:AC:1A:52:28:B3: 0F:A8:05:69:82:AB:51:EC:5D:3C:AB:EA:98:8E:90:1A:4E:70:76:AE: 6E:A2:DD:77:24:E1:83:81:4B:C7:54:9F:17:21:C5:E4:DE:52:54:55: B0:3C:FC:2A:54:E6:B4:9D:E6:01:04:2E:53:EB:4A:0B:47:B5:16:B0: A8:25:A1:1F:E6:41:67:58:48:0D:E2:54:8B:08:35:41:F7:7A:CB:E5: 20:E8:41:70:9C:74:4E:D3:63:99:B7:AE:FF:2C:F6:B1:3D:13:DD:DB: DE:26:59:ED:E0:DB:3B:77:C3:7C:44:49 parm: max_vfs:Maximum number of virtual functions to allocate per physical function (uint) parm: debug:Debug level (0=none,...,16=all) (int) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1233 F pulseaudio /dev/snd/pcmC0D0p: nicolas1233 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-08 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 13: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Shuttle Inc. SH570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=a2970c17-9a05-4c1c-9a6d-1e824048d839 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-46-generic N/A linux-backports-modules-5.11.0-46-generic N/A linux-firmware 1.187.24 RfKill: Tags: focal Uname: Linux 5.11.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.05 dmi.board.asset.tag: To Be Filled By O.E.M dmi.board.name: SH570 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M dmi.chassis.version: To Be Filled By O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.05:bd11/04/2021:br5.19:svnShuttleInc.:pnSH570:pvr1.0:skuToBeFilledByO.E.M:rvnShuttleInc.:rnSH570:rvr1.0:cvnToBeFilledByO.E.M:ct3:cvrToBeFilledByO.E.M: dmi.product.family: To Be Filled By O.E.M dmi.product.name: SH570 dmi.product.sku: To Be Filled By O.E.M dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958032] Re: [igb - Intel NIC] Adapter reset due to TX unit hangs
D6:4D:84:3E:3B:D2:13:35:47:CD:3D:76:48:97:4D:AC:1A:52:28:B3: 0F:A8:05:69:82:AB:51:EC:5D:3C:AB:EA:98:8E:90:1A:4E:70:76:AE: 6E:A2:DD:77:24:E1:83:81:4B:C7:54:9F:17:21:C5:E4:DE:52:54:55: B0:3C:FC:2A:54:E6:B4:9D:E6:01:04:2E:53:EB:4A:0B:47:B5:16:B0: A8:25:A1:1F:E6:41:67:58:48:0D:E2:54:8B:08:35:41:F7:7A:CB:E5: 20:E8:41:70:9C:74:4E:D3:63:99:B7:AE:FF:2C:F6:B1:3D:13:DD:DB: DE:26:59:ED:E0:DB:3B:77:C3:7C:44:49 parm: max_vfs:Maximum number of virtual functions to allocate per physical function (uint) parm: debug:Debug level (0=none,...,16=all) (int) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: nicolas1233 F pulseaudio + /dev/snd/pcmC0D0p: nicolas1233 F...m pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2022-01-08 (9 days ago) + InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Lsusb-t: + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M + |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M + |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M + |__ Port 13: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M + MachineType: Shuttle Inc. SH570 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=a2970c17-9a05-4c1c-9a6d-1e824048d839 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 + RelatedPackageVersions: + linux-restricted-modules-5.11.0-46-generic N/A + linux-backports-modules-5.11.0-46-generic N/A + linux-firmware 1.187.24 + RfKill: + + Tags: focal + Uname: Linux 5.11.0-46-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/04/2021 + dmi.bios.release: 5.19 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: 1.05 + dmi.board.asset.tag: To Be Filled By O.E.M + dmi.board.name: SH570 + dmi.board.vendor: Shuttle Inc. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: To Be Filled By O.E.M + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M + dmi.chassis.version: To Be Filled By O.E.M + dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.05:bd11/04/2021:br5.19:svnShuttleInc.:pnSH570:pvr1.0:skuToBeFilledByO.E.M:rvnShuttleInc.:rnSH570:rvr1.0:cvnToBeFilledByO.E.M:ct3:cvrToBeFilledByO.E.M: + dmi.product.family: To Be Filled By O.E.M + dmi.product.name: SH570 + dmi.product.sku: To Be Filled By O.E.M + dmi.product.version: 1.0 + dmi.sys.vendor: Shuttle Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1958032/+attachment/5554963/+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/1958032 Title: [igb - Intel NIC] Adapter reset due to TX unit hangs Status in linux package in Ubuntu: Confirmed Bug description: Hi, I get no network connection established. In dmesg I get repeatively messages regarding a TX hang and adapter reset: [ 202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ 204.929067] igb :01:00.0: Detected Tx Unit Hang Tx Queue <3> TDH <0> TDT <2> next_to_use <2> next_to_clean<0> buffer_info[next_to_clean] time_stamp next_to_watch<3bbba65a> jiffies desc.status <128200> [ 204.929065] igb :01:00.0: Detected Tx Unit Hang Tx Queue <2> TDH <0> TDT <2> next_to_use <2> next_to_clean<0> buffer_info[next_to_clean] time_sta
[Kernel-packages] [Bug 1956399] Re: Regression: kernel does not init graphics (?) on AMD Ryzen 5 3400G
+1 this is a bug for me too -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956399 Title: Regression: kernel does not init graphics (?) on AMD Ryzen 5 3400G Status in linux package in Ubuntu: Confirmed Bug description: After latest upgrade of linux-image to 5.13.0.23.34 system seem to boot, but it looks like graphics does not initialize correctly. After showing initial init logging, at the moment when X should init and graphics login should appear, monitor just goes to sleep and provides diagnostic message that there is no signal on selected input. apt upgrade log: Start-Date: 2022-01-04 23:21:11 Commandline: apt upgrade Requested-By: xx (1000) Install: linux-modules-extra-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-image-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-modules-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23:amd64 (5.13.0-23.23, automatic) Upgrade: linux-headers-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), google-chrome-stable:amd64 (96.0.4664.110-1, 97.0.4692.71-1), linux-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-image-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-libc-dev:amd64 (5.13.0-22.22, 5.13.0-23.23) End-Date: 2022-01-04 23:22:39 Currently working around this issues by booting previous version of the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-generic 5.13.0.23.34 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 2532 F pulseaudio /dev/snd/pcmC1D0p: alexei 2532 F...m pulseaudio /dev/snd/controlC0: alexei 2532 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 01:02:53 2022 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (2190 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp8s0no wireless extensions. lxcbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-05 (91 days ago) dmi.bios.date: 05/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.00 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd05/10/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951606] [NEW] bonding: arp monitoring is failing with tuntap interfaces
Public bug reported:
[Impact]
When tuntap interfaces are slaves of a bonding interface, arp monitoring
is unusable.
This is fixed upstream with commit a31d27fbed5d ("tun: fix bonding
active backup with arp monitoring"). It will be included in linux v5.16.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a31d27fbed5d
[Test Case]
Create a bonding with two tuntap interfaces and arp monitoring
configured. Before the patch, slave interfaces are flapping
continuously.
Example:
Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:28 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:31 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:31 dut-vm kernel: bond0: now running without any active interface!
Nov 19 16:12:32 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:32 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:32 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:35 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:35 dut-vm kernel: bond0: now running without any active interface!
Nov 19 16:12:36 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:36 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:36 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:37 dut-vm kernel: bond0: (slave ntfp3): link status definitely up
Nov 19 16:12:39 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:39 dut-vm kernel: bond0: (slave ntfp3): making interface the new
active one
[Regression Potential]
The patch is trivial, the potential regressions are low.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
[Impact]
When tuntap interfaces are slaves of a bonding interface, arp monitoring
- is fails
+ is unusable.
This is fixed upstream with commit a31d27fbed5d ("tun: fix bonding
active backup with arp monitoring"). It will be included in linux v5.16.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a31d27fbed5d
[Test Case]
Create a bonding with two tuntap interfaces and arp monitoring
configured. Before the patch, slave interfaces are flapping
continuously.
Example:
Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:28 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:31 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:31 dut-vm kernel: bond0: now running without any active
interface!
Nov 19 16:12:32 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:32 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:32 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:35 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:35 dut-vm kernel: bond0: now running without any active
interface!
Nov 19 16:12:36 dut-vm kernel: bond0: (slave ntfp2): link status definitely up
Nov 19 16:12:36 dut-vm kernel: bond0: (slave ntfp2): making interface the new
active one
Nov 19 16:12:36 dut-vm kernel: bond0: active interface up!
Nov 19 16:12:37 dut-vm kernel: bond0: (slave ntfp3): link status definitely up
Nov 19 16:12:39 dut-vm kernel: bond0: (slave ntfp2): link status definitely
down, disabling slave
Nov 19 16:12:39 dut-vm kernel: bond0: (slave ntfp3): making interface the new
active one
[Regression Potential]
The patch is trivial, the potential regressions are low.
** Summary changed:
- bondig: arp monitoring is failing with tuntap interfaces
+ bonding: arp monitoring is failing with tuntap interfaces
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1951606
Title:
bonding: arp monitoring is failing with tuntap interfaces
Status in linux package in Ubuntu:
New
Bug description:
[Impact]
When tuntap interfaces are slaves of a bonding interface, arp
monitoring is unusable.
This is fixed upstream with commit a31d27fbed5d ("tun: fix bonding
active backup with arp monitoring"). It will be included in linux
v5.16.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a31d27fbed5d
[Test Case]
Create a bonding with two tuntap interfaces and arp monitoring
configured. Before the patch, slave interfaces are flapping
continuously.
Example:
Nov 19 16:12:28 dut-vm kernel: bond0: (slave ntfp2): link status
[Kernel-packages] [Bug 1947164] Re: ebpf: bpf_redirect fails with ip6 gre interfaces
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1947164
Title:
ebpf: bpf_redirect fails with ip6 gre interfaces
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
The tc ebpf bpf_redirect() function cannot be used with ipv6 gre
interface.
This is fixed upstream with commit a3fa449ffcf5 ("net: handle
ARPHRD_IP6GRE in dev_is_mac_header_xmit()"), included in linux v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a3fa449ffcf5
It would probably be good to also backport this one: 3b707c3008ca
("net: dev_is_mac_header_xmit() true for ARPHRD_RAWIP").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3b707c3008ca
[Test Case]
Create an ebpf program that redirect packets to an ipv6 gre interface
and load it with tc.
[Regression Potential]
The patches are trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947164/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947164] Re: ebpf: bpf_redirect fails with ip6 gre interfaces
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1947164
Title:
ebpf: bpf_redirect fails with ip6 gre interfaces
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
The tc ebpf bpf_redirect() function cannot be used with ipv6 gre
interface.
This is fixed upstream with commit a3fa449ffcf5 ("net: handle
ARPHRD_IP6GRE in dev_is_mac_header_xmit()"), included in linux v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a3fa449ffcf5
It would probably be good to also backport this one: 3b707c3008ca
("net: dev_is_mac_header_xmit() true for ARPHRD_RAWIP").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3b707c3008ca
[Test Case]
Create an ebpf program that redirect packets to an ipv6 gre interface
and load it with tc.
[Regression Potential]
The patches are trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947164/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947164] Re: ebpf: bpf_redirect fails with ip6 gre interfaces
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1947164
Title:
ebpf: bpf_redirect fails with ip6 gre interfaces
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
The tc ebpf bpf_redirect() function cannot be used with ipv6 gre
interface.
This is fixed upstream with commit a3fa449ffcf5 ("net: handle
ARPHRD_IP6GRE in dev_is_mac_header_xmit()"), included in linux v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a3fa449ffcf5
It would probably be good to also backport this one: 3b707c3008ca
("net: dev_is_mac_header_xmit() true for ARPHRD_RAWIP").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3b707c3008ca
[Test Case]
Create an ebpf program that redirect packets to an ipv6 gre interface
and load it with tc.
[Regression Potential]
The patches are trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947164/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947164] Re: ebpf: bpf_redirect fails with ip6 gre interfaces
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1947164
Title:
ebpf: bpf_redirect fails with ip6 gre interfaces
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
The tc ebpf bpf_redirect() function cannot be used with ipv6 gre
interface.
This is fixed upstream with commit a3fa449ffcf5 ("net: handle
ARPHRD_IP6GRE in dev_is_mac_header_xmit()"), included in linux v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a3fa449ffcf5
It would probably be good to also backport this one: 3b707c3008ca
("net: dev_is_mac_header_xmit() true for ARPHRD_RAWIP").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3b707c3008ca
[Test Case]
Create an ebpf program that redirect packets to an ipv6 gre interface
and load it with tc.
[Regression Potential]
The patches are trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947164/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948343] Re: Docking Station crash ramdomly after october 19 updates
Update: 4 hours running Ubuntu 20.04.3 with monitor On, but not using it (using only the notebook display) not crashing at all. It appears to crash only, when are changes in the External monitor image. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948343 Title: Docking Station crash ramdomly after october 19 updates Status in linux package in Ubuntu: Confirmed Bug description: My dell D6000 dockingstation start crashing after installation of updates on october 19. Now, randomly the external HDMI monitor goes blank for 5 second until dock restart. But this fails make external webcam (connected to dockstation), and bluetooth headphones (mic at external web cam) got unconfigured, sending audio to the dock port and getting mic from it not regarding is not used, putting in a meeting without any sound. And because internet is also used via D6000 wired ethernet port, I got disconnected from VPN and RDP connections too. Release info: Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 18:00:54 2021 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 RelatedPackageVersions: linux-restricted-modules-5.10.0-1050-oem N/A linux-backports-modules-5.10.0-1050-oem N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.10.0-1050-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948343] Re: Docking Station crash ramdomly after october 19 updates
UPDATE: 3 hours running windows 10 -> no problem. 2 hours running Ubuntu 20.04.2 -> No problem 40 minutes running Ubuntu 20.04.3 -> Start crashing. Id think is not a Hardware problem. All it show its something in 20.04.3 updates/upgrades. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948343 Title: Docking Station crash ramdomly after october 19 updates Status in linux package in Ubuntu: Confirmed Bug description: My dell D6000 dockingstation start crashing after installation of updates on october 19. Now, randomly the external HDMI monitor goes blank for 5 second until dock restart. But this fails make external webcam (connected to dockstation), and bluetooth headphones (mic at external web cam) got unconfigured, sending audio to the dock port and getting mic from it not regarding is not used, putting in a meeting without any sound. And because internet is also used via D6000 wired ethernet port, I got disconnected from VPN and RDP connections too. Release info: Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 18:00:54 2021 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 RelatedPackageVersions: linux-restricted-modules-5.10.0-1050-oem N/A linux-backports-modules-5.10.0-1050-oem N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.10.0-1050-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948343] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1948343/+attachment/5535248/+files/ProcModules.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/1948343 Title: Docking Station crash ramdomly after october 19 updates Status in linux package in Ubuntu: Confirmed Bug description: My dell D6000 dockingstation start crashing after installation of updates on october 19. Now, randomly the external HDMI monitor goes blank for 5 second until dock restart. But this fails make external webcam (connected to dockstation), and bluetooth headphones (mic at external web cam) got unconfigured, sending audio to the dock port and getting mic from it not regarding is not used, putting in a meeting without any sound. And because internet is also used via D6000 wired ethernet port, I got disconnected from VPN and RDP connections too. Release info: Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 18:00:54 2021 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 RelatedPackageVersions: linux-restricted-modules-5.10.0-1050-oem N/A linux-backports-modules-5.10.0-1050-oem N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.10.0-1050-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948343] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1948343/+attachment/5535247/+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/1948343 Title: Docking Station crash ramdomly after october 19 updates Status in linux package in Ubuntu: Confirmed Bug description: My dell D6000 dockingstation start crashing after installation of updates on october 19. Now, randomly the external HDMI monitor goes blank for 5 second until dock restart. But this fails make external webcam (connected to dockstation), and bluetooth headphones (mic at external web cam) got unconfigured, sending audio to the dock port and getting mic from it not regarding is not used, putting in a meeting without any sound. And because internet is also used via D6000 wired ethernet port, I got disconnected from VPN and RDP connections too. Release info: Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 18:00:54 2021 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 RelatedPackageVersions: linux-restricted-modules-5.10.0-1050-oem N/A linux-backports-modules-5.10.0-1050-oem N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.10.0-1050-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948343] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1948343/+attachment/5535243/+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/1948343 Title: Docking Station crash ramdomly after october 19 updates Status in linux package in Ubuntu: Confirmed Bug description: My dell D6000 dockingstation start crashing after installation of updates on october 19. Now, randomly the external HDMI monitor goes blank for 5 second until dock restart. But this fails make external webcam (connected to dockstation), and bluetooth headphones (mic at external web cam) got unconfigured, sending audio to the dock port and getting mic from it not regarding is not used, putting in a meeting without any sound. And because internet is also used via D6000 wired ethernet port, I got disconnected from VPN and RDP connections too. Release info: Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 18:00:54 2021 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 RelatedPackageVersions: linux-restricted-modules-5.10.0-1050-oem N/A linux-backports-modules-5.10.0-1050-oem N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.10.0-1050-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948343] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1948343/+attachment/5535251/+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/1948343 Title: Docking Station crash ramdomly after october 19 updates Status in linux package in Ubuntu: Confirmed Bug description: My dell D6000 dockingstation start crashing after installation of updates on october 19. Now, randomly the external HDMI monitor goes blank for 5 second until dock restart. But this fails make external webcam (connected to dockstation), and bluetooth headphones (mic at external web cam) got unconfigured, sending audio to the dock port and getting mic from it not regarding is not used, putting in a meeting without any sound. And because internet is also used via D6000 wired ethernet port, I got disconnected from VPN and RDP connections too. Release info: Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 18:00:54 2021 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 RelatedPackageVersions: linux-restricted-modules-5.10.0-1050-oem N/A linux-backports-modules-5.10.0-1050-oem N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.10.0-1050-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948343] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1948343/+attachment/5535241/+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/1948343 Title: Docking Station crash ramdomly after october 19 updates Status in linux package in Ubuntu: Confirmed Bug description: My dell D6000 dockingstation start crashing after installation of updates on october 19. Now, randomly the external HDMI monitor goes blank for 5 second until dock restart. But this fails make external webcam (connected to dockstation), and bluetooth headphones (mic at external web cam) got unconfigured, sending audio to the dock port and getting mic from it not regarding is not used, putting in a meeting without any sound. And because internet is also used via D6000 wired ethernet port, I got disconnected from VPN and RDP connections too. Release info: Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 18:00:54 2021 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 RelatedPackageVersions: linux-restricted-modules-5.10.0-1050-oem N/A linux-backports-modules-5.10.0-1050-oem N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.10.0-1050-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948343] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1948343/+attachment/5535236/+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/1948343 Title: Docking Station crash ramdomly after october 19 updates Status in linux package in Ubuntu: Confirmed Bug description: My dell D6000 dockingstation start crashing after installation of updates on october 19. Now, randomly the external HDMI monitor goes blank for 5 second until dock restart. But this fails make external webcam (connected to dockstation), and bluetooth headphones (mic at external web cam) got unconfigured, sending audio to the dock port and getting mic from it not regarding is not used, putting in a meeting without any sound. And because internet is also used via D6000 wired ethernet port, I got disconnected from VPN and RDP connections too. Release info: Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 18:00:54 2021 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 RelatedPackageVersions: linux-restricted-modules-5.10.0-1050-oem N/A linux-backports-modules-5.10.0-1050-oem N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.10.0-1050-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948343] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1948343/+attachment/5535249/+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/1948343 Title: Docking Station crash ramdomly after october 19 updates Status in linux package in Ubuntu: Confirmed Bug description: My dell D6000 dockingstation start crashing after installation of updates on october 19. Now, randomly the external HDMI monitor goes blank for 5 second until dock restart. But this fails make external webcam (connected to dockstation), and bluetooth headphones (mic at external web cam) got unconfigured, sending audio to the dock port and getting mic from it not regarding is not used, putting in a meeting without any sound. And because internet is also used via D6000 wired ethernet port, I got disconnected from VPN and RDP connections too. Release info: Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 18:00:54 2021 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 RelatedPackageVersions: linux-restricted-modules-5.10.0-1050-oem N/A linux-backports-modules-5.10.0-1050-oem N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.10.0-1050-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948343] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1948343/+attachment/5535246/+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/1948343 Title: Docking Station crash ramdomly after october 19 updates Status in linux package in Ubuntu: Confirmed Bug description: My dell D6000 dockingstation start crashing after installation of updates on october 19. Now, randomly the external HDMI monitor goes blank for 5 second until dock restart. But this fails make external webcam (connected to dockstation), and bluetooth headphones (mic at external web cam) got unconfigured, sending audio to the dock port and getting mic from it not regarding is not used, putting in a meeting without any sound. And because internet is also used via D6000 wired ethernet port, I got disconnected from VPN and RDP connections too. Release info: Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 18:00:54 2021 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 RelatedPackageVersions: linux-restricted-modules-5.10.0-1050-oem N/A linux-backports-modules-5.10.0-1050-oem N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.10.0-1050-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948343] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1948343/+attachment/5535252/+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/1948343 Title: Docking Station crash ramdomly after october 19 updates Status in linux package in Ubuntu: Confirmed Bug description: My dell D6000 dockingstation start crashing after installation of updates on october 19. Now, randomly the external HDMI monitor goes blank for 5 second until dock restart. But this fails make external webcam (connected to dockstation), and bluetooth headphones (mic at external web cam) got unconfigured, sending audio to the dock port and getting mic from it not regarding is not used, putting in a meeting without any sound. And because internet is also used via D6000 wired ethernet port, I got disconnected from VPN and RDP connections too. Release info: Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 18:00:54 2021 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 RelatedPackageVersions: linux-restricted-modules-5.10.0-1050-oem N/A linux-backports-modules-5.10.0-1050-oem N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.10.0-1050-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948343] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1948343/+attachment/5535237/+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/1948343 Title: Docking Station crash ramdomly after october 19 updates Status in linux package in Ubuntu: Confirmed Bug description: My dell D6000 dockingstation start crashing after installation of updates on october 19. Now, randomly the external HDMI monitor goes blank for 5 second until dock restart. But this fails make external webcam (connected to dockstation), and bluetooth headphones (mic at external web cam) got unconfigured, sending audio to the dock port and getting mic from it not regarding is not used, putting in a meeting without any sound. And because internet is also used via D6000 wired ethernet port, I got disconnected from VPN and RDP connections too. Release info: Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 18:00:54 2021 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 RelatedPackageVersions: linux-restricted-modules-5.10.0-1050-oem N/A linux-backports-modules-5.10.0-1050-oem N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.10.0-1050-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948343] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1948343/+attachment/5535238/+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/1948343 Title: Docking Station crash ramdomly after october 19 updates Status in linux package in Ubuntu: Confirmed Bug description: My dell D6000 dockingstation start crashing after installation of updates on october 19. Now, randomly the external HDMI monitor goes blank for 5 second until dock restart. But this fails make external webcam (connected to dockstation), and bluetooth headphones (mic at external web cam) got unconfigured, sending audio to the dock port and getting mic from it not regarding is not used, putting in a meeting without any sound. And because internet is also used via D6000 wired ethernet port, I got disconnected from VPN and RDP connections too. Release info: Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 18:00:54 2021 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 RelatedPackageVersions: linux-restricted-modules-5.10.0-1050-oem N/A linux-backports-modules-5.10.0-1050-oem N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.10.0-1050-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948343] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1948343/+attachment/5535239/+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/1948343 Title: Docking Station crash ramdomly after october 19 updates Status in linux package in Ubuntu: Confirmed Bug description: My dell D6000 dockingstation start crashing after installation of updates on october 19. Now, randomly the external HDMI monitor goes blank for 5 second until dock restart. But this fails make external webcam (connected to dockstation), and bluetooth headphones (mic at external web cam) got unconfigured, sending audio to the dock port and getting mic from it not regarding is not used, putting in a meeting without any sound. And because internet is also used via D6000 wired ethernet port, I got disconnected from VPN and RDP connections too. Release info: Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 18:00:54 2021 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 RelatedPackageVersions: linux-restricted-modules-5.10.0-1050-oem N/A linux-backports-modules-5.10.0-1050-oem N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.10.0-1050-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948343] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1948343/+attachment/5535240/+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/1948343 Title: Docking Station crash ramdomly after october 19 updates Status in linux package in Ubuntu: Confirmed Bug description: My dell D6000 dockingstation start crashing after installation of updates on october 19. Now, randomly the external HDMI monitor goes blank for 5 second until dock restart. But this fails make external webcam (connected to dockstation), and bluetooth headphones (mic at external web cam) got unconfigured, sending audio to the dock port and getting mic from it not regarding is not used, putting in a meeting without any sound. And because internet is also used via D6000 wired ethernet port, I got disconnected from VPN and RDP connections too. Release info: Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 18:00:54 2021 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 RelatedPackageVersions: linux-restricted-modules-5.10.0-1050-oem N/A linux-backports-modules-5.10.0-1050-oem N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.10.0-1050-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948343] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1948343/+attachment/5535244/+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/1948343 Title: Docking Station crash ramdomly after october 19 updates Status in linux package in Ubuntu: Confirmed Bug description: My dell D6000 dockingstation start crashing after installation of updates on october 19. Now, randomly the external HDMI monitor goes blank for 5 second until dock restart. But this fails make external webcam (connected to dockstation), and bluetooth headphones (mic at external web cam) got unconfigured, sending audio to the dock port and getting mic from it not regarding is not used, putting in a meeting without any sound. And because internet is also used via D6000 wired ethernet port, I got disconnected from VPN and RDP connections too. Release info: Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 18:00:54 2021 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (64 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 RelatedPackageVersions: linux-restricted-modules-5.10.0-1050-oem N/A linux-backports-modules-5.10.0-1050-oem N/A linux-firmware 1.187.19 Tags: focal Uname: Linux 5.10.0-1050-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
