From: Grant Grundler <grundler@cup.hp.com>
To: John Marvin <jsm@udlkern.fc.hp.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Tulip Driver Bug
Date: Wed, 23 Feb 2000 10:22:27 -0800 [thread overview]
Message-ID: <200002231822.KAA15029@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Wed, 23 Feb 2000 09:25:55 PST." <200002231625.JAA27870@udlkern.fc.hp.com>
John Marvin wrote:
> My understanding is that this code tries to defer work until later because
> too many incoming packets have been handled during the current interrupt.
> The problem is that there is no later.
John,
thanks for bringing it this far.
Can someone verify the IRQ line is remains asserted?
If the IRQ line is asserted, this sounds like a problem in iosapic code.
I've seen this behavior before when iosapic_isr() didn't write the
correct value to the EOI register. I'll review the iosapic code.
But if someone could give me confidence the IRQ is asserted, I'd
appreciate it.
thanks,
grant
Grant Grundler
Unix Development Lab
+1.408.447.7253
prev parent reply other threads:[~2000-02-23 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-23 16:25 [parisc-linux] Tulip Driver Bug John Marvin
2000-02-23 18:22 ` Grant Grundler [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=200002231822.KAA15029@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=jsm@udlkern.fc.hp.com \
--cc=parisc-linux@thepuffingroup.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.