Max Laier wrote:
On Wednesday 05 January 2005 18:26, J. Martin Petersen wrote:
We just had another hard hang, and this time I managed to break to the
debugger on the serial console. I got this stack trace
http://www.aub.dk/~jmp/fw/trace, which seems to indicate that pf is
messing up somehow.
I just got another netstat: kvm_read: Bad address.
vm.kvm_free was 675278848 two seconds earlier and a couple of
seconds later (and also currently).
We just had another hard hang, and this time I managed to break to the
debugger on the serial console. I got this stack trace
On Wednesday 05 January 2005 18:26, J. Martin Petersen wrote:
I just got another netstat: kvm_read: Bad address.
vm.kvm_free was 675278848 two seconds earlier and a couple of
seconds later (and also currently).
We just had another hard hang, and this time I managed to break to the
You appear to be running out of kernel memory. Since you're
capturing the output of vmstat -m, you should check that for any
bins that are growing at a high rate of speed.
Seems possible that its in pf :)
I've checked the numbers from just before the freeze (it's
within 15
You might also log 'sysctl vm.kvm_free' and 'sysctl vm.zone'.
I just got another netstat: kvm_read: Bad address. vm.kvm_free was
675278848 two seconds earlier and a couple of seconds later (and also
currently).
The output from vm.zone a couple of seconds after:
vm.zone:
ITEMSIZE
On Mon, 13 Dec 2004, J. Martin Petersen wrote:
We are trying to gather some debug information for a problem that is
difficult to diagnose, as the machine always ends up hard frozen
(does not do anything, can not break to debugger, does not respond
to keyboard, etc.), so we are dumping
We are trying to gather some debug information for a problem that is
difficult to diagnose, as the machine always ends up hard frozen
(does not do anything, can not break to debugger, does not respond
to keyboard, etc.), so we are dumping output from netstat, vmstat,
iostat etc.
On Fri, 10 Dec 2004, J. Martin Petersen wrote:
We are trying to gather some debug information for a problem that is difficult
to diagnose, as the machine always ends up hard frozen (does not do anything,
can not break to debugger, does not respond to keyboard, etc.), so we are
dumping output
