Atit_Shah <Atit_Shah at satyam.com> wrote? > 1. Check your log buffer...your console may not be > initialized yet so all your printk are logged at a > particular memory location. Checkout the > System.map file in the Linux folder for "log_buf". > The address that you have there subtract it with > the kernel base address. Then in view your > memory at that location. We used U-Boot so we gave > the command > > md <log_buff address>
Interesting to me as well. I also have such a similar problem. But I wanna to know how I can return to u-boot with software workaround after kernel hanging. At least, I must power-off and power-on my target to get back to u-boot console. If so, the last kernel printk message would lost IMHO. Thanks, Sam P.S. Atit_Shah, if possibel, pls set your subscribing setting "...daily digest" as "no" to avoid reply inconvenience on the title:) _________________________________________________________ Do You Yahoo!? 150??MP3???????????? http://music.yisou.com/ ??????????????????? http://image.yisou.com 1G??1000??????????? http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_1g/
