[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] PCI interrupt setup failure: gateway

  • To: Xen Developers List <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Jonathan S. Shapiro" <shap@xxxxxxxxxxx>
  • Date: Fri, 06 May 2005 14:28:14 -0400
  • Delivery-date: Fri, 06 May 2005 18:27:49 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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.

In the pre-FC4 version of xen that is currently in the Fedora
development tree, I get the following diagnostic (from Xen) about midway
through the linux boot:

   PCI: No IRQ known for interrupt pin A of device 00:0a.0.
   Probably buggy MP table.

The PCI address in question is a cardbus bridge. The lspci info is

00:0a.o CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller
(rev 01)
        Subsystem: Rioworks: Unknown device 2032
        Flags: bus master, medium devsel, latency 168
        Memory at ffe7f000 (32-bit, non-prefetchable) [size=4K]
        Bus: primary=00, secondary=02, subordinate=05, sec-latency=176
        Memory window 1: 3ec00000-3efff000
        I/O window 0: 00004000-000040ff
        I/O window 1: 00004400-000044ff
        16-bit legacy interface ports at 0001

This is on a fairly new machine: Gateway 7426gx, which has an AMD64
mobile CPU.

Curiously, the system is also unable to locate the rhine ethernet device
at PCI 00:12.0, which the xen kernel claims is not present. This
suggests that other interrupt setup isn't going quite right either.

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.

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.


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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.