From owner-freebsd-emulation Mon Nov 2 00:28:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02558 for freebsd-emulation-outgoing; Mon, 2 Nov 1998 00:28:12 -0800 (PST) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from couatl.uchicago.edu (couatl.uchicago.edu [128.135.21.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02553 for ; Mon, 2 Nov 1998 00:28:11 -0800 (PST) (envelope-from sfarrell@couatl.uchicago.edu) Received: (from sfarrell@localhost) by couatl.uchicago.edu (8.9.1/8.9.0) id CAA07622; Mon, 2 Nov 1998 02:28:26 -0600 (CST) To: John Fieber Cc: freebsd emulation list Subject: Linux/Sybase on FreeBSD problems References: From: stephen farrell Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: 02 Nov 1998 02:28:26 -0600 In-Reply-To: John Fieber's message of "Mon, 2 Nov 1998 02:03:28 -0500 (EST)" Message-ID: <874ssi5wid.fsf@couatl.uchicago.edu> Lines: 88 X-Mailer: Gnus v5.6.42/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org emulation ppl: John and I have identical (well as close as we can muster) setups running FreeBSD-3.0R. His runs linux sybase; mine doesn't. We've gone through making sure we have all the same binaries, etc. The problem I have is when the server is first starting up... it seems to get a SEGV after doing a significant amount of work. This result is highly reproducible -- the SEGV always happens at the same time, after reading the same data). John Fieber writes: > On 2 Nov 1998, stephen farrell wrote: > > > http://people.healthquiz.com/~sfarrell/traces/linux_kdump.sf > > http://people.healthquiz.com/~sfarrell/traces/linux_kdump.jf > > > > might this be a race? > > The sigalarms after your SEGV are probably not comparable. As > for the absence of ALRMs up until very near then end, recall that > they are real time based so the fact that you have a wicked fast > CPU, wads of RAM for cache, and I'll bet positively sizzling > disks as well. Consequently I'll be getting a lot more ALRMs sf: p2/400 256MB jf: AMD ?? 64MB > than you during the startup just because it takes my machine a > while to slog through the process. I see--that makes sense. But still, it seems odd to me that the first time I catch a SIGALRM bad stuff happens... > I initially paid a bunch of attention to this when comparing with > a syscall trace made on a linux machine, then realized what was > going on and that it wasn't actually important. The ALRM handler > gets installed pretty early on and if I start the server fresh > and it all has to page in, I get a lot of signals going off > during startup. The second time around, not nearly so many since > everything is in cache and takes much less time. > > Incidentally, when comparing the traces, ran the linux one (the > reference) through cat -n, then went through the marking > corresponding line numbers of various "landmark" events, and in > much more detail in suspicious looking spots. It worked pretty > well and should be much easier for you since both of your traces > are in the same format. :) Hmm... well, yours installs the signal handler here (I'm assuming the memory addresses match up, which might be dubious): There is no sigalrm at this time. 1088 15462 dataserver RET read 2048/0x800 1089 15462 dataserver CALL linux_newselect(0,0x85c56a8,0,0,0x85c55a0) 1090 15462 dataserver RET linux_newselect 0 1091 15462 dataserver CALL linux_sigaction(0x1d,0x85c5494,0) 1092 15462 dataserver RET linux_sigaction 0 1093 15462 dataserver CALL linux_lseek(0x5,0x2800,0) 1094 15462 dataserver RET linux_lseek 10240/0x2800 1095 15462 dataserver CALL read(0x5,0x90be000,0x800) 1096 15462 dataserver GIO fd 5 read 2048 bytes Which is the one mine chokes on here: 26405 434 dataserver CALL linux_sigaction(0x1d,0x85c5494,0) 26406 434 dataserver RET linux_sigaction 0 26407 434 dataserver PSIG SIGSEGV caught handler=0x82955cc mask=0x0 code=0 As far as I can tell, the two traces are pretty much lock-step cruising through the master.dat file, but then mine bails as soon as it gets the SIGALRM. The turning point appears to be 0x5d9800. I guess since they do, in fact, differ, that mine must be trying to do a slightly different thing, which could be significant. Look at http://www.people.healthquiz.com/~sfarrell/traces/seek.txt (jf's trace is on the left; the filehandle replaced by "FH" is master.dat) -- Steve Farrell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Nov 3 16:32:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14301 for freebsd-emulation-outgoing; Tue, 3 Nov 1998 16:32:13 -0800 (PST) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from couatl.uchicago.edu (couatl.uchicago.edu [128.135.21.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14176 for ; Tue, 3 Nov 1998 16:32:03 -0800 (PST) (envelope-from sfarrell@couatl.uchicago.edu) Received: (from sfarrell@localhost) by couatl.uchicago.edu (8.9.1/8.9.0) id SAA01986; Tue, 3 Nov 1998 18:32:11 -0600 (CST) To: freebsd emulation list Subject: Sybase/FreeBSD update From: stephen farrell Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: 03 Nov 1998 18:32:11 -0600 Message-ID: <87yapsz4ac.fsf@couatl.uchicago.edu> Lines: 31 X-Mailer: Gnus v5.6.42/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a follow-up to my last post on the subject of problems with sybase/linux running under emulation in FreeBSD 3.0R. Here's what I've found out: The problem is triggered when maxusers is set from default 32 to 64 (sorry, no other data points). I've narrowed down the various variables that maxusers affect, and maxprocsperuid appears to be the culprit. Interestingly, even if the kernel is built with maxusers 64 (the broken value), then using sysctl to change maxprocsperuid will fix sybase's problem (I think you just need to frob it a bit--it doesn't matter what you set it to (521 is a known working value)). It might also be interesting to note that when sysctl is used to change maxprocsperuid, the value of that variable doesn't change in the kernel (at least as it's referenced in kernel_resource.c). I should point out that it appears to be a general kernel problem and not an emulation problem, as there are no references to maxusers and friends in the linux emulator. Please feel free to contact me for more information, but I don't expect to have a 3.0 box to play with again in the near future (weeks or couple of months). (Yes, I'm punting and using linux for this application... No, I'm not happy about it, but there are many reasons, not least of which is the license. I have put in my word to sybase to get a native port). -- Steve Farrell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Nov 3 23:40:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10236 for freebsd-emulation-outgoing; Tue, 3 Nov 1998 23:40:56 -0800 (PST) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from gates.kppm.ru (kppm.atcom.ru [195.133.148.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10208 for ; Tue, 3 Nov 1998 23:40:46 -0800 (PST) (envelope-from spy@kppm.ru) Received: from spy by gates.kppm.ru (8.8.7/8.8.7) with SMTP id KAA01703 for ; Wed, 4 Nov 1998 10:40:10 +0300 (MSK) (envelope-from spy@kppm.ru) Message-Id: <3.0.6.32.19981104104027.007953a0@kppm.ru> X-Sender: spy@kppm.ru (Unverified) X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 04 Nov 1998 10:40:27 +0300 To: freebsd-emulation@FreeBSD.ORG From: Paul Smirnoff Subject: I want to join the discussion on emulation under FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org HELP JOIN SUBS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Nov 4 07:29:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11192 for freebsd-emulation-outgoing; Wed, 4 Nov 1998 07:29:36 -0800 (PST) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11097 for ; Wed, 4 Nov 1998 07:29:30 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id KAA27281 for ; Wed, 4 Nov 1998 10:29:11 -0500 (EST) Received: from john.baldwinfamily.org (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id KAA20712 for ; Wed, 4 Nov 1998 10:29:10 -0500 (EST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 04 Nov 1998 10:29:06 -0500 (EST) Reply-To: jobaldwi@vt.edu Organization: Virginia Tech From: John Baldwin To: freebsd-emulation@FreeBSD.ORG Subject: Wine and Linux Emulation... Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hope this is the right list.... I've been having some problems with the combination of Linux emulation and Wine. I'm running 2.2.7-STABLE with linux_lib-2.5 and wine-98.09.27 if that helps. The problem is this, after I run a wine, Linux emulation is corrupted somehow. I can still run Adobe's Acrobat Reader 3.0 after running Wine, but Netscape Communicator Pro (4.05-us), and StarOffice-3.1b don't run quite the same. StarOffice apps just die, but netscape starts up and shows up in top as taking 10% of my CPU, but I never get an X window. It seems to just be spinning its wheels. Has anyone else had similar problems or know of a solution? Please cc me on replies as I'm not subscribed to this list. Thanks. - --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc In case of atomic attack, prayer in schools will be OK. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNkByv4jYza302vYpAQHohgMAl0Ha4fVA2l2IYJyFEg0uosuvJbKYhkNk MrFVcTnDcezCEzIAuzu7mm8OlbCn5I1pwcCoUrYWqQGP7IB3hsxuxY6saRbCZ7aJ fxEkpevLVyL0vDw0hmvgceY/pAqKOavT =PXUh -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Nov 4 17:59:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23902 for freebsd-emulation-outgoing; Wed, 4 Nov 1998 17:59:27 -0800 (PST) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23895 for ; Wed, 4 Nov 1998 17:59:23 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA06154; Thu, 5 Nov 1998 12:29:04 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA06891; Thu, 5 Nov 1998 12:29:02 +1030 (CST) Message-ID: <19981105122902.C784@freebie.lemis.com> Date: Thu, 5 Nov 1998 12:29:02 +1030 From: Greg Lehey To: jobaldwi@vt.edu, freebsd-emulation@FreeBSD.ORG Subject: Re: Wine and Linux Emulation... References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from John Baldwin on Wed, Nov 04, 1998 at 10:29:06AM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wednesday, 4 November 1998 at 10:29:06 -0500, John Baldwin wrote: > I've been having some problems with the combination of Linux emulation and > Wine. I'm running 2.2.7-STABLE with linux_lib-2.5 and wine-98.09.27 if that > helps. The problem is this, after I run a wine, Linux emulation is corrupted > somehow. I can still run Adobe's Acrobat Reader 3.0 after running Wine, but > Netscape Communicator Pro (4.05-us), and StarOffice-3.1b don't run quite the > same. StarOffice apps just die, but netscape starts up and shows up in top as > taking 10% of my CPU, but I never get an X window. It seems to just be > spinning its wheels. Has anyone else had similar problems or know of a > solution? Please cc me on replies as I'm not subscribed to this list. Thanks. Hmm. Sounds unlikely. Since you're running X: are you starting both from the same window? It's possible that your environment is getting screwed up. Try starting 2 xterms, then start a WINE application from one of them, then a Linux application from the other, and see what happens. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message