Bug 455701 - cpufreq driver get the wrong processor number in domain by ACPI _PSD table
cpufreq driver get the wrong processor number in domain by ACPI _PSD table
Status: CLOSED DUPLICATE of bug 428909
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
x86_64 Linux
low Severity high
: rc
: ---
Assigned To: Peter Martuccelli
Martin Jenner
Depends On: 428909
Blocks: 455516
  Show dependency treegraph
Reported: 2008-07-17 05:05 EDT by Song, Youquan
Modified: 2008-08-15 15:09 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-08-14 15:56:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch for commit ID 152c300d007c70c4a1847dad39ecdaba22e7d457 (3.56 KB, application/octet-stream)
2008-07-17 05:22 EDT, Song, Youquan
no flags Details

  None (edit)
Description Song, Youquan 2008-07-17 05:05:49 EDT
Description of problem:

Hardware: Tylersburg HEDT, Nehalem, BIOS SOX5810J.86A.0977.2008.0624.2121.
RHEL5.2 cpufreq driver get the the processor number in domain equal "0" by 
ACPI _PSD table. Actually, ACPI _PSD table show the processor number in domain 
equal "8".  In other hand, FedoraCore 9 can get the correct processor number 
in domain equaling "8". Processor number in domain is important parameter for 
cpufreq driver and governor do SW/HW coordination.  

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot RHEL5.2
2. cat /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus.
3. affected_cpus show "0". 
Actual results:

Expected results:

Additional info:
Comment 1 Song, Youquan 2008-07-17 05:16:27 EDT
I validation on the Tylersburg HEDT, the upstream patche can fix this bug. The 
commit ID 152c300d007c70c4a1847dad39ecdaba22e7d457.  

Comment 2 Song, Youquan 2008-07-17 05:22:28 EDT
Created attachment 312018 [details]
Patch for commit ID 152c300d007c70c4a1847dad39ecdaba22e7d457
Comment 3 Song, Youquan 2008-07-18 02:51:28 EDT
I can not access the 455516 bug.
Comment 4 John Villalovos 2008-07-25 09:29:21 EDT
This bug almost seems like a dupe of #428909 since the same patch solves both
Comment 5 Peter Martuccelli 2008-07-25 09:49:06 EDT
Build a brew kernel with the patch and have people test against bug 428909.  I
will mark this one as a duplicate depending on the test results.
Comment 6 Peter Martuccelli 2008-08-14 15:56:52 EDT

*** This bug has been marked as a duplicate of bug 428909 ***
Comment 7 John Villalovos 2008-08-15 13:28:40 EDT

Are there any BIOS settings which affect this?  I am trying to test on HEDT system with 0926 BIOS version
Comment 8 John Villalovos 2008-08-15 15:09:55 EDT
The BIOS on the system is SOX5810J.86A.1171.2008.0717.0926 so it is the 1171 BIOS.

Disregard BIOS revision I specified in Comment 7

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