Bug 429516 - booting with maxcpus=1 panics when starting cpufreq service [rhel-5.1.z]
Summary: booting with maxcpus=1 panics when starting cpufreq service [rhel-5.1.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.2
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: rc
: ---
Assignee: Anton Arapov
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On: 428331
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-21 09:48 UTC by RHEL Program Management
Modified: 2014-06-18 08:01 UTC (History)
5 users (show)

Fixed In Version: RHSA-2008-0275
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-20 09:58:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2008:0275 0 normal SHIPPED_LIVE Important: kernel security and bug fix update 2008-05-20 09:58:29 UTC

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
Note You need to log in before you can comment on or make changes to this bug.