From: Willy Tarreau <willy@w.ods.org>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: Willy Tarreau <willy@w.ods.org>,
Daniel Podlejski <underley@underley.eu.org>,
linux-kernel@vger.kernel.org
Subject: Re: AIC7xxx problem
Date: Sun, 1 Jun 2003 22:45:16 +0200 [thread overview]
Message-ID: <20030601204516.GA15693@alpha.home.local> (raw)
In-Reply-To: <2859720000.1054499680@aslan.scsiguy.com>
On Sun, Jun 01, 2003 at 02:34:40PM -0600, Justin T. Gibbs wrote:
> > Hmmm that makes quite a difference ! I didn't understand what happened between
> > these two outputs. Also, did you try with Justin's latest version of the driver:
> >
>
> My driver can't fix interrupt routing issues which is what Daniel's
> problem turned out to be. I'm really tempted to add an interrupt
> test to the driver attach so that these kinds of problems are clearly
> flagged and my driver doesn't continue to get blamed for interrupt
> routing it can't control.
If this is (relatively) easy to do, I really think it could be a valuable
diagnostic tool. I'd prefer to get a clear "fix your APIC" or any insult
about my hardware config than devices detection dying in endless timeout
loops.
This principle may even be generalized to any other driver which can make the
device trigger an interrupt.
Cheers,
Willy
next prev parent reply other threads:[~2003-06-01 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-31 16:59 AIC7xxx problem Daniel Podlejski
2003-06-01 8:19 ` Daniel Podlejski
2003-06-01 8:36 ` Willy Tarreau
2003-06-01 20:34 ` Justin T. Gibbs
2003-06-01 20:45 ` Willy Tarreau [this message]
2003-06-01 20:56 ` Zwane Mwaikambo
2003-06-01 21:37 ` Justin T. Gibbs
2003-06-01 21:38 ` Zwane Mwaikambo
-- strict thread matches above, loose matches on Subject: below --
2002-11-05 22:34 aic7xxx problem Emmanuel Fuste
2002-11-06 1:24 ` Philippe Troin
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=20030601204516.GA15693@alpha.home.local \
--to=willy@w.ods.org \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=underley@underley.eu.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