Problem with module_init?

Josh Boyer jwboyer at
Wed Apr 1 22:27:56 EST 2009

On Tue, Mar 31, 2009 at 11:11:53PM -0400, Sean MacLennan wrote:
>8d1cf34e7ad5c7738ce20d20bd7f002f562cb8b5 is first bad commit
>commit 8d1cf34e7ad5c7738ce20d20bd7f002f562cb8b5
>Author: Benjamin Herrenschmidt <benh at>
>Date:   Thu Mar 19 19:34:08 2009 +0000
>    powerpc/mm: Tweak PTE bit combination definitions
>    This patch tweaks the way some PTE bit combinations are defined, in
>    such a way that the 32 and 64-bit variant become almost identical
>    and that will make it easier to bring in a new common pte-* file
>    for the new variant of the Book3-E support.
>    The combination of bits defining access to kernel pages are now
>    clearly separated from the combination used by userspace and the
>    core VM. The resulting generated code should remain identical
>    unless I made a mistake. 
>    Note: While at it, I removed a non-sensical statement related to
>    CONFIG_KGDB in ppc_mmu_32.c which could cause kernel mappings to be
>    user accessible when that option is enabled. Probably something
>    that bitrot. 
>    Signed-off-by: Benjamin Herrenschmidt <benh at>
>:040000 040000 c105fb9641b078f1a8a60c2a7900ca2dd088b364
>e90678246962d7a455aa27ba12814c11cd9b3c22 M      arch

I'm assuming this is the result of a git-bisect run?

Can I also assume you were loading the module on your Warp board?

Ben, have you tested module loads on 4xx since you redid this?


More information about the Linuxppc-dev mailing list