From: Florian Lohoff <flo@rfc822.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: cause of early indigo2 crash
Date: Thu, 6 Apr 2000 23:05:05 +0200 [thread overview]
Message-ID: <20000406230505.E13727@paradigm.rfc822.org> (raw)
In-Reply-To: <Pine.GSO.4.10.10004061050160.28032-100000@dandelion.sonytel.be>; from Geert Uytterhoeven on Thu, Apr 06, 2000 at 10:51:17AM +0200
On Thu, Apr 06, 2000 at 10:51:17AM +0200, Geert Uytterhoeven wrote:
> What's here? Usually it tells the function where it crashes.
>
> > Thats it - Might the first area be DMA bounce buffer only which have to
> > be initialized in the memory controller ?
>
> I see these panics sometimes as well. Where does the crash happen? Please
> lookup in System.map.
Its in drivers/scsi/scsi_dma.c
It happens due to no available scsi dma buffers which is caused by
the fact that MAX_DMA_ADDRESS is below the lowest free memory segment
(Kernel overlaps). If i increase the MAX_DMA_ADDRESS include/asm/dma.h.
As most of the drivers dont use the MAX_DMA_ADDRESS (zone allocator should
have made it obsolete) i suggest leaving it like it is and changing
arch/mips/mm/init.c to:
#if defined(CONFIG_ISA) || defined(CONFIG_PCI)
if (low < max_dma)
zones_size[ZONE_DMA] = low;
else {
zones_size[ZONE_DMA] = max_dma;
zones_size[ZONE_NORMAL] = low - max_dma;
}
#else
zones_size[ZONE_DMA] = low;
#endif
as the dma.h comment says that this only applies to standard PC
dma controllers.
If no one objects ill commit this.
Flo
--
Florian Lohoff flo@rfc822.org +49-subject-2-change
"Technology is a constant battle between manufacturers producing bigger and
more idiot-proof systems and nature producing bigger and better idiots."
prev parent reply other threads:[~2000-04-06 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-05 20:34 cause of early indigo2 crash Florian Lohoff
2000-04-06 8:51 ` Geert Uytterhoeven
2000-04-06 10:08 ` Florian Lohoff
2000-04-06 21:05 ` Florian Lohoff [this message]
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=20000406230505.E13727@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linux@cthulhu.engr.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