From: Michael Eck <michael.eck@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Bridging QoS Box Crashing
Date: Mon, 23 Aug 2004 15:48:08 -0400 [thread overview]
Message-ID: <d82fbdb704082312482f02c2c8@mail.gmail.com> (raw)
Greetings,
I have a Debian Woody box running Linux 2.4.24, iptables 1.2.11 with
pom-ng-20040621
patches ipt_helper_invert-fix proc_net_conntrack-permissions CLASSIFY
CONNMARK, ipp2p, and l7-filter.
I have the kernel oops, and have processed the output with ksymoops
using logged output
for my /proc/ksym, and /proc/modules.
I'm not sure what I should do with the ksymoops output now that I've
done, as far as I can tell, all the
right things to make it intelligable to a developer. I'm writing this
here because I hadn't had any trouble with the machine until I applied
all of those patches and started running with them. At this point I'm
getting about 1 week uptimes until the kernel panics. I am not
finding any corresponding event to the oops and cannot therefore
reproduce it.
Apologies in advance if this is the wrong forum for this message.
I'll post the ksymoops output if it's appropriate.
Thanks for the help,
Michael Eck
Chilitech Internet Solutions, Inc
reply other threads:[~2004-08-23 19:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d82fbdb704082312482f02c2c8@mail.gmail.com \
--to=michael.eck@gmail.com \
--cc=netfilter@lists.netfilter.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