Bug 108192
| Summary: | kernel crashes during normal work | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Pawel Orzechowski <orzechowskip> | ||||||||||||
| Component: | kernel | Assignee: | Dave Jones <davej> | ||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> | ||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||
| Priority: | medium | ||||||||||||||
| Version: | 9 | CC: | pelayog, pfrields, riel | ||||||||||||
| 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:40 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: |
|
||||||||||||||
Created attachment 95546 [details]
output from /var/log/messages
Created attachment 95547 [details]
output from command "lsof -i "
Created attachment 95548 [details]
sample "ps -fe" output
If You have any suggestions, what should I do to track down problem, I will be glad to hear it. I am out of ideas. Regards Pawel Same problem here. With previous RH9 SMP kernels we got a panic every two days aprox. With 2.4.20-20.9smp we got a panic per one or two weeks, but today we had two panics in four hours, unfortunately I've logged only one of them. I think this bug is related to 107575. I'm attaching the contents of /var/log/messges, the output of lsmod, ps -ef and lsof -i. The relevant hardware: Intel SHG2 motheboard (HyperThreading enabled) 2 XEON 2.4Ghz CPUs, 1GB RAM, 4 SEAGATE ST336607LC disks. And four nics E100, E100, tg3 and 3c59x. Created attachment 95556 [details]
Contens of /var/log/messages, output from lsmod, ps -ef and lsof -i
My machine is equiped in "standard" hardware: CPU: Intel Pentium III 800 MHz RAM: 512 MB1760 5% /tmp /dev/hda6 2016016 1556056 357 HDD: 20 GB MB: MS-6309 (MSI) with VIA Apollo chipset Last night (well morning) my machine has crashed again. Regards Pawel Created attachment 95573 [details]
/var/log/messages from last crash
Looks like either two seperate bugs, or possible hardware problem. Have you tried memtest86 on this machine ? Yes I've been running MEMTEST86 for six hours with no errors. However, to be sure we'll replace the RAM and reboot with HyperThreading disable on the BIOS and UP kernel. So if the panic is caused by a faulty hardware it should be reproduced in one or two weeks. No, I haven't tried memtest86, I will do it and let you know. Hello, I have run memtest86 for a 4 days, and it did not detect any errors. Any suggestions? Try running the debug kernel for a while, see if that hits any of the bug checks. OK, how can I ran kernel in debug mode? Since I've switched to Fedora Core this error is not occuring any more. 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/ |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (compatible; Konqueror/3.1) Description of problem: From time to time I got kernel panic on my machine. It is difficult to qualify what is the reason. I do not load any modules, do not start any particular program. The machine is used as a desktop workstation, I'm using KDE 3.1.4. Some times the machine is being left overnight, when I'm back next morning it appeares it had crashed. Version-Release number of selected component (if applicable): kernel-2.4.20-20.9 How reproducible: Couldn't Reproduce Steps to Reproduce: 1. 2. 3. Additional info: