All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Re: how to avoid CPU watchdog error during debug
Date: Thu, 26 Aug 2021 19:34:04 +0200	[thread overview]
Message-ID: <75ff22e0-d516-bec5-9b11-6dda30933359@gmail.com> (raw)
In-Reply-To: <01cd01d7994d$6b063760$4112a620$@etri.re.kr>

On 8/25/21 3:06 AM, ckim@etri.re.kr wrote:
> Hello,
> 
> While debugging a kernel module, I get this error and the OS crashes.
> 
> [39068.833652] rcu: INFO: rcu_sched self-detected stall on CPU
> 
> [39068.834739] watchdog: BUG: soft lockup - CPU#3 stuck for 164s! 
> [systemd-journal:399]
> 
> [39068.834854] watchdog: BUG: soft lockup - CPU#0 stuck for 164s! 
> [test_axpu_app:2896]
> 
> This seems because I stopped the processor for debugging.
> 
> How can I avoid this watchdog error during debug?
> 
> Any help will be appreciated. Thanks!
> 
> Chan Kim
> 
> 
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> 

Hi Kim,

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







_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2021-08-26 17:34 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 [this message]
2021-08-30  1:46   ` ckim
2021-09-25 21:34     ` jim.cromie

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=75ff22e0-d516-bec5-9b11-6dda30933359@gmail.com \
    --to=philipp.g.hortmann@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    /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.