All of lore.kernel.org
 help / color / mirror / Atom feed
From: Teemu Koponen <tkoponen@iki.fi>
To: xen-devel@lists.xensource.com
Subject: Linux-XenU kernel panic in allocs after live migration
Date: Tue, 10 May 2005 00:04:46 +0300	[thread overview]
Message-ID: <c1994a358ee224bc27cd193b02222a3d@iki.fi> (raw)

Hi,

While testing the live migration I run into a Linux-xenU kernel panic 
that is basically a show stopper. So far I have tested both with 2.0.5 
and testing that is a few days old. It seems that (all?) kernel allocs 
after live migration fail as  e.g. ping started before migration still 
runs stable after migration, but on the other hand starting a new 
instance of ping results in a panic. Process crash stack traces, the 
kernel throws to the console, seem always to end a kernel alloc, 
version or another. Regular save and restore for xenU work fine.

My setup is a vanilla "xen-make-world" with the exception that I 
enabled devfs support for the xenU. Moreover, compressed ram disk 
support is compiled in, but the panics occur with cramfs ramdisks and 
regular ext2fs ramdisks. My xenU mounts its root over NFS.

Is this a SUE, a feature, or a bug? :-)

An example of numerous panics:

<1>invalid operand: 0000 [#3]
PREEMPT
Modules linked in:
CPU:    0
EIP:    0061:[<c016a4ab>]    Not tainted VLI
EFLAGS: 00010292   (2.6.10-xenU)
EIP is at new_inode+0x9/0x80
eax: c031b1a0   ebx: 00000001   ecx: 00000001   edx: 00000000
esi: 00000001   edi: b7faac40   ebp: ffffff9f   esp: c04dff1c
ds: 007b   es: 007b   ss: 0069
Process login (pid: 566, threadinfo=c04de000 task=c00f15a0)
Stack: 0000000e 00000001 c02261e1 c0453e00 00000001 c0226f3e c0147966 
00030002
        00000001 fbffc000 b7faac40 c04de000 c02271a5 00000001 00000001 
00000000
        c04dff78 00000000 c0227204 00000001 00000001 00000000 c04dff78 
fbffc000
Call Trace:
  [<c02261e1>] sock_alloc+0x14/0x6c
  [<c0226f3e>] __sock_create+0x65/0x29d
  [<c0147966>] anon_vma_unlink+0x66/0x74
  [<c02271a5>] sock_create+0x2f/0x33
  [<c0227204>] sys_socket+0x28/0x55
  [<c022803e>] sys_socketcall+0x89/0x251
  [<c011c375>] sys_time+0x15/0x4a
  [<c0109044>] syscall_call+0x7/0xb
Code: f6 81 04 01 00 00 30 74 0a 89 0c 24 e8 60 0d 00 00 eb c3 85 c9 75 
da 89 f6 8d bc 27 00 00 00 00 eb cd 53 b8 a0 b1 31 c0 83 ec 04 <0f> 0d 
08 90 8b 44 24 0c 89 04 24 e8 45 f6 ff ff 85 c0 89 c3 74

Teemu

--

             reply	other threads:[~2005-05-09 21:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09 21:04 Teemu Koponen [this message]
2005-05-11 15:31 ` Linux-XenU kernel panic in allocs after live migration Teemu Koponen
2005-05-11 17:51   ` Kip Macy
2005-05-12 11:22     ` Teemu Koponen

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=c1994a358ee224bc27cd193b02222a3d@iki.fi \
    --to=tkoponen@iki.fi \
    --cc=xen-devel@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.