virtualbox.org

End user forums for VirtualBox
https://forums.virtualbox.org/

VirtualBox 2.0.4 gets segfault and whole computer stucked

https://forums.virtualbox.org/viewtopic.php?t=12679

Page 1 of 1

VirtualBox 2.0.4 gets segfault and whole computer stucked

Posted: 28. Dec 2008, 12:14
by ernetas

Code: Select all

Dec 28 11:53:57 mercury [ 4707.220292] VirtualBox[12522]: segfault at 1c ip b5dae376 sp b49f4ac0 error 4 in VBoxVMM.so[b5d15000+f1000]
Dec 28 11:53:57 mercury [ 4707.224367] mm/memory.c:130: bad pgd 000844fb.
Dec 28 11:53:57 mercury [ 4707.224380] ------------[ cut here ]------------
Dec 28 11:53:57 mercury [ 4707.224382] kernel BUG at lib/prio_tree.c:294!
Dec 28 11:53:57 mercury [ 4707.224384] invalid opcode: 0000 [#1] SMP
Dec 28 11:53:57 mercury [ 4707.224387] last sysfs file: /sys/devices/platform/it87.656/fan4_input
Dec 28 11:53:57 mercury [ 4707.224388] Modules linked in: vboxdrv tuner tda9887 tuner_simple tuner_types tvaudio bttv videodev v4l1_compat ir_common compat_ioctl32 i2c_algo_bit v4l2_common videobuf_dma_sg nvidia(P) videobuf_core btcx_risc tveeprom
Dec 28 11:53:57 mercury [ 4707.224399]
Dec 28 11:53:57 mercury [ 4707.224402] Pid: 12522, comm: VirtualBox Tainted: P           (2.6.28-gentoo #5) P35C-DS3R
Dec 28 11:53:57 mercury [ 4707.224404] EIP: 0060:[<c0393f35>] EFLAGS: 00010217 CPU: 0
Dec 28 11:53:57 mercury [ 4707.224408] EIP is at prio_tree_remove+0x5d/0x98
Dec 28 11:53:57 mercury [ 4707.224410] EAX: f32715a4 EBX: f32715a4 ECX: f3271580 EDX: f32715a4
Dec 28 11:53:57 mercury [ 4707.224412] ESI: f3342f78 EDI: 00000000 EBP: ec56dc9c ESP: ec56dc80
Dec 28 11:53:57 mercury [ 4707.224414]  DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
Dec 28 11:53:57 mercury [ 4707.224416] Process VirtualBox (pid: 12522, ti=ec56c000 task=f36458e0 task.ti=ec56c000)
Dec 28 11:53:57 mercury [ 4707.224417] Stack:
Dec 28 11:53:57 mercury [ 4707.224419]  f32715a4 ec56dc8c c026149c ec56dcf0 f32715a4 f347e6c0 00000000 ec56dcb8
Dec 28 11:53:57 mercury [ 4707.224423]  c025f2e5 f3342f78 00000000 f3271580 f347e6c0 f3271580 ec56dcc4 c026512e
Dec 28 11:53:57 mercury [ 4707.224427]  f3342f60 ec56dcd8 c0265159 f3141180 f3271580 00000000 ec56dcf8 c0263898
Dec 28 11:53:57 mercury [ 4707.224432] Call Trace:
Dec 28 11:53:57 mercury [ 4707.224434]  [<c026149c>] ? pmd_none_or_clear_bad+0x24/0x2b
Dec 28 11:53:57 mercury [ 4707.224438]  [<c025f2e5>] ? vma_prio_tree_remove+0x3e/0xd1
Dec 28 11:53:57 mercury [ 4707.224441]  [<c026512e>] ? __remove_shared_vm_struct+0x49/0x4c
Dec 28 11:53:57 mercury [ 4707.224444]  [<c0265159>] ? unlink_file_vma+0x28/0x30
Dec 28 11:53:57 mercury [ 4707.224446]  [<c0263898>] ? free_pgtables+0x2a/0x79
Dec 28 11:53:57 mercury [ 4707.224449]  [<c0264e71>] ? unmap_region+0x81/0x98
Dec 28 11:53:57 mercury [ 4707.224451]  [<c026570c>] ? do_munmap+0x17c/0x1c6
Dec 28 11:53:57 mercury [ 4707.224454]  [<f82fca8b>] ? rtR0MemObjNativeFree+0x121/0x165 [vboxdrv]
Dec 28 11:53:57 mercury [ 4707.224461]  [<f82fb673>] ? RTR0MemObjFree+0x12e/0x26f [vboxdrv]
Dec 28 11:53:57 mercury [ 4707.224467]  [<c0235d82>] ? up+0x2b/0x2f
Dec 28 11:53:57 mercury [ 4707.224470]  [<c0270be8>] ? __slab_free+0x45/0x203
Dec 28 11:53:57 mercury [ 4707.224474]  [<c027fe85>] ? __d_free+0x3a/0x3d
Dec 28 11:53:57 mercury [ 4707.224477]  [<c0271515>] ? kmem_cache_free+0x53/0x5f
Dec 28 11:53:57 mercury [ 4707.224479]  [<c027fe85>] ? __d_free+0x3a/0x3d
Dec 28 11:53:57 mercury [ 4707.224482]  [<f82f8fd9>] ? supdrvCleanupSession+0xa9/0x238 [vboxdrv]
Dec 28 11:53:57 mercury [ 4707.224488]  [<f82f9178>] ? supdrvCloseSession+0x10/0x33 [vboxdrv]
Dec 28 11:53:57 mercury [ 4707.224494]  [<f82f703a>] ? RTAssertDoBreakpoint+0x1d/0x2b [vboxdrv]
Dec 28 11:53:57 mercury [ 4707.224499]  [<c0275198>] ? __fput+0x69/0xfa
Dec 28 11:53:57 mercury [ 4707.224501]  [<c0275537>] ? fput+0x17/0x1c
Dec 28 11:53:57 mercury [ 4707.224504]  [<c0272ddc>] ? filp_close+0x47/0x51
Dec 28 11:53:57 mercury [ 4707.224506]  [<c02245e4>] ? put_files_struct+0x68/0xaa
Dec 28 11:53:57 mercury [ 4707.224509]  [<c0224653>] ? exit_files+0x2d/0x31
Dec 28 11:53:57 mercury [ 4707.224511]  [<c02255e3>] ? do_exit+0x1bd/0x6ef
Dec 28 11:53:57 mercury [ 4707.224514]  [<c0225b94>] ? sys_exit_group+0x0/0x11
Dec 28 11:53:57 mercury [ 4707.224516]  [<c022cd6f>] ? get_signal_to_deliver+0x2fa/0x313
Dec 28 11:53:57 mercury [ 4707.224520]  [<f8c59002>] ? _nv003418rm+0x162/0x517 [nvidia]
Dec 28 11:53:57 mercury [ 4707.224679]  [<c0559f9e>] ? do_page_fault+0x0/0x54e
Dec 28 11:53:57 mercury [ 4707.224683]  [<c02030dc>] ? do_notify_resume+0x71/0x60a
Dec 28 11:53:57 mercury [ 4707.224686]  [<c02148f4>] ? force_sig_info_fault+0x21/0x25
Dec 28 11:53:57 mercury [ 4707.224689]  [<c0259c4b>] ? free_hot_page+0xa/0xc
Dec 28 11:53:57 mercury [ 4707.224692]  [<c0259d1c>] ? __free_pages+0x1b/0x26
Dec 28 11:53:57 mercury [ 4707.224695]  [<c0259d44>] ? free_pages+0x1d/0x1f
Dec 28 11:53:57 mercury [ 4707.224698]  [<c026350a>] ? print_vma_addr+0xae/0xcd
Dec 28 11:53:57 mercury [ 4707.224700]  [<c02239ac>] ? printk+0x15/0x17
Dec 28 11:53:57 mercury [ 4707.224702]  [<c055a4e3>] ? do_page_fault+0x545/0x54e
Dec 28 11:53:57 mercury [ 4707.224706]  [<f8c59002>] ? _nv003418rm+0x162/0x517 [nvidia]
Dec 28 11:53:57 mercury [ 4707.224855]  [<c0559f9e>] ? do_page_fault+0x0/0x54e
Dec 28 11:53:57 mercury [ 4707.224857]  [<c0203a8e>] ? work_notifysig+0x13/0x19
Dec 28 11:53:57 mercury [ 4707.224861]  [<f8c59002>] ? _nv003418rm+0x162/0x517 [nvidia]
Dec 28 11:53:57 mercury [ 4707.225001] Code: e8 c9 fd ff ff 8b 45 e8 3b 45 ec 59 72 04 8b 1b eb 03 8b 5b 04 8b 13 39 da 75 c5 39 5b 04 75 f2 8b 43 08 39 d8 75 16 39 1e 74 04 <0f> 0b eb fe c7 06 00 00 00 00 66 c7 46 04 01 00 eb 21 39 58 04
Dec 28 11:53:57 mercury [ 4707.225001] EIP: [<c0393f35>] prio_tree_remove+0x5d/0x98 SS:ESP 0068:ec56dc80
Dec 28 11:53:57 mercury [ 4707.225052] ---[ end trace 84e6b3fdeacf5967 ]---
Dec 28 11:53:57 mercury [ 4707.225054] Fixing recursive fault but reboot is needed!
After this, the only way to get back to work is to reset my machine. Is there any way to solve this problem?
It looks like this problem began occuring once I started using 2.6.28 so I'm also posting mines .config:
http://pastebin.com/f1aa715c9

Any ideas why this problem occurs? :)

Posted: 28. Dec 2008, 16:18
by TerryE
No but the most stable 2.0 release is 2.0.6. I'd move up to that first before trying to resolve 2.0 specific issues.

Posted: 28. Dec 2008, 17:21
by ernetas
Is Virtualbox 2.1 compatible with virtual hard drive 2.0.4 format? If yes, maybe I should migrate right to 2.1?

Posted: 29. Dec 2008, 17:22
by TerryE
Yes it is. VB 2.1.0 has some nice new features, nice new bugs and to be fair has removed a few 2.0.6 bugs. However, I am staying with 2.0.6 for my production work until 2.1.2 is released.

Posted: 29. Dec 2008, 21:08
by ernetas
TerryE wrote:However, I am staying with 2.0.6 for my production work until 2.1.2 is released.
Umm... Why? What's going to change in 2.1.2?

Posted: 29. Dec 2008, 22:28
by TerryE
ernetas wrote:Why? What's going to change in 2.1.2?
For a start, if you look at the open tickets report you will see that many of the critical problems with 2.1.0 are marked "moved into SVN" which means that the fixes have been coded and unit tested and will be rolled up into the 2.1.2 release.

Posted: 31. Dec 2008, 00:20
by Sasquatch
Please note that your kernel, 2.6.28, was released as final last week or so, before the new 2.1.0 was released. So a positive report that it's supported is not yet there. It's more likely that it will be in the new 2.1.2 release.
All times are UTC+02:00
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited