[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0904221321410.24310@gandalf.stny.rr.com>
Date: Wed, 22 Apr 2009 13:22:34 -0400 (EDT)
From: Steven Rostedt <rostedt@...dmis.org>
To: Jeremy Fitzhardinge <jeremy@...p.org>
cc: Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...e.hu>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Glauber de Oliveira Costa <gcosta@...hat.com>,
Chris Wright <chrisw@...s-sol.org>,
Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [PATCH 0/2] [GIT PULL] tracing: various bug fixes
On Wed, 22 Apr 2009, Jeremy Fitzhardinge wrote:
> >
> >
> > > Do you have CONFIG_PARAVIRT on? When I disabled it, I have yet to
> > > reproduce the bug. But I've only rebooted a few times. I'm going to
> > > continue to reboot to see if I can trigger it.
> > >
> >
> >
> > Yes it is enabled.
> >
> >
> >
> >
> > > I'm thinking that the paravirt alternative code may have clobbered a
> > > register in either the enable or disabling of interrupts. This might cause
> > > a strange value to go into the hardirqs_enabled flag.
> > >
> >
> >
> >
> > Ok I will try it without PARAVIRT and tell you if I can reproduce it.
> >
>
> Interesting. What code is generated for native_irq_enable/disable?
Note, when I take my standard config and enable PARAVIRT and LOCKDEP it
still boots up fine. It may be a combination of some configs :-/
I'm currently doing a "config bisect" to find out what configs are needed.
-- Steve
--
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