Date: Fri, 14 Apr 1995 10:06:05 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: wilko@yedi.iaf.nl (Wilko Bulte) Cc: FreeBSD-hackers@FreeBSD.org Subject: Re: NMI/parity error reporting Message-ID: <199504140806.KAA16838@uriah.heep.sax.de> In-Reply-To: <199504132025.WAA00806@yedi.iaf.nl> from "Wilko Bulte" at Apr 13, 95 10:25:08 pm
next in thread | previous in thread | raw e-mail | index | archive | help
As Wilko Bulte wrote: > > Sorry if this is a duplicate. I had the impression it didn't got to > -hackers. I remember your first posting... a while ago. > check_if_actually_parity_int > if not, report and panic > mask NMI for a while > clear parity hardware > install special NMI catcher > enable NMI > loop thru physmem from 0 to top of memory, scanning > memory, hoping error re-occurs > if it does, have catcher return *approximate* address > of error > if not, display message telling user > finally PANIC! Following the discussion about memory tests, i doubt you will be likely to see the error again. Anyway, if you need help with the assembly language part, i can support you. Write as much as you can in C, and hand off the remainder to me -- i'll see how to hack the assembler part. Btw., is there anybody out who knows how to convince gas to include line # debug information into the object file? (I mean, for an assembly language *source* file.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504140806.KAA16838>