[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070131232130.GC4137@inferi.kami.home>
Date: Thu, 1 Feb 2007 00:21:30 +0100
From: Mattia Dongili <malattia@...ux.it>
To: Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
mingo@...hat.com, tglx@...utronix.de
Subject: Re: 2.6.20-rc6-mm3
On Wed, Jan 31, 2007 at 10:52:41PM +0100, Mattia Dongili wrote:
> On Mon, Jan 29, 2007 at 08:45:28PM -0800, Andrew Morton wrote:
> >
> > Temporarily at
> >
> > http://userweb.kernel.org/~akpm/2.6.20-rc6-mm3/
> >
> > Will appear later at
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc6/2.6.20-rc6-mm3/
>
> I jumped from rc2-mm1 to rc6-mm3 and tried dynticks for the first time:
>
> ...
> Time: acpi_pm clocksource has been installed.
> Clocksource tsc unstable (delta = -275154141 ns)
> BUG: soft lockup detected on CPU#1!
> [<c0104dac>] show_trace_log_lvl+0x1a/0x2f
> [<c010540b>] show_trace+0x12/0x14
> [<c010548f>] dump_stack+0x16/0x18
> [<c0146e50>] softlockup_tick+0xa7/0xb6
> [<c01286c0>] run_local_timers+0x12/0x14
> [<c0128a61>] update_process_times+0x3e/0x63
> [<c01374c5>] tick_nohz_handler+0x7d/0xe3
> [<c01137c2>] smp_apic_timer_interrupt+0x71/0x83
> [<c01048f4>] apic_timer_interrupt+0x28/0x30
> [<c013709e>] tick_broadcast_oneshot_control+0x12/0xc8
> [<c0136a58>] tick_notify+0x1cd/0x241
> [<c012bd4e>] notifier_call_chain+0x2b/0x55
> [<c012bde2>] __raw_notifier_call_chain+0x19/0x1e
> [<c012be01>] raw_notifier_call_chain+0x1a/0x1c
> [<c01364ea>] clockevents_do_notify+0x11/0x13
> [<c013672d>] clockevents_notify+0x1c/0x53
> [<f8f7b5cb>] acpi_state_timer_broadcast+0x2e/0x31 [processor]
> [<f8f7c12f>] acpi_processor_idle+0x276/0x40b [processor]
> [<c0102435>] cpu_idle+0xad/0xd3
> [<c0112975>] start_secondary+0x32b/0x333
> [<00000000>] run_init_process+0x3fefed10/0x19
> =======================
>
> Full dmesg and config:
> http://oioio.altervista.org/linux/nohz_soft-lockup.dmesg
> http://oioio.altervista.org/linux/config-2.6.20-rc6-mm3-1
>
> As a side note the process becomes slower and slower as it proceeds,
> it's definitely noticeable during my iptables rules setup (nothing that
> complex, just default policies and subnet/lan accept rules).
> Building with NO_HZ=n right now.
yes, slowness is gone. Any useful information I can provide?
--
mattia
:wq!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists