From: Andrea Arcangeli <andrea@suse.de>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: Andrey Nekrasov <andy@spylog.ru>, linux-kernel@vger.kernel.org
Subject: Re: Adaptec Aic7xxx driver & 2.4.19pre8aa2
Date: Wed, 15 May 2002 18:48:02 +0200 [thread overview]
Message-ID: <20020515164802.GG25593@dualathlon.random> (raw)
In-Reply-To: <20020515130328.GA19698@spylog.ru> <200205151435.g4FEZo990223@aslan.scsiguy.com>
On Wed, May 15, 2002 at 08:35:50AM -0600, Justin T. Gibbs wrote:
> >Hello.
> >
> >Hardware motherboard: Intel "Lancewood" L440GX, SCSI integrated, last BIOS/BMC
> >
> >1. 2.4.19pre1aa1 : : 1CPU/HIGHMEM/3.5Gb
>
> The key bit in the dump is this:
>
> >scsi0:0:0:0: Attempting to queue an ABORT message
> >...
> >scsi0:0:4:0: Command already completed
>
> Interrupts are not getting routed correctly for your motherboard
> in the 2.4.19pre release you are running. I'm not sure what has
> changed there, but the aic7xxx driver is noticing, when told to
> abort a command, that it has already completed, but the interrupt
> for that completion was never received. You may see different
> results if you play with the APIC I/O option.
This is going to be a problem with mainline, if you could do a binary
search across the 2.4.19pre patches (from pre2 to pre8) that would limit
the bug to a certain diff. thanks,
Andrea
next prev parent reply other threads:[~2002-05-15 14:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 13:03 Andrey Nekrasov
2002-05-15 14:03 ` Meelis Roos
2002-05-15 14:37 ` Justin T. Gibbs
2002-05-15 19:19 ` AIC7XXX, 2.4.19-pre8 & AIC7850 problem Meelis Roos
2002-05-15 20:47 ` Andrey Nekrasov
2002-05-16 9:16 ` Meelis Roos
2002-05-15 14:35 ` Adaptec Aic7xxx driver & 2.4.19pre8aa2 Justin T. Gibbs
2002-05-15 16:48 ` Andrea Arcangeli [this message]
2002-05-15 15:30 ` Alan Cox
2002-05-15 15:17 ` Andrea Arcangeli
2002-05-16 12:13 ` Andrey Nekrasov
2002-05-15 20:40 ` Andrey Nekrasov
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=20020515164802.GG25593@dualathlon.random \
--to=andrea@suse.de \
--cc=andy@spylog.ru \
--cc=gibbs@scsiguy.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
all inboxes | Powered by JetHome®