qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: hugang@soulinfo.com
To: qemu-devel@nongnu.org, fabrice@bellard.org
Subject: Re: [Qemu-devel] Re: 2.6.10-mm3: swsusp: out of memory on resume
Date: Sun, 16 Jan 2005 12:38:27 +0800	[thread overview]
Message-ID: <20050116043827.GA6584@hugang.soulinfo.com> (raw)
In-Reply-To: <20050115164056.GA28549@hugang.soulinfo.com>

On Sun, Jan 16, 2005 at 12:40:56AM +0800, hugang@soulinfo.com wrote:
> On Sat, Jan 15, 2005 at 12:48:54PM +0100, Fabrice Bellard wrote:
...
> 
> 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,
> :)
> 
> 

Ok, I enable the raise_exception_err, and catach this.
.....
/* only works if protected mode and not VM86. seg_reg must be != R_CS */
void load_seg(int seg_reg, int selector)
{
    uint32_t e1, e2;
    int cpl, dpl, rpl;
    SegmentCache *dt;
    int index;
    target_ulong ptr;

    selector &= 0xffff;
    if ((selector & 0xfffc) == 0) {
        /* null selector case */
        if (seg_reg == R_SS)
            raise_exception_err(EXCP0D_GPF, 0);
        cpu_x86_load_seg_cache(env, seg_reg, selector, 0, 0, 0);
    } else {
	....

In the comment line, said must be != R_CS, But in code is check R_SS, I
just change R_SS to R_CS, then the software-suspend suspend part passed 
in qemu, I geting hang at copyback memory in resume, Still debuging...

:)

Maybe that, also useful for other, Eg. Win2k disk full...

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

  reply	other threads:[~2005-01-16  5:04 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
2005-01-16  4:38             ` hugang [this message]
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=20050116043827.GA6584@hugang.soulinfo.com \
    --to=hugang@soulinfo.com \
    --cc=fabrice@bellard.org \
    --cc=qemu-devel@nongnu.org \
    /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).