From owner-freebsd-questions@FreeBSD.ORG Fri Aug 27 14:21:55 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F5BD16A4CE for ; Fri, 27 Aug 2004 14:21:55 +0000 (GMT) Received: from york.smtp.ru (york.smtp.ru [62.118.249.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A10C43D41 for ; Fri, 27 Aug 2004 14:21:52 +0000 (GMT) (envelope-from adler@smtp.ru) Received: from [195.19.34.32] (account adler@smtp.ru HELO h32.net34.bmstu.ru) by york.smtp.ru (CommuniGate Pro SMTP 3.5.9) with ESMTP id 66886890 for freebsd-questions@FreeBSD.org; Fri, 27 Aug 2004 18:21:50 +0400 Date: Fri, 27 Aug 2004 18:18:23 +0400 From: Sopov Alexey X-Mailer: The Bat! (v2.04.7) CD5BF9353B3B7091 X-Priority: 3 (Normal) Message-ID: <1256744289.20040827181823@smtp.ru> To: Louis LeBlanc In-Reply-To: <20040827131301.GA58030@keyslapper.org> References: <20040827131301.GA58030@keyslapper.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: TIMEOUT - WRITE_DMA errors in security output X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: adler List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Aug 2004 14:21:55 -0000 Backup your data imediatly! I think your ad4 dies... LL> Hey all. I'm seeing some things I'm not comfortable with in the LL> security output from one of my systems - a new Dell Dimension 8300. LL> This is what I'm seeing: LL> key2.keyslapper.org kernel log messages: >> ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=31672255 >> ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=31672383 LL> The ad4 timeouts have happened before. They usually coincide with a LL> moderate to large port build. If I'm building some huge package like LL> OpenOffice or xorg when this happens, the whole system hangs. No LL> mouse, keyboard, nothing. Last time I just left it to see if things LL> resolved, and next morning I found it freshly rebooted. (I did LL> eventually get both OpenOffice and xorg built though) LL> Ad4 is a 160G hard drive with the following partitioning: LL> $ df -k LL> Filesystem 1K-blocks Used Avail Capacity Mounted on LL> /dev/ad4s1a 1012974 57462 874476 6% / LL> devfs 1 1 0 100% /dev LL> /dev/ad4s1h 57896520 4 53264796 0% /export LL> /dev/ad4s1g 60931274 2371112 53685662 4% /home LL> /dev/ad4s1e 1012974 7882 924056 1% /tmp LL> /dev/ad4s1f 20308398 4000050 14683678 21% /usr LL> /dev/ad4s1d 8122126 85068 7387288 1% /var LL> fdisk output is: LL> # fdisk LL> ******* Working on device /dev/ad4 ******* LL> parameters extracted from in-core disklabel are: LL> cylinders=310019 heads=16 sectors/track=63 (1008 blks/cyl) LL> Figures below won't work with BIOS for partitions not in cyl 1 LL> parameters to be used for BIOS calculations are: LL> cylinders=310019 heads=16 sectors/track=63 (1008 blks/cyl) LL> Media sector size is 512 LL> Warning: BIOS sector numbering starts with sector 1 LL> Information from DOS bootblock is: LL> The data for partition 1 is: LL> sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) LL> start 63, size 312496317 (152586 Meg), flag 80 (active) LL> beg: cyl 0/ head 1/ sector 1; LL> end: cyl 1023/ head 254/ sector 63 LL> The data for partition 2 is: LL> LL> The data for partition 3 is: LL> LL> The data for partition 4 is: LL> LL> Any other info that would help, please let me know, but I'd like to LL> know what the cause could be and how to fix it. LL> TIA LL> Lou -- [ /Iexa ] mailto:adler@smtp.ru