linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Mark Lord <lkml@rtr.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: usb device problem
Date: Tue, 06 Jun 2006 18:07:26 +0159	[thread overview]
Message-ID: <4485A855.1020602@gmail.com> (raw)
In-Reply-To: <4485A299.7070007@rtr.ca>

Mark Lord napsal(a):
> Jiri Slaby wrote:
>> Hello,
>>
>> I get this with 2.6.17-rc5-mm3 kernel:
> ..
>> usb-storage: device found at 10
>> usb-storage: waiting for device to settle before scanning
>>   Vendor:           Model:                   Rev:
>>   Type:   Direct-Access                      ANSI SCSI revision: 00
>> SCSI device sdb: 245920 512-byte hdwr sectors (126 MB)
> ..
>> now read and write and sync or umount, then:
>> ---
>> sd 10:0:0:0: SCSI error: return code = 0x10070000
>> end_request: I/O error, dev sdb, sector 1575
>> sd 10:0:0:0: SCSI error: return code = 0x10070000
>> end_request: I/O error, dev sdb, sector 1583
>> sd 10:0:0:0: SCSI error: return code = 0x10070000
>> end_request: I/O error, dev sdb, sector 1591
>> sd 10:0:0:0: SCSI error: return code = 0x10070000
>> end_request: I/O error, dev sdb, sector 1599
>> sd 10:0:0:0: SCSI error: return code = 0x10070000
>> end_request: I/O error, dev sdb, sector 1607
>> sd 10:0:0:0: SCSI error: return code = 0x10070000
>> end_request: I/O error, dev sdb, sector 1615
>> ... and so on. data are maybe there, but it takes so long to write a
>> meg file.
>> sometimes
> ..
> 
> This *looks* like maybe the drive reported a sector read error,
> and the standard "fail the whole request one block at a time"
> error mechanism from sd.c has kicked in.

Do you mean something like seek error, i.e. error in hardware, or how to call
this? This is brand new minisd card, it is possible to be waster, but it's
rather something bad in the software (writing by the device itself is perfomed
and data are ok). The error occurs accurately every 8 sectors...

> 
> I have a patch to fix this behaviour (in sd.c), but it has not yet
> been decided whether to go upstream with it or not.

Could you post me a copy, please?

thanks,
-- 
Jiri Slaby         www.fi.muni.cz/~xslaby
\_.-^-._   jirislaby@gmail.com   _.-^-._/
B67499670407CE62ACC8 22A032CC55C339D47A7E

  reply	other threads:[~2006-06-06 16:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 15:09 usb device problem Jiri Slaby
2006-06-06 15:43 ` Mark Lord
2006-06-06 16:08   ` Jiri Slaby [this message]
2006-06-06 18:07     ` Mark Lord
2006-06-06 18:13       ` Mark Lord
2006-06-06 21:37         ` Jiri Slaby
2006-06-06 22:46           ` Jiri Slaby
2006-06-07 13:14             ` Mark Lord

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=4485A855.1020602@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=lkml@rtr.ca \
    /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;
as well as URLs for NNTP newsgroup(s).