kernel crash dump caused by Google Chrome
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-
Mar 3 11:34:07 tteikhua check-new-
Mar 3 11:34:07 tteikhua systemd[2706]: update-
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]: [6910:6910:
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:0000000052
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags: 0x17ffffc000000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017ffffc0000000 dead000000000100 dead000000000122 0000000000000000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0000000000000001 0000000000000000 00008000ffffffff 0000000000000000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero _refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm input_leds xt_conntrack xt_MASQUERADE nf_conntrack_
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051] <TASK>
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069] get_page_
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle_
Mar 3 11:34:13 tteikhua kernel: [ 6927.882078] do_user_
Mar 3 11:34:13 tteikhua kernel: [ 6927.882080] exc_page_
Mar 3 11:34:13 tteikhua kernel: [ 6927.882083] asm_exc_
Mar 3 11:34:13 tteikhua kernel: [ 6927.882085] RIP: 0033:0x5650c5c1875a
Mar 3 11:34:13 tteikhua kernel: [ 6927.882087] Code: c0 e9 03 80 e1 07 be 01 00 00 00 d3 e6 40 0a 74 10 41 40 88 74 10 41 48 83 c3 08 49 8d 7f 18 4c 89 e0 48 d1 e8 89 03 0f 57 c0 <0f> 11 43 04 0f 11 43 14 c7 43 24 00 00 00 00 48 c7 43 28 ff ff ff
Mar 3 11:34:13 tteikhua kernel: [ 6927.882088] RSP: 002b:00007ffe3b
Mar 3 11:34:13 tteikhua kernel: [ 6927.882089] RAX: 00000b7d8114bea4 RBX: 000016fb03a79ff8 RCX: 0000000000018705
Mar 3 11:34:13 tteikhua kernel: [ 6927.882090] RDX: 000000000000061e RSI: 0000000000000020 RDI: 000016fb033170c0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882090] RBP: 00007ffe3b2d9400 R08: 0000000000989680 R09: 0000000000001b10
Mar 3 11:34:13 tteikhua kernel: [ 6927.882091] R10: 00007ffe3b31c090 R11: 00000000002b42b8 R12: 000016fb02297d48
Mar 3 11:34:13 tteikhua kernel: [ 6927.882091] R13: 000016fb035111b8 R14: 000016fb02297d18 R15: 000016fb033170a8
Mar 3 11:34:13 tteikhua kernel: [ 6927.882093] </TASK>
---
ProblemType: Bug
ApportVersion: 2.20.11-
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-02-23 (10 days ago)
InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS XTREME
Package: linux (not installed)
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.187.33
Tags: focal
Uname: Linux 5.15.0-60-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/18/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F32
dmi.board.
dmi.board.name: X570 AORUS XTREME
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: X570 MB
dmi.product.name: X570 AORUS XTREME
dmi.product.sku: Default string
dmi.product.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
affects: | ubuntu → linux (Ubuntu) |
tags: | added: focal |
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 2009114
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.