Run time fault 'Internal Panick'

[mike_rink]

Hi All,

Does anyone know what the following error is?

HLH: Internal Panick Task 26, double fault from 0x100DE6FA

I know that it has something to do with the High Level Interrupt. Can anyone shed more light on this?
I am running 7.50.0.A2 on a Q2698.

Thanks.

[Rex_alex]

Hi,

Not seen such error…
anyways… What exactly are you trying to do in the application ?

[awneil]

@mike_rink

HLH: Internal Panick Task 26, double fault from 0x100DE6FA

I think “Panick” i[/i] is a cutesy Linux-speak for “Fatal Error”

@Wikipedia

On the x86 architecture, a double fault exception occurs if the processor encounters a problem while trying to service a pending interrupt or exception.

en.wikipedia.org/wiki/Double_fault

In other words, it’s encountered an error in a state (HLH?) where it can’t handle the error - so it just has to crash

Sorry that doesn’t get you anywhere with solving the problem…

[awneil]

@I

I think “Panick” i[/i] is a cutesy Linux-speak for “Fatal Error”

@Wikipedia

A kernel panic is an action taken by an operating system upon detecting an internal fatal error from which it cannot safely recover. The term is largely specific to Unix and Unix-like systems; for Microsoft Windows operating systems the equivalent term is “bug check” (or, colloquially, “Blue Screen of Death”).

en.wikipedia.org/wiki/Kernel_panic

I think I’d start by checking pointers & memory allocation first…

Also note that doing a lot of Tracing in the Interrupt Handlers can be a Bad Thing…

Remember that the Interrupt Handlers are “Special” and have many restrictions on what you can do in them…

[mike_rink]

Thanks for your comments, guys.

I wrote OAT software that ran perfectly on a Q2686. I then changed the module to a Q2698 and re-compiled the software using V7.50.0.A2 suite and ran it. The error occured pretty much near the start of the software, so there must be a subtle difference between the two modules that prevented the OAT software running error free. Any ideas to look for would be welcome. I will check out the memory ideas that awneil suggested.

Thanks,
Mike