imdave@cbnewsc.ATT.COM (david.e.bodenstab) (12/05/89)
Release 2.4 has fixed the initial system hang when a process gets a 80287 exception, but there are still problems. If I return from the signal catching function after a SIGFPE, the system still hangs. Does anyone know what is *actually* going on? I know (from experimenting under MSDOS after enabling the IRQ in the second 8259) that I must issue an `outb' to port 0f0 -- otherwise the system hangs at the next `wait'. I assume that the `outb' clears the 80287 busy signal. Also, one must clear the 80287 status word before reloading the 287 with the frestore. Now, if this is so, what is the problem with the uport kernel? Can anyone shed any light on what is missing from the uport kernel that prevents the 80287 from being used after an exception? Thanks. Dave Bodenstab (708)9798114 ...att!iwtmx!imdave