xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Josef Vogt <josef.vogt@li-life.li>
Cc: xen-devel@lists.xensource.com
Subject: Re: Bug in PCI Passthrough
Date: Wed, 20 Apr 2011 15:38:37 -0400	[thread overview]
Message-ID: <20110420193836.GA32696@dumpdata.com> (raw)
In-Reply-To: <4DAF310F.4000401@li-life.li>

On Wed, Apr 20, 2011 at 09:16:31PM +0200, Josef Vogt wrote:
> Am 20.04.2011 14:51, schrieb Konrad Rzeszutek Wilk:
> >On Wed, Apr 20, 2011 at 11:15:23AM +0200, Josef Vogt wrote:
> >>Hello all
> >>
> >>I tried to enable PCI Passthrough in my Debian Squeeze installation.
> >>Unfortunately, it didnt work. The following bug showed up (excerpt
> >>from dmesg):
> >>
> >>[ 10.148612] uhci_hcd 0000:00:14.2: PCI INT D ->  Link[LNKD] ->  GSI 11
> >>(level, low) ->  IRQ 11
> >>[ 4.678352] Failed to setup GSI :11, err_code:-22
> >>[ 4.678480] dmfe 0000:00:0e.0: PCI INT A ->  Link[LNKB] ->  GSI 11 (level,
> >>low) ->  IRQ 11
> >>[ 6.868419] Failed to setup GSI :10, err_code:-22
> >That is most strange. Your interrupts are below IRQ 16, and they are level?
> >They should have been edge, unless you have some strange machine.
> >
> Hm... it's a rather old one: Compaq Deskpro PD1006 (Pentium III)

Can you boot the same kernel but without Xen and send the bootup output?
And also the /proc/interrupts (the full one).
> 
> >If you don't pass in the card to the DomU, but run it under Dom0, what is
> >the GSI and /proc/interrupts for the dmfe?
> 
> /proc/interrupts for dmfe in Dom0 (card is up and running, I disabled the other):
> cat /proc/interrupts | grep eth
> 11:        893  xen-pirq-xt-pic    uhci_hcd:usb1, eth0
> 
> GSI: I'm not so sure what you mean but this must be GSI 11 (see above or dmesg in attachment)

<blinks> Well, it looks like your motherboard has the IRQs below 16 to be level.
That is odd. 
> 
> >Can you also attach the full serial output? (so we can see the Xen hypervisor output
> >and the Linux Dom0 output).
> This is what i get (see attached logs)

Thank you.

  reply	other threads:[~2011-04-20 19:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20  9:15 Bug in PCI Passthrough Josef Vogt
2011-04-20 12:51 ` Konrad Rzeszutek Wilk
2011-04-20 19:16   ` Josef Vogt
2011-04-20 19:38     ` Konrad Rzeszutek Wilk [this message]
2011-04-20 20:01       ` Josef Vogt
2011-04-22 12:04         ` Was:Bug in PCI Passthrough. Is: XT-PIC controller not working with pvops kernel Konrad Rzeszutek Wilk
2011-04-22 12:41           ` Josef Vogt
2011-04-30 12:08             ` Josef Vogt
2011-05-02 14:06               ` Konrad Rzeszutek Wilk

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=20110420193836.GA32696@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=josef.vogt@li-life.li \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).