Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 2 Jul 2000 12:05:37 +0930
From:      Greg Lehey <grog@lemis.com>
To:        Greg Work <Greg@fatcanary.com.au>
Cc:        Larry Rosenman <ler@lerctr.org>, freebsd-stable@FreeBSD.ORG
Subject:   Re: AMD K6-2 / 550
Message-ID:  <20000702120537.T18213@wantadilla.lemis.com>
In-Reply-To: <001201bfe3cc$6e1b9c40$0200a8c0@gwork.org.au>
References:  <200006280311.e5S3BWb28882@lerami.lerctr.org> <003d01bfe3af$3c72c640$0200a8c0@gwork.org.au> <20000702114422.Q18213@wantadilla.lemis.com> <001201bfe3cc$6e1b9c40$0200a8c0@gwork.org.au>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday,  2 July 2000 at 11:52:54 +0930, Greg Work wrote:
>>> Just a quick question - *exactly* what was the symptoms of your problem?
>>>
>>> ive just turned a K6-2 300 into a BSD box, and make world fails with
>>> SIG's 10, 11 and 12 randomly.  I know its not the memory - i have
>>> been thrashing that memory for 12 mths now - never skipped a beat.
>>
>> You mean it never discovered a problem?  What software were you
>> running?
>
> Was running win98 - and used to dual boot 3.0 --> 3.2-STABLE with 98

> It got retired to a straight win98 box (ducks objects thrown at him) when i
> got a second machine

OK, this seems to contradict your previous statements ("just turned
into a BSD box").

>>> The CPU / Motherboard / Memory used to run BSD in the 2.2.8 - 3.2
>>> days no problems.  Now - no luck :( - i get random panics, SIG 10's
>>> to 12's and core dumps - unfortunately - i have no idea how to debug
>>> them :(
>>
>> If they're hardware related, there's probably not much to see except
>> that things will be different each time.
>>
>> I suspect that a large number of crashes on Microsoft machines are in
>> fact due to flaky hardware.  Despite my low opinion of Microsoft, I
>> have not had an unexpected crash of a Microsoft system in years (it
>> helps, of course, if you don't use them much :-).
>

> the funny thing was that it never skipped a beat under M$ after a
> bios flash (it didnt like my vid card - but thats another issue :) )

After a flash, or until after a flash?  Check the BIOS settings; maybe
they're overstressing the memory.

Greg
--
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-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000702120537.T18213>