On 17.03.2010 18:00, Max Laier wrote:
Can you enable WITNESS and compile in DDB. Make sure to report any LORs
and once the system freezes try to enter the debugger and get ps and
locks information.
show allchains
show alllocks
ps
After that you can try to "call doadump" so you get the informat
On Thursday 18 March 2010 15:04:06 Giulio Ferro wrote:
> On 17.03.2010 18:00, Max Laier wrote:
> > Can you enable WITNESS and compile in DDB. Make sure to report any LORs
> >
> >>> and once the system freezes try to enter the debugger and get ps and
> >>> locks information.
> >>>
> >>> show allchai
I have small network like this: [Internet] --- rl0(FreeBSD -
router)rl1 --- [Lan]
I wanted to make whole outgoing packets from the Lan look the same. It
means that every SYN packet has the same TCP/IP stack. So I thought
about PF's synproxy state. I know synproxy was made for other puprose
but I t
On 18.03.2010 15:26, Max Laier wrote:
Ok, it's happened again...
and once the system freezes try to enter the debugger and get ps and
locks information.
show allchains
No result
show alllocks
Process 4483 (sshd) thread 0xff0002ded3a0 (100159)
exclusive sx so_r
On Thursday 18 March 2010 17:39:29 Giulio Ferro wrote:
> On 18.03.2010 15:26, Max Laier wrote:
>
> Ok, it's happened again...
> and once the system freezes try to enter the debugger and get ps and
>
> > locks information.
> >
> > show allchains
>
> No result
Okay ... so it looks lik
On 18.03.2010 20:35, Max Laier wrote:
Okay ... so it looks like this is a live lock (not a deadlock) and it's
probably caused by relooping packets. Now we "only" have to find the culprit
for the loop ...
can you share your setup details, again? The simpler the better.
Ok
> uname -a
Fr
Duh, never thought of writing to this list first :/
Forwarded conversation
Subject: Crash in pf(4) with a fairly recent RELENG_8
From: *Vlad Galu*
Date: Thu, Mar 18, 2010 at 12:38 AM
To: freebsd-sta...@freebsd.org
Luckily I could find this coredump:
-- cut here --
#0
