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-10 03:12:04
|
Bugs item #2357595, was opened at 2008-11-29 03:59 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2357595&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: Fixed Priority: 7 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Henry N. (henryn) Summary: Some network card can't work well with ndis-bridge Initial Comment: "Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller", this card is integrated with asus p5q-se motherboard(I have updated to the latest driver), ping between the host and the colinux will hang the host(but arping works well). I also tested another card "Realtek RTL8168C(P)/8111C(P) PCI-E Gigabit Ethernet NIC", it is integrated with giga ep31 motherboard, but it did not have this problem. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-10 02:44 Message: Was a wrong parameter in case of non pending packet after NdisSend. Found and committed to SVN as revision r1218. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-12-09 22:32 Message: This is hard to debug. I found an error in co_debug now. All back call handlers, for example SendCompleteHandler=co_conet_proto_send_complete are in "IRQL: DISPATCH_LEVEL", see Requirements on this article http://msdn.microsoft.com/en-us/library/ms797308.aspx If we call a KeWaitForSingleObject from DISPATCH_LEVEL we risk a BSOD Bug Check 0xB8: ATTEMPTED_SWITCH_FROM_DPC (http://msdn.microsoft.com/en-us/library/ms795832.aspx). Exactly that does co_debug(), so I can not use it. An interesting article about IRQL I found here: http://ext2fsd.sourceforge.net/documents/irql.htm For the NdisSend, I assume any of the completion call backs tries NdisAcquireSpinLock, and that can hang on disabled interrupts (DISPATCH_LEVEL = disabled interrupts). NdisAcquireSpinLock is a macro for KeAcquireSpinLock. Should we use NdisDprAcquireSpinLock (alias KeAcquireSpinLockAtDpcLevel) in this call back routines? For better overview have created function flows graphics from ndis driver: http://www.henrynestler.com/colinux/codeviz/ndis-bridge/ ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-12-07 23:38 Message: Have a host with same problem. - That's good, so I can trace it. A ping from coLinux to host freezes the host. The card is a Realtek RTL8102E Family PCI-E Fast Ethernet NIC. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-12-04 08:15 Message: pcap-bridge did not have this problem. I also upgraded to 1130, this problem still existed. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-12-02 22:21 Message: The real problem is NdisSend() with dest == hostMac, previous comment is wrong. Drop packet with dest == OID_802_3_CURRENT_ADDRESS fix it, but host & guest can't commucation anymore. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-12-01 15:25 Message: After some research, I think the problem is packet forward loop. Filtering out packets from virtual mac to self/broadcast packets seems fix it. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-12-01 14:42 Message: New snapshot 1130 solve the Non-IP packet problem. This time I meet this bug too, my card is Atheros L2. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-12-01 00:16 Message: What does the problem, if you replace the ndis-bridge with pcap-bridge? Today the filter rule for ndis-bridge was changed. Perhaps this solves your problem? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2357595&group_id=98788 |
|
From: coLinux a. <col...@he...> - 2009-02-09 05:07:03
|
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-20090208/ colinux-0.8.0-20090208.src.tgz (684975 Bytes) daemons-0.8.0-20090208.dbg.zip (591647 Bytes) daemons-0.8.0-20090208.zip (478664 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 ------------------------------------------------------------------------ r1217 | henryn | 2009-02-08 20:44:06 +0000 (Sun, 08 Feb 2009) | 1 line Changed paths: M /branches/devel/src/colinux/user/slirp/tcp_input.c * Remove trailing whitespaces. ------------------------------------------------------------------------ r1216 | henryn | 2009-02-08 20:28:10 +0000 (Sun, 08 Feb 2009) | 1 line Changed paths: M /branches/devel/src/colinux/user/slirp/tcp_input.c * Slirp update from Qemu: TCPREXMTTHRESH as macro. ------------------------------------------------------------------------ r1215 | henryn | 2009-02-08 20:10:15 +0000 (Sun, 08 Feb 2009) | 1 line Changed paths: M /branches/devel/NEWS * Update news. ------------------------------------------------------------------------ r1214 | henryn | 2009-02-08 19:59:35 +0000 (Sun, 08 Feb 2009) | 2 lines Changed paths: M /branches/devel/src/colinux/user/slirp/tcp_input.c * Bug#2055697: Crashing SLiRP under heavy usage ktorrent. (Thanks Shai Vaingast) ------------------------------------------------------------------------ |
|
From: SourceForge.net <no...@so...> - 2009-02-08 20:09:04
|
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: Open Resolution: None 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-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: coLinux a. <col...@he...> - 2009-02-06 05:11:15
|
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-20090205/ colinux-0.8.0-20090205.src.tgz (684843 Bytes) daemons-0.8.0-20090205.dbg.zip (591796 Bytes) daemons-0.8.0-20090205.zip (478660 Bytes) modules-2.6.22.18-co-0.8.0-20090205.tgz (2599999 Bytes) vmlinux-2.6.22.18-co-0.8.0-20090205.zip (1762289 Bytes) Note, the autobuild compilation does not include an installer. Remember to reload the driver with these commands: colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver Inside coLinux please update modules as follow: rm -rf /lib/modules/*-co-* tar -xzf modules-*-co-*-20090205.tgz -C / The autobuild compilations are not official releases of Cooperative Linux software. There is no warranty that any autobuild version is stable. If use this autobuild version, please give us feedback of your experience. Job runs on machine with 64 bit version of gcc 4.1.2. A service from http://gcc.gnu.org/wiki/CompileFarm -- Lots of fun with newest version, Henry Nestler ------------------------------------------------------------------------ r1213 | henryn | 2009-02-05 21:42:14 +0000 (Thu, 05 Feb 2009) | 1 line Changed paths: M /branches/devel/src/colinux/os/winnt/kernel/conet.c * ndis-bridge: Bugfix "duplicate address detected". Filter out packets from send our self. ------------------------------------------------------------------------ r1212 | henryn | 2009-02-05 21:24:04 +0000 (Thu, 05 Feb 2009) | 4 lines Changed paths: M /branches/devel/patch/base-2.6.22.diff * Bug#2524658: Fixup FPU-faults on Raid from using MMX/XMM-registers. Disable SSE-instructions for raid-modules only. Leave userland SSE-Exceptions allowed, for example in Eclipse under Java. Read also comments on SVN revision r1205:r1207 and Bug#2551241. ------------------------------------------------------------------------ r1211 | henryn | 2009-02-05 21:03:15 +0000 (Thu, 05 Feb 2009) | 1 line Changed paths: M /branches/devel/patch/base-2.6.22.diff M /branches/devel/patch/timer-2.6.22.diff * Bug#2551241: Undoing commits in r1207+r1208 because this faults Eclipse. ------------------------------------------------------------------------ |
|
From: SourceForge.net <no...@so...> - 2009-02-06 00:15:29
|
Bugs item #2055697, was opened at 2008-08-17 12:15 Message generated for change (Settings changed) 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: Open Resolution: None 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-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-06 00:12:39
|
Bugs item #2055697, was opened at 2008-08-17 12:15 Message generated for change (Settings changed) 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: None Group: v0.7.x (release) Status: Closed Resolution: None 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-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-05 22:27:10
|
Bugs item #2551241, was opened at 2009-01-31 04:47 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&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: Fixed Priority: 5 Private: No Submitted By: Arya (aryairani) Assigned to: Henry N. (henryn) Summary: eclipse 3.4 won't start under devel-20090121 Initial Comment: Running XP Pro SP2. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-02-05 22:07 Message: Changes on MMX/XMM CPU caps reverted and committed as SVN revision 1211, so I close this bug for now. The Bug#2524658 on Raid we will change in an other way. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-02-02 20:57 Message: Have grepped some more and found: function do_simd_coprocessor_error() in kernel file arch/i386/kernel/traps.c This handles SSE exception from userland task. If MMX is disabled (coLinux 20080121), then it generates a SIGSEGV and kills the current task. If MMX is enabled, it sends a signal SIGFPE to the application (in the function simd_math_error). I will try to disable the MMX inside the raid5 + raid6 only, in same way it was for raid5 before. That means: No SSE-Instructions in kernel code, but allow SSE in user space. Of curse it would be nicer, to allow SSE-instructions also inside kernel code. But I have no idea to solve the problem, that started these bug. For the modules: initrd does not update the modules for same kernel version. initrd only copies modules ones per kernel version. That works only for released coLinux versions, but not for devel installations. Please update the modules manually by unpacking the modules tar from your current running kernel. If you have a initrd, than you can do it as follow: mkdir /mnt/cofs mount -t cofs cofs31 /mnt/cofs tar -xzf /mnt/cofs/vmlinux-modules.tar.gz -C / umount /mnt/cofs rmdir /mnt/cofs But I think, it is not a problem inside modules. All the CPU caps flags are inside the kernel file vmlinux. ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-02-02 06:40 Message: >From the first crash, maybe it is dying in a native method... Also, maybe Eclipse *doesn't* run on X86 machines without MMX... Have there been any made in the last 15 years? :) ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-02-02 06:37 Message: File Added: hs_err_pid2733.log ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-02-02 06:37 Message: The ThreadCountdownExtThread program builds and runs fine. (I had tried myself with an even simpler program before.) I see what you mean about the sse flags in the error log. I tried dpkg-reconfigure sun-java6-bin and sun-java6-jdk with no apparent improvement. I think I have the right kernel and modules for 20091221; I used the installer this time, and have initrd enabled in my config. If you think this might be the problem, is there some way I can verify that I have the right flies, from within colinux? my cpuinfo under 20091221: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi fxsr sse2 ss ht tm pbe constant_tsc pni monitor ds_cpl est tm2 cid xtpr arya@co-calculon:~$ eclipse/eclipse # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (nmethod.cpp:1707), pid=2954, tid=3085133488 # Error: guarantee(cont_offset != 0,"unhandled implicit exception in compiled code") # # Java VM: Java HotSpot(TM) Client VM (10.0-b23 mixed mode, sharing linux-x86) # An error report file with more information is saved as: # /home/arya/hs_err_pid2954.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Aborted arya@co-calculon:~$ ----------- with nofxsr, i get a different error: # # An unexpected error has been detected by Java Runtime Environment: # # SIGILL (0x4) at pc=0xb5223201, pid=2733, tid=3084830384 # # Java VM: Java HotSpot(TM) Client VM (10.0-b23 mixed mode, sharing linux-x86) # Problematic frame: # v ~BufferBlob::StubRoutines (1) # # An error report file with more information is saved as: # /home/arya/hs_err_pid2733.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Aborted Confusing! Still seems to run fine under devel-20091220. File Added: hs_err_pid2954.log ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-02-01 20:17 Message: I'm afraid, this is not directly a problem of SSE-instructions. If that so, then Eclipse would never run on CPU without XMM- and MMX-registers. The disabling of SSE is to simple to be the condition for the crash. In the last change, have disabled the CPU capability flags X86_FEATURE_MMX and X86_FEATURE_XMM. Similar does the kernel command line option "nofxsr" with X86_FEATURE_XMM and X86_FEATURE_FXSR. Please add "nofxsr" to coLinux config file and try the build devel-20090120 with Eclipse. I don't understand why Eclipse (or the Java behind) would use SSE instructions. and why it should crash on MMX/XMM-disabled CPU. All applications or kernel code, that use XMM/MMX-registers must save and restore the registers and must do this within disabled interrupts. Inside the kernel don't exist any code to global handle MMX/XMM-registers. All I found was an exclusive usage of these registers in the source of raid for i386. In last lines of you log I found "CPU:total 1 (1 cores per cpu, 2 threads per core) family 15 model 4 stepping 1, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ht". So, from where Java got this informations about mmx and sse? Does the Java runtime directly accessing these special registers? Arya, please try "dpkg-reconfigure sun-java6-bin" under the non SSE coLinux. I have JDK (Java 5) installed and a HelloWorld and a thread example runs nice. Arya, please try this on your system: Download the example from: http://www.idevelopment.info/data/Programming/java/threads/ThreadCountdownExtThread.java than run: javac ThreadCountdownExtThread.java java ThreadCountdownExtThread I have tested with packages sun-java5-bin and sun-java5-jdk installed. You have Java 6, so please check there with sun-java6-bin and sun-java6-jdk. My cpuinfo under coLinux-20090121: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi fxsr sse2 ss ht tm pbe nx constant_tsc pni monitor ds_cpl est tm2 ssse3 xtpr lahf_lm Eclipse is truly a very resource hungry application. Are you sure, that you have enough memory? Have you complete updated the kernel _and_ all modules for devel-20090121? ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 05:03 Message: P.S. It's not a problem for me to go back to SSE-enabled builds, I don't really need raid, I was just playing around with it earlier :) ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 04:50 Message: crap, I accidentally submitted an empty report when trying to upload crash log. no problem under 0.7.3 or devel-20090120, only under devel-20090121. I think eclipse is executing some SSE instructions, thus crashing under 20090121... I don't know under which circumstances javac emits SSE instructions, so I wasn't able to construct a simpler test case... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-05 22:24:46
|
Bugs item #2524658, was opened at 2009-01-20 21:54 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2524658&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: Pending Resolution: Accepted Priority: 5 Private: No Submitted By: Arya (aryairani) Assigned to: Henry N. (henryn) Summary: GPF trying to activate raid5 md array in 0.7.3 Initial Comment: I'm using the 0.7.3 release with the Ubuntu 7.10 disk image on XP Pro SP2. I'm very excited about being able to use coLinux to access md arrays under Windows. But I'm having some trouble. I've tried creating arrays using /dev/loopX, and also /dev/cobdX, with varying degrees of failure. sudo apt-get install mdadm mkdir ~/raid for i in ~/raid/{a,b,c,d}; do dd if=/dev/zero of=$i bs=10M count=1; sudo losetup -f $i; done arya@co-calculon:~/raid$ sudo losetup -a /dev/loop0: [7500]:16841 (/home/arya/raid/a) /dev/loop1: [7500]:16843 (/home/arya/raid/b) /dev/loop2: [7500]:16844 (/home/arya/raid/c) /dev/loop3: [7500]:16845 (/home/arya/raid/d) $ sudo modprobe md-mod $ sudo mdadm --create /dev/md0 --level=5 --raid-devices=4 /dev/loop{0,1,2,3} mdadm: array /dev/md0 started. arya@co-calculon:~/raid$ Looks good so far, right? But dmesg shows a GPF: md: bind<loop0> md: bind<loop1> md: bind<loop2> md: bind<loop3> raid5: automatically using best checksumming function: pIII_sse pIII_sse : 2469.600 MB/sec raid5: using function: pIII_sse (2469.600 MB/sec) raid6: int32x1 407 MB/s raid6: int32x2 678 MB/s raid6: int32x4 523 MB/s raid6: int32x8 480 MB/s raid6: mmxx1 1571 MB/s raid6: mmxx2 1866 MB/s raid6: sse1x1 933 MB/s raid6: sse1x2 1696 MB/s raid6: sse2x1 1742 MB/s raid6: sse2x2 2623 MB/s raid6: using algorithm sse2x2 (2623 MB/s) md: raid6 personality registered for level 6 md: raid5 personality registered for level 5 md: raid4 personality registered for level 4 raid5: device loop2 operational as raid disk 2 raid5: device loop1 operational as raid disk 1 raid5: device loop0 operational as raid disk 0 raid5: allocated 4196kB for md0 raid5: raid level 5 set md0 active with 3 out of 4 devices, algorithm 2 RAID5 conf printout: --- rd:4 wd:3 disk 0, o:1, dev:loop0 disk 1, o:1, dev:loop1 disk 2, o:1, dev:loop2 RAID5 conf printout: --- rd:4 wd:3 disk 0, o:1, dev:loop0 disk 1, o:1, dev:loop1 disk 2, o:1, dev:loop2 disk 3, o:1, dev:loop3 md: recovery of RAID array md0 md: minimum _guaranteed_ speed: 1000 KB/sec/disk. md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery. md: using 128k window, over a total of 10176 blocks. general protection fault: 0000 [#1] PREEMPT Modules linked in: raid456 xor md_mod ipv6 fuse CPU: 0 EIP: 0060:[<c0103d46>] Not tainted VLI EFLAGS: 00010002 (2.6.22.18-co-0.7.3 #1) EIP is at math_state_restore+0x26/0x50 eax: 8005003b ebx: d8814ab0 ecx: db4aed00 edx: 00000000 esi: db0a8000 edi: db4add00 ebp: db0a9ce0 esp: db0a9cd8 ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0068 Process md0_raid5 (pid: 2803, ti=db0a8000 task=d8814ab0 task.ti=db0a8000) Stack: db4abd00 db4acd00 db0a9d78 c01038fe db4abd00 db4aed00 00000003 db4acd00 db4add00 db0a9d78 db0a9d2c c146007b d881007b 00000000 ffffffff e0814bf3 00000060 00010206 8005003b db4ae000 00000010 00000000 00000000 00000000 Call Trace: [<c0103bba>] show_trace_log_lvl+0x1a/0x30 [<c0103c79>] show_stack_log_lvl+0xa9/0xd0 [<c01040eb>] show_registers+0x21b/0x3a0 [<c0104365>] die+0xf5/0x210 [<c010534d>] do_general_protection+0x1ad/0x1f0 [<c02a999a>] error_code+0x6a/0x70 [<c01038fe>] device_not_available+0x2e/0x33 [<e081282e>] xor_block+0x6e/0xa0 [xor] [<e095eaf8>] compute_block+0xd8/0x130 [raid456] [<e095fce7>] handle_stripe5+0x1197/0x13c0 [raid456] [<e0961522>] handle_stripe+0x32/0x16f0 [raid456] [<e0964007>] raid5d+0x2f7/0x450 [raid456] [<e094db00>] md_thread+0x30/0x100 [md_mod] [<c0123d32>] kthread+0x42/0x70 [<c01039c7>] kernel_thread_helper+0x7/0x10 ======================= Code: c3 8d 74 26 00 55 89 e5 83 ec 08 89 74 24 04 89 e6 89 1c 24 81 e6 00 e0 ff ff 8b 1e 0f 06 f6 43 0d 20 75 07 89 d8 e8 9a 37 00 00 <0f> ae 8b 10 02 00 00 83 4e 0c 01 fe 83 8d 01 00 00 8b 1c 24 8b EIP: [<c0103d46>] math_state_restore+0x26/0x50 SS:ESP 0068:db0a9cd8 note: md0_raid5[2803] exited with preempt_count 2 For reference: arya@co-calculon:~/raid$ sudo mdadm /dev/md0 /dev/md0: 29.81MiB raid5 4 devices, 1 spare. Use mdadm --detail for more detail. arya@co-calculon:~/raid$ sudo mdadm --detail /dev/md0 /dev/md0: Version : 00.90.03 Creation Time : Tue Jan 20 15:36:06 2009 Raid Level : raid5 Array Size : 30528 (29.82 MiB 31.26 MB) Used Dev Size : 10176 (9.94 MiB 10.42 MB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Tue Jan 20 15:36:06 2009 State : clean, degraded, recovering Active Devices : 3 Working Devices : 4 Failed Devices : 0 Spare Devices : 1 Layout : left-symmetric Chunk Size : 64K Rebuild Status : 0% complete UUID : 106a26c3:fae68f05:bc6a5c1d:79f7e806 (local to host co-calculon) Events : 0.1 Number Major Minor RaidDevice State 0 7 0 0 active sync /dev/loop0 1 7 1 1 active sync /dev/loop1 2 7 2 2 active sync /dev/loop2 4 7 3 3 spare rebuilding /dev/loop3 So due to the GPF the array is stuck in a degraded state. I'm pretty sure it's not actually recovering at this point. arya@co-calculon:~/raid$ sudo mdadm --stop /dev/md0 mdadm: fail to stop array /dev/md0: Device or resource busy arya@co-calculon:~/raid$ dmesg | tail -n 1 md: md0 still in use. arya@co-calculon:~/raid$ ----------------- Anyway, I tried again using block devices mapped to windows files: arya@co-calculon:~/raid$ cat /proc/partitions major minor #blocks name 117 0 2097152 cobd0 117 1 128 cobd1 117 3 2144646 cobd3 117 5 10240 cobd5 117 6 10240 cobd6 117 7 10240 cobd7 117 8 10240 cobd8 117 9 10240 cobd9 7 0 10240 loop0 7 1 10240 loop1 7 2 10240 loop2 7 3 10240 loop3 9 0 30528 md0 arya@co-calculon:~/raid$ sudo mdadm --create /dev/md1 --level=5 --raid-devices=4 /dev/cobd{5,6,7,8} dmesg shows: md: bind<cobd5> md: bind<cobd6> md: bind<cobd7> md: bind<cobd8> raid5: device cobd7 operational as raid disk 2 raid5: device cobd6 operational as raid disk 1 raid5: device cobd5 operational as raid disk 0 raid5: allocated 4196kB for md1 raid5: raid level 5 set md1 active with 3 out of 4 devices, algorithm 2 RAID5 conf printout: --- rd:4 wd:3 disk 0, o:1, dev:cobd5 disk 1, o:1, dev:cobd6 disk 2, o:1, dev:cobd7 RAID5 conf printout: --- rd:4 wd:3 disk 0, o:1, dev:cobd5 disk 1, o:1, dev:cobd6 disk 2, o:1, dev:cobd7 disk 3, o:1, dev:cobd8 md: recovery of RAID array md1 md: minimum _guaranteed_ speed: 1000 KB/sec/disk. md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery. md: using 128k window, over a total of 10176 blocks. general protection fault: 0000 [#2] PREEMPT Modules linked in: raid456 xor md_mod ipv6 fuse CPU: 0 EIP: 0060:[<c0103d46>] Not tainted VLI EFLAGS: 00010002 (2.6.22.18-co-0.7.3 #1) EIP is at math_state_restore+0x26/0x50 eax: 8005003b ebx: daa2d530 ecx: d91a5500 edx: 00000000 esi: d8fbe000 edi: d91a4500 ebp: d8fbfce0 esp: d8fbfcd8 ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0068 Process md1_raid5 (pid: 2888, ti=d8fbe000 task=daa2d530 task.ti=d8fbe000) Stack: d91a2500 d91a3500 d8fbfd78 c01038fe d91a2500 d91a5500 0000000b d91a3500 d91a4500 d8fbfd78 d8fbfd2c 0000007b 0000007b 00000000 ffffffff e0814aa8 00000060 00010202 8005003b d91a5000 00000010 00000000 00000000 00000000 Call Trace: [<c0103bba>] show_trace_log_lvl+0x1a/0x30 [<c0103c79>] show_stack_log_lvl+0xa9/0xd0 [<c01040eb>] show_registers+0x21b/0x3a0 [<c0104365>] die+0xf5/0x210 [<c010534d>] do_general_protection+0x1ad/0x1f0 [<c02a999a>] error_code+0x6a/0x70 [<c01038fe>] device_not_available+0x2e/0x33 [<e081282e>] xor_block+0x6e/0xa0 [xor] [<e095eaf8>] compute_block+0xd8/0x130 [raid456] [<e095fce7>] handle_stripe5+0x1197/0x13c0 [raid456] [<e0961522>] handle_stripe+0x32/0x16f0 [raid456] [<e0964007>] raid5d+0x2f7/0x450 [raid456] [<e094db00>] md_thread+0x30/0x100 [md_mod] [<c0123d32>] kthread+0x42/0x70 [<c01039c7>] kernel_thread_helper+0x7/0x10 ======================= Code: c3 8d 74 26 00 55 89 e5 83 ec 08 89 74 24 04 89 e6 89 1c 24 81 e6 00 e0 ff ff 8b 1e 0f 06 f6 43 0d 20 75 07 89 d8 e8 9a 37 00 00 <0f> ae 8b 10 02 00 00 83 4e 0c 01 fe 83 8d 01 00 00 8b 1c 24 8b EIP: [<c0103d46>] math_state_restore+0x26/0x50 SS:ESP 0068:d8fbfcd8 note: md1_raid5[2888] exited with preempt_count 2 On a previous attempt, I've also had it take colinux-daemon.exe into an infinite loop or something: arya@co-calculon:~$ cat /proc/partitions major minor #blocks name 117 0 2097152 cobd0 117 1 128 cobd1 117 5 10240 cobd5 117 6 10240 cobd6 117 7 10240 cobd7 117 8 10240 cobd8 117 9 10240 cobd9 arya@co-calculon:~$ sudo mdadm --create /dev/md0 --level=5 --raid-devices=4 /dev/cobd{5,6,7,8} mdadm: error opening /dev/md0: No such device or address arya@co-calculon:~$ sudo modprobe md-mod arya@co-calculon:~$ sudo mdadm --create /dev/md0 --level=5 --raid-devices=4 /dev/cobd{5,6,7,8} *crash* Can't kill colinux-daemon.exe, which is using 100% of one HT "cpu". colinux-daemon.exe output shows: md: bind<cobd5> md: bind<cobd6> md: bind<cobd7> md: bind<cobd8> raid5: automatically using best checksumming function: pIII_sse pIII_sse : 2282.400 MB/sec raid5: using function: pIII_sse (2282.400 MB/sec) raid6: int32x1 712 MB/s raid6: int32x2 714 MB/s raid6: int32x4 537 MB/s raid6: int32x8 491 MB/s raid6: mmxx1 1533 MB/s raid6: mmxx2 1893 MB/s raid6: sse1x1 954 MB/s console window shows this much, can't see where it started: [<c0103c79>] show_stack_log_lvl+0xa9/0xd0 [<c01040eb>] show_registers+0x21b/0x3a0 [<c0104365>] die+0xf5/0x210 [<c010b6fc>] do_page_fault+0x38c/0x6e0 [<c02a999a>] error_code+0x6a/0x70 [<c010c3f8>] deactivate_task+0x18/0x30 [<c02a7777>] __sched_text_start+0x377/0x670 [<c01144b4>] do_exit+0x7d4/0x940 [<c010447d>] die+0x20d/0x210 [<c010b6fc>] do_page_fault+0x38c/0x6e0 [<c02a999a>] error_code+0x6a/0x70 [<c010c3f8>] deactivate_task+0x18/0x30 [<c02a7777>] __sched_text_start+0x377/0x670 [<c01144b4>] do_exit+0x7d4/0x940 [<c010447d>] die+0x20d/0x210 [<c010b6fc>] do_page_fault+0x38c/0x6e0 [<c02a999a>] error_code+0x6a/0x70 [<c010c3f8>] deactivate_task+0x18/0x30 [<c02a7777>] __sched_text_start+0x377/0x670 [<c01144b4>] do_exit+0x7d4/0x940 [<c010447d>] die+0x20d/0x210 [<c010b6fc>] do_page_fault+0x38c/0x6e0 [<c02a999a>] error_code+0x6a/0x70 [<c010c3f8>] deactivate_task+0x18/0x30 Thanks for the all the amazing work already! ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-05 23:01 Message: Problems from disabling MMX/XMM in CPU caps we have seen on Bug#2551241. SSE-instructions needs to disable in kernel space only. SSE was used only for raid modules. Userland SSE-instractions should not disable. Eclipse/Java needs SIMD-Exceptions. So, only Raid modules are disabled for such instructions now. Committed as SVN revision r1212. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-01-24 13:57 Message: SSE2 is an extension of SSE. It is harmless, as long SSE is not enabled. SSE2 operations are not used without SSE support. In the kernel SSE is the macro X86_FEATURE_XMM (Streaming SIMD Extensions). SSE2 is X86_FEATURE_XMM2. The general problem is, that inside usage of MMX or SSE registers we can not allow an OS switch. These registers are not saved for OS switch. In native Linux kernel this is handled by disabling interrupts or by calling the preempt_disable() or kernel_fpu_begin(). But under coLinux we needs an OS switch for example for page allocations. Such will ends in an endless FPU fault loop. I will close this bug now and write some about SSE and MMX into the ToDo list. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-01-24 04:01 Message: The temporary fix seems to be working fine for raid5 and raid6 under the cases I tested before. Thanks! P.S. SSE2 flags is present in /proc/cpuinfo, but the RAID6 benchmark doesn't include sse2 anymore. Was that intentional? Cheers ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-01-22 19:31 Message: Hello Arya, it should be fixed generally now for all raid levels, and all other drivers. You will find the build under http://www.colinux.org/snapshots/ and in autobuild. Please remember to reboot after you have updated modules in your directory /lib/modules, and replace your kernel. In the kernel file "vmlinux" is the most important change. A very simple test for the crash was: while true; do rmmod raid456; rmmod xor; modprobe xor; modprobe raid456; sleep 1; done PS: I don't know why SF has dropped my post from yesterday here. :-( ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-01-21 21:07 Message: > raid6: mmxx1 739 MB/s > raid6: mmxx2 992 MB/s > raid6: sse1x1 462 MB/s > raid6: sse1x2 873 MB/s > raid6: sse2x1 1012 MB/s > raid6: sse2x2 1511 MB/s Oh yea, for raid6 some more "sse" operations are hidden in other files. I will fix it more generic, by disable all XMM/MMX features in the cpu caps. Please stand by and check the next autobuild. > [...] > Works ok with cobdX devices, I don't know why it crashed the firs time? I'm afraid, the old module "xor.ko" was always loaded at the time you have extracted the modules to /lib/modules. You need to reboot after update the modules. For the old raid5 I was testing very simple: while true; do rmmod xor; insmod xor.ko; sleep 1; done After 2...10 loops it's crashing. ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-21 18:23 Message: Whoops, duplicate post. ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-21 18:22 Message: Double-check same issue for raid6 (sse2x2?): arya@co-calculon:~/raid-test$ sudo mdadm --create /dev/md0 --level 6 --raid-devices=4 /dev/cobd{5,6,7,8} md: md0: raid array is not clean -- starting background reconstruction raid5: device cobd8 operational as raid disk 3 raid5: device cobd7 operational as raid disk 2 raid5: device cobd6 operational as raid disk 1 raid5: device cobd5 operational as raid disk 0 raid5: allocated 4196kB for md0 raid5: raid level 6 set md0 active with 4 out of 4 devices, algorithm 2 RAID5 conf printout: --- rd:4 wd:4 disk 0, o:1, dev:cobd5 disk 1, o:1, dev:cobd6 disk 2, o:1, dev:cobd7 disk 3, o:1, dev:cobd8 md: resync of RAID array md0 md: minimum _guaranteed_ speed: 1000 KB/sec/disk. md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync. md: using 128k window, over a total of 10176 blocks. general protection fault: 0000 [#1] PREEMPT Modules linked in: raid456 xor md_mod ipv6 fuse CPU: 0 <0>EIP: 0060:[<c0103d46>] Not tainted VLI <0>EFLAGS: 00010002 (2.6.22.18-co-0.8.0 #1) EIP is at math_state_restore+0x26/0x50 eax: 8005003b ebx: c15efab0 ecx: ffffffff edx: 00000000 esi: da812000 edi: 000003a0 ebp: da813db8 esp: da813db0 ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0068 Process md0_raid5 (pid: 2795, ti=da812000 task=c15efab0 task.ti=da812000) <0>Stack: da813e3c 000003a0 da813e24 c01038fe da813e3c ffffffff db686000 000003a0 <0> 000003a0 da813e24 db6863a0 0000007b 0000007b da810000 ffffffff e08c2d8b <0> 00000060 00010206 000003a0 00001000 00000004 da813e44 da813e40 db687000 <0>Call Trace: [<c0103bba>] show_trace_log_lvl+0x1a/0x30 [<c0103c79>] show_stack_log_lvl+0xa9/0xd0 [<c01040eb>] show_registers+0x21b/0x3a0 [<c0104365>] die+0xf5/0x210 [<c010534d>] do_general_protection+0x1ad/0x1f0 [<c03057fa>] error_code+0x6a/0x70 [<c01038fe>] device_not_available+0x2e/0x33 [<e08bdf8f>] compute_parity6+0x19f/0x330 [raid456] [<e08bfa40>] handle_stripe+0x1550/0x16f0 [raid456] [<e08c1007>] raid5d+0x2f7/0x450 [raid456] [<e0846b00>] md_thread+0x30/0x100 [md_mod] [<c0124462>] kthread+0x42/0x70 [<c01039c7>] kernel_thread_helper+0x7/0x10 ======================= Code: c3 8d 74 26 00 55 89 e5 83 ec 08 89 74 24 04 89 e6 89 1c 24 81 e6 00 e0 ff ff 8b 1e 0f 06 f6 43 0d 20 75 07 89 d8 e8 ea 38 00 00 <0f> ae 8b 10 02 00 00 83 4e 0c 01 fe 83 8d 01 00 00 8b 1c 24 8b EIP: [<c0103d46>] math_state_restore+0x26/0x50 SS:ESP 0068:da813db0 note: md0_raid5[2795] exited with preempt_count 2 ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-21 10:47 Message: Double-check same issue for raid6 (sse2x2?): arya@co-calculon:~/raid-test$ sudo mdadm --create /dev/md0 --level 6 --raid-devices=4 /dev/cobd{5,6,7,8} md: md0: raid array is not clean -- starting background reconstruction raid5: device cobd8 operational as raid disk 3 raid5: device cobd7 operational as raid disk 2 raid5: device cobd6 operational as raid disk 1 raid5: device cobd5 operational as raid disk 0 raid5: allocated 4196kB for md0 raid5: raid level 6 set md0 active with 4 out of 4 devices, algorithm 2 RAID5 conf printout: --- rd:4 wd:4 disk 0, o:1, dev:cobd5 disk 1, o:1, dev:cobd6 disk 2, o:1, dev:cobd7 disk 3, o:1, dev:cobd8 md: resync of RAID array md0 md: minimum _guaranteed_ speed: 1000 KB/sec/disk. md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync. md: using 128k window, over a total of 10176 blocks. general protection fault: 0000 [#1] PREEMPT Modules linked in: raid456 xor md_mod ipv6 fuse CPU: 0 <0>EIP: 0060:[<c0103d46>] Not tainted VLI <0>EFLAGS: 00010002 (2.6.22.18-co-0.8.0 #1) EIP is at math_state_restore+0x26/0x50 eax: 8005003b ebx: c15efab0 ecx: ffffffff edx: 00000000 esi: da812000 edi: 000003a0 ebp: da813db8 esp: da813db0 ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0068 Process md0_raid5 (pid: 2795, ti=da812000 task=c15efab0 task.ti=da812000) <0>Stack: da813e3c 000003a0 da813e24 c01038fe da813e3c ffffffff db686000 000003a0 <0> 000003a0 da813e24 db6863a0 0000007b 0000007b da810000 ffffffff e08c2d8b <0> 00000060 00010206 000003a0 00001000 00000004 da813e44 da813e40 db687000 <0>Call Trace: [<c0103bba>] show_trace_log_lvl+0x1a/0x30 [<c0103c79>] show_stack_log_lvl+0xa9/0xd0 [<c01040eb>] show_registers+0x21b/0x3a0 [<c0104365>] die+0xf5/0x210 [<c010534d>] do_general_protection+0x1ad/0x1f0 [<c03057fa>] error_code+0x6a/0x70 [<c01038fe>] device_not_available+0x2e/0x33 [<e08bdf8f>] compute_parity6+0x19f/0x330 [raid456] [<e08bfa40>] handle_stripe+0x1550/0x16f0 [raid456] [<e08c1007>] raid5d+0x2f7/0x450 [raid456] [<e0846b00>] md_thread+0x30/0x100 [md_mod] [<c0124462>] kthread+0x42/0x70 [<c01039c7>] kernel_thread_helper+0x7/0x10 ======================= Code: c3 8d 74 26 00 55 89 e5 83 ec 08 89 74 24 04 89 e6 89 1c 24 81 e6 00 e0 ff ff 8b 1e 0f 06 f6 43 0d 20 75 07 89 d8 e8 ea 38 00 00 <0f> ae 8b 10 02 00 00 83 4e 0c 01 fe 83 8d 01 00 00 8b 1c 24 8b EIP: [<c0103d46>] math_state_restore+0x26/0x50 SS:ESP 0068:da813db0 note: md0_raid5[2795] exited with preempt_count 2 ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-21 10:19 Message: The previous post was with 0.8.0 daily. Here I tried again, creating a new array rather than reassembling like with the previous example. It seems to have worked? md: bind<loop0> md: bind<loop1> md: bind<loop2> md: bind<loop3> raid5: measuring checksumming speed 8regs : 1577.200 MB/sec 8regs_prefetch: 1398.800 MB/sec 32regs : 788.000 MB/sec 32regs_prefetch: 861.600 MB/sec raid5: using function: 8regs (1577.200 MB/sec) raid6: int32x1 323 MB/s raid6: int32x2 321 MB/s raid6: int32x4 277 MB/s raid6: int32x8 258 MB/s raid6: mmxx1 739 MB/s raid6: mmxx2 992 MB/s raid6: sse1x1 462 MB/s raid6: sse1x2 873 MB/s raid6: sse2x1 1012 MB/s raid6: sse2x2 1511 MB/s raid6: using algorithm sse2x2 (1511 MB/s) md: raid6 personality registered for level 6 md: raid5 personality registered for level 5 md: raid4 personality registered for level 4 raid5: device loop2 operational as raid disk 2 raid5: device loop1 operational as raid disk 1 raid5: device loop0 operational as raid disk 0 raid5: allocated 4196kB for md0 raid5: raid level 5 set md0 active with 3 out of 4 devices, algorithm 2 RAID5 conf printout: --- rd:4 wd:3 disk 0, o:1, dev:loop0 disk 1, o:1, dev:loop1 disk 2, o:1, dev:loop2 RAID5 conf printout: --- rd:4 wd:3 disk 0, o:1, dev:loop0 disk 1, o:1, dev:loop1 disk 2, o:1, dev:loop2 disk 3, o:1, dev:loop3 md: recovery of RAID array md0 md: minimum _guaranteed_ speed: 1000 KB/sec/disk. md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery. md: using 128k window, over a total of 10176 blocks. md: md0: recovery done. RAID5 conf printout: --- rd:4 wd:4 disk 0, o:1, dev:loop0 disk 1, o:1, dev:loop1 disk 2, o:1, dev:loop2 disk 3, o:1, dev:loop3 Works ok with cobdX devices, I don't know why it crashed the firs time? ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-21 09:55 Message: Bad news, md: md0 stopped. md: bind<loop1> md: bind<loop2> md: bind<loop3> md: bind<loop0> md: md0 stopped. md: unbind<loop0> md: export_rdev(loop0) md: unbind<loop3> md: export_rdev(loop3) md: unbind<loop2> md: export_rdev(loop2) md: unbind<loop1> md: export_rdev(loop1) md: bind<loop1> md: bind<loop2> md: bind<loop3> md: bind<loop0> raid5: measuring checksumming speed 8regs : 1292.800 MB/sec 8regs_prefetch: 1210.400 MB/sec 32regs : 1184.000 MB/sec 32regs_prefetch: 1428.800 MB/sec raid5: using function: 32regs_prefetch (1428.800 MB/sec) raid6: int32x1 605 MB/s raid6: int32x2 563 MB/s raid6: int32x4 444 MB/s raid6: int32x8 424 MB/s raid6: mmxx1 1355 MB/s raid6: mmxx2 1579 MB/s raid6: sse1x1 758 MB/s raid6: sse1x2 1541 MB/s raid6: sse2x1 1667 MB/s colinux-console-nt only shows this much, which is missing the registers / EIP dump... [<c0103c79>] show_stack_log_lvl+0xa9/0xd0 [<c01040eb>] show_registers+0x21b/0x3a0 [<c0104365>] die+0xf5/0x210 [<c010b6cc>] do_page_fault+0x38c/0x6e0 [<c03057fa>] error_code+0x6a/0x70 [<c010c5c8>] deactivate_task+0x18/0x30 [<c03035d7>] __sched_text_start+0x377/0x670 [<c0114814>] do_exit+0x7f4/0x960 [<c010447d>] die+0x20d/0x210 [<c010b6cc>] do_page_fault+0x38c/0x6e0 [<c03057fa>] error_code+0x6a/0x70 [<c010c5c8>] deactivate_task+0x18/0x30 [<c03035d7>] __sched_text_start+0x377/0x670 [<c0114814>] do_exit+0x7f4/0x960 [<c010447d>] die+0x20d/0x210 [<c010b6cc>] do_page_fault+0x38c/0x6e0 [<c03057fa>] error_code+0x6a/0x70 [<c010c5c8>] deactivate_task+0x18/0x30 [<c03035d7>] __sched_text_start+0x377/0x670 [<c0114814>] do_exit+0x7f4/0x960 [<c010447d>] die+0x20d/0x210 [<c010b6cc>] do_page_fault+0x38c/0x6e0 [<c03057fa>] error_code+0x6a/0x70 [<c010c5c8>] deactivate_task+0x18/0x30 ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-21 01:29 Message: Excellent, thanks for tracking that down, henryn. I'll test the daily tomorrow, with the temporary fix, if it will still help? ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-01-21 00:31 Message: Loading and unloading a special version of module "raid456.ko" with only calling the function "calibrate_xor_block" does exactly your results: Crashing in math_state_restore, lots of page faults, and windows can not shutting down. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-01-20 23:53 Message: I assume, that the "pIII_sse" use a special register, we not have saved and restored in the passage page. That can crash the "math_state_restore". One option would be to support these xmm-registers for "sse", but currently I don't have idea how. The problem can be near the XMMS_SAVE/XMMS_RESTORE in top of include/asm-i386/xor.h: #define XMMS_SAVE do { \ preempt_disable(); \ cr0 = read_cr0(); \ clts(); \ These operations are well known candidate for crash and for endless page faults. Same we know from function math_state_restore in arch/i386/traps.c. A "clts" while hardware interrupts are enabled can crash coLinux. maniputating the register cr0 is also a high risk. The function "xor_block_pIII_sse" with special macros XMMS_SAVE/XMMS_RESTORE needs to check separately in a kernel test module, outside of the raid. Think, there needs something to do. As temporally idea have disabled the usage of xmm- and mmx-registers under coLinux for the xor-raid-functions. Please check the next autobuild. ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-20 22:09 Message: The 100% cpu crash seems reproducible if the cobd array is the first one I try to create that boot (i.e. the modules are being loaded for the first time?) Also (though not verified), I get the 100% cpu crash when making an array based on loop block devices if the loop devices are created to point to files using relative paths rather than absolute? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2524658&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-05 22:23:54
|
Bugs item #2548486, was opened at 2009-01-30 10:28 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2548486&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: Configuration Group: v0.8.x (devel) >Status: Closed >Resolution: Wont Fix Priority: 5 Private: No Submitted By: Arya (aryairani) Assigned to: Nobody/Anonymous (nobody) Summary: no networking when running devel-20090121 as NT service Initial Comment: Works fine when running from commandline: > colinux-daemon @config.conf but > colinux-daemon --install-service coLinux @config.conf > net start colinux results in linux booting without eth. Can you reproduce? Thanks, Arya P.S. Also it hung as I was switching back and forth between console and service instances C:\coLinux\devel-20090121>net stop colinux The coLinux service is stopping........ The coLinux service could not be stopped. But that was the first time it hanged. But it was also the first time I was switching back and forth much, to collect log info. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-05 23:05 Message: Ok. It was a problem from configuration. Will close this bug now. ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 05:53 Message: Thanks henryn, I used option A with great success. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-01-31 02:16 Message: Hello Arya, this is a problem of "udev" and different user accounts from start as service vs. command line start. coLinux stores the random created MACs inside the per User registry. So, you will have different MACs between the different starts. Ones use the Windows System account and the other the local User account. You will have different MAC for the network adapters between the different boot types. In the not working "run as service" you would see the networks as eth2 and eth3, I'm afraid. You can check this with this command on Linux: cat /proc/net/dev More about this "udev" problem can read here: https://sourceforge.net/tracker/index.php?func=detail&aid=1861876&group_id=98788&atid=622063 To fix this, you have two options: A) Copy the working random MACs to the config to have the same all times. 1. Run command line version 2. copy the MAC you will find with "ifconfig" for eth0 and eth1 3. paste these MACs to your config.conf after the eth0 and eth1, for example: eth0=slirp,00:ff:xx:xx:xx:xx eth1=tuntap,,00:ff:xx:xx:xx:xx Fill out the xx with your digits. Remember to set two commas on eth1 to skip the TAP-Name. 4. Shutdown coLinux and run it as service B) Setup a self made MAC for both adapters 1. Run coLinux 2. Remove all lines from /etc/udev/rules.d/z25_persistent-net.rules inside your Ubuntu. 3. Please add unique MAC number for each network in config.conf, for example eth0=slirp,02:00:00:00:00:01 eth1=tuntap,,02:00:00:00:00:02 Remember to set two commas on eth1 to skip the TAP-Name. A simple rule for self creating such MAC numbers: It should start with 02, and than follow ten random hex digits. The number you will use, should not exist in your network area near you. 4. Shutdown coLinux and start it again (don't use "reboot") With next starts it should have networks in both starting variants all times. For the "service could not be stopped" have no idea. Please open a new bug report, if you have more details. ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 00:59 Message: Sorry about that. XP Pro SP2 kernel=vmlinux cobd0="c:\coLinux\Ubuntu-7.10.ext3.2GB\Ubuntu-7.10.ext3.2gb.fs" cobd1="c:\coLinux\Ubuntu-7.10.ext3.2GB\swap128.fs" cobd2="\Device\Cdrom0" cobd3="\Device\Harddisk0\Partition4" cobd4="\Device\Harddisk0\Partition2" cofs0=c:\ cofs1=d:\ root=/dev/cobd0 ro eth0=slirp eth1=tuntap Again, networking works fine when I launch from commandline, no networking when I launch as service. I haven't checked whether cofs works or not when launching as a service... ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-01-30 10:49 Message: Please upload or paste your config.conf here. What is your host system? Windows XP with SP..., or Windows 2000? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2548486&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-05 21:07:43
|
Bugs item #2551241, was opened at 2009-01-31 04:47 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&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: None Priority: 5 Private: No Submitted By: Arya (aryairani) >Assigned to: Henry N. (henryn) Summary: eclipse 3.4 won't start under devel-20090121 Initial Comment: Running XP Pro SP2. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-05 22:07 Message: Changes on MMX/XMM CPU caps reverted and committed as SVN revision 1211, so I close this bug for now. The Bug#2524658 on Raid we will change in an other way. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-02-02 20:57 Message: Have grepped some more and found: function do_simd_coprocessor_error() in kernel file arch/i386/kernel/traps.c This handles SSE exception from userland task. If MMX is disabled (coLinux 20080121), then it generates a SIGSEGV and kills the current task. If MMX is enabled, it sends a signal SIGFPE to the application (in the function simd_math_error). I will try to disable the MMX inside the raid5 + raid6 only, in same way it was for raid5 before. That means: No SSE-Instructions in kernel code, but allow SSE in user space. Of curse it would be nicer, to allow SSE-instructions also inside kernel code. But I have no idea to solve the problem, that started these bug. For the modules: initrd does not update the modules for same kernel version. initrd only copies modules ones per kernel version. That works only for released coLinux versions, but not for devel installations. Please update the modules manually by unpacking the modules tar from your current running kernel. If you have a initrd, than you can do it as follow: mkdir /mnt/cofs mount -t cofs cofs31 /mnt/cofs tar -xzf /mnt/cofs/vmlinux-modules.tar.gz -C / umount /mnt/cofs rmdir /mnt/cofs But I think, it is not a problem inside modules. All the CPU caps flags are inside the kernel file vmlinux. ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-02-02 06:40 Message: >From the first crash, maybe it is dying in a native method... Also, maybe Eclipse *doesn't* run on X86 machines without MMX... Have there been any made in the last 15 years? :) ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-02-02 06:37 Message: File Added: hs_err_pid2733.log ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-02-02 06:37 Message: The ThreadCountdownExtThread program builds and runs fine. (I had tried myself with an even simpler program before.) I see what you mean about the sse flags in the error log. I tried dpkg-reconfigure sun-java6-bin and sun-java6-jdk with no apparent improvement. I think I have the right kernel and modules for 20091221; I used the installer this time, and have initrd enabled in my config. If you think this might be the problem, is there some way I can verify that I have the right flies, from within colinux? my cpuinfo under 20091221: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi fxsr sse2 ss ht tm pbe constant_tsc pni monitor ds_cpl est tm2 cid xtpr arya@co-calculon:~$ eclipse/eclipse # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (nmethod.cpp:1707), pid=2954, tid=3085133488 # Error: guarantee(cont_offset != 0,"unhandled implicit exception in compiled code") # # Java VM: Java HotSpot(TM) Client VM (10.0-b23 mixed mode, sharing linux-x86) # An error report file with more information is saved as: # /home/arya/hs_err_pid2954.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Aborted arya@co-calculon:~$ ----------- with nofxsr, i get a different error: # # An unexpected error has been detected by Java Runtime Environment: # # SIGILL (0x4) at pc=0xb5223201, pid=2733, tid=3084830384 # # Java VM: Java HotSpot(TM) Client VM (10.0-b23 mixed mode, sharing linux-x86) # Problematic frame: # v ~BufferBlob::StubRoutines (1) # # An error report file with more information is saved as: # /home/arya/hs_err_pid2733.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Aborted Confusing! Still seems to run fine under devel-20091220. File Added: hs_err_pid2954.log ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-02-01 20:17 Message: I'm afraid, this is not directly a problem of SSE-instructions. If that so, then Eclipse would never run on CPU without XMM- and MMX-registers. The disabling of SSE is to simple to be the condition for the crash. In the last change, have disabled the CPU capability flags X86_FEATURE_MMX and X86_FEATURE_XMM. Similar does the kernel command line option "nofxsr" with X86_FEATURE_XMM and X86_FEATURE_FXSR. Please add "nofxsr" to coLinux config file and try the build devel-20090120 with Eclipse. I don't understand why Eclipse (or the Java behind) would use SSE instructions. and why it should crash on MMX/XMM-disabled CPU. All applications or kernel code, that use XMM/MMX-registers must save and restore the registers and must do this within disabled interrupts. Inside the kernel don't exist any code to global handle MMX/XMM-registers. All I found was an exclusive usage of these registers in the source of raid for i386. In last lines of you log I found "CPU:total 1 (1 cores per cpu, 2 threads per core) family 15 model 4 stepping 1, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ht". So, from where Java got this informations about mmx and sse? Does the Java runtime directly accessing these special registers? Arya, please try "dpkg-reconfigure sun-java6-bin" under the non SSE coLinux. I have JDK (Java 5) installed and a HelloWorld and a thread example runs nice. Arya, please try this on your system: Download the example from: http://www.idevelopment.info/data/Programming/java/threads/ThreadCountdownExtThread.java than run: javac ThreadCountdownExtThread.java java ThreadCountdownExtThread I have tested with packages sun-java5-bin and sun-java5-jdk installed. You have Java 6, so please check there with sun-java6-bin and sun-java6-jdk. My cpuinfo under coLinux-20090121: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi fxsr sse2 ss ht tm pbe nx constant_tsc pni monitor ds_cpl est tm2 ssse3 xtpr lahf_lm Eclipse is truly a very resource hungry application. Are you sure, that you have enough memory? Have you complete updated the kernel _and_ all modules for devel-20090121? ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 05:03 Message: P.S. It's not a problem for me to go back to SSE-enabled builds, I don't really need raid, I was just playing around with it earlier :) ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 04:50 Message: crap, I accidentally submitted an empty report when trying to upload crash log. no problem under 0.7.3 or devel-20090120, only under devel-20090121. I think eclipse is executing some SSE instructions, thus crashing under 20090121... I don't know under which circumstances javac emits SSE instructions, so I wasn't able to construct a simpler test case... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-05 19:38:26
|
Bugs item #2055697, was opened at 2008-08-17 13:15 Message generated for change (Comment added) made by vshai 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: None Group: v0.7.x (release) Status: Closed Resolution: None 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: Shai (vshai) Date: 2009-02-05 21: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 19: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 10: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 10: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 16: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 13: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-04 02:08:53
|
Bugs item #1959846, was opened at 2008-05-07 18:38 Message generated for change (Comment added) made by jdstroy You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1959846&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: v0.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: George V. Reilly (george_v_reilly) Assigned to: Nobody/Anonymous (nobody) Summary: Bugcheck in coLinux when starting VM from Virtual PC 2007 Initial Comment: I sent the message below to Dan Aloni but never got a reply. I would have filed a bug back then, but there's no obvious link to the SF bug tracker on the colinux.org website. ---------- Forwarded message ---------- From: George V. Reilly <ge...@re...> Date: 2008/4/10 Subject: Bugcheck in coLinux when starting VM from VPC2007 To: Dan Aloni <da...@co...> I installed andLinux beta 1 rc6 yesterday, on a 4GB quad-core box running x86 Vista SP1. As soon as I launch a virtual machine in Virtual PC 2007, I get a bugcheck in colinux-daemon. This is 100% repeatable. 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: 80154000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ PEB is paged out (Peb.Ldr = 7ffdb00c). Type ".hh dbgerr001" for details PEB is paged out (Peb.Ldr = 7ffdb00c). Type ".hh dbgerr001" for details BUGCHECK_STR: 0x7f_8 TSS: 00000028 -- (.tss 0x28) eax=0000000d ebx=73571250 ecx=883a8ac0 edx=73571280 esi=00000000 edi=73571132 eip=81d0576a esp=73570e6c ebp=73571220 iopl=0 nv up di pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010002 nt!KeBugCheck2+0x1f: 81d0576a 89442424 mov dword ptr [esp+24h],eax ss:0010:73570e90=???????? Resetting default scope DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: colinux-daemon. CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 00000000 to 81d0576a STACK_TEXT: 00000000 81d0576a 00000000 00000000 00000000 nt!KiTrap08+0x75 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTrap08+75 81c91b9e ebee jmp nt!KiTrap08+0x65 (81c91b8e) SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiTrap08+75 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 47918b12 FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap08+75 BUCKET_ID: 0x7f_8_nt!KiTrap08+75 Followup: MachineOwner --------- 0: kd> kv ChildEBP RetAddr Args to Child 00000000 81d0576a 00000000 00000000 00000000 nt!KiTrap08+0x75 (FPO: TSS 28:0) 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f 0: kd> .tss 0x28 eax=0000000d ebx=73571250 ecx=883a8ac0 edx=73571280 esi=00000000 edi=73571132 eip=81d0576a esp=73570e6c ebp=73571220 iopl=0 nv up di pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010002 nt!KeBugCheck2+0x1f: 81d0576a 89442424 mov dword ptr [esp+24h],eax ss:0010:73570e90=???????? 0: kd> kv *** Stack trace for last set context - .thread/.cxr resets it ChildEBP RetAddr Args to Child 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f 0: kd> .ecxr Unable to get exception context, HRESULT 0x8000FFFF 0: kd> !thread THREAD 883a8ac0 Cid 0978.09c0 Teb: 7ffde000 Win32Thread: 00000000 RUNNING on processor 0 IRP List: 87e239f8: (0006,0094) Flags: 00060070 Mdl: 00000000 87e69f68: (0006,0094) Flags: 00060900 Mdl: 88dff0a0 Not impersonating DeviceMap 8ae08808 Owning Process 883855b8 Image: colinux-daemon.exe Wait Start TickCount 53407 Ticks: 0 Context Switch Count 85610 UserTime 00:00:00.031 KernelTime 00:00:05.397 Win32 Start Address 0x766cd1b9 Stack Init 8b243000 Current 8b2429b8 Base 8b243000 Limit 8b240000 Call 0 Priority 9 BasePriority 8 PriorityDecrement 0 IoPriority 2 PagePriority 5 ChildEBP RetAddr Args to Child 00000000 81d0576a 00000000 00000000 00000000 nt!KiTrap08+0x75 (FPO: TSS 28:0) 73571220 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x1f 0: kd> !pcr KPCR for Processor 0 at 81d30800: Major 1 Minor 1 NtTib.ExceptionList: 81d2abe8 NtTib.StackBase: 00000000 NtTib.StackLimit: 00000000 NtTib.SubSystemTib: 80154000 NtTib.Version: 003cb6e5 NtTib.UserPointer: 00000001 NtTib.SelfTib: 7ffde000 SelfPcr: 81d30800 Prcb: 81d30920 Irql: 0000001f IRR: 00000000 IDR: ffffffff InterruptMode: 00000000 IDT: 81afd400 GDT: 81afd000 TSS: 81d2e000 CurrentThread: 883a8ac0 NextThread: 00000000 IdleThread: 81d34640 DpcQueue: I have a crashdump, compressed down to 57MB at http://www.georgevreilly.com/temp/colinux-daemon.dmp.bz2 ---------------------------------------------------------------------- Comment By: John Stroy (jdstroy) Date: 2009-02-03 21:06 Message: This happens in 0.7.3 as well. 2.6.22.18-co-0.7.3 #1 PREEMPT Sat May 24 22:27:30 UTC 2008 i686 06/17 I got this to happen on Windows Server 2003 Enterprise Edition with MSVPC2007. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-05-09 19:26 Message: Logged In: YES user_id=579204 Originator: NO 0.7.1 has an known bug. Double, triple and endless faults I have seen. See http://www.andlinux.org/news.php for "Apr 18th, 2008". This was fixed in "Apr 21st, 2008: andLinux Beta 1 (final)" I not know ho you can update andLinux version without reinstalling all images. You can still update the coLinux executable files, linux.sys, vmlinux and modules from http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080416-Snapshot/packages/ No, your file have not loaded. Your output are well good and enough. I'm not familiar with this debugger. "!analyze -v" is all I know to do. If the bug would be in the linux.sys, then the !analyse would list such helpfull STACK, for example: http://www.henrynestler.com/colinux/testing/pfn-check-0.7.3/20080410-antinx/minidump041108-01.txt But the known bug is inside Linux kernel and pokes some wildly into the hosts memory, so we never have seen it from Windows debugger. The real interesting summary can read from this file: http://www.henrynestler.com/colinux/testing/pfn-check-0.7.3/20080410-antinx/bug16-recursive-page-fault-endless.txt ---------------------------------------------------------------------- Comment By: George V. Reilly (george_v_reilly) Date: 2008-05-09 18:45 Message: Logged In: YES user_id=737437 Originator: YES coLinux was installed by andLinux, not directly by me. C:\Program Files\andLinux>colinux-daemon --status-driver Cooperative Linux Daemon, 0.7.1 Compiled on Sat Jul 14 12:15:18 2007 checking if the driver is installed current state: 4 (fully initialized) current number of monitors: 1 current linux api version: 10 current periphery api version: 20 I'm running both andLinux and VPC 2007 on the same instance of Vista x86 SP1. They're peers. Vista is the host for both VPC and andLinux. andLinux is *not* running inside Virtual PC. Did you try downloading http://www.georgevreilly.com/temp/colinux-daemon.dmp.bz2 and examining it inside WinDbg? That contains the kernel's state at the moment it bugchecked. The !analyze output above isn't enough to tell you why it crashed. I'm not in a position today to attach a kernel debugger to this machine. It's my main dev machine and I don't want to do things that might bluescreen it. I'll install andLinux on another machine and see if I can repro the issue there. ---------------------------------------------------------------------- Comment By: George V. Reilly (george_v_reilly) Date: 2008-05-09 18:44 Message: Logged In: YES user_id=737437 Originator: YES coLinux was installed by andLinux, not directly by me. C:\Program Files\andLinux>colinux-daemon --status-driver Cooperative Linux Daemon, 0.7.1 Compiled on Sat Jul 14 12:15:18 2007 checking if the driver is installed current state: 4 (fully initialized) current number of monitors: 1 current linux api version: 10 current periphery api version: 20 I'm running both andLinux and VPC 2007 on the same instance of Vista x86 SP1. They're peers. Vista is the host for both VPC and andLinux. andLinux is *not* running inside Virtual PC. Did you try downloading http://www.georgevreilly.com/temp/colinux-daemon.dmp.bz2 and examining it inside WinDbg? That contains the kernel's state at the moment it bugchecked. The !analyze output above isn't enough to tell you why it crashed. I'm not in a position today to attach a kernel debugger to this machine. It's my main dev machine and I don't want to do things that might bluescreen it. I'll install andLinux on another machine and see if I can repro the issue there. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-05-09 16:50 Message: Logged In: YES user_id=579204 Originator: NO Hello George, Dan is not active anymore. In the bugcheck I can not see any informations why it crashes. Shure, I see colinux-daemon process was named. If I see right, this userland task kills the nt kernel driver? That I can not understand. In typically bugs the colinux-daemon calls linux.sys and this can crash. Why not there? Next question is, what rule have VPC2007 there? What is the real host for coLinux, and what is the host for VPC2007? You runs VPC2007 as other task on the same machine, and then starts coLinux parallel? Or you have running coLinux and start than VPC2007 parallel? Or runs you one VM in other VM? Is the driver coLinux installed right and running? Please check it with "colinux-daemon --status-driver". Can you run colinux-daemon from in the Windows Debugger? ( I don't know how, please ask Google ) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1959846&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-02 19:57:22
|
Bugs item #2551241, was opened at 2009-01-31 04:47 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&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: Open Resolution: None Priority: 5 Private: No Submitted By: Arya (aryairani) Assigned to: Nobody/Anonymous (nobody) Summary: eclipse 3.4 won't start under devel-20090121 Initial Comment: Running XP Pro SP2. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-02 20:57 Message: Have grepped some more and found: function do_simd_coprocessor_error() in kernel file arch/i386/kernel/traps.c This handles SSE exception from userland task. If MMX is disabled (coLinux 20080121), then it generates a SIGSEGV and kills the current task. If MMX is enabled, it sends a signal SIGFPE to the application (in the function simd_math_error). I will try to disable the MMX inside the raid5 + raid6 only, in same way it was for raid5 before. That means: No SSE-Instructions in kernel code, but allow SSE in user space. Of curse it would be nicer, to allow SSE-instructions also inside kernel code. But I have no idea to solve the problem, that started these bug. For the modules: initrd does not update the modules for same kernel version. initrd only copies modules ones per kernel version. That works only for released coLinux versions, but not for devel installations. Please update the modules manually by unpacking the modules tar from your current running kernel. If you have a initrd, than you can do it as follow: mkdir /mnt/cofs mount -t cofs cofs31 /mnt/cofs tar -xzf /mnt/cofs/vmlinux-modules.tar.gz -C / umount /mnt/cofs rmdir /mnt/cofs But I think, it is not a problem inside modules. All the CPU caps flags are inside the kernel file vmlinux. ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-02-02 06:40 Message: >From the first crash, maybe it is dying in a native method... Also, maybe Eclipse *doesn't* run on X86 machines without MMX... Have there been any made in the last 15 years? :) ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-02-02 06:37 Message: File Added: hs_err_pid2733.log ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-02-02 06:37 Message: The ThreadCountdownExtThread program builds and runs fine. (I had tried myself with an even simpler program before.) I see what you mean about the sse flags in the error log. I tried dpkg-reconfigure sun-java6-bin and sun-java6-jdk with no apparent improvement. I think I have the right kernel and modules for 20091221; I used the installer this time, and have initrd enabled in my config. If you think this might be the problem, is there some way I can verify that I have the right flies, from within colinux? my cpuinfo under 20091221: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi fxsr sse2 ss ht tm pbe constant_tsc pni monitor ds_cpl est tm2 cid xtpr arya@co-calculon:~$ eclipse/eclipse # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (nmethod.cpp:1707), pid=2954, tid=3085133488 # Error: guarantee(cont_offset != 0,"unhandled implicit exception in compiled code") # # Java VM: Java HotSpot(TM) Client VM (10.0-b23 mixed mode, sharing linux-x86) # An error report file with more information is saved as: # /home/arya/hs_err_pid2954.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Aborted arya@co-calculon:~$ ----------- with nofxsr, i get a different error: # # An unexpected error has been detected by Java Runtime Environment: # # SIGILL (0x4) at pc=0xb5223201, pid=2733, tid=3084830384 # # Java VM: Java HotSpot(TM) Client VM (10.0-b23 mixed mode, sharing linux-x86) # Problematic frame: # v ~BufferBlob::StubRoutines (1) # # An error report file with more information is saved as: # /home/arya/hs_err_pid2733.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Aborted Confusing! Still seems to run fine under devel-20091220. File Added: hs_err_pid2954.log ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-02-01 20:17 Message: I'm afraid, this is not directly a problem of SSE-instructions. If that so, then Eclipse would never run on CPU without XMM- and MMX-registers. The disabling of SSE is to simple to be the condition for the crash. In the last change, have disabled the CPU capability flags X86_FEATURE_MMX and X86_FEATURE_XMM. Similar does the kernel command line option "nofxsr" with X86_FEATURE_XMM and X86_FEATURE_FXSR. Please add "nofxsr" to coLinux config file and try the build devel-20090120 with Eclipse. I don't understand why Eclipse (or the Java behind) would use SSE instructions. and why it should crash on MMX/XMM-disabled CPU. All applications or kernel code, that use XMM/MMX-registers must save and restore the registers and must do this within disabled interrupts. Inside the kernel don't exist any code to global handle MMX/XMM-registers. All I found was an exclusive usage of these registers in the source of raid for i386. In last lines of you log I found "CPU:total 1 (1 cores per cpu, 2 threads per core) family 15 model 4 stepping 1, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ht". So, from where Java got this informations about mmx and sse? Does the Java runtime directly accessing these special registers? Arya, please try "dpkg-reconfigure sun-java6-bin" under the non SSE coLinux. I have JDK (Java 5) installed and a HelloWorld and a thread example runs nice. Arya, please try this on your system: Download the example from: http://www.idevelopment.info/data/Programming/java/threads/ThreadCountdownExtThread.java than run: javac ThreadCountdownExtThread.java java ThreadCountdownExtThread I have tested with packages sun-java5-bin and sun-java5-jdk installed. You have Java 6, so please check there with sun-java6-bin and sun-java6-jdk. My cpuinfo under coLinux-20090121: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi fxsr sse2 ss ht tm pbe nx constant_tsc pni monitor ds_cpl est tm2 ssse3 xtpr lahf_lm Eclipse is truly a very resource hungry application. Are you sure, that you have enough memory? Have you complete updated the kernel _and_ all modules for devel-20090121? ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 05:03 Message: P.S. It's not a problem for me to go back to SSE-enabled builds, I don't really need raid, I was just playing around with it earlier :) ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 04:50 Message: crap, I accidentally submitted an empty report when trying to upload crash log. no problem under 0.7.3 or devel-20090120, only under devel-20090121. I think eclipse is executing some SSE instructions, thus crashing under 20090121... I don't know under which circumstances javac emits SSE instructions, so I wasn't able to construct a simpler test case... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-02 05:40:25
|
Bugs item #2551241, was opened at 2009-01-31 03:47 Message generated for change (Comment added) made by aryairani You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&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: Open Resolution: None Priority: 5 Private: No Submitted By: Arya (aryairani) Assigned to: Nobody/Anonymous (nobody) Summary: eclipse 3.4 won't start under devel-20090121 Initial Comment: Running XP Pro SP2. ---------------------------------------------------------------------- >Comment By: Arya (aryairani) Date: 2009-02-02 05:40 Message: >From the first crash, maybe it is dying in a native method... Also, maybe Eclipse *doesn't* run on X86 machines without MMX... Have there been any made in the last 15 years? :) ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-02-02 05:37 Message: File Added: hs_err_pid2733.log ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-02-02 05:37 Message: The ThreadCountdownExtThread program builds and runs fine. (I had tried myself with an even simpler program before.) I see what you mean about the sse flags in the error log. I tried dpkg-reconfigure sun-java6-bin and sun-java6-jdk with no apparent improvement. I think I have the right kernel and modules for 20091221; I used the installer this time, and have initrd enabled in my config. If you think this might be the problem, is there some way I can verify that I have the right flies, from within colinux? my cpuinfo under 20091221: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi fxsr sse2 ss ht tm pbe constant_tsc pni monitor ds_cpl est tm2 cid xtpr arya@co-calculon:~$ eclipse/eclipse # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (nmethod.cpp:1707), pid=2954, tid=3085133488 # Error: guarantee(cont_offset != 0,"unhandled implicit exception in compiled code") # # Java VM: Java HotSpot(TM) Client VM (10.0-b23 mixed mode, sharing linux-x86) # An error report file with more information is saved as: # /home/arya/hs_err_pid2954.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Aborted arya@co-calculon:~$ ----------- with nofxsr, i get a different error: # # An unexpected error has been detected by Java Runtime Environment: # # SIGILL (0x4) at pc=0xb5223201, pid=2733, tid=3084830384 # # Java VM: Java HotSpot(TM) Client VM (10.0-b23 mixed mode, sharing linux-x86) # Problematic frame: # v ~BufferBlob::StubRoutines (1) # # An error report file with more information is saved as: # /home/arya/hs_err_pid2733.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Aborted Confusing! Still seems to run fine under devel-20091220. File Added: hs_err_pid2954.log ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-02-01 19:17 Message: I'm afraid, this is not directly a problem of SSE-instructions. If that so, then Eclipse would never run on CPU without XMM- and MMX-registers. The disabling of SSE is to simple to be the condition for the crash. In the last change, have disabled the CPU capability flags X86_FEATURE_MMX and X86_FEATURE_XMM. Similar does the kernel command line option "nofxsr" with X86_FEATURE_XMM and X86_FEATURE_FXSR. Please add "nofxsr" to coLinux config file and try the build devel-20090120 with Eclipse. I don't understand why Eclipse (or the Java behind) would use SSE instructions. and why it should crash on MMX/XMM-disabled CPU. All applications or kernel code, that use XMM/MMX-registers must save and restore the registers and must do this within disabled interrupts. Inside the kernel don't exist any code to global handle MMX/XMM-registers. All I found was an exclusive usage of these registers in the source of raid for i386. In last lines of you log I found "CPU:total 1 (1 cores per cpu, 2 threads per core) family 15 model 4 stepping 1, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ht". So, from where Java got this informations about mmx and sse? Does the Java runtime directly accessing these special registers? Arya, please try "dpkg-reconfigure sun-java6-bin" under the non SSE coLinux. I have JDK (Java 5) installed and a HelloWorld and a thread example runs nice. Arya, please try this on your system: Download the example from: http://www.idevelopment.info/data/Programming/java/threads/ThreadCountdownExtThread.java than run: javac ThreadCountdownExtThread.java java ThreadCountdownExtThread I have tested with packages sun-java5-bin and sun-java5-jdk installed. You have Java 6, so please check there with sun-java6-bin and sun-java6-jdk. My cpuinfo under coLinux-20090121: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi fxsr sse2 ss ht tm pbe nx constant_tsc pni monitor ds_cpl est tm2 ssse3 xtpr lahf_lm Eclipse is truly a very resource hungry application. Are you sure, that you have enough memory? Have you complete updated the kernel _and_ all modules for devel-20090121? ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 04:03 Message: P.S. It's not a problem for me to go back to SSE-enabled builds, I don't really need raid, I was just playing around with it earlier :) ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 03:50 Message: crap, I accidentally submitted an empty report when trying to upload crash log. no problem under 0.7.3 or devel-20090120, only under devel-20090121. I think eclipse is executing some SSE instructions, thus crashing under 20090121... I don't know under which circumstances javac emits SSE instructions, so I wasn't able to construct a simpler test case... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-02 05:37:58
|
Bugs item #2551241, was opened at 2009-01-31 03:47 Message generated for change (Comment added) made by aryairani You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&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: Open Resolution: None Priority: 5 Private: No Submitted By: Arya (aryairani) Assigned to: Nobody/Anonymous (nobody) Summary: eclipse 3.4 won't start under devel-20090121 Initial Comment: Running XP Pro SP2. ---------------------------------------------------------------------- >Comment By: Arya (aryairani) Date: 2009-02-02 05:37 Message: File Added: hs_err_pid2733.log ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-02-02 05:37 Message: The ThreadCountdownExtThread program builds and runs fine. (I had tried myself with an even simpler program before.) I see what you mean about the sse flags in the error log. I tried dpkg-reconfigure sun-java6-bin and sun-java6-jdk with no apparent improvement. I think I have the right kernel and modules for 20091221; I used the installer this time, and have initrd enabled in my config. If you think this might be the problem, is there some way I can verify that I have the right flies, from within colinux? my cpuinfo under 20091221: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi fxsr sse2 ss ht tm pbe constant_tsc pni monitor ds_cpl est tm2 cid xtpr arya@co-calculon:~$ eclipse/eclipse # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (nmethod.cpp:1707), pid=2954, tid=3085133488 # Error: guarantee(cont_offset != 0,"unhandled implicit exception in compiled code") # # Java VM: Java HotSpot(TM) Client VM (10.0-b23 mixed mode, sharing linux-x86) # An error report file with more information is saved as: # /home/arya/hs_err_pid2954.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Aborted arya@co-calculon:~$ ----------- with nofxsr, i get a different error: # # An unexpected error has been detected by Java Runtime Environment: # # SIGILL (0x4) at pc=0xb5223201, pid=2733, tid=3084830384 # # Java VM: Java HotSpot(TM) Client VM (10.0-b23 mixed mode, sharing linux-x86) # Problematic frame: # v ~BufferBlob::StubRoutines (1) # # An error report file with more information is saved as: # /home/arya/hs_err_pid2733.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Aborted Confusing! Still seems to run fine under devel-20091220. File Added: hs_err_pid2954.log ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-02-01 19:17 Message: I'm afraid, this is not directly a problem of SSE-instructions. If that so, then Eclipse would never run on CPU without XMM- and MMX-registers. The disabling of SSE is to simple to be the condition for the crash. In the last change, have disabled the CPU capability flags X86_FEATURE_MMX and X86_FEATURE_XMM. Similar does the kernel command line option "nofxsr" with X86_FEATURE_XMM and X86_FEATURE_FXSR. Please add "nofxsr" to coLinux config file and try the build devel-20090120 with Eclipse. I don't understand why Eclipse (or the Java behind) would use SSE instructions. and why it should crash on MMX/XMM-disabled CPU. All applications or kernel code, that use XMM/MMX-registers must save and restore the registers and must do this within disabled interrupts. Inside the kernel don't exist any code to global handle MMX/XMM-registers. All I found was an exclusive usage of these registers in the source of raid for i386. In last lines of you log I found "CPU:total 1 (1 cores per cpu, 2 threads per core) family 15 model 4 stepping 1, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ht". So, from where Java got this informations about mmx and sse? Does the Java runtime directly accessing these special registers? Arya, please try "dpkg-reconfigure sun-java6-bin" under the non SSE coLinux. I have JDK (Java 5) installed and a HelloWorld and a thread example runs nice. Arya, please try this on your system: Download the example from: http://www.idevelopment.info/data/Programming/java/threads/ThreadCountdownExtThread.java than run: javac ThreadCountdownExtThread.java java ThreadCountdownExtThread I have tested with packages sun-java5-bin and sun-java5-jdk installed. You have Java 6, so please check there with sun-java6-bin and sun-java6-jdk. My cpuinfo under coLinux-20090121: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi fxsr sse2 ss ht tm pbe nx constant_tsc pni monitor ds_cpl est tm2 ssse3 xtpr lahf_lm Eclipse is truly a very resource hungry application. Are you sure, that you have enough memory? Have you complete updated the kernel _and_ all modules for devel-20090121? ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 04:03 Message: P.S. It's not a problem for me to go back to SSE-enabled builds, I don't really need raid, I was just playing around with it earlier :) ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 03:50 Message: crap, I accidentally submitted an empty report when trying to upload crash log. no problem under 0.7.3 or devel-20090120, only under devel-20090121. I think eclipse is executing some SSE instructions, thus crashing under 20090121... I don't know under which circumstances javac emits SSE instructions, so I wasn't able to construct a simpler test case... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-02 05:37:34
|
Bugs item #2551241, was opened at 2009-01-31 03:47 Message generated for change (Comment added) made by aryairani You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&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: Open Resolution: None Priority: 5 Private: No Submitted By: Arya (aryairani) Assigned to: Nobody/Anonymous (nobody) Summary: eclipse 3.4 won't start under devel-20090121 Initial Comment: Running XP Pro SP2. ---------------------------------------------------------------------- >Comment By: Arya (aryairani) Date: 2009-02-02 05:37 Message: The ThreadCountdownExtThread program builds and runs fine. (I had tried myself with an even simpler program before.) I see what you mean about the sse flags in the error log. I tried dpkg-reconfigure sun-java6-bin and sun-java6-jdk with no apparent improvement. I think I have the right kernel and modules for 20091221; I used the installer this time, and have initrd enabled in my config. If you think this might be the problem, is there some way I can verify that I have the right flies, from within colinux? my cpuinfo under 20091221: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi fxsr sse2 ss ht tm pbe constant_tsc pni monitor ds_cpl est tm2 cid xtpr arya@co-calculon:~$ eclipse/eclipse # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (nmethod.cpp:1707), pid=2954, tid=3085133488 # Error: guarantee(cont_offset != 0,"unhandled implicit exception in compiled code") # # Java VM: Java HotSpot(TM) Client VM (10.0-b23 mixed mode, sharing linux-x86) # An error report file with more information is saved as: # /home/arya/hs_err_pid2954.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Aborted arya@co-calculon:~$ ----------- with nofxsr, i get a different error: # # An unexpected error has been detected by Java Runtime Environment: # # SIGILL (0x4) at pc=0xb5223201, pid=2733, tid=3084830384 # # Java VM: Java HotSpot(TM) Client VM (10.0-b23 mixed mode, sharing linux-x86) # Problematic frame: # v ~BufferBlob::StubRoutines (1) # # An error report file with more information is saved as: # /home/arya/hs_err_pid2733.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Aborted Confusing! Still seems to run fine under devel-20091220. File Added: hs_err_pid2954.log ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-02-01 19:17 Message: I'm afraid, this is not directly a problem of SSE-instructions. If that so, then Eclipse would never run on CPU without XMM- and MMX-registers. The disabling of SSE is to simple to be the condition for the crash. In the last change, have disabled the CPU capability flags X86_FEATURE_MMX and X86_FEATURE_XMM. Similar does the kernel command line option "nofxsr" with X86_FEATURE_XMM and X86_FEATURE_FXSR. Please add "nofxsr" to coLinux config file and try the build devel-20090120 with Eclipse. I don't understand why Eclipse (or the Java behind) would use SSE instructions. and why it should crash on MMX/XMM-disabled CPU. All applications or kernel code, that use XMM/MMX-registers must save and restore the registers and must do this within disabled interrupts. Inside the kernel don't exist any code to global handle MMX/XMM-registers. All I found was an exclusive usage of these registers in the source of raid for i386. In last lines of you log I found "CPU:total 1 (1 cores per cpu, 2 threads per core) family 15 model 4 stepping 1, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ht". So, from where Java got this informations about mmx and sse? Does the Java runtime directly accessing these special registers? Arya, please try "dpkg-reconfigure sun-java6-bin" under the non SSE coLinux. I have JDK (Java 5) installed and a HelloWorld and a thread example runs nice. Arya, please try this on your system: Download the example from: http://www.idevelopment.info/data/Programming/java/threads/ThreadCountdownExtThread.java than run: javac ThreadCountdownExtThread.java java ThreadCountdownExtThread I have tested with packages sun-java5-bin and sun-java5-jdk installed. You have Java 6, so please check there with sun-java6-bin and sun-java6-jdk. My cpuinfo under coLinux-20090121: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi fxsr sse2 ss ht tm pbe nx constant_tsc pni monitor ds_cpl est tm2 ssse3 xtpr lahf_lm Eclipse is truly a very resource hungry application. Are you sure, that you have enough memory? Have you complete updated the kernel _and_ all modules for devel-20090121? ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 04:03 Message: P.S. It's not a problem for me to go back to SSE-enabled builds, I don't really need raid, I was just playing around with it earlier :) ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 03:50 Message: crap, I accidentally submitted an empty report when trying to upload crash log. no problem under 0.7.3 or devel-20090120, only under devel-20090121. I think eclipse is executing some SSE instructions, thus crashing under 20090121... I don't know under which circumstances javac emits SSE instructions, so I wasn't able to construct a simpler test case... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-02-01 19:17:33
|
Bugs item #2551241, was opened at 2009-01-31 04:47 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&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: Open Resolution: None Priority: 5 Private: No Submitted By: Arya (aryairani) Assigned to: Nobody/Anonymous (nobody) Summary: eclipse 3.4 won't start under devel-20090121 Initial Comment: Running XP Pro SP2. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-02-01 20:17 Message: I'm afraid, this is not directly a problem of SSE-instructions. If that so, then Eclipse would never run on CPU without XMM- and MMX-registers. The disabling of SSE is to simple to be the condition for the crash. In the last change, have disabled the CPU capability flags X86_FEATURE_MMX and X86_FEATURE_XMM. Similar does the kernel command line option "nofxsr" with X86_FEATURE_XMM and X86_FEATURE_FXSR. Please add "nofxsr" to coLinux config file and try the build devel-20090120 with Eclipse. I don't understand why Eclipse (or the Java behind) would use SSE instructions. and why it should crash on MMX/XMM-disabled CPU. All applications or kernel code, that use XMM/MMX-registers must save and restore the registers and must do this within disabled interrupts. Inside the kernel don't exist any code to global handle MMX/XMM-registers. All I found was an exclusive usage of these registers in the source of raid for i386. In last lines of you log I found "CPU:total 1 (1 cores per cpu, 2 threads per core) family 15 model 4 stepping 1, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ht". So, from where Java got this informations about mmx and sse? Does the Java runtime directly accessing these special registers? Arya, please try "dpkg-reconfigure sun-java6-bin" under the non SSE coLinux. I have JDK (Java 5) installed and a HelloWorld and a thread example runs nice. Arya, please try this on your system: Download the example from: http://www.idevelopment.info/data/Programming/java/threads/ThreadCountdownExtThread.java than run: javac ThreadCountdownExtThread.java java ThreadCountdownExtThread I have tested with packages sun-java5-bin and sun-java5-jdk installed. You have Java 6, so please check there with sun-java6-bin and sun-java6-jdk. My cpuinfo under coLinux-20090121: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi fxsr sse2 ss ht tm pbe nx constant_tsc pni monitor ds_cpl est tm2 ssse3 xtpr lahf_lm Eclipse is truly a very resource hungry application. Are you sure, that you have enough memory? Have you complete updated the kernel _and_ all modules for devel-20090121? ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 05:03 Message: P.S. It's not a problem for me to go back to SSE-enabled builds, I don't really need raid, I was just playing around with it earlier :) ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 04:50 Message: crap, I accidentally submitted an empty report when trying to upload crash log. no problem under 0.7.3 or devel-20090120, only under devel-20090121. I think eclipse is executing some SSE instructions, thus crashing under 20090121... I don't know under which circumstances javac emits SSE instructions, so I wasn't able to construct a simpler test case... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-01-31 04:54:05
|
Bugs item #2548486, was opened at 2009-01-30 09:28 Message generated for change (Comment added) made by aryairani You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2548486&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: Open Resolution: None Priority: 5 Private: No Submitted By: Arya (aryairani) Assigned to: Nobody/Anonymous (nobody) Summary: no networking when running devel-20090121 as NT service Initial Comment: Works fine when running from commandline: > colinux-daemon @config.conf but > colinux-daemon --install-service coLinux @config.conf > net start colinux results in linux booting without eth. Can you reproduce? Thanks, Arya P.S. Also it hung as I was switching back and forth between console and service instances C:\coLinux\devel-20090121>net stop colinux The coLinux service is stopping........ The coLinux service could not be stopped. But that was the first time it hanged. But it was also the first time I was switching back and forth much, to collect log info. ---------------------------------------------------------------------- >Comment By: Arya (aryairani) Date: 2009-01-31 04:53 Message: Thanks henryn, I used option A with great success. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-01-31 01:16 Message: Hello Arya, this is a problem of "udev" and different user accounts from start as service vs. command line start. coLinux stores the random created MACs inside the per User registry. So, you will have different MACs between the different starts. Ones use the Windows System account and the other the local User account. You will have different MAC for the network adapters between the different boot types. In the not working "run as service" you would see the networks as eth2 and eth3, I'm afraid. You can check this with this command on Linux: cat /proc/net/dev More about this "udev" problem can read here: https://sourceforge.net/tracker/index.php?func=detail&aid=1861876&group_id=98788&atid=622063 To fix this, you have two options: A) Copy the working random MACs to the config to have the same all times. 1. Run command line version 2. copy the MAC you will find with "ifconfig" for eth0 and eth1 3. paste these MACs to your config.conf after the eth0 and eth1, for example: eth0=slirp,00:ff:xx:xx:xx:xx eth1=tuntap,,00:ff:xx:xx:xx:xx Fill out the xx with your digits. Remember to set two commas on eth1 to skip the TAP-Name. 4. Shutdown coLinux and run it as service B) Setup a self made MAC for both adapters 1. Run coLinux 2. Remove all lines from /etc/udev/rules.d/z25_persistent-net.rules inside your Ubuntu. 3. Please add unique MAC number for each network in config.conf, for example eth0=slirp,02:00:00:00:00:01 eth1=tuntap,,02:00:00:00:00:02 Remember to set two commas on eth1 to skip the TAP-Name. A simple rule for self creating such MAC numbers: It should start with 02, and than follow ten random hex digits. The number you will use, should not exist in your network area near you. 4. Shutdown coLinux and start it again (don't use "reboot") With next starts it should have networks in both starting variants all times. For the "service could not be stopped" have no idea. Please open a new bug report, if you have more details. ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-30 23:59 Message: Sorry about that. XP Pro SP2 kernel=vmlinux cobd0="c:\coLinux\Ubuntu-7.10.ext3.2GB\Ubuntu-7.10.ext3.2gb.fs" cobd1="c:\coLinux\Ubuntu-7.10.ext3.2GB\swap128.fs" cobd2="\Device\Cdrom0" cobd3="\Device\Harddisk0\Partition4" cobd4="\Device\Harddisk0\Partition2" cofs0=c:\ cofs1=d:\ root=/dev/cobd0 ro eth0=slirp eth1=tuntap Again, networking works fine when I launch from commandline, no networking when I launch as service. I haven't checked whether cofs works or not when launching as a service... ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-01-30 09:49 Message: Please upload or paste your config.conf here. What is your host system? Windows XP with SP..., or Windows 2000? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2548486&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-01-31 04:03:18
|
Bugs item #2551241, was opened at 2009-01-31 03:47 Message generated for change (Comment added) made by aryairani You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&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: Open Resolution: None Priority: 5 Private: No Submitted By: Arya (aryairani) Assigned to: Nobody/Anonymous (nobody) Summary: eclipse 3.4 won't start under devel-20090121 Initial Comment: Running XP Pro SP2. ---------------------------------------------------------------------- >Comment By: Arya (aryairani) Date: 2009-01-31 04:03 Message: P.S. It's not a problem for me to go back to SSE-enabled builds, I don't really need raid, I was just playing around with it earlier :) ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 03:50 Message: crap, I accidentally submitted an empty report when trying to upload crash log. no problem under 0.7.3 or devel-20090120, only under devel-20090121. I think eclipse is executing some SSE instructions, thus crashing under 20090121... I don't know under which circumstances javac emits SSE instructions, so I wasn't able to construct a simpler test case... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-01-31 03:50:53
|
Bugs item #2551241, was opened at 2009-01-31 03:47 Message generated for change (Comment added) made by aryairani You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&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: Open Resolution: None Priority: 5 Private: No Submitted By: Arya (aryairani) Assigned to: Nobody/Anonymous (nobody) Summary: eclipse 3.4 won't start under devel-20090121 Initial Comment: Running XP Pro SP2. ---------------------------------------------------------------------- >Comment By: Arya (aryairani) Date: 2009-01-31 03:50 Message: crap, I accidentally submitted an empty report when trying to upload crash log. no problem under 0.7.3 or devel-20090120, only under devel-20090121. I think eclipse is executing some SSE instructions, thus crashing under 20090121... I don't know under which circumstances javac emits SSE instructions, so I wasn't able to construct a simpler test case... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-01-31 03:47:34
|
Bugs item #2551241, was opened at 2009-01-31 03:47 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=2551241&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: Open Resolution: None Priority: 5 Private: No Submitted By: Arya (aryairani) Assigned to: Nobody/Anonymous (nobody) Summary: eclipse 3.4 won't start under devel-20090121 Initial Comment: Running XP Pro SP2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-01-31 01:17:09
|
Bugs item #2548486, was opened at 2009-01-30 10:28 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2548486&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: Open Resolution: None Priority: 5 Private: No Submitted By: Arya (aryairani) Assigned to: Nobody/Anonymous (nobody) Summary: no networking when running devel-20090121 as NT service Initial Comment: Works fine when running from commandline: > colinux-daemon @config.conf but > colinux-daemon --install-service coLinux @config.conf > net start colinux results in linux booting without eth. Can you reproduce? Thanks, Arya P.S. Also it hung as I was switching back and forth between console and service instances C:\coLinux\devel-20090121>net stop colinux The coLinux service is stopping........ The coLinux service could not be stopped. But that was the first time it hanged. But it was also the first time I was switching back and forth much, to collect log info. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-01-31 02:16 Message: Hello Arya, this is a problem of "udev" and different user accounts from start as service vs. command line start. coLinux stores the random created MACs inside the per User registry. So, you will have different MACs between the different starts. Ones use the Windows System account and the other the local User account. You will have different MAC for the network adapters between the different boot types. In the not working "run as service" you would see the networks as eth2 and eth3, I'm afraid. You can check this with this command on Linux: cat /proc/net/dev More about this "udev" problem can read here: https://sourceforge.net/tracker/index.php?func=detail&aid=1861876&group_id=98788&atid=622063 To fix this, you have two options: A) Copy the working random MACs to the config to have the same all times. 1. Run command line version 2. copy the MAC you will find with "ifconfig" for eth0 and eth1 3. paste these MACs to your config.conf after the eth0 and eth1, for example: eth0=slirp,00:ff:xx:xx:xx:xx eth1=tuntap,,00:ff:xx:xx:xx:xx Fill out the xx with your digits. Remember to set two commas on eth1 to skip the TAP-Name. 4. Shutdown coLinux and run it as service B) Setup a self made MAC for both adapters 1. Run coLinux 2. Remove all lines from /etc/udev/rules.d/z25_persistent-net.rules inside your Ubuntu. 3. Please add unique MAC number for each network in config.conf, for example eth0=slirp,02:00:00:00:00:01 eth1=tuntap,,02:00:00:00:00:02 Remember to set two commas on eth1 to skip the TAP-Name. A simple rule for self creating such MAC numbers: It should start with 02, and than follow ten random hex digits. The number you will use, should not exist in your network area near you. 4. Shutdown coLinux and start it again (don't use "reboot") With next starts it should have networks in both starting variants all times. For the "service could not be stopped" have no idea. Please open a new bug report, if you have more details. ---------------------------------------------------------------------- Comment By: Arya (aryairani) Date: 2009-01-31 00:59 Message: Sorry about that. XP Pro SP2 kernel=vmlinux cobd0="c:\coLinux\Ubuntu-7.10.ext3.2GB\Ubuntu-7.10.ext3.2gb.fs" cobd1="c:\coLinux\Ubuntu-7.10.ext3.2GB\swap128.fs" cobd2="\Device\Cdrom0" cobd3="\Device\Harddisk0\Partition4" cobd4="\Device\Harddisk0\Partition2" cofs0=c:\ cofs1=d:\ root=/dev/cobd0 ro eth0=slirp eth1=tuntap Again, networking works fine when I launch from commandline, no networking when I launch as service. I haven't checked whether cofs works or not when launching as a service... ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-01-30 10:49 Message: Please upload or paste your config.conf here. What is your host system? Windows XP with SP..., or Windows 2000? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2548486&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-01-30 23:59:34
|
Bugs item #2548486, was opened at 2009-01-30 09:28 Message generated for change (Comment added) made by aryairani You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2548486&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: Open Resolution: None Priority: 5 Private: No Submitted By: Arya (aryairani) Assigned to: Nobody/Anonymous (nobody) Summary: no networking when running devel-20090121 as NT service Initial Comment: Works fine when running from commandline: > colinux-daemon @config.conf but > colinux-daemon --install-service coLinux @config.conf > net start colinux results in linux booting without eth. Can you reproduce? Thanks, Arya P.S. Also it hung as I was switching back and forth between console and service instances C:\coLinux\devel-20090121>net stop colinux The coLinux service is stopping........ The coLinux service could not be stopped. But that was the first time it hanged. But it was also the first time I was switching back and forth much, to collect log info. ---------------------------------------------------------------------- >Comment By: Arya (aryairani) Date: 2009-01-30 23:59 Message: Sorry about that. XP Pro SP2 kernel=vmlinux cobd0="c:\coLinux\Ubuntu-7.10.ext3.2GB\Ubuntu-7.10.ext3.2gb.fs" cobd1="c:\coLinux\Ubuntu-7.10.ext3.2GB\swap128.fs" cobd2="\Device\Cdrom0" cobd3="\Device\Harddisk0\Partition4" cobd4="\Device\Harddisk0\Partition2" cofs0=c:\ cofs1=d:\ root=/dev/cobd0 ro eth0=slirp eth1=tuntap Again, networking works fine when I launch from commandline, no networking when I launch as service. I haven't checked whether cofs works or not when launching as a service... ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-01-30 09:49 Message: Please upload or paste your config.conf here. What is your host system? Windows XP with SP..., or Windows 2000? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2548486&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-01-30 09:49:41
|
Bugs item #2548486, was opened at 2009-01-30 09:28 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2548486&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: Open Resolution: None Priority: 5 Private: No Submitted By: Arya (aryairani) Assigned to: Nobody/Anonymous (nobody) Summary: no networking when running devel-20090121 as NT service Initial Comment: Works fine when running from commandline: > colinux-daemon @config.conf but > colinux-daemon --install-service coLinux @config.conf > net start colinux results in linux booting without eth. Can you reproduce? Thanks, Arya P.S. Also it hung as I was switching back and forth between console and service instances C:\coLinux\devel-20090121>net stop colinux The coLinux service is stopping........ The coLinux service could not be stopped. But that was the first time it hanged. But it was also the first time I was switching back and forth much, to collect log info. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-01-30 09:49 Message: Please upload or paste your config.conf here. What is your host system? Windows XP with SP..., or Windows 2000? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2548486&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-01-30 09:30:11
|
Bugs item #2548486, was opened at 2009-01-30 09:28 Message generated for change (Settings changed) made by aryairani You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2548486&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: Open Resolution: None Priority: 5 Private: No Submitted By: Arya (aryairani) Assigned to: Nobody/Anonymous (nobody) Summary: no networking when running devel-20090121 as NT service Initial Comment: Works fine when running from commandline: > colinux-daemon @config.conf but > colinux-daemon --install-service coLinux @config.conf > net start colinux results in linux booting without eth. Can you reproduce? Thanks, Arya P.S. Also it hung as I was switching back and forth between console and service instances C:\coLinux\devel-20090121>net stop colinux The coLinux service is stopping........ The coLinux service could not be stopped. But that was the first time it hanged. But it was also the first time I was switching back and forth much, to collect log info. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2548486&group_id=98788 |
81 messages has been excluded from this view by a project administrator.
