Custom Query (16363 matches)
Results (1627 - 1629 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2871 | fixed | NetBSD panics in spllower when run under VirtualBox2.1 | ||
| Description |
When attempting to install the latest NetBSD (5.99.something), all kernel options (ACPI/APIC) ended up resulting in NetBSD doing a panic in spllower when it tried to do: lock addl %eax,0(%eax) because %eax is 0. I don't know if this is a NetBSD problem or VirtualBox problem. |
|||
| #2872 | fixed | Installing NetBSD 4.99 crashes VirtualBox 2.1 (recompiler cpu: triple fault) | ||
| Description |
Attempting to boot a non-APIC kernel resulted in this... Crashed stack frames:
With the aide of Visual Studio, I can get the disasembly of where it panic'd: 6F845501 mov eax,6F8B3160h 6F845506 mov edx,6F8B37A3h 6F84550B mov dword ptr [esp+8],eax 6F84550F mov eax,10E5h 6F845514 mov dword ptr [esp+0Ch],edx 6F845518 mov dword ptr [esp+4],eax 6F84551C mov dword ptr [esp],0 6F845523 call 6F8ABB68 6F845528 mov dword ptr [esp+8],esi 6F84552C mov dword ptr [esp+4],edi 6F845530 mov dword ptr [esp],6F8B3780h 6F845537 call 6F8ABB60 6F84553C call 6F8ABB58 6F845541 int 3 <<<<<<<<<<********************* 6F845542 nop 6F845543 mov eax,dword ptr ds:[6F8BC570h] 6F845548 mov ebx,dword ptr [eax+6F30h] 6F84554E cmp byte ptr [ebx+13C2Ch],0 6F845555 jne 6F845568 6F845557 mov dword ptr [esp],ebx 6F84555A mov eax,0FFFFF703h 6F84555F mov dword ptr [esp+4],eax 6F845563 call 6F8AB8C8 6F845568 mov dword ptr [esp],ebx 6F84556B call 6F842DC0 6F845570 jmp 6F845557 |
|||
| #2873 | fixed | Kernel reports BUG: using smp_processor_id when VM shuts down. -> fixed in SVN | ||
| Description |
Upon shutdown of a guest VM I see this block in /var/log/messages: Dec 22 22:58:44 ex8185 BUG: using smp_processor_id() in preemptible [00000001] code: VirtualBox/8571 Dec 22 22:58:44 ex8185 caller is RTMpCpuId+0x8/0x3f [vboxdrv] Dec 22 22:58:44 ex8185 Pid: 8571, comm: VirtualBox Tainted: P 2.6.24-tuxonice-r9 #1 Dec 22 22:58:44 ex8185 [<c0104fd5>] show_trace_log_lvl+0x1a/0x2f Dec 22 22:58:44 ex8185 [<c0105948>] show_trace+0x12/0x14 Dec 22 22:58:44 ex8185 [<c01060fe>] dump_stack+0x6c/0x72 Dec 22 22:58:44 ex8185 [<c01f0500>] debug_smp_processor_id+0xa0/0xb4 Dec 22 22:58:44 ex8185 [<f9607d05>] RTMpCpuId+0x8/0x3f [vboxdrv] Dec 22 22:58:44 ex8185 [<f93ab4b1>] 0xf93ab4b1 Dec 22 22:58:44 ex8185 [<f93b4a29>] 0xf93b4a29 Dec 22 22:58:44 ex8185 [<f93b548f>] 0xf93b548f Dec 22 22:58:44 ex8185 [<f93b575c>] 0xf93b575c Dec 22 22:58:44 ex8185 [<f9604af5>] supdrvIOCtl+0xdfe/0x1565 [vboxdrv] Dec 22 22:58:44 ex8185 [<f9601161>] supdrvOSGetForcedAsyncTscMode+0x149/0x1fa [vboxdrv] Dec 22 22:58:44 ex8185 [<c0180aee>] do_ioctl+0x22/0x67 Dec 22 22:58:44 ex8185 [<c0180d5b>] vfs_ioctl+0x228/0x23b Dec 22 22:58:44 ex8185 [<c0180db0>] sys_ioctl+0x42/0x5a Dec 22 22:58:44 ex8185 [<c0103fd6>] sysenter_past_esp+0x5f/0x85 Dec 22 22:58:44 ex8185 ======================= It doesn't appear to affect operation of the host or subsequent operation of the virtualization system. |
|||

