From owner-freebsd-current Wed Sep 24 01:07:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA13449 for current-outgoing; Wed, 24 Sep 1997 01:07:39 -0700 (PDT) Received: from schizo.dk.tfs.com (mail.trw.dk [195.8.133.123]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA13442; Wed, 24 Sep 1997 01:07:33 -0700 (PDT) Received: from critter.freebsd.dk (critter.dk.tfs.com [140.145.230.252]) by schizo.dk.tfs.com (8.8.7/8.7.3) with ESMTP id KAA27249; Wed, 24 Sep 1997 10:07:01 +0200 (MET DST) Received: from critter.freebsd.dk (localhost.dk.tfs.com [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id KAA00659; Wed, 24 Sep 1997 10:06:21 +0200 (CEST) To: "John S. Dyson" cc: dyson@freebsd.org, current@freebsd.org Subject: Re: wd.c version 1.138 -> 1.139 broke wdreset ? In-reply-to: Your message of "Wed, 24 Sep 1997 02:56:34 CDT." <199709240756.CAA03553@dyson.iquest.net> Date: Wed, 24 Sep 1997 10:06:20 +0200 Message-ID: <657.875088380@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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() ? >> >Shouldn't have. The only substantial change that I made was to support >a different mechanism for the alternate port address. Maybe, if it doesn't >work for you, try printing out the value of the alt port addr. I'll be in >town until about 13 hr from now, so I can probably help. I will also try >turning APM mode on my drives, and see if that works. 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'm unfortunately at work, so I cannot tweak it now :-( -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."