From owner-freebsd-amd64@FreeBSD.ORG  Thu Apr 28 19:11:17 2011
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 9C158106566C;
	Thu, 28 Apr 2011 19:11:17 +0000 (UTC) (envelope-from mav@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 723828FC12;
	Thu, 28 Apr 2011 19:11:17 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p3SJBHL3029388;
	Thu, 28 Apr 2011 19:11:17 GMT
	(envelope-from mav@freefall.freebsd.org)
Received: (from mav@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p3SJBGSZ029384;
	Thu, 28 Apr 2011 19:11:16 GMT (envelope-from mav)
Date: Thu, 28 Apr 2011 19:11:16 GMT
Message-Id: <201104281911.p3SJBGSZ029384@freefall.freebsd.org>
To: yury@gorodok.net, mav@FreeBSD.org, freebsd-amd64@FreeBSD.org
From: mav@FreeBSD.org
Cc: 
Subject: Re: amd64/148526: [ahci] ahci driver does not boot on AMD chip
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2011 19:11:17 -0000

Synopsis: [ahci] ahci driver does not boot on AMD chip

State-Changed-From-To: open->closed
State-Changed-By: mav
State-Changed-When: Thu Apr 28 19:09:58 UTC 2011
State-Changed-Why: 
Specific case handled by setting tunable. Real problem cause and
possibility of permanent fix is unclear. May be board-specific.

http://www.freebsd.org/cgi/query-pr.cgi?pr=148526