Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-11-01 Thread Pat LaVarre
Heads up, I discarded the cc except the usb-storage folk when I replied at: Subject: [usb-storage] Linux dd misaligns why https://lists.one-eyed-alien.net/pipermail/usb-storage/2004-November/ 001108.html Pat LaVarre --- This SF.Net email is

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-11-01 Thread Alan Stern
On Sun, 31 Oct 2004, Pat LaVarre wrote: > Alan S: > > > Why do you say the I/O isn't aligned to page boundaries? > > The memory addresses of the data buffers were not visible. > > The lengths of the commands (CDB's) were aligned: x40 blocks always. > > The addresses (LBA's) of the commands wer

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-31 Thread Pat LaVarre
Andre S: c) We could try pldd in Windows next. Hmm: F:\>pldd.exe if=\\.\K: bs=32768 skip=0 >NUL x 28 00 00 81 45 00 00 00 40 00 .. .. .. .. .. .. "(@@AE@" x 70 00 04 00 00 00 00 0A 00 00 00 00 4B 00 00 00 "[EMAIL PROTECTED]JK@@@" x 00 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. "@@" 43

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-31 Thread Pat LaVarre
Alan S: Why do you say the I/O isn't aligned to page boundaries? The memory addresses of the data buffers were not visible. The lengths of the commands (CDB's) were aligned: x40 blocks always. The addresses (LBA's) of the commands were misaligned: hex x10 blocks off up away from zero. The retry w

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-31 Thread Andre Steinert
Hello, c) We could try pldd in Windows next. Hmm: F:\>pldd.exe if=\\.\K: bs=32768 skip=0 >NUL x 28 00 00 81 45 00 00 00 40 00 .. .. .. .. .. .. "(@@AE@" x 70 00 04 00 00 00 00 0A 00 00 00 00 4B 00 00 00 "[EMAIL PROTECTED]JK@@@" x 00 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. "@@" 4337

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-31 Thread Alan Stern
On Sun, 31 Oct 2004, Pat LaVarre wrote: > We also see sense byte[0] & x80 Valid clear, and bytes [3:4:5:6] INFO > zeroed. That makes me wonder why we saw Linux choose to retry another > 8 blocks along. 8 blocks * 0.5 KiB/block = 4 KiB = an x86 physical > page, I notice ... but I also notice t

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-31 Thread Pat LaVarre
Andres S: I patched pldd: int minSeconds = 30; Thank you. Please remind us now how it was, with the default 28 hour pause, you came to think you had seen a hang and resorted to shut down and restart? That's the test we want to try again with a short timeout, to see if Linux will tell us somethi

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-30 Thread Andre Steinert
Hello, Working from memory, I believe a similar pldd command is: pldd -v if=/dev/sg9 bs=32768 sbs=512 skip=x32B9E10 count=9 >/dev/null This command is slightly more complex than you saw before because in this simulation we have to recreate the rudeness of misalignment. The pldd way of doing that

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-29 Thread Pat LaVarre
Andres S: two more runs of dd, perhaps there's a pattern Certainly we have consistencies, thank you. Oct 30 01:06:12 titanic kernel: usb-storage: 28 00 01 98 ee 50 00 00 40 00 Oct 30 01:06:12 titanic kernel: usb-storage: Bulk Command S 0x43425355 T 0x66921 L 32768 F 128 Trg 0 LUN 0 CL 10 Oct 30

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-29 Thread Andre Steinert
Hello Pat, I'll give you two more runs of dd, perhaps there's a pattern causing the error: 1. run == Sa Okt 30 00:47:43 CEST 2004 dd: Lesen von ,,/dev/sda": Eingabe-/Ausgabefehler 13085+1 Datensätze ein 13085+1 Datensätze aus 13721444352 bytes transferred in 1109,784279 seconds (12364064 byte

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-29 Thread Pat LaVarre
// Everyone: I still don't have any "good" ideas ... we've got a long haul ahead of us if we only solve this as I know how ... would be goodness to get Genesys to tell us what they think those SK ASC ASCQ mean ... // Andre S: Pat, do you need more lines before the error occured? I'm happy - you'

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-29 Thread Andre Steinert
Hello, Me, I'm voting that, for this problem, as for most read/ write failures, we want to collect the CBW and CSW quoted above but also the CDB of: [...] titanic:~# cat nohup.out Fr Okt 29 14:40:56 CEST 2004 dd: Lesen von ,,/dev/sda": Eingabe-/Ausgabefehler 25971+1 Datensätze ein 25971+1 Datensät

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-28 Thread Pat LaVarre
--- http://lxr.linux.no/source/drivers/usb/storage/transport.c?v=2.6.8.1 ... 967 US_DEBUGP("Bulk Command S 0x%x T 0x%x L %d F %d Trg %d LUN %d CL %d\n", ... 1035 US_DEBUGP("Bulk Status S 0x%x T 0x%x R %u Stat 0x%x\n", --- I think those are among the first and last dmesg we want, n

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-28 Thread Pat LaVarre
Oct 26 23:53:09 titanic kernel: usb-storage: Bulk Command S 0x43425355 T 0x4d1a0 L 32768 F 128 Trg 0 LUN 0 CL 10 Oct 26 23:53:10 titanic kernel: usb-storage: Bulk Status S 0x53425355 T 0x4d1a0 R 0 Stat 0x1 Oct 26 23:53:10 titanic kernel: usb-storage: Bulk Command S 0x43425355 T 0x8004d1a0 L 18 F

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-27 Thread Andre Steinert
Hello, Hmmm... These lines look weird: Oct 26 23:53:09 titanic kernel: usb-storage: Bulk Command S 0x43425355 T 0x4d1a0 L 32768 F 128 Trg 0 LUN 0 CL 10 Oct 26 23:53:10 titanic kernel: usb-storage: Bulk Status S 0x53425355 T 0x4d1a0 R 0 Stat 0x1 Oct 26 23:53:10 titanic kernel: usb-storage: Bulk Co

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-27 Thread Alan Stern
On Wed, 27 Oct 2004, Andre Steinert wrote: > Hmmm... These lines look weird: > > Oct 26 23:53:09 titanic kernel: usb-storage: Bulk Command S 0x43425355 T > 0x4d1a0 L 32768 F 128 Trg 0 LUN 0 CL 10 > Oct 26 23:53:10 titanic kernel: usb-storage: Bulk Status S 0x53425355 T > 0x4d1a0 R 0 Stat 0x1 >

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-26 Thread Andre Steinert
Hello, [...] I think those are among the first and last dmesg we want, near the time of trouble. Giving us an extra paragraph before and afterwards probably wouldn't hurt either. titanic:~# cat dd2 date ; time dd if=$1 bs=1M >/dev/null titanic:~# ./dd2 /dev/sdc Di Okt 26 23:39:54 CEST 2004 dd: L

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-26 Thread Alan Stern
On Tue, 26 Oct 2004, Andre Steinert wrote: > > --- http://lxr.linux.no/source/drivers/usb/storage/transport.c?v=2.6.8.1 > > ... > > 967 US_DEBUGP("Bulk Command S 0x%x T 0x%x L %d F %d Trg %d LUN > > %d CL %d\n", > > ... > > 1035 US_DEBUGP("Bulk Status S 0x%x T 0x%x R %u Stat 0x%x\

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-26 Thread Andre Steinert
Hello, Note: I had to kill the pldd-prozess because accessing the first harddisk stopped after 30-60 mins but pldd neither finished nor displayed an error. No interesting dmesg near the kill? Or from your next shutdown? No: /var/log/messages: [...] Oct 20 13:27:36 titanic kernel: Attached scsi g

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-26 Thread Andre Steinert
Hello, Our Linux source comments do not confirm, but I think the corresponding dmesg Linux-ese is: --- http://lxr.linux.no/source/drivers/usb/storage/usb.c?v=2.6.8.1#L361 ... 361 US_DEBUG(usb_stor_show_command(us->srb)); 362 us->proto_handler(us->srb

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-20 Thread Pat LaVarre
Andre S: I'm offline for awhile now. When I return, unless someone has beat me to the work, ... I'll diff the hex dumps of block 0 from multiple runs at the same drive. After that I'll parse block 0 in accord with such examples as my: http://members.aol.com/plscsi/data/partboot.html http://m

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-20 Thread Pat LaVarre
Andre S: I think I remember that syntax like pldd if=\\.\A: ... will work in Windows, if your disk does begin with a Microsoft-style partition table. ... only works if the drive connected has an assigned drive-letter? Yes and no. Yes, I don't have the experience to teach me to accurately guess th

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-20 Thread Pat LaVarre
Andre S: I can't check the drive with this special error under windows because I'm not able to mount ext3 there. Ouch, I woke up in the night thinking about this remark ... Do you mean to say we've connected here in usb-storage before making destructive experiments ok? You haven't yet establishe

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-20 Thread Pat LaVarre
Andre S: Note: I had to kill the pldd-prozess because accessing the first harddisk stopped after 30-60 mins but pldd neither finished nor displayed an error. No interesting dmesg near the kill? Or from your next shutdown? Agreed, having reads of the disk do anything other than repeatedly succee

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-20 Thread Pat LaVarre
I see we're quoting CSW and sense. Sorry, I don't understand "CSW". I'm curious to see the CONFIG_USB_STORAGE_DEBUG dmesg quoted back from the corresponding CBW. The terms CBW and CSW come from the usbmassbulk_10.pdf standard. Our Linux source comments do not confirm, but I think the corresponding

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-20 Thread Andre Steinert
Hello, Oct 18 21:24:01 titanic kernel: usb-storage: -- code: 0x70, key: 0x4, ASC: 0x4b, ASCQ: 0x0 Oct 19 17:49:59 titanic kernel: SCSI error : <2 0 0 0> return code = 0x802 Oct 19 17:49:59 titanic kernel: Current sdc: sense key Hardware Error Oct 19 17:49:59 titanic kernel: Additional sense:

