Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Joel Soete <soete.joel@tiscali.be>
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: 2.6.... b2k panic with raid1 :-( (I/O MMU ... out of mapping ressources)
Date: Thu, 20 Jan 2005 23:08:56 -0700	[thread overview]
Message-ID: <20050121060856.GJ6582@colo.lackof.org> (raw)
In-Reply-To: <41DE61B800004297@mail-8-bnl.mail.tiscali.sys>

On Thu, Jan 20, 2005 at 11:51:00AM +0100, Joel Soete wrote:
> Hello all,
> 
> Since this morning I mirrored my disks (1 9Gb on 1 36Gb) but as soon as I
> try to 'apt-get update' the system now panic:
> 
> Kernel panic - not syncing: /CAD/linux-2.6.11-rc1-pa3/drivers/parisc/sba_iommu.c:
> I/O MMU @ fed20000 is out of mapping resources

Yes - this has been the expected behavior since ~1999.

The basic problem can be addressed by modifying the drivers that use DMA
services to also check dma_mapping_error() (or pci_dma_mapping_error()
if one prefers). I'll need to add some code to
include/asm-parisc/dma-mapping.h to provide support for failed mappings
before I can remove the panic. This won't happen soon unfortunately.

> I just find a work around: mark a slice failed (mdadm --fail /dev/sda10)
> and I can now doing my 'apt-get update'

Good idea - that just cut in half the number of mappings needed.

thanks for the report and feel free to remind in a few weeks about
this again.

grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

      reply	other threads:[~2005-01-21  6:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20 10:51 [parisc-linux] 2.6.... b2k panic with raid1 :-( (I/O MMU ... out of mapping ressources) Joel Soete
2005-01-21  6:08 ` Grant Grundler [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=20050121060856.GJ6582@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=soete.joel@tiscali.be \
    /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