Date: Sun, 7 Dec 2008 11:35:12 +0000
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Giangiacomo Mariotti" <gg.mariotti@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM] Hw problem or software bug? DMA: Out of SW-IOMMU
 space....
Message-ID: <20081207113512.1e067257@lxorguk.ukuu.org.uk>
In-Reply-To: <12bfabe40812061948w4069e389ub90c4af86a493da6@mail.gmail.com>
References: <12bfabe40812061948w4069e389ub90c4af86a493da6@mail.gmail.com>
Organization: Red Hat UK Cyf., Amberley Place, 107-111 Peascod Street,
 Windsor, Berkshire, SL4 1TE, Y Deyrnas Gyfunol. Cofrestrwyd yng Nghymru a
 Lloegr o'r rhif cofrestru 3798903
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1073
Lines: 24

On Sun, 7 Dec 2008 04:48:45 +0100
"Giangiacomo Mariotti" <gg.mariotti@gmail.com> wrote:

> I'm running Linux 2.6.27.8.(PS. Today I've sent another e-mail about a
> problem with my new Intel I7 920, but it doesn't seem related except
> for the fact that with 2.6.26.8 neither of them seem to occur.)
> I just read this through dmesg :
> Dec  7 03:33:49 debian-hell kernel: [57102.830078] DMA: Out of
> SW-IOMMU space for 16384 bytes at device 0000:00:1f.2

Either you have something that uses a vast amount of I/O bounce buffer
space or something is leaking it. In the end someone leaked enough that
the disk driver couldn't allocate bounce buffers.

Rather than the gigantic hal dump can you provide an lspci and an lsmod
output. That will give some idea what devices are in use and may help
identify the potential cause.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/