2009-03-05 09:51:46     Miss stack trace and back trace on kernel exception

2009-03-05 09:51:46     Miss stack trace and back trace on kernel exception

der knut (GERMANY)

Message: 70450   

Hello,

as I described at

http://blackfin.uclinux.org/gf/project/uclinux-dist/forum/?action=ForumBrowse&forum_id=39&forum_threadsort_by=most_recent_date&forum_threadsort_order=desc&_forum_action=ForumMessageBrowse&thread_id=32758

I have to switch off MPU to can run our app.

Now I get no further debug information just "Restarting System" and system stops. As I read the code the kernel recognized that something bad happened, but do not call the stack/back trace print out.

How can switch on stack/back trace again?

At .config I activate

#

# Kernel hacking

#

....

CONFIG_DEBUG_HUNT_FOR_ZERO=y

CONFIG_ACCESS_CHECK=y

....

I tried to swittch of syslog and do "echo 9 > /proc/sys/kernel/printk" but no further output on console.

Thanks a lot

Knut

TranslateQuoteReplyEditDelete

2009-03-05 12:56:43     Re: Miss stack trace and back trace on kernel exception

Mike Frysinger (UNITED STATES)

Message: 70458   

post the exact kernel output you're seeing ... i dont really understand what you're trying to describe

QuoteReplyEditDelete

2009-03-05 13:43:36     Re: Miss stack trace and back trace on kernel exception

der knut (GERMANY)

Message: 70462   

Hello,

just as I wrote. "Restarting System" is the only poutput I can see.

I used to a lot of stack and back trace information as I wrote in the original post.

What must be enabled to see stack/back trace on exception if MPU is disabled?

Thanks a lot

Knut

TranslateQuoteReplyEditDelete

2009-03-05 15:24:32     Re: Miss stack trace and back trace on kernel exception

Mike Frysinger (UNITED STATES)

Message: 70469   

then i really havent a clue what you're doing or what you're seeing

the message "Restarting System" only shows up when you run `reboot` ... and if you're rebooting, it makes no sense at all to see a crash message