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. > > 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. >Please try the latest tree that Mark posted. If it still doesn''t work, please open a bugzilla (bugzilla.xensource.com) and cc me and Keir with your full dmesg. -Arun _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jonathan S. Shapiro
2005-May-06 21:12 UTC
Re: [Xen-devel] PCI interrupt setup failure: gateway
On Fri, 2005-05-06 at 13:14 -0700, Arun Sharma wrote:> > PCI: No IRQ known for interrupt pin A of device 00:0a.0. > > Probably buggy MP table. > > > > Please try the latest tree that Mark posted. If it still doesn''t work, > please open a bugzilla (bugzilla.xensource.com) and cc me and Keir with > your full dmesg. >Happy to do so. In the event that I need to send you diagnostic output, is there some means to retrieve the boot messages from the xen subsystem as well? I ask because the diagnostic in question wasn''t a linux diagnostic. It was a xen diagnostic. shap _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jonathan S. Shapiro wrote:> On Fri, 2005-05-06 at 13:14 -0700, Arun Sharma wrote: > >>> PCI: No IRQ known for interrupt pin A of device 00:0a.0. >>> Probably buggy MP table. >>> >> >>Please try the latest tree that Mark posted. If it still doesn''t work, >>please open a bugzilla (bugzilla.xensource.com) and cc me and Keir with >>your full dmesg. >> > > > Happy to do so. In the event that I need to send you diagnostic output, > is there some means to retrieve the boot messages from the xen subsystem > as well? > > I ask because the diagnostic in question wasn''t a linux diagnostic. It > was a xen diagnostic. >Yes, if you use a line such as: kernel /xen.gz com1=115200,8n1 in your grub.conf (also called menu.lst), then you should be able to capture it via the serial console. If your dom0 boots, you can retrieve the same via: # xend start # xm dmesg > xen.txt # dmesg > linux.txt -Arun _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel