Re: Kingston Datatraveler
On Mon, 7 Jan 2008 16:36:56 -0500 (EST), Alan Stern <[EMAIL PROTECTED]> wrote: > I'm afraid I'm out of good ideas. You can try playing around with the > code in drivers/usb/storage/transport.c, adding delays here and there > to see if they make any difference. Sorry for repeating this, but usbmon provides a useful timestamp, especially on more modern systems with something like HPET timer. By comparing timestamps for the case of cat writing to serial port and to disk, one may be able to detect the difference and thus know where to add delays that Alan mentions above. -- Pete - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Kingston Datatraveler
On Thu, 3 Jan 2008, Brian Murphy wrote: > Hi, > > I tried this but it has the same result. I'm afraid I'm out of good ideas. You can try playing around with the code in drivers/usb/storage/transport.c, adding delays here and there to see if they make any difference. Alan Stern - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Kingston Datatraveler
Hi, I tried this but it has the same result. Brian On Dec 31, 2007 9:51 PM, Alan Stern <[EMAIL PROTECTED]> wrote: > On Sun, 30 Dec 2007, Brian Murphy wrote: > > > Hi, > > > > I install Win XP on the system and the drive works fine. > > > > I have tested this with both Ubuntu and Fedore destributions as well > > as kernels I have compiled myself. I have also tested it with 3 > > different Kingston drives. I have also used 3 different EMC-3610 > > boards just to ensure my board is not faulty. All with the same result > > > > Is there any way I can modifie the driver so I see the same result as > > when I put the debug output to the serial port. It seem to effect the > > timing and lets the drive work. > > You can try applying this patch. It implements Pete's suggestion to > slow down the data transfers. > > Alan Stern > > > Index: 2.6.24-rc5-mm1/drivers/usb/storage/unusual_devs.h > === > --- 2.6.24-rc5-mm1.orig/drivers/usb/storage/unusual_devs.h > +++ 2.6.24-rc5-mm1/drivers/usb/storage/unusual_devs.h > @@ -1223,6 +1223,13 @@ UNUSUAL_DEV( 0x090c, 0x1132, 0x, 0xf > US_SC_DEVICE, US_PR_DEVICE, NULL, > US_FL_FIX_CAPACITY ), > > +/* Reported by Brian Murphy <[EMAIL PROTECTED]> */ > +UNUSUAL_DEV( 0x0951, 0x1607, 0x0200, 0x0200, > + "Kingston", > + "DataTraveler", > + US_SC_DEVICE, US_PR_DEVICE, NULL, > + US_FL_GO_SLOW ), > + > /* This Pentax still camera is not conformant > * to the USB storage specification: - > * - It does not like the INQUIRY command. So we must handle this command > > - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Kingston Datatraveler
On Sun, 30 Dec 2007, Brian Murphy wrote: > Hi, > > I install Win XP on the system and the drive works fine. > > I have tested this with both Ubuntu and Fedore destributions as well > as kernels I have compiled myself. I have also tested it with 3 > different Kingston drives. I have also used 3 different EMC-3610 > boards just to ensure my board is not faulty. All with the same result > > Is there any way I can modifie the driver so I see the same result as > when I put the debug output to the serial port. It seem to effect the > timing and lets the drive work. You can try applying this patch. It implements Pete's suggestion to slow down the data transfers. Alan Stern Index: 2.6.24-rc5-mm1/drivers/usb/storage/unusual_devs.h === --- 2.6.24-rc5-mm1.orig/drivers/usb/storage/unusual_devs.h +++ 2.6.24-rc5-mm1/drivers/usb/storage/unusual_devs.h @@ -1223,6 +1223,13 @@ UNUSUAL_DEV( 0x090c, 0x1132, 0x, 0xf US_SC_DEVICE, US_PR_DEVICE, NULL, US_FL_FIX_CAPACITY ), +/* Reported by Brian Murphy <[EMAIL PROTECTED]> */ +UNUSUAL_DEV( 0x0951, 0x1607, 0x0200, 0x0200, + "Kingston", + "DataTraveler", + US_SC_DEVICE, US_PR_DEVICE, NULL, + US_FL_GO_SLOW ), + /* This Pentax still camera is not conformant * to the USB storage specification: - * - It does not like the INQUIRY command. So we must handle this command - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Kingston Datatraveler
On Sun, 30 Dec 2007 22:48:39 +, "Brian Murphy" <[EMAIL PROTECTED]> wrote: > I install Win XP on the system and the drive works fine. Great. I hope it was a dual-boot setup. > Is there any way I can modifie the driver so I see the same result as > when I put the debug output to the serial port. It seem to effect the > timing and lets the drive work. No, I don't think we have enough resolution for this... Although you can compare timestamps which usbmon reports in both cases. I do it sometimes in such instances. BTW: > > > I think your device is asking for US_FL_GO_SLOW or equivalent. You might want to throw that in and see if it sticks. -- Pete - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Kingston Datatraveler
Hi, I install Win XP on the system and the drive works fine. I have tested this with both Ubuntu and Fedore destributions as well as kernels I have compiled myself. I have also tested it with 3 different Kingston drives. I have also used 3 different EMC-3610 boards just to ensure my board is not faulty. All with the same result Is there any way I can modifie the driver so I see the same result as when I put the debug output to the serial port. It seem to effect the timing and lets the drive work. Thanks for your help. On Dec 22, 2007 3:46 AM, Alan Stern <[EMAIL PROTECTED]> wrote: > > On Fri, 21 Dec 2007, Pete Zaitcev wrote: > > > On Fri, 21 Dec 2007 10:50:06 +, "Brian Murphy" <[EMAIL PROTECTED]> > > wrote: > > > > > I just discover some thing, If I ouput the trace to > > > a serial port the system works fine. However If I output the trace to > > > the disk I have the same problem as before. [...] > > > > I think your device is asking for US_FL_GO_SLOW or equivalent. > > It keels over on the very first read after the WP sensing: > > > > > c12e7ea0 43055373 S Bo:1:004:2 -115 31 = 55534243 0b00 0010 > > > 8a28 0008 00 > > > c12e7ea0 43056075 C Bo:1:004:2 0 31 > > > > c12e7720 43056160 S Bi:1:004:1 -115 4096 < > > > c12e7720 43162104 C Bi:1:004:1 -84 0 > > > > I had major issues with the Kingston in the past because they do not > > like a halt clear while not halted, but nothing like this. Perhaps > > it's a new cheaper revision, buggier than before. > > That's possible. It leaves open the question of why the device works > okay when no mouse nor any other HID device is attached... > > Alan Stern > > - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Kingston Datatraveler
On Fri, 21 Dec 2007, Pete Zaitcev wrote: > On Fri, 21 Dec 2007 10:50:06 +, "Brian Murphy" <[EMAIL PROTECTED]> wrote: > > > I just discover some thing, If I ouput the trace to > > a serial port the system works fine. However If I output the trace to > > the disk I have the same problem as before. [...] > > I think your device is asking for US_FL_GO_SLOW or equivalent. > It keels over on the very first read after the WP sensing: > > > c12e7ea0 43055373 S Bo:1:004:2 -115 31 = 55534243 0b00 0010 > > 8a28 0008 00 > > c12e7ea0 43056075 C Bo:1:004:2 0 31 > > > c12e7720 43056160 S Bi:1:004:1 -115 4096 < > > c12e7720 43162104 C Bi:1:004:1 -84 0 > > I had major issues with the Kingston in the past because they do not > like a halt clear while not halted, but nothing like this. Perhaps > it's a new cheaper revision, buggier than before. That's possible. It leaves open the question of why the device works okay when no mouse nor any other HID device is attached... Alan Stern - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Kingston Datatraveler
On Fri, 21 Dec 2007 10:50:06 +, "Brian Murphy" <[EMAIL PROTECTED]> wrote: > I just discover some thing, If I ouput the trace to > a serial port the system works fine. However If I output the trace to > the disk I have the same problem as before. [...] I think your device is asking for US_FL_GO_SLOW or equivalent. It keels over on the very first read after the WP sensing: > c12e7ea0 43055373 S Bo:1:004:2 -115 31 = 55534243 0b00 0010 8a28 > 0008 00 > c12e7ea0 43056075 C Bo:1:004:2 0 31 > > c12e7720 43056160 S Bi:1:004:1 -115 4096 < > c12e7720 43162104 C Bi:1:004:1 -84 0 I had major issues with the Kingston in the past because they do not like a halt clear while not halted, but nothing like this. Perhaps it's a new cheaper revision, buggier than before. -- Pete - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Kingston Datatraveler
Hi, Here is the trace. I just discover some thing, If I ouput the trace to a serial port the system works fine. However If I output the trace to the disk I have the same problem as before. This trace is with the problem. c127f3e0 4628504 C Ii:1:001:1 0:128 1 = 04 c127f3e0 4628540 S Ii:1:001:1 -115:128 2 < c127f3e0 4628556 C Ii:1:001:1 0:128 1 = 04 c127f3e0 4628566 S Ii:1:001:1 -115:128 2 < c12e78a0 4628601 S Ci:1:001:0 s a3 00 0002 0004 4 < c12e78a0 4628623 C Ci:1:001:0 0 4 = 01010100 c12e78a0 4628638 S Co:1:001:0 s 23 01 0010 0002 0 c12e78a0 4628650 C Co:1:001:0 0 0 c12e78a0 4628673 S Ci:1:001:0 s a3 00 0002 0004 4 < c12e78a0 4628685 C Ci:1:001:0 0 4 = 0101 c12e78a0 4660477 S Ci:1:001:0 s a3 00 0002 0004 4 < c12e78a0 4660493 C Ci:1:001:0 0 4 = 0101 c12e78a0 4692473 S Ci:1:001:0 s a3 00 0002 0004 4 < c12e78a0 4692488 C Ci:1:001:0 0 4 = 0101 c12e78a0 4724476 S Ci:1:001:0 s a3 00 0002 0004 4 < c12e78a0 4724490 C Ci:1:001:0 0 4 = 0101 c12e78a0 4756477 S Ci:1:001:0 s a3 00 0002 0004 4 < c12e78a0 4756491 C Ci:1:001:0 0 4 = 0101 c12e78a0 4756530 S Co:1:001:0 s 23 03 0004 0002 0 c12e78a0 4756542 C Co:1:001:0 0 0 c12e78a0 4812481 S Ci:1:001:0 s a3 00 0002 0004 4 < c12e78a0 4812508 C Ci:1:001:0 0 4 = 0301 c12e78a0 4868484 S Co:1:001:0 s 23 01 0014 0002 0 c12e78a0 4868495 C Co:1:001:0 0 0 c12e78a0 4868522 S Ci:1:000:0 s 80 06 0100 0040 64 < c12e78a0 4868606 C Ci:1:000:0 0 8 = 12010001 0908 c12e78a0 4872507 S Co:1:001:0 s 23 03 0004 0002 0 c12e78a0 4872519 C Co:1:001:0 0 0 c127f3e0 4876486 C Ii:1:001:1 0:128 1 = 04 c127f3e0 4876498 S Ii:1:001:1 -115:128 2 < c12e78a0 4928487 S Ci:1:001:0 s a3 00 0002 0004 4 < c12e78a0 4928515 C Ci:1:001:0 0 4 = 0301 c12e78a0 4984489 S Co:1:001:0 s 23 01 0014 0002 0 c12e78a0 4984502 C Co:1:001:0 0 0 c12e78a0 4984513 S Co:1:000:0 s 00 05 0002 0 c12e78a0 4987440 C Co:1:000:0 0 0 c12e78a0 5004501 S Ci:1:002:0 s 80 06 0100 0012 18 < c12e78a0 5010438 C Ci:1:002:0 0 18 = 12010001 0908 51044614 0001 0001 c12e78a0 5010465 S Ci:1:002:0 s 80 06 0200 0009 9 < c12e78a0 5015434 C Ci:1:002:0 0 9 = 09021900 010100e0 32 c12e78a0 5015459 S Ci:1:002:0 s 80 06 0200 0019 25 < c12e78a0 5022433 C Ci:1:002:0 0 25 = 09021900 010100e0 32090400 00010900 0705 81030100 ff c12e78a0 5022776 S Co:1:002:0 s 00 09 0001 0 c12e78a0 5024450 C Co:1:002:0 0 0 c12e78a0 5024723 S Ci:1:002:0 s a0 06 2900 000f 15 < c12e78a0 5026461 C Ci:1:002:0 0 9 = 09290409 00326400 00 c12e78a0 5026624 S Ci:1:002:0 s 80 00 0002 2 < c12e78a0 5027461 C Ci:1:002:0 0 2 = 0100 c12e78a0 5027502 S Ci:1:002:0 s a0 00 0004 4 < c12e78a0 5028447 C Ci:1:002:0 0 4 = c12e7920 5028550 S Co:1:002:0 s 23 03 0008 0001 0 c12e7920 5029440 C Co:1:002:0 0 0 c12e7920 5029505 S Co:1:002:0 s 23 03 0008 0002 0 c12e7920 5030436 C Co:1:002:0 0 0 c12e7920 5030465 S Co:1:002:0 s 23 03 0008 0003 0 c12e7920 5031434 C Co:1:002:0 0 0 c12e7920 5031455 S Co:1:002:0 s 23 03 0008 0004 0 c12e7920 5032433 C Co:1:002:0 0 0 c12e78a0 5132499 S Ii:1:002:1 -115:128 1 < c12e7920 5132741 S Ci:1:001:0 s a3 00 0002 0004 4 < c12e7920 5132755 C Ci:1:001:0 0 4 = 0301 c12e7920 5132777 S Ci:1:002:0 s a3 00 0001 0004 4 < c12e7920 5134435 C Ci:1:002:0 0 4 = 0001 c12e7920 5134482 S Ci:1:002:0 s a3 00 0002 0004 4 < c12e7920 5135420 C Ci:1:002:0 0 4 = 0001 c12e7920 5135451 S Ci:1:002:0 s a3 00 0003 0004 4 < c12e7920 5136418 C Ci:1:002:0 0 4 = 0001 c12e7920 5136440 S Ci:1:002:0 s a3 00 0004 0004 4 < c12e7920 5137417 C Ci:1:002:0 0 4 = 0001 c12e78a0 8627828 C Ii:1:002:1 0:128 1 = 02 c12e78a0 8627842 S Ii:1:002:1 -115:128 1 < c12e7920 8627882 S Ci:1:002:0 s a3 00 0001 0004 4 < c12e7920 8629834 C Ci:1:002:0 0 4 = 01030100 c12e7920 8629860 S Co:1:002:0 s 23 01 0010 0001 0 c12e7920 8630832 C Co:1:002:0 0 0 c12e7920 8630869 S Ci:1:002:0 s a3 00 0001 0004 4 < c12e7920 8631834 C Ci:1:002:0 0 4 = 0103 c12e7920 8660701 S Ci:1:002:0 s a3 00 0001 0004 4 < c12e7920 8661827 C Ci:1:002:0 0 4 = 0103 c12e7920 8692701 S Ci:1:002:0 s a3 00 0001 0004 4 < c12e7920 8693822 C Ci:1:002:0 0 4 = 0103 c12e7920 8724703 S Ci:1:002:0 s a3 00 0001 0004 4 < c12e7920 8725818 C Ci:1:002:0 0 4 = 0103 c12e7920 8756705 S Ci:1:002:0 s a3 00 0001 0004 4 < c12e7920 8757811 C Ci:1:002:0 0 4 = 0103 c12e7920 8757858 S Co:1:002:0 s 23 03 0004 0001 0 c12e7920 8758811 C Co:1:002:0 0 0 c12e7920 8772706 S Ci:1:002:0 s a3 00 0001 0004 4 < c12e7920 8773811 C Ci:1:002:0 0 4 = 03031000 c12e7920 8828709 S Co:1:002:0 s 23 01 0014 0001 0 c12e7920 8829800 C Co:1:002:0 0 0 c12e7920 8829838 S Ci:1:000:0 s 80 06 0100 0040 64 < c12e7920 8836796 C Ci:1:000:0 0 18 = 12011001 0008 3c410032 10290102 0001 c12e7920 8836821 S Co:1:002:0 s 23 03 0004 0001 0 c12e7920 8837796 C Co:1:002:0 0 0 c12e7920 8852711 S Ci:1:002:0 s a3 00 0001 0
Re: Kingston Datatraveler
Can you provide a usbmon trace? Start the trace before plugging in the hub; that way it will show what happens when the hub is attached, when the mouse is plugged into the hub, and when the flash drive is plugged into the hub. Alan Stern - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Kingston Datatraveler
Hi, Yes, and I get the same result. On Dec 19, 2007 3:42 PM, Alan Stern <[EMAIL PROTECTED]> wrote: > Please don't top-post. > > > On Wed, 19 Dec 2007, Brian Murphy wrote: > > > Hi, > > > > Tried that and had the same result. I also tried different cables with > > the same result. I don't believe it is a cabling issue as I have > > several of these broads (Evalue Tehcnoligies ECM-3610) and it is > > reproducible regardless of what the cabling setup is. This boards has > > a VIA VT82C686B South bridge 352BGA. I have also tried several > > kernels all the way up to 2.6.23.9. > > > > On Dec 19, 2007 12:15 AM, Pete Zaitcev <[EMAIL PROTECTED]> wrote: > > > On Tue, 18 Dec 2007 16:27:28 +, "Brian Murphy" <[EMAIL PROTECTED]> > > > wrote: > > > > > > > sda:<6>usb 1-2: reset full speed USB device using uhci_hcd and address > > > > 8 > > > > usb 1-2: device descriptor read/64, error -84 > > > > > > Try to insert a self-powered hub. > > > > > > -- Pete > > Have you tried plugging both the flash drive and the HID device into > the external hub, with no other devices attached directly to the > computer? > > Alan Stern > > - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Kingston Datatraveler
Please don't top-post. On Wed, 19 Dec 2007, Brian Murphy wrote: > Hi, > > Tried that and had the same result. I also tried different cables with > the same result. I don't believe it is a cabling issue as I have > several of these broads (Evalue Tehcnoligies ECM-3610) and it is > reproducible regardless of what the cabling setup is. This boards has > a VIA VT82C686B South bridge 352BGA. I have also tried several > kernels all the way up to 2.6.23.9. > > On Dec 19, 2007 12:15 AM, Pete Zaitcev <[EMAIL PROTECTED]> wrote: > > On Tue, 18 Dec 2007 16:27:28 +, "Brian Murphy" <[EMAIL PROTECTED]> > > wrote: > > > > > sda:<6>usb 1-2: reset full speed USB device using uhci_hcd and address 8 > > > usb 1-2: device descriptor read/64, error -84 > > > > Try to insert a self-powered hub. > > > > -- Pete Have you tried plugging both the flash drive and the HID device into the external hub, with no other devices attached directly to the computer? Alan Stern - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Kingston Datatraveler
On Wed, 19 Dec 2007 10:03:57 +, "Brian Murphy" <[EMAIL PROTECTED]> wrote: > Hi, > > Tried that and had the same result. I also tried different cables with > the same result. I don't believe it is a cabling issue as I have > several of these broads (Evalue Tehcnoligies ECM-3610) and it is > reproducible regardless of what the cabling setup is. This boards has > a VIA VT82C686B South bridge 352BGA. I have also tried several > kernels all the way up to 2.6.23.9. > > On Dec 19, 2007 12:15 AM, Pete Zaitcev <[EMAIL PROTECTED]> wrote: >> On Tue, 18 Dec 2007 16:27:28 +, "Brian Murphy" > <[EMAIL PROTECTED]> wrote: >> >> > sda:<6>usb 1-2: reset full speed USB device using uhci_hcd and what about modprobe -r uhci_hcd and using ehci_hcd instead? Does it help ? -- Best Regards, Felipe Balbi http://felipebalbi.com [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Kingston Datatraveler
Hi, Tried that and had the same result. I also tried different cables with the same result. I don't believe it is a cabling issue as I have several of these broads (Evalue Tehcnoligies ECM-3610) and it is reproducible regardless of what the cabling setup is. This boards has a VIA VT82C686B South bridge 352BGA. I have also tried several kernels all the way up to 2.6.23.9. On Dec 19, 2007 12:15 AM, Pete Zaitcev <[EMAIL PROTECTED]> wrote: > On Tue, 18 Dec 2007 16:27:28 +, "Brian Murphy" <[EMAIL PROTECTED]> wrote: > > > sda:<6>usb 1-2: reset full speed USB device using uhci_hcd and address 8 > > usb 1-2: device descriptor read/64, error -84 > > Try to insert a self-powered hub. > > -- Pete > - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Kingston Datatraveler
On Tue, 18 Dec 2007 16:27:28 +, "Brian Murphy" <[EMAIL PROTECTED]> wrote: > sda:<6>usb 1-2: reset full speed USB device using uhci_hcd and address 8 > usb 1-2: device descriptor read/64, error -84 Try to insert a self-powered hub. -- Pete - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Kingston Datatraveler
Hi, I am having some problems with Kingston Datatravler USB flash drive. The key works fine when there is no mouse or other HID device is connected to the system however once you plug the mouse in and reinsert the USB key I get the following. This is a old board and is using the UHCI host controller. I have tried 3 of these keys so far and none of them work. usb 1-2: new full speed USB device using uhci_hcd and address 8 usb 1-2: configuration #1 chosen from 1 choice scsi1 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 8 usb-storage: waiting for device to settle before scanning Vendor: Kingston Model: DataTraveler 2.0 Rev: 1.00 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 3987456 512-byte hdwr sectors (2042 MB) sda: Write Protect is off sda: Mode Sense: 23 00 00 00 sda: assuming drive cache: write through SCSI device sda: 3987456 512-byte hdwr sectors (2042 MB) sda: Write Protect is off sda: Mode Sense: 23 00 00 00 sda: assuming drive cache: write through sda:<6>usb 1-2: reset full speed USB device using uhci_hcd and address 8 usb 1-2: device descriptor read/64, error -84 usb 1-2: device descriptor read/64, error -84 usb 1-2: reset full speed USB device using uhci_hcd and address 8 usb 1-2: device descriptor read/64, error -32 usb 1-2: device descriptor read/64, error -32 usb 1-2: reset full speed USB device using uhci_hcd and address 8 usb 1-2: device not accepting address 8, error -32 usb 1-2: reset full speed USB device using uhci_hcd and address 8 usb 1-2: device not accepting address 8, error -32 usb 1-2: USB disconnect, address 8 sd 1:0:0:0: SCSI error: return code = 0x0001 end_request: I/O error, dev sda, sector 0 Buffer I/O error on device sda, logical block 0 sd 1:0:0:0: SCSI error: return code = 0x0001 end_request: I/O error, dev sda, sector 0 Buffer I/O error on device sda, logical block 0 unable to read partition table sd 1:0:0:0: Attached scsi removable disk sda sd 1:0:0:0: Attached scsi generic sg0 type 0 usb-storage: device scan complete usb 1-2: new full speed USB device using uhci_hcd and address 9 usb 1-2: device descriptor read/64, error -32 usb 1-2: device descriptor read/64, error -32 usb 1-2: new full speed USB device using uhci_hcd and address 10 usb 1-2: device descriptor read/64, error -32 usb 1-2: device descriptor read/64, error -32 usb 1-2: new full speed USB device using uhci_hcd and address 11 usb 1-2: device not accepting address 11, error -32 usb 1-2: new full speed USB device using uhci_hcd and address 12 usb 1-2: device not accepting address 12, error -32 Regards, Brian J. - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
