linux kernel oops with vbox 3.1.0 (3.0.12 regression?)

[jhw]

vbox 3.1.0 for windows guest on linux host dies due to kernel oops while starting windows. vm worked ok with vbox 3.0.10. BUG: unable to handle kernel NULL pointer dereference at 00000410

[Technologov]

Please re-upload oops and vbox.log over here.

-Technologov

[jhw]

oops

[jhw]

vbox log

[Jaap Dijkshoorn]

I had the same issue with a linux guest on a linux host. As soon as i put a lot of load on the network for example rsync of a filesystem, the kernel of the guest does an oops and dies.

[Jaap Dijkshoorn]

some logs:

Dec  2 10:28:40 mapserver kernel: Oops: 0000 [#1] SMP 
Dec  2 10:28:40 mapserver kernel: last sysfs file: /sys/class/net/lo/operstate
Dec  2 10:28:40 mapserver kernel: CPU 2 
Dec  2 10:28:40 mapserver kernel: Modules linked in: autofs4 fuse dm_snapshot dm_mirror dm_region_hash dm_log dm_mod mptctl rdma_ucm rdma_cm iw_cm ib_addr ib_ipoib ib_ucm ib_cm ib_sa ib_uverbs ib_umad mlx4_ib mlx4_core ib_mad ib_core ohci_hcd ehci_hcd e1000 sg sr_mod cdrom [last unloaded: ipmi_msghandler]
Dec  2 10:28:40 mapserver kernel: Pid: 4414, comm: sshd Not tainted 2.6.31.5-sara #1 VirtualBox
Dec  2 10:28:40 mapserver kernel: RIP: 0010:[<ffffffff8102fc8c>]  [<ffffffff8102fc8c>] __wake_up_common+0x2c/0x90
Dec  2 10:28:40 mapserver kernel: RSP: 0018:ffff880115545c98  EFLAGS: 00010006
Dec  2 10:28:40 mapserver kernel: RAX: ffff880115557be0 RBX: 0000000000000286 RCX: 0000000000000001
Dec  2 10:28:40 mapserver kernel: RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffff88011e436000
Dec  2 10:28:40 mapserver kernel: RBP: ffff880115545cc8 R08: ffff880115557bc8 R09: ffff88011dda0cc0
Dec  2 10:28:40 mapserver kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff88011e436000
Dec  2 10:28:40 mapserver kernel: R13: 0000000000000001 R14: ffff88011e436008 R15: 0000000000000000
Dec  2 10:28:40 mapserver kernel: FS:  00007f71f57a9790(0000) GS:ffff880028055000(0000) knlGS:0000000000000000
Dec  2 10:28:40 mapserver kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec  2 10:28:40 mapserver kernel: CR2: ffff880115557be0 CR3: 00000001154dc000 CR4: 00000000000006e0
Dec  2 10:28:40 mapserver kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Dec  2 10:28:40 mapserver kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Dec  2 10:28:40 mapserver kernel: Process sshd (pid: 4414, threadinfo ffff880115544000, task ffff88011f060cd0)
Dec  2 10:28:40 mapserver kernel: Stack:
Dec  2 10:28:40 mapserver kernel: 0000000100000001 0000000000000286 ffff88011e436000 0000000000000001
Dec  2 10:28:40 mapserver kernel: <0> 0000000000000000 0000000000000001 ffff880115545d08 ffffffff8103287e
Dec  2 10:28:40 mapserver kernel: <0> ffff880115545d08 0000000000000001 0000000000000001 ffff88011e436000
Dec  2 10:28:40 mapserver kernel: Call Trace:
Dec  2 10:28:40 mapserver kernel: [<ffffffff8103287e>] __wake_up_sync_key+0x4e/0x70
Dec  2 10:28:40 mapserver kernel: [<ffffffff810328ab>] __wake_up_sync+0xb/0x10
Dec  2 10:28:40 mapserver kernel: [<ffffffff810d5bbb>] pipe_write+0x4bb/0x620
Dec  2 10:28:40 mapserver kernel: [<ffffffff810de678>] ? core_sys_select+0x208/0x2e0
Dec  2 10:28:40 mapserver kernel: [<ffffffff810cd961>] do_sync_write+0xf1/0x140
Dec  2 10:28:40 mapserver kernel: [<ffffffff810595c0>] ? autoremove_wake_function+0x0/0x40
Dec  2 10:28:40 mapserver kernel: [<ffffffff813ccf77>] ? thread_return+0x3e/0x667
Dec  2 10:28:40 mapserver kernel: [<ffffffff810ce46b>] vfs_write+0xcb/0x180
Dec  2 10:28:40 mapserver kernel: [<ffffffff810ce610>] sys_write+0x50/0x90
Dec  2 10:28:40 mapserver kernel: [<ffffffff8100bdab>] system_call_fastpath+0x16/0x1b
Dec  2 10:28:40 mapserver kernel: Code: 48 89 e5 41 57 4d 89 c7 41 56 4c 8d 77 08 41 55 41 89 d5 41 54 53 48 83 ec 08 89 75 d4 89 4d d0 48 8b 47 08 4c 8d 40 e8 49 39 c6 <49> 8b 50 18 74 45 48 8d 5a e8 eb 0f 0f 1f 84 00 00 00 00 00 49 
Dec  2 10:28:40 mapserver kernel: RIP  [<ffffffff8102fc8c>] __wake_up_common+0x2c/0x90
Dec  2 10:28:40 mapserver kernel: RSP <ffff880115545c98>
Dec  2 10:28:40 mapserver kernel: CR2: ffff880115557be0
Dec  2 10:28:40 mapserver kernel: ---[ end trace fe420dcc4f7f233e ]---

[kev]

I'm also seeing the same. Host OS is openSuSE 11.2 (64-bit), Guest OS is Windows XP. This VM worked on VirtualBox 3.0.10, but didn't work with 3.0.12

uname -a: Linux kj-desktop 2.6.31.5-0.1-desktop #1 SMP PREEMPT 2009-10-26 15:49:03 +0100 x86_64 x86_64 x86_64 GNU/Linux rpm -qa|grep VirtualBox: VirtualBox-3.1-3.1.0_55467_openSUSE111-1.x86_64

[jhw]

same problem in vbox 3.1.2

[Frank Mehnert]

Any change with VBox 3.1.6? Actually these kernel oopses are not really related. If you can reproduce such a host kernel oops with VBox 3.1.6 then please attach the whole host kernel log.

[jhw]

problem still occurs with 3.1.4 & 3.1.6; it also occurred with 3.0.12; the latest version in which it did not occur was 3.0.10

[jhw]

requested complete kernel log up to vbox failure

[jhw]

latest VBox.log with 3.1.6

[Technologov]

You running Mandriva Linux 2010 32-bit host ?

I have Mandriva Linux 2010 64-bit host + VBox 3.2.0, and all is great.

-Technologov

[jhw]

problem still occurs with vbox 3.2.2 on kernel 2.6.33.5-rt22 ( 32 bit machine )

[jhw]

VBox.log with 3.2.2

[jhw]

oops with 3.2.2

[jhw]

dmesg with 3.2.2

[Frank Mehnert]

Please could you attach your host kernel config? Does the host kernel crash as well if you start the guest with NAT?

[jhw]

kernel config for 2.6.33.5-rt22

[jhw]

i have never used NAT: i use only static ip addresses in my LAN: it makes managing firewalls and communication among the various hosts easier if they have definite addresses

[jhw]

problem still occurs with VBox 3.2.10 & kernel 2.6.36 ( from Mandriva ); since bitrot has affected 3.0.10, it fails to compile with 2.6.36, so i no longer have a usable version of VBox

[Frank Mehnert]

Is this a self-compiled kernel or do you use a self-compiled kernel?

[jhw]

the latest kernel is from mandriva: kernel-tmb-desktop-2.6.36-2mdv-1-1mdv2011.0.i586.rpm, kernel-tmb-desktop-devel-2.6.36-2mdv-1-1mdv2011.0.i586.rpm; i compile the vbox modules ( dkms ): gcc-4.5.1-1mnb2.i586.rpm, etc

[Frank Mehnert]

Still relevant with VBox 4.0.12?

[jhw]

problem still occurs with vbox 4.1.0 on kernel 2.6.38.8-tmb-desktop-1.mga2 #1 SMP PREEMPT Mon Jun 20 11:06:38 UTC 2011 i686 i686 i386 GNU/Linux ( from Mageia ); testing is a nuisance because after the oops, the vboxdrv module is left holding onto something, and cant be removed without causing a panic; leaving it causes a panic on shutdown

[Frank Mehnert]

Please reopen if still relevant with VBox 4.1.22.