Page Fault on real hardware
Matthias Lange
mlange at sec.t-labs.tu-berlin.de
Mon Oct 29 18:12:49 CET 2012
On Mon, Oct 29, 2012 at 09:54:40AM -0700, Wajidali Whowe wrote:
> Dear all,
>
> I also tried the x86-mp_vPCI_defconfig and x86-native_defconfig (For both of them I only deactivated PMEM support) and now they resulted in the following outputs, where the PC might also not be seen, i.e. there is no page fault but the Trap 13:
> ..
> ..
> vmlinuz . | main thread will be 414
> vmlinuz . | l4x_register_pointer_section: addr = 006a8000 size = 2072576
> vmlinuz . | section-with-init: virt: 0x6a8000 to 0x8a1fff [2024KiB]
> vmlinuz . | section-with-init: Phys: ....
> ..
> ..
> vmlinuz . | Loading: rom/ramdiskfs.tar.gz
> vmlinuz . | INITRD: Size of RAMdisk is 32768KiB
> vmlinuz . | RAMdisk from 18c000000 to 1ac00000 [32768KiB]
> Die message: Trap: 13
> vmlinuz . | panic: going to sleep forever, bye
>
>
> Would it be possible to find out the specific definitions for the Traps? For instance does Trap number (in our case 13) tell about the reasons?
Yes. Trap #13 on x86 is a general protection fault. See Intel's IA-32 Software
Developer Manual 3A, chapter 6 for more details.
Matthias.
--
Dipl.-Inf. Matthias Lange <mlange at sec.t-labs.tu-berlin.de>
Security in Telecommunications
TU Berlin / Telekom Innovation Laboratories
Ernst-Reuter-Platz 7, 10587 Berlin
Phone: +49 - 30 - 8353 58 553
Mobile: +49 - 160 - 587 28 07
Web: http://www.t-labs.tu-berlin.de/sect
More information about the l4-hackers
mailing list