From owner-freebsd-questions Wed Aug 27 00:37:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA16867 for questions-outgoing; Wed, 27 Aug 1997 00:37:49 -0700 (PDT) Received: from snitterly.nanoteq.co.za (snitterly.nanoteq.co.za [163.195.221.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA16859 for ; Wed, 27 Aug 1997 00:37:42 -0700 (PDT) Received: from pc-pvl.nanoteq.co.za (pc-pvl.nanoteq.co.za [163.195.219.103]) by snitterly.nanoteq.co.za (8.8.3/8.8.3) with SMTP id JAA22569 for ; Wed, 27 Aug 1997 09:40:54 GMT Received: by pc-pvl.nanoteq.co.za with Microsoft Mail id <01BCB2CC.CB022840@pc-pvl.nanoteq.co.za>; Wed, 27 Aug 1997 09:37:10 +0200 Message-ID: <01BCB2CC.CB022840@pc-pvl.nanoteq.co.za> From: "P. van Leeuwen" To: "'Doug White'" Cc: "'FreeBSD questions'" Subject: RE: calcru/wd error messages Date: Wed, 27 Aug 1997 09:37:09 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thanks for the advice Doug. I replaced the cable and started 9 concurrent finds and a make world and so far so good. Pierre P. van Leeuwen pvl@nanoteq.com http://www.nanoteq.co.za -----Original Message----- From: Doug White [SMTP:dwhite@gdi.uoregon.edu] Sent: 27 August 1997 03:12 To: P. van Leeuwen Cc: 'FreeBSD questions' Subject: Re: calcru/wd error messages On Tue, 26 Aug 1997, P. van Leeuwen wrote: > It's on a Pentium 133, 64M with a 3.1G Western Digital Caviar IDE drive > > Aug 26 10:15:23 groenie /kernel: calcru: negative time: -1285 usec > Aug 26 10:23:31 groenie /kernel: calcru: negative time: -944 usec > Aug 26 10:24:16 groenie /kernel: calcru: negative time: -827 usec > Aug 26 10:26:52 groenie /kernel: wd0: interrupt timeout: > Aug 26 10:26:53 groenie /kernel: wd0: status 58 error 0 > Aug 26 10:27:06 groenie /kernel: wd0: interrupt timeout: > Aug 26 10:27:06 groenie /kernel: wd0: status 58 error 1 > Are the two errors related? > > It is a fresh install of 2.2-970704-SNAP. The hard drive is brand new, > and I will take is back if that is the problem. This is the second install > on the drive, and both times a got the interrupt timeout error. The > previous time I also got errors from wdunwedge failing with some > error codes. I had a look at wd.c, but couldn't determine what the problem > was. I think the drive is just plain broken. :( I would agree. The controller may be doing wierd things to the system clock too. If replacing the cable, then the disk doesn't do anything then try replacing the controller. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major Spam routed to /dev/null by Procmail | Death to Cyberpromo