
Good afternoon! I've just built several variants of a 2.4.9 kernel for SuSE 7.2, and am having the same kernel panic no matter what I try in the configuration options. I started with a generic kernel tree from ftp.kernel.org, and applied (with no error messages) all the patches for 2.4.9 from ftp://ftp.suse.com/...../martel/next/ on the SuSE FTP site. Everything seemed fine, and the build went smoothly. In the build, I started with the default SuSE configuration file from /boot, did a "make oldconfig" to bring it up to 2.4.9, and then ran "make xconfig" to remove some stuff like Amateur Radio, ISDN, and MTD support, that I don't plan to use. I ran make dep, make bzImage, make modules, and make modules_install, in that order, after first making sure that the directory /lib/modules/2.4.9 was empty. Everything seemed to work fine. I copied the bzImage file to a new filename under /boot, configured /etc/lilo.conf as needed, then ran lilo. When I try to boot the new kernel, I get a panic with the following rather cryptic information: Process init (pid: 1, stackpage=c1409000) Stack: <<omitted for brevity>> Call Trace: <<omitted for brevity>> Code: 0f 0b eb 26 8d b6 00 00 00 00 83 7b 04 00 75 1d 68 b6 00 00 Kernel panic: Attempted to kill init! I know what init does, but I have no idea how it came to be that some process tried to kill it. Rebooting from the original kernel still works, so my system isn't hosed. I also tried rebooting from the rescue CD, immediately after the crash, to recover any useful log entries, but alas there is nothing being logged (too early in the boot process, I guess). The console seems to indicate that the crash is happening just after Reiserfs is loaded, but it scrolls by too fast for me to be sure. Has anyone seen this before, and if so, what should I be checking in my kernel config to isolate the problem? Thanks for any help someone can offer. Scott -- ------------------------------------------------------------ "I don't mind Microsoft making money. I mind them having a bad operating system." -- Linus Torvalds, in the NY Times Scott Courtney http://www.4th.com/