If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

FYI - I tested the upstream kernels (latest and daily) and found the self-same problem. Additional research found one claim that the nohz=off kernel parameter fixes the problem. This was in fact the work-around - if not the fix.

I am not sure I missed this or you did not say: has a previous release worked without problems or was this a new install? The last comment was from May to just to verify: does it still exist? And finally would adding "acpi_skip_timer_override" to the kernel command line change this? Generally is IRQ0 when looking at /proc/interrupts incrementing or seems stuck?

On 07/14/2010 08:08 AM, Stefan Bader wrote:
> Hi John,
>
> I am not sure I missed this or you did not say: has a previous release
> worked without problems or was this a new install?

This was a new installation.

> The last comment was
> from May to just to verify: does it still exist? And finally would
> adding "acpi_skip_timer_override" to the kernel command line change
> this? Generally is IRQ0 when looking at /proc/interrupts incrementing or
> seems stuck?

Sort of good and bad. Good because this helps you around the problem. But bad because the underlying problem is something not really be solved generically in Linux. In short the BIOS should set up the timer interrupt and tells the OS via the timer override to which interrupt pin the timer interrupts get delivered. This is usually a "it is 2 instead of 0". But everything breaks if that is not true.
So this would be something to fix in BIOS or at least requires someone with insight into the hw specifications and that is not open. You may try to check whether there is a BIOS update for this netbook that helps, but otherwise this workaround is the only solution I know.