From: Jeff Dike <jdike@addtoit.com>
To: Alberto Bertogli <albertito@gmail.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] [UML] Problems building and running 2.6.17-rc4 on x86-64
Date: Sun, 14 May 2006 23:39:19 -0400 [thread overview]
Message-ID: <20060515033919.GD21383@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20060514182541.GA4980@gmail.com>
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
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Dike <jdike@addtoit.com>
To: Alberto Bertogli <albertito@gmail.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] [UML] Problems building and running 2.6.17-rc4 on x86-64
Date: Sun, 14 May 2006 23:39:19 -0400 [thread overview]
Message-ID: <20060515033919.GD21383@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20060514182541.GA4980@gmail.com>
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
next prev parent reply other threads:[~2006-05-15 3:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 18:25 [uml-devel] [UML] Problems building and running 2.6.17-rc4 on x86-64 Alberto Bertogli
2006-05-14 18:25 ` Alberto Bertogli
2006-05-15 3:39 ` Jeff Dike [this message]
2006-05-15 3:39 ` [uml-devel] " Jeff Dike
2006-05-15 15:29 ` Alberto Bertogli
2006-05-15 15:29 ` Alberto Bertogli
2006-05-16 19:12 ` Jeff Dike
2006-05-16 19:12 ` Jeff Dike
2006-05-17 2:39 ` [uml-devel] [UML] Problems building and running 2.6.17-rc4 on x86-64ync-mailbox><next-undeleted><enter-command>set editor=vim Alberto Bertogli
2006-05-17 2:39 ` Alberto Bertogli
2006-05-17 6:36 ` Blaisorblade
2006-05-17 6:36 ` Blaisorblade
2006-05-17 18:57 ` [uml-devel] [UML] Problems building and running 2.6.17-rc4 on x86-64 Alberto Bertogli
2006-05-17 18:57 ` Alberto Bertogli
2006-05-18 19:48 ` Alberto Bertogli
2006-05-18 19:48 ` Alberto Bertogli
2006-05-19 1:20 ` Blaisorblade
2006-05-19 1:20 ` Blaisorblade
2006-05-17 18:12 ` [uml-devel] [UML] Problems building and running 2.6.17-rc4 on x86-64ync-mailbox><next-undeleted><enter-command>set editor=vim Jeff Dike
2006-05-17 18:12 ` Jeff Dike
2006-05-17 18:38 ` [uml-devel] [UML] Problems building and running 2.6.17-rc4 on x86-64 Alberto Bertogli
2006-05-17 18:38 ` Alberto Bertogli
2006-06-13 14:57 ` Alberto Bertogli
2006-06-13 14:57 ` Alberto Bertogli
2006-06-13 18:21 ` [uml-devel] " Jeff Dike
2006-06-13 18:21 ` Jeff Dike
2006-06-13 23:45 ` [uml-devel] " Paolo Giarrusso
2006-06-13 23:45 ` Paolo Giarrusso
2006-06-14 19:22 ` [uml-devel] " Jeff Dike
2006-06-14 19:22 ` Jeff Dike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060515033919.GD21383@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=albertito@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.