From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sssup.it (ms01.sssup.it [193.205.80.99]) by ozlabs.org (Postfix) with ESMTP id 09597B7107 for ; Thu, 6 Jan 2011 06:22:15 +1100 (EST) Message-ID: <4D24C4E1.1030007@evidence.eu.com> Date: Wed, 05 Jan 2011 20:22:09 +0100 From: michael MIME-Version: 1.0 To: Wolfgang Denk Subject: Re: mpc880 linux-2.6.32 slow running processes References: <20110105183506.07BB815243A@gemini.denx.de> In-Reply-To: <20110105183506.07BB815243A@gemini.denx.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: Rafael Beims , linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi On 01/05/2011 07:35 PM, Wolfgang Denk wrote: > Dear Rafael Beims, > > In message you wrote: >> I'm working with an MPC880 board that is supposed to run linux-2.6.32. After >> some work, I could get the kernel up and running, mounting a rootfs via >> NFS. > 2.6.32 is pretty old. Is there any specific reason for not using a > recent kernel version? > I think that all the kernel version has the same problem >> The problem that I'm facing now is that when I try to run any process (may >> be an ls, cat, or whatever), the response of the process is *very* slow >> (something like 10 to 20 seconds for a ls). > This sounds as if only the output to the (serial ?) console port was > slow - typically this happens when there is a problem with interrupt > assignment, and you receive charatcers only after each of these times > out. > It is not a serial/console/interrupt problem >> My question to all is, did anyone see something like this already? Besides > We have seen this many times in the past, when interrupts were not > working correctly. I recommend to check youyr device tree settings > for these. > > [It would have helped if you had included a log of your kernel's boot > messages.] > >> that, what is the status of the linux kernel support for the 8xx platform? > It is working and actively maintained, but 8xx is a platform that is > more or less hopelessly obsoleted - nobody uses it in new designs any > more, so there is little work going on with it in recent kernel > versions (at least compared with other architectures). > agree, this architecture is basically dead >> Is it being actively tested / used today? I ask this because it seems that > Yes, it is. > >> all the information on the internet very aged (forum discussions from 2005 >> and below mostly). >> Is there something that I can do to try to narrow the cause of the problem? > Check your interrupts. > > Best regards, > > Wolfgang Denk > Michael Trimarchi