From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: 2.6.26-rc8 pv_ops causes Unhandled invalid opcode fault/trap
Date: Tue, 23 Dec 2008 15:17:50 +0100 [thread overview]
Message-ID: <4950F30E.6060904@inria.fr> (raw)
In-Reply-To: <494D4AFD.3040903@goop.org>
Jeremy Fitzhardinge a écrit :
> Guillaume Rousse wrote:
>> Jeremy Fitzhardinge a écrit :
>>> Guillaume Rousse wrote:
>>>> Jeremy Fitzhardinge a écrit :
>>>>>> FWIW, I just tried 2.6.26-rc1 and it booted fine. I can narrow it
>>>>>> down further if that'd be useful to you.
>>>>>>
>>>>>
>>>>> Yes, please.
>>>> Was there any final conclusion there ? Because I'm currently trying
>>>> a 2.6.27.5 with the same kind of issue:
>>>
>>> I don't know of any outstanding bugs which cause this kind of
>>> symptom. What's happening on the Linux side when the domain crashes
>>> this way?
>> Immediate crash, without further information.
>>
>> I've opened a but report on mandriva bugzilla:
>> https://qa.mandriva.com/show_bug.cgi?id=46470
>
> Does earlyprintk=xen reveal anything more? What does the rip
> (ffffffff8020b3ed) map to in the kernel?
I guess earlyprintk=xen is a dom0 option, because passing it to domU
didn't change anything. The given adress map to set_page_prot, according
to the System.map file.
BTW, it only happens with ISCSI-stored hosts, whereas it works OK with
LVM-stored hosts (tough on slightly different hardware). On other hosts,
the guest kernel boots OK, and then fails to mount underlying FS (but
that's a different issue). I updated upstream report with details.
--
Guillaume Rousse
Service des Moyens Informatiques
INRIA Saclay - Ile de France
Tel: 01 69 35 69 62
next prev parent reply other threads:[~2008-12-23 14:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 14:38 2.6.26-rc8 pv_ops causes Unhandled invalid opcode fault/trap Christopher S. Aker
2008-07-03 15:44 ` Jeremy Fitzhardinge
2008-07-03 15:44 ` Jeremy Fitzhardinge
2008-07-03 16:00 ` Christopher S. Aker
2008-07-03 16:00 ` Christopher S. Aker
2008-07-03 17:34 ` Jeremy Fitzhardinge
2008-07-03 17:34 ` Jeremy Fitzhardinge
2008-07-03 18:24 ` Christopher S. Aker
2008-07-03 19:39 ` Jeremy Fitzhardinge
2008-07-03 20:38 ` Christopher S. Aker
2008-07-03 20:38 ` Christopher S. Aker
2008-07-03 21:04 ` Jeremy Fitzhardinge
2008-12-18 15:31 ` Guillaume Rousse
2008-12-19 21:26 ` Jeremy Fitzhardinge
2008-12-20 13:37 ` Guillaume Rousse
2008-12-20 19:43 ` Jeremy Fitzhardinge
2008-12-23 14:17 ` Guillaume Rousse [this message]
2008-12-31 21:45 ` Jeremy Fitzhardinge
2008-07-03 21:04 ` Jeremy Fitzhardinge
2008-07-03 19:39 ` Jeremy Fitzhardinge
2008-07-03 18:24 ` 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=4950F30E.6060904@inria.fr \
--to=guillaume.rousse@inria.fr \
--cc=jeremy@goop.org \
--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.