linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sam Song <samlinuxppc@yahoo.com.cn>
To: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: System hanged, which one is the killer? [was Re: What's the problem could be?]
Date: Tue, 14 Dec 2004 09:51:24 +0800 (CST)	[thread overview]
Message-ID: <20041214015124.55109.qmail@web15810.mail.cnb.yahoo.com> (raw)
In-Reply-To: <20041207113615.9141.qmail@web15805.mail.cnb.yahoo.com>

Sam Song <samlinuxppc@yahoo.com.cn> wrote:
> Hi, all
> 
> An system application crash running on 2.4.18 was
> happened on my custom 8xx board every now and then,
> especially recently. Yeah, the probelm is becoming
> more and more obvious. Personally, I deem it as an
> default of application software because there are
> some complicated application softwares like GUI and
a
> browser. But I also suspect that my custom keyboard
> did it because there were about 70-80 PCMCIA
> interrupts created once I hit just one key. I used
> PCMCIA interrupt to accept the rubber keyboard
> input.

Well, after some test on keyboard drivers, I found
that neither USB HOST keyboard nor my PCMCIA keyboard
could lead to system hang. It seems that the killer
isn't the PCMCIA keyboard driver.
 
> Any other possibility?

Seems have. The interesting thing was that I could
quit from the hanged application with a special key
and restarted the application and continued operate.
I, however, noticed some errors hints printed on the
LCD panel as "No enough video memory" during the
break.

So my attention was drawn to the 823 LCD driver. Two
different 10.4" SHARP TFT LCD panel with 640*480 and
800*600 were tested on the same target. I found that
640*480 system was more robust than 800*600 one. There
were also some hang happened with some disorder input
on 640*480 but the system could recover to normal
after some time like 3-5 mintues. The recoverable
result never appeared on 800*600.

Here I'd like to make sure one thing that whether I
could extend the video memory to meet the application
need. There are a lot of RAM on my target, at least
64MB. Any suggestion?

Thanks in advance,

=====
Best regards,

Sam

_________________________________________________________
Do You Yahoo!?
150万曲MP3疯狂搜,带您闯入音乐殿堂
http://music.yisou.com/
美女明星应有尽有,搜遍美图、艳图和酷图
http://image.yisou.com
1G就是1000兆,雅虎电邮自助扩容!
http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_1g/

  reply	other threads:[~2004-12-14  1:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-07 11:36 What's the problem could be? Sam Song
2004-12-14  1:51 ` Sam Song [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-14  2:04 System hanged, which one is the killer? [was Re: What's the problem could be?] Sam Song
2004-12-14  2:04 Sam Song

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=20041214015124.55109.qmail@web15810.mail.cnb.yahoo.com \
    --to=samlinuxppc@yahoo.com.cn \
    --cc=linuxppc-embedded@ozlabs.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).