[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1001250831110.2906@localhost.localdomain>
Date: Mon, 25 Jan 2010 09:46:03 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: LKML <linux-kernel@...r.kernel.org>
cc: d.okias@...il.com, bugzilla-daemon@...zilla.kernel.org,
x86@...nel.org
Subject: Re: [Bug 15076] System panic under load with
clockevents_program_event
Switched to email. Please reply to all instead of using the bugzilla
interface.
> --- Comment #4 from okias <d.okias@...il.com> 2010-01-22 10:17:25 ---
> and it's regression. Now I work on 2.6.32.3 and no problem.
That's a really weird one. The system is 50 min up and running and out
of the blue it crashes in clockevents_program_event(). This function
has been called a couple of thousand times before that point.
The only way to crash there is when *dev is pointing into nirwana. dev
comes from
int tick_program_event(ktime_t expires, int force)
{
struct clock_event_device *dev = __get_cpu_var(tick_cpu_device).evtdev;
according to the callchain. At this point nothing fiddles with
tick_cpu_device.evtdev, so I suspect some really nasty memory
corruption going on.
okias, can you please disable highmem support and verify whether the
problem persists ?
Thanks,
tglx
--
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