Date: Thu, 6 Apr 2000 03:32:51 -0500 From: "Shwim" <shwim@purdue.edu> To: "Greg Lehey" <grog@lemis.com>, "Ben Smithurst" <ben@scientia.demon.co.uk> Cc: <questions@FreeBSD.ORG> Subject: Re: sudden signal 11s Message-ID: <000c01bf9fa2$b3449d80$0301a8c0@my.domain> References: <20000405162637.A93540@strontium.scientia.demon.co.uk> <20000406112932.A73669@freebie.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It would seem to me it is some sort of hardware issue. What's the temperature on your CPU? Are you overclocking your CPU? Signal 11's refer to invalid system calls if I recall correctly, and I used to have this problem and it was my CPU (settings on the motherboard were too aggressive). It is possible that something in your BIOS or RAM could also be causing the sig 11's. It took me three days to diagnose my problem. I know the loss/flipping of bits going from RAM -> cache -> HDD or vice versa would cause sig 11's or sig 12's. Also depending on how much RAM you have, it could take longer to detect if it is a problem with the RAM. Pretty much the way to figure this out is by playing around with hardware and try duplicating the problem. if you can single out the piece of hardware which is either faulty or misconfigured, you'll be one step closer to OS Godliness. Manny ----- Original Message ----- From: Greg Lehey <grog@lemis.com> To: Ben Smithurst <ben@scientia.demon.co.uk> Cc: <questions@FreeBSD.ORG> Sent: Wednesday, April 05, 2000 8:59 PM Subject: Re: sudden signal 11s > On Wednesday, 5 April 2000 at 16:26:37 +0100, Ben Smithurst wrote: > > any idea what could cause this: > > > > Apr 5 15:43:18 platinum /kernel: pid 14338 (sshd), uid 0: exited on signal 11 (core dumped) > > Apr 5 15:50:11 platinum /kernel: pid 15991 (sshd), uid 0: exited on signal 11 (core dumped) > > Apr 5 15:50:14 platinum /kernel: pid 16416 (sshd), uid 0: exited on signal 11 (core dumped) > > Apr 5 15:50:25 platinum /kernel: pid 16903 (sshd), uid 0: exited on signal 11 (core dumped) > > Apr 5 15:50:45 platinum /kernel: pid 17715 (inetd), uid 0: exited on signal 11 (core dumped) > > Apr 5 15:50:45 platinum /kernel: pid 34134 (lpd), uid 0: exited on signal 11 (core dumped) > > Apr 5 15:50:45 platinum inetd[33097]: /usr/libexec/fingerd[17715]: exit status 0x8b > > Apr 5 15:50:45 platinum /kernel: pid 17945 (inetd), uid 0: exited on signal 11 (core dumped) > > Apr 5 15:50:45 platinum /kernel: pid 24914 (rpc.statd), uid 0: exited on signal 11 (core dumped) > > Apr 5 15:50:45 platinum /kernel: pid 21978 (portmap), uid 1: exited on signal 11 > > Apr 5 15:50:48 platinum /kernel: pid 18814 (sshd), uid 0: exited on signal 11 (core dumped) > > Apr 5 15:50:55 platinum /kernel: pid 18890 (sshd), uid 0: exited on signal 11 (core dumped) > > Apr 5 15:52:23 platinum /kernel: pid 19493 (sshd), uid 0: exited on signal 11 (core dumped) > > Apr 5 15:52:30 platinum /kernel: pid 19530 (sshd), uid 0: exited on signal 11 (core dumped) > > Apr 5 15:52:35 platinum /kernel: pid 19790 (sshd), uid 0: exited on signal 11 (core dumped) > > Apr 5 15:53:32 platinum /kernel: pid 23406 (xterm), uid 0: exited on signal 11 > > Apr 5 15:53:33 platinum /kernel: pid 21315 (sh), uid 1001: exited on signal 11 (core dumped) > > Apr 5 15:53:33 platinum /kernel: pid 20603 (xinit), uid 1001: exited on signal 10 (core dumped) > > Apr 5 15:54:45 platinum init: fatal signal: Segmentation fault > > Apr 5 15:55:15 platinum init: /etc/rc.shutdown returned status 11 > > > > normally I'd say faulty memory or something, but is that still a > > feasible explanation given how suddenly they started appearing, and that > > they've disappeared completely (for now at least) after a reboot? If > > faulty hardware was causing this many problems I'm kind of surprised > > nothing went wrong in the kernel to cause a panic. I've also done quite > > a few buildworlds on that machine, which I gather is one way to find > > faulty memory. :-) [currently doing a -j8 build now, no problems > > yet.] > > Strange. What version of FreeBSD is this? > > Greg > -- > When replying to this message, please copy the original recipients. > For more information, see http://www.lemis.com/questions.html > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000c01bf9fa2$b3449d80$0301a8c0>