From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Arnaud B." Subject: Re: Possible kernel regression between 3.0.31-rt51 and 3.4.x on PPC64 ? Date: Fri, 20 Jul 2012 15:30:23 +0200 Message-ID: References: <4FFDBE71.2000705@am.sony.com> <4FFF3877.6080007@am.sony.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: "Rowand, Frank" , "linux-rt-users@vger.kernel.org" To: frank.rowand@am.sony.com Return-path: Received: from mail-wg0-f44.google.com ([74.125.82.44]:36551 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753394Ab2GTNaZ (ORCPT ); Fri, 20 Jul 2012 09:30:25 -0400 Received: by wgbdr13 with SMTP id dr13so3646747wgb.1 for ; Fri, 20 Jul 2012 06:30:23 -0700 (PDT) In-Reply-To: Sender: linux-rt-users-owner@vger.kernel.org List-ID: Hi All, I don't know if it's useful, or not, but it still fails if I boot using "nosmp", but it's ok if I built a kernel without CONFIG_SMP. It's also ok with CONFIG_SMP and CONFIG_PREEMPT_RTB. So it's something related to PPC64 + SMP + PREEMPT_RT_FULL /Arnaud. 2012/7/13 Arnaud B. : > Thanks anyway ;) > > I made another try : same test case fail on 3.2.22-rt35 > So the regression is between 3.0 and 3.2 ! > > Is there any ppc64 user here ? > > /Arnaud. > > 2012/7/12 Frank Rowand : >> On 07/12/12 06:11, Arnaud B. wrote: >>> Here are 2 crash logs. One is normal booting, the other is with >>> CONFIG_DEBUG_RT_MUTEXES choosen. >>> for sure w in rt_mutex_top_waiter, return by plist_first_entry is >>> corrupted. There is even ASCII in it from time to time :p >> >> < snip > >> >>> 2012/7/11 Frank Rowand : >>>> On 07/11/12 09:02, Arnaud B. wrote: >>>>> Hi all, >> >> < snip > >> >>>>> If you need an more information, I got all this boards in front of me :) >>>> >>>> Can you show a little bit more of the messages aound the crash? For example >>>> the register contents. Disassembly of the instruction at pc, and a few before >>>> that. >>>> >>>> -Frank >> >> Thanks for the extra info. >> >> I was looking at a plist corruption issue on a 2.6.29 rt kernel, but it does not >> look like your situation at all. So I don't have anything useful to contribute >> about your case. >> >> -Frank