Re: perf sched record hangs machine

[Ingo Molnar]

* Cyrill Gorcunov <gorcunov@xxxxxxxxx> wrote:

> On 9/23/09, Ingo Molnar <mingo@xxxxxxx> wrote:
> >
> > * Chris Malley <mail@xxxxxxxxxxxxxxxxx> wrote:
> >
> >> 2009/9/23 Cyrill Gorcunov <gorcunov@xxxxxxxxx>:
> >> >
> >> > Btw, meanwhile Chris may try to pass lapic boot-option in attempt to
> >> > reenable apic via msr registers. Also (iirc) i feel we may be hiding
> >> > errors if complete noop apic would be used since i belive we need to
> >> > check out under which condition a particular operation is called and
> >> > when apic is disabled it's mean we're switched to UP mode and
> >> > inter-cpu interrupts are under suspicion too. Will take a look during
> >> > ~6 hours ;)
> >> >
> >>
> >> Hi Cyrill
> >>
> >> Heh, yes that just occurred to me as well.  With the lapic boot option
> >> I can't reproduce the problem, and get a good recording every time.
> >> Don't know why the BIOS had disabled it (can't see any specific
> >> option).
> >
> > Would still be important to fix the crash - there are boxes where lapics
> > are disabled permanently and cannot be re-enabled. (plus most people
> > dont touch their defaults and dont add funky boot options - so crashing
> > is not an option)
> >
> 
> Ingo, Chris, could you try Peter's patch? It seems like what we need.

It should fix the problem, but also the underlying uncleanliness should 
be fixed as well. We need an apic_none driver template with safe 
methods. Then all the scattered 'is the lapic enabled' open-coded checks 
of global flags can be removed.

	Ingo
--
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/