https://bugs.freedesktop.org/show_bug.cgi?id=105425
MirceaKitsune changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #77 from ptram...@gmail.com ---
I had the same problem with Xubuntu 17.10 and maybe 18.04 (can't remember). I
GPU would hang when watching Videos with mpv or even in Firefox. When I tested
gnome-shell this would also sporadically
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #76 from MirceaKitsune ---
(In reply to iive from comment #75)
That's what I feared too: I know Mesa depends on a lot of other libraries
(including LLVM) and you can't mix old and new versions between them. This is
my primary
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #75 from i...@yahoo.com ---
(In reply to MirceaKitsune from comment #73)
> (In reply to iive from comment #72)
>
> I've thought about testing an older version of Mesa too. Especially since,
> from what I can vaguely remember,
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #74 from MirceaKitsune ---
pcie_aspm=off makes no difference. In addition, I tried booting back to the
radeon module (instead of amdgpu) and disabling the SI scheduler: This seems to
have slightly mitigated the problem in some cases
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #73 from MirceaKitsune ---
(In reply to iive from comment #72)
I've thought about testing an older version of Mesa too. Especially since, from
what I can vaguely remember, certain system instabilities were introduced
roughly two
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #72 from i...@yahoo.com ---
(In reply to MirceaKitsune from comment #71)
> The Mesa 18.1.0 update, which was supposed to fix several GPU crashes, seems
> to have managed to expand this freeze instead: I now get it even when
> playing
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #71 from MirceaKitsune ---
The Mesa 18.1.0 update, which was supposed to fix several GPU crashes, seems to
have managed to expand this freeze instead: I now get it even when playing
simple 3D games with low-poly models and low-res
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #70 from MirceaKitsune ---
(In reply to iive from comment #69)
Just tried mesa_glthread=false RADEON_THREAD=false MESA_DEBUG=flush and got the
same results. The others seem a lot more complex:
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #69 from i...@yahoo.com ---
I'm really out of ideas...
Could you try using only the radeon kernel driver, just blacklist amdgpu one.
See if the blender trace hangs and netconsole still doesn't give any warnings.
See if you can
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #68 from MirceaKitsune ---
Created attachment 139283
--> https://bugs.freedesktop.org/attachment.cgi?id=139283=edit
Output of: watch --interval 0.1 sensors
(In reply to H4nN1baL from comment
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #67 from i...@yahoo.com ---
(In reply to MirceaKitsune from comment #63)
> (In reply to iive from comment #62)
>
> I booted my machine with the kernel parameter panic=30 as instructed. I then
> waited for over two minutes to see if
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #66 from H4nN1baL ---
Okay, thanks for your reply. Then our problems are unrelated.
Even so let me share you some intel. Disable any BIOS configuration related to
"GART" and "PCIE Spread Spectrum"(PCIe
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #65 from MirceaKitsune ---
(In reply to H4nN1baL from comment #64)
Just tested with "export MESA_EXTENSION_OVERRIDE=-GL_ARB_buffer_storage". It
did not affect the freeze triggered by playing
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #64 from H4nN1baL ---
I've been having a very different problem with AMD cards. But I have reason to
think that the problem could vary from one processor/chipset to another.
My problems disappear using
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #63 from MirceaKitsune ---
(In reply to iive from comment #62)
I booted my machine with the kernel parameter panic=30 as instructed. I then
waited for over two minutes to see if there's any
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #62 from i...@yahoo.com ---
You don't even get kernel panic, the machine just freezes.
Just to confirm that, add the following to the kernel line options in grub
"panic=30" . Then freeze the computer again.
If the kernel panics,
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #61 from MirceaKitsune ---
(In reply to iive from comment #60)
No, it never does. SysRq + R - E - S - U - B (pressed in slow order after one
another) does not reboot, nor make the hard drive
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #60 from i...@yahoo.com ---
(In reply to MirceaKitsune from comment #58)
> (In reply to iive from comment #57)
[...]
> And during the netconsole test, I did enable and use the SysRq keys
> (RESUB)... nothing got printed to the other
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #59 from MirceaKitsune ---
I'm not sure if this helps, but here is the darkplaces engine file responsible
for drawing shadows. Remember that when disabling shadows, the frequency of the
freeze
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #58 from MirceaKitsune ---
(In reply to iive from comment #57)
I believe I've already tried with nodma under Xonotic, as I previously
attempted playing with the following options and still got
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #57 from i...@yahoo.com ---
(In reply to MirceaKitsune from comment #56)
> I've preformed the netconsole test today. After over an hour of learning how
> it works, I set it up and could confirm that system messages are properly
>
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #56 from MirceaKitsune ---
I've preformed the netconsole test today. After over an hour of learning how it
works, I set it up and could confirm that system messages are properly received
by
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #55 from i...@yahoo.com ---
(In reply to MirceaKitsune from comment #54)
> But there's a bizarre twist this time: When playing back the trace generated
> by Blender, my system will freeze at various points during the replay!
>
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #54 from MirceaKitsune ---
I have some very interesting results from today: As instructed, I used the
latest version of apitrace. I cloned it straight from its Github repository and
compiled it
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #53 from MirceaKitsune ---
(In reply to iive from comment #52)
Ah... I do indeed have apitrace 7.1-3.89. I don't know if a newer version
exists on https://software.opensuse.org which is
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #52 from i...@yahoo.com ---
(In reply to MirceaKitsune from comment #51)
> Created attachment 139103 [details]
> Output of: systemctl | grep running
>
> (In reply to iive from comment #50)
>
> I've preformed many more tests during
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #51 from MirceaKitsune ---
Created attachment 139103
--> https://bugs.freedesktop.org/attachment.cgi?id=139103=edit
Output of: systemctl | grep running
(In reply to iive from comment #50)
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #50 from i...@yahoo.com ---
If this `messages` file is from the failed apitrace crash recording, then maybe
you should try again.
In the previous file I could see that SysRq has been used. Since the first
command you use also kills
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #49 from MirceaKitsune ---
Sorry about that: I posted my last message before reading your last one, and
didn't notice your mention about /var/log/messages being obsolete. Just
mentioning so you
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #48 from MirceaKitsune ---
Created attachment 139071
--> https://bugs.freedesktop.org/attachment.cgi?id=139071=edit
/var/log/messages
I managed to trigger the GPU freeze while running Xonotic
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #47 from i...@yahoo.com ---
(In reply to MirceaKitsune from comment #46)
> I found out what's causing the apitrace crash: It no longer happens when I
> use fresh settings, therefore something in my config was breaking it. Upon
>
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #46 from MirceaKitsune ---
I found out what's causing the apitrace crash: It no longer happens when I use
fresh settings, therefore something in my config was breaking it. Upon further
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #45 from MirceaKitsune ---
(In reply to iive from comment #44)
I'm doing my best to debug this as well as possible, but there are a lot of
points and it's hard to pay attention to everything. I
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #44 from i...@yahoo.com ---
You haven't looked for the kernel panic message in the logs.
I'm still waiting for it.
As for the trace. I did download and traced Xonotic before writing the
instructions. I had no issues using the EXACT
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #43 from MirceaKitsune ---
Created attachment 139054
--> https://bugs.freedesktop.org/attachment.cgi?id=139054=edit
Output of: apitrace replay xonotic-sdl.trace
And here's the console output
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #42 from MirceaKitsune ---
Created attachment 139053
--> https://bugs.freedesktop.org/attachment.cgi?id=139053=edit
Output of: apitrace trace xonotic-sdl
Here is the console output generated
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #41 from MirceaKitsune ---
Created attachment 139052
--> https://bugs.freedesktop.org/attachment.cgi?id=139052=edit
apitrace trace xonotic-sdl
I have attempted the apitrace test as
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #40 from i...@yahoo.com ---
It seems like the sysrq actually worked, I see it in the logs.
The crash has happened around Apr20 15:54. Unfortunately the kernel error/panic
message is missing in both logs. My distro doesn't have
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #39 from MirceaKitsune ---
Created attachment 138951
--> https://bugs.freedesktop.org/attachment.cgi?id=138951=edit
journalctl --since yesterday
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #37 from MirceaKitsune ---
I have just finished preforming the first new test.
First of all I must say I'm utterly amazed at the variability of this issue:
Last week when I played Xonotic with
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #38 from MirceaKitsune ---
Created attachment 138950
--> https://bugs.freedesktop.org/attachment.cgi?id=138950=edit
cat /var/log/messages
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #36 from MirceaKitsune ---
(In reply to iive from comment #35)
I will be busy tomorrow, and also wanted to look into how to do the other more
complicated tests. I'll be trying this out sometime
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #35 from i...@yahoo.com ---
Any results?
Enable SysRq, start Xonotic, set r_shadow 2, play until it crashes, use SysRq
to sync, umonut, reboot.
After reboot, check if the crash has been captured by syslog/journald.
If there is
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #34 from MirceaKitsune ---
(In reply to iive from comment #33)
Ahhh... you've reminded me of a detail that I have in fact noticed but forgot
to mention: After the machine freezes and becomes
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #33 from i...@yahoo.com ---
This doesn't sound good.
The sshd dying indicates that the kernel or the CPU has hang. If there is GPU
shader hang this doesn't happen right away, it usually waits 10 seconds before
attempting to reset the
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #32 from MirceaKitsune ---
(In reply to iive from comment #31)
Sounds a lot more complicated, but I'm gladly willing to try it as long as
there's no risk of anything permanently breaking my
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #31 from i...@yahoo.com ---
(In reply to MirceaKitsune from comment #29)
> For the first time ever, I might finally have some very good news on this
> issue! It will take several more days to confirm, then possibly another
> month to
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #30 from MirceaKitsune ---
Today's testing reveals an important detail I had missed: There are likely
multiple different crashes taking place... or at most one crash but triggered
by several
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #29 from MirceaKitsune ---
For the first time ever, I might finally have some very good news on this
issue! It will take several more days to confirm, then possibly another month
to pinpoint the
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #28 from MirceaKitsune ---
Just finished the last test from yesterday's recommendations. It appears I
cannot boot with iommu=off as that disables all USB devices, so I can't use a
keyboard and
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #27 from i...@yahoo.com ---
Loosing recently written files is unfortunately way too common, despite all
filesystem using journaling.
It might help if you call `sync` after writing the file.
If you have kernel with enabled
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #26 from MirceaKitsune ---
I preformed the next test suggested to me, by changing
/etc/X11/xorg.conf.d/50-device.conf to the following content:
Section "Device"
Identifier "Default Device"
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #25 from MirceaKitsune ---
Created attachment 138799
--> https://bugs.freedesktop.org/attachment.cgi?id=138799=edit
GALLIUM_HUD post crash photo
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #24 from MirceaKitsune ---
Created attachment 138798
--> https://bugs.freedesktop.org/attachment.cgi?id=138798=edit
GALLIUM_HUD pre crash screenshot
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #23 from MirceaKitsune ---
I just finished running the GALLIUM_HUD test, and will be taking a look at the
other options next. It was more difficult to test now since the freeze occurs
almost
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #22 from i...@yahoo.com ---
(In reply to MirceaKitsune from comment #21)
> (In reply to iive from comment #20)
>
> That's some amazing feedback, thank you very much! I'll definitely try those
> out, but I have a few questions about
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #21 from MirceaKitsune ---
(In reply to iive from comment #20)
That's some amazing feedback, thank you very much! I'll definitely try those
out, but I have a few questions about a few of these
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #20 from i...@yahoo.com ---
(In reply to MirceaKitsune from comment #16)
> I have moved on to testing the various kernel parameters available for my
> driver and card. As was pointed out by malcolmlewis on the openSUSE forums,
> they
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #19 from MirceaKitsune ---
(In reply to Alex Deucher from comment #18)
> Those parameters are not used on your chip.
That would be quite something, since after setting them I've clearly seen an
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #18 from Alex Deucher ---
(In reply to MirceaKitsune from comment #17)
> I will continue trying different values and seeing how tweaking them changes
> the issue. Please let me know what you think.
Those
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #17 from MirceaKitsune ---
I have a very important preliminary result: Today I tested the last amdgpu
parameters on the list, and seem to have found a set that greatly mitigates the
problem.
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #16 from MirceaKitsune ---
I have moved on to testing the various kernel parameters available for my
driver and card. As was pointed out by malcolmlewis on the openSUSE forums,
they can be
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #15 from MirceaKitsune ---
Today I've ran two tests to ensure that frequencies and DPM are not a factor.
- Setting the DPM profile to low by running the following commands as root:
echo
https://bugs.freedesktop.org/show_bug.cgi?id=105425
MirceaKitsune changed:
What|Removed |Added
See Also|
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #14 from MirceaKitsune ---
(In reply to iive from comment #13)
Like I said, I don't currently believe this is a hardware defect: My video card
isn't even 3 years old. It's a card from Gigabyte
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #13 from i...@yahoo.com ---
(In reply to MirceaKitsune from comment #10)
> Created attachment 138438 [details]
> Screenshot of the Blender window glitching
>
> I should add another detail to the discussion. I know this may be a
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #12 from MirceaKitsune ---
Created attachment 138483
--> https://bugs.freedesktop.org/attachment.cgi?id=138483=edit
Output of: watch cat /sys/kernel/debug/dri/0/amdgpu_pm_info
I decided to
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #11 from MirceaKitsune ---
I'm still struggling to debug this. The more I see the more my jaw drops.
First of all, the rule that disabling anti-aliasing decreases the frequency of
the freeze
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #10 from MirceaKitsune ---
Created attachment 138438
--> https://bugs.freedesktop.org/attachment.cgi?id=138438=edit
Screenshot of the Blender window glitching
I should add another detail to
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #9 from MirceaKitsune ---
And we have a verdict. The influential factor is by far the anti-aliasing, at
least in the case of Xonotic. The other cvars I previously mentioned have
absolutely no
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #8 from MirceaKitsune ---
Testing is still heavily undergoing. There's still nothing conclusive yet, but
I should definitely share a piece of information early on.
To my surprise, it would
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #7 from MirceaKitsune ---
I've been testing this crash using Xonotic during the past two days, granted
it's a game I have a lot of experience customizing. What I found is pretty
interesting and
https://bugs.freedesktop.org/show_bug.cgi?id=105425
Michel Dänzer changed:
What|Removed |Added
Component|Mesa core
74 matches
Mail list logo