Page Fault on real hardware
whowe123 at yahoo.com
Mon Oct 29 11:24:55 CET 2012
thank you very much for your fast reply. I have checked once again the boot parameters for kernel and here is the line to boot up the linux:
"rom/vmlinuz.android mem=256M console=ttyLv0 ramdisk=rom/rootfs.tar.gz root=1:0 ramdisk_size=32768 l4x_rd=rom/rootfs.tar.gz init=/etc/preinit");
In other words, the console parameter is already set as you pointed out. However, I will try the gdb/objdump option and inform you about it if I might successfully test it with gdb/objdump.
From: Adam Lackorzynski <adam at os.inf.tu-dresden.de>
To: l4-hackers at os.inf.tu-dresden.de
Sent: Friday, October 26, 2012 7:44 PM
Subject: Re: Page Fault on real hardware
On Thu Oct 25, 2012 at 09:18:30 -0700, Wajidali Whowe wrote:
> I have been trying to run L4linux on a real hardware (x86 PC). Everything seems fine once I try the image with the qemu, however the following error appears on the real hardware:
> vmlinuz . | main thread will be 413
> vmlinuz . | l4x_register_pointer_section: addr = 005e6000 size 929792
> vmlinuz . | section-with-init: virt: 0x5e6000 to 0x6c8fff [908KiB]
> vmlinuz . | section-with-init: virt: ....
> vmlinuz . | Loading: rom/ramdiskfs.tar.gz
> vmlinuz . | INITRD: Size of RAMdisk is 32768KiB
> vmlinuz . | RAMdisk from 188800000 to 1a800000 [32768KiB]
> vmlinuz . | Page fault (non-resolved): pfa=0 pc=473569
> Die message: Trap: 14
> vmlinuz . | panic: going to sleep forever, bye
> Would you please have an idea or a suggestion for this problem?
Do you have console=ttyLv0 on the linux command line? That would
probably give an ooops-printout with much more info, given it is already
that far in booting up that this works. Alternatively you can check with
gdb/objdump of vmlinux what's at and around 0x473569 to figure out
what's going on.
Adam adam at os.inf.tu-dresden.de
l4-hackers mailing list
l4-hackers at os.inf.tu-dresden.de
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the l4-hackers