Custom Search
|
Date: September 25, 2006
From: Henry Nestler <Henry.Ne@xxxxxxxx>
In-reply-to:
<026F8EEDAD2C4342A993203088C1FC050388A0FD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References:
<026F8EEDAD2C4342A993203088C1FC050388A0FD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Hello Nazarianin, Anders Eriksson C (KI/EAB) wrote: >>> Do you get: >>> $ gzcat /proc/config.gz | grep HOTPLUG >>> CONFIG_HOTPLUG=y >> >> Gentoo-CoLinux ~ # gzcat /proc/config.gz | grep HOTPLUG >> # CONFIG_HOTPLUG is not set >> > > Thanks, > > Let's see if we can get a new .15 out the door. I'm sorry. Have not enable this in all. 2.6.12 : # CONFIG_HOTPLUG is not set 2.6.13 : # CONFIG_HOTPLUG is not set 2.6.14 : # CONFIG_HOTPLUG is not set 2.6.15 : # CONFIG_HOTPLUG is not set 2.6.17 : CONFIG_HOTPLUG=y A other snapshot I have: http://www.henrynestler.com/colinux/testing/devel-2.6.17-hn/20060924/ * Known bugs for kernel 2.6.15 and 2.6.17: - Hostsystem (Windows XP) freezes some times after shutdown linux (no keyboard, no mouse). -- Henry Nestler ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: September 25, 2006
From: "Anders Eriksson C (KI/EAB)" <anders.c.eriksson@xxxxxxxxxxxx>
In-reply-to:
<130500333.20060925182826@xxxxxxxxxx>
References:
<130500333.20060925182826@xxxxxxxxxx>
> > > Do you get: > > > $ gzcat /proc/config.gz | grep HOTPLUG > > CONFIG_HOTPLUG=y > > > Gentoo-CoLinux ~ # gzcat /proc/config.gz | grep HOTPLUG > # CONFIG_HOTPLUG is not set > Thanks, Let's see if we can get a new .15 out the door. /A ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: September 25, 2006
From: nazarianin2000@xxxxxxxxxx
In-reply-to:
<026F8EEDAD2C4342A993203088C1FC0503889FCC@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References:
<1273531422.20060925153159@xxxxxxxxxx> <026F8EEDAD2C4342A993203088C1FC0503889FCC@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
> Do you get:
> $ gzcat /proc/config.gz | grep HOTPLUG
> CONFIG_HOTPLUG=y
Gentoo-CoLinux ~ # gzcat /proc/config.gz | grep HOTPLUG
# CONFIG_HOTPLUG is not set
--
Best regards,
Aleksey Leonov
mailto:nazarianin2000@xxxxxxxxxx
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: September 25, 2006
From: "Anders Eriksson C (KI/EAB)" <anders.c.eriksson@xxxxxxxxxxxx>
In-reply-to:
<1273531422.20060925153159@xxxxxxxxxx>
References:
<1273531422.20060925153159@xxxxxxxxxx>
> I don`t have experience in Linux. I use Gentoo in Colinux. When > CoLinux start i see error in /lib/rcscripts/addons/udev-start.sh in > line 46. I correct 2.6.15 to 2.6.17 in script and have all cobd in > /dev. > if [ "$(get_KV)" -gt "$(KV_to_int '2.6.17')" ] ; then > ebegin "Populating /dev with existing devices > through uevents" > trigger_events > eend 0 > else > ebegin "Populating /dev with existing devices > with udevstart" > /sbin/udevstart > eend 0 > fi > > CoLinux work good now. > Ok (running gentoo myself). That's a good indication that the kernel you use doesn't have hotplug in it. Do you get: $ gzcat /proc/config.gz | grep HOTPLUG CONFIG_HOTPLUG=y If not. That's the culpit. Henry: If this is the issue here, could you respin the 2.6.15 kernel? Getting even static /dev entries up in >=2.6.15 requires hotplug if you use udevd. /Anders ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: September 25, 2006
From: nazarianin2000@xxxxxxxxxx
In-reply-to:
<026F8EEDAD2C4342A993203088C1FC05038898E5@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References:
<109564182.20060923115401@xxxxxxxxxx> <026F8EEDAD2C4342A993203088C1FC05038898E5@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
>> I install snapshot 0.8.0 with kernel 2.6.15 and have trouble. I
>> have not cobd* devices in /dev. Previous i use 2.6.12-co-0.7.1
>> colinux.
>>
> Do you have all other normal entries in /dev, or is it close to empty?
> If it's nerely emty, it might be because udev wants hotplug in >=2.6.15
> kernels. I'm not sure if the distributed 2.6.15 has hotplug complied in
> (you can check that by peeking at /proc/config.gz).
I don`t have experience in Linux. I use Gentoo in Colinux. When
CoLinux start i see error in /lib/rcscripts/addons/udev-start.sh in
line 46. I correct 2.6.15 to 2.6.17 in script and have all cobd in
/dev.
if [ "$(get_KV)" -gt "$(KV_to_int '2.6.17')" ] ; then
ebegin "Populating /dev with existing devices through uevents"
trigger_events
eend 0
else
ebegin "Populating /dev with existing devices with udevstart"
/sbin/udevstart
eend 0
fi
CoLinux work good now.
Nazarianin.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: September 24, 2006
From: "Anders Eriksson C (KI/EAB)" <anders.c.eriksson@xxxxxxxxxxxx>
In-reply-to:
<109564182.20060923115401@xxxxxxxxxx>
References:
<109564182.20060923115401@xxxxxxxxxx>
> > Hello > > > snapshot with kernel 2.6.15 is available as Installer: > > I install snapshot 0.8.0 with kernel 2.6.15 and have trouble. I > have not cobd* devices in /dev. Previous i use 2.6.12-co-0.7.1 > colinux. > Do you have all other normal entries in /dev, or is it close to empty? If it's nerely emty, it might be because udev wants hotplug in >=2.6.15 kernels. I'm not sure if the distributed 2.6.15 has hotplug complied in (you can check that by peeking at /proc/config.gz). /Anders ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: September 23, 2006
From: Martin Afanasjew <martin-lists@xxxxxxxxxxxx>
In-reply-to:
<4514404A.6050005@xxxxxxxxxxxx>
References:
<4512FD8F.30003@xxxxxxxx> <4514404A.6050005@xxxxxxxxxxxx>
Martin Afanasjew wrote: > However, I tried the new snapshot after having used 0.7-hn14 (20060417) > for several months. <snip> I used 0.7.1-hn13 (20060417). Sorry for the wrong information. Regards, Martin ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: September 23, 2006
From: "SourceForge.net" <noreply@xxxxxxxxxxxxxxx>
Bugs item #1396459, was opened at 2006-01-03 17:27 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1396459&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: Rejected Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: coLinux Error 88054c01 Initial Comment: I am getting this error when I try to run coLinux 0.6.2 exit code 88054c01 error - CO_RC_ERROR_ERROR, line 339, file colinux/user/config.o (64) ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-09-22 23:05 Message: Logged In: NO The following suggestion resulted in a login prompt. BSOD, usually means you need to modify the boot.ini with /NoExecute=AlwaysOff as a workaround for a bug with DEP on modern CPUs. Thank you gboutwell! The fix was not as painful as was expected. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2006-09-13 03:29 Message: Logged In: YES user_id=579204 : <initrd path="initrd" /> : <bootparams>root=/dev/cobd0 devfs=mount,dall : ramdisk_size=8192 </bootparams> In config found an external bigger initrd file. This let me think it's from a distribution with non colinux kernel binaries. ---------------------------------------------------------------------- Comment By: George P Boutwell (gboutwel) Date: 2006-09-10 18:10 Message: Logged In: YES user_id=30412 Has this issue been resolved? ---------------------------------------------------------------------- Comment By: George P Boutwell (gboutwel) Date: 2006-05-12 21:00 Message: Logged In: YES user_id=30412 CO_RC_ERROR_ERROR usually means config (usually a path or file name) is wrong. BSOD, usually means you need to modify the boot.ini with /NoExecute=AlwaysOff as a workaround for a bug with DEP on modern CPUs. ---------------------------------------------------------------------- Comment By: SiMechanic (grhaag) Date: 2006-03-28 22:17 Message: Logged In: YES user_id=1486137 I've only tried 0.6.3. Downloaded and reinstalled using a different bzip2 tool. Downloaded another debian filesystem. Got the same message. Disabled the swap file by changing the enable="true" to "false". This resulted in the blue-screen-of-death with a DRIVER_IRQL_NOT_LESS_OR_EQUAL message. xxx step:0x000000D1 (0xf11cc01c, 0x000000ff, 0x00000008, 0xf11cc01c). Checked the files in the default xml file in a dos window. ---- start of debug log C:\coLinux>type Debug.log Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\>dir c:\coLinux\Debian-3.0r2.ext3-mit-backports.1gb Volume in drive C is WinXP Volume Serial Number is B4BA-6703 Directory of c:\coLinux 03/25/2006 11:01 AM 1,073,741,824 Debian-3.0r2.ext3-mit-backports.1gb 1 File(s) 1,073,741,824 bytes 0 Dir(s) 61,033,480,192 bytes free C:\>dir c:\coLinux\swap_128Mb Volume in drive C is WinXP Volume Serial Number is B4BA-6703 Directory of c:\coLinux 03/25/2006 01:59 PM 134,217,728 swap_128Mb 1 File(s) 134,217,728 bytes 0 Dir(s) 61,033,480,192 bytes free C:\>cd coLinux C:\coLinux>ls Debian-20040605-mit.ext3.1610mb colinux-slirp-net-daemon.exe Debian-3.0r2.ext3-mit-backports.1gb colinux.bat Debug.log default.colinux.xml README.txt default.colinux.xml.old REM default.colinux.xml~ Uninstall.exe default.colinux_golden.xml bzip2.exe initrd cofs.txt initrd.gz colinux-bridged-net-daemon.exe lib colinux-console-fltk.exe linux.sys colinux-console-nt.exe netdriver colinux-daemon.exe news.txt colinux-daemon.txt swap_128Mb colinux-debug-daemon.exe vmlinux colinux-net-daemon.exe vmlinux-modules.tar.gz ----- end of debug log ----- my default.colinux.xml <?xml version="1.0" encoding="UTF-8"?> <colinux> <!-- This line needs to point to your root file system. For example change "root_fs" to the name of the Debian image. Inside coLinux it will be /dev/cobd0 Block Device Aliasing: You can now handle most dual-boot issues by adding an alias="devname" to block_device. i.e. alias="hda", alias="hda1" You can do this for SCSI as well as IDE. You need to be aware that if you add an alias, you need to change your bootparams root="devname" appropriately (you may need to use devfs naming in some situations). --> <!-- <block_device index="0" path="\DosDevices\c:\coLinux\root_fs" enabled="true" /> --> <block_device index="0" path="\DosDevices\c:\coLinux\Debian-3.0r2.ext3-mit-backports.1gb" enabled="true" /> <!-- This line can specify a swap file if you wish, or an additional image file, it will /dev/cobd1. Additional block_devices can be specified in the same manner by increasing the index --> <!-- <block_device index="1" path="\DosDevices\c:\coLinux\swap_device" enabled="true" /> --> <block_device index="1" path="\DosDevices\c:\coLinux\swap_128Mb" enabled="true" /> <!-- This is an experimental feature, it may not function completely. <cofs_device index="0" type="flat" path="\DosDevices\C:\" enabled="true" /> --> <!-- bootparams allows you to pass kernel boot parameters --> <!-- <bootparams>root=/dev/cobd0</bootparams> --> <bootparams>root=/dev/cobd0 devfs=mount,dall ramdisk_size=8192 </bootparams> <!-- Initial RamDISK (initrd) support --> <!-- <initrd path="initrd.gz" /> --> <initrd path="initrd" /> <!-- image allows you to specify the kernel to boot --> <image path="vmlinux" /> <!-- this line allows you to specify the amount of memory available to coLinux --> <memory size="64" /> <!-- This allows you to modify networking parameters, see the README or website or wiki for more information --> <!-- <network index="0" type="tap" /> --> <network index="0" type="Local Area Connection 2" /> </colinux> ----------- end of my default.colinux.xml Still gives the same error message... What am I doing wrong or missing? I've been using the http://wiki.colinux.org/cgi-bin/GettingStarted instructions and the README.TXT document. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-03-28 07:31 Message: Logged In: NO Please download and use 0.6.3 as it has several significant bug fixes to 0.6.2. The above error is generally saying that it can't find a file referenced in teh config or the config file itself. Double-check all your paths for all the files you are referencing on the command-line and in the configuration file. ---------------------------------------------------------------------- Comment By: SiMechanic (grhaag) Date: 2006-03-25 18:10 Message: Logged In: YES user_id=1486137 Same error on 0.6.3 C:\coLinux>c:\coLinux\colinux-daemon.exe -t nt -c default.colinux.xml Cooperative Linux Daemon, 0.6.3 Compiled on Sun Feb 5 20:25:03 2006 daemon: exit code 8805bc01 daemon: error - CO_RC_ERROR_ERROR, line 367, file colinux/user/config.o (64) C:\coLinux>colinux.bat C:\coLinux>cd c: C:\coLinux C:\coLinux>REM c:\coLinux\colinux-daemon.exe -t nt -c default.colinux.xml C:\coLinux>c:\coLinux\colinux-daemon.exe -t fltk -c default.colinux.xml Cooperative Linux Daemon, 0.6.3 Compiled on Sun Feb 5 20:25:03 2006 daemon: exit code 8805bc01 daemon: error - CO_RC_ERROR_ERROR, line 367, file colinux/user/config.o (64) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1396459&group_id=98788 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: September 23, 2006
From: nazarianin2000@xxxxxxxxxx
In-reply-to:
<4512FD8F.30003@xxxxxxxx>
References:
<4512FD8F.30003@xxxxxxxx>
Hello
> snapshot with kernel 2.6.15 is available as Installer:
I install snapshot 0.8.0 with kernel 2.6.15 and have trouble. I
have not cobd* devices in /dev. Previous i use 2.6.12-co-0.7.1
colinux.
--
Best regards,
Nazarianin mailto:nazarianin2000@xxxxxxxxxx
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: September 22, 2006
From: Martin Afanasjew <martin-lists@xxxxxxxxxxxx>
In-reply-to:
<4512FD8F.30003@xxxxxxxx>
References:
<4512FD8F.30003@xxxxxxxx>
Hello, thanks for all your work on this. It's great to see coLinux progressing towards newer kernels. Sadly, I have no kernel hacking experience and thus won't be of any use I think... However, I tried the new snapshot after having used 0.7-hn14 (20060417) for several months. Everything works fine except _the time_ is behaving really strange. It immediately diverges from windows system time (keeps behind) and sometimes even moves backwards. Is there something I can do to help debug this problem? Any idea what to to look after? Were there changes in the coLinux patches or between 2.6.12 and 2.6.15 that may cause this? I should note that I use a custom kernel (based on 2.6.15.7 with coLinux patches from the source file). Regards, Martin Henry Nestler wrote: > Hello, > > snapshot with kernel 2.6.15 is available as Installer: > > http://www.colinux.org/snapshots/ > > Please read the NEWS and ChangeLog. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: September 22, 2006
From: Henry Nestler <Henry.Ne@xxxxxxxx>
Hello, snapshot with kernel 2.6.15 is available as Installer: http://www.colinux.org/snapshots/ Please read the NEWS and ChangeLog. -- Henry Nestler ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: September 20, 2006
From: "Anders Eriksson C (KI/EAB)" <anders.c.eriksson@xxxxxxxxxxxx>
In-reply-to:
<450EEAB1.6000900@xxxxxxxx>
References:
<450EEAB1.6000900@xxxxxxxx>
Thanks for the pointer, I just found this one http://www-128.ibm.com/developerworks/linux/library/l-memmod/?ca=dgr-lnx w09MemModel setting some context to the area and some other useful refs as well. -Anders > -----Original Message----- > From: Henry Nestler [mailto:Henry.Ne@xxxxxxxx] > Sent: den 18 september 2006 20:51 > To: Anders Eriksson C (KI/EAB); Cooperative Linux Development > Subject: Fw: Assignment of GDT entries > > Hello Anders, > > I found this thread in kernel mailing list. > > http://marc.theaimsgroup.com/?l=linux-kernel&m=115817473319565&w=2 > http://marc.theaimsgroup.com/?l=linux-kernel&m=115819376501674&w=2 > > Please read this, Linus and others give good comments about > the GDT/TLS > entries and how it's working. > > -- > Henry Nestler > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: September 18, 2006
From: "SourceForge.net" <noreply@xxxxxxxxxxxxxxx>
Bugs item #1551076, was opened at 2006-09-02 18:33 Message generated for change (Comment added) made by jernejs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1551076&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 Submitted By: Nobody/Anonymous (nobody) Assigned to: Henry N. (henryn) Summary: colinux-net-daemon.exe crashes on use with NFS Initial Comment: coLinux v0.6.4 I mounted an gentoo portage tree via a rw NFS mount point to save from having to do so much downloading, and 4 times while trying to complete the emerge the colinux-net-daemon.exe crashed with something like the following: colinux-net-daemon.exe caused an Access Violation at location 004013b0 in module colinux-net-daemon.exe Reading from location 8d7d5040. Registers: eax=86a17001 ebx=72c4e84c ecx=77e6f4bd edx=86a17001 esi=8d7d5030 edi=0042c184 eip=004013b0 esp=0022fd80 ebp=0022fd98 iopl=0 nv up ei pl nz na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010202 Call stack: 004013B0 colinux-net-daemon.exe:004013B0 00401509 colinux-net-daemon.exe:00401509 00401603 colinux-net-daemon.exe:00401603 00401735 colinux-net-daemon.exe:00401735 00401AF2 colinux-net-daemon.exe:00401AF2 00401237 colinux-net-daemon.exe:00401237 00401288 colinux-net-daemon.exe:00401288 77E523E5 kernel32.dll:77E523E5 IsProcessorFeaturePresent ---------------------------------------------------------------------- Comment By: Jernej Simoncic (jernejs) Date: 2006-09-18 21:05 Message: Logged In: YES user_id=632674 Thanks, the update seems to have fixed the problem. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2006-09-13 11:05 Message: Logged In: YES user_id=579204 004013b0 is this line: src/colinux/os/winnt/user/conet-daemon/main.c:110 do { message = (co_message_t *)buffer; message_size = message->size + sizeof (co_message_t); <=== crash It's fixed by Mitch. You can use this update: http://www.henrynestler.com/colinux/testing/stable-0.6.4- 2/update/ Henry ---------------------------------------------------------------------- Comment By: Mitch Bradley (wmb314) Date: 2006-09-12 20:10 Message: Logged In: YES user_id=1131764 This is very likely to be a manifestation of the problem observed in issue 1517979 "Network broke down". The root cause of that problem has been determined and a patch has been developed and tested. The problem code exists in all the network daemons, so it's very likely that a similar patch will be effective. ---------------------------------------------------------------------- Comment By: Jernej Simoncic (jernejs) Date: 2006-09-02 21:51 Message: Logged In: YES user_id=632674 When I tried running with debug enabled, Windows BSODed while wgetting to a NFS mount: Error code 1000008e, parameter1 c0000046, parameter2 e082a918, parameter3 f1652750, parameter4 00000000. The debug log is here: <http://gimp-win.sf.net/misc/debug.out.bz2> ---------------------------------------------------------------------- Comment By: Jernej Simoncic (jernejs) Date: 2006-09-02 20:41 Message: Logged In: YES user_id=632674 Oh, forgot to add, my OS is Windows Server 2003 R2 Standard Edition (5.2 R2 Build 3790.srv03_sp1_rtm.050324-1447). If it matters, I also have VMware server 1.0.1 installed. ---------------------------------------------------------------------- Comment By: Jernej Simoncic (jernejs) Date: 2006-09-02 20:29 Message: Logged In: YES user_id=632674 To be precise, the crash always happened while wget was downloading something to the NFS mount point. The crash occured both with tap and bridged networking. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1551076&group_id=98788 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: September 18, 2006
From: Henry Nestler <Henry.Ne@xxxxxxxx>
Hello Anders, I found this thread in kernel mailing list. http://marc.theaimsgroup.com/?l=linux-kernel&m=115817473319565&w=2 http://marc.theaimsgroup.com/?l=linux-kernel&m=115819376501674&w=2 Please read this, Linus and others give good comments about the GDT/TLS entries and how it's working. -- Henry Nestler ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: September 17, 2006
From: "SourceForge.net" <noreply@xxxxxxxxxxxxxxx>
Support Requests item #1560191, was opened at 2006-09-17 15:18 Message generated for change (Settings changed) made by fxdwg You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622064&aid=1560191&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Deleted Priority: 5 Submitted By: FXDWG (fxdwg) Assigned to: Nobody/Anonymous (nobody) Summary: exit code 8805f801 Initial Comment: I've installed WinPcap 3.1 and coLinux 0.6.4 on XP Pro w/SP2. coLinux will not launch. Command prompt shows: C:\coLinux>colinux-daemon -c my_colinux.xml Cooperative Linux Daemon, 0.6.4 Compiled on Mon May 29 22:19:09 2006 mapping cobd0 to \DosDevices\c:\coLinux\Debian- 3.0r2.ext3-mit-backports.1gb mapping cobd1 to \DosDevices\c:\coLinux\swap_512Mb daemon: exit code 8805f801 daemon: error - CO_RC_ERROR_ERROR, line 382, file colinux/user/config.o (64) All help is greatly appreciated. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622064&aid=1560191&group_id=98788 ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
Date: September 17, 2006
From: "SourceForge.net" <noreply@xxxxxxxxxxxxxxx>
Support Requests item #1560191, was opened at 2006-09-17 15:18 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622064&aid=1560191&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 Priority: 5 Submitted By: FXDWG (fxdwg) Assigned to: Nobody/Anonymous (nobody) Summary: exit code 8805f801 Initial Comment: I've installed WinPcap 3.1 and coLinux 0.6.4 on XP Pro w/SP2. coLinux will not launch. Command prompt shows: C:\coLinux>colinux-daemon -c my_colinux.xml Cooperative Linux Daemon, 0.6.4 Compiled on Mon May 29 22:19:09 2006 mapping cobd0 to \DosDevices\c:\coLinux\Debian- 3.0r2.ext3-mit-backports.1gb mapping cobd1 to \DosDevices\c:\coLinux\swap_512Mb daemon: exit code 8805f801 daemon: error - CO_RC_ERROR_ERROR, line 382, file colinux/user/config.o (64) All help is greatly appreciated. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622064&aid=1560191&group_id=98788 ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
Date: September 16, 2006
From: Frédéric L. W. Meunier <2@xxxxxxxxxxxxxx>
In-reply-to:
<450C601F.5040602-CEfNw1QHlwk@xxxxxxxxxxxxxxxx>
References:
<026F8EEDAD2C4342A993203088C1FC050335328D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <44C5433B.1080806@xxxxxxxx> <44CE7920.2090007@xxxxxxxx> <Pine.LNX.4.64.0608240046060.143@xxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.64.0608240055010.143@xxxxxxxxxxxxxxxxxxxxx> <44FF481E.9060206@xxxxxxxx> <Pine.LNX.4.64.0609161625160.16276@xxxxxxxxxxxxxxxxxxxxx> <450C601F.5040602@xxxxxxxx>
On Sat, 16 Sep 2006, Henry Nestler wrote:
Hello Frederic, Frédéric L. W. Meunier wrote:On Thu, 7 Sep 2006, Henry Nestler wrote:The old workarrount (sep-disable-2.6.15.patch) was only for Intel cpu types. This should fixed now for all cpu types in this build: http://www.henrynestler.com/colinux/testing/devel-2.6.15-hn/20060906/ Please read the readme file. More history is in kernel source patches: http://www.henrynestler.com/colinux/patches/devel/kernel-2.6.15/patches-2.6.15-20060906hn.tgzI've been running this version without any problems for 9 days, but today, while compiling a kernel with 'make -j4', I noticed the following:Sep 16 15:52:38 pervalidus kernel: EIP: 0060:[<c0104b56>] Not tainted VLI Sep 16 15:52:38 pervalidus kernel: EFLAGS: 00010002 (2.6.15-co-0.7.1-hn17) Sep 16 15:52:38 pervalidus kernel: EIP is at math_state_restore+0x16/0x40 Sep 16 15:52:38 pervalidus kernel: eax: 8005003b ebx: c126b030 ecx: 00000000 edx: 0000007b Sep 16 15:52:38 pervalidus kernel: esi: c03a4000 edi: c312d520 ebp: c03a5ec8 esp: c03a5ec0Sep 16 15:52:38 pervalidus kernel: ds: 007b es: 007b ss: 0068Sep 16 15:52:38 pervalidus kernel: Process watchdog/0 (pid: 3, threadinfo=c03a4000 task=c126b030)... Sep 16 15:52:47 pervalidus kernel: <3>BUG: soft lockup detected on CPU#0! ...I've no idea what it means or if it's related to coLinux. Nothing happened to coLinux, no crashes, kernel panic, just this in the log.oh, a bug on coprocessor handling?math_state_restore and device_not_available are called for floating point errors."BUG: soft lockup detected on CPU#"if I understand the kernel right, kernel detects a non running watchdog. Think, followed by the other error.Please give a output from /proc/cpuinfo the 'flags'. It could be interesting, if your CPU supports fxsave or fnsave.I think the watchdog process tryed to resotore the coprocessor, and that failed. The kernel under coLinux typicaly have the CPU not for long time, if you have heavy disk transfers. This could be a problem with the watchdog task. Or it's a general race condition under coLinux. I have no idea, what it is exactly.Thanks for the log output.
processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 8 model name : AMD Athlon(tm) XP 1700+ stepping : 1 cpu MHz : 0.000 cache size : 256 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow bogomips : 730.72 -- How to contact me - http://www.pervalidus.net/contact.html
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ coLinux-devel mailing list coLinux-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/colinux-devel
Date: September 16, 2006
From: Henry Nestler <Henry.Ne@xxxxxxxx>
In-reply-to:
<026F8EEDAD2C4342A993203088C1FC05037B8F6B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References:
<026F8EEDAD2C4342A993203088C1FC05037B8F6B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Anders Eriksson C (KI/EAB) wrote: >> Yes. I know. But see for 2.6.18-rc7: >> http://www.linux-m32r.org/lxr/http/source/arch/i386/kernel/cpu > /common.c?a=i386#L615 >> The kernel devolopers changed it again, and have also touble with >> dynamic GDT. >> >> Anders: An other idea is, to run coLinux as 'hotplugable' >> CPU. See that >> this CPU skipped simple the GDT setting with a "goto old_gdt". >> > > Yep. That might work. I don't know anyting about hotplugging CPUs > though. Wouldn't the boot CPU need the GDT stuff setup early on > anyway? Yes. But, the boot CPU is on Windows side. That's why colinux-daemon located the symbol gdt_table and setup the registers to that label for the for the first OS switch. see: src/colinux/user/daemon.c:372 (co_daemon_monitor_create) src/colinux/arch/i386/passage.c:729 (co_monitor_arch_passage_page_init) > generally, I think we should try to monitor the hotplug stuff and > try to use it as best we can. How about hotplugging the memory? > At least after the boot sequence, it would be cool to be able to > add/drop memory to the running instance using memory hotplug. ;-) I'm fighting with gdt and you are good dreaming ;-) Henry ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
Date: September 16, 2006
From: "Anders Eriksson C (KI/EAB)" <anders.c.eriksson@xxxxxxxxxxxx>
In-reply-to:
<450ADAEB.3030709@xxxxxxxx>
References:
<450ADAEB.3030709@xxxxxxxx>
> Yes. I know. But see for 2.6.18-rc7: > http://www.linux-m32r.org/lxr/http/source/arch/i386/kernel/cpu /common.c?a=i386#L615 > > The kernel devolopers changed it again, and have also touble with > dynamic GDT. > > Anders: An other idea is, to run coLinux as 'hotplugable' > CPU. See that > this CPU skipped simple the GDT setting with a "goto old_gdt". > Yep. That might work. I don't know anyting about hotplugging CPUs though. Wouldn't the boot CPU need the GDT stuff setup early on anyway? generally, I think we should try to monitor the hotplug stuff and try to use it as best we can. How about hotplugging the memory? At least after the boot sequence, it would be cool to be able to add/drop memory to the running instance using memory hotplug. /A ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
Date: September 16, 2006
From: Henry Nestler <Henry.Ne@xxxxxxxx>
In-reply-to:
<Pine.LNX.4.64.0609161625160.16276@xxxxxxxxxxxxxxxxxxxxx>
References:
<026F8EEDAD2C4342A993203088C1FC050335328D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <44C5433B.1080806@xxxxxxxx> <44CE7920.2090007@xxxxxxxx> <Pine.LNX.4.64.0608240046060.143@xxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.64.0608240055010.143@xxxxxxxxxxxxxxxxxxxxx> <44FF481E.9060206@xxxxxxxx> <Pine.LNX.4.64.0609161625160.16276@xxxxxxxxxxxxxxxxxxxxx>
Hello Frederic, Frédéric L. W. Meunier wrote: > On Thu, 7 Sep 2006, Henry Nestler wrote: > >> The old workarrount (sep-disable-2.6.15.patch) was only for Intel cpu >> types. This should fixed now for all cpu types in this build: >> http://www.henrynestler.com/colinux/testing/devel-2.6.15-hn/20060906/ >> >> Please read the readme file. More history is in kernel source patches: >> http://www.henrynestler.com/colinux/patches/devel/kernel-2.6.15/patches-2.6.15-20060906hn.tgz > > I've been running this version without any problems for 9 days, > but today, while compiling a kernel with 'make -j4', I noticed > the following: > > Sep 16 15:52:38 pervalidus kernel: EIP: 0060:[<c0104b56>] Not tainted > VLI > Sep 16 15:52:38 pervalidus kernel: EFLAGS: 00010002 (2.6.15-co-0.7.1-hn17) > Sep 16 15:52:38 pervalidus kernel: EIP is at math_state_restore+0x16/0x40 > Sep 16 15:52:38 pervalidus kernel: eax: 8005003b ebx: c126b030 ecx: > 00000000 edx: 0000007b > Sep 16 15:52:38 pervalidus kernel: esi: c03a4000 edi: c312d520 ebp: > c03a5ec8 esp: c03a5ec0 > Sep 16 15:52:38 pervalidus kernel: ds: 007b es: 007b ss: 0068 > Sep 16 15:52:38 pervalidus kernel: Process watchdog/0 (pid: 3, > threadinfo=c03a4000 task=c126b030) > ... > Sep 16 15:52:47 pervalidus kernel: <3>BUG: soft lockup detected on CPU#0! > ... > > I've no idea what it means or if it's related to coLinux. > Nothing happened to coLinux, no crashes, kernel panic, just > this in the log. > oh, a bug on coprocessor handling? math_state_restore and device_not_available are called for floating point errors. "BUG: soft lockup detected on CPU#" if I understand the kernel right, kernel detects a non running watchdog. Think, followed by the other error. Please give a output from /proc/cpuinfo the 'flags'. It could be interesting, if your CPU supports fxsave or fnsave. I think the watchdog process tryed to resotore the coprocessor, and that failed. The kernel under coLinux typicaly have the CPU not for long time, if you have heavy disk transfers. This could be a problem with the watchdog task. Or it's a general race condition under coLinux. I have no idea, what it is exactly. Thanks for the log output. -- Henry ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
Date: September 16, 2006
From: Frédéric L. W. Meunier <2@xxxxxxxxxxxxxx>
In-reply-to:
<44FF481E.9060206-CEfNw1QHlwk@xxxxxxxxxxxxxxxx>
References:
<026F8EEDAD2C4342A993203088C1FC050335328D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <44C5433B.1080806@xxxxxxxx> <44CE7920.2090007@xxxxxxxx> <Pine.LNX.4.64.0608240046060.143@xxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.64.0608240055010.143@xxxxxxxxxxxxxxxxxxxxx> <44FF481E.9060206@xxxxxxxx>
On Thu, 7 Sep 2006, Henry Nestler wrote: > The old workarrount (sep-disable-2.6.15.patch) was only for Intel cpu > types. This should fixed now for all cpu types in this build: > http://www.henrynestler.com/colinux/testing/devel-2.6.15-hn/20060906/ > > Please read the readme file. More history is in kernel source patches: > http://www.henrynestler.com/colinux/patches/devel/kernel-2.6.15/patches-2.6.15-20060906hn.tgz I've been running this version without any problems for 9 days, but today, while compiling a kernel with 'make -j4', I noticed the following: Sep 16 15:52:38 pervalidus kernel: general protection fault: 0000 [#1] Sep 16 15:52:38 pervalidus kernel: Modules linked in: Sep 16 15:52:38 pervalidus kernel: CPU: 0 Sep 16 15:52:38 pervalidus kernel: EIP: 0060:[<c0104b56>] Not tainted VLI Sep 16 15:52:38 pervalidus kernel: EFLAGS: 00010002 (2.6.15-co-0.7.1-hn17) Sep 16 15:52:38 pervalidus kernel: EIP is at math_state_restore+0x16/0x40 Sep 16 15:52:38 pervalidus kernel: eax: 8005003b ebx: c126b030 ecx: 00000000 edx: 0000007b Sep 16 15:52:38 pervalidus kernel: esi: c03a4000 edi: c312d520 ebp: c03a5ec8 esp: c03a5ec0 Sep 16 15:52:38 pervalidus kernel: ds: 007b es: 007b ss: 0068 Sep 16 15:52:38 pervalidus kernel: Process watchdog/0 (pid: 3, threadinfo=c03a4000 task=c126b030) Sep 16 15:52:38 pervalidus kernel: Stack: c126b1f0 c312d6e0 c03a5f14 c0103654 c126b1f0 00000000 c126b030 c312d6e0 Sep 16 15:52:38 pervalidus kernel: c312d520 c03a5f14 c7174000 0000007b 0000007b ffffffff c0101183 00000060 Sep 16 15:52:38 pervalidus kernel: 00010002 c126b030 c6e6daa0 c126b030 042c1d80 c7175fb4 c027a56c c03a5f54 Sep 16 15:52:38 pervalidus kernel: Call Trace: Sep 16 15:52:38 pervalidus kernel: [<c0103925>] show_stack+0x75/0x90 Sep 16 15:52:38 pervalidus kernel: [<c0103a78>] show_registers+0x118/0x190 Sep 16 15:52:38 pervalidus kernel: [<c0103c25>] die+0xb5/0x130 Sep 16 15:52:38 pervalidus kernel: [<c01043c0>] do_general_protection+0x150/0x170 Sep 16 15:52:38 pervalidus kernel: [<c01035ff>] error_code+0x4f/0x60 Sep 16 15:52:38 pervalidus kernel: [<c0103654>] device_not_available+0x24/0x29 Sep 16 15:52:38 pervalidus kernel: [<c027a56c>] schedule+0x31c/0x610 Sep 16 15:52:38 pervalidus kernel: Code: 89 c7 f3 a5 89 d1 83 e1 03 74 02 f3 a4 5a 5e 5f 5d c3 8d 76 00 55 89 e5 56 53 be 00 e0 ff ff 21 e6 8b 1e 0f 06 f6 43 0d 20 74 1a <0f> ae 8b 20 02 00 00 8b 5e 0c 83 cb 01 89 5e 0c 8d 65 f8 5b 5e Sep 16 15:52:47 pervalidus kernel: <3>BUG: soft lockup detected on CPU#0! Sep 16 15:52:47 pervalidus kernel: Sep 16 15:52:47 pervalidus kernel: Pid: 26134, comm: cc1 Sep 16 15:52:47 pervalidus kernel: EIP: 9de4:[<c02c2ba0>] CPU: 0 Sep 16 15:52:47 pervalidus kernel: EIP is at contig_page_data+0x260/0x554 Sep 16 15:52:47 pervalidus kernel: EFLAGS: c0133db4 Not tainted (2.6.15-co-0.7.1-hn17) Sep 16 15:52:47 pervalidus kernel: EAX: feaff000 EBX: 00000046 ECX: c3149dcc EDX: 00000615 Sep 16 15:52:47 pervalidus kernel: ESI: 00000000 EDI: 00000001 EBP: c010d26a DS: f4c0 ES: f250 Sep 16 15:52:47 pervalidus kernel: CR0: 8005003b CR2: 40405000 CR3: 07593000 CR4: 00000600 Sep 16 15:52:47 pervalidus kernel: [<c0100b85>] show_regs+0x105/0x130 Sep 16 15:52:47 pervalidus kernel: [<c012eadd>] softlockup_tick+0x4d/0x60 Sep 16 15:52:47 pervalidus kernel: [<c011da8a>] do_timer+0x3a/0xf0 Sep 16 15:52:47 pervalidus kernel: [<c0107032>] timer_interrupt+0x22/0x60 Sep 16 15:52:47 pervalidus kernel: [<c012ec05>] handle_IRQ_event+0x35/0x80 Sep 16 15:52:47 pervalidus kernel: [<c012ecac>] __do_IRQ+0x5c/0xb0 Sep 16 15:52:47 pervalidus kernel: [<c0104c2d>] do_IRQ+0x1d/0x30 Sep 16 15:52:47 pervalidus kernel: [<c010d135>] co_handle_jiffies+0x55/0x70 Sep 16 15:52:47 pervalidus kernel: [<c012f9b5>] co_callback+0x75/0x160 Sep 16 15:52:47 pervalidus kernel: [<c0107ae3>] proxy_interrupt_handler+0x53/0x60 Sep 16 15:52:47 pervalidus kernel: [<c0108a9b>] IRQ_proxy_0x53_interrupt+0x1b/0x30 Sep 16 15:52:47 pervalidus kernel: [<c0144e5e>] free_page_and_swap_cache+0x1e/0x40 Sep 16 15:52:47 pervalidus kernel: [<c013d5ff>] zap_pte_range+0x14f/0x220 Sep 16 15:52:47 pervalidus kernel: [<c013d767>] unmap_page_range+0x97/0x150 Sep 16 15:52:47 pervalidus kernel: [<c013d8ea>] unmap_vmas+0xca/0x1a0 Sep 16 15:52:47 pervalidus kernel: [<c0141c2e>] exit_mmap+0x4e/0xd0 Sep 16 15:52:47 pervalidus kernel: [<c0113ca3>] mmput+0x23/0x80 Sep 16 15:52:47 pervalidus kernel: [<c0117307>] exit_mm+0x67/0xe0 Sep 16 15:52:47 pervalidus kernel: [<c0117ca0>] do_exit+0xf0/0x370 Sep 16 15:52:47 pervalidus kernel: [<c0117f8d>] do_group_exit+0x2d/0x80 Sep 16 15:52:47 pervalidus kernel: [<c0117ff1>] sys_exit_group+0x11/0x20 Sep 16 15:52:47 pervalidus kernel: [<c0102629>] syscall_call+0x7/0xb I've no idea what it means or if it's related to coLinux. Nothing happened to coLinux, no crashes, kernel panic, just this in the log. -- How to contact me - http://www.pervalidus.net/contact.html ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
Date: September 15, 2006
From: Henry Nestler <Henry.Ne@xxxxxxxx>
In-reply-to:
<121565a0609150916g3f5e9577ie9f25096cbd37579@xxxxxxxxxxxxxx>
References:
<4509CC1A.2070703@xxxxxxxx> <121565a0609150916g3f5e9577ie9f25096cbd37579@xxxxxxxxxxxxxx>
George P Boutwell wrote: > On 9/14/06, Henry Nestler <Henry.Ne@xxxxxxxx> wrote: > >> this is the first build with kernel 2.6.17: >> >> http://www.henrynestler.com/colinux/testing/devel-2.6.17-hn/20060914/ >> >> It is a very badly hacking, I reverted various changes on the GDT stuff >> on vanilla kernel between 2.6.15 and 2.6.17. After that, coLinux runs >> without crashing. > > :). That's one way... Probably not the way we want to do it in the > long run (be harder to justify inclusion in to vanilla kernel) Yes. I know. But see for 2.6.18-rc7: http://www.linux-m32r.org/lxr/http/source/arch/i386/kernel/cpu/common.c?a=i386#L615 The kernel devolopers changed it again, and have also touble with dynamic GDT. Anders: An other idea is, to run coLinux as 'hotplugable' CPU. See that this CPU skipped simple the GDT setting with a "goto old_gdt". >> - add cloop module > > I'm working on this, got quite a ways last night just need to finish > it up and I'll send you an patch when I have it. I will add it and you can test it later. -- Henry Nestler ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
Date: September 15, 2006
From: "George P Boutwell" <george.boutwell@xxxxxxxxx>
In-reply-to:
<23bcb8700609150740w41510d5fn7aa5185ba2625b59@xxxxxxxxxxxxxx>
References:
<121565a0609021611j607dda70ge71799c55bbbb8fd@xxxxxxxxxxxxxx> <45087188.2050200@xxxxxxxx> <121565a0609141418t31bc8bf8j76f1439d016e06c8@xxxxxxxxxxxxxx> <450A64AA.20302@xxxxxxxx> <23bcb8700609150726s3c004c09o4263647fa676483d@xxxxxxxxxxxxxx> <23bcb8700609150740w41510d5fn7aa5185ba2625b59@xxxxxxxxxxxxxx>
Yes... Making a educated guess is one approach... Another is to attempt the operation and let the user know that is the reason for the failure... Naming conventions for images that state how big the image is uncompressed is another... changing our installer to 'build an image' based on a user selected image size is yet another way... Lots of other ways, as well... I'm just saying that making the installer simpler to use, invites simpler users to use it and they aren't going to be as forgiving when it just doesn't work... I'm not saying we should have that as a goal, I'd just rather handle the possibilities up-front than to have users pressuring us to fix the problem after the fact. George On 9/15/06, Bill C. Riemers <docbill@xxxxxxxxxxxxx> wrote: > Sorry, brain fart. Assuming something like 3:1 for a filesystem is probably > only a reasonable high estimate if the filesystem is being extracted to NTFS > with holes... Maybe it would just be better to recommend to the user they > have at least 4GB of free disk space available. If they want to try it with > less, they can. > > Bill > > > > On 9/15/06, Bill C. Riemers <docbill@xxxxxxxxxxxxx> wrote: > > > > This could probably be done just by assuming a high compression ration > like 3:1 and offering the option to continue even if the check fails. > > > > > > Bill > > > > > > > > > > On 9/15/06, Henry Nestler <Henry.Ne@xxxxxxxx> wrote: > > > George P Boutwell wrote: > > > > On 9/13/06, Henry Nestler <Henry.Ne@xxxxxxxx> wrote: > > > >> > 3) Re-Write the README for 0.7.x, Ideally I'd like the new README > to > > > >> > be short and brief and give folks pointers where to go for most of > the > > > >> > information that's in there now. > > > >> > > > >> Add a text file or html as manual, that shows the parameter, the > config > > > >> options and some samples. Currently it's scattered in various files > > > >> (RUNNING, doc/colinux-daemon, doc/cofs) with unsorted samples. > > > > > > > > Is was thinking basically that we get the colinux-daemon to dump it > > > > out (more or less does now), or like you suggest provide an 'man page' > > > > in text file that ships with colinux. > > > > > > Not a real man page. > > > > > > Yes, the dumps where gets from colinux-daemon starts without parameter > > > should put into the text file. Think, nobody would run this daemon to > > > get the parameter. > > > > > > One text file with a list of all parameters. And a sample to that > > > parameter. In the same text file the config parameters and one or more > > > samples. Remove the text file doc/cofs. > > > > > > >> > 4) Update/Create an 0.7.x Known Issues/Problems page that could be > > > >> > pointed to from the README > > > >> > > > >> If we can not solve the DEP/Noexecute bug: The instaler should show > an > > > >> extra page with a warning and a "howto change the boot.ini ...". The > > > >> installer should sheck the CPU for typical candidate for crashing > > > >> (Intel, >1GB RAM + SP2 + PAE enabled + boot.ini has an entry > > > >> noexecute=OptIn) > > > > > > > > Hmm... I'm ok with that. I'd rather track down the problem and fix > > > > it, though if we could. > > > > I'm trying to recall... does the coLinux installer crash during the > > > > install (probably the colinux-daemon --install-driver), if it does not > > > > only would we have to display the message, but we'd have to 'abort' > > > > the install or skip the colinux-daemon --install-driver & inform the > > > > user of how to run it. > > > > > > No, the installer is not crashing in the "colinux-daemon > > > --install-driver". It's later on first running Linux. > > > > > > > > > > >> > 5) Create 0.7.x default colinux config which uses initrd.gz & SLiRP > to > > > >> > have a running 'very limited' but internet connected coLinux at the > > > >> > end of the install. > > > >> > > > >> I'm preferred to use the first network with slirp (eth0). Power > users > > > >> should use the second network (eth1) for additional types (tap, > > > >> Pcap-bridged). We should clear about this before changing the > images, > > > >> so all images have similar networks on startup. > > > > > > > > I think we are in agreement here more or less. But for me power > > > > users are free to 'take over' eth0 and not use slirp at all if that's > > > > what they wish to do... Just the installer & images are going to be > > > > initially set-up that way. > > > > > > Yes, that I mean. > > > > > > > > > > >> > 6) Update install to make TAP optional install and require that it > be > > > >> > specifically selected. > > > >> > > > >> Very good idea. The Pcap-Bridged in same. > > > > > > > > Yes, if Pcap-Bridge is not already this way it should be this way. > > > > Except that PCap's actuall driver needs to be a seperate install like > > > > it is now. This is a request from the PCap project's developers. > > > > > > > >> The installer should have two or more "InstType". For sample > Standard, > > > >> Full and User. The Standard should be the typical installation with > > > >> Slirp only and a Debian (or ArchLinux) image. > > > > > > > > I'm not targetting this situation in this release of coLinux, but I'm > > > > not against it either. > > > > > > OK. Stike it out. > > > > > > >> The installer should uncompressing the image file, selectable by a > > > >> checkbox "yes/no". > > > > > > > > Again, I'm not targetting this for this release of coLinux. If we do > > > > something like this, I feel that if at all possible, we should do a > > > > free space check that includes this file uncompressed... otherwise we > > > > are just inviting users to be frustrated when they download coLinux > > > > run the install and it dies uncompressing because it ran out of disk > > > > space. > > > > > > Hm. This would be complicated. The installer is not known the unpacked > > > size. > > > > > > -- > > > Henry Nestler > > > > > > > ------------------------------------------------------------------------- > > > Using Tomcat but need to do more? Need to support web services, > security? > > > Get stuff done quickly with pre-integrated technology to make your job > easier > > > Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > > _______________________________________________ > > > coLinux-devel mailing list > > > coLinux-devel@xxxxxxxxxxxxxxxxxxxxx > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > -- George ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
Date: September 15, 2006
From: "George P Boutwell" <george.boutwell@xxxxxxxxx>
In-reply-to:
<450A64AA.20302@xxxxxxxx>
References:
<121565a0609021611j607dda70ge71799c55bbbb8fd@xxxxxxxxxxxxxx> <45087188.2050200@xxxxxxxx> <121565a0609141418t31bc8bf8j76f1439d016e06c8@xxxxxxxxxxxxxx> <450A64AA.20302@xxxxxxxx>
On 9/15/06, Henry Nestler <Henry.Ne@xxxxxxxx> wrote: > > Is was thinking basically that we get the colinux-daemon to dump it > > out (more or less does now), or like you suggest provide an 'man page' > > in text file that ships with colinux. > > Not a real man page. > > Yes, the dumps where gets from colinux-daemon starts without parameter > should put into the text file. Think, nobody would run this daemon to > get the parameter. > > One text file with a list of all parameters. And a sample to that > parameter. In the same text file the config parameters and one or more > samples. Remove the text file doc/cofs. I think we are in agreement here. We really need a on-stop shop for parameters & samples. I still think that the daemon should dump (an fairly abbreviated) parameters if ran without command or that we should had an typical --help or -h command-line switch. > > Again, I'm not targetting this for this release of coLinux. If we do > > something like this, I feel that if at all possible, we should do a > > free space check that includes this file uncompressed... otherwise we > > are just inviting users to be frustrated when they download coLinux > > run the install and it dies uncompressing because it ran out of disk > > space. > > Hm. This would be complicated. The installer is not known the unpacked > size. Yes... I'm aware of that. Bare minimum if the uncompression fails and the reason for the failure is not enough disk space, the user should be properly informed of that and the install cleaned-up (so as to not leave the users computer in an out of disk space condition) -- George ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
Date: September 15, 2006
From: "SourceForge.net" <noreply@xxxxxxxxxxxxxxx>
Support Requests item #1559441, was opened at 2006-09-15 09:16 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622064&aid=1559441&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 Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: OpenAFS support Initial Comment: Is there any plan for supporting OpenAFS? I used colinux-0.6.3-pre13 based on a gentoo image. I have been able to use the OpenAFS package compiled with vannila 2.6.11 kernel source. It worked pretty well although sometimes the afs connection got broken and I had to restart the service. But then a recent windows xp update is in conflicts with colinux. So I had to update my colinux to version 0.6.4. However, this time I could not start the afs service. The error message said 'invalid module format'. As I understand, 0.6.4 uses the same version of kernel(2.6.11). I tried to recompile OpenAFS, but to no avail. Can somebody help? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622064&aid=1559441&group_id=98788 ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
Date: September 15, 2006
From: "George P Boutwell" <george.boutwell@xxxxxxxxx>
In-reply-to:
<4509CC1A.2070703@xxxxxxxx>
References:
<4509CC1A.2070703@xxxxxxxx>
On 9/14/06, Henry Nestler <Henry.Ne@xxxxxxxx> wrote: > this is the first build with kernel 2.6.17: > > http://www.henrynestler.com/colinux/testing/devel-2.6.17-hn/20060914/ > > It is a very badly hacking, I reverted various changes on the GDT stuff > on vanilla kernel between 2.6.15 and 2.6.17. After that, coLinux runs > without crashing. :). That's one way... Probably not the way we want to do it in the long run (be harder to justify inclusion in to vanilla kernel) > - add cloop module I'm working on this, got quite a ways last night just need to finish it up and I'll send you an patch when I have it. > - check and repair Linux as host (it's broken currently) I was thinking on support linux as host more formally, ie with the up-coming release having linux binaries or an linux 'tar ball' of pre-build binaries (except the kernel module of course) with directions/instructinos on how to build the kernel module using their kernel's compiler so that it would be sure to work. > Be very carefully. This build is not well testested. Savve all your > work and _reboot_ your Windows host _before_ you starts it in first time! :). -- George ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
Date: September 15, 2006
From: "Bill C. Riemers" <docbill@xxxxxxxxxxxxx>
In-reply-to:
<23bcb8700609150726s3c004c09o4263647fa676483d@xxxxxxxxxxxxxx>
References:
<121565a0609021611j607dda70ge71799c55bbbb8fd@xxxxxxxxxxxxxx> <45087188.2050200@xxxxxxxx> <121565a0609141418t31bc8bf8j76f1439d016e06c8@xxxxxxxxxxxxxx> <450A64AA.20302@xxxxxxxx> <23bcb8700609150726s3c004c09o4263647fa676483d@xxxxxxxxxxxxxx>
This could probably be done just by assuming a high compression ration like 3:1 and offering the option to continue even if the check fails.
BillOn 9/15/06, Henry Nestler <Henry.Ne@xxxxxxxx> wrote:George P Boutwell wrote:
> On 9/13/06, Henry Nestler <Henry.Ne@xxxxxxxx> wrote:
>> > 3) Re-Write the README for 0.7.x, Ideally I'd like the new README to
>> > be short and brief and give folks pointers where to go for most of the
>> > information that's in there now.
>>
>> Add a text file or html as manual, that shows the parameter, the config
>> options and some samples. Currently it's scattered in various files
>> (RUNNING, doc/colinux-daemon, doc/cofs) with unsorted samples.
>
> Is was thinking basically that we get the colinux-daemon to dump it
> out (more or less does now), or like you suggest provide an 'man page'
> in text file that ships with colinux.
Not a real man page.
Yes, the dumps where gets from colinux-daemon starts without parameter
should put into the text file. Think, nobody would run this daemon to
get the parameter.
One text file with a list of all parameters. And a sample to that
parameter. In the same text file the config parameters and one or more
samples. Remove the text file doc/cofs.
>> > 4) Update/Create an 0.7.x Known Issues/Problems page that could be
>> > pointed to from the README
>>
>> If we can not solve the DEP/Noexecute bug: The instaler should show an
>> extra page with a warning and a "howto change the boot.ini ...". The
>> installer should sheck the CPU for typical candidate for crashing
>> (Intel, >1GB RAM + SP2 + PAE enabled + boot.ini has an entry
>> noexecute=OptIn)
>
> Hmm... I'm ok with that. I'd rather track down the problem and fix
> it, though if we could.
> I'm trying to recall... does the coLinux installer crash during the
> install (probably the colinux-daemon --install-driver), if it does not
> only would we have to display the message, but we'd have to 'abort'
> the install or skip the colinux-daemon --install-driver & inform the
> user of how to run it.
No, the installer is not crashing in the "colinux-daemon
--install-driver". It's later on first running Linux.
>
>> > 5) Create 0.7.x default colinux config which uses initrd.gz & SLiRP to
>> > have a running 'very limited' but internet connected coLinux at the
>> > end of the install.
>>
>> I'm preferred to use the first network with slirp (eth0). Power users
>> should use the second network (eth1) for additional types (tap,
>> Pcap-bridged). We should clear about this before changing the images,
>> so all images have similar networks on startup.
>
> I think we are in agreement here more or less. But for me power
> users are free to 'take over' eth0 and not use slirp at all if that's
> what they wish to do... Just the installer & images are going to be
> initially set-up that way.
Yes, that I mean.
>
>> > 6) Update install to make TAP optional install and require that it be
>> > specifically selected.
>>
>> Very good idea. The Pcap-Bridged in same.
>
> Yes, if Pcap-Bridge is not already this way it should be this way.
> Except that PCap's actuall driver needs to be a seperate install like
> it is now. This is a request from the PCap project's developers.
>
>> The installer should have two or more "InstType". For sample Standard,
>> Full and User. The Standard should be the typical installation with
>> Slirp only and a Debian (or ArchLinux) image.
>
> I'm not targetting this situation in this release of coLinux, but I'm
> not against it either.
OK. Stike it out.
>> The installer should uncompressing the image file, selectable by a
>> checkbox "yes/no".
>
> Again, I'm not targetting this for this release of coLinux. If we do
> something like this, I feel that if at all possible, we should do a
> free space check that includes this file uncompressed... otherwise we
> are just inviting users to be frustrated when they download coLinux
> run the install and it dies uncompressing because it ran out of disk
> space.
Hm. This would be complicated. The installer is not known the unpacked
size.
--
Henry Nestler
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
coLinux-devel mailing list
coLinux-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/colinux-devel
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ coLinux-devel mailing list coLinux-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/colinux-devel
Date: September 15, 2006
From: "Bill C. Riemers" <docbill@xxxxxxxxxxxxx>
In-reply-to:
<450A64AA.20302@xxxxxxxx>
References:
<121565a0609021611j607dda70ge71799c55bbbb8fd@xxxxxxxxxxxxxx> <45087188.2050200@xxxxxxxx> <121565a0609141418t31bc8bf8j76f1439d016e06c8@xxxxxxxxxxxxxx> <450A64AA.20302@xxxxxxxx>
George P Boutwell wrote:
> On 9/13/06, Henry Nestler <Henry.Ne@xxxxxxxx> wrote:
>> > 3) Re-Write the README for 0.7.x, Ideally I'd like the new README to
>> > be short and brief and give folks pointers where to go for most of the
>> > information that's in there now.
>>
>> Add a text file or html as manual, that shows the parameter, the config
>> options and some samples. Currently it's scattered in various files
>> (RUNNING, doc/colinux-daemon, doc/cofs) with unsorted samples.
>
> Is was thinking basically that we get the colinux-daemon to dump it
> out (more or less does now), or like you suggest provide an 'man page'
> in text file that ships with colinux.
Not a real man page.
Yes, the dumps where gets from colinux-daemon starts without parameter
should put into the text file. Think, nobody would run this daemon to
get the parameter.
One text file with a list of all parameters. And a sample to that
parameter. In the same text file the config parameters and one or more
samples. Remove the text file doc/cofs.
>> > 4) Update/Create an 0.7.x Known Issues/Problems page that could be
>> > pointed to from the README
>>
>> If we can not solve the DEP/Noexecute bug: The instaler should show an
>> extra page with a warning and a "howto change the boot.ini ...". The
>> installer should sheck the CPU for typical candidate for crashing
>> (Intel, >1GB RAM + SP2 + PAE enabled + boot.ini has an entry
>> noexecute=OptIn)
>
> Hmm... I'm ok with that. I'd rather track down the problem and fix
> it, though if we could.
> I'm trying to recall... does the coLinux installer crash during the
> install (probably the colinux-daemon --install-driver), if it does not
> only would we have to display the message, but we'd have to 'abort'
> the install or skip the colinux-daemon --install-driver & inform the
> user of how to run it.
No, the installer is not crashing in the "colinux-daemon
--install-driver". It's later on first running Linux.
>
>> > 5) Create 0.7.x default colinux config which uses initrd.gz & SLiRP to
>> > have a running 'very limited' but internet connected coLinux at the
>> > end of the install.
>>
>> I'm preferred to use the first network with slirp (eth0). Power users
>> should use the second network (eth1) for additional types (tap,
>> Pcap-bridged). We should clear about this before changing the images,
>> so all images have similar networks on startup.
>
> I think we are in agreement here more or less. But for me power
> users are free to 'take over' eth0 and not use slirp at all if that's
> what they wish to do... Just the installer & images are going to be
> initially set-up that way.
Yes, that I mean.
>
>> > 6) Update install to make TAP optional install and require that it be
>> > specifically selected.
>>
>> Very good idea. The Pcap-Bridged in same.
>
> Yes, if Pcap-Bridge is not already this way it should be this way.
> Except that PCap's actuall driver needs to be a seperate install like
> it is now. This is a request from the PCap project's developers.
>
>> The installer should have two or more "InstType". For sample Standard,
>> Full and User. The Standard should be the typical installation with
>> Slirp only and a Debian (or ArchLinux) image.
>
> I'm not targetting this situation in this release of coLinux, but I'm
> not against it either.
OK. Stike it out.
>> The installer should uncompressing the image file, selectable by a
>> checkbox "yes/no".
>
> Again, I'm not targetting this for this release of coLinux. If we do
> something like this, I feel tha