From: Matthew Wilcox <matthew@wil.cx>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-scsi@vger.kernel.org
Subject: Re: [Bug 13716] New: The AIC-7892P controller does not work any more
Date: Sun, 5 Jul 2009 13:51:26 -0600 [thread overview]
Message-ID: <20090705195126.GT5480@parisc-linux.org> (raw)
In-Reply-To: <bug-13716-11613@http.bugzilla.kernel.org/>
On Sun, Jul 05, 2009 at 07:23:18PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=13716
>
> The usual probe fails with an error message saying that no IRQ could be
> assigned to the controller, possibly due to a corrupt MP table.
>
> The controller works fine with 2.6.30.1 and below.
>
> This is how the adapter is normally initialized (messages from 2.6.29.6):
> aic7xxx 0000:01:03.0: PCI INT A -> GSI 28 (level, low) -> IRQ 28
> scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
> <Adaptec aic7892 Ultra160 SCSI adapter>
> aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
>
> With 2.6.31-rc1, the kernel freezes with an error message and tries to restart
> the controller periodically, which always fails.
That sounds like you have an interrupt routing problem, not a problem
with the AIC driver. Can you bisect this down to a particular commit?
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-07-05 19:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-05 19:23 [Bug 13716] New: The AIC-7892P controller does not work any more bugzilla-daemon
2009-07-05 19:51 ` Matthew Wilcox [this message]
2009-07-05 19:51 ` [Bug 13716] " bugzilla-daemon
2009-07-05 19:54 ` [Bug 13716] New: " James Bottomley
2009-07-05 19:54 ` [Bug 13716] " bugzilla-daemon
2009-07-05 21:19 ` bugzilla-daemon
2009-08-10 14:50 ` bugzilla-daemon
2009-08-10 14:50 ` bugzilla-daemon
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=20090705195126.GT5480@parisc-linux.org \
--to=matthew@wil.cx \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).