Bug 6286
Summary: | USBLAN is broken for Motorola Linux phones | ||
---|---|---|---|
Product: | Drivers | Reporter: | Dmitry Nezhevenko (dion) |
Component: | USB | Assignee: | Greg Kroah-Hartman (greg) |
Status: | REJECTED DOCUMENTED | ||
Severity: | normal | CC: | dbrownell |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.16 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 5089 | ||
Attachments: | tweak MTU for BLAN mode |
Description
Dmitry Nezhevenko
2006-03-26 14:30:43 UTC
David, any ideas? The data transfer paths of the "usbnet" driver haven't changed much in ages, and they behave fine with stress tests for other peripherals. Built the USB stack with CONFIG_USB_DEBUG and provide the relevant output. With this phone and this chipset, that would include the /sys/class/usb_host/usb_hostN/async file at two points: (a) right after the interface has been configured, which should show a queue of RX packets; and (b) when it's in this "slow" mode. My first guess would be that the phone itself has problems, since Linux is able to deliver packets faster than some peripheral controller drivers are able to handle them. Hi. Thanks for reply. After plugin device and when udev loaded modules this file is empty. After executing ifup usb0: ed/f57be040 fs dev4 ep2in max 64 00401104 DATA0 td f4cd3000 in 1514 cc=f urb f4beb1a0 (f0140000) td f4cd3040 in 1514 cc=f urb f4beba20 (f0140000) td f4cd3080 in 1514 cc=f urb f4beb820 (f0140000) td f4cd3100 in 1514 cc=f urb f4beb120 (f0140000) I can see followed messages in syslog: Mar 27 14:13:18 debian kernel: usb0: rxqlen 0 --> 4 Mar 27 14:13:28 debian kernel: usb0: no IPv6 routers present Mar 27 14:14:39 debian kernel: ohci_hcd 0000:00:02.1: urb f4beba20 path 2 ep2in 83160000 cc 8 --> status -75 Mar 27 14:14:39 debian kernel: ohci_hcd 0000:00:02.1: urb f4beb820 path 2 ep2in 83160000 cc 8 --> status -75 Mar 27 14:14:39 debian kernel: ohci_hcd 0000:00:02.1: urb f4beb120 path 2 ep2in 83160000 cc 8 --> status -75 Mar 27 14:14:40 debian kernel: ohci_hcd 0000:00:02.1: urb f4beb1a0 path 2 ep2in 83160000 cc 8 --> status -75 Mar 27 14:14:41 debian kernel: ohci_hcd 0000:00:02.1: urb f4beba20 path 2 ep2in 83160000 cc 8 --> status -75 Mar 27 14:14:42 debian kernel: ohci_hcd 0000:00:02.1: urb f4beb820 path 2 ep2in 83160000 cc 8 --> status -75 Mar 27 14:14:46 debian kernel: ohci_hcd 0000:00:02.1: urb f4beb120 path 2 ep2in 83160000 cc 8 --> status -75 Mar 27 14:14:53 debian kernel: ohci_hcd 0000:00:02.1: urb f4beb1a0 path 2 ep2in 83160000 cc 8 --> status -75 As i say in my previous post, phone works well with 2.6.13 kernel and I never see messages like such before. There are one different: In 2.6.16 kernel udev loads 2 modules when i plug phone: cdc_ether and zaurus. But on 2.6.13 kernel there is no zaurus module and phone works with usbnet module. Looks like this is not kernel bug. It's work after changing MTU to 1000: usb0 Link encap:Ethernet HWaddr CE:FE:08:43:E2:5B inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1000 Metric:1 RX packets:4196 errors:0 dropped:0 overruns:0 frame:0 TX packets:4329 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:797403 (778.7 KiB) TX bytes:447712 (437.2 KiB) So i think, that bug can be closed now. Ok, thanks for the report, am closing. Created attachment 8026 [details]
tweak MTU for BLAN mode
See if this improves anything. There were two reports of similar bugs, and on
a closer look I noticed that the BLAN code was not performing some tweaks that
the older code did.
Yes. this patch is useful. After applying and remove MTU=1000 from config file i got MTU=1494 and usblan works fine without any problems. |