From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Willy Tarreau <willy@w.ods.org>,
Daniel Podlejski <underley@underley.eu.org>,
linux-kernel@vger.kernel.org
Subject: Re: AIC7xxx problem
Date: Sun, 01 Jun 2003 15:37:47 -0600 [thread overview]
Message-ID: <2878250000.1054503467@aslan.scsiguy.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0306011647431.19313-100000@montezuma.mastecende.com>
>> 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.
>
> Which aspect of interrupt routing is broken so that we at least can have a
> go at fixing it? I might be missing something here but it looks fine,
> could you elaborate?
Daniel is comparing 2.4.20-ac2 with 2.4.21-rc6. In 2.4.20-ac2, APIC
routing is disabled by default and his kernel works. In 2.4.21-rc6,
APIC routing is enabled by default and interrupts are not properly
routed to his SCSI controller. If he boots with noapic, everything
works fine. You'll have to ask Daniel for more details on his system
if you want to figure out why interrupts are not being delivered.
All I know is, from the output and his testing, it is pretty obvious
that interrupts are not being delivered.
--
Justin
next prev parent reply other threads:[~2003-06-01 21:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-31 16:59 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
2003-06-01 20:56 ` Zwane Mwaikambo
2003-06-01 21:37 ` Justin T. Gibbs [this message]
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=2878250000.1054503467@aslan.scsiguy.com \
--to=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=underley@underley.eu.org \
--cc=willy@w.ods.org \
--cc=zwane@linuxpower.ca \
/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
all inboxes | Powered by JetHome®