From: michael <michael@evidence.eu.com>
To: Wolfgang Denk <wd@denx.de>
Cc: Rafael Beims <rbeims@gmail.com>, linuxppc-dev@ozlabs.org
Subject: Re: mpc880 linux-2.6.32 slow running processes
Date: Wed, 05 Jan 2011 20:22:09 +0100 [thread overview]
Message-ID: <4D24C4E1.1030007@evidence.eu.com> (raw)
In-Reply-To: <20110105183506.07BB815243A@gemini.denx.de>
Hi
On 01/05/2011 07:35 PM, Wolfgang Denk wrote:
> Dear Rafael Beims,
>
> In message<AANLkTin5XTnDEu1BJUOeF0UWtfEpotW5Bq__i8g6U05h@mail.gmail.com> 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
prev parent reply other threads:[~2011-01-05 19:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 18:09 mpc880 linux-2.6.32 slow running processes Rafael Beims
2011-01-05 18:23 ` michael
[not found] ` <AANLkTi=uvunJ-ZFVGHZZExgBaNL9Sh0uZ3OiiCrcPnx=@mail.gmail.com>
2011-01-05 18:45 ` Fwd: " Rafael Beims
2011-01-05 19:13 ` michael
2011-01-05 23:42 ` Scott Wood
2011-01-06 12:52 ` michael
2011-01-06 16:52 ` Joakim Tjernlund
2011-01-07 10:00 ` Rafael Beims
2011-01-08 21:43 ` Joakim Tjernlund
2011-01-10 16:35 ` Rafael Beims
2011-01-10 16:55 ` Joakim Tjernlund
2011-01-11 16:00 ` Joakim Tjernlund
2011-01-21 6:53 ` Heiko Schocher
2011-01-22 9:50 ` Joakim Tjernlund
2011-01-05 18:35 ` Wolfgang Denk
2011-01-05 18:50 ` Rafael Beims
2011-01-05 19:22 ` michael [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D24C4E1.1030007@evidence.eu.com \
--to=michael@evidence.eu.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=rbeims@gmail.com \
--cc=wd@denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.