From: "ph0x" <ph0x@freequest.net>
To: "'Jesse Brandeburg'" <jesse.brandeburg@gmail.com>
Cc: <linux-kernel@vger.kernel.org>,
"'Kernel Netdev Mailing List'" <netdev@vger.kernel.org>
Subject: RE: PROBLEM: bug in e1000 module causes very high CPU load
Date: Sun, 11 Dec 2005 20:41:18 +0100 [thread overview]
Message-ID: <20051211194114.GBCH17186.mxfep02.bredband.com@ph0x> (raw)
In-Reply-To: <4807377b0512101416t2f3a04c5ua6859ab3d99e8d07@mail.gmail.com>
>please send the output of cat /proc/interrupts, I'm worried you have
>an issue due to interrupt sharing. If it does fail again and is still
>usable, please send the output of ethtool -d eth0, and ethtool -S
>eth0. Also, is there any chance you can try the 6.2.15 driver from
>http://prdownloads.sf.net/e1000
ph0x@orion:~$ cat /proc/interrupts
CPU0
0: 113068493 XT-PIC timer
2: 0 XT-PIC cascade
8: 1 XT-PIC rtc
9: 0 XT-PIC acpi
10: 25386110 XT-PIC eth1
11: 29562097 XT-PIC eth0
12: 527004 XT-PIC uhci_hcd:usb1, uhci_hcd:usb2
14: 565520 XT-PIC ide0
15: 1887 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0
The problem is that the card has never been rendered unusable, it just
starts to have performance issues.
I've compiled the new driver and installed it. I'll schedule a reboot later
this week to get it working.
I've also built 2.6.14.3, which was activeted by a reboot this Saturday.
I'll let you know if the new driver worked.
>do you have a test to reproduce this?
Yes, let the server act as usual, it just starts happening out of the blue.
No new hardware has been added or removed, no new programs has been
installed.
Only thing upgrades was the kernel.
>Thanks, Jesse
Thanks,
Andreas
next prev parent reply other threads:[~2005-12-11 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051210114100.QFYF676.mxfep01.bredband.com@ph0x>
2005-12-10 22:16 ` PROBLEM: bug in e1000 module causes very high CPU load Jesse Brandeburg
2005-12-11 19:41 ` ph0x [this message]
2005-12-23 23:14 ` Leroy van Logchem
2006-01-10 2:41 ` Jesse Brandeburg
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=20051211194114.GBCH17186.mxfep02.bredband.com@ph0x \
--to=ph0x@freequest.net \
--cc=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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