Version-Release number of selected component:
libreport version: 2.0.13
:Thread no. 1 (10 frames)
: #0 for_each_irq at classify.c
: #1 clear_obj_stats at cputree.c
: #2 for_each_object at irqbalance.h
: #3 clear_obj_stats at cputree.c
: #4 for_each_object at irqbalance.h
: #5 clear_obj_stats at cputree.c
: #6 for_each_object at irqbalance.h
: #7 clear_obj_stats at cputree.c
: #8 for_each_object at irqbalance.h
: #9 clear_obj_stats at cputree.c
Created attachment 615644 [details]
Created attachment 615645 [details]
Created attachment 615646 [details]
Created attachment 615647 [details]
Created attachment 615648 [details]
Created attachment 615649 [details]
Created attachment 615650 [details]
Created attachment 615651 [details]
Created attachment 615652 [details]
*** Bug 860410 has been marked as a duplicate of this bug. ***
*** Bug 866861 has been marked as a duplicate of this bug. ***
*** Bug 862926 has been marked as a duplicate of this bug. ***
*** Bug 879917 has been marked as a duplicate of this bug. ***
believe this is fixed by upstream commit 11277c20cf15e1782b9c53538a6f728060ac814c
irqbalance-1.0.3-7.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing irqbalance-1.0.3-7.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
irqbalance-1.0.3-7.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
I just had abrt report this. However, I don't seem to have any clear way to get at the details. If it helps, I'm running Fedora 17 PAE, fully updated.
Abrt should be able to export all the report data you see attached here from the crash you encountered. Please use that to open a new bug.
Abrt simply tells me that this was reported as bug 860410 and refuses to do anything else. However, I also have this from the ABRT Server, which might be what you want: https://retrace.fedoraproject.org/faf/reports/7239/
If you need more info, please point me to instructions on getting what's needed out of abrt. I understand that you want as much data to go on as possible, I just don't know how to get it to you. (I haven't deleted the report from abrt and won't until I'm sure it's not going to be needed.)
This just happened again, and abrt reports that I'm using irqbalance-1.0.3-7.fc17, so it doesn't look like it's been fixed. And, if it matters, it's also still pointing to the same report at retrace.fedoraproject.org. If there's a way to force abrt to open a new bug, or export the data you need, feel free to email me privately with instructions.
hmm, very strange. Looking again at your stack traces it appears that you got caught in an infinite loop of numa nodes. For the life of me I cannot see how that happens. Can you stop the irqbalance service, and run this command manually:
and capture the output to a file? That may give us some insight on how your topology is getting corrupted.
OK, that I can do. You didn't say how long, so I gave it about ten minutes or so. BTW, shouldn't somebody re-open this bug?
Created attachment 746297 [details]
Debug info from irqbalance
Petr, can you please take another look at this. From the debug output, it appears that the system is not numa capable, but irqbalance should handle that just fine.
Hi Joe and Neil,
apologize for delay, I'll take care about it.
could you send me an output of "tree /sys/devices/system/node/" in case this directory exists on your system?
[joe@khorlia Desktop]$ tree /sys/devices/system/node
/sys/devices/system/node [error opening dir]
0 directories, 0 files
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.