All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Sander Eikelenboom <linux@eikelenboom.it>,
	Jan Beulich <JBeulich@suse.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: dom0 kernel - irq nobody cared ... the continuing saga ..
Date: Mon, 9 Feb 2015 15:18:15 +0000	[thread overview]
Message-ID: <54D8CFB7.6060000@citrix.com> (raw)
In-Reply-To: <132553031.20150209160327@eikelenboom.it>

On 09/02/15 15:03, Sander Eikelenboom wrote:
> Hi Jan / David / Konrad,
> 
> I was just testing a 3.19 kernel on my intel machine and again
> ran into the sporadically appearing "irq nobody cared" on the dom0 kernel.
> This occurs now for quite some kernel versions (running xen-unstable now,
> but it also appeared in the past with builds that are now xen-4.5).

I wouldn't suspect anything Xen related here.  IRQ #18 is a shared
line-level interrupt so other driver/device that was/is sharing than
line is misbehaving.

I'd recommend seeing if your BIOS has a option to put the disk
controllers into AHCI mode which would allow them to use MSIs (I think).

David

  reply	other threads:[~2015-02-09 15:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09 15:03 dom0 kernel - irq nobody cared ... the continuing saga Sander Eikelenboom
2015-02-09 15:18 ` David Vrabel [this message]
2015-02-09 15:39   ` Sander Eikelenboom
2015-02-09 16:36   ` Jan Beulich
2015-02-09 17:13     ` Sander Eikelenboom
2015-02-10  8:48       ` Jan Beulich
2015-02-10  9:19         ` Sander Eikelenboom
2015-02-10  9:35           ` Jan Beulich
2015-02-10 10:03             ` Sander Eikelenboom
2015-02-10 10:36               ` Jan Beulich
2015-02-10 10:47                 ` Sander Eikelenboom
2015-02-10 10:57                   ` Jan Beulich
2015-02-10 10:59                   ` Andrew Cooper
2015-02-10 11:21                     ` Jan Beulich
2015-02-10 13:07             ` Sander Eikelenboom
2015-02-10 13:26               ` Jan Beulich
2015-02-10 15:35                 ` Sander Eikelenboom
2015-02-10 15:46                   ` Konrad Rzeszutek Wilk
2015-02-10 16:22                   ` Jan Beulich
2015-02-10 17:30                     ` Sander Eikelenboom
2015-02-10 17:47                       ` Jan Beulich
2015-02-10 18:26                         ` Sander Eikelenboom
2015-02-10 15:13               ` 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=54D8CFB7.6060000@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux@eikelenboom.it \
    --cc=xen-devel@lists.xen.org \
    /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.