From owner-freebsd-current@FreeBSD.ORG Tue Sep 27 00:05:09 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1057216A41F for ; Tue, 27 Sep 2005 00:05:09 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: from pne-smtpout1-sn2.hy.skanova.net (pne-smtpout1-sn2.hy.skanova.net [81.228.8.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9049A43D48 for ; Tue, 27 Sep 2005 00:05:08 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: from royal64.emp.zapto.org (195.198.193.104) by pne-smtpout1-sn2.hy.skanova.net (7.2.060.1) id 4332AC78000EF845; Tue, 27 Sep 2005 02:05:07 +0200 Date: Tue, 27 Sep 2005 02:05:03 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: <4F9C9299A10AE74E89EA580D14AA10A605F552@royal64.emp.zapto.org> Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Thread-Topic: "TIMEOUT - READ_DMA48 retrying" has suddenly started appearing (RELENG_6) Thread-Index: AcXC9xVxfbXw+ducTiug5vP/qHH+0w== From: "Daniel Eriksson" To: "FreeBSD Current" Cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= Subject: "TIMEOUT - READ_DMA48 retrying" has suddenly started appearing (RELENG_6) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Sep 2005 00:05:09 -0000 I'm running RELENG_6 on two machines, one SMP and one UP (both using = SCHED_4BSD). I cvsup/update the OS a few times a week, and after an = update on Saturday (24/9) I've seen multiple "TIMEOUT - READ_DMA48 = retrying" errors on both machines, causing all sorts of trouble (broken = arrays, panics, ...). After a reboot the disks have come back to life = and seem to work just fine. It could just be a coincidence and multiple disks on two separate = machines have started to go bad, but since the disks are different = models on different ATA/SATA controllers in different machines it could = also be an indication that something has happened with FBSD. If it's a = FBSD problem then the "offending" code was added some time between = Monday 19/9 and Saturday 24/9. Is anyone else experiencing similar problems? /Daniel Eriksson