From owner-freebsd-questions  Tue Aug 26 18:12:23 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA22435
          for questions-outgoing; Tue, 26 Aug 1997 18:12:23 -0700 (PDT)
Received: from gdi.uoregon.edu (cisco-ts14-line6.uoregon.edu [128.223.150.172])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA22430
          for <questions@FreeBSD.ORG>; Tue, 26 Aug 1997 18:12:18 -0700 (PDT)
Received: from localhost (dwhite@localhost)
          by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id SAA04198;
          Tue, 26 Aug 1997 18:12:06 -0700 (PDT)
Date: Tue, 26 Aug 1997 18:12:06 -0700 (PDT)
From: Doug White <dwhite@gdi.uoregon.edu>
X-Sender: dwhite@localhost
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: "P. van Leeuwen" <pvl@nanoteq.com>
cc: "'FreeBSD questions'" <questions@FreeBSD.ORG>
Subject: Re: calcru/wd error messages
In-Reply-To: <01BCB21F.9EF52ED0@pc-pvl.nanoteq.co.za>
Message-ID: <Pine.BSF.3.96.970826181120.4178C-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

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<rdy,seekdone,drq> error 0       
> Aug 26 10:27:06 groenie /kernel: wd0: interrupt timeout:                        
> Aug 26 10:27:06 groenie /kernel: wd0: status 58<rdy,seekdone,drq> error 1<no_dam
> 
> 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