On Wed, 11 Sep 2002, Nate Lawson wrote:
> This is being worked on. See msg thread in cvs-all, starting with:
> <[EMAIL PROTECTED]>. You can back out the
> change (1.49) if you need to get running.
Sorry, 1.50 fixed the problem. I reverted back to kernel.old
anyways which was from a pr
This is being worked on. See msg thread in cvs-all, starting with:
<[EMAIL PROTECTED]>. You can back out the
change (1.49) if you need to get running.
-Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Revelent info:
* $FreeBSD: src/sys/kern/kern_acct.c,v 1.49 2002/09/11 04:10:41 arr Exp $
Console output...
Starting syslogd.
Sep 11 12:35:51 bigbang syslogd: kernel boot file is /boot/kernel/kernel
Starting named.
Starting ntpdate.
Turning on accounting.
recursed on non-recursive lock (sleep mut
On Mon, Oct 29, 2001 at 02:19:16PM +, Eric P Liedtke wrote:
> I own and MSI 694D Pro MoBo. It's a VIA 694x chip based dual P-III board.
> I recently installed a version of 5.0 from March, and it was running fine.
> I cvsup'd and rebuilt everything Friday night. When I tried to boot the new
>
"Eric P Liedtke" <[EMAIL PROTECTED]> writes:
> Warning: devsm() called on 154/0
> Warning: Driver mistake: destroy_dev on 154/0
> panic don't do that
Please refer to the first paragraph of section 19.2.1.4 in the
handbook.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mai
I own and MSI 694D Pro MoBo. It's a VIA 694x chip based dual P-III board.
I recently installed a version of 5.0 from March, and it was running fine.
I cvsup'd and rebuilt everything Friday night. When I tried to boot the new
kernel it was panicing on a call to destroy_dev() on device 154/0 which
