*BSD News Article 21332


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!usc!acsc.com!acsc.com!fmayhar
From: fmayhar@acsc.com (Frank Mayhar)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: Problems with installation of NetBSD 0.9...
Date: 22 Sep 1993 16:19:58 GMT
Organization: Advanced Computing Systems Company
Lines: 39
Distribution: world
Message-ID: <27ptve$fqr@acsc.com>
References: <27ldlm$j27@acsc.com> <AARON.93Sep21184413@downstage.comp.vuw.ac.nz> <27nuut$gou@acsc.com>
Reply-To: fmayhar@acsc.com
NNTP-Posting-Host: cpuserver.acsc.com

In article <27nuut$gou@acsc.com>, fmayhar@acsc.com (Frank Mayhar) writes:
|> This shouldn't be the problem (although I can't categorically state that
|> it is not), since while the NetBSD driver knows about the second IDE drive
|> (because it saw it in a probe), it is not used anywhere in NetBSD.  It's
|> a DOS-only drive, and therefore has no NetBSD partition, nor does it
|> appear in /etc/fstab.
|> 
|> It really looks like the "ISA strayintr 7" message is related to my
|> trouble, because it is then and only then that I have problems.  I
|> plan to try configuring with the lpt device at that interrupt tonight.
|> I doubt that it will help, though.

OK, last night I tried configuring the lpt device, _and_ tried the
"swap on wd0 and wd1" trick.  Things are still in a bad way.  I no
longer see "ISA strayintr 7" messages, but I do still see the "wdc0:
extra interrupt" message.  The system seems slightly more reliable,
in that it doesn't _always_ hang on boot, but it still sometimes hangs,
only one time out of the three or four that I rebooted it last night.

The really bad news is that this hasn't affected the SCSI problem at
all. It appears at this point that the "ISA strayintr 7" message is
entirely unrelated to the problem. If I do any serious amount of I/O
through the SCSI controller (again, it's an Adaptec 1542B), it soon
hangs, and eventually complains that the controller has timed out. This
happens with both the disk (during fsck or regular disk I/O), and with
the tape. I had absolutely no problems when running 386bsd for over
eight months, so I _don't_ think it's the hardware, and, in fact, I
can use the tape drive from DOS (with the appropriate driver), with no
problems.

I'm beginning to get desperate.  Unfortunately, I just don't have time
at the moment to delve into the code and find the problem myself.  If
I can't make some progress on this, I'll have to fall back to FreeBSD,
although I would really prefer to run NetBSD.  Any help at all would
be *greatly* appreciated.
-- 
Frank Mayhar  fmayhar@acsc.com
	      Advanced Computing Systems Company
	      3000 S. Robertson Blvd. Suite 400, LA, CA 90034   (310) 815-4858