Date: Sat, 03 Oct 1998 12:01:48 -0700 From: Mike Smith <mike@smith.net.au> To: John Fieber <jfieber@indiana.edu> Cc: nash@mcs.net, emulation@FreeBSD.ORG Subject: Re: Sybase update Message-ID: <199810031901.MAA07047@word.smith.net.au> In-Reply-To: Your message of "Sat, 03 Oct 1998 10:15:58 CDT." <Pine.BSF.4.02A.9810031000150.369-100000@fallout.campusview.indiana.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > * 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. Ok. Definitely worth getting that fixed. > > > 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. If you could replicate it with a kernel containing DDB, it would be interesting to see if we could get a trace. My suspicion is that it was probably in the emulator LKM. > > 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? Whack a few quick printfs in kern/uipc_socket2.c:sowakeup(), as this is where the signal is generated. > > 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. More interesting. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810031901.MAA07047>