From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756681AbZFSIB4 (ORCPT ); Fri, 19 Jun 2009 04:01:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754235AbZFSIBs (ORCPT ); Fri, 19 Jun 2009 04:01:48 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:47985 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752256AbZFSIBs (ORCPT ); Fri, 19 Jun 2009 04:01:48 -0400 Date: Fri, 19 Jun 2009 01:01:51 -0700 (PDT) Message-Id: <20090619.010151.83084255.davem@davemloft.net> To: mingo@elte.hu Cc: sam@ravnborg.org, akpm@linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: backtrace symbols are bolixed... From: David Miller In-Reply-To: <20090619073053.GA5445@elte.hu> References: <20090619.002101.45610359.davem@davemloft.net> <20090619073053.GA5445@elte.hu> X-Mailer: Mew version 6.2.51 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Ingo Molnar Date: Fri, 19 Jun 2009 09:30:53 +0200 > * David Miller wrote: > >> Sometime in the last day or so backtrace symbol printouts >> have become useless: >> >> [ 0.000000] WARNING: at mm/bootmem.c:535 __stop_notes+0xbb10/0x1d660() >> [ 0.000000] Modules linked in: >> [ 0.000000] Call Trace: >> [ 0.000000] [00000000008611b4] __stop_notes+0xbb10/0x1d660 >> [ 0.000000] [000000000086195c] __stop_notes+0xc2b8/0x1d660 >> [ 0.000000] [0000000000861a28] __stop_notes+0xc384/0x1d660 >> [ 0.000000] [0000000000858678] __stop_notes+0x2fd4/0x1d660 >> [ 0.000000] [000000000085684c] __stop_notes+0x11a8/0x1d660 >> [ 0.000000] [00000000006e8bdc] _etext+0xfffffffffffe59f4/0xe18 >> [ 0.000000] [0000000000000000] (null) >> >> I'll try to bisect but maybe someone can figure it out quickly >> meanwhile. > > I saw this too. One change that went upstream when i started seeing > these weird backtraces is: The patch from Mike Frysinger posted by Stephen Rothwell fixes it for me.