[opensuse] Too long timeout in openSUSE 11.2 boot
I am trying to boot openSUSE 11.2 in some special hardware (VME-based intel PC). Overall, it works ok. With one glitch: When booting, the system stops with this message: Set System Time to the current Hardware Clock and waits 3 or so minutes, and then prints: failed The boot continues, and the system is usable. My questions are: 1. Could there be something in the setting of the hardware clock that could take 3 minutes to fail? 2. It is possible to tell the boot not to set the hardware clock? Preferably on the boot command line. This is in a system where it's concept of time does matter. Which rc script does this occur in? Based on when it is happening, it seems to be S02haldaemon. Sound right? TIA for any light shed. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer wrote:
I don't know much but note that the error message is about setting the system time from the hardware clock, not vice-versa.
Well S04boot.clock seems a more likely candidate :) It contains several variables so I guess that it is possible. There seems to be one called USE_HWCLOCK that is set in /etc/init.d/boot.clock that might do something relevant. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-11-15 at 13:40 +0000, Dave Howorth wrote:
I meant to say what the message said. Sorry for the confusion.
I was looking in runlevel 5. Mainly because it seems to happen immediately before the ethernet devices are started. With so much of the boot happening in parallel, it can get confusing to know where something was that failed. But I see then further in the boot.mgs log: Failed features: boot.clock So you are surely right. Perhaps it is the adjtime command. Maybe the time is so far off that the gradual adjust takes time to complete. It is a minimal system that boots via PXE. It works on lots of hardware. The reported hardware is the first where something looks amiss.
Given the message given and the time when the delay occurs, I bet it is not the code that this controls. Of course, maybe it still contributes to the situation. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2010-11-15 at 15:00 +0100, Roger Oberholtzer wrote:
No, during boot adjustement is as "brutal" as needed, not "gradual".
It is a minimal system that boots via PXE. It works on lots of hardware. The reported hardware is the first where something looks amiss.
You should write a bugzilla about it.
There are several variables. You could try, for the moment, disabling the whole script: if boot succeds, then the next step would be to insert "-x" to bash line (if my memory is correct) so that it prints each line as it is executed and you can learn which one fails. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAkzhVX4ACgkQtTMYHG2NR9WjUwCfbBH9ckdSNADjzWL+++zYlT74 5MUAnjdw6/Y47CLVXimWoLZNAxbrSHyU =XwcI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 15/11/10 10:03, Roger Oberholtzer escribió:
I am trying to boot openSUSE 11.2 in some special hardware (VME-based intel PC). Overall, it works ok. With one glitch:
Try openSUSE 11.3, if that does not work, fill a bug report, including the output of hwinfo . -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-11-15 at 21:15 -0300, Cristian Rodríguez wrote:
These are diskless images (PXE + AoE) I make with KIWI. Setting up a local KIWI build for 11.3 is possible, but nothing I can do today. I will file a bug report when I know there is indeed a bug. I can say that this behavior was not seen in 10.3. I am having this confirmed so that the problem is not that the hardware has gone kaplooie since it last ran with 10.3. Those things do happen :( -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-11-15 at 21:15 -0300, Cristian Rodríguez wrote:
I have tested the same hardware with a 10.3 boot image, and this does not happen. It boots in less than one minute. The 11.3 takes over 4 minutes. I do not see in the various boot logs in the 10.3 boot anything about setting the rtc. I would imagine it did this in 10.3 as well. Not sure how to proceed. I don't want to file a bug report before I know there is a bug, as opposed to some mistake on my part. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2010-11-16 at 11:04 +0100, Roger Oberholtzer wrote:
minutes. I do not see in the various boot logs in the 10.3 boot anything about setting the rtc. I would imagine it did this in 10.3 as well.
The clock setting procedure has changed quite a bit in 11.2.
Not sure how to proceed. I don't want to file a bug report before I know there is a bug, as opposed to some mistake on my part.
Unless you changed the boot scripts, it is nothing you do. The only adjustement is this: /etc/sysconfig/clock ## Description: Write back system time to the hardware clock ## Type: yesno ## Default: yes # # Is set to "yes" write back the system time to the hardware # clock at reboot or shutdown. Usefull if hardware clock is # much more inaccurate than system clock. Set to "no" if # system time does it wrong due e.g. missed timer interrupts. # If set to "no" the hardware clock adjust feature is also # skipped because it is rather useless without writing back # the system time to the hardware clock. # SYSTOHC="yes" - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAkziayAACgkQtTMYHG2NR9UEaQCdElWmO3tuftS4VDbYRq5tlDcD UfYAn27OiISXgLtYq8fVIfwFSZK2fP1p =zuF0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer wrote:
I don't know much but note that the error message is about setting the system time from the hardware clock, not vice-versa.
Well S04boot.clock seems a more likely candidate :) It contains several variables so I guess that it is possible. There seems to be one called USE_HWCLOCK that is set in /etc/init.d/boot.clock that might do something relevant. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-11-15 at 13:40 +0000, Dave Howorth wrote:
I meant to say what the message said. Sorry for the confusion.
I was looking in runlevel 5. Mainly because it seems to happen immediately before the ethernet devices are started. With so much of the boot happening in parallel, it can get confusing to know where something was that failed. But I see then further in the boot.mgs log: Failed features: boot.clock So you are surely right. Perhaps it is the adjtime command. Maybe the time is so far off that the gradual adjust takes time to complete. It is a minimal system that boots via PXE. It works on lots of hardware. The reported hardware is the first where something looks amiss.
Given the message given and the time when the delay occurs, I bet it is not the code that this controls. Of course, maybe it still contributes to the situation. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2010-11-15 at 15:00 +0100, Roger Oberholtzer wrote:
No, during boot adjustement is as "brutal" as needed, not "gradual".
It is a minimal system that boots via PXE. It works on lots of hardware. The reported hardware is the first where something looks amiss.
You should write a bugzilla about it.
There are several variables. You could try, for the moment, disabling the whole script: if boot succeds, then the next step would be to insert "-x" to bash line (if my memory is correct) so that it prints each line as it is executed and you can learn which one fails. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAkzhVX4ACgkQtTMYHG2NR9WjUwCfbBH9ckdSNADjzWL+++zYlT74 5MUAnjdw6/Y47CLVXimWoLZNAxbrSHyU =XwcI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 15/11/10 10:03, Roger Oberholtzer escribió:
I am trying to boot openSUSE 11.2 in some special hardware (VME-based intel PC). Overall, it works ok. With one glitch:
Try openSUSE 11.3, if that does not work, fill a bug report, including the output of hwinfo . -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-11-15 at 21:15 -0300, Cristian Rodríguez wrote:
These are diskless images (PXE + AoE) I make with KIWI. Setting up a local KIWI build for 11.3 is possible, but nothing I can do today. I will file a bug report when I know there is indeed a bug. I can say that this behavior was not seen in 10.3. I am having this confirmed so that the problem is not that the hardware has gone kaplooie since it last ran with 10.3. Those things do happen :( -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-11-15 at 21:15 -0300, Cristian Rodríguez wrote:
I have tested the same hardware with a 10.3 boot image, and this does not happen. It boots in less than one minute. The 11.3 takes over 4 minutes. I do not see in the various boot logs in the 10.3 boot anything about setting the rtc. I would imagine it did this in 10.3 as well. Not sure how to proceed. I don't want to file a bug report before I know there is a bug, as opposed to some mistake on my part. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Carlos E. R. -
Cristian Rodríguez -
Dave Howorth -
Roger Oberholtzer