Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755031AbYHYAT4 (ORCPT ); Sun, 24 Aug 2008 20:19:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752992AbYHYATt (ORCPT ); Sun, 24 Aug 2008 20:19:49 -0400 Received: from khc.piap.pl ([195.187.100.11]:39061 "EHLO khc.piap.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752433AbYHYATs (ORCPT ); Sun, 24 Aug 2008 20:19:48 -0400 To: Jari Aalto Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.25 DMA: Out of SW-IOMMU space - Asus M2N32 AMD 8GB memory References: <48B1D82C.5000107@shaw.ca> <87d4jyys7y.fsf@jondo.cante.net> From: Krzysztof Halasa Date: Mon, 25 Aug 2008 02:19:46 +0200 In-Reply-To: <87d4jyys7y.fsf@jondo.cante.net> (Jari Aalto's message of "Mon\, 25 Aug 2008 01\:16\:01 +0300") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 901 Lines: 23 Jari Aalto writes: > What, if after booting to 2.6.26 and without any 'iommu' boot parameters, > there still appears "Out of Iommu space" messages? What kind of logs > should I post? You shouldn't be getting "Out of SW-IOMMU space" messages when not using SW-IOMMU. > I'm a bit nervous due to past experience of complete hardd disk > corruption. But if that was problem with the old kernel and more later > versions are safer in this repect, I could once more. I'm not sure if the newer versions are safer. It may be a hardware/BIOS problem and it may happen again. Make sure you have a usable backup first. -- Krzysztof Halasa -- 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/