LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: linuxppcdev@qbjnet.com
To: linuxppc-dev@ozlabs.org
Subject: Re: DMA appears broken in 2.6.11 for Mac 7200
Date: 18 Mar 2005 02:55:29 -0000	[thread overview]
Message-ID: <20050318025529.553.qmail@kunk.qbjnet.com> (raw)

Ben Said:
> On Mon, 2005-03-14 at 03:51 +0000, linuxppcdev@qbjnet.com wrote:
> > Just updated a couple of old Mac 7200 (601) boxen and ran into trouble with
> > the ide driver and a promise PDC20267 card. 
> > 
> > The very same drives and card work fine on a 9500 but hang on a 7200. If
> > I set the kernel arg ide=nodma I get in the dmesg:
> > ide_setup: ide=nodma : Prevented DMA
> > and the 7200 boots and runs fine.
> > 
> > Another suspect, the mace ethernet driver (which also appears to use DMA)
> > doesn't work on the 7200 with 2.6.11 but does with 2.4.28 and it works 
> > with 2.6.11 on the 9500.
> 
> Interesting. Not sure what's up, though. Those old machines were known
> to have bugs relative to cache coherency... also check wetehr we are
> setting the cache line size properly in PCI devices. You can also try to
> disable use of PCI memory write & invalidate command in all devices.
 
Did some more testing on this. Built a 2.4.30-pre1 kernel from bk source.

DMA works fine booting 2.4.30

I compared the dmesg and lspci and I see no differences in the cache line
size.

Is it possible that the ppc 601 kernel fixes aren't getting done properly
in 2.6??

Bob

             reply	other threads:[~2005-03-18  2:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18  2:55 linuxppcdev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-14 17:52 DMA appears broken in 2.6.11 for Mac 7200 linuxppcdev
2005-03-14  3:51 linuxppcdev
2005-03-14  6:58 ` Benjamin Herrenschmidt

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=20050318025529.553.qmail@kunk.qbjnet.com \
    --to=linuxppcdev@qbjnet.com \
    --cc=linuxppc-dev@ozlabs.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