Hi,
I’m trying to find out where a boot pause of 15s happens, but boot.msg doesn’t show any timestamps so that’s impossible to tell.
Following www.kernel.org/pub/linux/kernel/people/gregkh/lkn/lkn_pdf/ch09.pdf, I tried putting the “time” command line parameter in the boot loader settings. However, at least in boot.msg no timestamps show up.
Am I looking into the wrong logfile, or giving the wrong parameter, or is there an entirely different way of getting those timestamps?
Thanks for any hints!
schnabeltasse adjusted his/her AFDB on Friday 15 May 2009 20:56 to write:
>
> Hi,
>
> I’m trying to find out where a boot pause of 15s happens, but boot.msg
> doesn’t show any timestamps so that’s impossible to tell.
>
> Following
> www.kernel.org/pub/linux/kernel/people/gregkh/lkn/lkn_pdf/ch09.pdf, I
> tried putting the “time” command line parameter in the boot loader
> settings. However, at least in boot.msg no timestamps show up.
>
> Am I looking into the wrong logfile, or giving the wrong parameter, or
> is there an entirely different way of getting those timestamps?
>
> Thanks for any hints!
>
>
A similar prob with another person happened last week, I advised he
installed bootchart ( in the pss repos IIRC) and after looking at his graph we found there was a find` running before the bootmesg starts, this turned
out that the machine was looking for samba shares which he no longer was
using.
It could be that or it could be something you had plugged in when installing
but no longer have, usb stick, usb drive etc…
Or have you moved deleted any partitions?
If you use bootchart and cannot figure out then post it online somewhere and
drop us the link so we can have a glance.
HTH
–
Mark
Nullus in verba
Nil illigitimi carborundum
Thanks Mark for replying.
The first effect of bootchart was to show the log on the screen already when the pause happens (where there was nothing to be seen before). That leads me to believe that it is a DSDT problem, as described in https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/100110/comments/10. I followed that and configured my modified DSDT file via ACPI_DSDT in /etc/sysconfig/kernel, but that didn’t help. Maybe I made a mistake here somewhere (how can I tell my DSDT has been properly picked up?)
However, you can see the bootchart in http://img211.imageshack.us/img211/3165/bootcharts.png, but it doesn’t help much, I’m afraid…
I believe the line where the pause happens to be this one:
<6>ACPI: EC: non-query interrupt received, switching to interrupt mode
But how the heck can I get timestamps at the beginning of the lines in boot.msg instead of numbers??
Seems to be the same bug as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263140, which doesn’t seem to be fixed yet anywhere.
schnabeltasse adjusted his/her AFDB on Friday 15 May 2009 22:56 to write:
>
> Thanks Mark for replying.
>
> The first effect of bootchart was to show the log on the screen already
> when the pause happens (where there was nothing to be seen before). That
> leads me to believe that it is a DSDT problem, as described in
> http://tinyurl.com/pdub3u. I followed that and configured my modified
> DSDT file via ACPI_DSDT in /etc/sysconfig/kernel, but that didn’t help.
> Maybe I made a mistake here somewhere (how can I tell my DSDT has been
> properly picked up?)
>
> However, you can see the bootchart in
> http://img211.imageshack.us/img211/3165/bootcharts.png, but it doesn’t
> help much, I’m afraid…
>
> I believe the line where the pause happens to be this one:
>> <6>ACPI: EC: non-query interrupt received, switching to interrupt mode
> But how the heck can I get timestamps at the beginning of the lines in
> boot.msg instead of numbers??
>
>
You just caught me turning in, had a really really quick look:
You have raid setup?
Is this pause happening approx 35s in ti;; approx 50s?
That is all I can think of off the top of my head, the cells have decided to
go on strike ( busy day ), will have a look later after a kip.
–
Mark
Nullus in verba
Nil illigitimi carborundum
