Welp, wish me luck as well. I haven't had a -current system that booted in about a
week. I noticed that there've been changes to the acpi stuff in my cvsup this morning,
so I'm hoping maybe the fix is in there.
-----Original Message-----
From: David Wolfskill [mailto:[EMAIL PROTECTED]]
Sent: Wed 7/31/2002 4:11 PM
To: [EMAIL PROTECTED]
Cc:
Subject: Re: Today's -CURRENT -- SMP OK; UP panics
>Date: Wed, 31 Jul 2002 11:58:04 -0700 (PDT)
>From: David Wolfskill <[EMAIL PROTECTED]>
>[Re: panic during probes at boot time for today's -CURRENT....]
Well, absent any better ideas, I rebooted the laptop, but into
single-user mode. It came up just fine, so I did the "fsck -p"; no
problem.
So I rebooted again (multi-user mode); it's up & running as I type --
I'm logged in, running X, and:
g1-9(5.0-C)[1] uname -a
FreeBSD g1-9.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #7: Wed Jul 31
10:45:23 PDT 2002 [EMAIL PROTECTED]:/common/S3/obj/usr/src/sys/LAPTOP_30W
i386
g1-9(5.0-C)[2]
Weird.
Cheers,
david (links to my resume at http://www.catwhisker.org/~david)
--
David H. Wolfskill [EMAIL PROTECTED]
To paraphrase David Hilbert, there can be no conflicts between Microsoft
and the discipline of systems administration, since they have nothing in
common.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
N…'²æìr¸›zǧvf¢–Ú&j:+v‰¨·ž è® "¶§²æìr¸›yúÞy» rêëz{bžØ^n‡r¡ûazg¬±¨
