Re: Fatal trap 9: general protection fault while in kernel mode

>Date: Fri, 28 Mar 2003 18:34:31 -0800 (PST)
>From: David Wolfskill <david_at_catwhisker.org>

>>Date: Fri, 28 Mar 2003 08:46:39 -0800 (PST)
>>From: David Wolfskill <david_at_catwhisker.org>

>[Yes, I'm responding to my own post....]

Again.

Well, I tried "panic", and that just got me

Fatal trap 3: breakpoint instruction fault while in kernel mode

so I said "reset"; after it came up, I re-did the same sequence --
logged in via SSH, poked around (OK; ran "healthd -d" and watched for at
least a couple of different values to change), then issued

	sudo boot0cfg -s 1 ad0 && sudo halt -p || sudo reboot

(same as before), and got:

Local package initialization: apache cvsupd 
.
Additional TCP options:.

Fri Mar 28 19:05:16 PST 2003

FreeBSD/i386 (freebeast.catwhisker.org) (console)

login: Mar 28 19:10:03 freebeast halt: halted by david
Mar 28 19:10:03 freebeast syslogd: exiting on signal 15
boot() called on cpu#1
Waiting (max 60 seconds) for system process `vnlru' to stop...stopped
Waiting (max 60 seconds) for system process `bufdaemon' to
stop...stopped
Waiting (max 60 seconds) for system process `syncer' to stop...stopped

syncing disks... 2 
done
Uptime: 9m7s

[followed by a "click" and a cessation of 4 fans blowing].

So about the only thing I see that this last experiment demonstrates is
that SMP vs. UP isn't known to be a significant issue for whatever was
causing the problem.

Tomorrow, I expect to be trying to build -CURRENT while running today's;
that could prove "interesting".

Peace,
david       (links to my resume at http://www.catwhisker.org/~david)
-- 
David H. Wolfskill				david_at_catwhisker.org
Based on what I have seen to date, the use of Microsoft products is not
consistent with reliability.  I recommend FreeBSD for reliable systems.