[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5a4c581d0806211022w58648606g65089598524721db@mail.gmail.com>
Date: Sat, 21 Jun 2008 19:22:38 +0200
From: "Alessandro Suardi" <alessandro.suardi@...il.com>
To: "Ingo Molnar" <mingo@...e.hu>
Cc: "Peter Zijlstra" <a.p.zijlstra@...llo.nl>,
"Vegard Nossum" <vegard.nossum@...il.com>,
"Thomas Gleixner" <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [2.6.26-rc5-git2] WARNING: at kernel/lockdep.c:2658 check_flags+0x4c/0x128()
On Thu, Jun 12, 2008 at 12:56 PM, Alessandro Suardi
<alessandro.suardi@...il.com> wrote:
> On Thu, Jun 12, 2008 at 9:30 AM, Ingo Molnar <mingo@...e.hu> wrote:
>>
>> * Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
>>
>>> On Thu, 2008-06-12 at 08:55 +0200, Vegard Nossum wrote:
>>>
>>>
>>> > From: Vegard Nossum <vegard.nossum@...il.com>
>>> > Date: Thu, 12 Jun 2008 08:49:18 +0200
>>> > Subject: [PATCH] x86: more hardirq annotations for notify_die()
>>> >
>>> > Reported-by: Alessandro Suardi <alessandro.suardi@...il.com>
>>> > Signed-off-by: Vegard Nossum <vegard.nossum@...il.com>
>>> > ---
>>> > arch/x86/kernel/traps_32.c | 1 +
>>> > 1 files changed, 1 insertions(+), 0 deletions(-)
>>> >
>>> > diff --git a/arch/x86/kernel/traps_32.c b/arch/x86/kernel/traps_32.c
>>> > index bde6f63..be9ecae 100644
>>> > --- a/arch/x86/kernel/traps_32.c
>>> > +++ b/arch/x86/kernel/traps_32.c
>>> > @@ -569,6 +569,7 @@ void do_##name(struct pt_regs *regs, long error_code) \
>>> > #define DO_VM86_ERROR(trapnr, signr, str, name) \
>>> > void do_##name(struct pt_regs *regs, long error_code) \
>>> > { \
>>> > + trace_hardirqs_fixup(); \
>>> > if (notify_die(DIE_TRAP, str, regs, error_code, trapnr, signr) \
>>> > == NOTIFY_STOP) \
>>> > return; \
>>>
>>> Yeah, I think this is ok, actual traps don't have any way of knowing the
>>> actual IRQ state afaik. So
>>>
>>> Acked-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>
>>
>> applied to tip/x86/urgent - thanks.
>>
>> Alessandro, does the patch from Vegard fix the ltrace warning for you?
>>
>> Ingo
>>
>
> I don't know whether the issue is reproducable at will.
>
> I'll give the patch a go when I come home from work
> later, trying to put back the rogue nautilus RPM and
> putting it under ltrace, then report back.
>
> Thanks for the quick turnaround, hope to be able to
> provide feedback later. Ciao,
All right, finally had time to try this one, and it's good for
me - patch on top of 2.6.26-rc7, the WARNING does not
appear in over three minutes of ltracing nautilus even
with load climbing up to 6 while just two gnome-terminals
(one running 'top' and the other running 'ltrace') and a
firefox with two tabs are opened under XVnc. Hence,
Tested-by: <alessandro.suardi@...il.com>
BTW, both the old and the new nautilus package have
horrible performance under VNC, I guess I noticed the
new one simply due to a fresh-start effect...
Thanks !
--alessandro
"Give me love / Or give me hate
Give me anything that's not just ok"
(Sophia, 'Weightless')
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists