Subject: Re: 1.5 dies at login:
To: None <port-i386@netbsd.org>
From: Mike Cheponis <mac@Wireless.Com>
List: port-i386
Date: 01/21/2001 19:17:19
I'm not using NFS anywhere on my network.  Thanks for the possibility, tho!

-Mike

p.s. I -am- seeing SIGBUS from time to time with the recent seti version
setiathome-3.03.i386-unknown-netbsd1.3 - I'm beginning to wonder if my h/w
is flaky?  (But when seti get SIGBUS at least only seti goes down.)


On Sun, 21 Jan 2001, Dave Burgess wrote:

>I use NFS to minimize the multiple instances of the files.  When the
>server that NFS is on isn't reachable, I see exactly the same kind of
>problems.  Are you running anything with NFS (especially with your new
>server as a client?).
>
>That's my only experience with this kind of problem....

>Mike Cheponis wrote:
>>
>>
>>>>Plus, not being able to log into the console directly seems very strange.
>>
>>>>Clearly, I've not been able to see what processes were running at that time.
>>
>>>No ddb on the machine ? On the console you could enter it via 'ctrl-alt-esc'
>>>and then type 'ps' to see what's running.
>>
>>Yikes, yes, next time I'll 'ctrl-alt-esc' to see what's running (blush!)
>>
>>>>I was running two tasks to test the machine's reliability, which
>>>>compiled, gzipped, deleted the .o file and then looped using C and f77.  And
>>>
>>>Didn't you see anything strange in top ?
>>
>>Unfortunately, all my windows into that machine were minimized when it
>>crashed, and I didn't see anything unusual when I maximized the (now dead)
>>windown running top.
>>
>>Next time it happens, I'll work to collect more clues.  Thanks -Mike