>Date: Wed, 21 Nov 2001 08:05:18 -0800 (PST)
>From: David Wolfskill <[EMAIL PROTECTED]>

>Anyway, I now have my first panic on boot from -CURRENT since setting
>up the serial console; modulo cut/paste damage, the following ought to
>be fairly accurate.  :-}

Eh, well... my laptop came up OK after building today's -CURRENT from
what ought to be the same sources.  And trying to go ahead & force a
re-boot on the build system from my (remote) serial console didn't work
too well:

db> panic
panic: from debugger
cpuid = 1; lapic.id = 01000000
Stopped at      0xc03618d8:     addb    %al,0(%eax)
db> panic
panic: from debugger
cpuid = 1; lapic.id = 01000000
boot() called on cpu#1
Uptime: 15s
Automatic reboot in 15 seconds - press a key on the console to abort
--> Press a key on the console to reboot <--
cpu_reset called on cpu#1
cpu_reset: Stopping other CPUs
timeout stopping cpus
cpu_reset: Restarting BSP
cpu_reset: Failed to restart BSP

and it doesn't appear to be responsive at this point.  But since the
laptop is up & runnning:

m133[1] uname -a
FreeBSD m133.whistle.com 5.0-CURRENT FreeBSD 5.0-CURRENT #178: Wed Nov 21 09:16:17 PST 
2001     root@localhost:/common/S3/obj/usr/src/sys/LAPTOP_30W  i386

it seems that the problem is much less likely of general interest.

Sorry for the noise,
David H. Wolfskill                              [EMAIL PROTECTED]
As a computing professional, I believe it would be unethical for me to
advise, recommend, or support the use (save possibly for personal
amusement) of any product that is or depends on any Microsoft product.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to