I just tried out the new grSec kernels 2.6.10, and found out (after hours of recompiling) that, if CONFIG_PAX_KERNEXEC is enabled, the kernel panics very shortly after being loaded by grub. I can't copy & paste the exact error message (don't have a serial terminal), but it says something about "Bad EIP value". I'll attach my config for further investigation, I tried that config on a Duron and on a P4, so it seems to be no CPU-specific problem. Some info on my system: Portage 2.0.51-r10 (hardened/x86/2.6, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.7-hardened-r18 i686) ================================================================= System uname: 2.6.7-hardened-r18 i686 AMD Duron(tm) Gentoo Base System version 1.6.8 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Jan 9 2005, 17:42:07)] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r2 sys-devel/libtool: 1.5.10-r2 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon -mtune=athlon -mmmx -m3dnow -O2 -pipe -fomit-frame-pointer -ffast-math -fforce-addr -falign-functions=4" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon -mtune=athlon -mmmx -m3dnow -O2 -pipe -fomit-frame-pointer -ffast-math -fforce-addr -falign-functions=4" DISTDIR="/storage/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox" GENTOO_MIRRORS="http://ftp.easynet.nl/mirror/gentoo/ ftp://gentoo.inode.at/source/ http://gentoo.inode.at" MAKEOPTS="-j2" PKGDIR="/storage/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage/" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://localhost/gentoo-portage" USE="3dnow acpi apache2 apm bcmath berkdb bzlib calendar chroot cpdflib crypt ctype curl curlwrappers dba dlloader erandom exif exim exiscan-acl fam flatfile ftp gd gdbm gif gmp gpm hardened hardenedphp iconv imagemagick imap inifile innodb ithreads java jpeg ldap maildir mhash mime mmx mysql nagios-dns nagios-ntp nagios-ping nagios-ssh ncurses nls nptl nptlonly pam parse-clocks pcntl pcre pdflib perl pic pie png posix python readline samba sasl session sharedmem simplexml slang snmp sockets socks5 spell spl sse ssl sysvipc tcpd threads tidy tiff tokenizer truetype usb vhosts wddx wildlsearch x86 xml xml2 xmlrpc xsl zlib" Unset: LDFLAGS
Created attachment 48367 [details] The kernel config
This happens when you just copy a .config and start compiling, because generally you will end up having PCI_BIOS enabled. Try changing CONFIG_PCI_BIOS=y to # CONFIG_PCI_BIOS is not set when making use of KERNEXEC
Please reopen if the issue still exists after you disable PCI_BIOS.
Thx, that did it (almost :) ). Had to change PCI access method in menuconfig from 'any' to 'direct' - else it did change CONFIG_PCI_BIOS always back to 'y' on compile. Now it works :)
*** Bug 83061 has been marked as a duplicate of this bug. ***
