netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Snook <csnook@redhat.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Jay Cliburn <jacliburn@bellsouth.net>,
	"Jay L. T. Cornwall" <jay@esuna.co.uk>,
	Luca Tettamanti <kronos.it@gmail.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] atl1: disable 64bit DMA
Date: Mon, 25 Jun 2007 19:40:26 -0400	[thread overview]
Message-ID: <4680526A.3020908@redhat.com> (raw)
In-Reply-To: <46804CFC.4000702@pobox.com>

Jeff Garzik wrote:
> Jay Cliburn wrote:
>> On Mon, 25 Jun 2007 17:57:20 -0400
>> Chris Snook <csnook@redhat.com> wrote:
>>
>>> Jay L. T. Cornwall wrote:
>>>> Chris Snook wrote:
>>>>
>>>>> What boards have we seen this on?  It's quite possible this is:
>>>> I can reproduce on an Asus P5K with a Core 2 Duo E6600.
>>>>
>>>> lspci identifies the controller as:
>>>>   02:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit
>>>>   Ethernet Adapter (rev b0)
>>>>
>>>> dmesg notes the PCI-DMA mapping implementation:
>>>>   PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
>>>>
>>> I had a hunch this was on Intel.  I'd rather just disable this when
>>> swiotlb is in use, unless we get more complaints.  It's probably
>>> ultimately a BIOS quirk anyway.
>>
>> So far we have reports from both camps:
>>
>> Asus M2N8-VMX (AM2):    1 report of lockup
>> http://sourceforge.net/mailarchive/forum.php?thread_name=46780384.063603.26165%40m12-15.163.com&forum_name=atl1-devel 
>>
>>
>> Asus P5K (LGA775):    2 reports of lockups
>> http://sourceforge.net/mailarchive/forum.php?thread_name=467E7E34.4010603%40gmail.com&forum_name=atl1-devel 
>>
>> http://lkml.org/lkml/2007/6/25/107
>>
>> The common denominator in these reports is 4GB RAM.
> 
> Although its possible this device doesn't really support 64-bit, it's 
> more likely that this is a platform problem of some sort, or a driver 
> bug of some sort.  In the driver, maybe it has a problem when you 
> -cross- a 4GB boundary, which is not uncommon.
> 
>     Jeff

I'm going on the record to say I don't trust the chipsets on these boards, and 
I'd like anyone having these problems to let us 
(atl1-devel@lists.sourceforge.net) know if they encounter similar problems with 
any other hardware.  That said, I'm not going to stand in the way of stability 
just because it *might* be someone else's fault.  I don't think limiting 
ourselves to dma32, at least while we track this down, is much of a loss on 
current hardware.

Acked-By: Chris Snook <csnook@redhat.com>

  reply	other threads:[~2007-06-25 23:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <467B12CA.5060405@esuna.co.uk>
     [not found] ` <467BE118.4090308@redhat.com>
     [not found]   ` <467BE4F1.7040308@esuna.co.uk>
     [not found]     ` <467D0EB0.9030100@esuna.co.uk>
     [not found]       ` <20070624125957.2e27820c@osprey.hogchain.net>
     [not found]         ` <467ED4A8.4080500@esuna.co.uk>
     [not found]           ` <20070624164519.04f215b8@osprey.hogchain.net>
     [not found]             ` <467FB237.2030703@esuna.co.uk>
     [not found]               ` <467FB844.6060702@bellsouth.net>
2007-06-25 21:18                 ` [PATCH] atl1: disable 64bit DMA Luca Tettamanti
2007-06-25 21:36                   ` Chris Snook
2007-06-25 21:51                     ` Jay L. T. Cornwall
2007-06-25 21:57                       ` Chris Snook
2007-06-25 23:00                         ` Jay Cliburn
2007-06-25 23:17                           ` Jeff Garzik
2007-06-25 23:40                             ` Chris Snook [this message]
2007-06-26 21:12                             ` Luca
2007-06-27  0:16                   ` 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=4680526A.3020908@redhat.com \
    --to=csnook@redhat.com \
    --cc=jacliburn@bellsouth.net \
    --cc=jay@esuna.co.uk \
    --cc=jgarzik@pobox.com \
    --cc=kronos.it@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;
as well as URLs for NNTP newsgroup(s).