Re: [usb-storage] Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-19 Thread Pat LaVarre
Oct 18 21:24:01 titanic kernel: usb-storage: -- code: 0x70, key: 0x4, ASC: 0x4b, ASCQ: 0x0 Oct 19 17:49:59 titanic kernel: SCSI error : <2 0 0 0> return code = 0x802 Oct 19 17:49:59 titanic kernel: Current sdc: sense key Hardware Error Oct 19 17:49:59 titanic kernel: Additional sense: Data ph

Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-19 Thread Alan Stern
On Tue, 19 Oct 2004, Andre Steinert wrote: > Hello Alan, > > I don't think that it's a harddisk-fault because > - each run of full md5sum-procedure returns different "faulty" sectors > - the same error occurs on two different drives. The drive with the > error shown below is new. > > Do you nee

Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-19 Thread Alan Stern
On Mon, 18 Oct 2004, Andre Steinert wrote: > The attached logfile contains only the relevant period. To help you > finding the right section where the error occured (the file contains > 3922341 lines, 290 MB decompressed): > > [...] > Oct 18 21:24:01 titanic kernel: usb-storage: -- transfer com

Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-18 Thread Alan Stern
On Mon, 18 Oct 2004, Andre Steinert wrote: > Hi Alan, > > could you give me an example-debug message that I should see in the > logfiles? > I reconfigured, then recompiled the kernel (without make-kpkg clean to > save time) but at the moment, I couldn't determine if there a verbose > debugging

Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-18 Thread Alan Stern
On Mon, 18 Oct 2004, Andre Steinert wrote: > It's not a problem of the TetraHub. I connected the Genesys directly to > the NEC-card: > > titanic:/var/log# tail -f -n 0 messages > Oct 18 12:10:18 titanic kernel: SCSI error : <4 0 0 0> return code = > 0x802 > Oct 18 12:10:18 titanic kernel: C

