Bug 113351
Summary: | System non-usable after 2 days of stress | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | keith mannth <kmannth> | ||||||
Component: | kernel | Assignee: | Dave Anderson <anderson> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 3.0 | CC: | barryn, jamesclv, lcm, petrides | ||||||
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: | 2007-10-19 19:31:27 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: | |||||||||
Attachments: |
|
Description
keith mannth
2004-01-12 23:59:15 UTC
Created attachment 96914 [details]
var/log/messages from system
Created attachment 96919 [details]
first var/log/messages
had remove some of the data due to size constraints
Well, there's nothing to work with here. Please reproduce the hang state, and then forward the outputs of: Alt-Sysrq-m Alt-Sysrq-p (several in a row) Alt-Sysrq-w Alt-Sysrq-t Before starting your tests, make sure /proc/sys/kernel/sysrq is set to 1, or that "kernel.sysrq" is set to 1 in /etc/sysctl.conf. I am currently testing with 2 systems to see the issue again and to get the above outputs. update to my last request: please do the Alt-Sysrq-w last, as it is possible that it will hang the console (and never return) if one of the cpus is spinning on a lock with interrupts disabled. So, if you get the same hang please do the Alt-Sysrq's in this order: Alt-Sysrq-m Alt-Sysrp-p (several in a row) Alt-Sysrq-t Alt-Sysrq-w Well I have been testing 2 systems for 6 days had havent seen the issue again. If I see it again and am able capture any debug output I will post again. Thanks. This sounds a bit like bug 117210. This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |