Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752269Ab0AYLdN (ORCPT ); Mon, 25 Jan 2010 06:33:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751872Ab0AYLdM (ORCPT ); Mon, 25 Jan 2010 06:33:12 -0500 Received: from fg-out-1718.google.com ([72.14.220.152]:59093 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751826Ab0AYLdL (ORCPT ); Mon, 25 Jan 2010 06:33:11 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=MbbTHngw7sWTTlocbRFZ+Eg1h7X0BEW/y2ztfCKliYmPNNJsmbiuVRPOfZjdJx5eCU 1nyHTmtUZTktfMbdWWOTa1YVJReoA87325O1HJy5BXRJ+104c3SByqjnrD6q7JeD5Nkh sYKiwSQNjLuPyNC90kRbnD9O5fsQ/qox8qFrg= MIME-Version: 1.0 In-Reply-To: References: <201001221017.o0MAHQmu015858@demeter.kernel.org> Date: Mon, 25 Jan 2010 12:33:09 +0100 Message-ID: Subject: Re: [Bug 15076] System panic under load with clockevents_program_event From: okias To: Thomas Gleixner Cc: LKML , bugzilla-daemon@bugzilla.kernel.org, x86@kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1349 Lines: 42 Okey, I try without highmem soon. 2010/1/25, Thomas Gleixner : > Switched to email. Please reply to all instead of using the bugzilla > interface. > >> --- Comment #4 from okias 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 > -- Jabber/XMPP: okias@isgeek.info SIP VoIP: sip:17474537254@proxy01.sipphone.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/