From: James Bottomley <James.Bottomley@SteelEye.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Burton Windle <bwindle@fint.org>,
linux-kernel@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Sumant Patro <sumant.patro@lsi.com>,
megaraidlinux@lsi.com, linux-scsi@vger.kernel.org
Subject: Re: 2.6.23-rc9 boot failure (megaraid?)
Date: Tue, 02 Oct 2007 15:38:13 -0500 [thread overview]
Message-ID: <1191357493.3530.129.camel@localhost.localdomain> (raw)
In-Reply-To: <20071002181518.GC10852@stusta.de>
On Tue, 2007-10-02 at 20:15 +0200, Adrian Bunk wrote:
> Cc's added, the complete bug report is at
> http://lkml.org/lkml/2007/10/2/243
>
> On Tue, Oct 02, 2007 at 12:48:26PM -0400, Burton Windle wrote:
> > 2.6.23-rc9 fails to boot for me; 2.6.22.9 works fine.
> >
> > System is a Dell Poweredge with PERC 2/DC with RAID1 volume.
> >...
>
> Thanks for your report.
>
> Diff'ing the dmesg's shows:
>
> <-- snip -->
>
> scsi0: scanning scsi channel 4 [P0] for physical devices.
> scsi0: scanning scsi channel 5 [P1] for physical devices.
> st: Version 20070203, fixed bufsize 32768, s/g segs 256
> -sd 0:0:0:0: [sda] 17547264 512-byte hardware sectors (8984 MB)
> +sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
> +sd 0:0:0:0: [sda] 1 512-byte hardware sectors (0 MB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Asking for cache data failed
> sd 0:0:0:0: [sda] Assuming drive cache: write through
> -sd 0:0:0:0: [sda] 17547264 512-byte hardware sectors (8984 MB)
> +sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
> +sd 0:0:0:0: [sda] 1 512-byte hardware sectors (0 MB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Asking for cache data failed
> sd 0:0:0:0: [sda] Assuming drive cache: write through
> sda: sda1
> + sda: p1 exceeds device capacity
>
> <-- snip -->
>
> - case MEGA_BULK_DATA:
> - if (scb->cmd->use_sg == 0)
> - length = scb->cmd->request_bufflen;
> - else {
> - struct scatterlist *sgl =
> - (struct scatterlist *)scb->cmd->request_buffer;
> - length = sgl->length;
> - }
> - pci_unmap_page(adapter->dev, scb->dma_h_bulkdata,
> - length, scb->dma_direction);
> - break;
> -
This is the problem piece I think. We've reintroduced a very old bug:
commit 51c928c34fa7cff38df584ad01de988805877dba
Author: James Bottomley <James.Bottomley@SteelEye.com>
Date: Sat Oct 1 09:38:05 2005 -0500
[SCSI] Legacy MegaRAID: Fix READ CAPACITY
Some Legacy megaraid cards can't actually cope with the scatter/gather
version of the READ CAPACITY command (which is what we now send them
since altering all SCSI internal I/O to go via the block layer). Fix
this (and a few other broken megaraid driver assumptions) by sending
the non-sg version of the command if the sg list only has a single
element.
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
So what we have to do is put back the check for use_sg == 1 and send
that as a bulk transfer command.
James
next prev parent reply other threads:[~2007-10-02 20:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 16:48 2.6.23-rc9 boot failure (megaraid?) Burton Windle
2007-10-02 18:15 ` Adrian Bunk
2007-10-02 18:46 ` Burton Windle
2007-10-02 19:55 ` Rafael J. Wysocki
2007-10-02 20:38 ` James Bottomley [this message]
2007-10-03 0:00 ` FUJITA Tomonori
2007-10-03 23:32 ` Patro, Sumant
2007-10-03 23:46 ` FUJITA Tomonori
2007-10-04 7:28 ` Jens Axboe
2007-10-04 10:20 ` FUJITA Tomonori
2007-10-04 10:36 ` Jens Axboe
2007-10-04 12:50 ` James Bottomley
2007-10-04 10:48 ` Adrian Bunk
2007-10-04 10:55 ` FUJITA Tomonori
2007-10-04 11:00 ` Jens Axboe
2007-10-03 0:09 ` FUJITA Tomonori
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=1191357493.3530.129.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=bunk@kernel.org \
--cc=bwindle@fint.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=megaraidlinux@lsi.com \
--cc=sumant.patro@lsi.com \
/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