Arjan van de Ven wrote:
> On Wed, 2006-08-16 at 18:06 +0200, Michael Buesch wrote:
>> On Wednesday 16 August 2006 05:54, Larry Finger wrote:
>>>
>>> I'm at a loss here. Can anyone explain how to interpret this dump? I
>>> think I see a general protection fault, but what to do from there is a
>>> my
Michael Buesch wrote:
>
> Hm, weird bug.
> I can't reproduce this on i386 or PPC.
> Could it be a bug in the lockdep code?
>
It could be. I'll send it on to LKML. Perhaps one of the experts
there can tell us. It doesn't seem to cause any trouble, but I get
one of these when bcm43xx starts.
Are
On Wed, 2006-08-16 at 18:06 +0200, Michael Buesch wrote:
> On Wednesday 16 August 2006 05:54, Larry Finger wrote:
> > Using vanilla wireless-2.6 from Linville's tree as updated today, I
> > get a warning generated by the statement
> > if (DEBUG_LOCKS_WARN_ON(!irqs_disabled()))
> > in kerne
On Wednesday 16 August 2006 05:54, Larry Finger wrote:
> Using vanilla wireless-2.6 from Linville's tree as updated today, I
> get a warning generated by the statement
> if (DEBUG_LOCKS_WARN_ON(!irqs_disabled()))
> in kernel.lockdep.c. This warning only occurs when my wireless
> interface
Using vanilla wireless-2.6 from Linville's tree as updated today, I
get a warning generated by the statement
if (DEBUG_LOCKS_WARN_ON(!irqs_disabled()))
in kernel.lockdep.c. This warning only occurs when my wireless
interface is inserted and bcm43xx-softmac is activated. For that
reason I h
