Re: [Xenomai-help] NMI watchdog: Loading of xeno_native leads...

[Jan Kiszka <jan.kiszka@domain.hid>]

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

M. Koehrer wrote:
> Hi!
> 
> It was the compiler!!! Using gcc-3.3 solved the issue.
> That means, that somehow gcc-4.1.2 must not be used with Xenomai currently...

OK, this needs some examination then. Can anyone reproduce this issue?
/me is currently lacking the compiler.

>  
> This allowed me to catch the system hang I was hunting for since yesterday...
> And I got it.
> I write the information I found on the console (I have not tried with console redirection yet...).
> CPU 0, eip c010122d
> EIP 0060:[<c010122d>]
> EFLAGS 00000246
> EIP is at mwait_idle_with_hints+0x2c/0x2e
> eax:0 ebx:c0498000 ecx:0 edx:0
> 
> Call Trace
> mwait_idle+0x0/0x2e
> mwait_idle+0x1d/0x2e
> cpu_idle+0x44/0x86
> start_kernel+0x1f1/0x1f5
> unknown_bootoption+0x0/0x191

Well, this caught your box in the idle loop - not that informative yet.
We must probably look beyond the last context switch. Please switch on
the I-pipe tracer (kernel hacking -> I-pipe debugging) and configure
back_trace_points to, hmm, say 200. On NMI alarm, we should then see a
function call trace.

> 
> I'll try to reproduce the same with console redirection, however, I hope this could help already!
> 
> Regards
> 
> Mathias

Thanks for your effort,

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]