From: Julian H. Stacey
Steven Hartland wrote:
data. In addition to that I dont have to sit though 1 hour worth of
offline checks when it crashes for what ever reason which I do on
our
FreeBSD boxes.
[Apologies if I missed something, coming in late on thread, but ...]
FreeBSD-4 does
Hi, every once in a while (about once a week lately), one of my
servers has been known to stop responding. Upon connecting the serial
console, I find myself at a debugger prompt. This is the output I've
gotten this time.
I do think I have a debug kernel on that machine, what can I do to
I have a low end DELL Lattitude that has been successfully
running 5.4-RELEASE. I have tried loading 6.0-BETA3 three
times and it panics every time early while loading the Minimal
system. Does anyone else see this? (I haven't ruled out a disk problem)
Hand transcribed from the screen:
panic:
Jim C. Nasby wrote:
On Tue, Aug 30, 2005 at 10:57:53AM +1000, Robert Backhaus wrote:
[ ... ]
Simply because not every port works with -O2 optimisations. It caused
bad code in some circumstances.
Is there an automated way to identify those ports so they can be forced
not to use -O higer than
On Sat, 2005-08-27 at 03:51, Igor Sysoev wrote:
On Tue, 23 Aug 2005, Tomaz Borstnar wrote:
Would some kind soul MFC ffs_softdep.c 1.182, softdep.h 1.18 into
RELENG_4 as well? This bug is also present in FreeBSD 4.x. Found it ever
since 4.7.
I saw this annoying bug at least
On Wed, Aug 31, 2005 at 12:51:00PM +0200, Eirik ?verby wrote:
Hi, every once in a while (about once a week lately), one of my
servers has been known to stop responding. Upon connecting the serial
console, I find myself at a debugger prompt. This is the output I've
gotten this time.
I
On Wed, 31 Aug 2005, Stephan Uphoff wrote:
On Sat, 2005-08-27 at 03:51, Igor Sysoev wrote:
On Tue, 23 Aug 2005, Tomaz Borstnar wrote:
Would some kind soul MFC ffs_softdep.c 1.182, softdep.h 1.18 into
RELENG_4 as well? This bug is also present in FreeBSD 4.x. Found it ever
since 4.7.
On Aug 31, 2005, at 8:28 PM, Kris Kennaway wrote:
On Wed, Aug 31, 2005 at 12:51:00PM +0200, Eirik ?verby wrote:
Hi, every once in a while (about once a week lately), one of my
servers has been known to stop responding. Upon connecting the serial
console, I find myself at a debugger prompt.
From: Darren Pilgrim [EMAIL PROTECTED]
Date: Tue, 30 Aug 2005 23:07:16 -0700
Sender: [EMAIL PROTECTED]
From: Julian H. Stacey
Steven Hartland wrote:
data. In addition to that I dont have to sit though 1 hour worth of
offline checks when it crashes for what ever reason which I do on
On Wed, Aug 31, 2005 at 10:57:05AM -0400, Chuck Swiger wrote:
Jim C. Nasby wrote:
On Tue, Aug 30, 2005 at 10:57:53AM +1000, Robert Backhaus wrote:
[ ... ]
Simply because not every port works with -O2 optimisations. It caused
bad code in some circumstances.
Is there an automated way to
Jim C. Nasby wrote:
Even if the identification can't be done automatically, it still seems
like it would be good to start identifying ports that don't support -O
by hand, and having the ports force a correct -O setting. Most ports
support -O2 (if not -O3), and it would be nice if people could
On Tue, 30 Aug 2005 12:41:37 +0400 Boris Samorodov wrote:
On Sun, 28 Aug 2005 17:09:47 +0200 Rene Ladan wrote:
On Sun, Aug 28, 2005 at 04:30:19PM +0400, Boris Samorodov wrote:
As for 5.x notes about -O2 (libalias, gcc) were removed at revision
1.229.2.7 of
On Tue, 30 Aug 2005, Oliver Fromme wrote:
I get the following output under FreeBSD 6.0-BETA3 when WITNESS is
enabled. It doesn't seem to cause any harm, though. I cvsupped this
system to RELENG_6 a few days ago.
I have no idea what is causing this output, whether should worry about
it, or
13 matches
Mail list logo
