Re: [PATCH] Gigabit Ethernet support for forcedeth

[Manfred Spraul]

Tim Waugh wrote:

> > Which phy is used by your board? Could you enable dprintk (near line 
> > 115) and reload the driver?
> >    
>
> I've enabled dprintk and captured *.debug syslog output from a normal
> boot.  Here is the result:
>
> http://cyberelk.net/tim/tmp/forcedeth-debug
>
>  
The log is very odd - why are there two lines with

> forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.28.

Did you rmmod/insmod the driver twice?


Could you manually insmod the driver, wait for two seconds and then call 
ifup? The new driver
- resets the phy during _probe. The result is no link for a few seconds, 
until autonegotiation has completed.
- check if there is a link during _open(). If there is a link, it's 
used. If there is no link, then it relies on the link irq to detect it.

I frequently see the "no link" messages during ifup, but on my system 
the driver recovers as soon as the autonegotiation is completed. Perhaps 
I must add a link handling timer that polls for link changes.

If a delay before ifup is not enough: manually call nv_link_irq even if 
NVREG_IRQ_LINK is not set. If this is not enough: comment out the 
NVREG_MIISTAT_LINKCHANGE test in nv_link_irq.

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