From owner-freebsd-current Thu Oct 9 07:10:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA02072 for current-outgoing; Thu, 9 Oct 1997 07:10:39 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from al.imforei.apana.org.au (pjchilds@al.imforei.apana.org.au [202.12.89.41]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA02061 for ; Thu, 9 Oct 1997 07:10:27 -0700 (PDT) (envelope-from pjchilds@al.imforei.apana.org.au) Received: (from pjchilds@localhost) by al.imforei.apana.org.au (beBop) id XAA02412; Thu, 9 Oct 1997 23:40:14 +0930 (CST) Date: Thu, 9 Oct 1997 23:40:14 +0930 (CST) From: Peter Childs Message-Id: <199710091410.XAA02412@al.imforei.apana.org.au> To: phk@critter.freebsd.dk (Poul-Henning Kamp), freebsd-current@freebsd.org Subject: Re: wd.c version 1.138 -> 1.139 broke wdreset ? X-Newsreader: TIN [UNIX 1.3 unoff BETA 970731; i386 FreeBSD 2.2-STABLE] Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <657.875088380@critter.freebsd.dk> you wrote: > In message <199709240756.CAA03553@dyson.iquest.net>, "John S. Dyson" writes: > >Poul-Henning Kamp said: > >> > >> It looks to me like the 1.138 to 1.139 commit broke wdreset() ? > Well, I couldn't resume my laptops disk until I backed this out. > Soren complained about lack of recovery the other evening in case of > a bad block, I belive it is the same problem. I've noticed a problem just of late we two or three system locks with a "wdunwedge failed" message... i was thinking this was a sign of impending hardware failure, but have had no time to investigate. My wd.c is 1.119.2.8 (2.2-stable)... Related problem?, or tangent? Regards, Peter -- Peter Childs --- http://www.imforei.apana.org.au/~pjchilds Finger pjchilds@al.imforei.apana.org.au for public PGP key