From owner-freebsd-stable Tue Dec 18 12:55:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vortex.wa4phy.net (cc449817-a.mrtnz1.ga.home.com [24.12.79.51]) by hub.freebsd.org (Postfix) with ESMTP id 2AD0837B41C for ; Tue, 18 Dec 2001 12:55:24 -0800 (PST) Received: from vortex.wa4phy.net (localhost.wa4phy.net [127.0.0.1]) by vortex.wa4phy.net (8.11.6/8.11.6) with ESMTP id fBIKtN306242 for ; Tue, 18 Dec 2001 15:55:23 -0500 (EST) (envelope-from sam@wa4phy.net) Message-ID: <3C1FAD3B.C9343CD2@vortex.wa4phy.net> Date: Tue, 18 Dec 2001 15:55:23 -0500 From: Sam Drinkard Organization: You Gotta Be Kiddin! X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.4-STABLE i386) X-Accept-Language: en, ja MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: ata0 -- again Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Just had this happen while I was at the console, and noticed the cd spinning up for no reason, and it appeared everything sort of just suspended for a moment or two. Then got the ata0 write command again on the xconsole. ad0: WRITE command timeout tag=0 serv=0 - resetting ata0: resetting devices .. ata0: mask=01 ostat0=d0 ostat2=00 ata0-slave: ATAPI probe a=00 b=00 ata0-master: ATAPI probe a=00 b=00 ata0: mask=01 status0=50 status1=00 ata0-master: ATA probe a=01 b=a5 ata0: devices=01 ata0-master: success setting UDMA4 on VIA chip done Yesterday morning after a reboot, I did a boot -v to see what all was happening. There are things in the boot message I don't understand, but I'm hesisitant to send the whole thing unless somebody specifically wants to see it. The oddities are probing stuff that DOES exist, but says it doesn't, and other oddities (at least to me) If any of this might help solve the write command timeouts, I'll be glad to attach it.. Thanks.. Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message