From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.5 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 628ABC432BE for ; Mon, 30 Aug 2021 01:47:17 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 9C00860F25 for ; Mon, 30 Aug 2021 01:47:16 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 9C00860F25 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=etri.re.kr Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94.2) (envelope-from ) id 1mKWNp-0006JQ-R9; Sun, 29 Aug 2021 21:46:45 -0400 Received: from mscreen.etri.re.kr ([129.254.9.16]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (Exim 4.94.2) (envelope-from ) id 1mKWNj-0006FH-Pv for kernelnewbies@kernelnewbies.org; Sun, 29 Aug 2021 21:46:40 -0400 Received: from unknown (HELO send002-relay.gov-dooray.com) (211.180.235.153) by 129.254.9.16 with ESMTP; 30 Aug 2021 10:46:32 +0900 X-Original-SENDERIP: 211.180.235.153 X-Original-MAILFROM: ckim@etri.re.kr X-Original-RCPTTO: kernelnewbies@kernelnewbies.org Received: from [10.162.225.112] (HELO smtp002-imp.gov-dooray.com) ([10.162.225.112]) by send002-relay.gov-dooray.com with SMTP id 5b837d3d612c3877; Mon, 30 Aug 2021 10:46:31 +0900 DKIM-Signature: a=rsa-sha256; b=c32tSpiJmTDFNIydJvlb3nMNWjPTLRQNb3N+CValNcMH/aDxOBh9R1MiCgjyawJaQ71rNThG7W ZMk9NQ9cuFB+hra/yXiF4JuzJ/bNbb+ktaOl069+/1O74EKAx1iUQnarxHZ9zzT9BtySlyC+vtUj wsYSvYtFPr+2/PuhExMZ4N8UWimqBYIqMmGaRaCi8X/dkMqPQPzkzBaaELal57VY0O2Ar8d7E5i4 Rf4uDISfYOs4RXdEjLyYAsAHwZDoqVI3n2TO2X6mK4+50twY8dCVcEik91oMLG+Avlf0QriAZ81q cka8rwrSdJUS0VgdWihrglp/2/0kdrEvPeGKV2JQ==; c=relaxed/relaxed; s=selector; d=dooray.com; v=1; bh=Bz3aKlemi1ryBoZaQGraF0UH1MhZXFQ24hiwDi8BgzI=; h=From:To:Subject:Message-ID; Received: from [129.254.132.39] (HELO CHANKIMPC) ([129.254.132.39]) by smtp002-imp.gov-dooray.com with SMTP id 8f6e47af612c3877; Mon, 30 Aug 2021 10:46:31 +0900 From: To: "'Philipp Hortmann'" , References: <01cd01d7994d$6b063760$4112a620$@etri.re.kr> <75ff22e0-d516-bec5-9b11-6dda30933359@gmail.com> In-Reply-To: <75ff22e0-d516-bec5-9b11-6dda30933359@gmail.com> Subject: RE: how to avoid CPU watchdog error during debug Date: Mon, 30 Aug 2021 10:46:31 +0900 Message-ID: <02f301d79d40$db6dc170$92494450$@etri.re.kr> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQEw5jqyWovnQIr9JgEqq7c2Sx2heQFGdhHBrM568xA= Content-Language: ko X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org > > 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 > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies@kernelnewbies.org > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies