From: Scott Wood <scottwood@freescale.com>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: Oops in fs_enet driver with preempt-rt
Date: Tue, 20 May 2008 10:41:45 -0500 [thread overview]
Message-ID: <4832F139.1020502@freescale.com> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B046E72C3@ismail.innsys.innovsys.com>
Rune Torgersen wrote:
> 0xc0196d84 is in fs_enet_interrupt
> (drivers/net/fs_enet/fs_enet-main.c:473).
> 468 if (fpi->use_napi)
> 469 int_clr_events &= ~fep->ev_napi_rx;
> 470
> 471 (*fep->ops->clear_int_events)(dev,
> int_clr_events);
> 472
> 473 if (int_events & fep->ev_err)
> 474 (*fep->ops->ev_error)(dev, int_events);
> 475
> 476 if (int_events & fep->ev_rx) {
> 477 if (!fpi->use_napi)
> (gdb)
Do you have shared interrupt debugging turned on? That breaks this
driver, and a patch to remove the shared flag was nacked in favor of
actually fixing the driver, which I haven't gotten around to.
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Rune Torgersen <runet@innovsys.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
netdev@vger.kernel.org
Subject: Re: Oops in fs_enet driver with preempt-rt
Date: Tue, 20 May 2008 10:41:45 -0500 [thread overview]
Message-ID: <4832F139.1020502@freescale.com> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B046E72C3@ismail.innsys.innovsys.com>
Rune Torgersen wrote:
> 0xc0196d84 is in fs_enet_interrupt
> (drivers/net/fs_enet/fs_enet-main.c:473).
> 468 if (fpi->use_napi)
> 469 int_clr_events &= ~fep->ev_napi_rx;
> 470
> 471 (*fep->ops->clear_int_events)(dev,
> int_clr_events);
> 472
> 473 if (int_events & fep->ev_err)
> 474 (*fep->ops->ev_error)(dev, int_events);
> 475
> 476 if (int_events & fep->ev_rx) {
> 477 if (!fpi->use_napi)
> (gdb)
Do you have shared interrupt debugging turned on? That breaks this
driver, and a patch to remove the shared flag was nacked in favor of
actually fixing the driver, which I haven't gotten around to.
-Scott
next prev parent reply other threads:[~2008-05-20 15:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 14:40 Oops in fs_enet driver with preempt-rt Rune Torgersen
2008-05-20 14:40 ` Rune Torgersen
2008-05-20 14:53 ` Rune Torgersen
2008-05-20 14:53 ` Rune Torgersen
2008-05-20 15:41 ` Scott Wood [this message]
2008-05-20 15:41 ` Scott Wood
2008-05-20 16:08 ` Rune Torgersen
2008-05-20 16:08 ` Rune Torgersen
2008-05-20 16:14 ` Rune Torgersen
2008-05-20 16:14 ` Rune Torgersen
2008-05-20 16:21 ` Scott Wood
2008-05-20 16:21 ` Scott Wood
2008-05-20 16:31 ` Rune Torgersen
2008-05-20 16:31 ` Rune Torgersen
2008-05-20 16:31 ` Rune Torgersen
2008-05-20 17:33 ` Kumar Gala
2008-05-20 18:53 ` Rune Torgersen
2008-05-20 18:53 ` Rune Torgersen
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=4832F139.1020502@freescale.com \
--to=scottwood@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=runet@innovsys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.