From: Markus Schuster <ma.schuster@gmx.de>
To: xen-devel@lists.xensource.com
Subject: Re: Re: Massive problems with 'PCI-DMA: Out of SW-IOMMU space for XXX bytes [..]' with 3Ware controller
Date: Fri, 30 Nov 2007 17:39:54 +0100 [thread overview]
Message-ID: <fipeck$7vc$1@ger.gmane.org> (raw)
In-Reply-To: C36F97C0.10B66%Keir.Fraser@cl.cam.ac.uk
Hi,
I finally have results for you:
The one you already know:
64bit Xen 3.1.2
64bit 2.6.18
=> FAIL
Here my tested results:
32bit Xen 3.1.2 PAE
32bit 2.6.18 PAE
=> FAIL
64bit Xen 3.1.2
32bit 2.6.18 PAE
=> FAIL
32bit Xen 3.1.2 NON-PAE
32bit 2.6.16 NON-PAE
=> OK (I've written over 15GB to disk without problems)
I had to use a NON-PAE version of Xen for testing my old working 2.6.16
kernel, 'cause it doesn't have PAE enabled (I thought it would have, but
well..).
But all 3.1.2 Xen binaries have been built from the same source.
One interesting fact: The server mainboard has some onboard SATA ports. If I
connect a hard disc to this ports, I can write to them without problems.
Just in conjunction with the 3Ware I suffer from this problem.
The bug seems to be in the kernel part, not the hypervisor itself, as my old
kernel works without problems.
Regards,
Markus
next prev parent reply other threads:[~2007-11-30 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-25 16:03 Massive problems with 'PCI-DMA: Out of SW-IOMMU space for XXX bytes [..]' with 3Ware controller Markus Schuster
2007-11-25 16:59 ` Keir Fraser
2007-11-25 21:08 ` Markus Schuster
2007-11-25 21:21 ` Keir Fraser
2007-11-25 21:34 ` Markus Schuster
2007-11-30 16:39 ` Markus Schuster [this message]
2007-12-03 14:40 ` Christopher S. Aker
2007-11-26 16:12 ` Christopher S. Aker
-- strict thread matches above, loose matches on Subject: below --
2008-01-28 21:33 Markus Schuster
2008-01-28 21:58 ` Keir Fraser
2008-01-29 22:38 ` Markus Schuster
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='fipeck$7vc$1@ger.gmane.org' \
--to=ma.schuster@gmx.de \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.