Bug 217373
Summary: | irqbalance segmentation fault | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bryce <root> | ||||
Component: | irqbalance | Assignee: | Neil Horman <nhorman> | ||||
Status: | CLOSED WONTFIX | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 6 | CC: | horsley1953, triage | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | bzcl34nup | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2008-05-06 16:57:55 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Bryce
2006-11-27 16:13:33 UTC
I think this is a xen enabled kernel right? this is probably a segfault that I recently fixed under RHEL5. Must have forgotten to do this in FC6. Please try the attached patch in irqbalance and confirm that it fixes the problem. Thanks! Created attachment 142197 [details]
patch to increase max interrupts on irqbalance for xen kernels
Sooo close but no cigar 8) Actually I talked to ARjan about it (since he originally wrote the code) the issu is the interrupts number In this case the kernel has assigned the utterly WILD number of 8411 as an interrupt number to the ethernet controller. The way irqbalance works, it won't find a slot for that as even with your patch it only has slots for IRQ's from 0 up to 1023. Now On the good side, Arjan has actually been busy rewriting this code though he's awaiting Intel's lawyers to give him signoff to release it. So in conclusion,.. IRQ number 8411 is WAY too big for irqbalance least in the manner it handles it currently (even with your patch) Replacement irqbalance code is due out in a day or so's time Phil =--= Well, he's right, 8411 is a wild number. Unfortunately, I'm waiting for arjan to send me his new code too, and I'm not sure that it will solve this problem. To be honest, Barring arjan doing a linked list in the new irqbalance that isn't directly indexed by irq number, this is likely going to be a WONTFIX. Is there anyway you can get that ethernet controller assigned a lower irq value? We just installed FC6 x86_64 on a whopping huge server at work (4 dual core opterons), and I see what is probably the same irqbalance segfault when the system boots (though it seems to work without it - don't know what the long term implications of no irqbalance might be). Having antagonized Arjan for ages thers a newer update that I've tried and works http://www.irqbalance.org/download.php Phil =--= yeah, I pushed -0.55-2 for fc6 last night. This bug will close once the release team gets it into the fc6 updates repository pushed Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |