2.6.20-rc6 SCSI error: I/O error - trouble with mass storage devices ?!

Soeren Sonnenburg <[email protected]>
Newsgroups gmane.linux.usb.devel,gmane.linux.kernel
Message-ID <1169909796.2462.56.camel@localhost>
Dear all,

I am trying to use a P990 phone in via mass storage under linux. I was
able to copy data to/from the phone without trouble under winxp but
receive millions of I/O errors (see below (*), basically on any sector).
As this was also happening on a casio camera (and working on winxp) I
tried a couple of things to nail this down:

1) I removed the ehci module (the P990's mass storage device seems to be
usb1.1 anyway, the casio cam has USB2) such that the UHCI module takes
over => same errors

2) I disabled all the as EXPERIMENTAL marked features under USB support,
i.e. Full speed ISO transactions, Root Hub Transaction Translators,
Improved Transaction Translator scheduling and USB selective
suspend/resume and wakeup => same errors

3) Tried with a sandisk 2G memory stick -> no problems at all

4) I enabled usb mass storage verbose debug output and collected 2 runs
of I/O once with the sandisk and one with the P990 (attached as sandisk
and p990)

5) ran a complete scandisk / check sectors under winxp  -> no problems

6) I tried on a completely different machine running 2.6.19.2 but still
got the same results.

Now I am clueless what could have gone wrong (as I *think* this was all
working at some point at least before firmware updates) and what the
difference between these mass storage devices is.

(*)
usb-storage: device scan complete
scsi 4:0:0:0: Direct-Access              P990i            1.0  PQ: 0 ANSI: 0
SCSI device sdb: 3995272 512-byte hdwr sectors (2046 MB)
sdb: Write Protect is off
sdb: Mode Sense: 03 00 00 00
sdb: assuming drive cache: write through
SCSI device sdb: 3995272 512-byte hdwr sectors (2046 MB)
sdb: Write Protect is off
sdb: Mode Sense: 03 00 00 00
sdb: assuming drive cache: write through
 sdb:
sd 4:0:0:0: Attached scsi removable disk sdb
sd 4:0:0:0: Attached scsi generic sg2 type 0
sd 4:0:0:0: SCSI error: return code = 0x10070000
end_request: I/O error, dev sdb, sector 7
Buffer I/O error on device sdb, logical block 7
lost page write due to I/O error on sdb
Buffer I/O error on device sdb, logical block 8
lost page write due to I/O error on sdb
Buffer I/O error on device sdb, logical block 9
lost page write due to I/O error on sdb
Buffer I/O error on device sdb, logical block 10
lost page write due to I/O error on sdb
Buffer I/O error on device sdb, logical block 11
lost page write due to I/O error on sdb
[...]
sd 4:0:0:0: SCSI error: return code = 0x10070000
end_request: I/O error, dev sdb, sector 434937
sd 4:0:0:0: SCSI error: return code = 0x10070000
end_request: I/O error, dev sdb, sector 435177
sd 4:0:0:0: SCSI error: return code = 0x10070000
end_request: I/O error, dev sdb, sector 435417
sd 4:0:0:0: SCSI error: return code = 0x10070000
end_request: I/O error, dev sdb, sector 435657
sd 4:0:0:0: SCSI error: return code = 0x10070000
end_request: I/O error, dev sdb, sector 1411257
sd 4:0:0:0: SCSI error: return code = 0x10070000
end_request: I/O error, dev sdb, sector 1411497
sd 4:0:0:0: SCSI error: return code = 0x10070000


Any ideas,
Soeren
-- 
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
p990.bz2 (application/x-bzip, 234.1 KB) - not displayed
sandisk.bz2 (application/x-bzip, 5.6 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.