Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264734AbUFLMk2 (ORCPT ); Sat, 12 Jun 2004 08:40:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264737AbUFLMk2 (ORCPT ); Sat, 12 Jun 2004 08:40:28 -0400 Received: from nepa.nlc.no ([195.159.31.6]:62395 "HELO nepa.nlc.no") by vger.kernel.org with SMTP id S264734AbUFLMk1 (ORCPT ); Sat, 12 Jun 2004 08:40:27 -0400 Message-ID: <1191.83.109.11.80.1087044017.squirrel@nepa.nlc.no> Date: Sat, 12 Jun 2004 14:40:17 +0200 (CEST) Subject: Re: new kernel bug From: stian@nixia.no To: linux-kernel@vger.kernel.org Cc: "Manuel Arostegui Ramirez" User-Agent: SquirrelMail/1.4.0-1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 627 Lines: 17 You can keep an eye on the "timer + fpu stuff locks my console race" thread I orignaly created when I found the bug or see here for web version: http://marc.theaimsgroup.com/?l=linux-kernel&m=108704334308688&w=2 I'll put on a quick 2.4.26 fix that should work (can't test, since my linux box that I have physical access to isn't wired to the Internett currently) Stian Skjelstad - 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/