From: Jan Kiszka <jan.kiszka@web.de>
To: "David S. Ahern" <daahern@cisco.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] ehci: fix infinite loop with usb netdevice
Date: Mon, 19 Apr 2010 23:26:04 +0200 [thread overview]
Message-ID: <4BCCCA6C.6020808@web.de> (raw)
In-Reply-To: <4BC7D75D.9020302@cisco.com>
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
David S. Ahern wrote:
> Hi Jan:
>
> The attached addresses the spinning with the usb net device. Now I can
> enable the device and ethtool shows a link:
>
> # ifconfig usb0 up
> # ethtool usb0
> Settings for usb0:
> Current message level: 0x00000007 (7)
> Link detected: yes
>
> Though dhclient still can't get an address. After a bit of
> instrumentation it appears that packets are lost in the receive the path
> somewhere:
>
> usb0 Link encap:Ethernet HWaddr 42:5F:CA:51:54:77
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:5513 (5.3 KiB)
>
> I looked at an x3650M2 with an IMM. It has a usb-based ethernet device.
> I compared the output of lsusb -v from the IMM with the qemu usb net
> device and nothing jumps out -- other than the fact that the IMM's
> network device shows up on a uhci bus.
>
Thanks merged (a git-formatted patch would have been even better :) ).
Yeah, the behavior is as before here as well. So there was or was not
USB traffic between device and controller that points to incoming
frames? Guess we need to debug through the device if there was.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
prev parent reply other threads:[~2010-04-19 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 3:19 [Qemu-devel] [PATCH] ehci: fix infinite loop with usb netdevice David S. Ahern
2010-04-19 21:26 ` Jan Kiszka [this message]
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=4BCCCA6C.6020808@web.de \
--to=jan.kiszka@web.de \
--cc=daahern@cisco.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.