On Thu, Mar 13, 2014 at 09:38:45AM -0400, Ilia Mirkin wrote:
On Sun, Mar 9, 2014 at 10:51 AM, Marcin Slusarz marcin.slusarz@gmail.com wrote:
[ 326.168487] ====================================================== [ 326.168491] [ INFO: possible circular locking dependency detected ] [ 326.168496] 3.13.6 #1270 Not tainted [ 326.168500] ------------------------------------------------------- [ 326.168504] ldconfig/22297 is trying to acquire lock: [ 326.168507] (&(&priv->fan->lock)->rlock){-.-...}, at: [<ffffffffa00d5363>] nouveau_fan_update+0xeb/0x252 [nouveau] [ 326.168551] but task is already holding lock: [ 326.168555] (&(&priv->sensor.alarm_program_lock)->rlock){-.-...}, at: [<ffffffffa00d6a8a>] alarm_timer_callback+0xf1/0x179 [nouveau] [ 326.168587] which lock already depends on the new lock. (...)
Marcin, how reproducible is this? What hardware was this on? If it's reasonably reproducible perhaps it makes sense to file a bug in the fd.o tracker?
It happened only once so far (but I don't use this machine every day) - on the first boot of 3.13 kernel. At that time the machine was quite hot (it was rebuilding the whole system (Gentoo) *and* CPU fan was dusty), so it probably affected GPU temperature. It's NVA8 card (dmesg attached).
Marcin