From owner-freebsd-questions  Tue Aug 26 04:59:17 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id EAA05871
          for questions-outgoing; Tue, 26 Aug 1997 04:59:17 -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 EAA05865
          for <questions@freebsd.org>; Tue, 26 Aug 1997 04:59:06 -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 NAA16794 for <questions@freebsd.org>; Tue, 26 Aug 1997 13:01:17 GMT
Received: by pc-pvl.nanoteq.co.za with Microsoft Mail
	id <01BCB21F.9EF52ED0@pc-pvl.nanoteq.co.za>; Tue, 26 Aug 1997 12:57:34 +0200
Message-ID: <01BCB21F.9EF52ED0@pc-pvl.nanoteq.co.za>
From: "P. van Leeuwen" <pvl@nanoteq.com>
To: "'FreeBSD questions'" <questions@freebsd.org>
Subject: calcru/wd error messages
Date: Tue, 26 Aug 1997 12:57:32 +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

Hi 

I'm getting a couple of error messages, and I hope someone can 
explain  them to me.

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. :(

thanks 
Pierre