From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106474] "CPU1 stuck for XXs: Xorg" since update to linux-4.16.x
Date: Fri, 11 May 2018 06:41:05 +0000 [thread overview]
Message-ID: <bug-106474-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1081 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106474
Bug ID: 106474
Summary: "CPU1 stuck for XXs: Xorg" since update to
linux-4.16.x
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: linuxhippy@gmail.com
Created attachment 139489
--> https://bugs.freedesktop.org/attachment.cgi?id=139489&action=edit
screenshot
After updating the Laptop of a friend running Fedora 27 to linux-4.16.4/5/6 it
frequently gets stuck when starting Xorg - please see the attached screenshot.
The machine is a AMD Beema based Hewlett-Packard HP 355 G2/22C1, BIOS F.10
02/12/2015 running the latest Fedora 27 packages.
Graphics stack is default (glamor, radeon kernel module).
Linux-4.15.17 works absolutly flawless.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2495 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 reply other threads:[~2018-05-11 6:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 6:41 bugzilla-daemon [this message]
2018-05-11 6:42 ` [Bug 106474] "CPU1 stuck for XXs: Xorg" since update to linux-4.16.x bugzilla-daemon
2018-05-11 14:51 ` bugzilla-daemon
2018-05-11 17:15 ` bugzilla-daemon
2019-11-19 9:33 ` 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-106474-502@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).