From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com, anibal@debian.org,
notting@redhat.com, pbrobinson@gmail.com, crrodriguez@suse.de,
bwalle@suse.de
Subject: irqbalance seg faults with 2.6.38 or later kernels [patch + solution included] if running under Xen hypervisor
Date: Tue, 10 May 2011 20:33:47 -0400 [thread overview]
Message-ID: <20110511003347.GA29851@dumpdata.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]
The reason behind it is that irqbalance parses the /proc/interrupts
and whenever it hits something it can't understand:
RES: 191614137 73904910 Rescheduling interrupts
It will count the number of interrupts towards the IRQ 0. That IRQ does exist
when the kernel boots under baremetal:
0: 46 0 IO-APIC-edge timer
but under Xen, the timer interrupts are initialized much later:
272: 41197188 0 xen-percpu-virq timer0
and the first IRQ that is used is not zero, but rather one:
1: 73037 0 0 0 0 0 xen-pirq-ioapic-edge i8042
so when irqbalance tries to account for the IRQ 'RES' to the IRQ 0
it fails and segfaults. The attached patch fixes it for whoever else is
hitting this problem. I am not sure who the upstream maintainer is for this so
I am sending this patch to the different distros as well.
--- irqbalance-0.56.orig/procinterrupts.c 2010-06-10 10:45:55.000000000 -0400
+++ irqbalance-0.56/procinterrupts.c 2011-05-10 20:22:06.897465003 -0400
@@ -50,7 +50,7 @@ void parse_proc_interrupts(void)
int cpunr;
int number;
uint64_t count;
- char *c, *c2;
+ char *c, *c2, *err;
if (getline(&line, &size, file)==0)
break;
@@ -64,7 +64,11 @@ void parse_proc_interrupts(void)
continue;
*c = 0;
c++;
- number = strtoul(line, NULL, 10);
+ number = strtoul(line, &err, 10);
+ /* Man page says that if that happens and number == 0, then it
+ * failed to parse. */
+ if (err == line && number == 0)
+ continue;
count = 0;
cpunr = 0;
[-- Attachment #2: irqbalance.patch --]
[-- Type: text/x-diff, Size: 673 bytes --]
--- irqbalance-0.56.orig/procinterrupts.c 2010-06-10 10:45:55.000000000 -0400
+++ irqbalance-0.56/procinterrupts.c 2011-05-10 20:22:06.897465003 -0400
@@ -50,7 +50,7 @@ void parse_proc_interrupts(void)
int cpunr;
int number;
uint64_t count;
- char *c, *c2;
+ char *c, *c2, *err;
if (getline(&line, &size, file)==0)
break;
@@ -64,7 +64,11 @@ void parse_proc_interrupts(void)
continue;
*c = 0;
c++;
- number = strtoul(line, NULL, 10);
+ number = strtoul(line, &err, 10);
+ /* Man page says that if that happens and number == 0, then it
+ * failed to parse. */
+ if (err == line && number == 0)
+ continue;
count = 0;
cpunr = 0;
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2011-05-11 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 0:33 Konrad Rzeszutek Wilk [this message]
2011-05-11 8:16 ` irqbalance seg faults with 2.6.38 or later kernels [patch + solution included] if running under Xen hypervisor Jan Beulich
2011-05-11 13:10 ` Konrad Rzeszutek Wilk
2011-05-11 13:41 ` Jan Beulich
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=20110511003347.GA29851@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=anibal@debian.org \
--cc=bwalle@suse.de \
--cc=crrodriguez@suse.de \
--cc=notting@redhat.com \
--cc=pbrobinson@gmail.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.