From: Tom Rini <trini@kernel.crashing.org>
To: Dan Malek <dan@mvista.com>
Cc: Eli Chen <eli@routefree.com>,
brian.kuschak@skystream.com,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: dcache BUG()
Date: Mon, 7 May 2001 14:30:47 -0700 [thread overview]
Message-ID: <20010507143047.B1118@opus.bloom.county> (raw)
In-Reply-To: <3AF710DC.37209810@mvista.com>; from dan@mvista.com on Mon, May 07, 2001 at 05:17:16PM -0400
On Mon, May 07, 2001 at 05:17:16PM -0400, Dan Malek wrote:
> > ... This is really just a work around for us until we find out what
> > is the real problem.
>
> Is there some simple test I can use to trigger this problem? It
> would be nice if you could try a "newer" kernel from FSM Labs. This
> was originally in the linuxppc_2_5 tree, and we are merging/changing
> trees at the moment. I don't remember the URL......TOM, can you
> provide some insight?
Er, 2_5 isn't unavailable yet. bk://source.mvista.com/linuxppc_2_5 (mirror)
or bk://bitkeeper.fsmlabs.com:5005 (master). But 2_5 is 'dead' in the sense
that stuff is being moved to a new tree. The new tree should be a lot more
populated (with new 6xx/7xx/74xx, 8xx, 82xx and some 4xx) stuff after my
finals (And I've got 2 tomorrow, so adios. :))
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-05-07 21:30 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 19:04 dcache BUG() Eli Chen
2001-05-07 21:04 ` Dan Malek
2001-05-07 21:17 ` Dan Malek
2001-05-07 21:30 ` Tom Rini [this message]
2001-05-07 23:03 ` Dan Malek
2001-05-07 21:47 ` Eli Chen
2001-05-07 23:01 ` Dan Malek
2001-05-07 23:06 ` Gabriel Paubert
2001-05-07 23:15 ` Dan Malek
2001-05-07 23:28 ` Gabriel Paubert
2001-05-07 23:35 ` Eli Chen
2001-05-07 23:36 ` Dan Malek
2001-05-08 0:16 ` Eli Chen
2001-05-08 0:41 ` Dan Malek
2001-05-08 1:14 ` Eli Chen
2001-05-08 1:11 ` Dan Malek
2001-05-08 18:01 ` David Blythe
2001-05-08 20:27 ` Dan Malek
2001-05-08 21:34 ` David Blythe
2001-05-08 21:49 ` Dan Malek
2001-05-08 22:34 ` Ira Weiny
2001-05-08 22:53 ` Dan Malek
2001-05-08 1:37 ` Gabriel Paubert
2001-05-08 1:44 ` Dan Malek
2001-05-07 23:40 ` Gabriel Paubert
-- strict thread matches above, loose matches on Subject: below --
2001-05-12 0:44 Brian Kuschak
2001-05-12 0:57 ` Eli Chen
2001-05-14 9:28 ` Gabriel Paubert
2001-05-10 21:20 Brian Kuschak
2001-05-10 21:26 ` Dan Malek
2001-05-09 16:40 Brian Kuschak
2001-05-09 18:31 ` Dan Malek
2001-05-09 19:18 ` Gabriel Paubert
2001-05-10 18:39 ` Frank Rowand
2001-05-10 18:49 ` Gabriel Paubert
2001-05-10 19:10 ` Frank Rowand
2001-05-11 4:23 ` Paul Mielke
2001-05-11 10:09 ` Gabriel Paubert
2001-05-10 20:56 ` Dan Malek
2001-05-10 23:14 ` Cort Dougan
2001-05-11 11:01 ` Gabriel Paubert
2001-05-11 10:57 ` Gabriel Paubert
2001-05-11 18:49 ` Dan Malek
2001-05-08 17:43 Brian Kuschak
2001-05-09 11:06 ` Gabriel Paubert
2001-05-08 15:43 Brian Kuschak
2001-05-08 3:36 Brian Kuschak
2001-05-08 1:53 Brian Kuschak
2001-05-08 2:03 ` Dan Malek
2001-05-08 11:59 ` Gabriel Paubert
2001-05-08 0:40 Brian Kuschak
2001-05-07 23:01 Brian Kuschak
2001-05-07 22:19 Brian Kuschak
2001-05-07 22:35 ` Cort Dougan
2001-05-07 22:43 ` Eli Chen
2001-05-07 17:21 Brian Kuschak
2001-05-07 20:58 ` Dan Malek
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=20010507143047.B1118@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=brian.kuschak@skystream.com \
--cc=dan@mvista.com \
--cc=eli@routefree.com \
--cc=linuxppc-embedded@lists.linuxppc.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).