Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 81514 - System will not power down after upgrade to 2.4.18-19.8.0.athlon
System will not power down after upgrade to 2.4.18-19.8.0.athlon
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
athlon Linux
medium Severity low
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-01-09 19:37 EST by Robert Knight
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-30 11:40:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robert Knight 2003-01-09 19:37:43 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; T312461; YComp

Description of problem:
After I upgraded to 2.4.18-19.8.0.athlon from the default kernel in 8.0, my 
system will not longer power itself off.

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

How reproducible:

Steps to Reproduce:
1. Boot up using the 2.4.18-19.8.0 Kernel
2. Shutdown the system

Actual Results:  The system goes as far as showing the "Power Down" message but 
never powers down the system.

Expected Results:  The system should power itself down

Additional info:

Gateway Select 600mhz Athlon 384Mb Ram
Comment 1 Bugzilla owner 2004-09-30 11:40:23 EDT
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

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