Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 429516

Summary: booting with maxcpus=1 panics when starting cpufreq service [rhel-5.1.z]
Product: Red Hat Enterprise Linux 5 Reporter: RHEL Program Management <pm-rhel>
Component: kernelAssignee: Anton Arapov <anton>
Status: CLOSED ERRATA QA Contact: Martin Jenner <mjenner>
Severity: high Docs Contact:
Priority: urgent    
Version: 5.2CC: anderson, bmaly, jplans, nobody, qcai
Target Milestone: rcKeywords: Regression, ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: RHSA-2008-0275 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-20 09:58:42 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:
Bug Depends On: 428331    
Bug Blocks:    

Description RHEL Program Management 2008-01-21 09:48:46 UTC
This bug has been copied from bug #428331 and has been proposed
to be backported to 5.1 z-stream (EUS).

Comment 2 RHEL Program Management 2008-01-21 09:56:55 UTC
This bugzilla has Keywords: Regression.  

Since no regressions are allowed between releases, 
it is also being proposed as a blocker for this release.  

Please resolve ASAP.

Comment 3 Anton Arapov 2008-01-21 18:23:48 UTC
A patch for this issue has been included in build 2.6.18-53.1.8.el5.

Comment 4 Anton Arapov 2008-01-22 12:22:08 UTC
has been reverted in build 2.6.18-53.1.9.el5.

Comment 5 Anton Arapov 2008-05-07 12:38:47 UTC
A patch for this issue has been included in build 2.6.18-53.1.21.el5.

Comment 9 errata-xmlrpc 2008-05-20 09:58:42 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2008-0275.html