public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frans Klaver <fransklaver@gmail.com>
To: linux cbon <linuxcbon@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: is kernel slower at loading for some hardware ?
Date: Fri, 8 May 2015 20:24:21 +0200	[thread overview]
Message-ID: <20150508182421.GA1759@bugger.home> (raw)
In-Reply-To: <CAJ-LWjP9hfDUD2YVo5YPPxLCgYWa5wxBRqwjp32ZefpkUhqA9A@mail.gmail.com>

On Tue, May 05, 2015 at 12:20:31AM +0100, linux cbon wrote:
> On Mon, May 4, 2015 at 8:50 AM, Frans Klaver <fransklaver@gmail.com> wrote:
> > On Mon, May 4, 2015 at 7:21 AM, linux cbon <linuxcbon@gmail.com> wrote:
> >> Hi,
> >> during boot up, I am trying to find where the kernel takes more time
> >> to do actions (is slower ?).
> >> I looked at dmesg and found some places where it takes more time, but
> >> not sure if this is normal :
> (.......)
> > All hardware is different and therefore initialization time can be
> > different per component. Besides that, you're looking at something
> > that depends on how verbose the driver's logs are. It may well be that
> > the kernel is doing a lot of work, but just doesn't output anything
> > that clears the minimum log level.
> > Frans
> 
> 
> Hi Frans,
> I would like to have the maximal verbose logs,
> can you please tell me what is the way to achieve this ?
> And do you know the best way to find out where the kernel
> is getting slow and is having problems ?
> Thanks for your help.

Maybe this page can help you further:

http://elinux.org/Debugging_by_printing

Good luck,
Frans

      reply	other threads:[~2015-05-08 18:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04  5:21 is kernel slower at loading for some hardware ? linux cbon
2015-05-04  7:50 ` Frans Klaver
2015-05-04 23:20   ` linux cbon
2015-05-08 18:24     ` Frans Klaver [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=20150508182421.GA1759@bugger.home \
    --to=fransklaver@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxcbon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox