Re: early_ioremap messages with old ASUS board

[Frans Pop]

Jens Rosenboom wrote:
> Running 2.6.31-rc4 I get the following dmesg output:
>
> [ 0.000000] early_ioremap(000f0000, 00010000) [0] => Pid: 0, comm:
> swapper Not tainted 2.6.31-rc4 #36
> [ 0.000000] Call Trace:
> [ 0.000000]  [<c136e48b>] ? printk+0x18/0x1d
> [ 0.000000]  [<c15513ff>] __early_ioremap+0x74/0x1e9
> [ 0.000000]  [<c15515aa>] early_ioremap+0x1a/0x1c
> [ 0.000000]  [<c156194e>] dmi_scan_machine+0x1a/0x1af
> [ 0.000000]  [<c15404c5>] ? parse_early_options+0x23/0x25
> [ 0.000000]  [<c1543d92>] setup_arch+0x3d0/0x922
> [ 0.000000]  [<c1166e82>] ? __spin_lock_init+0x32/0x60
> [ 0.000000]  [<c1540897>] start_kernel+0x77/0x2da
> [ 0.000000]  [<c1540352>] i386_start_kernel+0x7c/0x83
> [ 0.000000] 00000000 + ffe00000

Did .31-rc3 work correctly?

If it did, then could you try if reverting commit 857fdc53a0a9 helps?
It's a bit of a wild guess, but it solved an iomem change on my notebook.

Cheers,
FJP
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/