Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755517AbYARIuZ (ORCPT ); Fri, 18 Jan 2008 03:50:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752323AbYARIuN (ORCPT ); Fri, 18 Jan 2008 03:50:13 -0500 Received: from smtp2.linux-foundation.org ([207.189.120.14]:39219 "EHLO smtp2.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750950AbYARIuL (ORCPT ); Fri, 18 Jan 2008 03:50:11 -0500 Date: Fri, 18 Jan 2008 00:44:16 -0800 From: Andrew Morton To: Kamalesh Babulal Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, Andy Whitcroft , Balbir Singh Subject: Re: 2.6.24-rc8-mm1 Kernel oops will running kernbench Message-Id: <20080118004416.6a757169.akpm@linux-foundation.org> In-Reply-To: <479064F0.7040305@linux.vnet.ibm.com> References: <20080117023514.9df393cf.akpm@linux-foundation.org> <479064F0.7040305@linux.vnet.ibm.com> X-Mailer: Sylpheed 2.4.1 (GTK+ 2.8.17; x86_64-unknown-linux-gnu) 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 Content-Length: 1966 Lines: 40 On Fri, 18 Jan 2008 14:06:00 +0530 Kamalesh Babulal wrote: > Hi Andrew, > > Following oops was seen while running kernbench on one of test machine > (power4+ box). I tried reproducing the oops but was unsuccessful. > I will try to reproduce the oops with debug info compiled. > > > Oops: Kernel access of bad area, sig: 11 [#1] > SMP NR_CPUS=32 NUMA pSeries > Modules linked in: > NIP: 0000000000004570 LR: 000000000fc42dc0 CTR: 0000000000000000 > REGS: c00000077b6bf8c0 TRAP: 0300 Not tainted (2.6.24-rc8-mm1-autotest) > MSR: 8000000000001000 CR: 28022422 XER: 00000000 > DAR: c00000077b6bfce0, DSISR: 000000000a000000 > TASK = c000000773164c40[19588] 'as' THREAD: c00000077b6bc000 CPU: 1 > GPR00: 0000000000004000 c00000077b6bfb40 0000000000007346 000000000000d032 > GPR04: 000000000000043a 0000000000000000 000000000000000c 0000000000000004 > GPR08: 000000000fd278c8 0000000048022424 c00000077b6bfe30 0000998be2321500 > GPR12: 8000000000001030 c0000000005f6280 0000000010030000 0000000010030000 > GPR16: 0000000010030000 0000000010050000 000000001006aac0 0000000010053cd0 > GPR20: 0000000000000000 0000000000000fe0 0000000010050000 0000000010050000 > GPR24: 0000000000000ff8 0000000000000fe8 0000000000000062 000000000fd27490 > GPR28: 000000000fd274c8 0000000010099420 000000000fd25ff4 000000001009a400 > NIP [0000000000004570] 0x4570 > LR [000000000fc42dc0] 0xfc42dc0 > Call Trace: > [c00000077b6bfb40] [c00000077b292000] 0xc00000077b292000 (unreliable) > Instruction dump: > 48000000 XXXXXXXX XXXXXXXX XXXXXXXX 41820008 XXXXXXXX XXXXXXXX XXXXXXXX > 48000010 XXXXXXXX XXXXXXXX XXXXXXXX f92101a0 XXXXXXXX XXXXXXXX XXXXXXXX > odd. Where did the stack trace go? -- 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/