From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99275] Kernel 4.9: amdgpu regression; gui flickers; amd radeon rx 460
Date: Sun, 29 Jan 2017 19:11:09 +0000 [thread overview]
Message-ID: <bug-99275-502-F2rt1lBZti@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99275-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1685 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99275
--- Comment #13 from Reimar Imhof <tuxuser@quantentunnel.de> ---
after I've had seen, 4.8 hat the same problem I tried to find the first good
4.8.x:
> git bisect new
107d026ae1c80ac0881f791a58cd115321d111ca is the first new commit
commit 107d026ae1c80ac0881f791a58cd115321d111ca
Author: Will Deacon <will.deacon@arm.com>
Date: Fri Aug 26 11:36:39 2016 +0100
arm64: debug: avoid resetting stepping state machine when TIF_SINGLESTEP
commit 3a402a709500c5a3faca2111668c33d96555e35a upstream.
When TIF_SINGLESTEP is set for a task, the single-step state machine is
enabled and we must take care not to reset it to the active-not-pending
state if it is already in the active-pending state.
Unfortunately, that's exactly what user_enable_single_step does, by
unconditionally setting the SS bit in the SPSR for the current task.
This causes failures in the GDB testsuite, where GDB ends up missing
expected step traps if the instruction being stepped generates another
trap, e.g. PTRACE_EVENT_FORK from an SVC instruction.
This patch fixes the problem by preserving the current state of the
stepping state machine when TIF_SINGLESTEP is set on the current thread.
Cc: <stable@vger.kernel.org>
Reported-by: Yao Qi <yao.qi@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
:040000 040000 98b6a8a0d27ab29b17b6b617e52beb33d56dc604
46030e41ff5783555a6d6e895799aabbe3a0c46e M arch
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2781 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-01-29 19:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 19:25 [Bug 99275] Kernel 4.9: amdgpu regression; gui flickers; amd radeon rx 460 bugzilla-daemon
2017-01-04 19:34 ` bugzilla-daemon
2017-01-04 21:17 ` bugzilla-daemon
2017-01-04 21:17 ` bugzilla-daemon
2017-01-04 21:18 ` bugzilla-daemon
2017-01-04 21:24 ` bugzilla-daemon
2017-01-04 21:35 ` bugzilla-daemon
2017-01-05 9:56 ` bugzilla-daemon
2017-01-05 18:09 ` bugzilla-daemon
2017-01-05 18:36 ` bugzilla-daemon
2017-01-16 20:55 ` bugzilla-daemon
2017-01-29 19:03 ` bugzilla-daemon
2017-01-29 19:04 ` bugzilla-daemon
2017-01-29 19:11 ` bugzilla-daemon [this message]
2017-01-29 19:13 ` bugzilla-daemon
2017-01-31 6:42 ` bugzilla-daemon
2017-02-01 21:08 ` bugzilla-daemon
2017-02-01 22:10 ` bugzilla-daemon
2017-02-03 20:05 ` bugzilla-daemon
2017-02-03 20:11 ` bugzilla-daemon
2017-02-03 20:46 ` bugzilla-daemon
2017-02-12 16:12 ` bugzilla-daemon
2017-02-12 16:17 ` bugzilla-daemon
2017-02-12 16:30 ` bugzilla-daemon
2017-02-12 19:21 ` bugzilla-daemon
2017-02-13 3:10 ` bugzilla-daemon
2017-02-13 18:55 ` bugzilla-daemon
2017-02-14 2:10 ` bugzilla-daemon
2017-02-14 11:55 ` bugzilla-daemon
2017-02-14 11:57 ` bugzilla-daemon
2017-02-14 12:02 ` bugzilla-daemon
2017-02-14 14:05 ` bugzilla-daemon
2017-02-14 15:29 ` bugzilla-daemon
2017-02-14 19:32 ` bugzilla-daemon
2017-02-22 21:25 ` bugzilla-daemon
2017-02-22 21:26 ` bugzilla-daemon
2018-03-24 11:20 ` bugzilla-daemon
2018-12-19 20:07 ` bugzilla-daemon
2019-11-19 8:12 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-99275-502-F2rt1lBZti@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.