Hi there,
On Friday 06 May 2005 19:28, Jonathan S. Shapiro wrote:
> I'm seeing what appears to be an interrupt setup failure. It occurs both
> in the current pre-FC4 xen RPM and also in the xen-unstable tree from
> last night. I'm unable to pull from the bitkeeper repository -- Larry
> McVoy denied us a license because we work on OpenCM and that competes
> with Bitkeeper.
Have you tried SourcePuller? http://sourceforge.net/projects/sourcepuller/
It's the notorious Tridge-designed BK client. It doesn't have the SCM
functionality but should perhaps be sufficient to get the latest source out
of BK?
Or there's the BK open source client http://www.bitmover.com/bk-client.shar -
this was originally under the "No Whiners License" but I think it's actually
BSD licensed, or something similar.
Anyhow, I stuck a tarball of the latest and greatest BK tree at:
http://www.cl.cam.ac.uk/~maw48/xen-devel-20050506-maw.bk.tar.bz2
It should contain the latest patches - maybe it will help.
> Since I cannot get to the bitkeeper repository, I attempted to build and
> run the latest xen-unstable tarball -- partly because that has some of
> the new ACPI patches. This didn't help at all -- I suspect the problem
> is that cardbus support may not exist in Xen yet.
Xen doesn't let Linux see behind Cardbus bridges, so that wouldn't work. The
new PCI / ACPI patches may support it, although I haven't tried.
Cheers,
Mark
> However, I *did* notice that xen-unstable exhibits significantly reduced
> function relative to the current FC4-devel RPM. X windows crashes, one
> of the early setup tools in the boot process also crashes. Possibly
> Jeremy's patches are not migrating back into the tree promptly?
>
> At the moment, I'ld appreciate some guidance on where to look.
>
> shap
>
> On Thu, 2005-05-05 at 02:35 +0100, Ian Pratt wrote:
> > > I now have xen up from the FC4-- repository on two machines.
> > > One works fine, the other is a very new amd64, and xen is
> > > having trouble parsing the bios tables (therefore unable to
> > > find the interrupt line for the enet controller).
> >
> > The ACPI patch went in to unstable.bk yesterday -- it would be very
> > interesting to know whether it helped or made things worse.
> >
> > > I'm happy to instrument/debug, but who's the right contact
> > > person? Can join xen-developers list if needed, but the
> > > traffic is heavy...
> >
> > I'd prefer I you could post to xen-devel, even if you don't subscribe.
> >
> > Thanks,
> > Ian
> >
> > > shap
> > >
> > > On Sun, 2005-05-01 at 05:26 +0100, Ian Pratt wrote:
> > > > > > BTW: big ACPI support patch going in next week. Mightn't be
> > > > >
> > > > > too hard
> > > > >
> > > > > > to get power management working on top of it...
> > > > >
> > > > > Great. Now if only you would dump bitkeeper. One of the
> > >
> > > reasons that
> > >
> > > > > I have been unable to track the Xen project more closely
> > >
> > > is that I
> > >
> > > > > cannot install the bitkeeper client. Linus isn't the only
> > >
> > > person for
> > >
> > > > > whom Larry has made legal problems.
> > > >
> > > > We'll be putting up a CVS server of the head of the repository.
> > > >
> > > > Ian
>
> _______________________________________________
> 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
|
Home