Re: Dell SAS5 Performance Issue

2007-04-24 Thread J. Martin Petersen
Matthew Jacob wrote: Is there any news on the performance of this card? I personally have not been able to reproduce the problem. It seems to occur whether in Integrated Raid or not. It seems to be related to specific backplanes and drives. It's an important problem to solve I agree. We

Re: netstat fails with memory allocation error and error in kvm_read

2005-01-06 Thread J. Martin Petersen
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

RE: netstat fails with memory allocation error and error in kvm_read

2005-01-05 Thread J. Martin Petersen
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

RE: netstat fails with memory allocation error and error in kvm_read

2004-12-16 Thread J. Martin Petersen
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

RE: netstat fails with memory allocation error and error in kvm_read

2004-12-13 Thread J. Martin Petersen
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.

netstat fails with memory allocation error and error in kvm_read

2004-12-10 Thread J. Martin Petersen
Hi 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. quite often.