Most recent kernel where this bug did not occur: 2.6.15
Hardware Environment: USB 1.1 hub
Software Environment: cat/minicom
character transfer between pc and hp4x stopped working with kernel 2.6.16
Steps to reproduce:
plug hp4x device (it is properly recognized), start minicom, type characters in minicom or on hp4x, nothing appears on the other side. With 2.6.15 it works ok.
I enabled debugging in the module, and I'll attach lsusb + dmesg
Note that the USBDEVFS_CONTROL errors in dmesg correspond to the "cannot read device status" error in lsusb
Created attachment 8034 [details]
dmesg of lsusb + minicom try
Created attachment 8035 [details]
*** Bug 6509 has been marked as a duplicate of this bug. ***
I don't see anything wrong with that kernel log, what are you seeing
happening? I see the data go to the device successfully, and that's about it.
Indeed, data seems to go, but the device doesn't get it at all. And in the first part of the log (where it looks like the device is idle), I was actually typing data from the device to the computer (which it apparently never received).
Is this fixed in the latest 2.6.18-rc5 release?
2.6.18-rc5 works fine indeed, thanks!