From: Joe Buehler <aspam@cox.net>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: kernel panic in fib_rules_lookup [2.6.27.7 vendor-patched]
Date: Tue, 26 Oct 2010 09:53:45 -0400 [thread overview]
Message-ID: <4CC6DD69.4020502@cox.net> (raw)
In-Reply-To: <1288100208.3169.112.camel@edumazet-laptop>
Eric Dumazet wrote:
> Well, it would be surprising this being wrong and crash only once in a
> while in fib_rules_lookup
> Did you tried my last patch ?
There was a patch to the kernel by David Daney back in January to
improve performance of Octeon memory barriers. The patch changes the
generic MIPS barrier code to introduce optimizations for Octeon. The
LINUX version I am using is from the Octeon SDK and appears to have an
early version of this patch. It's broken however -- the Jan patch has
proper SYNCW instructions in smp_wmb while the SDK version does not.
I have made your changes but will also fold in this change, then start
some load testing.
The real-time scheduler is broken in the LINUX I am using -- I get
kernel crashes -- and I would be most happy if the SYNCW fix fixed that
also.
Joe Buehler
next prev parent reply other threads:[~2010-10-26 13:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 17:14 kernel panic in fib_rules_lookup [2.6.27.7 vendor-patched] Joe Buehler
2010-10-12 17:40 ` Eric Dumazet
2010-10-13 11:18 ` Joe Buehler
2010-10-20 17:43 ` Joe Buehler
2010-10-20 22:05 ` Eric Dumazet
2010-10-22 20:30 ` Joe Buehler
2010-10-23 3:44 ` Eric Dumazet
2010-10-23 15:11 ` Eric Dumazet
2010-10-23 15:24 ` Eric Dumazet
2010-10-23 15:40 ` Joe Buehler
2010-10-23 16:07 ` Eric Dumazet
2010-10-23 15:33 ` Joe Buehler
2010-10-23 16:35 ` Eric Dumazet
2010-10-23 17:37 ` "Oleg A. Arkhangelsky"
2010-10-23 19:44 ` Eric Dumazet
2010-10-26 18:43 ` David Miller
2010-10-26 13:29 ` Joe Buehler
2010-10-26 13:36 ` Eric Dumazet
2010-10-26 13:53 ` Joe Buehler [this message]
2010-10-26 13:58 ` Eric Dumazet
2010-10-26 14:33 ` Eric Dumazet
2010-10-26 14:41 ` Joe Buehler
2010-10-27 21:01 ` Joe Buehler
2010-10-27 21:05 ` Eric Dumazet
2010-12-02 13:36 ` Joe Buehler
2010-12-02 14:04 ` Eric Dumazet
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=4CC6DD69.4020502@cox.net \
--to=aspam@cox.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).