From: "Chris Friesen" <cfriesen@nortel.com>
To: David Miller <davem@davemloft.net>
Cc: jesse.brandeburg@intel.com, linuxppc-dev@ozlabs.org,
netdev@vger.kernel.org, romieu@fr.zoreil.com
Subject: Re: [BUG] oops in net_rx_action on 64-bit powerpc
Date: Fri, 24 Oct 2008 17:39:00 -0600 [thread overview]
Message-ID: <49025C94.60406@nortel.com> (raw)
In-Reply-To: <20081023.171614.72881694.davem@davemloft.net>
David Miller wrote:
> From: "Brandeburg, Jesse" <jesse.brandeburg@intel.com> Date: Thu, 23 Oct
> 2008 14:50:06 -0700
>
>> Chris Friesen wrote:
>>> I tried booting a post 2.6.27 -git on a Motorola ATCA6101 (very similar
>>> to a Maple board). The first time I booted I got the first log below
>>> via the serial console. I rebooted and got as far as a login prompt.
>>> I was able to log in via the serial console, but then got an almost
>>> identical oops again, as shown in the second log below.
>>>
>>> I configed out the gigE drivers for the backplane so the only remaining
>>> network link was the e100 link used for booting, but the problem
>>> remained.
>>>
>>> Anyone have any idea what might be causing this?
>>>
>>> Thanks,
>>>
>>> Chris
>>>
>>>
>>> Starting xinetd: [ OK ] Starting cron: [ OK ] Unable to handle
>>> kernel paging request for data at address 0x00100108
>> that 00100108 pattern looks familiar, I'm not much help here, but I think
>> that had something to do with the list management of the poll_list in a
>> netdev struct.
>>
>> so now you just have to figure out why someone's netdev struct is
>> becoming NULL. :-)
>
> Usually this is an indication of returning the wrong value from the
> driver's ->poll() routine.
Looks like I was wrong before...the remaining ethernet link is an AMD-8111,
not an e100. Sorry about that.
I backed out 6ba33ac "amd8111e: delete non NAPI code from the driver". With
NAPI disabled, the blade appears stable. With NAPI enabled, the original
problem recurred.
So...it would appear that the NAPI code is somehow buggy, and 6ba33ac should
probably be reverted until the problem is found and fixed.
Chris
next prev parent reply other threads:[~2008-10-24 23:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 19:59 [BUG] oops in net_rx_action on 64-bit powerpc Chris Friesen
2008-10-23 21:50 ` Brandeburg, Jesse
2008-10-24 0:16 ` David Miller
2008-10-24 23:39 ` Chris Friesen [this message]
2008-10-24 23:41 ` David Miller
2008-10-25 5:42 ` Chris Friesen
2008-10-25 7:17 ` David Miller
2008-10-28 0:13 ` Chris Friesen
2008-10-28 22:51 ` David Miller
2008-10-28 22:59 ` Chris Friesen
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=49025C94.60406@nortel.com \
--to=cfriesen@nortel.com \
--cc=davem@davemloft.net \
--cc=jesse.brandeburg@intel.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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).