Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!spool.mu.edu!bloom-beacon.mit.edu!senator-bedfellow.mit.edu!athena.mit.edu!tania From: tania@athena.mit.edu (Tania Lewandowski) Newsgroups: comp.os.386bsd.bugs Subject: Adaptec 1542 bug - MBO not free Date: 5 Dec 1993 21:51:50 GMT Organization: Massachusetts Institute of Technology Lines: 21 Distribution: world Message-ID: <2dtl5m$6qh@senator-bedfellow.MIT.EDU> NNTP-Posting-Host: e40-008-5.mit.edu Hi All: I have a 386bsd 0.1 system, patch level 0.2.3. I haven't been able to upgrade yet to Free/NetBSD but am trying to find time to do so. Until I'm able, I'm trying to come up with a quick fix to a bug which seems to be biting me with increasing frequency lately. Basically, all is running smoothly on the system when suddenly the message 'MBO not free' begins to flood the console in a vertical column and all activity on the system just stops. A reboot is the only way to recover. I have looked through the o/s source and it seems likely that this error message is related to the file aha1542.c. My question is, I know that there was a patch kit version 0.2.4 - Does anyone familiar with that patch level know if any part of it may provide some kind of fix for my current problem? This bug is pretty nasty because it seems to occur when the probability is high for a filesystem to be trashed as a result of resetting the hardware ungracefully. I have had to newfs and restore twice already. Any tips that anyone could furnish me with to provide some short term relief to this problem would be hugely appreciated! Thanks! -Tania