USB2 crashes big time

xushi · 08-19-2005, 07:25 AM

I've been getting this for quite a while now... It's really starting to annoy me.

My USB2 keeps occasionaly dying on me. This occurs alot when i'm reading from or writing to DVD9 through my external dvd writer.

If writing, all goes well, suddenly speed drops to 0, and it just stays there.. you can't cancel k3b, you can't close it, you cant kill the proccess.. nothing

If reading from (like playing a video from it), ithe video freezes, and same thing.. you cant close mplayer, kill kfmclient or mplayer.

Some odd output is displayed in dmesg. This is the output when reading fails. I think its the same error as writing too.

Code:

usb 1-2: USB disconnect, address 3
usb 1-2.2: USB disconnect, address 4
drivers/usb/class/usblp.c: usblp0: removed
usb 1-2.4: USB disconnect, address 5
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19
usb 1-2.4: usb_sg_cancel, unlink --> -19

I cant bring up USB2 again at all after this... no matter how many reboots i do, or switching off the laptop and back on. The only solution is to switch around whatever i have in the ports, so that something else which is working is on the crashed usb port (and vice versa), boot the machine, then shut it down, switch back the ports, then boot again....

And this has happened in more than 1 distro. My chipsets are VIA based.

Any ideas? its really starting to annoy me as most of my data now is on DVD9 and i cant afford such crashes.

edit: when i say 'i cant bring up usb2 again', i mean it seems completly dead. Plugging in the device again reports nothing in dmesg at all. Also, the reason behind the reboot i think has to do with it re-identifying with the usb ports. My theory is, if you keep what's in there and reboots, it will insist that nothing works. If you mix them around, it will re-identify and reactivate everything bring it all up again, where afterwards you can put the devices back to their original ports...

also, when i'm rebooting the first time, my / partition refuses to unmount ... it tries and tries, then it says can't umount it, press CTRL+D to continue (a forced reboot).

Thanks.

keefaz · 08-19-2005, 07:53 AM

Shared IRQ problem ? What does cat /proc/interrupts say ?
Or maybe the USB chipset is not able to handle big transfer
(like 4GB data burned to DVD)

xushi · 08-19-2005, 08:31 AM

Code:

l # cat /proc/interrupts
           CPU0       
  0:    3534960    IO-APIC-edge  timer
  1:       4242    IO-APIC-edge  i8042
  8:          0    IO-APIC-edge  rtc
 10:          9   IO-APIC-level  acpi
 12:       9406    IO-APIC-edge  i8042
 14:     130153    IO-APIC-edge  ide0
 15:         21    IO-APIC-edge  ide1
169:     933587   IO-APIC-level  eth0
177:         51   IO-APIC-level  VIA8233
185:      98869   IO-APIC-level  ehci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4
NMI:       3102 
LOC:    3534441 
ERR:          0
MIS:          0

Quote:

Or maybe the USB chipset is not able to handle big transfer
(like 4GB data burned to DVD)

Doubt it, because this is happening with files / avi files as small as 150 megs on the media.

keefaz · 08-19-2005, 12:46 PM

Your IRQs seem fine

Did you enable USB support as built-in or as module ?

xushi · 08-19-2005, 12:54 PM

From what i can see, its all built in.

Code:

 linux # cat .config | grep USB
# USB devices
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set
# USB support
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
# Miscellaneous USB options
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set
# USB Host Controller Drivers
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# USB Device Class drivers
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=y
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' may also be needed; 
e USB_STORAGE Help for more information
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# USB Input Devices
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
CONFIG_USB_HIDDEV=y
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_MTOUCH is not set
# CONFIG_USB_EGALAX is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set
# USB Imaging devices
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# USB Multimedia devices
# CONFIG_USB_DABUSB is not set
# Video4Linux support is needed for USB Multimedia device support
# USB Network Adapters
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
CONFIG_USB_MON=y
# USB port drivers
# USB Serial Converter support
# CONFIG_USB_SERIAL is not set
# USB Miscellaneous drivers
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGETKIT is not set
# CONFIG_USB_PHIDGETSERVO is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_TEST is not set
# USB ATM/DSL drivers
# USB Gadget Support
# CONFIG_USB_GADGET is not set

keefaz · 08-19-2005, 01:01 PM

I would try to enable usb-storage, ohci-hcd, uhci-hcd and ehci-hcd as
module to see if that change something, and you will have the possibility to
rmmod them to reset USB ports

xushi · 08-19-2005, 01:23 PM

Good idea, ill give it a try and test it over the next day or two.

Thanks.

Also.. is there any 'debug' option i can/should enable to get more information about the crashes ?

keefaz · 08-19-2005, 01:58 PM

There is the USB verbose debug messages option in kernel config, but I never used it

Ilgar · 08-21-2005, 02:23 AM

Quote:

I cant bring up USB2 again at all after this... no matter how many reboots i do, or switching off the laptop and back on. The only solution is to switch around whatever i have in the ports, so that something else which is working is on the crashed usb port (and vice versa), boot the machine, then shut it down, switch back the ports, then boot again....

And this has happened in more than 1 distro. My chipsets are VIA based.

First of all, I'm nowhere near being an expert on this. But wouldn't a software-related issue be gone after rebooting, or an IRQ type problem come up at every single boot? What you describe above suggests to me that there's something up with the hardware. Reminds me of my MSN DSL modem which goes crazy once in a while and is fixed by hard reboot.

xushi · 08-21-2005, 03:10 AM

Quote:

Originally posted by Ilgar
wouldn't a software-related issue be gone after rebooting, or an IRQ type problem come up at every single boot?

I thought about that, to me, its true, unless the software was more down to earth rather than an application (like OS related / BIOS maby ).

Quote:

What you describe above suggests to me that there's something up with the hardware.

If its hardware related, then i'd see it happening all the time, regardless if i burn or not, or if i'm burning DVD9 or DVD5. But this only happens when i burn DVD9.. I haven't seen it crash with normal DVD5s .. Nor have i seen it crash while printing, or scanning.

I've seen this happen once before on an Asus a7n8x delux machine i had, where if the machine crashed, my usb port with the mouse would die on me. And no number of reboots or power off/on would bring it back up. The only way back then for me to fix the problem was to (sigh...) stick in a WinXP cd, let it go through the initial setup to detect the USB ports, and to switch them on for me, then reboot back to my OS

Ilgar · 08-21-2005, 02:45 PM

Quote:

If its hardware related, then i'd see it happening all the time, regardless if i burn or not, or if i'm burning DVD9 or DVD5. But this only happens when i burn DVD9.. I haven't seen it crash with normal DVD5s .. Nor have i seen it crash while printing, or scanning.

Something in the burning process could be triggering the error. As you say, it could be a software problem at the BIOS level but still it would be weird. The device is recognized at normal reboot. Then the problem happens and you reboot with the same hardware, same BIOS, same OS, and it doesn't work. Only after making some "hard" changes (unplug/switch/plug) it works. The second problem you describe is also of similar kind. In that case (the Asus one) were you keeping the DVD plugged while Win detected the USB ports? Obviously something needs to be "reset", I'm just wondering whether it's the DVD device or the USB controller.

Anyway, as I said I'm no expert, mine are just theories. As a last suggestion, you may want to check your DVD vendor's site for firmware updates. It may help.