Bug 92323
| Summary: | Kernel 2.4.20 crashing Redhat 7.x | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | ru |
| Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
| Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | ru |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-09-30 15:41:03 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
what kind of video hardware do you have? Is there anything in /var/log/messages about the oops ? There are couple different kinds of video hardware involved, as shown below. Nvidia GeForce2 MXR and Matrox Graphics G400 AGP. The systems went down abruptely and left no error messages in /var/log/messages file. 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 persists. 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/ |
Description of problem: The new kernel 2.4.20-13.7 and 2.4.20-18.7 both cause Redhat 7.3 and 7.1 systems to hang. The sympton appears to be crashing X server. After that happens, no remote nor console logins can take place. Version-Release number of selected component (if applicable): kernel-smp-2.4.20-13.7.i686 and kernel-smp-2.4.20-18.7.i686 How reproducible: Just install the kernel. The system will hang in random. But killing "gdm" process will also cause kernel to hang. One of my colleagues claimed that staying in runlevel 3 will solve the problem. But I need to run in runlevel 5. Steps to Reproduce: 1.First of all, upgrade the kernel to either 2.4.20-13.7 or 2.4.20-18.7 2.Change lilo.conf (or grub.conf) and reboot the system 3.Login remotely as root and kill gdm process. The system will hang at this point but still pingable on the network. Power cycle is needed to bring back the system. Actual results: Expected results: Additional info: