kernel crash

Bug #1988688 reported by Aaahh Ahh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Happens randomly after some period of time after boot (sometimes 10 minutes, sometimes 3 hours), had Spotify open. Sorry for the lack of detail.

ProblemType: KernelCrash
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-15-generic 5.19.0-15.15
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: aaahh 3617 F.... pipewire
                      aaahh 3621 F.... wireplumber
 /dev/snd/pcmC0D0p: aaahh 3617 F...m pipewire
 /dev/snd/seq: aaahh 3617 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sun Sep 4 14:32:42 2022
InstallationDate: Installed on 2022-06-10 (86 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220608)
MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop X3400PA_K3400PA
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=b4b8a8e0-4db7-4db5-87ef-acecd2aed677 ro quiet splash crashkernel=512M-:192M vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-15-generic N/A
 linux-backports-modules-5.19.0-15-generic N/A
 linux-firmware 20220831.gitd3c92280-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/14/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: X3400PA.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X3400PA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX3400PA.300:bd02/14/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopX3400PA_K3400PA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX3400PA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Vivobook
dmi.product.name: Vivobook_ASUSLaptop X3400PA_K3400PA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Aaahh Ahh (woohoomoo2u) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Aaahh Ahh (woohoomoo2u) wrote :

Did not happen on 5.15, suspend is also broken with the new update to 5.19, along with virtualbox/qemu

Revision history for this message
Matthew Ruffell (mruffell) wrote :
Download full text (3.4 KiB)

This is a pretty bizarre crash to tell you the truth. It occurred during execution of a userspace program, doing a syscall to kernel space. There's a bunch of userspace addresses in the registers, stack and the faulting address, and the call trace has consecutive syscalls, and we fault in some general cputime accounting.

I'll have a look, but in the meantime, are you interested in testing the 5.19.0-15-generic kernel that just came to Kinetic, instead of the mainline 5.19.3-051903-generic kernel you were using?

[ 9598.344441] general protection fault, probably for non-canonical address 0x7fffffff80000037: 0000 [#1] PREEMPT SMP NOPTI
[ 9598.344452] CPU: 7 PID: 11108 Comm: DOM Worker Kdump: loaded Not tainted 5.19.3-051903-generic #202208211442
[ 9598.344458] Hardware name: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop X3400PA_K3400PA/X3400PA, BIOS X3400PA.300 02/14/2022
[ 9598.344460] RIP: 0010:thread_group_cputime+0xa6/0x150
[ 9598.344470] Code: 48 89 33 49 8b 8c 24 a0 02 00 00 48 89 4b 10 49 8b 95 f8 0b 00 00 4c 8b 42 10 48 83 c2 10 49 8d 80 80 f5 ff ff 49 39 d0 74 41 <48> 8b 90 b8 0a 00 00 48 03 b8 b0 0a 00 00 48 89 7b 08 48 01 d6 48
[ 9598.344474] RSP: 0018:ffffaac8c2ed7c98 EFLAGS: 00010887
[ 9598.344480] RAX: 7fffffff7ffff57f RBX: ffffaac8c2ed7cc8 RCX: 8000001bf8b9cad6
[ 9598.344483] RDX: ffff904008952890 RSI: 800000057eb34cff RDI: 800000153ced94ff
[ 9598.344486] RBP: ffffaac8c2ed7cb8 R08: 7fffffff7fffffff R09: 00000000000001c0
[ 9598.344489] R10: 0000000000000000 R11: 0000000000000000 R12: ffff904008952880
[ 9598.344491] R13: ffff90405e7ba000 R14: ffff904008952a2c R15: 0000000000000000
[ 9598.344494] FS: 00007f6276992700(0000) GS:ffff9041837c0000(0000) knlGS:0000000000000000
[ 9598.344498] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 9598.344501] CR2: 00007f62347b9000 CR3: 000000010bfac005 CR4: 0000000000770ee0
[ 9598.344505] PKRU: 55555554
[ 9598.344507] Call Trace:
[ 9598.344510] <TASK>
[ 9598.344514] thread_group_cputime_adjusted+0x33/0x80
[ 9598.344520] getrusage+0xac/0x430
[ 9598.344527] __do_sys_getrusage+0x4b/0x90
[ 9598.344534] __x64_sys_getrusage+0x15/0x20
[ 9598.344539] do_syscall_64+0x59/0x90
[ 9598.344546] ? __secure_computing+0x93/0xf0
[ 9598.344553] ? syscall_trace_enter.constprop.0+0xa3/0x1b0
[ 9598.344558] ? exit_to_user_mode_prepare+0x37/0xb0
[ 9598.344562] ? syscall_exit_to_user_mode+0x26/0x50
[ 9598.344567] ? do_syscall_64+0x69/0x90
[ 9598.344573] ? exit_to_user_mode_prepare+0x95/0xb0
[ 9598.344576] ? syscall_exit_to_user_mode+0x26/0x50
[ 9598.344580] ? do_syscall_64+0x69/0x90
[ 9598.344586] ? syscall_exit_to_user_mode+0x26/0x50
[ 9598.344590] ? do_syscall_64+0x69/0x90
[ 9598.344595] ? exc_page_fault+0x87/0x180
[ 9598.344600] entry_SYSCALL_64_after_hwframe+0x63/0xcd
[ 9598.344605] RIP: 0033:0x7f62b200edeb
[ 9598.344610] Code: 8b 15 a9 80 0d 00 f7 d8 64 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa b8 62 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 75 80 0d 00 f7 d8 64 89 01 48
[ 9598.344614] RSP: 002b:00007f6276991088 EFLAGS: 00000246 ORIG_RAX: 0000000000000062
[ 9598.344619] RAX: ffffffffffffffda RBX: 00007f626c8875a0 RCX: 00007f62b200edeb
[ 9598.344622] ...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.