Re: Regression in 2.6.22, clock problems on Turion with 32-bit kernel

From: Tim Gardner
Date: Fri Aug 03 2007 - 10:57:00 EST


One other option that allows these systems to boot is 'acpi=off', though
that is hardly useful on a laptop.

rtg

Ben Collins wrote:
> Tim and I have both experienced this problem. With 2.6.20 things worked
> perfectly fine on these systems. The two machines are a Dell 1501 Turion
> X2 and Dell 1521 Turion X2.
>
> With 2.6.22 the kernel hangs shortly after starting up, but after
> several minutes, you can get activity by tapping keyboard (generating
> interrupts). We have NO_HZ and HIGH_RES enabled, but even disabling this
> doesn't help.
>
> I've tried every combination of boot param revolving around clocksource
> and interrupts. The only thing that gets me booting is nolapic, but then
> again, that knocks me down to a single cpu. Setting maxcpus=1 or nosmp
> doesn't fix it.
>
> We both bisected (separately I might add) down to this commit:
>
> commit e9e2cdb412412326c4827fc78ba27f410d837e6e
> Author: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
> Date: Fri Feb 16 01:28:04 2007 -0800
>
> [PATCH] clockevents: i386 drivers
>
> Add clockevent drivers for i386: lapic (local) and PIT/HPET (global). Update
> the timer IRQ to call into the PIT/HPET driver's event handler and the
> lapic-timer IRQ to call into the lapic clockevent driver. The assignement of
> timer functionality is delegated to the core framework code and replaces the
> compile and runtime evalution in do_timer_interrupt_hook()
>
> Use the clockevents broadcast support and implement the lapic_broadcast
> function for ACPI.
>
> No changes to existing functionality.
>
> Note, the problem doesn't happen when using an x86_64 kernel with the
> same basic config, on the same machine.
>
> Hoping to get some tips to test something a bit more specific in this
> patch.
>


--
Tim Gardner tim.gardner@xxxxxxxxxx
-
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/