How to prevent system from becoming unresponsive when an app is using 2/3 cpu?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I did some poking around and it looks like this particular error has been around for a few years, and ATI hasn't been able to fix it (or maybe they don't want to...you never know with ATI...). And I'm not convinced it has anything to do with the problem I'm having.
I noticed that 3.2.11 is up on kernel.org, so I grabbed that. Patch with BFS patch. Compile. Boot. Black screen, hard lock. Reconfigure so that BFS is not enabled, compile, boot, boots just fine.
For some reason, enabling BFS gives me black screen with hard lock on boot. Not sure why. It boots and runs fine with the code there if BFS is disabled.
my own experience with fglrx is less than stellar, using nvidia now.
regarding BFS, it locks up before the fglrx module is loaded, right? maybe you can send your kernel config and lspci to Con Kolivas, to give him a chance to fix it: kernel at kolivas dot org
I did some poking around and it looks like this particular error has been around for a few years, and ATI hasn't been able to fix it (or maybe they don't want to...you never know with ATI...). And I'm not convinced it has anything to do with the problem I'm having.
OK then I believe you are back to having Wine D3D emulation be the culprit. You are not hard locking when you are playing your SimCity, so your scheduler is working fine. BFS is a different problem.
However, I think that if fglrx is bugging out like that and everyone is seeing it, even if it is not fatal, I would have to question the quality of the driver.
Distribution: Slackware 14.2 soon to be Slackware 15
Posts: 699
Original Poster
Rep:
Quote:
Originally Posted by the3dfxdude
So, this is pointing to your video driver and not the scheduler. I can't say for sure, but this seem to be an smp bug in fglrx.
Is there anything that can be done about this, or am I at the mercy of ATI and their drivers?
I've upgraded to their current driver, and am currently running the 3.3 kernel. With this combination, anything that does anything with graphics, be it a game running via wine or even something as simple as cityville in the browser, will cause the gui to hard lock. No display update, and the mouse and keyboard do not respond. I can't even switch to a terminal when this happens, and the capslock/numlock light will not toggle.
I can ssh into the box and terminate the app, which will be using max cpu, and everything else will resume once I do this.
The page generally recommends to set one core. I do not know if you tried that.
Also, I find this comment especially interesting:
Quote:
OpenGL rendering
by Marcin Falkiewicz on Saturday January 15th 2011, 16:16
SimCity 4 supports OpenGL mode under -dpengl, which seems to work better than software on some configurations (I'm not sure does editing reg do the same)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.