All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Fleury <emmanuel.fleury@labri.fr>
To: linux-kernel@vger.kernel.org
Subject: [2.6.14.5] iounmap: bad address
Date: Thu, 29 Dec 2005 12:04:35 +0100	[thread overview]
Message-ID: <43B3C2C3.1070201@labri.fr> (raw)

Hi,

I am running a 2.6.14.5 on a Transmeta Crusoe laptop (Vaio PCG-C1MZ) and
I'm having some troubles with the iounmap function. Each time I'm
shutting down the machine or even just stopping the gdm daemon, I got
the following error log:

iounmap: bad address d7233000
 [iounmap+197/208] iounmap+0xc5/0xd0
 [page_remove_rmap+59/96] page_remove_rmap+0x3b/0x60
 [radeon_do_cleanup_cp+856/1056] radeon_do_cleanup_cp+0x358/0x420
 [radeon_do_release+165/288] radeon_do_release+0xa5/0x120
 [drm_takedown+43/960] drm_takedown+0x2b/0x3c0
 [drm_release+1010/1232] drm_release+0x3f2/0x4d0
 [__handle_mm_fault+447/464] __handle_mm_fault+0x1bf/0x1d0
 [__fput+176/400] __fput+0xb0/0x190
 [filp_close+82/144] filp_close+0x52/0x90
 [sys_close+124/128] sys_close+0x7c/0x80
 [syscall_call+7/11] syscall_call+0x7/0xb

I guess the problem is located in arch/i386/mm/ioremap.c where:

write_lock(&vmlist_lock);
p = __remove_vm_area((void *)(PAGE_MASK & (unsigned long __force)addr));
if (!p) {
         printk(KERN_WARNING "iounmap: bad address %p\n", addr);
         dump_stack();
         goto out_unlock;
}

So, it seems that remove_vm_area is returning NULL, and I don't know
why... :-/

Can somebody help me out ?

Regards
-- 
Emmanuel Fleury

The highest goal of computer science is to automate that
which can be automated.
  -- D. L. VerLee

             reply	other threads:[~2005-12-29 11:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-29 11:04 Emmanuel Fleury [this message]
2006-01-03 11:24 ` [2.6.14.5] iounmap: bad address Dave Airlie

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=43B3C2C3.1070201@labri.fr \
    --to=emmanuel.fleury@labri.fr \
    --cc=linux-kernel@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 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.