On Wed, August 6, 2008 21:50, Francois Romieu wrote:
quoted text
> Indan Zupancic <indan@nul.nu> :
> [...]
>> "git log drivers/net/r8169.c" shows only two commits since May 11:
>
> $ git rev-list v2.6.26..v2.6.27-rc1 -- drivers/net/r8169.c
> 77332894c21165404496c56763d7df6c15c4bb09
> f887cce8de019bb32917789379af89ae4c0294ee
> 865c652d6be9929927cabdc54b137b7541eb6612
> 1087f4f4af302e6e2fa40dd741f306444d90bece
>
>> r8169: avoid thrashing PCI conf space above RTL_GIGA_MAC_VER_06
>>
>> r8169: multicast register update
>>
>> Then at May 11 comes:
>>
>> r8169: remove non-napi code
>>
>> But I think that was in 2.6.26 already.
>
> No. :o)

Oh...

I tried 2.6.27-rc2 with that patch reverted and NAPI disabled,
but that didn't work either, so it seems it's something a level
higher. (No way that that last patch could cause this...)

You said off-list that I may want to check if there is any aspm
related message in dmesg. Well, I get this:

  Pre-1.1 PCIe device detected, disable ASPM for 0000:00:1c.1.
  It can be enabled forcedly with 'pcie_aspm=force'

So I guess it's unlikely that it causes any problems, except
if the driver assumes it's always enabled. Booting with
pcie_aspm=force didn't change anything (though strangely
enough I still get the same message as above).

All in all I'll wait till rc3 and see how things are then.

Thank you for the help,

Indan


--
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