Searched hist:"8 e929d6553a758fdaa96adfbaa1928c3850028a2" (Results 1 – 2 of 2) sorted by relevance
/freebsd/sys/amd64/amd64/ |
H A D | vm_machdep.c | diff 8e929d6553a758fdaa96adfbaa1928c3850028a2 Sat May 16 16:44:11 CEST 1998 KATO Takenori <kato@FreeBSD.org> Some of newer PC-98 may cause "Windows Protection Fault" when booting Windows 95 after rebooting FreeBSD without power off. In PC-98 system, reboot mode is set via I/O port 0x37 in cpu_reset(), and accessing of this port is the reason of the problem. To avnoid the fault, current status of reboot mode should be checked before accessing the I/O port. diff 8e929d6553a758fdaa96adfbaa1928c3850028a2 Sat May 16 16:44:11 CEST 1998 KATO Takenori <kato@FreeBSD.org> Some of newer PC-98 may cause "Windows Protection Fault" when booting Windows 95 after rebooting FreeBSD without power off. In PC-98 system, reboot mode is set via I/O port 0x37 in cpu_reset(), and accessing of this port is the reason of the problem. To avnoid the fault, current status of reboot mode should be checked before accessing the I/O port.
|
/freebsd/sys/i386/i386/ |
H A D | vm_machdep.c | diff 8e929d6553a758fdaa96adfbaa1928c3850028a2 Sat May 16 16:44:11 CEST 1998 KATO Takenori <kato@FreeBSD.org> Some of newer PC-98 may cause "Windows Protection Fault" when booting Windows 95 after rebooting FreeBSD without power off. In PC-98 system, reboot mode is set via I/O port 0x37 in cpu_reset(), and accessing of this port is the reason of the problem. To avnoid the fault, current status of reboot mode should be checked before accessing the I/O port. diff 8e929d6553a758fdaa96adfbaa1928c3850028a2 Sat May 16 16:44:11 CEST 1998 KATO Takenori <kato@FreeBSD.org> Some of newer PC-98 may cause "Windows Protection Fault" when booting Windows 95 after rebooting FreeBSD without power off. In PC-98 system, reboot mode is set via I/O port 0x37 in cpu_reset(), and accessing of this port is the reason of the problem. To avnoid the fault, current status of reboot mode should be checked before accessing the I/O port.
|