[Kernel-packages] [Bug 2037501] [NEW] Bluetooth hci0: timeout waiting for suspend events
Public bug reported: If the laptop is suspended with Bluetooth on then sometimes it is stuck on black screen with the following text. Bluetooth hci0: timeout waiting for suspend events there were also a few other lines similar to this. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-84-generic 5.15.0-84.93 ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116 Uname: Linux 5.15.0-84-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pbtron 2646 F pulseaudio /dev/snd/pcmC2D0p: pbtron 2646 F...m pulseaudio /dev/snd/controlC0: pbtron 2646 F pulseaudio /dev/snd/controlC1: pbtron 2646 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 11:07:07 2023 MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA506II_FA566II ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=UUID=cce780b5-b701-430e-9c7f-acf732a00af2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-84-generic N/A linux-backports-modules-5.15.0-84-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.18 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506II.316 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506II dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.12 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506II.316:bd03/12/2021:br5.16:efr3.12:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA15FA506II_FA566II:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506II:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming A15 dmi.product.name: ASUS TUF Gaming A15 FA506II_FA566II dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/2037501 Title: Bluetooth hci0: timeout waiting for suspend events Status in linux package in Ubuntu: New Bug description: If the laptop is suspended with Bluetooth on then sometimes it is stuck on black screen with the following text. Bluetooth hci0: timeout waiting for suspend events there were also a few other lines similar to this. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-84-generic 5.15.0-84.93 ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116 Uname: Linux 5.15.0-84-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pbtron 2646 F pulseaudio /dev/snd/pcmC2D0p: pbtron 2646 F...m pulseaudio /dev/snd/controlC0: pbtron 2646 F pulseaudio /dev/snd/controlC1: pbtron 2646 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 11:07:07 2023 MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA506II_FA566II ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=UUID=cce780b5-b701-430e-9c7f-acf732a00af2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-84-generic N/A linux-backports-modules-5.15.0-84-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.18 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506II.316 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506II dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.12 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506II.316:bd03/12/2021:br5.16:efr3.12:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA15FA506II_FA566II:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506II:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming A15 dmi.product.name: ASUS TUF Gaming A15 FA506II_FA566II dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[Kernel-packages] [Bug 2037490] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2037490/+attachment/5704779/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037490
Title:
"call trace" is reported for mptsas driver
Status in linux package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce:
1. install a ubuntu 23.10 VM on an ESXi Server
2. hot add a lsilogicsas controller and a lsilogicsas disk
Call Trace will be reported in dmesg log
[ 176.181166]
[ 176.181167] UBSAN: array-index-out-of-bounds in
/build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22
[ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA
[1]'
[ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted
6.5.0-5-generic #5-Ubuntu
[ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference
Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023
[ 176.181179] Call Trace:
[ 176.181181]
[ 176.181183] dump_stack_lvl+0x48/0x70
[ 176.181228] dump_stack+0x10/0x20
[ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas]
[ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas]
[ 176.181257] ? __pfx_scsi_runtime_idle+0x10/0x10
[ 176.181264] ? rpm_idle+0x1dc/0x2b0
[ 176.181269] mptsas_scan_sas_topology+0x32/0x210 [mptsas]
[ 176.181277] ? scsi_autopm_put_host+0x1a/0x30
[ 176.181280] mptsas_probe.part.0+0x3cc/0x570 [mptsas]
[ 176.181289] mptsas_probe+0x1e/0x30 [mptsas]
[ 176.181298] local_pci_probe+0x44/0xb0
[ 176.181302] pci_call_probe+0x55/0x190
[ 176.181307] pci_device_probe+0x84/0x120
[ 176.181312] really_probe+0x1c4/0x410
[ 176.181316] __driver_probe_device+0x8c/0x180
[ 176.181320] driver_probe_device+0x24/0xd0
[ 176.181324] __driver_attach+0x10b/0x210
[ 176.181327] ? __pfx___driver_attach+0x10/0x10
[ 176.181330] bus_for_each_dev+0x8a/0xf0
[ 176.181333] driver_attach+0x1e/0x30
[ 176.181336] bus_add_driver+0x127/0x240
[ 176.181340] driver_register+0x5e/0x130
[ 176.181343] ? __pfx_mptsas_init+0x10/0x10 [mptsas]
[ 176.181352] __pci_register_driver+0x62/0x70
[ 176.181356] mptsas_init+0x119/0xff0 [mptsas]
[ 176.181365] do_one_initcall+0x5b/0x340
[ 176.181371] do_init_module+0x68/0x260
[ 176.181375] load_module+0xba1/0xcf0
[ 176.181380] ? vfree+0xff/0x2d0
[ 176.181385] init_module_from_file+0x96/0x100
[ 176.181388] ? init_module_from_file+0x96/0x100
[ 176.181394] idempotent_init_module+0x11c/0x2b0
[ 176.181399] __x64_sys_finit_module+0x64/0xd0
[ 176.181402] do_syscall_64+0x59/0x90
[ 176.181409] ? exit_to_user_mode_prepare+0x30/0xb0
[ 176.181413] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181417] ? do_syscall_64+0x68/0x90
[ 176.181421] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181424] ? do_syscall_64+0x68/0x90
[ 176.181428] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 176.181432] RIP: 0033:0x7f847a725c5d
[ 176.181441] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48
[ 176.181481] RSP: 002b:7fff6734e878 EFLAGS: 0246 ORIG_RAX:
0139
[ 176.181484] RAX: ffda RBX: 563ba212a6b0 RCX:
7f847a725c5d
[ 176.181486] RDX: 0004 RSI: 7f847aa0144a RDI:
000d
[ 176.181488] RBP: 7f847aa0144a R08: 0040 R09:
fde0
[ 176.181490] R10: fe18 R11: 0246 R12:
0002
[ 176.181526] R13: 563ba2216ae0 R14: R15:
563ba20dff90
[ 176.181531]
[ 176.181532]
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:vmware 950 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-09-26 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0
[Kernel-packages] [Bug 2037490] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2037490/+attachment/5704778/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037490
Title:
"call trace" is reported for mptsas driver
Status in linux package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce:
1. install a ubuntu 23.10 VM on an ESXi Server
2. hot add a lsilogicsas controller and a lsilogicsas disk
Call Trace will be reported in dmesg log
[ 176.181166]
[ 176.181167] UBSAN: array-index-out-of-bounds in
/build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22
[ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA
[1]'
[ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted
6.5.0-5-generic #5-Ubuntu
[ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference
Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023
[ 176.181179] Call Trace:
[ 176.181181]
[ 176.181183] dump_stack_lvl+0x48/0x70
[ 176.181228] dump_stack+0x10/0x20
[ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas]
[ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas]
[ 176.181257] ? __pfx_scsi_runtime_idle+0x10/0x10
[ 176.181264] ? rpm_idle+0x1dc/0x2b0
[ 176.181269] mptsas_scan_sas_topology+0x32/0x210 [mptsas]
[ 176.181277] ? scsi_autopm_put_host+0x1a/0x30
[ 176.181280] mptsas_probe.part.0+0x3cc/0x570 [mptsas]
[ 176.181289] mptsas_probe+0x1e/0x30 [mptsas]
[ 176.181298] local_pci_probe+0x44/0xb0
[ 176.181302] pci_call_probe+0x55/0x190
[ 176.181307] pci_device_probe+0x84/0x120
[ 176.181312] really_probe+0x1c4/0x410
[ 176.181316] __driver_probe_device+0x8c/0x180
[ 176.181320] driver_probe_device+0x24/0xd0
[ 176.181324] __driver_attach+0x10b/0x210
[ 176.181327] ? __pfx___driver_attach+0x10/0x10
[ 176.181330] bus_for_each_dev+0x8a/0xf0
[ 176.181333] driver_attach+0x1e/0x30
[ 176.181336] bus_add_driver+0x127/0x240
[ 176.181340] driver_register+0x5e/0x130
[ 176.181343] ? __pfx_mptsas_init+0x10/0x10 [mptsas]
[ 176.181352] __pci_register_driver+0x62/0x70
[ 176.181356] mptsas_init+0x119/0xff0 [mptsas]
[ 176.181365] do_one_initcall+0x5b/0x340
[ 176.181371] do_init_module+0x68/0x260
[ 176.181375] load_module+0xba1/0xcf0
[ 176.181380] ? vfree+0xff/0x2d0
[ 176.181385] init_module_from_file+0x96/0x100
[ 176.181388] ? init_module_from_file+0x96/0x100
[ 176.181394] idempotent_init_module+0x11c/0x2b0
[ 176.181399] __x64_sys_finit_module+0x64/0xd0
[ 176.181402] do_syscall_64+0x59/0x90
[ 176.181409] ? exit_to_user_mode_prepare+0x30/0xb0
[ 176.181413] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181417] ? do_syscall_64+0x68/0x90
[ 176.181421] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181424] ? do_syscall_64+0x68/0x90
[ 176.181428] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 176.181432] RIP: 0033:0x7f847a725c5d
[ 176.181441] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48
[ 176.181481] RSP: 002b:7fff6734e878 EFLAGS: 0246 ORIG_RAX:
0139
[ 176.181484] RAX: ffda RBX: 563ba212a6b0 RCX:
7f847a725c5d
[ 176.181486] RDX: 0004 RSI: 7f847aa0144a RDI:
000d
[ 176.181488] RBP: 7f847aa0144a R08: 0040 R09:
fde0
[ 176.181490] R10: fe18 R11: 0246 R12:
0002
[ 176.181526] R13: 563ba2216ae0 R14: R15:
563ba20dff90
[ 176.181531]
[ 176.181532]
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:vmware 950 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-09-26 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 vmwgfxdrmfb
[Kernel-packages] [Bug 2037490] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2037490/+attachment/5704777/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037490
Title:
"call trace" is reported for mptsas driver
Status in linux package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce:
1. install a ubuntu 23.10 VM on an ESXi Server
2. hot add a lsilogicsas controller and a lsilogicsas disk
Call Trace will be reported in dmesg log
[ 176.181166]
[ 176.181167] UBSAN: array-index-out-of-bounds in
/build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22
[ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA
[1]'
[ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted
6.5.0-5-generic #5-Ubuntu
[ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference
Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023
[ 176.181179] Call Trace:
[ 176.181181]
[ 176.181183] dump_stack_lvl+0x48/0x70
[ 176.181228] dump_stack+0x10/0x20
[ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas]
[ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas]
[ 176.181257] ? __pfx_scsi_runtime_idle+0x10/0x10
[ 176.181264] ? rpm_idle+0x1dc/0x2b0
[ 176.181269] mptsas_scan_sas_topology+0x32/0x210 [mptsas]
[ 176.181277] ? scsi_autopm_put_host+0x1a/0x30
[ 176.181280] mptsas_probe.part.0+0x3cc/0x570 [mptsas]
[ 176.181289] mptsas_probe+0x1e/0x30 [mptsas]
[ 176.181298] local_pci_probe+0x44/0xb0
[ 176.181302] pci_call_probe+0x55/0x190
[ 176.181307] pci_device_probe+0x84/0x120
[ 176.181312] really_probe+0x1c4/0x410
[ 176.181316] __driver_probe_device+0x8c/0x180
[ 176.181320] driver_probe_device+0x24/0xd0
[ 176.181324] __driver_attach+0x10b/0x210
[ 176.181327] ? __pfx___driver_attach+0x10/0x10
[ 176.181330] bus_for_each_dev+0x8a/0xf0
[ 176.181333] driver_attach+0x1e/0x30
[ 176.181336] bus_add_driver+0x127/0x240
[ 176.181340] driver_register+0x5e/0x130
[ 176.181343] ? __pfx_mptsas_init+0x10/0x10 [mptsas]
[ 176.181352] __pci_register_driver+0x62/0x70
[ 176.181356] mptsas_init+0x119/0xff0 [mptsas]
[ 176.181365] do_one_initcall+0x5b/0x340
[ 176.181371] do_init_module+0x68/0x260
[ 176.181375] load_module+0xba1/0xcf0
[ 176.181380] ? vfree+0xff/0x2d0
[ 176.181385] init_module_from_file+0x96/0x100
[ 176.181388] ? init_module_from_file+0x96/0x100
[ 176.181394] idempotent_init_module+0x11c/0x2b0
[ 176.181399] __x64_sys_finit_module+0x64/0xd0
[ 176.181402] do_syscall_64+0x59/0x90
[ 176.181409] ? exit_to_user_mode_prepare+0x30/0xb0
[ 176.181413] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181417] ? do_syscall_64+0x68/0x90
[ 176.181421] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181424] ? do_syscall_64+0x68/0x90
[ 176.181428] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 176.181432] RIP: 0033:0x7f847a725c5d
[ 176.181441] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48
[ 176.181481] RSP: 002b:7fff6734e878 EFLAGS: 0246 ORIG_RAX:
0139
[ 176.181484] RAX: ffda RBX: 563ba212a6b0 RCX:
7f847a725c5d
[ 176.181486] RDX: 0004 RSI: 7f847aa0144a RDI:
000d
[ 176.181488] RBP: 7f847aa0144a R08: 0040 R09:
fde0
[ 176.181490] R10: fe18 R11: 0246 R12:
0002
[ 176.181526] R13: 563ba2216ae0 R14: R15:
563ba20dff90
[ 176.181531]
[ 176.181532]
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:vmware 950 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-09-26 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0
[Kernel-packages] [Bug 2037490] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2037490/+attachment/5704780/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037490
Title:
"call trace" is reported for mptsas driver
Status in linux package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce:
1. install a ubuntu 23.10 VM on an ESXi Server
2. hot add a lsilogicsas controller and a lsilogicsas disk
Call Trace will be reported in dmesg log
[ 176.181166]
[ 176.181167] UBSAN: array-index-out-of-bounds in
/build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22
[ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA
[1]'
[ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted
6.5.0-5-generic #5-Ubuntu
[ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference
Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023
[ 176.181179] Call Trace:
[ 176.181181]
[ 176.181183] dump_stack_lvl+0x48/0x70
[ 176.181228] dump_stack+0x10/0x20
[ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas]
[ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas]
[ 176.181257] ? __pfx_scsi_runtime_idle+0x10/0x10
[ 176.181264] ? rpm_idle+0x1dc/0x2b0
[ 176.181269] mptsas_scan_sas_topology+0x32/0x210 [mptsas]
[ 176.181277] ? scsi_autopm_put_host+0x1a/0x30
[ 176.181280] mptsas_probe.part.0+0x3cc/0x570 [mptsas]
[ 176.181289] mptsas_probe+0x1e/0x30 [mptsas]
[ 176.181298] local_pci_probe+0x44/0xb0
[ 176.181302] pci_call_probe+0x55/0x190
[ 176.181307] pci_device_probe+0x84/0x120
[ 176.181312] really_probe+0x1c4/0x410
[ 176.181316] __driver_probe_device+0x8c/0x180
[ 176.181320] driver_probe_device+0x24/0xd0
[ 176.181324] __driver_attach+0x10b/0x210
[ 176.181327] ? __pfx___driver_attach+0x10/0x10
[ 176.181330] bus_for_each_dev+0x8a/0xf0
[ 176.181333] driver_attach+0x1e/0x30
[ 176.181336] bus_add_driver+0x127/0x240
[ 176.181340] driver_register+0x5e/0x130
[ 176.181343] ? __pfx_mptsas_init+0x10/0x10 [mptsas]
[ 176.181352] __pci_register_driver+0x62/0x70
[ 176.181356] mptsas_init+0x119/0xff0 [mptsas]
[ 176.181365] do_one_initcall+0x5b/0x340
[ 176.181371] do_init_module+0x68/0x260
[ 176.181375] load_module+0xba1/0xcf0
[ 176.181380] ? vfree+0xff/0x2d0
[ 176.181385] init_module_from_file+0x96/0x100
[ 176.181388] ? init_module_from_file+0x96/0x100
[ 176.181394] idempotent_init_module+0x11c/0x2b0
[ 176.181399] __x64_sys_finit_module+0x64/0xd0
[ 176.181402] do_syscall_64+0x59/0x90
[ 176.181409] ? exit_to_user_mode_prepare+0x30/0xb0
[ 176.181413] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181417] ? do_syscall_64+0x68/0x90
[ 176.181421] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181424] ? do_syscall_64+0x68/0x90
[ 176.181428] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 176.181432] RIP: 0033:0x7f847a725c5d
[ 176.181441] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48
[ 176.181481] RSP: 002b:7fff6734e878 EFLAGS: 0246 ORIG_RAX:
0139
[ 176.181484] RAX: ffda RBX: 563ba212a6b0 RCX:
7f847a725c5d
[ 176.181486] RDX: 0004 RSI: 7f847aa0144a RDI:
000d
[ 176.181488] RBP: 7f847aa0144a R08: 0040 R09:
fde0
[ 176.181490] R10: fe18 R11: 0246 R12:
0002
[ 176.181526] R13: 563ba2216ae0 R14: R15:
563ba20dff90
[ 176.181531]
[ 176.181532]
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:vmware 950 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-09-26 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom,
[Kernel-packages] [Bug 2037490] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2037490/+attachment/5704776/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037490
Title:
"call trace" is reported for mptsas driver
Status in linux package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce:
1. install a ubuntu 23.10 VM on an ESXi Server
2. hot add a lsilogicsas controller and a lsilogicsas disk
Call Trace will be reported in dmesg log
[ 176.181166]
[ 176.181167] UBSAN: array-index-out-of-bounds in
/build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22
[ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA
[1]'
[ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted
6.5.0-5-generic #5-Ubuntu
[ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference
Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023
[ 176.181179] Call Trace:
[ 176.181181]
[ 176.181183] dump_stack_lvl+0x48/0x70
[ 176.181228] dump_stack+0x10/0x20
[ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas]
[ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas]
[ 176.181257] ? __pfx_scsi_runtime_idle+0x10/0x10
[ 176.181264] ? rpm_idle+0x1dc/0x2b0
[ 176.181269] mptsas_scan_sas_topology+0x32/0x210 [mptsas]
[ 176.181277] ? scsi_autopm_put_host+0x1a/0x30
[ 176.181280] mptsas_probe.part.0+0x3cc/0x570 [mptsas]
[ 176.181289] mptsas_probe+0x1e/0x30 [mptsas]
[ 176.181298] local_pci_probe+0x44/0xb0
[ 176.181302] pci_call_probe+0x55/0x190
[ 176.181307] pci_device_probe+0x84/0x120
[ 176.181312] really_probe+0x1c4/0x410
[ 176.181316] __driver_probe_device+0x8c/0x180
[ 176.181320] driver_probe_device+0x24/0xd0
[ 176.181324] __driver_attach+0x10b/0x210
[ 176.181327] ? __pfx___driver_attach+0x10/0x10
[ 176.181330] bus_for_each_dev+0x8a/0xf0
[ 176.181333] driver_attach+0x1e/0x30
[ 176.181336] bus_add_driver+0x127/0x240
[ 176.181340] driver_register+0x5e/0x130
[ 176.181343] ? __pfx_mptsas_init+0x10/0x10 [mptsas]
[ 176.181352] __pci_register_driver+0x62/0x70
[ 176.181356] mptsas_init+0x119/0xff0 [mptsas]
[ 176.181365] do_one_initcall+0x5b/0x340
[ 176.181371] do_init_module+0x68/0x260
[ 176.181375] load_module+0xba1/0xcf0
[ 176.181380] ? vfree+0xff/0x2d0
[ 176.181385] init_module_from_file+0x96/0x100
[ 176.181388] ? init_module_from_file+0x96/0x100
[ 176.181394] idempotent_init_module+0x11c/0x2b0
[ 176.181399] __x64_sys_finit_module+0x64/0xd0
[ 176.181402] do_syscall_64+0x59/0x90
[ 176.181409] ? exit_to_user_mode_prepare+0x30/0xb0
[ 176.181413] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181417] ? do_syscall_64+0x68/0x90
[ 176.181421] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181424] ? do_syscall_64+0x68/0x90
[ 176.181428] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 176.181432] RIP: 0033:0x7f847a725c5d
[ 176.181441] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48
[ 176.181481] RSP: 002b:7fff6734e878 EFLAGS: 0246 ORIG_RAX:
0139
[ 176.181484] RAX: ffda RBX: 563ba212a6b0 RCX:
7f847a725c5d
[ 176.181486] RDX: 0004 RSI: 7f847aa0144a RDI:
000d
[ 176.181488] RBP: 7f847aa0144a R08: 0040 R09:
fde0
[ 176.181490] R10: fe18 R11: 0246 R12:
0002
[ 176.181526] R13: 563ba2216ae0 R14: R15:
563ba20dff90
[ 176.181531]
[ 176.181532]
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:vmware 950 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-09-26 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
[Kernel-packages] [Bug 2037490] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2037490/+attachment/5704775/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037490
Title:
"call trace" is reported for mptsas driver
Status in linux package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce:
1. install a ubuntu 23.10 VM on an ESXi Server
2. hot add a lsilogicsas controller and a lsilogicsas disk
Call Trace will be reported in dmesg log
[ 176.181166]
[ 176.181167] UBSAN: array-index-out-of-bounds in
/build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22
[ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA
[1]'
[ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted
6.5.0-5-generic #5-Ubuntu
[ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference
Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023
[ 176.181179] Call Trace:
[ 176.181181]
[ 176.181183] dump_stack_lvl+0x48/0x70
[ 176.181228] dump_stack+0x10/0x20
[ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas]
[ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas]
[ 176.181257] ? __pfx_scsi_runtime_idle+0x10/0x10
[ 176.181264] ? rpm_idle+0x1dc/0x2b0
[ 176.181269] mptsas_scan_sas_topology+0x32/0x210 [mptsas]
[ 176.181277] ? scsi_autopm_put_host+0x1a/0x30
[ 176.181280] mptsas_probe.part.0+0x3cc/0x570 [mptsas]
[ 176.181289] mptsas_probe+0x1e/0x30 [mptsas]
[ 176.181298] local_pci_probe+0x44/0xb0
[ 176.181302] pci_call_probe+0x55/0x190
[ 176.181307] pci_device_probe+0x84/0x120
[ 176.181312] really_probe+0x1c4/0x410
[ 176.181316] __driver_probe_device+0x8c/0x180
[ 176.181320] driver_probe_device+0x24/0xd0
[ 176.181324] __driver_attach+0x10b/0x210
[ 176.181327] ? __pfx___driver_attach+0x10/0x10
[ 176.181330] bus_for_each_dev+0x8a/0xf0
[ 176.181333] driver_attach+0x1e/0x30
[ 176.181336] bus_add_driver+0x127/0x240
[ 176.181340] driver_register+0x5e/0x130
[ 176.181343] ? __pfx_mptsas_init+0x10/0x10 [mptsas]
[ 176.181352] __pci_register_driver+0x62/0x70
[ 176.181356] mptsas_init+0x119/0xff0 [mptsas]
[ 176.181365] do_one_initcall+0x5b/0x340
[ 176.181371] do_init_module+0x68/0x260
[ 176.181375] load_module+0xba1/0xcf0
[ 176.181380] ? vfree+0xff/0x2d0
[ 176.181385] init_module_from_file+0x96/0x100
[ 176.181388] ? init_module_from_file+0x96/0x100
[ 176.181394] idempotent_init_module+0x11c/0x2b0
[ 176.181399] __x64_sys_finit_module+0x64/0xd0
[ 176.181402] do_syscall_64+0x59/0x90
[ 176.181409] ? exit_to_user_mode_prepare+0x30/0xb0
[ 176.181413] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181417] ? do_syscall_64+0x68/0x90
[ 176.181421] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181424] ? do_syscall_64+0x68/0x90
[ 176.181428] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 176.181432] RIP: 0033:0x7f847a725c5d
[ 176.181441] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48
[ 176.181481] RSP: 002b:7fff6734e878 EFLAGS: 0246 ORIG_RAX:
0139
[ 176.181484] RAX: ffda RBX: 563ba212a6b0 RCX:
7f847a725c5d
[ 176.181486] RDX: 0004 RSI: 7f847aa0144a RDI:
000d
[ 176.181488] RBP: 7f847aa0144a R08: 0040 R09:
fde0
[ 176.181490] R10: fe18 R11: 0246 R12:
0002
[ 176.181526] R13: 563ba2216ae0 R14: R15:
563ba20dff90
[ 176.181531]
[ 176.181532]
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:vmware 950 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-09-26 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
[Kernel-packages] [Bug 2037490] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2037490/+attachment/5704773/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037490
Title:
"call trace" is reported for mptsas driver
Status in linux package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce:
1. install a ubuntu 23.10 VM on an ESXi Server
2. hot add a lsilogicsas controller and a lsilogicsas disk
Call Trace will be reported in dmesg log
[ 176.181166]
[ 176.181167] UBSAN: array-index-out-of-bounds in
/build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22
[ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA
[1]'
[ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted
6.5.0-5-generic #5-Ubuntu
[ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference
Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023
[ 176.181179] Call Trace:
[ 176.181181]
[ 176.181183] dump_stack_lvl+0x48/0x70
[ 176.181228] dump_stack+0x10/0x20
[ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas]
[ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas]
[ 176.181257] ? __pfx_scsi_runtime_idle+0x10/0x10
[ 176.181264] ? rpm_idle+0x1dc/0x2b0
[ 176.181269] mptsas_scan_sas_topology+0x32/0x210 [mptsas]
[ 176.181277] ? scsi_autopm_put_host+0x1a/0x30
[ 176.181280] mptsas_probe.part.0+0x3cc/0x570 [mptsas]
[ 176.181289] mptsas_probe+0x1e/0x30 [mptsas]
[ 176.181298] local_pci_probe+0x44/0xb0
[ 176.181302] pci_call_probe+0x55/0x190
[ 176.181307] pci_device_probe+0x84/0x120
[ 176.181312] really_probe+0x1c4/0x410
[ 176.181316] __driver_probe_device+0x8c/0x180
[ 176.181320] driver_probe_device+0x24/0xd0
[ 176.181324] __driver_attach+0x10b/0x210
[ 176.181327] ? __pfx___driver_attach+0x10/0x10
[ 176.181330] bus_for_each_dev+0x8a/0xf0
[ 176.181333] driver_attach+0x1e/0x30
[ 176.181336] bus_add_driver+0x127/0x240
[ 176.181340] driver_register+0x5e/0x130
[ 176.181343] ? __pfx_mptsas_init+0x10/0x10 [mptsas]
[ 176.181352] __pci_register_driver+0x62/0x70
[ 176.181356] mptsas_init+0x119/0xff0 [mptsas]
[ 176.181365] do_one_initcall+0x5b/0x340
[ 176.181371] do_init_module+0x68/0x260
[ 176.181375] load_module+0xba1/0xcf0
[ 176.181380] ? vfree+0xff/0x2d0
[ 176.181385] init_module_from_file+0x96/0x100
[ 176.181388] ? init_module_from_file+0x96/0x100
[ 176.181394] idempotent_init_module+0x11c/0x2b0
[ 176.181399] __x64_sys_finit_module+0x64/0xd0
[ 176.181402] do_syscall_64+0x59/0x90
[ 176.181409] ? exit_to_user_mode_prepare+0x30/0xb0
[ 176.181413] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181417] ? do_syscall_64+0x68/0x90
[ 176.181421] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181424] ? do_syscall_64+0x68/0x90
[ 176.181428] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 176.181432] RIP: 0033:0x7f847a725c5d
[ 176.181441] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48
[ 176.181481] RSP: 002b:7fff6734e878 EFLAGS: 0246 ORIG_RAX:
0139
[ 176.181484] RAX: ffda RBX: 563ba212a6b0 RCX:
7f847a725c5d
[ 176.181486] RDX: 0004 RSI: 7f847aa0144a RDI:
000d
[ 176.181488] RBP: 7f847aa0144a R08: 0040 R09:
fde0
[ 176.181490] R10: fe18 R11: 0246 R12:
0002
[ 176.181526] R13: 563ba2216ae0 R14: R15:
563ba20dff90
[ 176.181531]
[ 176.181532]
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:vmware 950 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-09-26 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0
[Kernel-packages] [Bug 2037490] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2037490/+attachment/5704774/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037490
Title:
"call trace" is reported for mptsas driver
Status in linux package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce:
1. install a ubuntu 23.10 VM on an ESXi Server
2. hot add a lsilogicsas controller and a lsilogicsas disk
Call Trace will be reported in dmesg log
[ 176.181166]
[ 176.181167] UBSAN: array-index-out-of-bounds in
/build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22
[ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA
[1]'
[ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted
6.5.0-5-generic #5-Ubuntu
[ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference
Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023
[ 176.181179] Call Trace:
[ 176.181181]
[ 176.181183] dump_stack_lvl+0x48/0x70
[ 176.181228] dump_stack+0x10/0x20
[ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas]
[ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas]
[ 176.181257] ? __pfx_scsi_runtime_idle+0x10/0x10
[ 176.181264] ? rpm_idle+0x1dc/0x2b0
[ 176.181269] mptsas_scan_sas_topology+0x32/0x210 [mptsas]
[ 176.181277] ? scsi_autopm_put_host+0x1a/0x30
[ 176.181280] mptsas_probe.part.0+0x3cc/0x570 [mptsas]
[ 176.181289] mptsas_probe+0x1e/0x30 [mptsas]
[ 176.181298] local_pci_probe+0x44/0xb0
[ 176.181302] pci_call_probe+0x55/0x190
[ 176.181307] pci_device_probe+0x84/0x120
[ 176.181312] really_probe+0x1c4/0x410
[ 176.181316] __driver_probe_device+0x8c/0x180
[ 176.181320] driver_probe_device+0x24/0xd0
[ 176.181324] __driver_attach+0x10b/0x210
[ 176.181327] ? __pfx___driver_attach+0x10/0x10
[ 176.181330] bus_for_each_dev+0x8a/0xf0
[ 176.181333] driver_attach+0x1e/0x30
[ 176.181336] bus_add_driver+0x127/0x240
[ 176.181340] driver_register+0x5e/0x130
[ 176.181343] ? __pfx_mptsas_init+0x10/0x10 [mptsas]
[ 176.181352] __pci_register_driver+0x62/0x70
[ 176.181356] mptsas_init+0x119/0xff0 [mptsas]
[ 176.181365] do_one_initcall+0x5b/0x340
[ 176.181371] do_init_module+0x68/0x260
[ 176.181375] load_module+0xba1/0xcf0
[ 176.181380] ? vfree+0xff/0x2d0
[ 176.181385] init_module_from_file+0x96/0x100
[ 176.181388] ? init_module_from_file+0x96/0x100
[ 176.181394] idempotent_init_module+0x11c/0x2b0
[ 176.181399] __x64_sys_finit_module+0x64/0xd0
[ 176.181402] do_syscall_64+0x59/0x90
[ 176.181409] ? exit_to_user_mode_prepare+0x30/0xb0
[ 176.181413] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181417] ? do_syscall_64+0x68/0x90
[ 176.181421] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181424] ? do_syscall_64+0x68/0x90
[ 176.181428] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 176.181432] RIP: 0033:0x7f847a725c5d
[ 176.181441] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48
[ 176.181481] RSP: 002b:7fff6734e878 EFLAGS: 0246 ORIG_RAX:
0139
[ 176.181484] RAX: ffda RBX: 563ba212a6b0 RCX:
7f847a725c5d
[ 176.181486] RDX: 0004 RSI: 7f847aa0144a RDI:
000d
[ 176.181488] RBP: 7f847aa0144a R08: 0040 R09:
fde0
[ 176.181490] R10: fe18 R11: 0246 R12:
0002
[ 176.181526] R13: 563ba2216ae0 R14: R15:
563ba20dff90
[ 176.181531]
[ 176.181532]
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:vmware 950 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-09-26 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0
[Kernel-packages] [Bug 2037490] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2037490/+attachment/5704772/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037490
Title:
"call trace" is reported for mptsas driver
Status in linux package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce:
1. install a ubuntu 23.10 VM on an ESXi Server
2. hot add a lsilogicsas controller and a lsilogicsas disk
Call Trace will be reported in dmesg log
[ 176.181166]
[ 176.181167] UBSAN: array-index-out-of-bounds in
/build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22
[ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA
[1]'
[ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted
6.5.0-5-generic #5-Ubuntu
[ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference
Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023
[ 176.181179] Call Trace:
[ 176.181181]
[ 176.181183] dump_stack_lvl+0x48/0x70
[ 176.181228] dump_stack+0x10/0x20
[ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas]
[ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas]
[ 176.181257] ? __pfx_scsi_runtime_idle+0x10/0x10
[ 176.181264] ? rpm_idle+0x1dc/0x2b0
[ 176.181269] mptsas_scan_sas_topology+0x32/0x210 [mptsas]
[ 176.181277] ? scsi_autopm_put_host+0x1a/0x30
[ 176.181280] mptsas_probe.part.0+0x3cc/0x570 [mptsas]
[ 176.181289] mptsas_probe+0x1e/0x30 [mptsas]
[ 176.181298] local_pci_probe+0x44/0xb0
[ 176.181302] pci_call_probe+0x55/0x190
[ 176.181307] pci_device_probe+0x84/0x120
[ 176.181312] really_probe+0x1c4/0x410
[ 176.181316] __driver_probe_device+0x8c/0x180
[ 176.181320] driver_probe_device+0x24/0xd0
[ 176.181324] __driver_attach+0x10b/0x210
[ 176.181327] ? __pfx___driver_attach+0x10/0x10
[ 176.181330] bus_for_each_dev+0x8a/0xf0
[ 176.181333] driver_attach+0x1e/0x30
[ 176.181336] bus_add_driver+0x127/0x240
[ 176.181340] driver_register+0x5e/0x130
[ 176.181343] ? __pfx_mptsas_init+0x10/0x10 [mptsas]
[ 176.181352] __pci_register_driver+0x62/0x70
[ 176.181356] mptsas_init+0x119/0xff0 [mptsas]
[ 176.181365] do_one_initcall+0x5b/0x340
[ 176.181371] do_init_module+0x68/0x260
[ 176.181375] load_module+0xba1/0xcf0
[ 176.181380] ? vfree+0xff/0x2d0
[ 176.181385] init_module_from_file+0x96/0x100
[ 176.181388] ? init_module_from_file+0x96/0x100
[ 176.181394] idempotent_init_module+0x11c/0x2b0
[ 176.181399] __x64_sys_finit_module+0x64/0xd0
[ 176.181402] do_syscall_64+0x59/0x90
[ 176.181409] ? exit_to_user_mode_prepare+0x30/0xb0
[ 176.181413] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181417] ? do_syscall_64+0x68/0x90
[ 176.181421] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181424] ? do_syscall_64+0x68/0x90
[ 176.181428] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 176.181432] RIP: 0033:0x7f847a725c5d
[ 176.181441] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48
[ 176.181481] RSP: 002b:7fff6734e878 EFLAGS: 0246 ORIG_RAX:
0139
[ 176.181484] RAX: ffda RBX: 563ba212a6b0 RCX:
7f847a725c5d
[ 176.181486] RDX: 0004 RSI: 7f847aa0144a RDI:
000d
[ 176.181488] RBP: 7f847aa0144a R08: 0040 R09:
fde0
[ 176.181490] R10: fe18 R11: 0246 R12:
0002
[ 176.181526] R13: 563ba2216ae0 R14: R15:
563ba20dff90
[ 176.181531]
[ 176.181532]
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:vmware 950 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-09-26 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 vmwgfxdrmfb
[Kernel-packages] [Bug 2037490] Re: "call trace" is reported for mptsas driver
apport information
** Tags added: apport-collected mantic
** Description changed:
Steps to reproduce:
1. install a ubuntu 23.10 VM on an ESXi Server
2. hot add a lsilogicsas controller and a lsilogicsas disk
Call Trace will be reported in dmesg log
[ 176.181166]
[ 176.181167] UBSAN: array-index-out-of-bounds in
/build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22
[ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA
[1]'
[ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted
6.5.0-5-generic #5-Ubuntu
[ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference
Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023
[ 176.181179] Call Trace:
[ 176.181181]
[ 176.181183] dump_stack_lvl+0x48/0x70
[ 176.181228] dump_stack+0x10/0x20
[ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas]
[ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas]
[ 176.181257] ? __pfx_scsi_runtime_idle+0x10/0x10
[ 176.181264] ? rpm_idle+0x1dc/0x2b0
[ 176.181269] mptsas_scan_sas_topology+0x32/0x210 [mptsas]
[ 176.181277] ? scsi_autopm_put_host+0x1a/0x30
[ 176.181280] mptsas_probe.part.0+0x3cc/0x570 [mptsas]
[ 176.181289] mptsas_probe+0x1e/0x30 [mptsas]
[ 176.181298] local_pci_probe+0x44/0xb0
[ 176.181302] pci_call_probe+0x55/0x190
[ 176.181307] pci_device_probe+0x84/0x120
[ 176.181312] really_probe+0x1c4/0x410
[ 176.181316] __driver_probe_device+0x8c/0x180
[ 176.181320] driver_probe_device+0x24/0xd0
[ 176.181324] __driver_attach+0x10b/0x210
[ 176.181327] ? __pfx___driver_attach+0x10/0x10
[ 176.181330] bus_for_each_dev+0x8a/0xf0
[ 176.181333] driver_attach+0x1e/0x30
[ 176.181336] bus_add_driver+0x127/0x240
[ 176.181340] driver_register+0x5e/0x130
[ 176.181343] ? __pfx_mptsas_init+0x10/0x10 [mptsas]
[ 176.181352] __pci_register_driver+0x62/0x70
[ 176.181356] mptsas_init+0x119/0xff0 [mptsas]
[ 176.181365] do_one_initcall+0x5b/0x340
[ 176.181371] do_init_module+0x68/0x260
[ 176.181375] load_module+0xba1/0xcf0
[ 176.181380] ? vfree+0xff/0x2d0
[ 176.181385] init_module_from_file+0x96/0x100
[ 176.181388] ? init_module_from_file+0x96/0x100
[ 176.181394] idempotent_init_module+0x11c/0x2b0
[ 176.181399] __x64_sys_finit_module+0x64/0xd0
[ 176.181402] do_syscall_64+0x59/0x90
[ 176.181409] ? exit_to_user_mode_prepare+0x30/0xb0
[ 176.181413] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181417] ? do_syscall_64+0x68/0x90
[ 176.181421] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181424] ? do_syscall_64+0x68/0x90
[ 176.181428] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 176.181432] RIP: 0033:0x7f847a725c5d
[ 176.181441] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48
[ 176.181481] RSP: 002b:7fff6734e878 EFLAGS: 0246 ORIG_RAX:
0139
[ 176.181484] RAX: ffda RBX: 563ba212a6b0 RCX:
7f847a725c5d
[ 176.181486] RDX: 0004 RSI: 7f847aa0144a RDI:
000d
[ 176.181488] RBP: 7f847aa0144a R08: 0040 R09:
fde0
[ 176.181490] R10: fe18 R11: 0246 R12:
0002
[ 176.181526] R13: 563ba2216ae0 R14: R15:
563ba20dff90
[ 176.181531]
[ 176.181532]
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.27.0-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/seq:vmware 950 F pipewire
+ CRDA: N/A
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 23.10
+ InstallationDate: Installed on 2023-09-26 (0 days ago)
+ InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
+ IwConfig:
+ lono wireless extensions.
+
+ ens33 no wireless extensions.
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ Lsusb-t:
+
+ Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
+ MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
+ Package: linux (not installed)
+ ProcEnviron:
+ LANG=en_US.UTF-8
+ PATH=(custom, no user)
+ SHELL=/bin/bash
+ TERM=xterm-256color
+ ProcFB: 0 vmwgfxdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=e70caf6c-4fa5-4fd6-9a60-61d851a337f9 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
+ RelatedPackageVersions:
+ linux-restricted-modules-6.5.0-5-generic N/A
+ linux-backports-modules-6.5.0-5-generic N/A
+
[Kernel-packages] [Bug 2037490] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2037490/+attachment/5704771/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037490
Title:
"call trace" is reported for mptsas driver
Status in linux package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce:
1. install a ubuntu 23.10 VM on an ESXi Server
2. hot add a lsilogicsas controller and a lsilogicsas disk
Call Trace will be reported in dmesg log
[ 176.181166]
[ 176.181167] UBSAN: array-index-out-of-bounds in
/build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22
[ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA
[1]'
[ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted
6.5.0-5-generic #5-Ubuntu
[ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference
Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023
[ 176.181179] Call Trace:
[ 176.181181]
[ 176.181183] dump_stack_lvl+0x48/0x70
[ 176.181228] dump_stack+0x10/0x20
[ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas]
[ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas]
[ 176.181257] ? __pfx_scsi_runtime_idle+0x10/0x10
[ 176.181264] ? rpm_idle+0x1dc/0x2b0
[ 176.181269] mptsas_scan_sas_topology+0x32/0x210 [mptsas]
[ 176.181277] ? scsi_autopm_put_host+0x1a/0x30
[ 176.181280] mptsas_probe.part.0+0x3cc/0x570 [mptsas]
[ 176.181289] mptsas_probe+0x1e/0x30 [mptsas]
[ 176.181298] local_pci_probe+0x44/0xb0
[ 176.181302] pci_call_probe+0x55/0x190
[ 176.181307] pci_device_probe+0x84/0x120
[ 176.181312] really_probe+0x1c4/0x410
[ 176.181316] __driver_probe_device+0x8c/0x180
[ 176.181320] driver_probe_device+0x24/0xd0
[ 176.181324] __driver_attach+0x10b/0x210
[ 176.181327] ? __pfx___driver_attach+0x10/0x10
[ 176.181330] bus_for_each_dev+0x8a/0xf0
[ 176.181333] driver_attach+0x1e/0x30
[ 176.181336] bus_add_driver+0x127/0x240
[ 176.181340] driver_register+0x5e/0x130
[ 176.181343] ? __pfx_mptsas_init+0x10/0x10 [mptsas]
[ 176.181352] __pci_register_driver+0x62/0x70
[ 176.181356] mptsas_init+0x119/0xff0 [mptsas]
[ 176.181365] do_one_initcall+0x5b/0x340
[ 176.181371] do_init_module+0x68/0x260
[ 176.181375] load_module+0xba1/0xcf0
[ 176.181380] ? vfree+0xff/0x2d0
[ 176.181385] init_module_from_file+0x96/0x100
[ 176.181388] ? init_module_from_file+0x96/0x100
[ 176.181394] idempotent_init_module+0x11c/0x2b0
[ 176.181399] __x64_sys_finit_module+0x64/0xd0
[ 176.181402] do_syscall_64+0x59/0x90
[ 176.181409] ? exit_to_user_mode_prepare+0x30/0xb0
[ 176.181413] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181417] ? do_syscall_64+0x68/0x90
[ 176.181421] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181424] ? do_syscall_64+0x68/0x90
[ 176.181428] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 176.181432] RIP: 0033:0x7f847a725c5d
[ 176.181441] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48
[ 176.181481] RSP: 002b:7fff6734e878 EFLAGS: 0246 ORIG_RAX:
0139
[ 176.181484] RAX: ffda RBX: 563ba212a6b0 RCX:
7f847a725c5d
[ 176.181486] RDX: 0004 RSI: 7f847aa0144a RDI:
000d
[ 176.181488] RBP: 7f847aa0144a R08: 0040 R09:
fde0
[ 176.181490] R10: fe18 R11: 0246 R12:
0002
[ 176.181526] R13: 563ba2216ae0 R14: R15:
563ba20dff90
[ 176.181531]
[ 176.181532]
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:vmware 950 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-09-26 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0
[Kernel-packages] [Bug 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
** Description changed: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. - 3. suspend then check slp_s0_residency_usec + 3. suspend then check slp_s0_residency_usec_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.5 source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: New Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037493] [NEW] Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
Public bug reported: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Lunar) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Tags: flying-fox oem-priority originate-from-2025203 originate-from-2027772 ** Description changed: [Impact] - System can't enter suspend on AHCI mode, - the CPU FAN and System FAN is running, PSU LED is on. + System can't enter suspend on AHCI mode, + the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... - rtcwake: wakeup from "mem" using /dev/rtc0 at Wed Jul 19 05:13:56 2023 + rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. ** Tags added: flying-fox oem-priority originate-from-2025203 ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Tags added: originate-from-2027772 ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in
[Kernel-packages] [Bug 2013027] Re: Issues over broadcom brcmfmac43455 firmware
[Expired for linux-firmware (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013027 Title: Issues over broadcom brcmfmac43455 firmware Status in linux-firmware package in Ubuntu: Expired Status in linux-firmware-raspi2 package in Ubuntu: Invalid Bug description: Hi, I have a Kodlix Z83-II minicomputer that employs a broadcom chipset for WIFI. The only way to make wifi on that PC work is to use the firmware from the windows image, even if that chipset is apparently managed in ubuntu. With the firmware files provided by ubuntu you get no 5GHz for wifi. The problem is that every time ubuntu updates the firmware package, firmware files dropped in /lib/firmware get overwritten, linking to some file in the cypress sub-directory. - Ideally, Ubuntu should provide all the firmware files that might be needed. Maybe this is not possible as there is a too large variety of different firmwares for broadcom chipsets or licesing issues preventing distribution. - As a second possibility, there should be a way to drop files in /lib/firmware 'side to side' to the distro ones, without having the risk of finding the manually added files rewritten. This implies that different pieces of hardware use firmware files with different filenames. Don't know if this is truly possible, as I do not know how the linux kernel decides the name of the firmware to load. - In cases like mine, it seems that the ubuntu firmware package puts in place symlinks to have brcmfmac43455 files point to the corresponding cypress cyfmac43455 files. Possibly, the package could avoid creating the symlinks if a brcmfmac43455 file is manually placed in lib/firmware. - As a last resort, I think that the documentation in `/usr/share/doc/linux-firmware` should be augmented to describe the most appropriate way to prevent custom firmware files from being rewritten: marking files not-writable? introducing diversions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028830] Re: [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot
** Changed in: linux (Ubuntu) Status: In Progress => 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/2028830 Title: [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu release: sune@jekaterina:~/src/deb$ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 sune@jekaterina:~/src/deb$ Package: linux-image- unsigned-6.5.0-060500rc1-generic_6.5.0-060500rc1.202307232333_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline (rc2 and rc3 also affected) Expectation: System boots normally Actual results: See below On the request of Koba Ko on the kernel-t...@lists.ubuntu.com mailing list, I hereby submit the following: Do note that two "types" are mentioned, and that I am willing the assist in testing, as, obviously, I have a system with a controller covered by the mpt3sas driver. This is output from attempted boot of 6.5-rc3 from kernel-ppa, but it is similar to rcs 1 and 2: UBSAN: array-index-out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/npt3sas/mpt3sas_scsih.c:4667:12 index 1 is out of range for type ’MPI12_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih-c:4023:12 index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6810:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6598:38 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6602:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux-drivers/scsi/mpt3sas/mpt3sas_scsih.c:6619:7 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c::21 index 1 is out of range for type ’MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7649:32 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7651:23 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7655:12 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [EDIT] the next error, repeating for ~1½ hours before finishing boot, was unrelated to mpt2sas and UBSAN. That error was "Timed out for waiting the udey queue being empty." Bug subject altered to reflect this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028830/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037490] 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 2037490 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/2037490 Title: "call trace" is reported for mptsas driver Status in linux package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. install a ubuntu 23.10 VM on an ESXi Server 2. hot add a lsilogicsas controller and a lsilogicsas disk Call Trace will be reported in dmesg log [ 176.181166] [ 176.181167] UBSAN: array-index-out-of-bounds in /build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22 [ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA [1]' [ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted 6.5.0-5-generic #5-Ubuntu [ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023 [ 176.181179] Call Trace: [ 176.181181] [ 176.181183] dump_stack_lvl+0x48/0x70 [ 176.181228] dump_stack+0x10/0x20 [ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas] [ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas] [ 176.181257] ? __pfx_scsi_runtime_idle+0x10/0x10 [ 176.181264] ? rpm_idle+0x1dc/0x2b0 [ 176.181269] mptsas_scan_sas_topology+0x32/0x210 [mptsas] [ 176.181277] ? scsi_autopm_put_host+0x1a/0x30 [ 176.181280] mptsas_probe.part.0+0x3cc/0x570 [mptsas] [ 176.181289] mptsas_probe+0x1e/0x30 [mptsas] [ 176.181298] local_pci_probe+0x44/0xb0 [ 176.181302] pci_call_probe+0x55/0x190 [ 176.181307] pci_device_probe+0x84/0x120 [ 176.181312] really_probe+0x1c4/0x410 [ 176.181316] __driver_probe_device+0x8c/0x180 [ 176.181320] driver_probe_device+0x24/0xd0 [ 176.181324] __driver_attach+0x10b/0x210 [ 176.181327] ? __pfx___driver_attach+0x10/0x10 [ 176.181330] bus_for_each_dev+0x8a/0xf0 [ 176.181333] driver_attach+0x1e/0x30 [ 176.181336] bus_add_driver+0x127/0x240 [ 176.181340] driver_register+0x5e/0x130 [ 176.181343] ? __pfx_mptsas_init+0x10/0x10 [mptsas] [ 176.181352] __pci_register_driver+0x62/0x70 [ 176.181356] mptsas_init+0x119/0xff0 [mptsas] [ 176.181365] do_one_initcall+0x5b/0x340 [ 176.181371] do_init_module+0x68/0x260 [ 176.181375] load_module+0xba1/0xcf0 [ 176.181380] ? vfree+0xff/0x2d0 [ 176.181385] init_module_from_file+0x96/0x100 [ 176.181388] ? init_module_from_file+0x96/0x100 [ 176.181394] idempotent_init_module+0x11c/0x2b0 [ 176.181399] __x64_sys_finit_module+0x64/0xd0 [ 176.181402] do_syscall_64+0x59/0x90 [ 176.181409] ? exit_to_user_mode_prepare+0x30/0xb0 [ 176.181413] ? syscall_exit_to_user_mode+0x37/0x60 [ 176.181417] ? do_syscall_64+0x68/0x90 [ 176.181421] ? syscall_exit_to_user_mode+0x37/0x60 [ 176.181424] ? do_syscall_64+0x68/0x90 [ 176.181428] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 176.181432] RIP: 0033:0x7f847a725c5d [ 176.181441] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48 [ 176.181481] RSP: 002b:7fff6734e878 EFLAGS: 0246 ORIG_RAX: 0139 [ 176.181484] RAX: ffda RBX: 563ba212a6b0 RCX: 7f847a725c5d [ 176.181486] RDX: 0004 RSI: 7f847aa0144a RDI: 000d [ 176.181488] RBP: 7f847aa0144a R08: 0040 R09: fde0 [ 176.181490] R10: fe18 R11: 0246 R12: 0002 [ 176.181526] R13: 563ba2216ae0 R14: R15: 563ba20dff90 [ 176.181531] [ 176.181532] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037490] [NEW] "call trace" is reported for mptsas driver
Public bug reported: Steps to reproduce: 1. install a ubuntu 23.10 VM on an ESXi Server 2. hot add a lsilogicsas controller and a lsilogicsas disk Call Trace will be reported in dmesg log [ 176.181166] [ 176.181167] UBSAN: array-index-out-of-bounds in /build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22 [ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA [1]' [ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted 6.5.0-5-generic #5-Ubuntu [ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023 [ 176.181179] Call Trace: [ 176.181181] [ 176.181183] dump_stack_lvl+0x48/0x70 [ 176.181228] dump_stack+0x10/0x20 [ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas] [ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas] [ 176.181257] ? __pfx_scsi_runtime_idle+0x10/0x10 [ 176.181264] ? rpm_idle+0x1dc/0x2b0 [ 176.181269] mptsas_scan_sas_topology+0x32/0x210 [mptsas] [ 176.181277] ? scsi_autopm_put_host+0x1a/0x30 [ 176.181280] mptsas_probe.part.0+0x3cc/0x570 [mptsas] [ 176.181289] mptsas_probe+0x1e/0x30 [mptsas] [ 176.181298] local_pci_probe+0x44/0xb0 [ 176.181302] pci_call_probe+0x55/0x190 [ 176.181307] pci_device_probe+0x84/0x120 [ 176.181312] really_probe+0x1c4/0x410 [ 176.181316] __driver_probe_device+0x8c/0x180 [ 176.181320] driver_probe_device+0x24/0xd0 [ 176.181324] __driver_attach+0x10b/0x210 [ 176.181327] ? __pfx___driver_attach+0x10/0x10 [ 176.181330] bus_for_each_dev+0x8a/0xf0 [ 176.181333] driver_attach+0x1e/0x30 [ 176.181336] bus_add_driver+0x127/0x240 [ 176.181340] driver_register+0x5e/0x130 [ 176.181343] ? __pfx_mptsas_init+0x10/0x10 [mptsas] [ 176.181352] __pci_register_driver+0x62/0x70 [ 176.181356] mptsas_init+0x119/0xff0 [mptsas] [ 176.181365] do_one_initcall+0x5b/0x340 [ 176.181371] do_init_module+0x68/0x260 [ 176.181375] load_module+0xba1/0xcf0 [ 176.181380] ? vfree+0xff/0x2d0 [ 176.181385] init_module_from_file+0x96/0x100 [ 176.181388] ? init_module_from_file+0x96/0x100 [ 176.181394] idempotent_init_module+0x11c/0x2b0 [ 176.181399] __x64_sys_finit_module+0x64/0xd0 [ 176.181402] do_syscall_64+0x59/0x90 [ 176.181409] ? exit_to_user_mode_prepare+0x30/0xb0 [ 176.181413] ? syscall_exit_to_user_mode+0x37/0x60 [ 176.181417] ? do_syscall_64+0x68/0x90 [ 176.181421] ? syscall_exit_to_user_mode+0x37/0x60 [ 176.181424] ? do_syscall_64+0x68/0x90 [ 176.181428] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 176.181432] RIP: 0033:0x7f847a725c5d [ 176.181441] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48 [ 176.181481] RSP: 002b:7fff6734e878 EFLAGS: 0246 ORIG_RAX: 0139 [ 176.181484] RAX: ffda RBX: 563ba212a6b0 RCX: 7f847a725c5d [ 176.181486] RDX: 0004 RSI: 7f847aa0144a RDI: 000d [ 176.181488] RBP: 7f847aa0144a R08: 0040 R09: fde0 [ 176.181490] R10: fe18 R11: 0246 R12: 0002 [ 176.181526] R13: 563ba2216ae0 R14: R15: 563ba20dff90 [ 176.181531] [ 176.181532] ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: Steps to reproduce: - 1. install a ubuntu 23.10 VM on an ESXi Server - 2. hot add a logicsas controller and a logicsas disk + 1. install a ubuntu 23.10 VM on an ESXi Server + 2. hot add a lsilogicsas controller and a lsilogicsas disk Call Trace will be reported in dmesg log [ 176.181166] [ 176.181167] UBSAN: array-index-out-of-bounds in /build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22 [ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA [1]' [ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted 6.5.0-5-generic #5-Ubuntu [ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023 [ 176.181179] Call Trace: [ 176.181181] [ 176.181183] dump_stack_lvl+0x48/0x70 [ 176.181228] dump_stack+0x10/0x20 [ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas] [ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas] [ 176.181257] ? __pfx_scsi_runtime_idle+0x10/0x10 [ 176.181264] ? rpm_idle+0x1dc/0x2b0 [ 176.181269] mptsas_scan_sas_topology+0x32/0x210 [mptsas] [
[Kernel-packages] [Bug 2036587] Re: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals
** Description changed: [SRU Justification] [Impact] IOMMU related peripherals cannot work. [Fix] - CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. - CONFIG_MTK_IOMMU=m + CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. CONFIG_IOMMU_IO_PGTABLE_ARMV7S is also enabled due to dependency. [Test Case] - 1. build test - 2. running the kernel on the target mediatek platform + build test. + this is the first step to enable the platform on generic kernel. to fully enable the platform, there are some modifications still needed, so only the build test is performed at this stage. [Where problems could occur] - + to enable MTK_IOMMU as a module, IOMMU_IO_PGTABLE_ARMV7S needs to be built-in. the risk would be low because it's not used by default and it needs the driver to allocate by demand. [Other info] the purpose of this is to make ubuntu as an arm systemready ir distribution for mediatek platform. https://developer.arm.com/documentation/DUI1101/2-0/Test-SystemReady- IR/Test-installation-of-Linux-distributions?lang=en -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036587 Title: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals Status in linux package in Ubuntu: Incomplete Status in linux source package in Mantic: Incomplete Bug description: [SRU Justification] [Impact] IOMMU related peripherals cannot work. [Fix] CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. CONFIG_IOMMU_IO_PGTABLE_ARMV7S is also enabled due to dependency. [Test Case] build test. this is the first step to enable the platform on generic kernel. to fully enable the platform, there are some modifications still needed, so only the build test is performed at this stage. [Where problems could occur] to enable MTK_IOMMU as a module, IOMMU_IO_PGTABLE_ARMV7S needs to be built-in. the risk would be low because it's not used by default and it needs the driver to allocate by demand. [Other info] the purpose of this is to make ubuntu as an arm systemready ir distribution for mediatek platform. https://developer.arm.com/documentation/DUI1101/2-0/Test-SystemReady- IR/Test-installation-of-Linux-distributions?lang=en To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036281] Re: activate bpf LSM by default
> BPF LSM is the only major LSM that has a potential platform available for targeting generic sw security solutions and generic performance sw solutions between multiple distros. So no specific software solution in mind? Only generic hypothetical solutions? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036281 Title: activate bpf LSM by default Status in linux package in Ubuntu: Incomplete Bug description: in Fedora/RHEL if I want to see if the bpf LSM is active/available in the kernel I can go here: [root@virtualrocky]# cat /sys/kernel/security/lsm lockdown,capability,yama,selinux,bpf[root@virtualrocky]# but if I do the same thing in Ubuntu 22.0.4 bpf is NOT there: root@virtual-ubuntu2204:/# cat /sys/kernel/security/lsm lockdown,capability,landlock,yama,apparmorroot@virtual-ubuntu2204:/# Please add bpf LSM to the CONFIG_LSM See discourse for background info https://discourse.ubuntu.com/t/ask-us-anything-about-ubuntu- kernels/27664/127?u=why2jjj root@virtual-ubuntu2204:/opt/# cat /proc/version_signature Ubuntu 5.15.0-82.91-generic 5.15.111 THANK YOU! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfreyensee 2526 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-08-29 (17 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) MachineType: Parallels Software International Inc. Parallels Virtual Platform NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-82-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-82-generic N/A linux-backports-modules-5.15.0-82-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.18 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-82-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/03/2023 dmi.bios.release: 18.3 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 18.3.2 (53621) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 2 dmi.chassis.vendor: Parallels Software International Inc. dmi.ec.firmware.release: 18.3 dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr18.3.2(53621):bd07/03/2023:br18.3:efr18.3:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct2:cvr:skuUndefined: dmi.product.family: Parallels VM dmi.product.name: Parallels Virtual Platform dmi.product.sku: Undefined dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988806] Re: Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
** Changed in: linux (Ubuntu Mantic)
Milestone: ubuntu-23.10-beta => None
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/1988806
Title:
Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
Status in Release Notes for Ubuntu:
Invalid
Status in linux package in Ubuntu:
Triaged
Status in linux-hwe-5.19 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-5.19 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.19 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-hwe-5.19 source package in Lunar:
Invalid
Status in linux source package in Mantic:
Triaged
Status in linux-hwe-5.19 source package in Mantic:
Invalid
Bug description:
With below commit in 5.16 upstream kernel, support for
mdev_set_iommu_device() kABI was removed from kernel as there were no
in-tree drivers making use of the kABI.
fda49d97f2c4 ("vfio: remove the unused mdev iommu hook")
This kABI is used by SRIOV based Nvidia vGPU on Ubuntu 22.04. Ampere+
(SRIOV based) Nvidia vGPU use kernel's mdev framework and use this
kABI to pin all guest memory during VM boot.
As HWE kernel (for Ubuntu 22.04) will switch to 5.19 upstream kernel,
it will not include this kABI and as a result will break SRIOV based
Nvidia vGPU. So, filing this bug to request to have a custom patch in
HWE kernel which doesn't remove the support for
mdev_set_iommu_device() kABI.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1988806/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037477] Re: package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2037477 Title: package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: Installed nvidia-dkms-535 package post-installation script subprocess returned error exit status 10 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33+1 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: morante4409 F wireplumber /dev/snd/seq:morante4406 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 26 12:19:59 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2023-08-07 (50 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Dell Inc. Inspiron 15 3511 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=0c9fb687-120b-4b0c-8e75-2d51af14e8f6 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: dkms Title: package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0NG31W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd08/11/2023:br1.24:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0NG31W:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2037477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037477] [NEW] package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Public bug reported: Installed nvidia-dkms-535 package post-installation script subprocess returned error exit status 10 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33+1 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: morante4409 F wireplumber /dev/snd/seq:morante4406 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 26 12:19:59 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2023-08-07 (50 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Dell Inc. Inspiron 15 3511 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=0c9fb687-120b-4b0c-8e75-2d51af14e8f6 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: dkms Title: package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0NG31W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd08/11/2023:br1.24:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0NG31W:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2037477 Title: package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: Installed nvidia-dkms-535 package post-installation script subprocess returned error exit status 10 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33+1 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: morante4409 F wireplumber /dev/snd/seq:morante4406 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 26 12:19:59 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2023-08-07 (50 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Dell Inc. Inspiron 15 3511 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=0c9fb687-120b-4b0c-8e75-2d51af14e8f6 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: dkms Title: package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0NG31W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd08/11/2023:br1.24:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0NG31W:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2037477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
** Changed in: ubuntu-drivers-common (Ubuntu Mantic) Milestone: ubuntu-23.10-beta => ubuntu-23.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Incomplete Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Incomplete Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037476] 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 2037476 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/2037476 Title: 6.2.0-33-generic insert CF card in USB internal reader crash Status in linux package in Ubuntu: Incomplete Bug description: System locks up when inserting a Linux formatted CF card in the internal USB reader. A crash the other day, then 3 times in a row with rebooting before I could mount the card. Ubuntu 6.2.0-33.33-generic 6.2.16 ubuntu-bug linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037476] [NEW] 6.2.0-33-generic insert CF card in USB internal reader crash
Public bug reported: System locks up when inserting a Linux formatted CF card in the internal USB reader. A crash the other day, then 3 times in a row with rebooting before I could mount the card. Ubuntu 6.2.0-33.33-generic 6.2.16 ubuntu-bug linux ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037476 Title: 6.2.0-33-generic insert CF card in USB internal reader crash Status in linux package in Ubuntu: Incomplete Bug description: System locks up when inserting a Linux formatted CF card in the internal USB reader. A crash the other day, then 3 times in a row with rebooting before I could mount the card. Ubuntu 6.2.0-33.33-generic 6.2.16 ubuntu-bug linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@Souvik It's a typical error that happens when: -you have already run once the compiler (each run delete the makefile, so ... "no rule to make target" -or your have many directory linux* in your home directory in the both situations DELETE all the linux-* directory and linux-* files in your homedir, and run once again the script. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022
[Kernel-packages] [Bug 2036587] Re: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals
** Description changed: + [SRU Justification] + [Impact] IOMMU related peripherals cannot work. [Fix] - The CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. - + CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. CONFIG_MTK_IOMMU=m + [Test Case] + 1. build test + 2. running the kernel on the target mediatek platform + + [Where problems could occur] + + [Other info] - effected kernel (5.19~latest) - ubuntu kernel for lunar, Kinetic, and Mantic. + the purpose of this is to make ubuntu as an arm systemready ir distribution for mediatek platform. + + https://developer.arm.com/documentation/DUI1101/2-0/Test-SystemReady- + IR/Test-installation-of-Linux-distributions?lang=en -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036587 Title: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals Status in linux package in Ubuntu: Incomplete Status in linux source package in Mantic: Incomplete Bug description: [SRU Justification] [Impact] IOMMU related peripherals cannot work. [Fix] CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. CONFIG_MTK_IOMMU=m [Test Case] 1. build test 2. running the kernel on the target mediatek platform [Where problems could occur] [Other info] the purpose of this is to make ubuntu as an arm systemready ir distribution for mediatek platform. https://developer.arm.com/documentation/DUI1101/2-0/Test-SystemReady- IR/Test-installation-of-Linux-distributions?lang=en To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036988] Re: Unable to boot on Lenovo L590 Laptop
Added | grep ^ii for readability: $ dpkg -l | grep linux-| grep ^ii ii binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 amd64GNU binary utilities, for x86-64-linux-gnu target ii linux-base4.5ubuntu9 all Linux image base package ii linux-firmware 20220329.git681281e4-0ubuntu3.18all Firmware for Linux kernel drivers ii linux-generic 5.15.0.84.81 amd64Complete Generic Linux kernel and headers ii linux-generic-hwe-20.04 5.15.0.84.81 amd64Complete Generic Linux kernel and headers (dummy transitional package) ii linux-generic-hwe-22.04 6.2.0.33.33~22.04.10 amd64Complete Generic Linux kernel and headers ii linux-headers-5.11.1-051101 5.11.1-051101.202103031212 all Header files related to Linux kernel version 5.11.1 ii linux-headers-5.11.1-051101-generic 5.11.1-051101.202103031212 amd64Linux kernel headers for version 5.11.1 on 64 bit x86 SMP ii linux-headers-5.11.10-051110 5.11.10-051110.202103251032 all Header files related to Linux kernel version 5.11.10 ii linux-headers-5.11.10-051110-generic 5.11.10-051110.202103251032 amd64Linux kernel headers for version 5.11.10 on 64 bit x86 SMP ii linux-headers-5.15.0-84 5.15.0-84.93 all Header files related to Linux kernel version 5.15.0 ii linux-headers-5.15.0-84-generic 5.15.0-84.93 amd64Linux kernel headers for version 5.15.0 on 64 bit x86 SMP ii linux-headers-5.9.0-0509005.9.0-050900.202010112230 all Header files related to Linux kernel version 5.9.0 ii linux-headers-5.9.0-050900-generic5.9.0-050900.202010112230 amd64Linux kernel headers for version 5.9.0 on 64 bit x86 SMP ii linux-headers-6.2.0-33-generic6.2.0-33.33~22.04.1 amd64Linux kernel headers for version 6.2.0 on 64 bit x86 SMP ii linux-headers-generic 5.15.0.84.81 amd64Generic Linux kernel headers ii linux-headers-generic-hwe-22.04 6.2.0.33.33~22.04.10 amd64Generic Linux kernel headers ii linux-hwe-6.2-headers-6.2.0-336.2.0-33.33~22.04.1 all Header files related to Linux kernel version 6.2.0 ii linux-image-5.15.0-84-generic 5.15.0-84.93 amd64Signed kernel image generic ii linux-image-6.2.0-26-generic 6.2.0-26.26 amd64Signed kernel image generic ii linux-image-6.5.0-6-generic 6.5.0-6.6 amd64Signed kernel image generic ii linux-image-generic 5.15.0.84.81 amd64Generic Linux kernel image ii linux-image-generic-hwe-22.04 6.2.0.33.33~22.04.10 amd64Generic Linux kernel image ii linux-libc-dev:amd64 5.15.0-84.93 amd64Linux Kernel Headers for development ii linux-modules-5.15.0-84-generic 5.15.0-84.93 amd64Linux kernel extra modules for version 5.15.0 on 64 bit x86 SMP ii linux-modules-5.9.0-050900-generic5.9.0-050900.202010112230 amd64Linux kernel extra modules for version 5.9.0 on 64 bit x86 SMP ii linux-modules-6.2.0-26-generic6.2.0-26.26 amd64Linux kernel extra modules for version 6.2.0 on 64 bit x86 SMP ii linux-modules-6.5.0-6-generic 6.5.0-6.6 amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-modules-extra-5.15.0-84-generic 5.15.0-84.93 amd64Linux kernel extra modules for version 5.15.0 on 64 bit x86 SMP ii linux-modules-extra-6.2.0-33-generic 6.2.0-33.33~22.04.1 amd64Linux kernel extra modules for version 6.2.0 on 64 bit x86 SMP ii linux-modules-extra-6.5.0-6-generic 6.5.0-6.6 amd64Linux kernel extra modules for version 6.5.0 on 64 bit x86 SMP ii linux-sound-base 1.0.25+dfsg-0ubuntu7
[Kernel-packages] [Bug 2037335] Re: kernel leaking TCP_MEM
Rebuilt the AMI with 5.15.0-1045-aws and the problem is gone. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-aws-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2037335 Title: kernel leaking TCP_MEM Status in linux-meta-aws-6.2 package in Ubuntu: New Bug description: We are running our Kafka brokers on Jammy on ARM64. Previous they were on kernel version 5.15.0-1028-aws, but a few weeks ago we built a new AMI and it picked up 6.2.0-1009-aws, and we have also upgraded to 6.2.0-1012-aws and found the same problem. What we expected to happen: TCP memory (TCP_MEM) to fluctuate but stay relatively low (on a busy production broker running 5.15.0-1028-aws, we average 1900 pages over a 24 hour period) What happened instead: TCP memory (TCP_MEM) continues to rise until hitting the limit (1.5 million pages as configured currently). At this point, the broker is no longer able to properly create new connections and we start seeing "kernel: TCP: out of memory -- consider tuning tcp_mem" in dmesg output. If allowed to continue, the broker will eventually isolate itself from the rest of the cluster since it can't talk to the other brokers. Attached is a graph of the average TCP memory usage per kernel version for our production environment over the past 24 hours. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-aws 6.2.0.1012.12~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1012.12~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1012-aws aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-east-1 CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Sep 25 20:56:02 2023 Ec2AMI: ami-0b9c5aafc5b2a4725 Ec2AMIManifest: (unknown) Ec2Architecture: arm64 Ec2AvailabilityZone: us-east-1b Ec2Imageid: ami-0b9c5aafc5b2a4725 Ec2InstanceType: im4gn.4xlarge Ec2Instancetype: im4gn.4xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-east-1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-aws-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-meta-aws-6.2/+bug/2037335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Changed in: linux (Ubuntu) Milestone: None => ubuntu-23.10 -- 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 2024900] Re: Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present
** Tags removed: verification-needed-focal-linux-aws-5.15 verification-needed-focal-linux-azure verification-needed-focal-linux-bluefield verification-needed-focal-linux-ibm verification-needed-jammy-linux-aws verification-needed-jammy-linux-aws-6.2 verification-needed-jammy-linux-azure verification-needed-lunar-linux-azure verification-needed-lunar-linux-riscv verification-needed-lunar-linux-starfive ** Tags added: verification-done-focal-linux-aws-5.15 verification-done-focal-linux-azure verification-done-focal-linux-bluefield verification-done-focal-linux-ibm verification-done-jammy-linux-aws verification-done-jammy-linux-aws-6.2 verification-done-jammy-linux-azure verification-done-lunar-linux-azure verification-done-lunar-linux-riscv verification-done-lunar-linux-starfive ** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024900 Title: Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: 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 Committed Bug description: SRU Justification [Impact] If the daemon is started and the vmbus is not present it will just exit with an error: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/tree/tools/hv/hv_kvp_daemon.c#n1424 Thus, it would make sense to add "ConditionPathExists=/dev/vmbus/hv_kvp" in linux-cloud-tools- common.hv-kvp-daemon.service to prevent systemd from starting the daemon if the device is not there. [Test Plan] Start an Azure cloud instance and check for /dev/vmbus/hv_kvp and that hv-kvp-daemon is running. Start a non-Azure cloud instance and check that hv-kvp-daemon is not running. [Regression potential] Its possible that kv-hvp-daemon is not started when it should be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034747] Re: Azure: Fix Infiniband identifier order
** Tags removed: verification-needed-jammy-linux-azure
** Tags added: verification-done-jammy-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2034747
Title:
Azure: Fix Infiniband identifier order
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
In Progress
Bug description:
SRU Justification
[Impact]
Commit ad95515bf1d391326b362d8b0c1e6e3bd74046b6 ('RDMA/mana_ib: Add a
driver for Microsoft Azure Network Adapter') is part of the MANA
Infiniband backport. However, a commit was missed that updated the
'enum rdma_driver_id' list of identifiers. Since these are order and
value specific user space applications are not able to correctly
identify the MANA RDMA driver.
[Test Plan]
MSFT tested.
[Regression Potential]
Existing applications don't work with MANA RDMA anyway, so there is no
regression potential.
[Other Info]
SF: #00368017
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2034747/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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
I have confirmed that this issue with not being able to capture kernel dump with a mantic arm64 kernel is not new. using the arm64 6.5 kernel (6.5.0-5) in the release pocket I captured the following during test. ``` 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-5-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-6.5.0-5-generic current state:Not ready to kdump kexec command: no kexec command recorded ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-5-generic #5-Ubuntu SMP PREEMPT_DYNAMIC Wed Sep 6 15:36:23 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux ubuntu@cloudimg:~$ sudo cat /proc/cmdline BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=e7604ab2-200c-4f34-ab11-47e78ac4b8bd ro console=tty1 console=ttyS0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M ubuntu@cloudimg:~$ sudo dmesg | grep -i crash [0.00] crashkernel reserved: 0xde00 - 0xfe00 (512 MB) [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=e7604ab2-200c-4f34-ab11-47e78ac4b8bd ro console=tty1 console=ttyS0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M [ 87.054802] pstore: Using crash dump compression: deflate ubuntu@cloudimg:~$ sudo cat /proc/sys/kernel/sysrq 176 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 13:44:22 UTC; 7min ago Process: 514 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/SUCCESS) Main PID: 514 (code=exited, status=0/SUCCESS) CPU: 4min 46.461s Sep 26 13:38:21 cloudimg systemd[1]: Starting kdump-tools.service - Kernel crash dump capture service... Sep 26 13:38:32 cloudimg kdump-tools[514]: Starting kdump-tools: Sep 26 13:38:32 cloudimg kdump-tools[535]: * Creating symlink /var/lib/kdump/vmlinuz Sep 26 13:38:41 cloudimg kdump-tools[577]: kdump-tools: Generating /var/lib/kdump/initrd.img-6.5.0-5-generic Sep 26 13:44:11 cloudimg kdump-tools[535]: * Creating symlink /var/lib/kdump/initrd.img Sep 26 13:44:22 cloudimg kdump-tools[535]: * failed to load kdump kernel Sep 26 13:44:22 cloudimg kdump-tools[5536]: failed to load kdump kernel Sep 26 13:44:22 cloudimg systemd[1]: Finished kdump-tools.service - Kernel crash dump capture service. ubuntu@cloudimg:~$ sudo ls -al /var/lib/kdump/vmlinuz lrwxrwxrwx 1 root root 29 Sep 26 13:38 /var/lib/kdump/vmlinuz -> /boot/vmlinuz-6.5.0-5-generic ubuntu@cloudimg:~$ sudo file /boot/vmlinuz-6.5.0-5-generic /boot/vmlinuz-6.5.0-5-generic: gzip compressed data, was "vmlinuz-6.5.0-5-generic.efi.signed", last modified: Thu Sep 7 10:43:26 2023, max compression, from Unix, original size modulo 2^32 54989192 ``` .. but the `Cannot determine the file type of /var/lib/kdump/vmlinuz` in the `sudo service kdump-tools status` as @xnox has also reproduced with `kexec` is new. I have also confirmed that capturing kernel crash dump with the amd64 kernel 6.5.0-5 & 6.5.0-6 works as expected. -- 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,
[Kernel-packages] [Bug 2028550] Re: Backport support to tolerate ZSTD compressed firmware files
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028550 Title: Backport support to tolerate ZSTD compressed firmware files Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: [ Impact ] * To ensure reliable dist-upgrades in case of partial upgrades or upgrade failures, it is desirable for LTS GA kernel to support features that next-LTS GA kernel will rely on. * Specifically it is being discussed to switch linux-firmware to ZSTD compressed one (see bug #1942260) * To ensure that failed dist-upgrades can still boot after-partial upgrade it is desirable to suppport zstd compressed firmware [ Test Plan ] * Boot new build of GA linux kernel with CONFIG_FW_LOADER_COMPRESS_ZSTD * Check that existing firmware files loaded on a given machine can be compressed with zstd and still loaded by this kernel * Check that depmod / initramfs-tools all support .zst compressed firmware [ Where problems could occur ] * Once this is inroduced in jammy-GA kernel it may cripple into focal-hwe kernels too, and people may start relying on this feature despite not universally supported by all other focal kernels. This should be trivial to catch in SRUs for example, do not accept SRUs of firmwares that ship themselves as .zst in Jammy and lower. [ Other Info ] * See https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html and https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033441] Re: linux-firmware is outdated
Hi Timo,
does testing
https://launchpad.net/ubuntu/+source/linux-firmware/20230323.gitbcdcfbcf-0ubuntu1.7
require some specific kernel version, or can I drop this FW into Ubuntu Jammy,
running linux-image 6.2.0-33?
I'm running KDE Neon, so updating to Lobster is not an option at the
moment, and I'm forced to running 5.19.X kernel for now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2033441
Title:
linux-firmware is outdated
Status in linux-firmware package in Ubuntu:
Triaged
Status in linux-firmware source package in Lunar:
Fix Committed
Bug description:
[Impact]
This is optimus laptop with Intel 11th Gen and Nvidia.
In recent kernels like 6.2.0 it gives a blank screen after booting and if
nouveau.modset=1 is set, it completely freeze the system.
I remember it was working fine in 5.x kernels.
Now I have to blacklist nouveau and use Nvidia driver instead.
Using this commit of linux-firmware solved the issue:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/nvidia?id=2e92a49f90f73c8edc44b25c6e669d5e70893c90
[Fix]
Upstream commit 2e92a49f90f9 ("nvidia: update Tu10x and Tu11x signed
firmware to support newer Turing HW")
[Test Case]
Boot a machine with relevant GPU.
[Where Problems Could Occur]
Updated Nvidia FW so limited to machines with relevant GPUs.
[Additional Information]
# journalctl -b -2 | grep nouveau
Aug 29 21:07:54 ZB kernel: Command line: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic
root=/dev/mapper/vgubuntu-root ro nouveau.modeset=1 quiet splash
Aug 29 21:07:54 ZB kernel: Kernel command line:
BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro
nouveau.modeset=1 quiet splash
Aug 29 21:07:54 ZB kernel: nouveau: detected PR support, will not use DSM
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: enabling device ( ->
0003)
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: NVIDIA TU117 (167000a1)
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: bios: version 90.17.61.00.73
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: pmu: firmware unavailable
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: fb: 2048 MiB GDDR6
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: halted
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC SCTL 7021
TIDX 1b1f
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 23ac
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2055
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2305
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 201c
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2303
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2051
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 269e
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2617
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25e8
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b2
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 1822
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 1a97
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 26c8
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2318
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: DRM: VRAM: 2048 MiB
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: DRM: GART: 536870912 MiB
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: DRM: BIT table
[Kernel-packages] [Bug 2036742] Re: amdgpu crash on Mantic
Thanks for checking. So good to know it hasn't regressed from stable in 5.10. Can you redo your 5.15 test with the firmware in place so we can see if we're OK there or not? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036742 Title: amdgpu crash on Mantic Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Booting from USB the latest Mantic Desktop daily image (2023-09-20), just after the initial logs, nothing is displayed on screen. The system is still alive since _autoinstall_ works as intended. Once provisioned, the problem is still present. It seems related to https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2029396 . dmesg attached. [Test Case] Live boot Ubuntu Mantic Desktop canary (2023-09-19) [Where Problems Could Occur] Dell Optiplex 5090 - Intel Core(TM) i7-11700 - Advanced Micro Devices, Inc. [AMD/ATI] - 1002:699f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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: Unable to capture kernel crash dump using arm64 mantic 6.5.0-6-generic -proposed kernel
$ sudo /tmp/tmp.u3jP6LAlnj/usr/local/sbin/kexec --debug -l -c /boot/vmlinuz-6.5.0-6-generic arch_process_options:178: command_line: (null) arch_process_options:180: initrd: (null) arch_process_options:182: dtb: (null) arch_process_options:185: console: (null) Try gzip decompression. kernel: 0x8e4ef010 kernel_size: 0xda0988 set_phys_offset: phys_offset : 4000 (method : vmcoreinfo pt_note) get_memory_ranges:+[0] 4000 - 00023c58 get_memory_ranges:- fa00 - get_memory_ranges:- 0001001dc000 - 0001001dcfff get_memory_ranges:- 00010021 - 00010021 get_memory_ranges:- 00010022 - 00010022 get_memory_ranges:- 00010023 - 00010023 get_memory_ranges:- 00010954 - 00010a0f get_memory_ranges:- 00022fb5 - 00022fb50fff get_memory_ranges:- 00022fd5d000 - 00022fd64fff get_memory_ranges:- 00023440 - 00023c3f get_memory_ranges:- 00023c4a6000 - 00023c4a6fff get_memory_ranges:- 00023c58 - 00023c58 get_memory_ranges:+[9] 00023c73 - 00023fbf get_memory_ranges:- 00023dbf1000 - 00023e7f1fff get_memory_ranges:- 00023eaff000 - 00023ebbefff get_memory_ranges:- 00023ebbf000 - 00023ebb get_memory_ranges:- 00023ebc - 00023ebf get_memory_ranges:- 00023ec02000 - 00023ec03fff get_memory_ranges:- 00023ec04000 - 00023ec04fff get_memory_ranges:- 00023ec05000 - 00023fbf get_memory_ranges:+[12] 00023ffe - 00023fff get_memory_ranges:- 00023ffe - 00023fff System RAM ranges; 4000-f9ff (0) 0001-0001001dbfff (0) 0001001dd000-00010020 (0) 00010024-00010953 (0) 00010a10-00022fb4 (0) 00022fb51000-00022fd5cfff (0) 00022fd65000-0002343f (0) 00023c40-00023c4a5fff (0) 00023c4a7000-00023c57 (0) 00023c73-00023dbf0fff (0) 00023e7f2000-00023eafefff (0) 00023ec0-00023ec01fff (0) elf_arm64_probe: Not an ELF executable. image_arm64_probe: Bad arm64 image header. pez_arm64_probe: PROBE. pez_prepare: kexec can only decompress gziped and lzma images. Cannot determine the file type of /boot/vmlinuz-6.5.0-6-generic Even git snapshot of kexec-tools cannot handle zstd commpressed zimg ** Summary changed: - Unable to capture kernel crash dump using arm64 mantic 6.5.0-6-generic -proposed kernel + kexec enable to load/kdump zstd compressed zimg ** Changed in: kdump-tools (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: kexec-tools (Ubuntu) Importance: Undecided => Wishlist ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Tags added: block-proposed-mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. Matching subscriptions: Maintainer 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
[Kernel-packages] [Bug 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1987190 Title: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1 Status in zfs-linux package in Ubuntu: Confirmed Bug description: I have a server that has been running its data volume using ZFS in 20.04 without any problem. The volume is using ZFS encryption and a raidz1-0 configuration. I performed a scrub operations before the upgrade and it did not find any problem. After the reboot for the upgrade, I was welcomed with the following message: status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A The volumes still do not have any checksum error but there are 5 zvols that are not accessible. zpool status displays a line similar to the below for each of the five: errors: Permanent errors have been detected in the following files: tank/data/data:<0x0> I run a scrub and it has not identified any problem but the error messages are not there and the data is still not available. There are 10+ other zvols in the zpool that do not have any kind of problem. I have been unable to identify any correlation between the zvols that are failing. I have seen people reporting similar problems in github after the 20.04 to the 22.04 upgrade (see https://github.com/openzfs/zfs/issues/13763). I wonder how widespread the problem will be as more people upgrades to 22.04. I will try to downgrade the version of zfs in the system and report back ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.4-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Aug 20 22:24:54 2022 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1
Hi, Attached an up-to-date patch for 2.1.5-1ubuntu6~22.04.1 to be used in Walter his steps in #4 (editing in launchpad is hard :-( ) ** Patch added: "zfs-dkms-2.1.5-1-fix-zero-mac-io-error.patch" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987190/+attachment/5704587/+files/zfs-dkms-2.1.5-1-fix-zero-mac-io-error.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1987190 Title: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1 Status in zfs-linux package in Ubuntu: Confirmed Bug description: I have a server that has been running its data volume using ZFS in 20.04 without any problem. The volume is using ZFS encryption and a raidz1-0 configuration. I performed a scrub operations before the upgrade and it did not find any problem. After the reboot for the upgrade, I was welcomed with the following message: status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A The volumes still do not have any checksum error but there are 5 zvols that are not accessible. zpool status displays a line similar to the below for each of the five: errors: Permanent errors have been detected in the following files: tank/data/data:<0x0> I run a scrub and it has not identified any problem but the error messages are not there and the data is still not available. There are 10+ other zvols in the zpool that do not have any kind of problem. I have been unable to identify any correlation between the zvols that are failing. I have seen people reporting similar problems in github after the 20.04 to the 22.04 upgrade (see https://github.com/openzfs/zfs/issues/13763). I wonder how widespread the problem will be as more people upgrades to 22.04. I will try to downgrade the version of zfs in the system and report back ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.4-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Aug 20 22:24:54 2022 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1987190 Title: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1 Status in zfs-linux package in Ubuntu: Confirmed Bug description: I have a server that has been running its data volume using ZFS in 20.04 without any problem. The volume is using ZFS encryption and a raidz1-0 configuration. I performed a scrub operations before the upgrade and it did not find any problem. After the reboot for the upgrade, I was welcomed with the following message: status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A The volumes still do not have any checksum error but there are 5 zvols that are not accessible. zpool status displays a line similar to the below for each of the five: errors: Permanent errors have been detected in the following files: tank/data/data:<0x0> I run a scrub and it has not identified any problem but the error messages are not there and the data is still not available. There are 10+ other zvols in the zpool that do not have any kind of problem. I have been unable to identify any correlation between the zvols that are failing. I have seen people reporting similar problems in github after the 20.04 to the 22.04 upgrade (see https://github.com/openzfs/zfs/issues/13763). I wonder how widespread the problem will be as more people upgrades to 22.04. I will try to downgrade the version of zfs in the system and report back ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.4-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Aug 20 22:24:54 2022 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036587] Re: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals
** No longer affects: lunar (Ubuntu) ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036587 Title: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals Status in linux package in Ubuntu: Incomplete Status in linux source package in Mantic: Incomplete Bug description: [Impact] IOMMU related peripherals cannot work. [Fix] The CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. CONFIG_MTK_IOMMU=m [Other info] effected kernel (5.19~latest) ubuntu kernel for lunar, Kinetic, and Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019868] Re: ubuntu_kernel_selftests:net:tls: 88 failed test cases on jammy/fips
FIPS kernels are no longer failing with these tests, as they are now skipped. I verified the output of the net:tls tests from the following kernels: - j:fips 5.15.0-85.95+fips1 - j:aws-fips 5.15.0-1046.51+fips3 - j:ibm-gt-fips 5.15.0-1045.48+fips1 Test results output: # # PASSED: 179 / 179 tests passed. # # Totals: pass:91 fail:0 xfail:0 xpass:0 skip:88 error:0 ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019868 Title: ubuntu_kernel_selftests:net:tls: 88 failed test cases on jammy/fips Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: These failures happen on all supported architectures, when fips=1. When fips=0, all test cases pass. The results are shown below: make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/src/linux' TAP version 13 1..1 # selftests: net: tls # TAP version 13 # 1..179 # # Starting 179 tests from 6 test cases. # # RUN global.non_established ... # #OK global.non_established # ok 1 global.non_established # # RUN global.keysizes ... # #OK global.keysizes # ok 2 global.keysizes # # RUN tls_basic.base_base ... # #OK tls_basic.base_base # ok 3 tls_basic.base_base # # RUN tls.12_gcm.sendfile ... # #OK tls.12_gcm.sendfile # ok 4 tls.12_gcm.sendfile # # RUN tls.12_gcm.send_then_sendfile ... # #OK tls.12_gcm.send_then_sendfile # ok 5 tls.12_gcm.send_then_sendfile # # RUN tls.12_gcm.recv_max ... # #OK tls.12_gcm.recv_max # ok 6 tls.12_gcm.recv_max # # RUN tls.12_gcm.recv_small ... # #OK tls.12_gcm.recv_small # ok 7 tls.12_gcm.recv_small # # RUN tls.12_gcm.msg_more ... # #OK tls.12_gcm.msg_more # ok 8 tls.12_gcm.msg_more # # RUN tls.12_gcm.msg_more_unsent ... # #OK tls.12_gcm.msg_more_unsent # ok 9 tls.12_gcm.msg_more_unsent # # RUN tls.12_gcm.sendmsg_single ... # #OK tls.12_gcm.sendmsg_single # ok 10 tls.12_gcm.sendmsg_single # # RUN tls.12_gcm.sendmsg_fragmented ... # #OK tls.12_gcm.sendmsg_fragmented # ok 11 tls.12_gcm.sendmsg_fragmented # # RUN tls.12_gcm.sendmsg_large ... # #OK tls.12_gcm.sendmsg_large # ok 12 tls.12_gcm.sendmsg_large # # RUN tls.12_gcm.sendmsg_multiple ... # #OK tls.12_gcm.sendmsg_multiple # ok 13 tls.12_gcm.sendmsg_multiple # # RUN tls.12_gcm.sendmsg_multiple_stress ... # #OK tls.12_gcm.sendmsg_multiple_stress # ok 14 tls.12_gcm.sendmsg_multiple_stress # # RUN tls.12_gcm.splice_from_pipe ... # #OK tls.12_gcm.splice_from_pipe # ok 15 tls.12_gcm.splice_from_pipe # # RUN tls.12_gcm.splice_from_pipe2 ... # #OK tls.12_gcm.splice_from_pipe2 # ok 16 tls.12_gcm.splice_from_pipe2 # # RUN tls.12_gcm.send_and_splice ... # #OK tls.12_gcm.send_and_splice # ok 17 tls.12_gcm.send_and_splice # # RUN tls.12_gcm.splice_to_pipe ... # #OK tls.12_gcm.splice_to_pipe # ok 18 tls.12_gcm.splice_to_pipe # # RUN tls.12_gcm.recvmsg_single ... # #OK tls.12_gcm.recvmsg_single # ok 19 tls.12_gcm.recvmsg_single # # RUN tls.12_gcm.recvmsg_single_max ... # #OK tls.12_gcm.recvmsg_single_max # ok 20 tls.12_gcm.recvmsg_single_max # # RUN tls.12_gcm.recvmsg_multiple ... # #OK tls.12_gcm.recvmsg_multiple # ok 21 tls.12_gcm.recvmsg_multiple # # RUN tls.12_gcm.single_send_multiple_recv ... # #OK tls.12_gcm.single_send_multiple_recv # ok 22 tls.12_gcm.single_send_multiple_recv # # RUN tls.12_gcm.multiple_send_single_recv ... # #OK tls.12_gcm.multiple_send_single_recv # ok 23 tls.12_gcm.multiple_send_single_recv # # RUN tls.12_gcm.single_send_multiple_recv_non_align ... # #OK tls.12_gcm.single_send_multiple_recv_non_align # ok 24 tls.12_gcm.single_send_multiple_recv_non_align # # RUN tls.12_gcm.recv_partial ... # #OK tls.12_gcm.recv_partial # ok 25 tls.12_gcm.recv_partial # # RUN tls.12_gcm.recv_nonblock ... # #OK tls.12_gcm.recv_nonblock # ok 26 tls.12_gcm.recv_nonblock # # RUN
[Kernel-packages] [Bug 2019880] Re: ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on jammy/fips
FIPS kernels are no longer failing with these tests. I verified the output of the net:vrf-xfrm-tests.sh tests from the following kernels: - j:fips 5.15.0-85.95+fips1 - j:aws-fips 5.15.0-1046.51+fips3 - j:ibm-gt-fips 5.15.0-1045.48+fips1 Test results output: # Tests passed: 14 # Tests failed: 0 ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019880 Title: ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on jammy/fips Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: These failures happen on all supported architectures, when fips=1. When fips=0, all test cases pass. Results are shown below: make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/src/linux' TAP version 13 1..1 # selftests: net: vrf-xfrm-tests.sh # # No qdisc on VRF device # TEST: IPv4 no xfrm policy [ OK ] # TEST: IPv6 no xfrm policy [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy with VRF in selector [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy with xfrm device [FAIL] # TEST: IPv6 xfrm policy with xfrm device [FAIL] # # netem qdisc on VRF device # TEST: IPv4 no xfrm policy [ OK ] # TEST: IPv6 no xfrm policy [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy with VRF in selector [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy with xfrm device [FAIL] # TEST: IPv6 xfrm policy with xfrm device [FAIL] # # Tests passed: 6 # Tests failed: 8 not ok 1 selftests: net: vrf-xfrm-tests.sh # exit=1 make: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests/net' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2019880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034277] Re: Azure: net: mana: Add page pool for RX buffers
** Tags removed: verification-needed-jammy-linux-azure verification-needed-lunar-linux-azure ** Tags added: verification-done-jammy-linux-azure verification-done-lunar-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2034277 Title: Azure: net: mana: Add page pool for RX buffers Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Released Bug description: SRU Justification [Impact] Microsoft has requested this path be added to the 5.15 and 6.2 Azure kernels. Add page pool for RX buffers for faster buffer cycle and reduce CPU usage. [Test Plan] MSFT tested. [Regression Potential] Could cause receive packet corruption. [Other Info] SF: #00365760 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2034277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037403] 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 2037403 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/2037403 Title: PCI BARs larger than 128GB are disabled Status in linux package in Ubuntu: Incomplete Status in linux-bluefield package in Ubuntu: New Status in linux source package in Jammy: Incomplete Status in linux-bluefield source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] Current linux-bluefield kernel reports that PCI BARs larger than 128GB are disabled. Increase the maximum PCI BAR size from 128GB to 8TB for future expansion. [Test Plan] Use updated kernel with PCI device with PCI BARs larger than 128GB. [Where problems could occur] No potential problems are expected. [Other Info] Testing has been provided by the customer. This patch is a cherry-pick from the upstream 5.18 kernel. It is intended for linux-bluefield kernel re-spin but it may be also suitable for the generic kernel (separate submission). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037403] Re: PCI BARs larger than 128GB are disabled
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037403 Title: PCI BARs larger than 128GB are disabled Status in linux package in Ubuntu: New Status in linux-bluefield package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] Current linux-bluefield kernel reports that PCI BARs larger than 128GB are disabled. Increase the maximum PCI BAR size from 128GB to 8TB for future expansion. [Test Plan] Use updated kernel with PCI device with PCI BARs larger than 128GB. [Where problems could occur] No potential problems are expected. [Other Info] Testing has been provided by the customer. This patch is a cherry-pick from the upstream 5.18 kernel. It is intended for linux-bluefield kernel re-spin but it may be also suitable for the generic kernel (separate submission). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037403] [NEW] PCI BARs larger than 128GB are disabled
Public bug reported: [SRU Justification] [Impact] Current linux-bluefield kernel reports that PCI BARs larger than 128GB are disabled. Increase the maximum PCI BAR size from 128GB to 8TB for future expansion. [Test Plan] Use updated kernel with PCI device with PCI BARs larger than 128GB. [Where problems could occur] No potential problems are expected. [Other Info] Testing has been provided by the customer. This patch is a cherry-pick from the upstream 5.18 kernel. It is intended for linux-bluefield kernel re-spin but it may be also suitable for the generic kernel (separate submission). ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New ** Affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Package changed: linux-azure (Ubuntu) => linux-bluefield (Ubuntu) ** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2037403 Title: PCI BARs larger than 128GB are disabled Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: In Progress Bug description: [SRU Justification] [Impact] Current linux-bluefield kernel reports that PCI BARs larger than 128GB are disabled. Increase the maximum PCI BAR size from 128GB to 8TB for future expansion. [Test Plan] Use updated kernel with PCI device with PCI BARs larger than 128GB. [Where problems could occur] No potential problems are expected. [Other Info] Testing has been provided by the customer. This patch is a cherry-pick from the upstream 5.18 kernel. It is intended for linux-bluefield kernel re-spin but it may be also suitable for the generic kernel (separate submission). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2037403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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: Unable to capture kernel crash dump using arm64 mantic 6.5.0-6-generic -proposed kernel
** Changed in: kdump-tools (Ubuntu) Status: New => Incomplete ** Changed in: kexec-tools (Ubuntu) Status: New => Triaged -- 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: Unable to capture kernel crash dump using arm64 mantic 6.5.0-6-generic -proposed kernel Status in kdump-tools package in Ubuntu: Incomplete Status in kexec-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete 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 2037402] [NEW] radeon driver doesn't work
Public bug reported: With linux-image later than 5.15.0-73-generic Ubuntu 20.04 blacks out at booting. My hardwware is iMac 21 inch mid 2011 (CPU Core i3 540, 16GB DRAM). The video driver shown by lshw is Mobility Radeon HD 4670. After the drives are checked, the screen blacks out. However, the system itself seems to boot normally. I can ssh to it from other machines. Now I use linux-image-5.15.0-73-generic, which is the latest kernel for radeon to work normally. The followings are the outputs of "journalctl -b | grep radeon" of 5.15.0-84-generic and 5.15.0-73-generic. Comparing with the log of 5.15.0-73-generic, systemd seems to stop 5Screen Backlight Brightness with 15.0-84-generic. *** "journalctl -b | grep radeon" of 5.15.0-84-generic *** Sep 24 21:33:13 ubuntu2004-imac kernel: [drm] radeon kernel modesetting enabled. Sep 24 21:33:13 ubuntu2004-imac kernel: radeon :01:00.0: vgaarb: deactivate vga console Sep 24 21:33:13 ubuntu2004-imac kernel: radeon :01:00.0: No more image in the PCI ROM Sep 24 21:33:13 ubuntu2004-imac kernel: radeon :01:00.0: VRAM: 256M 0x - 0x0FFF (256M used) Sep 24 21:33:13 ubuntu2004-imac kernel: radeon :01:00.0: GTT: 1024M 0x1000 - 0x4FFF Sep 24 21:33:13 ubuntu2004-imac kernel: [drm] radeon: 256M of VRAM memory ready Sep 24 21:33:13 ubuntu2004-imac kernel: [drm] radeon: 1024M of GTT memory ready. Sep 24 21:33:13 ubuntu2004-imac kernel: [drm] radeon: dpm initialized Sep 24 21:33:13 ubuntu2004-imac kernel: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 Sep 24 21:33:13 ubuntu2004-imac kernel: radeon :01:00.0: WB enabled Sep 24 21:33:13 ubuntu2004-imac kernel: radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 Sep 24 21:33:13 ubuntu2004-imac kernel: radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c Sep 24 21:33:13 ubuntu2004-imac kernel: radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 Sep 24 21:33:13 ubuntu2004-imac kernel: radeon :01:00.0: radeon: MSI limited to 32-bit Sep 24 21:33:13 ubuntu2004-imac kernel: radeon :01:00.0: radeon: using MSI. Sep 24 21:33:13 ubuntu2004-imac kernel: [drm] radeon: irq initialized. Sep 24 21:33:13 ubuntu2004-imac kernel: [drm] radeon atom DIG backlight initialized Sep 24 21:33:13 ubuntu2004-imac kernel: fbcon: radeondrmfb (fb0) is primary device Sep 24 21:33:13 ubuntu2004-imac kernel: radeon :01:00.0: [drm] fb0: radeondrmfb frame buffer device Sep 24 21:33:13 ubuntu2004-imac kernel: [drm] Initialized radeon 2.50.0 20080528 for :01:00.0 on minor 0 Sep 24 21:33:06 ubuntu2004-imac systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:radeon_bl0... Sep 24 21:33:06 ubuntu2004-imac systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:radeon_bl0. Sep 24 21:34:05 ubuntu2004-imac systemd[1]: Stopping Load/Save Screen Backlight Brightness of backlight:radeon_bl0... Sep 24 21:34:05 ubuntu2004-imac systemd[1]: systemd-backlight@backlight:radeon_bl0.service: Succeeded. Sep 24 21:34:05 ubuntu2004-imac systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:radeon_bl0. *** end *** *** "journalctl -b | grep radeon" of 5.15.0-73-generic *** Sep 24 21:35:27 ubuntu2004-imac kernel: [drm] radeon kernel modesetting enabled. Sep 24 21:35:27 ubuntu2004-imac kernel: radeon :01:00.0: vgaarb: deactivate vga console Sep 24 21:35:27 ubuntu2004-imac kernel: radeon :01:00.0: No more image in the PCI ROM Sep 24 21:35:27 ubuntu2004-imac kernel: radeon :01:00.0: VRAM: 256M 0x - 0x0FFF (256M used) Sep 24 21:35:27 ubuntu2004-imac kernel: radeon :01:00.0: GTT: 1024M 0x1000 - 0x4FFF Sep 24 21:35:27 ubuntu2004-imac kernel: [drm] radeon: 256M of VRAM memory ready Sep 24 21:35:27 ubuntu2004-imac kernel: [drm] radeon: 1024M of GTT memory ready. Sep 24 21:35:27 ubuntu2004-imac kernel: [drm] radeon: dpm initialized Sep 24 21:35:27 ubuntu2004-imac kernel: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 Sep 24 21:35:27 ubuntu2004-imac kernel: radeon :01:00.0: WB enabled Sep 24 21:35:27 ubuntu2004-imac kernel: radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 Sep 24 21:35:27 ubuntu2004-imac kernel: radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c Sep 24 21:35:27 ubuntu2004-imac kernel: radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 Sep 24 21:35:27 ubuntu2004-imac kernel: radeon :01:00.0: radeon: MSI limited to 32-bit Sep 24 21:35:27 ubuntu2004-imac kernel: radeon :01:00.0: radeon: using MSI. Sep 24 21:35:27 ubuntu2004-imac kernel: [drm] radeon: irq initialized. Sep 24 21:35:27 ubuntu2004-imac kernel: [drm] radeon atom DIG backlight initialized Sep 24 21:35:27 ubuntu2004-imac kernel: fbcon: radeondrmfb (fb0) is primary device Sep 24
[Kernel-packages] [Bug 2037398] Re: Unable to capture kernel crash dump using arm64 mantic 6.5.0-6-generic -proposed kernel
** Also affects: kexec-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/2037398 Title: Unable to capture kernel crash dump using arm64 mantic 6.5.0-6-generic -proposed kernel Status in kdump-tools package in Ubuntu: New Status in kexec-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete 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 2037398] 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 2037398 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/2037398 Title: Unable to capture kernel crash dump using arm64 mantic 6.5.0-6-generic -proposed kernel Status in kdump-tools package in Ubuntu: New Status in kexec-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete 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 2037398] Re: Unable to capture kernel crash dump using arm64 mantic 6.5.0-6-generic -proposed kernel
** Also affects: kdump-tools (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. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/2037398 Title: Unable to capture kernel crash dump using arm64 mantic 6.5.0-6-generic -proposed kernel Status in kdump-tools package in Ubuntu: New Status in kexec-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete 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 2037400] [NEW] nvidia drivers not included in initramfs
Public bug reported:
/usr/share/initramfs-tools/hooks/framebuffer-nvidia looks only for *.ko
modules:
```
copy_modules_dir_filter()
{
[...]
for kmod in $(find "${MODULESDIR}/${dir}" ${exclude:-} -name "$pattern*.ko"
-print); do
manual_add_modules $(basename ${kmod} .ko)
done
}
```
But the kernel modules are zstd compressed on mantic:
```
# ls /lib/modules/6.5.0-5-generic/updates/dkms/ -1
nvidia-drm.ko.zst
nvidia-modeset.ko.zst
nvidia-peermem.ko.zst
nvidia-uvm.ko.zst
nvidia.ko.zst
```
** Affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Critical
Status: New
** Affects: nvidia-graphics-drivers-535 (Ubuntu Mantic)
Importance: Critical
Status: New
** Also affects: nvidia-graphics-drivers-535 (Ubuntu Mantic)
Importance: Critical
Status: New
--
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/2037400
Title:
nvidia drivers not included in initramfs
Status in nvidia-graphics-drivers-535 package in Ubuntu:
New
Status in nvidia-graphics-drivers-535 source package in Mantic:
New
Bug description:
/usr/share/initramfs-tools/hooks/framebuffer-nvidia looks only for
*.ko modules:
```
copy_modules_dir_filter()
{
[...]
for kmod in $(find "${MODULESDIR}/${dir}" ${exclude:-} -name
"$pattern*.ko" -print); do
manual_add_modules $(basename ${kmod} .ko)
done
}
```
But the kernel modules are zstd compressed on mantic:
```
# ls /lib/modules/6.5.0-5-generic/updates/dkms/ -1
nvidia-drm.ko.zst
nvidia-modeset.ko.zst
nvidia-peermem.ko.zst
nvidia-uvm.ko.zst
nvidia.ko.zst
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2037400/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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] [NEW] Unable to capture kernel crash dump using arm64 mantic 6.5.0-6-generic -proposed kernel
Public bug reported: 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. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037398 Title: Unable to capture kernel crash dump using arm64 mantic 6.5.0-6-generic -proposed kernel Status in linux package in Ubuntu: New 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
[Kernel-packages] [Bug 2036988] Re: Unable to boot on Lenovo L590 Laptop
Hrm. Can you show the output of `dpkg -l | grep linux-'? -- 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/2036988 Title: Unable to boot on Lenovo L590 Laptop Status in linux-hwe-6.2 package in Ubuntu: New Bug description: With Kernel images 6.2.0-32 and 6.2.0-33, I can no longer boot ubuntu on my laptop. On regular graphic boot it just hangs on a black screen. With advanced boot options and selecting the current kernel, it hangs immediately after "Loading initial ramdisk" without any error message. I have to select an older kernel release to boot. 6.2.0-26 is the latest I know to work. We have another identical laptop of type Lenovo L590 also installed with Ubuntu and it shows the same behavior, so it's likely not a hardware problem on my device. The CPU type is Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz. 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-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: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 16:51:07 2023 InstallationDate: Installed on 2020-04-24 (1245 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-11-20 (304 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] Re: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform
In summary, need blob of following paths: * intel/ibt-0180-0041.ddc * intel/ibt-0180-0041.sfi * iwlwifi-ma-b0-gf-a0-83.ucode * iwlwifi-ma-b0-gf-a0.pnvm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] [NEW] Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform
Public bug reported: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2037255 somerville ** Tags added: oem-priority originate-from-2037255 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037224] Re: Multiple RTL8851BE BT stability issues
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-firmware (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-firmware (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Mantic)
Importance: Undecided => High
** Changed in: linux-firmware (Ubuntu Mantic)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2037224
Title:
Multiple RTL8851BE BT stability issues
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
In Progress
Bug description:
[SRU Justification]
[Impact]
There are multiple stability issues for RTL8851B.
Issue-1:
After disabling BT and leaving it idle for a period, manually turning on the
RTL8851BE will fail.
Issue-2:
Failed to probe Bluetooth USB interface after resumed from suspend. There may
be
either failure to read device descriptors:
usb 1-14: device descriptor read/64, error -71
or tx command timeout:
Bluetooth: hci0: Opcode 0x2041 failed: -110
Bluetooth: hci0: command 0x2041 tx timeout
[Fix]
Upstream commit addc33924 ("rtl_bt: Update RTL8851B BT USB firmware to
0x048A_D230").
[Test Case]
$ checkbox-cli run
com.canonical.plainbox::suspend/suspend_advanced_auto
[Where problems could occur]
This updates opaque firmware blobs, so it could bring further stability issues
and/or power consumption changes.
[Other Info]
While RTL8851B is only supported in oem-6.5 and linux/mantic >= 6.4, only
jammy
and mantic are nominated for fix.
= original bug report ==
[issue 1]
After disabling BT and leaving it idle for a period, manually turning
on the RTL8851BE will fail. (Can't reproduce on Wifi functionality.)
Test step:
1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0)
2. Check BT function after boot into OS.
3. Manually turn OFF BT function. Then wait for 1 minute.
4. Manually turn ON the BT function.
5. Unable to enable BT function. (issue occurs)
[issue 2]
System usb got tx command timeout after suspend resume.
Log:
Got read usb descriptor fail after suspend resume.
Sep 11 16:37:37 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
Sep 11 16:37:37 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:39 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
And tx command timeout.
Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: Opcode 0x2041 failed: -110
Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: command 0x2041 tx timeout
Sep 11 16:37:41 ubuntu kernel: usb 1-14: new full-speed USB device number 4
using xhci_hcd
Sep 11 16:37:41 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Test step:
1. Install dell-bto-jammy-jellyfish-abra-X96-20230822-1.iso
2. Boot into OS
3. checkbox-cli run com.canonical.plainbox::suspend/suspend_advanced_auto
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037224/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037224] Re: Multiple RTL8851BE BT stability issues
SRU:
* https://lists.ubuntu.com/archives/kernel-team/2023-September/143190.html
(jammy)
* https://lists.ubuntu.com/archives/kernel-team/2023-September/143191.html
(mantic)
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ There are multiple stability issues for RTL8851B.
+
+ Issue-1:
+
+ After disabling BT and leaving it idle for a period, manually turning on the
+ RTL8851BE will fail.
+
+ Issue-2:
+
+ Failed to probe Bluetooth USB interface after resumed from suspend. There may
be
+ either failure to read device descriptors:
+
+ usb 1-14: device descriptor read/64, error -71
+
+ or tx command timeout:
+
+ Bluetooth: hci0: Opcode 0x2041 failed: -110
+ Bluetooth: hci0: command 0x2041 tx timeout
+
+ [Fix]
+
+ Upstream commit addc33924 ("rtl_bt: Update RTL8851B BT USB firmware to
+ 0x048A_D230").
+
+ [Test Case]
+
+ $ checkbox-cli run com.canonical.plainbox::suspend/suspend_advanced_auto
+
+ [Where problems could occur]
+
+ This updates opaque firmware blobs, so it could bring further stability issues
+ and/or power consumption changes.
+
+ [Other Info]
+
+ While RTL8851B is only supported in oem-6.5 and linux/mantic >= 6.4, only
jammy
+ and mantic are nominated for fix.
+
+ = original bug report ==
+
[issue 1]
After disabling BT and leaving it idle for a period, manually turning on
the RTL8851BE will fail. (Can't reproduce on Wifi functionality.)
Test step:
1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0)
2. Check BT function after boot into OS.
3. Manually turn OFF BT function. Then wait for 1 minute.
4. Manually turn ON the BT function.
5. Unable to enable BT function. (issue occurs)
[issue 2]
System usb got tx command timeout after suspend resume.
Log:
Got read usb descriptor fail after suspend resume.
Sep 11 16:37:37 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
Sep 11 16:37:37 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:39 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
And tx command timeout.
Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: Opcode 0x2041 failed: -110
Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: command 0x2041 tx timeout
Sep 11 16:37:41 ubuntu kernel: usb 1-14: new full-speed USB device number 4
using xhci_hcd
Sep 11 16:37:41 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Test step:
1. Install dell-bto-jammy-jellyfish-abra-X96-20230822-1.iso
2. Boot into OS
3. checkbox-cli run com.canonical.plainbox::suspend/suspend_advanced_auto
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2037224
Title:
Multiple RTL8851BE BT stability issues
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
In Progress
Bug description:
[SRU Justification]
[Impact]
There are multiple stability issues for RTL8851B.
Issue-1:
After disabling BT and leaving it idle for a period, manually turning on the
RTL8851BE will fail.
Issue-2:
Failed to probe Bluetooth USB interface after resumed from suspend. There may
be
either failure to read device descriptors:
usb 1-14: device descriptor read/64, error -71
or tx command timeout:
Bluetooth: hci0: Opcode 0x2041 failed: -110
Bluetooth: hci0: command 0x2041 tx timeout
[Fix]
Upstream commit addc33924 ("rtl_bt: Update RTL8851B BT USB firmware to
0x048A_D230").
[Test Case]
$ checkbox-cli run
com.canonical.plainbox::suspend/suspend_advanced_auto
[Where problems could occur]
This updates opaque firmware blobs, so it could bring further stability issues
and/or power consumption changes.
[Other Info]
While RTL8851B is only supported in oem-6.5 and linux/mantic >= 6.4, only
jammy
and mantic are nominated for fix.
= original bug report ==
[issue 1]
After disabling BT and leaving it idle for a period, manually turning
on the RTL8851BE will fail. (Can't reproduce on Wifi functionality.)
Test step:
1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0)
2. Check BT function after boot into OS.
3. Manually turn OFF BT function. Then wait for 1 minute.
4. Manually turn ON the BT function.
5. Unable to enable BT function. (issue occurs)
[issue 2]
System usb got tx command timeout after
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
make: Entering directory '/usr/src/linux-headers-6.2.0-33-generic' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc-11 (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0 You are using: gcc-11 (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0 scripts/Makefile.build:41: /home/souvik/Makefile: No such file or directory make[1]: *** No rule to make target '/home/souvik/Makefile'. Stop. make: *** [Makefile:2026: /home/souvik] Error 2 make: Leaving directory '/usr/src/linux-headers-6.2.0-33-generic' cp: cannot stat 'uvcvideo.ko': No such file or directory This error while running your script @giuliano69 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware
[Kernel-packages] [Bug 2037224] Re: Multiple RTL8851BE BT stability issues
Accepted in upstream as commit addc33924 ("rtl_bt: Update RTL8851B BT
USB firmware to 0x048A_D230").
** Summary changed:
- Failed to manually enable the RTL8851BE BT function
+ Multiple RTL8851BE BT stability issues
** Description changed:
+ [issue 1]
+
After disabling BT and leaving it idle for a period, manually turning on
the RTL8851BE will fail. (Can't reproduce on Wifi functionality.)
Test step:
1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0)
2. Check BT function after boot into OS.
3. Manually turn OFF BT function. Then wait for 1 minute.
4. Manually turn ON the BT function.
5. Unable to enable BT function. (issue occurs)
+
+ [issue 2]
+
+ System usb got tx command timeout after suspend resume.
+
+ Log:
+
+ Got read usb descriptor fail after suspend resume.
+
+ Sep 11 16:37:37 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
+ Sep 11 16:37:37 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
+ Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
+ Sep 11 16:37:38 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
+ Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
+ Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
+ Sep 11 16:37:39 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
+
+ And tx command timeout.
+
+ Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: Opcode 0x2041 failed: -110
+ Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: command 0x2041 tx timeout
+ Sep 11 16:37:41 ubuntu kernel: usb 1-14: new full-speed USB device number 4
using xhci_hcd
+ Sep 11 16:37:41 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
+
+ Test step:
+ 1. Install dell-bto-jammy-jellyfish-abra-X96-20230822-1.iso
+ 2. Boot into OS
+ 3. checkbox-cli run com.canonical.plainbox::suspend/suspend_advanced_auto
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2037224
Title:
Multiple RTL8851BE BT stability issues
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
New
Status in linux-firmware source package in Jammy:
New
Status in linux-firmware source package in Mantic:
New
Bug description:
[issue 1]
After disabling BT and leaving it idle for a period, manually turning
on the RTL8851BE will fail. (Can't reproduce on Wifi functionality.)
Test step:
1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0)
2. Check BT function after boot into OS.
3. Manually turn OFF BT function. Then wait for 1 minute.
4. Manually turn ON the BT function.
5. Unable to enable BT function. (issue occurs)
[issue 2]
System usb got tx command timeout after suspend resume.
Log:
Got read usb descriptor fail after suspend resume.
Sep 11 16:37:37 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
Sep 11 16:37:37 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:39 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
And tx command timeout.
Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: Opcode 0x2041 failed: -110
Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: command 0x2041 tx timeout
Sep 11 16:37:41 ubuntu kernel: usb 1-14: new full-speed USB device number 4
using xhci_hcd
Sep 11 16:37:41 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Test step:
1. Install dell-bto-jammy-jellyfish-abra-X96-20230822-1.iso
2. Boot into OS
3. checkbox-cli run com.canonical.plainbox::suspend/suspend_advanced_auto
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037224/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037273] Re: Realtek 8852CE WiFi 6E country code udpates
SRU:
* https://lists.ubuntu.com/archives/kernel-team/2023-September/143188.html
(mantic)
* http://10.131.201.69/kernel/jammy-linux-oem/pulls/74 (oem-6.5)
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ Missing WiFi 6G band for interested countries.
+
+ [Fix]
+
+ Upstream v6.6-rc1 commit f585f4ab0b99 ("wifi: rtw89: regd: update
+ regulatory map to R64-R43").
+
+ [Test Case]
+
+ Use `iw list` to check if 6G bands are then enabled.
+
+ [Where problems could occur]
+
+ This enables corresponding 6G bands for rtw89 driven devices. There
+ should be no other side effects.
+
+ [Other Info]
+
+ Nominated for oem-6.5 and mantic. Since this is in v6.6-rc1, Unstable is
+ skipped.
+
+ = original bug report ==
+
Proposed fix:
https://patchwork.kernel.org/project/linux-wireless/patch/20230815120253.9901-1-pks...@realtek.com/
Accepted in wireless-next as commit f585f4ab0b99 ("wifi: rtw89: regd: update
regulatory map to R64-R43") and is in v6.6-rc1 now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037273
Title:
Realtek 8852CE WiFi 6E country code udpates
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing WiFi 6G band for interested countries.
[Fix]
Upstream v6.6-rc1 commit f585f4ab0b99 ("wifi: rtw89: regd: update
regulatory map to R64-R43").
[Test Case]
Use `iw list` to check if 6G bands are then enabled.
[Where problems could occur]
This enables corresponding 6G bands for rtw89 driven devices. There
should be no other side effects.
[Other Info]
Nominated for oem-6.5 and mantic. Since this is in v6.6-rc1, Unstable
is skipped.
= original bug report ==
Proposed fix:
https://patchwork.kernel.org/project/linux-wireless/patch/20230815120253.9901-1-pks...@realtek.com/
Accepted in wireless-next as commit f585f4ab0b99 ("wifi: rtw89: regd: update
regulatory map to R64-R43") and is in v6.6-rc1 now.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037273/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037375] [NEW] package linux-image-6.2.0-33-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-6.2.0-33-generic
Public bug reported: Update manager can't reports a bug. updates are not executed ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic (not installed) ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 26 06:16:15 2023 ErrorMessage: impossible de copier les données extraites pour « ./boot/vmlinuz-6.2.0-33-generic » vers « /boot/vmlinuz-6.2.0-33-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) InstallationDate: Installed on 2023-04-25 (153 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A 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 (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-6.2.0-33-generic » vers « /boot/vmlinuz-6.2.0-33-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) UpgradeStatus: Upgraded to jammy on 2023-04-25 (153 days ago) ** 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/2037375 Title: package linux-image-6.2.0-33-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-6.2.0-33-generic » vers « /boot/vmlinuz-6.2.0-33-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Update manager can't reports a bug. updates are not executed ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic (not installed) ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 26 06:16:15 2023 ErrorMessage: impossible de copier les données extraites pour « ./boot/vmlinuz-6.2.0-33-generic » vers « /boot/vmlinuz-6.2.0-33-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) InstallationDate: Installed on 2023-04-25 (153 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A 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 (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-6.2.0-33-generic » vers « /boot/vmlinuz-6.2.0-33-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) UpgradeStatus: Upgraded to jammy on 2023-04-25 (153 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2037375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025672] Re: Support Realtek RTL8852CE WiFi 6E/BT Combo
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2025672 Title: Support Realtek RTL8852CE WiFi 6E/BT Combo Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Invalid Status in linux-firmware source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2025672 [Impact] Realtek RTL8852CE WiFi 6E/BT Combo takes new firmware to enable 6E features. [Fix] * Bluetooth - kernel + 8b1d66b50437 Bluetooth: btrtl: Add support for RTL8852C (v5.19-rc1) + 9a24ce5e29b1 Bluetooth: btrtl: Firmware format v2 support (v6.4-rc1) + bd003fb338af Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C (linux-next) - firmware + 8a2d81176 rtl_bt: Add firmware and config files for RTL8852C (jammy) + d3c922805 rtl_bt: Update RTL8852C BT USB firmware to 0xDFB8_5A33 (jammy) + cfbd66816 rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A (jammy) + c51488ffb rtl_bt: Update RTL8852C BT USB firmware to 0xD7B8_FABF (lunar) + 55e744853 rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225 (mantic, change binary format) + 7ed62638b Revert "rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225" (mantic) + 42d31f8f6 rtl_bt: Add firmware v2 file for RTL8852C (mantic) * WiFi - kernel + 59b4cc439f18 wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() (linux-next) - firmware + d2aac63b8 rtw89: 8852c: update fw to v0.27.56.1 (jammy) + 9e91f0ce6 rtw89: 8852c: update fw to v0.27.56.8 (lunar) + c9c19583f rtw89: 8852c: update fw to v0.27.56.9 (lunar) + fc5a25fa0 rtw89: 8852c: update fw to v0.27.56.10 (lunar) + b9c8e9f70 rtw89: 8852c: update fw to v0.27.56.13 (mantic) [Test Case] Basic bluetooth, wifi operations. This is verified with all related kernel/series combinations: * linux-hwe5.19/jammy * linux-hwe-6.2/jammy * linux-oem-6.0/jammy * linux-oem-6.1/jammy * linux-oem-6.5/jammy * ilnux/mantic [Where problems could occur] New device firmware blob, even blob format changes. Expect bugs, power consumption issues, etc. [Other Info] Bluetooth V2 firmware support was first landed to v6.4, and the binary rename in linux-next now. To preserve consistency, Unstable, Mantic and OEM-6.5 kernels are nominated for fix. As for linux-firmware, the only target is Jammy. == original bug description == Support Realtek RTL8852CE WiFi 6E/BT Combo * Bluetooth - kernel + 8b1d66b50437 Bluetooth: btrtl: Add support for RTL8852C (v5.19-rc1) + 9a24ce5e29b1 Bluetooth: btrtl: Firmware format v2 support (v6.4-rc1) + bd003fb338af Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C (linux-next) - firmware + 8a2d81176 rtl_bt: Add firmware and config files for RTL8852C (jammy) + d3c922805 rtl_bt: Update RTL8852C BT USB firmware to 0xDFB8_5A33 (jammy) + cfbd66816 rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A (jammy) + c51488ffb rtl_bt: Update RTL8852C BT USB firmware to 0xD7B8_FABF (lunar) + 55e744853 rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225 (mantic, change binary format) + 7ed62638b Revert "rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225" (mantic) + 42d31f8f6 rtl_bt: Add firmware v2 file for RTL8852C (mantic) * WiFi - kernel + 59b4cc439f18 wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() (linux-next) - firmware + d2aac63b8 rtw89: 8852c: update fw to v0.27.56.1 (jammy) + 9e91f0ce6 rtw89: 8852c: update fw to v0.27.56.8 (lunar) + c9c19583f rtw89: 8852c: update fw to v0.27.56.9 (lunar) + fc5a25fa0 rtw89: 8852c: update fw to v0.27.56.10 (lunar) + b9c8e9f70 rtw89: 8852c: update fw to v0.27.56.13 (mantic) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 2037273] Re: Realtek 8852CE WiFi 6E country code udpates
** Description changed:
Proposed fix:
https://patchwork.kernel.org/project/linux-wireless/patch/20230815120253.9901-1-pks...@realtek.com/
- Accepted in wireless-next as commit f585f4ab0b99 ("wifi: rtw89: regd: update
regulatory map to R64-R43").
+ Accepted in wireless-next as commit f585f4ab0b99 ("wifi: rtw89: regd: update
regulatory map to R64-R43") and is in v6.6-rc1 now.
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux (Ubuntu Mantic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037273
Title:
Realtek 8852CE WiFi 6E country code udpates
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
Proposed fix:
https://patchwork.kernel.org/project/linux-wireless/patch/20230815120253.9901-1-pks...@realtek.com/
Accepted in wireless-next as commit f585f4ab0b99 ("wifi: rtw89: regd: update
regulatory map to R64-R43") and is in v6.6-rc1 now.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037273/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037261] Re: Kernel 6.2.0-33 - Unable to power down (shutdown) or suspend
** Summary changed: - Kernel 6.2.0-33 + Kernel 6.2.0-33 - Unable to power down (shutdown) or suspend ** Summary changed: - Kernel 6.2.0-33 - Unable to power down (shutdown) or suspend + 6.2.0-33 - Unable to power down (shutdown) or suspend -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037261 Title: 6.2.0-33 - Unable to power down (shutdown) or suspend Status in linux package in Ubuntu: Confirmed Bug description: Unable to power down (shutdown) or suspend. Very slow boot up. --- Ubuntu 5.15.0-84.93-generic 5.15.116 (Restored via timeshift) --- HArdware: Dell XPS-17 (9710) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lewis 1834 F pulseaudio /dev/snd/controlC1: lewis 1834 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.2 InstallationDate: Installed on 2023-09-17 (8 days ago) InstallationMedia: Linux Mint 21.2 "Victoria" - Release amd64 20230711 MachineType: Dell Inc. XPS 17 9710 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=UUID=8b01a895-ce2e-405e-b5f3-47167dd8ffeb ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116 RelatedPackageVersions: linux-restricted-modules-5.15.0-84-generic N/A linux-backports-modules-5.15.0-84-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.18 Tags: victoria Uname: Linux 5.15.0-84-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2023 dmi.bios.release: 1.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.0 dmi.board.name: 0Y1K2K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd06/06/2023:br1.21:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn0Y1K2K:rvrA00:cvnDellInc.:ct10:cvr:sku0A5D: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
