Re: linux-next: Tree for June 13: IO APIC breakage on HP nx6325

From: Thomas Gleixner
Date: Wed Jun 18 2008 - 08:42:28 EST


On Wed, 18 Jun 2008, Thomas Gleixner wrote:
> On Wed, 18 Jun 2008, Rafael J. Wysocki wrote:
> > On Wednesday, 18 of June 2008, Rafael J. Wysocki wrote:
> > > On Tuesday, 17 of June 2008, Rafael J. Wysocki wrote:
> > > > On Tuesday, 17 of June 2008, Thomas Gleixner wrote:
> > > > > On Tue, 17 Jun 2008, Rafael J. Wysocki wrote:
> > > > > >
> > > > > > BTW, with the C1E patches reverted I don't get the
> > > > > > WARNING: at /home/rafael/src/linux-next/kernel/smp.c:215 smp_call_function_single+0x3d/0xa2
> > > > > > in the log. Thomas?
> > > > >
> > > > > Yeah, my bad. Fix below.
> > > >
> > > > Thanks, it eliminates the WARNING, but still the box doesn't work with
> > > > the "x86: add C1E aware idle function" patch applied, even with 'highres=off'.
> > > >
> > > > The main symptom is that CPU loads are computed incorrectly (I got X using 126%
> > > > of CPU time from 'top', for example). Apart from this, some processes (like
> > > > gkrellm) seem to be 'frozen' and only change their state in 'jumps', as though
> > > > they only got CPU from time to time at random.
> > > >
> > > > Reverting the above-mentioned patch fixes those problems.
> > >
> > > Ah. If your fix is replaced with the appended one, the system happily works
> > > with C1E and highres.
> >
> > Scratch that. The symptoms appeared later this time, that's all. I've just got
> > b43 consuming 90+ % of the CPU time. :-(
>
> I would have been pretty surprised if it had helped :)
>
> Does the box boot when you disable the local apic timer on the kernel
> command line with the patch applied ?
>
> Also does forcing hpet change anything ?

I just checked that the original c1e series and the affected code in
tip are not different. IIRC you confirmed that the C1E patches would
work on your box. So I wonder what else got changed which causes these
problems.

Thanks,
tglx
--
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/