WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Unable to handle paging request

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Unable to handle paging request
From: "Rishi Gokhale" <Rishi.Gokhale@xxxxxxxxxxxxxxxxxx>
Date: Wed, 3 Jan 2007 15:01:04 -0500
Delivery-date: Thu, 04 Jan 2007 01:22:22 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccvceYsKigGfK7aTKKODL9h4rQ/2w==
Thread-topic: Unable to handle paging request

Hey Guys,

 

I am using the xen 2.6.11.12 xen kernel to run a xen system. Am pretty new to xen and xen administration.

 

I have a script that builds rpms. So basically the things happening are

 

Tarring some code

Compiling it

And packaging it into rpms.

 

While this script is running I sometimes get Unable to handle paging request issues that crash the xen client, the logs are as follows

 

Jan  2 19:40:15  server sshd(pam_unix)[10954]: session opened for user tabasco2 by (uid=500)

Jan  2 19:42:19 server kernel: Unable to handle kernel paging request at virtual address c00cf680

Jan  2 19:42:19 server kernel:  printing eip:

Jan  2 19:42:19 server kernel: c0144c78

Jan  2 19:42:19 server kernel: *pde = ma 0af0f067 pa 005e0067

Jan  2 19:42:19 server kernel: *pte = ma 0a7a0063 pa 000cf063

Jan  2 19:42:19 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:19 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:19 server kernel:  [<c01452f4>] __blk_queue_bounce+0x1d4/0x260

Jan  2 19:42:19 server kernel:  [<c01453b6>] blk_queue_bounce+0x36/0x50

Jan  2 19:42:19 server kernel:  [<c0290a7c>] __make_request+0x4c/0x550

Jan  2 19:42:19 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:19 server kernel:  [<c0291332>] generic_make_request+0x92/0x200

Jan  2 19:42:19 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:20 server kernel:  [<c010dbce>] do_IRQ+0x1e/0x30

Jan  2 19:42:20 server kernel:  [<c0105eb3>] evtchn_do_upcall+0x83/0xa0

Jan  2 19:42:20 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:20 server kernel:  [<c013a511>] mempool_alloc+0x81/0x1f0

Jan  2 19:42:20 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:20 server kernel:  [<c02914fa>] submit_bio+0x5a/0xf0

Jan  2 19:42:20 server kernel:  [<c0274040>] memmove+0x50/0x70

Jan  2 19:42:20 server kernel:  [<c015e6eb>] bio_alloc+0x16b/0x1e0

Jan  2 19:42:20 server kernel:  [<c015a6c0>] end_buffer_write_sync+0x0/0x70

Jan  2 19:42:20 server kernel:  [<c015def5>] submit_bh+0xe5/0x130

Jan  2 19:42:20 server kernel:  [<c015dfc2>] ll_rw_block+0x82/0xb0

Jan  2 19:42:20 server kernel:  [<c01d6d1e>] journal_commit_transaction+0xa3e/0x1250

Jan  2 19:42:20 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:20 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:20 server kernel:  [<c01d996d>] kjournald+0xdd/0x290

Jan  2 19:42:20 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:20 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:20 server kernel:  [<c0109172>] ret_from_fork+0x6/0x1c

Jan  2 19:42:20 server kernel:  [<c01d9870>] commit_timeout+0x0/0x10

Jan  2 19:42:20 server kernel:  [<c01d9890>] kjournald+0x0/0x290

Jan  2 19:42:20 server kernel:  [<c01071e5>] kernel_thread_helper+0x5/0x10

