• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 314 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/DRA76P: make kernel continue after panic

user5119143
Prodigy 20 points

Part Number: DRA76P

Tool/software: Linux

Hi all,

Our project adapt J6P(Dra76x) processor, with kernel 4.4.84. Our development boards' sound subsystem receive external reference clock as clock source.  By coincidence we found if the clock lose, kernel will panic and cycles most times while probe davinci_mcasp_probe and invoke __pm_runtime_idle, but occasionally kernel be able to pass the ridge and boot system success. In order to explicit the phenomenon, we 

cut off the reference clock line in hardware and found kernel can boot up indeed. 

So could anybody explain why it is, why kernel panic and cycles and why sometimes kernel can go over with just some warnings. Thanks. 

  • 0
    TI__Expert 8250 points

    Hi

    Any unexpected condition in the kernel code (drivers, kernel sub systems) would be handled as either a warning condition(when recoverable, but still warrant user attention) or as unrecoverable panic() condition (system cannot proceed, and in some cases you would want to dump kernel memory using debug tools to analyze what happened, continuing execution not possible/desirable in such cases)

    The kernel back traces should give you an indication on the call stack and what part of the system was triggering the condition