Bug 83425 - Interrupts are not distributed evenly among the Xeon processors (Gallatin/Prestonia).
Interrupts are not distributed evenly among the Xeon processors (Gallatin/Pre...
Status: CLOSED ERRATA
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-03 23:05 EST by Larry Troan
Modified: 2016-04-18 05:39 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-12-16 19:25:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
cpuinfo.out (1.75 KB, text/plain)
2003-02-03 23:06 EST, Larry Troan
no flags Details
interrupts.out (856 bytes, text/plain)
2003-02-03 23:06 EST, Larry Troan
no flags Details

  None (edit)
Description Larry Troan 2003-02-03 23:05:11 EST
PROBLEM DESCRIPTION: Interrupts are not distributed evenly among the Xeon
processors.  However, with the Pentium 3 processors, the information is properly
displayed.  /proc/interrupts shows that all interrupts are being processed
through CPU0 ONLY.

Server: Any server with Pentium 4/ Xeon processors

Attached are the outputs to /proc/interrupts and /proc/cpuinfo.  

----------
Action by: Bryan.Leopard
Issue Registered
----------
Action by: Bryan.Leopard


Status set to: Waiting on Tech
File uploaded: cpuinfo.out

----------
Action by: Bryan.Leopard


File uploaded: interrupts.out


THIS IS ISSUE TRACKER 14892, opened as sev 2
Comment 1 Larry Troan 2003-02-03 23:06:01 EST
Created attachment 89826 [details]
cpuinfo.out
Comment 2 Larry Troan 2003-02-03 23:06:44 EST
Created attachment 89827 [details]
interrupts.out
Comment 3 Arjan van de Ven 2003-02-04 10:22:50 EST
fixed with a more recent kernel-utils package.

Note You need to log in before you can comment on or make changes to this bug.