Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756303Ab0A1XzK (ORCPT ); Thu, 28 Jan 2010 18:55:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755043Ab0A1XzJ (ORCPT ); Thu, 28 Jan 2010 18:55:09 -0500 Received: from fg-out-1718.google.com ([72.14.220.159]:60484 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753365Ab0A1XzH (ORCPT ); Thu, 28 Jan 2010 18:55:07 -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=BL9qlfiPK347oS+lbvuBUYnks1Ocys/Xszn+mw9MBa89Xd7CIX0gg6iIoAbn0ftE96 XffkyNGVdrnVIBEB5/RqCtupvlm/rpJlgyju5B5U9n1jG41C0xTDWxjLRyyq/tiB9neX CY5Lxfct99RjRA+04JAl4JzE/rYOKAeq8J8+k= MIME-Version: 1.0 In-Reply-To: References: <201001221017.o0MAHQmu015858@demeter.kernel.org> Date: Fri, 29 Jan 2010 00:55:05 +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: 2055 Lines: 64 I'm afraid it freezed even without HIGHMEM. I left computer run (compilation KDE 4.3.95) and when I come back, lcd was in dpms mode and led was blinking. So it look like same problem. Maybe without HIGHMEM it takes longer until problem appear. 2010/1/26, okias : > Lastest git without HIGHMEM look good. If no problems occur, then I > try use kernel with HIGHMEM and see what change... > > 2010/1/25, okias : >> 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 >> > > > -- > Jabber/XMPP: okias@isgeek.info > SIP VoIP: sip:17474537254@proxy01.sipphone.com > -- 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/