From: Dave Hansen <haveblue@us.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: acenic >4gig sendfile problem
Date: Mon, 10 Jun 2002 14:55:23 -0700 [thread overview]
Message-ID: <3D05204B.4010103@us.ibm.com> (raw)
When doing sendfile with my acenic card on my 8xPIII-700 and PAE
running 2.4.18, I'm getting all zeros in the files being transmitted.
Running the Redhat 2.4.18-4 kernel fixes the problem. I saw this
entry in the rpm's changelog:
* Sat Aug 25 2001 Ingo Molnar <mingo@redhat.com>
- fix the acenic driver bug that caused random kernel memory being
sent out on the wire, on x86 systems with more than 4 GB RAM.
I tried to pull the relevant bits out of
linux-2.4.17-selected-ac-bits.patch and linux-2.4.18-tg3.patch, with
no success. I mailed Ingo with no response.
Does anybody remember what the fix was, or still have the patch handy?
--
Dave Hansen
haveblue@us.ibm.com
next reply other threads:[~2002-06-10 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 21:55 Dave Hansen [this message]
2002-06-24 15:31 ` acenic >4gig sendfile problem Jes Sorensen
2002-06-24 15:54 ` Roy Sigurd Karlsbakk
2002-06-24 16:02 ` David S. Miller
2002-06-25 6:46 ` Dave Hansen
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=3D05204B.4010103@us.ibm.com \
--to=haveblue@us.ibm.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