* [Qemu-devel] ARMv6 el + vfp: User Mode signals uncaught target signal 4 (Illegal instruction)
@ 2008-12-05 10:17 Martin Mohring
2008-12-05 11:55 ` Laurent Desnogues
0 siblings, 1 reply; 8+ messages in thread
From: Martin Mohring @ 2008-12-05 10:17 UTC (permalink / raw)
To: qemu-devel; +Cc: Andrew Christian
Hi,
I put together a qemu from recent svn trunk -r 5862.
when running armv6 eabi + vfp binaries in user mode emulation, i get:
qemu: uncaught target signal 4 (Illegal instruction) - exiting
running the same compiled for armv5 eabi + vfp works. I use the binaries
from mojo (mojo.handhelds.org) project, they ported Ubuntu 8.04 to arm.
They also have a compiled version for ARMv6 + VFP, which I wanted to try
in the openSUSE Buildservice.
How do I find out whats wrong? From the source code, I would guess qemu
is implemented up to ARMv7, right?
Cheers,
Martin
Maintainer + Developer OBS / opensuse.org
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] ARMv6 el + vfp: User Mode signals uncaught target signal 4 (Illegal instruction)
2008-12-05 10:17 [Qemu-devel] ARMv6 el + vfp: User Mode signals uncaught target signal 4 (Illegal instruction) Martin Mohring
@ 2008-12-05 11:55 ` Laurent Desnogues
2008-12-05 12:34 ` Riku Voipio
` (2 more replies)
0 siblings, 3 replies; 8+ messages in thread
From: Laurent Desnogues @ 2008-12-05 11:55 UTC (permalink / raw)
To: qemu-devel
On Fri, Dec 5, 2008 at 11:17 AM, Martin Mohring
<martin.mohring@opensuse.org> wrote:
> I put together a qemu from recent svn trunk -r 5862.
>
> when running armv6 eabi + vfp binaries in user mode emulation, i get:
>
> qemu: uncaught target signal 4 (Illegal instruction) - exiting
>
> running the same compiled for armv5 eabi + vfp works. I use the binaries
> from mojo (mojo.handhelds.org) project, they ported Ubuntu 8.04 to arm.
> They also have a compiled version for ARMv6 + VFP, which I wanted to try
> in the openSUSE Buildservice.
You should specify the CPU when launching qemu. Look at "qemu -cpu ?"
output and select the right one. You probably want -cpu arm1136.
> How do I find out whats wrong? From the source code, I would guess qemu
> is implemented up to ARMv7, right?
Yes ARMv7 is in, including NEON.
HTH,
Laurent
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] ARMv6 el + vfp: User Mode signals uncaught target signal 4 (Illegal instruction)
2008-12-05 11:55 ` Laurent Desnogues
@ 2008-12-05 12:34 ` Riku Voipio
2008-12-05 12:35 ` Martin Mohring
2008-12-05 12:35 ` Martin Mohring
2 siblings, 0 replies; 8+ messages in thread
From: Riku Voipio @ 2008-12-05 12:34 UTC (permalink / raw)
To: qemu-devel
On Fri, Dec 05, 2008 at 12:55:52PM +0100, Laurent Desnogues wrote:
> > qemu: uncaught target signal 4 (Illegal instruction) - exiting
> You should specify the CPU when launching qemu. Look at "qemu -cpu ?"
> output and select the right one. You probably want -cpu arm1136.
I've seen some other fall in this pitfall. Is there a specific reason why
linux-user/main.c defaults to on arm to "arm926" instead of "any" as
some other archs do?
--
"rm -rf" only sounds scary if you don't have backups
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] ARMv6 el + vfp: User Mode signals uncaught target signal 4 (Illegal instruction)
2008-12-05 11:55 ` Laurent Desnogues
2008-12-05 12:34 ` Riku Voipio
@ 2008-12-05 12:35 ` Martin Mohring
2008-12-05 12:35 ` Martin Mohring
2 siblings, 0 replies; 8+ messages in thread
From: Martin Mohring @ 2008-12-05 12:35 UTC (permalink / raw)
To: qemu-devel
Laurent Desnogues wrote:
> On Fri, Dec 5, 2008 at 11:17 AM, Martin Mohring
> <martin.mohring@opensuse.org> wrote:
>
>> I put together a qemu from recent svn trunk -r 5862.
>>
>> when running armv6 eabi + vfp binaries in user mode emulation, i get:
>>
>> qemu: uncaught target signal 4 (Illegal instruction) - exiting
>>
>> running the same compiled for armv5 eabi + vfp works. I use the binaries
>> from mojo (mojo.handhelds.org) project, they ported Ubuntu 8.04 to arm.
>> They also have a compiled version for ARMv6 + VFP, which I wanted to try
>> in the openSUSE Buildservice.
>>
>
> You should specify the CPU when launching qemu. Look at "qemu -cpu ?"
> output and select the right one. You probably want -cpu arm1136.
>
I use qemu user mode, and call qemu with host linux kernels binfmt
handler. How do I specify the cpu type there? Or must I compile in the
"default cpu type" somehow?
>
>> How do I find out whats wrong? From the source code, I would guess qemu
>> is implemented up to ARMv7, right?
>>
>
> Yes ARMv7 is in, including NEON.
>
>
I thought that, from looking into the code. I was sure I missed something...
Martin
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] ARMv6 el + vfp: User Mode signals uncaught target signal 4 (Illegal instruction)
2008-12-05 11:55 ` Laurent Desnogues
2008-12-05 12:34 ` Riku Voipio
2008-12-05 12:35 ` Martin Mohring
@ 2008-12-05 12:35 ` Martin Mohring
2008-12-05 12:57 ` Laurent Desnogues
2 siblings, 1 reply; 8+ messages in thread
From: Martin Mohring @ 2008-12-05 12:35 UTC (permalink / raw)
To: qemu-devel
Laurent Desnogues wrote:
> On Fri, Dec 5, 2008 at 11:17 AM, Martin Mohring
> <martin.mohring@opensuse.org> wrote:
>
>> I put together a qemu from recent svn trunk -r 5862.
>>
>> when running armv6 eabi + vfp binaries in user mode emulation, i get:
>>
>> qemu: uncaught target signal 4 (Illegal instruction) - exiting
>>
>> running the same compiled for armv5 eabi + vfp works. I use the binaries
>> from mojo (mojo.handhelds.org) project, they ported Ubuntu 8.04 to arm.
>> They also have a compiled version for ARMv6 + VFP, which I wanted to try
>> in the openSUSE Buildservice.
>>
>
> You should specify the CPU when launching qemu. Look at "qemu -cpu ?"
> output and select the right one. You probably want -cpu arm1136.
>
I use qemu user mode, and call qemu with host linux kernels binfmt
handler. How do I specify the cpu type there? Or must I compile in the
"default cpu type" somehow?
>
>> How do I find out whats wrong? From the source code, I would guess qemu
>> is implemented up to ARMv7, right?
>>
>
> Yes ARMv7 is in, including NEON.
>
>
I thought that, from looking into the code. I was sure I missed something...
Martin
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] ARMv6 el + vfp: User Mode signals uncaught target signal 4 (Illegal instruction)
2008-12-05 12:35 ` Martin Mohring
@ 2008-12-05 12:57 ` Laurent Desnogues
2008-12-05 13:28 ` Martin Mohring
2008-12-05 21:00 ` Martin Mohring
0 siblings, 2 replies; 8+ messages in thread
From: Laurent Desnogues @ 2008-12-05 12:57 UTC (permalink / raw)
To: qemu-devel
On Fri, Dec 5, 2008 at 1:35 PM, Martin Mohring
<martin.mohring@opensuse.org> wrote:
>> You should specify the CPU when launching qemu. Look at "qemu -cpu ?"
>> output and select the right one. You probably want -cpu arm1136.
>>
> I use qemu user mode, and call qemu with host linux kernels binfmt
> handler. How do I specify the cpu type there? Or must I compile in the
> "default cpu type" somehow?
You mean you can't pass command line parameters to qemu?
Then follow Riku Voipio's advice and change in linux_user/main.c
cpu_model = "arm926"; to cpu_model = "any";.
Laurent
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] ARMv6 el + vfp: User Mode signals uncaught target signal 4 (Illegal instruction)
2008-12-05 12:57 ` Laurent Desnogues
@ 2008-12-05 13:28 ` Martin Mohring
2008-12-05 21:00 ` Martin Mohring
1 sibling, 0 replies; 8+ messages in thread
From: Martin Mohring @ 2008-12-05 13:28 UTC (permalink / raw)
To: qemu-devel
Laurent Desnogues wrote:
> On Fri, Dec 5, 2008 at 1:35 PM, Martin Mohring
> <martin.mohring@opensuse.org> wrote:
>
>>> You should specify the CPU when launching qemu. Look at "qemu -cpu ?"
>>> output and select the right one. You probably want -cpu arm1136.
>>>
>>>
>> I use qemu user mode, and call qemu with host linux kernels binfmt
>> handler. How do I specify the cpu type there? Or must I compile in the
>> "default cpu type" somehow?
>>
>
> You mean you can't pass command line parameters to qemu?
> Then follow Riku Voipio's advice and change in linux_user/main.c
> cpu_model = "arm926"; to cpu_model = "any";.
>
I have seen his e-mail (too late). I am compiling my new qemu already,
with new default cpu type for arm.
Martin
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] ARMv6 el + vfp: User Mode signals uncaught target signal 4 (Illegal instruction)
2008-12-05 12:57 ` Laurent Desnogues
2008-12-05 13:28 ` Martin Mohring
@ 2008-12-05 21:00 ` Martin Mohring
1 sibling, 0 replies; 8+ messages in thread
From: Martin Mohring @ 2008-12-05 21:00 UTC (permalink / raw)
To: qemu-devel
Laurent Desnogues wrote:
> On Fri, Dec 5, 2008 at 1:35 PM, Martin Mohring
> <martin.mohring@opensuse.org> wrote:
>
>>> You should specify the CPU when launching qemu. Look at "qemu -cpu ?"
>>> output and select the right one. You probably want -cpu arm1136.
>>>
>>>
>> I use qemu user mode, and call qemu with host linux kernels binfmt
>> handler. How do I specify the cpu type there? Or must I compile in the
>> "default cpu type" somehow?
>>
>
> You mean you can't pass command line parameters to qemu?
> Then follow Riku Voipio's advice and change in linux_user/main.c
> cpu_model = "arm926"; to cpu_model = "any";.
>
I followed your advise, and put cpu_model = "any"; in. Tnx for the fast
help.
It works fine now. Do you think it would make sense to make this default
for user mode / arm ?
Martin
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2008-12-05 21:00 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-12-05 10:17 [Qemu-devel] ARMv6 el + vfp: User Mode signals uncaught target signal 4 (Illegal instruction) Martin Mohring
2008-12-05 11:55 ` Laurent Desnogues
2008-12-05 12:34 ` Riku Voipio
2008-12-05 12:35 ` Martin Mohring
2008-12-05 12:35 ` Martin Mohring
2008-12-05 12:57 ` Laurent Desnogues
2008-12-05 13:28 ` Martin Mohring
2008-12-05 21:00 ` Martin Mohring
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).