All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arun Sharma <arun.sharma@intel.com>
To: "Jonathan S. Shapiro" <shap@eros-os.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: PCI interrupt setup failure: gateway
Date: Fri, 06 May 2005 15:18:58 -0700	[thread overview]
Message-ID: <427BED52.70004@intel.com> (raw)
In-Reply-To: <1115413976.6039.0.camel@deskjob.eros-os.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

  reply	other threads:[~2005-05-06 22:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1115404114.25201@unix-os.sc.intel.com>
2005-05-06 20:14 ` PCI interrupt setup failure: gateway Arun Sharma
2005-05-06 21:12   ` Jonathan S. Shapiro
2005-05-06 22:18     ` Arun Sharma [this message]
2005-05-06 18:28 Jonathan S. Shapiro
2005-05-06 18:07 ` Mark Williamson
2005-05-08 18:57   ` Jonathan S. Shapiro
2005-05-08 11:18 ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=427BED52.70004@intel.com \
    --to=arun.sharma@intel.com \
    --cc=shap@eros-os.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.