From owner-freebsd-questions@FreeBSD.ORG Fri Aug 27 22:47:29 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 562BD16A4CE for ; Fri, 27 Aug 2004 22:47:29 +0000 (GMT) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6A5943D67 for ; Fri, 27 Aug 2004 22:47:28 +0000 (GMT) (envelope-from leblanc@keyslapper.org) Received: from localhost ([151.203.91.144]) by out001.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040827224718.WRGF24594.out001.verizon.net@localhost>; Fri, 27 Aug 2004 17:47:18 -0500 Received: from keyslapper.org (localhost [127.0.0.1]) by localhost (8.12.11/8.12.11) with ESMTP id i7RMlFYY062353; Fri, 27 Aug 2004 18:47:17 -0400 (EDT) (envelope-from leblanc@keyslapper.org) Received: (from leblanc@localhost) by keyslapper.org (8.12.11/8.12.11/Submit) id i7RMlDQh062352; Fri, 27 Aug 2004 18:47:13 -0400 (EDT) (envelope-from leblanc) Date: Fri, 27 Aug 2004 18:47:13 -0400 From: Louis LeBlanc To: Sopov Alexey Message-ID: <20040827224713.GA62316@keyslapper.org> Mail-Followup-To: Sopov Alexey , Louis LeBlanc References: <20040827131301.GA58030@keyslapper.org> <1256744289.20040827181823@smtp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1256744289.20040827181823@smtp.ru> User-Agent: Mutt/1.5.6i X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [151.203.91.144] at Fri, 27 Aug 2004 17:47:18 -0500 cc: Louis LeBlanc 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: freebsd-questions@FreeBSD.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Aug 2004 22:47:29 -0000 I doubt this is the problem. The disk is only a couple months old and hasn't seen any abuse so far. It is also unlikely to be "goofy data cables" as suggested by another poster. The cable is no older than the drive, and no more abused. Thanks all the same. Lou On 08/27/04 06:18 PM, Sopov Alexey sat at the `puter and typed: > 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 > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > -- Louis LeBlanc FreeBSD@keyslapper.org Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ I object to intellect without discipline; I object to power without constructive purpose. -- Spock, "The Squire of Gothos", stardate 2124.5