Bug 220803 - Hard / Fatal error
Summary: Hard / Fatal error
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
(Show other bugs)
Version: 5
Hardware: i386 Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
Whiteboard: new bzcl34nup
: 220804 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2006-12-27 07:38 UTC by Ramesh C Suri
Modified: 2008-05-06 17:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 17:14:48 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Ramesh C Suri 2006-12-27 07:38:40 UTC
Description of problem:

 am using Fedora Core 5. I updated the system using system update application 
It automatically updated to kernel 2.6.18-1.2257.fc5smp.
Now I am getting the following error while cold booting after power on

FATAL: error inserting acpi_cpufreq
No such device.

I have to try 6 to 8 times to successfully boot the system. Once booted no 
No problem with reboot command. Of-course the FATAL error message appears 
every time
while booting cold or reboot. I understand this is recent built Build date: 
Sat Dec 16 00:53:59 2006 

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

How reproducible:
hard error always

Steps to Reproduce:
1. cold boot
2.warm boot using reboot
Actual results:
Does not boot for 6 to 8 times after cold boot
boots first time on warm boot using reboot
Expected results:
error message appears 

Additional info:none

Comment 1 John Thacker 2007-01-12 15:39:13 UTC
Updating version to FC5 per comment

Comment 2 Ramesh C Suri 2007-01-23 07:11:01 UTC
 Making the following entry in the file /etc/cpuspeed.conf  
solved my problem. Thanks Jarod Wilson

Comment 3 Eric Sandeen 2007-05-31 16:30:42 UTC
*** Bug 220804 has been marked as a duplicate of this bug. ***

Comment 4 Bug Zapper 2008-04-04 05:22:19 UTC
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.

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:

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

Comment 5 Bug Zapper 2008-05-06 17:14:46 UTC
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.

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