From owner-freebsd-current Tue Oct 6 02:07:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA07141 for freebsd-current-outgoing; Tue, 6 Oct 1998 02:07:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA07136 for ; Tue, 6 Oct 1998 02:07:08 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id CAA20893 for ; Tue, 6 Oct 1998 02:06:59 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id LAA23211 for freebsd-current@freefall.cdrom.com; Tue, 6 Oct 1998 11:06:58 +0200 (MEST) (envelope-from kuku) Date: Tue, 6 Oct 1998 11:06:58 +0200 (MEST) From: Christoph Kukulies Message-Id: <199810060906.LAA23211@gilberto.physik.RWTH-Aachen.DE> To: freebsd-current@freefall.cdrom.com Subject: wd0: interrupt timeout Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is this a wd driver problem in -current or is my (a couple of months old Fujitsu 2.6 GB ) disk drive about to die? during fsck and before in a running system that built worlds but was tending to spuriously reboot in the past while running a very uptodate -current: wd0: interrupt timeout: wd0: status 59 error 40 wd0: wdtimeout() DMA status 4 wd0s1e: soft error reading fsbn 65 of 64-175 (wd0s1 bn 333889; cn 331 tn 3 sn 53) wd0: status 58 error 1 wd0s1e: hard error reading fsbn 67 of 64-175 (wd0s1 bn 333891; cn 331 tn 3 sn 54) wd0: status 59 error 40 ... wd0s1e: reverting to non-multi sector mode reading fsbn 64 of 64-79 ... and so on... -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message