I saw that yesterday, and fixed it by:
config -r CRITTER
In message <[EMAIL PROTECTED]>, Christopher Masto writes:
>Yesterday and today, after a cvsup and kernel build, I get a panic
>very early in the boot on my laptop. What's left on the screen is a
>general protection fault in kernel mode, and an attempt to trace just
>causes another panic. Tomorrow I will put a serial cable on it and
>get some details, but I'm guessing that this comes from the recent
>BUF_STRATEGY stuff, possibly breaking in the wd driver (which might
>be why there hasn't been a report yet if most everyone is using ata).
>I'm stuck with wd for the moment (pccard compact flash stuff), so if
>that's it and it hasn't been repaired by then, I'll dig into it.
>Christopher Masto Senior Network Monkey NetMonger Communications
>[EMAIL PROTECTED] [EMAIL PROTECTED] http://www.netmonger.net
>Free yourself, free your machine, free the daemon -- http://www.freebsd.org/
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-current" in the body of the message
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message