From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Sharma Subject: Re: PCI interrupt setup failure: gateway Date: Fri, 06 May 2005 15:18:58 -0700 Message-ID: <427BED52.70004@intel.com> References: <427BD033.6090202@intel.com> <1115413976.6039.0.camel@deskjob.eros-os.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1115413976.6039.0.camel@deskjob.eros-os.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Jonathan S. Shapiro" Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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