Bug 112100 - computer freezes - keyboard leds blink at starting non-interactive
computer freezes - keyboard leds blink at starting non-interactive
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-12-14 13:24 EST by Need Real Name
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:51:03 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 Need Real Name 2003-12-14 13:24:18 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)

Description of problem:
with the most recent kernel update kernel-2.4.22-1.2129.nptl,
my computer just freezes just after the point in startup where the
show details/hid details screen is. the keyboard leds begin to blink and 
the only option is to hit the reset button (ctrl-alt-bksp,ctrl-alt-del
don't do anything). the last kernel was fine.

not sure what problem is. booting into single user mode with this
kernel is ok.

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

How reproducible:

Steps to Reproduce:
1. boot with kernel-2.4.22-1.2129.nptl

Actual Results:  computer froze, only option was reset button

Expected Results:  expected gdm login

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