From: David Hollis <dhollis@davehollis.com>
To: Bernhard Rosenkraenzer <bero@arklinux.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc2-mm2: D-Link DUB-E100 Rev. B broken
Date: Mon, 23 Oct 2006 15:05:00 -0400 [thread overview]
Message-ID: <1161630300.4824.7.camel@dhollis-lnx.sunera.com> (raw)
In-Reply-To: <200610232041.48998.bero@arklinux.org>
On Mon, 2006-10-23 at 20:41 +0200, Bernhard Rosenkraenzer wrote:
> Hi,
> D-Link DUB-E100 Rev. B USB Ethernet adapters have worked ok in some recent
> kernels - in rc2-mm2, they're broken again; they're detected correctly and
> the asix module is autoloaded, but after "ifconfig eth0 192.168.0.15 netmask
> 255.255.255.0", the box becomes unresponsive and keeps repeating
>
> eth0: Failed to enable software MII access
> eth0: Failed to enable hardware MII access
> eth0: Failed to enable software MII access
> eth0: Failed to enable hardware MII access
> eth0: Failed to enable software MII access
> eth0: Failed to enable hardware MII access
> eth0: Failed to enable software MII access
> eth0: Failed to enable hardware MII access
> eth0: Failed to enable software MII access
> eth0: Failed to enable hardware MII access
> eth0: Failed to write Medium Mode to 0x0334: ffffff92
Hmm, the only change that you may not have is to wrap the MII calls with
a Mutex, though that isn't likely the culprit here (even though the
message is talking about MII access). Could you enable the DEBUG define
at the top of the driver and see what kind of output you get in dmesg?
--
David Hollis <dhollis@davehollis.com>
next prev parent reply other threads:[~2006-10-23 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 18:41 Bernhard Rosenkraenzer
2006-10-23 19:05 ` David Hollis [this message]
2006-10-23 19:45 ` Bernhard Rosenkraenzer
2006-10-23 19:59 ` Bernhard Rosenkraenzer
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=1161630300.4824.7.camel@dhollis-lnx.sunera.com \
--to=dhollis@davehollis.com \
--cc=bero@arklinux.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®