From owner-freebsd-emulation Sat Oct 3 08:17:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17096 for freebsd-emulation-outgoing; Sat, 3 Oct 1998 08:17:40 -0700 (PDT) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17090; Sat, 3 Oct 1998 08:17:38 -0700 (PDT) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with SMTP id KAA03727; Sat, 3 Oct 1998 10:15:58 -0500 (EST) Date: Sat, 3 Oct 1998 10:15:58 -0500 (EST) From: John Fieber To: Mike Smith cc: msmith@FreeBSD.ORG, nash@mcs.net, emulation@FreeBSD.ORG Subject: Re: Sybase update In-Reply-To: <199810030648.XAA01122@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 2 Oct 1998, Mike Smith wrote: > Presumably it enables SIGIO delivery? It's masked by default... >From the trace... sigaction(SIGIO, {0x82b3f10, [], 0}, NULL) = 0 > > * The SIGIO and SIGURG values in linux.h were reversed. I > > think they must have come from an incorrect man page (I found > > one on the net that had them wrong). > > When you say "reversed", can you be more specific? The header I have > here gives SIGIO and SIGURG the same value (23). I "misspoke"...not reversed. A real linux kernel has SIGURG as 23 and SIGIO as 29 (and SIGPOLL as a synonym for SIGIO). When sybase installs the SIGIO handler, it uses signal 29. > > Note that fixing the second without fixing the first resulted in a > > panic suggesting that somewhere in the kernel, there must be some > > action on the signals. > > That's not too good. Did you get an idea as to where the panic was? First time I was on an X display and didn't see any messages. Second time I did it where I could see the messages an the only one was "panic syncing disks" or whatever the text is...no details about where. > It sounds like you're extremely close. If you build the Linux LKM with > DEBUG defined, you should get a pile of "linux_sendsig" messages. You > can see the code that's meant to send the signal into the Linux process > in linux_sysvec.c:linux_sendsig(). I already turned on that particulary debugging printf there and no SIGIOs show up. Is there something I can use to examine the flags on the socket to see if the async flag got properly set? > Interesting. Does the Linux uname(2) call return a fully-qualified > hostname? I believe so which is which I'm doubting this is the real problem. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message