From: John Wong <kernel@implode.net>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: via-rhine on 2.4.23-pre6 Too much work at interrupt, status=0x00001000. (fwd)
Date: Fri, 24 Oct 2003 15:43:55 -0700 [thread overview]
Message-ID: <20031024224355.GA2826@gambit.implode.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0310241101320.1354-100000@logos.cnet>
On Fri, Oct 24, 2003 at 11:02:30AM -0200, Marcelo Tosatti wrote:
>
>
> On Wed, 22 Oct 2003, John Wong wrote:
>
> > Could the problem detailed in the thread:
> >
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=106687979128274&w=2
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=106688008628516&w=2
> >
> > with reference to 8390-based drivers affect the via-rhine driver?
>
> No this is a different bug.
>
> In previous message you said 2.4.22 also was spitting "too much work at
> interrupt". Correct?
Correct. 2.4.22 had this same problem.
> Which kernel works on this box?
I have never had a kernel that has worked with this box as is. The
2.4.22 kernel worked fine on the system before I replaced the
motherboard/CPU/RAM. 2.4.22 was compiled with Pentium optimizations for
a Pentium 100 on a 430FX chipset. 2.4.23-pre6 (now pre7) is compiled
with K6 optimizations for a K6 2 500 on a MVP3 chipset. ACPI was
initially enabled on the 23-preX kernels, but disabled when Jeff
suggested it might have been the problem. Both systems
used the same OS/harddrive/NICs.
John
prev parent reply other threads:[~2003-10-24 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0310171852330.12627-100000@logos.cnet>
2003-10-17 22:09 ` via-rhine on 2.4.23-pre6 Too much work at interrupt, status=0x00001000. (fwd) Jeff Garzik
2003-10-19 6:09 ` John Wong
[not found] ` <20031019071012.GA13898@gambit.implode.net>
2003-10-19 7:22 ` John Wong
2003-10-23 4:23 ` John Wong
2003-10-24 13:02 ` Marcelo Tosatti
2003-10-24 22:43 ` John Wong [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031024224355.GA2826@gambit.implode.net \
--to=kernel@implode.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).