From owner-freebsd-stable@FreeBSD.ORG Thu Jun 23 19:54:21 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 115CA16A41C for ; Thu, 23 Jun 2005 19:54:21 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id C12F643D1D for ; Thu, 23 Jun 2005 19:54:20 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA96C8.dip0.t-ipconnect.de [84.170.150.200]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 4CFA3317C3; Thu, 23 Jun 2005 21:57:09 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j5NJsFTU002207; Thu, 23 Jun 2005 21:54:16 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Message-Id: <200506231954.j5NJsFTU002207@drjekyll.mkbuelow.net> From: Matthias Buelow To: Joao Carlos Mendes Luis In-Reply-To: Message from Joao Carlos Mendes Luis of "Thu, 23 Jun 2005 15:42:55 -0300." <42BB02AF.3080702@jonny.eng.br> X-Mailer: MH-E 7.84; nmh 1.0.4; GNU Emacs 21.3.1 Date: Thu, 23 Jun 2005 21:54:15 +0200 Sender: mkb@mkbuelow.net Cc: stable@freebsd.org Subject: Re: ATA problems with FreeBSD 5.4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jun 2005 19:54:21 -0000 Joao Carlos Mendes Luis writes: >kernel sends some messages, "ata0-master: failure - ATA_IDENTIFY timed >out", "ata0-master: failure - ATA_IDENTIFY timed out", and them no hard >disk is identified, so I cannot install the system. If I boot from a >pre-installed hard disk, its even worse, after these message, I get a I've started experiencing the same here, occasionally on reboot, but only after I have upgraded to 5.4-STABLE on June 21. Before, I haven't seen that issue. In a similar situation to yours, Windows XP here has no problems so I don't assume it's hardware related. (And, when it actually boot, the problem doesn't seem occur anymore then while the system is up.) I'm now hesitating to update other machines because of that, hope it gets identified (and fixed) soon. mkb.