From: David Vrabel <david.vrabel@citrix.com>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: xen devel <xen-devel@lists.xensource.com>
Subject: Re: vmalloc_sync_all() patch problems?
Date: Wed, 28 Sep 2011 15:45:30 +0100 [thread overview]
Message-ID: <4E83330A.3030509@citrix.com> (raw)
In-Reply-To: <4E832F1A.3030209@theshore.net>
On 28/09/11 15:28, Christopher S. Aker wrote:
> 4.1.2-rc3-pre @ 23159
> 3.0.4 + vmalloc_sync_all() patch
This is surprising as that vmalloc_sync_all() patch is a revert of a
recent change only present in 3.0 and others have reported the patch
works for them.
You're going to have to provide more information on your system and
tests I think.
David
> While running my Xen test suite:
>
> BUG: unable to handle kernel paging request at bffffd68
> IP: [<c102bb51>] vmalloc_sync_all+0x141/0x1e0
> *pdpt = 0000000027d71027 *pde = 0000000000000000
> Oops: 0000 [#1] SMP
> Modules linked in: ebt_arp ip6t_rt ebt_mark ebt_limit ip6table_mangle
> xt_mark ebtable_nat ebtable_filter
> Pid: 39, comm: xenwatch Not tainted 3.0.4-1 #1 Supermicro X8DTU/X8DTU
> EIP: 0061:[<c102bb51>] EFLAGS: 00010283 CPU: 3
> EIP is at vmalloc_sync_all+0x141/0x1e0
> EAX: bffffd68 EBX: efe5a720 ECX: 00000008 EDX: 00000001
> ESI: ea082a34 EDI: c1a73d68 EBP: eb1d9e80 ESP: eb1d9e4c
> DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0069
> Process xenwatch (pid: 39, ti=eb1d8000 task=eb11b0c0 task.ti=eb1d8000)
> Stack:
> 2b048000 00000000 2b048000 00000000 fffff001 00000008 c0000d68 7bf85067
> f5a00000 00000018 ea254480 eb1d9f14 eb1d9f54 eb1d9e94 c10e5212 c10e35a0
> 00000000 e7d3d600 eb1d9ee4 c1446275 eb1d9ea8 c13932c0 e7d3d600 00000011
> Call Trace:
> [<c10e5212>] alloc_vm_area+0x42/0x60
> [<c10e35a0>] ? is_vmalloc_or_module_addr+0x50/0x50
> [<c1446275>] xen_blkif_map+0x35/0x1e0
> [<c13932c0>] ? xen_evtchn_do_upcall+0x20/0x30
> [<c1446a61>] frontend_changed+0x261/0x2d0
> [<c139852d>] xenbus_otherend_changed+0x7d/0x90
> [<c1398732>] frontend_changed+0x12/0x20
> [<c1396aa5>] xenwatch_thread+0x85/0x130
> [<c10625d0>] ? wake_up_bit+0x60/0x60
> [<c1396a20>] ? split+0xd0/0xd0
> [<c10621e4>] kthread+0x74/0x80
> [<c1062170>] ? kthread_worker_fn+0x160/0x160
> [<c16ca2b6>] kernel_thread_helper+0x6/0x10
> Code: c1 89 c7 81 e7 00 f0 ff ff 03 7d e4 8b 17 89 55 e8 8b 4f 04 83 e2
> 01 89 4d e0 0f 84 68 ff ff ff 8b 45 dc 25 00 f0 ff ff 03 45 e4 <8b> 08
> 8b 50 04 f6 c1 01 89 55 dc 74 7a 8b 55 dc 89 c8 ff 15 14
> EIP: [<c102bb51>] vmalloc_sync_all+0x141/0x1e0 SS:ESP 0069:eb1d9e4c
> CR2: 00000000bffffd68
> ---[ end trace 486c192808e46938 ]---
> INFO: rcu_sched_state detected stall on CPU 7 (t=60000 jiffies)
> INFO: rcu_sched_state detected stall on CPU 7 (t=240030 jiffies)
> ... and so on
>
> -Chris
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-09-28 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 14:28 vmalloc_sync_all() patch problems? Christopher S. Aker
2011-09-28 14:45 ` David Vrabel [this message]
2011-09-28 16:02 ` Christopher S. Aker
2011-09-28 17:04 ` David Vrabel
2011-09-30 15:38 ` Christopher S. Aker
2011-10-10 15:51 ` Konrad Rzeszutek Wilk
2011-10-11 15:18 ` Christopher S. Aker
2011-10-11 17:28 ` Konrad Rzeszutek Wilk
2011-10-12 19:37 ` Christopher S. Aker
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=4E83330A.3030509@citrix.com \
--to=david.vrabel@citrix.com \
--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.