From owner-freebsd-mobile  Mon Oct 20 11:53:20 1997
Return-Path: <owner-freebsd-mobile>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA12740
          for mobile-outgoing; Mon, 20 Oct 1997 11:53:20 -0700 (PDT)
          (envelope-from owner-freebsd-mobile)
Received: from dominator.eecs.harvard.edu (dominator.eecs.harvard.edu [140.247.60.28])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA12735
          for <freebsd-mobile@freebsd.org>; Mon, 20 Oct 1997 11:53:15 -0700 (PDT)
          (envelope-from karp@eecs.harvard.edu)
Received: (from karp@localhost) by dominator.eecs.harvard.edu (8.6.12/8.6.12) id OAA13219; Mon, 20 Oct 1997 14:53:06 -0400
Date: Mon, 20 Oct 1997 14:53:06 -0400
From: Brad Karp <karp@eecs.harvard.edu>
Message-Id: <199710201853.OAA13219@dominator.eecs.harvard.edu>
To: bryan@yahoo-inc.com
Subject: Re:  memory corruption?
Cc: freebsd-mobile@freebsd.org
Sender: owner-freebsd-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> i also sometimes get these messages about wd0:
>   fegmania /kernel: wd0: interrupt timeout:
>  fegmania /kernel: wd0: status 58<rdy,seekdone,drq> error 1<no_dam>

I posted a note to freebsd-mobile about similar messages a few weeks ago.

I was getting these messages along with _long_ disk timeouts--like two
minutes or more.

And the problem only worsened.

In the end, surmising a dying disk, I exchanged the laptop (an IBM 380).

I've had the new one for over a week now, and it's not given me a single
timeout message or long disk timeout. (Whereas the old one gave me both
several times per hour.)

So at least for me, the wd0 timeout messages _did_ indicate a bad disk.
Seems to me there could be many reasons for the messages other than a bad
disk, though.

Just a data point...

-Brad, karp@eecs.harvard.edu