From: Pete Popov <ppopov@pacbell.net>
To: Matthew Dharm <mdharm@momenco.com>
Cc: linux-mips <linux-mips@oss.sgi.com>
Subject: RE: Help with OOPSes, anyone?
Date: 28 Jan 2002 15:54:47 -0800 [thread overview]
Message-ID: <1012262087.8518.174.camel@zeus> (raw)
In-Reply-To: <NEBBLJGMNKKEEMNLHGAIAEBJCFAA.mdharm@momenco.com>
On Mon, 2002-01-28 at 15:31, Matthew Dharm wrote:
> Well, here's the latest test results...
>
> The 2.4.0 kernel from MontaVista seems to work just fine. Of course,
> it doesn't have support for the full range of interrupts, but that's a
> separate matter. But it doesn't crash under big compiles.
2.4.0 from MontaVista? Do you mean the very first release, which was
2.4.0-test9?
> 2.4.17 with CONFIG_MIPS_UNCACHED crashes. It takes longer, but that
> may just be a function of it running so much slower. The BogoMIPS
> drops by a factor of 100. Ouch.
>
> So it doesn't look like a cache problem after all. And it does
> suggest that something introduced between 2.4.0 and .17 is what broke
> things. But what that is, I have no idea.
>
> I'm going to try Jason's modified cache code just in case, but I doubt
> that will change anything. We'll have to see, tho.
>
> Does anyone have any other suggestions to try? I'm starting to wonder
> if perhaps the PROM isn't setting up the SDRAM properly, but that
> conflicts with the working 2.4.0 kernel -- the PROM is the same in
> both cases, so I would expect a PROM error to affect both versions.
>
> I'm running out of ideas here... anyone?
If you're absolutely sure 2.4.0-test9 doesn't crash (you ran the test
"enough" times), perhaps you can start testing kernels between 2.4.0 and
2.4.17. And, you did get rid of the 'wait' instruction in 2.4.17,
right ;-)?
Pete
next prev parent reply other threads:[~2002-01-29 0:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-27 8:22 Help with OOPSes, anyone? Matthew Dharm
2002-01-27 10:53 ` Jason Gunthorpe
2002-01-27 22:26 ` Matthew Dharm
2002-01-28 2:39 ` Jason Gunthorpe
2002-01-28 23:31 ` Matthew Dharm
2002-01-28 23:31 ` Matthew Dharm
2002-01-28 23:50 ` Matthew Dharm
2002-01-28 23:50 ` Matthew Dharm
2002-01-28 23:54 ` Pete Popov [this message]
2002-01-29 0:09 ` Matthew Dharm
2002-01-29 0:22 ` Pete Popov
2002-01-29 2:03 ` Matthew Dharm
2002-01-29 2:29 ` Pete Popov
2002-01-29 6:18 ` Matthew Dharm
2002-01-29 16:47 ` Pete Popov
2002-01-27 17:33 ` Pete Popov
2002-01-27 22:24 ` Matthew Dharm
-- strict thread matches above, loose matches on Subject: below --
2002-01-29 18:27 Manoj Ekbote
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=1012262087.8518.174.camel@zeus \
--to=ppopov@pacbell.net \
--cc=linux-mips@oss.sgi.com \
--cc=mdharm@momenco.com \
/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