Bug 55638
| Summary: | [vmware] 2.4.9-7 kernel unstable | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | John Smith <jds10> |
| Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
| Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.2 | CC: | mharris |
| 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: | 2001-11-12 19:28:48 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
John Smith
2001-11-03 16:07:24 UTC
this was already reported many times but RH seems to ingnore it. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=54931 totally different thing, as it doesn't seem that the other bug has VMWare involved. for vmware you NEED the very very latest kernel modules from the vmware website and with those you have a chance of it working. THe 3.0 beta seems to work pretty well with newer kernels.... but it's not something that is supported. Inserting "random" kernel modules that then crash your system... the vendor of those modules is your best hope of getting things fixed. I am using the very latest VMware modules (unless they have changed since yesterday). Please note that updating the locate database also regularly crashes the system -- VMware was never running when this happened, and may well not have even been installed on one or two occasions. I now have a new symptom: on the laptop, on the (less unstable) distributed 2.4.9-7 kernel without ntfs support, I have now lost all sound. This appears to have happened after booting into Windows 2000 and then back into Linux. I cannot use a system that is so unreliable. I only upgraded to 2.4.9-7 to avoid the notional danger of the /usr/bin/newgrp vulnerability, but what I have ended up with is far worse. Is the 2.4.7-10 kernel distributed with RH 7.2 more stable, or do I have to back off further? (I have upgraded my filesystems from ext2 to ext3, so presumably I cannot back off very far.) I've had pretty good luck with a pair of Tyan Tiger 100 System with dual PIII 800 MHz and 640 MB RAM running VMWARE. (One system actually has two 850's and only 512 MB RAM, but same mobo.) The system with the slightly older BIOS (The dual 800 with 640 MB) throws a lot of APIC Error 0x2 and Ox4, but that doesn't seem to matter. The kernel is 2.4.10-7 (RH 7.2 Enigma) and VMWARE is 3.0, compiled from the TAR sources. I never enabled the sound (Similar problem to yours the one time I tried it). Have you tried a clean install and updating your systems' BIOS's to the latest version? Actually, an EXT3 drive WILL work in an system that supports EXT2. EXT3 is just EXT2 with the Journal files, drivers, and control software added, so EXT3 drives will work under EXT2 except that the Journal files won't be used (and may actually show up on the filesystem, so don't erase or alter them if you intend to use the drive in EXT3 again.) VMware like other software containing binary only kernel modules, is not supported by Red Hat. It is possible that you may be able to obtain VMware technical support on the VMware website, or from them directly however. |