From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: 2.6.26-rc8 pv_ops causes Unhandled invalid opcode fault/trap Date: Thu, 01 Jan 2009 08:45:41 +1100 Message-ID: <495BE805.10308@goop.org> References: <486CE463.3070002@theshore.net> <486CF3F7.3030309@goop.org> <486CF789.7030700@theshore.net> <486D0DA6.7010901@goop.org> <486D197A.7040808@theshore.net> <486D2AED.4020407@goop.org> <486D38D5.5000901@theshore.net> <486D3EC3.1010303@goop.org> <494A6CDC.8090204@inria.fr> <494C1177.8060101@goop.org> <494CF52B.7030400@inria.fr> <494D4AFD.3040903@goop.org> <4950F30E.6060904@inria.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4950F30E.6060904@inria.fr> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Guillaume Rousse Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org Guillaume Rousse wrote: > Jeremy Fitzhardinge a =E9crit : >> Guillaume Rousse wrote: >>> Jeremy Fitzhardinge a =E9crit : >>>> Guillaume Rousse wrote: >>>>> Jeremy Fitzhardinge a =E9crit : >>>>>>> FWIW, I just tried 2.6.26-rc1 and it booted fine. I can narrow=20 >>>>>>> it down further if that'd be useful to you. >>>>>>> =20 >>>>>> >>>>>> Yes, please. >>>>> Was there any final conclusion there ? Because I'm currently=20 >>>>> 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=20 >>>> symptom. What's happening on the Linux side when the domain=20 >>>> 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=3D46470 >> >> Does earlyprintk=3Dxen reveal anything more? What does the rip=20 >> (ffffffff8020b3ed) map to in the kernel? > I guess earlyprintk=3Dxen is a dom0 option, because passing it to domU=20 > didn't change anything. It will be most helpful if you're running a debug=3Dy build of Xen, so th= e=20 domU's early console output appears on the Xen console. > The given adress map to set_page_prot, according to the System.map file= . That's interesting. > BTW, it only happens with ISCSI-stored hosts, whereas it works OK with=20 > LVM-stored hosts (tough on slightly different hardware).=20 Uh, that's very mysterious. The underlying storage shouldn't have any=20 effect on whether the kernel can boot - it's either loaded or not. > On other hosts, the guest kernel boots OK, and then fails to mount=20 > underlying FS (but that's a different issue). I updated upstream=20 > report with details. I'm on vacation at the moment, but I'll give this a closer look when I=20 return. J