From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Sven Köhler" <sven.koehler@gmail.com>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken
Date: Tue, 17 Mar 2009 09:52:59 -0700 [thread overview]
Message-ID: <49BFD56B.1040003@goop.org> (raw)
In-Reply-To: <49BFAEFA.80605@gmail.com>
Sven Köhler wrote:
> Jeremy Fitzhardinge schrieb:
>
>> Sven Köhler wrote:
>>
>>> Jeremy Fitzhardinge schrieb:
>>>
>>>> Jeremy Fitzhardinge wrote:
>>>>
>>>>> Do you have auditing enabled?
>>>>>
>>>> (No)
>>>>
>>> You answered yourself, right?
>>> (yes, CONFIG_AUDIT is disabled)
>>>
>>> Can I supply you with any further information?
>>>
>> I need to find/set up an AMD system to try to repro it I think. I think
>> the problem is actually the return from the syscall, rather than the
>> syscall entry itself. What happens if you run the program under either
>> strace or gdb?
>>
>
> The program just works:
>
> # strace ./a.out
> execve("./a.out", ["./a.out"], [/* 24 vars */]) = 0
> [ Process PID=8968 runs in 32 bit mode. ]
> uname({sys="Linux", node="xen-to1", ...}) = 0
> brk(0) = 0x80c3000
> brk(0x80c3cb0) = 0x80c3cb0
> set_thread_area(0xffa5182c) = 0
> brk(0x80e4cb0) = 0x80e4cb0
> brk(0x80e5000) = 0x80e5000
> fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> 0) = 0xfffffffff7f51000
> write(1, "Hallo Welt!\n"..., 12Hallo Welt!
> ) = 12
> exit_group(0) = ?
>
OK, that confirms that its sysret32 that's failing. vdso32=0 on the
kernel command line should be the workaround until we've got a proper fix.
J
next prev parent reply other threads:[~2009-03-17 16:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gpe0vg$j67$1@ger.gmane.org>
2009-03-13 21:11 ` 2.6.28.7 domU: 32-bit emulation seems to be broken Sven Köhler
2009-03-14 0:38 ` Jeremy Fitzhardinge
2009-03-14 0:59 ` Jeremy Fitzhardinge
2009-03-14 8:48 ` Sven Köhler
2009-03-14 22:03 ` Jeremy Fitzhardinge
2009-03-15 11:39 ` Sven Köhler
2009-03-15 15:32 ` Jeremy Fitzhardinge
2009-03-15 17:43 ` Sven Köhler
2009-03-15 17:45 ` Jeremy Fitzhardinge
2009-03-15 22:18 ` [Xen-devel] " Sven Köhler
2009-03-15 22:21 ` Sven Köhler
2009-03-15 17:48 ` Jeremy Fitzhardinge
2009-03-15 12:24 ` Sven Köhler
2009-03-15 13:30 ` [Xen-users] " Boris Derzhavets
2009-03-15 15:32 ` Jeremy Fitzhardinge
2009-03-15 16:28 ` Jeremy Fitzhardinge
2009-03-15 17:27 ` [Xen-devel] " Sven Köhler
2009-03-16 20:20 ` Jeremy Fitzhardinge
2009-03-16 20:23 ` Jeremy Fitzhardinge
2009-03-16 22:29 ` Sven Köhler
2009-03-16 22:36 ` Jeremy Fitzhardinge
2009-03-17 14:08 ` Sven Köhler
2009-03-17 16:52 ` Jeremy Fitzhardinge [this message]
2009-03-17 20:31 ` [Xen-devel] " Sven Köhler
2009-03-17 21:14 ` Jeremy Fitzhardinge
2009-08-10 11:21 ` Milan Holzäpfel
2009-08-10 12:59 ` Christoph Egger
2009-08-11 7:36 ` Milan Holzäpfel
2009-08-14 20:55 ` Jeremy Fitzhardinge
2009-03-14 9:13 ` [Xen-devel] " Sven Köhler
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=49BFD56B.1040003@goop.org \
--to=jeremy@goop.org \
--cc=sven.koehler@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/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.