From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org
Subject: Re: [discuss] Re: x86_64: 2.6.14-rc4 swiotlb broken
Date: Mon, 17 Oct 2005 20:08:24 +0200
User-Agent: KMail/1.8
Cc: Ravikiran G Thirumalai <kiran@scalex86.org>,
       Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
       linux-kernel@vger.kernel.org, tglx@linutronix.de, shai@scalex86.org,
       clameter@engr.sgi.com
References: <20051017093654.GA7652@localhost.localdomain> <200510171740.57614.ak@suse.de> <20051017175231.GA4959@localhost.localdomain>
In-Reply-To: <20051017175231.GA4959@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200510172008.24669.ak@suse.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 859
Lines: 25

On Monday 17 October 2005 19:52, Ravikiran G Thirumalai wrote:

> No they are not.  IBM X460s are generally available machines and  the bug
> affects those boxes. 

No reports from that front so far.

> How can there be a major kernel release which is known 
> to have breakage??

Welcome to the painful real world of software engineering.

Every software has bugs and if you want to ever get a release out you
have to make such decisions sometimes. 

As an alternative I can just backout the patch that enables the Intel
SRAT code. That is probably better for a short term fix and will
not regress anybody.

-Andi
-
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/