Re: [Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-18 Thread Andre Steinert
Hello, The wiring: NEC USB 2.0 (internal PCI) | v Cypress TetraHub USB 2.0 (5 1/4" Front-Side Case-Hub) | | | v v v 3 * Genesys Logic USB 2.0 (different harddisks) Perhaps, I should try connecting the USB 2.0-harddisks directly to NEC back-side USB 2.0 connectors (could be TetraHub the problem)? I

[Linux-usb-users] Data phase error not solved in 2.6.9-final

2004-10-18 Thread Andre Steinert
Hello, I compiled 2.6.9-final kernel (http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.9-final.tar.bz2) yesterday and tried to read large amounts of data from two of the three usb 2.0 harddisks. titanic:~# cat /sys/bus/scsi/devices/0\:0\:0\:0/max_sectors 64 titanic:~# cat /sys/bus/

Re: [Linux-usb-users] Data phase error

2004-10-17 Thread Andre Steinert
Hello Alan, > There is a well-known problem with drives using the Genesys Logic > interface chip. A work-around was first included in 2.6.9-rc1; any > kernel from that point on should work okay. Ok, I'll wait for 2.6.9-release to do the kernel-build the debian-way. Or is it possible to include thi

Re: [Linux-usb-users] Data phase error

2004-10-17 Thread Alan Stern
On Sun, 17 Oct 2004, Andre Steinert wrote: > Hello, > > when reading large amounts of data from my usb 2.0-harddisk, I'll get > "Data phase"-errors. (About 3-7 errors when reading 220 GB). Note that > I'll only get these errors if I read the harddisk. If I copy from one > harddisk to another,

[Linux-usb-users] Data phase error

2004-10-17 Thread Andre Steinert
Hello, when reading large amounts of data from my usb 2.0-harddisk, I'll get "Data phase"-errors. (About 3-7 errors when reading 220 GB). Note that I'll only get these errors if I read the harddisk. If I copy from one harddisk to another, I'll only get these errors at the source, not the destin