http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c1 Mircea Kitsune changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High --- Comment #1 from Mircea Kitsune --- This continues to be a huge issue with the latest Tumbleweed packages! The system now freezes and crashes on a hourly basis. It's likely something triggering a GPU crash, as it only seems to happen the moment certain desktop effects occur or given panels pop up; Even bringing up the taskbar (from auto-hide) or clicking the arrow which expands the system tray can cause it. The only way to recover the system without restarting is to immediately hit "control + alt + backspace" to kill x11 once noticing the freeze, before it has time to become permanent or the glitches I mentioned take place. Can anyone else confirm this please, and let us know whether a solution is being worked on? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c3 --- Comment #3 from Mircea Kitsune --- I discovered an important detail today: The crash is not limited to KDE desktop effects, unlike most crashes of this sort and what I initially suspected! I've had compositing disabled for several hours (alt + shift + F12) yet the exact same crash occurred just now: All windows and buttons froze in place while only the mouse cursor could be moved, the monitor then turned itself on and off a few times, and I found myself back to the login manager. Upon killing X11 and logging back in, I was presented with a window asking to check my compositor settings... indicating that KDE might have detected compositing as a source, although it's been entirely turned off so that couldn't be true. Could a maintainer or developer familiar with this part of the system please be dispatched to the issue? I have reported it two weeks ago, and so far there has been no official response here. While I understand the developers are busy with other concerns, this is a major problem due to which I can't keep my system from being shot down at random daily intervals. Considering that such a crash may occur anytime, including during a package update or while other processes are handling data, it leaves my system at risk of data corruption! Additionally, could I please request that updates for x11 and the AMD video driver are prioritized? http://tumbleweed.boombatower.com indicates that Devel has the following versions pending: xorg-x11-server 1.19.3 (currently 1.19.2), xf86-video-ati 7.9.0 (currently 7.8.0), Mesa 17.0.2 (currently 17.0.1). Yesterday's Factory snapshot appears to have ignored these packages. As Kernel updates don't seem to affect the issue, I'm hoping a new version of one of these components might include a solution. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c5 --- Comment #5 from Mircea Kitsune --- Created attachment 718223 --> http://bugzilla.opensuse.org/attachment.cgi?id=718223&action=edit Xorg.0.log -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c7 --- Comment #7 from Mircea Kitsune --- Created attachment 718225 --> http://bugzilla.opensuse.org/attachment.cgi?id=718225&action=edit journalctl -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c9 --- Comment #9 from Mircea Kitsune --- Created attachment 718227 --> http://bugzilla.opensuse.org/attachment.cgi?id=718227&action=edit lspci -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c11 --- Comment #11 from Mircea Kitsune --- I apologize for the chain of comments! I'm also discussing this issue on IRC (#dri-devel on irc.freenode.org) and someone seemingly familiar with the code took a look at the logs I posted. Apparently this is a GPU lockup after all. They suggested I tell the llvm packagers to revert r280589. Someone else also mentioned a regression in llvm 3.9.1. The log of our conversation can also be found online, in case I happened to miss any significant details: https://people.freedesktop.org/~cbrill/dri-log/?channel=dri-devel&date=2017-03-21 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c14 Mircea Kitsune changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #14 from Mircea Kitsune --- To my stupefaction, the exact same issue has been re-introduced and is happening again. After another openSUSE Tumbleweed snapshot and several package updates, I believe approximately 2 days ago, the freeze occurs once more. I can however confirm that for approximately 8 days before that, the problem went away as I had one week of uninterrupted uptime. Can someone please analyze what changes fit this time pattern? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c16 Ismail Donmez changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |IN_PROGRESS --- Comment #16 from Ismail Donmez --- Hi Mircea, (In reply to Mircea Kitsune from comment #15)

I feel that at this point, I should express my disappointment regarding the lack of attention this report has received over the course of a month. I marked it as high priority (which I believe it is), posted about this on the forum, and wrote about it to the Factory mailing list (where it was completely ignored). To this day, I still have no idea what this is or when and how it might be fixed.

