From: Andrew Morton <akpm@osdl.org>
To: earny@net4u.de
Cc: list-lkml@net4u.de, linux-kernel@vger.kernel.org,
Richard Henderson <rth@twiddle.net>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: Re: ALPHA 2.6.17-rc5 AIC7###: does not boot
Date: Wed, 31 May 2006 15:46:48 -0700 [thread overview]
Message-ID: <20060531154648.53539006.akpm@osdl.org> (raw)
In-Reply-To: <200605301834.19795.list-lkml@net4u.de>
Ernst Herzberg <list-lkml@net4u.de> wrote:
>
> moinmoin.
>
> 2.6.16.18 boots and runs without problems.
>
> 2.6.17-rc5 with patch
> "[PATCH] alpha: generic hweight (Re: ALPHA 2.6.17-rc5 compile error)"
> http://www.ussg.iu.edu/hypermail/linux/kernel/0605.3/1559.html
>
> hangs with
>
> [....]
> scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
> <Adaptec aic7895 Ultra SCSI adapter>
> aic7895C: Ultra Wide Channel B, SCSI Id=7, 32/253 SCBs
>
> 1:0:0:0: Attempting to queue an ABORT message
> CDB:CDB: 0x12 0x12 0x0 0x0 0x0 0x0 0x0 0x0 0x24 0x24 0x0 0x0
> 1:0:0:0: Command already completed
> aic7xxx_abort returns 0x2002
> 1:0:0:0: Attempting to queue an ABORT message
> CDB: 0x12 0x0 0x0 0x0 0x24 0x0
> 1:0:0:0: Command already completed
> aic7xxx_abort returns 0x2002
> [....]
>
> dmesg (captured with netconsole and netcat, most messages are duplicated
> but better than nothing)
>
> ...
>
James sayeth "Best guess would be lost interrupt ... especially if there's
no device usually at target1:0:0 (i.e. the machine doesn't get a reply it
expects doing the initial inquiry)."
But I don't recall us making any changes in the Alpha interrupt-management
code post-2.6.16. Perhaps it was PCI changes which introduced this
regression.
next prev parent reply other threads:[~2006-05-31 22:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 16:34 Ernst Herzberg
2006-05-31 22:46 ` Andrew Morton [this message]
2006-06-01 16:16 ` Ivan Kokshaysky
2006-06-01 17:11 ` Ernst Herzberg
2006-06-01 17:33 ` Andrew Morton
2006-06-01 21:13 ` Ivan Kokshaysky
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=20060531154648.53539006.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=earny@net4u.de \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=list-lkml@net4u.de \
--cc=rth@twiddle.net \
/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®