All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: xen devel <xen-devel@lists.xensource.com>
Subject: Re: [pv_ops domU] 2.6.30.5 - unable to handle kernel paging request / refresh_cpu_vm_stats / vmstat_update
Date: Mon, 17 Aug 2009 21:30:44 -0700	[thread overview]
Message-ID: <4A8A2E74.9010202@goop.org> (raw)
In-Reply-To: <4A89F539.2070801@theshore.net>

On 08/17/09 17:26, Christopher S. Aker wrote:
> Xen 3.3.4 64 bit
> 2.6.18 dom0 PAE
> 2.6.30.5 PAE domU
>
> BUG: unable to handle kernel paging request at 96443ad8
> IP: [<c0172b50>] refresh_cpu_vm_stats+0x70/0xc0
> *pdpt = 000000047b6e8027
> Oops: 0002 [#1] SMP
> last sysfs file:
> Modules linked in:
>
> Pid: 14, comm: events/3 Not tainted (2.6.30.5-linode20 #1)
> EIP: 0061:[<c0172b50>] EFLAGS: 00010246 CPU: 3
> EIP is at refresh_cpu_vm_stats+0x70/0xc0
> EAX: 96443a80 EBX: ffffffff ECX: 00000200 EDX: f57520c0
> ESI: c06fb300 EDI: c06fb100 EBP: d6073f2c ESP: d6073f28
>  DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0069
> Process events/3 (pid: 14, ti=d6072000 task=d605fc00 task.ti=d6072000)
> Stack:
>  00000200 00000000 00000000 00000000 00000000 00000000 00000000 00000000
>  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
>  00000000 00000000 00000000 00000000 d7033584 d7036b80 d7033580 c0172ba0
> Call Trace:
>  [<c0172ba0>] ? vmstat_update+0x0/0x30
>  [<c0172bab>] ? vmstat_update+0xb/0x30
>  [<c013afac>] ? worker_thread+0x12c/0x1c0
>  [<c011ee9b>] ? __wake_up_common+0x4b/0x80
>  [<c013ddb0>] ? autoremove_wake_function+0x0/0x40
>  [<c013ae80>] ? worker_thread+0x0/0x1c0
>  [<c013dab9>] ? kthread+0x49/0x80
>  [<c013da70>] ? kthread+0x0/0x80
>  [<c0108757>] ? kernel_thread_helper+0x7/0x10
> Code: 15 00 74 2f ff 15 1c 2c 6d c0 89 c1 ff 15 24 2c 6d c0 0f be 5c
> 16 15 89 c8 c6 44 16 15 00 ff 15 20 2c 6d c0 8d 84 97 80 06 00 00 <f0>
> 01 58 58 01 5c 95 00 83 c2 01 83 fa 13 75 c2 e8 4b 7c 42 00
> EIP: [<c0172b50>] refresh_cpu_vm_stats+0x70/0xc0 SS:ESP 0069:d6073f28
> CR2: 0000000096443ad8
> ---[ end trace c608c08376e3b403 ]---
>
> Full log: http://p.linode.com/2866

Does this happen every time, sometimes or just once?  Is it new with
2.6.30.5?  Are you using CONFIG_HIGHPTE?  What's the kernel config?

The top of the log appears to be missing.

Thanks,
    J

  reply	other threads:[~2009-08-18  4:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18  0:26 [pv_ops domU] 2.6.30.5 - unable to handle kernel paging request / refresh_cpu_vm_stats / vmstat_update Christopher S. Aker
2009-08-18  4:30 ` Jeremy Fitzhardinge [this message]
2009-08-18 14:16   ` Christopher S. Aker
2009-08-18 20:15     ` Jeremy Fitzhardinge
2009-08-18 20:56       ` Jeremy Fitzhardinge
2009-08-20 19:11       ` Jed Smith
2009-08-20 23:31         ` Jeremy Fitzhardinge
2009-08-21  0:13           ` Jed Smith
2009-08-21  0:38             ` Jeremy Fitzhardinge
2009-08-21 14:57               ` Jed Smith
2009-08-21 16:20                 ` Jeremy Fitzhardinge
2009-08-21 16:30                   ` Jed Smith
2009-08-21 16:16         ` Jeremy Fitzhardinge
2009-08-21 17:02           ` Jed Smith
2009-08-21 17:44             ` Jeremy Fitzhardinge
2009-08-21 16:16     ` Jeremy Fitzhardinge

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=4A8A2E74.9010202@goop.org \
    --to=jeremy@goop.org \
    --cc=caker@theshore.net \
    --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.