Custom Query (16363 matches)
Results (1663 - 1665 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2936 | fixed | Virtualbox-ose doesn't compile with kernel-headers-2.6.28 => Fixed in SVN | ||
| Description |
In file included from /usr/include/linux/byteorder/little_endian.h:14,
/usr/include/linux/byteorder/swabb.h: In function '__u32 __fswahw32(__u32)':
kmk [2]: * [/var/tmp/portage/app-emulation/virtualbox-ose-2.1.0/work/VirtualBox-2.1.0/out/linux.amd64/release/obj/Drivers/Storage/DrvHostDVD.o] Error 1 New in kernel-headers-2.6.28 is that beside swab.h also <linux/byteorder/swabb.h> gets included by include/linux/byteorder/little_endian.h. This include makes the trouble with C++ as posted. Virtualbox comes with its own swab.h header and that gets included by src/VBox/Devices/Storage/DrvHostDVD after defining _LINUX_BYTEORDER_SWAB_H. By defining also _LINUX_BYTEORDER_SWABB_H in src/VBox/Devices/Storage/DrvHostDVD, the inclusion of linux/byteorder/swabb.h is omitted and the build succeeds. |
|||
| #2937 | fixed | Windows Vista Host Blue screen crash from net filter -> fixed in SVN/2.1.2 | ||
| Description |
VBOX Net Filter seemed to have caused a Windows Blue Screen. I have attached the dump analysis below. Microsoft (R) Windows Debugger Version 6.8.0004.0 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini010109-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: c:\windows\symbols Executable search path is: Unable to load image ntoskrnl.exe, Win32 error 0n2 * WARNING: Unable to verify timestamp for ntoskrnl.exe Windows Kernel Version 6002 (Service Pack 2.113) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x82612000 PsLoadedModuleList = 0x82729c70 Debug session time: Thu Jan 1 18:38:00.588 2009 (GMT-5) System Uptime: 1 days 11:32:07.904 Unable to load image ntoskrnl.exe, Win32 error 0n2 * WARNING: Unable to verify timestamp for ntoskrnl.exe Loading Kernel Symbols ................................................................................................................................................................................................................................................. Loading User Symbols Loading unloaded module list ............ *
* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {c0000005, 9e671d08, f5b4fb80, f5b4f87c} * WARNING: Unable to verify timestamp for VBoxNetFlt.sys * ERROR: Module load completed but symbols could not be loaded for VBoxNetFlt.sys Probably caused by : VBoxNetFlt.sys ( VBoxNetFlt+2fcf ) Followup: MachineOwner 0: kd> !analyze -v *
* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 9e671d08, The address that the exception occurred at Arg3: f5b4fb80, Exception Record Address Arg4: f5b4f87c, Context Record Address Debugging Details: EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: +ffffffff9e671d08 9e671d08 f3a7 repe cmps dword ptr [esi],dword ptr es:[edi] EXCEPTION_RECORD: f5b4fb80 -- (.exr 0xfffffffff5b4fb80) ExceptionAddress: 9e671d08
NumberParameters: 2 Attempt to read from address 00000024 CONTEXT: f5b4f87c -- (.cxr 0xfffffffff5b4f87c) eax=00000000 ebx=8ccf06d0 ecx=00000001 edx=00000006 esi=00000024 edi=8ac18108 eip=9e671d08 esp=f5b4fc48 ebp=f5b4fc6c iopl=0 nv up ei pl nz na po cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010203 9e671d08 f3a7 repe cmps dword ptr [esi],dword ptr es:[edi] ds:0023:00000024=???????? es:0023:8ac18108=51e81300 Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: @FrÚ ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. READ_ADDRESS: 00000024 FAILED_INSTRUCTION_ADDRESS: +ffffffff9e671d08 9e671d08 f3a7 repe cmps dword ptr [esi],dword ptr es:[edi] BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from 9e66e52b to 9e671d08 STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. f5b4fc6c 9e66e52b 8ccf06d0 f5b4fcd8 9946a978 0x9e671d08 f5b4fc84 9e66e682 00000000 00000001 9946a978 0x9e66e52b f5b4fcc0 9e66e962 00000000 f5b4fcd8 8ccf06d0 0x9e66e682 f5b4fce8 9e66f20c 8ccf06d0 00000001 9946a978 0x9e66e962 f5b4fd0c 8f2c6fcf 85703c88 9946a978 00000001 0x9e66f20c f5b4fd48 8f2c7101 925e6bcc 925e6b70 00000000 VBoxNetFlt+0x2fcf f5b4fd7c 827e2e13 925e6bcc 908b6716 00000000 VBoxNetFlt+0x3101 f5b4fdc0 826cadc6 8f2c7070 925e6bcc 00000000 ntCmGetSystemControlValues+0x8b f5b4fdcc 00000000 00000000 00000000 00000000 ntObQueryObjectAuditingByHandle+0x9b FOLLOWUP_IP: VBoxNetFlt+2fcf 8f2c6fcf ?? ??? SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: VBoxNetFlt+2fcf FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxNetFlt IMAGE_NAME: VBoxNetFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4948ccb9 STACK_COMMAND: .cxr 0xfffffffff5b4f87c ; kb FAILURE_BUCKET_ID: 0x7E_BAD_IP_VBoxNetFlt+2fcf BUCKET_ID: 0x7E_BAD_IP_VBoxNetFlt+2fcf Followup: MachineOwner |
|||
| #2938 | fixed | /etc/init.d/vboxdrv setup fails on Gentoo Linux with "/sbin/functions.sh: No such file or directory" => Fixed in SVN | ||
| Description |
On Gentoo Linux the file "functions.sh" moved from /sbin/functions.sh to /etc/init.d/functions.sh a couple of month (years?) ago ... Please modify in file /etc/init.d/vboxdrv:
to
In Virtualbox 2.1.0 it is line 98 of /etc/init.d/vboxdrv. The problem exists in VirtualBox since version 1.4.x or 1.5.x or so. |
|||

