Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 8 Nov 2001 17:38:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 8 Nov 2001 17:38:12 -0500 Received: from cc1095243-a.thrp1.fl.home.com ([24.37.231.148]:23566 "EHLO Artifact") by vger.kernel.org with ESMTP id ; Thu, 8 Nov 2001 17:38:07 -0500 Message-ID: <006c01c168a6$1be38540$c800000a@Artifact> From: "Wilson" To: In-Reply-To: Subject: Re: Any lingering Athlon bugs in Kernel 2.4.14? Date: Thu, 8 Nov 2001 17:38:38 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org ----- Original Message ----- From: "Mark Hahn" To: "Wilson" Cc: Sent: Thursday, November 08, 2001 5:16 PM Subject: Re: Any lingering Athlon bugs in Kernel 2.4.14? > > Bugs in the Athlon optimizations present in the Linux kernel. > > what bugs would those be? if you're thinking of the infamous > "my athlon dies when I boot a CONFIG_MK7 kernel on a kt133", > it is by all accounts a *chipset* bug, not a kernel bug. > it's still unclear whether the voodoo workaround > (in both linux and ac) is doing something sensible. > Perhaps I should have said "Unfortunate interactions" rather than "bug." The bottom line is that some people have trouble running Linux with "Athlon" selected as the processor type. I was just trying to reassure the original poster that there wasn't anything wrong with the Athlon CPU itself. - 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/