From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: tanure@linux.com
Cc: "kernelnewbies@kernelnewbies.org"
<kernelnewbies@kernelnewbies.org>, aleave <aleave@protonmail.com>
Subject: Re: How to printk synchronously
Date: Wed, 27 Nov 2019 04:18:00 -0500 [thread overview]
Message-ID: <548800.1574846280@turing-police> (raw)
In-Reply-To: <CAJX_Q+0i7diV5j0G11bCDPf3SHLse0AxZktuvz4m0_iwbE=WoA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 882 bytes --]
On Tue, 26 Nov 2019 22:31:08 +0000, Lucas Tanure said:
> Hi,
>
> What about ftrace ? Documentation/trace/ftrace.txt
That won't help - his ^@^@^@ is a result of the system stopping and no longer
writing to disk, so his logfile has blocks allocated to it but not yet written
to.
Using ftrace will have the same problem, if his kernel is locking up and not
syncing to disk.
A better approach would be to use netconsole to send all the console output to
another machine, or serial console if that's an option.
Though I have to wonder how he's determining it's a deadlock issue rather than
a panic that's just plain stopping the system - building the kernel with
lockdep support should reveal the issue before a lockup. And if it *is* a
deadlock, there should be sufficient info in the watchdog logging (assuming the
hardware has some sort of watchdog support, as most systems do).
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-11-27 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 20:07 How to printk synchronously aleave
2019-11-26 22:31 ` Lucas Tanure
2019-11-27 9:18 ` Valdis Klētnieks [this message]
2019-11-28 6:12 ` Muni Sekhar
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=548800.1574846280@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=aleave@protonmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=tanure@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).