1 |
IRQ processing smells like the problem - trouble pops up with NFS/ftp/ping/whatever, but only when I saturate the link. Back to .28 until that "minor" bug is fixed. |
2 |
|
3 |
Thanks. |
4 |
|
5 |
On Wed, Apr 01, 2009 at 12:15:43PM +0000, Duncan wrote: |
6 |
> Kyle Liddell <kyle@××××××××××××××××.net> posted |
7 |
> 20090401060645.GA4182@athlon, excerpted below, on Wed, 01 Apr 2009 |
8 |
> 02:06:45 -0400: |
9 |
> |
10 |
> > After upgrading the kernel from 2.6.28-gentoo-r3 to 2.6.29, I'm having a |
11 |
> > weird problem: If I make "light" use of the network (ssh, email, http, |
12 |
> > etc), no trouble. But, if I make "heavy" use of the network (say, |
13 |
> > copying a few GB from a local NFS server to /dev/null), the network |
14 |
> > interface stops working almost immediately. ifconfig, mii-tool, the |
15 |
> > NIC's led, and the switch's LED all say that the link is still up. But, |
16 |
> > all my connections time out, ping gets no replies, etc. (I'm using the |
17 |
> > via-velocity driver for my motherboard's built-in 1GB NIC.) |
18 |
> |
19 |
> I'm unsure if your hardware is affected, but there's a known NAPI and |
20 |
> interrupt related regression in 2.6.29. It was due to a commit trying to |
21 |
> fix another bug just a few hours before release, and the discovery and |
22 |
> subsequent bug trace was one of two subthreads quickly attached to Linus' |
23 |
> 2.6.29 official announcement. (FWIW, the other subthread was even more |
24 |
> fallout from the earlier ext4 data loss over improper shutdown, where |
25 |
> ext3 was fine. That has and continues to generate HUGE subthreads all |
26 |
> over the place, from the Ubuntu bug filing that was one of the first |
27 |
> reports of it to LKML to /. to LWN. ext4 may have had the dev- removed |
28 |
> from the name, but it's not exactly stable as this demonstrates, and |
29 |
> what's worse, many people including Ted Tso seem to think the problem |
30 |
> really is NOTABUG.) |
31 |
> |