Em Wed, 3 Sep 2008 19:05:39 +0200 (CEST) Thomas Gleixner escreveu: | On Wed, 3 Sep 2008, Dmitry Nezhevenko wrote: | > On Wed, Sep 03, 2008 at 05:15:40PM +0200, Thomas Gleixner wrote: | > > On Wed, 3 Sep 2008, Thomas Gleixner wrote: | > > > Dont think so. Your dmesg outputs do not show any sign of that | > > > disease. | > > > | > > > Can you try the patch below please ? | > | > I'm not original problem reporter. However I'm experiencing possible same | > problem with MSI M673 laptop. Here is link to bugzilla report (with | > dmesgs and other info): | > http://bugzilla.kernel.org/show_bug.cgi?id=11101 | > | > 2.6.27-rc4 on this machine freezes with exactly same messages: | > | > hpet0: at MMIO 0xfed00000, IRQ 2, 8, 31 | > hpet0: 3 32-bit timers, 25000000 Hz | > ACPI: RTC can wake from S4 | > | > This patch do not help me | > | > > @@ -228,6 +228,8 @@ static void tick_do_broadcast_on_off(voi | > > if (!tick_device_is_functional(dev)) | > > goto out; | > > | > > + bc_stoppped = cpus_empty(tick_broadcast_mask); | > | > btw little type here, should be "bc_stopped" | | Yeah, noticed already. Sorry. | | Find a debug patch below, which looks at the two functions which might | loop forver under certain conditions. Does one of the checks hit ? I can actually boot with this patch. Was this intended? As the dmesg has various WARN_ON() outputs I'm attaching it, this is the first one: """ PCI: Using ACPI for IRQ routing DMAR:parse DMAR table failure. hpet0: at MMIO 0xfed00000, IRQs 2, 8, 31 hpet0: 3 32-bit timers, 25000000 Hz Switched to high resolution mode on CPU 0 tick_broadcast_set_event is stuck f09fa64 f0a01e4 ------------[ cut here ]------------ WARNING: at kernel/time/tick-broadcast.c:383 tick_broadcast_set_event+0x97/0xc0() Modules linked in: Pid: 0, comm: swapper Not tainted 2.6.27-rc5-test9 #69 Call Trace: [] warn_on_slowpath+0x5f/0x90 [] ? printk+0x67/0x70 [] ? getnstimeofday+0x49/0xc0 [] ? ktime_get_ts+0x59/0x60 [] tick_broadcast_set_event+0x97/0xc0 [] tick_broadcast_oneshot_control+0x11a/0x130 [] tick_notify+0x2f5/0x420 [] notifier_call_chain+0x3f/0x80 [] raw_notifier_call_chain+0x11/0x20 [] clockevents_notify+0x2b/0x90 [] c1e_idle+0x85/0x130 [] ? atomic_notifier_call_chain+0x11/0x20 [] cpu_idle+0x72/0x100 [] start_secondary+0x151/0x1ab ---[ end trace 4eaa2a86a8e2da22 ]--- Switched to high resolution mode on CPU 1 """ -- Luiz Fernando N. Capitulino