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: SourceForge.net <no...@so...> - 2008-06-27 20:39:22
|
Bugs item #1995862, was opened at 2008-06-17 11:33 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1995862&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: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Mike Frysinger (vapier) Assigned to: Nobody/Anonymous (nobody) Summary: udp forwarded packets over slirp have incorrect source ip Initial Comment: after upgrading from coLinux 0.7.1 to 0.7.3, my TFTP connection failed. the coLinux setup is: eth0=slirp,,tcp:22:22/tcp:333:22/tcp:10000:10000/udp:69:69 connecting from an external machine (named "G5") to the windows machine which forwards port 69 (tftp) to the colinux system which is running a tftp server running tcpdump against 0.7.1 shows: 01:34:47.410000 IP G5.60808 > 10.0.2.15.tftp: 15 RRQ "moo" netascii running tcpdump against 0.7.3 shows: 01:44:45.645802 IP 10.0.2.2.33431 > 10.0.2.15.tftp: 15 RRQ "moo" netascii for some reason the forwarded packet had the source IP changed from the real external machine (G5) to the windows' side of the slirp tunnel (10.0.2.2). this means the tftp server then attempts to reply to "10.0.2.2" instead of "G5" and things obviously fail. merely replacing 'colinux-slirp-net-daemon.exe' in 0.7.3 with the version from 0.7.1 allows things to work as expected under 0.7.3 tcp forwarded packets work with both versions though, so it seems like a udp-specific issue ? ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2008-06-27 22:39 Message: Logged In: YES user_id=579204 Originator: NO Some lines in source was missing to change between SVN revisions 479 and 480, you have mailed me. Many thanks for your details. Bug has been fixed in SVN revision 1060 (stable) and 1061 (devel) now. An update colinux-slirp-net-daemon-0.7.3-2.zip is available from SF file releases: http://downloads.sourceforge.net/colinux/coLinux-0.7.2-src.tar.gz?download ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1995862&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2008-06-17 09:33:24
|
Bugs item #1995862, was opened at 2008-06-17 05:33 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1995862&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: Open Resolution: None Priority: 5 Private: No Submitted By: Mike Frysinger (vapier) Assigned to: Nobody/Anonymous (nobody) Summary: udp forwarded packets over slirp have incorrect source ip Initial Comment: after upgrading from coLinux 0.7.1 to 0.7.3, my TFTP connection failed. the coLinux setup is: eth0=slirp,,tcp:22:22/tcp:333:22/tcp:10000:10000/udp:69:69 connecting from an external machine (named "G5") to the windows machine which forwards port 69 (tftp) to the colinux system which is running a tftp server running tcpdump against 0.7.1 shows: 01:34:47.410000 IP G5.60808 > 10.0.2.15.tftp: 15 RRQ "moo" netascii running tcpdump against 0.7.3 shows: 01:44:45.645802 IP 10.0.2.2.33431 > 10.0.2.15.tftp: 15 RRQ "moo" netascii for some reason the forwarded packet had the source IP changed from the real external machine (G5) to the windows' side of the slirp tunnel (10.0.2.2). this means the tftp server then attempts to reply to "10.0.2.2" instead of "G5" and things obviously fail. merely replacing 'colinux-slirp-net-daemon.exe' in 0.7.3 with the version from 0.7.1 allows things to work as expected under 0.7.3 tcp forwarded packets work with both versions though, so it seems like a udp-specific issue ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1995862&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2008-06-11 20:53:13
|
Bugs item #1991232, was opened at 2008-06-11 22:04 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1991232&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: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: slirp appears to be I/O bound Initial Comment: The SLIRP network interface is I/O bound. In other words, the speed of the hard disk where Colinux is installed limits the speed that it can send network data. I'm really not sure if this is a bug in colinux-daemon.exe, colinux-slirp-net-daemon.exe, the host OS, or some combination. Detailed information: My host OS is Windows XP Professional SP2. I was running Colinux from a slow USB 1.0 external hard disk. I was running a graphically intensive X client in Colinux, connecting via SLIRP to an Xming server running on the same physical machine under the host OS. The UI was running very slowly, but Task Manager was registering almost no CPU utilization (I have a 1.8 GHz Pentium 4). However, the I/O {Read,Write} Bytes columns in Task Manager indicated that colinux-slirp-net-daemon.exe was reading and writing massive amounts of data -- at about the speed of my hard disk. To confirm my suspicions, I moved the colinux .exe files to the (much faster) internal hard disk and the UI lag went away. My Colinux disk image is still on the slow USB 1.0 hard disk; I only moved the Colinux binaries. (This rules out the possibility that my X client was somehow I/O bound.) Moving the colinux .exe files to a faster disk is a workaround that is feasible on my machine and gives acceptable performance for my application, but in general there is no good reason for the SLIRP network bandwidth to be limited by hard disk I/O bandwidth, so I'm filing this as a bug. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2008-06-11 22:53 Message: Logged In: YES user_id=579204 Originator: NO Please referer the used coLinux version. In version 0.8.0 have performance improvements, you can enable "setcobd=async" to split disk i/o from all other task. Without async (the default is sync) all I/O operations are delayed as long the disk block is not written/read on host side. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1991232&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2008-06-11 20:04:03
|
Bugs item #1991232, was opened at 2008-06-11 13:04 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1991232&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: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: slirp appears to be I/O bound Initial Comment: The SLIRP network interface is I/O bound. In other words, the speed of the hard disk where Colinux is installed limits the speed that it can send network data. I'm really not sure if this is a bug in colinux-daemon.exe, colinux-slirp-net-daemon.exe, the host OS, or some combination. Detailed information: My host OS is Windows XP Professional SP2. I was running Colinux from a slow USB 1.0 external hard disk. I was running a graphically intensive X client in Colinux, connecting via SLIRP to an Xming server running on the same physical machine under the host OS. The UI was running very slowly, but Task Manager was registering almost no CPU utilization (I have a 1.8 GHz Pentium 4). However, the I/O {Read,Write} Bytes columns in Task Manager indicated that colinux-slirp-net-daemon.exe was reading and writing massive amounts of data -- at about the speed of my hard disk. To confirm my suspicions, I moved the colinux .exe files to the (much faster) internal hard disk and the UI lag went away. My Colinux disk image is still on the slow USB 1.0 hard disk; I only moved the Colinux binaries. (This rules out the possibility that my X client was somehow I/O bound.) Moving the colinux .exe files to a faster disk is a workaround that is feasible on my machine and gives acceptable performance for my application, but in general there is no good reason for the SLIRP network bandwidth to be limited by hard disk I/O bandwidth, so I'm filing this as a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1991232&group_id=98788 |
|
From: Henry N. <Hen...@Ar...> - 2008-06-08 10:00:00
|
Cooperative Linux version 0.7.3 released now. This is an upgrade with new kernel 2.6.22.18 and lots of fixed bugs. There are no changes between 0.7.3-rc5 and this release version. We released the binary from builddate 24-May-2008. Users of this snapshot don't need an update. Download: http://sourceforge.net/projects/colinux/files Notes: http://sourceforge.net/project/shownotes.php?release_id=385643&group_id=98788 Changelog: http://www.colinux.org/snapshots/stable-ChangeLog Wiki: http://colinux.wikia.com/ NEWS of Version 0.7.3 Bugfixes: * Check ELF header before accessing kernel vmlinux (fix exception). * Fix problems with memory hole from shared video cards and the error message "PFN to high". * Bugfix host freeze after "Using IPI Shortcut mode" and other randomly crashes at mounting the root file system with types ext2 or ext3. Daemon: * Add build date to exe file properties. * View build timestamp of ntkernel driver with --status-driver. * Bug #1861876: Random created MAC stored in Registry to have same on every start. [HKCU\Software\coLinux] * Bugfix: Image files >=4GB fails with size error on parameter "-v 3". * Workarround for unresponsive key inputs on Vista flooded nt-console. Linux driver will sleep now, if message queues have to many entries and user task is busy. Network daemons drivers changed also into this mode. * Incrase NT console screen to most as can without scrollbars at startup. Kernel: * Kernel has been updated to 2.6.22.18 * Kernel config added: More Netfilters (NF_NAT and more), Network Security Marking, RAID and LVM as module (MD), extended attributes for ext2/ext3/reiser/jfs/xfs, Quota, Kernel automounter support, eCrypt filesystem, and more... * Removed: KALLSYMS_ALL (Debugging symbols) * SELINUX support. To enable, set selinux=1 in colinux.conf * Fix for splice local root exploit is included, details on http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.22.18 * Feature Requests #1421120: Fixup "vim fsync" error on cofs. * Bugfix get_size for double opened block devices. * Fix BSOD on "stty rows N" where n>25. Disable resize. (Paolo Minazzi) * Bugfix: CR3 wrong converted for register dumps inside page fault handler. Installer: * Update image ArchLinux-2007.08-2 * Text '* Notes' sometimes was only shown as '*', adjust field sizes * Feature Requests #1898468: expose install folder as variable %COLINUX% Buildsystem: * New option --errfile use different file for stdout and stderr. -- Henry N. |
|
From: Henry N. <Hen...@Ar...> - 2008-05-27 23:47:07
|
Oliver Metz wrote: > Hi Henry, > I tried to run your "benchmark". Why do I get better results with sync mode? Did I miss something? > > Greets Oliver > > settings.txt: > cobd0=Drives\base.drv > cobd1=Drives\swap.drv > cobd2=Drives\home.drv > > # /usr/bin/time --format='real %e\nuser %U\nsys %S\nIO %w\n' -- dd if=/dev/zero of=/tmp/foo bs=200M count=1 > 1+0 records in > 1+0 records out > 209715200 bytes (210 MB) copied, 4.78007 seconds, 43.9 MB/s > real 4.78 > user 0.00 > sys 3.03 > IO 1 > # /usr/bin/time --format='real %e\nuser %U\nsys %S\nIO %w\n' -- dd if=/dev/zero of=/tmp/foo bs=200M count=1 > 1+0 records in > 1+0 records out > 209715200 bytes (210 MB) copied, 9.11014 seconds, 23.0 MB/s > real 9.12 > user 0.01 > sys 1.99 > IO 1549 > # uname -a > Linux andLinux 2.6.22.18-co-0.8.0 #1 PREEMPT Sun May 11 22:48:31 UTC 2008 i686 GNU/Linux Because the dd on sync mode has only one Operating System switch (Linux-windows and back, you can see "IO 1"). On async mode you have 1549 OS switches. The difference is, that all task are blocked 4.78 seconds in sync mode. In the async mode other tasks can run, for the time the blocks will be written on Windows side. The system is more usable in the time, and this adds time. Additionalny a liddle overhead is for an extra OS switch at end of every block. Async makes the complete system more smovly, but I/O is not faster ready. Your Linux can do other things, in the I/O-waiting time. See, that the "sys" time is smaller as in sync mode. Watch the cpu load via "top" at the async test. Cpu is idle more. ;-) -- Henry N. |
|
From: Oliver M. <Oli...@fs...> - 2008-05-27 23:10:00
|
Hi Henry, I tried to run your "benchmark". Why do I get better results with sync mode? Did I miss something? Greets Oliver settings.txt: cobd0=Drives\base.drv cobd1=Drives\swap.drv cobd2=Drives\home.drv # /usr/bin/time --format='real %e\nuser %U\nsys %S\nIO %w\n' -- dd if=/dev/zero of=/tmp/foo bs=200M count=1 1+0 records in 1+0 records out 209715200 bytes (210 MB) copied, 4.78007 seconds, 43.9 MB/s real 4.78 user 0.00 sys 3.03 IO 1 # /usr/bin/time --format='real %e\nuser %U\nsys %S\nIO %w\n' -- dd if=/dev/zero of=/tmp/foo bs=200M count=1 1+0 records in 1+0 records out 209715200 bytes (210 MB) copied, 9.11014 seconds, 23.0 MB/s real 9.12 user 0.01 sys 1.99 IO 1549 # uname -a Linux andLinux 2.6.22.18-co-0.8.0 #1 PREEMPT Sun May 11 22:48:31 UTC 2008 i686 GNU/Linux |
|
From: coLinux a. <col...@he...> - 2008-05-24 04:12:26
|
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-20080523/ colinux-0.8.0-20080523.src.tgz (692610 Bytes) daemons-0.8.0-20080523.dbg.zip (1353267 Bytes) daemons-0.8.0-20080523.zip (1051223 Bytes) modules-2.6.22.18-co-0.8.0-20080523.tgz (2600461 Bytes) vmlinux-2.6.22.18-co-0.8.0-20080523.zip (1762331 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-*-20080523.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 ------------------------------------------------------------------------ r1053 | henryn | 2008-05-23 23:22:51 +0000 (Fri, 23 May 2008) | 1 line Changed paths: M /branches/devel/src/colinux/os/winnt/user/console-nt/widget.cpp * ntconsole: Fixup failed SetConsoleWindowInfo from small start window. ------------------------------------------------------------------------ r1052 | henryn | 2008-05-23 23:07:20 +0000 (Fri, 23 May 2008) | 1 line Changed paths: M /branches/devel/patch/base-2.6.22.diff * CR3 wrong converted for register dumps inside page fault handler. ------------------------------------------------------------------------ |
|
From: SourceForge.net <no...@so...> - 2008-05-23 21:25:02
|
Bugs item #1970018, was opened at 2008-05-23 02:05 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1970018&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: Interface (example) >Group: v0.7.x (release) >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Cannot choose TAP devices manually Initial Comment: Hi, When I set my TAP devices (of which i have 3) inside my config file, colinux-deamon just tries to open the first one it finds for three times, and it fails for the second and thirth time since the device is already opened. Now, I'm positive I haven't mispelled the names and that the devices actually exist, since everything works when using colinux-net-deamon manually after I start colinux-deamon. More about this strange error: I'm pretty sure that colinux-daemon actually reads these lines containing my TAP devices because when I mispell tuntap (for lets say tap), colinux-daemon gives me an error. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2008-05-23 23:24 Message: Logged In: YES user_id=579204 Originator: NO Ah, thanks. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-05-23 20:09 Message: Logged In: NO It isn't a bug after all, my mistake. The problem arises when you use a whitespace character (e.g. eth0=tuntap, "...") ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-05-23 02:07 Message: Logged In: NO I forgot to mention, I'm using coLinux-0.7.2 on WinXP, and my email is del...@ho... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1970018&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2008-05-23 18:09:55
|
Bugs item #1970018, was opened at 2008-05-22 17:05 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1970018&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: Interface (example) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Cannot choose TAP devices manually Initial Comment: Hi, When I set my TAP devices (of which i have 3) inside my config file, colinux-deamon just tries to open the first one it finds for three times, and it fails for the second and thirth time since the device is already opened. Now, I'm positive I haven't mispelled the names and that the devices actually exist, since everything works when using colinux-net-deamon manually after I start colinux-deamon. More about this strange error: I'm pretty sure that colinux-daemon actually reads these lines containing my TAP devices because when I mispell tuntap (for lets say tap), colinux-daemon gives me an error. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-05-23 11:09 Message: Logged In: NO It isn't a bug after all, my mistake. The problem arises when you use a whitespace character (e.g. eth0=tuntap, "...") ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-05-22 17:07 Message: Logged In: NO I forgot to mention, I'm using coLinux-0.7.2 on WinXP, and my email is del...@ho... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1970018&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2008-05-23 00:07:08
|
Bugs item #1970018, was opened at 2008-05-22 17:05 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1970018&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: Interface (example) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Cannot choose TAP devices manually Initial Comment: Hi, When I set my TAP devices (of which i have 3) inside my config file, colinux-deamon just tries to open the first one it finds for three times, and it fails for the second and thirth time since the device is already opened. Now, I'm positive I haven't mispelled the names and that the devices actually exist, since everything works when using colinux-net-deamon manually after I start colinux-deamon. More about this strange error: I'm pretty sure that colinux-daemon actually reads these lines containing my TAP devices because when I mispell tuntap (for lets say tap), colinux-daemon gives me an error. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-05-22 17:07 Message: Logged In: NO I forgot to mention, I'm using coLinux-0.7.2 on WinXP, and my email is del...@ho... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1970018&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2008-05-23 00:05:53
|
Bugs item #1970018, was opened at 2008-05-22 17:05 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1970018&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: Interface (example) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Cannot choose TAP devices manually Initial Comment: Hi, When I set my TAP devices (of which i have 3) inside my config file, colinux-deamon just tries to open the first one it finds for three times, and it fails for the second and thirth time since the device is already opened. Now, I'm positive I haven't mispelled the names and that the devices actually exist, since everything works when using colinux-net-deamon manually after I start colinux-deamon. More about this strange error: I'm pretty sure that colinux-daemon actually reads these lines containing my TAP devices because when I mispell tuntap (for lets say tap), colinux-daemon gives me an error. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1970018&group_id=98788 |
|
From: Kasprzyk, N. <NKa...@im...> - 2008-05-21 11:48:39
|
Hello Henry.
Thanks for your quick answer. I needed some more time and did tests with
and without the proposed "lpj" kernel parameter.
The results:
lpj=3000000
===========
Cooperative Linux Daemon, 0.8.0
Daemon compiled on Sun May 11 22:49:57 2008
PID: 1636
colinux: booting
Linux version 2.6.22.18-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE
Linux)) #1
PREEMPT Sun May 11 22:48:31 UTC 2008
128MB LOWMEM available.
initrd enabled: start: 0xc7f9a000 size: 0x00065881
Entering add_active_range(0, 0, 32768) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 0
Normal 0 -> 32768
early_node_map[1] active PFN ranges
0: 0 -> 32768
On node 0 totalpages: 32768
DMA zone: 0 pages used for memmap
Normal zone: 256 pages used for memmap
Normal zone: 32512 pages, LIFO batch:7
Built 1 zonelists. Total pages: 32512
Kernel command line: root=/dev/hda1 lpj=3000000
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Setting proxy interrupt vectors
PID hash table entries: 512 (order: 9, 2048 bytes)
Console: colour CoCON 80x25
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
conet-slirp-daemon: running
Memory: 125268k/131072k available (2058k kernel code, 0k reserved, 585k
data, 14
0k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xffffc000 - 0xfffff000 ( 12 kB)
vmalloc : 0xc8800000 - 0xffffa000 ( 887 MB)
lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
.init : 0xc0398000 - 0xc03bb000 ( 140 kB)
.data : 0xc0302ac8 - 0xc03951e4 ( 585 kB)
.text : 0xc0100000 - 0xc0302ac8 (2058 kB)
Calibrating delay loop (skipped)... 600.00 BogoMIPS preset
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
colinux: Linux VM terminated
colinux: BUG at
...412.svn/linux-2.6.22.18-source/kernel/posix-cpu-timers.c:1295
lpj=1000
========
Slows down the Virtual PC in a way that you believe that the Virtual PC
does not work anymore. The VirtualPC process takes 100% of the
performance of one of my processors. Fortunately, I have two of them. ;)
The last line in the concole is:
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
lpj=5000000
===========
Same behavior as with lpj=1000.
Lpj=3000000 again
=================
Now, it stops at line
.text : 0xc0100000 - 0xc0302ac8 (2058 kB)
Without lpj
===========
I tried one CoLinux version from 05/11/2008. That is the trace:
colinux: booting
Linux version 2.6.22.18-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE
Linux)) #1
PREEMPT Sun May 11 22:48:31 UTC 2008
128MB LOWMEM available.
initrd enabled: start: 0xc7f9a000 size: 0x00065881
Entering add_active_range(0, 0, 32768) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 0
Normal 0 -> 32768
early_node_map[1] active PFN ranges
0: 0 -> 32768
On node 0 totalpages: 32768
DMA zone: 0 pages used for memmap
Normal zone: 256 pages used for memmap
Normal zone: 32512 pages, LIFO batch:7
Built 1 zonelists. Total pages: 32512
Kernel command line: root=/dev/hda1
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Setting proxy interrupt vectors
PID hash table entries: 512 (order: 9, 2048 bytes)
Console: colour CoCON 80x25
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 125268k/131072k available (2058k kernel code, 0k reserved, 585k
data, 14
0k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xffffc000 - 0xfffff000 ( 12 kB)
vmalloc : 0xc8800000 - 0xffffa000 ( 887 MB)
lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
.init : 0xc0398000 - 0xc03bb000 ( 140 kB)
.data : 0xc0302ac8 - 0xc03951e4 ( 585 kB)
.text : 0xc0100000 - 0xc0302ac8 (2058 kB)
WARNING: at
/home/hn/colinux/build/devel-gcc412.svn/linux-2.6.22.18-source/kerne
l/softirq.c:122 _local_bh_enable()
[<c0103b7a>] show_trace_log_lvl+0x1a/0x30
[<c0103cb2>] show_trace+0x12/0x20
[<c0104ae5>] dump_stack+0x15/0x20
[<c0115e7a>] _local_bh_enable+0x9a/0xb0
[<c0115f1a>] __do_softirq+0x8a/0xa0
[<c0115f65>] do_softirq+0x35/0x40
[<c01161d3>] irq_exit+0x43/0x50
[<c013d174>] co_callback+0x174/0x380
[<c010a5a1>] proxy_interrupt_handler+0x51/0x70
[<c0103873>] common_interrupt+0x23/0x30
[<c010a4df>] co_register_timer+0xf/0x20
[<c0398b60>] start_kernel+0x1c0/0x2b0
[<00000000>] _stext+0x3fefff50/0x20
[<c010a1de>] co_start_arch+0xfe/0x170
[<c0109ec5>] co_arch_start_kernel+0x0/0xb
=======================
Calibrating delay loop... colinux: Linux VM terminated
colinux: BUG at
...412.svn/linux-2.6.22.18-source/kernel/posix-cpu-timers.c:1295
conet-slirp-daemon: monitor open failed
conet-slirp-daemon: exitcode 8a66b801
At the end of every of the "lpj" tests I had to restart VirtualPC
because it hangs.
Do you have another proposal?
Nico
> -----Original Message-----
> From: Henry Nestler [mailto:Hen...@Ar...]
> Sent: Tuesday, May 20, 2008 2:16 AM
> To: Kasprzyk, Nico
> Cc: col...@li...
> Subject: Re: [coLinux-devel] CoLinux and Virtual PC
>
> Kasprzyk, Nico wrote:
> > Some days before, I tried to run CoLinux 0.8.0 in one
> Virtual PC Windows
> > XP session. Short summary: It did not work. It is not
> possible for me to
> > judge whether CoLinux may be corrected to run in Virtual PC
> or if this
> > is one real serious problem.
> >
> > Thus, i ask the list: Do you think that it will be possible to run
> > CoLinux with Virtual PC?
> >
> >
> > Best regards,
> >
> > Nico
> >
> >
> > An older version did not run with error:
> > ========================================
> >
> > Cooperative Linux Daemon, 0.8.0
> > Daemon compiled on Sun Jan 20 19:01:26 2008
> >
> > PID: 2316
> > colinux: booting
> > Linux version 2.6.22-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE
> > Linux)) #1 PRE
> > EMPT Sun Jan 20 18:59:42 CET 2008
> > 128MB LOWMEM available.
> > initrd enabled: start: 0xc7f9a000 size: 0x00065881
> > [...]
> > Calibrating delay loop... WARNING: at
> >
> /home/hn/colinux/build/devel-gcc412/linux-2.6.22-source/kernel
> /softirq.c:122 _local_bh_enable()
>
> This ia a line with:
> WARN_ON_ONCE(!irqs_disabled());
>
> > [<c0103b7a>] show_trace_log_lvl+0x1a/0x30
> > [<c0103cb2>] show_trace+0x12/0x20
> > [<c0104ae5>] dump_stack+0x15/0x20
> > [<c0115cfa>] _local_bh_enable+0x9a/0xb0
> > [<c0115d9a>] __do_softirq+0x8a/0xa0
> > [<c0115de5>] do_softirq+0x35/0x40
> > [<c0116053>] irq_exit+0x43/0x50
> > [<c013d154>] co_callback+0x164/0x2f0
> > [<c010a681>] proxy_interrupt_handler+0x41/0x50
> > [<c0103873>] common_interrupt+0x23/0x30
> > [<c0396b65>] start_kernel+0x1c5/0x2b0
> > [<00000000>] _stext+0x3fefff50/0x20
> > [<c010a30e>] co_start_arch+0xfe/0x170
> > [<c0109e95>] co_arch_start_kernel+0x0/0xb
> > =======================
> > colinux: Linux VM terminated
> > colinux: BUG at
> > ...vel-gcc412/linux-2.6.22-source/kernel/posix-cpu-timers.c:1295
>
> This is the line
> BUG_ON(!irqs_disabled());
>
> Think, we can fix it. Our timer callback leaks somethere with enabled
> interrupts. I'm afraid.
>
> As workarround set loops_per_jiffy manualy as kernelparameter and skip
> the calibration: "lpj=3000000" (see kernel source
> Documentation/kernel-parameters.txt:910)
>
> We currently have kernel 2.6.22.18 and some changes on the proxy
> interrupt handler. Please give the latest snapshot a try. If that also
> fails, then send please the new stack trace again.
>
> > A newer version stopped working with:
> > =====================================
> >
> > Cooperative Linux Daemon, 0.8.0
> > Daemon compiled on Tue May 13 04:06:17 2008
> >
> > daemon: exit code 83279001
> > daemon: error - CO_RC_ERROR_ERROR, line 484, file
> > src/colinux/user/daemon.c (25)
>
> The driver is not loaded correctly.
> First, please run this and send me your result:
> * cd C:\colinux
> * colinux-daemon --status-driver
>
> To fix it, please do follow steps
> * cd C:\colinux
> * colinux-daemon --remove-driver
> * colinux-daemon --install-driver
> * colinux-daemon --status-driver
>
> If that not helps, then reboot windows between remove and install.
>
> --
> Henry N.
>
|
|
From: coLinux a. <col...@he...> - 2008-05-21 04:12:44
|
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-20080520/ colinux-0.8.0-20080520.src.tgz (692579 Bytes) daemons-0.8.0-20080520.dbg.zip (1353131 Bytes) daemons-0.8.0-20080520.zip (1051149 Bytes) modules-2.6.22.18-co-0.8.0-20080520.tgz (2600458 Bytes) vmlinux-2.6.22.18-co-0.8.0-20080520.zip (1762262 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-*-20080520.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 ------------------------------------------------------------------------ r1051 | henryn | 2008-05-20 21:04:47 +0000 (Tue, 20 May 2008) | 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/patch/coconsole-core.diff M /branches/devel/src/colinux/common/console.c M /branches/devel/src/colinux/common/console.h M /branches/devel/src/colinux/kernel/monitor.c M /branches/devel/src/colinux/os/winnt/user/console-nt/widget.cpp M /branches/devel/src/colinux/user/console-base/console.cpp * Console size defined by two macros in src/colinux/common/console.h now: CO_CONSOLE_WIDTH 80 CO_CONSOLE_HEIGHT 25 After change, rebuild daemons and linux.sys (make clean && make colinux). Remove and install driver linux.sys on host to have new size. * CO_OPERATION_CONSOLE_SIZES: Linux kernel gets size from ntkernel at runtime now, no needs to recompile. Based on patch from Reini Urban 2004-11-07 http://xarch.tu-graz.ac.at/home/rurban/ Ported to coLinux 0.8.x by Henry Nestler ------------------------------------------------------------------------ |
|
From: David H. L. Jr. <dh...@dl...> - 2008-05-20 00:40:44
|
There is a 2 part article article on using colinux for embedded
software development in Circuit Cellar #213 and #214.
Once CC's publish rights expire (about 4 months) I will make it
available to the colinux website.
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dh...@dl... http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
|
|
From: Henry N. <Hen...@Ar...> - 2008-05-20 00:15:16
|
Kasprzyk, Nico wrote:
> Some days before, I tried to run CoLinux 0.8.0 in one Virtual PC Windows
> XP session. Short summary: It did not work. It is not possible for me to
> judge whether CoLinux may be corrected to run in Virtual PC or if this
> is one real serious problem.
>
> Thus, i ask the list: Do you think that it will be possible to run
> CoLinux with Virtual PC?
>
>
> Best regards,
>
> Nico
>
>
> An older version did not run with error:
> ========================================
>
> Cooperative Linux Daemon, 0.8.0
> Daemon compiled on Sun Jan 20 19:01:26 2008
>
> PID: 2316
> colinux: booting
> Linux version 2.6.22-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE
> Linux)) #1 PRE
> EMPT Sun Jan 20 18:59:42 CET 2008
> 128MB LOWMEM available.
> initrd enabled: start: 0xc7f9a000 size: 0x00065881
> [...]
> Calibrating delay loop... WARNING: at
> /home/hn/colinux/build/devel-gcc412/linux-2.6.22-source/kernel/softirq.c:122 _local_bh_enable()
This ia a line with:
WARN_ON_ONCE(!irqs_disabled());
> [<c0103b7a>] show_trace_log_lvl+0x1a/0x30
> [<c0103cb2>] show_trace+0x12/0x20
> [<c0104ae5>] dump_stack+0x15/0x20
> [<c0115cfa>] _local_bh_enable+0x9a/0xb0
> [<c0115d9a>] __do_softirq+0x8a/0xa0
> [<c0115de5>] do_softirq+0x35/0x40
> [<c0116053>] irq_exit+0x43/0x50
> [<c013d154>] co_callback+0x164/0x2f0
> [<c010a681>] proxy_interrupt_handler+0x41/0x50
> [<c0103873>] common_interrupt+0x23/0x30
> [<c0396b65>] start_kernel+0x1c5/0x2b0
> [<00000000>] _stext+0x3fefff50/0x20
> [<c010a30e>] co_start_arch+0xfe/0x170
> [<c0109e95>] co_arch_start_kernel+0x0/0xb
> =======================
> colinux: Linux VM terminated
> colinux: BUG at
> ...vel-gcc412/linux-2.6.22-source/kernel/posix-cpu-timers.c:1295
This is the line
BUG_ON(!irqs_disabled());
Think, we can fix it. Our timer callback leaks somethere with enabled
interrupts. I'm afraid.
As workarround set loops_per_jiffy manualy as kernelparameter and skip
the calibration: "lpj=3000000" (see kernel source
Documentation/kernel-parameters.txt:910)
We currently have kernel 2.6.22.18 and some changes on the proxy
interrupt handler. Please give the latest snapshot a try. If that also
fails, then send please the new stack trace again.
> A newer version stopped working with:
> =====================================
>
> Cooperative Linux Daemon, 0.8.0
> Daemon compiled on Tue May 13 04:06:17 2008
>
> daemon: exit code 83279001
> daemon: error - CO_RC_ERROR_ERROR, line 484, file
> src/colinux/user/daemon.c (25)
The driver is not loaded correctly.
First, please run this and send me your result:
* cd C:\colinux
* colinux-daemon --status-driver
To fix it, please do follow steps
* cd C:\colinux
* colinux-daemon --remove-driver
* colinux-daemon --install-driver
* colinux-daemon --status-driver
If that not helps, then reboot windows between remove and install.
--
Henry N.
|
|
From: Kasprzyk, N. <NKa...@im...> - 2008-05-19 14:58:12
|
Hello.
Some days before, I tried to run CoLinux 0.8.0 in one Virtual PC Windows
XP session. Short summary: It did not work. It is not possible for me to
judge whether CoLinux may be corrected to run in Virtual PC or if this
is one real serious problem.
Thus, i ask the list: Do you think that it will be possible to run
CoLinux with Virtual PC?
Best regards,
Nico
An older version did not run with error:
========================================
Cooperative Linux Daemon, 0.8.0
Daemon compiled on Sun Jan 20 19:01:26 2008
PID: 2316
colinux: booting
Linux version 2.6.22-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE
Linux)) #1 PRE
EMPT Sun Jan 20 18:59:42 CET 2008
128MB LOWMEM available.
initrd enabled: start: 0xc7f9a000 size: 0x00065881
Entering add_active_range(0, 0, 32768) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 0
Normal 0 -> 32768
early_node_map[1] active PFN ranges
0: 0 -> 32768
On node 0 totalpages: 32768
DMA zone: 0 pages used for memmap
Normal zone: 256 pages used for memmap
Normal zone: 32512 pages, LIFO batch:7
Built 1 zonelists. Total pages: 32512
Kernel command line: root=/dev/hda1
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Setting proxy interrupt vectors
PID hash table entries: 512 (order: 9, 2048 bytes)
Console: colour CoCON 80x25
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 125212k/131072k available (2050k kernel code, 0k reserved, 581k
data, 14
0k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xffffc000 - 0xfffff000 ( 12 kB)
vmalloc : 0xc8800000 - 0xffffa000 ( 887 MB)
lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
.init : 0xc0396000 - 0xc03b9000 ( 140 kB)
conet-slirp-daemon: running
.data : 0xc0300b48 - 0xc03921e4 ( 581 kB)
.text : 0xc0100000 - 0xc0300b48 (2050 kB)
Calibrating delay loop... WARNING: at
/home/hn/colinux/build/devel-gcc412/linux-
2.6.22-source/kernel/softirq.c:122 _local_bh_enable()
[<c0103b7a>] show_trace_log_lvl+0x1a/0x30
[<c0103cb2>] show_trace+0x12/0x20
[<c0104ae5>] dump_stack+0x15/0x20
[<c0115cfa>] _local_bh_enable+0x9a/0xb0
[<c0115d9a>] __do_softirq+0x8a/0xa0
[<c0115de5>] do_softirq+0x35/0x40
[<c0116053>] irq_exit+0x43/0x50
[<c013d154>] co_callback+0x164/0x2f0
[<c010a681>] proxy_interrupt_handler+0x41/0x50
[<c0103873>] common_interrupt+0x23/0x30
[<c0396b65>] start_kernel+0x1c5/0x2b0
[<00000000>] _stext+0x3fefff50/0x20
[<c010a30e>] co_start_arch+0xfe/0x170
[<c0109e95>] co_arch_start_kernel+0x0/0xb
=======================
colinux: Linux VM terminated
colinux: BUG at
...vel-gcc412/linux-2.6.22-source/kernel/posix-cpu-timers.c:1295
A newer version stopped working with:
=====================================
Cooperative Linux Daemon, 0.8.0
Daemon compiled on Tue May 13 04:06:17 2008
daemon: exit code 83279001
daemon: error - CO_RC_ERROR_ERROR, line 484, file
src/colinux/user/daemon.c (25)
|
|
From: baldyeti <e_...@ho...> - 2008-05-13 17:20:11
|
Hi Henry, just wanted to let you know I upgraded to RC4 and it's still running fine. Looks like you really fixed those nasty crashes; thanks for that. And sorry for the noise I also wanted to check I could reply through gmane since the policy change ;-) --bald On 12/05/2008 20:04, Henry Nestler wrote: > Hello, > > Next release candidate 0.7.3-RC4 with kernel 2.6.22.18 is available from > snapshot page. http://www.colinux.org/snapshots/ > > Last week was fixed some Vista problems on nt-console. > Many other small bugs are fixed. For details, please read the NEWS. > http://www.colinux.org/snapshots/stable-NEWS > > After testing phase this will release out next weeks. |
|
From: coLinux a. <col...@he...> - 2008-05-13 04:07:25
|
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-20080512/ colinux-0.8.0-20080512.src.tgz (692359 Bytes) daemons-0.8.0-20080512.dbg.zip (1353098 Bytes) daemons-0.8.0-20080512.zip (1051109 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 The vmlinux and modules are up to date. Please use last version from http://www.henrynestler.com/colinux/autobuild/devel-20080425/ 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 ------------------------------------------------------------------------ r1049 | henryn | 2008-05-12 20:29:29 +0000 (Mon, 12 May 2008) | 1 line Changed paths: M /branches/devel/configure * configure: bunzip2 failed, from SVN r1003. (Paolo Minazzi) ------------------------------------------------------------------------ |
|
From: Henry N. <Hen...@Ar...> - 2008-05-12 18:04:01
|
Hello, Next release candidate 0.7.3-RC4 with kernel 2.6.22.18 is available from snapshot page. http://www.colinux.org/snapshots/ Last week was fixed some Vista problems on nt-console. Many other small bugs are fixed. For details, please read the NEWS. http://www.colinux.org/snapshots/stable-NEWS After testing phase this will release out next weeks. -- Henry N. |
|
From: coLinux a. <col...@he...> - 2008-05-12 04:07:38
|
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-20080511/ colinux-0.8.0-20080511.src.tgz (692353 Bytes) daemons-0.8.0-20080511.dbg.zip (1353095 Bytes) daemons-0.8.0-20080511.zip (1051108 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 The vmlinux and modules are up to date. Please use last version from http://www.henrynestler.com/colinux/autobuild/devel-20080425/ 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 ------------------------------------------------------------------------ r1046 | henryn | 2008-05-11 21:26:36 +0000 (Sun, 11 May 2008) | 1 line Changed paths: M /branches/devel/src/colinux/kernel/manager.c * co_manager_send: Exit sleep wait, if monitor closed. ------------------------------------------------------------------------ r1045 | henryn | 2008-05-11 11:26:03 +0000 (Sun, 11 May 2008) | 1 line Changed paths: M /branches/devel/src/colinux/kernel/manager.c * co_manager_send: Move debug prints outside sleepping loop. ------------------------------------------------------------------------ r1044 | henryn | 2008-05-11 09:03:35 +0000 (Sun, 11 May 2008) | 1 line Changed paths: M /branches/devel/src/colinux/common/queue.c M /branches/devel/src/colinux/common/queue.h M /branches/devel/src/colinux/os/linux/kernel/module/pages.c * co_os_get_page: GFP_ZERO as parameter to alloc_pages. (Linux as host) ------------------------------------------------------------------------ r1043 | henryn | 2008-05-11 08:58:36 +0000 (Sun, 11 May 2008) | 3 lines Changed paths: M /branches/devel/src/colinux/common/messages.h M /branches/devel/src/colinux/kernel/manager.c * co_manager_send: Limit queue entries and sleep, if user task is busy. Fix for unresponsable keybord on flooded ntconsole output under Vista. ------------------------------------------------------------------------ r1042 | henryn | 2008-05-11 08:34:26 +0000 (Sun, 11 May 2008) | 1 line Changed paths: M /branches/devel/src/colinux/os/winnt/user/reactor.c * packet_read_async: Fixup double data write (from r1041) ------------------------------------------------------------------------ |
|
From: coLinux a. <col...@he...> - 2008-05-11 04:07:39
|
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-20080510/ colinux-0.8.0-20080510.src.tgz (692210 Bytes) daemons-0.8.0-20080510.dbg.zip (1353160 Bytes) daemons-0.8.0-20080510.zip (1051149 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 The vmlinux and modules are up to date. Please use last version from http://www.henrynestler.com/colinux/autobuild/devel-20080425/ 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 ------------------------------------------------------------------------ r1041 | henryn | 2008-05-10 23:37:28 +0000 (Sat, 10 May 2008) | 1 line Changed paths: M /branches/devel/NEWS M /branches/devel/src/colinux/os/winnt/user/reactor.c * packet_read_async: Remove the loop to have keyboard inputs on overflooded console. ------------------------------------------------------------------------ r1040 | henryn | 2008-05-10 23:29:22 +0000 (Sat, 10 May 2008) | 1 line Changed paths: M /branches/devel/src/colinux/os/winnt/kernel/alloc.c M /branches/devel/src/colinux/os/winnt/kernel/lowlevel/alloc.c * ntkernel: Dont include asm/page.h - Problems with 2.6.25 kernel header types.h and "fd_set" ------------------------------------------------------------------------ r1039 | henryn | 2008-05-10 23:23:40 +0000 (Sat, 10 May 2008) | 1 line Changed paths: M /branches/devel/src/colinux/os/winnt/kernel/alloc.c M /branches/devel/src/colinux/os/winnt/kernel/lowlevel/alloc.c * ntkernel: CO_ARCH_PAGE_SIZE should use on host side, not PAGE_SIZE ------------------------------------------------------------------------ |
|
From: SourceForge.net <no...@so...> - 2008-05-09 23:26:19
|
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: 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: 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...> - 2008-05-09 22:45:09
|
Bugs item #1959846, was opened at 2008-05-07 15:38 Message generated for change (Comment added) made by george_v_reilly 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: George V. Reilly (george_v_reilly) Date: 2008-05-09 15: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 15: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 13: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...> - 2008-05-09 22:44:48
|
Bugs item #1959846, was opened at 2008-05-07 15:38 Message generated for change (Comment added) made by george_v_reilly 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: George V. Reilly (george_v_reilly) Date: 2008-05-09 15: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 13: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 |
81 messages has been excluded from this view by a project administrator.
