From: David Ford <david@blue-labs.org>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: A.J.Scott@casdn.neu.edu,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.8 aic7xxx -- continuous bus resets
Date: Thu, 16 Aug 2001 21:32:06 -0400 [thread overview]
Message-ID: <3B7C7416.2060006@blue-labs.org> (raw)
In-Reply-To: <200108170001.f7H01GI82362@aslan.scsiguy.com>
IIRC, the fix for this in my situation was due to the pci irq routing on
that particular motherboard and using noapic solved it.
Has the irq routing been fixed to date?
David
Justin T. Gibbs wrote:
>>I thought I'd look at the 2.4.8 kernel while I figure out what's
>>wrong with my 2.2.18 installation. The kernel loading gets stuck with
>>errors from the aic7xxx driver, which keeps timeing out querying the
>>bus looking for non-existant drives, and when it finaly tries to
>>query a drive that exists it claims to see bus errors. End result is
>>that Linux 2.4.8 never mounts any drives or finishes loading.
>>
>>The system is an IBM 704 with a built in adaptec aic-7880U
>>controller, with two drives on first scsi buss.
>>
>>2.2.18 has no problems with the adaptec controllers, but has other
>>issues, which seem to be timer related.
>>
>
>2.4.9 has the latest aic7xxx driver in it. Can you see if that changes
>things for you? If not, can you hook up a serial console to the machine
>and provide all of the messages from an aic7xxx=verbose boot?
>
next prev parent reply other threads:[~2001-08-17 1:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 20:04 2.4.8 aic7xxx -- continuous bus resets Andrew Scott
2001-08-17 0:01 ` Justin T. Gibbs
2001-08-17 1:32 ` David Ford [this message]
2001-09-20 15:54 ` 2.4.10pre10 aic7xxx problem Benjamin Herrenschmidt
2001-09-20 17:10 ` Justin T. Gibbs
2001-08-20 13:41 ` 2.4.8 aic7xxx -- continuous bus resets Andrew Scott
2001-08-20 20:32 ` Justin T. Gibbs
2001-08-20 15:12 ` Andrew Scott
2001-08-20 20:32 ` Justin T. Gibbs
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=3B7C7416.2060006@blue-labs.org \
--to=david@blue-labs.org \
--cc=A.J.Scott@casdn.neu.edu \
--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