Bug 94484 - Kernel BUG with latest radeon driver
Summary: Kernel BUG with latest radeon driver
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: high critical
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-10 21:52 UTC by Tyler Brock
Modified: 2019-11-19 09:13 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
journalctl output when radeon driver crashes (7.98 KB, text/plain)
2016-03-10 21:52 UTC, Tyler Brock
no flags Details
Output from journalctl -ab (276.73 KB, text/plain)
2016-03-17 16:51 UTC, Tyler Brock
no flags Details
dmesg output (68.24 KB, text/plain)
2016-03-17 16:53 UTC, Tyler Brock
no flags Details
journalctl output showing error (3.88 MB, text/plain)
2016-03-17 16:56 UTC, Tyler Brock
no flags Details

Description Tyler Brock 2016-03-10 21:52:29 UTC
Created attachment 122213 [details]
journalctl output when radeon driver crashes

Hey everyone, I'm running Linux 4.4.5 and Radeon driver xf86-video-ati 1:7.6.1 on wayland.

I had no problems about a week ago but since using this version I frequently go to wake up my display by hitting a key on keyboard or moving the mouse and find that my computer has completely crashed (requiring a hard reboot).

I've included the relevant output from journalctl.
Comment 1 Alex Deucher 2016-03-11 15:21:22 UTC
Please attach your xorg log and dmesg output.  Any chance you could bisect?
Comment 2 Tyler Brock 2016-03-17 16:51:24 UTC
Created attachment 122382 [details]
Output from journalctl -ab

I'm running wayland so there is no xorg.log but I can provide the output of journalctl
Comment 3 Tyler Brock 2016-03-17 16:53:04 UTC
Created attachment 122383 [details]
dmesg output

Adding dmesg output
Comment 4 Tyler Brock 2016-03-17 16:56:30 UTC
Created attachment 122384 [details]
journalctl output showing error

Ugh sorry, this is the one you want. The other two attachments were for this boot (which is fine) and not the prior one.
Comment 5 Tyler Brock 2016-03-24 17:38:00 UTC
Anything I can do to help? Bisecting would be hard as its not reproducible 100% of the time. It would essentially take a day to test each revision.
Comment 6 Michel Dänzer 2016-03-25 00:44:31 UTC
(In reply to Tyler Brock from comment #5)
> Anything I can do to help? Bisecting would be hard as its not reproducible
> 100% of the time. It would essentially take a day to test each revision.

That's fine; take your time. (If you had started when you reported the bug, you might be done by now :)
Comment 7 Martin Peres 2019-11-19 09:13:50 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/699.


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.