From: Andrew Morton <akpm@linux-foundation.org>
To: Steffen Klassert <klassert@mathematik.tu-chemnitz.de>
Cc: shemminger@vyatta.com, gerhard_pircher@gmx.net, netdev@vger.kernel.org
Subject: Re: 3c59x: shared interrupt problem
Date: Tue, 10 Mar 2009 14:55:42 -0700 [thread overview]
Message-ID: <20090310145542.499128ef.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090310081628.GA3217@newton.mathematik.tu-chemnitz.de>
On Tue, 10 Mar 2009 09:16:28 +0100
Steffen Klassert <klassert@mathematik.tu-chemnitz.de> wrote:
> On Mon, Mar 09, 2009 at 04:49:27PM -0700, Stephen Hemminger wrote:
> > On Mon, 09 Mar 2009 23:42:53 +0100
> > "Gerhard Pircher" <gerhard_pircher@gmx.net> wrote:
> >
> > > Hi!
> > >
> > > Large network transfers fail on my machine (with kernel versions
> > > >v2.6.26) with the kernel oops below. eth0 (3c59x driver) normally
> > > shares its IRQ line with 3 OHCI USB ports (IRQ 7), as the excerpt of
> > > /proc/interrupt shows. Removing USB support from the kernel makes it
> > > work again. I wasn't able to do a full git bisect run yet, as v2.6.27
> > > didn't produce a bootable kernel image for my machine. The machine is
> > > an AmigaOne PowerPC G4 with an onboard 3c920 network chip.
> > >
> > > Any idea?
> >
> > Does this help, it looks like boomerang_interrupt was not doing
> > shared irq stuff correctly.
> >
> > --- a/drivers/net/3c59x.c 2009-03-09 16:07:13.372670015 -0700
> > +++ b/drivers/net/3c59x.c 2009-03-09 16:08:50.214357441 -0700
> > @@ -2301,6 +2301,7 @@ boomerang_interrupt(int irq, void *dev_i
> > void __iomem *ioaddr;
> > int status;
> > int work_done = max_interrupt_work;
> > + int handled = 0;
> >
> > ioaddr = vp->ioaddr;
> >
> > @@ -2323,6 +2324,7 @@ boomerang_interrupt(int irq, void *dev_i
> > printk(KERN_DEBUG "boomerang_interrupt(1): status = 0xffff\n");
> > goto handler_exit;
> > }
> > + handled = 1;
> >
> > if (status & IntReq) {
> > status |= vp->deferred;
> > @@ -2417,7 +2419,7 @@ boomerang_interrupt(int irq, void *dev_i
> > dev->name, status);
> > handler_exit:
> > spin_unlock(&vp->lock);
> > - return IRQ_HANDLED;
> > + return IRQ_RETVAL(handled);
> > }
> >
> > static int vortex_rx(struct net_device *dev)
> >
>
> This basically reverts a patch from akpm (bitkeeper cset 1.1046.95.8)
> This patch was to workaround lots of "nobody cared" warnings generated by
> boomerang_interrupt().
> I added Andrew to the Cc, perhaps he can remember some details on this.
>
Beats me. Do you havea full copy of that patch, including changelog?
Thanks.
next prev parent reply other threads:[~2009-03-10 21:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 22:42 3c59x: shared interrupt problem Gerhard Pircher
2009-03-09 23:49 ` Stephen Hemminger
2009-03-10 8:16 ` Steffen Klassert
2009-03-10 21:55 ` Andrew Morton [this message]
2009-03-11 11:38 ` Steffen Klassert
2009-03-13 22:51 ` David Miller
2009-03-14 14:08 ` Steffen Klassert
2009-03-14 18:40 ` David Miller
2009-03-17 9:37 ` Gerhard Pircher
[not found] ` <20090310090053.322240@gmx.net>
2009-03-11 11:31 ` Steffen Klassert
2009-03-27 7:59 ` Steffen Klassert
2009-03-28 14:17 ` Gerhard Pircher
2009-04-21 18:36 ` Gerhard Pircher
-- strict thread matches above, loose matches on Subject: below --
2009-03-11 22:42 Gerhard Pircher
2009-03-12 14:39 ` Steffen Klassert
2009-03-12 15:12 ` Gerhard Pircher
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=20090310145542.499128ef.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gerhard_pircher@gmx.net \
--cc=klassert@mathematik.tu-chemnitz.de \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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.