https://bugzilla.kernel.org/show_bug.cgi?id=207383
aka...@pm.me changed:
What|Removed |Added
CC||aka...@pm.me
--- Comment #121 from
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #120 from Duncan (1i5t5.dun...@cox.net) ---
On Wed, 06 Jan 2021 12:05:17 +
bugzilla-dae...@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=207383
>
> --- Comment #119 from Duncan (1i5t5.dun...@cox.net)
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #119 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to Christopher Snowhill from comment #118)
> Now experiencing this attempting to run Luxmark with literally any OpenCL
> runtime on my RX 480, be it ROCm, Clover, or AMDGPU Pro
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #118 from Christopher Snowhill (kod...@gmail.com) ---
Now experiencing this attempting to run Luxmark with literally any OpenCL
runtime on my RX 480, be it ROCm, Clover, or AMDGPU Pro 20.45. Goody gumdrops,
wlroots added support for
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #117 from Duncan (1i5t5.dun...@cox.net) ---
For those on stable-series 5.4 and/or interested in related bugs...
FWIW, there's an (apparently different) atomic_commit_tail bug reported against
5.4.58 now, bug #208913, with the patch
https://bugzilla.kernel.org/show_bug.cgi?id=207383
Duncan (1i5t5.dun...@cox.net) changed:
What|Removed |Added
Status|NEW |RESOLVED
Kernel
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #115 from Duncan (1i5t5.dun...@cox.net) ---
So 5.8.0 has been out for a few hours with the patch-fix, and I see Greg K-H
has it applied to the 5.7 stable tree as well as 5.4 LTS (the bug was in 5.4
but latent, not exposed until
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #114 from Jeremy Kescher (jer...@kescher.at) ---
(In reply to Duncan from comment #108)
> (In reply to Paul Menzel from comment #107)
> > Everyone seeing this, it’d be great, if you tested
> >
> > [PATCH] drm/amd/display: Clear
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #113 from laser.eyess.track...@gmail.com ---
I have been using this patch for about 24 hours now, and there has not been any
noticeable performance degradation. I have not experienced any crashes, but it
was much harder for me to get
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #112 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to Paul Menzel from comment #107)
> Everyone seeing this, it’d be great, if you tested
>
> [PATCH] drm/amd/display: Clear dm_state for fast updates
For the record, with no
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #111 from mn...@protonmail.com ---
Yeah, no noticeable performance impact on my end either. I don't really
see why it would cause a performance impact either. I could run a benchmark
to compare but I don't really know what to
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #110 from Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) ---
That's inline with the expectations I think.
That patch shouldn't cause any performance or stuttering impacts and it should
resolve the protection fault.
If there were
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #109 from zzyx...@gmail.com ---
I've been testing mnrzk's patch for about 12 hours as well, so far so good. No
obvious performance degradation has appeared, at least that I can discern just
by "feel". My testing has been interrupted a
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #108 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to Paul Menzel from comment #107)
> Everyone seeing this, it’d be great, if you tested
>
> [PATCH] drm/amd/display: Clear dm_state for fast updates
I've been testing it
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #107 from Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de)
---
Everyone seeing this, it’d be great, if you tested
[PATCH] drm/amd/display: Clear dm_state for fast updates
and reported any noticeable performance
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #106 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to Duncan from comment #101)
> (In reply to Nicholas Kazlauskas from comment #95)
> > Created attachment 290583 [details]
> >
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #105 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to Duncan from comment #102)
> (In reply to Duncan from comment #101)
> > (In reply to Nicholas Kazlauskas from comment #95)
> > >
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #104 from mn...@protonmail.com ---
(In reply to mnrzk from comment #103)
> (In reply to Nicholas Kazlauskas from comment #95)
> > Created attachment 290583 [details]
> > 0001-drm-amd-display-Force-add-all-CRTCs-to-state-when-us.patch
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #103 from mn...@protonmail.com ---
(In reply to Nicholas Kazlauskas from comment #95)
> Created attachment 290583 [details]
> 0001-drm-amd-display-Force-add-all-CRTCs-to-state-when-us.patch
>
> So the sequence looks like the
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #102 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to Duncan from comment #101)
> (In reply to Nicholas Kazlauskas from comment #95)
> > 0001-drm-amd-display-Force-add-all-CRTCs-to-state-when-us.patch
>
> Just booted to 5.8-rc7
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #101 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to Nicholas Kazlauskas from comment #95)
> Created attachment 290583 [details]
> 0001-drm-amd-display-Force-add-all-CRTCs-to-state-when-us.patch
Just booted to 5.8-rc7 with this
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #100 from mn...@protonmail.com ---
I posted the patch on the LKML [1] just now so I can get the other
reviewers' input on it. I think it's safe to say that it's working now due
to how much I've tested it but I will test more over the
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #99 from mn...@protonmail.com ---
(In reply to Nicholas Kazlauskas from comment #98)
> As much as I'd like to remove the DRM private object from the state instead
> of just carrying it over I'd really rather not be hacking around
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #98 from Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) ---
As much as I'd like to remove the DRM private object from the state instead of
just carrying it over I'd really rather not be hacking around behavior from the
DRM core
https://bugzilla.kernel.org/show_bug.cgi?id=207383
mn...@protonmail.com changed:
What|Removed |Added
Attachment #290485|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #96 from mn...@protonmail.com ---
(In reply to Nicholas Kazlauskas from comment #95)
> Created attachment 290583 [details]
> 0001-drm-amd-display-Force-add-all-CRTCs-to-state-when-us.patch
>
> So the sequence looks like the
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #95 from Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) ---
Created attachment 290583
--> https://bugzilla.kernel.org/attachment.cgi?id=290583=edit
0001-drm-amd-display-Force-add-all-CRTCs-to-state-when-us.patch
So the sequence
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #94 from mn...@protonmail.com ---
I just got this interesting log w/ drm.debug=0x54 right before a crash:
[ 971.537862] [drm:drm_atomic_state_init [drm]] Allocated atomic state
cac2d51a
[ 971.537909]
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #93 from mn...@protonmail.com ---
(In reply to Nicholas Kazlauskas from comment #92)
> This sounds very similar to a bug I fixed a year ago but that issue was with
> freeing the dc_state.
>
>
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #92 from Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) ---
This sounds very similar to a bug I fixed a year ago but that issue was with
freeing the dc_state.
https://bugzilla.kernel.org/show_bug.cgi?id=204181
1. Client requests
https://bugzilla.kernel.org/show_bug.cgi?id=207383
laser.eyess.track...@gmail.com changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #90 from mn...@protonmail.com ---
(In reply to Christian König from comment #89)
> (In reply to mnrzk from comment #87)
> > Good news, I wrote a patch that fixed this bug on my machine and submitted
> > it to the Linux kernel mailing
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #89 from Christian König (christian.koe...@amd.com) ---
(In reply to mnrzk from comment #87)
> Good news, I wrote a patch that fixed this bug on my machine and submitted
> it to the Linux kernel mailing list [1].
You should probably
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #88 from mn...@protonmail.com ---
Created attachment 290485
--> https://bugzilla.kernel.org/attachment.cgi?id=290485=edit
Possible bug fix #1
(In reply to mnrzk from comment #87)
> Good news, I wrote a patch that fixed this bug on
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #87 from mn...@protonmail.com ---
Good news, I wrote a patch that fixed this bug on my machine and submitted
it to the Linux kernel mailing list [1].
I've tested this for almost 12 hours with KASAN enabled and 3 hours with
all
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #86 from mn...@protonmail.com ---
Created attachment 290475
--> https://bugzilla.kernel.org/attachment.cgi?id=290475=edit
KASAN Use-after-free
Good news, I got KASAN to spit out a use-after-free bug report.
Here's the KASAN bug
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #85 from mn...@protonmail.com ---
(In reply to Christian König from comment #83)
> Instead of working around the bug I think we should concentrate on nailing
> the root cause.
>
> I suggest to insert an use after free check into just
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #84 from Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) ---
We don't manually free the dm_state from amdgpu, that should be handled by the
DRM core.
It should generally only be freed once it's no longer use by the DRM core as
well
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #83 from Christian König (christian.koe...@amd.com) ---
Instead of working around the bug I think we should concentrate on nailing the
root cause.
I suggest to insert an use after free check into just that structure. In other
words
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #82 from mn...@protonmail.com ---
(In reply to Kees Cook from comment #81)
> I assume this is the change, BTW:
>
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h
> b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h
>
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #81 from Kees Cook (k...@outflux.net) ---
I assume this is the change, BTW:
diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h
b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h
index d61186ff411d..2b8da2b17a5d 100644
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #80 from Kees Cook (k...@outflux.net) ---
(In reply to mnrzk from comment #79)
> I wonder if there's any way to set a watchpoint to see where exactly the
> dm_atomic_state gets filled with garbage data.
mm/slub.c set_freepointer()
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #79 from mn...@protonmail.com ---
(In reply to Kees Cook from comment #78)
> (In reply to mnrzk from comment #76)
> > If my understanding is correct, base would have previously been filled with
> > the freelist pointer (since it's the
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #78 from Kees Cook (k...@outflux.net) ---
(In reply to mnrzk from comment #76)
> If my understanding is correct, base would have previously been filled with
> the freelist pointer (since it's the first 8 bytes). Now since the freelist
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #77 from Kees Cook (k...@outflux.net) ---
(Midair collision... you saw the same about the structure layout as I did.
Here's my comment...)
(In reply to mnrzk from comment #30)
> I've been looking at this bug for a while now and I'll
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #76 from mn...@protonmail.com ---
(In reply to Kees Cook from comment #75)
> Hi!
>
> First, let me say sorry for all the work my patch has caused! It seems like
> it might be tickling another (previously dormant) bug in the gpu
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #75 from Kees Cook (k...@outflux.net) ---
Hi!
First, let me say sorry for all the work my patch has caused! It seems like it
might be tickling another (previously dormant) bug in the gpu driver.
(In reply to mnrzk from comment #30)
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #74 from Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de) ---
I sent a message to the LKML and amd-gfx list [1], asking Kees and Andrew on
how to proceed.
[1]: https://lkml.org/lkml/2020/7/21/729
"[Regression] hangs
https://bugzilla.kernel.org/show_bug.cgi?id=207383
Jeremy Kescher (jer...@kescher.at) changed:
What|Removed |Added
CC||jer...@kescher.at
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #72 from Vinicius (mphant...@yahoo.com.br) ---
Confirming that reverting 3202fa62f, cbfc35a48 and 89b83f282, fixed my
polaris10 too.
Tested with 5.7.8 and 5.7.9, Radeon RX 570.
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #71 from Anthony Ruhier (anthony.ruh...@gmail.com) ---
Just to give some news, I can confirm that I haven't had any freeze since
Wednesday. Usually, when my system just idled, it would quickly trigger the
bug. That or doing something
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #70 from Stratos Zolotas (str...@gmail.com) ---
(In reply to Anthony Ruhier from comment #69)
>
> You're talking about having the bug with 5.7.7 vanilla, right? Not with the
> revert of the commits quoted above?
Yes! It seemed to
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #69 from Anthony Ruhier (anthony.ruh...@gmail.com) ---
(In reply to Stratos Zolotas from comment #68)
> (In reply to Stratos Zolotas from comment #60)
> >
> > To make things looks more strange... I have a non-explicable development
>
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #68 from Stratos Zolotas (str...@gmail.com) ---
(In reply to Stratos Zolotas from comment #60)
>
> To make things looks more strange... I have a non-explicable development
> with this issue. When it appeared to me I was in the middle
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #67 from Anthony Ruhier (anthony.ruh...@gmail.com) ---
No freeze for me too, and I compiled firefox yesterday, which usually triggers
a freeze on 5.7, and nothing yet. That's some really good news if it stays
true, thanks a lot
https://bugzilla.kernel.org/show_bug.cgi?id=207383
Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #65 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to Duncan from comment #63)
> NB: The 3202fa62f followups are cbfc35a48 and 89b83f282. That should let
> anyone else with git and kernel building skills try reverting the three.
>
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #64 from Anthony Ruhier (anthony.ruh...@gmail.com) ---
(In reply to Duncan from comment #63)
> (In reply to Duncan from comment #62)
> > I've applied the three 320-and-followups revert-patches to
> > v5.8-rc5-8-g0dc589da8 and just did
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #63 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to Duncan from comment #62)
> I've applied the three 320-and-followups revert-patches to
> v5.8-rc5-8-g0dc589da8 and just did the rebuild with them applied.
> Now to reboot to it
https://bugzilla.kernel.org/show_bug.cgi?id=207383
Duncan (1i5t5.dun...@cox.net) changed:
What|Removed |Added
Kernel Version|5.7-rc1 - 5.7 - 5.8-rc4+|5.7-rc1 - 5.7 - 5.8-rc5+
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #61 from Christopher Snowhill (kod...@gmail.com) ---
It may be worth noting that I also haven't experienced this crash lately, and
one of the things I did recently was update my motherboard BIOS, which included
an update from AGESA
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #60 from Stratos Zolotas (str...@gmail.com) ---
(In reply to Chan Cuan from comment #59)
> I didn't have this issue prior to installing the 5.7.7 kernel though...
To make things looks more strange... I have a non-explicable
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #59 from chancua...@gmail.com ---
(In reply to Paul Menzel from comment #54)
> (In reply to Stratos Zolotas from comment #53)
>
> > Don't know if it helps. I'm getting a similar issue on Opensuse Tumbleweed
> > with kernel 5.7.7.
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #58 from Anthony Ruhier (anthony.ruh...@gmail.com) ---
Sorry, I forgot to say that I have a vega64.
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #57 from Anthony Ruhier (anthony.ruh...@gmail.com) ---
To give some precision about the kernel version range, I'm staying on 5.6.19
for a while, which doesn't have the issue. It's pretty bad though, as it's EOL.
Only the 5.7 branch
https://bugzilla.kernel.org/show_bug.cgi?id=207383
Duncan (1i5t5.dun...@cox.net) changed:
What|Removed |Added
Kernel Version|5.7-rc1 - 5.7 - 5.8-rc1+|5.7-rc1 - 5.7 - 5.8-rc4+
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #55 from Stratos Zolotas (str...@gmail.com) ---
(In reply to Paul Menzel from comment #54)
> Thank you for your report. How quickly can you reproduce it? If you could
> bisect the issue to pinpoint the culprit commit between 5.7.5
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #54 from Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de) ---
(In reply to Stratos Zolotas from comment #53)
> Don't know if it helps. I'm getting a similar issue on Opensuse Tumbleweed
> with kernel 5.7.7. Reverting to kernel
https://bugzilla.kernel.org/show_bug.cgi?id=207383
Stratos Zolotas (str...@gmail.com) changed:
What|Removed |Added
CC||str...@gmail.com
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #52 from Michel Dänzer (mic...@daenzer.net) ---
(In reply to rtmasura+kernel from comment #51)
> that didn't read well, with vblank_mode off for XFWM I don't have this issue
> at all.
That just avoids the problem by not doing any
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #51 from rtmasura+ker...@hotmail.com ---
that didn't read well, with vblank_mode off for XFWM I don't have this issue at
all.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #50 from rtmasura+ker...@hotmail.com ---
I have 3 monitors, 2 1080p and one 1440p. Happens when I use vblank_mode glx or
xpresent, off and I'm stable.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #49 from Christopher Snowhill (kod...@gmail.com) ---
One possibility that I hadn't considered when I was originally testing this. I
use the GNOME 3 desktop on Arch, and have two monitors, one 3840x2160@60Hz, one
1920x1080@60Hz, both
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #48 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to Duncan from comment #47)
> > [I]dea to just try patch-reverting them on top of
> > 5.7 or current 5.8-rc, thus eliminating the apparently unrelated
> > kernel-panics I''ve twice
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #47 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to Duncan from comment #39)
> 28 candidates ATM, several of which are OCFS2 or spelling
> fixes neither of which should affect this bug. Excluding those there are
> eleven left;
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #46 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to Fabian Möller from comment #45)
> Applying 6eb3cf2e06d22b2b08e6b0ab48cb9c05a8e1a107 to v5.7.7 fixed the issue
> for a RX5700/Navi10 under Wayland for me.
Polaris11 uses a
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #45 from Fabian Möller (fabian...@gmail.com) ---
(In reply to Christopher Snowhill from comment #43)
> What about this patch?
>
> https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-5.
>
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #44 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to Christopher Snowhill from comment #43)
> What about this patch?
>
> https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-5.
> 8=6eb3cf2e06d22b2b08e6b0ab48cb9c05a8e1a107
https://bugzilla.kernel.org/show_bug.cgi?id=207383
Christopher Snowhill (kod...@gmail.com) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #42 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to Alex Deucher from comment #40)
> Does this patch help?
No. v5.7 with the patch applied gave me the same graphics freeze, with the
usual log trace confirming it's _this_ bug.
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #41 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to Alex Deucher from comment #40)
> Does this patch help?
Booted to v5.7 with it applied now. We'll see. Since the bug can take awhile
to trigger on my hardware, if the patch
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #40 from Alex Deucher (alexdeuc...@gmail.com) ---
Does this patch help?
https://gitlab.freedesktop.org/drm/amd/uploads/356586b6aa81f64cfa9b4b034499fdd8/amdgpu-bugfix-revert-vmalloc-size-change.patch
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=207383
Duncan (1i5t5.dun...@cox.net) changed:
What|Removed |Added
Attachment #290101|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=207383
Duncan (1i5t5.dun...@cox.net) changed:
What|Removed |Added
Attachment #290093|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #37 from mn...@protonmail.com ---
>Notice, no drm tree, tho whatever buggy commit it is obviously affects
>drm/amdgpu.
Yeah, I kind of noticed that while I was just skimming through the commit
history. Perhaps it's possible that the
https://bugzilla.kernel.org/show_bug.cgi?id=207383
Duncan (1i5t5.dun...@cox.net) changed:
What|Removed |Added
Attachment #289911|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #35 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to mnrzk from comment #34)
> Has anyone tried 5.8-rc3? I've been testing it out for the past 3 hours and
> it seems stable to me.
I have now (well, v5.8.0-rc3-00017-g7c30b859a).
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #34 from mn...@protonmail.com ---
Has anyone tried 5.8-rc3? I've been testing it out for the past 3 hours and it
seems stable to me. Also, there were some amdgpu drm fixes pushed between rc2
and rc3 which could have fixed it.
Could
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #33 from Michel Dänzer (mic...@daenzer.net) ---
(In reply to rtmasura+kernel from comment #24)
> xfwm4 --replace --vblank=glx &
FWIW, I recommend
xfwm4 --vblank=xpresent
instead. --vblank=glx is less efficient and relies on rather
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #32 from Duncan (1i5t5.dun...@cox.net) ---
Created attachment 289911
--> https://bugzilla.kernel.org/attachment.cgi?id=289911=edit
Partial git bisect log
(In reply to zzyxpaw from comment #29)
> @Duncan I'm not sure if you want to
https://bugzilla.kernel.org/show_bug.cgi?id=207383
Duncan (1i5t5.dun...@cox.net) changed:
What|Removed |Added
Kernel Version|5.7-rc1, 5.7-rc2, 5.7-rc3 |5.7-rc1 - 5.7 - 5.8-rc1+
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #30 from mn...@protonmail.com ---
I've been looking at this bug for a while now and I'll try to share what I've
found about it.
In some conditions, when amdgpu_dm_atomic_commit_tail calls
dm_atomic_get_new_state,
https://bugzilla.kernel.org/show_bug.cgi?id=207383
zzyx...@gmail.com changed:
What|Removed |Added
CC||zzyx...@gmail.com
--- Comment #29
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #28 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to rtmasura+kernel from comment #27)
> and another crash, chrome's good at causing them (watching youtube). Used -s
> "" for the setting which I think should set it to 'auto', and
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #27 from rtmasura+ker...@hotmail.com ---
and another crash, chrome's good at causing them (watching youtube). Used -s ""
for the setting which I think should set it to 'auto', and what I assumed was
default. I've changed that to -s
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #26 from rtmasura+ker...@hotmail.com ---
and just got another crash, only watching a video in chrome. Guess the chrome
bit at the end might be more important than I thought
I *think* I've turned off the glx for xfwm.. we'll see. My
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #25 from rtmasura+ker...@hotmail.com ---
Same kernel (5.7.4) and I'll try to reproduce it, and if it happens I'll turn
off the screen tear and try to reproduce again
Let me know if that's anything I can provide you
--
You are
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #24 from rtmasura+ker...@hotmail.com ---
I've been up and stable on XFCE4 since that last message, but just crashed
today with a bit of a different error. This happened after I turned on a screen
tear fix:
xfconf-query -c xfwm4 -p
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #23 from rtmasura+ker...@hotmail.com ---
Yeah, over 24 hours and still stable. And glad I could help, I rarely have
anything I can give back to the community.
And wow, that much work. Truly, we all do appreciate your work, but I
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #22 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to rtmasura+kernel from comment #21)
> OK. I've uninstalled the vast majority of KDE and am using a vanilla XFCE4.
> It's been about 12 hours on 5.7.4-arch1-1 and I have yet to have
1 - 100 of 108 matches
Mail list logo
