From: Anthony B. <br...@st...> - 2004-12-03 07:22:43
|
I'm attempting to build a 2.4 guest that will run and function on our 2.6.5 SKAS enabled host (stock SuSE kernel). I moved the compile to a SuSE 9.0 installation when I experienced problems (redefinition errors) compiling the kernel on the SuSE 9.1 Professional distribution. Both the kernel and image worked fine on the older development machine (once I changed the compiler optimization to '-O1'). However, I just copied the kernel and image back over to our SuSE 9.1 machine. While the kernel will "launch", it appears to freeze or hang immediately. I see the following: $ /bin/linux-2.4.27-bs1-32bit umid=test-1 mem=128M con=pts con0=fd:0,fd:1 ubd0=/opt/images/instances/test_root.img ubd1=/opt/images/instances/test_swap.img eth0=tuntap,test-1-0,fe:fd:c6:6b:03:47 Checking for the skas3 patch in the host...found Checking for /proc/mm...found Checking PROT_EXEC mmap in /tmp...OK [1]+ Stopped /bin/linux-2.4.27-bs1-32bit umid=test-1 mem=128M con=pts con0=fd:0,fd:1 ubd0=/opt/images/instances/test_root.img ubd1=/opt/images/instances/test_swap.img eth0=tuntap,test-1-0,fe:fd:c6:6b:03:47 $ I was quite shocked that the process would "stop" by itself. I then attempted to attach with gdb using: # gdb /bin/linux-2.4.27-bs1-32bit 25303 GNU gdb 6.1 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-suse-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1". Attaching to program: /bin/linux-2.4.27-bs1-32bit, process 25303 At this point, gdb "freezes" as well. I can't do anything until I close the shell in which I originally launched the 2.4.27 kernel. Even "kill -9 25303" does not affect the process. The only way I've been able to produce a backtrace was: 1. Shift back to the user shell that originally launched the process. Issue: $ kill %1 [1]+ Stopped /bin/linux-2.4.27-bs1-32bit umid=test-1 mem=128M con=pts con0=fd:0,fd:1 ubd0=/opt/images/instances/test-1_root.img ubd1=/opt/images/instances/test-1_swap.img eth0=tuntap,mbar-1-0,fe:fd:c6:6b:03:47 2. I then see output in gdb: Reading symbols from /lib/libutil.so.1...done. Loaded symbols for /lib/libutil.so.1 Reading symbols from /lib/tls/libc.so.6...done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 0xffffe410 in ?? () (gdb) 3. At this point, I can create a backtrace: (gdb) bt #0 0xffffe410 in ?? () #1 0xbffff768 in ?? () #2 0x00000002 in ?? () #3 0xbffff758 in ?? () #4 0x400a2543 in __waitpid_nocancel () from /lib/tls/libc.so.6 #5 0x080ec31c in start_userspace (cpu=25305) at process.c:119 #6 0x080ece88 in start_uml_skas () at process_kern.c:161 #7 0x080eb50f in linux_main (argc=8, argv=0xbffff8f4) at um_arch.c:398 #8 0x080542a7 in main (argc=8, argv=0xbffff8f4, envp=0xbffff918) at arch/um/main.c:148 (gdb) Ideas? How can I get this image to launch on the 9.1 machine? Help is greatly appreciated! Tony |