From: Duncan Sands <baldrick@free.fr>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com, laforge@gnumonks.org
Subject: Re: Oops at __neigh_for_each_release (2.6.9-rc3)
Date: Sat, 2 Oct 2004 09:58:00 +0200 [thread overview]
Message-ID: <200410020958.01197.baldrick@free.fr> (raw)
In-Reply-To: <20041001135636.0c071602.davem@davemloft.net>
> > EIP is at __neigh_for_each_release+0x32/0xb0
>
> Give this patch a try. And please report networking bugs
> to netdev@oss.sgi.com in the future, thanks.
OK, will do. I tested the patch Linus committed - it indeed fixes
the oops.
Thanks a lot!
Duncan.
prev parent reply other threads:[~2004-10-02 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200410012217.35264.baldrick@free.fr>
2004-10-01 20:56 ` Oops at __neigh_for_each_release (2.6.9-rc3) David S. Miller
2004-10-02 7:58 ` Duncan Sands [this message]
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=200410020958.01197.baldrick@free.fr \
--to=baldrick@free.fr \
--cc=davem@davemloft.net \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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).