On 17.03.2010 09:12, Daniel Hartmeier wrote:
On Tue, Mar 16, 2010 at 03:19:51PM -0400, kevin wrote:
I would like to assist in diagnosing this issue so if anyone wants me to
check anything or test, please let me know. I would really like to
understand this problem.
What are your setti
On 17.03.2010 11:47, Giulio Ferro wrote:
On 17.03.2010 09:12, Daniel Hartmeier wrote:
On Tue, Mar 16, 2010 at 03:19:51PM -0400, kevin wrote:
I would like to assist in diagnosing this issue so if anyone wants
me to
check anything or test, please let me know. I would really like to
understand
hine...
Greg
From: owner-freebsd...@freebsd.org [owner-freebsd...@freebsd.org] On Behalf Of
Giulio Ferro [au...@zirakzigil.org]
Sent: 17 March 2010 15:46
To: Daniel Hartmeier
Cc: freebsd-...@freebsd.org; freebsd-pf@freebsd.org
Subject: Re: PF + BRIDGE + PFSYN
On 17.03.2010 17:47, Max Laier wrote:
On Wednesday 17 March 2010 17:37:31 Giulio Ferro wrote:
On 17.03.2010 16:50, Greg Hennessy wrote:
A possible corner case with the virtual hosting platform ?
Try changing the NICS from EM to something else supported RL on vmware
IIRC
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 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 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