Hi, all I am using VirtualBox 3.2.0 on Fedora 12 x86_64. When I enable page fusion for Windows guest, it will cause kernel oops.
My host: AMD Athlon 64 X2 4200+, 4GB RAM, Fedora 12 x86_64. Guest: two virtual processors, 1GB RAM, enable VT, Windows XP Professional 32bit. I have tested two kernel 2.6.32.12-115.fc12.x86_64 and the problem can be reproduced on 2.6.32.14-127.fc12.x86_64 kernel. ABRT generates bug report automatically. I sent it as an attachment. When kernel oops appears, gnome-terminal shows some information. Just hope my report will help vbox team fix this bug. Liang Suilong -- Fedora && Debian User, former Ubuntu User My Page: http://www.liangsuilong.info Fedora Project Contributor -- Packager && Ambassador https://fedoraproject.org/wiki/User:Liangsuilong
Pid: 6100, comm: VirtualBox Tainted: P 2.6.32.14-127.fc12.x86_64 #1 Unknow RIP: 0010:[<ffffffffa0e2a9a0>] [<ffffffffa0e2a9a0>] g_abExecMemory+0x1e560/0x180000 [vboxdrv] RSP: 0018:ffff88007fec5a28 EFLAGS: 00010292 RAX: 0000000000000000 RBX: ffffc90009c8b0a8 RCX: 00000000ffffffff RDX: 0000000000000002 RSI: ffffc90009c95000 RDI: 0000000000000000 RBP: ffff88007fec5a38 R08: 0000000000000002 R09: ffff880076984010 R10: ffffc90009c8a000 R11: 0000000000000246 R12: 00000000fffffe98 R13: ffff88005d947710 R14: 0000000000000007 R15: 0000000000000006 FS: 00007f5c52608710(0000) GS:ffff880005900000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000028 CR3: 0000000118854000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process VirtualBox (pid: 6100, threadinfo ffff88007fec4000, task ffff8800b60d0000) Stack: ffffc90009c8a000 0000000000000006 ffff88007fec5a58 ffffffffa0e2bd9d 00007f5c50b1d720 ffffffffa0e0d3f0 ffff88007fec5b08 ffffffffa0e1ea1c 00007f5c27c6cbf0 ffffc90009ca5000 0000000000006db9 000000005f60e001 Call Trace: [<ffffffffa0e2bd9d>] g_abExecMemory+0x1f95d/0x180000 [vboxdrv] [<ffffffffa0e0d3f0>] ? g_abExecMemory+0xfb0/0x180000 [vboxdrv] [<ffffffffa0e1ea1c>] g_abExecMemory+0x125dc/0x180000 [vboxdrv] [<ffffffffa0e42d39>] ? g_abExecMemory+0x368f9/0x180000 [vboxdrv] [<ffffffffa0e0d3f0>] ? g_abExecMemory+0xfb0/0x180000 [vboxdrv] [<ffffffffa0e0d412>] g_abExecMemory+0xfd2/0x180000 [vboxdrv] [<ffffffffa0e62e4a>] g_abExecMemory+0x56a0a/0x180000 [vboxdrv] [<ffffffff810785f0>] ? up+0x39/0x3e [<ffffffffa0e0246d>] ? RTSemFastMutexRelease+0x49/0x54 [vboxdrv] [<ffffffffa0e105c2>] ? g_abExecMemory+0x4182/0x180000 [vboxdrv] [<ffffffff81078717>] ? down+0x38/0x3d [<ffffffffa0e12262>] ? g_abExecMemory+0x5e22/0x180000 [vboxdrv] [<ffffffffa0e0cc19>] g_abExecMemory+0x7d9/0x180000 [vboxdrv] [<ffffffffa0e20471>] g_abExecMemory+0x14031/0x180000 [vboxdrv] [<ffffffffa0e20be0>] g_abExecMemory+0x147a0/0x180000 [vboxdrv] [<ffffffff8110e3c5>] ? __kmalloc+0x14c/0x15e [<ffffffffa0dfc121>] supdrvIOCtl+0x123b/0x20e7 [vboxdrv] [<ffffffffa0e006e5>] ? rtR0MemAlloc+0x97/0xc2 [vboxdrv] [<ffffffffa0e0051d>] ? rtR0MemFree+0x21/0x71 [vboxdrv] [<ffffffffa0df8341>] VBoxDrvLinuxIOCtl+0x124/0x1a3 [vboxdrv] [<ffffffff81010580>] ? __unlazy_fpu+0x78/0x85 [<ffffffff8112a5d8>] vfs_ioctl+0x22/0x87 [<ffffffff8104eb3e>] ? finish_task_switch+0x48/0xad [<ffffffff8112ab34>] do_vfs_ioctl+0x47b/0x4c1 [<ffffffff8145557d>] ? thread_return+0x78/0xdb [<ffffffff8112abd0>] sys_ioctl+0x56/0x79 [<ffffffff81011d32>] system_call_fastpath+0x16/0x1b Code: 54 41 89 f4 53 8b 07 48 89 fb 3d 26 03 79 19 0f 85 c4 00 00 00 8b 07 3d 26 03 79 19 0f 85 bf 00 00 00 48 8b 7f 48 e8 40 8e 02 00 <4c> 8b 48 28 41 b8 ff ff ff ff 31 d2 44 89 c0 f0 0f b1 53 04 0f RIP [<ffffffffa0e2a9a0>] g_abExecMemory+0x1e560/0x180000 [vboxdrv] RSP <ffff88007fec5a28>
[fed...@fedora-desktop ~]$ Message from sysl...@localhost at May 31 23:52:09 ... kernel:Oops: 0000 [#1] SMP Message from sysl...@localhost at May 31 23:52:09 ... kernel:last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq Message from sysl...@localhost at May 31 23:52:09 ... kernel:Stack: Message from sysl...@localhost at May 31 23:52:09 ... kernel:Call Trace: Message from sysl...@localhost at May 31 23:52:09 ... kernel:Code: 54 41 89 f4 53 8b 07 48 89 fb 3d 26 03 79 19 0f 85 c4 00 00 00 8b 07 3d 26 03 79 19 0f 85 bf 00 00 00 48 8b 7f 48 e8 40 8e 02 00 <4c> 8b 48 28 41 b8 ff ff ff ff 31 d2 44 89 c0 f0 0f b1 53 04 0f Message from sysl...@localhost at May 31 23:52:09 ... kernel:CR2: 0000000000000028
_______________________________________________ vbox-dev mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-dev
