Re: traceback on 3.2.7-rt13

Thomas Gleixner
2012-03-02T10:41:13Z

[-- Attachment #1: Type: TEXT/PLAIN, Size: 792 bytes --]

On Thu, 1 Mar 2012, John Kacur wrote:
> On Thu, Mar 1, 2012 at 4:23 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> > That's why I asked to revert the
> >
> >       acpi-make-gbl-hardware-lock-raw.patch
> >       acpi-make-ec-lock-raw-as-well.patch
> >
> > patches, so we can get that information.
> >
> > It might be a non issue on 3.2 and only a 3.0 problem, but as I can't
> > find anything I'm going to drop those patches from the next 3.2
> > release and wait for proper bugreports coming again :)
> >
>
> FWIW
> I believe the latter comes from here: https://lkml.org/lkml/2011/12/3/53

And how does that help? I know that the ec lock conversion was a
follow up to the gbl hardware lock conversion, but I need to see the
backtrace again which made us convert gbl lock.

Thanks,

tglx