Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ralf@uni-koblenz.de
To: karo@artcom.net, mike@mdhill.interlog.com
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Uploads ...
Date: Fri, 12 Dec 1997 02:42:09 +0100	[thread overview]
Message-ID: <19971212024209.20676@uni-koblenz.de> (raw)
In-Reply-To: <34906346.C1FB7311@artcom.net>; from Benjamin Pannier on Thu, Dec 11, 1997 at 11:03:50PM +0100

On Thu, Dec 11, 1997 at 11:03:50PM +0100, Benjamin Pannier wrote:

> tty01 at 0xbfbd9830 (irq = 21) is Zilog8530
> loop: registered device at major 7
> Got a bus error IRQ, shouldn't ...

Bad, the two register dumps you and Mike mailed don't make very much
sense; the epc register is pointer to completly different routines.
What both reports have in common is that the kernel dies after the
initialisation of the loop device.  The loop driver is actually
``harmless'' as it has no SGI specific code.  The next driver to
be initialized would be the SCSI driver, so the problem is there.
This and the useless epc values might indicate a problem with the
hpc dma.

I wonder if the DMA engine in the HPC might still be active?

I'm going to try to solve the problem by starring at the source.  If
this doesn't help, could you guys please run a special debug kernel
that I'll make for you?

  Ralf

  reply	other threads:[~1997-12-12  3:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-08 14:06 Uploads Ralf Baechle
1997-12-08 14:58 ` Uploads Alan Cox
1997-12-08 14:58   ` Uploads Alan Cox
1997-12-08 15:12   ` Uploads Ralf Baechle
1997-12-09  6:03 ` Uploads Alex deVries
1997-12-09  7:42   ` Uploads ralf
1997-12-10  0:34 ` Uploads Michael Hill
1997-12-10  3:02   ` Uploads ralf
1997-12-11 22:03     ` Uploads Benjamin Pannier
1997-12-12  1:42       ` ralf [this message]
     [not found]     ` <9712110612.ZM1219@mdhill.interlog.com>
1997-12-12  2:34       ` Indy crash during bootup ralf
1997-12-12  3:15         ` William J. Earl
1997-12-12  3:42           ` ralf
1997-12-12 10:04         ` Benjamin Pannier

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=19971212024209.20676@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=karo@artcom.net \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=mike@mdhill.interlog.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