Messages in this thread |  | | Date | Tue, 05 Sep 2006 21:03:17 +0200 | From | Stefan Richter <> | Subject | Re: 2.6.18-rc5-mm1 + all hotfixes -- INFO: possible recursive locking detected |
| |
Miles Lane wrote: > On 9/5/06, Andrew Morton <akpm@osdl.org> wrote: >> On Tue, 5 Sep 2006 10:37:51 -0700 >> "Miles Lane" <miles.lane@gmail.com> wrote: >> >>> ieee1394: Node changed: 0-01:1023 -> 0-00:1023 >>> ieee1394: Node changed: 0-02:1023 -> 0-01:1023 >>> ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0080880002103eae] >>> >>> ============================================= >>> [ INFO: possible recursive locking detected ] >>> 2.6.18-rc5-mm1 #2 >>> --------------------------------------------- >>> knodemgrd_0/2321 is trying to acquire lock: >>> (&s->rwsem){----}, at: [<f8958897>] nodemgr_probe_ne+0x311/0x38d [ieee1394] >>> >>> but task is already holding lock: >>> (&s->rwsem){----}, at: [<f8959078>] nodemgr_host_thread+0x717/0x883 [ieee1394]
How often does this happen?
[...] >> That's a 1394 glitch, possibly introduced by git-ieee1394.patch. > > Would you like me to verify that removing the patch fixes it, or > should I wait for the 2.6.18-rc6-mm1 tree?
My patches "ieee1394: nodemgr: switch to kthread api, replace reset semaphore" and "ieee1394: nodemgr: convert nodemgr_serialize semaphore to mutex" may be relevant. They are included in git-ieee1394.patch.
Could you revert them individually and test? It should be possible to just "patch -p1 -R < ...." the following patchfiles: http://me.in-berlin.de/~s5r6/linux1394/updates/2.6.18-rc5/patches/119-ieee1394-nodemgr-convert-nodemgr_serialize-semaphore-to-mutex.patch If the problem persists, also revert http://me.in-berlin.de/~s5r6/linux1394/updates/2.6.18-rc5/patches/118-ieee1394-nodemgr-switch-to-kthread-api--replace-reset-semaphore.patch
If that does not help, install them again and unapply all ieee1394 patches from -mm. If you have the time.
Thanks a lot, -- Stefan Richter -=====-=-==- =--= --=-= http://arcgraph.de/sr/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |