From: Juergen Braukmann <juergen.braukmann@ruhr-west.de>
To: Grant Grundler <grundler@dsl2.external.hp.com>
Cc: parisc list <parisc-linux@lists.parisc-linux.org>
Subject: [parisc-linux] Solved: C110, kernel Panics, still more tears ;-(
Date: Sun, 21 Jul 2002 11:42:33 +0200 [thread overview]
Message-ID: <3D3A8209.DCAC18F7@ruhr-west.de> (raw)
In-Reply-To: 20020720152919.9D690483D@dsl2.external.hp.com
Grant Grundler schrieb:
>
> Juergen Braukmann wrote:
> > Hi Grant and all,
> >
> > still more tears. I compiled and replaced the kernel, using 2.4.18pa55.
> > I used the setting of ccio_mem_ratio=16, but still my kernel panics with
> > Kernel panic: ccio-dma.c ccio_alloc_range() I/O MMU is out of mapping
> > resources.
> > In interrupt handler - not syncing
>
> Sorry - my bad - I think I have it backwards.
> Using a smaller value will result in more IOMMU resource.
>
> > would there be more chance with the ccio_mem_ratio setting of 8?
>
> Or 2 or 1 even.
I use a setting of 2 now and was able to ftp a good collection of
kernel.tar.gz files without crash. I hope this darn baby is *not*
playing tricks on me now, since I was once able to ftp a 200 MB file
without crash too. But all left to do is wait and watch and declare it
fixed for the time beeing.
>
> > there a way to use more than one Kernel alternativly and select it at
> > boottime with palo? Is there an example palo.conf somewhere?
>
> Yes. Interrupt the boot process before palo is loaded and then
> type "Y" to "Interact with IPL (Y/N/Q)?" question. You can then
> specify which vmlinux to boot.
>
yep. I started to use "easy" names (as you suggested). I had to try
that, since my default kernel had the setting of 16 and crashes saving a
3MB kernel...
Thanks to all involved to solve this problem.
Juergen
--
=========================================== __ _
Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __
Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ /
===========================================_\_v __/_/_//_/\_,_/ /_/\_\
next prev parent reply other threads:[~2002-07-21 10:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 16:08 [parisc-linux] C110, kernel Panics, still more tears ;-( Juergen Braukmann
2002-07-19 23:34 ` Ryan Bradetich
2002-07-20 9:53 ` Juergen Braukmann
2002-07-20 10:21 ` Peter Mottram
2002-07-20 15:40 ` Grant Grundler
2002-07-20 15:37 ` Grant Grundler
2002-07-20 22:54 ` Juergen Braukmann
2002-07-20 15:29 ` Grant Grundler
2002-07-20 22:57 ` Juergen Braukmann
2002-07-21 1:38 ` Grant Grundler
2002-07-21 9:42 ` Juergen Braukmann [this message]
2002-07-21 19:02 ` [parisc-linux] Solved: " Ryan Bradetich
2002-07-22 14:24 ` [parisc-linux] " Bjorn Helgaas
2002-07-22 15:29 ` Grant Grundler
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=3D3A8209.DCAC18F7@ruhr-west.de \
--to=juergen.braukmann@ruhr-west.de \
--cc=grundler@dsl2.external.hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
/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