Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.sdsmt.edu!nntp.uac.net!cancer.vividnet.com!hunter.premier.net!bofh.dot!news.mathworks.com!newsfeed.internetmci.com!vixen.cso.uiuc.edu!usenet From: Vladimir Roubtsov <roubtsov> Newsgroups: comp.unix.bsd.freebsd.misc Subject: /kernel: "rtinit: wrong ifa ...." ???? Date: 30 May 1996 20:00:55 GMT Organization: University of Illinois at Urbana Lines: 20 Message-ID: <4okupn$k38@vixen.cso.uiuc.edu> NNTP-Posting-Host: alecto.physics.uiuc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 1.1N (X11; I; IRIX 5.3 IP22) X-URL: news:comp.unix.bsd.freebsd.misc Hi: A question to knowledgeable folks: what can a message /kernel: rtinit: wrong (or bad) ifa: <some hex #> was <different hex #> ( or close to this ) possibly mean ? I am not sure what sequence of events triggers this, I've only seen this twice in ~month of using 2.1R. What "ifa" stands for isn't obvious to me. I am running 2.1R with trimmed kernel (support for hardware I don't have removed; EOI feature of master interrupt controller turned on) on Pentium 75 Tyan Titan III PCI mbrd with Cirrus PCI SVGA video card and WD 1.2 Gb EIDE hard drive. It is possible that both times I was running X312_SVGA server and running user-land ppp on COM2. The X server might've been in 16bpp mode in which case it was using linear addressing and memory-mapped IO (as configured by me; this screws things up in regular 8bpp mode though). Any help will be appreciated, Vlad.