Matthew Thyer m...@camtech.com.au writes:
On Sun, 14 Feb 1999, Erik Funkenbusch wrote:
During a make world (usually about 10-20 minutes in on my P100) everything
just comes to a grinding halt. No disk activity, but the screen saver will
kick in (despite the shell being in the middle of
Recently I've been trying to upgrade an early januarrry -current to
current -current. I've rebuilt the kernel several times over the last few
days (with new cvsup's) so i've eliminated any freak check-in mismatches.
During a make world (usually about 10-20 minutes in on my P100) everything
just
I'm getting something similar. I thought it was my mainboard, as the one
I currently have has some other problems (doesn't take the Nvidia TNT
card)
During heavy disk i/o the system freezes up for about 10 seconds or so,
and then things continue. I'm getting these messages:
wd0: interrupt
Shouldn't a make world take about 10 hours on a P100 ?? -depends on
the speed of your disks.
You should probably remove all the junk in /usr/obj from previous
make worlds, then run make cleandir in /usr/src and then try
a make world again.
The messages about no such user 'tty' indicate your /etc
On Sun, 14 Feb 1999, Erik Funkenbusch wrote:
Recently I've been trying to upgrade an early januarrry -current to
current -current. I've rebuilt the kernel several times over the last few
days (with new cvsup's) so i've eliminated any freak check-in mismatches.
During a make world (usually
:Recently I've been trying to upgrade an early januarrry -current to
:current -current. I've rebuilt the kernel several times over the last few
:days (with new cvsup's) so i've eliminated any freak check-in mismatches.
:
:During a make world (usually about 10-20 minutes in on my P100) everything
On Sun, 14 Feb 1999, Brian Feldman wrote:
I'm also getting messages from de0 and lo0 that say:
de0 XXX: driver didn't set ifq_maxlen
That's mostly harmless. It's a warning to driver maintainers that was just
put in recently; the driver hasn't ever set ifq_maxlen, no doubt.
I see this
On Mon, 15 Feb 1999, Kris Kennaway wrote:
I see this on lo0 every time I boot - is this a problem in 3.1 as well, or
just -current? It's probably not good to leave these messages in 3.1 as it
ships, if the former.
FWIW I'm seeing this at bootup now:
ep0 XXX: driver didn't set ifq_maxlen
lo0
