Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 80683 - Complete system lockup/hang
Summary: Complete system lockup/hang
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.3
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2002-12-29 18:51 UTC by Need Real Name
Modified: 2007-04-18 16:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-09-30 15:40:21 UTC

Attachments (Terms of Use)

Description Need Real Name 2002-12-29 18:51:35 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.8-26mdk i686)

Description of problem:
The system locked-up and was completely unresponsive to
the console.

Attemps to telnet in received only

Connected to <hostname>.
Escape character is '^]'.

Kernel is 2.4.18-10smp

I had to actually press the reset button to reboot it.

Is there a startup script or other procedure I can follow
to have the newly rebooted system save the previous kernel's

Alternatively, is there are keystroke sequence to generate a 
panic/crash dump so the "hung" kernel's state can be analyzed?

Any documentation on diagnosing a hung system like this would
be helpful.

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

How reproducible:
Didn't try

Additional info:

Comment 1 Bugzilla owner 2004-09-30 15:40:21 UTC
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 ( maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at:

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