All of lore.kernel.org
 help / color / mirror / Atom feed
From: jim.cromie@gmail.com
To: ckim@etri.re.kr
Cc: Philipp Hortmann <philipp.g.hortmann@gmail.com>,
	kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: how to avoid CPU watchdog error during debug
Date: Sat, 25 Sep 2021 15:34:57 -0600	[thread overview]
Message-ID: <CAJfuBxzTjc1iX=eohgMzqNE7qKZHkKGfDtBjS2V34FWYT5Vb8g@mail.gmail.com> (raw)
In-Reply-To: <02f301d79d40$db6dc170$92494450$@etri.re.kr>

On Sun, Aug 29, 2021 at 7:46 PM <ckim@etri.re.kr> wrote:
>
>
> >
> > 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 Philipp
> >
> Hi, 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

      reply	other threads:[~2021-09-25 21:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25  1:06 how to avoid CPU watchdog error during debug ckim
2021-08-26 17:34 ` Philipp Hortmann
2021-08-30  1:46   ` ckim
2021-09-25 21:34     ` jim.cromie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJfuBxzTjc1iX=eohgMzqNE7qKZHkKGfDtBjS2V34FWYT5Vb8g@mail.gmail.com' \
    --to=jim.cromie@gmail.com \
    --cc=ckim@etri.re.kr \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=philipp.g.hortmann@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.