From: Chuck Ebbert <cebbert@redhat.com>
To: Chris Snook <csnook@redhat.com>
Cc: Jay Cliburn <jacliburn@bellsouth.net>, Netdev <netdev@vger.kernel.org>
Subject: Re: atl1 driver corrupting memory?
Date: Wed, 25 Jul 2007 17:31:02 -0400 [thread overview]
Message-ID: <46A7C116.4010900@redhat.com> (raw)
In-Reply-To: <46A7BEF9.1000600@redhat.com>
On 07/25/2007 05:22 PM, Chris Snook wrote:
> Chuck Ebbert wrote:
>> I have a report of random errors when using the atl1 driver
>> with kernel 2.6.22.1. Could that be a problem fixed by the
>> recent changes to DMA setup in 2.6.23-rc?
>
> I hope so. As far as we can tell the driver and the NIC itself are
> doing the right thing, and the pci layer or chipset is screwing up the
> 64-bit DMA. This only manifests when physical memory addresses cross
> the 4 GB boundary, and as far as I'm aware atl1 is only used on desktop
> boards, so we don't have a lot of testers. If someone wants to buy me
> and Jay more RAM so we can test it ourselves, I guess we wouldn't object :)
>
Our reporter has 8GB of memory in an x86_64 machine.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249511
> I favor disabling 64-bit DMA in atl1 until Atheros can track this down
> in the lab. If we don't get confirmation that this bug is fixed by the
> DMA changes, I think we should revert to 32-bit DMA for 2.6.23.
> Limiting ourselves to 32-bit DMA on desktop systems is a lot less bad
> than allowing arbitrary memory corruption.
>
This is what was committed.
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=3f516c00d416bd39aab6cfb348b68919e295fe23
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ef76e3e2505db01f7d4b537854f4a177220c26c8
next prev parent reply other threads:[~2007-07-25 21:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 18:33 atl1 driver corrupting memory? Chuck Ebbert
2007-07-25 21:22 ` Chris Snook
2007-07-25 21:31 ` Chuck Ebbert [this message]
2007-07-25 21:35 ` Chris Snook
2007-07-26 0:24 ` Jay Cliburn
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=46A7C116.4010900@redhat.com \
--to=cebbert@redhat.com \
--cc=csnook@redhat.com \
--cc=jacliburn@bellsouth.net \
--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).