Re: 2.6.17-mm4 + hostap + pcmcia + lockdep -- possible recursive locking detected -- (af_callback_keys + sk->sk_family#3){-.-?}, at: [<c119d8db>] sock_def_readable+0x15/0x69

[Miles Lane]

On 7/2/06, Ingo Molnar <mingo@xxxxxxx> wrote:
> * Ingo Molnar <mingo@xxxxxxx> wrote:
>
> > * Miles Lane <miles.lane@xxxxxxxxx> wrote:
> >
> > > I have patches for hostap, pcmcia and lockdep applied to this kernel.
> > > These patches are the ones resulting from several recent message
> > > threads. I just noticed this in my kernel log:
> > >
> > > [ INFO: possible recursive locking detected ]
> > > ---------------------------------------------
> >
> > ok, lockdep should allow same-class read-lock recursion too, because
> > it's used by real code and is being relied upon. Could you try the patch
> > below? [...]
>
> the patches are also included in the latest -mm5 combo patch at:
>
>   http://redhat.com/~mingo/lockdep-patches/lockdep-combo-2.6.17-mm5.patch

I have not seen this particular INFO message show up again.
Therefore, I haven't tested your latest patch yet.  I wanted to determine
whether this problem would occur often.  If you like I can go ahead and
test the patch anyhow.  I am currently testing mm5 + the pcmcia patch and
the hostap patch.  I am looking into a crashing (system lockup) bug that is
triggered by removing my Linksys USB 10/100 Ethernet adapter.  This
problem is 100% repeatable.  I am working on setting up a remote
debugging configuration.

Would you like me to go ahead and test your latest patch?

Thanks,
           Miles
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/