Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: ralf@uni-koblenz.de
Cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: One good and some bad news
Date: Tue, 14 Jul 1998 00:08:25 +0200	[thread overview]
Message-ID: <19980714000825.24064@alpha.franken.de> (raw)
In-Reply-To: <19980713023606.U10756@uni-koblenz.de>; from ralf@uni-koblenz.de on Mon, Jul 13, 1998 at 02:36:06AM +0200

On Mon, Jul 13, 1998 at 02:36:06AM +0200, ralf@uni-koblenz.de wrote:
> On Sun, Jul 12, 1998 at 11:53:19PM +0200, Thomas Bogendoerfer wrote:
> > good to know, as the address was really bogus. Is there a chance to
> > print out the faulting physical address for a bus error ? This would
> > give us some chances to find the real culprit. But it still hasn't happen
> > again.
> 
> Basically what to do would be to modify the kernel such that it will work
> with caches disabled.  Then you get (almost) precise exceptions again.
> Alternative and with less impact on the performance you could try to
> writeback the caches in strategic positions for debugging.  That makes a
> kind of a barrier for DBE exceptions.

ugly. I hope, that I won't need it.

> You patch looks good, could you commit it?  Thanks.

I do, when I've merged my stuff with the latest CVS commits. 

Thomas

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

  reply	other threads:[~1998-07-13 22:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-12  9:29 One good and some bad news Thomas Bogendoerfer
1998-07-12 17:01 ` ralf
1998-07-12 21:53   ` Thomas Bogendoerfer
1998-07-13  0:36     ` ralf
1998-07-13 22:08       ` Thomas Bogendoerfer [this message]
1998-07-12 18:55 ` Thomas Bogendoerfer

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=19980714000825.24064@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-mips@fnet.fr \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@uni-koblenz.de \
    /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