Re: how to avoid CPU watchdog error during debug
From: jim.cromie@gmail.com
Date: 2021-09-25 21:35:30
On Sun, Aug 29, 2021 at 7:46 PM [off-list ref] wrote:
quoted
since many things are time depending in the kernel it is difficult to stop parts of the kernel. The question is if it is really absolutely necessary to do this? Why you can not do it by logging with printk? Debugging is described in: https://www.doc-developpement-durable.org/file/Projets- informatiques/cours-&-manuels- informatiques/Linux/Linux%20Kernel%20Development,%203rd%20Edition.pdf See Chapter 18 Debugging Thanks! Bye PhilippHi, Philipp, I've found your answer too late. Thanks for the info(I learned something about the early_prink from the book). Actually, shortly after I sent my question, I learned how to make printk appear in the console (not in the dmesg buffer) and was using it. (I added the line "kernel.prink = 5 4 1 7" in the /etc/sysctl.conf file. So I've set the default console log level to 5 making default printk appear in the console.) Thanks! Chan
thanks for the followup _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies