Message-ID: <47BF0CE2.306@compro.net>
Date: Fri, 22 Feb 2008 12:56:50 -0500
From: Mark Hounschell <markh@compro.net>
Reply-To: markh@compro.net
Organization: Compro Computer Svcs.
User-Agent: Thunderbird 2.0.0.9 (X11/20070801)
MIME-Version: 1.0
To: Mike Christie <michaelc@cs.wisc.edu>
CC: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: New 2.6.24.2 SG_IO SCSI problems
References: <47BD9588.9080803@compro.net> <47BEFD4B.9060803@cs.wisc.edu> <47BEFF5F.9020002@cs.wisc.edu>
In-Reply-To: <47BEFF5F.9020002@cs.wisc.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1206
Lines: 32

Mike Christie wrote:
> Mike Christie wrote:
>> 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.
>>>
>>
>> Are you doing SG_IO to the sg device (/dev/sg*) or to the block device
>> (/dev/sdX)?
> 
> If you are doing SG_IO to the sg device, then I know of one regression
> (well not regression exactly, but I fixed a bug but the patch got
> partially overwritten by another patch and that caused a new bug). Both
> bugs are fixed in 2.6.25-rc2. Could you try that out if you are doing
> SG_IO to the sg device.
> 

Yes, I'm using /dev/sg*. And yes again I'll checkout 2.6.25-rc2 ASIC.

Thanks
Mark
--
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/