[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46379A7E.3000109@interia.pl>
Date: Tue, 01 May 2007 21:52:30 +0200
From: Rafał Bilski <rafalbilski@...eria.pl>
To: Mark Brown <broonie@...ena.org.uk>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: Natsemi DP83815 driver spaming
>> eth0: Media selection timer tick.
>> eth0: possible phy reset: re-initializing
>
> This is why the reset is being triggered - it's a workaround for a hardware
> bug which checks to make sure the hardware is in the state that the
> kernel thinks it is is going off. The code has this explanatory comment:
>
> * 2) check for sudden death of the NIC:
> * It seems that a reference set for this chip went out with incorrect info,
> * and there exist boards that aren't quite right. An unexpected voltage
> * drop can cause the PHY to get itself in a weird state (basically reset).
> * NOTE: this only seems to affect revC chips.
>
Code commented out and NIC is working OK. Strange.
eth0: DSPCFG accepted after 0 usec.
eth0: link up.
eth0: Setting full-duplex based on negotiated link capability.
dspcfg = 0x00000000 np->dspcfg = 0x00005060
dspcfg = 0x00000000 np->dspcfg = 0x00005060
dspcfg = 0x00000000 np->dspcfg = 0x00005060
dspcfg = 0x00000000 np->dspcfg = 0x00005060
dspcfg = 0x00000000 np->dspcfg = 0x00005060
dspcfg = 0x00000000 np->dspcfg = 0x00005060
dspcfg = 0x00000000 np->dspcfg = 0x00005060
One problem solved in mean time :-)
> PCI: CS5530 video turned off.
[BTW, as Andrew said please don't drop people from the CC.]
I didn't. It is Thunderbird. I'm included instead of You. Fixed
manually this time.
Regards
Rafał
----------------------------------------------------------------------- Linda jako gospodyni domowa - zobacz!!!
>>> http://link.interia.pl/f1a79
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists