All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Larson <plars@linuxtestproject.org>
To: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: xen problem with save/restore
Date: Tue, 07 Dec 2004 21:05:13 -0600	[thread overview]
Message-ID: <1102475112.2708.1.camel@localhost.localdomain> (raw)
In-Reply-To: <1102394677.3302.4.camel@localhost.localdomain>

I just tried this on the same system/compiler with the xeno-unstable.bk
tree and save/restore worked for me.  Anyone know of a something in
unstable that might make this work?

Thanks,
Paul Larson

On Mon, 2004-12-06 at 22:44, Paul Larson wrote:
> Interesting, I'm using this on a different machine now and getting a
> slightly different error when I restore:
> Unable to handle kernel NULL pointer dereference at virtual address
> 00000007
>  printing eip:
> c0302407
> *pde = ma 00000000 pa 55555000
>  [<c012bbee>] worker_thread+0x1ea/0x2e0
> 
> The new machine is my laptop, an IBM T41p, but otherwise much the same
> (debian sarge, same compiler, etc).
> 
> Thanks,
> Paul Larson
> On Fri, 2004-12-03 at 10:58, Paul Larson wrote:
> > I think I've seen something similar to this posted recently, but I can't
> > find the message to reply to.  I build xen-2.0-testing from source
> > yesterday.  I have debian sarge running on all my domains right now.  I
> > was trying the save/restore feature out, and got this after restoring
> > and consoling into a session:
> > 
> > ************ REMOTE CONSOLE: CTRL-] TO QUIT ********
> > Unable to handle kernel NULL pointer dereference at virtual address
> > 00000007
> >  printing eip:
> > c030e587
> > *pde = ma 00000000 pa 55555000
> >  [<c0109f80>] __do_suspend+0x19f/0x1e0
> > 
> >  [<c012ca65>] worker_thread+0x22b/0x32f
> > 
> >  [<c010a088>] __shutdown_handler+0x0/0x48
> > 
> >  [<c01196c0>] default_wake_function+0x0/0x12
> > 
> >  [<c01196c0>] default_wake_function+0x0/0x12
> > 
> >  [<c012c83a>] worker_thread+0x0/0x32f
> > 
> >  [<c0130b89>] kthread+0xa5/0xab
> > 
> >  [<c0130ae4>] kthread+0x0/0xab
> > 
> >  [<c010f411>] kernel_thread_helper+0x5/0xb
> > 
> > Oops: 0002 [#1]
> > PREEMPT DEBUG_PAGEALLOC
> > Modules linked in:
> > CPU:    0
> > EIP:    0061:[<c030e587>]    Not tainted VLI
> > EFLAGS: 00010203   (2.6.9-xenU)
> > EIP is at init_tsc+0x4b/0x9e
> > eax: c02c6dd4   ebx: 0000c000   ecx: fbffc000   edx: 00000001
> > esi: 00000010   edi: c0102000   ebp: 00000000   esp: c0039f04
> > ds: 007b   es: 007b   ss: 0069
> > Process events/0 (pid: 3, threadinfo=c0038000 task=c003cac0)
> > Stack: c010eadd 00000000 c0109f80 fbffc000 000001e1 00000063 8ed0dd7b
> > 00000042
> >        c02c3200 c2dc5000 c02c5d80 00000000 c0038000 00000000 c012ca65
> > 00000000
> >        c0039f74 00000000 c003bf10 c0038000 c0038000 c0038000 c010a088
> > c0038000
> > Call Trace:
> >  [<c010eadd>] time_resume+0x12/0x51
> > 
> >  [<c0109f80>] __do_suspend+0x19f/0x1e0
> > 
> >  [<c012ca65>] worker_thread+0x22b/0x32f
> > 
> >  [<c010a088>] __shutdown_handler+0x0/0x48
> > 
> >  [<c01196c0>] default_wake_function+0x0/0x12
> > 
> >  [<c01196c0>] default_wake_function+0x0/0x12
> > 
> >  [<c012c83a>] worker_thread+0x0/0x32f
> > 
> >  [<c0130b89>] kthread+0xa5/0xab
> > 
> >  [<c0130ae4>] kthread+0x0/0xab
> > 
> >  [<c010f411>] kernel_thread_helper+0x5/0xb
> > 
> > Code: 00 00 00 00 00 00 00 00 70 0d 5a f6 00 00 00 00 00 00 00 00 00 00
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 21 00 00 00 00 00 <00> 4e
> > f7 ac 41 c8 a8 af 41 61 21 4c 41 00 00 00 00 00 00 01 00
> > 
> > I'm just starting to play with xen, so I haven't figured out much of the
> > debugging stuff yet.  If someone can point me in the right direction
> > though, I'd be happy to try to collect some more data if there's
> > anything that would be useful.
> > 
> > Thanks,
> > Paul Larson
> > 
> > 
> > 
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real users.
> > Discover which products truly live up to the hype. Start reading now. 
> > http://productguide.itmanagersjournal.com/
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/xen-devel
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-12-08  3:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-03 16:58 xen problem with save/restore Paul Larson
2004-12-03 17:48 ` Jérôme Petazzoni
2004-12-03 18:27   ` Brian Wolfe
2004-12-03 18:54   ` Paul Larson
2004-12-07  4:44 ` Paul Larson
2004-12-08  3:05   ` Paul Larson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-09 15:47 Ian Pratt
2004-12-09 21:56 ` Paul Larson
2004-12-09 16:55   ` Nuutti Kotivuori
2004-12-11 15:35   ` Paul Larson
2004-12-08  1:20 Ian Pratt
2004-12-09  0:44 ` Paul Larson
2004-12-08 19:59   ` Keir Fraser
2004-12-09  4:20     ` Paul Larson
2004-12-03 15:22 Paul Larson

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=1102475112.2708.1.camel@localhost.localdomain \
    --to=plars@linuxtestproject.org \
    --cc=xen-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.