On Tue, May 01, 2007 at 12:25:20PM +0200, Rafał Bilski wrote: > 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. I'd suggest checking your power supply as a first step. [BTW, as Andrew said please don't drop people from the CC.] -- "You grabbed my hand and we fell into it, like a daydream - or a fever."
Attachment:
signature.asc
Description: Digital signature
- Follow-Ups:
- Re: Natsemi DP83815 driver spaming
- From: Rafał Bilski <[email protected]>
- Re: Natsemi DP83815 driver spaming
- From: Rafał Bilski <[email protected]>
- Re: Natsemi DP83815 driver spaming
- References:
- Natsemi DP83815 driver spaming
- From: Rafał Bilski <[email protected]>
- Re: Natsemi DP83815 driver spaming
- From: Andrew Morton <[email protected]>
- Re: Natsemi DP83815 driver spaming
- From: Mark Brown <[email protected]>
- Re: Natsemi DP83815 driver spaming
- From: Rafał Bilski <[email protected]>
- Natsemi DP83815 driver spaming
- Prev by Date: Re: [PATCH 2/2] AFS/AF_RXRPC: Miscellaneous fixes
- Next by Date: Re: [Kernel-discuss] Re: [RFC, PATCH 0/4] SoC base drivers
- Previous by thread: Re: Natsemi DP83815 driver spaming
- Next by thread: Re: Natsemi DP83815 driver spaming
- Index(es):
 |