xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Marcial Rion <marcial.rion@swissonline.ch>
Cc: xen-devel@lists.xensource.com
Subject: Re: Issue with pv_ops Kernel 2.6.31.6 and Xen
Date: Mon, 8 Feb 2010 18:40:12 -0500	[thread overview]
Message-ID: <20100208234012.GA12527@phenom.dumpdata.com> (raw)
In-Reply-To: <4B70869A.5030701@swissonline.ch>

> Well, the console is not the problem (works as intended). It's raher the
> IRQ's taht are getting mixed up. It seems it's doing twice a mapping of
> IRQ (especially 9), once in XEN and once by the Kernel, which leeds to
> ACPI failing and no network connectivity (see also start oft his thread
> at
> http://lists.xensource.com/archives/html/xen-devel/2010-01/msg01049.html;
> somehow seems to got lost :-) ).

Ohh, that one.

Can you instrument this piece of code:

413         if (request_irq(irq, acpi_irq, IRQF_SHARED, "acpi", acpi_irq)) {
 414                 printk(KERN_ERR PREFIX "SCI (IRQ%d) allocation failed\n", irq);
 415                 return AE_NOT_ACQUIRED;
 416         }

To print out the return value of request_irq and see what it returns?

If it is EINVAL, instrument the 'request_irq' around its 'return
-EINVAL' to see which one fails.

Also can you provide the full serial output of the failing system
including Xen output?

      reply	other threads:[~2010-02-08 23:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22 22:38 Issue with pv_ops Kernel 2.6.31.6 and Xen Marcial Rion
2010-01-28  5:59 ` Marcial Rion
2010-01-28 19:46   ` Konrad Rzeszutek Wilk
2010-01-29 23:55     ` Marcial Rion
2010-01-30 21:11     ` Marcial Rion
2010-02-07 15:39       ` Marcial Rion
2010-02-08 18:22         ` Konrad Rzeszutek Wilk
2010-02-08 21:48           ` Marcial Rion
2010-02-08 23:40             ` Konrad Rzeszutek Wilk [this message]

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=20100208234012.GA12527@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=marcial.rion@swissonline.ch \
    --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).