WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] boot failure in recent cset... dom0 compat issue?

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] boot failure in recent cset... dom0 compat issue?
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Fri, 30 Jan 2009 15:51:47 +0000 (GMT)
Cc:
Delivery-date: Fri, 30 Jan 2009 07:54:07 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1938a110-71c6-4d49-b011-d34e2a9f4bc0@default>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> 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 
> 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?
> 
> 
> I can confirm that c/s 19064 boots my dom0 fine and
> c/s 19065 fails to boot.
> 
> > > 3.1-timeframe 2.6.18.8-based dom0.
> 
> 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?)
> 
> My machine is a standard Intel Weybridge box (though
> its possible the firmware is old).
> 
> > -----Original Message-----
> > From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx]
> > 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?
> > 
> > 
> > Shouldn't be a dom0 compat issue. More likely something to do 
> > with the Xen
> > heap removal. Some issues are fixed already but perhaps more 
> > are lurking.
> > 
> >  -- Keir
> > 
> > On 29/01/2009 22:12, "Dan Magenheimer" 
> > <dan.magenheimer@xxxxxxxxxx> wrote:
> > 
> > > 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.)
> > > 
> > > Thanks,
> > > Dan
> > > 
> > > 
> > > (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=0x104)
> > > ata1: port failed to respond (30 secs)
> > > ata1: COMRESET failed (device not ready)
> > > ata1.00: revalidation failed (errno=-5)
> > > ata1: port failed to respond (30 secs)
> > > ata1: COMRESET failed (device not ready)
> > > ata1.00: revalidation failed (errno=-5)
> > > 
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-devel
> > 
> > 
> >
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel