On 01/13/2013 05:36 AM, John Morris wrote:
> On 01/12/2013 11:31 AM, Gilles Chanteperdrix wrote:
>> On 01/12/2013 06:26 PM, John Morris wrote:
>>> 1) Most worrisome is "kernel BUG at mm/mmap.c:2313! invalid opcode:
>>> 0000 [#2] SMP". Is this related to HEAPSZ or STACKPOOLSZ? My mind is
>>> getting foggy about all the things I've seen, but it seems like it was
>>> happening earlier in the tests until these config values were quadrupled.
>>
>>
>> Could you check whether you can reproduce this issue with the I-pipe
>> patch for 3.5.7 ? The next xenomai release will be based on this version
>> on x86 anyway. Branch for-core-3.5.7 in ipipe-gch.git
>
> Different problem; Xenomai wouldn't start:
>
> I-pipe: could not find timer for cpu #0
>
> dmesg:
> http://www.zultron.com/static/2013/01/xenomai/3.5.7-test/foo-dmesg-3.5.7.log
>
> .config:
> www.zultron.com/static/2013/01/xenomai/3.5.7-test/foo-kernel-3.5.7.config
>
> FYI, I found this same problem on two of my systems while testing your
> Debian packages. Both AMD Athlon II 64-bit (one single, one dual core).
> They're about the same generation of motherboards, AM2 or AM2+ socket.
> One is AMD 770 chipset, the other NVidia GeForce 6100 / nForce 430.
>
> Hardware looks similar to Mariusz's in this post, where he had the same
> problem:
>
> http://www.xenomai.org/pipermail/xenomai/2012-December/027121.html
>
> He's also running AMD 64-bit on a Gigabyte motherboard, but the next
> generation AM3 socket, Phenom CPU, AMD 890 chipset. I don't have a C1E
> BIOS option on these boards to enable/disable. These same motherboards
> don't suffer this problem with mainline Xenomai on 3.5.3.
If you had the same problem as Marius, you would have seen it with
3.5.3, and you would get the message in the dmesg about C1E, so, it is
probably something else. Could you run
cat /proc/timer_list
?
--
Gilles.
_______________________________________________
Xenomai mailing list
[email protected]
http://www.xenomai.org/mailman/listinfo/xenomai
