On Mon, 30 Jan 2006, Jens Axboe wrote:
> > > If this is a hardware bug, why am I only seeing it now all of a sudden?
> > > I'll try with e1000 drivers from an older kernel on this box now, just
> > > to be sure. Starting with 2.6.14, although I'm pretty certain that
> > > 2.6.15 worked flawlessly as well.
> >
> > Just copying over e1000/* from 2.6.14 works great, no timeouts
> > experienced. It's scp'ed ~150MiB now, before it threw timeouts before it
> > hit 16MiB even. Rate is about ~800KiB/sec, this is over the internet
> > through my router. This must be a driver bug introduced recently. I'll
> > try 2.6.15 e1000 as well, but as written above, I'm pretty sure the bug
> > only started to show its ugly face after the e1000 updates in
> > 2.6.16-rc1.
>
> 2.6.15 hangs as well. So: 2.6.14 good, 2.6.15 bad :-)
>
> I'll stop testing now and live with 2.6.14 until you have something for
> me to try out.
Recompile with 2.6.14 drivers and retest just to be sure - it's
definitely working. I can say that fairly certainly, since the newer
kernels throw up so quickly.
Okay, good to know that 2.6.14 works.
We've been unable to repro this here, please send your motherboard info
(or just output of dmidecode) and .config, as well as the output of
ethtool -e
Please make sure you're running the latest bios for your machine.
Thanks in advance,
Jesse
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
