Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 113955 - upgrading non-smp kernel on Dell PE 1650 locks up system
upgrading non-smp kernel on Dell PE 1650 locks up system
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i686 Linux
high Severity high
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2004-01-20 11:53 EST by Stephen Lawrence Jr.
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-29 15:58:59 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 Stephen Lawrence Jr. 2004-01-20 11:53:15 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.4)

Description of problem:
Upgrading the kernel using 'rpm -ivh' for the latest kernel causes the
entire system to freeze, requiring a powerdown to restore systems
operation. Upgrading the SMP version of the kernel does not seem to
cause this issue.

Dell poweredge 1650

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

How reproducible:

Steps to Reproduce:
1. download the latest kernel rpm for 2.4.22-1.2149
2. rpm 'ivh kernel-2.4.22-1.2149.nptl.rpm'

Actual Results:  System freezes after hash marks are complete

Additional info:
Comment 1 David Lawrence 2004-09-29 15:58:59 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.