2.6.27.2 USB reset/IO Error problem when high load on ICH9 USB
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 12 lines · Kasper Sandberg
Hello..
I had to write an image to some usb flash drives, more specifically, 4GB kingston datatraveler sticks, and i figured, instead of doing just 1 at a time, i may aswell do 4, so i plugged in 4, and started 4 dd's of the images, to sdc, sdd, sde, sdf. However, i got usb disconnects and IO error messages from the kernel, these are at end of message. I had previously done ~5 writes of images to 5 other flash disks with no problem, but when i tried the next batch, those 4, it gave these errors. I killed the dd's, pulled them all out, and put in 1 at a time, and it worked perfectly.
Quoted 2 lines
unfortunately the first kernel messages have been flooded away. If you need .config and/or the boot kernel messages, i can reboot and get it.
It seems suspicious that only the sde one (with address 6) seems to be having problems. Are you sure that drive wasn't faulty or somehow not plugged in properly?
Quoted 13 lines · Robert Hancock
Quoted 12 lines · Kasper Sandberg
Hello..
I had to write an image to some usb flash drives, more specifically, 4GB kingston datatraveler sticks, and i figured, instead of doing just 1 at a time, i may aswell do 4, so i plugged in 4, and started 4 dd's of the images, to sdc, sdd, sde, sdf. However, i got usb disconnects and IO error messages from the kernel, these are at end of message. I had previously done ~5 writes of images to 5 other flash disks with no problem, but when i tried the next batch, those 4, it gave these errors. I killed the dd's, pulled them all out, and put in 1 at a time, and it worked perfectly.
Quoted 6 lines
Quoted 2 lines
unfortunately the first kernel messages have been flooded away. If you need .config and/or the boot kernel messages, i can reboot and get it.
It seems suspicious that only the sde one (with address 6) seems to be having problems. Are you sure that drive wasn't faulty or somehow not plugged in properly?
I am absolutely positive it was plugged in properly, and i am also sure the usb port isnt broken, i have tested all of them, though, this is first time i have had so many in use concurrently, maybe its a power issue? (which would be weird though, as flash devices shouldnt be using so much power)
as for faulty, i did use that exact drive again, when i reverted back to doing one by one.
Quoted 5 lines
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 5 lines
I am absolutely positive it was plugged in properly, and i am also sure the usb port isnt broken, i have tested all of them, though, this is first time i have had so many in use concurrently, maybe its a power issue? (which would be weird though, as flash devices shouldnt be using so much power)
FWIW I've found that on my ICH9 based PC, whenever I copy a fairly large (>50MB) amount of data onto a USB flash drive, my USB keyboard plays up for up to half an hour after the transfer, generating random keypresses all over the place.
The first time it happened I thought I had some sort of spyware/virus on my PC, but it reliably happens whenever I copy lots of data onto the flash. After about half an hour or so it settles down and everything goes back to normal.
I thought it was a problem with the keyboard driver, as it doesn't affect the whole keyboard (the base keyboard is handled by the Linux USB keyboard driver and that works fine, but the userspace program "g15daemon" handles the extra non-standard keys, and these are the ones that randomly get pressed after a large data transfer.)
Last time this happened I checked the data coming in over evdev, and the extra keypresses were generated entirely in software - no evdev data was coming in unless I was physically pressing the key. But still Linux was receiving spurious keypress events. (Which is why I suspected the userspace program.)
Perhaps it's not g15daemon (nobody else has reported this behaviour), but something USB related instead?
This is with 2.6.23.9, though.
Cheers,
Adam.