Subject: Re: New 2.6.24.2 SG_IO SCSI problems
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: markh@compro.net
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
In-Reply-To: <47BD9588.9080803@compro.net>
References: <47BD9588.9080803@compro.net>
Content-Type: text/plain
Date: Thu, 21 Feb 2008 09:41:13 -0600
Message-Id: <1203608474.3208.10.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1127
Lines: 23

On Thu, 2008-02-21 at 10:15 -0500, Mark Hounschell wrote:
> I seem to have run into some sort of regression in the SG_IO interface of 2.6.24.2. 
> I have an application that up until 2.6.24 worked fine. The 2.6.23.16 kernel works fine.
> 
> During reads I get these kernel messages. Writes and other functions _seem_ OK. Actually basic
> reads  are working. Its with large BC reads using an io_vec list that the problem shows up.
> 
> Feb 21 09:27:51 harley kernel: (scsi1:A:2:0): data overrun detected in Data-in phase.  Tag == 0x1.
> Feb 21 09:27:51 harley kernel: (scsi1:A:2:0): Have seen Data Phase.  Length = 256.  NumSGs = 1.
> Feb 21 09:27:51 harley kernel: sg[0] - Addr 0x06256100 : Length 256

Help me a little here.  What was the io_vec and command you sent in to
produce this?  The aic debugging information implies a single element sg
list for a 256 byte read.

James


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/