Subject: Re: [PATCH] 8xx: tlbie debugging aid (try #2)

From: Dan Malek <[email-masked]>
Date: Mon, 27 Jun 2005 16:18:14 -0400

On Jun 27, 2005, at 10:28 AM, Marcelo Tosatti wrote:

> it yields
>
> _tlbie on pinned range: c0000000-c1800000
> Badness in _tlbie at arch/ppc/mm/pgtable.c:527
> Call trace:
>  [c0005530] dump_stack+0x18/0x28
>  [c0003628] check_bug_trap+0x84/0xac
>  [c00037b0] ProgramCheckException+0x160/0x1a0
>  [c0002d50] ret_from_except_full+0x0/0x4c
>  [c000a91c] _tlbie+0x94/0xa0
>  [c902f018] alloc_init_module+0x18/0x40 [alloc]
>  [c002c4ac] sys_init_module+0x224/0x324
>  [c00026f0] ret_from_syscall+0x0/0x44

How much real memory on your board?
We need to ensure VMALLOC_START is beyond
the pinned entries.  We should make all of the code
much smarter to pin on the real space that is on
the board.  For testing now, just make VMALLOC_OFFSET
32M, which will push the start to the 32M boundary
after the kernel.

Thanks.

	-- Dan