From: RAJESH DASARI <raajeshdasari@gmail.com>
To: linux-usb@vger.kernel.org
Subject: Reg: USB network interface is down after the reboot
Date: Thu, 26 Dec 2019 15:01:03 +0530 [thread overview]
Message-ID: <CAPXMrf_d_uKZbohYWfO8rVEg7voBhESesU0w8Ng0M=wsw_75FQ@mail.gmail.com> (raw)
Hi,
I have an USB network Interface connected between two devices.
usb0
Device A --------- Device B
Device A side:
ifconfig usb0
usb0 Link encap:Ethernet HWaddr 72:81:17:44:9A:C6
inet addr:169.254.0.18 Bcast:0.0.0.0 Mask:255.255.240.0
inet6 addr: fe80::7081:17ff:fe44:9ac6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:7553 (7.3 KiB)
Device B side:
ifconfig usb0
usb0 Link encap:Ethernet HWaddr DA:A4:50:01:5C:B8
inet addr:169.254.0.17 Bcast:169.254.15.255 Mask:255.255.240.0
inet6 addr: fe80::d8a4:50ff:fe01:5cb8/64 Scope:Link
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:913 errors:200 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:319658 (312.1 KiB)
Ping from device A usb to device B usb interface is working fine.
# ping 169.254.0.17
PING 169.254.0.17 (169.254.0.17) 56(84) bytes of data.
64 bytes from 169.254.0.17: icmp_seq=1 ttl=64 time=0.807 ms
64 bytes from 169.254.0.17: icmp_seq=2 ttl=64 time=0.459 ms
I have restarted the Device B and i could see the below logs on Device
A console.
usb 1-3.3: USB disconnect, device number 5
cdc_ether 1-3.3:2.0 usb0: unregister 'cdc_ether' usb-0000:00:15.0-3.3,
CDC Ethernet Device
usb 1-3.4: USB disconnect, device number 6
usb 1-3: USB disconnect, device number 4
When the Device B was coming up the below logs are seen on the device
A console.
usb 1-3.3: new high-speed USB device number 8 using xhci_hcd
cdc_ether 1-3.3:2.0 usb0: register 'cdc_ether' at
usb-0000:00:15.0-3.3, CDC Ethernet Device, 4e:7b:fc:19:ad:62
Device B side usb0 interface is up and RUNNING after the Device B
reboot but the usb0 interface on the device A shows that interface is
down and it is RUNNING bit
is set not set.
Device B side:
ifconfig usb0
usb0 Link encap:Ethernet HWaddr 76:2D:4D:E7:76:73
inet addr:169.254.0.17 Bcast:169.254.15.255 Mask:255.255.240.0
inet6 addr: fe80::742d:4dff:fee7:7673/64 Scope:Link
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:8 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:648 (648.0 B)
Device A side:
ifconfig usb0
usb0 Link encap:Ethernet HWaddr 72:81:17:44:9A:C6
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Driver used at device A side:
ethtool -i usb0
driver: cdc_ether
version: 22-Aug-2005
firmware-version: CDC Ethernet Device
expansion-rom-version:
bus-info: usb-0000:00:15.0-3.3
kernel version: 4.9.164
Could someone please help, why the usb0 is down on Device A side and
it there is any known issue or is this expected behaviour?
Regards,
Rajesh.
next reply other threads:[~2019-12-26 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 9:31 RAJESH DASARI [this message]
2019-12-30 9:22 ` Reg: USB network interface is down after the reboot RAJESH DASARI
2020-01-13 13:48 ` Oliver Neukum
2020-01-14 5:10 ` RAJESH DASARI
2020-01-14 17:15 ` Oliver Neukum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPXMrf_d_uKZbohYWfO8rVEg7voBhESesU0w8Ng0M=wsw_75FQ@mail.gmail.com' \
--to=raajeshdasari@gmail.com \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).