Kernel Newbies archive mirror
 help / color / mirror / Atom feed
From: Christian Stalp <cstalp@topcon.com>
To: "kernelnewbies@kernelnewbies.org" <kernelnewbies@kernelnewbies.org>
Subject: Kernel freeze down while booting
Date: Fri, 22 Sep 2023 12:10:00 +0000	[thread overview]
Message-ID: <DM6PR06MB51930D369D972806E898BEA5A5FFA@DM6PR06MB5193.namprd06.prod.outlook.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1906 bytes --]

Hello, I have the issue that my kernel freezes down during the boot phase. It is most probably in the later states, when the inbuild drivers are executed and initialized, shortly before the filesystem mount. I enabled ftrace by putting "ftrace_dump_on_oops" and ftrace=function or ftrace=wakeup into the kernel commandline. But ftrace=function led to a system, that was so slowly that the issue never hit. Ftrace=wakeup was answered with a message "ftrace bootup tracer 'wakeup' not registered. But not always. I have several devices with the same kernel and image but sometimes this message shows up.
But the main problem here is, that the kernel freezes sometimes down and doesn't has a chance to throw an oops. And it's different where it freeze each time. Which is most probably due the problem that printk doesn't write its buffer to the console each time it's invoked. So printk isn't a utility to pinpoint exactly where the kernel freezes. And ftrace neither, because it's within the kernel and freezes down with the whole kernel. At least in the way I using it. Is there any mean to narrow down, where a kernel freezes which is not invasive and doesn't slow down the kernel so much? Besides, I had one kernel oops but then I got the message: Dumping ftrace buffer (ftrace buffer empty) but in that case I didn't choose a tracer (no ftrace=......)
The system is a i.MX6 ARMv7 with kernel 5.4.256. It's a yocto build.


Thank you in advance

BR Chris
Confidentiality Notice: This message (including attachments) is a private communication solely for use of the intended recipient(s). If you are not the intended recipient(s) or believe you received this message in error, notify the sender immediately and then delete this message. Any other use, retention, dissemination or copying is prohibited and may be a violation of law, including the Electronic Communication Privacy Act of 1986.   

[-- Attachment #1.2: Type: text/html, Size: 4033 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

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

             reply	other threads:[~2023-09-22 12:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22 12:10 Christian Stalp [this message]
2023-09-22 13:44 ` Kernel freeze down while booting Greg KH

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=DM6PR06MB51930D369D972806E898BEA5A5FFA@DM6PR06MB5193.namprd06.prod.outlook.com \
    --to=cstalp@topcon.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).