xen-bugs

[Top] [All Lists]

[Xen-bugs] [Bug 1227] Out of SW-IOMMU space, 3ware Raid controller/3w-xx

from [bugzilla-daemon]

[Permanent Link][Original]

To:	xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-bugs] [Bug 1227] Out of SW-IOMMU space, 3ware Raid controller/3w-xxxx module
From:	bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date:	Thu, 13 Oct 2011 08:45:16 -0700
Delivery-date:	Thu, 13 Oct 2011 08:45:25 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<bug-1227-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help:	<mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id:	Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post:	<mailto:xen-bugs@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to:	bugs@xxxxxxxxxxxxxxxxxx
Sender:	xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1227

fthain@xxxxxxxxxxxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |INVALID

------- Comment #12 from fthain@xxxxxxxxxxxxxxxxxxx  2011-10-13 08:45 -------
> > So.. why are you not using the default values (64MB)

I mistakenly wrote:

> Using the default value crashed out on the x3550 when aacraid died (out of
> SW-IOMMU space). The backtrace revealed that the problem was apparently DMA
> buffer shortage. (So I don't see why this bug report is marked
> "RESOLVED/INVALID".)

Sorry, I misremembered the sequence of events. I think wasn't using the default
at the time of the aacraid crash a year ago.

So to better answer your question, I wasn't using the default because back in
2007 when this system was running an OpenSUSE dom0 kernel, the swiotlb
parameter was required in order to make aacraid work at all. Everything has
been upgraded since but the kernel arguments were never revisited. The bug may
well be invalid. I need to do some more tests.

Regarding the 64 MB default, is that 512 x 128 K or 8192 x 8K? Is it equivalent
to swiotlb=nslabs=8192? And is that the same as swiotlb=8192?

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-bugs] [Bug 1227] Out of SW-IOMMU space, 3ware Raid controller/3w-xxxx module, bugzilla-daemon [Xen-bugs] [Bug 1227] Out of SW-IOMMU space, 3ware Raid controller/3w-xxxx module, bugzilla-daemon [Xen-bugs] [Bug 1227] Out of SW-IOMMU space, 3ware Raid controller/3w-xxxx module, bugzilla-daemon [Xen-bugs] [Bug 1227] Out of SW-IOMMU space, 3ware Raid controller/3w-xxxx module, bugzilla-daemon <=

Previous by Date:	[Xen-bugs] [Bug 1227] Out of SW-IOMMU space, 3ware Raid controller/3w-xxxx module, bugzilla-daemon
Next by Date:	[Xen-bugs] [Bug 1769] xl created hvm windows gets stuck after guest reboot, bugzilla-daemon
Previous by Thread:	[Xen-bugs] [Bug 1227] Out of SW-IOMMU space, 3ware Raid controller/3w-xxxx module, bugzilla-daemon
Indexes:	[Date] [Thread] [Top] [All Lists]