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 :
[ 0.070964] smpboot: CPU0: AMD Athlon(tm) 7750 Dual-Core Processor
(fam: 10, model: 02, stepping: 03)
[ 0.175415] Performance Events: AMD PMU driver.
[ 0.248501] NET: Registered protocol family 1
[ 0.248515] pci 0000:00:01.0: MSI quirk detected; subordinate MSI disabled
[ 1.878384] pci 0000:01:05.0: Video device with shadowed ROM
[ 2.225414] ata3: SATA link down (SStatus 0 SControl 300)
[ 2.392196] ata1: softreset failed (device not ready)
[ 2.392199] ata1: applying PMP SRST workaround and retrying
[ 2.422234] usb 3-1: new low-speed USB device number 2 using ohci-pci
[ 2.559072] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2.695906] hid-generic 0003:04F3:0103.0002: input: USB HID v1.11
Device [HID 04f3:0103] on usb-0000:00:12.0-1/input1
[ 2.882804] tsc: Refined TSC clocksource calibration: 2712.351 MHz
[ 3.059684] ata1: softreset failed (device not ready)
[ 3.059687] ata1: applying PMP SRST workaround and retrying
[ 3.236722] sda: sda1 sda2
[ 3.236880] sd 0:0:0:0: [sda] Attached SCSI disk
[ 3.472247] input: ImPS/2 Logitech Wheel Mouse as
/devices/platform/i8042/serio1/input/input2
[ 3.475012] md: Waiting for all devices to be available before autodetect
[ 3.526543] Freeing unused kernel memory: 796K (ffffffff816a3000 -
ffffffff8176a000)
[ 3.887420] Switched to clocksource tsc
[ 4.953361] random: nonblocking pool is initialized
Not sure if it is normal or not...maybe it's just normal behavior or
cannot get any faster...
Thanks for reading.
Cheers
On Mon, May 4, 2015 at 7:21 AM, linux cbon <[email protected]> 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 :
>
> [ 0.070964] smpboot: CPU0: AMD Athlon(tm) 7750 Dual-Core Processor
> (fam: 10, model: 02, stepping: 03)
> [ 0.175415] Performance Events: AMD PMU driver.
>
> [ 0.248501] NET: Registered protocol family 1
> [ 0.248515] pci 0000:00:01.0: MSI quirk detected; subordinate MSI disabled
> [ 1.878384] pci 0000:01:05.0: Video device with shadowed ROM
>
> [ 2.225414] ata3: SATA link down (SStatus 0 SControl 300)
> [ 2.392196] ata1: softreset failed (device not ready)
> [ 2.392199] ata1: applying PMP SRST workaround and retrying
> [ 2.422234] usb 3-1: new low-speed USB device number 2 using ohci-pci
> [ 2.559072] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>
> [ 2.695906] hid-generic 0003:04F3:0103.0002: input: USB HID v1.11
> Device [HID 04f3:0103] on usb-0000:00:12.0-1/input1
> [ 2.882804] tsc: Refined TSC clocksource calibration: 2712.351 MHz
> [ 3.059684] ata1: softreset failed (device not ready)
> [ 3.059687] ata1: applying PMP SRST workaround and retrying
>
> [ 3.236722] sda: sda1 sda2
> [ 3.236880] sd 0:0:0:0: [sda] Attached SCSI disk
> [ 3.472247] input: ImPS/2 Logitech Wheel Mouse as
> /devices/platform/i8042/serio1/input/input2
> [ 3.475012] md: Waiting for all devices to be available before autodetect
>
> [ 3.526543] Freeing unused kernel memory: 796K (ffffffff816a3000 -
> ffffffff8176a000)
> [ 3.887420] Switched to clocksource tsc
> [ 4.953361] random: nonblocking pool is initialized
>
> Not sure if it is normal or not...maybe it's just normal behavior or
> cannot get any faster...
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
On Mon, May 4, 2015 at 8:50 AM, Frans Klaver <[email protected]> wrote:
> On Mon, May 4, 2015 at 7:21 AM, linux cbon <[email protected]> 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.
Linuxcbon
On Tue, May 05, 2015 at 12:20:31AM +0100, linux cbon wrote:
> On Mon, May 4, 2015 at 8:50 AM, Frans Klaver <[email protected]> wrote:
> > On Mon, May 4, 2015 at 7:21 AM, linux cbon <[email protected]> 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