From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andreas Kinzler <ml-xen-devel@hfp.de>
Cc: "Alan J. Wylie" <NDA5OWUy@wylie.me.uk>, xen-devel@lists.xensource.com
Subject: Re: Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
Date: Tue, 12 Oct 2010 11:49:29 -0700 [thread overview]
Message-ID: <4CB4ADB9.2030704@goop.org> (raw)
In-Reply-To: <4CB41800.7050806@hfp.de>
On 10/12/2010 01:10 AM, Andreas Kinzler wrote:
> On 07.10.2010 11:57, Alan J. Wylie wrote:
>> System: Supermicro SM-SC825TQ-R720LPB, 8GB RAM
>> Motherboard: X8DTL
>> Processor: 1 x Intel XEON E5506 quad core
>> RAID controller: LSI MegaRAID SAS 8708
>>
>> Bisected (by hand) to between
>> 69e50db2 (good) 2.6.32.21 "Merge commit 'v2.6.32.21' into
>> xen/next-2.6.32"
>> and
>> dda56688 (bad) "Merge branch 'xen/next' into
>> xen/next-2.6.32"
>>
>> ffffffff8100bd10 T get_phys_to_machine
>> ffffffff8100bd4c t pin_pagetable_pfn
>
> I am afflicted by this problem for a long while now. Should look very
> familiar to you. See
> http://lists.xensource.com/archives/html/xen-devel/2010-09/msg00758.html
>
> No solution till now.
Is it not fixed by current xen/stable-2.6.32.x kernels?
J
next prev parent reply other threads:[~2010-10-12 18:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 9:57 Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)" Alan J. Wylie
2010-10-07 10:25 ` Alan J. Wylie
2010-10-08 14:08 ` Alan J. Wylie
2010-10-12 8:10 ` Andreas Kinzler
2010-10-12 18:49 ` Jeremy Fitzhardinge [this message]
2010-10-12 20:02 ` Valtteri Kiviniemi
2010-10-13 0:26 ` Jeremy Fitzhardinge
2010-10-13 7:03 ` Valtteri Kiviniemi
2010-10-13 7:26 ` Alan J. Wylie
2010-10-13 11:04 ` Alan J. Wylie
2010-10-13 13:52 ` Alan J. Wylie
2010-10-13 14:17 ` Alan J. Wylie
2010-10-13 15:52 ` Alan J. Wylie
2010-10-19 13:15 ` Andreas Kinzler
2010-10-19 13:51 ` Alan J. Wylie
2010-10-19 14:29 ` Gianni Tedesco
2010-10-19 14:58 ` sven
2010-10-19 15:45 ` Gianni Tedesco
2010-10-19 18:01 ` sven
2010-10-19 18:20 ` Gianni Tedesco
2010-10-19 19:05 ` sven
2010-10-19 23:31 ` Andreas Kinzler
2010-10-20 8:54 ` Gianni Tedesco
2010-10-29 15:44 ` Gianni Tedesco
2010-10-29 16:15 ` Konrad Rzeszutek Wilk
2010-11-01 13:37 ` Jeremy Fitzhardinge
2010-11-01 17:39 ` Konrad Rzeszutek Wilk
2010-11-01 17:46 ` Jeremy Fitzhardinge
2010-11-01 17:46 ` Konrad Rzeszutek Wilk
2010-11-01 18:16 ` Jeremy Fitzhardinge
2010-11-01 18:19 ` Gianni Tedesco
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=4CB4ADB9.2030704@goop.org \
--to=jeremy@goop.org \
--cc=NDA5OWUy@wylie.me.uk \
--cc=ml-xen-devel@hfp.de \
--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.