After updating from sys-kernel/hardened-sources-2.6.14-r3 to 2.6.14-r5, my machine fails to boot. The error message 'Failed to open an initial console' is displayed and the system automatically restarts. How the problem occured: I emerged 2.6.14-r5, copied over my .config and executed 'make oldconfig' and then 'make install' (I do not use any kernel modules). After trying to reboot into the new kernel, the above problem occured. 2.6.14-r3 still works perfectly with the exact same config. Output of 'emerge info' follows. Portage 2.0.54 (default-linux/x86/2005.0, gcc-3.4.4, glibc-2.3.5-r2, 2.6.14-hardened-r3 i686) ================================================================= System uname: 2.6.14-hardened-r3 i686 Intel(R) Celeron(R) CPU 2.40GHz Gentoo Base System version 1.6.14 dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="de_DE.utf8" LC_ALL="de_DE.utf8" LINGUAS="de" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 apache2 bash-completion crypt hardened nls nptl pam ssl tcpd unicode linguas_de userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LDFLAGS, MAKEOPTS, PORTDIR_OVERLAY
Please attach to this bug: * The ".config" files from both your 2.6.14-r3 and 2.6.14-r5 source trees * The output of the "dmesg" command having booted with your 2.6.14-r3 kernel Thanks.
Created attachment 79148 [details] kernel config This is my .config which is working with the 2.6.14-hardened-r3 kernel, but not with r5. After executing 'make oldconfig' in the r5 kernel tree, the only diff between this one and the newly generated .config is in the version comments.
Created attachment 79149 [details] dmesg output The output of 'dmesg' running 2.6.14-hardened-r3.
Created attachment 79150 [details] config diff Output of 'diff -u' between the r3 config and the r5 config after running 'make oldconfig' in the r5 tree.
OK, can you also attach/say: * lscpi output * information about arguments passed to kernel and/or the relevant conf snippet * which version of udev you're running Can you also do the following: # mkdir /tmproot # mount -o bind / /tmproot # ls -l /tmproot/dev/{null,console} <-- what does this say?
Created attachment 79173 [details] lspci Outpout of 'lspci'.
Created attachment 79174 [details] grub config
> * which version of udev you're running I am running sys-fs/udev-079-r1.
(In reply to comment #5) > # mkdir /tmproot > # mount -o bind / /tmproot > # ls -l /tmproot/dev/{null,console} <-- what does this say? # ls -l /tmproot/dev/console /tmproot/dev/null crw------- 1 root tty 5, 1 17. Feb 2005 /tmproot/dev/console crwxrwxrwx 1 root root 1, 3 17. Feb 2005 /tmproot/dev/null
Here are two things for you to test. Firstly, to apply the following patch to your existing 2.6.14-r5 tree and test: * http://tinyurl.com/rwz9z Secondly, to install the sources from scratch like so (then test again with same .config): # UNIPATCH_EXCLUDE="1410" emerge =hardened-sources-2.6.14-r5 Please let me know the outcome as soon as you can - thanks.
Changing resolution to TEST-REQUEST and removing the block (until the reporter responds). Please see bug 121925 for details of further work on the hardened-sources tree as it stands.
Note that hardened-sources-2.6.14-r6 has been committed so it would be good for this to be tested. It incorporates the patch linked to in comment 10.
Sorry for the delay. I will test this with -r6 ASAP.
It seems to be fixed in -r6. Thanks.
Great! Thanks for testing it.
Oops, wrong resolution - re-opening to rectify ...
Marking as FIXED :)