Kernel Bug Tracker – Bug 11215
INFO: possible recursive locking detected ps2_command
Last modified: 2013-12-19 15:04:16 UTC
Subject : INFO: possible recursive locking detected ps2_command
Submitter : "Zdenek Kabelac" <email@example.com>
Date : 2008-07-31 9:41
References : http://marc.info/?l=linux-kernel&m=121749737011637&w=4
This entry is being used for tracking a regression from 2.6.26. Please don't
close it until the problem is fixed in the mainline.
Methinks this should be assigned to Dmitry, not Russell.
Actually Peter... I don't know why lockdep annotation only works first time around.
Handled-By : Dmitry Torokhov <firstname.lastname@example.org>
No, it is not handled by me. As far as I know locking in serio and psmouse is correct and I do not know lockdep well enough to tell why the annotation on pass-through port works only once.
Not-Handled-By : Dmitry Torokhov <email@example.com>
Handled-By : Peter Zijlstra <firstname.lastname@example.org>
Just an update as a response to automatically generated request message from Rafael - this trace is still displayed when PS2 mouse is reattached to my docking station.
Tested with todays kernel commit: 10fec20ef5eec1c91913baec1225400f0d02df40
Warning message still present with commit: (Tue Aug 26 10:45:20 2008)
Obviously no one has made any updates in lockdep checker neither in ps2 driver - so I still get the same INFO call while using 2.6.28-rc3 kernel
Not-Handled-By : Peter Zijlstra <email@example.com>
This INFO trace is still present in 2.6.28-rc8 - someone should probably check if the nesting of this lock is properly marked in the source, so the lockdep validator could be quiet.
*** Bug 11662 has been marked as a duplicate of this bug. ***
*** Bug 15371 has been marked as a duplicate of this bug. ***
Hum... I _guess_ this is still present.
Nobody here wanna show off a little lockdep-fu?
Hey. I reported similar report few months ago. See bug #34922 . It happened when resuming my ThinkPad T43. I was not using any docking station, and was just using internal tracpoint and/or touchpad. So it is essentially impossible it was disconected physically. It can still be possible there were some power fluctutations and trackpoint chipset performed reset, and this triggered this problem. It can be also purly software problem in kernel.
*** Bug 34922 has been marked as a duplicate of this bug. ***