From: Nathan March <nathan@gt.net>
To: "Xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: 4.1.1 dom0 kernel panic "No available IRQ to bind to: increae nr_irqs!"
Date: Mon, 22 Aug 2011 13:22:06 -0700 [thread overview]
Message-ID: <4E52BA6E.5000409@gt.net> (raw)
Hi,
I've run into an issue where after spawning more than ~22 VMs, the dom0
will panic with:
Kernel panic - not syncing: No available IRQ to bind to: increase nr_irqs!
xen7 ~ # dmesg | grep IRQ
[ 40.430664] NR_IRQS:4352 nr_irqs:512
This is on xen 4.1.1 with the 2.6.32.43 kernel from jeremy xen.git.
I do have sparse IRQ's on:
CONFIG_SPARSE_IRQ=y
I've found numerous comments about this online, but they primarily seem
to apply to earlier versions of xen. More recent comments seem to
indicate it shouldn't be a problem since the IRQ's are dynamically
increased? The kernel doesn't seem to have NR_IRQS specified anywhere
that I can see...
Can anyone point me in the right direction to resolve this?
Thanks,
Nathan
next reply other threads:[~2011-08-22 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 20:22 Nathan March [this message]
2011-08-22 20:59 ` 4.1.1 dom0 kernel panic "No available IRQ to bind to: increae nr_irqs!" 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=4E52BA6E.5000409@gt.net \
--to=nathan@gt.net \
--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).