From: John Wong <kernel@implode.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: 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: Wed, 22 Oct 2003 21:23:49 -0700 [thread overview]
Message-ID: <20031023042349.GA6861@gambit.implode.net> (raw)
In-Reply-To: <3F90687E.8030601@pobox.com>
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?
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
>
>
>
next prev parent reply other threads:[~2003-10-23 4:23 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 [this message]
2003-10-24 13:02 ` Marcelo Tosatti
2003-10-24 22:43 ` John Wong
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=20031023042349.GA6861@gambit.implode.net \
--to=kernel@implode.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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).