public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alberto Bertogli <albertito@gmail.com>
To: Jeff Dike <jdike@addtoit.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: Mon, 15 May 2006 12:29:58 -0300	[thread overview]
Message-ID: <20060515152958.GA4553@gmail.com> (raw)
In-Reply-To: <20060515033919.GD21383@ccure.user-mode-linux.org>

On Sun, May 14, 2006 at 11:39:19PM -0400, Jeff Dike wrote:
> 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.

Thanks!


> > 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?

Sure, here it is:
(gdb) disas stub_segv_handler
Dump of assembler code for function stub_segv_handler:
0x000000006027c0e0 <stub_segv_handler+0>:       mov    %rdx,%r8
0x000000006027c0e3 <stub_segv_handler+3>:       mov    0xd8(%r8),%rax
0x000000006027c0ea <stub_segv_handler+10>:      mov    $0x7fbffff000,%rdx
0x000000006027c0f4 <stub_segv_handler+20>:      mov    %rax,0x8(%rdx)
0x000000006027c0f8 <stub_segv_handler+24>:      mov    0xc0(%r8),%rax
0x000000006027c0ff <stub_segv_handler+31>:      mov    %eax,(%rdx)
0x000000006027c101 <stub_segv_handler+33>:      mov    0xc8(%r8),%rax
0x000000006027c108 <stub_segv_handler+40>:      mov    %eax,0x10(%rdx)
0x000000006027c10b <stub_segv_handler+43>:      mov    $0x27,%eax
0x000000006027c110 <stub_segv_handler+48>:      syscall
0x000000006027c112 <stub_segv_handler+50>:      mov    $0x3e,%edx
0x000000006027c117 <stub_segv_handler+55>:      movslq %eax,%rdi
0x000000006027c11a <stub_segv_handler+58>:      mov    $0xa,%esi
0x000000006027c11f <stub_segv_handler+63>:      mov    %rdx,%rax
0x000000006027c122 <stub_segv_handler+66>:      syscall
0x000000006027c124 <stub_segv_handler+68>:      mov    %r8,%rsp
0x000000006027c127 <stub_segv_handler+71>:      mov    $0xf,%rax
0x000000006027c12e <stub_segv_handler+78>:      syscall
0x000000006027c130 <stub_segv_handler+80>:      retq
End of assembler dump.


Please let me know if you need anything else.

Thanks,
		Alberto



  reply	other threads:[~2006-05-15 15:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-14 18:25 [UML] Problems building and running 2.6.17-rc4 on x86-64 Alberto Bertogli
2006-05-15  3:39 ` [uml-devel] " Jeff Dike
2006-05-15 15:29   ` Alberto Bertogli [this message]
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  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-18 19:48           ` Alberto Bertogli
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:38           ` [uml-devel] [UML] Problems building and running 2.6.17-rc4 on x86-64 Alberto Bertogli
2006-06-13 14:57 ` Alberto Bertogli
2006-06-13 18:21   ` Jeff Dike
2006-06-13 23:45     ` Paolo Giarrusso
2006-06-14 19:22       ` [uml-devel] " 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=20060515152958.GA4553@gmail.com \
    --to=albertito@gmail.com \
    --cc=jdike@addtoit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox