Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Feb 2002 10:23:51 -0800 (PST)
From:      David Wolfskill <david@catwhisker.org>
To:        current@freebsd.org
Subject:   Hang on flushing buffers w/today's -CURRENT, SMP system
Message-ID:  <20020212021300.A1D869F158@okeeffe.bestweb.net>

next in thread | raw e-mail | index | archive | help
OK; I got today's -CURRENT built & running on each of my build
machine (freebeast) & my laptop.  (Got today's -STABLE built
earlier; I mention this as a reference point/comparison.  I
similarly note that I've been tracking each daily on each machine
for several months, and that today is the first time I've seen
this problem.)

Anyway, the laptop seems fairly normal:  I got -CURRENT built, booted
it up, ran a few things, used boot0cfg to switch to the slice with
today's -STABLE, and it came right down (gracefully) and back up again:

g1-7(4.5-S)[1] uname -a
FreeBSD g1-7.catwhisker.org 4.5-STABLE FreeBSD 4.5-STABLE #74: Fri Feb  8 05:58:01 PST 2002     root@d144.catwhisker.org:/common/S1/obj/usr/src/sys/LAPTOP_30W  i386
g1-7(4.5-S)[2] 


But on the build machine, I got it running -CURRENT, then did the
same procedure (boot0cfg & reboot), but on the (serial) console, I
see:


Feb  8 08:45:32 freebeast mountd[181]: bad exports list line /cdrom            -ro -alldirs
 apache cvsupd

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020212021300.A1D869F158>