Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA613 ; Sat, 06 Feb 93 01:01:40 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!sdd.hp.com!apollo.hp.com!netnews From: sommerfeld@apollo.hp.com (Bill Sommerfeld) Subject: Re: [386bsd] accessing wd1 hangs system Sender: usenet@apollo.hp.com (Usenet News) Message-ID: <SOMMERFELD.93Feb4124615@blatt.apollo.hp.com> In-Reply-To: ken@cujo.curtin.edu.au's message of Thu, 4 Feb 1993 00:45:49 GMT Date: Thu, 4 Feb 1993 17:43:09 GMT Lines: 49 References: <1993Feb4.004549.5345@cujo.curtin.edu.au> Nntp-Posting-Host: snarfblatt.ch.apollo.hp.com Organization: Hewlett Packard In article <1993Feb4.004549.5345@cujo.curtin.edu.au> ken@cujo.curtin.edu.au (Ken Taylor) writes: Newsgroups: comp.unix.bsd Path: apollo.hp.com!sdd.hp.com!zaphod.mps.ohio-state.edu!howland.reston.ans.net!spool.mu.edu!sgiblab!munnari.oz.au!uniwa!cujo!ken From: ken@cujo.curtin.edu.au (Ken Taylor) Organization: Curtin University of Technology X-Newsreader: TIN [version 1.1 PL7] Date: Thu, 4 Feb 1993 00:45:49 GMT Lines: 45 I have seen others who have had this problem before, but heven't seen any answers: I have two IDE drives (which work fine under everything else) and have installed the 0.2 patchkit. The second drive is seen and reported at boot time.. I managed to disklabel the second drive (it deleted the old DOS partition and seemed to work fine) and everything seemed fine until I rebooted.. After a reboot, ANY access to wd1 hangs the system solid.. I had this problem on a 486/33; one possible cause is some sort of race condition in drive initialization code (it worked maybe 50% of the time with "turbo" turned off and none of the time with it turned on). The "workaround" is to reconfigure your kernel to have the *potential* to swap on wd0 and wd1 right now, there should be a line in the kernel config file along the lines of: config 386bsd root on wd0 swap on wd0 and as0 Change that to: config 386bsd root on wd0 swap on wd0 and wd1 and as0 reconfig, rebuild, install the new kernel, and reboot. Don't send me mail asking how to do the latter stages; instructions on how to do this are posted here periodically. - Bill