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 12:08:31 +0200 [thread overview]
Message-ID: <20000406120830.A276@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:
> > scsi::resize_dma_pool: WARNING, dma_sectors=0, wanted=48, scaling
> > WARNING, not enough memory, pool not expanded
> > Unable to handle kernel paging request at virtual address 00000000, epc == 880cc668, ra == 880cc5d8
> > [...]
> ^^^^^
> What's here? Usually it tells the function where it crashes.
:) I dont have an System.map available - But i think i know the cause
of the crash - I think the arch/mips/arc/memory.c forgets to
allocate/not-free the memory the kernel - I dont think the ARC Prom is
able to mark the kernel memory different - But i cant see a location
where it explicitly reserves/allocates the kernel pages. Dec and ddb
to something like free_bootmem(bootmap,&_end,size-_end) - Nothing
like that in the arc things ... They free all memory segments
the ARC Prom gives back as "MEMTYPE_FREE" (arc_contigm, arc_freem)
and then it just takes the largest segment (there are 2 segments
- before and after the arc-prom segment) and installs the bootmem-map
in there. The next alloc and memset causes the crash as it allocates
from 88002000 which is the end of the mem map - My suspicion is (Which
ill try tonight) that the memory map with 2 pages is that small
that is just overwrites parts of the kernel with no effect - The next alloc
and memset is 4MB - This destroys the kernel completely and though causes
a crash.
> I see these panics sometimes as well. Where does the crash happen? Please
> lookup in System.map.
Ill do tonight
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."
next prev parent reply other threads:[~2000-04-06 10:45 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 [this message]
2000-04-06 21:05 ` Florian Lohoff
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=20000406120830.A276@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