Long shot - intel graphics driver bug / fix / update strategy?
by slackerDude from LinuxQuestions.org on (#50E88)
Just over a year ago, I built 12 machines for my wife's classroom to replace REALLY old P4 machines that could no longer run a recent browser. Lacking valid win10 licenses, I used slack14-current as of Dec 14, 2018 and chrome 71.0.3578.98-x86_64-1 - I think that was the current version around that time. They only need to run a couple of websites, and everything seemed to work just fine with chrome.
Recently, on a specific website (lexiacore5.com), a specific page tries to use webgl and aborts, leaving a blank page. The error logs say something about losing webgl context (maybe an opengl message as well). Firefox works just fine, but of course, now some machines are running chrome (school recommendation is to use chrome where possible, so I did that), 2 are using firefox. It's a workaround, but not ideal.
Here's the curious part: I built the machines using Intel DH61 and BE61 boards and G945/G960 and similar dual-core Celerons. BOTH machines that failed were running G2120 chips - and the BIOS of at least one is late enough that the chip should be supported. It boots properly and ran fine for a year until this page did this. I did some stress testing (running 2 different browser tests at the same time) and it's NOT an overheating issue or an out-of-memory issue. And it repeatedly and reliably failed ONLY on those two machines. Machines with G940s, G960s, etc AND some much newer machines we've gotten since with i5 44xx or 45xx CPUs are running fine.
This leads me to think that back then, there was a bug for that specific chip model opengl/webgl driver from Intel?
Here's where the long shot comes in - obviously, with the recent updates to current, as well as the KDE5 migration, etc, I can't imagine things going smoothly doing just an upgrade. PLUS, that would leave 2 machines with KDE5 and 10 with KDE4, which is also a no-go.
Anyone know how to search the kernel update logs to figure out where this issue might have been fixed and a way to update to that specific kernel, if still in the 4.19 series or not too much later? Current kernel is 4.19.9. Is there a way to do all that with the basic slackpkg tools, etc?
Or, alternatively, is there a way to get the exact current snapshot as of the day the bug was fixed and do a full re-install of those two machines only?
Just haven't had much time to get into all this in recent years - 25 years ago, I knew much more about kernel releases, bugs fixes, etc :-)
Recently, on a specific website (lexiacore5.com), a specific page tries to use webgl and aborts, leaving a blank page. The error logs say something about losing webgl context (maybe an opengl message as well). Firefox works just fine, but of course, now some machines are running chrome (school recommendation is to use chrome where possible, so I did that), 2 are using firefox. It's a workaround, but not ideal.
Here's the curious part: I built the machines using Intel DH61 and BE61 boards and G945/G960 and similar dual-core Celerons. BOTH machines that failed were running G2120 chips - and the BIOS of at least one is late enough that the chip should be supported. It boots properly and ran fine for a year until this page did this. I did some stress testing (running 2 different browser tests at the same time) and it's NOT an overheating issue or an out-of-memory issue. And it repeatedly and reliably failed ONLY on those two machines. Machines with G940s, G960s, etc AND some much newer machines we've gotten since with i5 44xx or 45xx CPUs are running fine.
This leads me to think that back then, there was a bug for that specific chip model opengl/webgl driver from Intel?
Here's where the long shot comes in - obviously, with the recent updates to current, as well as the KDE5 migration, etc, I can't imagine things going smoothly doing just an upgrade. PLUS, that would leave 2 machines with KDE5 and 10 with KDE4, which is also a no-go.
Anyone know how to search the kernel update logs to figure out where this issue might have been fixed and a way to update to that specific kernel, if still in the 4.19 series or not too much later? Current kernel is 4.19.9. Is there a way to do all that with the basic slackpkg tools, etc?
Or, alternatively, is there a way to get the exact current snapshot as of the day the bug was fixed and do a full re-install of those two machines only?
Just haven't had much time to get into all this in recent years - 25 years ago, I knew much more about kernel releases, bugs fixes, etc :-)