Bug 5474
| Summary: | frequent kernel crash | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Brian Gunney <btng> |
| Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0 | CC: | davem |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2000-02-05 23:41:13 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: | |||
|
Description
Brian Gunney
1999-10-02 15:38:19 UTC
One thing you can do is run the oops through the 'ksymoops' program (it's included in the kernel source in /usr/src/linux/scripts/ksymoops). This will show exactly where the kernel dies at. assigned to dledford assigned to dledford Please download and install the 2.2.12-20 kernel from the Red Hat Linux 6.1 distribution and see if the problem continues. Report that back here. Until we know if the problem still happens this bug report will be on hold. ------- Additional Comments From 10/11/99 09:04 ------- Where is the Oops file located? I've updated to kernel 2.2.12-20--The problem still exists. The problem description you've given so far sounds largely like a hardware corruption issue. We have a standard test we run on systems to see if there are hardware problems. That test requires about 100MBytes of free disk space, one of the linux-2.2.x.tar.gz kernel source tar balls, and the following script: #!/bin/sh rm -fr linux linux.save tar xzf linux-2.2.0.tar.gz mv linux linux.save i=0 while [ "$i" -lt "10" ]; do tar xzf linux-2.2.0.tar.gz diff -U 3 -rN linux.save linux rm -rf linux i=`expr $i + 1` done rm -fr linux.save _______End of Script______ If you run that script and it generates any output on your computer screen at all, then you most likely have hardware corruption. I realize this isn't something one would expect to show up just by upgrading the OS, but keep in mind that with each version of our product that we release, the kernel typically just keeps getting faster and faster, and the later kernels can cause problems to show up on systems that were just barely eeking by before. I got output from running the script, so it must be hardware. |