Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!werple.apana.org.au!otis.apana.org.au!serval.net.wsu.edu!netnews.nwnet.net!oracle.pnl.gov!osi-east2.es.net!cronkite.nersc.gov!dancer.ca.sandia.gov!overload.lbl.gov!lll-winken.llnl.gov!uwm.edu!news.alpha.net!news.mathworks.com!noc.near.net!seqp4!sequoia!grego From: grego@sequoiasequoia.com (Gregory O'Neil) Subject: 386BSD MMU Read Faults - panic Organization: Sequoia Systems, Inc. Date: Thu, 8 Dec 1994 15:29:18 GMT Message-ID: <D0I0Cv.1v8@seqp4.sequoia.com> X-Newsreader: Tin 1.1 PL3 Sender: news@seqp4.sequoia.com (news administrator) Lines: 19 I'm getting frequent MMU read fault @ 0x696f7373 trap 12 code fe010000 eip fe010ebd cs 8 eflags 10206 comm ksh cr2 696f7373 cpl 0 panic:trap boot/dump It is easily reproduced by using the ksh history buffer, occuring 80% this way. I've only been working with 386BSD for about 2 weeks, so I'm still learning how to work these issues. Is this a known problem, or am I experiencing a localized problem? My config: 486DX33, 8Mb Mem, Adaptec 1542 with 2 Seagate 600+ Mb drives, 16 Mb swap. -- Greg O'Neil - Mktg Tech Eng - SMP FT SVR4 Unix grego@sequoia.com - Sequoia Systems Inc. (508)480-0800x1759 My opinions are mine MINE. Mine MiNe mInE minE! And they may also be wrong.