Boot message: Stabilization not found. Waiting 10 seconds

[Lebenskuenstler]

Hi,

since the last yum update to kernel 2.6.27.4-79 I get this confusing error message prior to boot, even before LVM is loading. Afterwards everything goes fine.

Anyone might guess what this is about?

The precise message is:
could not detect stabilization, waiting 10 seconds.

[G3R]

I confirm the bug.

[chrz]

I've got the same situation. Is it on bugzilla ?

[Lebenskuenstler]

Originally Posted by chrz

I've got the same situation. Is it on bugzilla ?

https://bugzilla.redhat.com/show_bug.cgi?id=470628

Please add anything that might be useful.

[glennzo]

It's now Nov 20 and this appears to still be happening. I'm getting it with kernel 2.6.27.5-113.fc10.i686 and have been getting the error with the last few kernels. Just did an update but have yet to reboot with newest kernel. I'll report back in a few minutes.

Edit: Now running kernel 2.6.27.5-117.fc10.i686 and the "problem" still lives.

[robghealey]

When I first boot my linux box, the first line in the startup is:

"cannot detect stabilization, waiting 10 seconds..."

It then boots properly without any problems....

Can someone tell me why?

[glennzo]

https://bugzilla.redhat.com/show_bug.cgi?id=470628

[cougar618]

I get that message after unsucessfully trying to use suspend.

[Jake]

I'm also now getting it on Fedora 10 x86_64, happens on both Fedora 10 Installs.

[robghealey]

I guess that no one has any ideas on what to do or how to get rid of it yet!

I, too, am running Fedora 10 with 2.6.27.5-117 and I have it also...

[scottro]

Apparently not. Looking at the bug report, I didn't bother adding anything, since it's just what others are seeing. There was a bit of talk about it on the testing list as well.

It's just one more of those improvements that one gets with a cutting edge distro.

Seriously, I *believe* (meaning DO NOT TAKE THIS AS FACT) that it's an undesired result of the whole effort to speed up the boot process, and so, eventually, will be fixed. This is part of the process--something not working quite correctly as it's developed.

In this particular case, it's really pretty harmless, more of a minor annoyance, though, of course, the first time you see it, you wonder if you've run into a serious issue that is going to prevent the boot from continuing.

I do have to say, however, that even with this ten second time out, I do believe that boot time has improved.

[Jake]

Maybe it has improved. but to be honest, Yes I like the new time thing, but what was they doing with plymouth? seriously. that thing "Guesses" how far it is at booting, meaning it'll go all the way to the end, with just the 10 second wait, rather than actually working how the old ones were, were it actually meant something. I would have preferred it if they had made it how they made the rhgb bar. meaning, it's correct. But to be honest. it doesn't bother me. as when my system boots I don't sit there and look at it because it boots up so much stuff, it's a good 5 minute boot But that is because of my config, not Fedora.

[scottro]

The good about Plymouth.
It boots more quickly. The graphic is quite nice.
It's very easy to turn off by removing the rhgb and quiet words from the kernel line in grub.
The bad
It hides just about everything from the user. Hitting escape, as described in the release notes, only, at least in my experience, starts showing the user what's happening after interactive startup begins.
It doesn't work properly with several popular cards, though in most cases, it can be worked around by adding a vga=0x318 (for most machines) or vga=0x315 (for some netbooks).

I assume it will gradually get better, but more importantly, it's at least one case where they give the user a relatively easy way of turning it off.

[bee]

Hi
I've just installed F10

When i turn on my system, before LUKS asks me for the disk password, i read this message:

Could not detect stabilization, waiting 10 seconds

After waiting for ten seconds LUKS prompt for the disk password and the system starts.
It must be something related with the kernel because while the disk is encrypted nothing can be executed from there.
So, i'm just looking for a way to get rid of that message... do you know how?
I've found in this forum another message talking about this problem (archived in the old alpha f10) but not solutions there.... is the only way just wait for some lucky update!?

bye!!!

[1weak1]

Problem exists since preview release (on bugzilla since 7th november), I'm surprised they didn't fixed it before final. Fedora would boot really fast if not 10 sec delay. Lets hope for "lucky update"