From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 114061] New: xorg session flickers after resume from suspend
Date: Tue, 08 Mar 2016 23:44:22 +0000 [thread overview]
Message-ID: <bug-114061-11804@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=114061
Bug ID: 114061
Summary: xorg session flickers after resume from suspend
Product: Drivers
Version: 2.5
Kernel Version: 4.1.18
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Infiniband/RDMA
Assignee: drivers_infiniband-rdma-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org
Reporter: e.sovetkin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Regression: No
Created attachment 208321
--> https://bugzilla.kernel.org/attachment.cgi?id=208321&action=edit
git bisect log
Xorg session flickers after resume from suspend. Restarting Xorg solves the
issue.
The problem occurs in linux-lts 4.1.18-1 and linux-lts 4.1.19-1.
Downgrading to linux-lts 4.1.17-1 solves the issue.
Journal doesn't have any relevant messages (compared logs with 4.1.17-1 and
4.1.19-1 running kernel).
Additional info:
* Laptop: Medion Akoya
* CPU: Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz
* core/linux-lts 4.1.18-1, 4.1.19-1 affected. 4.1.17 is not affected
Steps to reproduce: put machine to suspend, resume.
git bisect leads to the following commit:
# first bad commit: [40ced0bb2cd8bd17c4f1061176c2ca1db71ec667] dmaengine:
at_xdmac: fix resume for cyclic transfers
git bisect log is attached
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2016-03-08 23:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-114061-11804@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.