Derkjan de Haan wrote:
Today, after a cvsup (RELENG_6) and a rebuild of kernel and world, my
system no longer boots. It hangs on
Waiting 5 seconds for SCSI devices to settle
Booting from the previous kernel allows my system to boot again. Please
let
me know if I can do anything
.
regards,
Derkjan de Haan
dmesg:
Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 6.0-STABLE #5: Mon Jan 30 10:45:52 CET 2006
[EMAIL PROTECTED]:/usr
- Original Message -
From: Jon Noack [EMAIL PROTECTED]
To: Bartosz Fabianowski [EMAIL PROTECTED]
Cc: Chris [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, January 06, 2005 7:35 PM
Subject: Re: Instant reboots with CPUTYPE=pentium-m
Bartosz Fabianowski wrote:
I
I sometimes get this error message:
sshd[543767]: WARNING: DNS lookup failed for 171.31.1.21
Why is this error message?
For what sshd needs DNS? If the DNS is unavailable I can't
log into my computer. How can I resolve this problem, so I
can still login if the DNS is not available?
IIRC sshd does
With these simple tests, I come to the conclusion that
make -j$n buildworld is best with n = number of CPUs.
Does that make sense?
Yes, I believe this makes sense. The recommendations made in the handbook
(n = 4) date back from the time when IO was the bottleneck in the
compilation process
0xe6b0b864 in ?? ()
#54 0xc1d0b7d0 in ?? ()
#55 0xc061c4e3 in sched_switch ()
Previous frame inner to this frame (corrupt stack?)
- Original Message -
From: Derkjan de Haan [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, November 07, 2004 5:57 PM
Subject: 5.3R crash while building world
All,
I installed 5.3R on one of my systems, but as soon as I attempt to compile
something (make buildworld), after 10 seconds or so gcc bombs with an
internal compiler error,
and/or the machine crashes with a 'fatal trap 12' error. This seems to
happen at random places.
The dumps and some
There's your problem: your userland is out of sync with your kernel.
Just rebuild your system (i.e. kernel AND userland) to get rid of the
problem.
I don't think that's the case here. I'm using a recent 4-stable and I'm
seeing the same:
ipf: IP Filter: v3.4.31 (336)
Kernel: IP Filter: v3.4.35
- Original Message -
From: Dimitry Andric [EMAIL PROTECTED]
To: Derkjan de Haan [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, November 05, 2004 8:54 PM
Subject: Re: ipf
I can't seem to find any PR matching this problem, however...
I have just filed my first PR. Let's see how
