All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Dom0 losing interrupts???
Date: Mon, 14 Feb 2011 07:59:35 +0100	[thread overview]
Message-ID: <4D58D2D7.9010803@ts.fujitsu.com> (raw)

Hi,

while trying to reproduce Andre's cpupool problem I ran into another issue:

Dom0 seems to lose hardware interrupts when it has more vcpus than pcpus
available. First I thought this could be due to my cpupool patches, but the
problem can be easily reproduced by pinning all Dom0 vcpus to a few physical
cpus and doing a parallel build then.

I used xen-unstable, kernel 2.6.32.24 from SLES11 SP1 on a 12 core INTEL
nehalem machine. I pinned all 12 Dom0 vcpus to pcpu 1-2 and started a parallel
build. After about 2 minutes the first missing interrupts were reported, a
little bit later the next one, no xen messages are printed:

[230644.814834] ata1: lost interrupt (Status 0x50)
[230682.814399] ata1: lost interrupt (Status 0x50)
[230690.814467] ata1: lost interrupt (Status 0x58)
...
[230856.718437] sd 4:2:0:0: [sda] megasas: RESET -843713 cmd=2a retries=0
[230856.739457] megaraid_sas: HBA reset handler invoked without an internal 
reset condition.
[230856.766435] megasas: [ 0]waiting for 16 commands to complete

Has anyone observed a similar behavior?


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

             reply	other threads:[~2011-02-14  6:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14  6:59 Juergen Gross [this message]
2011-02-14  8:58 ` Dom0 losing interrupts??? André Przywara
2011-02-14  9:26 ` Jan Beulich
2011-02-14  9:38   ` Juergen Gross
2011-02-14  9:58     ` Jan Beulich
2011-02-14 11:21       ` George Dunlap
2011-02-14 11:46         ` Juergen Gross

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=4D58D2D7.9010803@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --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.