Bug 106474 - "CPU1 stuck for XXs: Xorg" since update to linux-4.16.x
Summary: "CPU1 stuck for XXs: Xorg" since update to linux-4.16.x
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-11 06:41 UTC by Clemens Eisserer
Modified: 2019-11-19 09:33 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
screenshot (274.76 KB, image/jpeg)
2018-05-11 06:41 UTC, Clemens Eisserer 		no flags Details
dmesg of the affected machine running 4.15.17 (70.81 KB, text/plain)
2018-05-11 06:42 UTC, Clemens Eisserer 		no flags Details
View All

Description Clemens Eisserer 2018-05-11 06:41:05 UTC 
Created attachment 139489 [details]
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.
Comment 1 Clemens Eisserer 2018-05-11 06:42:14 UTC 
Created attachment 139490 [details]
dmesg of the affected machine running 4.15.17
Comment 2 Alex Deucher 2018-05-11 14:51:14 UTC 
Can you bisect?
Comment 3 Clemens Eisserer 2018-05-11 17:15:40 UTC 
unfortunately not on that machine :/
Comment 4 Martin Peres 2019-11-19 09:33:34 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/851.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.