From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from edu-smtp-01.edutel.nl (edu-smtp-01.edutel.nl [88.159.1.175]) by ozlabs.org (Postfix) with ESMTP id 1B6ADB70A9 for ; Fri, 8 Oct 2010 01:22:19 +1100 (EST) Message-ID: <4CADD77A.90503@neli.hopto.org> Date: Thu, 07 Oct 2010 16:21:46 +0200 From: Micha Nelissen MIME-Version: 1.0 To: Bastiaan Nijkamp Subject: Re: Serial RapidIO Maintaintance read causes lock up References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Bastian, Bastiaan Nijkamp wrote: > It seems i forgot to include the relevant TLB entries in U-Boot and the > Device Tree in the e-mail, so here they are: > > The TLB entries in U-Boot: The kernel maintains the TLB, you must not set those in U-boot. It might cause conflicts when the kernel chooses its virtual memory space. You should only configure LAWs in U-boot as the kernel does not do that. That's the physical address you pass in the DTB (which seems to work, reading your kernel log). Do you access RapidIO space in U-boot also? Do you have a logic analyser, then you can see whether the read is actually coming out. Check whether the time-to-live, packet and link timeouts have been set to sane values to prevent deadlocks (especially time-to-live). At least then your kernel will crash instead of lock up. Micha