GPU (driver?) issue on AMD integrated graphics and GNOME: freezes and severe glitches
Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
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.
Ah, useful to note I guess, I have one 8gb RAM stick and 1 32GB stick. Speed matches at 3200 Mt/s but I don't know about the timings, I didn't check. Shouldn't cause corruption, only decreased performance anyways right?
You might go faster without the 8G. 32G is plenty. Ram is 128 bits wide, so the computer can use a single 128 bit load instruction and get both 64 bit chunks in an optimised way. I think the best way to have 32G is 2x16G
The ram access cycle is something like 6-1-1-1, or 5-2-2-2. I really don't know, I've stopped reading up on stuff. The numbers are wait states. So you access a new address, and have to endure 6 wait cycles. But then the succeeding ones (+1) come much faster. Caches follow their own rules.
It is true that things go very fast these days but poor design or specification can introduce extra wait states and reduce throughput significantly. It's getting crazy difficult to debug these types of faults.
I would recommend varying every setting you can, to see if you find anything that alters when it occurs.
Should also record (make a log file), of what you were doing when it occurred.
Any information given to the upstream people (mesa, etc.) on the situation that triggers a fault will help get it fixed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.