Bug 101455
| Summary: | Upgrade to 2.4.20-19.8 kernel causes swap thrashing | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Mitch Pirtle <mitchy> |
| Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
| Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | CC: | riel |
| 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: | 2004-09-30 15:41:23 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: | |||
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: I installed RH8.0 on my laptop (IBM ThinkPad T30), and everything was fine. Then I upgraded the kernel to 2.4.20-19.8, as per up2date. Now when I boot into the 2.4.20-19.8 kernel, 'vmstat 1' reports constant si and so, despite having plenty of ram... Rebooting into the old 2.4.18-4 kernel makes it go away. Version-Release number of selected component (if applicable): kernel-2.4.20-19.8 How reproducible: Guaranteed, tested over two days and too durn many reboots. :^/ Steps to Reproduce: 1. Get a TP T30 2. Slap RH8 on it 3. Run up2date, do the kernel mambo 4. Sing "Anticipation..." Actual results: A laptop that is not manageable due to pitiful performance, and I'm easy to please (living on a dual PIII-450 MHz at home)... Expected results: Upgraded kernel should fix things, not break them. Additional info: I already lost plenty of time thinking it was RPM or apt4rpm related, now it is quite clear that it is a kernel/swap issue.