linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Pokki <kalle.pokki@iki.fi>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Badness in dma_alloc_init
Date: Mon, 09 Jan 2006 14:31:03 +0200	[thread overview]
Message-ID: <43C25787.4010204@iki.fi> (raw)

Hi all,

I'm having some trouble with the DMA allocation using Linux 2.6.14-rc2 + 
some platform modifications. Namely, the dma_alloc_coherent() function 
returns bogus virtual addresses causing machine check exceptions. At 
boot, the kernel complains there is something wrong, but I cannot figure 
out how to fix it. CONFIG_CONSISTENT_START is at its default value, 
0xff100000. Any hints where to look further?

Oh, this is a custom 8xx board. Has the support for DMA in 8xx been 
unstable at the time of pre-2.6.14?

Linux version 2.6.14-rc2 (kp@host32.eke.fi) (gcc version 4.0.0 (DENX 
ELDK 4.0 4.
0.0)) #1 Mon Jan 9 12:53:41 EET 2006
Built 1 zonelists
Kernel command line: root=/dev/mtdblock1 ro console=ttyCPM0,115200
PID hash table entries: 256 (order: 8, 4096 bytes)
Decrementer Frequency = 247500000/60
Console: colour dummy device 80x25
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 30268k available (1608k kernel code, 376k data, 100k init, 0k 
highmem)
Mount-cache hash table entries: 512
Badness in dma_alloc_init at arch/ppc/kernel/dma-mapping.c:348
Call trace: [c0003670]  [c0003f24]  [c0003320]  [c01e2ad0]  [c000228c]  
[c000551
c]

... followed by otherwise good startup.

             reply	other threads:[~2006-01-09 12:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 12:31 Kalle Pokki [this message]
2006-01-09 12:53 ` Badness in dma_alloc_init Aristeu Sergio Rozanski Filho
2006-01-09 13:35   ` Kalle Pokki

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=43C25787.4010204@iki.fi \
    --to=kalle.pokki@iki.fi \
    --cc=linuxppc-embedded@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;
as well as URLs for NNTP newsgroup(s).