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] PCI interrupt setup failure: gateway

To: "Jonathan S. Shapiro" <shap@xxxxxxxxxxx>
Subject: Re: [Xen-devel] PCI interrupt setup failure: gateway
From: Arun Sharma <arun.sharma@xxxxxxxxx>
Date: Fri, 06 May 2005 15:18:58 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 06 May 2005 22:18:21 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1115413976.6039.0.camel@xxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <mailman.1115404114.25201@xxxxxxxxxxxxxxxxxxxx> <427BD033.6090202@xxxxxxxxx> <1115413976.6039.0.camel@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2-1.3.2 (X11/20050324)
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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>