Messages in this thread | | | Date | Sun, 14 May 2006 23:39:19 -0400 | From | Jeff Dike <> | Subject | Re: [uml-devel] [UML] Problems building and running 2.6.17-rc4 on x86-64 |
| |
On Sun, May 14, 2006 at 03:25:41PM -0300, Alberto Bertogli wrote: > So I copied them from sysdeps/x86_64/jmpbuf-offsets.h, and building went > on. Probably, the same happens under i386.
The current patch for this is http://user-mode-linux.sourceforge.net/work/current/2.6/2.6.17-rc4/patches/jmpbuf
I need to redo it, but that works for now.
> Then, it built fine, but at the end several errors showed up: > MODPOST > WARNING: vmlinux - Section mismatch: reference to .init.text:do_mount_root from .bss between '__guard@@GLIBC_2.3.2' (at offset 0x603c5688) and 'stdout@@GLIBC_2.2.5'
I have no idea what these mean, but they seem not to affect the viability of the resulting kernel.
> It begins to boot, but panics right after mounting root: > > [42949373.800000] kjournald starting. Commit interval 5 seconds > [42949373.800000] EXT3-fs: mounted filesystem with ordered data mode. > [42949373.800000] VFS: Mounted root (ext3 filesystem) readonly. > [42949373.800000] Kernel panic - not syncing: handle_trap - failed to wait at end of syscall, errno = 0, status = 2943
This is a segfault happening when it shouldn't.
Can you disassemble stub_segv_handler and send me the output? If you're unfamiliar with gdb, it works like this:
% gdb linux GNU gdb Red Hat Linux (6.3.0.0-1.122rh) 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 "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1".
(gdb) disas stub_segv_handler Dump of assembler code for function stub_segv_handler: 0x00000000601610c8 <stub_segv_handler+0>: push %rbp 0x00000000601610c9 <stub_segv_handler+1>: mov %rsp,%rbp 0x00000000601610cc <stub_segv_handler+4>: mov %rdx,%r8 ...
There was a bug like this a month or so ago, but it has been in mainline for a while, so this should be something different.
Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |