Menu
▾
▴
colinux-devel — Cooperative Linux development mailing list
You can subscribe to this list here.
| 2004 |
Jan
(64) |
Feb
(530) |
Mar
(266) |
Apr
(580) |
May
(360) |
Jun
(161) |
Jul
(185) |
Aug
(164) |
Sep
(123) |
Oct
(160) |
Nov
(59) |
Dec
(84) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(156) |
Feb
(95) |
Mar
(124) |
Apr
(81) |
May
(79) |
Jun
(179) |
Jul
(35) |
Aug
(64) |
Sep
(56) |
Oct
(57) |
Nov
(18) |
Dec
(41) |
| 2006 |
Jan
(65) |
Feb
(37) |
Mar
(59) |
Apr
(73) |
May
(65) |
Jun
(27) |
Jul
(54) |
Aug
(76) |
Sep
(103) |
Oct
(23) |
Nov
(45) |
Dec
(29) |
| 2007 |
Jan
(41) |
Feb
(47) |
Mar
(61) |
Apr
(24) |
May
(14) |
Jun
(6) |
Jul
(23) |
Aug
(30) |
Sep
(16) |
Oct
(9) |
Nov
(53) |
Dec
(36) |
| 2008 |
Jan
(19) |
Feb
(49) |
Mar
(74) |
Apr
(21) |
May
(24) |
Jun
(5) |
Jul
(9) |
Aug
(53) |
Sep
(26) |
Oct
(23) |
Nov
(32) |
Dec
(19) |
| 2009 |
Jan
(47) |
Feb
(49) |
Mar
(39) |
Apr
(61) |
May
(28) |
Jun
(19) |
Jul
(12) |
Aug
(10) |
Sep
(31) |
Oct
(16) |
Nov
(60) |
Dec
(26) |
| 2010 |
Jan
(17) |
Feb
(9) |
Mar
(32) |
Apr
(11) |
May
(24) |
Jun
(33) |
Jul
(5) |
Aug
(2) |
Sep
(7) |
Oct
(8) |
Nov
(17) |
Dec
(7) |
| 2011 |
Jan
(12) |
Feb
(16) |
Mar
(2) |
Apr
(12) |
May
(5) |
Jun
(10) |
Jul
(3) |
Aug
(3) |
Sep
(2) |
Oct
(1) |
Nov
(17) |
Dec
(1) |
| 2012 |
Jan
(9) |
Feb
(9) |
Mar
(8) |
Apr
(4) |
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(8) |
Sep
(11) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
| 2013 |
Jan
|
Feb
(7) |
Mar
(4) |
Apr
(10) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(3) |
| 2016 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: coLinux a. <col...@he...> - 2009-05-25 04:12:12
|
The autobuild system has detected a new revision in the source repository. Review last changed from changelog.txt, also attached in mail. Download the compiled version: http://www.henrynestler.com/colinux/autobuild/devel-20090525/ colinux-0.8.0-20090525.src.tgz (684701 Bytes) daemons-0.8.0-20090525.dbg.zip (589854 Bytes) daemons-0.8.0-20090525.zip (477286 Bytes) modules-2.6.22.18-co-0.8.0-20090525.tgz (2636284 Bytes) vmlinux-2.6.22.18-co-0.8.0-20090525.zip (1673559 Bytes) Note, the autobuild compilation does not include an installer. Remember to reload the driver with these commands: colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver Inside coLinux please update modules as follow: rm -rf /lib/modules/*-co-* tar -xzf modules-*-co-*-20090525.tgz -C / The autobuild compilations are not official releases of Cooperative Linux software. There is no warranty that any autobuild version is stable. If use this autobuild version, please give us feedback of your experience. Job runs on machine with 64 bit version of gcc 4.1.2. A service from http://gcc.gnu.org/wiki/CompileFarm -- Lots of fun with newest version, Henry Nestler ------------------------------------------------------------------------ r1256 | henryn | 2009-05-25 00:02:56 +0000 (Mon, 25 May 2009) | 1 line Changed paths: M /branches/devel/patch/kbd-2.6.22.diff * keyboard_inject_utf8: Add prototype to header. ------------------------------------------------------------------------ r1255 | henryn | 2009-05-24 23:22:45 +0000 (Sun, 24 May 2009) | 4 lines Changed paths: M /branches/devel/patch/base-2.6.22.diff M /branches/devel/patch/cobd-async-2.6.22.diff M /branches/devel/patch/kbd-2.6.22.diff M /branches/devel/patch/kbd-core.diff M /branches/devel/src/colinux/os/linux/user/console/head.cpp M /branches/devel/src/colinux/os/winnt/user/console/head.cpp M /branches/devel/src/colinux/os/winnt/user/console-nt/widget.cpp Contributed by Paolo Minazzi: * CO_KBD_SCANCODE_RAW, CO_KBD_SCANCODE_ASCII, PasteClipboardIntoColinux: Insert keys from fltk console without keyboard mapping. * co_scan_code_t.down: is obsolate, removed. ------------------------------------------------------------------------ r1254 | henryn | 2009-05-24 22:50:45 +0000 (Sun, 24 May 2009) | 1 line Changed paths: M /branches/devel/src/colinux/os/linux/user/console/head.cpp * main_key_scan_qwerty: Unused. Removed. (Linux as host) ------------------------------------------------------------------------ r1253 | henryn | 2009-05-24 22:47:57 +0000 (Sun, 24 May 2009) | 2 lines Changed paths: M /branches/devel/src/colinux/os/linux/user/console/head.cpp * global_event_hook: Handle extended keys, for example ALT+CurRight. (Linux as host, ported from Windows host code.) ------------------------------------------------------------------------ r1252 | henryn | 2009-05-24 22:42:14 +0000 (Sun, 24 May 2009) | 1 line Changed paths: M /branches/devel/src/colinux/os/linux/user/console/head.cpp * scan_code_state (Linux as host): Array needs up to index 0x1FF. ------------------------------------------------------------------------ r1251 | henryn | 2009-05-24 22:13:06 +0000 (Sun, 24 May 2009) | 1 line Changed paths: M /branches/devel/src/colinux/os/linux/kernel/module/alloc.c * co_os_userspace_unmap (Linux as host): Syntax error. ------------------------------------------------------------------------ |
|
From: coLinux a. <col...@he...> - 2009-05-21 04:12:04
|
The autobuild system has detected a new revision in the source repository. Review last changed from changelog.txt, also attached in mail. Download the compiled version: http://www.henrynestler.com/colinux/autobuild/devel-20090520/ colinux-0.8.0-20090520.src.tgz (685014 Bytes) daemons-0.8.0-20090520.dbg.zip (589979 Bytes) daemons-0.8.0-20090520.zip (477414 Bytes) modules-2.6.22.18-co-0.8.0-20090520.tgz (2636349 Bytes) vmlinux-2.6.22.18-co-0.8.0-20090520.zip (1673190 Bytes) Note, the autobuild compilation does not include an installer. Remember to reload the driver with these commands: colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver Inside coLinux please update modules as follow: rm -rf /lib/modules/*-co-* tar -xzf modules-*-co-*-20090520.tgz -C / The autobuild compilations are not official releases of Cooperative Linux software. There is no warranty that any autobuild version is stable. If use this autobuild version, please give us feedback of your experience. Job runs on machine with 64 bit version of gcc 4.1.2. A service from http://gcc.gnu.org/wiki/CompileFarm -- Lots of fun with newest version, Henry Nestler ------------------------------------------------------------------------ r1250 | henryn | 2009-05-20 22:50:06 +0000 (Wed, 20 May 2009) | 1 line Changed paths: M /branches/devel/NEWS M /branches/devel/bin/build-common.sh * w32api upgrade to Version 3.13 ------------------------------------------------------------------------ r1249 | henryn | 2009-05-20 22:47:46 +0000 (Wed, 20 May 2009) | 1 line Changed paths: M /branches/devel/NEWS M /branches/devel/src/colinux/arch/i386/passage.c * VMX: Comments. ------------------------------------------------------------------------ r1248 | henryn | 2009-05-20 20:40:43 +0000 (Wed, 20 May 2009) | 11 lines Changed paths: M /branches/devel/patch/base-2.6.22.diff M /branches/devel/patch/cobd-async-2.6.22.diff M /branches/devel/src/colinux/arch/i386/defs.h M /branches/devel/src/colinux/arch/i386/passage.c M /branches/devel/src/colinux/user/daemon.c * Bug #1959846, #2760666: VMX mode in Virtual PC or VirtualBOX mode causes BSOD STOP: 0x0000007F 0x00000008 (UNEXPECTED_KERNEL_MODE_TRAP Double Fault) If an other virtualizion is running in VMX mode, disable paging or clearing some bits of register CR4 would receiving a gereral protection fault. Currently coLinux can't cooperate with such hardware virtualisation. coLinux will abort the Linux guest, but don't crash the host for now. Thanks Sander Vanleeuwen from http://www.virtualbox.org/ticket/3724#comment:8 ------------------------------------------------------------------------ |
|
From: SourceForge.net <no...@so...> - 2009-05-20 21:26:39
|
Bugs item #2747242, was opened at 2009-04-09 12:18 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2747242&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Daemons (Windows) Group: v0.7.x (release) >Status: Closed >Resolution: Works For Me Priority: 5 Private: No Submitted By: MerseyViking (merseyviking) >Assigned to: Henry N. (henryn) Summary: cofs and cmake Initial Comment: I'm using andLinux to do some cross-platform development using cmake (version 2.4-patch 7) as the makefile generator. If I have a cofs mount pointing to my Windows drive, cmake falls over when trying to compile a simple test app. If the same directory is mounted as a SMB share, it works fine. The error I get from cmake is: $ cmake . -G"Unix Makefiles" -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- broken CMake Error: The C compiler "/usr/bin/gcc" is not able to compile a simple test program. It fails with the following output: make: *** Makefile: No such file or directory. Stop. CMake will not be able to correctly generate this project. -- Configuring done I appreciate this may be an issue with cmake, such as it creating funky filenames that cofs can't deal with, but it makes more sense for a filesystem to support a tool rather than the other way round. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-12 21:51 Message: Of curse, the same result without ccache: henry@coLinux:/media/windows$ cmake . -G"Unix Makefiles" -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Check size of void* -- Check size of void* - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Configuring done -- Generating done -- Build files have been written to: /media/windows Henry ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-12 21:45 Message: What version of coLinux do you use? ("uname -r") Please update to version 0.7.4 from http://www.colinux.org/snapshots/ Some of these errors are fixed in the new version, for example see * Bug #2176188: File sync wrong on cofs, command after mv/rename fails. But remember: cofs is a FAT filesystem and not all of the native filesystems works there. Symlinks are not supported. There exist also some problems with timestamps. So, some make utilities means that the file is in future. This is a result from small timediff between Host and Guest. Builds on cofs are limited to use, that generally can not change. I'm prefer to compile under your home directory and sync your work with rsync to the cofs drive on windows side. A quick test under Debian 4.0 with coLinux 0.7.4-rc1 is working perfectly: henry@coLinux:/media/windows$ uname -r 2.6.22.18-co-0.7.4 henry@coLinux:/media/windows$ cmake --version cmake version 2.4-patch 5 henry@coLinux:/media/windows$ mount | grep cofs0 cofs0 on /media/windows type cofs (rw,noexec,nosuid,nodev,uid=1000,gid=1000) henry@coLinux:/media/windows$ ls CMakeLists.txt main.c henry@coLinux:/media/windows$ cat CMakeLists.txt add_executable(halloworld main.c) henry@coLinux:/media/windows$ cat main.c #include <stdio.h> int main() { printf("Hallo World!\n"); return 0; } henry@coLinux:/media/windows$ cmake . -G"Unix Makefiles" -- Check for working C compiler: /home/hn/bin/ccache/gcc -- Check for working C compiler: /home/hn/bin/ccache/gcc -- works -- Check size of void* -- Check size of void* - done -- Check for working CXX compiler: /home/hn/bin/ccache/c++ -- Check for working CXX compiler: /home/hn/bin/ccache/c++ -- works -- Configuring done -- Generating done -- Build files have been written to: /media/windows henry@coLinux:/media/windows$ make Scanning dependencies of target halloworld [100%] Building C object CMakeFiles/halloworld.dir/main.o Linking C executable halloworld [100%] Built target halloworld ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2747242&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-05-20 20:58:20
|
Bugs item #2760666, was opened at 2009-04-14 04:50 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crash / BSOD Group: None Status: Closed Resolution: Accepted Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Henry N. (henryn) Summary: VirtualBOX causes BSOD STOP: 0x0000007F 0x00000008 Initial Comment: Running Parallels or VMWare to virtualise a virtual machine doesnt result in crashing. Trying to boot Windows XP on VirtualBOX at the same time as running COLinux causes it to BSOD the host system (Windows Vista) Its strange but why does VBox BSOD the system whereas Parallels/VMWare can virtualise fine alongside COLinux.. Reproduction: Install VirtualBox Install COLinux V8 Run COLinux Create a new Windows VM In Virtualbox Attempt to Boot the new VM Into Windows setup. BSOD ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-05-20 22:57 Message: This artifact has been marked as a duplicate of artifact 1959846 with reason: Both results from VMX mode. We will follow it in one Artifact only now. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-05-20 22:52 Message: Based on idea by Sander Vanleeuwen (http://www.virtualbox.org/ticket/3724#comment:8), have added a check for running VMX. If CPU is unning in VMX mode, coLinux still aborts the guest system, and no longer will crash the host. It's coded in current devel snapshot from SVN revision 1248. Sorry, that we currently don't have support for this mode. I'm locking into Intel manuals to find a solution to run in a cooperative way. Henry ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-29 23:50 Message: coLinux Bug #1959846 seems me the same problem. With a very good crash dump report. Virtual PC 2007 is running there at same time under Vista. https://sourceforge.net/tracker/?func=detail&aid=1959846&group_id=98788&atid=622063 ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-04-29 13:01 Message: I have a similar problem with Windows XP host. (32-bit) Minidumps are not getting generated. Even if PAE/NX/DEP technologies are turned off completely. Nobody: please use some nickname so we could identify you. Nobody: please specify VirtualBox version, and if you use VT-x or not (Hardware Virtualization) For me, the crash happens only with Hardware Virtualization enabled. -Technologov ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-04-29 12:47 Message: Here is the original bug report: Host crash: vboxdrv crashes, when run in VMX mode, together with coLinux http://www.virtualbox.org/ticket/3724 -Technologov ---------------------------------------------------------------------- Comment By: Juergen (juergen_01) Date: 2009-04-29 08:57 Message: Some time ago, a had the same problem with randomly getting a kernel stack overflow. The problem was caused by too many enabled network services on a network interface. I had installed VirtualBox, MS Virtual PC, Norton Internet Security, Cisco VPN Client and MS Network Monitor. All these programs installed a network service. After I disabled 2 or 3 of the network services I was not using at that time, I solved the problem with the kernel stack overflow. You have to disable the services it on every network interface. Well, a BSOD can also be caused by the virtualization features of the CPU. If I am running a VM in VBox with Intel-VT enabled and then starting only the Virtual PC application, my computer is crashing with a BSOD. On an older CPU with no Intel-VT I never had this problem. On this older CPU, I never had any problems with running VBox VMs and colinux instances concurrently. If you do not get a crash dump, this might be caused by the Data-Execution-Prevention in Windows. If this is also enabled for normal applications and not only for windows services, then you will never get a crash dump. Windows is still writing crash dump information to pagefile.sys but it does not generate a crash dump file on next startup. I had the same problem while getting the kernel stack overflow. After disabling DEP for every application Windows created crash dump files again. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-29 03:21 Message: Double fault A double fault occurs when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially, however there are several exceptions that cannot be handled serially and in this situation the processor signals a double fault. The two primary causes for this are hardware and kernel stack overflows. Hardware problems are usually related to CPU, RAM, or bus. Kernel stack overflows are almost always caused by faulty kernel-mode drivers. I can rule out my CPU/RAM since they are relatively new components.. VMWare/Parallels work alongside COLinux just not VirtualBox. I've stress tested this thing for over 72 hours about 2 weeks back since I installed a new CPU cooler.. So I'm guessing its the Kernel Stack Overflow? Any chance you can attempt to reproduce? My Vista is being a pain, its set to do a full mem dump on BSOD but that crash doesnt generate one. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-28 23:49 Message: > STOP: 0x0000007F (0x00000008, 0x801B1000, 0x00000000, 0x00000000) STOP 0x0000007F : UNEXPECTED_KERNEL_MODE_TRAP (sse [1]) 0x00000008 : Double Fault 0x801B1000 : I found no references for that value. [1] http://support.microsoft.com/kb/137539 ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-28 18:04 Message: The system doesnt generate a Minidump from this crash even though configured to. Error is as follows: STOP: 0x0000007F (0x00000008, 0x801B1000, 0x00000000, 0x00000000) With no further details ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-14 19:57 Message: It would be nice to get an analyze from minidump of that BSOD, so we can see, what caused this crash. Please read "Howto use Windows crash dump" in your colinux file "debugging.txt" or here from source: http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging Henry ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-05-20 20:57:12
|
Bugs item #2760666, was opened at 2009-04-14 04:50 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crash / BSOD Group: None Status: Open Resolution: Accepted Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Henry N. (henryn) Summary: VirtualBOX causes BSOD STOP: 0x0000007F 0x00000008 Initial Comment: Running Parallels or VMWare to virtualise a virtual machine doesnt result in crashing. Trying to boot Windows XP on VirtualBOX at the same time as running COLinux causes it to BSOD the host system (Windows Vista) Its strange but why does VBox BSOD the system whereas Parallels/VMWare can virtualise fine alongside COLinux.. Reproduction: Install VirtualBox Install COLinux V8 Run COLinux Create a new Windows VM In Virtualbox Attempt to Boot the new VM Into Windows setup. BSOD ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-05-20 22:57 Message: This artifact has been marked as a duplicate of artifact 1959846 with reason: Both results from VMX mode. We will follow it in one Artifact only now. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-05-20 22:52 Message: Based on idea by Sander Vanleeuwen (http://www.virtualbox.org/ticket/3724#comment:8), have added a check for running VMX. If CPU is unning in VMX mode, coLinux still aborts the guest system, and no longer will crash the host. It's coded in current devel snapshot from SVN revision 1248. Sorry, that we currently don't have support for this mode. I'm locking into Intel manuals to find a solution to run in a cooperative way. Henry ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-29 23:50 Message: coLinux Bug #1959846 seems me the same problem. With a very good crash dump report. Virtual PC 2007 is running there at same time under Vista. https://sourceforge.net/tracker/?func=detail&aid=1959846&group_id=98788&atid=622063 ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-04-29 13:01 Message: I have a similar problem with Windows XP host. (32-bit) Minidumps are not getting generated. Even if PAE/NX/DEP technologies are turned off completely. Nobody: please use some nickname so we could identify you. Nobody: please specify VirtualBox version, and if you use VT-x or not (Hardware Virtualization) For me, the crash happens only with Hardware Virtualization enabled. -Technologov ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-04-29 12:47 Message: Here is the original bug report: Host crash: vboxdrv crashes, when run in VMX mode, together with coLinux http://www.virtualbox.org/ticket/3724 -Technologov ---------------------------------------------------------------------- Comment By: Juergen (juergen_01) Date: 2009-04-29 08:57 Message: Some time ago, a had the same problem with randomly getting a kernel stack overflow. The problem was caused by too many enabled network services on a network interface. I had installed VirtualBox, MS Virtual PC, Norton Internet Security, Cisco VPN Client and MS Network Monitor. All these programs installed a network service. After I disabled 2 or 3 of the network services I was not using at that time, I solved the problem with the kernel stack overflow. You have to disable the services it on every network interface. Well, a BSOD can also be caused by the virtualization features of the CPU. If I am running a VM in VBox with Intel-VT enabled and then starting only the Virtual PC application, my computer is crashing with a BSOD. On an older CPU with no Intel-VT I never had this problem. On this older CPU, I never had any problems with running VBox VMs and colinux instances concurrently. If you do not get a crash dump, this might be caused by the Data-Execution-Prevention in Windows. If this is also enabled for normal applications and not only for windows services, then you will never get a crash dump. Windows is still writing crash dump information to pagefile.sys but it does not generate a crash dump file on next startup. I had the same problem while getting the kernel stack overflow. After disabling DEP for every application Windows created crash dump files again. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-29 03:21 Message: Double fault A double fault occurs when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially, however there are several exceptions that cannot be handled serially and in this situation the processor signals a double fault. The two primary causes for this are hardware and kernel stack overflows. Hardware problems are usually related to CPU, RAM, or bus. Kernel stack overflows are almost always caused by faulty kernel-mode drivers. I can rule out my CPU/RAM since they are relatively new components.. VMWare/Parallels work alongside COLinux just not VirtualBox. I've stress tested this thing for over 72 hours about 2 weeks back since I installed a new CPU cooler.. So I'm guessing its the Kernel Stack Overflow? Any chance you can attempt to reproduce? My Vista is being a pain, its set to do a full mem dump on BSOD but that crash doesnt generate one. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-28 23:49 Message: > STOP: 0x0000007F (0x00000008, 0x801B1000, 0x00000000, 0x00000000) STOP 0x0000007F : UNEXPECTED_KERNEL_MODE_TRAP (sse [1]) 0x00000008 : Double Fault 0x801B1000 : I found no references for that value. [1] http://support.microsoft.com/kb/137539 ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-28 18:04 Message: The system doesnt generate a Minidump from this crash even though configured to. Error is as follows: STOP: 0x0000007F (0x00000008, 0x801B1000, 0x00000000, 0x00000000) With no further details ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-14 19:57 Message: It would be nice to get an analyze from minidump of that BSOD, so we can see, what caused this crash. Please read "Howto use Windows crash dump" in your colinux file "debugging.txt" or here from source: http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging Henry ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-05-20 20:53:30
|
Bugs item #1959846, was opened at 2008-05-08 00:38 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1959846&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Crash / BSOD Group: v0.7.x (release) Status: Open >Resolution: Accepted Priority: 5 Private: No Submitted By: George V. Reilly (george_v_reilly) >Assigned to: Henry N. (henryn) Summary: Bugcheck in coLinux when starting VM from Virtual PC 2007 Initial Comment: I sent the message below to Dan Aloni but never got a reply. I would have filed a bug back then, but there's no obvious link to the SF bug tracker on the colinux.org website. ---------- Forwarded message ---------- From: George V. Reilly <ge...@re...> Date: 2008/4/10 Subject: Bugcheck in coLinux when starting VM from VPC2007 To: Dan Aloni <da...@co...> I installed andLinux beta 1 rc6 yesterday, on a 4GB quad-core box running x86 Vista SP1. As soon as I launch a virtual machine in Virtual PC 2007, I get a bugcheck in colinux-daemon. This is 100% repeatable. 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: 80154000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ PEB is paged out (Peb.Ldr = 7ffdb00c). Type ".hh dbgerr001" for details PEB is paged out (Peb.Ldr = 7ffdb00c). Type ".hh dbgerr001" for details BUGCHECK_STR: 0x7f_8 TSS: 00000028 -- (.tss 0x28) eax=0000000d ebx=73571250 ecx=883a8ac0 edx=73571280 esi=00000000 edi=73571132 eip=81d0576a esp=73570e6c ebp=73571220 iopl=0 nv up di pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010002 nt!KeBugCheck2+0x1f: 81d0576a 89442424 mov dword ptr [esp+24h],eax ss:0010:73570e90=???????? Resetting default scope DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: colinux-daemon. CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 00000000 to 81d0576a STACK_TEXT: 00000000 81d0576a 00000000 00000000 00000000 nt!KiTrap08+0x75 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTrap08+75 81c91b9e ebee jmp nt!KiTrap08+0x65 (81c91b8e) SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiTrap08+75 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 47918b12 FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap08+75 BUCKET_ID: 0x7f_8_nt!KiTrap08+75 Followup: MachineOwner --------- 0: kd> kv ChildEBP RetAddr Args to Child 00000000 81d0576a 00000000 00000000 00000000 nt!KiTrap08+0x75 (FPO: TSS 28:0) 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f 0: kd> .tss 0x28 eax=0000000d ebx=73571250 ecx=883a8ac0 edx=73571280 esi=00000000 edi=73571132 eip=81d0576a esp=73570e6c ebp=73571220 iopl=0 nv up di pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010002 nt!KeBugCheck2+0x1f: 81d0576a 89442424 mov dword ptr [esp+24h],eax ss:0010:73570e90=???????? 0: kd> kv *** Stack trace for last set context - .thread/.cxr resets it ChildEBP RetAddr Args to Child 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f 0: kd> .ecxr Unable to get exception context, HRESULT 0x8000FFFF 0: kd> !thread THREAD 883a8ac0 Cid 0978.09c0 Teb: 7ffde000 Win32Thread: 00000000 RUNNING on processor 0 IRP List: 87e239f8: (0006,0094) Flags: 00060070 Mdl: 00000000 87e69f68: (0006,0094) Flags: 00060900 Mdl: 88dff0a0 Not impersonating DeviceMap 8ae08808 Owning Process 883855b8 Image: colinux-daemon.exe Wait Start TickCount 53407 Ticks: 0 Context Switch Count 85610 UserTime 00:00:00.031 KernelTime 00:00:05.397 Win32 Start Address 0x766cd1b9 Stack Init 8b243000 Current 8b2429b8 Base 8b243000 Limit 8b240000 Call 0 Priority 9 BasePriority 8 PriorityDecrement 0 IoPriority 2 PagePriority 5 ChildEBP RetAddr Args to Child 00000000 81d0576a 00000000 00000000 00000000 nt!KiTrap08+0x75 (FPO: TSS 28:0) 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f 0: kd> !pcr KPCR for Processor 0 at 81d30800: Major 1 Minor 1 NtTib.ExceptionList: 81d2abe8 NtTib.StackBase: 00000000 NtTib.StackLimit: 00000000 NtTib.SubSystemTib: 80154000 NtTib.Version: 003cb6e5 NtTib.UserPointer: 00000001 NtTib.SelfTib: 7ffde000 SelfPcr: 81d30800 Prcb: 81d30920 Irql: 0000001f IRR: 00000000 IDR: ffffffff InterruptMode: 00000000 IDT: 81afd400 GDT: 81afd000 TSS: 81d2e000 CurrentThread: 883a8ac0 NextThread: 00000000 IdleThread: 81d34640 DpcQueue: I have a crashdump, compressed down to 57MB at http://www.georgevreilly.com/temp/colinux-daemon.dmp.bz2 ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-05-20 22:53 Message: Based on idea by Sander Vanleeuwen (http://www.virtualbox.org/ticket/3724#comment:8), have added a check for running VMX. If CPU is unning in VMX mode, coLinux still aborts the guest system, and no longer will crash the host. It's coded in current devel snapshot from SVN revision 1248. Sorry, that we currently don't have support for this mode. I'm locking into Intel manuals to find a solution to run in a cooperative way. Henry ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-05-17 02:22 Message: This report looks similar to this: http://www.virtualbox.org/ticket/3724 -Technologov ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-05-10 09:53 Message: I am having the same issue. Anyone looking into this? Any chance of this getting fixed? I can help with testing if needed. ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-04-30 01:26 Message: This report looks similar to this: [https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 this report] ---------------------------------------------------------------------- Comment By: John Stroy (jdstroy) Date: 2009-02-04 03:06 Message: This happens in 0.7.3 as well. 2.6.22.18-co-0.7.3 #1 PREEMPT Sat May 24 22:27:30 UTC 2008 i686 06/17 I got this to happen on Windows Server 2003 Enterprise Edition with MSVPC2007. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-05-10 01:26 Message: Logged In: YES user_id=579204 Originator: NO 0.7.1 has an known bug. Double, triple and endless faults I have seen. See http://www.andlinux.org/news.php for "Apr 18th, 2008". This was fixed in "Apr 21st, 2008: andLinux Beta 1 (final)" I not know ho you can update andLinux version without reinstalling all images. You can still update the coLinux executable files, linux.sys, vmlinux and modules from http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080416-Snapshot/packages/ No, your file have not loaded. Your output are well good and enough. I'm not familiar with this debugger. "!analyze -v" is all I know to do. If the bug would be in the linux.sys, then the !analyse would list such helpfull STACK, for example: http://www.henrynestler.com/colinux/testing/pfn-check-0.7.3/20080410-antinx/minidump041108-01.txt But the known bug is inside Linux kernel and pokes some wildly into the hosts memory, so we never have seen it from Windows debugger. The real interesting summary can read from this file: http://www.henrynestler.com/colinux/testing/pfn-check-0.7.3/20080410-antinx/bug16-recursive-page-fault-endless.txt ---------------------------------------------------------------------- Comment By: George V. Reilly (george_v_reilly) Date: 2008-05-10 00:45 Message: Logged In: YES user_id=737437 Originator: YES coLinux was installed by andLinux, not directly by me. C:\Program Files\andLinux>colinux-daemon --status-driver Cooperative Linux Daemon, 0.7.1 Compiled on Sat Jul 14 12:15:18 2007 checking if the driver is installed current state: 4 (fully initialized) current number of monitors: 1 current linux api version: 10 current periphery api version: 20 I'm running both andLinux and VPC 2007 on the same instance of Vista x86 SP1. They're peers. Vista is the host for both VPC and andLinux. andLinux is *not* running inside Virtual PC. Did you try downloading http://www.georgevreilly.com/temp/colinux-daemon.dmp.bz2 and examining it inside WinDbg? That contains the kernel's state at the moment it bugchecked. The !analyze output above isn't enough to tell you why it crashed. I'm not in a position today to attach a kernel debugger to this machine. It's my main dev machine and I don't want to do things that might bluescreen it. I'll install andLinux on another machine and see if I can repro the issue there. ---------------------------------------------------------------------- Comment By: George V. Reilly (george_v_reilly) Date: 2008-05-10 00:44 Message: Logged In: YES user_id=737437 Originator: YES coLinux was installed by andLinux, not directly by me. C:\Program Files\andLinux>colinux-daemon --status-driver Cooperative Linux Daemon, 0.7.1 Compiled on Sat Jul 14 12:15:18 2007 checking if the driver is installed current state: 4 (fully initialized) current number of monitors: 1 current linux api version: 10 current periphery api version: 20 I'm running both andLinux and VPC 2007 on the same instance of Vista x86 SP1. They're peers. Vista is the host for both VPC and andLinux. andLinux is *not* running inside Virtual PC. Did you try downloading http://www.georgevreilly.com/temp/colinux-daemon.dmp.bz2 and examining it inside WinDbg? That contains the kernel's state at the moment it bugchecked. The !analyze output above isn't enough to tell you why it crashed. I'm not in a position today to attach a kernel debugger to this machine. It's my main dev machine and I don't want to do things that might bluescreen it. I'll install andLinux on another machine and see if I can repro the issue there. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-05-09 22:50 Message: Logged In: YES user_id=579204 Originator: NO Hello George, Dan is not active anymore. In the bugcheck I can not see any informations why it crashes. Shure, I see colinux-daemon process was named. If I see right, this userland task kills the nt kernel driver? That I can not understand. In typically bugs the colinux-daemon calls linux.sys and this can crash. Why not there? Next question is, what rule have VPC2007 there? What is the real host for coLinux, and what is the host for VPC2007? You runs VPC2007 as other task on the same machine, and then starts coLinux parallel? Or you have running coLinux and start than VPC2007 parallel? Or runs you one VM in other VM? Is the driver coLinux installed right and running? Please check it with "colinux-daemon --status-driver". Can you run colinux-daemon from in the Windows Debugger? ( I don't know how, please ask Google ) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1959846&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-05-20 20:52:41
|
Bugs item #2760666, was opened at 2009-04-14 04:50 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crash / BSOD Group: None Status: Open >Resolution: Accepted Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) >Assigned to: Henry N. (henryn) Summary: VirtualBOX causes BSOD STOP: 0x0000007F 0x00000008 Initial Comment: Running Parallels or VMWare to virtualise a virtual machine doesnt result in crashing. Trying to boot Windows XP on VirtualBOX at the same time as running COLinux causes it to BSOD the host system (Windows Vista) Its strange but why does VBox BSOD the system whereas Parallels/VMWare can virtualise fine alongside COLinux.. Reproduction: Install VirtualBox Install COLinux V8 Run COLinux Create a new Windows VM In Virtualbox Attempt to Boot the new VM Into Windows setup. BSOD ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-05-20 22:52 Message: Based on idea by Sander Vanleeuwen (http://www.virtualbox.org/ticket/3724#comment:8), have added a check for running VMX. If CPU is unning in VMX mode, coLinux still aborts the guest system, and no longer will crash the host. It's coded in current devel snapshot from SVN revision 1248. Sorry, that we currently don't have support for this mode. I'm locking into Intel manuals to find a solution to run in a cooperative way. Henry ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-29 23:50 Message: coLinux Bug #1959846 seems me the same problem. With a very good crash dump report. Virtual PC 2007 is running there at same time under Vista. https://sourceforge.net/tracker/?func=detail&aid=1959846&group_id=98788&atid=622063 ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-04-29 13:01 Message: I have a similar problem with Windows XP host. (32-bit) Minidumps are not getting generated. Even if PAE/NX/DEP technologies are turned off completely. Nobody: please use some nickname so we could identify you. Nobody: please specify VirtualBox version, and if you use VT-x or not (Hardware Virtualization) For me, the crash happens only with Hardware Virtualization enabled. -Technologov ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-04-29 12:47 Message: Here is the original bug report: Host crash: vboxdrv crashes, when run in VMX mode, together with coLinux http://www.virtualbox.org/ticket/3724 -Technologov ---------------------------------------------------------------------- Comment By: Juergen (juergen_01) Date: 2009-04-29 08:57 Message: Some time ago, a had the same problem with randomly getting a kernel stack overflow. The problem was caused by too many enabled network services on a network interface. I had installed VirtualBox, MS Virtual PC, Norton Internet Security, Cisco VPN Client and MS Network Monitor. All these programs installed a network service. After I disabled 2 or 3 of the network services I was not using at that time, I solved the problem with the kernel stack overflow. You have to disable the services it on every network interface. Well, a BSOD can also be caused by the virtualization features of the CPU. If I am running a VM in VBox with Intel-VT enabled and then starting only the Virtual PC application, my computer is crashing with a BSOD. On an older CPU with no Intel-VT I never had this problem. On this older CPU, I never had any problems with running VBox VMs and colinux instances concurrently. If you do not get a crash dump, this might be caused by the Data-Execution-Prevention in Windows. If this is also enabled for normal applications and not only for windows services, then you will never get a crash dump. Windows is still writing crash dump information to pagefile.sys but it does not generate a crash dump file on next startup. I had the same problem while getting the kernel stack overflow. After disabling DEP for every application Windows created crash dump files again. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-29 03:21 Message: Double fault A double fault occurs when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially, however there are several exceptions that cannot be handled serially and in this situation the processor signals a double fault. The two primary causes for this are hardware and kernel stack overflows. Hardware problems are usually related to CPU, RAM, or bus. Kernel stack overflows are almost always caused by faulty kernel-mode drivers. I can rule out my CPU/RAM since they are relatively new components.. VMWare/Parallels work alongside COLinux just not VirtualBox. I've stress tested this thing for over 72 hours about 2 weeks back since I installed a new CPU cooler.. So I'm guessing its the Kernel Stack Overflow? Any chance you can attempt to reproduce? My Vista is being a pain, its set to do a full mem dump on BSOD but that crash doesnt generate one. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-28 23:49 Message: > STOP: 0x0000007F (0x00000008, 0x801B1000, 0x00000000, 0x00000000) STOP 0x0000007F : UNEXPECTED_KERNEL_MODE_TRAP (sse [1]) 0x00000008 : Double Fault 0x801B1000 : I found no references for that value. [1] http://support.microsoft.com/kb/137539 ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-28 18:04 Message: The system doesnt generate a Minidump from this crash even though configured to. Error is as follows: STOP: 0x0000007F (0x00000008, 0x801B1000, 0x00000000, 0x00000000) With no further details ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-14 19:57 Message: It would be nice to get an analyze from minidump of that BSOD, so we can see, what caused this crash. Please read "Howto use Windows crash dump" in your colinux file "debugging.txt" or here from source: http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging Henry ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 |
|
From: Benjamin H. <bh...@ud...> - 2009-05-20 12:56:04
|
Hi, I have just tested openwrt-uml running under Pubuntu (Colinux) under Windows Vista: http://zoobab.wikidot.com/openwrt-and-user-mode-linux#toc8 Everything seems to run fine. -- Benjamin Henrion <bhenrion at ffii.org> FFII Brussels - +32-484-566109 - +32-2-4148403 |
|
From: coLinux a. <col...@he...> - 2009-05-20 04:33:22
|
The autobuild system has detected a new revision in the source repository. Review last changed from changelog.txt, also attached in mail. Download the compiled version: http://www.henrynestler.com/colinux/autobuild/devel-20090519/ colinux-0.8.0-20090519.src.tgz (684743 Bytes) daemons-0.8.0-20090519.dbg.zip (589917 Bytes) daemons-0.8.0-20090519.zip (477338 Bytes) modules-2.6.22.18-co-0.8.0-20090519.tgz (2636584 Bytes) vmlinux-2.6.22.18-co-0.8.0-20090519.zip (1673147 Bytes) Note, the autobuild compilation does not include an installer. Remember to reload the driver with these commands: colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver Inside coLinux please update modules as follow: rm -rf /lib/modules/*-co-* tar -xzf modules-*-co-*-20090519.tgz -C / The autobuild compilations are not official releases of Cooperative Linux software. There is no warranty that any autobuild version is stable. If use this autobuild version, please give us feedback of your experience. Job runs on machine with 64 bit version of gcc 4.1.2. A service from http://gcc.gnu.org/wiki/CompileFarm -- Lots of fun with newest version, Henry Nestler ------------------------------------------------------------------------ r1247 | henryn | 2009-05-19 19:22:18 +0000 (Tue, 19 May 2009) | 8 lines Changed paths: M /branches/devel/patch/base-2.6.22.diff M /branches/devel/src/colinux/arch/i386/passage.c M /branches/devel/src/colinux/arch/i386/utils.c M /branches/devel/src/colinux/arch/i386/utils.h * Remove floating point handling from passage page code. FPU save/restore only on demand and only inside Linux guest kernel, if Linux kernel or Linux userland needs the FPU. In cases where FPU was not used on Linux guest side, the registers of FPU are not touched. That saves some time between operating system switches. It's 1 percent (or less) faster now. * Increase CO_LINUX_API_VERSION to 13, avoids crashes. (Contributed by Paolo Minazzi and Henry Nestler) ------------------------------------------------------------------------ r1246 | henryn | 2009-05-19 18:59:56 +0000 (Tue, 19 May 2009) | 1 line Changed paths: M /branches/devel/src/colinux/kernel/monitor.c * Fixup warning unused label "error_3". ------------------------------------------------------------------------ |
|
From: H. N. <hen...@ar...> - 2009-05-17 11:00:36
|
tarsman wrote: > My network setup (TAP) works fine with coLinux 0.7.3. > in my config file: > eth0=tuntap,"TAPA", > eth1=pcap-bridge,"winXP", > > But not in coLinux 0.7.4 even if I made a clean installation. > I got this error: > eth0: /ERROR while getting interface flags/: /No such device > / eth1: /ERROR while getting interface flags/: /No such device/ udev renames the interfaces based on different MAC numbers. Please follow the notes for upgrading, and remove all entries from /etc/udev/rules.d/z25_persistent-net.rules, than reboot coLinux. All details about this problen found in Bug #1861876 http://sourceforge.net/tracker/?func=detail&aid=1861876&group_id=98788&atid=622063 -- Henry N. --------------------------------------------------------- ... Es folgt Arcor Werbung | Ads follows by Arcor ... Arcor.de Gaming Area - kostenfrei daddeln bis der Arzt kommt! Jetzt checken und aus über 80 Spielen wählen! http://www.arcor.de/footer-gaming/ |
|
From: tarsman <ta...@gm...> - 2009-05-17 07:20:56
|
Hi all!, My network setup (TAP) works fine with coLinux 0.7.3. in my config file: eth0=tuntap,"TAPA", eth1=pcap-bridge,"winXP", But not in coLinux 0.7.4 even if I made a clean installation. I got this error: eth0: ERROR while getting interface flags: No such device eth1: ERROR while getting interface flags: No such device/ /Host OS is windowsXP Pro SP3. And I am using Debian image. Any insights? Thanks, tarsman |
|
From: tarsman <ta...@gm...> - 2009-05-17 06:28:43
|
Hi all!,
My network setup (TAP) works fine with coLinux 0.7.3.
in my config file:
eth0=tuntap,"TAPA",
eth1=pcap-bridge,"winXP",
But not in coLinux 0.7.4 even if I made a clean installation.
I got this error:
eth0: /ERROR while getting interface flags/: /No such device
/ eth1: /ERROR while getting interface flags/: /No such device/
Host OS is windowsXP Pro SP3.
Any insights?
Thanks,
tarsman
|
|
From: SourceForge.net <no...@so...> - 2009-05-17 00:22:12
|
Bugs item #1959846, was opened at 2008-05-08 01:38 Message generated for change (Comment added) made by technologov You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1959846&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: v0.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: George V. Reilly (george_v_reilly) Assigned to: Nobody/Anonymous (nobody) Summary: Bugcheck in coLinux when starting VM from Virtual PC 2007 Initial Comment: I sent the message below to Dan Aloni but never got a reply. I would have filed a bug back then, but there's no obvious link to the SF bug tracker on the colinux.org website. ---------- Forwarded message ---------- From: George V. Reilly <ge...@re...> Date: 2008/4/10 Subject: Bugcheck in coLinux when starting VM from VPC2007 To: Dan Aloni <da...@co...> I installed andLinux beta 1 rc6 yesterday, on a 4GB quad-core box running x86 Vista SP1. As soon as I launch a virtual machine in Virtual PC 2007, I get a bugcheck in colinux-daemon. This is 100% repeatable. 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: 80154000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ PEB is paged out (Peb.Ldr = 7ffdb00c). Type ".hh dbgerr001" for details PEB is paged out (Peb.Ldr = 7ffdb00c). Type ".hh dbgerr001" for details BUGCHECK_STR: 0x7f_8 TSS: 00000028 -- (.tss 0x28) eax=0000000d ebx=73571250 ecx=883a8ac0 edx=73571280 esi=00000000 edi=73571132 eip=81d0576a esp=73570e6c ebp=73571220 iopl=0 nv up di pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010002 nt!KeBugCheck2+0x1f: 81d0576a 89442424 mov dword ptr [esp+24h],eax ss:0010:73570e90=???????? Resetting default scope DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: colinux-daemon. CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 00000000 to 81d0576a STACK_TEXT: 00000000 81d0576a 00000000 00000000 00000000 nt!KiTrap08+0x75 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTrap08+75 81c91b9e ebee jmp nt!KiTrap08+0x65 (81c91b8e) SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiTrap08+75 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 47918b12 FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap08+75 BUCKET_ID: 0x7f_8_nt!KiTrap08+75 Followup: MachineOwner --------- 0: kd> kv ChildEBP RetAddr Args to Child 00000000 81d0576a 00000000 00000000 00000000 nt!KiTrap08+0x75 (FPO: TSS 28:0) 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f 0: kd> .tss 0x28 eax=0000000d ebx=73571250 ecx=883a8ac0 edx=73571280 esi=00000000 edi=73571132 eip=81d0576a esp=73570e6c ebp=73571220 iopl=0 nv up di pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010002 nt!KeBugCheck2+0x1f: 81d0576a 89442424 mov dword ptr [esp+24h],eax ss:0010:73570e90=???????? 0: kd> kv *** Stack trace for last set context - .thread/.cxr resets it ChildEBP RetAddr Args to Child 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f 0: kd> .ecxr Unable to get exception context, HRESULT 0x8000FFFF 0: kd> !thread THREAD 883a8ac0 Cid 0978.09c0 Teb: 7ffde000 Win32Thread: 00000000 RUNNING on processor 0 IRP List: 87e239f8: (0006,0094) Flags: 00060070 Mdl: 00000000 87e69f68: (0006,0094) Flags: 00060900 Mdl: 88dff0a0 Not impersonating DeviceMap 8ae08808 Owning Process 883855b8 Image: colinux-daemon.exe Wait Start TickCount 53407 Ticks: 0 Context Switch Count 85610 UserTime 00:00:00.031 KernelTime 00:00:05.397 Win32 Start Address 0x766cd1b9 Stack Init 8b243000 Current 8b2429b8 Base 8b243000 Limit 8b240000 Call 0 Priority 9 BasePriority 8 PriorityDecrement 0 IoPriority 2 PagePriority 5 ChildEBP RetAddr Args to Child 00000000 81d0576a 00000000 00000000 00000000 nt!KiTrap08+0x75 (FPO: TSS 28:0) 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f 0: kd> !pcr KPCR for Processor 0 at 81d30800: Major 1 Minor 1 NtTib.ExceptionList: 81d2abe8 NtTib.StackBase: 00000000 NtTib.StackLimit: 00000000 NtTib.SubSystemTib: 80154000 NtTib.Version: 003cb6e5 NtTib.UserPointer: 00000001 NtTib.SelfTib: 7ffde000 SelfPcr: 81d30800 Prcb: 81d30920 Irql: 0000001f IRR: 00000000 IDR: ffffffff InterruptMode: 00000000 IDT: 81afd400 GDT: 81afd000 TSS: 81d2e000 CurrentThread: 883a8ac0 NextThread: 00000000 IdleThread: 81d34640 DpcQueue: I have a crashdump, compressed down to 57MB at http://www.georgevreilly.com/temp/colinux-daemon.dmp.bz2 ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-05-17 03:22 Message: This report looks similar to this: http://www.virtualbox.org/ticket/3724 -Technologov ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-05-10 10:53 Message: I am having the same issue. Anyone looking into this? Any chance of this getting fixed? I can help with testing if needed. ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-04-30 02:26 Message: This report looks similar to this: [https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 this report] ---------------------------------------------------------------------- Comment By: John Stroy (jdstroy) Date: 2009-02-04 04:06 Message: This happens in 0.7.3 as well. 2.6.22.18-co-0.7.3 #1 PREEMPT Sat May 24 22:27:30 UTC 2008 i686 06/17 I got this to happen on Windows Server 2003 Enterprise Edition with MSVPC2007. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-05-10 02:26 Message: Logged In: YES user_id=579204 Originator: NO 0.7.1 has an known bug. Double, triple and endless faults I have seen. See http://www.andlinux.org/news.php for "Apr 18th, 2008". This was fixed in "Apr 21st, 2008: andLinux Beta 1 (final)" I not know ho you can update andLinux version without reinstalling all images. You can still update the coLinux executable files, linux.sys, vmlinux and modules from http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080416-Snapshot/packages/ No, your file have not loaded. Your output are well good and enough. I'm not familiar with this debugger. "!analyze -v" is all I know to do. If the bug would be in the linux.sys, then the !analyse would list such helpfull STACK, for example: http://www.henrynestler.com/colinux/testing/pfn-check-0.7.3/20080410-antinx/minidump041108-01.txt But the known bug is inside Linux kernel and pokes some wildly into the hosts memory, so we never have seen it from Windows debugger. The real interesting summary can read from this file: http://www.henrynestler.com/colinux/testing/pfn-check-0.7.3/20080410-antinx/bug16-recursive-page-fault-endless.txt ---------------------------------------------------------------------- Comment By: George V. Reilly (george_v_reilly) Date: 2008-05-10 01:45 Message: Logged In: YES user_id=737437 Originator: YES coLinux was installed by andLinux, not directly by me. C:\Program Files\andLinux>colinux-daemon --status-driver Cooperative Linux Daemon, 0.7.1 Compiled on Sat Jul 14 12:15:18 2007 checking if the driver is installed current state: 4 (fully initialized) current number of monitors: 1 current linux api version: 10 current periphery api version: 20 I'm running both andLinux and VPC 2007 on the same instance of Vista x86 SP1. They're peers. Vista is the host for both VPC and andLinux. andLinux is *not* running inside Virtual PC. Did you try downloading http://www.georgevreilly.com/temp/colinux-daemon.dmp.bz2 and examining it inside WinDbg? That contains the kernel's state at the moment it bugchecked. The !analyze output above isn't enough to tell you why it crashed. I'm not in a position today to attach a kernel debugger to this machine. It's my main dev machine and I don't want to do things that might bluescreen it. I'll install andLinux on another machine and see if I can repro the issue there. ---------------------------------------------------------------------- Comment By: George V. Reilly (george_v_reilly) Date: 2008-05-10 01:44 Message: Logged In: YES user_id=737437 Originator: YES coLinux was installed by andLinux, not directly by me. C:\Program Files\andLinux>colinux-daemon --status-driver Cooperative Linux Daemon, 0.7.1 Compiled on Sat Jul 14 12:15:18 2007 checking if the driver is installed current state: 4 (fully initialized) current number of monitors: 1 current linux api version: 10 current periphery api version: 20 I'm running both andLinux and VPC 2007 on the same instance of Vista x86 SP1. They're peers. Vista is the host for both VPC and andLinux. andLinux is *not* running inside Virtual PC. Did you try downloading http://www.georgevreilly.com/temp/colinux-daemon.dmp.bz2 and examining it inside WinDbg? That contains the kernel's state at the moment it bugchecked. The !analyze output above isn't enough to tell you why it crashed. I'm not in a position today to attach a kernel debugger to this machine. It's my main dev machine and I don't want to do things that might bluescreen it. I'll install andLinux on another machine and see if I can repro the issue there. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-05-09 23:50 Message: Logged In: YES user_id=579204 Originator: NO Hello George, Dan is not active anymore. In the bugcheck I can not see any informations why it crashes. Shure, I see colinux-daemon process was named. If I see right, this userland task kills the nt kernel driver? That I can not understand. In typically bugs the colinux-daemon calls linux.sys and this can crash. Why not there? Next question is, what rule have VPC2007 there? What is the real host for coLinux, and what is the host for VPC2007? You runs VPC2007 as other task on the same machine, and then starts coLinux parallel? Or you have running coLinux and start than VPC2007 parallel? Or runs you one VM in other VM? Is the driver coLinux installed right and running? Please check it with "colinux-daemon --status-driver". Can you run colinux-daemon from in the Windows Debugger? ( I don't know how, please ask Google ) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1959846&group_id=98788 |
|
From: Alexey E. <al...@gm...> - 2009-05-17 00:21:14
|
Hi all ! A while back (on 21.apr.2009) I wrote that coLinux and VirtualBox running together result in Windows host BSOD Crash. VirtualBox team says, that coLinux driver does things that are not allowed in VMX root mode. Here is the continuation of the story: http://www.virtualbox.org/ticket/3724 any ideas? -- -Alexey Eromenko "Technologov" |
|
From: <bcc...@si...> - 2009-05-16 10:18:27
|
I'm a big fan of coLinux, and I'm wondering when will it support x86_64 host, I compile it in x86_64 redhat linux, and got the following errors:
make[2]: Entering directory `/usr/src/kernels/2.6.9-55.EL-smp-x86_64'
LD /opt/linux/coLinux-0.7.2/src/colinux/os/linux/kernel/module/.module.arch_build/built-in.o
CC /opt/linux/coLinux-0.7.2/src/colinux/os/linux/kernel/module/.module.arch_build/antinx.o
{standard input}: Assembler messages:
{standard input}:423: Error: suffix or operands invalid for `mov'
{standard input}:424: Error: suffix or operands invalid for `mov'
make[4]: *** [/opt/linux/coLinux-0.7.2/src/colinux/os/linux/kernel/module/.module.arch_build/antinx.o] Error 1
make[3]: *** [/opt/linux/coLinux-0.7.2/src/colinux/os/linux/kernel/module/.module.arch_build] Error 2
make[2]: *** [_module_/opt/linux/coLinux-0.7.2/src/colinux/os/linux/kernel/module] Error 2
make[2]: Leaving directory `/usr/src/kernels/2.6.9-55.EL-smp-x86_64'
Error: Target not build (TargetNotBuildError)
make[1]: *** [colinux] Error 1
make[1]: Leaving directory `/opt/linux/coLinux-0.7.2/src'
make: *** [colinux] Error 2
if I use the gcc -m32 option then I got the following errors:
/root/glibc/linux/coLinux-0.7.3/src/colinux/os/linux/kernel/module/.module.arch_build/antinx.c:1: error: code model ‘kernel’ not supported in the 32 bit mode
|
|
From: Henry N. <hen...@ar...> - 2009-05-15 19:57:50
|
Cooperative Linux version 0.7.4 was released now. Release: 0.7.4 Kernel: 2.6.22.18 Build date: 15-April-2009 Lots of bugs are fixed. New device scsi for whole disk, faster kernel mode bridged network, cofs supports unix file attributes, variable size for boot console, and some small things more. Please check the project file release and wiki for information, updates and progress. Downloads: http://sourceforge.net/projects/colinux/files Changes: http://colinux.wikia.com/wiki/Version_0.7.4 Wiki: http://colinux.wikia.com Snapshots: http://www.colinux.org/snapshots ---- NEWS Filesystem: * New: cofs rename allows to overwrite files with ReadOnly attrib. * New: cofs supports flat file modes "rwx" for owner. Mount option "noattrib" disables these attribute mapping for older compatibility. * Use "setcobd=async" to enable asynchronous mode for cobd devices. * Bug #2013435: cobd supports read-only files now. * Bug #2152550: cofs atime and mtime was swapped on time set. * Bug #2176188: File sync wrong on cofs, command after mv/rename fails. Network: * pcap-bridge: Fix suspend problems. Reconnect after loosing adapter. * New network "ndis-bridge" works in kernel mode and is the faster alternative to pcap-bridge. (Ligong Liu) * Bug #1396539: Fixing the "eth0: duplicate address detected!". New filter rule for ndis-bridge and pcap-bridge is: "(ether dst MAC) or (multicast and not ether src MAC)" * Bug #2055697: Crashing SLiRP under heavy usage ktorrent. (Shai Vaingast) * Bug #2357494,#2365031: ndis-bridge was not working with PPPoE, AoE and others types as IP and ARP packets. Type filter removed now. Console and daemons: * New: Added "cocon=COLSxROWS" to use console size, other than 80x25. * Bug #1117788: Fix sticky ALT after system menu from ALT-Space. * Bug #2013501: Stop with error message on empty parameters. * Bug #2593186: FLTK console command prompt display problems. (Shai Vaingast) * Bugfix: Enclose spaces in current directory for install-service. Kernel: * scsi: New device for images with partition tables and works async. Usage "scsi0=disk,file.img" or "scsi1=cdrom,file.iso" (Steve Shoecraft) * Added virtual pci device handling. "lspci" is working (Steve Shoecraft) * Add PG_co_host_mapped, save many OS switching times: speed up coLinux. * New: /proc/colinux/stats show counts of OS switches. * unionfs-2.2.4 added as module. (Marwan Al-Sabbagh) * Add sysenter / sysexit restoration support, for cpu with SEP feature. * Bug #2524658: GPF on raid5/6 md array by accessing MMX/XMM-registers. * Feature req #2114493: Add iscsi kernel support (CONFIG_ISCSI_TCP). Installer: * New images: Fedora 10, Ubuntu 7.10 Debugging: * Enable host kernel debug via registry [HKLM\SOFTWARE\coLinux] "Debug" Updated libraries and tools: * mingw 3.14 * w32api 3.11 -- Henry N. |
|
From: SourceForge.net <no...@so...> - 2009-05-13 15:01:09
|
Bugs item #1745597, was opened at 2007-06-29 23:23 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1745597&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: BSOD on Windows Server 2003 with Adaptec AIC-9580W RAID Ctrl Initial Comment: I am trying to install coLinux-0.6.4.exe on a system that is running Windows server 2003 and has a Adaptec AIC-9580W RAID controller (aka ServeRAID 8k-l or 8k) installed on it. The installation gets about 98% complete and then it gives the BSOD (blus screen of death) with the STOP: 0x1111777A (0x0, 0x0, 0x0, 0x0) code at the bottom. I have been able to install colinux-0.6.4 on systems that are running Windows Server 2003, but do not have the RAID Controller HW. I was also able to install colinux-0.6.4 on a system that is running Windows 2000 and has a Adaptec AIC-9580W RAID controller (aka ServeRAID 8k-l or 8k) installed on it. I have tired various configuratoins in the boot.ini file (i.e. /NOEXECUTE, /APE, /NOAPE etc), but the BSOD still shows up. I have also tried coLinux development version 0.8.0. This version installs the linux.sys driver (using the colinux-daemon --install-driver commmand) without giving the BSOD, but when coLinux-daemon.exe is executed the BSOD shows up with the following message: IRQL_NOT_LESS_OR_EQUAL Here is some system information on the machine that has Windows Server 2003 and the Adaptec AIC-9580W RAID controller (aka ServeRAID 8k-l or 8k) installed on it: a two socket server utilizing Intel Xeon 5000 series processors Intel 5000X chipset Adaptec AIC-9580W RAID controller (aka ServeRAID 8k-l or 8k) Max memory supported is 32GB. Anyone have any suggestions as to what the cause of the BSOD is? Thank you ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-05-13 15:00 Message: Does the latest build (0.8.0) able to run under Window 2003 Server R2 SP2 with more than 4GB?? ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-09-24 18:46 Message: Logged In: YES user_id=579204 Originator: NO ok, was an older colinux driver without versions checking. Closed bug now. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-08-21 16:12 Message: Logged In: NO Solved! one uppon a time it happens that there was a linux.sys which did not run with mem=128, running with mem=126 was OK. That was 0.6.1 or 0.6.2! And that linux.sys was installed on the box which BSODs. After deinstalling: No problems any more! Thanks a lot! But i am pretty sure i started the colinux 0.7.1 daemon from the pen drive. Why didn't it complain about that old driver? Was the BSOD faster? Some infos over the old driver: hardware wizzard shows as details only: ROOT\LEGACY_COLINUXDRIVER\0000 dir: 29.05.2004 16:59 237.649 coLinux-0.6.1.tar.gz 05.02.2005 10:57 422.441 colinux-0.6.2.tar.gz 29.05.2004 15:20 274.784 colinux-bridged-net-daemon.exe 29.05.2004 15:20 713.682 colinux-console-fltk.exe 29.05.2004 15:20 402.411 colinux-console-nt.exe 29.05.2004 15:20 338.449 colinux-daemon.exe 29.05.2004 15:20 274.032 colinux-net-daemon.exe 14.07.2004 00:54 62.146.666 Debian-20040605-mit.ext3.1610mb.bz2 09.06.2005 15:18 18.329.320 Debian-3.0r0.ext3.1gb.bz2 10.11.2004 17:05 1.073.741.824 Debian-3.0r2.ext3-mit-backports.1gb 27.06.2004 00:36 22.449.829 Debian-3.0r2.ext3-mit-backports.1gb.bz2 25.04.2004 16:35 1.112 default.colinux.xml 10.11.2004 17:03 1.247 default.colinux.xml.$$$ 10.11.2004 17:04 1.256 default.colinux.xml.old 29.05.2004 15:20 94.327 linux.sys 09.06.2005 15:10 <DIR> netdriver 20.04.2004 06:43 5.014 README 09.06.2005 15:10 60.313 Uninstall.exe 29.05.2004 14:32 1.822.230 vmlinux 29.05.2004 15:20 641.763 vmlinux-modules.tar.gz After deinstalling the old colinux and install 0.8.0 i get, when started from pendrive: Cooperative Linux Daemon, 0.7.1 Compiled on Sat Jul 14 12:15:18 2007 using 'vmlinux' as kernel image configuring 128 MB of virtual RAM mapping cobd4 to \Device\Cdrom0 mapping cobd1 to \??\E:\colinux.disks\swap_file mapping cobd0 to \??\E:\colinux.disks\Debian-3.0r2.ext3-mit-backports.1gb mapping hdc to cobd4 mapping hdb to cobd1 mapping hda to cobd0 configured Slirp as eth0 redirections tcp:15022:22/tcp:15080:80/tcp:5901:5901 mapping cofs0 to \??\E:\colinux.disks\exchange using 'initrd.gz' as initrd image mapping cofs31 to \??\E:\coLinux kernel boot parameters: 'root=/dev/cobd0' colinux: manager open: last error: Das System kann die angegebene Datei nicht finden. daemon: exit code 8320a80e daemon: can't access CoLinuxDriver, please check status driver! back to "E:\coLinux\colinuxstart.cmd"... So i it is still a dream to run a "linux-in-a-box" without an installed driver or admin rights. Mark Russinovich (wininterals etc.) one made that trick with his "filemon" IIRC. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-08-21 08:56 Message: Logged In: YES user_id=579204 Originator: NO There exist an variable for total ram used by coLinux (your "mem=xx") This variable exist in a struct on daemon and will transfer to the driver linux.sys, this calls than the malloc. (has to do with co_os_physical_memory_pages() and the automatic down rounder for variable "hostmem_used") Very old coLinux has no version check (think before 0.6.4, but not remember). Current Daemon first checks the version of linux.sys and don't start. You can start coLinux from a USB stick. But you need to load ones the driver. After you have the driver updated, you can run without admin rights. If you say, this machine has never been seen coLinux before, then the daemon would not start. Check the hardware device manager and enable "hidden devices", then you can see the colinux driver, under "non PnP drivers". This scren shows the way howto find the driver by mouse clicks: http://www.henrynestler.com/colinux/screenshoots/driver-details-grayed.png Remove this driver and restart windows. Or run "colinux-daemon.exe --remove-driver" (do the same without reboot). ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-08-20 22:42 Message: Logged In: NO >>Comment By: Henry N. (henryn) >Date: 2007-08-20 11:58 >Message: >Logged In: YES >user_id=579204 >Originator: NO >Hello, >can't resolve the stack to source, because I can't find a matching >binary linux.sys from there you got the BSOD. I used the normal linux.sys from the windows install. I added file sizes and dates. >Your address "linux+52e6" is inside the >function co_os_malloc, >and the condition for this bug is a call "co_os_malloc(0)". Jepp. i already analyzed the sources but could not see any place where co_os_malloc etc. could(!) be called with a "0". At all locations (i found) that param was a compile time constant value excpt one. So it currently sounds like an ugly pointer error or bad case/table jump. >Are you shure, that you have called >"colinux-daemon.exe --remove-driver" >and "colinux-daemon.exe --install-driver" >between the change of coLinux versions? Hm. No. because i assumed that the machine never saw colinux before. And i was not aware that this could be a problem at all because I spawned colinux from a 4GB USB-Drive without any install because in wanted to test it without admin rights... I was very surprised to BSOD a box (without admin rights, i thought), but if an old installed driver was used, a BSOD is possible. Would colinux-daemon.exe use any installed linux.sys without any version check? That would explain the problem. I'll have a look if a (very old) linux.sys was installed long time ago tomorrow. >Replacing the file linux.sys and the exe daemons in the directory >are not enough. I thought it would, because i did not install it. Maybe some else did. My intention was do have "my own linux on a stick" but if it uses the installed stone aged linux.sys it could always crash. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-08-20 09:58 Message: Logged In: YES user_id=579204 Originator: NO Hello, can't resolve the stack to source, because I can't find a matching binary linux.sys from there you got the BSOD. Your address "linux+52e6" is inside the function co_os_malloc, and the condition for this bug is a call "co_os_malloc(0)". See line 63: http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/src/colinux/os/winnt/kernel/lowlevel/alloc.c?view=markup The 1111777A exist only ones in the source. So your address "linux+52e6" should match an address ones behind the BugCheck-call. > ef6d92db 687a771111 push 1111777Ah <-- BugCheck code > ef6d92e0 ff1518e16def call dword ptr [linux+0xa118 (ef6de118)] <-- calls KeBugCheck > ef6d92e6 <--- this is the sddress you see in stack trace In your disassemble I can see. But, I have no this file, you used. We must use exactly the same linux.sys for analysis from where you got the bug. I see different build date and file size for linux.sys. Nothing of my known files matched with your disassembler output. Are you shure, that you have called "colinux-daemon.exe --remove-driver" and "colinux-daemon.exe --install-driver" between the change of coLinux versions? Replacing the file linux.sys and the exe daemons in the directory are not enough. I have added more informations to the bugcheck 1111777A to see the caller. Please do a clean install from http://www.henrynestler.com/colinux/testing/devel-0.8.0/20070819-Snapshot/ I see, you have WinDbg installed. This is very good. You can send me the output from "kd> !analyze -v" via Mail. In "debugging.txt" have added the way howto resolve the symbols from linux.sys by hands. Hope, this helps. Henry ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-08-08 08:26 Message: Logged In: YES user_id=579204 Originator: NO BSOD 0x1111777A can have more as one initial errors (more as the known and fixed call). Many thanks for the 'STACK_TEXT:', can see the linux calls. Will check it. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-08-07 15:00 Message: Logged In: NO Sorry, I forgot to emphesis: I already tried the "developer driver" as the file date "2007-07-14" indicates. So: BSOD 0x111177A is not fixed in 0.71 Have not tried 0.8 because there is no zip where i can take the driver from. But as 0.8 and 0.71 has the same patches... Have tried Debug version of 0.71, but the symbol information is not acepted by kernel debugger and thatverion ist a bit older. Debug version 0.7.1 (build on 26 March 2007) still show the BSOD. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-08-07 14:51 Message: Logged In: NO linux.sys BSDOD 0x111177A coLinux-0.7.1 Internal Version: 1.1.0.0 linux.sys 69120 byte 2007-07-14 14:15 Debug: linux.sys 139.730 139.730 2007-03-09 02:42 (But symbols are not usable) Starting gives BSOD on an normal Office PC running "Windows XP 2002 SP2 Celeron 2,80GHz, 504MB RAM" 512MiB RAM, 2GiB Swap Trendmicro Virus scanner "Slirp" network So that's no problem of "too much memory", i assume. Invoked by from USB flash drive by: set ETH=eth0=slirp,,tcp:5022:22 set WINSHARE=cofs0=\colinux.disks\exchange set MEM=128 set CDROM0=cobd4=\Device\Cdrom0 hdc=:cobd4 set BOOTDEV=cobd0 set ROOTFS=%BOOTDEV%=\colinux.disks\Debian-3.0r2.ext3-mit-backports.imi set ROOTFS=%BOOTDEV%=\colinux.disks\Debian-3.0r2.ext3-mit-backports.1gb set ROOTFS=%ROOTFS% root=/dev/%BOOTDEV% hda=:%BOOTDEV% set SWAPDEV=cobd1 set SWAPFS=%SWAPDEV%=\colinux.disks\swap_file hdb=:%SWAPDEV% set OPTIONS=-k set OPTIONS=%OPTIONS% -t NT \coLinux\colinux-daemon.exe %OPTIONS% kernel=vmlinux initrd=initrd.gz mem=%MEM% %CDROM0% %SWAPFS% %ROOTFS% %WINSHARE% %ETH% Reducing paramters to minimum does not change behavior. --- Analysis of core dump: kd -z c:\Dump\MEMORY.DMP -i c:\coLinux\ -y c:\Symbols\ *** ERROR: Symbol file could not be found. Defaulted to export symbols for NDIS.sys - Probably caused by : linux.sys ( linux+52e6 ) Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatibl Product: WinNt, suite: TerminalServer SingleUserTS Built by: 2600.xpsp_sp2_gdr Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620 Debug session time: Tue Aug 7 11:27:53.602 2007 (GMT+2) System Uptime: 0 days 0:25:19.109 PEB is paged out (Peb.Ldr = 7ffdc00c). Type ".hh dbgerr001" for details BugCheck 1111777A, {0, 0, 0, 0} Probably caused by : linux.sys ( linux+52e6 ) MODULE_NAME: linux FAULTING_MODULE: 804d7000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 40b88e1b DEFAULT_BUCKET_ID: WRONG_SYMBOLS BUGCHECK_STR: 0x111777A LAST_CONTROL_TRANSFER: from ef6d92e6 to 80533523 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. ee441b14 ef6d92e6 1111777a 818fc65c ee441b74 nt!KeBugCheck+0x14 ee441b34 ef6d7742 00000000 00000000 ee441bc4 linux+0x52e6 ee441b74 ef6d7aa6 81beb3a8 00000000 818fc638 linux+0x3742 ee441b94 ef6d7c5b 81beb3a8 81705000 80561b40 linux+0x3aa6 ee441bc4 ef6d86c4 81beb3a8 00000011 81705000 linux+0x3c5b ee441c14 ef6d86f3 81beb2f0 81a85418 81705000 linux+0x46c4 ee441c34 804e37f7 81beb2f0 81a85418 806ee2d0 linux+0x46f3 ee441c58 8057ad03 81beb2f0 81a85418 818fc650 nt!IofCallDriver+0x32 ee441d00 8057d281 000007c8 00000000 00000000 nt!SeQueryAuthenticationIdToken+0x6c6 ee441d34 804de7ec 000007c8 00000000 00000000 nt!NtDeviceIoControlFile+0x2a ee441ddc 804f827a f8332b85 82187f48 00000000 nt!ZwYieldExecution+0xb78 ee441de0 f8332b85 82187f48 00000000 0000037f nt!KeInitializeTimer+0x107 ee441de4 82187f48 00000000 0000037f 00000000 NDIS!NdisFreeToBlockPool+0x15e1 ee441de8 00000000 0000037f 00000000 00000000 0x82187f48 STACK_COMMAND: kb FOLLOWUP_IP: linux+52e6 ef6d92e6 83c40c add esp,0Ch SYMBOL_STACK_INDEX: 1 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: linux.sys SYMBOL_NAME: linux+52e6 BUCKET_ID: WRONG_SYMBOLS kd> r eax=ffdff13c ebx=00000000 ecx=00000000 edx=00000032 esi=81beb3a8 edi=818fc65c eip=80533523 esp=ee441afc ebp=ee441b14 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286 nt!KeBugCheck+0x14: 80533523 5d pop ebp kd> u nt!KeBugCheck+0x14: 80533523 5d pop ebp 80533524 c20400 ret 4 80533527 90 nop kd> u ef6d92d8 linux+0x52d8: ef6d92d8 83ec0c sub esp,0Ch ef6d92db 687a771111 push 1111777Ah ef6d92e0 ff1518e16def call dword ptr [linux+0xa118 (ef6de118)] ef6d92e6 83c40c add esp,0Ch ef6d92e9 ebd5 jmp linux+0x52c0 (ef6d92c0) ef6d92eb 90 nop ef6d92ec 8d742600 lea esi,[esi] ef6d92f0 55 push ebp linux+0x52c0: ef6d92c0 83ec04 sub esp,4 ef6d92c3 68636f6c78 push 786C6F63h ef6d92c8 53 push ebx ef6d92c9 6a00 push 0 ef6d92cb ff15fce06def call dword ptr [linux+0xa0fc (ef6de0fc)] ef6d92d1 8b5dfc mov ebx,dword ptr [ebp-4] ef6d92d4 89ec mov esp,ebp ef6d92d6 5d pop ebp C:\Programme\Debugging Tools for Windows>dir d:\coLinux\linux.sys 19.03.2007 02:42 139.730 linux.sys C:\Programme\Debugging Tools for Windows>symchk.exe d:\coLinux\linux.sys SYMCHK: linux.sys FAILED - Built without debugging information. SYMCHK: FAILED files = 1 SYMCHK: PASSED + IGNORED files = 0 Source: System Error Cat: (102) ID: 1003 Error code 1111777a, 1. Parameter 00000000, 2. Parameter 00000000, 3. Parameter 00000000, 4. Parameter 00000000. 0000: 53 79 73 74 65 6d 20 45 System E 0008: 72 72 6f 72 20 20 45 72 rror Er 0010: 72 6f 72 20 63 6f 64 65 ror code 0018: 20 31 31 31 31 37 37 37 1111777 0020: 61 20 20 50 61 72 61 6d a Param 0028: 65 74 65 72 73 20 30 30 eters 00 0030: 30 30 30 30 30 30 2c 20 000000, 0038: 30 30 30 30 30 30 30 30 00000000 0040: 2c 20 30 30 30 30 30 30 , 000000 0048: 30 30 2c 20 30 30 30 30 00, 0000 0050: 30 30 30 30 0000 ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-07-02 18:18 Message: Logged In: YES user_id=579204 Originator: NO Yes, the BSOD (0x1111777A) is fixed at 2007-03-24 in Version 0.8.0 http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/src/colinux/os/winnt/kernel/lowlevel/misc.c?view=log BSOD also fixed in pre version 0.7.1 (build on 26 March 2007). Version 0.6.4 would no fix, is to old. The changes on linux.sys installer prevents the install of this driver, if you have more than 4GB RAM, but should no crash with IRQL_NOT_LESS_OR_EQUAL, if the daemon tries to load it. How many memory you have? 32GB? What says the screen by pressing keys Win+Pause? The main problem is: You have to many memory. CoLinux would run, if you limit your host memory to 4GB totaly RAM /MAXMEM=4096 in your C:\BOOT.INI Sorry more is not usable by current design ;-( CoLinux can not run on machines with more as 4GB RAM. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1745597&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-05-10 07:53:42
|
Bugs item #1959846, was opened at 2008-05-07 22:38 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1959846&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: v0.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: George V. Reilly (george_v_reilly) Assigned to: Nobody/Anonymous (nobody) Summary: Bugcheck in coLinux when starting VM from Virtual PC 2007 Initial Comment: I sent the message below to Dan Aloni but never got a reply. I would have filed a bug back then, but there's no obvious link to the SF bug tracker on the colinux.org website. ---------- Forwarded message ---------- From: George V. Reilly <ge...@re...> Date: 2008/4/10 Subject: Bugcheck in coLinux when starting VM from VPC2007 To: Dan Aloni <da...@co...> I installed andLinux beta 1 rc6 yesterday, on a 4GB quad-core box running x86 Vista SP1. As soon as I launch a virtual machine in Virtual PC 2007, I get a bugcheck in colinux-daemon. This is 100% repeatable. 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: 80154000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ PEB is paged out (Peb.Ldr = 7ffdb00c). Type ".hh dbgerr001" for details PEB is paged out (Peb.Ldr = 7ffdb00c). Type ".hh dbgerr001" for details BUGCHECK_STR: 0x7f_8 TSS: 00000028 -- (.tss 0x28) eax=0000000d ebx=73571250 ecx=883a8ac0 edx=73571280 esi=00000000 edi=73571132 eip=81d0576a esp=73570e6c ebp=73571220 iopl=0 nv up di pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010002 nt!KeBugCheck2+0x1f: 81d0576a 89442424 mov dword ptr [esp+24h],eax ss:0010:73570e90=???????? Resetting default scope DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: colinux-daemon. CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 00000000 to 81d0576a STACK_TEXT: 00000000 81d0576a 00000000 00000000 00000000 nt!KiTrap08+0x75 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTrap08+75 81c91b9e ebee jmp nt!KiTrap08+0x65 (81c91b8e) SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiTrap08+75 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 47918b12 FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap08+75 BUCKET_ID: 0x7f_8_nt!KiTrap08+75 Followup: MachineOwner --------- 0: kd> kv ChildEBP RetAddr Args to Child 00000000 81d0576a 00000000 00000000 00000000 nt!KiTrap08+0x75 (FPO: TSS 28:0) 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f 0: kd> .tss 0x28 eax=0000000d ebx=73571250 ecx=883a8ac0 edx=73571280 esi=00000000 edi=73571132 eip=81d0576a esp=73570e6c ebp=73571220 iopl=0 nv up di pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010002 nt!KeBugCheck2+0x1f: 81d0576a 89442424 mov dword ptr [esp+24h],eax ss:0010:73570e90=???????? 0: kd> kv *** Stack trace for last set context - .thread/.cxr resets it ChildEBP RetAddr Args to Child 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f 0: kd> .ecxr Unable to get exception context, HRESULT 0x8000FFFF 0: kd> !thread THREAD 883a8ac0 Cid 0978.09c0 Teb: 7ffde000 Win32Thread: 00000000 RUNNING on processor 0 IRP List: 87e239f8: (0006,0094) Flags: 00060070 Mdl: 00000000 87e69f68: (0006,0094) Flags: 00060900 Mdl: 88dff0a0 Not impersonating DeviceMap 8ae08808 Owning Process 883855b8 Image: colinux-daemon.exe Wait Start TickCount 53407 Ticks: 0 Context Switch Count 85610 UserTime 00:00:00.031 KernelTime 00:00:05.397 Win32 Start Address 0x766cd1b9 Stack Init 8b243000 Current 8b2429b8 Base 8b243000 Limit 8b240000 Call 0 Priority 9 BasePriority 8 PriorityDecrement 0 IoPriority 2 PagePriority 5 ChildEBP RetAddr Args to Child 00000000 81d0576a 00000000 00000000 00000000 nt!KiTrap08+0x75 (FPO: TSS 28:0) 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f 0: kd> !pcr KPCR for Processor 0 at 81d30800: Major 1 Minor 1 NtTib.ExceptionList: 81d2abe8 NtTib.StackBase: 00000000 NtTib.StackLimit: 00000000 NtTib.SubSystemTib: 80154000 NtTib.Version: 003cb6e5 NtTib.UserPointer: 00000001 NtTib.SelfTib: 7ffde000 SelfPcr: 81d30800 Prcb: 81d30920 Irql: 0000001f IRR: 00000000 IDR: ffffffff InterruptMode: 00000000 IDT: 81afd400 GDT: 81afd000 TSS: 81d2e000 CurrentThread: 883a8ac0 NextThread: 00000000 IdleThread: 81d34640 DpcQueue: I have a crashdump, compressed down to 57MB at http://www.georgevreilly.com/temp/colinux-daemon.dmp.bz2 ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-05-10 07:53 Message: I am having the same issue. Anyone looking into this? Any chance of this getting fixed? I can help with testing if needed. ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-04-29 23:26 Message: This report looks similar to this: [https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 this report] ---------------------------------------------------------------------- Comment By: John Stroy (jdstroy) Date: 2009-02-04 02:06 Message: This happens in 0.7.3 as well. 2.6.22.18-co-0.7.3 #1 PREEMPT Sat May 24 22:27:30 UTC 2008 i686 06/17 I got this to happen on Windows Server 2003 Enterprise Edition with MSVPC2007. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-05-09 23:26 Message: Logged In: YES user_id=579204 Originator: NO 0.7.1 has an known bug. Double, triple and endless faults I have seen. See http://www.andlinux.org/news.php for "Apr 18th, 2008". This was fixed in "Apr 21st, 2008: andLinux Beta 1 (final)" I not know ho you can update andLinux version without reinstalling all images. You can still update the coLinux executable files, linux.sys, vmlinux and modules from http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080416-Snapshot/packages/ No, your file have not loaded. Your output are well good and enough. I'm not familiar with this debugger. "!analyze -v" is all I know to do. If the bug would be in the linux.sys, then the !analyse would list such helpfull STACK, for example: http://www.henrynestler.com/colinux/testing/pfn-check-0.7.3/20080410-antinx/minidump041108-01.txt But the known bug is inside Linux kernel and pokes some wildly into the hosts memory, so we never have seen it from Windows debugger. The real interesting summary can read from this file: http://www.henrynestler.com/colinux/testing/pfn-check-0.7.3/20080410-antinx/bug16-recursive-page-fault-endless.txt ---------------------------------------------------------------------- Comment By: George V. Reilly (george_v_reilly) Date: 2008-05-09 22:45 Message: Logged In: YES user_id=737437 Originator: YES coLinux was installed by andLinux, not directly by me. C:\Program Files\andLinux>colinux-daemon --status-driver Cooperative Linux Daemon, 0.7.1 Compiled on Sat Jul 14 12:15:18 2007 checking if the driver is installed current state: 4 (fully initialized) current number of monitors: 1 current linux api version: 10 current periphery api version: 20 I'm running both andLinux and VPC 2007 on the same instance of Vista x86 SP1. They're peers. Vista is the host for both VPC and andLinux. andLinux is *not* running inside Virtual PC. Did you try downloading http://www.georgevreilly.com/temp/colinux-daemon.dmp.bz2 and examining it inside WinDbg? That contains the kernel's state at the moment it bugchecked. The !analyze output above isn't enough to tell you why it crashed. I'm not in a position today to attach a kernel debugger to this machine. It's my main dev machine and I don't want to do things that might bluescreen it. I'll install andLinux on another machine and see if I can repro the issue there. ---------------------------------------------------------------------- Comment By: George V. Reilly (george_v_reilly) Date: 2008-05-09 22:44 Message: Logged In: YES user_id=737437 Originator: YES coLinux was installed by andLinux, not directly by me. C:\Program Files\andLinux>colinux-daemon --status-driver Cooperative Linux Daemon, 0.7.1 Compiled on Sat Jul 14 12:15:18 2007 checking if the driver is installed current state: 4 (fully initialized) current number of monitors: 1 current linux api version: 10 current periphery api version: 20 I'm running both andLinux and VPC 2007 on the same instance of Vista x86 SP1. They're peers. Vista is the host for both VPC and andLinux. andLinux is *not* running inside Virtual PC. Did you try downloading http://www.georgevreilly.com/temp/colinux-daemon.dmp.bz2 and examining it inside WinDbg? That contains the kernel's state at the moment it bugchecked. The !analyze output above isn't enough to tell you why it crashed. I'm not in a position today to attach a kernel debugger to this machine. It's my main dev machine and I don't want to do things that might bluescreen it. I'll install andLinux on another machine and see if I can repro the issue there. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-05-09 20:50 Message: Logged In: YES user_id=579204 Originator: NO Hello George, Dan is not active anymore. In the bugcheck I can not see any informations why it crashes. Shure, I see colinux-daemon process was named. If I see right, this userland task kills the nt kernel driver? That I can not understand. In typically bugs the colinux-daemon calls linux.sys and this can crash. Why not there? Next question is, what rule have VPC2007 there? What is the real host for coLinux, and what is the host for VPC2007? You runs VPC2007 as other task on the same machine, and then starts coLinux parallel? Or you have running coLinux and start than VPC2007 parallel? Or runs you one VM in other VM? Is the driver coLinux installed right and running? Please check it with "colinux-daemon --status-driver". Can you run colinux-daemon from in the Windows Debugger? ( I don't know how, please ask Google ) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1959846&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-04-29 23:26:07
|
Bugs item #1959846, was opened at 2008-05-08 01:38 Message generated for change (Comment added) made by technologov You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1959846&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: v0.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: George V. Reilly (george_v_reilly) Assigned to: Nobody/Anonymous (nobody) Summary: Bugcheck in coLinux when starting VM from Virtual PC 2007 Initial Comment: I sent the message below to Dan Aloni but never got a reply. I would have filed a bug back then, but there's no obvious link to the SF bug tracker on the colinux.org website. ---------- Forwarded message ---------- From: George V. Reilly <ge...@re...> Date: 2008/4/10 Subject: Bugcheck in coLinux when starting VM from VPC2007 To: Dan Aloni <da...@co...> I installed andLinux beta 1 rc6 yesterday, on a 4GB quad-core box running x86 Vista SP1. As soon as I launch a virtual machine in Virtual PC 2007, I get a bugcheck in colinux-daemon. This is 100% repeatable. 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: 80154000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ PEB is paged out (Peb.Ldr = 7ffdb00c). Type ".hh dbgerr001" for details PEB is paged out (Peb.Ldr = 7ffdb00c). Type ".hh dbgerr001" for details BUGCHECK_STR: 0x7f_8 TSS: 00000028 -- (.tss 0x28) eax=0000000d ebx=73571250 ecx=883a8ac0 edx=73571280 esi=00000000 edi=73571132 eip=81d0576a esp=73570e6c ebp=73571220 iopl=0 nv up di pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010002 nt!KeBugCheck2+0x1f: 81d0576a 89442424 mov dword ptr [esp+24h],eax ss:0010:73570e90=???????? Resetting default scope DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: colinux-daemon. CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 00000000 to 81d0576a STACK_TEXT: 00000000 81d0576a 00000000 00000000 00000000 nt!KiTrap08+0x75 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTrap08+75 81c91b9e ebee jmp nt!KiTrap08+0x65 (81c91b8e) SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiTrap08+75 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 47918b12 FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap08+75 BUCKET_ID: 0x7f_8_nt!KiTrap08+75 Followup: MachineOwner --------- 0: kd> kv ChildEBP RetAddr Args to Child 00000000 81d0576a 00000000 00000000 00000000 nt!KiTrap08+0x75 (FPO: TSS 28:0) 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f 0: kd> .tss 0x28 eax=0000000d ebx=73571250 ecx=883a8ac0 edx=73571280 esi=00000000 edi=73571132 eip=81d0576a esp=73570e6c ebp=73571220 iopl=0 nv up di pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010002 nt!KeBugCheck2+0x1f: 81d0576a 89442424 mov dword ptr [esp+24h],eax ss:0010:73570e90=???????? 0: kd> kv *** Stack trace for last set context - .thread/.cxr resets it ChildEBP RetAddr Args to Child 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f 0: kd> .ecxr Unable to get exception context, HRESULT 0x8000FFFF 0: kd> !thread THREAD 883a8ac0 Cid 0978.09c0 Teb: 7ffde000 Win32Thread: 00000000 RUNNING on processor 0 IRP List: 87e239f8: (0006,0094) Flags: 00060070 Mdl: 00000000 87e69f68: (0006,0094) Flags: 00060900 Mdl: 88dff0a0 Not impersonating DeviceMap 8ae08808 Owning Process 883855b8 Image: colinux-daemon.exe Wait Start TickCount 53407 Ticks: 0 Context Switch Count 85610 UserTime 00:00:00.031 KernelTime 00:00:05.397 Win32 Start Address 0x766cd1b9 Stack Init 8b243000 Current 8b2429b8 Base 8b243000 Limit 8b240000 Call 0 Priority 9 BasePriority 8 PriorityDecrement 0 IoPriority 2 PagePriority 5 ChildEBP RetAddr Args to Child 00000000 81d0576a 00000000 00000000 00000000 nt!KiTrap08+0x75 (FPO: TSS 28:0) 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f 0: kd> !pcr KPCR for Processor 0 at 81d30800: Major 1 Minor 1 NtTib.ExceptionList: 81d2abe8 NtTib.StackBase: 00000000 NtTib.StackLimit: 00000000 NtTib.SubSystemTib: 80154000 NtTib.Version: 003cb6e5 NtTib.UserPointer: 00000001 NtTib.SelfTib: 7ffde000 SelfPcr: 81d30800 Prcb: 81d30920 Irql: 0000001f IRR: 00000000 IDR: ffffffff InterruptMode: 00000000 IDT: 81afd400 GDT: 81afd000 TSS: 81d2e000 CurrentThread: 883a8ac0 NextThread: 00000000 IdleThread: 81d34640 DpcQueue: I have a crashdump, compressed down to 57MB at http://www.georgevreilly.com/temp/colinux-daemon.dmp.bz2 ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-04-30 02:26 Message: This report looks similar to this: [https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 this report] ---------------------------------------------------------------------- Comment By: John Stroy (jdstroy) Date: 2009-02-04 04:06 Message: This happens in 0.7.3 as well. 2.6.22.18-co-0.7.3 #1 PREEMPT Sat May 24 22:27:30 UTC 2008 i686 06/17 I got this to happen on Windows Server 2003 Enterprise Edition with MSVPC2007. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-05-10 02:26 Message: Logged In: YES user_id=579204 Originator: NO 0.7.1 has an known bug. Double, triple and endless faults I have seen. See http://www.andlinux.org/news.php for "Apr 18th, 2008". This was fixed in "Apr 21st, 2008: andLinux Beta 1 (final)" I not know ho you can update andLinux version without reinstalling all images. You can still update the coLinux executable files, linux.sys, vmlinux and modules from http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080416-Snapshot/packages/ No, your file have not loaded. Your output are well good and enough. I'm not familiar with this debugger. "!analyze -v" is all I know to do. If the bug would be in the linux.sys, then the !analyse would list such helpfull STACK, for example: http://www.henrynestler.com/colinux/testing/pfn-check-0.7.3/20080410-antinx/minidump041108-01.txt But the known bug is inside Linux kernel and pokes some wildly into the hosts memory, so we never have seen it from Windows debugger. The real interesting summary can read from this file: http://www.henrynestler.com/colinux/testing/pfn-check-0.7.3/20080410-antinx/bug16-recursive-page-fault-endless.txt ---------------------------------------------------------------------- Comment By: George V. Reilly (george_v_reilly) Date: 2008-05-10 01:45 Message: Logged In: YES user_id=737437 Originator: YES coLinux was installed by andLinux, not directly by me. C:\Program Files\andLinux>colinux-daemon --status-driver Cooperative Linux Daemon, 0.7.1 Compiled on Sat Jul 14 12:15:18 2007 checking if the driver is installed current state: 4 (fully initialized) current number of monitors: 1 current linux api version: 10 current periphery api version: 20 I'm running both andLinux and VPC 2007 on the same instance of Vista x86 SP1. They're peers. Vista is the host for both VPC and andLinux. andLinux is *not* running inside Virtual PC. Did you try downloading http://www.georgevreilly.com/temp/colinux-daemon.dmp.bz2 and examining it inside WinDbg? That contains the kernel's state at the moment it bugchecked. The !analyze output above isn't enough to tell you why it crashed. I'm not in a position today to attach a kernel debugger to this machine. It's my main dev machine and I don't want to do things that might bluescreen it. I'll install andLinux on another machine and see if I can repro the issue there. ---------------------------------------------------------------------- Comment By: George V. Reilly (george_v_reilly) Date: 2008-05-10 01:44 Message: Logged In: YES user_id=737437 Originator: YES coLinux was installed by andLinux, not directly by me. C:\Program Files\andLinux>colinux-daemon --status-driver Cooperative Linux Daemon, 0.7.1 Compiled on Sat Jul 14 12:15:18 2007 checking if the driver is installed current state: 4 (fully initialized) current number of monitors: 1 current linux api version: 10 current periphery api version: 20 I'm running both andLinux and VPC 2007 on the same instance of Vista x86 SP1. They're peers. Vista is the host for both VPC and andLinux. andLinux is *not* running inside Virtual PC. Did you try downloading http://www.georgevreilly.com/temp/colinux-daemon.dmp.bz2 and examining it inside WinDbg? That contains the kernel's state at the moment it bugchecked. The !analyze output above isn't enough to tell you why it crashed. I'm not in a position today to attach a kernel debugger to this machine. It's my main dev machine and I don't want to do things that might bluescreen it. I'll install andLinux on another machine and see if I can repro the issue there. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-05-09 23:50 Message: Logged In: YES user_id=579204 Originator: NO Hello George, Dan is not active anymore. In the bugcheck I can not see any informations why it crashes. Shure, I see colinux-daemon process was named. If I see right, this userland task kills the nt kernel driver? That I can not understand. In typically bugs the colinux-daemon calls linux.sys and this can crash. Why not there? Next question is, what rule have VPC2007 there? What is the real host for coLinux, and what is the host for VPC2007? You runs VPC2007 as other task on the same machine, and then starts coLinux parallel? Or you have running coLinux and start than VPC2007 parallel? Or runs you one VM in other VM? Is the driver coLinux installed right and running? Please check it with "colinux-daemon --status-driver". Can you run colinux-daemon from in the Windows Debugger? ( I don't know how, please ask Google ) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1959846&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-04-29 21:50:50
|
Bugs item #2760666, was opened at 2009-04-14 04:50 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crash / BSOD Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) >Summary: VirtualBOX causes BSOD STOP: 0x0000007F 0x00000008 Initial Comment: Running Parallels or VMWare to virtualise a virtual machine doesnt result in crashing. Trying to boot Windows XP on VirtualBOX at the same time as running COLinux causes it to BSOD the host system (Windows Vista) Its strange but why does VBox BSOD the system whereas Parallels/VMWare can virtualise fine alongside COLinux.. Reproduction: Install VirtualBox Install COLinux V8 Run COLinux Create a new Windows VM In Virtualbox Attempt to Boot the new VM Into Windows setup. BSOD ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-04-29 23:50 Message: coLinux Bug #1959846 seems me the same problem. With a very good crash dump report. Virtual PC 2007 is running there at same time under Vista. https://sourceforge.net/tracker/?func=detail&aid=1959846&group_id=98788&atid=622063 ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-04-29 13:01 Message: I have a similar problem with Windows XP host. (32-bit) Minidumps are not getting generated. Even if PAE/NX/DEP technologies are turned off completely. Nobody: please use some nickname so we could identify you. Nobody: please specify VirtualBox version, and if you use VT-x or not (Hardware Virtualization) For me, the crash happens only with Hardware Virtualization enabled. -Technologov ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-04-29 12:47 Message: Here is the original bug report: Host crash: vboxdrv crashes, when run in VMX mode, together with coLinux http://www.virtualbox.org/ticket/3724 -Technologov ---------------------------------------------------------------------- Comment By: Juergen (juergen_01) Date: 2009-04-29 08:57 Message: Some time ago, a had the same problem with randomly getting a kernel stack overflow. The problem was caused by too many enabled network services on a network interface. I had installed VirtualBox, MS Virtual PC, Norton Internet Security, Cisco VPN Client and MS Network Monitor. All these programs installed a network service. After I disabled 2 or 3 of the network services I was not using at that time, I solved the problem with the kernel stack overflow. You have to disable the services it on every network interface. Well, a BSOD can also be caused by the virtualization features of the CPU. If I am running a VM in VBox with Intel-VT enabled and then starting only the Virtual PC application, my computer is crashing with a BSOD. On an older CPU with no Intel-VT I never had this problem. On this older CPU, I never had any problems with running VBox VMs and colinux instances concurrently. If you do not get a crash dump, this might be caused by the Data-Execution-Prevention in Windows. If this is also enabled for normal applications and not only for windows services, then you will never get a crash dump. Windows is still writing crash dump information to pagefile.sys but it does not generate a crash dump file on next startup. I had the same problem while getting the kernel stack overflow. After disabling DEP for every application Windows created crash dump files again. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-29 03:21 Message: Double fault A double fault occurs when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially, however there are several exceptions that cannot be handled serially and in this situation the processor signals a double fault. The two primary causes for this are hardware and kernel stack overflows. Hardware problems are usually related to CPU, RAM, or bus. Kernel stack overflows are almost always caused by faulty kernel-mode drivers. I can rule out my CPU/RAM since they are relatively new components.. VMWare/Parallels work alongside COLinux just not VirtualBox. I've stress tested this thing for over 72 hours about 2 weeks back since I installed a new CPU cooler.. So I'm guessing its the Kernel Stack Overflow? Any chance you can attempt to reproduce? My Vista is being a pain, its set to do a full mem dump on BSOD but that crash doesnt generate one. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-28 23:49 Message: > STOP: 0x0000007F (0x00000008, 0x801B1000, 0x00000000, 0x00000000) STOP 0x0000007F : UNEXPECTED_KERNEL_MODE_TRAP (sse [1]) 0x00000008 : Double Fault 0x801B1000 : I found no references for that value. [1] http://support.microsoft.com/kb/137539 ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-28 18:04 Message: The system doesnt generate a Minidump from this crash even though configured to. Error is as follows: STOP: 0x0000007F (0x00000008, 0x801B1000, 0x00000000, 0x00000000) With no further details ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-14 19:57 Message: It would be nice to get an analyze from minidump of that BSOD, so we can see, what caused this crash. Please read "Howto use Windows crash dump" in your colinux file "debugging.txt" or here from source: http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging Henry ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-04-29 21:17:00
|
Support Requests item #2783377, was opened at 2009-04-29 05:58 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622064&aid=2783377&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None >Group: None >Status: Deleted Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) >Summary: Grom (spam) Initial Comment: Very good resourse : [url=http://vivat.isuisse.com/www.jackbutterfield.com.html]www.jackbutterfield.com[/url] [url=http://bolika.isuisse.com/imbackoffice.com.html]imbackoffice.com[/url] <a href=http://lione.ibelgique.com/dixieechoes.com.html>dixieechoes.com</a> http://teyri.isuisse.com/www.mypartywishes.com.html Thanks! ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-04-29 23:16 Message: URLs are faked virus infections ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622064&aid=2783377&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-04-29 21:09:34
|
Feature Requests item #2783376, was opened at 2009-04-29 05:53 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2783376&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: None Group: None >Status: Deleted Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) >Summary: Grom (spam) Initial Comment: Very good resourse : [url=http://damgo.isuisse.com/wibw.com.html]wibw.com[/url] <a href=http://kiozy.isuisse.com/mrdavers.com.html>mrdavers.com</a> <a href=http://makire.isuisse.com/www.mda.state.mn.us.nh3.htm.html>www.mda.state.mn.us.nh3.htm</a> http://diolia.isuisse.com/blackwhitepleasures.com.html http://lirofen.iquebec.com/januarysacademyofdance.com.html Thanks! ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-04-29 23:09 Message: URLs are faked Virus-infections ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2783376&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-04-29 11:01:35
|
Bugs item #2760666, was opened at 2009-04-14 05:50 Message generated for change (Comment added) made by technologov You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crash / BSOD Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: VirtualBOX causes BSOD Initial Comment: Running Parallels or VMWare to virtualise a virtual machine doesnt result in crashing. Trying to boot Windows XP on VirtualBOX at the same time as running COLinux causes it to BSOD the host system (Windows Vista) Its strange but why does VBox BSOD the system whereas Parallels/VMWare can virtualise fine alongside COLinux.. Reproduction: Install VirtualBox Install COLinux V8 Run COLinux Create a new Windows VM In Virtualbox Attempt to Boot the new VM Into Windows setup. BSOD ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-04-29 14:01 Message: I have a similar problem with Windows XP host. (32-bit) Minidumps are not getting generated. Even if PAE/NX/DEP technologies are turned off completely. Nobody: please use some nickname so we could identify you. Nobody: please specify VirtualBox version, and if you use VT-x or not (Hardware Virtualization) For me, the crash happens only with Hardware Virtualization enabled. -Technologov ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-04-29 13:47 Message: Here is the original bug report: Host crash: vboxdrv crashes, when run in VMX mode, together with coLinux http://www.virtualbox.org/ticket/3724 -Technologov ---------------------------------------------------------------------- Comment By: Juergen (juergen_01) Date: 2009-04-29 09:57 Message: Some time ago, a had the same problem with randomly getting a kernel stack overflow. The problem was caused by too many enabled network services on a network interface. I had installed VirtualBox, MS Virtual PC, Norton Internet Security, Cisco VPN Client and MS Network Monitor. All these programs installed a network service. After I disabled 2 or 3 of the network services I was not using at that time, I solved the problem with the kernel stack overflow. You have to disable the services it on every network interface. Well, a BSOD can also be caused by the virtualization features of the CPU. If I am running a VM in VBox with Intel-VT enabled and then starting only the Virtual PC application, my computer is crashing with a BSOD. On an older CPU with no Intel-VT I never had this problem. On this older CPU, I never had any problems with running VBox VMs and colinux instances concurrently. If you do not get a crash dump, this might be caused by the Data-Execution-Prevention in Windows. If this is also enabled for normal applications and not only for windows services, then you will never get a crash dump. Windows is still writing crash dump information to pagefile.sys but it does not generate a crash dump file on next startup. I had the same problem while getting the kernel stack overflow. After disabling DEP for every application Windows created crash dump files again. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-29 04:21 Message: Double fault A double fault occurs when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially, however there are several exceptions that cannot be handled serially and in this situation the processor signals a double fault. The two primary causes for this are hardware and kernel stack overflows. Hardware problems are usually related to CPU, RAM, or bus. Kernel stack overflows are almost always caused by faulty kernel-mode drivers. I can rule out my CPU/RAM since they are relatively new components.. VMWare/Parallels work alongside COLinux just not VirtualBox. I've stress tested this thing for over 72 hours about 2 weeks back since I installed a new CPU cooler.. So I'm guessing its the Kernel Stack Overflow? Any chance you can attempt to reproduce? My Vista is being a pain, its set to do a full mem dump on BSOD but that crash doesnt generate one. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-29 00:49 Message: > STOP: 0x0000007F (0x00000008, 0x801B1000, 0x00000000, 0x00000000) STOP 0x0000007F : UNEXPECTED_KERNEL_MODE_TRAP (sse [1]) 0x00000008 : Double Fault 0x801B1000 : I found no references for that value. [1] http://support.microsoft.com/kb/137539 ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-28 19:04 Message: The system doesnt generate a Minidump from this crash even though configured to. Error is as follows: STOP: 0x0000007F (0x00000008, 0x801B1000, 0x00000000, 0x00000000) With no further details ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-14 20:57 Message: It would be nice to get an analyze from minidump of that BSOD, so we can see, what caused this crash. Please read "Howto use Windows crash dump" in your colinux file "debugging.txt" or here from source: http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging Henry ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 |
|
From: Alexey E. <al...@gm...> - 2009-04-29 10:54:01
|
BTW: This coLinux bug looks exactly like my problem: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 -- -Alexey Eromenko "Technologov" |
|
From: SourceForge.net <no...@so...> - 2009-04-29 10:47:10
|
Bugs item #2760666, was opened at 2009-04-14 05:50 Message generated for change (Comment added) made by technologov You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crash / BSOD Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: VirtualBOX causes BSOD Initial Comment: Running Parallels or VMWare to virtualise a virtual machine doesnt result in crashing. Trying to boot Windows XP on VirtualBOX at the same time as running COLinux causes it to BSOD the host system (Windows Vista) Its strange but why does VBox BSOD the system whereas Parallels/VMWare can virtualise fine alongside COLinux.. Reproduction: Install VirtualBox Install COLinux V8 Run COLinux Create a new Windows VM In Virtualbox Attempt to Boot the new VM Into Windows setup. BSOD ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2009-04-29 13:47 Message: Here is the original bug report: Host crash: vboxdrv crashes, when run in VMX mode, together with coLinux http://www.virtualbox.org/ticket/3724 -Technologov ---------------------------------------------------------------------- Comment By: Juergen (juergen_01) Date: 2009-04-29 09:57 Message: Some time ago, a had the same problem with randomly getting a kernel stack overflow. The problem was caused by too many enabled network services on a network interface. I had installed VirtualBox, MS Virtual PC, Norton Internet Security, Cisco VPN Client and MS Network Monitor. All these programs installed a network service. After I disabled 2 or 3 of the network services I was not using at that time, I solved the problem with the kernel stack overflow. You have to disable the services it on every network interface. Well, a BSOD can also be caused by the virtualization features of the CPU. If I am running a VM in VBox with Intel-VT enabled and then starting only the Virtual PC application, my computer is crashing with a BSOD. On an older CPU with no Intel-VT I never had this problem. On this older CPU, I never had any problems with running VBox VMs and colinux instances concurrently. If you do not get a crash dump, this might be caused by the Data-Execution-Prevention in Windows. If this is also enabled for normal applications and not only for windows services, then you will never get a crash dump. Windows is still writing crash dump information to pagefile.sys but it does not generate a crash dump file on next startup. I had the same problem while getting the kernel stack overflow. After disabling DEP for every application Windows created crash dump files again. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-29 04:21 Message: Double fault A double fault occurs when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially, however there are several exceptions that cannot be handled serially and in this situation the processor signals a double fault. The two primary causes for this are hardware and kernel stack overflows. Hardware problems are usually related to CPU, RAM, or bus. Kernel stack overflows are almost always caused by faulty kernel-mode drivers. I can rule out my CPU/RAM since they are relatively new components.. VMWare/Parallels work alongside COLinux just not VirtualBox. I've stress tested this thing for over 72 hours about 2 weeks back since I installed a new CPU cooler.. So I'm guessing its the Kernel Stack Overflow? Any chance you can attempt to reproduce? My Vista is being a pain, its set to do a full mem dump on BSOD but that crash doesnt generate one. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-29 00:49 Message: > STOP: 0x0000007F (0x00000008, 0x801B1000, 0x00000000, 0x00000000) STOP 0x0000007F : UNEXPECTED_KERNEL_MODE_TRAP (sse [1]) 0x00000008 : Double Fault 0x801B1000 : I found no references for that value. [1] http://support.microsoft.com/kb/137539 ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-28 19:04 Message: The system doesnt generate a Minidump from this crash even though configured to. Error is as follows: STOP: 0x0000007F (0x00000008, 0x801B1000, 0x00000000, 0x00000000) With no further details ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-04-14 20:57 Message: It would be nice to get an analyze from minidump of that BSOD, so we can see, what caused this crash. Please read "Howto use Windows crash dump" in your colinux file "debugging.txt" or here from source: http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging Henry ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2760666&group_id=98788 |
81 messages has been excluded from this view by a project administrator.
