Date: Tue, 14 Mar 2000 21:37:43 -0800 (PST) From: kfarmer@sympatico.ca To: freebsd-gnats-submit@FreeBSD.org Subject: kern/17385: Support for IIT's "XC87SLC-33" numeric processor broken in FreeBSD4.0 Message-ID: <200003150537.VAA69397@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 17385 >Category: kern >Synopsis: Support for IIT's "XC87SLC-33" numeric processor broken in FreeBSD4.0 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Mar 14 21:40:02 PST 2000 >Closed-Date: >Last-Modified: >Originator: Kelvin Farmer >Release: FreeBSD-4.0 >Organization: >Environment: affects FreeBSD-3.1 and later. >Description: kernel.GENERIC from FreeBSD 4.0 causes panic after line: npx0: Using INT 13 interface Fatal trap 12: page fault while in kernel mode supervisor read, page not present ... npx0 flags 0x08 doesn't help. 'disable npx0' in config> doesn't stop npx0 from being probed(?) either (like it has in earlier releases). >How-To-Repeat: attempt to boot FreeBSD 3.1 or greater on specific hardware. (486SLC2 CPU with IIT "XC87SLC-33" Numeric Processor) Note: same hardware runs FreeBSD-3.0, win95 with no problems. Same computer with IIT co-cpu physically removed runs FreeBSD-4.0 ok. >Fix: in FreeBSD3.x, disable npx0 in config screen. in FreeBSD4.0, it doesn't seem to be possible to disable npx0 when numeric processor is present, but "broken". If nothing else, add a comment to hardware.txt indicating that support for this math co-cpu is broken. - not that its likely that many of these machines are still around. =) >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003150537.VAA69397>