Bug 88216
Summary: | Scheduler behaves strangely when running 2 or more GL apps | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Greg Corson <greg_corson> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | gmotor, k.georgiou |
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: | 2006-02-21 18:52:32 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
Greg Corson
2003-04-07 18:39:59 UTC
sounds like a nvidia interaction with our changed scheduler indeed. *** This bug has been marked as a duplicate of 73733 *** Ok, I've retested on several machines with SOFTWARE ONLY GL. This problem does not appear HOWEVER running even one copy of glxgears makes the system almost totaly un-responsive. Moving windows, pulling up menus...etc all take 20-30 seconds if you can get them to work at all. The scheduler appears to be giving all the CPU time to X and leaving nothing for any other task. I don't know if you would call this a bug but I don't recall it happening with RedHat 7.x releases. Possiblly this is an artifact of having X run at nice -10? My setup: Athlon 2000XP, Gigabyte K7 Triton Motherboard, 512Mb RAM, Matrox G550, RH9 + updates. I'm seeing exactly the problem described above. Two instances of glxgears and the scheduler seems to misbehave. Start four running and the problems are even more pronounced. This is with a *MATROX* card... not an nvidia. Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |