Has anyone else noticed problems with 39-rc1+ sometimes not booting
into run-level 3? It seems to just go directly to root console prompt
sometimes. Seems it was easier to reproduce on -rc1 and early more
buggy kernels, for what that's worth..
Ben
--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com
On Tue, May 10, 2011 at 8:31 PM, Ben Greear <[email protected]> wrote:
> Has anyone else noticed problems with 39-rc1+ sometimes not booting
> into run-level 3? ?It seems to just go directly to root console prompt
> sometimes. ?Seems it was easier to reproduce on -rc1 and early more
> buggy kernels, for what that's worth..
Haven't seen this one - F14 always booted into runlevel 3 on my Dell
Latitude E6400... and since I save all my kernel .config files I can tell
you which kernels I've tested:
[root@duff src]# ls .config-2.6.39-rc*
.config-2.6.39-rc1 .config-2.6.39-rc3-git3 .config-2.6.39-rc4-git8
.config-2.6.39-rc1-git1 .config-2.6.39-rc3-git4 .config-2.6.39-rc5
.config-2.6.39-rc1-git2 .config-2.6.39-rc3-git6 .config-2.6.39-rc5-git1
.config-2.6.39-rc1-git3 .config-2.6.39-rc3-git7 .config-2.6.39-rc5-git2
.config-2.6.39-rc1-git5 .config-2.6.39-rc4 .config-2.6.39-rc5-git4
.config-2.6.39-rc2 .config-2.6.39-rc4-git1 .config-2.6.39-rc5-git6
.config-2.6.39-rc2-git1 .config-2.6.39-rc4-git2 .config-2.6.39-rc5-git7
.config-2.6.39-rc2-git2 .config-2.6.39-rc4-git4 .config-2.6.39-rc6
.config-2.6.39-rc2-git3 .config-2.6.39-rc4-git5 .config-2.6.39-rc6-git2
.config-2.6.39-rc3 .config-2.6.39-rc4-git6 .config-2.6.39-rc6-git6
.config-2.6.39-rc3-git1 .config-2.6.39-rc4-git7 .config-2.6.39-rc7
[root@duff ~]# grep "^id" /etc/inittab
id:3:initdefault:
--alessandro
?"There's always a siren singing you to shipwreck"
?? (Radiohead, "There There")
On 05/10/2011 02:31 PM, Ben Greear wrote:
> Has anyone else noticed problems with 39-rc1+ sometimes not booting
> into run-level 3? It seems to just go directly to root console prompt
> sometimes. Seems it was easier to reproduce on -rc1 and early more
> buggy kernels, for what that's worth..
I don't know exactly which version it was, but when I was bisecting some
unrelated breakage in 2.6.39-rc7, some of the test kernels got stuck in
some early systemd stage (F15 beta) and failed to make progress. But
I've never seen this on new kernels or on 2.6.38.y.
--Andy
>
> Ben
>