Oops - 2.4.17rc1 (with iptables 2.4.6)

[Whit Blauvelt]

Turns out it didn't leave a trace in the logs, but had a hard Oops less than
an hour into running this on a box that's been rock-solid stable for a
couple years, most recently running 2.2.19. 

Sorry I didn't hand copy the Oops screen - no time for that. Back to 2.2.19.
So this isn't so useful a report, except maybe to caution going beyond the
"rc" stage too soon on this one, just in case.

The iptables patch applied to it was just with the standard features,
nothing experimental.

Whit