Sorry for my silence but I am already working on upgrading llvm to 4.0 which I hope will fix this issue, if not then we can ask for a revert on the llvm mailing list for the problematic commit. Randomly reverting commits on llvm can have bad consequences. Sadly the Open Build Service seems to be slow these days and it takes a lot of back and forth to see if my commits work or not. You can see the progress in https://build.opensuse.org/package/show/devel:tools:compiler/llvm4 Thanks, ismail -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c18 kevin Zhu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Z_kvn@yahoo.com --- Comment #18 from kevin Zhu --- Hello Since I last month installed Tumbleweed I have experienced the same issue at least 3 times: my monitor screen would randomly freeze when I was using Firefox but mouse cursor could still move. Ctrl+Alt+F1 didn't work. Fingers crossed. Regards, Kevin -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c20 --- Comment #20 from Mircea Kitsune --- Very important note: While investigating a completely unrelated bug, I remembered that KWin was configured to use egl over glx on my machine. I believe glx is the old render architecture, whereas egl is the new renderer which uses OpenGL and is visibly a lot faster. Considering that desktop activity was always the cause of the freezes in some form, I have a strong suspicion that this might have something to do with the GPU freezes as well! It's a very likely candidate because egl involves experimental OpenGL rendering, and since it's not enabled by default that would also explain why few other people are able to reproduce the GPU lockups. I have just now switched back to glx and therefore haven't had the time to confirm this, but I'm willing to bet it just might make the problem go away... I will immediately post an update if and when I'm proven wrong obviously. If anyone else wants to test this theory and help in reproducing the system freeze, consider switching to egl rendering. Obviously this means your machine might start freezing as well, so only do this if there's no risk of data loss or major annoyance. The switch is done by opening ~/.config/kwinrc in a text editor and changing: GLPlatformInterface=egl to GLPlatformInterface=glx Note that if you're using an Aurorae theme, you might experience the bug I mentioned above, which involves KWin no longer rendering window decorations. Here are the reports for that in case anyone is curious: https://bugzilla.opensuse.org/show_bug.cgi?id=1033598 https://bugs.kde.org/show_bug.cgi?id=378663 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c22 --- Comment #22 from Ismail Donmez --- llvm4 is now accepted into Factory and should be in the next update. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c24 --- Comment #24 from Ismail Donmez --- (In reply to kevin Zhu from comment #23)

(In reply to Ismail Donmez from comment #22)

...

llvm4 is now accepted into Factory and should be in the next update.

Thanks Ismail. As an enthusiastic non-developer Linux user, I wonder whether there is any way to apply the patch myself without waiting for a build? Is there any guide, or just roughly the direction, that you may kindly show me? :)

Since more than one package is involved here (llvm, Mesa, ...) I would really want you to expect the next update. It should happen this week, if not I'll create a test repo for you people. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c26 --- Comment #26 from Mircea Kitsune --- llvm 4.0.0 is now in openSUSE Tumbleweed: I have preformed a 'zypper dup', installed it, and restarted. Now it's time to see if this really makes the freeze go away. Please allow me to keep this issue open for another month to make sure it's truly gone: If through some stretch of imagination I see the problem again, I'll immediately post a reply here and let everyone know! I need to take at least several days to have no doubt it has been solved, due to how far its probability seems to have ranged. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c28 --- Comment #28 from Mircea Kitsune --- (In reply to Ismail Donmez from comment #27) Oh... thank you for this info. I also noticed that Mesa 17.0.4 is waiting in Devel... maybe an update on that can also be pooled in the process? Anyway I'll wait until the recompilation happens, and will ignore the freeze until then if I see it again. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c30 --- Comment #30 from Ismail Donmez --- (In reply to Mircea Kitsune from comment #29)

A 'zypper dup' earlier today upgraded my machine to Kernel 4.10.10 and reinstalled Mesa 17.0.3. I understand this means that llvm 4.0.0 should be in effect on both of these components, and if llvm was at fault the issue should now disappear. I've had more freezes during the last few days, and if somehow they continue even after this we'll seriously need to dig further. I will immediately let everyone know if I see another freeze from this point on.

