From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Juergen Braukmann <juergen.braukmann@ruhr-west.de>
Cc: parisc list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] C110, kernel Panics, still more tears ;-(
Date: Sat, 20 Jul 2002 09:29:19 -0600 [thread overview]
Message-ID: <20020720152919.9D690483D@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Juergen Braukmann <juergen.braukmann@ruhr-west.de> of "Fri, 19 Jul 2002 18:08:09 +0200." <3D383969.1657EF43@ruhr-west.de>
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.
> 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.
grant
next prev parent reply other threads:[~2002-07-20 15:29 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 [this message]
2002-07-20 22:57 ` Juergen Braukmann
2002-07-21 1:38 ` Grant Grundler
2002-07-21 9:42 ` [parisc-linux] Solved: " Juergen Braukmann
2002-07-21 19:02 ` 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=20020720152919.9D690483D@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=juergen.braukmann@ruhr-west.de \
--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