From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Magenheimer Subject: RE: boot failure in recent cset... dom0 compat issue? Date: Fri, 30 Jan 2009 15:51:47 +0000 (GMT) Message-ID: <9b34506b-01c3-4bb2-b940-3661c23e3c4e@default> References: <1938a110-71c6-4d49-b011-d34e2a9f4bc0@default> Mime-Version: 1.0 Content-Type: text/plain; charset=Windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1938a110-71c6-4d49-b011-d34e2a9f4bc0@default> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser , "Xen-Devel (E-mail)" List-Id: xen-devel@lists.xenproject.org > Sorry, that was a typo, should have been 3.3(.0)-timeframe > 2.6.18.8-based dom0, built 2008 Sept 18, probably from whatever > was auto-hg-pull'ed by a Xen build on that day. (Is there > a way similar to xm info to check the c/s of a dom0?) In case it matters, it appears dom0 was c/s 664 from http://xenbits.xensource.com/linux-2.6.18-xen.hg (Found from code examination... is there a better way to find the c/s of a dom0?) > -----Original Message----- > From: Dan Magenheimer=20 > Sent: Friday, January 30, 2009 8:40 AM > To: Keir Fraser; Xen-Devel (E-mail) > Subject: RE: [Xen-devel] boot failure in recent cset... dom0 compat > issue? >=20 >=20 > I can confirm that c/s 19064 boots my dom0 fine and > c/s 19065 fails to boot. >=20 > > > 3.1-timeframe 2.6.18.8-based dom0. >=20 > Sorry, that was a typo, should have been 3.3(.0)-timeframe > 2.6.18.8-based dom0, built 2008 Sept 18, probably from whatever > was auto-hg-pull'ed by a Xen build on that day. (Is there > a way similar to xm info to check the c/s of a dom0?) >=20 > My machine is a standard Intel Weybridge box (though > its possible the firmware is old). >=20 > > -----Original Message----- > > From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > > Sent: Thursday, January 29, 2009 3:32 PM > > To: Dan Magenheimer; Xen-Devel (E-mail) > > Subject: Re: [Xen-devel] boot failure in recent cset... dom0 compat > > issue? > >=20 > >=20 > > Shouldn't be a dom0 compat issue. More likely something to do=20 > > with the Xen > > heap removal. Some issues are fixed already but perhaps more=20 > > are lurking. > >=20 > > -- Keir > >=20 > > On 29/01/2009 22:12, "Dan Magenheimer"=20 > > wrote: > >=20 > > > Hmmm... somewhere between xen-unstable cset 19043 and 19109 > > > my Intel Weybridge box stops booting dom0. Is this a known > > > problem? I am admittedly trying to boot a 4 months old > > > 3.1-timeframe 2.6.18.8-based dom0. Were hypervisor changes > > > made recently that render older dom0's useless? (I realize > > > this happens sometimes with xen-unstable, just wondering if > > > this is indeed the problem and, if so, if it was intentional.) > > >=20 > > > Thanks, > > > Dan > > >=20 > > >=20 > > > (XEN) PCI add device 00:03.2 > > > (XEN) PCI remove device 00:03.2 > > > (XEN) PCI add device 00:1f.5 > > > (XEN) PCI remove device 00:1f.5 > > > (XEN) PCI add device 00:1a.7 > > > (XEN) PCI add device 00:1d.7 > > > (XEN) PCI add device 00:1a.0 > > > (XEN) PCI add device 00:1a.1 > > > (XEN) PCI add device 00:1a.2 > > > (XEN) PCI add device 00:1d.0 > > > (XEN) PCI add device 00:1d.1 > > > (XEN) PCI add device 00:1d.2 > > > (XEN) PCI add device 00:1f.2 > > > ata1.00: failed to set xfermode (err_mask=3D0x104) > > > ata1: port failed to respond (30 secs) > > > ata1: COMRESET failed (device not ready) > > > ata1.00: revalidation failed (errno=3D-5) > > > ata1: port failed to respond (30 secs) > > > ata1: COMRESET failed (device not ready) > > > ata1.00: revalidation failed (errno=3D-5) > > >=20 > > >=20 > > >=20 > > >=20 > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel@lists.xensource.com > > > http://lists.xensource.com/xen-devel > >=20 > >=20 > > >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >