usbnet frames mangled
Hi,
using an ipaq running 2.4.17-rmk5-hh5 as "usb client" (usbnet connection), I got lots frames mangled (about 95%). For example, a typical ping request:
0000 48 3f 05 1f 43 9a c6 33 f5 8f d9 b3 08 00 45 00 H?..C..3 ......E. 0010 00 54 00 00 40 00 40 01 36 a5 01 01 01 01 01 01 .T..@.@. 6....... 0020 01 02 08 00 86 99 df 00 05 00 b5 bd 7f 3c 65 68 ........ .....<eh 0030 08 00 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15 ........ ........ 0040 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 ........ .. !"#$% 0050 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 &'()*+,- ./012345 0060 36 37 67
is often received as:
0000 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 ........ .. !"#$% 0010 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 &'()*+,- ./012345 0020 36 37 67
which of course doesn't mean anything. I saw this behavior since I upgraded my desktop from 2.4.18-ac2 to 2.4.19-pre1-ac1
Quoted 3 lines · Xavier Bestel
which of course doesn't mean anything. I saw this behavior since I upgraded my desktop from 2.4.18-ac2 to 2.4.19-pre1-ac1
So you kept your USB client at the same version, but your host changed versions? And 2.4.18-ac2 works, but 2.4.19-pre1-ac1 doesn't?
Can you see if 2.4.19-pre2 works or not for you?
And which USB host controller driver are you using?
thanks,
greg k-h
Quoted 7 lines · Greg KH
Quoted 3 lines · Xavier Bestel
which of course doesn't mean anything. I saw this behavior since I upgraded my desktop from 2.4.18-ac2 to 2.4.19-pre1-ac1
So you kept your USB client at the same version, but your host changed versions? And 2.4.18-ac2 works, but 2.4.19-pre1-ac1 doesn't?
That's it.
Quoted 1 line
Can you see if 2.4.19-pre2 works or not for you?
It works pretty well.
Quoted 1 line
And which USB host controller driver are you using?
uhci (not JE. I've compiled both as modules, but uhci seems to be used).
Xav
Quoted 6 lines · Xavier Bestel
Quoted 5 lines · Greg KH
Quoted 3 lines · Xavier Bestel
which of course doesn't mean anything. I saw this behavior since I upgraded my desktop from 2.4.18-ac2 to 2.4.19-pre1-ac1
Quoted 8 lines
Quoted 2 lines
So you kept your USB client at the same version, but your host changed versions? And 2.4.18-ac2 works, but 2.4.19-pre1-ac1 doesn't?
That's it.
Quoted 1 line
Can you see if 2.4.19-pre2 works or not for you?
It works pretty well.
So you don't have a problem with 2.4.19-pre2? Great :)
thanks,
greg k-h
Quoted 10 lines · Greg KH
Quoted 9 lines · Xavier Bestel
Quoted 7 lines · Greg KH
Quoted 3 lines · Xavier Bestel
which of course doesn't mean anything. I saw this behavior since I upgraded my desktop from 2.4.18-ac2 to 2.4.19-pre1-ac1
So you kept your USB client at the same version, but your host changed versions? And 2.4.18-ac2 works, but 2.4.19-pre1-ac1 doesn't?
Quoted 7 lines
Quoted 5 lines
That's it.
Quoted 1 line
Can you see if 2.4.19-pre2 works or not for you?
It works pretty well.
So you don't have a problem with 2.4.19-pre2? Great :)
Err ... I just understood today the freeze problems I had are due to USB, but didn't manage to produce a valid testcase yet. Apparently, if I plug back my ipaq then modprobe usbnet, the desktop hangs. If I modprobe first, it works well.
Xav