From owner-freebsd-current Sat Dec 6 15:11:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA22582 for current-outgoing; Sat, 6 Dec 1997 15:11:30 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA22571 for ; Sat, 6 Dec 1997 15:11:25 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id QAA08464 for ; Sat, 6 Dec 1997 16:11:24 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id QAA06842; Sat, 6 Dec 1997 16:11:23 -0700 Date: Sat, 6 Dec 1997 16:11:23 -0700 Message-Id: <199712062311.QAA06842@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-current@FreeBSD.ORG Subject: Re: wd0 interrupt timeout X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Again, spam killers have been killing *real* email. ------- start of forwarded message ------- From: Nate Williams To: Kris Kennaway Cc: freebsd-current@FreeBSD.ORG Date: Sat, 6 Dec 1997 11:05:53 -0700 > For the past several days (the first time being on Dec 2 as shown) I've been > seeing the following messages popping up: > > Dec 2 12:09:11 morden /kernel: wd0: interrupt timeout: > Dec 2 12:09:11 morden /kernel: wd0: status 50 error 0 > Dec 2 12:09:11 morden /kernel: wd0: wdtimeout() DMA status 4 ... > > The system will completely hang for several seconds - no process > activity, no disk activity, nothing - then the drive in question makes > the "powering up" sound it does when I first power up the machine, the > error appears on the console and activity resumes. I see this on my laptop, and I suspect a bad disk drive, and/or a bad sector that isn't getting mapped automagically. Nate ------- end of forwarded message -------