From: Pete Popov <ppopov@mvista.com>
To: G H <giles67@yahoo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: do_ri failure in cache flushing routines
Date: Thu, 05 Aug 2004 15:31:33 -0700 [thread overview]
Message-ID: <4112B545.8090103@mvista.com> (raw)
In-Reply-To: <20040805201643.6422.qmail@web50806.mail.yahoo.com>
G H wrote:
> At the moment I don't have the board set up for using kgdb and it's
> complicated by the fact that we only have one serial console port. But
> I am looking into setting it up for kgdb now.
A single serial port will work fine.
>
> As far as stressing the system, it doesn't have enough resources (
> disk space ) to be able to compile the kernel, but we did write a
> simple program that would stress the system by spawning multiple
> threads, each one performing floating point calculations. With this
> test, top reported a load average of over 400 and we have
> seen no failure so far.
You can use an NFS mounted root fs to do native builds, assuming you
have a native toolchain. That's an excellent stress test.
Pete
>
> */Pete Popov <ppopov@mvista.com>/* wrote:
>
> G H wrote:
>
> > I've not had much response to this question so I would like to
> > rephrase it :
> >
> > Can anyone think of any possible scenario where do_ri could
> occur in
> > blast_icache32() ??
> >
> > Is this possibly a cache synchronisation problem ??
> >
>
> Could be a hardware memory glitch. I would use kgdb to put a
> breakpoint
> there and see what the data in memory looks like when this happens --
> look for memory corruption, etc.
>
> Pete
>
> > TIA
> >
> > >While testing out an amd au1500 based board I have been getting "
> > do_ri " exceptions >that always occur in the cache flushing
> routines.
> > More often than not in >blast_icache_32().
> >
> > >So far this has mainly happened after running the board for
> days on
> > end while running >multiple telnet sessions t! o it. It has
> sometimes (
> > quite rarely ) happened after a few >hours to a day of multiple
> telnet
> > session use.
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
> >
>
> ------------------------------------------------------------------------
> Do you Yahoo!?
> Yahoo! Mail Address AutoComplete
> <http://us.rd.yahoo.com/mail_us/taglines/aac/*http://promotions.yahoo.com/new_mail/static/ease.html>
> - You start. We finish.
next prev parent reply other threads:[~2004-08-05 22:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 18:04 do_ri failure in cache flushing routines G H
2004-08-05 18:09 ` Pete Popov
2004-08-05 18:13 ` Pete Popov
2004-08-05 20:16 ` G H
2004-08-05 22:31 ` Pete Popov [this message]
2004-08-05 18:11 ` Jun Sun
2004-08-05 20:25 ` G H
2004-08-05 20:25 ` G H
-- strict thread matches above, loose matches on Subject: below --
2004-08-03 16:19 G H
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=4112B545.8090103@mvista.com \
--to=ppopov@mvista.com \
--cc=giles67@yahoo.com \
--cc=linux-mips@linux-mips.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