Re: 2.6.6-mm1

[Andrew Morton]

Sid Boyce <sboyce@xxxxxxxxxxxxxxxx> wrote:
>
> Oops on x86_only, x86_64 is OK.
> 
> ...
> Unable to handle kernel NULL pointer dereference at virtual address 00000000
> printing eip:
> c0163921
> *pde = 00000000
>  Oops: 0000 [#1]
>  PREEMPT DEBUG_PAGEALLOC
>  CPU:    0
>  EIP:    0060:[<c0163921>]    Not tainted VLI
>  EFLAGS: 00010296   (2.6.6-mm1) 
>  EIP is at locks_alloc_lock+0x1/0x20
>  eax: de016f6c   ebx: bffff1e0   ecx: bffff1e0   edx: 00000007
>  esi: bffff1e0   edi: 00000000   ebp: dff7bf90   esp: dff7bf34
>  ds: 007b   es: 007b   ss: 0068
>  Process init (pid: 1, threadinfo=dff7b000 task=dff7ca70)
>  Stack: dff7bf90 c0165856 00000000 00000246 fffbd13f fffbd13f 00000007 de016f6c 
>         dff7bf94 c011a52c ffffffff 000001ff bffff008 fa49babf 00000000 003fffff 
>         00000000 fffbd13f dff7bf9c dff7bfac bffff1e0 ffffffea 00000000 dff7bfa4 
>  Call Trace:
>   [<c01061e6>] show_stack+0xa6/0xb0
>   [<c0106358>] show_registers+0x148/0x1c0
>   [<c0106505>] die+0xa5/0x110
>   [<c0112682>] do_page_fault+0x3b2/0x538
>   [<c0105e55>] error_code+0x2d/0x38
>   [<c01618a5>] generic_file_fcntl+0xd5/0x1e0
>   [<c0161ae0>] sys_fcntl64+0x80/0xa0
>   [<c0105c4b>] syscall_call+0x7/0xb

Is this repeatable?  A null-pointer deref at
locks_alloc_lock+0x1/0x20 seems not possible.

Please send the output of

	nm -n vmlinux | grep -5 locks_alloc_lock


-
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/