From: "David S. Miller" <davem@redhat.com>
To: akpm@digeo.com
Cc: johnstul@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: tg3 - irq #: nobody cared!
Date: Tue, 06 May 2003 21:03:32 -0700 (PDT) [thread overview]
Message-ID: <20030506.210332.23029446.davem@redhat.com> (raw)
In-Reply-To: <20030506220802.6d494326.akpm@digeo.com>
From: Andrew Morton <akpm@digeo.com>
Date: Tue, 6 May 2003 22:08:02 -0700
So I'd be suspecting the scenario which Alan outlined: the IRQ
handler looped around, scooped up the interrupt source before the
APIC delivered the IRQ.
That certainly what happens with tg3.
Suggest we ignore these reports until that is sorted out.
Ok.
next prev parent reply other threads:[~2003-05-07 4:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 22:03 tg3 - irq #: nobody cared! john stultz
2003-05-07 4:58 ` David S. Miller
2003-05-07 5:08 ` Andrew Morton
2003-05-07 4:03 ` David S. Miller [this message]
2003-05-07 11:57 Chuck Ebbert
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=20030506.210332.23029446.davem@redhat.com \
--to=davem@redhat.com \
--cc=akpm@digeo.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@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).