Thread View: comp.sys.ibm.pc.rt
3 messages
3 total messages
Started by Douglas Allen Luce
Tue, 29 Sep 1992 02:43
Mouse Resolution Error
Author: Douglas Allen Luce
Date: Tue, 29 Sep 1992 02:43
Date: Tue, 29 Sep 1992 02:43
41 lines
2270 bytes
2270 bytes
Hello, I run AOS 4.3 on an APC, and for the most part it's been running well. I've got a 4-port Async card that has had 16550's shoved into the 8250 sockets, and am running modified asy drivers (by Tim Theisen, Peter Honeyman mainly) so as to keep my SLIP link running. I've been getting some odd crashes that I can't quite figure out: Here's a dump from /usr/adm/messages: Sep 28 08:15:13 telerama syslogd: restart Sep 28 08:15:13 telerama vmunix: msreset: couldn't set resolution Sep 28 08:15:13 telerama vmunix: asy0: input overrun Sep 28 08:15:13 telerama vmunix: trap: mcs_pcs=0x100<MACHINE-CHECK>, info=0x0, i ar=0xe0003e34, ics_cs=0xa870018<CHKSTOP-MASK,XLATE,STG-PROT> Sep 28 08:15:13 telerama vmunix: CSR=220000ff Sep 28 08:15:13 telerama vmunix: R0 ... R3 00000a87 1ffff4b8 00000000 00000010 Sep 28 08:15:13 telerama vmunix: R4 ... R7 00000019 1ffff508 e007d768 00400000 Sep 28 08:15:13 telerama vmunix: R8 ... Rb 00000000 0000001a 00000000 1ffff714 Sep 28 08:15:13 telerama vmunix: Rc ... Rf ff0049d8 e0003e18 e007d204 e001ee50 Sep 28 08:15:13 telerama vmunix: SER=1000<LOAD> SEAR=ff000000 TRAR=f40800 TCR=10 7f<TLIPT> HAT/IPT=7f Sep 28 08:15:13 telerama vmunix: panic: machine check Sep 28 08:15:13 telerama vmunix: asy0: input overrun Sep 28 08:15:13 telerama vmunix: syncing disks... 5 4 3 2 1 done I'm a bit baffled by this; from what I can tell, the CPU was pulling in stuff from an I/O section while this happened (asy0?), but it crashed. The tech docs say that there's supposed to be a bit set to prevent the cpu from dying when an I/O error occurs. This happens every couple of days or so. Currently, the SLIP link is at 19200. When I jack it up to 38400, I get similar machine checks every couple of hours (but no "mouse resolution" messages). Has anyone seen this before? Doug
Re: Mouse Resolution Error
Author: Steve Dyer
Date: Tue, 29 Sep 1992 17:45
Date: Tue, 29 Sep 1992 17:45
28 lines
1715 bytes
1715 bytes
In article <0elw=Nm00XQL8ycFls@andrew.cmu.edu> Douglas Allen Luce <dl2p+@andrew.cmu.edu> writes:
>I've got a 4-port Async card that has had 16550's shoved into the 8250
>sockets, and am running modified asy drivers (by Tim Theisen, Peter
>Honeyman mainly) so as to keep my SLIP link running. I've been getting
>some odd crashes that I can't quite figure out:
>
>Sep 28 08:15:13 telerama vmunix: panic: machine check
>
>I'm a bit baffled by this; from what I can tell, the CPU was pulling in
>stuff from an I/O section while this happened (asy0?), but it crashed.
>The tech docs say that there's supposed to be a bit set to prevent the
>cpu from dying when an I/O error occurs.
>
>Has anyone seen this before?
Do you have the "spurious machine check" patch to trap.c installed?
I don't have any of this available anymore, but Bill ____ (gad, I forget
his name, but he was one of the AOS RT gurus) who was then of IBM's Palo
Alto division simply put a case statement in the main switch statement of
trap() in trap.c which caused the case of a machine check or machine check
in user mode (when no additional bits were set in the machine check status
register).
My RT used to crash several times a day until this change was made.
--
Steve Dyer
dyer@ursa-major.spdcc.com aka {ima,harvard,rayssd,linus,m2c}!spdcc!dyer
Re: spurious machine check
Author: Steve Dyer
Date: Tue, 29 Sep 1992 18:17
Date: Tue, 29 Sep 1992 18:17
14 lines
913 bytes
913 bytes
Whoops, I exited from the editor too soon.
In article <1992Sep29.174559.28145@spdcc.com> dyer@spdcc.com (Steve Dyer) writes:
>...simply put a case statement in the main switch statement of
>trap() in trap.c which caused the case of a machine check or machine check
>in user mode (when no additional bits were set in the machine check status
>register)
to be ignored.
--
Steve Dyer
dyer@ursa-major.spdcc.com aka {ima,harvard,rayssd,linus,m2c}!spdcc!dyer
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads