From: Ben Liblit <liblit@acm.org>
To: David Miller <davem@davemloft.net>
Cc: jesse.brandeburg@intel.com, mchan@broadcom.com,
akpm@linux-foundation.org, netdev@vger.kernel.org,
bugme-daemon@bugzilla.kernel.org, john.ronciak@intel.com
Subject: Re: [Bugme-new] [Bug 10600] New: e1000 updates rx_bytes infrequently
Date: Mon, 12 May 2008 01:26:06 -0500 [thread overview]
Message-ID: <4827E2FE.1040109@acm.org> (raw)
In-Reply-To: <20080511.231806.193710614.davem@davemloft.net>
David Miller wrote:
> You're missing a zero in that string, it's "e1000e" not "e100e", and
> did you make sure to enable CONFIG_E1000E in your kernel config?
Sorry, that was a typo in my comment but not in my actual experiments.
I used "e1000e", not "e100e". CONFIG_E1000E is enabled, and "lsmod"
confirmed that the e1000e module was definitely loaded into the kernel.
"The kernel", for the record, is the current Fedora 8 kernel,
2.6.24.5-85.fc8.
I realize that pristine, self-built kernels are preferred for bug
reporting. I am currently building my own 2.6.25.3 so that I can affirm
or refute Jesse Brandeburg's claim (comment #12) that this bug is fixed
in 2.6.25-rc1 and later. I'll report my findings when available,
assuming I still remember how to install my own kernels. (Yes, yes,
I've gotten soft and lazy.)
next prev parent reply other threads:[~2008-05-12 6:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10600-10286@http.bugzilla.kernel.org/>
2008-05-05 22:55 ` [Bugme-new] [Bug 10600] New: e1000 updates rx_bytes infrequently Andrew Morton
2008-05-05 23:18 ` David Miller
2008-05-05 23:55 ` Ben Liblit
2008-05-06 1:17 ` Michael Chan
2008-05-06 0:43 ` Krzysztof Oledzki
2008-05-06 1:55 ` Michael Chan
2008-05-06 1:24 ` Ben Liblit
2008-05-06 17:22 ` Brandeburg, Jesse
2008-05-06 20:49 ` Brandeburg, Jesse
2008-05-12 5:44 ` Ben Liblit
2008-05-12 6:18 ` David Miller
2008-05-12 6:26 ` Ben Liblit [this message]
2008-05-12 6:42 ` Ben Liblit
2008-05-06 0:55 ` Michael Chan
2008-05-05 23:53 ` David Miller
2008-05-05 23:38 ` Ben Liblit
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=4827E2FE.1040109@acm.org \
--to=liblit@acm.org \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=mchan@broadcom.com \
--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;
as well as URLs for NNTP newsgroup(s).