RE: ARM with Qemu
"Nicolas VARONA" <[email protected]>
| Newsgroups | gmane.comp.micro-kernel.l4.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi,
>Ok. Lets look deeper. [...] What do we see?
I have done the test on both the board and Qemu.
On Qemu, I can see those lines:
jdb: T
5% of 32768 Perf:ACor 1=00000000(:e0) index
2=00000000(:e0)
vcpu: 003e exc #11 err=44000000 pc=132cd8 sp=bfbb9c88 state=2f task 1781
vcpu: 003e ret pc=ae3c sp=bfbb9aec state=2f task=D:4c 1780
vcpu: 003e exc #11 err=44000000 pc=b1bc sp=bfbb9c44 state=2f task=D 1779
vcpu: 003e ret pc=b24c sp=bfbb9c2c state=2f task=D:4d 1778
vcpu: 003e exc #11 err=44000000 pc=b24c sp=bfbb9c2c state=2f task=D 1777
vcpu: 003e ret pc=e920 sp=bfbb9c60 state=2f task=D:4d 1776
vcpu: 003e pf pc=e920 pfa=e920 err=80000007 state=2f task=D:4d 1775
vcpu: 003e ret pc=14edd4 sp=bfbb9bc8 state=2f task=D:4d 1774
vcpu: 003e exc #11 err=44000000 pc=14edd4 sp=bfbb9bc8 state=2f task 1773
vcpu: 003e ret pc=dbf0 sp=bfbb9c08 state=2f task=D:4d 1772
vcpu: 003e pf pc=dbf0 pfa=dbf0 err=80000007 state=2f task=D:4d 1771
vcpu: 003e ret pc=127850 sp=bfbb9bd0 state=2f task=D:4d 1770
vcpu: 003e pf pc=127850 pfa=127850 err=80000007 state=2f task=D:4d 1769
vcpu: 003e ret pc=14ee48 sp=bfbb9bd0 state=2f task=D:4d 1768
vcpu: 003e exc #11 err=44000000 pc=b1bc sp=bfbb9c44 state=2f task=D 1767
vcpu: 003e ret pc=b24c sp=bfbb9c2c state=2f task=D:50 1766
vcpu: 003e exc #11 err=44000000 pc=b24c sp=bfbb9c2c state=2f task=D 1765
vcpu: 003e ret pc=b230 sp=bfbb9c30 state=2f task=D:50 1764
vcpu: 003e pf pc=b230 pfa=b230 err=80000007 state=2f task=D:50 1763
vcpu: 003e ret pc=e920 sp=bfbb9c60 state=2f task=D:50 1762
vcpu: 003e pf pc=e920 pfa=e920 err=80000007 state=2f task=D:50 1761
[...]
On the Board I have those:
jdb: T
0% of 32768 Perf:ACor 1=00000000(:e0) index
2=00000000(:e0)
vcpu: 003e pf pc=fb86c pfa=bf5b3030 err=90000007 state=2f task=D:4 30
vcpu: 003e ret pc=fb850 sp=bf5b2ee8 state=2f task=D:44 29
vcpu: 003e pf pc=fb850 pfa=fb850 err=80000007 state=2f task=D:44 28
vcpu: 003e ret pc=c4d0 sp=bf5b2ef4 state=2f task=D:44 27
vcpu: 003e pf pc=c4d0 pfa=bf5b2ef0 err=9000084f state=2f task=D:44 26
vcpu: 003e ret pc=c4c8 sp=bf5b2ef0 state=2f task=D:44 25
vcpu: 003e pf pc=c4c8 pfa=bf5b2ef0 err=90000005 state=2f task=D:44 24
vcpu: 003e ret pc=c4c0 sp=bf5b2ef0 state=2f task=D:44 23
vcpu: 003e pf pc=c4c0 pfa=c4c0 err=80000005 state=2f task=D:44 22
vcpu: 003e ret pc=c4c0 sp=bf5b2ef0 state=27 task=D:44 21
vcpu: 003e ret pc=21581d0 sp=5c2787c state=5 task=D:34 20
vcpu: 003e ipc from D:41 task=D:5 sp=5c2787c 19
vcpu: 003e ret pc=2151e38 sp=5c27d44 state=5 task=D:34 18
vcpu: 003e ipc from D:41 task=D:5 sp=5c27d44 17
vcpu: 003e ret pc=208e8c8 sp=5c27e90 state=5 task=D:34 16
vcpu: 003e ipc from D:41 task=D:5 sp=5c27e90 15
vcpu: 003e ret pc=20dcdbc sp=5c27db8 state=5 task=D:34 14
vcpu: 003e ipc from D:41 task=D:5 sp=5c27db8 13
vcpu: 003e ret pc=2157a8c sp=5c27c9c state=5 task=D:34 12
vcpu: 003e ipc from D:41 task=D:5 sp=5c27c9c 11
vcpu: 003e ret pc=2153cd8 sp=5c27d30 state=5 task=D:34 10
[...]
>Hmm, maybe lets first look at the segfault, maybe it's related but probably not.
It's strange because all seem to be well enabled and I have the same segfault. I give you the output with the configuration file we tested last time:
[...]
Freeing unused kernel memory: 116K (0230f000 - 0232c000)
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
CPU: 0 PID: 1 Comm: init Not tainted 3.16.0-l4 #45
[<0200caa0>] (unwind_backtrace) from [<020055e8>] (show_stack+0x10/0x14)
[<020055e8>] (show_stack) from [<022441e4>] (panic+0x7c/0x1e0)
[<022441e4>] (panic) from [<0201e6d4>] (do_exit+0x708/0x7a0)
[<0201e6d4>] (do_exit) from [<0201e838>] (do_group_exit+0x3c/0x9c)
[<0201e838>] (do_group_exit) from [<020283bc>] (get_signal_to_deliver+0x148/0x490)
[<020283bc>] (get_signal_to_deliver) from [<02006be8>] (do_signal+0x114/0x448)
[<02006be8>] (do_signal) from [<02006fc4>] (do_work_pending+0xa8/0xf8)
[<02006fc4>] (do_work_pending) from [<02008970>] (l4x_pre_iret_work.isra.24.part.25+0x60/0x100)
[<02008970>] (l4x_pre_iret_work.isra.24.part.25) from [<020099f0>] (l4x_vcpu_entry_c+0x274/0x1da8)
[<020099f0>] (l4x_vcpu_entry_c) from [<0000c4ec>] (0xc4ec)
---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
panic: going to sleep forever, bye
vmlinuz.| panic: going to sleep forever, bye
Thanks in advance for your help,
Nicolas
-----Message d'origine-----
De : l4-hackers [mailto:[email protected]] De la part de Adam Lackorzynski
Envoyé : jeudi 19 mars 2015 23:47
À : [email protected]
Objet : Re: ARM with Qemu
Hi,
On Wed Mar 18, 2015 at 10:26:46 +0100, Nicolas VARONA wrote:
> >Other issue could be a missing CONFIG_AEABI.
>
> Thanks for your reply and your time. Nonetheless the CONFIG_AEABI is enabled in L4linux:
Ok. Lets look deeper. Fiasco's debugger has a tracebuffer, we'll use it
to find out more. Please make sure 'extended logging' is enabled in
Fiasco's config. Then, before it happens, enter the jdb, shift-O will
show a selection menu. Enable 'VCPU events' (via return). Let it run
further (via 'g'). Then, enter jdb again, shift-T will show up the
tracebuffer, latest entry is on the top. What do we see?
> >But I suppose you tried that already?
>
> I have already tried the configuration file this way with the same result (I can reach the end of the boot but I have no input and I can enter into the jdb in Qemu).
Hmm, maybe lets first look at the segfault, maybe it's related but
probably not.
Adam
--
Adam [email protected]
Lackorzynski http://os.inf.tu-dresden.de/~adam/
_______________________________________________
l4-hackers mailing list
[email protected]
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers