Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!news.kei.com!sol.ctr.columbia.edu!howland.reston.ans.net!darwin.sura.net!sgiblab!pacbell.com!uop!napa!hughes
From: hughes@napa.eng.uop.edu (Ken Hughes)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: [NetBSD 0.9] patch to wd.c for IDE controller weirdnesses
Followup-To: comp.os.386bsd.bugs
Date: 3 Jan 1994 22:45:34 GMT
Organization: Electrical and Computer Engineering, University of the Pacific
Lines: 52
Message-ID: <2ga76e$r01@unix1.cc.uop.edu>
References: <2ga4l7$i75@explorer.clark.net>
NNTP-Posting-Host: napa.eng.uop.edu
X-Newsreader: TIN [version 1.2 PL2]
Eric S. Hvozda (ack@clark.net) wrote:
: Ok, I got it on, but now I keep getting this during boot:
: Jan 3 13:03:35 DECpc /netbsd: NetBSD 0.9 (DECPC) #0: Mon Jan 3 11:07:50 EST 1994
:....
: Jan 3 13:03:36 DECpc /netbsd: lpt0 at 0x378-0x37f irq 7 on isa
: Jan 3 13:03:36 DECpc /netbsd: wdc0 at 0x1f0-0x1f7 irq 14 on isa
: Jan 3 13:03:36 DECpc /netbsd: wd0 at wdc0 targ 0: 234MB 723 cyl, 13 head, 51 sec <QUANTUM LP240A GM240A01X>
: Jan 3 13:03:36 DECpc /netbsd: wd1 at wdc0 targ 1: 234MB 967 cyl, 16 head, 31 sec <Maxtor 7245 AT>
:......
: Jan 3 13:03:36 DECpc /netbsd: biomask 4040 ttymask 109a netmask 8000 impmask 109a
: Jan 3 13:03:36 DECpc /netbsd: lpt0: stray interrupt sts=0x87
: Jan 3 13:03:36 DECpc /netbsd: wdc0: extra interrupt
: Jan 3 13:03:36 DECpc /netbsd: wdc0: timeout in wdintr WDCS_BUSY
: Jan 3 13:03:36 DECpc /netbsd: wdc0: timeout in wdintr WDCS_DRQ
: Jan 3 13:03:36 DECpc /netbsd: wdc0: timeout in wdintr WDCS_DRQ
: Jan 3 13:03:36 DECpc /netbsd: wd0d: hard error reading fsbn 1 (wd0 bn 1;
: cn 0 tn 0 sn 1)<4>wd0: cannot find label (disk label I/O error)
:
: After this it complains about needing to fsck wd0a by hand and drops to
: single user. If I fsck, it locks. If I just exit to multi-user, it
: hangs, but ^C brings it back and it continues and bootstraps Ok. However
: any attempt to mount, fsck, or otherwise touch wd0 period results in a lock.
: Lock is (a lock is defined as being inactive for 10+ mins).
:
: It's apparent It's having problems with two IDE drives, but I don't know
: why. Is it because of the patch? It would appear so since backing the patch
: off makes the problem go away. Does this imply I have to choose between
: no more IDE lock ups and having two IDE drives? It would seem that way, but
: tell me it isn't so.
Don't know of this is related, but I had a similar problem this weekend when
I tried to add a second IDE drive to my system. The system booed fine with
one drive (wd0) but adding the second caused a panic/trap/reboot. After
capturing the fleeting message on my video recorded and finding the complaint
"no disk label on wd0", I discovered that NetBSD was ignoring the CMOS
configuration for wd0 and using the parameters as (apparently) queried from
the drive. Luckily, my master drive is a Maxtor which I could jumper to
specify the "default" configuration and after doing this things were fine.
I found this curious since the CMOS parameters were apparently used when
running in a single disk system, just not when the second drive was present]
on the IDE chain.
On another note, I started getting the "lpt0: stray interrupt 7" errors also
when the second drive was added.
--
Ken Hughes | "I can't believe this is my life;
(khughes@uop.edu) | I'm going to have to send my SAT
Electrical and Computer Engr | scores to San Quentin instead of
University of the Pacific | Stanford..." _Heathers_