On Mon, Apr 30, 2007 at 08:55:22PM -0700, Andrew Morton wrote:
On Mon, 30 Apr 2007 22:58:47 +0200 Rafał Bilski [off-list ref] wrote:
quoted
quoted
ezri user.info kernel: eth0: DSPCFG accepted after 0 usec.
ezri user.notice kernel: eth0: Wake-up event 0x80000a
ezri user.info kernel: eth0: Setting full-duplex based on negotiated link capability.
Could you please run "ethtool -s eth0 msglvl 0xffffffff" to turn logging
from the driver right up and send a log? This will spam the log if
there is any traffic but should say why the driver is doing this.
It seems to be repeatedly setting the same duplex setting. The closest
thing I can see in there in recent times is
68c90166e4aaa15ddcdd4778ad30bfb8b32534be, "Add support for using MII port
with no PHY".
It's not just setting the same duplex setting, the WoL message indicates
that it's doing that as part of init_registers() which should only be
happening in error handling paths and during resume or open.
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."