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...> - 2009-02-21 04:15:26
|
Bugs item #2622508, was opened at 2009-02-21 04:15 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=2622508&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: slight UI glitch wrt fltk console Initial Comment: the fltk console app doesn't seem to handle window resizing events properly, in fact it doesn't even honor terminal events resulting from running "reset" in order to make the console adjust to the new window layout. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2622508&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-18 23:36:47
|
Bugs item #2587396, was opened at 2009-02-11 03:42 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2587396&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: None Status: Open >Resolution: Accepted Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) >Summary: Shutdown coLinux hang host on Windows 2000 Initial Comment: I report this problem in #2445837 Unfortunate, the problem live also. I try the autobuild-20090210, it hang also. step: 1. Boot your linux with cmd set COLINUX_NO_SMP_WORKAROUND=N colinux-daemon.exe -t FLTK cocon=116x36 kernel=vmlinux mem=500 cobd0=..\root_fs cobd1=..\swap_fs eth0=ndis-bridge,"本地连接" setcobd=async root=/dev/cobd0 ro 2. login to linux 3. execute 'halt'. Now, you will found process 'colinux-ndis-net-daemon.exe' can not halt, and host can not do manything(include close system), you must hard-reset your PC. btw: another info when I use my build-20081209, it work fine, and when I replace vmlinux in build-20090211, it will report "colinux: BUG at /develop/build/linux-2.6.22.18/block/elevator.c:780" I do not known what's wrong in kernel patch. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-18 22:32 Message: Hello, this is not a problem of ndis-bridge only. I have this also without ndis-bridge. That's why have changed the title line here. I's something with shutting down sequence of coLinux kernel driver and the attached daemons under Windows 2000 only. Host: 256MB RAM, Windows 2000 (no Service packs), single core Here is my config: colinux-daemon kernel=vmlinux mem=64 ^ cobd0=Debian-4.0r0-etch.ext3 root=/dev/cobd0 ^ eth0=slirp CoLinux have only started, and than used the FLTK Menu "Monitor * Shutdown". Sometimes this simple configuration above hangs on CMD.EXE, sometimes the Slirp daemon. After the shutdown it hangs with these last 3 lines: System halted. colinux: Linux VM terminated colinux: halted, exiting. If I open ProcessExplorer for this task, then the GUI goes into completely unusable state. Mouse can move. But all windows are frozen. Only the tilte line of running Windows task can activate and deactivate by mouse click. CTRL-ALT-DEL cleans the desktop, but the "logon Windows" comes not up. Only Power off or Reset key can use to reboot the host. With this config it hangs very rarely (1 hangs of 30 starts): colinux-daemon kernel=vmlinux mem=64 ^ cobd0=Debian-4.0r0-etch.ext3 root=/dev/cobd0 If I add more network devices, then the system hangs more often. For example with eth0 and eth1 it hangs very often: colinux-daemon kernel=vmlinux mem=64 ^ cobd0=Debian-4.0r0-etch.ext3 root=/dev/cobd0 ^ eth0=slirp ^ eth1=ndis-bridge,"LAN" My fovorite for test is this. This automatically "halt" the Linux directly after boot is complete (start in runlevel 0): colinux-daemon kernel=vmlinux init 0 ^ cobd0=Debian-4.0r0-etch.ext3 root=/dev/cobd0 ^ eth0=slirp ^ eth1=ndis-bridge,"LAN" ^ cofs0=. The last running snapshot found at 2008-11-30 (no problems). The first with problem found in snapshot 2009-01-13 (hangs with eth0+eth1). Can you confirm this? Old snapshots exists at http://www.henrynestler.com/colinux/testing/devel-0.8.0/ ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-02-12 02:28 Message: 1. My host is Windows2000 SP4, 1GB RAM, Core Duo 2.8GHz 2. When I set 'COLINUX_NO_SMP_WORKAROUND=Y', the 'colinux-ndis-net-daemon.exe' can be close, but 'colinux-console-fltk.exe' can not, and hang my system also. 3. use cmdline 'init 1', I look 'colinux-ndis-net-daemon.exe' running, and I got same as (2) 4. I look the info below: io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-02-11 08:36 Message: What is the host system? Windows XP or Windows 2000? Does it hang with COLINUX_NO_SMP_WORKAROUND=Y ? Does it hang, if you boots without using network? For example by adding "init 1" to the kernel parameters (starts in runlevel 1). For the elevator.c:780 you have changed the IO Scheduler to CFQ? "setcobd=async" does not work in conjunction with "elevator=cfq". I have added as separate bug artifact #2588147 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2587396&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-18 21:22:09
|
Bugs item #2445837, was opened at 2008-12-18 19:07 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2445837&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.8.x (devel) Status: Closed Resolution: Duplicate Priority: 5 Private: No Submitted By: Xuefer (xuefer) Assigned to: Henry N. (henryn) Summary: colinux+ndis-bridge hang with vbox 2.1 Initial Comment: Virtualbox version: VirtualBox-2.1.0-41146-Win_x86.msi (got from http://www.filehippo.com/download_virtualbox/ same file as official though) colinux version: 0.8.0-20080924, 0.8.0-20081212 windows version: xp with all SP/hotfix patched guest os: gentoo configuration: ======== kernel=vmlinux mem=512 video0=4 kernel=vmlinux mem=512 video0=4 #eth0=pcap-bridge,ADSLModem #eth1=pcap-bridge,coLinux,00:ff:4f:0d:e7:c0 eth1=ndis-bridge,coLinux,00:ff:4f:0d:e7:c0 root=/dev/sda3 sda2=\Device\Harddisk1\Partition2 sda3=\Device\Harddisk1\Partition3 sda5=\Device\Harddisk1\Partition4 cofs0=\DosDevices\c:\app\system\colinux\ cofs1=\DosDevices\c:\ cofs2=\DosDevices\d:\ cofs3=\DosDevices\i:\ cofs4=\DosDevices\g:\ bootlevel=c.boot softlevel=c.default setcobd=async ========= it used to work when i have virtualbox VirtualBox-2.0.6-39760-Win_x86.msi installed. but when i upgrade virtualbox to 2.1.0-41146-Win_x86, colinux network stopped working. i restart colinux and the whole system just stuck there, no keyb/mouse response. this is a ndis-bridge specified problem again. works fine with pcap-bridge to reproduce it 1. install colinux, configure with ndis-bridge 2. install VirtualBox-2.1.0-41146-Win_x86.msi (just install, no need to run it) 3. start colinux i guess it's relatived to the driver (filter?) vbox2.1 installed for each network adapter: VBoxNetFlt Driver, VirtualBox Host Interface Networking Driver ---------------------------------------------------------------------- Comment By: Xuefer (xuefer) Date: 2009-02-10 04:51 Message: i can confirm it fixed. thanks ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-02-10 02:49 Message: I feel, it is the same problem as in Bug #2357595. We have fixed a wrong parameter for packet injection, that freeze the host. Please test with a build from SVN revision r1218 or later. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-01-21 02:26 Message: The date means I checkout latest SVN code and rebuild in this day. I have been re-patch kernel(I do not rebuild compiler, FLTK, etc). then do "--remove-driver" and "--install-driver" also. I must go home tomorrow, I will recheck my build next month. btw: I upgrade my cross-GCC to 4.2.4, the build 20081209 & 20090105 both compile with it. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-01-19 22:47 Message: Hello, with the "win2k sp4", can you please check on what revision does start exactly the problem. Between 20081209 and 20090105 have many small changes, and for date 2008-12-09 I can not find any change in changelog (http://www.colinux.org/snapshots/devel-ChangeLog). You will find some older binaries and sources under http://www.henrynestler.com/colinux/autobuild/ If you have self build coLinux: Remember that you need to re-patch and re-build the kernel, if any of the files are changed in directory "patch/*.diff", and be sure to have called "--remove-driver" and "--install-driver" while coLinux is not running. If you build coLinux from source, you can use "svn update rNNNN" with any revision number NNNN, to find the exactly revision number what does create the "halt" problem. Use initrd, to avoid loosing data on your filesystem. For example: colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0 eth1=ndis-bridge,"LAN" ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-01-19 06:16 Message: Yes, I got this bug also. I build colinux myself, I build about every two weeks. My compute run win2k sp4, the colinux build at 20081209 can be work fine, but 20090105 and later wrong. I can boot the colinux and do any works. but when I 'halt' the linux, the colinux-ndis-net-daemon.exe can not stop, it will hang my computer, I can not open any program, can not reboot. I must turn off(or hard-reset) my computer to continue. ---------------------------------------------------------------------- Comment By: Xuefer (xuefer) Date: 2008-12-18 19:12 Message: network adapters: 1. WAN: nvidia nforce 10/100/1000Mbps Ethernet (i don't think it relatived to this problem) 2. coLinux: Microsoft Loopback Adapter i just found a workaround 1. right click "coLinux" adapter 2. uncheck "VirtualBox Host Interface Networking Driver" press OK ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2445837&group_id=98788 |
|
From: coLinux a. <col...@he...> - 2009-02-16 05:07:02
|
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-20090215/ colinux-0.8.0-20090215.src.tgz (685201 Bytes) daemons-0.8.0-20090215.dbg.zip (591682 Bytes) daemons-0.8.0-20090215.zip (478700 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-20090205/ 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 ------------------------------------------------------------------------ r1224 | henryn | 2009-02-15 19:23:57 +0000 (Sun, 15 Feb 2009) | 2 lines Changed paths: M /branches/devel/NEWS M /branches/devel/src/colinux/common/console.c * Bug #2593186: FLTK console command prompt display problems. (Contributed by Shai Vaingast) ------------------------------------------------------------------------ |
|
From: SourceForge.net <no...@so...> - 2009-02-15 19:26:08
|
Bugs item #2593186, was opened at 2009-02-12 15:32 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2593186&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: Fixed Priority: 5 Private: No Submitted By: Shai (vshai) Assigned to: Nobody/Anonymous (nobody) Summary: FLTK console command prompt display problems Initial Comment: I've experienced issues with the FLTK console (colinux-console-fltk.exe) but was unable to reproduce the problem systematically. What would happen is that using the command line, either with tab-completion or with scroll history (ctrl-p/up-arrow) at times text would not be cleared properly, leaving leftover text from the previously entered command. I've finally managed to pinpoint the problem and it appears to be related to all these issues (tab completion, history, backspace, etc.) To reproduce the problem, in a bash shell using colinux-console-fltk.exe, do the following: 1. Type a very long string, at least 40 characters, say: $ 1234567890123456789012345678901234567890 Now, press ctrl-a to get to the start of the line and press delete three times. What you'll see is this: $ 4567890123456789012345678901222234567890 Notice how the digit 2 towards the end of the string are multiplied 4 times. The right output should be of course: $ 4567890123456789012345678901234567890 There are many other ways to cause this to happen, and it appears to be happening when the command string length is about 40 characters long. Configuration: this happens on Windows XP SP3; both version 0.8.x and 0.7.3. This does not happen on colinux-console-nt.exe as far as I could tell. Thanks, - Shai ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-15 20:26 Message: Thanks, committed to SVN as revision r1224. ---------------------------------------------------------------------- Comment By: Shai (vshai) Date: 2009-02-15 12:25 Message: The cause for this is the number of bytes to memmov() function call in file src/colinux/common/console.c, it should be multiplied by the sizeof(co_console_cell_t). There are two calls to memmov() that don't multiply by the sizeof value. Since the sizeof(co_console_cell_t) is probably 2 bytes long (character and attribute), this very easily explains the reason why after 40 bytes on a 80 characters monitor text appears wrong. This is the modification that seems to be working for me: *** console.c Sun Feb 15 03:15:10 2009 --- console_old.c Sun Feb 15 03:14:39 2009 *************** *** 176,182 **** while (t <= b) { memmove(&console->screen[y*console->x+x], &console->screen[t*console->x+l], ! (r-l+1)*sizeof(co_console_cell_t)); t++; y++; } --- 176,182 ---- while (t <= b) { memmove(&console->screen[y*console->x+x], &console->screen[t*console->x+l], ! r-l+1); t++; y++; } *************** *** 185,191 **** while (t <= b) { memmove(&console->screen[y*console->x+x], &console->screen[b*console->x+l], ! (r-l+1)*sizeof(co_console_cell_t)); b--; y--; } --- 185,191 ---- while (t <= b) { memmove(&console->screen[y*console->x+x], &console->screen[b*console->x+l], ! r-l+1); b--; y--; } I've only tested it on Windows XP with coLinux version 0.8.0 (but I think it should fix 0.7.3 as well). This might also explain other related issues with the FLTK console display. - Shai ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2593186&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-15 11:25:43
|
Bugs item #2593186, was opened at 2009-02-12 16:32 Message generated for change (Comment added) made by vshai You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2593186&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: Shai (vshai) Assigned to: Nobody/Anonymous (nobody) Summary: FLTK console command prompt display problems Initial Comment: I've experienced issues with the FLTK console (colinux-console-fltk.exe) but was unable to reproduce the problem systematically. What would happen is that using the command line, either with tab-completion or with scroll history (ctrl-p/up-arrow) at times text would not be cleared properly, leaving leftover text from the previously entered command. I've finally managed to pinpoint the problem and it appears to be related to all these issues (tab completion, history, backspace, etc.) To reproduce the problem, in a bash shell using colinux-console-fltk.exe, do the following: 1. Type a very long string, at least 40 characters, say: $ 1234567890123456789012345678901234567890 Now, press ctrl-a to get to the start of the line and press delete three times. What you'll see is this: $ 4567890123456789012345678901222234567890 Notice how the digit 2 towards the end of the string are multiplied 4 times. The right output should be of course: $ 4567890123456789012345678901234567890 There are many other ways to cause this to happen, and it appears to be happening when the command string length is about 40 characters long. Configuration: this happens on Windows XP SP3; both version 0.8.x and 0.7.3. This does not happen on colinux-console-nt.exe as far as I could tell. Thanks, - Shai ---------------------------------------------------------------------- >Comment By: Shai (vshai) Date: 2009-02-15 13:25 Message: The cause for this is the number of bytes to memmov() function call in file src/colinux/common/console.c, it should be multiplied by the sizeof(co_console_cell_t). There are two calls to memmov() that don't multiply by the sizeof value. Since the sizeof(co_console_cell_t) is probably 2 bytes long (character and attribute), this very easily explains the reason why after 40 bytes on a 80 characters monitor text appears wrong. This is the modification that seems to be working for me: *** console.c Sun Feb 15 03:15:10 2009 --- console_old.c Sun Feb 15 03:14:39 2009 *************** *** 176,182 **** while (t <= b) { memmove(&console->screen[y*console->x+x], &console->screen[t*console->x+l], ! (r-l+1)*sizeof(co_console_cell_t)); t++; y++; } --- 176,182 ---- while (t <= b) { memmove(&console->screen[y*console->x+x], &console->screen[t*console->x+l], ! r-l+1); t++; y++; } *************** *** 185,191 **** while (t <= b) { memmove(&console->screen[y*console->x+x], &console->screen[b*console->x+l], ! (r-l+1)*sizeof(co_console_cell_t)); b--; y--; } --- 185,191 ---- while (t <= b) { memmove(&console->screen[y*console->x+x], &console->screen[b*console->x+l], ! r-l+1); b--; y--; } I've only tested it on Windows XP with coLinux version 0.8.0 (but I think it should fix 0.7.3 as well). This might also explain other related issues with the FLTK console display. - Shai ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2593186&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-12 14:32:54
|
Bugs item #2593186, was opened at 2009-02-12 16:32 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=2593186&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: Shai (vshai) Assigned to: Nobody/Anonymous (nobody) Summary: FLTK console command prompt display problems Initial Comment: I've experienced issues with the FLTK console (colinux-console-fltk.exe) but was unable to reproduce the problem systematically. What would happen is that using the command line, either with tab-completion or with scroll history (ctrl-p/up-arrow) at times text would not be cleared properly, leaving leftover text from the previously entered command. I've finally managed to pinpoint the problem and it appears to be related to all these issues (tab completion, history, backspace, etc.) To reproduce the problem, in a bash shell using colinux-console-fltk.exe, do the following: 1. Type a very long string, at least 40 characters, say: $ 1234567890123456789012345678901234567890 Now, press ctrl-a to get to the start of the line and press delete three times. What you'll see is this: $ 4567890123456789012345678901222234567890 Notice how the digit 2 towards the end of the string are multiplied 4 times. The right output should be of course: $ 4567890123456789012345678901234567890 There are many other ways to cause this to happen, and it appears to be happening when the command string length is about 40 characters long. Configuration: this happens on Windows XP SP3; both version 0.8.x and 0.7.3. This does not happen on colinux-console-nt.exe as far as I could tell. Thanks, - Shai ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2593186&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-12 01:28:19
|
Bugs item #2587396, was opened at 2009-02-11 02:42 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2587396&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: ndis-bridge hang host Initial Comment: I report this problem in #2445837 Unfortunate, the problem live also. I try the autobuild-20090210, it hang also. step: 1. Boot your linux with cmd set COLINUX_NO_SMP_WORKAROUND=N colinux-daemon.exe -t FLTK cocon=116x36 kernel=vmlinux mem=500 cobd0=..\root_fs cobd1=..\swap_fs eth0=ndis-bridge,"本地连接" setcobd=async root=/dev/cobd0 ro 2. login to linux 3. execute 'halt'. Now, you will found process 'colinux-ndis-net-daemon.exe' can not halt, and host can not do manything(include close system), you must hard-reset your PC. btw: another info when I use my build-20081209, it work fine, and when I replace vmlinux in build-20090211, it will report "colinux: BUG at /develop/build/linux-2.6.22.18/block/elevator.c:780" I do not known what's wrong in kernel patch. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-02-12 01:28 Message: 1. My host is Windows2000 SP4, 1GB RAM, Core Duo 2.8GHz 2. When I set 'COLINUX_NO_SMP_WORKAROUND=Y', the 'colinux-ndis-net-daemon.exe' can be close, but 'colinux-console-fltk.exe' can not, and hang my system also. 3. use cmdline 'init 1', I look 'colinux-ndis-net-daemon.exe' running, and I got same as (2) 4. I look the info below: io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-02-11 07:36 Message: What is the host system? Windows XP or Windows 2000? Does it hang with COLINUX_NO_SMP_WORKAROUND=Y ? Does it hang, if you boots without using network? For example by adding "init 1" to the kernel parameters (starts in runlevel 1). For the elevator.c:780 you have changed the IO Scheduler to CFQ? "setcobd=async" does not work in conjunction with "elevator=cfq". I have added as separate bug artifact #2588147 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2587396&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-11 07:36:37
|
Bugs item #2587396, was opened at 2009-02-11 03:42 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2587396&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: ndis-bridge hang host Initial Comment: I report this problem in #2445837 Unfortunate, the problem live also. I try the autobuild-20090210, it hang also. step: 1. Boot your linux with cmd set COLINUX_NO_SMP_WORKAROUND=N colinux-daemon.exe -t FLTK cocon=116x36 kernel=vmlinux mem=500 cobd0=..\root_fs cobd1=..\swap_fs eth0=ndis-bridge,"本地连接" setcobd=async root=/dev/cobd0 ro 2. login to linux 3. execute 'halt'. Now, you will found process 'colinux-ndis-net-daemon.exe' can not halt, and host can not do manything(include close system), you must hard-reset your PC. btw: another info when I use my build-20081209, it work fine, and when I replace vmlinux in build-20090211, it will report "colinux: BUG at /develop/build/linux-2.6.22.18/block/elevator.c:780" I do not known what's wrong in kernel patch. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-11 08:36 Message: What is the host system? Windows XP or Windows 2000? Does it hang with COLINUX_NO_SMP_WORKAROUND=Y ? Does it hang, if you boots without using network? For example by adding "init 1" to the kernel parameters (starts in runlevel 1). For the elevator.c:780 you have changed the IO Scheduler to CFQ? "setcobd=async" does not work in conjunction with "elevator=cfq". I have added as separate bug artifact #2588147 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2587396&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-11 07:31:46
|
Bugs item #2588147, was opened at 2009-02-11 08:31 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=2588147&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: Linux Kernel Group: v0.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Henry N. (henryn) Assigned to: Nobody/Anonymous (nobody) Summary: block/elevator.c:780 for setcobd=async Initial Comment: "colinux: BUG at /develop/build/linux-2.6.22.18/block/elevator.c:780" With "setcobd=async elevator=cfq" as kernel parameter or with changed kernel config for IO Scheduler to CFQ this bug will happens. One of usable scheduler for asynchronous block device is anticipatory. More have not tested. Please leave the kernel config as follow: CONFIG_IOSCHED_AS=y CONFIG_DEFAULT_IOSCHED="anticipatory" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2588147&group_id=98788 |
|
From: coLinux a. <col...@he...> - 2009-02-11 05:07:11
|
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-20090210/ colinux-0.8.0-20090210.src.tgz (685166 Bytes) daemons-0.8.0-20090210.dbg.zip (591709 Bytes) daemons-0.8.0-20090210.zip (478716 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-20090205/ 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 ------------------------------------------------------------------------ r1223 | henryn | 2009-02-10 23:49:37 +0000 (Tue, 10 Feb 2009) | 1 line Changed paths: M /branches/devel/NEWS * News: Update and sorted. ------------------------------------------------------------------------ r1222 | henryn | 2009-02-10 23:27:14 +0000 (Tue, 10 Feb 2009) | 3 lines Changed paths: M /branches/devel/src/colinux/os/winnt/user/conet-bridged-daemon/main.c * Bug#1396539: Fix pcap-bridge mirrors self sending broadcast packets. Multicast implicates broadcast packets, so this not needs to extra filter. Filter rule changed to "(ether dst MAC) or (multicast and not ether src MAC)" ------------------------------------------------------------------------ r1221 | henryn | 2009-02-10 23:23:40 +0000 (Tue, 10 Feb 2009) | 1 line Changed paths: M /branches/devel/src/colinux/os/winnt/kernel/conet.c * ndis-bridge: Check source mac only for broadcast/multicast packets. ------------------------------------------------------------------------ r1220 | henryn | 2009-02-10 23:21:11 +0000 (Tue, 10 Feb 2009) | 1 line Changed paths: M /branches/devel/src/colinux/os/winnt/kernel/conet.c * ndis-bridge: Multicast implicates broadcast packets, not needs extra filter. ------------------------------------------------------------------------ r1219 | henryn | 2009-02-10 22:28:26 +0000 (Tue, 10 Feb 2009) | 1 line Changed paths: M /branches/devel/NEWS M /branches/devel/src/colinux/os/winnt/user/console-nt/widget.cpp * Bug#1117788: Fix sticky Alt or Shift after system menu from Alt-Space (nt console). ------------------------------------------------------------------------ |
|
From: SourceForge.net <no...@so...> - 2009-02-11 02:52:54
|
Bugs item #2587396, was opened at 2009-02-11 02:42 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=2587396&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: ndis-bridge hang host Initial Comment: I report this problem in #2445837 Unfortunate, the problem live also. I try the autobuild-20090210, it hang also. step: 1. Boot your linux with cmd set COLINUX_NO_SMP_WORKAROUND=N colinux-daemon.exe -t FLTK cocon=116x36 kernel=vmlinux mem=500 cobd0=..\root_fs cobd1=..\swap_fs eth0=ndis-bridge,"本地连接" setcobd=async root=/dev/cobd0 ro 2. login to linux 3. execute 'halt'. Now, you will found process 'colinux-ndis-net-daemon.exe' can not halt, and host can not do manything(include close system), you must hard-reset your PC. btw: another info when I use my build-20081209, it work fine, and when I replace vmlinux in build-20090211, it will report "colinux: BUG at /develop/build/linux-2.6.22.18/block/elevator.c:780" I do not known what's wrong in kernel patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2587396&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-10 23:44:33
|
Bugs item #1955601, was opened at 2008-05-01 20:55 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1955601&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.8.x (devel) >Status: Closed >Resolution: Duplicate Priority: 5 Private: No Submitted By: Arion Lawrence (arionl) Assigned to: Nobody/Anonymous (nobody) Summary: IPv6 not supported in colinux-*-net-daemon.exe Initial Comment: IPv6 doesn't work inside coLinux even with the "ipv6" kernel module loaded. It seems that the "colinux-*-net-daemon.exe" programs don't pass IPv6 packets from the host to coLinux. CoLinux can try to send IPv6 packets (i.e., router solicitation) and I have verified that the packets get transmitted via sniffer, but it does not receive any responses. Looks like the host-side filtering doesn't pass IPv6 ethernet frames. Excerpt from /devel-colinux-20080420/src/colinux/os/winnt/kernel/conet.c if ( co_conet_ntohs(pEthHdr->h_proto) == ETH_P_IP ) { if ( RtlCompareMemory(pEthHdr->h_dest, "\xFF\xFF\xFF\xFF\xFF\xFF", 6) == 6 ) { [ ...debug stuff...] return TRUE; } else if ( RtlCompareMemory(pEthHdr->h_dest, adapter->macaddr, 6) == 6 ) { [ ...debug stuff...] return TRUE; } else { [ ...debug stuff... ] return FALSE; } } else if ( co_conet_ntohs(pEthHdr->h_proto) == ETH_P_ARP ) { [ ...debug stuff... ] return TRUE; } else { co_debug("not IP or ARP protocol"); return FALSE; } The ethernet frame filter these daemons use only pass ARP and IP packets. They need to include ETH_P_IPV6 (frame type 0x86DD) so the packets can pass. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-11 00:44 Message: This should be fixed from removing the IP frame checks. See Bug #2357494. All packets are filtered on MAC layer only now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1955601&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-10 23:29:52
|
Bugs item #1396539, was opened at 2006-01-04 05:52 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1396539&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.8.x (devel) >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Xuan Baldauf (mediumnet) >Assigned to: Henry N. (henryn) Summary: colinux-bridged-net-daemon.exe mirrors broadcast packets Initial Comment: The current implementation of "colinux-bridged-net-daemon.exe" (from http://www.colinux.org/snapshots/devel-coLinux-20051013.exe ) mirrors broadcast packets back: A broadcast packet sent from the colinux instance within Windows to the Windows networking will get mirrored back to the colinux instance. Thus, linux thinks that some other network member has the same MAC address, and spits out warning messages like "eth0: duplicate address detected!", which pollute the kernel log buffer and log files. Previous versions of "colinux-bridged-net-daemon.exe" (http://www.colinux.org/snapshots/stable-coLinux-20050524.exe AFAIK) did not mirror back broadcast packets. (However, the performance of previous "colinux-bridged-net-daemon.exe" versions was miserable.) ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-11 00:29 Message: Filter rule changed to "(ether dst MAC) or (multicast and not ether src MAC)". Committed to SVN as revision r1222. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1396539&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-10 23:06:49
|
Bugs item #1117788, was opened at 2005-02-07 11:24 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1117788&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: Fixed Priority: 5 Private: No Submitted By: user222 (user222) >Assigned to: Henry N. (henryn) Summary: NT console problem Initial Comment: When running Colinux with the NT console instead of the FLTK console, pressing [ALT-SPACE] makes it impossible to resume the session. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-10 23:33 Message: As workaround you can press ones the ALT key, then keyboard is usable again. The sticky ALT after exit from system menu is handled now inside the nt console. Committed to SVN as revision r1219. ---------------------------------------------------------------------- Comment By: Danny Staple (orionrobots) Date: 2005-06-23 01:10 Message: Logged In: YES user_id=748225 Interesting issue. Putty appears to handle this by overriding or unassigning the default action for alt-space. I would suggest that the same method is used with the colinux-console. ---------------------------------------------------------------------- Comment By: George P Boutwell (gboutwel) Date: 2005-02-22 18:06 Message: Logged In: YES user_id=30412 Ok. I see the same thing with Midnight Commander. ---------------------------------------------------------------------- Comment By: user222 (user222) Date: 2005-02-22 17:06 Message: Logged In: YES user_id=1120398 {_I'm not able to duplicate, this, can you give more details, what program you running in coLinux that things ALT is still pressed, etc?_} the GNU Midnight Commander ---------------------------------------------------------------------- Comment By: George P Boutwell (gboutwel) Date: 2005-02-21 21:24 Message: Logged In: YES user_id=30412 I'm not able to duplicate, this, can you give more details, what program you running in coLinux that things ALT is still pressed, etc? ---------------------------------------------------------------------- Comment By: BJH (californiakidd) Date: 2005-02-07 14:24 Message: Logged In: YES user_id=4134 The is a known issue. Try and Alt and Space seperately and see if your application accepts input that as a Alt-Space combination. ---------------------------------------------------------------------- Comment By: user222 (user222) Date: 2005-02-07 12:16 Message: Logged In: YES user_id=1120398 Sorry, wrong submission. If you press [ALT-SPACE] in the NT Colinux console, the window operation menu pops up and Colinux would think the [ALT] key is still held. You would need to press the [ALT] key again to "release" the key. ---------------------------------------------------------------------- Comment By: user222 (user222) Date: 2005-02-07 12:03 Message: Logged In: YES user_id=1120398 ...the session without restarting the NT Colinux console. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1117788&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-10 20:58:17
|
Bugs item #2176188, was opened at 2008-10-18 09:20 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2176188&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.8.x (devel) >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Henry N. (henryn) Summary: file sync wrong on cofs, command after mv/rename fails Initial Comment: I found some problem in cofs filesystem. ex: mv t1 t2 stat t2 many times I got "t2 not found". it see like the second command exec before the first finished. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-10 21:58 Message: Think, can close this bug now. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-11-30 01:30 Message: The d_move patch was replaced by inode_rename patch on host side, see SVN revision r1148 + r1149. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-11-12 19:59 Message: Your patch was committed to SVN as revision r1133. Thanks! ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-11-12 16:28 Message: chenm001 (chenm003 AT 163 DOT com) if this patch has any bug, please tell me, I will tract again. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-11-12 01:26 Message: Yes, that solved this bug. NFS does it too. So it it very good. Thanks. What name I can honor in SVN? :-) Henry ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-11-11 10:19 Message: Here is my patch, I do not known it is good way, but it work fine in my computer. static int fuse_rename(struct inode *olddir, struct dentry *oldent, struct inode *newdir, struct dentry *newent) { struct fuse_conn *fc = INO_FC(olddir); struct fuse_in in = FUSE_IN_INIT; struct fuse_out out = FUSE_OUT_INIT; struct fuse_rename_in inarg; memset(&inarg, 0, sizeof(inarg)); inarg.newdir = newdir->i_ino; in.h.opcode = FUSE_RENAME; in.h.ino = olddir->i_ino; in.numargs = 3; in.args[0].size = sizeof(inarg); in.args[0].value = &inarg; in.args[1].size = oldent->d_name.len + 1; in.args[1].value = oldent->d_name.name; in.args[2].size = newent->d_name.len + 1; in.args[2].value = newent->d_name.name; request_send(fc, &in, &out); if (!out.h.error) { uncache_dir(olddir); + d_move(oldent, newent); if (olddir != newdir) uncache_dir(newdir); } return out.h.error; } ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-11-06 22:17 Message: Yes, SVN r1127 corrected only the swapped atime and mtime, and not the cache problem on rename. You have a patch? Nice. Please let's see. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-10-29 04:04 Message: Unfortunately, SVN revision r1127 do not fix this bug. When I remove my "d_move" patch, problem was recurrence. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-10-28 00:24 Message: With these script the "touch -d 1970-1-1 b" after the "mv" fails all times: rm -f a b touch a mv a b touch -d 1970-1-1 b ls --full-time b Same problem with overwrite on move: touch a b mv a b touch -d 1970-1-1 b ls --full-time b On cofs the touch after "mv" fails: touch: setting times of `b': No such file or directory -rw-r--r-- 1 root root 0 2008-10-27 23:29:50.000000000 +0000 b On cobd or with 'nocache' it works: -rw-r--r-- 1 root root 0 1970-01-01 00:00:00.000000000 +0000 b ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-10-23 03:18 Message: Close inode cache possible loss performance, it is a little bug in rename only. I fix this bug yesterday. and I will use the my new kernel some days, if that has other problem, I can fix it. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-10-22 13:41 Message: The inode cache is default enabled for 1 Second. You can disable it by adding "nocache" to mount options, for example: mount -o nocache -t cofs 0 /mnt/windows More cosf options, see cofs.txt in your coLinux installation or here: http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/cofs ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-10-21 13:48 Message: I trace the code, it see like rename bug, the filename change, but inode not. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-10-18 09:24 Message: Excuse me, I think this bug same as #2152550 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2176188&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-10 20:54:10
|
Bugs item #2055697, was opened at 2008-08-17 12:15 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2055697&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: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Ritesh Raj Sarraf (riteshsarraf) Assigned to: Nobody/Anonymous (nobody) Summary: colinux slirp daemon keeps crashing Initial Comment: I'm using coLinux (andLinux precisely) to use my favorite torrent app, ktorrent. Many of the times, coLinux keeps crashing in colinux-slirp-daemon.exe I'll attach the crash logs. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-10 21:54 Message: Shai reported that is fixed now. So, I close this bug now. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-02-08 21:09 Message: Thanks Shai Vaingast for the patch. Committed to SVN as revision r1214. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-02-06 01:12 Message: Ok, thanks vshai. The stack with labels: COLINUX-SLIRP-NET-DAEMON! 00402b90() _tcp_input+0x5f0 COLINUX-SLIRP-NET-DAEMON! 004089db() _slirp_select_poll+0x11b COLINUX-SLIRP-NET-DAEMON! 00401d77() _co_slirp_main+0x237 COLINUX-SLIRP-NET-DAEMON! 0040130d() _main+0x2d COLINUX-SLIRP-NET-DAEMON! 00401247() ___mingw_CRTStartup+0xf7 COLINUX-SLIRP-NET-DAEMON! 00401298() _mainCRTStartup+0x18 Here the assembler with source line numbers: src/colinux/user/slirp/tcp_input.c:1403 402b76: 8b 7d d0 mov 0xffffffd0(%ebp),%edi 402b79: 8b 47 08 mov 0x8(%edi),%eax 402b7c: 83 e8 03 sub $0x3,%eax 402b7f: 66 83 f8 07 cmp $0x7,%ax 402b83: 0f 86 d4 01 00 00 jbe 402d5d <_tcp_input+0x7bd> 402b89: 8d b4 26 00 00 00 00 lea 0x0(%esi),%esi src/colinux/user/slirp/tcp_input.c:1460 ===> 402b90: 0f b7 46 0a movzwl 0xa(%esi),%eax <=== 402b94: 48 dec %eax 402b95: 66 83 f8 04 cmp $0x4,%ax 402b99: 77 0a ja 402ba5 <_tcp_input+0x605> 402b9b: 80 7e 28 1b cmpb $0x1b,0x28(%esi) 402b9f: 0f 84 e6 01 00 00 je 402d8b <_tcp_input+0x7eb> src/colinux/user/slirp/tcp_input.c:1468 402ba5: 8b 45 b4 mov 0xffffffb4(%ebp),%eax 402ba8: 85 c0 test %eax,%eax 402baa: 75 0d jne 402bb9 <_tcp_input+0x619> 402bac: 8b 4d d0 mov 0xffffffd0(%ebp),%ecx 402baf: f6 41 1c 01 testb $0x1,0x1c(%ecx) 402bb3: 0f 84 29 fe ff ff je 4029e2 <_tcp_input+0x442> src/colinux/user/slirp/tcp_input.c:1469 Here is this source line number 1460 on SF: http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/src/colinux/user/slirp/tcp_input.c?view=markup#l_1460 ---------------------------------------------------------------------- Comment By: Shai (vshai) Date: 2009-02-05 20:38 Message: I think this should be re-opened. I've caused this to happen several times and it seems that the crash happens at the same point (i.e., same IP, dame call stack, same disassembly location, etc.) The reason for this does seem to heavy network related, such as the case running bittorrents. My setup is: coLinux 0.7.3 Slirp to connect to the Internet. TAP to connect to the host and share files. Linux Gentoo. Windows XP SP3. Call stack: COLINUX-SLIRP-NET-DAEMON! 00402b90() COLINUX-SLIRP-NET-DAEMON! 004089db() COLINUX-SLIRP-NET-DAEMON! 00401d77() COLINUX-SLIRP-NET-DAEMON! 0040130d() COLINUX-SLIRP-NET-DAEMON! 00401247() COLINUX-SLIRP-NET-DAEMON! 00401298() KERNEL32! 7c817067() Registers: EAX = 00000001 EBX = 00000002 ECX = 77C2C2E3 EDX = 00030608 ESI = 0051B03C EDI = 005143E0 EIP = 00402B90 ESP = 0023FA20 EBP = 0023FA98 EFL = 00000246 MM0 = 0000000000000000 MM1 = 0000000000000000 MM2 = 0000000000000000 MM3 = 0000000000000000 MM4 = 0000000000000000 MM5 = 0000003800000000 MM6 = 0000000000000000 MM7 = 004012A000000000 XMM0 = 00000000000000000000000000000000 XMM1 = 00000000000000000000000000000000 XMM2 = 00000000000000000000000000000000 XMM3 = 00000000000000000000000000000000 XMM4 = 00000000000000000000000000000000 XMM5 = 00000000000000000000000000000000 XMM6 = 00000000000000000000000000000000 XMM7 = 00000000000000000000000000000000 CS = 001B DS = 0023 ES = 0023 SS = 0023 FS = 003B GS = 0000 OV=0 UP=0 EI=1 PL=0 ZR=1 AC=0 PE=1 CY=0 0051B046 = ???? XMM0DL = +0.00000000000000E+000 XMM0DH = +0.00000000000000E+000 XMM1DL = +0.00000000000000E+000 XMM1DH = +0.00000000000000E+000 XMM2DL = +0.00000000000000E+000 XMM2DH = +0.00000000000000E+000 XMM3DL = +0.00000000000000E+000 XMM3DH = +0.00000000000000E+000 XMM4DL = +0.00000000000000E+000 XMM4DH = +0.00000000000000E+000 XMM5DL = +0.00000000000000E+000 XMM5DH = +0.00000000000000E+000 XMM6DL = +0.00000000000000E+000 XMM6DH = +0.00000000000000E+000 XMM7DL = +0.00000000000000E+000 XMM7DH = +0.00000000000000E+000 XMM00 = +0.00000E+000 XMM01 = +0.00000E+000 XMM02 = +0.00000E+000 XMM03 = +0.00000E+000 XMM10 = +0.00000E+000 XMM11 = +0.00000E+000 XMM12 = +0.00000E+000 XMM13 = +0.00000E+000 XMM20 = +0.00000E+000 XMM21 = +0.00000E+000 XMM22 = +0.00000E+000 XMM23 = +0.00000E+000 XMM30 = +0.00000E+000 XMM31 = +0.00000E+000 XMM32 = +0.00000E+000 XMM33 = +0.00000E+000 XMM40 = +0.00000E+000 XMM41 = +0.00000E+000 XMM42 = +0.00000E+000 XMM43 = +0.00000E+000 XMM50 = +0.00000E+000 XMM51 = +0.00000E+000 XMM52 = +0.00000E+000 XMM53 = +0.00000E+000 XMM60 = +0.00000E+000 XMM61 = +0.00000E+000 XMM62 = +0.00000E+000 XMM63 = +0.00000E+000 XMM70 = +0.00000E+000 XMM71 = +0.00000E+000 XMM72 = +0.00000E+000 XMM73 = +0.00000E+000 MXCSR = 00001F80 ST0 = +0.00000000000000000e+0000 ST1 = +0.00000000000000000e+0000 ST2 = +0.00000000000000000e+0000 ST3 = +0.00000000000000000e+0000 ST4 = +0.00000000000000000e+0000 ST5 = +0.00000000000000000e+0000 ST6 = +0.00000000000000000e+0000 ST7 = +0.00000000000000000e+0000 CTRL = 037F STAT = 0000 TAGS = FFFF EIP = 00000000 CS = 0000 DS = 0000 EDO = 00000000 Disassembly (current location is 00402B90, I've added a few lines before as well). 00402B66 je 00402B90 00402B68 mov ecx,dword ptr [ebp-30h] 00402B6B cmp word ptr [ecx+8],9 00402B70 jle 00402D67 00402B76 mov edi,dword ptr [ebp-30h] 00402B79 mov eax,dword ptr [edi+8] 00402B7C sub eax,3 00402B7F cmp ax,7 00402B83 jbe 00402D5D 00402B89 lea esi,[esi] ---> 00402B90 movzx eax,word ptr [esi+0Ah] 00402B94 dec eax 00402B95 cmp ax,4 00402B99 ja 00402BA5 00402B9B cmp byte ptr [esi+28h],1Bh 00402B9F je 00402D8B 00402BA5 mov eax,dword ptr [ebp-4Ch] 00402BA8 test eax,eax 00402BAA jne 00402BB9 00402BAC mov ecx,dword ptr [ebp-30h] 00402BAF test byte ptr [ecx+1Ch],1 00402BB3 je 004029E2 00402BB9 mov ebx,dword ptr [ebp-30h] 00402BBC mov dword ptr [ebp+8],ebx 00402BBF lea esp,[ebp-0Ch] 00402BC2 pop ebx 00402BC3 pop esi 00402BC4 pop edi 00402BC5 pop ebp 00402BC6 jmp 00406460 00402BCB mov ebx,dword ptr [ebp-30h] 00402BCE movsx edx,word ptr [ebx+8] 00402BD2 cmp dx,9 00402BD6 jg 00402B4E 00402BDC mov eax,dword ptr [esi+18h] 00402BDF cmp eax,dword ptr [ebx+6Ch] 00402BE2 jne 00402BEC 00402BE4 cmp dword ptr [ebx],ebx 00402BE6 je 004031AE 00402BEC mov ebx,dword ptr [ebp-68h] 00402BEF sub esp,4 00402BF2 push ebx 00402BF3 push esi The exception is an access violation. Thanks, - Shai ---------------------------------------------------------------------- Comment By: Ritesh Raj Sarraf (riteshsarraf) Date: 2008-09-16 18:30 Message: I want to close this bug report because I moved to Bridge Mode, where I don't see the crash. Even in slirp mode, this bug is reproducible under heavy load. While I can't define *heavy*, I don't think a lot of people are seeing this bug. So I'm closing it because I can't follow up on this atm. ---------------------------------------------------------------------- Comment By: Ritesh Raj Sarraf (riteshsarraf) Date: 2008-08-18 09:15 Message: Logged In: YES user_id=382018 Originator: YES I just looked into Event Viewer. There is nothing logged related to coLinux. :-( ---------------------------------------------------------------------- Comment By: Ritesh Raj Sarraf (riteshsarraf) Date: 2008-08-18 09:01 Message: Logged In: YES user_id=382018 Originator: YES THank you. I tried that. But Windows didn't allow me to copy paste that particular data. I'll see again to figure out how more info can be extracted. From my use, I can say is that colinux-slirp-daemon.exe is at fault. It keeps crashing very often. The crash is triggered especially when heavy network is done (I can't define how heavy. For me it was just a torrent app with 50-60k bandwidth utilization). Crashes are ugly and bad. So I moved to native coLinux (I was using andLinux). Now, I've configured my network with WinPCAP in Bridged mode. My setup is now running for 12+ hours without any problems. I'm still using the same applications. Hence, I'm sure it is a bug with colinux-slirp-daemon.exe. I'll try to reproduce the bug with the old setup once again and see if I can get the information that you're asking for. And btw, thank you very much for coLinux. It is one great application I can give to my Windows colleagues to enjoy Linux. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-08-17 15:35 Message: Logged In: YES user_id=579204 Originator: NO Hello Ritesh, the files you have send does not help to find the bug. It's a list of files only. We need informations about the crash position in the file, an instruction pointer or current cpu register values. One or more hexadecimal address numbers related to the colinux-slirp-net-daemon. Perhaps you would find such in your Windows event logger. Or, from the window, you have seen the crash, open the option "more details". ---------------------------------------------------------------------- Comment By: Ritesh Raj Sarraf (riteshsarraf) Date: 2008-08-17 12:16 Message: Logged In: YES user_id=382018 Originator: YES File Added: colinux-slirp-daemon-crash.txt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2055697&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-10 20:52:37
|
Bugs item #2013435, was opened at 2008-07-08 14:22 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2013435&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: Fixed Priority: 5 Private: No Submitted By: Adrien Beau (abeau) Assigned to: Henry N. (henryn) Summary: cobd does not work with read-only files Initial Comment: I have created an ISO file with the Windows port of cdrtools, and set it read-only (an old habit). I then tried to mount it in the guest OS (a Slackware 12.1 installation initrd that I patched to include coLinux devices and kernel modules): ~# mount /dev/hdc /cdrom mount: you must specify the filesystem type ~# mount -t iso9660 /dev/hdc /cdrom mount: /dev/hdc: can't read superblock After solving other problems with my hda and hdb devices (it turns out I was trying to use whole-disk images instead of filesystem images) and discovering hdc had a different problem after all, I was a bit lucky to try first to remove the read-only flag from the ISO file in Windows. It solved my problem immediately: ~# mount /dev/hdc /cdrom ~# mount proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) /dev/hdc on /var/log/mount type iso9660 (rw) (Note that in the Slackware installation initrd, /cdrom is a symlink to /var/log/mount.) My configuration, in case I missed a parameter (having read config.c, I doubt it): # --- configuration start --- kernel="C:\Linux\colinux\vmlinux" hda1="C:\Linux\slackware\colinux\slackware-12.1-colinux.partition" hdb1="C:\Linux\slackware\colinux\swap.partition" hdc="C:\Linux\slackware\colinux\install\slackware-12.1.iso" initrd="C:\Linux\slackware\colinux\install\initrd.img" root=/dev/hda1 rw # --- configuration end --- This is a minor bug, but I believe the current behavior should be documented at the very least. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-10 21:52 Message: Will be usable in next release. I close this bug now. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-10-26 23:48 Message: Thanks for this report. Read only mount for such files are supported in next coLinux version now. Committed as SVN revision r1129 for the devel version 0.8.0 and available from next autobuild. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2013435&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-10 20:50:52
|
Bugs item #2077641, was opened at 2008-08-27 08:33 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&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.8.x (devel) >Status: Closed >Resolution: Duplicate Priority: 5 Private: No Submitted By: eugenesan (eugenesan) Assigned to: Nobody/Anonymous (nobody) >Summary: Randoms Windows XPSP3 hangs (ndis-bridge) Initial Comment: Hi, I've noticed that builds created in last several months randomly crashes or hangs my host system. In earlier versions BSOD with linux.sys failure would appear and on builds since ~1/7/2008 Windows just hangs... I must notice that there where also some changes to my host system(not sure if changes and crashes appeared simultaneously): * CPU Pentium M => Core2Duo (IBM T43->T61) * Windows SP2 => SP3 * No other notable changes performed In addition crashes appears regardless usage of: * cobd or scsi * cobd async or sync * pcap-bridnge or ndis-bridge My coLinux starts as service using following command: "C:\Program Files\coLinux\colinux-daemon.exe" --run-service:D:\My Apps\Batch "coLinux" mem=512 kernel="C:\Program Files\coLinux\vmlinux" exec0="D:\My Apps\pulseaudio\pulseaudio.exe" scsi0=disk,"\\.\PhysicalDrive0" cofs0=c:\ cofs1=d:\ root=/dev/sda2 eth1=ndis-bridge,"Local","00:xx:xx:xx:xx:2B" eth2=ndis-bridge,"VirtualCoLinux","00:xx:xx:xx:xx:00" eth3=tuntap,"VirtualCoLinux","00:xx:xx:xx:xx:60" ttys0=COM5,"BAUD=115200 PARITY=n DATA=8 STOP=1 dtr=on rts=on" * cofs almost never used * ttys almost never used, but serial physically hooked to device and probably gets some data on RX once a while. * VirtualCoLinux is coLinux TAP device used both as Host-Only and NAT gateway (I am using VMWARE network stack for NAT/DHCP). * partitions (of course) never cross-mounted * no signs of errors of any kind from linux side(but, maybe, some random networking outages) * Crashes tends to appear only when is xserver running (via freenx). Lately system hangs on almost every X session init :-( I am looking into effective way for debugging that issue and possible suggestions about problems my configuration may have. Thanks ahead ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-10 21:50 Message: Bug #2357595 solves many variants of hanging or freezing PCs. Mostly with network traffic between coLinux and host over ndis-bridge. If will close this bug now. ---------------------------------------------------------------------- Comment By: eugenesan (eugenesan) Date: 2008-10-10 16:43 Message: Hi, I still don't know what was the exact reason for crashes/hangs, but I've found how I can avoid this. First, In configuration I was bridging (pcap or ndis) on tun interface that also was connected to colinux. Second, I was using serial (ttys) feature on USB to RS232 dongle. When I disabled both of mentioned above, the problem disappeared. At the moment it runs for more then a week without a sign of problem. I don't know if binding network interfaces to the same source may couse any problems. But I think serial emulation can be a problem in my case, since I am using it on laptop and USB dongle with serial port comes and goes at least once a day. BTW: I am using latest testing build 20080923. Thank you for help. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-09-07 16:50 Message: Logged In: YES user_id=579204 Originator: NO Hello Eugenesan, VDSO needs to telling the glibc how to make a syscall. With vdso=0 on startup or with write 0 to vdso_enabled, the VDSO page is no loger fix mapped on ffffe000 (see http://www.trilithium.com/johan/2005/08/linux-gate/) - it goes to randomly virtual address. Debian 4 has problems, if I boot with vdso=1 (coLinux default) and write 0 later. The current terminal kills the INIT task. Linux can not shutdown. The other consoles (tty1, tty2, ...) are still running. I can boot all my distries (SuSE 9.0, Debian 3.0, Debian 4.0) with boot parameter vdso=0. Of curse, if I boot with 0, there is no problem with write 0 to vdso_enabled. vdso=0 is the default config for x86 Kernels ("CONFIG_COMPAT_VDSO is not set"). Can we set vdso=0 as coLinux default now? I think yes. Anybody can test this with boot parameter "vdso=0". By the while have enabled the feature for sysenter and sysexit (SEP). All current cpus would have this feature. This has also something to do with the VDSO. Eugenesan, please try this build and boot with vdso=0 and lets write to vdso_enabled. This should run without problems. Second, please test with parameter vdso=1 (or without this) and lets write 0 to vdso_enabled. Is this crashing? New Snapshot exist on http://www.colinux.org/snapshots/ PS: Before you risk losing data from crash tests, it's good idea to SYNC all data to harddisk before runs colinux-daemon. I have this in my batch files for testings now: http://technet.microsoft.com/en-us/sysinternals/bb897438.aspx Henry ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-08-30 19:50 Message: Logged In: YES user_id=579204 Originator: NO Ah, thanks. Very good detection. Default for Linux VDSO is disabled. I know, that my coLinux SuSE 9.0 hangs, if VDSO is disabled in kernel config. I have explicitly enabled VDSO compatibility in the config. But, I was not thinking about a User or Distry would disable this at runtime. If that helps: It would be easy for coLinux kernel code, to make /proc/sys/vm/vdso_enabled read only. ;-) Of curse, you can run "colinux-debug-daemon.exe -d -p -s prints=31,misc=31 ..." on a command prompt, before you starts the service from Windows control applet. The parameter "misc=31" there is the same as you would run "colinux-daemon -v 31 ..." ---------------------------------------------------------------------- Comment By: eugenesan (eugenesan) Date: 2008-08-30 16:25 Message: Logged In: YES user_id=1010208 Originator: YES Boot-up problems solved, "echo 0 > /proc/sys/vm/vdso_enabled" hangs coLinux. Hope my software will survive that... Can I enable debug when starting daemon as service? ---------------------------------------------------------------------- Comment By: eugenesan (eugenesan) Date: 2008-08-30 14:49 Message: Logged In: YES user_id=1010208 Originator: YES Hi, After reboot debug started to work. Digging in... ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-08-30 13:54 Message: Logged In: YES user_id=579204 Originator: NO Debugging.txt is up to date. The last you will find here: http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging To catch some from crashing, the debug-daemon often can't help. To trace such, needs to put some debugging into the scripts inside the distribution. You say, that it is a problem in runlevel 2, then try to trace the steps between runlevel 1 and 2. Run you system with runlevel 1 ("init 1") in the coLinux boot parameter. Add 'set -x' in the top of the script for runlevel switching code. Than switch with command 'init 2' on Linux prompt to next runlevel, For me it is the file /etc/init.d/rc under SuSE. Good idea is also to put 'echo "$0 $service start ..."; sleep 3' into the inner of the for-loop before execute the next script (ones of /etc/init.d/rc2.d/S##...), to see what script will be start as next. - The loop what is locate the K## and S## to start/stop actions. Some distributions have a special environment in the rc scripts to enable a verbose mode. This is in my script for trace boot steps: blogger "$service start" echo "$0 $service start ..."; sleep 3 ### Trace: inserted for coLinux debugging ### $i start; status=$? Henry ---------------------------------------------------------------------- Comment By: eugenesan (eugenesan) Date: 2008-08-30 13:08 Message: Logged In: YES user_id=1010208 Originator: YES Hi Henry, Thanks for reply. I do use version you are proposing and still experiencing crashes. In addition my system currently do not pass switching to runlevel 2, I've even reinstalled the whole distribution. Probably something changed in distribution's updated packages, because it was working for months... About debugging, I have hard times enabling it. Adding -v # makes no change, debug daemon outputs nothing. Is debugging.txt is outdated or I am missing something? Thanks ahead Eugene ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-08-29 20:35 Message: Logged In: YES user_id=579204 Originator: NO Hello Eugenesan, have you checked the last build from http://www.colinux.org/snapshots/ from 23-Aug-2008? I ask, because all versions before this snapshot have memory leakages and race conditions in the interrupt handler. I found they by heavy network checks with the ndis-bridge and the tool "netio". The last version was running without problems over many hours. Some more details you can read from "Recent ChangeLog", the revisions from r1114 and r1118 can also be fixed the problem, you described here. For debugging, run the command line you have posted from Windows prompt without the parameter "--run-service:" and add the parameter "-v 3" instead (Verbose). A small bug I see: Path parameter is broken from space in "My Apps". Is harmless, because you you have full paths for all files there. Henry ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-10 20:47:57
|
Bugs item #2042470, was opened at 2008-08-08 04:56 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2042470&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.8.x (devel) >Status: Closed >Resolution: Duplicate Priority: 5 Private: No Submitted By: Xuefer (xuefer) Assigned to: Nobody/Anonymous (nobody) Summary: 0.8.0-20080803 pcap/ndis-bridge stop working after hours Initial Comment: after some hours i fond that ndis-bridge stop working, the process is still there but ping timeout network interface on xp: Bridge [ lan, lo ] gentoo config: eth0=ndis-bridge,lo,00:ff:4f:0d:e7:c0 other information is same as in: http://sourceforge.net/tracker/index.php?func=detail&aid=1952057&group_id=98788&atid=622063 ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-10 21:47 Message: Bug #2357595 solves the problem with ndis. The bugs was happen mostly, for pings on fast network cards or to the host. Mostly, if packets does not need to send over the line (internal loopback without hardware delays). I close this bug now. ---------------------------------------------------------------------- Comment By: Xuefer (xuefer) Date: 2008-08-12 19:22 Message: Logged In: YES user_id=185131 Originator: YES reproduced with pcap again now. be aware that its Bridge [ lan, lo ], and i pcap/ndis-bridge on "lo". i can pcap-bridge but not ndis-bridge on Bridge, "lo" is the only chance to use ndis-bridge for me. ---------------------------------------------------------------------- Comment By: Xuefer (xuefer) Date: 2008-08-12 15:55 Message: Logged In: YES user_id=185131 Originator: YES i thought i had a reason why i was using Bridge instead of lo interface for pcap-bridge (and now ndis-bridge). i remember now. it's because exact the same problem as this ticket. a. IIRC, with pcap-bridge, when it "stopped" working, i ping windows (host) from gentoo linux (colinux guest) and it starts working again. i'm not sure if this is a "windows bridge" problem or just a "colinux with windows bridge" problem b. current test result with ndis-bridge, when it "stopped" working i can ping router from host and from guest, but not ping/tcp between host<->guest however arp works for host<->guest Network Configuration: Bridge --- WAN ----(connected to)---> router \--------- lo ---(ndis bridge)-------> colinux ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-08-10 22:40 Message: Logged In: YES user_id=579204 Originator: NO Is fixed in SVN revision 1106. Please download the latest version (devel-20080810) from snapshots http://www.colinux.org/snapshots/ ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-08-09 19:40 Message: Logged In: YES user_id=579204 Originator: NO Thanks for the entry here and in bug #1952057. It is a memory leakage in kernel memory. I can reproduce it with netio. Download netio*.zip from http://www.ars.de/ars/ars.nsf/docs/netio Copy the file linux-i386 into coLinux. Run "netio -s" on a server, or perhaps on a windows host. Run this line in coLinux: # while true; do ./netio -b 2k -u 192.168.2.102; sleep 5; done Now, watch Windows Taskmanager in section "Kernel-memory (KB)" the value for "Total". For pcap-bridge the memory goes up to +60MB over normal and it goes down at the "sleep 5". For ndis-bridge the memory incrased +6MB on every test loop. WARNING! 1. pcap-bridge crashes, if it receives 4KB segemnts. That's why I tested with parameter "-b 2k". This is perhaps an other problem. 2. After longer running ndis-bridge Windows have problems on storing files, and can crash on shutdown. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2042470&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-10 20:42:56
|
Bugs item #1952057, was opened at 2008-04-26 04:52 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1952057&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.8.x (devel) >Status: Closed >Resolution: Duplicate Priority: 5 Private: No Submitted By: Xuefer (xuefer) Assigned to: Nobody/Anonymous (nobody) Summary: 0.8.0-20080420 ndis-bridge hang system Initial Comment: config gentoo.txt: kernel=vmlinux mem=256 # the old one which is ok # eth0=pcap-bridge,Bridge,00:ff:4f:0d:e7:c0 # the new one which hang eth0=ndis-bridge,Bridge,00:ff:4f:0d:e7:c0 root=/dev/sda3 sda2=\Device\Harddisk1\Partition2 sda3=\Device\Harddisk1\Partition3 sda5=\Device\Harddisk1\Partition4 cofs0=\DosDevices\c:\app\system\colinux\ cofs1=\DosDevices\c:\ cofs2=\DosDevices\d:\ cofs3=\DosDevices\e:\ bootlevel=c.boot softlevel=c.default setcobd=async "Bridge" is an windows xp bridge interface that bridge 2 of my interfaces, WAN (which is a real eth card) and lo (loopback virtual device). i use bridge because i want to "interface down" issue when the wire is unplugged from eth card, since lo is always up so "Bridge" will be up too. when i do "net start gentoo" (colinux), it boots nicely but as soon as it reach one of the init.d script (/etc/init.d/net.eth0, i guess), the whole box become slower and slower, any windows becomes not responding, and lastly only mouse pointer is active, i have to reset the box ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-10 21:42 Message: Crashing ndis was fixed in Bug #2357595, and committed to SVN as revision r1218. Feel free to reopen this bug, if it not solved the problem here. ---------------------------------------------------------------------- Comment By: Xuefer (xuefer) Date: 2008-08-11 06:15 Message: Logged In: YES user_id=185131 Originator: YES colinux config file: kernel=vmlinux mem=256 #video0=4 #eth0=pcap-bridge,ADSLModem #eth1=tuntap,coeth1 #eth0=pcap-bridge,lo,00:ff:4f:0d:e7:c0 eth0=ndis-bridge,Bridge,00:ff:4f:0d:e7:c0 root=/dev/sda3 sda2=\Device\Harddisk1\Partition2 sda3=\Device\Harddisk1\Partition3 sda5=\Device\Harddisk1\Partition4 cofs0=\DosDevices\c:\app\system\colinux\ cofs1=\DosDevices\c:\ cofs2=\DosDevices\d:\ cofs3=\DosDevices\e:\ bootlevel=c.boot softlevel=c.default setcobd=async ---------------------------------------------------------------------- Comment By: Xuefer (xuefer) Date: 2008-08-11 06:10 Message: Logged In: YES user_id=185131 Originator: YES still reproduced in 0.8.0-20080810 CPU: AMD Athlon(tm) 64 X2 Dual MEM: 2G (128M shared with nvidia geforce 6150SE on board) System: Windows XP Pro SP3 with latested patches ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-08-10 23:54 Message: Logged In: YES user_id=579204 Originator: NO The title problem and "box become slower and slower" was solved as memory leakage and is fixed in todays snapshot. I can use ndis-bridge on a Windwos-Bridged network. The only difference I can see, is that a Windows-Bridge is slower as direct Ethernet adapter. Please check it again with the latest version. ---------------------------------------------------------------------- Comment By: Xuefer (xuefer) Date: 2008-08-07 08:45 Message: Logged In: YES user_id=185131 Originator: YES about the network latency and slow samba: c:\> ping router ... Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 ... **** ping latency with pcap-bridge c:\> ping colinux ... Reply from 192.168.0.3: bytes=32 time=15ms TTL=64 Reply from 192.168.0.3: bytes=32 time=16ms TTL=64 ... see? colinux on the same box as my windows xp has higher latency than a real network adapter on wire. *** samba latency with pcap-bridge it took me's 5 seconds to open \\gentoo\etc\ and when i drag the scroll bar down, it take some seconds to get it display because windows explorer is requesting for more data from samba but colinux network has high latency **** was using ndis-bridge c:\> ping colinux ... Reply from 192.168.0.3: bytes=32 time<1ms TTL=64 ... cool, as fast as a real interface *** samba latency with pcap-bridge just seems as fast as a another real matchin that run linux serving samba, no latency thanks for the great work on ndis-bridge ---------------------------------------------------------------------- Comment By: Xuefer (xuefer) Date: 2008-08-07 08:35 Message: Logged In: YES user_id=185131 Originator: YES still reproduced in 0.8.0-20080803 i was about to file a bug claim that colinux network latency is high and make samba slow but i found a workaround to this bug. pcap based config that working fine: eth0=pcap-bridge,Bridge,00:ff:4f:0d:e7:c0 ndis based config that hang: eth0=ndis-bridge,Bridge,00:ff:4f:0d:e7:c0 ndis based config that workaround: eth0=ndis-bridge,lo,00:ff:4f:0d:e7:c0 so pcap-bridge will work on Bridge interface (and maybe "lo" interface, not tested) but ndis-bridge will hang when using Bridge interface can u pls fix it? either disallow user to use bridge interface or fix the problem ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1952057&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-10 20:38:17
|
Bugs item #1834295, was opened at 2007-11-19 02:35 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1834295&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.8.x (devel) >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Henry N. (henryn) Summary: devel-20071110 restart instancely Initial Comment: i've just downloaded latest version from http://www.henrynestler.com/colinux/autobuild/devel-20071110/, when i do "net start gentoo" and my winxpsp2 restart immediately host system: winxpsp2 with all latest patches installed hd: sata guest system: gentoo, but it restart before it gets to init i guess host mem: 2G total - 128M video mem guest mem: 256M i'm out of idea on writing the report, what else info should i write here? ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-10 21:38 Message: think it's time to close this now. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-04-26 04:45 Message: Logged In: NO i'm not sure why would i "mixed the versions", isn't colinux driver installer supposed to detect the installtion failure/success to avoid mixing? i tried a clean restart of windows xp, remove the driver and reinstall it, it seems work. i'm not really sure what had happened. it would be nice if colinux do a check and ensure everything is after driver/daemon installtion, and before starting up itself ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-04-17 00:05 Message: Logged In: YES user_id=579204 Originator: NO Fixed in 0.7.3 RC3 and snapshot devel 0.8.0-20080415, http://www.colinux.org/snapshots/ ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-01-06 18:40 Message: Logged In: YES user_id=579204 Originator: NO Some notes about debugging and my no longtime existing links. The build 20071219-hostmem-debug should not use, I will remove this next times. All things are added at this build: http://www.henrynestler.com/colinux/autobuild/devel-20071221/ Full text "how to debug colinux" is this here: http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/doc/debugging Not need full memory dumps. Small minidumps (64KB) are good enough for debugging. If you have a second PC: DbgView and colinux-debug-daemon works also over network. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-05 18:02 Message: Logged In: NO stuck at "service local starting" (gentoo) is a gentoo + kernel issue, not colinux issue as i can reproduce it without colinux with new kernel version as in colinux. i found the options in Systemsettings, and it was configured to dump but there was no dump. and i didn't see any BSOD before it restart. i'll try anyway ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-05 17:54 Message: Logged In: NO Try to use less guest memroy, say 63MB ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-05 17:45 Message: Logged In: NO Do you have any entries in the XP eventlog arround the reboot? Could you forbit XP to do a restart but display the BSOD and to write a full memory dump? (Somewhere in "Systemsettings") How many "kernel memory" does sysmon show? What happens if you launch it directly via commandline, and not as system service? If you like, you migh try to use the windows kernel debug version. there is a little text "how to debug colinux" http://www.henrynestler.com/colinux/testing/devel-0.8.0/20071219-hostmem-debug/readme.txt ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-05 17:41 Message: Logged In: NO Do you have any entries in the XP eventlog arround the reboot? Could you forbit XP to do a restart but display the BSOD and to write a full memory dump? (Somewhere in "Systemsettings") How many "kernel memory" does sysmon show? What happens if you launch it directly via commandline, and not as system service? If you like, you migh try to use the windows kernel debug version. there is a little text "how to debug colinux" http://www.henrynestler.com/colinux/testing/devel-0.8.0/20071219-hostmem-debug/readme.txt ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-05 16:38 Message: Logged In: NO devel-0.8.0/20071105-Snapshot is the same and devel-20071221/ won't restart instancely but stuck at "service local starting" (gentoo), possible due to iptables initialize incompletely issue. and FYI: stable-0.7.2/20071218-Snapshot will restart instancely ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-11-28 20:32 Message: Logged In: YES user_id=579204 Originator: NO Not need to test all the autobuilds. Autobuilds are currently in moving and very unstable. devel-20071108 and later was build on a 64 bit platform. I'm not sure about side effects there. Yust try the snapshot 20071105. This was build more saver from my devolopment build. This is the current good tested devel version. Zip files of that version will find in packages on http://www.henrynestler.com/colinux/testing/devel-0.8.0/20071105-Snapshot/ ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-11-28 07:31 Message: Logged In: NO but anyway, i'll try other tips you gave that i've not tried yet, including the initrd and give u feedback later ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-11-28 07:26 Message: Logged In: NO i was using devel 0.8.0 too but forgot which date (about months ago) i grab from your autobuild and i'm sure i could uninstall/install correctly for 0.6.x-release 0.7.x -auto-build-or-release 0.8.x-old-autobuild previously, and i could switch between them, but just not this with devel-20071110 (though i've not tested all devel 0.8.x devel-2007* yet). i have a script that remove service/driver every time before i switch, and install them after. i do not use initrd since when the i began to use coliunx, developers suggested me to disable it for one of the boot problem for me. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-11-19 20:27 Message: Logged In: YES user_id=579204 Originator: NO I'm afraid, you starts an mixed old and new version. What version have before the update? Go into Windows service control center and check the properties of "gentoo". Is the path to colinux-daemon.exe right? >From some older versions (0.6.x) you MUST create new the entry for running as service (--remove-service/--install-service). If the path was changed on update, you must create new the service. Check an minimalistig ramdisk running. The ramdisk is also included in the installer. Download http://www.henrynestler.com/colinux/tools/initrd-20060831.gz Create a batch and start it: colinux-daemon kernel=vmlinux initrd=initrd-20060831.gz root=/dev/ram0 This should give an Linux prompt. Try to savely installing it: - Remove the driver colinux-daemon.exe --remove-driver - Reboot WinXP - Check, that the driver is not installed: colinux-daemon.exe --status-driver This should give an error. - Install the driver colinux-daemon.exe --install-driver ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1834295&group_id=98788 |
|
From: coLinux a. <col...@he...> - 2009-02-10 05:07:02
|
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-20090210/ colinux-0.8.0-20090210.src.tgz (684970 Bytes) daemons-0.8.0-20090210.dbg.zip (591660 Bytes) daemons-0.8.0-20090210.zip (478680 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-20090205/ 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 ------------------------------------------------------------------------ r1218 | henryn | 2009-02-10 01:38:31 +0000 (Tue, 10 Feb 2009) | 2 lines Changed paths: M /branches/devel/src/colinux/os/winnt/kernel/conet.c * Bug#2357595: Bugfix ndis-bridge, hangs PC while ping the host ip. co_conet_proto_send_complete() was called with wrong parameter. ------------------------------------------------------------------------ |
|
From: SourceForge.net <no...@so...> - 2009-02-10 04:08:02
|
Bugs item #2445837, was opened at 2008-12-18 19:07 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2445837&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.8.x (devel) >Status: Pending >Resolution: Duplicate Priority: 5 Private: No Submitted By: Xuefer (xuefer) Assigned to: Henry N. (henryn) Summary: colinux+ndis-bridge hang with vbox 2.1 Initial Comment: Virtualbox version: VirtualBox-2.1.0-41146-Win_x86.msi (got from http://www.filehippo.com/download_virtualbox/ same file as official though) colinux version: 0.8.0-20080924, 0.8.0-20081212 windows version: xp with all SP/hotfix patched guest os: gentoo configuration: ======== kernel=vmlinux mem=512 video0=4 kernel=vmlinux mem=512 video0=4 #eth0=pcap-bridge,ADSLModem #eth1=pcap-bridge,coLinux,00:ff:4f:0d:e7:c0 eth1=ndis-bridge,coLinux,00:ff:4f:0d:e7:c0 root=/dev/sda3 sda2=\Device\Harddisk1\Partition2 sda3=\Device\Harddisk1\Partition3 sda5=\Device\Harddisk1\Partition4 cofs0=\DosDevices\c:\app\system\colinux\ cofs1=\DosDevices\c:\ cofs2=\DosDevices\d:\ cofs3=\DosDevices\i:\ cofs4=\DosDevices\g:\ bootlevel=c.boot softlevel=c.default setcobd=async ========= it used to work when i have virtualbox VirtualBox-2.0.6-39760-Win_x86.msi installed. but when i upgrade virtualbox to 2.1.0-41146-Win_x86, colinux network stopped working. i restart colinux and the whole system just stuck there, no keyb/mouse response. this is a ndis-bridge specified problem again. works fine with pcap-bridge to reproduce it 1. install colinux, configure with ndis-bridge 2. install VirtualBox-2.1.0-41146-Win_x86.msi (just install, no need to run it) 3. start colinux i guess it's relatived to the driver (filter?) vbox2.1 installed for each network adapter: VBoxNetFlt Driver, VirtualBox Host Interface Networking Driver ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-10 02:49 Message: I feel, it is the same problem as in Bug #2357595. We have fixed a wrong parameter for packet injection, that freeze the host. Please test with a build from SVN revision r1218 or later. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-01-21 02:26 Message: The date means I checkout latest SVN code and rebuild in this day. I have been re-patch kernel(I do not rebuild compiler, FLTK, etc). then do "--remove-driver" and "--install-driver" also. I must go home tomorrow, I will recheck my build next month. btw: I upgrade my cross-GCC to 4.2.4, the build 20081209 & 20090105 both compile with it. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-01-19 22:47 Message: Hello, with the "win2k sp4", can you please check on what revision does start exactly the problem. Between 20081209 and 20090105 have many small changes, and for date 2008-12-09 I can not find any change in changelog (http://www.colinux.org/snapshots/devel-ChangeLog). You will find some older binaries and sources under http://www.henrynestler.com/colinux/autobuild/ If you have self build coLinux: Remember that you need to re-patch and re-build the kernel, if any of the files are changed in directory "patch/*.diff", and be sure to have called "--remove-driver" and "--install-driver" while coLinux is not running. If you build coLinux from source, you can use "svn update rNNNN" with any revision number NNNN, to find the exactly revision number what does create the "halt" problem. Use initrd, to avoid loosing data on your filesystem. For example: colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0 eth1=ndis-bridge,"LAN" ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-01-19 06:16 Message: Yes, I got this bug also. I build colinux myself, I build about every two weeks. My compute run win2k sp4, the colinux build at 20081209 can be work fine, but 20090105 and later wrong. I can boot the colinux and do any works. but when I 'halt' the linux, the colinux-ndis-net-daemon.exe can not stop, it will hang my computer, I can not open any program, can not reboot. I must turn off(or hard-reset) my computer to continue. ---------------------------------------------------------------------- Comment By: Xuefer (xuefer) Date: 2008-12-18 19:12 Message: network adapters: 1. WAN: nvidia nforce 10/100/1000Mbps Ethernet (i don't think it relatived to this problem) 2. coLinux: Microsoft Loopback Adapter i just found a workaround 1. right click "coLinux" adapter 2. uncheck "VirtualBox Host Interface Networking Driver" press OK ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2445837&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-10 03:52:11
|
Bugs item #2445837, was opened at 2008-12-19 02:07 Message generated for change (Settings changed) made by xuefer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2445837&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.8.x (devel) >Status: Closed Resolution: Duplicate Priority: 5 Private: No Submitted By: Xuefer (xuefer) Assigned to: Henry N. (henryn) Summary: colinux+ndis-bridge hang with vbox 2.1 Initial Comment: Virtualbox version: VirtualBox-2.1.0-41146-Win_x86.msi (got from http://www.filehippo.com/download_virtualbox/ same file as official though) colinux version: 0.8.0-20080924, 0.8.0-20081212 windows version: xp with all SP/hotfix patched guest os: gentoo configuration: ======== kernel=vmlinux mem=512 video0=4 kernel=vmlinux mem=512 video0=4 #eth0=pcap-bridge,ADSLModem #eth1=pcap-bridge,coLinux,00:ff:4f:0d:e7:c0 eth1=ndis-bridge,coLinux,00:ff:4f:0d:e7:c0 root=/dev/sda3 sda2=\Device\Harddisk1\Partition2 sda3=\Device\Harddisk1\Partition3 sda5=\Device\Harddisk1\Partition4 cofs0=\DosDevices\c:\app\system\colinux\ cofs1=\DosDevices\c:\ cofs2=\DosDevices\d:\ cofs3=\DosDevices\i:\ cofs4=\DosDevices\g:\ bootlevel=c.boot softlevel=c.default setcobd=async ========= it used to work when i have virtualbox VirtualBox-2.0.6-39760-Win_x86.msi installed. but when i upgrade virtualbox to 2.1.0-41146-Win_x86, colinux network stopped working. i restart colinux and the whole system just stuck there, no keyb/mouse response. this is a ndis-bridge specified problem again. works fine with pcap-bridge to reproduce it 1. install colinux, configure with ndis-bridge 2. install VirtualBox-2.1.0-41146-Win_x86.msi (just install, no need to run it) 3. start colinux i guess it's relatived to the driver (filter?) vbox2.1 installed for each network adapter: VBoxNetFlt Driver, VirtualBox Host Interface Networking Driver ---------------------------------------------------------------------- >Comment By: Xuefer (xuefer) Date: 2009-02-10 11:51 Message: i can confirm it fixed. thanks ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-02-10 09:49 Message: I feel, it is the same problem as in Bug #2357595. We have fixed a wrong parameter for packet injection, that freeze the host. Please test with a build from SVN revision r1218 or later. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-01-21 09:26 Message: The date means I checkout latest SVN code and rebuild in this day. I have been re-patch kernel(I do not rebuild compiler, FLTK, etc). then do "--remove-driver" and "--install-driver" also. I must go home tomorrow, I will recheck my build next month. btw: I upgrade my cross-GCC to 4.2.4, the build 20081209 & 20090105 both compile with it. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-01-20 05:47 Message: Hello, with the "win2k sp4", can you please check on what revision does start exactly the problem. Between 20081209 and 20090105 have many small changes, and for date 2008-12-09 I can not find any change in changelog (http://www.colinux.org/snapshots/devel-ChangeLog). You will find some older binaries and sources under http://www.henrynestler.com/colinux/autobuild/ If you have self build coLinux: Remember that you need to re-patch and re-build the kernel, if any of the files are changed in directory "patch/*.diff", and be sure to have called "--remove-driver" and "--install-driver" while coLinux is not running. If you build coLinux from source, you can use "svn update rNNNN" with any revision number NNNN, to find the exactly revision number what does create the "halt" problem. Use initrd, to avoid loosing data on your filesystem. For example: colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0 eth1=ndis-bridge,"LAN" ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-01-19 13:16 Message: Yes, I got this bug also. I build colinux myself, I build about every two weeks. My compute run win2k sp4, the colinux build at 20081209 can be work fine, but 20090105 and later wrong. I can boot the colinux and do any works. but when I 'halt' the linux, the colinux-ndis-net-daemon.exe can not stop, it will hang my computer, I can not open any program, can not reboot. I must turn off(or hard-reset) my computer to continue. ---------------------------------------------------------------------- Comment By: Xuefer (xuefer) Date: 2008-12-19 02:12 Message: network adapters: 1. WAN: nvidia nforce 10/100/1000Mbps Ethernet (i don't think it relatived to this problem) 2. coLinux: Microsoft Loopback Adapter i just found a workaround 1. right click "coLinux" adapter 2. uncheck "VirtualBox Host Interface Networking Driver" press OK ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2445837&group_id=98788 |
81 messages has been excluded from this view by a project administrator.
