From owner-freebsd-hackers Sat Jul 18 06:41:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20802 for freebsd-hackers-outgoing; Sat, 18 Jul 1998 06:41:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20797 for ; Sat, 18 Jul 1998 06:41:36 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id NAA29879 for ; Sat, 18 Jul 1998 13:41:23 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA11341; Sat, 18 Jul 1998 15:41:22 +0200 (MET DST) Message-ID: <19980718154122.53467@follo.net> Date: Sat, 18 Jul 1998 15:41:22 +0200 From: Eivind Eklund To: hackers@FreeBSD.ORG Subject: Weird bug strikes in _NPX_ when adding PnP support to i4b Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm slightly stuck here. I have done "draft code" (not nicely enough integrated, but should be correct) to add PnP support to i4b. This work fine for one card, but when I use two PnP cards, npx (of all weird things) crash here: * 16 works. */ printf("EE: npxprobe1 checks for exception 16\n"); control &= ~(1 << 2); /* enable divide by 0 trap */ fldcw(&control); npx_traps_while_probing = npx_intrs_while_probing = 0; printf("EE: npxprobe1 checks for divide by 0\n"); fp_divide_by_0(); if (npx_traps_while_probing != 0) { /* * Good, exception 16 works. */ printf("EE: exception 16 OK\n"); npx_ex16 = 1; The first two printfs get through, before the third the machine spontaneously reboot (and it sporadically reboot long before NPX, but I assume this is related to the same root cause). I don't have much of an i386-specific clue; I'd appreciate it if anybody have ideas of what could cause it. I'll probably track it down eventually, but would like to get it out of the world as fast as possible... Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message