On 05/25/07 11:07, Volker wrote:
...
I'm using the following additional kernel options:
makeoptions DEBUG=-g
options KDB
options KDB_UNATTENDED
options KDB_TRACE
options DDB
options WITNESS
options WITNESS_SKIPSPIN
options INVARIANTS
Kris, Roger all,
On 05/23/07 23:58, Kris Kennaway wrote:
On Wed, May 23, 2007 at 11:31:32PM +0100, Volker wrote:
talking to myself... ;)
On 2007-05-23 10:27, Volker wrote:
Unfortunately three hours later, the machine died completely. It has
been a hardware failure which came quietly.
Sorry
Using a debug kernel, the machine came up quickly with this LOR
after the reboot:
lock order reversal:
1st 0xc077078c tcp (tcp) @ /usr/src/sys/netinet/tcp_input.c:625
2nd 0xc4f18180 pf task mtx (pf task mtx) @
/usr/src/sys/modules/pf/../../contrib/pf/net/pf.c:6386
KDB: stack backtrace:
On Friday 25 May 2007 04:07, Volker wrote:
Kris, Roger all,
well, we replaced the broken machine (totally different hardware),
took one of the mirrored hard disks into this replacement machine
and took this replacement into production.
Unfortunately it took less than 16 hours for this
On 05/25/07 15:01, Roger Miranda - Digital Relay Inc. wrote:
...
Volker Kris,
Sorry for kind of hi-jacking your thread. Just hopefully we all can work
together to fix this issue (if there is one).
For me, that's ok as it may (or may not) be a similar problem.
Out machine did goto in to a
On 05/25/07 13:45, Volker wrote:
Using a debug kernel, the machine came up quickly with this LOR after
the reboot:
lock order reversal:
1st 0xc077078c tcp (tcp) @ /usr/src/sys/netinet/tcp_input.c:625
2nd 0xc4f18180 pf task mtx (pf task mtx) @
On Fri, May 25, 2007 at 05:17:02PM +0200, Volker wrote:
My assumption: The LORs are somewhat pf related but are not related
to the lockdown of the system. Am I correct?
No, they could be the cause. Make sure you have read the BUGS section
of pf.conf, and if this is not relevant to your
On Fri, 25 May 2007, Volker wrote:
Using a debug kernel, the machine came up quickly with this LOR after the
reboot:
lock order reversal:
1st 0xc077078c tcp (tcp) @ /usr/src/sys/netinet/tcp_input.c:625
2nd 0xc4f18180 pf task mtx (pf task mtx) @
Roger Miranda wrote:
Volker wrote:
[...]
I've attached the latest dmesg, can you see any similarities (as it
still might be a hardware issue)?
[...]
Our current version is: FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0
Looks like you are also using the EM network adapter driver.
On 05/23/07 09:17, Oliver Fromme wrote:
Roger Miranda wrote:
Volker wrote:
[...]
I've attached the latest dmesg, can you see any similarities (as it
still might be a hardware issue)?
[...]
Our current version is: FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0
Looks like you are
On Tuesday 22 May 2007 14:03, Kris Kennaway wrote:
What happens if you enable INVARIANTS and/or WITNESS?
I have enabled WITNESS, I have no experienced a freeze yet. But i did notice
on boot an WITNESS message for if_bridge.
See attached. Could this be causing the freeze?
softdep_waitidle:
talking to myself... ;)
On 2007-05-23 10:27, Volker wrote:
Currently I'm watching this machine over the distance and waiting for the
freeze...
...and the machine freeze came this afternoon. I've had a good dump
of the network traffic and haven't seen any strange network traffic.
On Wed, May 23, 2007 at 11:31:32PM +0100, Volker wrote:
talking to myself... ;)
On 2007-05-23 10:27, Volker wrote:
Currently I'm watching this machine over the distance and waiting for the
freeze...
...and the machine freeze came this afternoon. I've had a good dump
of the network
On Wed, May 23, 2007 at 02:57:59PM -0500, Roger Miranda wrote:
On Tuesday 22 May 2007 14:03, Kris Kennaway wrote:
What happens if you enable INVARIANTS and/or WITNESS?
I have enabled WITNESS, I have no experienced a freeze yet. But i did
notice
on boot an WITNESS message for
Hi!
Starting yesterday I'm experiencing machine freezes on a 6.2-R
system (remote to me). The strange thing: It occurs twice a day, in
the morning hours (both freezes are within 1-2 hours) and for the
rest of the day everything runs fine.
The machine does not respond anymore (no net, no
Volker wrote:
My first thought is a hardware problem but why does it occur that less
and only in the morning? My next thought is a DoS attack
(CVE-2007-0244?) but can that lead into a machine freeze?
When in the morning? If it's around 3-4 am, that's when the (often
hardware intensive)
On 05/22/07 17:18, Ivan Voras wrote:
Volker wrote:
My first thought is a hardware problem but why does it occur that less
and only in the morning? My next thought is a DoS attack
(CVE-2007-0244?) but can that lead into a machine freeze?
When in the morning? If it's around 3-4 am, that's when
On Tuesday 22 May 2007 08:15, Volker wrote:
Hi!
Starting yesterday I'm experiencing machine freezes on a 6.2-R
system (remote to me). The strange thing: It occurs twice a day, in
the morning hours (both freezes are within 1-2 hours) and for the
rest of the day everything runs fine.
The
On 05/22/07 18:24, Roger Miranda wrote:
On Tuesday 22 May 2007 08:15, Volker wrote:
Hi!
Starting yesterday I'm experiencing machine freezes on a 6.2-R
system (remote to me). The strange thing: It occurs twice a day, in
the morning hours (both freezes are within 1-2 hours) and for the
rest of
Am Dienstag, den 22.05.2007, 17:53 +0200 schrieb Volker:
On 05/22/07 17:18, Ivan Voras wrote:
Volker wrote:
My first thought is a hardware problem but why does it occur that less
and only in the morning? My next thought is a DoS attack
(CVE-2007-0244?) but can that lead into a machine
On Tuesday 22 May 2007 11:41, Volker wrote:
There's nothing of interest in the logs (I suspect it's too late to
have any daemon write something to syslogd as the system is then
dead). As I also think, this is somehow related to network traffic,
I'll try to monitor it's traffic starting
On Tue, May 22, 2007 at 12:24:36PM -0500, Roger Miranda wrote:
On Tuesday 22 May 2007 11:41, Volker wrote:
There's nothing of interest in the logs (I suspect it's too late to
have any daemon write something to syslogd as the system is then
dead). As I also think, this is somehow related to
What happens if you enable INVARIANTS and/or WITNESS?
Thanks Kris.
I am going to compile that into the kernel right now. Well keep the list
posted on any issues.
___
freebsd-stable@freebsd.org mailing list
23 matches
Mail list logo
