From: "Jörn Nettingsmeier" <nettings@folkwang-hochschule.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 8139too.c and 2.4.4-pre1 kernel burp
Date: Tue, 17 Apr 2001 18:05:17 +0200 [thread overview]
Message-ID: <3ADC69BD.C94454CC@folkwang-hochschule.de> (raw)
In-Reply-To: <3AD6C572.7A9FA060@folkwang-hochschule.de> <3AD78005.B8C5F094@mandrakesoft.com>
hello jeff !
with the 8139too v. 0.9.16 from
http://sourceforge.net/projects/gkernel/ and kernel 2.4.4-pre3, i
see no more errors of the "too much work at interrupt" type.
i used to see the errors even under normal load, starting
immediately after booting.
so far, i did some nfs and flood-pinging, and all seems to be well.
if you want me to run more specific tests, let me know.
thanks,
jörn
Jeff Garzik wrote:
>
> Jörn Nettingsmeier wrote:
> >
> > 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?
> >
> > i'm seeing this, too. it occurs *very* often during access of the
> > card:
> >
> > Apr 13 11:08:11 kleineronkel kernel: eth0: Too much work at
> > interrupt, IntrStatus=0x0001.
> > Apr 13 11:08:44 kleineronkel last message repeated 869 times
> > Apr 13 11:09:29 kleineronkel last message repeated 59 times
> > Apr 13 11:10:04 kleineronkel last message repeated 2 times
> > Apr 13 11:11:43 kleineronkel last message repeated 149 times
> > Apr 13 11:11:59 kleineronkel last message repeated 4 times
> > Apr 13 11:13:01 kleineronkel last message repeated 7 times
> > Apr 13 11:15:01 kleineronkel kernel: eth0: Too much work at
> > interrupt, IntrStatus=0x0001.
> > Apr 13 11:16:15 kleineronkel last message repeated 6 times
> > Apr 13 11:16:15 kleineronkel kernel: eth0: Too much work at
> > interrupt, IntrStatus=0x0001.
> > Apr 13 11:18:01 kleineronkel last message repeated 5 times
> > Apr 13 11:18:06 kleineronkel modprobe: modprobe: Can't locate module
> > net-pf-10
> > Apr 13 11:18:08 kleineronkel sshd[1631]: Accepted password for ROOT
> > from 127.0.0.1 port 32948
> > Apr 13 11:18:08 kleineronkel modprobe: modprobe: Can't locate module
> > net-pf-10
> > Apr 13 11:18:09 kleineronkel kernel: eth0: Too much work at
> > interrupt, IntrStatus=0x0001.
> >
> > and so on.
> >
> > it might be important that i'm sharing the IRQ:
> >
> > kleineronkel:~ # cat /proc/interrupts
> > CPU0 CPU1
> > 0: 294470 246477 IO-APIC-edge timer
> > 1: 4552 5266 IO-APIC-edge keyboard
> > 2: 0 0 XT-PIC cascade
> > 8: 2 0 IO-APIC-edge rtc
> > 12: 29084 29205 IO-APIC-edge PS/2 Mouse
> > 14: 4 4 IO-APIC-edge ide0
> > 15: 4924 5704 IO-APIC-edge ide1
> > 16: 1256 1373 IO-APIC-level EMU10K1
> > 17: 0 0 IO-APIC-level Ensoniq AudioPCI
> > 19: 76145 76111 IO-APIC-level aic7xxx, eth0
> > NMI: 0 0
> > LOC: 540865 540843
> > ERR: 0
> >
> > and yes, this is an SMP box (dual p3/600) with a bx chipset.
> >
> > please keep me on cc:, as i have only archive access to LKML.
> > thanks.
> > btw, jeff, the old "kernel: eth0: Abnormal interrupt, status
> > 0000000[2,6]" messages have disappeared since 2.4.3 or so.
>
> I've fixed this locally. I just need to test all the RTL chips (five or
> six variants) before I send the next patch to Linus/Alan...
>
> --
> 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."
--
Jörn Nettingsmeier
home://Kurfürstenstr.49.45138.Essen.Germany
phone://+49.201.491621
http://www.folkwang-hochschule.de/~nettings/
http://www.linuxdj.com/audio/lad/
next prev parent reply other threads:[~2001-04-17 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-13 9:22 8139too.c and 2.4.4-pre1 kernel burp 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-09 2:05 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
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=3ADC69BD.C94454CC@folkwang-hochschule.de \
--to=nettings@folkwang-hochschule.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.