Re: rumpbake support for baked-in rootfs

  • From: Antti Kantee <pooka@xxxxxx>
  • To: rumpkernel-users@xxxxxxxxxxxxx
  • Date: Wed, 10 Jun 2015 09:35:16 +0000

On 10/06/15 06:09, Andrew Stuart wrote:

I’ll try now to hook that into the code as you suggest.

OK I’m still doing something wrong here because my kernels are not booting on
EC2. Any clues as to what I could try next?

mounted tmpfs on /tmp
Page fault at linear address 0x0, rip 0x198a4e, regs 0x6a33fe28, sp 0x6a33fed0,
our_sp 0x6a33fe10, code 0
Thread: main
RIP: e030:[<0000000000198a4e>]
RSP: e02b:000000006a33fed0 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000000000000a
RDX: 00000000003df480 RSI: 0000000000000000 RDI: 000000000020be43
RBP: 0000000000000000 R08: 0000000001202000 R09: 0000000001221ff0
R10: 0000000000fcf5d0 R11: 0000000000fd6e00 R12: 0000000000000000
R13: 000000206c404d20 R14: 0000000000001802 R15: 0000000000000000
base is 0 Page fault in pagetable walk (access to invalid memory?).

Try a debugger. You can find out which bit of code is running into a null pointer by loading up the baked binary into gdb and typing "l *0x198a4e" (just loading, no need to run it). After we know which code is running into trouble, it's easier to figure out what's wrong.

Other related posts: