Messages in this thread | | | Date | Sun, 19 Oct 2003 00:22:18 -0700 | From | John Wong <> | Subject | Re: via-rhine on 2.4.23-pre6 Too much work at interrupt, status=0x00001000. (fwd) |
| |
Reposting to the LKML as my previous post had a technical difficulty.
John
On Sun, Oct 19, 2003 at 12:10:12AM -0700, John Wong wrote: > I received the same problem with 2.4.23-pre2. Just to amuse myself, I > booted up 2.4.22 and the problem of Too much work still occurs. > > John > > On Sat, Oct 18, 2003 at 11:09:53PM -0700, John Wong wrote: > > Hi, > > > > I took a slightly different route, and updated the kernel to 2.4.23-pre7 > > and disabled ACPI. The problem did reoccur, so this would rule out > > ACPI. I will downgrade the kernel to pre2 now. > > > > Oct 18 21:46:58 cyclops kernel: eth0: Too much work at interrupt, > > status=0x00001000. > > > > John > > > > On Fri, Oct 17, 2003 at 06:09:02PM -0400, Jeff Garzik wrote: > > > >Date: Thu, 16 Oct 2003 12:27:17 -0700 > > > >From: John Wong <kernel@implode.net> > > > >To: linux-kernel@vger.kernel.org > > > >Subject: via-rhine on 2.4.23-pre6 Too much work at interrupt, > > > > status=0x00001000. > > > > > > > >The system used to run 2.4.22 and did not have this too much work > > > >problem. There were some other hardware changes. The system used to be > > > >a Pentium 100 on a Triton 430FX chipset Intel Advanced/EV board. Now it > > > >is a K6 2 - 500 on a Via Apollo MVP3 chipset on FIC VA-503+ board. > > > >The NIC stayed the same. The kernel was recompiled and ACPI was > > > >enabled. > > > > > > > >I noticed in 2.4.23-pre2 -> pre3 > > > > [netdrvr] sync with 2.5: epic100, fealnx, via-rhine, winbond-840 > > > > > > > > > This cset contains no functional via-rhine changes... First thing to do > > > would be try to 2.4.23-pre2. But my main suspect would be ACPI. > > > > > > Jeff > > > > > > > > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |