From: Ralf Baechle <ralf@oss.sgi.com>
To: clemej <clemej@mail.alum.rpi.edu>
Cc: linux-mips@oss.sgi.com
Subject: Re: Okay, lost
Date: Wed, 19 Jul 2000 16:08:13 +0200 [thread overview]
Message-ID: <20000719160813.A13006@bacchus.dhis.org> (raw)
In-Reply-To: <200007182323.AA145031220@mail.alum.rpi.edu>; from clemej@mail.alum.rpi.edu on Tue, Jul 18, 2000 at 11:23:22PM -0400
On Tue, Jul 18, 2000 at 11:23:22PM -0400, clemej wrote:
> When I was bitten by the infamous '-N' bug, it seems to me the
> exception I got said "UTLB" in it somewhere. This one doesn't.
> So maybe that's not the problem.
>
> And I think I might be being bitten by the same thing. All 2.4
> kernels I've tried die with what seems to be a similar error on
> my Indigo2 (R4400 200Mhz). I thought I read somewhere something
> about XZ graphics causing problems and boards should be
> removed... why? Could this be the cause? I have XZ in my
> machine.... I want to try a few more things before sounding too
> many alarms though...
The XZ graphics isn't supported nor do we properly detect and avoid it
which is why the kernel blows up on XZ. Now, Ulf had the same problem
and as he knows about this issue I guess there is a real problem
hidden behind that ...
Ralf
next prev parent reply other threads:[~2000-07-19 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-19 3:23 Okay, lost clemej
2000-07-19 3:23 ` clemej
2000-07-19 14:08 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-18 1:53 A. Wrasman
2000-07-18 3:23 ` Ralf Baechle
2000-07-18 22:27 ` Ulf Carlsson
[not found] ` <20000719140505.A12322@bacchus.dhis.org>
[not found] ` <20000719210555.A15023@enchanted.net>
[not found] ` <20000720141319.A26191@bacchus.dhis.org>
[not found] ` <20000722123548.A785@enchanted.net>
[not found] ` <20000723030324.A2710@bacchus.dhis.org>
2000-07-23 19:56 ` A. Wrasman
2000-07-18 4:00 ` Keith M Wesolowski
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=20000719160813.A13006@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=clemej@mail.alum.rpi.edu \
--cc=linux-mips@oss.sgi.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