Jan  2 19:42:20 server kernel: Oops: 0003 [#1]

Jan  2 19:42:20 server kernel: PREEMPT

Jan  2 19:42:20 server kernel: CPU:    0

Jan  2 19:42:20 server kernel: EIP:    0061:[<c0144c78>]    Not tainted VLI

Jan  2 19:42:20 server kernel: EFLAGS: 00010206   (2.6.11.12-4-xenU)

Jan  2 19:42:20 server kernel: EIP is at kmap_high+0x1b8/0x210

Jan  2 19:42:20 server kernel: eax: 64eb5063   ebx: fb9a0000   ecx: 000001a0   edx: 0005a63a

Jan  2 19:42:20 server kernel: esi: c1b4c740   edi: 00000063   ebp: c00cf000   esp: f36efc04

Jan  2 19:42:20 server kernel: ds: 007b   es: 007b   ss: 0069

Jan  2 19:42:20 server kernel: Process kjournald (pid: 819, threadinfo=f36ee000 task=f19d8a00)

Jan  2 19:42:20 server kernel: Stack: c1b4c740 00000000 00000000 f19d8a00 c0132b40 f36efc38 f36efc38 c1d2af00

Jan  2 19:42:20 server kernel:        00000220 00000000 00000000 f19d8a00 c0132b40 f36efc38 f36efc38 00000010

Jan  2 19:42:20 server kernel:        fb9a0000 00000000 f30c4be0 ed9ae480 c05f6f60 f30c4bf0 c01452f4 c1b4c740

Jan  2 19:42:20 server kernel: Call Trace:

Jan  2 19:42:20 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:20 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:20 server kernel:  [<c01452f4>] __blk_queue_bounce+0x1d4/0x260

Jan  2 19:42:20 server kernel:  [<c01453b6>] blk_queue_bounce+0x36/0x50

Jan  2 19:42:20 server kernel:  [<c0290a7c>] __make_request+0x4c/0x550

Jan  2 19:42:20 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:20 server kernel:  [<c0291332>] generic_make_request+0x92/0x200

Jan  2 19:42:20 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:20 server kernel:  [<c010dbce>] do_IRQ+0x1e/0x30

Jan  2 19:42:20 server kernel:  [<c0105eb3>] evtchn_do_upcall+0x83/0xa0

Jan  2 19:42:20 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:20 server kernel:  [<c013a511>] mempool_alloc+0x81/0x1f0

Jan  2 19:42:20 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:20 server kernel:  [<c02914fa>] submit_bio+0x5a/0xf0

Jan  2 19:42:20 server kernel:  [<c0274040>] memmove+0x50/0x70

Jan  2 19:42:20 server kernel:  [<c015e6eb>] bio_alloc+0x16b/0x1e0

Jan  2 19:42:20 server kernel:  [<c015a6c0>] end_buffer_write_sync+0x0/0x70

Jan  2 19:42:20 server kernel:  [<c015def5>] submit_bh+0xe5/0x130

Jan  2 19:42:20 server kernel:  [<c015dfc2>] ll_rw_block+0x82/0xb0

Jan  2 19:42:20 server kernel:  [<c01d6d1e>] journal_commit_transaction+0xa3e/0x1250

Jan  2 19:42:21 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:21 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:21 server kernel:  [<c01d996d>] kjournald+0xdd/0x290

Jan  2 19:42:21 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:21 server kernel:  [<c0132b40>] autoremove_wake_function+0x0/0x60

Jan  2 19:42:21 server kernel:  [<c0109172>] ret_from_fork+0x6/0x1c

Jan  2 19:42:21 server kernel:  [<c01d9870>] commit_timeout+0x0/0x10

Jan  2 19:42:21 server kernel:  [<c01d9890>] kjournald+0x0/0x290

Jan  2 19:42:21 server kernel:  [<c01071e5>] kernel_thread_helper+0x5/0x10

Jan  2 19:42:21 server kernel: Code: c0 c1 ff 05 c1 e7 0c 09 c7 f7 c7 01 00 00 00 89 f8 74 18 a1 44 db 3f c0 89 fa c1 ea 0c 81 e7 ff 0f 0

0 00 8b 04 90 c1 e0 0c 09 f8 <89> 44 8d 00 a1 60 fc 40 c0 bd 01 00 00 00 89 5c 24 04 89 34 24

Jan  2 19:42:21 server kernel:  <6>note: kjournald[819] exited with preempt_count 1

Jan  2 19:46:26 server syslogd 1.4.1: restart.

Jan  2 19:46:26 server syslog: syslogd startup succeeded

 

 

Any help on how to troubleshoot this issue will be greatly appreciated.

 

Rishi

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>