From: James Bottomley <James.Bottomley@SteelEye.com>
To: bernd-schubert@gmx.de
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: aic79xx oops
Date: Sat, 10 Sep 2005 10:06:05 -0500 [thread overview]
Message-ID: <1126364765.4813.16.camel@mulgrave> (raw)
In-Reply-To: <200509091325.45620.bernd.schubert@pci.uni-heidelberg.de>
On Fri, 2005-09-09 at 13:25 +0200, Bernd Schubert wrote:
> Vendor: transtec Model: T5008 Rev: 0001
> Type: Direct-Access ANSI SCSI revision: 03
> scsi4:A:0:0: Tagged Queuing enabled. Depth 32
> SCSI device sdc: 4101521408 512-byte hdwr sectors (2099979 MB)
> SCSI device sdc: drive cache: write back
> SCSI device sdc: 4101521408 512-byte hdwr sectors (2099979 MB)
> SCSI device sdc: drive cache: write back
> sdc: sdc1 sdc2 sdc3 < sdc5 sdc6 sdc7 sdc8 >
> Attached scsi disk sdc at scsi4, channel 0, id 0, lun 0
> Attached scsi generic sg2 at scsi4, channel 0, id 0, lun 0, type 0
> scsi: host 4 channel 0 id 0 lun 0x00000200080c0400 has a LUN larger than
> currently supported.
> scsi: host 4 channel 0 id 0 lun1002486961 has a LUN larger than allowed by the
> host adapter
> scsi: host 4 channel 0 id 0 lun 0x01000000407a27c0 has a LUN larger than
> currently supported.
> scsi: host 4 channel 0 id 0 lun 0x007a27c0d05d27c0 has a LUN larger than
> currently supported.
> scsi: host 4 channel 0 id 0 lun 0x305e27c0907b27c0 has a LUN larger than
> currently supported.
> scsi: host 4 channel 0 id 0 lun 0xf08227c0b08d27c0 has a LUN larger than
> currently supported.
> scsi: host 4 channel 0 id 0 lun 0x307827c0008527c0 has a LUN larger than
> currently supported.
> scsi: host 4 channel 0 id 0 lun 0x00000000b06727c0 has a LUN larger than
> currently supported.
> scsi: host 4 channel 0 id 0 lun 0x306727c0706727c0 has a LUN larger than
> currently supported.
This looks symptomatic of a report luns failure
> EIP is at ahd_send_async+0xde/0x2a0 [aic79xx]
This I'm not sure about. There are some fixes that may correct this in
the current kernel tree head (i.e. beyond 2.6.13), if you could give
that a go.
James
prev parent reply other threads:[~2005-09-10 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 11:25 aic79xx oops Bernd Schubert
2005-09-10 15:06 ` James Bottomley [this message]
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=1126364765.4813.16.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=bernd-schubert@gmx.de \
--cc=linux-kernel@vger.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