From: Whit Blauvelt <whit@transpect.com>
To: linux-kernel@vger.kernel.org
Subject: Oops - 2.4.17rc1 (with iptables 2.4.6)
Date: Sat, 15 Dec 2001 00:56:41 -0500 [thread overview]
Message-ID: <20011215005641.A810@china.patternbook.com> (raw)
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
next reply other threads:[~2001-12-15 5:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-15 5:56 Whit Blauvelt [this message]
2001-12-15 9:02 ` Oops - 2.4.17rc1 (with iptables 2.4.6) Edward Killips
[not found] ` <1008396931.17483.0.camel@psuedomode>
2001-12-17 18:29 ` Oops - 2.4.17rc1 Whit Blauvelt
[not found] ` <3C1AEFB7.119D8902@pobox.com>
2001-12-17 18:34 ` Whit Blauvelt
-- strict thread matches above, loose matches on Subject: below --
2001-12-15 9:19 Oops - 2.4.17rc1 (with iptables 2.4.6) Edward Killips
2001-12-15 14:53 Thomas Hood
2001-12-15 18:20 ` James A Sutherland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011215005641.A810@china.patternbook.com \
--to=whit@transpect.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox