On Saturday 07 July 2007, Gene Heskett wrote: >On Friday 06 July 2007, Alan Stern wrote: >>On Fri, 6 Jul 2007, Gene Heskett wrote: >>> So the next thing to do is find a wall wart that will add some power >>> either directly to it, or to the hub its plugged into? As I'm in the >>> middle of West Virginia, this should be fun as all we have are Staples, >>> Ciorcuit City & Radio Shack. I could probably build one with an lm317 >>> quicker than I could find on actually made for it. Sigh... >> >>Actually the next thing to do is what I suggested before: Run a kernel >>with CONFIG_USB_STORAGE_DEBUG turned on and post the dmesg log. >> >>Alan Stern > >I did that once already Alan. Since that boot, usb_storage has been quite >voluable, about a 64 meg flash that is plugged in but at the time virtually >nothing about the maxtor. And now the ring buffer is so full of the scans >for the stick I'd never be able to separate it out. So let me do the cycle >again.
Humm. I thought I'd be smart and plugged the extra pigtail of the cable in first (power the power), but that first reset the box, then powered it down! But left the hd access led on for about 20 seconds? So I'm rebooted for the 2nd time, which BTW took 2, 5 second presses of the power switch to get it to power up again. The first one just completed the power off cycle I guess. Anyway, here goes plugging in the regular cable. By the time I do that, and get back to the keyboard,(I have to crawl under the next desk to plug it into a root port & its too crowded for these old bones) the dmesg ring buffer has overflowed with several dozens of this verse: usb-storage: *** thread awakened. usb-storage: Command TEST_UNIT_READY (6 bytes) usb-storage: 00 00 00 00 00 00 usb-storage: Bulk Command S 0x43425355 T 0xbb L 0 F 0 Trg 0 LUN 3 CL 6 usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes usb-storage: Status code 0; transferred 31/31 usb-storage: -- transfer complete usb-storage: Bulk command transfer result=0 usb-storage: Attempting to get CSW... usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes usb-storage: Status code 0; transferred 13/13 usb-storage: -- transfer complete usb-storage: Bulk status result = 0 usb-storage: Bulk Status S 0x53425355 T 0xbb R 0 Stat 0x1 usb-storage: -- transport indicates command failure usb-storage: Issuing auto-REQUEST_SENSE usb-storage: Bulk Command S 0x43425355 T 0xbc L 18 F 128 Trg 0 LUN 3 CL 6 usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes usb-storage: Status code 0; transferred 31/31 usb-storage: -- transfer complete usb-storage: Bulk command transfer result=0 usb-storage: usb_stor_bulk_transfer_buf: xfer 18 bytes usb-storage: Status code 0; transferred 18/18 usb-storage: -- transfer complete usb-storage: Bulk data transfer result 0x0 usb-storage: Attempting to get CSW... usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes usb-storage: Status code 0; transferred 13/13 usb-storage: -- transfer complete usb-storage: Bulk status result = 0 usb-storage: Bulk Status S 0x53425355 T 0xbc R 0 Stat 0x0 usb-storage: -- Result from auto-sense is 0 usb-storage: -- code: 0x70, key: 0x2, ASC: 0x3a, ASCQ: 0x0 usb-storage: (Unknown Key): (unknown ASC/ASCQ) usb-storage: scsi cmd done, result=0x2 usb-storage: *** thread sleeping. According to: dmesg|grep 'usb-storage: -- code:'|wc -l there are 73 of them and its not incrementing the count, so I'd assume its either actually quit, or that's the size limit of the ring buffer. According to htop, usb-storage is occasionally waking up, running itself up near the top of the list but not showing any actual cpu usage (0.0) at say 300 second intervals. The messages file on the other hand, says this: Jul 7 01:21:45 coyote kernel: usb 3-2: new high speed USB device using ehci_hcd and address 12 Jul 7 01:21:45 coyote kernel: usb 3-2: Product: Maxtor OneTouch III Jul 7 01:21:45 coyote kernel: usb 3-2: Manufacturer: Maxtor Jul 7 01:21:45 coyote kernel: usb 3-2: SerialNumber: RA01ZFQC Jul 7 01:21:45 coyote kernel: usb 3-2: configuration #1 chosen from 1 choice Jul 7 01:21:45 coyote kernel: SCSI subsystem initialized Jul 7 01:21:45 coyote kernel: Initializing USB Mass Storage driver... Jul 7 01:21:45 coyote kernel: scsi0 : SCSI emulation for USB Mass Storage devices Jul 7 01:21:45 coyote kernel: scsi1 : SCSI emulation for USB Mass Storage devices Jul 7 01:21:45 coyote kernel: usbcore: registered new interface driver usb-storage Jul 7 01:21:45 coyote kernel: USB Mass Storage support registered. Jul 7 01:21:50 coyote kernel: scsi 0:0:0:0: Direct-Access Generic STORAGE DEVICE 9317 PQ: 0 ANSI: 0 Jul 7 01:21:50 coyote kernel: scsi 0:0:0:1: Direct-Access Generic STORAGE DEVICE 9317 PQ: 0 ANSI: 0 Jul 7 01:21:50 coyote kernel: scsi 0:0:0:2: Direct-Access Generic STORAGE DEVICE 9317 PQ: 0 ANSI: 0 Jul 7 01:21:50 coyote kernel: scsi 0:0:0:3: Direct-Access Generic STORAGE DEVICE 9317 PQ: 0 ANSI: 0 Jul 7 01:21:50 coyote kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk Jul 7 01:21:50 coyote kernel: sd 0:0:0:1: [sdb] Attached SCSI removable disk Jul 7 01:21:50 coyote kernel: sd 0:0:0:2: [sdc] Attached SCSI removable disk Jul 7 01:21:50 coyote kernel: sd 0:0:0:3: [sdd] Attached SCSI removable disk Jul 7 01:21:51 coyote kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 Jul 7 01:21:51 coyote kernel: sd 0:0:0:1: Attached scsi generic sg1 type 0 Jul 7 01:21:51 coyote kernel: sd 0:0:0:2: Attached scsi generic sg2 type 0 Jul 7 01:21:51 coyote kernel: sd 0:0:0:3: Attached scsi generic sg3 type 0 Jul 7 01:21:56 coyote kernel: usb 3-2: reset high speed USB device using ehci_hcd and address 12 Jul 7 01:22:01 coyote kernel: usb 3-2: device descriptor read/64, error -71 Jul 7 01:22:11 coyote kernel: usb 3-2: reset high speed USB device using ehci_hcd and address 12 Jul 7 01:22:38 coyote last message repeated 3 times Jul 7 01:22:38 coyote kernel: scsi 1:0:0:0: scsi: Device offlined - not ready after error recovery And the drive has not spun up. It is plugged into a root port. And that is the best I can do unless someone knows howto do a running capture of the dmesg ring buffer so that I can show what actually occurs at the instant of the plugin. ISTR its set for 128k in the build. That could be expanded as I have a gig of ram, so even 10 megs could be done I'd think unless there is a pointer size limit to the ring buffer. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If wishes were horses, then beggars would be thieves. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
