From: "Art Wagner" <awagner@qwest.net>
To: "Jeff Garzik" <jgarzik@mandrakesoft.com>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: 8139too.c and 2.4.4-pre1 kernel burp
Date: Wed, 11 Apr 2001 19:15:05 +0000 [thread overview]
Message-ID: <3AD4AD39.6B070782@qwest.net> (raw)
In-Reply-To: <3AD118F4.3050507@xmission.com> <3AD11A13.6E52A515@mandrakesoft.com>
Jeff;
I am getting the same problem with 2.4.3-ac4.
See the attached messages log and system Information.
The problem seems to be traffic sensitive, with higher
traffic between my system and the Cisco 675 DSL modem at
10.0.0.1.
Please let me know if I can provide any further useful
information.
Art Wagner
Jeff Garzik wrote:
>
> Frank Jacobberger wrote:
> >
> > Jeff,
> >
> > I noticed the following on boot with 2.4.4-pre1:
> >
> > kernel: eth0: Too much work at interrupt, IntrStatus=0x0001.
> >
> > What is this saying to me :)
>
> How often does this occur? A lot, or just once or twice?
>
> --
> Jeff Garzik | Sam: "Mind if I drive?"
> Building 1024 | Max: "Not if you don't mind me clawing at the dash
> MandrakeSoft | and shrieking like a cheerleader."
> -
> 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/
next prev parent reply other threads:[~2001-04-12 2:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 2:05 8139too.c and 2.4.4-pre1 kernel burp Frank Jacobberger
2001-04-09 2:10 ` Jeff Garzik
2001-04-09 5:45 ` Frank Jacobberger
2001-04-11 8:12 ` Stefan Becker
2001-04-11 19:15 ` Art Wagner [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-13 9:22 Jörn Nettingsmeier
2001-04-13 9:28 ` Jörn Nettingsmeier
2001-04-13 22:39 ` Jeff Garzik
2001-04-17 16:05 ` Jörn Nettingsmeier
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=3AD4AD39.6B070782@qwest.net \
--to=awagner@qwest.net \
--cc=jgarzik@mandrakesoft.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