All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: "Per Øyvind Karlsen" <peroyvind@sintrax.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: unresolved symbols for drm module on sparc64
Date: Wed, 5 Apr 2006 18:30:34 +0200	[thread overview]
Message-ID: <20060405163034.GE8673@stusta.de> (raw)
In-Reply-To: <200604051530.00883.peroyvind@sintrax.net>

On Wed, Apr 05, 2006 at 03:30:00PM +0200, Per Øyvind Karlsen wrote:
> When building 2.6.17-rc1 on sparc64 I run into this problem:
> if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F System.map 
> -b /root/RPM/BUILD/kernel-linus-2.6/temp-root -r 2.6.17-rc1.16mdksmp; fi
> WARNING: /root/RPM/BUILD/kernel-linus-2.6/temp-root/lib/modules/2.6.17-rc1.16mdksmp/kernel/drivers/char/drm/drm.ko 
> needs unknown symbol dma_alloc_coherent
> WARNING: /root/RPM/BUILD/kernel-linus-2.6/temp-root/lib/modules/2.6.17-rc1.16mdksmp/kernel/drivers/char/drm/drm.ko 
> needs unknown symbol dma_free_coherent
> make: *** [_modinst_post] Error 1
> 
> I'm not subscribed to the list, just thought that I should report since it 
> recently broke, so CC me if any more info is needed.
> I'm also attaching my .config in case it might be of help:)
>...

Thanks for your report.

This is a known bug, and a fix is available at
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17-rc1/2.6.17-rc1-mm1/broken-out/drm_pci-needs-dma-mappingh.patch
 
cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2006-04-05 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-05 13:30 unresolved symbols for drm module on sparc64 Per Øyvind Karlsen
2006-04-05 16:30 ` Adrian Bunk [this message]

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=20060405163034.GE8673@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peroyvind@sintrax.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.