Yes, please. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c32 --- Comment #32 from kevin Zhu --- I had 'downgraded' the system to 42.2 Gnome and it had been ok for first a few days until there was a couple of freeze s. I guess the issue have to do with the Nividia video card's open source video driver. I will try to set up the prioritory driver and see what happens. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c34 Mircea Kitsune changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P1 - Urgent Severity|Major |Critical --- Comment #34 from Mircea Kitsune --- Once again, I'm dealing with at least one system crash per day. The latest one happens even after upgrading to the 4.11.0 Kernel, meaning the error was ported to it as well. Why are the developers so incapable this time? This has been happening for nearly 3 darn months! The problem has been fixed twice, and each time it's returned after over 2 weeks. Can someone please explain what the heck is going on here? At this stage, it feels like someone is actively developing and updating this freeze against the latest system components... I don't even see how it could survive through this many package updates by chance alone, it is ridiculous. And please don't lecture me on how this is free software, and I should only be complaining if I was actually paying the developers: There is a limit beyond which an important piece of software, be it a free Linux distribution or component, can break and stay broken. To literally be unable to keep a system running without the image suddenly freezing and the monitor shutting down every single day, for over a quarter of an year... that goes far beyond that limit. I'm sorry for the outburst, but at this stage I think something needed to be said. I did not expect something like this to get dragged so far, and that I'd be unable to keep my system running for months. I'm going to bump the severity of this issue again, in hopes that someone can please take a look at it so I can run my system normally again! Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c36 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 - Urgent |P2 - High --- Comment #36 from Takashi Iwai --- If it's a GPU lockup, and it's in the fairly recent upstream code, could you rather raise the report to upstream (e.g. bugzilla.freedesktop.org)? There you may get more attention. Also, please don't touch the priority field of bugzilla. It's not the field the reporter may modify. You can adjust the severity, but not the priority. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c38 --- Comment #38 from Ismail Donmez --- (In reply to Mircea Kitsune from comment #37)

