From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 16 Jan 2002 15:28:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 16 Jan 2002 15:28:38 -0500 Received: from zeus.kernel.org ([204.152.189.113]:38805 "EHLO zeus.kernel.org") by vger.kernel.org with ESMTP id ; Wed, 16 Jan 2002 15:28:28 -0500 Subject: Re: floating point exception From: Christian Thalinger To: Zwane Mwaikambo Cc: linux-kernel , "Richard B. Johnson" , davej@suse.de In-Reply-To: In-Reply-To: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.1 Date: 16 Jan 2002 21:26:42 +0100 Message-Id: <1011212807.507.3.camel@sector17.home.at> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2002-01-16 at 15:32, Zwane Mwaikambo wrote: > Can you also reproduce _without_ loading NVdriver, just to make everybody > happy. > > Thanks, > Zwane Mwaikambo > Sure, same breakdown. Maybe it's really an dual athlon xp issue as dave jones mentioned. But shouldn't this also occur when i trigger a floating point exception myself? Is there a way to check which floating point exception was raised by the seti client? Regards.