From: Mark Hounschell <markh@compro.net>
To: linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: New 2.6.24.2 SG_IO SCSI problems
Date: Thu, 21 Feb 2008 10:15:20 -0500 [thread overview]
Message-ID: <47BD9588.9080803@compro.net> (raw)
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
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
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
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
.
.
.
.
.
.
The status elements of the sg_io_hdr_t structure used in the application returns
status = 0x0 msg_status 0x0 host_status = 0x7 driver_status = 0x0
The hardware in use on this particular machine is an simple Adaptec AHA-2930CU talking to an old
IMPRIMIS 94601-15 1.2GB disk drive.
Again, all this works fine with the 2.6.23.11 kernel
Any help would be appreciated
Regards
Mark Hounschell
next reply other threads:[~2008-02-21 15:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 15:15 Mark Hounschell [this message]
2008-02-21 15:41 ` New 2.6.24.2 SG_IO SCSI problems James Bottomley
2008-02-21 16:21 ` Mark Hounschell
2008-02-22 10:03 ` Mark Hounschell
2008-02-22 16:50 ` Mike Christie
2008-02-22 16:59 ` Mike Christie
2008-02-22 17:56 ` Mark Hounschell
2008-02-22 21:38 ` Mark Hounschell
2008-02-22 22:25 ` Mike Christie
2008-02-22 22:48 ` Tony Battersby
2008-02-23 11:16 ` Mark Hounschell
2008-03-05 11:58 ` Mark Hounschell
2008-03-05 15:44 ` James Bottomley
2008-03-05 16:28 ` Mark Hounschell
2008-03-05 17:13 ` Mike Christie
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=47BD9588.9080803@compro.net \
--to=markh@compro.net \
--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