From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by ozlabs.org (Postfix) with ESMTP id 4143AB70E7 for ; Wed, 3 Nov 2010 23:49:43 +1100 (EST) To: divya Subject: Re: Oops while running systemtap on the p6 machine against the kernel version 2.6.36-rc7-git3 References: <4CB704AC.4070203@linux.vnet.ibm.com> From: fche@redhat.com (Frank Ch. Eigler) Date: Wed, 03 Nov 2010 08:49:39 -0400 In-Reply-To: <4CB704AC.4070203@linux.vnet.ibm.com> (dipraksh@linux.vnet.ibm.com's message of "Thu, 14 Oct 2010 18:55:00 +0530") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linuxppc-dev@ozlabs.org, systemtap@sources.redhat.com List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , divya writes: > While running systemtap tests on the p6 machine , against the kernel version 2.6.36-rc7-git3 > Oops occured , here are the call trace > > BUG: spinlock bad magic on CPU#6, stapio/20398 > -- 0:conmux-control -- time-stamp -- Oct/13/10 2:49:18 --res > lock: c000000000fcfa18, .magic: 00000000, .owner:/-1, .owner_cpu: 0 > [...] jistone committed some timing-related changes last night. Would you mind trying a new build on your ppc box? It seems as through there is a concurrency problem with the timer shutdown process. If the problem still occurs, we might need to instrument that part of the kernel and/or runtime code to figure it out. - FChE