From: Ernst Herzberg <earny@net4u.de>
To: linux-kernel@vger.kernel.org
Cc: Patrick McHardy <kaber@trash.net>,
"David S. Miller" <davem@davemloft.net>,
Kernel Netdev Mailing List <netdev@vger.kernel.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: 2.6.16-rc4 bridge/iptables Oops
Date: Tue, 21 Feb 2006 02:11:21 +0100 [thread overview]
Message-ID: <200602210211.22364.earny@net4u.de> (raw)
In-Reply-To: <43FA0C02.8000909@trash.net>
On Monday 20 February 2006 19:35, Patrick McHardy wrote:
> Ernst Herzberg wrote:
> > This machine oopses one to three (or more?) times a day. Occurs since
> > upgrading from -rc3 to -rc4 (and adding/reconfiguring raid).
> >
> > It is reproducable, i have only to wait 10min to a couple of hours:-)
> >
> > Opps copy/pasted from a serial console, long lines maybe truncated.
> > dmesg is from the _previous_ boot/oops....
> >
> > -------------------------------------------
> > Oops: 0000 [#1]
> > PREEMPT
> > Modules linked in: ebt_log ebt_ip ebtable_filter ebtables nfsd exportfs
> > lockd sunrpc w83627hf hwmon_vid i2c_isa xt_tcpudp xt_state ipt_MASQUERADE
> > iptable_e CPU: 0
> > EIP: 0060:[<b033fbf3>] Not tainted VLI
> > EFLAGS: 00010282 (2.6.16-rc4 #3)
> > EIP is at xfrm_lookup+0x1f/0x47d
> This patch should fix it. Please test it and report if it helps.
oernie:~ # uname -a ; uptime
Linux oernie 2.6.16-rc4 #1 PREEMPT Mon Feb 20 22:07:34 CET 2006 i686 Intel(R)
Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux
02:06:00 up 3:53, 4 users, load average: 0.08, 0.15, 0.10
No oops so far. Serial console still connected, will report if this or a
similar problem occurs again.
Thanks!
<earn/>
next prev parent reply other threads:[~2006-02-21 1:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200602201651.50217.list-lkml@net4u.de>
2006-02-20 18:35 ` 2.6.16-rc4 bridge/iptables Oops Patrick McHardy
2006-02-21 1:11 ` Ernst Herzberg [this message]
2006-02-21 3:08 ` Patrick McHardy
2006-02-21 4:07 ` David S. Miller
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=200602210211.22364.earny@net4u.de \
--to=earny@net4u.de \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).