Comment 6 for bug 372685

Unfortunately I reinstalled intrepid, so can't supply the specific diagnostics.

However, when I went back to intrepid, I had the same problem.

When my network stopped during file transfer I took a look at dmesg, and it had a message regarding clocksource tsc being unstable.

Not clear why this should affect the NIC, but after a quick search on the web, it seems that the fix is to either stick a new battery in the motherboard, or put clocksource=hpet into the boot parameters.

not having a battery handy, I tried the clocksource=hpet option, and everything has been fine for the last day or two.

I'm going to keep an eye on it, and if it is still fine, will reinstall jaunty at the weekend, and test.

Perhaps I've always had an unstable clocksource, and there is something in the recent kernel that is more sensitive to it?

Jeff.