All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Thomas Meyer <thomas@m3y3r.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dwmw2@infradead.org, c-d.hailfinger.devel.2006@gmx.net,
	dolsen@lnxi.com, rjackson@lnxi.com
Subject: Re: WARNING: at arch/x86/mm/ioremap.c:226
Date: Mon, 20 Oct 2008 11:53:54 -0700	[thread overview]
Message-ID: <20081020185353.GF7829@linux-os.sc.intel.com> (raw)
In-Reply-To: <20081020112851.3ea44576@infradead.org>

On Mon, Oct 20, 2008 at 11:28:51AM -0700, Arjan van de Ven wrote:
> [   16.914566] ck804xrom ck804xrom_init_one(): Unable to register resource 0x00000000ff000000-0x00000000ffffffff - kernel bug?
> [   16.914575] resource map sanity check conflict: 0xff000000
> 0xffffffff 0xff780000 0xffffffff reserved
> 
> [   16.914636]  [<c042c02c>] ioremap_nocache+0xd/0xf
> [   16.914640]  [<f87e4246>] ? init_ck804xrom+0x246/0x4c7 [ck804xrom]
> [   16.914643]  [<f87e4246>] init_ck804xrom+0x246/0x4c7 [ck804xrom]
> 
> the init_ck804xrom driver seems to be requesting a bunch of memory with
> ioremap that crosses several resources...
> which is very bad.
> 
> Can you sent the /proc/iomem file ?

drivers/mtd/maps/ck804xrom.c is hardcoding the address as:

	window->phys = 0xff000000; /* 16MiB, hardcoded for now */

followed by:

	ioremap_nocache(window->phys, window->size);

And later I see something like:

#if 1
	/* The probe sequence run over the firmware hub lock
	 * registers sets them to 0x7 (no access).
	 * Probe at most the last 4MiB of the address space.
	 */
	if (map_top < 0xffc00000)
		map_top = 0xffc00000;
#endif

If they are only probing the last 4MB, the above window mapping can also be
reduced accordingly.

Copying some folks.

thanks,
suresh

      parent reply	other threads:[~2008-10-20 18:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 18:07 WARNING: at arch/x86/mm/ioremap.c:226 Thomas Meyer
2008-10-20 18:28 ` Arjan van de Ven
2008-10-20 18:53   ` Thomas Meyer
2008-10-20 18:53   ` Suresh Siddha [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=20081020185353.GF7829@linux-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=arjan@infradead.org \
    --cc=c-d.hailfinger.devel.2006@gmx.net \
    --cc=dolsen@lnxi.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjackson@lnxi.com \
    --cc=thomas@m3y3r.de \
    /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.