qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: hugang@soulinfo.com
To: qemu-devel@nongnu.org, fabrice@bellard.org
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [Qemu-devel] Re: 2.6.10-mm3: swsusp: out of memory on resume
Date: Sun, 16 Jan 2005 00:40:56 +0800	[thread overview]
Message-ID: <20050115164056.GA28549@hugang.soulinfo.com> (raw)
In-Reply-To: <41E90326.2020901@bellard.org>

On Sat, Jan 15, 2005 at 12:48:54PM +0100, Fabrice Bellard wrote:
.....
> I recently made a fix in fxsave/fxrestor which may correct some issues 
> on x86_64. Strangely, the CVS commit mail did not appear on the mailing 
> list...
> 
> The state of x86_64 is that the install of Fedora core 3 for x86_64 
> begins to work (you can select the language for example), but there are 
> some invalid characters displayed on screen. I believe there is a sign 
> extension problem in a 64 bit instruction.
> 
> Now that SSE and MMX are implemented, no feature is lacking in the QEMU 
> x86_64 emulation... "just" a problem of debugging now :-)

When I using Qemu as X86_64 emulataion for testing software suspend, I
get the first oops the instruction is this, 
IN:
0xffffffff80116a8a:  movzwl 0x8(%rbx),%eax
0xffffffff80116a8e:  mov    %eax,%ss	<- general protection 

That's in 
arch/x86_64/kernel/suspend.c +105
 asm volatile ("movw %0, %%ss" :: "r" (ctxt->ss)); <-- general protection.

I don't why, but I check %eax and %ss are same value, so I just comment 
this line, the oops go away, But still geting hang, Now I have no idea,
:)


I put the all logs in this 
 http://soulinfo.com/~hugang/swsusp/x86_64_log/

thanks.

-- 
Hu Gang       .-.
              /v\
             // \\ 
Linux User  /(   )\  [204016]
GPG Key ID   ^^-^^   http://soulinfo.com/~hugang/hugang.asc

  reply	other threads:[~2005-01-15 17:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.58.0412241434110.17285@ppc970.osdl.org>
     [not found] ` <200501131909.26021.rjw@sisk.pl>
     [not found]   ` <20050114143400.GA27657@hugang.soulinfo.com>
     [not found]     ` <200501150042.35377.rjw@sisk.pl>
2005-01-15  1:21       ` [Qemu-devel] Re: 2.6.10-mm3: swsusp: out of memory on resume (was: Re: Ho ho ho - Linux v2.6.10) hugang
2005-01-15 11:48         ` [Qemu-devel] Re: 2.6.10-mm3: swsusp: out of memory on resume Fabrice Bellard
2005-01-15 16:40           ` hugang [this message]
2005-01-16  4:38             ` hugang
2005-01-15 18:02           ` [Qemu-devel] W2K SP0 Status (was: Re: 2.6.10-mm3: swsusp: out of memory on resume) Tim
2005-01-17 18:02           ` [Qemu-devel] Re: Re: 2.6.10-mm3: swsusp: out of memory on resume Ronald
2005-01-17 21:54             ` Fabrice Bellard
2005-01-22  4:17               ` [Qemu-devel] " Anand Kumria
2005-01-22 12:42                 ` Johannes Schindelin
     [not found]         ` <200501151147.32919.rjw@sisk.pl>
     [not found]           ` <200501152220.42129.rjw@sisk.pl>
2005-01-16  5:54             ` [Qemu-devel] Re: 2.6.10-mm3: swsusp: out of memory on resume (was: Re: Ho ho ho - Linux v2.6.10) hugang
2005-01-16 10:07               ` Rafael J. Wysocki

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=20050115164056.GA28549@hugang.soulinfo.com \
    --to=hugang@soulinfo.com \
    --cc=fabrice@bellard.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rjw@sisk.pl \
    /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;
as well as URLs for NNTP newsgroup(s).