Date: Wed, 28 Feb 2001 23:07:02 -0600 From: "Josh Paetzel" <jpaetzel@hutchtel.net> To: "Alexey Dokuchaev" <danfe@inet.ssc.nsu.ru> Cc: <questions@FreeBSD.ORG> Subject: Re: FreeBSD 4-STABLE + XFree86 4.0.2 : caughting nasty signals! Message-ID: <00ca01c0a20d$862637a0$6100000a@vladsempire.net> References: <Pine.LNX.4.10.10102281023540.20870-100000@inet.ssc.nsu.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Alexey Dokuchaev" <danfe@inet.ssc.nsu.ru> To: "Josh Paetzel" <jpaetzel@hutchtel.net> Cc: <questions@FreeBSD.ORG> Sent: Tuesday, February 27, 2001 10:26 PM Subject: Re: FreeBSD 4-STABLE + XFree86 4.0.2 : caughting nasty signals! > On Wed, 28 Feb 2001, Josh Paetzel wrote: > > > sig 11s are usually a symptom of bad RAM. Try swapping it out. > > > > I thought of it, but... > > Well, I have Win2k installed on the same box, and it doesn't complain at > all. And, how to explain those 'sig 6' messages in dmesg?! > > Still, I guess I will give another memory a chance. > > file://danfe > > Remember that windows loads from high memory down, and FreeBSD loads from low memory up. Also, windows is far more likely to try and place nice with broken hardware than FreeBSD is. I don't have a clue about the sig 6s. I've never seen them before. Josh > 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?00ca01c0a20d$862637a0$6100000a>