I have been trying to narrow down a problem I have been having for some time 
which relates to USB.

I have a Compaq M700 notebook with a single USB port.
My normal configuration then has 
        a banksia 4 port USB hub with external power
Port 1) Epson 610U scanner
Port 2) ISD 200 USB to ATA (IDE) adaptor with 60 Gig HDD
Port 3) Canon S400SP USB printer
Port 4) ISD 200 USB to ATA (IDE) adaptor with LG GCE-8160B CD-RW (only rarely 
turned on but always plugged in.

My problem is basically that after a certain amount of usage (time varies) 
access the HDD ceases and in order to regain the ability the read and write 
to the drive I have to reboot as I cannot unload the usb-storage module from 
the kernel. The [usb-storage-0] process shows up as defunct in ps but also 
cannot be killed.

I had my computer running over the weekend to try and narrow down the area of 
the fault. I ran the computer with vmware (program I suspected may have been 
causing a problem and the ISD-200 with the HDD plugged directly into the back 
of the notebook. It ran for more than a day without incident. As the problem 
normally shows itself well within a day I took this to mean that there was no 
problem here (also there were not the disconnect/reconnect messages in the 
log files something that always preeceeds the lock up.)

I also run just the sanner plugged directly into the computer USB without any 
problem for about 1 day and once again no disconnect/reconnect messages in 
the log files.

Then I unplugged the scanner and plugged in the hub. all was OK.

The ker-info.crash file shows the log of what happened once I started to plug 
in my additional pieces of equipment again. There is a spate of 
disconnect/reconnect messages and then all seems to be OK for a while, some 
more disconnect/reconnects and then big ugly problems.

I know it's a long mail but I'm realy having problems tracking this down (and 
it's my first time at trying to find out what is going wrong)

I have a couple of logs attached about 7K in total. The usb.debug.crash is a 
dump from syslog will all info upto debug level included. I have also 
compiled in usb-storage debug so it is fairly verbose. 

usb.kern-info.crash has the kernel info level messages and covers a much 
longer period hopefully showing how my machine got into the sate that it did.

Any help on this would be much appreciated. I either have a hardware problem 
with my hub or there is a bug in USB (hub.c, scanner.c would be my guess). 
Unfortunately I cannot program so I need help. I can test and capture info if 
I know how to do it.



Many thanks,

David Price

Attachment: usb.kern-info.crash.gz
Description: GNU Zip compressed data

Attachment: usb.debug.crash.gz
Description: GNU Zip compressed data

Reply via email to