From: Ondrej Zary <linux@rainbow-software.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Oops after 30 days of uptime
Date: Fri, 1 Sep 2006 20:00:58 +0200 [thread overview]
Message-ID: <200609012000.58873.linux@rainbow-software.org> (raw)
In-Reply-To: <44F86732.5060501@trash.net>
On Friday 01 September 2006 19:00, Patrick McHardy wrote:
> Ondrej Zary wrote:
> > Hello,
> > my home router crashed after about a month. It does this sometimes but
> > this time I was able to capture the oops. Here is the result of running
> > ksymoops on it (took a photo of the screen and then manually converted to
> > plain-text). Does it look like a bug or something other?
> >
> >
> > Code; c01eeb9e <init_or_cleanup+15e/160>
> > 00000000 <_EIP>:
> > Code; c01eeb9e <init_or_cleanup+15e/160> <=====
> > 0: 8b 5e 18 mov 0x18(%esi),%ebx <=====
> > Code; c01eeba1 <ip_conntrack_protocol_register+1/70>
> > 3: 11 d8 adc %ebx,%eax
>
> This looks like a bug in some out of tree protocol module (2.4 only
> contains the built-in protocols). Did you apply any netfilter patches?
No patches, it's clean 2.4.31.
Hopefully I typed all the numbers correctly...
These network-related things are enabled:
CONFIG_PACKET=y
CONFIG_NETFILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_INET_ECN=y
CONFIG_SYN_COOKIES=y
CONFIG_IP_NF_CONNTRACK=y
CONFIG_IP_NF_FTP=y
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_MATCH_LIMIT=y
CONFIG_IP_NF_MATCH_MARK=y
CONFIG_IP_NF_MATCH_HELPER=y
CONFIG_IP_NF_MATCH_STATE=y
CONFIG_IP_NF_MATCH_CONNTRACK=y
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_NAT=y
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_REDIRECT=y
CONFIG_IP_NF_NAT_FTP=y
CONFIG_IP_NF_MANGLE=y
CONFIG_IP_NF_TARGET_TOS=y
CONFIG_IP_NF_TARGET_MARK=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CBQ=y
CONFIG_NET_SCH_HTB=y
CONFIG_NET_SCH_PRIO=y
CONFIG_NET_SCH_RED=y
CONFIG_NET_SCH_SFQ=y
CONFIG_NET_SCH_TBF=y
CONFIG_NET_SCH_GRED=y
CONFIG_NET_SCH_INGRESS=y
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_ROUTE4=y
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=y
CONFIG_NET_CLS_U32=y
CONFIG_NET_CLS_POLICE=y
--
Ondrej Zary
next prev parent reply other threads:[~2006-09-01 18:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 16:52 Oops after 30 days of uptime Ondrej Zary
2006-09-01 17:00 ` Patrick McHardy
2006-09-01 18:00 ` Ondrej Zary [this message]
2006-09-03 20:03 ` Ondrej Zary
2006-09-09 5:10 ` Willy Tarreau
2006-09-09 5:20 ` Willy Tarreau
2006-09-09 10:15 ` Ondrej Zary
2006-09-09 10:19 ` Willy Tarreau
2006-09-09 10:43 ` Ondrej Zary
2006-09-09 11:38 ` Ondrej Zary
2006-09-10 8:26 ` Willy Tarreau
2006-09-10 10:43 ` Ondrej Zary
2006-09-10 13:16 ` Willy Tarreau
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=200609012000.58873.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=kaber@trash.net \
--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