linux-kernel - [drm:radeon_cp_idle] *ERROR* radeon_cp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1212347789.2580.9.camel@odie.local>
Date:	Sun, 01 Jun 2008 21:16:29 +0200
From:	Simon Holm Thøgersen <odie@...aau.dk>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Cc:	Eric Anholt <eric@...olt.net>, David Airlie <airlied@...ux.ie>,
	dri-devel@...ts.sourceforge.net
Subject: [drm:radeon_cp_idle] *ERROR* radeon_cp_idle called without lock
	held

I can easily trigger an endless stream of the following three lines

[drm:radeon_cp_idle] *ERROR* radeon_cp_idle called without lock held,
held  0 owner eb0908c0 eb0908c0
[drm:radeon_cp_reset] *ERROR* radeon_cp_reset called without lock held,
held  0 owner eb0908c0 eb0908c0
[drm:radeon_cp_start] *ERROR* radeon_cp_start called without lock held,
held  0 owner eb0908c0 eb0908c0

and thereby also lock my system completely up.

I did not dig into this problem, except for applying the attached patch
in order to get some more info and BUG_ON after the first round of
errors, so that sysRq remained usable and I could produce a bunch of
extra data in the dmesg.

Attached is also my config and the output of `lspci -vv' and `dmesg'.

Any ideas?


Simon Holm Thøgersen

View attachment "add-drm-bug_on.patch" of type "text/x-patch" (562 bytes)

View attachment "config" of type "text/plain" (48261 bytes)

View attachment "dmesg" of type "text/plain" (90575 bytes)

View attachment "lspci-vv" of type "text/plain" (11793 bytes)