On Thu, Aug 7, 2008 at 4:31 PM, Francois Romieu <romieu@fr.zoreil.com> wrote:
quoted text
> John P Poet <jppoet@gmail.com> :
> [...]
>> That does not make any difference.
>>
>> I will say, that the problem seems to be reduced by this patch (or the
>> 0002-r8169-avoid-thrashing-PCI-conf-space-above-RTL_GIGA.patch).
>>
>> Before, I was getting failures two or three times an hour.  With
>> either of these patches applied, the failure rate has dropped to one
>> every two to four hours.
>
> I have updated the kit at http://userweb.kernel.org/~romieu/r8169/2.6.27-rc2
>
> Can you give it a try ?

At first I *just* applied 20080807-r8169-test.patch, but the NIC did
not initialize during boot.  So, I also applied
0002-r8169-avoid-thrashing-PCI-conf-space-above-RTL_GIGA.patch.  After
that, it booted okay.

However, in general use it is much worse.  May just be bad luck (or
something in the 2.26.2 kernel?), but the timeout message are rampant:

Aug  7 21:14:58 saphire kernel: NETDEV WATCHDOG: eth0: transmit timed out
Aug  7 21:14:58 saphire kernel: r8169: eth0: link up


John
-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html