FC18 kernel crash

Discussions related to using VirtualBox on Linux hosts.
Post Reply
csreynolds
Posts: 3
Joined: 20. Mar 2013, 16:14

FC18 kernel crash

Post by csreynolds »

I have run in to a problem that I cannot figure out. I'm running FC18 with the latest kernel. The problem did not happen with kernel 3.7.x

All my VMs will crash(completely hang and not respond) and have to be forcefully killed at seemingly random times. The guest OS does not matter. I have Windows and Linux guests both crashing.

I thought something might be goofed up with my FC install, so i did a fresh OS install and I still get the same crashes.

I'm assuming there is something goofy between the 3.8.x kernel and Virtualbox, but I cannot see what.

Any help would be appreciated.

Code: Select all

[creynolds@localhost ~]$ uname -a
Linux localhost.localdomain 3.8.3-203.fc18.x86_64 #1 SMP Mon Mar 18 12:59:28 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Code: Select all

[creynolds@localhost ~]$ rpm -qa | grep Virt
kmod-VirtualBox-3.8.3-203.fc18.x86_64-4.2.10-1.fc18.1.x86_64
VirtualBox-4.2.10-1.fc18.x86_64
important parts during crash from /var/log/messages

Code: Select all

Mar 20 13:54:45 localhost kernel: [ 8110.143146] BUG: unable to handle kernel paging request at 00007f733854b140
Mar 20 13:54:45 localhost kernel: [ 8110.143153] IP: [<ffffffffa108207a>] 0xffffffffa1082079
Mar 20 13:54:45 localhost kernel: [ 8110.143158] PGD 593d03067 PUD 5938ba067 PMD 593f04067 PTE 595118166
Mar 20 13:54:45 localhost kernel: [ 8110.143162] Oops: 0000 [#2] SMP 
Mar 20 13:54:45 localhost kernel: [ 8110.143165] Modules linked in: fuse ebtable_nat nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE bnep bluetooth rfkill ip6table_mangle ip6t_REJECT nf_conntrack_i
pv6 nf_defrag_ipv6 iptable_nat nf_nat_ipv4 nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ebtable_filter ebtables binfmt_misc ip6table_filter ip6_tables be2iscsi iscsi_boot_sysf
s bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi snd_hda_codec_hdmi snd_hda_codec_realtek nvi
dia(POF) snd_hda_intel snd_hda_codec snd_usb_audio snd_usbmidi_lib snd_hwdep snd_rawmidi snd_seq snd_seq_device snd_pcm snd_page_alloc snd_timer e1000e snd iTCO_wdt soundcore vboxnetadp(OF) vboxnetflt(OF) vboxdr
v(OF) iTCO_vendor_support lpc_ich mfd_core i7core_edac i2c_i801 edac_core i2c_core ioatdma dca vhost_net coretemp serio_raw microcode tun macvtap macvlan kvm_intel kvm uinput mptsas firewire_ohci mptscsih mptbas
e firewire_core crc32c_intel crc_itu_t megaraid_sas scsi_transport_sas
Mar 20 13:54:45 localhost kernel: [ 8110.143202] CPU 19 
Mar 20 13:54:45 localhost kernel: [ 8110.143205] Pid: 5580, comm: EMT-0 Tainted: PF     D  C O 3.8.3-203.fc18.x86_64 #1 Supermicro X8DA3/X8DA3
Mar 20 13:54:45 localhost kernel: [ 8110.143207] RIP: 0010:[<ffffffffa108207a>]  [<ffffffffa108207a>] 0xffffffffa1082079
Mar 20 13:54:45 localhost kernel: [ 8110.143210] RSP: 0018:ffff880bb6317bc8  EFLAGS: 00010246
Mar 20 13:54:45 localhost kernel: [ 8110.143211] RAX: 0000000000000000 RBX: ffffc90017efc000 RCX: 0000000000000000
Mar 20 13:54:45 localhost kernel: [ 8110.143213] RDX: 0000000000000000 RSI: 0000000000000007 RDI: ffffc90017ee1000
Mar 20 13:54:45 localhost kernel: [ 8110.143214] RBP: ffff880bb6317c78 R08: 00007f733854b140 R09: 000000021e7fc000
Mar 20 13:54:45 localhost kernel: [ 8110.143215] R10: 0000000000000008 R11: 0000000000000000 R12: 000000021e7fc000
Mar 20 13:54:45 localhost kernel: [ 8110.143216] R13: 0000000000000002 R14: ffffc90017ee1000 R15: 0000000000000000
Mar 20 13:54:45 localhost kernel: [ 8110.143217] FS:  00007f733bd35700(0000) GS:ffff880c3fce0000(0000) knlGS:0000000000000000
Mar 20 13:54:45 localhost kernel: [ 8110.143218] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Mar 20 13:54:45 localhost kernel: [ 8110.143219] CR2: 00007f733854b140 CR3: 00000005991db000 CR4: 00000000000027e0
Mar 20 13:54:45 localhost kernel: [ 8110.143221] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Mar 20 13:54:45 localhost kernel: [ 8110.143222] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Mar 20 13:54:45 localhost kernel: [ 8110.143223] Process EMT-0 (pid: 5580, threadinfo ffff880bb6316000, task ffff880c1bcf2ec0)
Mar 20 13:54:45 localhost kernel: [ 8110.143224] Stack:
Mar 20 13:54:45 localhost kernel: [ 8110.143225]  ffff880bb6317bf8 00007f733a7d5b60 00007f733a7d5b60 ffffc90017ee1000
Mar 20 13:54:45 localhost kernel: [ 8110.143228]  0000000000000000 00007f733a7be9e0 ffff81e060000fff 0000000000000000
Mar 20 13:54:45 localhost kernel: [ 8110.143231]  000000021e7fc000 880c3fce4000007f ffffc90017efcb40 ffff880bb6317ca7
Mar 20 13:54:45 localhost kernel: [ 8110.143233] Call Trace:
Mar 20 13:54:45 localhost kernel: [ 8110.143248]  [<ffffffffa0202a57>] ? supdrvIOCtlFast+0x77/0xa0 [vboxdrv]
Mar 20 13:54:45 localhost kernel: [ 8110.143254]  [<ffffffffa01ff37c>] ? VBoxDrvLinuxIOCtl_4_2_10+0x4c/0x1e0 [vboxdrv]
Mar 20 13:54:45 localhost kernel: [ 8110.143260]  [<ffffffff811aef89>] ? do_vfs_ioctl+0x99/0x580
Mar 20 13:54:45 localhost kernel: [ 8110.143265]  [<ffffffff8129a37a>] ? inode_has_perm.isra.31.constprop.61+0x2a/0x30
Mar 20 13:54:45 localhost kernel: [ 8110.143269]  [<ffffffff8129bbb7>] ? file_has_perm+0x97/0xb0
Mar 20 13:54:45 localhost kernel: [ 8110.143271]  [<ffffffff811af501>] ? sys_ioctl+0x91/0xb0
Mar 20 13:54:45 localhost kernel: [ 8110.143275]  [<ffffffff81658699>] ? system_call_fastpath+0x16/0x1b
Mar 20 13:54:45 localhost kernel: [ 8110.143276] Code: 55 c8 4c 89 ce 4c 89 f7 48 89 4d 88 4c 89 4d 90 e8 2c ab 00 00 85 c0 89 c2 48 8b 4d 88 4c 8b 4d 90 0f 88 36 06 00 00 4c 8b 45 c8 <41> f7 00 02 02 00 00 0f 85 49 01 00 00 48 85 c9 0f 84 98 00 00 
Mar 20 13:54:45 localhost kernel: [ 8110.143294] RIP  [<ffffffffa108207a>] 0xffffffffa1082079
Mar 20 13:54:45 localhost kernel: [ 8110.143297]  RSP <ffff880bb6317bc8>
Mar 20 13:54:45 localhost kernel: [ 8110.143297] CR2: 00007f733854b140
Mar 20 13:54:45 localhost kernel: [ 8110.143302] ---[ end trace 9600081150f1d6ab ]---
vbox.log from crash attached.
Attachments
VBox.log
(58.81 KiB) Downloaded 13 times
csreynolds
Posts: 3
Joined: 20. Mar 2013, 16:14

Re: FC18 kernel crash

Post by csreynolds »

I can boot into an older kernel and i have no problems. Is there a way I can get more detailed info on why the crash is happening? I'd like to help resolve this issue if i can.

Code: Select all

[creynolds@localhost trunk]$ uname -a
Linux localhost.localdomain 3.6.10-4.fc18.x86_64 #1 SMP Tue Dec 11 18:01:27 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
I would try the 3.7.x kernel but its no longer available in repos via yum. Not messing with that jazz.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: FC18 kernel crash

Post by Perryg »

These kinds of problems that are reproducible should be reported to bugtracker. If you have not signed on to Bugtracker before you will need to select a new Nickname to be able to report issues.
It would also help if you can post the ticket number here so other can see the progress, add information, or see the final results.

Note: this may not even be a bug in VirtualBox, but it is effecting VirtualBox so I would search for a ticket and add to it or create a new one.
csreynolds
Posts: 3
Joined: 20. Mar 2013, 16:14

Re: FC18 kernel crash

Post by csreynolds »

:D already on top of ticket creation. I neglected to link this post to the issue. My bad. :oops:

https://www.virtualbox.org/ticket/11610
Post Reply