Bug 126180
Summary: | Updated kernel (2.6.6-1.435.x86_64) unstable | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Lamont Peterson <peregrine> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | pfrields, tim |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-04-16 05:30:57 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
Lamont Peterson
2004-06-17 07:01:14 UTC
This text from my original post: Booting into the 2.6.5-1.358smp kernel (shipped w/FC2) ...should continue on to include: fixed the problem and the ststem has been rock solid since. The newer 2.6.6-1.435.2.3smp kernel also exhibits the same instability problems on AMD64, though it does take just a little bit longer to manifest than for the 2.6.6-1.435smp kernel. There are still no log messages that seem to indicate anything related, but I need to spend more time to finish digging through them to be sure. Just to add to this we have seen this exact same effect on 3 Dual opteron servers running 2.6.6-1.435.2.3smp works without problems, kernel-smp-2.6.7-1.494.2.2 hard locks up. the ammount of time varies from about 15 minutes to 12 hours. The load on the machine seems to make little difference and there is no debugging information on the console, local syslog logs or remote syslog logs. We have Tyan 2882 motherboards with 2Gb of ECC RAM (no errors reported) and Opteron 242s. There is a 3ware 7000-series ATA-RAID controller card in the machines as well. Should I open this as a seperate bug or leave it here? For me, the 2.6.7 & 2.6.8 kernels run flawlessly. The problem has disappeared, entirely. I only experienced problems with the whole 2.6.6 line of kernel packages. I have gone back and tried to find something that was common that I could nail down as a cause (like, "when I do X if Y, Z, W & V are like thus, then it crashes), without any success. It's helpful to know that the problem has gone (in same ways at least), I feel more confident to update to the 521 kernel now. I'm still having hard lockups with 2.6.8-1.521. The system is the following: 1x Athlon64 3000+ CPU (754 pin) 1x VIA k8vm800m MicroATX motherboard 1x Nvidia GF4-MX 440 AGP 8x GPU (using the nv open-source driver) 2x PC3200 512MB RAM (1GB total) 1x Seagate 120GB SATA HD 1x Seagage 40GB PATA HD 1x SONY DRU-700a DVD writer FC2 installed from CD-ROM and updated via yum. The system lock up hard randomly after 5-120 minutes, irrespective of the load and component temperature. No log is left behind, total mystery, very frustrating. The system is solid so far (uptime of a few hours) under WinXP SP2 and Linux FC2 for Athlon32, same level of patching. mass update for old bugs: Is this still a problem with the 2.6.9 based update kernel ? The 2.6.8 & 2.6.9 kernels are all completly stable. No problems that I can see. My system still has all the same hardware as I listed at the top of this bug. Fedora Core 2 has now reached end of life, and no further updates will be provided by Red Hat. The Fedora legacy project will be producing further kernel updates for security problems only. If this bug has not been fixed in the latest Fedora Core 2 update kernel, please try to reproduce it under Fedora Core 3, and reopen if necessary, changing the product version accordingly. Thank you. |