[Kernel-packages] [Bug 2037906] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2037906/+attachment/5706604/+files/Lspci-vt.txt
--
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/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in bluez package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
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.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037906] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2037906/+attachment/5706605/+files/Lsusb.txt
--
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/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in bluez package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
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.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037906] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2037906/+attachment/5706606/+files/Lsusb-t.txt
--
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/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in bluez package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
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.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037906] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2037906/+attachment/5706607/+files/Lsusb-v.txt
--
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/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in bluez package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
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.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037906] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2037906/+attachment/5706608/+files/ProcCpuinfo.txt
--
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/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in bluez package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
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.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037906] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2037906/+attachment/5706609/+files/ProcCpuinfoMinimal.txt
--
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/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in bluez package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
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.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037906] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2037906/+attachment/5706610/+files/ProcEnviron.txt
--
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/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in bluez package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
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.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037906] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2037906/+attachment/5706611/+files/ProcInterrupts.txt
--
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/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in bluez package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
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.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037906] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2037906/+attachment/5706612/+files/ProcModules.txt
--
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/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in bluez package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
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.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037906] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2037906/+attachment/5706613/+files/UdevDb.txt
--
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/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in bluez package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
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.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037906] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2037906/+attachment/5706614/+files/acpidump.txt
--
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/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in bluez package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
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.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037906] getfacl.txt
apport information
** Attachment added: "getfacl.txt"
https://bugs.launchpad.net/bugs/2037906/+attachment/5706616/+files/getfacl.txt
--
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/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in bluez package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
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.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037906] rfkill.txt
apport information
** Attachment added: "rfkill.txt"
https://bugs.launchpad.net/bugs/2037906/+attachment/5706617/+files/rfkill.txt
--
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/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in bluez package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
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.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037906] syslog.txt
apport information
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/bugs/2037906/+attachment/5706618/+files/syslog.txt
--
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/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in bluez package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
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.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026652] Re: Suspend Broken
Thanks for filing this. I'm also seeing similar behavior (suspend appears to work, but wakes up immediately to a locked screen). I'm also on nouveau drivers. $ uname -srm Linux 6.2.0-34-generic x86_64 $ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 Also happy to provide any other info. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2026652 Title: Suspend Broken Status in linux-signed-lowlatency package in Ubuntu: New Bug description: When I go to suspend my system via the UI "Suspend" option, the system fails to suspend. Instead it looks like its going to suspend, and then wakes up but with a locked screen. When I use `pm-suspend` from the command line, it suspends the system, but does not lock the screen. I have the Settings -> Privacy -> Screen Lock -> "Lock Screen on Suspend" setting enabled. I am using the Nouveau driver, with Wayland, using GNOME 44.2. This bug only started when I switched away from using any of the NVIDIA drivers, so its probably partially Nouveau related. Switching back to the NVIDIA drivers (I tried them all) isn't an option, because they break: 1. External monitor connectivity 2. VMWare Horizon Debug info: 1. `lsb_release -rd` Description: Ubuntu 23.04 Release: 23.04 2. `uname -srm` Linux 6.2.0-1007-lowlatency x86_64 Please let me know of any other information needed to debug this. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7 ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12 Uname: Linux 6.2.0-1007-lowlatency x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 9 10:26:06 2023 InstallationDate: Installed on 2021-12-18 (567 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: linux-signed-lowlatency UpgradeStatus: Upgraded to lunar on 2023-04-26 (73 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2026652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036184] Re: Infinite systemd loop when power off the machine with multiple MD RAIDs
I've identified a bug impacting Linux kernel images 6.0, 6.1, and 6.2 on
Jammy. As I'm new to the Launchpad bugs platform, I'm seeking
clarification on the process. Will the fix be incorporated into the
upcoming Linux kernel releases for Jammy?
Additionally, I've noticed a submitted patch in the mailing list that
would fix issue for Jammy kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2036184
Title:
Infinite systemd loop when power off the machine with multiple MD
RAIDs
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[Impact]
The system with multiple MD RAIDs sometimes hangs while rebooting, that's
because of the systemd can't stop and close the MD disk.
[Fix]
This commit fixes the issue, and this issue has been introduced by
12a6caf27324 ("md: only delete entries from all_mddevs when the disk is freed")
after v6.0
https://patchwork.kernel.org/project/linux-
raid/patch/20230914152416.10819-1-mariusz.tkac...@linux.intel.com/
[Test case]
1. Reboot the system with multiple MD RAIDs at least 10 times.
2. Make sure the system can reboot successfully every time.
3. You should not see error messages like below.
[ 205.360738] systemd-shutdown[1]: Stopping MD devices.
[ 205.366384] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs
[ 205.373327] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus
[ 205.380427] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class
[ 205.388257] systemd-shutdown[1]: Stopping MD /dev/md127 (9:127).
[ 205.394880] systemd-shutdown[1]: Failed to sync MD block device /dev/md127,
ignoring: Input/output error
[ 205.404975] md: md127 stopped.
[ 205.470491] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126).
[ 205.770179] md: md126: resync interrupted.
[ 205.776258] md126: detected capacity change from 1900396544 to 0
[ 205.783349] md: md126 stopped.
[ 205.862258] systemd-shutdown[1]: Stopping MD /dev/md125 (9:125).
[ 205.862435] md: md126 stopped.
[ 205.868376] systemd-shutdown[1]: Failed to sync MD block device /dev/md125,
ignoring: Input/output error
[ 205.872845] block device autoloading is deprecated and will be removed.
[ 205.880955] md: md125 stopped.
[ 205.934349] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:7).
[ 205.947707] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or
resource busy
[ 205.957004] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:6).
[ 205.964177] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or
resource busy
[ 205.973155] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124).
[ 205.979789] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or
resource busy
[ 205.988475] systemd-shutdown[1]: Not all MD devices stopped, 4 left.
[Where problems could occur]
It fixes the data race issue, should not introduce any regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2036184/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853306] Re: [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part
** Tags removed: verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux-aws verification-needed-jammy-linux-xilinx-zynqmp ** Tags added: verification-done-focal-linux-aws-5.15 verification-done-jammy-linux-aws verification-done-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853306 Title: [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [ Impact ] * Currently the PCI passthrough implementation for s390x is based on intercepting PCI I/O instructions, which leads to a reduced I/O performance compared to the execution of PCI instructions directly in LPAR. * Hence users may face I/O bottlenecks when using PCI devices in passthrough mode based on the current implementation. * For avoiding this and to improve performance, the interpretive execution of the PCI store and PCI load instructions get enabled. * A further improvement is achieved by enabling the Adapter-Event-Notification Interpretation (AENI). * Since LTS releases are the main focus for stable and long running KVM workloads, it is highly desired to get this backported to the jammy kernel (and because the next LTS is still some time away). [ Test Plan ] * Hardware used: z14 or greater LPAR, PCI-attached devices (RoCE VFs, ISM devices, NVMe drive) * Setup: Both the kernel and QEMU features are needed for the feature to function (an upstream QEMU can be used to verify the kernel early), and the facility is only avaialble on z14 or newer. When any of those pieces is missing, the interpretation facility will not be used. When both the kernel and QEMU features are included in their respective packages, and running in an LPAR on a z14 or newer machine, this feature will be enabled automatically. Existing supported devices should behave as before with no changes required by an end-user (e.g. no changes to libvirt domain definitions) -- but will now make use of the interpretation facility. Additionally, ISM devices will now be eligible for vfio-pci passthrough (where before QEMU would exit on error if attempting to provide an ISM device for vfio-pci passthrough, preventing the guest from starting) * Testing will include the following scenarios, repeated each for RoCE, ISM and NVMe: 1) Testing of basic device passthrough (create a VM with a vfio-pci device as part of the libvirt domain definition, passing through a RoCE VF, an ISM device, or an NVMe drive. Verify that the device is available in the guest and functioning) 2) Testing of device hotplug/unplug (create a VM with a vfio-pci device, virsh detach-device to remove the device from the running guest, verify the device is removed from the guest, then virsh attach-device to hotplug the device to the guest again, verify the device functions in the guest) 3) Host power off testing: Power off the device from the host, verify that the device is unplugged from the guest as part of the poweroff 4) Guest power off testing: Power off the device from within the guest, verify that the device is unusuable in the guest, power the device back on within the guest and verify that the device is once again usable. 5) Guest reboot testing: (create a VM with a vfio-pci device, verify the device is in working condition, reboot the guest, verify that the device is still usable after reboot) Testing will include the following scenarios specifically for ISM devices: 1) Testing of SMC-D v1 fallback: Using 2 ISM devices on the same VCHID that share a PNETID, create 2 guests and pass one ISM device via vfio-pci device to each guest. Establish TCP connectivity between the 2 guests using the libvirt default network, and then use smc_run (https://manpages.ubuntu.com/manpages/jammy/man8/smc_run.8.html) to run an iperf workload between the 2 guests (will include both short workloads and longer-running workloads). Verify that SMC-D transfer was used between the guests instead of TCP via 'smcd stats' (https://manpages.ubuntu.com/manpages/jammy/man8/smcd.8.html) 2) Testing of SMC-D v2: Same as above, but using 2 ISM devices on the same VCHID that have no PNETID specified Testing will include the following scenarios specifically for RoCE devices: 1) Ping testing: Using 2 RoCE VFs that share a common network,
[Kernel-packages] [Bug 2038105] Re: Intel Graphic driver crash ( Mosaic mode )
@Timo , we still don't have anyway to apport collect via CLI ? We don't want to bother the client by messing is graphical session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038105 Title: Intel Graphic driver crash ( Mosaic mode ) Status in linux package in Ubuntu: Incomplete Bug description: With pentium G7400 ( UHD Intel 710 ) several times per day the screen is corrupted , tested on several screen , the client has to reboot the machine ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Oct 2 15:14:06 2023 InstallationDate: Installed on 2023-08-10 (53 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036968] Re: Mantic minimized/minimal cloud images do not receive IP address during provisioning; systemd regression with wait-online
@xnox I have successfully verified that -proposed arm64 kernel `6.5.0-7-generic` results in successful network configuration when tested using qemu on an amd64 host. See https://people.canonical.com/~philroche/20231003-mantic-minimal- proposed-kernel/ for cloud-init logs, some debug output and test 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/2036968 Title: Mantic minimized/minimal cloud images do not receive IP address during provisioning; systemd regression with wait-online Status in cloud-images: New Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Triaged Bug description: Following a recent change from linux-kvm kernel to linux-generic kernel in the mantic minimized images, there is a reproducable bug where a guest VM does not have an IP address assigned as part of cloud-init provisioning. This is easiest to reproduce when emulating arm64 on amd64 host. The bug is a race condition, so there could exist fast enough virtualisation on fast enough hardware where this bug is not present but in all my testing I have been able to reproduce. The latest mantic minimized images from http://cloud- images.ubuntu.com/minimal/daily/mantic/ have force initrdless boot and no initrd to fallback to. This but is not present in the non minimized/base images @ http://cloud-images.ubuntu.com/mantic/ as these boot with initrd with the required drivers present for virtio-net. Reproducer ``` wget -O "launch-qcow2-image-qemu-arm64.sh" https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/launch-qcow2-image-qemu-arm64.sh chmod +x ./launch-qcow2-image-qemu-arm64.sh wget https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/livecd.ubuntu-cpc.img ./launch-qcow2-image-qemu-arm64.sh --password passw0rd --image ./livecd.ubuntu-cpc.img ``` You will then be able to log in with user `ubuntu` and password `passw0rd`. You can run `ip a` and see that there is a network interface present (separate to `lo`) but no IP address has been assigned. ``` ubuntu@cloudimg:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff ``` This is because when cloud-init is trying to configure network interfaces it doesn't find any so it doesn't configure any. But by the time boot is complete the network interface is present but cloud-init provisioning has already completed. You can verify this by running `sudo cloud-init clean && sudo cloud- init init` You can then see a successfully configured network interface ``` ubuntu@cloudimg:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic enp0s1 valid_lft 86391sec preferred_lft 86391sec inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr noprefixroute valid_lft 86393sec preferred_lft 14393sec inet6 fe80::5054:ff:fe12:3456/64 scope link valid_lft forever preferred_lft forever ``` The bug is also reproducible with amd64 guest on adm64 host on older/slower hardware. The suggested fixes while debugging this issue are: * to include `virtio-net` as a built-in in the mantic generic kernel * understand what needs to change in cloud-init so that it can react to late additions of network interfaces I will file a separate bug against cloud-init to address the race condition on emulated guest/older hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035181] Re: Regression for ubuntu_bpf test build on Jammy 5.15.0-85.95
The same commit which broke Jammy now is applied for the 2023.10.02
cycle for Lunar.
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Lunar)
Status: New => Confirmed
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035181
Title:
Regression for ubuntu_bpf test build on Jammy 5.15.0-85.95
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Confirmed
Bug description:
[Impact]
Commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work
with CO-RE") from stable update breaks the ubuntu_bpf test build and
cause net:udpgro_bench.sh, net:udpgro.sh, net:veth.sh in
ubuntu_kernel_selftests stopped working, as they require bpf selftest
to be built first.
The following is extracted from the commit message:
The problem is the new offsetof() does not play nice with static asserts.
Given that the context is a static assert (and CO-RE relocation is not
needed at compile time), offsetof() usage can be replaced by restoring
the original offsetof() definition as __builtin_offsetof().
[Test Plan]
Build bpf selftest in tools/testing/selftests with the following command:
make headers; make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= \
clean all KDIR=/usr/src/linux-headers-5.15.0-85-generic/
The build can finish successfully with patched kernel source code.
[Where problems could occur]
Fix limited to testing tool, if this fix is incorrect the bpf selftest
build will remain broken.
== Original bug report ==
Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04
This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84
is a security cycle, in which the ubuntu_bpf test was not triggered
there)
Test build failed with:
CLNG-BPF [test_maps] test_btf_map_in_map.o
CLNG-BPF [test_maps] test_btf_newkv.o
CLNG-BPF [test_maps] test_btf_nokv.o
CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o
CLNG-BPF [test_maps] test_cgroup_link.o
CLNG-BPF [test_maps] test_check_mtu.o
CLNG-BPF [test_maps] test_cls_redirect.o
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from
latest version at 'include/uapi/linux/bpf.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs
from latest version at 'include/uapi/linux/netlink.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs
from latest version at 'include/uapi/linux/if_link.h'
progs/test_cls_redirect.c:90:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv4.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
progs/test_cls_redirect.c:95:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv6.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
2 errors generated.
make[1]: *** [Makefile:470:
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_cls_redirect.o]
Error 1
make: *** [Makefile:171: all] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2035181/+s
[Kernel-packages] [Bug 2033732] Re: SMB 1 broken in kernel linux-generic-hwe-22.04 (version 6.2.0-31)
This problem seems fixed now, or at least I am no longer having problems with this Linux Kernel version: 6.2.0-34-generic #34~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 13:12:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux Can somebody else confirm this? I don't know yet how to check whether that patch mentioned above is included in the latest Ubuntu Kernel version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2033732 Title: SMB 1 broken in kernel linux-generic-hwe-22.04 (version 6.2.0-31) Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: I was running Ubuntu 22.04.3 on kernel version 5.15.0-82-generic, and I installed package linux-generic-hwe-22.04 in order to upgrade to kernel version 6.2.0-31. That upgrade broke the SMB version 1 protocol. I know that it is an old, deprecated protocol, but I still have to access some legacy systems and devices in a local network. This breakage has been discussed on the Internet. It is a Linux kernel regression. This is the commit that fixes it. It is a very small change: 2f6f19c7aaad "cifs: fix regression in very old smb1 mounts" https://github.com/torvalds/linux/commit/2f6f19c7aaad5005dc75298a413eb0243c5d312d I am no Linux kernel expert. Could you please backport that fix to the kernel versions that linux-generic-hwe-22.04 installs? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2033732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035181] Re: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
** Summary changed:
- Regression for ubuntu_bpf test build on Jammy 5.15.0-85.95
+ Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035181
Title:
Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Confirmed
Bug description:
[Impact]
Commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work
with CO-RE") from stable update breaks the ubuntu_bpf test build and
cause net:udpgro_bench.sh, net:udpgro.sh, net:veth.sh in
ubuntu_kernel_selftests stopped working, as they require bpf selftest
to be built first.
The following is extracted from the commit message:
The problem is the new offsetof() does not play nice with static asserts.
Given that the context is a static assert (and CO-RE relocation is not
needed at compile time), offsetof() usage can be replaced by restoring
the original offsetof() definition as __builtin_offsetof().
[Test Plan]
Build bpf selftest in tools/testing/selftests with the following command:
make headers; make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= \
clean all KDIR=/usr/src/linux-headers-5.15.0-85-generic/
The build can finish successfully with patched kernel source code.
[Where problems could occur]
Fix limited to testing tool, if this fix is incorrect the bpf selftest
build will remain broken.
== Original bug report ==
Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04
This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84
is a security cycle, in which the ubuntu_bpf test was not triggered
there)
Test build failed with:
CLNG-BPF [test_maps] test_btf_map_in_map.o
CLNG-BPF [test_maps] test_btf_newkv.o
CLNG-BPF [test_maps] test_btf_nokv.o
CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o
CLNG-BPF [test_maps] test_cgroup_link.o
CLNG-BPF [test_maps] test_check_mtu.o
CLNG-BPF [test_maps] test_cls_redirect.o
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from
latest version at 'include/uapi/linux/bpf.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs
from latest version at 'include/uapi/linux/netlink.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs
from latest version at 'include/uapi/linux/if_link.h'
progs/test_cls_redirect.c:90:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv4.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
progs/test_cls_redirect.c:95:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv6.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
2 errors generated.
make[1]: *** [Makefile:470:
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_cls_redirect.o]
Error 1
make: *** [Makefile:171: all] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2035181/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://la
[Kernel-packages] [Bug 2036968] Re: Mantic minimized/minimal cloud images do not receive IP address during provisioning; systemd regression with wait-online
I have also successfully verified that -proposed amd64 kernel `6.5.0-7-generic` results in successful network configuration when tested using qemu on an amd64 host with older hardware (ThinkPad T460 with 6th gen intel i5 which is the same hardware which we were able to reproduce the issue on previously). See https://people.canonical.com/~philroche/20231003-mantic-minimal- proposed-kernel/amd64/ for cloud-init logs, some debug output and test 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/2036968 Title: Mantic minimized/minimal cloud images do not receive IP address during provisioning; systemd regression with wait-online Status in cloud-images: New Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Triaged Bug description: Following a recent change from linux-kvm kernel to linux-generic kernel in the mantic minimized images, there is a reproducable bug where a guest VM does not have an IP address assigned as part of cloud-init provisioning. This is easiest to reproduce when emulating arm64 on amd64 host. The bug is a race condition, so there could exist fast enough virtualisation on fast enough hardware where this bug is not present but in all my testing I have been able to reproduce. The latest mantic minimized images from http://cloud- images.ubuntu.com/minimal/daily/mantic/ have force initrdless boot and no initrd to fallback to. This but is not present in the non minimized/base images @ http://cloud-images.ubuntu.com/mantic/ as these boot with initrd with the required drivers present for virtio-net. Reproducer ``` wget -O "launch-qcow2-image-qemu-arm64.sh" https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/launch-qcow2-image-qemu-arm64.sh chmod +x ./launch-qcow2-image-qemu-arm64.sh wget https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/livecd.ubuntu-cpc.img ./launch-qcow2-image-qemu-arm64.sh --password passw0rd --image ./livecd.ubuntu-cpc.img ``` You will then be able to log in with user `ubuntu` and password `passw0rd`. You can run `ip a` and see that there is a network interface present (separate to `lo`) but no IP address has been assigned. ``` ubuntu@cloudimg:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff ``` This is because when cloud-init is trying to configure network interfaces it doesn't find any so it doesn't configure any. But by the time boot is complete the network interface is present but cloud-init provisioning has already completed. You can verify this by running `sudo cloud-init clean && sudo cloud- init init` You can then see a successfully configured network interface ``` ubuntu@cloudimg:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic enp0s1 valid_lft 86391sec preferred_lft 86391sec inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr noprefixroute valid_lft 86393sec preferred_lft 14393sec inet6 fe80::5054:ff:fe12:3456/64 scope link valid_lft forever preferred_lft forever ``` The bug is also reproducible with amd64 guest on adm64 host on older/slower hardware. The suggested fixes while debugging this issue are: * to include `virtio-net` as a built-in in the mantic generic kernel * understand what needs to change in cloud-init so that it can react to late additions of network interfaces I will file a separate bug against cloud-init to address the race condition on emulated guest/older hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035116] Re: allow io_uring to be disabled in runtime
** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2035116 Title: allow io_uring to be disabled in runtime Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Triaged Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] io_uring has been an important attack vector in the recent years in local privilege escalation attacks. Allowing admins that don't use io_uring to disable it in their systems allows them to reduce their attack surface. [Test case] sysctl -w kernel.io_uring_disabled=1 then try to use io_uring from an unprivileged user, then try it with privileges (CAP_SYS_ADMIN) Actually also tried setting kernel.io_uring_disabled=2 and checking that neither (privileged or unprivileged worked). Then testing setting it back to 0. Then tested with io_uring_disabled set to 1 and io_uring_group=1000 and that it worked for group 1000, then set it to 1001 and verified that it didn't work anymore for group 1000. [Potential regression] Uses can be denied from using io_uring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036377] Re: Fix RCU warning on AMD laptops
** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2036377 Title: Fix RCU warning on AMD laptops Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Scary kernel splat about RCU can be observed everytime laptop resumes from suspend. [Fix] Use non-atomic notifier for power supply change to relax the constraint. [Test] Once the fix is applied, no more RCU warning can be found after several suspend/resume cycle. [Where problems could occur] Essentially no regression potential. Atomic notifier should be used by core kernel, and things like power supply doesn't need to be atomic anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2036377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: linux-kvm (Ubuntu Mantic) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2019040 Title: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images Status in linux package in Ubuntu: Fix Committed Status in linux-kvm package in Ubuntu: Invalid Status in linux-meta-azure package in Ubuntu: Invalid Status in linux-meta-kvm package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-kvm source package in Jammy: Fix Released Status in linux-meta-azure source package in Jammy: Invalid Status in linux-meta-kvm source package in Jammy: New Status in linux source package in Kinetic: Fix Committed Status in linux-kvm source package in Kinetic: In Progress Status in linux-meta-azure source package in Kinetic: Invalid Status in linux-meta-kvm source package in Kinetic: New Status in linux source package in Lunar: Fix Released Status in linux-kvm source package in Lunar: Fix Released Status in linux-meta-azure source package in Lunar: New Status in linux-meta-kvm source package in Lunar: New Status in linux source package in Mantic: Fix Committed Status in linux-kvm source package in Mantic: Invalid Status in linux-meta-azure source package in Mantic: Invalid Status in linux-meta-kvm source package in Mantic: Invalid Bug description: SRU Justification [Impact] The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. [Fix] Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_INTEGRITY_MACHINE_KEYRING CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring implementation is patched to skip the check enabled by this kconfig) (The latter two are needed to ensure that MoK keys can be used to verify dm-verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. To verify whether this works, add a certificate to MOK, boot and check the content of the secondary keyring. The machine keyring should show up under it, and it should show the certificates loaded in MOK. E.g.: $ sudo keyctl show %:.secondary_trusted_keys Keyring 159454604 ---lswrv 0 0 keyring: .secondary_trusted_keys 88754641 ---lswrv 0 0 \_ keyring: .builtin_trusted_keys 889010778 ---lswrv 0 0 | \_ asymmetric: Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1 799434660 ---lswrv 0 0 | \_ asymmetric: Debian Secure Boot Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f 541326986 ---lswrv 0 0 \_ keyring: .machine 188508854 ---lswrv 0 0 \_ asymmetric: Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1 475039424 ---lswrv 0 0 \_ asymmetric: sb-bluca: Secure Boot Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479 [Regression Potential] MOK keys may not be correctly read. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
** Changed in: mutter (Ubuntu Mantic) Milestone: None => ubuntu-23.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: In Progress Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
Thanks Mario! I checked, and I have the newest mesa: ``` $ apt search mesa-vdpau Sorting... Done Full Text Search... Done mesa-vdpau-drivers/mantic,now 23.2.1-1ubuntu2 amd64 [installed,automatic] Mesa VDPAU video acceleration drivers ``` Funny thing is that the bug is no longer reproducible - everything is working properly, yay! Could it be that mesa was upgraded a couple of days ago, resolving the issue? Anyways, the issue looks to be fixed now. Thanks again! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037641 Title: amdgpu: [gfxhub0] no-retry page fault Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. The setup: the machine is connected to an external monitor via USB-C. Running kernel 6.5 on Ubuntu 23.10. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583]
[Kernel-packages] [Bug 1628204] Re: linux: 4.4.0-41.61 -proposed tracker
The information you provided appears to be related to a specific version of the Linux kernel in the Ubuntu operating system's "proposed" repository. The "proposed" repository in Ubuntu is where packages are initially placed for testing before they are moved to the stable release you can visit to the https://downloadertwitter.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
I'd say that's very likely. That mesa upgrade just landed in the archive a few days ago and the trace you reported looks more like how a mesa bug manifests. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037641 Title: amdgpu: [gfxhub0] no-retry page fault Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Bug description: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. The setup: the machine is connected to an external monitor via USB-C. Running kernel 6.5 on Ubuntu 23.10. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206588] amdgpu :06:00.0: amdgpu:
[Kernel-packages] [Bug 1800562] Re: Remove obsolete "nousb" option in kdump command-line for newer kernels
** Tags removed: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Remove obsolete "nousb" option in kdump command-line for newer kernels
Status in makedumpfile package in Ubuntu:
Confirmed
Status in kdump-tools source package in Xenial:
New
Status in makedumpfile source package in Xenial:
Won't Fix
Status in kdump-tools source package in Bionic:
New
Status in makedumpfile source package in Bionic:
Confirmed
Status in kdump-tools source package in Eoan:
New
Status in makedumpfile source package in Eoan:
Won't Fix
Status in kdump-tools source package in Focal:
New
Status in makedumpfile source package in Focal:
Confirmed
Status in kdump-tools source package in Groovy:
New
Status in makedumpfile source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Kdump command-line include an obsolete "nousb" parameter by default, which
can cause a misimpression: users will think they are not booting with USB, but
they are.
* Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case
the subsystem is built-in). This was changed by commit 097a9ea0e48
("usb: make "nousb" a clear module parameter").
* USB may be pretty essential in case for example kdump users need to
decrypt a disk under LUKS, and there's only an USB keyboard connected
to the system. Given the option is innocuous since Bionic, we should
just drop it to prevent confusion.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'nousb' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is extremely low, since the "nousb" parameter
is not used since Bionic although is there. Any bugs we would have by
changing this are still valid by not removing the option - the
semantics with or without "nosub" is the same since from Bionic.
NOTICE we won't change Xenial, it can use kernel 4.4 which indeed
disables USB by taking the "nousb" parameter.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037789] Re: I must plug an external keyboard+mouse on Lenovo V15 Gen 4
This is what I get after last update (attached file) ** Attachment added: "devices" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2037789/+attachment/5706725/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2037789 Title: I must plug an external keyboard+mouse on Lenovo V15 Gen 4 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Hello everyone, I'm Jean-Marie, my journey with linux has just started. So I can't use my touchpad and keyboard on this new Lenovo V15 Gen 4 "cat /proc/bus/input/devices" doesn't show "I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio2/input0 S: Sysfs=/devices/platform/i8042/serio2/input/input8 U: Uniq= H: Handlers=mouse2 event8 B: EV=b B: KEY=420 0 7 0 0 0 0 0 0 0 0 B: ABS=1103" but instead of it I get "I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:08/LNXVIDEO:00/input/input3 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=046d Product=c077 Version=0111 N: Name="Logitech USB Optical Mouse" P: Phys=usb-:04:00.4-2/input0 S: Sysfs=/devices/pci:00/:00:08.1/:04:00.4/usb3/3-2/3-2:1.0/0003:046D:C077.0003/input/input7 U: Uniq= H: Handlers=mouse0 event6 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:14.3/PNP0C09:00/VPC2004:00/input/input8 U: Uniq= H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=13 B: KEY=8000 1000 0 81000800100c03 44300400 0 2 B: MSC=10 I: Bus=0003 Vendor=5986 Product=2160 Version=5806 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:05:00.0-1/button S: Sysfs=/devices/pci:00/:00:08.3/:05:00.0/usb5/5-1/5-1:1.0/input/input9 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.1/sound/card0/input10 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.1/sound/card0/input11 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.6/sound/card1/input12 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.6/sound/card1/input13 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0003 Vendor=04ca Product=007d Version=0111 N: Name="Liteon Technology Corp. USB wired keyboard" P: Phys=usb-:04:00.4-1/input0 S: Sysfs=/devices/pci:00/:00:08.1/:04:00.4/usb3/3-1/3-1:1.0/0003:04CA:007D.0004/input/input14 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=04ca Product=007d Version=0111 N: Name="Liteon Technology Corp. USB wired keyboard Consumer Control" P: Phys=usb-:04:00.4-1/input1 S: Sysfs=/devices/pci:00/:00:08.1/:04:00.4/usb3/3-1/3-1:1.1/0003:04CA:007D.0005/input/input15 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=1f B: KEY=33eff 0 0 48317aff32d bfd6 1 130c730b17c000 267bfad9415fed 9e16804400 1002 B: REL=1040 B: ABS=1 B: MSC=10 I: Bus=0003 Vendor=04ca Product=007d Version=0111 N: Name="Liteon Technology Corp. USB wired keyboard System Control" P: Phys=usb-:04:00.4-1/input1 S: Sysfs=/devices/pci:00/:00:08.1/:04:00.4/usb3/3-1/3-1:1.1/0003:04CA:007D.0005/input/i
[Kernel-packages] [Bug 2030238] Re: my trackpad not working after installing ubuntu not even detecting
Same issue here even after today's update ** Attachment added: "devices" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2030238/+attachment/5706726/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2030238 Title: my trackpad not working after installing ubuntu not even detecting Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: my elen trackpad is not working after installing ubuntu 22.02.2 lts not even detecting it from the start so how could someone use system if trackpad not working please fix this bug as soon as possible ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 5 03:49:25 2023 SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2030238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037936] Re: Exclude DRM drivers from linux-modules
** Also affects: linux-raspi (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: linux-raspi (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037936 Title: Exclude DRM drivers from linux-modules Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi source package in Jammy: Fix Committed Status in linux-raspi source package in Lunar: Fix Committed Status in linux-raspi source package in Mantic: Fix Released Bug description: [Impact] DRM modules and their firmwares end up in the initrd and blow up its size. Most of them, especially nouveau and radeon, are unlikely to be used on a Pi, so move the modules to linux-modules-extra. [Fix] Moeve DRM modules to linux-modules-extra. [Test Case] Install new kernel and inspect initrd. Verify display still comes up. [Regression Potential] Blank display if a module is moved that is used for the primary display. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2037936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037938] Re: Include USB drivers in linux-modules
** Also affects: linux-raspi (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: linux-raspi (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037938 Title: Include USB drivers in linux-modules Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi source package in Jammy: Fix Committed Status in linux-raspi source package in Lunar: Fix Committed Status in linux-raspi source package in Mantic: Fix Released Bug description: [Impact] UC22 users are using wifi dongles and drivers are missing in the pi- kernel snap. I.e., Some useful USB drivers (specifically for USB wifi dongles) are missing in linux-modules, so include (almost) all USB drivers in linux-modules. [Fix] They're small enough, so include most USB drivers in linux-modules. [Test Case] Install kernel and inspect installed modules. [Regression Potential] More modules that might get loaded -> kernel crashes, stack traces, hangs, ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2037938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037398] Re: kexec enable to load/kdump zstd compressed zimg
-6 kernel is respun, migration of -7 or higher is good ** Tags removed: block-proposed-mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2037398 Title: kexec enable to load/kdump zstd compressed zimg Status in kdump-tools package in Ubuntu: Invalid Status in kexec-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Triaged Bug description: While testing the 6.5.0-6-generic proposed arm64 generic kernel I encountered issues being able to use kdump. After enabling -proposed and installing the -proposed 6.5.0-6 kernel and rebooting I encountered the following: `kdump-config show` shows `current state:Not ready to kdump` and looking at the status of the kdump-tools services I see `Cannot determine the file type of /var/lib/kdump/vmlinuz` Full output: ``` ubuntu@cloudimg:~$ sudo kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.5.0-6-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-6.5.0-6-generic current state:Not ready to kdump kexec command: no kexec command recorded ubuntu@cloudimg:~$ sudo service kdump-tools status ● kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; preset: enabled) Active: active (exited) since Tue 2023-09-26 09:21:44 UTC; 5min ago Process: 515 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/SUCCESS) Main PID: 515 (code=exited, status=0/SUCCESS) CPU: 4min 21.329s Sep 26 09:16:14 cloudimg systemd[1]: Starting kdump-tools.service - Kernel crash dump capture service... Sep 26 09:16:24 cloudimg kdump-tools[515]: Starting kdump-tools: Sep 26 09:16:24 cloudimg kdump-tools[537]: * Creating symlink /var/lib/kdump/vmlinuz Sep 26 09:16:32 cloudimg kdump-tools[580]: kdump-tools: Generating /var/lib/kdump/initrd.img-6.5.0-6-generic Sep 26 09:21:42 cloudimg kdump-tools[537]: * Creating symlink /var/lib/kdump/initrd.img Sep 26 09:21:43 cloudimg kdump-tools[5538]: Cannot determine the file type of /var/lib/kdump/vmlinuz Sep 26 09:21:44 cloudimg kdump-tools[537]: * failed to load kdump kernel Sep 26 09:21:44 cloudimg kdump-tools[5539]: failed to load kdump kernel Sep 26 09:21:44 cloudimg systemd[1]: Finished kdump-tools.service - Kernel crash dump capture service. ubuntu@cloudimg:~$ ls -al /var/lib/kdump/vmlinuz lrwxrwxrwx 1 root root 29 Sep 26 09:16 /var/lib/kdump/vmlinuz -> /boot/vmlinuz-6.5.0-6-generic ubuntu@cloudimg:~$ file /var/lib/kdump/vmlinuz /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.5.0-6-generic ubuntu@cloudimg:~$ sudo file /boot/vmlinuz-6.5.0-6-generic /boot/vmlinuz-6.5.0-6-generic: PE32+ executable (EFI application) Aarch64 (stripped to external PDB), for MS Windows, 2 sections ``` The reboot with 6.5.0-6 was successful and the reboot after linux-crashdump install was successful too. I used https://ubuntu.com/server/docs/kernel-crash-dump guide for installing linux-crashdump and attempting to trigger a dump. I used arm64 qcow cloud image from http://cloud- images.ubuntu.com/mantic/20230925/mantic-server-cloudimg-arm64.img to test the above emulated on amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2037398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025054] Re: snap-kernel-uc22 lacks atheros firmware
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025054 Title: snap-kernel-uc22 lacks atheros firmware Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Summary] The Atheros firmware files aren't available in the snap-kernel-uc22 snap, used in Ubuntu Core Desktop, so the Bluetooth module in Asus Zenbook UX21-e (and probably in a lot more devices) doesn't work. [Steps to reproduce] Boot, from a power-down state, a device with an Atheros-based Bluetooth module, into Ubuntu Core Desktop, open a root terminal and type bluetoothctl devices It returns the error 'No default controller available', because the Bluetooth module firmware wasn't loaded. Now, from a power-down state, boot into an Ubuntu live session (for example, from an USB pendrive), and when the desktop appears, reboot the computer (without powering it down) into Ubuntu Core Desktop and type again in a root terminal bluetoothctl devices This time there is no error, because the Bluetooth device firmware was already loaded in the Ubuntu live session. [Expected result] The call to `bluetoothctl devices` should not return any error. [Actual result] The call to `bluetoothctl devices` returns the 'No default controller available' error. [Failure rate] 3/3 [Stage] Patch available to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038437] [NEW] mantic:linux ubuntu_qrt_kernel_security.KernelSecurityTest.test_082_stack_guard_kernel: Could not find a suitable kernel module to test
You have been subscribed to a public bug: Running the ubuntu_qrt_kernel_security suite as part of the linux (selftest) suite produces the following error: stdout: Running test: './test-kernel-security.py' distro: 'Ubuntu 23.10' kernel: '6.5.0-7.7 (Ubuntu 6.5.0-7.7-generic 6.5.3)' arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu') stderr: test_082_stack_guard_kernel (__main__.KernelSecurityTest.test_082_stack_guard_kernel) Kernel stack guard ... FAIL == FAIL: test_082_stack_guard_kernel (__main__.KernelSecurityTest.test_082_stack_guard_kernel) Kernel stack guard -- Traceback (most recent call last): File "/tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 758, in test_082_stack_guard_kernel self.assertTrue(module, 'Could not find a suitable kernel module to test') AssertionError: '' is not true : Could not find a suitable kernel module to test There is no clear indication which module(s) are attempted but probably those got renamed or this is due to compressing the modules resulting in different filename extensions. ** Affects: linux (Ubuntu) Importance: Medium Status: Triaged ** Tags: kernel-adt-failure -- mantic:linux ubuntu_qrt_kernel_security.KernelSecurityTest.test_082_stack_guard_kernel: Could not find a suitable kernel module to test https://bugs.launchpad.net/bugs/2038437 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025054] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2025054 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025054 Title: snap-kernel-uc22 lacks atheros firmware Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Summary] The Atheros firmware files aren't available in the snap-kernel-uc22 snap, used in Ubuntu Core Desktop, so the Bluetooth module in Asus Zenbook UX21-e (and probably in a lot more devices) doesn't work. [Steps to reproduce] Boot, from a power-down state, a device with an Atheros-based Bluetooth module, into Ubuntu Core Desktop, open a root terminal and type bluetoothctl devices It returns the error 'No default controller available', because the Bluetooth module firmware wasn't loaded. Now, from a power-down state, boot into an Ubuntu live session (for example, from an USB pendrive), and when the desktop appears, reboot the computer (without powering it down) into Ubuntu Core Desktop and type again in a root terminal bluetoothctl devices This time there is no error, because the Bluetooth device firmware was already loaded in the Ubuntu live session. [Expected result] The call to `bluetoothctl devices` should not return any error. [Actual result] The call to `bluetoothctl devices` returns the 'No default controller available' error. [Failure rate] 3/3 [Stage] Patch available to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038437] [NEW] mantic:linux ubuntu_qrt_kernel_security.KernelSecurityTest.test_082_stack_guard_kernel: Could not find a suitable kernel module to test
Public bug reported: Running the ubuntu_qrt_kernel_security suite as part of the linux (selftest) suite produces the following error: stdout: Running test: './test-kernel-security.py' distro: 'Ubuntu 23.10' kernel: '6.5.0-7.7 (Ubuntu 6.5.0-7.7-generic 6.5.3)' arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu') stderr: test_082_stack_guard_kernel (__main__.KernelSecurityTest.test_082_stack_guard_kernel) Kernel stack guard ... FAIL == FAIL: test_082_stack_guard_kernel (__main__.KernelSecurityTest.test_082_stack_guard_kernel) Kernel stack guard -- Traceback (most recent call last): File "/tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 758, in test_082_stack_guard_kernel self.assertTrue(module, 'Could not find a suitable kernel module to test') AssertionError: '' is not true : Could not find a suitable kernel module to test There is no clear indication which module(s) are attempted but probably those got renamed or this is due to compressing the modules resulting in different filename extensions. ** Affects: linux (Ubuntu) Importance: Medium Status: Triaged ** Affects: linux (Ubuntu Mantic) Importance: Medium Status: Triaged ** Tags: kernel-adt-failure ** Package changed: ubuntu => linux (Ubuntu) ** Also affects: linux (Ubuntu Mantic) Importance: Medium Status: Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038437 Title: mantic:linux ubuntu_qrt_kernel_security.KernelSecurityTest.test_082_stack_guard_kernel: Could not find a suitable kernel module to test Status in linux package in Ubuntu: Triaged Status in linux source package in Mantic: Triaged Bug description: Running the ubuntu_qrt_kernel_security suite as part of the linux (selftest) suite produces the following error: stdout: Running test: './test-kernel-security.py' distro: 'Ubuntu 23.10' kernel: '6.5.0-7.7 (Ubuntu 6.5.0-7.7-generic 6.5.3)' arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu') stderr: test_082_stack_guard_kernel (__main__.KernelSecurityTest.test_082_stack_guard_kernel) Kernel stack guard ... FAIL == FAIL: test_082_stack_guard_kernel (__main__.KernelSecurityTest.test_082_stack_guard_kernel) Kernel stack guard -- Traceback (most recent call last): File "/tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 758, in test_082_stack_guard_kernel self.assertTrue(module, 'Could not find a suitable kernel module to test') AssertionError: '' is not true : Could not find a suitable kernel module to test There is no clear indication which module(s) are attempted but probably those got renamed or this is due to compressing the modules resulting in different filename extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038443] [NEW] mantic:linux: ubuntu_qrt_apparmor: ApparmorTestsuites.test_regression_testsuiteattach_disconnected.
Public bug reported: This might be apparmor, the test case, kernel or anything in between: 7720s running attach_disconnected 7720s Fatal Error (unix_fd_server): Unable to run test sub-executable ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: apparmor (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Mantic) Importance: Medium Status: Confirmed ** Tags: kernel-adt-failure ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Medium Status: 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/2038443 Title: mantic:linux: ubuntu_qrt_apparmor: ApparmorTestsuites.test_regression_testsuiteattach_disconnected. Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in apparmor source package in Mantic: New Status in linux source package in Mantic: Confirmed Bug description: This might be apparmor, the test case, kernel or anything in between: 7720s running attach_disconnected 7720s Fatal Error (unix_fd_server): Unable to run test sub-executable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2038443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038440] [NEW] mantic:linux: ubuntu_qrt_kernel_security: KernelSecurityConfigTest.test_290_config_hardened_usercopy skipped
Public bug reported: 6395s 11:42:55 DEBUG| Running 'python3 ./test-kernel-security.py -v KernelSecurityConfigTest.test_290_config_hardened_usercopy' 6395s 11:42:55 DEBUG| [stdout] Running test: './test-kernel-security.py' distro: 'Ubuntu 23.10' kernel: '6.5.0-7.7 (Ubuntu 6.5.0-7.7-generic 6.5.3)' arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu') 6395s 11:42:55 ERROR| [stderr] test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest.test_290_config_hardened_usercopy) 6395s 11:42:55 ERROR| [stderr] Ensure CONFIG_HARDENED_USERCOPY is set ... (skipped: HARDENED_USERCOPY depends on the allocator and strict devmem) FAIL 6395s 11:42:55 ERROR| [stderr] 6395s 11:42:55 ERROR| [stderr] == 6395s 11:42:55 ERROR| [stderr] FAIL: test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest.test_290_config_hardened_usercopy) 6395s 11:42:55 ERROR| [stderr] Ensure CONFIG_HARDENED_USERCOPY is set 6395s 11:42:55 ERROR| [stderr] -- 6395s 11:42:55 ERROR| [stderr] Traceback (most recent call last): 6395s 11:42:55 ERROR| [stderr] File "/tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 2724, in test_290_config_hardened_usercopy 6395s 11:42:55 ERROR| [stderr] self.assertKernelConfigUnset(config_name) 6395s 11:42:55 ERROR| [stderr] File "/tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 223, in assertKernelConfigUnset 6395s 11:42:55 ERROR| [stderr] self.assertFalse(self._test_config(name), 6395s 11:42:55 ERROR| [stderr] AssertionError: True is not false : HARDENED_USERCOPY option was expected to be unset in the kernel config ** Affects: linux (Ubuntu) Importance: Medium Status: Triaged ** Affects: linux (Ubuntu Mantic) Importance: Medium Status: Triaged ** Tags: kernel-adt-failure ** Also affects: linux (Ubuntu Mantic) Importance: Medium Status: Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038440 Title: mantic:linux: ubuntu_qrt_kernel_security: KernelSecurityConfigTest.test_290_config_hardened_usercopy skipped Status in linux package in Ubuntu: Triaged Status in linux source package in Mantic: Triaged Bug description: 6395s 11:42:55 DEBUG| Running 'python3 ./test-kernel-security.py -v KernelSecurityConfigTest.test_290_config_hardened_usercopy' 6395s 11:42:55 DEBUG| [stdout] Running test: './test-kernel- security.py' distro: 'Ubuntu 23.10' kernel: '6.5.0-7.7 (Ubuntu 6.5.0-7.7-generic 6.5.3)' arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu') 6395s 11:42:55 ERROR| [stderr] test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest.test_290_config_hardened_usercopy) 6395s 11:42:55 ERROR| [stderr] Ensure CONFIG_HARDENED_USERCOPY is set ... (skipped: HARDENED_USERCOPY depends on the allocator and strict devmem) FAIL 6395s 11:42:55 ERROR| [stderr] 6395s 11:42:55 ERROR| [stderr] == 6395s 11:42:55 ERROR| [stderr] FAIL: test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest.test_290_config_hardened_usercopy) 6395s 11:42:55 ERROR| [stderr] Ensure CONFIG_HARDENED_USERCOPY is set 6395s 11:42:55 ERROR| [stderr] -- 6395s 11:42:55 ERROR| [stderr] Traceback (most recent call last): 6395s 11:42:55 ERROR| [stderr] File "/tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 2724, in test_290_config_hardened_usercopy 6395s 11:42:55 ERROR| [stderr] self.assertKernelConfigUnset(config_name) 6395s 11:42:55 ERROR| [stderr] File "/tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 223, in assertKernelConfigUnset 6395s 11:42:55 ERROR| [stderr] self.assertFalse(self._test_config(name), 6395s 11:42:55 ERROR| [stderr] AssertionError: True is not false : HARDENED_USERCOPY option was expected to be unset in the kernel config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035128] Re: mlxbf-gige: Enable the OOB port in mlxbf_gige_open
This bug was fixed in the package linux-bluefield - 5.4.0-1072.78 --- linux-bluefield (5.4.0-1072.78) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1072.78 -proposed tracker (LP: #2033834) * Focal update: v5.4.248 upstream stable release (LP: #2031121) - [Config] bluefield: updateconfigs for DECNET * mlxbf-gige: Enable the OOB port in mlxbf_gige_open (LP: #2035128) - SAUCE: mlxbf-gige: Enable the OOB port in mlxbf_gige_open [ Ubuntu: 5.4.0-164.181 ] * focal/linux: 5.4.0-164.181 -proposed tracker (LP: #2033867) * Please enable Renesas RZ platform serial installer (LP: #2022361) - [Config] enable hihope RZ/G2M serial console * Azure: hv_netvsc: add support for vlans in AF_PACKET mode (LP: #2030872) - hv_netvsc: add support for vlans in AF_PACKET mode * systemd mount units fail during boot, while file system is correctly mounted (LP: #1837227) - list: introduce list_for_each_continue() - proc/mounts: add cursor * CVE-2023-40283 - Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_ready_cb * CVE-2023-20588 - x86/bugs: Increase the x86 bugs vector size to two u32s - x86/CPU/AMD: Do not leak quotient data after a division by 0 - x86/CPU/AMD: Fix the DIV(0) initial fix attempt * CVE-2023-4194 - net: tun_chr_open(): set sk_uid from current_fsuid() - net: tap_open(): set sk_uid from current_fsuid() * CVE-2023-1206 - tcp: Reduce chance of collisions in inet6_hashfn(). * CVE-2021-4001 - bpf: Fix toctou on read-only map's constant scalar tracking * Focal update: v5.4.248 upstream stable release (LP: #2031121) - test_firmware: fix a memory leak with reqs buffer - KEYS: asymmetric: Copy sig and digest in public_key_verify_signature() - dasd: refactor dasd_ioctl_information - s390/dasd: Use correct lock while counting channel queue length - power: supply: ab8500: Fix external_power_changed race - power: supply: sc27xx: Fix external_power_changed race - power: supply: bq27xxx: Use mod_delayed_work() instead of cancel() + schedule() - ARM: dts: vexpress: add missing cache properties - power: supply: Ratelimit no data debug output - platform/x86: asus-wmi: Ignore WMI events with codes 0x7B, 0xC0 - regulator: Fix error checking for debugfs_create_dir - irqchip/meson-gpio: Mark OF related data as maybe unused - power: supply: Fix logic checking if system is running from battery - btrfs: handle memory allocation failure in btrfs_csum_one_bio - parisc: Improve cache flushing for PCXL in arch_sync_dma_for_cpu() - parisc: Flush gatt writes and adjust gatt mask in parisc_agp_mask_memory() - MIPS: Alchemy: fix dbdma2 - mips: Move initrd_start check after initrd address sanitisation. - xen/blkfront: Only check REQ_FUA for writes - drm:amd:amdgpu: Fix missing buffer object unlock in failure path - ocfs2: fix use-after-free when unmounting read-only filesystem - ocfs2: check new file size on fallocate call - nios2: dts: Fix tse_mac "max-frame-size" property - nilfs2: fix incomplete buffer cleanup in nilfs_btnode_abort_change_key() - nilfs2: fix possible out-of-bounds segment allocation in resize ioctl - kexec: support purgatories with .text.hot sections - powerpc/purgatory: remove PGO flags - nouveau: fix client work fence deletion race - RDMA/uverbs: Restrict usage of privileged QKEYs - net: usb: qmi_wwan: add support for Compal RXM-G1 - ALSA: hda/realtek: Add a quirk for Compaq N14JP6 - Remove DECnet support from kernel - [Config] updateconfigs for DECNET - USB: serial: option: add Quectel EM061KGL series - serial: lantiq: add missing interrupt ack - usb: dwc3: gadget: Reset num TRBs before giving back the request - spi: spi-fsl-dspi: Remove unused chip->void_write_data - spi: fsl-dspi: avoid SCK glitches with continuous transfers - netfilter: nfnetlink: skip error delivery on batch in case of ENOMEM - ping6: Fix send to link-local addresses with VRF. - RDMA/rxe: Remove the unused variable obj - RDMA/rxe: Removed unused name from rxe_task struct - RDMA/rxe: Fix the use-before-initialization error of resp_pkts - iavf: remove mask from iavf_irq_enable_queues() - IB/uverbs: Fix to consider event queue closing also upon non-blocking mode - IB/isert: Fix dead lock in ib_isert - IB/isert: Fix possible list corruption in CMA handler - IB/isert: Fix incorrect release of isert connection - ipvlan: fix bound dev checking for IPv6 l3s mode - sctp: fix an error code in sctp_sf_eat_auth() - igb: fix nvm.ops.read() error handling - drm/nouveau/dp: check for NULL nv_connector->native_mode - drm/nouveau/kms: Don't change EDID when it hasn't actually changed - drm/nouveau: add nv_encoder pointer check for NULL - net/sched: cls_api: Fix lockup on flushing explicitly created chain - net: lapbether: only support eth
[Kernel-packages] [Bug 2031121] Re: Focal update: v5.4.248 upstream stable release
This bug was fixed in the package linux - 5.4.0-164.181 --- linux (5.4.0-164.181) focal; urgency=medium * focal/linux: 5.4.0-164.181 -proposed tracker (LP: #2033867) * Please enable Renesas RZ platform serial installer (LP: #2022361) - [Config] enable hihope RZ/G2M serial console * Azure: hv_netvsc: add support for vlans in AF_PACKET mode (LP: #2030872) - hv_netvsc: add support for vlans in AF_PACKET mode * systemd mount units fail during boot, while file system is correctly mounted (LP: #1837227) - list: introduce list_for_each_continue() - proc/mounts: add cursor * CVE-2023-40283 - Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_ready_cb * CVE-2023-20588 - x86/bugs: Increase the x86 bugs vector size to two u32s - x86/CPU/AMD: Do not leak quotient data after a division by 0 - x86/CPU/AMD: Fix the DIV(0) initial fix attempt * CVE-2023-4194 - net: tun_chr_open(): set sk_uid from current_fsuid() - net: tap_open(): set sk_uid from current_fsuid() * CVE-2023-1206 - tcp: Reduce chance of collisions in inet6_hashfn(). * CVE-2021-4001 - bpf: Fix toctou on read-only map's constant scalar tracking * Focal update: v5.4.248 upstream stable release (LP: #2031121) - test_firmware: fix a memory leak with reqs buffer - KEYS: asymmetric: Copy sig and digest in public_key_verify_signature() - dasd: refactor dasd_ioctl_information - s390/dasd: Use correct lock while counting channel queue length - power: supply: ab8500: Fix external_power_changed race - power: supply: sc27xx: Fix external_power_changed race - power: supply: bq27xxx: Use mod_delayed_work() instead of cancel() + schedule() - ARM: dts: vexpress: add missing cache properties - power: supply: Ratelimit no data debug output - platform/x86: asus-wmi: Ignore WMI events with codes 0x7B, 0xC0 - regulator: Fix error checking for debugfs_create_dir - irqchip/meson-gpio: Mark OF related data as maybe unused - power: supply: Fix logic checking if system is running from battery - btrfs: handle memory allocation failure in btrfs_csum_one_bio - parisc: Improve cache flushing for PCXL in arch_sync_dma_for_cpu() - parisc: Flush gatt writes and adjust gatt mask in parisc_agp_mask_memory() - MIPS: Alchemy: fix dbdma2 - mips: Move initrd_start check after initrd address sanitisation. - xen/blkfront: Only check REQ_FUA for writes - drm:amd:amdgpu: Fix missing buffer object unlock in failure path - ocfs2: fix use-after-free when unmounting read-only filesystem - ocfs2: check new file size on fallocate call - nios2: dts: Fix tse_mac "max-frame-size" property - nilfs2: fix incomplete buffer cleanup in nilfs_btnode_abort_change_key() - nilfs2: fix possible out-of-bounds segment allocation in resize ioctl - kexec: support purgatories with .text.hot sections - powerpc/purgatory: remove PGO flags - nouveau: fix client work fence deletion race - RDMA/uverbs: Restrict usage of privileged QKEYs - net: usb: qmi_wwan: add support for Compal RXM-G1 - ALSA: hda/realtek: Add a quirk for Compaq N14JP6 - Remove DECnet support from kernel - [Config] updateconfigs for DECNET - USB: serial: option: add Quectel EM061KGL series - serial: lantiq: add missing interrupt ack - usb: dwc3: gadget: Reset num TRBs before giving back the request - spi: spi-fsl-dspi: Remove unused chip->void_write_data - spi: fsl-dspi: avoid SCK glitches with continuous transfers - netfilter: nfnetlink: skip error delivery on batch in case of ENOMEM - ping6: Fix send to link-local addresses with VRF. - RDMA/rxe: Remove the unused variable obj - RDMA/rxe: Removed unused name from rxe_task struct - RDMA/rxe: Fix the use-before-initialization error of resp_pkts - iavf: remove mask from iavf_irq_enable_queues() - IB/uverbs: Fix to consider event queue closing also upon non-blocking mode - IB/isert: Fix dead lock in ib_isert - IB/isert: Fix possible list corruption in CMA handler - IB/isert: Fix incorrect release of isert connection - ipvlan: fix bound dev checking for IPv6 l3s mode - sctp: fix an error code in sctp_sf_eat_auth() - igb: fix nvm.ops.read() error handling - drm/nouveau/dp: check for NULL nv_connector->native_mode - drm/nouveau/kms: Don't change EDID when it hasn't actually changed - drm/nouveau: add nv_encoder pointer check for NULL - net/sched: cls_api: Fix lockup on flushing explicitly created chain - net: lapbether: only support ethernet devices - net: tipc: resize nlattr array to correct size - selftests/ptp: Fix timestamp printf format for PTP_SYS_OFFSET - afs: Fix vlserver probe RTT handling - neighbour: Remove unused inline function neigh_key_eq16() - net: Remove unused inline function dst_hold_and_use() - neighbour: delete neigh_lookup_nodev as not used - drm/n
[Kernel-packages] [Bug 2030872] Re: Azure: hv_netvsc: add support for vlans in AF_PACKET mode
This bug was fixed in the package linux - 5.4.0-164.181 --- linux (5.4.0-164.181) focal; urgency=medium * focal/linux: 5.4.0-164.181 -proposed tracker (LP: #2033867) * Please enable Renesas RZ platform serial installer (LP: #2022361) - [Config] enable hihope RZ/G2M serial console * Azure: hv_netvsc: add support for vlans in AF_PACKET mode (LP: #2030872) - hv_netvsc: add support for vlans in AF_PACKET mode * systemd mount units fail during boot, while file system is correctly mounted (LP: #1837227) - list: introduce list_for_each_continue() - proc/mounts: add cursor * CVE-2023-40283 - Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_ready_cb * CVE-2023-20588 - x86/bugs: Increase the x86 bugs vector size to two u32s - x86/CPU/AMD: Do not leak quotient data after a division by 0 - x86/CPU/AMD: Fix the DIV(0) initial fix attempt * CVE-2023-4194 - net: tun_chr_open(): set sk_uid from current_fsuid() - net: tap_open(): set sk_uid from current_fsuid() * CVE-2023-1206 - tcp: Reduce chance of collisions in inet6_hashfn(). * CVE-2021-4001 - bpf: Fix toctou on read-only map's constant scalar tracking * Focal update: v5.4.248 upstream stable release (LP: #2031121) - test_firmware: fix a memory leak with reqs buffer - KEYS: asymmetric: Copy sig and digest in public_key_verify_signature() - dasd: refactor dasd_ioctl_information - s390/dasd: Use correct lock while counting channel queue length - power: supply: ab8500: Fix external_power_changed race - power: supply: sc27xx: Fix external_power_changed race - power: supply: bq27xxx: Use mod_delayed_work() instead of cancel() + schedule() - ARM: dts: vexpress: add missing cache properties - power: supply: Ratelimit no data debug output - platform/x86: asus-wmi: Ignore WMI events with codes 0x7B, 0xC0 - regulator: Fix error checking for debugfs_create_dir - irqchip/meson-gpio: Mark OF related data as maybe unused - power: supply: Fix logic checking if system is running from battery - btrfs: handle memory allocation failure in btrfs_csum_one_bio - parisc: Improve cache flushing for PCXL in arch_sync_dma_for_cpu() - parisc: Flush gatt writes and adjust gatt mask in parisc_agp_mask_memory() - MIPS: Alchemy: fix dbdma2 - mips: Move initrd_start check after initrd address sanitisation. - xen/blkfront: Only check REQ_FUA for writes - drm:amd:amdgpu: Fix missing buffer object unlock in failure path - ocfs2: fix use-after-free when unmounting read-only filesystem - ocfs2: check new file size on fallocate call - nios2: dts: Fix tse_mac "max-frame-size" property - nilfs2: fix incomplete buffer cleanup in nilfs_btnode_abort_change_key() - nilfs2: fix possible out-of-bounds segment allocation in resize ioctl - kexec: support purgatories with .text.hot sections - powerpc/purgatory: remove PGO flags - nouveau: fix client work fence deletion race - RDMA/uverbs: Restrict usage of privileged QKEYs - net: usb: qmi_wwan: add support for Compal RXM-G1 - ALSA: hda/realtek: Add a quirk for Compaq N14JP6 - Remove DECnet support from kernel - [Config] updateconfigs for DECNET - USB: serial: option: add Quectel EM061KGL series - serial: lantiq: add missing interrupt ack - usb: dwc3: gadget: Reset num TRBs before giving back the request - spi: spi-fsl-dspi: Remove unused chip->void_write_data - spi: fsl-dspi: avoid SCK glitches with continuous transfers - netfilter: nfnetlink: skip error delivery on batch in case of ENOMEM - ping6: Fix send to link-local addresses with VRF. - RDMA/rxe: Remove the unused variable obj - RDMA/rxe: Removed unused name from rxe_task struct - RDMA/rxe: Fix the use-before-initialization error of resp_pkts - iavf: remove mask from iavf_irq_enable_queues() - IB/uverbs: Fix to consider event queue closing also upon non-blocking mode - IB/isert: Fix dead lock in ib_isert - IB/isert: Fix possible list corruption in CMA handler - IB/isert: Fix incorrect release of isert connection - ipvlan: fix bound dev checking for IPv6 l3s mode - sctp: fix an error code in sctp_sf_eat_auth() - igb: fix nvm.ops.read() error handling - drm/nouveau/dp: check for NULL nv_connector->native_mode - drm/nouveau/kms: Don't change EDID when it hasn't actually changed - drm/nouveau: add nv_encoder pointer check for NULL - net/sched: cls_api: Fix lockup on flushing explicitly created chain - net: lapbether: only support ethernet devices - net: tipc: resize nlattr array to correct size - selftests/ptp: Fix timestamp printf format for PTP_SYS_OFFSET - afs: Fix vlserver probe RTT handling - neighbour: Remove unused inline function neigh_key_eq16() - net: Remove unused inline function dst_hold_and_use() - neighbour: delete neigh_lookup_nodev as not used - drm/n
[Kernel-packages] [Bug 2030818] Re: Focal update: v5.4.247 upstream stable release
This bug was fixed in the package linux - 5.4.0-164.181 --- linux (5.4.0-164.181) focal; urgency=medium * focal/linux: 5.4.0-164.181 -proposed tracker (LP: #2033867) * Please enable Renesas RZ platform serial installer (LP: #2022361) - [Config] enable hihope RZ/G2M serial console * Azure: hv_netvsc: add support for vlans in AF_PACKET mode (LP: #2030872) - hv_netvsc: add support for vlans in AF_PACKET mode * systemd mount units fail during boot, while file system is correctly mounted (LP: #1837227) - list: introduce list_for_each_continue() - proc/mounts: add cursor * CVE-2023-40283 - Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_ready_cb * CVE-2023-20588 - x86/bugs: Increase the x86 bugs vector size to two u32s - x86/CPU/AMD: Do not leak quotient data after a division by 0 - x86/CPU/AMD: Fix the DIV(0) initial fix attempt * CVE-2023-4194 - net: tun_chr_open(): set sk_uid from current_fsuid() - net: tap_open(): set sk_uid from current_fsuid() * CVE-2023-1206 - tcp: Reduce chance of collisions in inet6_hashfn(). * CVE-2021-4001 - bpf: Fix toctou on read-only map's constant scalar tracking * Focal update: v5.4.248 upstream stable release (LP: #2031121) - test_firmware: fix a memory leak with reqs buffer - KEYS: asymmetric: Copy sig and digest in public_key_verify_signature() - dasd: refactor dasd_ioctl_information - s390/dasd: Use correct lock while counting channel queue length - power: supply: ab8500: Fix external_power_changed race - power: supply: sc27xx: Fix external_power_changed race - power: supply: bq27xxx: Use mod_delayed_work() instead of cancel() + schedule() - ARM: dts: vexpress: add missing cache properties - power: supply: Ratelimit no data debug output - platform/x86: asus-wmi: Ignore WMI events with codes 0x7B, 0xC0 - regulator: Fix error checking for debugfs_create_dir - irqchip/meson-gpio: Mark OF related data as maybe unused - power: supply: Fix logic checking if system is running from battery - btrfs: handle memory allocation failure in btrfs_csum_one_bio - parisc: Improve cache flushing for PCXL in arch_sync_dma_for_cpu() - parisc: Flush gatt writes and adjust gatt mask in parisc_agp_mask_memory() - MIPS: Alchemy: fix dbdma2 - mips: Move initrd_start check after initrd address sanitisation. - xen/blkfront: Only check REQ_FUA for writes - drm:amd:amdgpu: Fix missing buffer object unlock in failure path - ocfs2: fix use-after-free when unmounting read-only filesystem - ocfs2: check new file size on fallocate call - nios2: dts: Fix tse_mac "max-frame-size" property - nilfs2: fix incomplete buffer cleanup in nilfs_btnode_abort_change_key() - nilfs2: fix possible out-of-bounds segment allocation in resize ioctl - kexec: support purgatories with .text.hot sections - powerpc/purgatory: remove PGO flags - nouveau: fix client work fence deletion race - RDMA/uverbs: Restrict usage of privileged QKEYs - net: usb: qmi_wwan: add support for Compal RXM-G1 - ALSA: hda/realtek: Add a quirk for Compaq N14JP6 - Remove DECnet support from kernel - [Config] updateconfigs for DECNET - USB: serial: option: add Quectel EM061KGL series - serial: lantiq: add missing interrupt ack - usb: dwc3: gadget: Reset num TRBs before giving back the request - spi: spi-fsl-dspi: Remove unused chip->void_write_data - spi: fsl-dspi: avoid SCK glitches with continuous transfers - netfilter: nfnetlink: skip error delivery on batch in case of ENOMEM - ping6: Fix send to link-local addresses with VRF. - RDMA/rxe: Remove the unused variable obj - RDMA/rxe: Removed unused name from rxe_task struct - RDMA/rxe: Fix the use-before-initialization error of resp_pkts - iavf: remove mask from iavf_irq_enable_queues() - IB/uverbs: Fix to consider event queue closing also upon non-blocking mode - IB/isert: Fix dead lock in ib_isert - IB/isert: Fix possible list corruption in CMA handler - IB/isert: Fix incorrect release of isert connection - ipvlan: fix bound dev checking for IPv6 l3s mode - sctp: fix an error code in sctp_sf_eat_auth() - igb: fix nvm.ops.read() error handling - drm/nouveau/dp: check for NULL nv_connector->native_mode - drm/nouveau/kms: Don't change EDID when it hasn't actually changed - drm/nouveau: add nv_encoder pointer check for NULL - net/sched: cls_api: Fix lockup on flushing explicitly created chain - net: lapbether: only support ethernet devices - net: tipc: resize nlattr array to correct size - selftests/ptp: Fix timestamp printf format for PTP_SYS_OFFSET - afs: Fix vlserver probe RTT handling - neighbour: Remove unused inline function neigh_key_eq16() - net: Remove unused inline function dst_hold_and_use() - neighbour: delete neigh_lookup_nodev as not used - drm/n
[Kernel-packages] [Bug 2022361] Re: Please enable Renesas RZ platform serial installer
This bug was fixed in the package linux - 5.4.0-164.181 --- linux (5.4.0-164.181) focal; urgency=medium * focal/linux: 5.4.0-164.181 -proposed tracker (LP: #2033867) * Please enable Renesas RZ platform serial installer (LP: #2022361) - [Config] enable hihope RZ/G2M serial console * Azure: hv_netvsc: add support for vlans in AF_PACKET mode (LP: #2030872) - hv_netvsc: add support for vlans in AF_PACKET mode * systemd mount units fail during boot, while file system is correctly mounted (LP: #1837227) - list: introduce list_for_each_continue() - proc/mounts: add cursor * CVE-2023-40283 - Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_ready_cb * CVE-2023-20588 - x86/bugs: Increase the x86 bugs vector size to two u32s - x86/CPU/AMD: Do not leak quotient data after a division by 0 - x86/CPU/AMD: Fix the DIV(0) initial fix attempt * CVE-2023-4194 - net: tun_chr_open(): set sk_uid from current_fsuid() - net: tap_open(): set sk_uid from current_fsuid() * CVE-2023-1206 - tcp: Reduce chance of collisions in inet6_hashfn(). * CVE-2021-4001 - bpf: Fix toctou on read-only map's constant scalar tracking * Focal update: v5.4.248 upstream stable release (LP: #2031121) - test_firmware: fix a memory leak with reqs buffer - KEYS: asymmetric: Copy sig and digest in public_key_verify_signature() - dasd: refactor dasd_ioctl_information - s390/dasd: Use correct lock while counting channel queue length - power: supply: ab8500: Fix external_power_changed race - power: supply: sc27xx: Fix external_power_changed race - power: supply: bq27xxx: Use mod_delayed_work() instead of cancel() + schedule() - ARM: dts: vexpress: add missing cache properties - power: supply: Ratelimit no data debug output - platform/x86: asus-wmi: Ignore WMI events with codes 0x7B, 0xC0 - regulator: Fix error checking for debugfs_create_dir - irqchip/meson-gpio: Mark OF related data as maybe unused - power: supply: Fix logic checking if system is running from battery - btrfs: handle memory allocation failure in btrfs_csum_one_bio - parisc: Improve cache flushing for PCXL in arch_sync_dma_for_cpu() - parisc: Flush gatt writes and adjust gatt mask in parisc_agp_mask_memory() - MIPS: Alchemy: fix dbdma2 - mips: Move initrd_start check after initrd address sanitisation. - xen/blkfront: Only check REQ_FUA for writes - drm:amd:amdgpu: Fix missing buffer object unlock in failure path - ocfs2: fix use-after-free when unmounting read-only filesystem - ocfs2: check new file size on fallocate call - nios2: dts: Fix tse_mac "max-frame-size" property - nilfs2: fix incomplete buffer cleanup in nilfs_btnode_abort_change_key() - nilfs2: fix possible out-of-bounds segment allocation in resize ioctl - kexec: support purgatories with .text.hot sections - powerpc/purgatory: remove PGO flags - nouveau: fix client work fence deletion race - RDMA/uverbs: Restrict usage of privileged QKEYs - net: usb: qmi_wwan: add support for Compal RXM-G1 - ALSA: hda/realtek: Add a quirk for Compaq N14JP6 - Remove DECnet support from kernel - [Config] updateconfigs for DECNET - USB: serial: option: add Quectel EM061KGL series - serial: lantiq: add missing interrupt ack - usb: dwc3: gadget: Reset num TRBs before giving back the request - spi: spi-fsl-dspi: Remove unused chip->void_write_data - spi: fsl-dspi: avoid SCK glitches with continuous transfers - netfilter: nfnetlink: skip error delivery on batch in case of ENOMEM - ping6: Fix send to link-local addresses with VRF. - RDMA/rxe: Remove the unused variable obj - RDMA/rxe: Removed unused name from rxe_task struct - RDMA/rxe: Fix the use-before-initialization error of resp_pkts - iavf: remove mask from iavf_irq_enable_queues() - IB/uverbs: Fix to consider event queue closing also upon non-blocking mode - IB/isert: Fix dead lock in ib_isert - IB/isert: Fix possible list corruption in CMA handler - IB/isert: Fix incorrect release of isert connection - ipvlan: fix bound dev checking for IPv6 l3s mode - sctp: fix an error code in sctp_sf_eat_auth() - igb: fix nvm.ops.read() error handling - drm/nouveau/dp: check for NULL nv_connector->native_mode - drm/nouveau/kms: Don't change EDID when it hasn't actually changed - drm/nouveau: add nv_encoder pointer check for NULL - net/sched: cls_api: Fix lockup on flushing explicitly created chain - net: lapbether: only support ethernet devices - net: tipc: resize nlattr array to correct size - selftests/ptp: Fix timestamp printf format for PTP_SYS_OFFSET - afs: Fix vlserver probe RTT handling - neighbour: Remove unused inline function neigh_key_eq16() - net: Remove unused inline function dst_hold_and_use() - neighbour: delete neigh_lookup_nodev as not used - drm/n
[Kernel-packages] [Bug 2038447] [NEW] mantic:linux: ubuntu_cve_kernel.CVE-2016-3134/5 fail to unshare
Public bug reported: 16371s 14:29:11 INFO | *** CVE-2016-3134 *** 16371s 14:29:11 DEBUG| Running 'make -C /tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3134 check' 16371s 14:29:11 DEBUG| [stdout] make: Entering directory '/tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3134' 16371s 14:29:11 DEBUG| [stdout] gcc -w -o netfilter_setsockopt_v3 netfilter_setsockopt_v3.c 16371s 14:29:11 DEBUG| [stdout] sudo -u '#1000' ./netfilter_setsockopt_v3 16371s 14:29:11 ERROR| [stderr] unshare: Permission denied 16371s 14:29:11 ERROR| [stderr] make: *** [Makefile:10: check] Error 255 16373s 14:29:13 INFO | *** CVE-2016-3135 *** 16373s 14:29:13 DEBUG| Running 'make -C /tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3135 check' 16373s 14:29:13 DEBUG| [stdout] make: Entering directory '/tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3135' 16373s 14:29:13 DEBUG| [stdout] gcc -w -o netfilter_setsockopt_v4 netfilter_setsockopt_v4.c 16373s 14:29:13 DEBUG| [stdout] sudo -u '#1000' ./netfilter_setsockopt_v4 16373s 14:29:13 ERROR| [stderr] unshare: Permission denied ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Mantic) Importance: Medium Status: Confirmed ** Tags: kernel-adt-failure ** Also affects: linux (Ubuntu Mantic) Importance: Medium Status: Confirmed ** Description changed: 16371s 14:29:11 INFO | *** CVE-2016-3134 *** 16371s 14:29:11 DEBUG| Running 'make -C /tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3134 check' 16371s 14:29:11 DEBUG| [stdout] make: Entering directory '/tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3134' 16371s 14:29:11 DEBUG| [stdout] gcc -w -o netfilter_setsockopt_v3 netfilter_setsockopt_v3.c 16371s 14:29:11 DEBUG| [stdout] sudo -u '#1000' ./netfilter_setsockopt_v3 16371s 14:29:11 ERROR| [stderr] unshare: Permission denied 16371s 14:29:11 ERROR| [stderr] make: *** [Makefile:10: check] Error 255 + + 16373s 14:29:13 INFO | *** CVE-2016-3135 *** + 16373s 14:29:13 DEBUG| Running 'make -C /tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3135 check' + 16373s 14:29:13 DEBUG| [stdout] make: Entering directory '/tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3135' + 16373s 14:29:13 DEBUG| [stdout] gcc -w -o netfilter_setsockopt_v4 netfilter_setsockopt_v4.c + 16373s 14:29:13 DEBUG| [stdout] sudo -u '#1000' ./netfilter_setsockopt_v4 + 16373s 14:29:13 ERROR| [stderr] unshare: Permission denied ** Summary changed: - mantic:linux: ubuntu_cve_kernel.CVE-2016-3134 fails + mantic:linux: ubuntu_cve_kernel.CVE-2016-3134/5 fail to unshare -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038447 Title: mantic:linux: ubuntu_cve_kernel.CVE-2016-3134/5 fail to unshare Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Confirmed Bug description: 16371s 14:29:11 INFO | *** CVE-2016-3134 *** 16371s 14:29:11 DEBUG| Running 'make -C /tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3134 check' 16371s 14:29:11 DEBUG| [stdout] make: Entering directory '/tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3134' 16371s 14:29:11 DEBUG| [stdout] gcc -w -o netfilter_setsockopt_v3 netfilter_setsockopt_v3.c 16371s 14:29:11 DEBUG| [stdout] sudo -u '#1000' ./netfilter_setsockopt_v3 16371s 14:29:11 ERROR| [stderr] unshare: Permission denied 16371s 14:29:11 ERROR| [stderr] make: *** [Makefile:10: check] Error 255 16373s 14:29:13 INFO | *** CVE-2016-3135 *** 16373s 14:29:13 DEBUG| Running 'make -C /tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3135 check' 16373s 14:29:13 DEBUG| [stdout] make: Entering directory '/tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3135' 16373s 14:29:13 DEBUG| [stdout] gcc -w -o netfilter_setsockopt_v4 netfilter_setsockopt_v4.c 16373s 14:29:13 DEBUG| [stdout] sudo -u '#1000' ./netfilter_setsockopt_v4 16373s 14:29:13 ERROR| [stderr] unshare: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Remove obsolete "nousb" option in kdump command-line for newer kernels
"patch" flag removed from the attachment
"patch" tag removed
~ubuntu-sponsors unsubscribed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Remove obsolete "nousb" option in kdump command-line for newer kernels
Status in makedumpfile package in Ubuntu:
Confirmed
Status in kdump-tools source package in Xenial:
New
Status in makedumpfile source package in Xenial:
Won't Fix
Status in kdump-tools source package in Bionic:
New
Status in makedumpfile source package in Bionic:
Confirmed
Status in kdump-tools source package in Eoan:
New
Status in makedumpfile source package in Eoan:
Won't Fix
Status in kdump-tools source package in Focal:
New
Status in makedumpfile source package in Focal:
Confirmed
Status in kdump-tools source package in Groovy:
New
Status in makedumpfile source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Kdump command-line include an obsolete "nousb" parameter by default, which
can cause a misimpression: users will think they are not booting with USB, but
they are.
* Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case
the subsystem is built-in). This was changed by commit 097a9ea0e48
("usb: make "nousb" a clear module parameter").
* USB may be pretty essential in case for example kdump users need to
decrypt a disk under LUKS, and there's only an USB keyboard connected
to the system. Given the option is innocuous since Bionic, we should
just drop it to prevent confusion.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'nousb' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is extremely low, since the "nousb" parameter
is not used since Bionic although is there. Any bugs we would have by
changing this are still valid by not removing the option - the
semantics with or without "nosub" is the same since from Bionic.
NOTICE we won't change Xenial, it can use kernel 4.4 which indeed
disables USB by taking the "nousb" parameter.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted
This bug was fixed in the package linux - 5.4.0-164.181 --- linux (5.4.0-164.181) focal; urgency=medium * focal/linux: 5.4.0-164.181 -proposed tracker (LP: #2033867) * Please enable Renesas RZ platform serial installer (LP: #2022361) - [Config] enable hihope RZ/G2M serial console * Azure: hv_netvsc: add support for vlans in AF_PACKET mode (LP: #2030872) - hv_netvsc: add support for vlans in AF_PACKET mode * systemd mount units fail during boot, while file system is correctly mounted (LP: #1837227) - list: introduce list_for_each_continue() - proc/mounts: add cursor * CVE-2023-40283 - Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_ready_cb * CVE-2023-20588 - x86/bugs: Increase the x86 bugs vector size to two u32s - x86/CPU/AMD: Do not leak quotient data after a division by 0 - x86/CPU/AMD: Fix the DIV(0) initial fix attempt * CVE-2023-4194 - net: tun_chr_open(): set sk_uid from current_fsuid() - net: tap_open(): set sk_uid from current_fsuid() * CVE-2023-1206 - tcp: Reduce chance of collisions in inet6_hashfn(). * CVE-2021-4001 - bpf: Fix toctou on read-only map's constant scalar tracking * Focal update: v5.4.248 upstream stable release (LP: #2031121) - test_firmware: fix a memory leak with reqs buffer - KEYS: asymmetric: Copy sig and digest in public_key_verify_signature() - dasd: refactor dasd_ioctl_information - s390/dasd: Use correct lock while counting channel queue length - power: supply: ab8500: Fix external_power_changed race - power: supply: sc27xx: Fix external_power_changed race - power: supply: bq27xxx: Use mod_delayed_work() instead of cancel() + schedule() - ARM: dts: vexpress: add missing cache properties - power: supply: Ratelimit no data debug output - platform/x86: asus-wmi: Ignore WMI events with codes 0x7B, 0xC0 - regulator: Fix error checking for debugfs_create_dir - irqchip/meson-gpio: Mark OF related data as maybe unused - power: supply: Fix logic checking if system is running from battery - btrfs: handle memory allocation failure in btrfs_csum_one_bio - parisc: Improve cache flushing for PCXL in arch_sync_dma_for_cpu() - parisc: Flush gatt writes and adjust gatt mask in parisc_agp_mask_memory() - MIPS: Alchemy: fix dbdma2 - mips: Move initrd_start check after initrd address sanitisation. - xen/blkfront: Only check REQ_FUA for writes - drm:amd:amdgpu: Fix missing buffer object unlock in failure path - ocfs2: fix use-after-free when unmounting read-only filesystem - ocfs2: check new file size on fallocate call - nios2: dts: Fix tse_mac "max-frame-size" property - nilfs2: fix incomplete buffer cleanup in nilfs_btnode_abort_change_key() - nilfs2: fix possible out-of-bounds segment allocation in resize ioctl - kexec: support purgatories with .text.hot sections - powerpc/purgatory: remove PGO flags - nouveau: fix client work fence deletion race - RDMA/uverbs: Restrict usage of privileged QKEYs - net: usb: qmi_wwan: add support for Compal RXM-G1 - ALSA: hda/realtek: Add a quirk for Compaq N14JP6 - Remove DECnet support from kernel - [Config] updateconfigs for DECNET - USB: serial: option: add Quectel EM061KGL series - serial: lantiq: add missing interrupt ack - usb: dwc3: gadget: Reset num TRBs before giving back the request - spi: spi-fsl-dspi: Remove unused chip->void_write_data - spi: fsl-dspi: avoid SCK glitches with continuous transfers - netfilter: nfnetlink: skip error delivery on batch in case of ENOMEM - ping6: Fix send to link-local addresses with VRF. - RDMA/rxe: Remove the unused variable obj - RDMA/rxe: Removed unused name from rxe_task struct - RDMA/rxe: Fix the use-before-initialization error of resp_pkts - iavf: remove mask from iavf_irq_enable_queues() - IB/uverbs: Fix to consider event queue closing also upon non-blocking mode - IB/isert: Fix dead lock in ib_isert - IB/isert: Fix possible list corruption in CMA handler - IB/isert: Fix incorrect release of isert connection - ipvlan: fix bound dev checking for IPv6 l3s mode - sctp: fix an error code in sctp_sf_eat_auth() - igb: fix nvm.ops.read() error handling - drm/nouveau/dp: check for NULL nv_connector->native_mode - drm/nouveau/kms: Don't change EDID when it hasn't actually changed - drm/nouveau: add nv_encoder pointer check for NULL - net/sched: cls_api: Fix lockup on flushing explicitly created chain - net: lapbether: only support ethernet devices - net: tipc: resize nlattr array to correct size - selftests/ptp: Fix timestamp printf format for PTP_SYS_OFFSET - afs: Fix vlserver probe RTT handling - neighbour: Remove unused inline function neigh_key_eq16() - net: Remove unused inline function dst_hold_and_use() - neighbour: delete neigh_lookup_nodev as not used - drm/n
[Kernel-packages] [Bug 2038446] [NEW] mantic:linux: net:rtnetlink.sh: address proto IPv(4/6) failing
Public bug reported: 9017s 12:26:37 DEBUG| [stdout] # PASS: neigh get 9018s 12:26:38 DEBUG| [stdout] # PASS: bridge_parent_id 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # RTNETLINK answers: Cannot assign requested address 9018s 12:26:38 DEBUG| [stdout] # RTNETLINK answers: Cannot assign requested address 9018s 12:26:38 DEBUG| [stdout] # FAIL: address proto IPv4 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9019s 12:26:39 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9019s 12:26:39 DEBUG| [stdout] # RTNETLINK answers: Cannot assign requested address 9019s 12:26:39 DEBUG| [stdout] # RTNETLINK answers: Cannot assign requested address 9019s 12:26:39 DEBUG| [stdout] # FAIL: address proto IPv6 ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Mantic) Importance: Medium Status: Confirmed ** Tags: kernel-adt-failure ** Also affects: apparmor (Ubuntu Mantic) Importance: Medium Status: Confirmed ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: apparmor (Ubuntu) ** No longer affects: apparmor (Ubuntu Mantic) ** Changed in: linux (Ubuntu Mantic) Status: New => Confirmed ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038446 Title: mantic:linux: net:rtnetlink.sh: address proto IPv(4/6) failing Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Confirmed Bug description: 9017s 12:26:37 DEBUG| [stdout] # PASS: neigh get 9018s 12:26:38 DEBUG| [stdout] # PASS: bridge_parent_id 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # RTNETLINK answers: Cannot assign requested address 9018s 12:26:38 DEBUG| [stdout] # RTNETLINK answers: Cannot assign requested address 9018s 12:26:38 DEBUG| [stdout] # FAIL: address proto IPv4 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9019s 12:26:39 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9019s 12:26:39 DEBUG| [stdout] # RTNETLINK answers: Cannot assign requested address 9019s 12:26:39 DEBUG| [stdout] # RTNETLINK answers: Cannot assign requested address 9019s 12:26:39 DEBUG| [stdout] # FAIL: address proto IPv6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035356] Re: Jammy update: v6.1.50 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1023.23
---
linux-oem-6.1 (6.1.0-1023.23) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1023.23 -proposed tracker (LP: #2033827)
* Jammy update: v6.1.53 upstream stable release (LP: #2035359)
- Revert "bridge: Add extack warning when enabling STP in netns."
- Partially revert "drm/amd/display: Fix possible underflow for displays
with
large vblank"
- scsi: ufs: Try harder to change the power mode
- Revert "Revert drm/amd/display: Enable Freesync Video Mode by default"
- ARM: dts: imx: Set default tuning step for imx7d usdhc
- powerpc/boot: Disable power10 features after BOOTAFLAGS assignment
- media: uapi: HEVC: Add num_delta_pocs_of_ref_rps_idx field
- Revert "MIPS: unhide PATA_PLATFORM"
- phy: qcom-snps-femto-v2: use qcom_snps_hsphy_suspend/resume error code
- media: amphion: use dev_err_probe
- media: pulse8-cec: handle possible ping error
- media: pci: cx23885: fix error handling for cx23885 ATSC boards
- 9p: virtio: fix unlikely null pointer deref in handle_rerror
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ksmbd: fix out of bounds in smb3_decrypt_req()
- ksmbd: validate session id and tree id in compound request
- ksmbd: no response from compound read
- ksmbd: fix out of bounds in init_smb2_rsp_hdr()
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ASoC: nau8821: Add DMI quirk mechanism for active-high jack-detect
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoC: rt5682-sdw: fix for JD event handling in ClockStop Mode0
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: rt711: fix for JD event handling in ClockStop Mode0
- ASoC: rt711-sdca: fix for JD event handling in ClockStop Mode0
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- ALSA: usb-audio: Add quirk for Microsoft Modern Wireless Headset
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86/intel/hid: Add HP Dragonfly G2 to VGBS DMI quirks
- platform/x86: think-lmi: Use kfree_sensitive instead of kfree
- platform/x86: asus-wmi: Fix setting RGB mode on some TUF laptops
- platform/x86: huawei-wmi: Silence ambient light sensor
- drm/amd/smu: use AverageGfxclkFrequency* to replace previous GFX Curr
Clock
- drm/amd/display: Guard DCN31 PHYD32CLK logic against chip family
- drm/amd/display: Exit idle optimizations before attempt to access PHY
- ovl: Always reevaluate the file signature for IMA
- ata: pata_arasan_cf: Use dev_err_probe() instead dev_err() in data_xfer()
- ALSA: usb-audio: Update for native DSD support quirks
- staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER
- security: keys: perform capable check only on privileged operations
- kprobes: Prohibit probing on CFI preamble symbol
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- vmbus_testing: fix wrong python syntax for integer value comparison
- Revert "wifi: ath6k: silence false positive -Wno-dangling-pointer warning
on
GCC 12"
- net: dsa: microchip: KSZ9477 register regmap alignment to 32 bit
boundaries
- net: annotate data-races around sk->sk_{rcv|snd}timeo
- net: usb: qmi_wwan: add Quectel EM05GV2
- wifi: brcmfmac: Fix field-spanning write in brcmf_scan_params_v2_to_v1()
- powerpc/powermac: Use early_* IO variants in via_calibrate_decr()
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- platform/x86/amd/pmf: Fix unsigned comparison with less than zero
- scsi: lpfc: Remove reftag check in DIF paths
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- net: hns3: restore user pause configure when disable autoneg
- drm/amdgpu: Match against exact bootloader status
- wifi: cfg80211: remove links only on AP
- wifi: mac80211: Use active_links instead of valid_links in Tx
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- cifs: fix sockaddr comparison in iface_cmp
- cifs: fix max_credits implementation
- sctp: handle invalid error codes without calling BUG()
- scsi: aacraid: Reply queue mapping to CPUs based on IRQ affinity
- scsi: storvsc: Always set no_report_opcodes
- scsi: lpfc: Fix incorrect big endian type assignment in bsg loopback path
- LoongArch: Let pmd_present() return true when splitting pmd
- LoongArch: Fix the write_fcsr() macro
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- net: sfp: handle 100G/25G active optical cables in sfp_parse_sup
[Kernel-packages] [Bug 2035357] Re: Jammy update: v6.1.51 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1023.23
---
linux-oem-6.1 (6.1.0-1023.23) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1023.23 -proposed tracker (LP: #2033827)
* Jammy update: v6.1.53 upstream stable release (LP: #2035359)
- Revert "bridge: Add extack warning when enabling STP in netns."
- Partially revert "drm/amd/display: Fix possible underflow for displays
with
large vblank"
- scsi: ufs: Try harder to change the power mode
- Revert "Revert drm/amd/display: Enable Freesync Video Mode by default"
- ARM: dts: imx: Set default tuning step for imx7d usdhc
- powerpc/boot: Disable power10 features after BOOTAFLAGS assignment
- media: uapi: HEVC: Add num_delta_pocs_of_ref_rps_idx field
- Revert "MIPS: unhide PATA_PLATFORM"
- phy: qcom-snps-femto-v2: use qcom_snps_hsphy_suspend/resume error code
- media: amphion: use dev_err_probe
- media: pulse8-cec: handle possible ping error
- media: pci: cx23885: fix error handling for cx23885 ATSC boards
- 9p: virtio: fix unlikely null pointer deref in handle_rerror
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ksmbd: fix out of bounds in smb3_decrypt_req()
- ksmbd: validate session id and tree id in compound request
- ksmbd: no response from compound read
- ksmbd: fix out of bounds in init_smb2_rsp_hdr()
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ASoC: nau8821: Add DMI quirk mechanism for active-high jack-detect
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoC: rt5682-sdw: fix for JD event handling in ClockStop Mode0
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: rt711: fix for JD event handling in ClockStop Mode0
- ASoC: rt711-sdca: fix for JD event handling in ClockStop Mode0
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- ALSA: usb-audio: Add quirk for Microsoft Modern Wireless Headset
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86/intel/hid: Add HP Dragonfly G2 to VGBS DMI quirks
- platform/x86: think-lmi: Use kfree_sensitive instead of kfree
- platform/x86: asus-wmi: Fix setting RGB mode on some TUF laptops
- platform/x86: huawei-wmi: Silence ambient light sensor
- drm/amd/smu: use AverageGfxclkFrequency* to replace previous GFX Curr
Clock
- drm/amd/display: Guard DCN31 PHYD32CLK logic against chip family
- drm/amd/display: Exit idle optimizations before attempt to access PHY
- ovl: Always reevaluate the file signature for IMA
- ata: pata_arasan_cf: Use dev_err_probe() instead dev_err() in data_xfer()
- ALSA: usb-audio: Update for native DSD support quirks
- staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER
- security: keys: perform capable check only on privileged operations
- kprobes: Prohibit probing on CFI preamble symbol
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- vmbus_testing: fix wrong python syntax for integer value comparison
- Revert "wifi: ath6k: silence false positive -Wno-dangling-pointer warning
on
GCC 12"
- net: dsa: microchip: KSZ9477 register regmap alignment to 32 bit
boundaries
- net: annotate data-races around sk->sk_{rcv|snd}timeo
- net: usb: qmi_wwan: add Quectel EM05GV2
- wifi: brcmfmac: Fix field-spanning write in brcmf_scan_params_v2_to_v1()
- powerpc/powermac: Use early_* IO variants in via_calibrate_decr()
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- platform/x86/amd/pmf: Fix unsigned comparison with less than zero
- scsi: lpfc: Remove reftag check in DIF paths
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- net: hns3: restore user pause configure when disable autoneg
- drm/amdgpu: Match against exact bootloader status
- wifi: cfg80211: remove links only on AP
- wifi: mac80211: Use active_links instead of valid_links in Tx
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- cifs: fix sockaddr comparison in iface_cmp
- cifs: fix max_credits implementation
- sctp: handle invalid error codes without calling BUG()
- scsi: aacraid: Reply queue mapping to CPUs based on IRQ affinity
- scsi: storvsc: Always set no_report_opcodes
- scsi: lpfc: Fix incorrect big endian type assignment in bsg loopback path
- LoongArch: Let pmd_present() return true when splitting pmd
- LoongArch: Fix the write_fcsr() macro
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- net: sfp: handle 100G/25G active optical cables in sfp_parse_sup
[Kernel-packages] [Bug 2035358] Re: Jammy update: v6.1.52 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1023.23
---
linux-oem-6.1 (6.1.0-1023.23) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1023.23 -proposed tracker (LP: #2033827)
* Jammy update: v6.1.53 upstream stable release (LP: #2035359)
- Revert "bridge: Add extack warning when enabling STP in netns."
- Partially revert "drm/amd/display: Fix possible underflow for displays
with
large vblank"
- scsi: ufs: Try harder to change the power mode
- Revert "Revert drm/amd/display: Enable Freesync Video Mode by default"
- ARM: dts: imx: Set default tuning step for imx7d usdhc
- powerpc/boot: Disable power10 features after BOOTAFLAGS assignment
- media: uapi: HEVC: Add num_delta_pocs_of_ref_rps_idx field
- Revert "MIPS: unhide PATA_PLATFORM"
- phy: qcom-snps-femto-v2: use qcom_snps_hsphy_suspend/resume error code
- media: amphion: use dev_err_probe
- media: pulse8-cec: handle possible ping error
- media: pci: cx23885: fix error handling for cx23885 ATSC boards
- 9p: virtio: fix unlikely null pointer deref in handle_rerror
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ksmbd: fix out of bounds in smb3_decrypt_req()
- ksmbd: validate session id and tree id in compound request
- ksmbd: no response from compound read
- ksmbd: fix out of bounds in init_smb2_rsp_hdr()
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ASoC: nau8821: Add DMI quirk mechanism for active-high jack-detect
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoC: rt5682-sdw: fix for JD event handling in ClockStop Mode0
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: rt711: fix for JD event handling in ClockStop Mode0
- ASoC: rt711-sdca: fix for JD event handling in ClockStop Mode0
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- ALSA: usb-audio: Add quirk for Microsoft Modern Wireless Headset
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86/intel/hid: Add HP Dragonfly G2 to VGBS DMI quirks
- platform/x86: think-lmi: Use kfree_sensitive instead of kfree
- platform/x86: asus-wmi: Fix setting RGB mode on some TUF laptops
- platform/x86: huawei-wmi: Silence ambient light sensor
- drm/amd/smu: use AverageGfxclkFrequency* to replace previous GFX Curr
Clock
- drm/amd/display: Guard DCN31 PHYD32CLK logic against chip family
- drm/amd/display: Exit idle optimizations before attempt to access PHY
- ovl: Always reevaluate the file signature for IMA
- ata: pata_arasan_cf: Use dev_err_probe() instead dev_err() in data_xfer()
- ALSA: usb-audio: Update for native DSD support quirks
- staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER
- security: keys: perform capable check only on privileged operations
- kprobes: Prohibit probing on CFI preamble symbol
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- vmbus_testing: fix wrong python syntax for integer value comparison
- Revert "wifi: ath6k: silence false positive -Wno-dangling-pointer warning
on
GCC 12"
- net: dsa: microchip: KSZ9477 register regmap alignment to 32 bit
boundaries
- net: annotate data-races around sk->sk_{rcv|snd}timeo
- net: usb: qmi_wwan: add Quectel EM05GV2
- wifi: brcmfmac: Fix field-spanning write in brcmf_scan_params_v2_to_v1()
- powerpc/powermac: Use early_* IO variants in via_calibrate_decr()
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- platform/x86/amd/pmf: Fix unsigned comparison with less than zero
- scsi: lpfc: Remove reftag check in DIF paths
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- net: hns3: restore user pause configure when disable autoneg
- drm/amdgpu: Match against exact bootloader status
- wifi: cfg80211: remove links only on AP
- wifi: mac80211: Use active_links instead of valid_links in Tx
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- cifs: fix sockaddr comparison in iface_cmp
- cifs: fix max_credits implementation
- sctp: handle invalid error codes without calling BUG()
- scsi: aacraid: Reply queue mapping to CPUs based on IRQ affinity
- scsi: storvsc: Always set no_report_opcodes
- scsi: lpfc: Fix incorrect big endian type assignment in bsg loopback path
- LoongArch: Let pmd_present() return true when splitting pmd
- LoongArch: Fix the write_fcsr() macro
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- net: sfp: handle 100G/25G active optical cables in sfp_parse_sup
[Kernel-packages] [Bug 2035354] Re: Jammy update: v6.1.48 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1023.23
---
linux-oem-6.1 (6.1.0-1023.23) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1023.23 -proposed tracker (LP: #2033827)
* Jammy update: v6.1.53 upstream stable release (LP: #2035359)
- Revert "bridge: Add extack warning when enabling STP in netns."
- Partially revert "drm/amd/display: Fix possible underflow for displays
with
large vblank"
- scsi: ufs: Try harder to change the power mode
- Revert "Revert drm/amd/display: Enable Freesync Video Mode by default"
- ARM: dts: imx: Set default tuning step for imx7d usdhc
- powerpc/boot: Disable power10 features after BOOTAFLAGS assignment
- media: uapi: HEVC: Add num_delta_pocs_of_ref_rps_idx field
- Revert "MIPS: unhide PATA_PLATFORM"
- phy: qcom-snps-femto-v2: use qcom_snps_hsphy_suspend/resume error code
- media: amphion: use dev_err_probe
- media: pulse8-cec: handle possible ping error
- media: pci: cx23885: fix error handling for cx23885 ATSC boards
- 9p: virtio: fix unlikely null pointer deref in handle_rerror
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ksmbd: fix out of bounds in smb3_decrypt_req()
- ksmbd: validate session id and tree id in compound request
- ksmbd: no response from compound read
- ksmbd: fix out of bounds in init_smb2_rsp_hdr()
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ASoC: nau8821: Add DMI quirk mechanism for active-high jack-detect
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoC: rt5682-sdw: fix for JD event handling in ClockStop Mode0
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: rt711: fix for JD event handling in ClockStop Mode0
- ASoC: rt711-sdca: fix for JD event handling in ClockStop Mode0
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- ALSA: usb-audio: Add quirk for Microsoft Modern Wireless Headset
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86/intel/hid: Add HP Dragonfly G2 to VGBS DMI quirks
- platform/x86: think-lmi: Use kfree_sensitive instead of kfree
- platform/x86: asus-wmi: Fix setting RGB mode on some TUF laptops
- platform/x86: huawei-wmi: Silence ambient light sensor
- drm/amd/smu: use AverageGfxclkFrequency* to replace previous GFX Curr
Clock
- drm/amd/display: Guard DCN31 PHYD32CLK logic against chip family
- drm/amd/display: Exit idle optimizations before attempt to access PHY
- ovl: Always reevaluate the file signature for IMA
- ata: pata_arasan_cf: Use dev_err_probe() instead dev_err() in data_xfer()
- ALSA: usb-audio: Update for native DSD support quirks
- staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER
- security: keys: perform capable check only on privileged operations
- kprobes: Prohibit probing on CFI preamble symbol
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- vmbus_testing: fix wrong python syntax for integer value comparison
- Revert "wifi: ath6k: silence false positive -Wno-dangling-pointer warning
on
GCC 12"
- net: dsa: microchip: KSZ9477 register regmap alignment to 32 bit
boundaries
- net: annotate data-races around sk->sk_{rcv|snd}timeo
- net: usb: qmi_wwan: add Quectel EM05GV2
- wifi: brcmfmac: Fix field-spanning write in brcmf_scan_params_v2_to_v1()
- powerpc/powermac: Use early_* IO variants in via_calibrate_decr()
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- platform/x86/amd/pmf: Fix unsigned comparison with less than zero
- scsi: lpfc: Remove reftag check in DIF paths
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- net: hns3: restore user pause configure when disable autoneg
- drm/amdgpu: Match against exact bootloader status
- wifi: cfg80211: remove links only on AP
- wifi: mac80211: Use active_links instead of valid_links in Tx
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- cifs: fix sockaddr comparison in iface_cmp
- cifs: fix max_credits implementation
- sctp: handle invalid error codes without calling BUG()
- scsi: aacraid: Reply queue mapping to CPUs based on IRQ affinity
- scsi: storvsc: Always set no_report_opcodes
- scsi: lpfc: Fix incorrect big endian type assignment in bsg loopback path
- LoongArch: Let pmd_present() return true when splitting pmd
- LoongArch: Fix the write_fcsr() macro
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- net: sfp: handle 100G/25G active optical cables in sfp_parse_sup
[Kernel-packages] [Bug 2035355] Re: Jammy update: v6.1.49 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1023.23
---
linux-oem-6.1 (6.1.0-1023.23) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1023.23 -proposed tracker (LP: #2033827)
* Jammy update: v6.1.53 upstream stable release (LP: #2035359)
- Revert "bridge: Add extack warning when enabling STP in netns."
- Partially revert "drm/amd/display: Fix possible underflow for displays
with
large vblank"
- scsi: ufs: Try harder to change the power mode
- Revert "Revert drm/amd/display: Enable Freesync Video Mode by default"
- ARM: dts: imx: Set default tuning step for imx7d usdhc
- powerpc/boot: Disable power10 features after BOOTAFLAGS assignment
- media: uapi: HEVC: Add num_delta_pocs_of_ref_rps_idx field
- Revert "MIPS: unhide PATA_PLATFORM"
- phy: qcom-snps-femto-v2: use qcom_snps_hsphy_suspend/resume error code
- media: amphion: use dev_err_probe
- media: pulse8-cec: handle possible ping error
- media: pci: cx23885: fix error handling for cx23885 ATSC boards
- 9p: virtio: fix unlikely null pointer deref in handle_rerror
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ksmbd: fix out of bounds in smb3_decrypt_req()
- ksmbd: validate session id and tree id in compound request
- ksmbd: no response from compound read
- ksmbd: fix out of bounds in init_smb2_rsp_hdr()
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ASoC: nau8821: Add DMI quirk mechanism for active-high jack-detect
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoC: rt5682-sdw: fix for JD event handling in ClockStop Mode0
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: rt711: fix for JD event handling in ClockStop Mode0
- ASoC: rt711-sdca: fix for JD event handling in ClockStop Mode0
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- ALSA: usb-audio: Add quirk for Microsoft Modern Wireless Headset
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86/intel/hid: Add HP Dragonfly G2 to VGBS DMI quirks
- platform/x86: think-lmi: Use kfree_sensitive instead of kfree
- platform/x86: asus-wmi: Fix setting RGB mode on some TUF laptops
- platform/x86: huawei-wmi: Silence ambient light sensor
- drm/amd/smu: use AverageGfxclkFrequency* to replace previous GFX Curr
Clock
- drm/amd/display: Guard DCN31 PHYD32CLK logic against chip family
- drm/amd/display: Exit idle optimizations before attempt to access PHY
- ovl: Always reevaluate the file signature for IMA
- ata: pata_arasan_cf: Use dev_err_probe() instead dev_err() in data_xfer()
- ALSA: usb-audio: Update for native DSD support quirks
- staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER
- security: keys: perform capable check only on privileged operations
- kprobes: Prohibit probing on CFI preamble symbol
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- vmbus_testing: fix wrong python syntax for integer value comparison
- Revert "wifi: ath6k: silence false positive -Wno-dangling-pointer warning
on
GCC 12"
- net: dsa: microchip: KSZ9477 register regmap alignment to 32 bit
boundaries
- net: annotate data-races around sk->sk_{rcv|snd}timeo
- net: usb: qmi_wwan: add Quectel EM05GV2
- wifi: brcmfmac: Fix field-spanning write in brcmf_scan_params_v2_to_v1()
- powerpc/powermac: Use early_* IO variants in via_calibrate_decr()
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- platform/x86/amd/pmf: Fix unsigned comparison with less than zero
- scsi: lpfc: Remove reftag check in DIF paths
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- net: hns3: restore user pause configure when disable autoneg
- drm/amdgpu: Match against exact bootloader status
- wifi: cfg80211: remove links only on AP
- wifi: mac80211: Use active_links instead of valid_links in Tx
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- cifs: fix sockaddr comparison in iface_cmp
- cifs: fix max_credits implementation
- sctp: handle invalid error codes without calling BUG()
- scsi: aacraid: Reply queue mapping to CPUs based on IRQ affinity
- scsi: storvsc: Always set no_report_opcodes
- scsi: lpfc: Fix incorrect big endian type assignment in bsg loopback path
- LoongArch: Let pmd_present() return true when splitting pmd
- LoongArch: Fix the write_fcsr() macro
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- net: sfp: handle 100G/25G active optical cables in sfp_parse_sup
[Kernel-packages] [Bug 2035313] Re: Fix non-working I219 after system sleep
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1023.23
---
linux-oem-6.1 (6.1.0-1023.23) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1023.23 -proposed tracker (LP: #2033827)
* Jammy update: v6.1.53 upstream stable release (LP: #2035359)
- Revert "bridge: Add extack warning when enabling STP in netns."
- Partially revert "drm/amd/display: Fix possible underflow for displays
with
large vblank"
- scsi: ufs: Try harder to change the power mode
- Revert "Revert drm/amd/display: Enable Freesync Video Mode by default"
- ARM: dts: imx: Set default tuning step for imx7d usdhc
- powerpc/boot: Disable power10 features after BOOTAFLAGS assignment
- media: uapi: HEVC: Add num_delta_pocs_of_ref_rps_idx field
- Revert "MIPS: unhide PATA_PLATFORM"
- phy: qcom-snps-femto-v2: use qcom_snps_hsphy_suspend/resume error code
- media: amphion: use dev_err_probe
- media: pulse8-cec: handle possible ping error
- media: pci: cx23885: fix error handling for cx23885 ATSC boards
- 9p: virtio: fix unlikely null pointer deref in handle_rerror
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ksmbd: fix out of bounds in smb3_decrypt_req()
- ksmbd: validate session id and tree id in compound request
- ksmbd: no response from compound read
- ksmbd: fix out of bounds in init_smb2_rsp_hdr()
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ASoC: nau8821: Add DMI quirk mechanism for active-high jack-detect
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoC: rt5682-sdw: fix for JD event handling in ClockStop Mode0
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: rt711: fix for JD event handling in ClockStop Mode0
- ASoC: rt711-sdca: fix for JD event handling in ClockStop Mode0
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- ALSA: usb-audio: Add quirk for Microsoft Modern Wireless Headset
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86/intel/hid: Add HP Dragonfly G2 to VGBS DMI quirks
- platform/x86: think-lmi: Use kfree_sensitive instead of kfree
- platform/x86: asus-wmi: Fix setting RGB mode on some TUF laptops
- platform/x86: huawei-wmi: Silence ambient light sensor
- drm/amd/smu: use AverageGfxclkFrequency* to replace previous GFX Curr
Clock
- drm/amd/display: Guard DCN31 PHYD32CLK logic against chip family
- drm/amd/display: Exit idle optimizations before attempt to access PHY
- ovl: Always reevaluate the file signature for IMA
- ata: pata_arasan_cf: Use dev_err_probe() instead dev_err() in data_xfer()
- ALSA: usb-audio: Update for native DSD support quirks
- staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER
- security: keys: perform capable check only on privileged operations
- kprobes: Prohibit probing on CFI preamble symbol
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- vmbus_testing: fix wrong python syntax for integer value comparison
- Revert "wifi: ath6k: silence false positive -Wno-dangling-pointer warning
on
GCC 12"
- net: dsa: microchip: KSZ9477 register regmap alignment to 32 bit
boundaries
- net: annotate data-races around sk->sk_{rcv|snd}timeo
- net: usb: qmi_wwan: add Quectel EM05GV2
- wifi: brcmfmac: Fix field-spanning write in brcmf_scan_params_v2_to_v1()
- powerpc/powermac: Use early_* IO variants in via_calibrate_decr()
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- platform/x86/amd/pmf: Fix unsigned comparison with less than zero
- scsi: lpfc: Remove reftag check in DIF paths
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- net: hns3: restore user pause configure when disable autoneg
- drm/amdgpu: Match against exact bootloader status
- wifi: cfg80211: remove links only on AP
- wifi: mac80211: Use active_links instead of valid_links in Tx
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- cifs: fix sockaddr comparison in iface_cmp
- cifs: fix max_credits implementation
- sctp: handle invalid error codes without calling BUG()
- scsi: aacraid: Reply queue mapping to CPUs based on IRQ affinity
- scsi: storvsc: Always set no_report_opcodes
- scsi: lpfc: Fix incorrect big endian type assignment in bsg loopback path
- LoongArch: Let pmd_present() return true when splitting pmd
- LoongArch: Fix the write_fcsr() macro
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- net: sfp: handle 100G/25G active optical cables in sfp_parse_sup
[Kernel-packages] [Bug 2035116] Re: allow io_uring to be disabled in runtime
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1023.23
---
linux-oem-6.1 (6.1.0-1023.23) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1023.23 -proposed tracker (LP: #2033827)
* Jammy update: v6.1.53 upstream stable release (LP: #2035359)
- Revert "bridge: Add extack warning when enabling STP in netns."
- Partially revert "drm/amd/display: Fix possible underflow for displays
with
large vblank"
- scsi: ufs: Try harder to change the power mode
- Revert "Revert drm/amd/display: Enable Freesync Video Mode by default"
- ARM: dts: imx: Set default tuning step for imx7d usdhc
- powerpc/boot: Disable power10 features after BOOTAFLAGS assignment
- media: uapi: HEVC: Add num_delta_pocs_of_ref_rps_idx field
- Revert "MIPS: unhide PATA_PLATFORM"
- phy: qcom-snps-femto-v2: use qcom_snps_hsphy_suspend/resume error code
- media: amphion: use dev_err_probe
- media: pulse8-cec: handle possible ping error
- media: pci: cx23885: fix error handling for cx23885 ATSC boards
- 9p: virtio: fix unlikely null pointer deref in handle_rerror
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ksmbd: fix out of bounds in smb3_decrypt_req()
- ksmbd: validate session id and tree id in compound request
- ksmbd: no response from compound read
- ksmbd: fix out of bounds in init_smb2_rsp_hdr()
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ASoC: nau8821: Add DMI quirk mechanism for active-high jack-detect
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoC: rt5682-sdw: fix for JD event handling in ClockStop Mode0
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: rt711: fix for JD event handling in ClockStop Mode0
- ASoC: rt711-sdca: fix for JD event handling in ClockStop Mode0
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- ALSA: usb-audio: Add quirk for Microsoft Modern Wireless Headset
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86/intel/hid: Add HP Dragonfly G2 to VGBS DMI quirks
- platform/x86: think-lmi: Use kfree_sensitive instead of kfree
- platform/x86: asus-wmi: Fix setting RGB mode on some TUF laptops
- platform/x86: huawei-wmi: Silence ambient light sensor
- drm/amd/smu: use AverageGfxclkFrequency* to replace previous GFX Curr
Clock
- drm/amd/display: Guard DCN31 PHYD32CLK logic against chip family
- drm/amd/display: Exit idle optimizations before attempt to access PHY
- ovl: Always reevaluate the file signature for IMA
- ata: pata_arasan_cf: Use dev_err_probe() instead dev_err() in data_xfer()
- ALSA: usb-audio: Update for native DSD support quirks
- staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER
- security: keys: perform capable check only on privileged operations
- kprobes: Prohibit probing on CFI preamble symbol
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- vmbus_testing: fix wrong python syntax for integer value comparison
- Revert "wifi: ath6k: silence false positive -Wno-dangling-pointer warning
on
GCC 12"
- net: dsa: microchip: KSZ9477 register regmap alignment to 32 bit
boundaries
- net: annotate data-races around sk->sk_{rcv|snd}timeo
- net: usb: qmi_wwan: add Quectel EM05GV2
- wifi: brcmfmac: Fix field-spanning write in brcmf_scan_params_v2_to_v1()
- powerpc/powermac: Use early_* IO variants in via_calibrate_decr()
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- platform/x86/amd/pmf: Fix unsigned comparison with less than zero
- scsi: lpfc: Remove reftag check in DIF paths
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- net: hns3: restore user pause configure when disable autoneg
- drm/amdgpu: Match against exact bootloader status
- wifi: cfg80211: remove links only on AP
- wifi: mac80211: Use active_links instead of valid_links in Tx
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- cifs: fix sockaddr comparison in iface_cmp
- cifs: fix max_credits implementation
- sctp: handle invalid error codes without calling BUG()
- scsi: aacraid: Reply queue mapping to CPUs based on IRQ affinity
- scsi: storvsc: Always set no_report_opcodes
- scsi: lpfc: Fix incorrect big endian type assignment in bsg loopback path
- LoongArch: Let pmd_present() return true when splitting pmd
- LoongArch: Fix the write_fcsr() macro
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- net: sfp: handle 100G/25G active optical cables in sfp_parse_sup
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1023.23
---
linux-oem-6.1 (6.1.0-1023.23) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1023.23 -proposed tracker (LP: #2033827)
* Jammy update: v6.1.53 upstream stable release (LP: #2035359)
- Revert "bridge: Add extack warning when enabling STP in netns."
- Partially revert "drm/amd/display: Fix possible underflow for displays
with
large vblank"
- scsi: ufs: Try harder to change the power mode
- Revert "Revert drm/amd/display: Enable Freesync Video Mode by default"
- ARM: dts: imx: Set default tuning step for imx7d usdhc
- powerpc/boot: Disable power10 features after BOOTAFLAGS assignment
- media: uapi: HEVC: Add num_delta_pocs_of_ref_rps_idx field
- Revert "MIPS: unhide PATA_PLATFORM"
- phy: qcom-snps-femto-v2: use qcom_snps_hsphy_suspend/resume error code
- media: amphion: use dev_err_probe
- media: pulse8-cec: handle possible ping error
- media: pci: cx23885: fix error handling for cx23885 ATSC boards
- 9p: virtio: fix unlikely null pointer deref in handle_rerror
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ksmbd: fix out of bounds in smb3_decrypt_req()
- ksmbd: validate session id and tree id in compound request
- ksmbd: no response from compound read
- ksmbd: fix out of bounds in init_smb2_rsp_hdr()
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ASoC: nau8821: Add DMI quirk mechanism for active-high jack-detect
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoC: rt5682-sdw: fix for JD event handling in ClockStop Mode0
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: rt711: fix for JD event handling in ClockStop Mode0
- ASoC: rt711-sdca: fix for JD event handling in ClockStop Mode0
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- ALSA: usb-audio: Add quirk for Microsoft Modern Wireless Headset
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86/intel/hid: Add HP Dragonfly G2 to VGBS DMI quirks
- platform/x86: think-lmi: Use kfree_sensitive instead of kfree
- platform/x86: asus-wmi: Fix setting RGB mode on some TUF laptops
- platform/x86: huawei-wmi: Silence ambient light sensor
- drm/amd/smu: use AverageGfxclkFrequency* to replace previous GFX Curr
Clock
- drm/amd/display: Guard DCN31 PHYD32CLK logic against chip family
- drm/amd/display: Exit idle optimizations before attempt to access PHY
- ovl: Always reevaluate the file signature for IMA
- ata: pata_arasan_cf: Use dev_err_probe() instead dev_err() in data_xfer()
- ALSA: usb-audio: Update for native DSD support quirks
- staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER
- security: keys: perform capable check only on privileged operations
- kprobes: Prohibit probing on CFI preamble symbol
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- vmbus_testing: fix wrong python syntax for integer value comparison
- Revert "wifi: ath6k: silence false positive -Wno-dangling-pointer warning
on
GCC 12"
- net: dsa: microchip: KSZ9477 register regmap alignment to 32 bit
boundaries
- net: annotate data-races around sk->sk_{rcv|snd}timeo
- net: usb: qmi_wwan: add Quectel EM05GV2
- wifi: brcmfmac: Fix field-spanning write in brcmf_scan_params_v2_to_v1()
- powerpc/powermac: Use early_* IO variants in via_calibrate_decr()
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- platform/x86/amd/pmf: Fix unsigned comparison with less than zero
- scsi: lpfc: Remove reftag check in DIF paths
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- net: hns3: restore user pause configure when disable autoneg
- drm/amdgpu: Match against exact bootloader status
- wifi: cfg80211: remove links only on AP
- wifi: mac80211: Use active_links instead of valid_links in Tx
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- cifs: fix sockaddr comparison in iface_cmp
- cifs: fix max_credits implementation
- sctp: handle invalid error codes without calling BUG()
- scsi: aacraid: Reply queue mapping to CPUs based on IRQ affinity
- scsi: storvsc: Always set no_report_opcodes
- scsi: lpfc: Fix incorrect big endian type assignment in bsg loopback path
- LoongArch: Let pmd_present() return true when splitting pmd
- LoongArch: Fix the write_fcsr() macro
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- net: sfp: handle 100G/25G active optical cables in sfp_parse_sup
[Kernel-packages] [Bug 2038437] Re: mantic:linux ubuntu_qrt_kernel_security.KernelSecurityTest.test_082_stack_guard_kernel: Could not find a suitable kernel module to test
Patch in attach (against qa-regression-testing) allows to fix this issue. ** Patch added: "0001-scripts-test-kernel-security.py-support-zstd-compres.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038437/+attachment/5706797/+files/0001-scripts-test-kernel-security.py-support-zstd-compres.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038437 Title: mantic:linux ubuntu_qrt_kernel_security.KernelSecurityTest.test_082_stack_guard_kernel: Could not find a suitable kernel module to test Status in linux package in Ubuntu: Triaged Status in linux source package in Mantic: Triaged Bug description: Running the ubuntu_qrt_kernel_security suite as part of the linux (selftest) suite produces the following error: stdout: Running test: './test-kernel-security.py' distro: 'Ubuntu 23.10' kernel: '6.5.0-7.7 (Ubuntu 6.5.0-7.7-generic 6.5.3)' arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu') stderr: test_082_stack_guard_kernel (__main__.KernelSecurityTest.test_082_stack_guard_kernel) Kernel stack guard ... FAIL == FAIL: test_082_stack_guard_kernel (__main__.KernelSecurityTest.test_082_stack_guard_kernel) Kernel stack guard -- Traceback (most recent call last): File "/tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 758, in test_082_stack_guard_kernel self.assertTrue(module, 'Could not find a suitable kernel module to test') AssertionError: '' is not true : Could not find a suitable kernel module to test There is no clear indication which module(s) are attempted but probably those got renamed or this is due to compressing the modules resulting in different filename extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035359] Re: Jammy update: v6.1.53 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1023.23
---
linux-oem-6.1 (6.1.0-1023.23) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1023.23 -proposed tracker (LP: #2033827)
* Jammy update: v6.1.53 upstream stable release (LP: #2035359)
- Revert "bridge: Add extack warning when enabling STP in netns."
- Partially revert "drm/amd/display: Fix possible underflow for displays
with
large vblank"
- scsi: ufs: Try harder to change the power mode
- Revert "Revert drm/amd/display: Enable Freesync Video Mode by default"
- ARM: dts: imx: Set default tuning step for imx7d usdhc
- powerpc/boot: Disable power10 features after BOOTAFLAGS assignment
- media: uapi: HEVC: Add num_delta_pocs_of_ref_rps_idx field
- Revert "MIPS: unhide PATA_PLATFORM"
- phy: qcom-snps-femto-v2: use qcom_snps_hsphy_suspend/resume error code
- media: amphion: use dev_err_probe
- media: pulse8-cec: handle possible ping error
- media: pci: cx23885: fix error handling for cx23885 ATSC boards
- 9p: virtio: fix unlikely null pointer deref in handle_rerror
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ksmbd: fix out of bounds in smb3_decrypt_req()
- ksmbd: validate session id and tree id in compound request
- ksmbd: no response from compound read
- ksmbd: fix out of bounds in init_smb2_rsp_hdr()
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ASoC: nau8821: Add DMI quirk mechanism for active-high jack-detect
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoC: rt5682-sdw: fix for JD event handling in ClockStop Mode0
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: rt711: fix for JD event handling in ClockStop Mode0
- ASoC: rt711-sdca: fix for JD event handling in ClockStop Mode0
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- ALSA: usb-audio: Add quirk for Microsoft Modern Wireless Headset
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86/intel/hid: Add HP Dragonfly G2 to VGBS DMI quirks
- platform/x86: think-lmi: Use kfree_sensitive instead of kfree
- platform/x86: asus-wmi: Fix setting RGB mode on some TUF laptops
- platform/x86: huawei-wmi: Silence ambient light sensor
- drm/amd/smu: use AverageGfxclkFrequency* to replace previous GFX Curr
Clock
- drm/amd/display: Guard DCN31 PHYD32CLK logic against chip family
- drm/amd/display: Exit idle optimizations before attempt to access PHY
- ovl: Always reevaluate the file signature for IMA
- ata: pata_arasan_cf: Use dev_err_probe() instead dev_err() in data_xfer()
- ALSA: usb-audio: Update for native DSD support quirks
- staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER
- security: keys: perform capable check only on privileged operations
- kprobes: Prohibit probing on CFI preamble symbol
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- vmbus_testing: fix wrong python syntax for integer value comparison
- Revert "wifi: ath6k: silence false positive -Wno-dangling-pointer warning
on
GCC 12"
- net: dsa: microchip: KSZ9477 register regmap alignment to 32 bit
boundaries
- net: annotate data-races around sk->sk_{rcv|snd}timeo
- net: usb: qmi_wwan: add Quectel EM05GV2
- wifi: brcmfmac: Fix field-spanning write in brcmf_scan_params_v2_to_v1()
- powerpc/powermac: Use early_* IO variants in via_calibrate_decr()
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- platform/x86/amd/pmf: Fix unsigned comparison with less than zero
- scsi: lpfc: Remove reftag check in DIF paths
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- net: hns3: restore user pause configure when disable autoneg
- drm/amdgpu: Match against exact bootloader status
- wifi: cfg80211: remove links only on AP
- wifi: mac80211: Use active_links instead of valid_links in Tx
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- cifs: fix sockaddr comparison in iface_cmp
- cifs: fix max_credits implementation
- sctp: handle invalid error codes without calling BUG()
- scsi: aacraid: Reply queue mapping to CPUs based on IRQ affinity
- scsi: storvsc: Always set no_report_opcodes
- scsi: lpfc: Fix incorrect big endian type assignment in bsg loopback path
- LoongArch: Let pmd_present() return true when splitting pmd
- LoongArch: Fix the write_fcsr() macro
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- net: sfp: handle 100G/25G active optical cables in sfp_parse_sup
[Kernel-packages] [Bug 2037417] [NEW] mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
You have been subscribed to a public bug: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: maas-images Importance: Undecided Status: New ** Affects: ubuntu-power-systems Importance: Undecided Status: Confirmed ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed -- mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems https://bugs.launchpad.net/bugs/2037417 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033642] Re: Jammy update: v6.1.47 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1023.23
---
linux-oem-6.1 (6.1.0-1023.23) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1023.23 -proposed tracker (LP: #2033827)
* Jammy update: v6.1.53 upstream stable release (LP: #2035359)
- Revert "bridge: Add extack warning when enabling STP in netns."
- Partially revert "drm/amd/display: Fix possible underflow for displays
with
large vblank"
- scsi: ufs: Try harder to change the power mode
- Revert "Revert drm/amd/display: Enable Freesync Video Mode by default"
- ARM: dts: imx: Set default tuning step for imx7d usdhc
- powerpc/boot: Disable power10 features after BOOTAFLAGS assignment
- media: uapi: HEVC: Add num_delta_pocs_of_ref_rps_idx field
- Revert "MIPS: unhide PATA_PLATFORM"
- phy: qcom-snps-femto-v2: use qcom_snps_hsphy_suspend/resume error code
- media: amphion: use dev_err_probe
- media: pulse8-cec: handle possible ping error
- media: pci: cx23885: fix error handling for cx23885 ATSC boards
- 9p: virtio: fix unlikely null pointer deref in handle_rerror
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ksmbd: fix out of bounds in smb3_decrypt_req()
- ksmbd: validate session id and tree id in compound request
- ksmbd: no response from compound read
- ksmbd: fix out of bounds in init_smb2_rsp_hdr()
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ASoC: nau8821: Add DMI quirk mechanism for active-high jack-detect
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoC: rt5682-sdw: fix for JD event handling in ClockStop Mode0
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: rt711: fix for JD event handling in ClockStop Mode0
- ASoC: rt711-sdca: fix for JD event handling in ClockStop Mode0
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- ALSA: usb-audio: Add quirk for Microsoft Modern Wireless Headset
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86/intel/hid: Add HP Dragonfly G2 to VGBS DMI quirks
- platform/x86: think-lmi: Use kfree_sensitive instead of kfree
- platform/x86: asus-wmi: Fix setting RGB mode on some TUF laptops
- platform/x86: huawei-wmi: Silence ambient light sensor
- drm/amd/smu: use AverageGfxclkFrequency* to replace previous GFX Curr
Clock
- drm/amd/display: Guard DCN31 PHYD32CLK logic against chip family
- drm/amd/display: Exit idle optimizations before attempt to access PHY
- ovl: Always reevaluate the file signature for IMA
- ata: pata_arasan_cf: Use dev_err_probe() instead dev_err() in data_xfer()
- ALSA: usb-audio: Update for native DSD support quirks
- staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER
- security: keys: perform capable check only on privileged operations
- kprobes: Prohibit probing on CFI preamble symbol
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- vmbus_testing: fix wrong python syntax for integer value comparison
- Revert "wifi: ath6k: silence false positive -Wno-dangling-pointer warning
on
GCC 12"
- net: dsa: microchip: KSZ9477 register regmap alignment to 32 bit
boundaries
- net: annotate data-races around sk->sk_{rcv|snd}timeo
- net: usb: qmi_wwan: add Quectel EM05GV2
- wifi: brcmfmac: Fix field-spanning write in brcmf_scan_params_v2_to_v1()
- powerpc/powermac: Use early_* IO variants in via_calibrate_decr()
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- platform/x86/amd/pmf: Fix unsigned comparison with less than zero
- scsi: lpfc: Remove reftag check in DIF paths
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- net: hns3: restore user pause configure when disable autoneg
- drm/amdgpu: Match against exact bootloader status
- wifi: cfg80211: remove links only on AP
- wifi: mac80211: Use active_links instead of valid_links in Tx
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- cifs: fix sockaddr comparison in iface_cmp
- cifs: fix max_credits implementation
- sctp: handle invalid error codes without calling BUG()
- scsi: aacraid: Reply queue mapping to CPUs based on IRQ affinity
- scsi: storvsc: Always set no_report_opcodes
- scsi: lpfc: Fix incorrect big endian type assignment in bsg loopback path
- LoongArch: Let pmd_present() return true when splitting pmd
- LoongArch: Fix the write_fcsr() macro
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- net: sfp: handle 100G/25G active optical cables in sfp_parse_sup
[Kernel-packages] [Bug 2035116] Re: allow io_uring to be disabled in runtime
** Changed in: linux (Ubuntu Jammy) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2035116 Title: allow io_uring to be disabled in runtime Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] io_uring has been an important attack vector in the recent years in local privilege escalation attacks. Allowing admins that don't use io_uring to disable it in their systems allows them to reduce their attack surface. [Test case] sysctl -w kernel.io_uring_disabled=1 then try to use io_uring from an unprivileged user, then try it with privileges (CAP_SYS_ADMIN) Actually also tried setting kernel.io_uring_disabled=2 and checking that neither (privileged or unprivileged worked). Then testing setting it back to 0. Then tested with io_uring_disabled set to 1 and io_uring_group=1000 and that it worked for group 1000, then set it to 1001 and verified that it didn't work anymore for group 1000. [Potential regression] Uses can be denied from using io_uring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019024] Re: Migrate oem-5.17 and oem-6.0 to oem-6.1
This bug was fixed in the package linux-restricted-modules-oem-6.1 - 6.1.0-1023.23+3 --- linux-restricted-modules-oem-6.1 (6.1.0-1023.23+3) jammy; urgency=medium * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (adhoc/2023.09.04) -- Andy Whitcroft Wed, 27 Sep 2023 10:55:17 +0100 ** Changed in: linux-restricted-modules-oem-6.1 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-meta-oem-6.1 (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2019024 Title: Migrate oem-5.17 and oem-6.0 to oem-6.1 Status in linux-meta-oem-6.1 package in Ubuntu: Invalid Status in linux-restricted-modules-oem-6.1 package in Ubuntu: Invalid Status in linux-meta-oem-6.1 source package in Jammy: Fix Released Status in linux-restricted-modules-oem-6.1 source package in Jammy: Fix Released Bug description: [Impact] Migrate oem-5.17 and oem-6.0 to oem-6.1 now that there should be no functional regressions left anymore. [Test case] Update a machine with oem-5.17/oem-6.0 metapackages to the proposed ones, and verify that all packages (including nvidia etc) migrate properly. [Where things could go wrong] In theory we might miss a package to transition, but at this point this is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-6.1/+bug/2019024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019024] Re: Migrate oem-5.17 and oem-6.0 to oem-6.1
This bug was fixed in the package linux-meta-oem-6.1 - 6.1.0.1023.24 --- linux-meta-oem-6.1 (6.1.0.1023.24) jammy; urgency=medium * Migrate oem-5.17 and oem-6.0 to oem-6.1 (LP: #2019024) - [Packaging] Migrate oem-22.04a and oem-22.04b to oem-22.04c -- Timo Aaltonen Tue, 19 Sep 2023 11:23:27 +0300 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2019024 Title: Migrate oem-5.17 and oem-6.0 to oem-6.1 Status in linux-meta-oem-6.1 package in Ubuntu: Invalid Status in linux-restricted-modules-oem-6.1 package in Ubuntu: Invalid Status in linux-meta-oem-6.1 source package in Jammy: Fix Released Status in linux-restricted-modules-oem-6.1 source package in Jammy: Fix Released Bug description: [Impact] Migrate oem-5.17 and oem-6.0 to oem-6.1 now that there should be no functional regressions left anymore. [Test case] Update a machine with oem-5.17/oem-6.0 metapackages to the proposed ones, and verify that all packages (including nvidia etc) migrate properly. [Where things could go wrong] In theory we might miss a package to transition, but at this point this is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-6.1/+bug/2019024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038437] Re: mantic:linux ubuntu_qrt_kernel_security.KernelSecurityTest.test_082_stack_guard_kernel: Could not find a suitable kernel module to test
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038437 Title: mantic:linux ubuntu_qrt_kernel_security.KernelSecurityTest.test_082_stack_guard_kernel: Could not find a suitable kernel module to test Status in linux package in Ubuntu: Triaged Status in linux source package in Mantic: Triaged Bug description: Running the ubuntu_qrt_kernel_security suite as part of the linux (selftest) suite produces the following error: stdout: Running test: './test-kernel-security.py' distro: 'Ubuntu 23.10' kernel: '6.5.0-7.7 (Ubuntu 6.5.0-7.7-generic 6.5.3)' arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu') stderr: test_082_stack_guard_kernel (__main__.KernelSecurityTest.test_082_stack_guard_kernel) Kernel stack guard ... FAIL == FAIL: test_082_stack_guard_kernel (__main__.KernelSecurityTest.test_082_stack_guard_kernel) Kernel stack guard -- Traceback (most recent call last): File "/tmp/autopkgtest.Si3gP4/build.moT/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 758, in test_082_stack_guard_kernel self.assertTrue(module, 'Could not find a suitable kernel module to test') AssertionError: '' is not true : Could not find a suitable kernel module to test There is no clear indication which module(s) are attempted but probably those got renamed or this is due to compressing the modules resulting in different filename extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2030049] Re: v4l2 driver fails with "Unknown pixelformat 0x00000000"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2030049 Title: v4l2 driver fails with "Unknown pixelformat 0x" Status in linux-meta package in Ubuntu: Confirmed Bug description: [ 8550.165027] Unknown pixelformat 0x [ 8550.165044] WARNING: CPU: 2 PID: 22808 at drivers/media/v4l2-core/v4l2-ioctl.c:1500 v4l_fill_fmtdesc+0x1968/0x1990 [videodev] [ 8550.165056] Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_realtek sunrpc binfmt_misc snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi iwlmvm snd_hda_codec snd_usb_audio intel_rapl_msr snd_hda_core intel_rapl_common snd_usbmidi_lib snd_hwdep edac_mce_amd mac80211 snd_pcm kvm_amd snd_seq_midi snd_seq_midi_event asus_ec_sensors nls_iso8859_1 libarc4 snd_rawmidi btusb kvm uvcvideo btrtl snd_seq btbcm videobuf2_vmalloc btintel videobuf2_memops irqbypass snd_seq_device btmtk videobuf2_v4l2 rapl snd_timer bluetooth iwlwifi videodev snd videobuf2_common ecdh_generic eeepc_wmi wmi_bmof mxm_wmi k10temp ccp input_leds joydev mc soundcore cfg80211 ecc nvidia_uvm(POE) mac_hid sch_fq_codel msr parport_pc ppdev lp parport ramoops pstore_blk reed_solomon pstore_zone efi_pstore ip_tables x_tables autofs4 dm_crypt hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) [ 8550.165087] mfd_aaeon drm_kms_helper asus_wmi crct10dif_pclmul syscopyarea ledtrig_audio crc32_pclmul sysfillrect sparse_keymap polyval_clmulni sysimgblt polyval_generic ghash_clmulni_intel sha512_ssse3 aesni_intel platform_profile drm crypto_simd cryptd igb nvme r8169 ahci xhci_pci i2c_piix4 video libahci dca xhci_pci_renesas realtek i2c_algo_bit nvme_core nvme_common wmi [ 8550.165099] CPU: 2 PID: 22808 Comm: brave Tainted: PW OE 6.2.0-26-generic #26~22.04.1-Ubuntu [ 8550.165101] Hardware name: ASUS System Product Name/ROG CROSSHAIR VIII DARK HERO, BIOS 4402 02/03/2023 [ 8550.165102] RIP: 0010:v4l_fill_fmtdesc+0x1968/0x1990 [videodev] [ 8550.165110] Code: ff ff bb 01 00 00 00 49 c7 c4 da 82 50 c4 e9 42 e7 ff ff 41 80 7d 0c 00 0f 85 81 e7 ff ff 48 c7 c7 2c 84 50 c4 e8 08 27 60 e0 <0f> 0b be 20 00 00 00 49 8d 4d 2c 49 8d 7d 0c 31 db 48 c7 c2 48 84 [ 8550.165111] RSP: 0018:b741104ffbd8 EFLAGS: 00010246 [ 8550.165113] RAX: RBX: c474ad60 RCX: [ 8550.165113] RDX: RSI: RDI: [ 8550.165114] RBP: b741104ffbf8 R08: R09: [ 8550.165114] R10: R11: R12: b741104ffd30 [ 8550.165115] R13: b741104ffd30 R14: 8a0df371f300 R15: 8a0dab340018 [ 8550.165116] FS: 7f813006e2c0() GS:8a148ea8() knlGS: [ 8550.165117] CS: 0010 DS: ES: CR0: 80050033 [ 8550.165117] CR2: 115c08fe3c5c CR3: 000138386000 CR4: 00750ee0 [ 8550.165118] PKRU: 5554 [ 8550.165119] Call Trace: [ 8550.165119] [ 8550.165122] v4l_enum_fmt+0x1b4/0x1f0 [videodev] [ 8550.165130] __video_do_ioctl+0x1c2/0x5b0 [videodev] [ 8550.165137] ? __check_object_size.part.0+0x3a/0x150 [ 8550.165141] ? video_get_user.constprop.0+0x17d/0x1e0 [videodev] [ 8550.165148] video_usercopy+0x210/0x760 [videodev] [ 8550.165156] ? __pfx___video_do_ioctl+0x10/0x10 [videodev] [ 8550.165164] video_ioctl2+0x15/0x30 [videodev] [ 8550.165171] v4l2_ioctl+0x6c/0xb0 [videodev] [ 8550.165179] __x64_sys_ioctl+0x9d/0xe0 [ 8550.165181] do_syscall_64+0x5c/0x90 [ 8550.165183] ? syscall_exit_to_user_mode+0x2a/0x50 [ 8550.165184] ? do_syscall_64+0x69/0x90 [ 8550.165186] ? exit_to_user_mode_prepare+0x3b/0xd0 [ 8550.165188] ? syscall_exit_to_user_mode+0x2a/0x50 [ 8550.165189] ? do_syscall_64+0x69/0x90 [ 8550.165190] ? syscall_exit_to_user_mode+0x2a/0x50 [ 8550.165191] ? do_syscall_64+0x69/0x90 [ 8550.165192] ? do_syscall_64+0x69/0x90 [ 8550.165193] ? do_syscall_64+0x69/0x90 [ 8550.165194] ? do_syscall_64+0x69/0x90 [ 8550.165195] ? do_syscall_64+0x69/0x90 [ 8550.165196] entry_SYSCALL_64_after_hwframe+0x72/0xdc [ 8550.165199] RIP: 0033:0x7f813111aaff [ 8550.165200] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00 [ 8550.165200] RSP: 002b:7ffcf47c23f0 EFLAGS: 0246 ORIG_RAX: 0010 [ 8550.165202] RAX: ffda RBX: 0018 RCX: 7f813111aaff [ 8550.165202] RDX: 7ffcf47c2470 RSI: c0405602 RDI: 0018
[Kernel-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in linux source package in Mantic: New Status in systemd source package in Mantic: Confirmed Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
** Project changed: linux => linux (Ubuntu) ** Changed in: linux (Ubuntu) Milestone: None => ubuntu-23.10 ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Mantic) Importance: Undecided Status: 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/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in linux source package in Mantic: New Status in systemd source package in Mantic: Confirmed Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037417] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2037417 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in linux source package in Mantic: Incomplete Status in systemd source package in Mantic: Confirmed Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Hello Endre, I have written email to Rayen to consider this bug status change and requested to let us know about the solution. Regards, Pradip Kumar Das -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Fix Released Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038467] [NEW] package linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-33-generic package pre-removal script subprocess r
Public bug reported: package linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-33-generic package pre- removal script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 4 23:41:30 2023 ErrorMessage: installed linux-image-6.2.0-33-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2023-07-30 (66 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: linux-signed-hwe-6.2 Title: package linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-33-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038467 Title: package linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-33-generic package pre- removal script subprocess returned error exit status 1 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: package linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-33-generic package pre- removal script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 4 23:41:30 2023 ErrorMessage: installed linux-image-6.2.0-33-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2023-07-30 (66 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: linux-signed-hwe-6.2 Title: package linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-33-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038469] [NEW] Kernel does not boot, stays at "Loading initial ramdisk..."
Public bug reported: Kernel 6.2.0-26 works Kernel 6.2.0-32 does not boot Kernel 6.2.0-33 does not boot Kernel 6.2.0-34 does not boot Steps to reproduce: 1. Select kernel in grub, boot Result: Screen shows "Loading initial ramdisk..." forever, system does not boot. Envirement: Lenovo Thinkbook with AMD Ryzen CPU and GPU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Oct 4 20:41:25 2023 InstallationDate: Installed on 2022-04-08 (544 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220408) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038469 Title: Kernel does not boot, stays at "Loading initial ramdisk..." Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Kernel 6.2.0-26 works Kernel 6.2.0-32 does not boot Kernel 6.2.0-33 does not boot Kernel 6.2.0-34 does not boot Steps to reproduce: 1. Select kernel in grub, boot Result: Screen shows "Loading initial ramdisk..." forever, system does not boot. Envirement: Lenovo Thinkbook with AMD Ryzen CPU and GPU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Oct 4 20:41:25 2023 InstallationDate: Installed on 2022-04-08 (544 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220408) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037789] Re: I must plug an external keyboard+mouse on Lenovo V15 Gen 4
One more update this (european) evening. Still no change "Device" file updated ** Attachment added: "devices" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2037789/+attachment/5706815/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2037789 Title: I must plug an external keyboard+mouse on Lenovo V15 Gen 4 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Hello everyone, I'm Jean-Marie, my journey with linux has just started. So I can't use my touchpad and keyboard on this new Lenovo V15 Gen 4 "cat /proc/bus/input/devices" doesn't show "I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio2/input0 S: Sysfs=/devices/platform/i8042/serio2/input/input8 U: Uniq= H: Handlers=mouse2 event8 B: EV=b B: KEY=420 0 7 0 0 0 0 0 0 0 0 B: ABS=1103" but instead of it I get "I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:08/LNXVIDEO:00/input/input3 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=046d Product=c077 Version=0111 N: Name="Logitech USB Optical Mouse" P: Phys=usb-:04:00.4-2/input0 S: Sysfs=/devices/pci:00/:00:08.1/:04:00.4/usb3/3-2/3-2:1.0/0003:046D:C077.0003/input/input7 U: Uniq= H: Handlers=mouse0 event6 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:14.3/PNP0C09:00/VPC2004:00/input/input8 U: Uniq= H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=13 B: KEY=8000 1000 0 81000800100c03 44300400 0 2 B: MSC=10 I: Bus=0003 Vendor=5986 Product=2160 Version=5806 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:05:00.0-1/button S: Sysfs=/devices/pci:00/:00:08.3/:05:00.0/usb5/5-1/5-1:1.0/input/input9 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.1/sound/card0/input10 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.1/sound/card0/input11 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.6/sound/card1/input12 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.6/sound/card1/input13 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0003 Vendor=04ca Product=007d Version=0111 N: Name="Liteon Technology Corp. USB wired keyboard" P: Phys=usb-:04:00.4-1/input0 S: Sysfs=/devices/pci:00/:00:08.1/:04:00.4/usb3/3-1/3-1:1.0/0003:04CA:007D.0004/input/input14 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=04ca Product=007d Version=0111 N: Name="Liteon Technology Corp. USB wired keyboard Consumer Control" P: Phys=usb-:04:00.4-1/input1 S: Sysfs=/devices/pci:00/:00:08.1/:04:00.4/usb3/3-1/3-1:1.1/0003:04CA:007D.0005/input/input15 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=1f B: KEY=33eff 0 0 48317aff32d bfd6 1 130c730b17c000 267bfad9415fed 9e16804400 1002 B: REL=1040 B: ABS=1 B: MSC=10 I: Bus=0003 Vendor=04ca Product=007d Version=0111 N: Name="Liteon Technology Corp. USB wired keyboard System Control" P: Phys=usb-:04:00.4-1/input1 S: Sysfs=/devices/pci:00/:00:08.1/:04:00.4/usb3/3-1/3-1:1.1/0
[Kernel-packages] [Bug 2037672] Re: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen
Also - can you still repro with mesa 23.2.1-1ubuntu2? This just landed right after you reported this issue. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: Confirmed => 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/2037672 Title: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Incomplete Bug description: Hi, Switching a video to or from fullscreen freezes the screen for around 10 seconds. This happens with Totem as well as VLC so its not related to a specific app. Additional observations: - The issue seems to be connected to the video's bitrate. With low bitrate videos I cannot trigger the freeze. However, videos with high bandwidth trigger the freeze reliably. Specs: Ubuntu 23.10 up to date as of 28.09.2023 AMD Ryzen 7 PRO 6850U Kernel 6.5.0-5-generic Grub configured with: amdgpu.vm_update_mode=3 Syslog shows: 2023-09-28T20:02:29.803955+02:00 kernel: [27003.800898] amdgpu :04:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32771, for process Xwayland pid 2113 thread Xwayland:cs0 pid 2311) 2023-09-28T20:02:39.975854+02:00 kernel: [27013.972772] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
I believe reproducer is: wget https://images.maas.io/ephemeral-v3/candidate/mantic/amd64/20231004.1/ga-23.10/generic/boot-kernel wget https://images.maas.io/ephemeral-v3/candidate/mantic/amd64/20231004.1/ga-23.10/generic/boot-initrd qemu-system-x86_64 -m 4G -smp 2 -nic user,model=virtio-net-pci -kernel boot-kernel -initrd boot-initrd --append 'ip=dhcp root=squash:http://images.maas.io/ephemeral-v3/candidate/mantic/amd64/20231004.1/squashfs overlayroot=tmpfs overlayroot_cfgdisk=disabled systemd.log_level=debug systemd.log_target=console systemd.journald.forward_to_console=1 debug=y' for faster download you might want to have squashfs on local lan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in linux source package in Mantic: Incomplete Status in systemd source package in Mantic: Confirmed Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Hi Pradip, if Rayen is not in any team to fix the issue, how can he decide if it is solved or not? I think there is an issue how the workflows are running. There should be a solution explained and then confirmed by at least a few affected users or by time if at least one confirmation is given that the fix is working. Now somebody is saying the fix issued, but nobody else knows what is that and how to apply. My computer is still not having the fix. I cannot find such a kernel, called linux.signed-hwe-6.2 or I am looking for it at a wrong place. But thanks for trying to get this to the right direction. Kind regards Endre -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Fix Released Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 41624] Re: Replaying journals of other OS's filesystems, by mounting them, is unsafe
Over a decade later... but this might help someone. There is a way around this mess, with some caveats. You can set the block device to readonly using blockdev. This works as desired a lot of the time. However, sometimes (or perhaps everytime certain filesystems need to replay the journal), the will cause the kernel to refuse to mount the filesystem. The way around this is to, as mentioned above, replay the journal to ram. As far as I know, no filesystems support this natively. What can be done is to use dm-snapshot to create a snapshot of the block device with the cow file residing on a tmpfs. Then mount the snapshot device's filesystem as readonly. In this case the log will be replayed to ram. The caveat here is that, when in this state, the underlying block device should not be written to. So effectively the block device is locked up until the snapshot device is removed. A scenario where this might be an issue is as follows. You have a harddrive with isos on an ext4 filesystem that you use to grub iso loopback mount to boot from. When booting one of the isos, you use the snapshot setup with this filesystem because you don't know if its part of a hibernation image or not. When the livecd is up and running, you will not be able to modify the filesystem (you can write to it, but all changes are in ram and will be lost). That's as it should be if the filesystem is part of a hibernation image, but it might be more likely that its not. And in that case, it might be confusing why this restriction exists. What would be good is to have code that can detect if the system has a hibernation image or even better if the filesystem was mounted while a hibernation happened (not sure if that's possible). Then the snapshot work around could be done only when needed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/41624 Title: Replaying journals of other OS's filesystems, by mounting them, is unsafe Status in iso-scan package in Ubuntu: Triaged Status in linux package in Ubuntu: Won't Fix Status in lupin package in Ubuntu: Triaged Status in partman-basicfilesystems package in Ubuntu: Fix Released Status in os-prober package in Debian: Fix Released Bug description: I have just done a clean install of recent dapper (20060426.1 live i386) on my main testbed machine. The automatic volume discovery system has not only found the filesystems from various of the other installations (which is not quite so bad) but has dug into my LVM system and found the fs for a frozen Xen image ! This kind of thing can cause serious data loss. Modern journalling filesystems go even more badly wrong than traditional fs's if they are accessed by two running systems in an interleaved fashion, which is what results if Dapper automatically finds and mounts these filesystems, replaying the journal, while a frozen (whether by a VM like Xen or by ordinary hibernation) image has them mounted. In the current setup I think it would be easy to cause disaster simply by installing dapper twice on the same machine and then continuously hibernating one while using the other. More complex schemes are also possible. All of these filesystems discovered in this way should be made read- only unless it can be somehow known that it's safe to make them r/w. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iso-scan/+bug/41624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
** Tags added: foundaitions-todo ** Tags removed: foundaitions-todo ** Tags added: foundations-todo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in linux source package in Mantic: Incomplete Status in systemd source package in Mantic: Confirmed Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
I accidentally changed the status and can't revert it back to 'confirmed.' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Fix Released Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
btw this problem persists even in the latest kernel version 6.5 on Ubuntu 23.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Fix Released Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2030872] Re: Azure: hv_netvsc: add support for vlans in AF_PACKET mode
This bug is awaiting verification that the linux-azure/5.4.0-1118.125 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-azure' to 'verification-done-focal- linux-azure'. If the problem still exists, change the tag 'verification- needed-focal-linux-azure' to 'verification-failed-focal-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-azure-v2 verification-needed-focal-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2030872 Title: Azure: hv_netvsc: add support for vlans in AF_PACKET mode Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification [Impact] Microsoft has requested the inclusion of [1] into the Focal Azure kernel. [1] - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fdd8fac47ce67bae17feed9b74b3505e432fe561 [Test Plan] Microsoft Tested [Regression potential] Could affect 802.1Q packets [Other Info] SF: #00365836 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030872/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022361] Re: Please enable Renesas RZ platform serial installer
This bug is awaiting verification that the linux-azure/5.4.0-1118.125
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-azure' to 'verification-done-focal-
linux-azure'. If the problem still exists, change the tag 'verification-
needed-focal-linux-azure' to 'verification-failed-focal-linux-azure'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux-azure-v2
verification-needed-focal-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2022361
Title:
Please enable Renesas RZ platform serial installer
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
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
The ubuntu installer does not work via serial ports for Renesas boards like
RZ/G2M-HiHope
(https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board,
RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board
(https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC).
The installation can be done using HDMI ports, but it would be nice to
support installation via serial port as well.
[Test case]
Try to install Ubuntu on a Renesas board.
[Fix]
Statically build SuperH SCI(F) serial port support (with
earlyconsole).
[Regression potential]
Statically building an additional driver in the kernel can make the
kernel image bigger, potentially causing boot issues in small (arm64 /
armhf) platforms.
[Original bug report]
Package: linux
Version: Ubuntu-6.2.0-21.21
Severity: normal
File: /mantic/debian.master/config/annotations
Dear Maintainer,
The ubuntu kernel is missing a few configuration options for Renesas
RZ/G2M MPU as below:
#Modify the following config from m to y.
CONFIG_SERIAL_SH_SCI=y
#add below configuration
CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_SERIAL_SH_SCI_EARLYCON=y
The above changes are required in annotations file:
"/mantic/debian.master/config/annotations"
code location:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372
#Modify the following line (change 'm' to 'y')
CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>
#Add the following lines:
CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>
Could you please add those configuration options to the Ubuntu kernel?
Best Regards
John
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022361/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted
This bug is awaiting verification that the linux-azure/5.4.0-1118.125 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-azure' to 'verification-done-focal- linux-azure'. If the problem still exists, change the tag 'verification- needed-focal-linux-azure' to 'verification-failed-focal-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-azure-v2 verification-needed-focal-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837227 Title: systemd mount units fail during boot, while file system is correctly mounted Status in systemd: New Status in Ubuntu Pro: In Progress Status in Ubuntu Pro 18.04 series: In Progress Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in systemd source package in Bionic: Won't Fix Status in linux source package in Focal: Fix Released Status in systemd source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] systemd mount units fail during boot, and the system boots into emergency mode [Test Plan] This issue seems to happen randomly, and doesn't seem related to a specific mount unit. We've used a test script with good results during investigation to reproduce similar mount failures in a running system, and have seen a strong correlation between the script failures and the boot time mount failures. The attached 'rep-tmpfs.sh' script should be used to validate that mount points are working correctly under stress. One can run through the different variants as below: # ./rep-tmpfs.sh --variant-0 # ./rep-tmpfs.sh --variant-1 # ./rep-tmpfs.sh --variant-2 # ./rep-tmpfs.sh --variant-3 # ./rep-tmpfs.sh --variant-4 All of these should run successfully without any reported errors. [Where problems could occur] The patches change the way systemd tracks and handles mount points in general, so potential regressions could affect other mount units. We should keep an eye out for any issues with mounting file systems, as well as rapid mount/unmount operations. Successful test runs with the reproducer script should increase reliability in having no new regressions. [Other Info] This has been tackled upstream with several attempts, which have resulted in the final patch from 2022: 01400460ae16 core/mount: adjust deserialized state based on /proc/self/mountinfo For Bionic, systemd requires several dependency patches as below: 6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a new unit cycle 7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the other way round 350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() results 1d086a6e5972 mount: mark an existing "mounting" unit from /proc/self/mountinfo as "just_mounted" Additionally, the kernel also requires the following patches: 28ca0d6d39ab list: introduce list_for_each_continue() 9f6c61f96f2d proc/mounts: add cursor [Original Description] In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode with a failed mount unit (ext4 file system), while the corresponding file system is in fact correctly mounted. It happens roughly once every 1000 reboots. It seems to be related with this bug : https://github.com/systemd/systemd/issues/10872 Is it possible to apply the fix (https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21) in Ubuntu 18.04 ? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1837227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038486] [NEW] Jammy update: v5.15.128 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.128 upstream stable release from git://git.kernel.org/ mmc: sdhci-f-sdh30: Replace with sdhci_pltfm selftests: forwarding: tc_actions: cleanup temporary files when test is aborted selftests: forwarding: tc_actions: Use ncat instead of nc macsec: Fix traffic counters/statistics macsec: use DEV_STATS_INC() net/tls: Perform immediate device ctx cleanup when possible net/tls: Multi-threaded calls to TX tls_dev_del net: tls: avoid discarding data on record close PCI: tegra194: Fix possible array out of bounds access ARM: dts: imx6dl: prtrvt, prtvt7, prti6q, prtwd2: fix USB related warnings iopoll: Call cpu_relax() in busy loops ASoC: SOF: Intel: fix SoundWire/HDaudio mutual exclusion dma-remap: use kvmalloc_array/kvfree for larger dma memory remap HID: logitech-hidpp: Add USB and Bluetooth IDs for the Logitech G915 TKL Keyboard HID: add quirk for 03f0:464a HP Elite Presenter Mouse RDMA/mlx5: Return the firmware result upon destroying QP/RQ ovl: check type and offset of struct vfsmount in ovl_entry smb: client: fix warning in cifs_smb3_do_mount() media: v4l2-mem2mem: add lock to protect parameter num_rdy usb: gadget: u_serial: Avoid spinlock recursion in __gs_console_push media: platform: mediatek: vpu: fix NULL ptr dereference thunderbolt: Read retimer NVM authentication status prior tb_retimer_set_inbound_sbtx() usb: chipidea: imx: don't request QoS for imx8ulp usb: chipidea: imx: add missing USB PHY DPDM wakeup setting gfs2: Fix possible data races in gfs2_show_options() pcmcia: rsrc_nonstatic: Fix memory leak in nonstatic_release_resource_db() firewire: net: fix use after free in fwnet_finish_incoming_packet() watchdog: sp5100_tco: support Hygon FCH/SCH (Server Controller Hub) Bluetooth: L2CAP: Fix use-after-free Bluetooth: btusb: Add MT7922 bluetooth ID for the Asus Ally drm/amdgpu: Fix potential fence use-after-free v2 fs/ntfs3: Enhance sanity check while generating attr_list fs: ntfs3: Fix possible null-pointer dereferences in mi_read() fs/ntfs3: Mark ntfs dirty when on-disk struct is corrupted ALSA: hda/realtek: Add quirks for Unis H3C Desktop B760 & Q760 ALSA: hda: fix a possible null-pointer dereference due to data race in snd_hdac_regmap_sync() powerpc/kasan: Disable KCOV in KASAN code ring-buffer: Do not swap cpu_buffer during resize process iio: add addac subdirectory iio: adc: stx104: Utilize iomap interface iio: adc: stx104: Implement and utilize register structures iio: stx104: Move to addac subdirectory iio: addac: stx104: Fix race condition for stx104_write_raw() iio: addac: stx104: Fix race condition when converting analog-to-digital igc: read before write to SRRCTL register ARM: dts: aspeed: asrock: Correct firmware flash SPI clocks drm/amd/display: save restore hdcp state when display is unplugged from mst hub drm/amd/display: phase3 mst hdcp for multiple displays drm/amd/display: fix access hdcp_workqueue assert usb: dwc3: gadget: Synchronize IRQ between soft connect/disconnect usb: dwc3: Remove DWC3 locking during gadget suspend/resume usb: dwc3: Fix typos in gadget.c USB: dwc3: gadget: drop dead hibernation code usb: dwc3: gadget: Improve dwc3_gadget_suspend() and dwc3_gadget_resume() tty: serial: fsl_lpuart: Add i.MXRT1050 support tty: serial: fsl_lpuart: make rx_watermark configurable for different platforms tty: serial: fsl_lpuart: reduce RX watermark to 0 on LS1028A USB: dwc3: qcom: fix NULL-deref on suspend USB: dwc3: fix use-after-free on core driver unbind mmc: bcm2835: fix deferred probing mmc: sunxi: fix deferred probing ARM: dts: imx6sll: fixup of operating points ARM: dts: nxp/imx6sll: fix wrong property name in usbphy node btrfs: move out now unused BG from the reclaim list virtio-mmio: don't break lifecycle of vm_dev vduse: Use proper spinlock for IRQ injection cifs: fix potential oops in cifs_oplock_break i2c: bcm-iproc: Fix bcm_iproc_i2c_isr deadlock issue i2c: hisi: Only handle the interrupt of the driver's transfer fbdev: mmp: fix value check in mmphw_probe() powerpc/rtas_flash: allow user copy to flash block cache objects tty: n_gsm: fix the UAF caused by race condition in gsm_cleanup_mux tty: serial: fsl_lpuart: Clear the error flags by writing 1 for lpuart32 platforms btrfs: fix BUG_ON condition in btrfs_cancel_balance i2c: designware: Correct length byte validation logic i2c: designware: Handle invalid SMBus block data response length value net: xfrm: Fix xfrm_address_filter OOB read net: af_key: fix sadb_x_filter validation net: xfrm: Amend XFRMA_SEC_CTX nla_policy structure xfrm: f
[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
** Also affects: linux-oem-6.5 (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/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!
Those messages are not displayed when I boot my system with a mainline Linux
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where
such a message could be printed.
Therefore, those messages are probably caused by an Ubuntu patch.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bonnaudl 4827 F wireplumber
/dev/snd/seq:bonnaudl 4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
** Changed in: linux-oem-6.5 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!
Those messages are not displayed when I boot my system with a mainline Linux
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where
such a message could be printed.
Therefore, those messages are probably caused by an Ubuntu patch.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bonnaudl 4827 F wireplumber
/dev/snd/seq:bonnaudl 4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
** Also affects: util-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/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: New Status in linux source package in Mantic: Incomplete Status in systemd source package in Mantic: Confirmed Status in util-linux source package in Mantic: New Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
So the cause of this, I am fairly sure, is the new "libmount-mountfd" support in util-linux which seems to have the consequence that "mount -o remount $mountpoint" fails for an overlay that references paths no longer available in the current mount namespace. You can see the discussion of a similar-but-not-the-same issue here https://github.com/util-linux/util-linux/issues/1992 I'm trying to come up with a reproducer but I have to head afk now. I'll file a bug upstream when I get that done. Maybe we should build util-linux with --disable-libmount-mountfd-support for now (bit late in the release cycle to be uploading util-linux though...) ** Bug watch added: github.com/util-linux/util-linux/issues #1992 https://github.com/util-linux/util-linux/issues/1992 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: New Status in linux source package in Mantic: Incomplete Status in systemd source package in Mantic: Confirmed Status in util-linux source package in Mantic: New Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970389] Re: [nvidia] Janky text entry and frames appear out of order in Xwayland apps
** No longer affects: nvidia-graphics-drivers-510 (Ubuntu) ** No longer affects: nvidia-graphics-drivers-525 (Ubuntu) ** No longer affects: nvidia-graphics-drivers-535 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/1970389 Title: [nvidia] Janky text entry and frames appear out of order in Xwayland apps Status in X.Org X server: New Status in xwayland package in Ubuntu: Triaged Bug description: When writing into text fields in some applications (Firefox, VS Code) on Jammy in a GNOME / Wayland session, I can see an effect best described as the glyphs appearing / disappearing sometimes repeatedly. I have attached a recording from my phone (since attempting to record a screencast fails). This doesn't happen always, and it appear somehow sensitive to some environmental condition (load?) since for example when I'm on a video call, the effect seems to not be happening so often. I have also experienced a few instances of a currently not-focused window disappearing (seeing through to a window that is below that window), but cannot reproduce that reliably. I have the NVIDIA driver 510 in use, RTX3090-only 16-core Zen1 Threadripper system with no integrated GPU. No similar effects visible when in a GNOME / Xorg session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 12:17:02 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-08 (168 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-22 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1970389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978905] Re: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports)
** No longer affects: nvidia-graphics-drivers-510 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1978905 Title: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports) Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports) This is different to the usual dual GPU setup where Intel is primary and Nvidia is secondary. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1978905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016933] Re: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU
** No longer affects: nvidia-graphics-drivers-530 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-530 in Ubuntu. https://bugs.launchpad.net/bugs/2016933 Title: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU Status in xwayland package in Ubuntu: New Bug description: On Wayland only, offloading works for `glxinfo` but cannot run 3D app like X-Plane 11: $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep "OpenGL vendor string" OpenGL vendor string: NVIDIA Corporation $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./X-Plane\ 11/X-Plane-x86_64 Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 04:30:34 2023 InstallationDate: Installed on 2023-01-04 (104 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2016933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Hi Pradip, as you have issued this bug report, could you reset it to confirmed somehow or issue a new bug report, please? There many people who have effected by this bug. I think most of the AMD 6000 and 7000 series laptops from some specific manufacturer. Lot of discussion forums having the same issue mentioned, but no solution so far. Thanks Endre -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Fix Released Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
Ah no it's a bit simpler than that https://github.com/util-linux/util- linux/issues/2528. --disable-libmount-mountfd-support looking better tbh. ** Bug watch added: github.com/util-linux/util-linux/issues #2528 https://github.com/util-linux/util-linux/issues/2528 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: New Status in linux source package in Mantic: Incomplete Status in systemd source package in Mantic: Confirmed Status in util-linux source package in Mantic: New Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
Unfortunately the problem is still reproducible even with the newest mesa, even though it looks like it's much less frequent. Yesterday evening I got another crash, with mesa 23.2.1-1ubuntu2: ``` 2023-10-04T22:33:15.415854+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119146] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:4 pasid:32770, for process Xwayland pid 4940 thread Xwayland:cs0 pid 5015) 2023-10-04T22:33:15.415871+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119168] amdgpu :06:00.0: amdgpu: in page starting at address 0xe5ea2326e000 from IH client 0x1b (UTCL2) 2023-10-04T22:33:15.415873+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119180] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00400430 2023-10-04T22:33:15.415874+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119187] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-10-04T22:33:15.415875+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119194] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x0 2023-10-04T22:33:15.415876+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119200] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-10-04T22:33:15.415878+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119206] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-10-04T22:33:15.415878+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119212] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-10-04T22:33:15.415879+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119218] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-10-04T22:33:15.415881+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119750] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:4 pasid:32770, for process Xwayland pid 4940 thread Xwayland:cs0 pid 5015) 2023-10-04T22:33:15.415881+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119768] amdgpu :06:00.0: amdgpu: in page starting at address 0xe5ea2326f000 from IH client 0x1b (UTCL2) 2023-10-04T22:33:15.415883+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119780] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00400430 2023-10-04T22:33:15.415884+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119787] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-10-04T22:33:15.415885+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119793] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x0 2023-10-04T22:33:15.415885+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119800] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-10-04T22:33:15.415886+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119806] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-10-04T22:33:15.415887+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119812] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-10-04T22:33:15.415888+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119818] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-10-04T22:33:25.115577+03:00 mavi-ThinkPad-T14s kernel: [ 1085.820288] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_low timeout, signaled seq=75561, emitted seq=75563 2023-10-04T22:33:25.115600+03:00 mavi-ThinkPad-T14s kernel: [ 1085.821169] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 4940 thread Xwayland:cs0 pid 5015 2023-10-04T22:33:25.115602+03:00 mavi-ThinkPad-T14s kernel: [ 1085.822031] amdgpu :06:00.0: amdgpu: GPU reset begin! 2023-10-04T22:33:25.347547+03:00 mavi-ThinkPad-T14s kernel: [ 1086.052065] [drm] psp gfx command UNLOAD_TA(0x2) failed and response status is (0x117) 2023-10-04T22:33:25.375820+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078048] amdgpu :06:00.0: amdgpu: MODE2 reset 2023-10-04T22:33:25.375835+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078296] amdgpu :06:00.0: amdgpu: GPU reset succeeded, trying to resume 2023-10-04T22:33:25.375837+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078498] [drm] PCIE GART of 1024M enabled. 2023-10-04T22:33:25.375838+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078503] [drm] PTB located at 0x00F43FC0 2023-10-04T22:33:25.375839+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078625] [drm] PSP is resuming... 2023-10-04T22:33:26.075542+03:00 mavi-ThinkPad-T14s kernel: [ 1086.780162] [drm] reserve 0x40 from 0xf43f80 for PSP TMR 2023-10-04T22:33:26.363527+03:00 mavi-ThinkPad-T14s kernel: [ 1087.066834] amdgpu :06:00.0: amdgpu: RAS: optional ras ta ucode is not available 2023-10-04T22:33:26.375796+03:00 mavi-ThinkPad-T14s kernel: [ 1087.078189] amdgpu :06:00.0: amdgpu: RAP: optional rap ta ucode is not available 2023-10-04T22:33:26.375806+03:00 mavi-ThinkPad-T14s kernel: [ 1087.078196] amdgpu :06:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available 2023-10-04T22:33:26.375808+03:00 mavi-ThinkPad-T14s kernel: [ 1087.078204] amdgpu :06:00.0: amdgpu: SMU is resuming... 2023-10-04T22:33:26.375809+03:00 mavi-ThinkPad-T14s kernel: [ 1087.079063] amdgpu :06:00.0: amdgpu: SMU is resumed succ
[Kernel-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
The process is Intellij IDEA, running on Java 17 in Xwayland. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037641 Title: amdgpu: [gfxhub0] no-retry page fault Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Bug description: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. The setup: the machine is connected to an external monitor via USB-C. Running kernel 6.5 on Ubuntu 23.10. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206588] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206592] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077726+03:00 mavi-ThinkPad-T14s kernel: [ 422.206597] amd
[Kernel-packages] [Bug 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
The firmware introduce the issue, https://bugs.launchpad.net/somerville/+bug/2036493, mark it as failed. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-failed verification-failed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Triaged Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: SRU Jusitification for firmware-sof [Impact] To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 [Fix] Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too [Test Case] Install the fixes on the target platform(RPL Dell SKU 0BDA) and verify the audio function. 1. Install the firmware-sof on platform(RPL) with Audio Smart AMP IC ALC1319D 2. Make sure the audio works 3. Also try above steps on other platforms(ADL/TGL) to make sure the audio keep working. [Where problems could occur] New firmware may affect ADL, RPL, and TGL platforms, we need to verify it on not only the target platform, but other existing platforms. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
