Package: linux-image-2.6.18-4-powerpc
Version: 2.6.18.dfsg.1-12etch2
The noisy panic may be a diff problem to the sudden death which just
stops logging and requires a reset. I had stopped nmbd and smokeping
and it was still locking up.
I did have one where dis{pl,m}ay had crashed, but keyboard worked so I
could shutdown for warm reboot. With the hard locks there is no
response to ping or keyboard. There is also no disc activity.
I have noted port scans (or peer to peer replies) in last entries
before it stopped so I changed rules to log everything, but I also
stopped NAT and it kept working!
The requests for 22/tcp are obviously port scans. This variable makes
it a little hard to reproduce often. Crash frequency is low, but would
be annoying in a production environment.
Changed rules to stop logging everything, but leave NAT off and it is
still working. Still getting scanned.
Running behind masquerade with some redirects and MoL also sets up its
own NAT. I now pull NAT modules out after stopping MoL.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
