On 07/11/2013 04:55 PM, Helmut Schaa wrote:
On Wed, Jul 10, 2013 at 2:19 PM, John Crispin <[email protected]> wrote:
On 10/07/13 14:17, Helmut Schaa wrote:
On Tue, Jul 9, 2013 at 2:34 PM, Helmut Schaa
<[email protected]> wrote:
On Tue, Jul 9, 2013 at 2:19 PM, John Crispin<[email protected]> wrote:
ok, i just started a build for a qemu image ....
Thanks, I'm not entirely sure if it is 100% reproducible.
Rebooting again gave me a working ubusd again.
Sorry for the noise, I'm not able to reproduce this issue anymore.
Helmut
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Hi Helmut,
its not really noise ... you are the 3rd person to have seen this
sporadically. i believe there is a weird race condition or similar.
unfortunatley i have so far not seen it myself. i hope we will eventually
track it down, it only happens very rarely it seems :-(
Ok, I'll keep my eyes open if it happens again ...
Helmut
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Hi,
If i complied -march=atom (Target Options -O2 -pipe -march=atom
-fno-caller-saves) i got "ubus x86: Failed to connect to ubus".
When i tried to run ubusd i see illegal instruction error.
This "-O2 -pipe -march=i686 -fno-caller-saves" is okay. No problem.
Thanks for your time and jobs.
Remzi
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
