qemu again :(

qemu again :(

[Steffen Sledz]

Yesterday i tried to use OE at my new notebook for the first time. But
i hit a qemu problem again:

# bitbake emacs (clean build)

ERROR: function do_compile failed
ERROR: log data follows
(/home/sledz/work/HydraIP/OE/tmp.4/work/armv5te-angstrom-linux-gnueabi/emacs-22.3-r1/temp/log.do_compile.8552)
| NOTE: make -j 8 QEMU=qemu-arm  -s 1048576 -L
/home/sledz/work/HydraIP/OE/tmp.4/work/armv5te-angstrom-linux-gnueabi/emacs-22.3-r1/qemu-treedir
...
| mmap: Permission denied
| make[1]: *** [test-distrib] Error 255

All solutions for this problem i found see the cause in a wrong
setting of mmap_min_addr (see e.g.
<http://www.bugcommunity.com/wiki/index.php/Kernel_and_Rootfs_Build_System#Potential_Problems_.26_Their_Solutions:>).

But this setting is correct at my notebook:

# cat /proc/sys/vm/mmap_min_addr
0

Hmmmm? What else could be the cause for this error?

Steffen

Re: qemu again :(

[Robert P. J. Day]

On Wed, 4 Nov 2009, Steffen Sledz wrote:

> Yesterday i tried to use OE at my new notebook for the first time. But
> i hit a qemu problem again:
>
> # bitbake emacs (clean build)
>
> ERROR: function do_compile failed
> ERROR: log data follows
> (/home/sledz/work/HydraIP/OE/tmp.4/work/armv5te-angstrom-linux-gnueabi/emacs-22.3-r1/temp/log.do_compile.8552)
> | NOTE: make -j 8 QEMU=qemu-arm  -s 1048576 -L
> /home/sledz/work/HydraIP/OE/tmp.4/work/armv5te-angstrom-linux-gnueabi/emacs-22.3-r1/qemu-treedir
> ...
> | mmap: Permission denied
> | make[1]: *** [test-distrib] Error 255
>
> All solutions for this problem i found see the cause in a wrong
> setting of mmap_min_addr (see e.g.
> <http://www.bugcommunity.com/wiki/index.php/Kernel_and_Rootfs_Build_System#Potential_Problems_.26_Their_Solutions:>).
>
> But this setting is correct at my notebook:
>
> # cat /proc/sys/vm/mmap_min_addr
> 0
>
> Hmmmm? What else could be the cause for this error?

  i suspect koen will hate me for this but i documented what it took
for me to build angstrom over at my wiki:

http://www.crashcourse.ca/wiki/index.php/Angstrom

and if you read carefully, you'll notice that even if that value is
correctly set to zero, you might still get an SELinux violation.  it's
just a suggestion.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================

Re: qemu again :(

[Steffen Sledz]

Robert P. J. Day wrote:
>> Yesterday i tried to use OE at my new notebook for the first time. But
>> i hit a qemu problem again:
>> ...
>> | mmap: Permission denied
>>
>> All solutions for this problem i found see the cause in a wrong
>> setting of mmap_min_addr (see e.g.
>> <http://www.bugcommunity.com/wiki/index.php/Kernel_and_Rootfs_Build_System#Potential_Problems_.26_Their_Solutions:>).
>>
>> But this setting is correct at my notebook:
>>
>> # cat /proc/sys/vm/mmap_min_addr
>> 0

> ...
> and if you read carefully, you'll notice that even if that value is
> correctly set to zero, you might still get an SELinux violation.  it's
> just a suggestion.

Thanx for the hint, but there's no SELinux (and no Apparmor) running.

Steffen

Re: qemu again :(

[Marc Olzheim]

[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]

On Thu, Nov 05, 2009 at 10:29:32AM +0100, Steffen Sledz wrote:
> >> Yesterday i tried to use OE at my new notebook for the first time. But
> >> i hit a qemu problem again:
> >> ...
> >> | mmap: Permission denied
> >>
> >> All solutions for this problem i found see the cause in a wrong
> >> setting of mmap_min_addr (see e.g.
> >> <http://www.bugcommunity.com/wiki/index.php/Kernel_and_Rootfs_Build_System#Potential_Problems_.26_Their_Solutions:>).
> >>
> >> But this setting is correct at my notebook:
> >>
> >> # cat /proc/sys/vm/mmap_min_addr
> >> 0
> 
> > ...
> > and if you read carefully, you'll notice that even if that value is
> > correctly set to zero, you might still get an SELinux violation.  it's
> > just a suggestion.
> 
> Thanx for the hint, but there's no SELinux (and no Apparmor) running.

I have the same problem on Ubuntu 9.10 (karmic).
When I pass -r 2.6.18 or lower to qemu though, the qemu hangs itself and
will never finish. With -r 2.6.19 and up, it gives me the "mmap: No such
device or address" message.

Did you find a solution in the mean time ?

Marc

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: qemu again :(

[Steffen Sledz]

Marc Olzheim wrote:
> I have the same problem on Ubuntu 9.10 (karmic).
> When I pass -r 2.6.18 or lower to qemu though, the qemu hangs itself and
> will never finish. With -r 2.6.19 and up, it gives me the "mmap: No such
> device or address" message.
> 
> Did you find a solution in the mean time ?

No, sorry. Problem is still pending.  :(

Steffen