All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Liwei <xieliwei@gmail.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: "ACPI: Unable to start the ACPI Interpreter"
Date: Mon, 27 Jun 2011 15:30:51 -0400	[thread overview]
Message-ID: <20110627193051.GA14665@dumpdata.com> (raw)
In-Reply-To: <BANLkTim7suw8ZU5xUkCD6AzJBCWJUN_9mw@mail.gmail.com>

On Tue, Jun 28, 2011 at 03:18:21AM +0800, Liwei wrote:
> On 28 June 2011 03:10, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> >
> > Another glance shows:
> >
> > (2.6.32):
> > [    3.502771] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 20 low level)
> > [    3.502773] xen: sci override: source_irq=9 global_irq=20 trigger=c polarity=3
> > [    3.502775] xen: registering gsi 20 triggering 0 polarity 1
> > [    3.502780]   alloc irq_desc for 20 on node 0
> >
> > So it has IRQ 9 mapped to IRQ 20 while in 3.0:
> >
> > [    3.803695] xen: --> pirq=7 -> irq=7
> > [    3.803699] xen: --> pirq=8 -> irq=8
> > [    3.803702] xen: --> pirq=10 -> irq=10
> >
> > we skip over IRQ 9. We should have gotten something like this:
> >
> > [    7.059735] xen_map_pirq_gsi: returning irq 20 for gsi 9
> > [    7.064933] xen: --> pirq=20 -> irq=9
> >
> > But we did not. If you can instrument 'acpi_get_override_irq' to see
> > at which of the numerous 'return -1' it fails  that might narrow down
> > the issue.
> >
> 
> Erm, do you want me to set up some kernel tracing or just add a printk
> to acpi_get_override_irq? My kernel hacking foo is very limited.

Just splash some printk's around there and print out the values of gsi and pins.
Nothing fancy.

  reply	other threads:[~2011-06-27 19:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24 18:55 "ACPI: Unable to start the ACPI Interpreter" Liwei
2011-06-25 12:33 ` Liwei
     [not found]   ` <20110627133936.GB6978@dumpdata.com>
2011-06-27 15:12     ` Liwei
2011-06-27 16:32       ` Konrad Rzeszutek Wilk
2011-06-27 16:59         ` Liwei
2011-06-27 17:33           ` Konrad Rzeszutek Wilk
2011-06-27 18:23             ` Liwei
2011-06-27 18:59               ` Konrad Rzeszutek Wilk
2011-06-27 19:10               ` Konrad Rzeszutek Wilk
2011-06-27 19:18                 ` Liwei
2011-06-27 19:30                   ` Konrad Rzeszutek Wilk [this message]
2011-06-27 20:32                     ` Liwei
2011-06-27 21:09                       ` Liwei
2011-06-28 18:12                         ` Konrad Rzeszutek Wilk
2011-06-28 18:33                           ` Liwei
2011-06-28 19:27                             ` Konrad Rzeszutek Wilk
2011-06-28 19:49                               ` Liwei
2011-06-28 19:51                                 ` Konrad Rzeszutek Wilk
2011-06-28 19:55                                   ` Liwei
2011-06-28 20:44                                     ` Konrad Rzeszutek Wilk
2011-06-29 13:09                                       ` Liwei
2011-06-29 13:37                                         ` Liwei
  -- strict thread matches above, loose matches on Subject: below --
2011-06-29 14:23 Konrad Wilk
2011-06-29 15:20 ` Liwei

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=20110627193051.GA14665@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xieliwei@gmail.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.