From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755508AbYIDX3O (ORCPT ); Thu, 4 Sep 2008 19:29:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752316AbYIDX24 (ORCPT ); Thu, 4 Sep 2008 19:28:56 -0400 Received: from www.tglx.de ([62.245.132.106]:35509 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750844AbYIDX2z (ORCPT ); Thu, 4 Sep 2008 19:28:55 -0400 Date: Fri, 5 Sep 2008 01:27:06 +0200 (CEST) From: Thomas Gleixner To: Andrew Morton cc: torvalds@linux-foundation.org, sfr@canb.auug.org.au, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, yhlu.kernel@gmail.com, ink@jurassic.park.msu.ru, jbarnes@virtuousgeek.org, netdev@vger.kernel.org, viro@zeniv.linux.org.uk, ebiederm@xmission.com, dwmw2@infradead.org, sam@ravnborg.org, johnstul@us.ibm.com Subject: Re: linux-next: Tree for September 3 In-Reply-To: <20080904161746.dc4800a4.akpm@linux-foundation.org> Message-ID: References: <20080903191619.6b6b230e.sfr@canb.auug.org.au> <20080903214634.ea17ff53.akpm@linux-foundation.org> <20080903223318.84b6ce8b.akpm@linux-foundation.org> <20080904012544.cabed847.akpm@linux-foundation.org> <20080904015701.5959623a.akpm@linux-foundation.org> <20080904104554.32ffebea.akpm@linux-foundation.org> <20080904113408.d47c65f6.akpm@linux-foundation.org> <20080904161746.dc4800a4.akpm@linux-foundation.org> User-Agent: Alpine 1.10 (LFD 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 4 Sep 2008, Andrew Morton wrote: > > > > Cute, NULL pointer in the timer check code. Can you please addr2line > > the exact code line or upload the vmlinux somewhere ? > > > > erm, I might have lost that binary, and it only happened the once. It > happened shortly after the machine had fully booted, during > establishment of the first sshd session. > > It nuked the machine really well, too. I had to pull the battery to > get it back. Known problem on Sonys. :( > fwiw: > > (gdb) l *0xc0126e7f > 0xc0126e7f is in get_next_timer_interrupt (kernel/timer.c:863). > warning: Source file is more recent than executable. > 858 for (array = 0; array < 4; array++) { > 859 struct tvec *varp = varray[array]; > 860 > 861 index = slot = timer_jiffies & TVN_MASK; > 862 do { > 863 list_for_each_entry(nte, varp->vec + slot, entry) { > 864 found = 1; > 865 if (time_before(nte->expires, expires)) > 866 expires = nte->expires; > 867 } > > which looks reasonable. Yeah, as Linus decoded it's that loop. So we look at some corrupted entry here. CONFIG_DEBUG_OBJECTS (add debug_objects to the command line as well) should catch it when this is a timer being discarded, freed or reinitialized. Otherwise, when it is just random corruption it wont help much. Thanks, tglx