From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30437 invoked by alias); 24 Oct 2007 20:46:23 -0000 Received: (qmail 30425 invoked by uid 22791); 24 Oct 2007 20:46:23 -0000 X-Spam-Check-By: sourceware.org Received: from nz-out-0506.google.com (HELO nz-out-0506.google.com) (64.233.162.225) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 24 Oct 2007 20:46:20 +0000 Received: by nz-out-0506.google.com with SMTP id x7so282212nzc for ; Wed, 24 Oct 2007 13:46:18 -0700 (PDT) Received: by 10.114.254.1 with SMTP id b1mr1118712wai.1193258777810; Wed, 24 Oct 2007 13:46:17 -0700 (PDT) Received: by 10.114.38.16 with HTTP; Wed, 24 Oct 2007 13:46:17 -0700 (PDT) Message-ID: Date: Wed, 24 Oct 2007 20:46:00 -0000 From: "Grant Likely" To: "Matt Mackall" Subject: Re: Apparent kernel bug with GDB on ppc405 Cc: linuxppc-embedded@ozlabs.org, gdb@sourceware.org In-Reply-To: <20071024204215.GC19691@waste.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071024194640.GB19691@waste.org> <20071024204215.GC19691@waste.org> X-Google-Sender-Auth: 2788f74eca3913df Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-10/txt/msg00210.txt.bz2 On 10/24/07, Matt Mackall wrote: > On Wed, Oct 24, 2007 at 02:28:14PM -0600, Grant Likely wrote: > > On 10/24/07, Matt Mackall wrote: > > > I'm trying to debug a trivial statically-linked hello world program on > > > a Xilinx PPC 405 and I'm seeing the following behavior: > > > > > > > > > > > Any suggestions? > > > > http://thread.gmane.org/gmane.linux.ports.ppc.embedded/11202 > > > > I was fighting with a similar problem almost 2 years ago. Looks like > > it might be related. At some point the problem seemed to go away and > > I determined what the root cause was. :-( > > > > I haven't been using gdb lately, so I don't know if it's the same > > problem. Nobody I had talked to had seen the issue on other 405 > > platforms. It could very well be something virtex-specific. > > Could be the same problem, but I'm seeing only your symptom 3 so far. > > I've tried throwing some larger hammers at the problem. Flushing all > of the dcache and icache (flush_dcache_all and > flush_instruction_cache) isn't helping. But printk(".") does! It's really true; printk *is* the most valuable tool kernel hackers have for debugging. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. grant.likely@secretlab.ca (403) 399-0195