Re: pvgrub crashing after selecting kernel to boot

[Jeremy Fitzhardinge <jeremy@goop.org>]

On 03/03/2010 04:32 PM, Jeremy Fitzhardinge wrote:
> I've also started seeing crashes on 64-bit pvgrub after selecting the 
> kernel to boot:
>
> Thread "kbdfront close": pointer: 0x2020004580, stack: 0xcf0000
> close fb: backend at /local/domain/0/backend/vfb/1/0
> close kbd: backend at /local/domain/0/backend/vkbd/1/0
> shutdown_kbdfront: error changing state to 5: ENOENT
> Thread "kbdfront close" exited.
> Page fault at linear address 0x100953340, rip 0x4b768, regs 0xcdfa68, 
> sp 0xcdfb18, our_sp 0xcdfa20, code 2
> Thread: main
> RIP: e030:[<000000000004b768>]
extras/mini-os/mm.c:276

> RSP: e02b:0000000000cdfb18  EFLAGS: 00010293
> RAX: 0000000000e2e000 RBX: 0000000000cdfb98 RCX: 0000000100953338
> RDX: 0000000000000001 RSI: 0000000000953188 RDI: 0000000000000000
> RBP: 0000000000cdfb28 R08: 0000000100953338 R09: 0000000000e2c000
> R10: 00000000deadbeef R11: 0000000000200030 R12: 0000000000000003
> R13: 0000002020305018 R14: 0000000000000000 R15: 0000000000002000
> base is 0xcdfb28 caller is 0x57cbd
extras/mini-os/arch/x86/traps.c:147

> base is 0xcdfb88 caller is 0x3067
??:0
> base is 0xcdfc88 caller is 0x5c1b3
stubdom/newlib-x86_64/x86_64-xen-elf/newlib/libc/stdlib/../../../../../newlib-1.16.0/newlib/libc/stdlib/mallocr.c:2947

> base is 0xcdfcd8 caller is 0x5be0a
stubdom/newlib-x86_64/x86_64-xen-elf/newlib/libc/stdlib/../../../../../newlib-1.16.0/newlib/libc/stdlib/realloc.c:19

> base is 0xcdfcf8 caller is 0x3db6
stubdom/grub/mini-os.c:165

> base is 0xcdfd38 caller is 0x402e
stubdom/grub/mini-os.c:187

> base is 0xcdfd58 caller is 0x8341
stubdom/grub/../grub-upstream/stage2/builtins.c:2713

> base is 0xcdfd98 caller is 0xaa2f
stubdom/grub/../grub-upstream/stage2/cmdline.c:256


> base is 0xcdfdd8 caller is 0x108ca
stubdom/grub/../grub-upstream/stage2/stage2.c:769


> base is 0xcdfe88 caller is 0x10f62
stubdom/grub/../grub-upstream/stage2/stage2.c:1121


> base is 0xcdff48 caller is 0x4343
stubdom/grub/mini-os.c:763

> base is 0xcdff58 caller is 0x4b48a
extras/mini-os/main.c:162

> base is 0xcdffe8 caller is 0x33da
gdtoa-hexnan.c:0
>
> cdfb00: 18 fb cd 00 00 00 00 00 2b e0 00 00 00 00 00 00
> cdfb10: 20 18 5a bb 00 00 00 00 25 40 98 33 01 00 00 00
> cdfb20: 98 fb cd 00 00 00 00 00 88 fb cd 00 00 00 00 00
> cdfb30: bd 7c 05 00 00 00 00 00 25 40 98 33 01 00 00 00
>
> cdfb10: 20 18 5a bb 00 00 00 00 25 40 98 33 01 00 00 00
> cdfb20: 98 fb cd 00 00 00 00 00 88 fb cd 00 00 00 00 00
> cdfb30: bd 7c 05 00 00 00 00 00 25 40 98 33 01 00 00 00
> cdfb40: 38 18 5a bb 00 00 00 00 03 00 00 00 01 00 00 00
>
> 4b750: f2 b9 80 31 95 00 48 8b 04 f1 4c 8b 00 4c 89 04
> 4b760: f1 48 8b 08 48 8b 70 08 48 89 71 08 39 d7 74 49
> 4b770: be 01 00 00 00 41 b8 80 31 95 00 83 ea 01 8d 4a
> 4b780: 0c 48 89 f3 48 d3 e3 4c 8d 0c 18 41 89 51 10 4c
> Pagetable walk from virt 100953340, base a9c000:
>  L4 = 00000000bf570067 (0xa9d000)  [offset = 0]
>   L3 = 0000000000000000 (0xfffffffffffff000)  [offset = 4]
> Page fault in pagetable walk (access to invalid memory?).
>

> Please addr2line these callers and the crash IP

I'm disappointed you can't just intuit it.

     J