From owner-freebsd-current@FreeBSD.ORG Mon Feb 9 05:20:31 2004 Return-Path: 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 037EF16A4CE for ; Mon, 9 Feb 2004 05:20:31 -0800 (PST) Received: from sophia3.e-shell.net (sophia3.e-shell.net [64.246.46.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id D83E743D1D for ; Mon, 9 Feb 2004 05:20:30 -0800 (PST) (envelope-from loox@e-shell.net) Received: from 10.170.0.96 (host-200-56-121-128.block.alestra.net.mx [200.56.121.128]) by sophia3.e-shell.net (Postfix) with ESMTP id 1E16D658004 for ; Mon, 9 Feb 2004 07:34:18 -0600 (CST) From: Axel Gonzalez Date: Mon, 9 Feb 2004 07:22:19 -0600 User-Agent: KMail/1.6 MIME-Version: 1.0 Content-Disposition: inline X-UID: 6 To: freebsd-current@freebsd.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200402090722.19717.loox@e-shell.net> X-Mailman-Approved-At: Mon, 09 Feb 2004 05:46:17 -0800 Subject: sata drive problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Mon, 09 Feb 2004 13:20:31 -0000 Evren Yurtesen wrote: >Hello, I have a system which had problems with the following errors >after working perfectly for 2 days. Is there any suggestions about what >can I do about this? else than checking the cables :) I think the drives >work fine also. They were doing pretty fine with another mainboard. When under heavy load, i get the error (just tested from a cvsup 09/02/2004 src): ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=... ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=... sometimes it crashes right away, sometimes it waits a little. can't get the exact LBA sectors because the system crashes cold, and its not logged (i've seen the error before a crash) Using a previous kernel snapshot (around jan 20, 2004), i can work normally, even with heavy loads. The relevant system data: Feb 9 06:48:06 kernel: ACPI APIC Table: Feb 9 06:48:06 moonlight kernel: CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2394.01-MHz 686-class CPU) Feb 9 06:48:06 moonlight kernel: Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Feb 9 06:48:06 moonlight kernel: Features=0xbfebfbff Feb 9 06:48:06 moonlight kernel: Hyperthreading: 2 logical CPUs ... Feb 9 06:48:06 moonlight kernel: ata0: at 0x1f0 irq 14 on atapci0 Feb 9 06:48:06 moonlight kernel: ata0: [MPSAFE] Feb 9 06:48:06 moonlight kernel: ata1: at 0x170 irq 15 on atapci0 Feb 9 06:48:06 moonlight kernel: ata1: [MPSAFE] Feb 9 06:48:06 moonlight kernel: atapci1: port 0xdc00-0xdc0f,0xe000-0xe003,0xe400-0xe407,0xe800-0xe803,0xec00-0xec07 irq 18 at device 31.2 on pci0 Feb 9 06:48:06 moonlight kernel: atapci1: [MPSAFE] Feb 9 06:48:06 moonlight kernel: ata2: at 0xec00 on atapci1 Feb 9 06:48:06 moonlight kernel: ata2: [MPSAFE] Feb 9 06:48:06 moonlight kernel: ata3: at 0xe400 on atapci1 Feb 9 06:48:06 moonlight kernel: ata3: [MPSAFE] Feb 9 06:48:06 moonlight kernel: pci0: at device 31.3 (no driver attached) ... Feb 9 06:48:06 moonlight kernel: GEOM: create disk ad0 dp=0xc44aa160 Feb 9 06:48:06 moonlight kernel: ad0: 57241MB [116301/16/63] at ata0-master UDMA100 Feb 9 06:48:06 moonlight kernel: acd0: CDRW at ata1-master PIO4 Feb 9 06:48:06 moonlight kernel: GEOM: create disk ad4 dp=0xc459a360 Feb 9 06:48:06 moonlight kernel: ad4: 78167MB [158816/16/63] at ata2-master UDMA100 Feb 9 06:48:06 moonlight kernel: GEOM: create disk cd0 dp=0xc449d600