Date: Mon, 23 Oct 2006 15:05:00 -0400
From: David Hollis <dhollis@davehollis.com>
Subject: Re: 2.6.19-rc2-mm2: D-Link DUB-E100 Rev. B broken
In-reply-to: <200610232041.48998.bero@arklinux.org>
To: Bernhard Rosenkraenzer <bero@arklinux.org>
Cc: linux-kernel@vger.kernel.org
Message-id: <1161630300.4824.7.camel@dhollis-lnx.sunera.com>
MIME-version: 1.0
Content-type: text/plain
Content-transfer-encoding: 7bit
References: <200610232041.48998.bero@arklinux.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1457
Lines: 32

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>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/