From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 216349] Kernel panic in a Ubuntu VM running on Proxmox
Date: Sat, 13 Aug 2022 13:30:05 +0000 [thread overview]
Message-ID: <bug-216349-28872-FKkd5elcW1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216349-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216349
--- Comment #10 from John Park (jdpark.au@gmail.com) ---
I experienced another panic today. Log below
---
[38049.665307] traps: PANIC: double fault, error_code: 0x0
[38049.665352] double fault: 0000 [#1] SMP PTI
[38049.665362] CPU: 1 PID: 3295 Comm: lighttpd Not tainted 5.15.0-46-generic
#49-Ubuntu
[38049.665388] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
[38049.665395] RIP: 0010:error_entry+0x0/0x130
[38049.665466] Code: de eb 0a f3 48 0f ae db e9 21 fd ff ff 85 db 0f 85 19 fd
ff ff 0f 01 f8 e9 11 fd ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 <fc> 56 48
8b 74 24 08 48 89 7c 24 08 52 51 50 41 50 41 51 41 52 41
[38049.665471] RSP: 0018:ffffb507830aa35d EFLAGS: 00010002
[38049.665480] RAX: 00007ffe5be0c194 RBX: 00007ffe5be0c1e0 RCX:
00007ffe5be0c194
[38049.665484] RDX: 0000000000000070 RSI: 0000000000000010 RDI:
ffffb507830a3cf8
[38049.665487] RBP: ffffb507830a3cd8 R08: 0000000000000001 R09:
0000000000000000
[38049.665491] R10: 0000000000000001 R11: 0000000000000000 R12:
ffff91c59f1a9880
[38049.665494] R13: ffff91c4d1be2d80 R14: 0000000000080800 R15:
ffff91c49d517700
[38049.665499] FS: 00007f96e38ef680(0000) GS:ffff91c5bbd00000(0000)
knlGS:0000000000000000
[38049.665503] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[38049.665507] CR2: ffffb507830aa348 CR3: 00000000090c0000 CR4:
00000000000006e0
[38049.665518] Call Trace:
[38049.665542] Modules linked in: cp210x usbserial cdc_acm tls veth xt_nat
xt_tcpudp xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo nft_counter
xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc overlay
sch_fq_codel joydev input_leds serio_raw qemu_fw_cfg mac_hid dm_multipath
scsi_dh_rdac scsi_dh_emc scsi_dh_alua netconsole ipmi_devintf pstore_blk mtd
ramoops pstore_zone reed_solomon ipmi_msghandler msr efi_pstore ip_tables
x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq
libcrc32c raid1 raid0 multipath linear bochs drm_vram_helper drm_ttm_helper ttm
drm_kms_helper hid_generic syscopyarea sysfillrect sysimgblt fb_sys_fops usbhid
cec rc_core xhci_pci hid psmouse xhci_pci_renesas drm i2c_piix4 pata_acpi
virtio_net net_failover failover virtio_scsi floppy
[38049.687192] ---[ end trace e501d4c27d1b1728 ]---
[38049.687196] RIP: 0010:error_entry+0x0/0x130
[38049.687203] Code: de eb 0a f3 48 0f ae db e9 21 fd ff ff 85 db 0f 85 19 fd
ff ff 0f 01 f8 e9 11 fd ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 <fc> 56 48
8b 74 24 08 48 89 7c 24 08 52 51 50 41 50 41 51 41 52 41
[38049.687227] RSP: 0018:ffffb507830aa35d EFLAGS: 00010002
[38049.687229] RAX: 00007ffe5be0c194 RBX: 00007ffe5be0c1e0 RCX:
00007ffe5be0c194
[38049.687230] RDX: 0000000000000070 RSI: 0000000000000010 RDI:
ffffb507830a3cf8
[38049.687231] RBP: ffffb507830a3cd8 R08: 0000000000000001 R09:
0000000000000000
[38049.687241] R10: 0000000000000001 R11: 0000000000000000 R12:
ffff91c59f1a9880
[38049.687242] R13: ffff91c4d1be2d80 R14: 0000000000080800 R15:
ffff91c49d517700
[38049.687243] FS: 00007f96e38ef680(0000) GS:ffff91c5bbd00000(0000)
knlGS:0000000000000000
[38049.687244] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[38049.687245] CR2: ffffb507830aa348 CR3: 00000000090c0000 CR4:
00000000000006e0
[38049.687249] Kernel panic - not syncing: Fatal exception in interrupt
[38049.687476] Kernel Offset: 0x34400000 from 0xffffffff81000000 (relocation
range: 0xffffffff80000000-0xffffffffbfffffff)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-08-13 13:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 12:13 [Bug 216349] New: Kernel panic in a Ubuntu VM running on Proxmox bugzilla-daemon
2022-08-10 13:44 ` [Bug 216349] " bugzilla-daemon
2022-08-10 14:29 ` bugzilla-daemon
2022-08-10 15:43 ` bugzilla-daemon
2022-08-11 5:50 ` bugzilla-daemon
2022-08-11 5:52 ` bugzilla-daemon
2022-08-11 8:18 ` bugzilla-daemon
2022-08-11 8:29 ` bugzilla-daemon
2022-08-13 2:55 ` bugzilla-daemon
2022-08-13 2:59 ` bugzilla-daemon
2022-08-13 13:30 ` bugzilla-daemon [this message]
2022-08-17 14:35 ` bugzilla-daemon
2022-08-17 15:37 ` bugzilla-daemon
2022-08-22 5:01 ` [Bug 216349] Kernel panics in VMs running on an Intel N5105 " bugzilla-daemon
2022-08-24 12:33 ` bugzilla-daemon
2022-10-27 23:55 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-216349-28872-FKkd5elcW1@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox