Subject: Re: `MDIC write error' on wm0 after resuming from suspend
To: Lubomir Sedlacik <salo@Xtrmntr.org>
From: Steven M. Bellovin <smb@cs.columbia.edu>
List: current-users
Date: 01/02/2006 13:33:24
In message <20060102180352.GE3161@Xtrmntr.org>, Lubomir Sedlacik writes:
>
>--r7U+bLA8boMOj+mD
>Content-Type: text/plain; charset=us-ascii
>Content-Disposition: inline
>Content-Transfer-Encoding: quoted-printable
>
>On Mon, Jan 02, 2006 at 06:23:50PM +0100, Jukka Salmi wrote:
>> on an IBM ThinkPad X40 running NetBSD/i386 3.99.15 (GENERIC_LAPTOP +
>> APM kernel) the wm(4) interface works fine until the system resumes
>> from suspend. After doing so, ifconfig reports `status: no carrier',
>> the following is printed to the console:
>>=20
>> wm0: reset failed to complete
>> wm0: MDIC write error: phy 1 reg 4
>> wm0: MDIC write error: phy 1 reg 9
>> wm0: MDIC write error: phy 1 reg 0
>> [...]
>>=20
>> Has anybody seen this problem before?
>
>i am repeatedly getting:
>
> wm0: MDIC write timed out: phy 1 reg 31
> wm0: MDIC write timed out: phy 1 reg 0
>
>as soon as i bring up the interface while no wire is plugged in.
>
>also see kern/31041
>
If dhclient is running with no cable, I get lots of
wm0: device timeout (txfree 4095 txsfree 63 txnext 45)
but they've always seemed harmless. I have no problem with suspend/
resume on a Thinkpad T42 running 3.99.15 from 26 December.
--Steven M. Bellovin, http://www.cs.columbia.edu/~smb