Hello Francois,

after having some issues with networking on Fedora 10 I was given your
name to provide some data to. See this fedora forum
post :http://forums.fedoraforum.org/showthread.php?t=205609

I hope you'll be able to get to the bottom of this failure. I have
attached the information suggested in the above post, plus some further
information. In a nutshell, on my hardware the network is unusable after
bootup, until the user crashes the r8169 module by timing out a hostname
lookup. I have included the repeatable crash testcase in the attached
file.

I believe that simply removing the module and modprobing it back in
again after bootup also delivers a working network without the oops.

Let me know if you need any further information, or want me to test
further.

Regards

Dale

[ message continues ]

On Sun, 30 Nov 2008 23:29:14 +1300

This line from your dmesg caught my eye.

Clocksource tsc unstable (delta = -249993826 ns)

Does booting with clocksource=hpet change anything?  What about the
others in 
/sys/devices/system/clocksource/clocksource0/available_clocksource

Jay
--

[ message continues ]

Jay Cliburn <jcliburn@gmail.com> :

Once this is done, can your send your .config and tell if simply
issuing an 'ethtool -s eth0 autoneg off' then 'ethtool -s eth0 autoneg on' 
makes a difference ?

-- 
Ueimor
--

[ message continues ]