From: Danny <dannydaemonic@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: netdev@oss.sgi.com
Subject: Re: mm kernel oops with r8169 & named, PREEMPT
Date: Wed, 13 Oct 2004 13:28:55 -0700 [thread overview]
Message-ID: <9625752b04101313283f035423@mail.gmail.com> (raw)
In-Reply-To: <200410131129.05657.jdmason@us.ltcfwd.linux.ibm.com>
On Wed, 13 Oct 2004 11:29:05 -0500, Jon Mason wrote:
> Can you confirm that you are running r8169 driver with NAPI and TSO turned on,
> along with Preemptable Kernel? Also, I didn't see anything in the Oops
> specific to the r8169 driver, do you have another adapter available to run
> the same test on? Finally, what is your setup (arch, # of cpus, etc)?
I am using the r8169 driver with NAPI and preemptable kernel. I don't
remember or see any option for offloading but it sounds like something
I'd turn on. Let me know what I should look for in my config, or
check here:
http://members.cox.net/valenzdu/.config
I no longer have a 2nd nic adapter, but I did first notice the problem
when I installed this one. However, if I don't load that module I'm
not able to duplicate the problem by running named on the other
interface. Running named triggers it 100% of the time on the r8169
based nic.
The arch is x86 (athlon) with just 1 cpu. Since I'm not sure what's
wrong here I'm not sure what's relevant. Here is more info about my
setup:
http://members.cox.net/valenzdu/proc-cpuinfo
http://members.cox.net/valenzdu/proc-iomem
http://members.cox.net/valenzdu/proc-ioports
http://members.cox.net/valenzdu/proc-modules
http://members.cox.net/valenzdu/proc-version
http://members.cox.net/valenzdu/stdout-lspci
http://members.cox.net/valenzdu/stdout-ver_linux
prev parent reply other threads:[~2004-10-13 20:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9625752b041012230068619e68@mail.gmail.com>
[not found] ` <20041013072814.GA24066@electric-eye.fr.zoreil.com>
2004-10-13 16:05 ` mm kernel oops with r8169 & named, PREEMPT Danny
[not found] ` <9625752b041013091772e26739@mail.gmail.com>
2004-10-13 16:18 ` Danny
2004-10-13 16:29 ` Jon Mason
2004-10-13 18:18 ` Francois Romieu
2004-10-13 20:44 ` Danny
[not found] ` <9625752b04101313417be4cf90@mail.gmail.com>
[not found] ` <20041013205433.GC30761@electric-eye.fr.zoreil.com>
2004-10-13 21:59 ` Danny
2004-10-14 22:04 ` Danny
2004-10-15 16:18 ` Francois Romieu
2004-10-15 21:07 ` Danny
2004-10-16 10:01 ` profile path bug again (was Re: mm kernel oops with r8169 & named, PREEMPT) Francois Romieu
2004-10-16 15:52 ` Danny
2004-10-13 20:28 ` Danny [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=9625752b04101313283f035423@mail.gmail.com \
--to=dannydaemonic@gmail.com \
--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).