On Thu, Jul 8, 2010 at 12:34 AM, Richard Toohey <[email protected]> wrote: > On 8/07/2010, at 2:45 PM, Daniel Melameth wrote: >> On Fri, Jun 18, 2010 at 11:08 PM, Daniel Melameth <[email protected]> >> wrote: >>> On my firewall at home, on occasion, running systat queues leaves me with >> an >>> unresponsive system. pings are not returned and the keyboard at the >> console >>> is unresponsive. Sometimes the command works fine and sometimes it does >>> not--though it does seem the issue is more likely to occur when the system >>> has an uptime of more than a week or two. I'm uncertain how to >> troubleshoot >>> this further and I have been unable to reproduce the issue on other >>> 4.7-stable systems (though these other systems are not running the same >>> hardware and software). >> >> I upgraded the system several days ago to a snapshot from just before >> the hackathon, and the system appeared more stable, but I can now also >> instantly kill the box by running netstat -m after about five days of >> uptime. >> >> Ideas appreciated... >> > Hardware?
Perhaps, but the machine did not have this issue on 4.6 from just a couple of months ago. This box NEVER freezes--UNLESS I run either of these two commands (so far). I can recompile the kernel and userland multiple times with nary a hiccup. > Tried different NICs? RAM? Put the HD in another machine? No. With it being an older notebook and having three NICs, I'm a bit limited in my flexibility and recreating the same environment on another machine for an extended period of time. > No-one else seems to be seeing this (or reporting it) and you can't > reproduce on other machines, so worth eliminating hardware. > > Anything unusual or different about this machine or what you run on it? Since it's for home use, but probably elaborate home use, maybe. I have multiple NICs, VLANs, pppoe, pflog, nfdump, named--it's also my personal web server and is doing some minor nfs.
