search

byteduck / duckOS

An x86 monolithic kernel and operating system written in modern C++. Comes with in-house graphical applications and command line utilities, plus ports of existing software. And yes, it runs DOOM!
GNU General Public License v3.0
619 stars 25 forks source link

Bochs: MSDOS compatibility FPU exception #13

Open PF94 opened 2 years ago

PF94 commented 2 years ago 
00248059642i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00248059645i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00248059646i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00248059651i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00248059652i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00248059653i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00248059656i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00248059657i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00248059658i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00353638642i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00353638644i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00353638650i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00353638651i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00353638744i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00353638746i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00353638752i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00353638753i[CPU0  ] math_abort: MSDOS compatibility FPU exception
00369645001i[CPU0  ] math_abort: MSDOS compatibility FPU exception

This seems to occur everytime when Task manager warns with "Tried queuing blocked thread". I don't know if this is an issue or not considering it locks Pond up.

byteduck commented 2 years ago

Looks like that's due to the NE (fpu error reporting) flag in cr0 being set to 0, which bochs doesn't like. Maybe I should fix that :)