(In reply to Ismail Donmez from comment #35)

...

I understand your frustration but basically logs show that you are getting random GPU lockups, searching Google for "radeon r7 370 lockup" shows a lot of results even from Windows. So at this point I believe this might be a hardware problem.

I considered a hardware problem, but that seems unlikely for many reasons: The video card is still very new (about an year now) and a solid Gigabyte model... I've had another Radeon / Gigabyte card before it, which lasted me for nearly a decade. This issue is also triggered only by the KDE desktop, when certain desktop effects play or I select some windows (even with effects turned off)... I play high-end games on my machine, yet even they don't trigger this exact crash! The behavior of the crash also closely indicates a software problem... hardware issues usually cause a total freeze (Kernel panic), whereas this only freezes the desktop (without mouse pointer) then causes the monitor to shut down.

I can't see if in this bug report but did you try to set kwin to use XRender instead of OpenGL? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 Tomáš Chvátal changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #718222|application/x-trash |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c40 --- Comment #40 from Mircea Kitsune --- More info after the latest crash: In ~/.config/kwinrc I tried setting GLCore=false and GLColorCorrection=false, however none of these seem to affect the problem although I found them suspicious. I wonder if other such settings, such as vsync (tearing prevention) could make a difference... there are many combinations to try, and I'm not sure which also affect the system when compositing is off. When the system doesn't completely freeze, the behavior of the problem can be very strange at times; Last night after the desktop froze, I quickly hit Control + Alt + Backspace several times to kill X11... the system went into a console, which started flashing continuously together with the HDD led. I couldn't do anything on my keyboard and mouse... but once I pressed the power button it stopped and the machine shut itself down quickly and cleanly, meaning it still received the power off signal and managed to recover from that. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c42 --- Comment #42 from Mircea Kitsune --- After another two weeks of absence, the issue was apparently reimplemented on top of Kernel 4.11.3 + Mesa 17.1.1 + Plasma 5.10.0, likely sometime during the last few days. The behavior is once again identical, with alt-tab switching or desktop effects causing everything but the mouse pointer to freeze then after 10 seconds the monitor shuts down. Other unrelated GPU crashes (such as those caused by some games) behave by the classic model, where the entire system simple freezes in place at once... that's a very different result from this freeze, and likely confirms this is a different type of crash. At this point I have almost no doubt this is an attack that's being deliberately programmed, and manually reimplemented on top of new drivers once it gets fixed. The cycle seems to be that a kernel or driver update resolves the issue, then the creators of the crash require about two weeks to patch it and reimplement the exact same functionality. This is the 4th time the story repeats. I tried steering away from this possibility until I was sure, as I didn't want it triggering any unnecessary arguments... if this is an attack then investigating it as such might help in finding its source more quickly. There's simply no way something this precise could happen by itself for nearly half an year, always coming back with the exact same effects after a period of absence... all despite radical changes to nearly every driver and system component, which would have no doubt altered the behavior of the initial problem in some form. Therefore I hope everyone can see why I'm now going with this theory and greatly considering the option of malicious intent. I have no idea how the virus (?) could be updated on my computer, as it's likely not through the package update system directly. However I suspect it's using a constant series of vulnerabilities in one or more system components, which should be fixed by the developers if they exist. I would appreciate any ideas on both how the malicious code might be inserted into the computer, as well as finding the vulnerability within radeon / Mesa / X11 / etc that it exploits. Please let me know what your thoughts are! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c44 --- Comment #44 from Mircea Kitsune --- Created attachment 729307 --> http://bugzilla.opensuse.org/attachment.cgi?id=729307&action=edit Photo of the corrupt image on the screen I have discovered some very important details today. Everyone following up on the report, please see this comment! Recently I realized that a useful test would be to jump into a different run level once I notice the crash, in order to see how the system behaves there. A few minutes ago another freeze took place, so I instantly hit Control + Alt + F1 to go to a console. What I noticed was pretty remarkable and sheds light on a few aspects: I could keep typing in the console for nearly 10 seconds, but after that the exact same behavior still took place (monitor turned itself on and off two times then the image froze). This time however I was able to toggle the NumLock led a minute after the crash, while also seeing the HDD led still working; That means this is not (always) a total system freeze such as a Kernel panic... instead it appears to be the image output corrupting and staying that way, freezing only specific components with it (I was still unable to issue a blind reboot command for instance). To put everything into an approximate timeline, this is what happened: 00 seconds in: The crash occurs. 02 seconds in: I notice and instantly hit Control + Alt + F1. 05 seconds in: I'm taken to a console where everything works fine: I see the blinking cursor, can write my login and password, etc. 12 seconds in: Suddenly the monitor turns off and back on several times, then the image remains frozen in place. This time however, the screen did not remain turned off or black. Instead it stayed stuck in a state showing corrupt lines and rectangles of random colors. I took a photo of my screen with my smartphone, which I attached to this issue. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c46 --- Comment #46 from Mircea Kitsune --- Thought I'd also post another detail that might be useful, I'm not sure how much it relates to the freeze but better be safe than sorry; I have the following two environment variables added to my ~/.profile file, which basically tell Mesa to post errors to a log file: export MESA_DEBUG=1 export MESA_LOG_FILE=/home/mircea/.mesa_stderr There's one reoccurring line which keeps getting printed in there. It's added periodically with no side effects, but I imagine it could still have some relation to the trigger of the freeze: Mesa: User error: GL_INVALID_OPERATION in glTexSubImage2D(invalid texture image) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c48 --- Comment #48 from Mircea Kitsune --- Today I discovered that even when not toggling desktop effects at runtime, the freeze can still be mined into the system. I got a crash after 1 day of uptime, no toggling of desktop compositing required. I find it remarkable how the cause of the crash appears to have immediately changed after me making the comment above yesterday; I tested my theory that desktop effects are the root for 2 months, yet the moment I publish my observations the behavior changes in less than a day. This further makes me concerned that someone might be deliberately programming this crash using vulnerabilities in system components, solely for how strange this coincidence is. I'm still waiting for the developers to help investigate this further whatever the case, as I cannot find any explanation at this point. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c50 --- Comment #50 from Mircea Kitsune --- Created attachment 735385 --> http://bugzilla.opensuse.org/attachment.cgi?id=735385&action=edit Output of "dmesg -w" This is perhaps the most important piece of information I managed to gather on the problem thus far. If you have a technical understanding of this data, please take a look at the log and let us know what it says! I was able to run a SSH session on my computer from another machine. In it I left the command "dmesg -w" running. I toggled desktop effects last night to provoke a crash today, which happened as expected and allowed me to conduct the test. This is basically what dmesg is seeing in realtime as the system is crashing. I can't make sense of the information, but it definitely looks descriptive. Although the computer seemed completely frozen locally, the output continued flowing on the other machine printing new information every few seconds. I had to wait in order to catch some of the red lines in the console. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c52 Michal Srb changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(sonichedgehog_hyp | |erblast00@yahoo.com) --- Comment #52 from Michal Srb --- This bug was assigned to the llvm maintainer to build llvm package with the commit r280589 reverted for testing. I have inherited it now. However, based on the additional information it doesn't look like it is a bug in llvm. User-space can do whatever it wants, if it causes lockups, it is bug in kernel. The dmesg you posted is useful. It definitely looks like locking problem. The other warnings are probably just caused by the earlier errors. However, the dmesg doesn't look complete - there may have been some errors before the ones in the log. Can you try to get dmesg again, this time complete? Ideally showing everything from boot until the lockup. To address some of your earlier comments: (In reply to Mircea Kitsune from comment #15)

I feel that at this point, I should express my disappointment regarding the lack of attention this report has received over the course of a month. I marked it as high priority (which I believe it is), posted about this on the forum, and wrote about it to the Factory mailing list (where it was completely ignored). To this day, I still have no idea what this is or when and how it might be fixed.

You are running Tumbleweed - bleeding edge. And this issue is likely hardware specific - if we don't have your hardware, all we can do is guess what may be wrong. (In reply to Mircea Kitsune from comment #46)

Mesa: User error: GL_INVALID_OPERATION in glTexSubImage2D(invalid texture image)

Some application is using OpenGL badly. It shouldn't cause issue like this. (In reply to Mircea Kitsune from comment #48)

I find it remarkable how the cause of the crash appears to have immediately changed after me making the comment above yesterday; I tested my theory that desktop effects are the root for 2 months, yet the moment I publish my observations the behavior changes in less than a day. This further makes me concerned that someone might be deliberately programming this crash using vulnerabilities in system components, solely for how strange this coincidence is.

Nah, locking issues are typically random and rare. That makes them hard to reproduce and debug. Nobody is hacking you. (In reply to Mircea Kitsune from comment #49)

Created attachment 735281 [details] Memtest86 screenshot

Your system memory is ok, that's good, but says nothing about GPU. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c54 --- Comment #54 from Mircea Kitsune --- Sorry about that, wrong link in the previous comment: https://bugs.freedesktop.org/show_bug.cgi?id=100306 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c56 Mircea Kitsune changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sonichedgehog_hyp | |erblast00@yahoo.com) | --- Comment #56 from Mircea Kitsune --- Created attachment 735590 --> http://bugzilla.opensuse.org/attachment.cgi?id=735590&action=edit Output of "dmesg -w" (full) Full output of "dmesg -w", recorded by running "dmesg -w > filename.txt". The previous one was incomplete as it was subject to console line limitations, cutting off the moment when the crash actually occurs. I left the command running in a different runlevel; This time the crash didn't shut down the monitor after switching to it (Control + Alt + F1) so I was able to cleanly shut down dmesg then issue a normal reboot. I waited there for about 5 minutes before doing so, to give dmesg time to record as much information as possible. The crash appears to start at the following lines: [112873.658950] radeon 0000:03:00.0: ring 4 stalled for more than 10024msec [112873.658953] radeon 0000:03:00.0: GPU lockup (current fence id 0x000000000072f6bd last fence id 0x000000000072f6c1 on ring 4) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 Mircea Kitsune changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=101325 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c59 --- Comment #59 from Mircea Kitsune --- Further more, I suspect I now know what the culprit component is. It's very likely that the problem lies within Mesa itself, and was introduced in the switch between 13.0 and 17.0. This was confirmed by the bug report I linked previously, which I strongly believe is related to the issue I'm experiencing here: Another person there was able to verify that their crash happens with Mesa 17 but not 13. Looking at the dates, I realize that I started experiencing this problem precisely when openSUSE Tumbleweed upgraded from Mesa 13.0 to 17.0: Mesa 17 landed in early March 2017, it was a few days later that the issues began, which I then reported the following week (08 March 2017). See my comment in the other bug for more info on this: https://bugs.freedesktop.org/show_bug.cgi?id=101325#c22 I also seem to confirm that the issue only affects RadeonSI cards but not R600: My laptop has a Mobility Radeon HD 5470 card (R600) whereas my desktop has a Radeon R7 370 card (RadeonSI). I've been away for two weeks and have been using my laptop exclusively during this time, which has the exact same OS and configuration as my desktop. I was able to preform every task I do on my desktop from my laptop, including the triggers I described above... I have never experienced this freeze with the laptop. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1028575 http://bugzilla.opensuse.org/show_bug.cgi?id=1028575#c61 Michal Srb changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |DUPLICATE --- Comment #61 from Michal Srb --- As far as I can tell this is duplicate of bug #1084767. Good luck solving the issue with upstream, they know the drivers best. *** This bug has been marked as a duplicate of bug 1084767 *** -- You are receiving this mail because: You are on the CC list for the bug.