Bug 23812 - links2 triggers a lockdep trace in drm-next with KMS on
Summary: links2 triggers a lockdep trace in drm-next with KMS on
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-09 07:47 UTC by Radosław Szkodziński
Modified: 2019-11-19 08:08 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Lockdep trace (13.51 KB, text/plain)
2009-09-09 07:47 UTC, Radosław Szkodziński 		no flags Details
View All

Description Radosław Szkodziński 2009-09-09 07:47:40 UTC 
Created attachment 29350 [details]
Lockdep trace

Links2 (the text/low-graphic browser) with framebuffer support on triggers the attached lockdep trace when exiting.
Both KMS and links2 work correctly afterwards.

KMS is enabled and working, drm-next commit cecc6b63a5de547a345c491bb4c18c01a15984a4
The card is RV670, Mobility Radeon HD3850.
Comment 1 Martin Peres 2019-11-19 08:08:00 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/71.

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.