From owner-freebsd-current@FreeBSD.ORG  Sun Sep 11 03:10:54 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
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 7588016A41F;
	Sun, 11 Sep 2005 03:10:54 +0000 (GMT) (envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 18F5543D45;
	Sun, 11 Sep 2005 03:10:54 +0000 (GMT) (envelope-from imp@bsdimp.com)
Received: from localhost (localhost.village.org [127.0.0.1] (may be forged))
	by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j8B39GN1063823;
	Sat, 10 Sep 2005 21:09:16 -0600 (MDT) (envelope-from imp@bsdimp.com)
Date: Sat, 10 Sep 2005 21:08:59 -0600 (MDT)
Message-Id: <20050910.210859.133432771.imp@bsdimp.com>
To: joao.barros@gmail.com
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <70e8236f05091016251510408c@mail.gmail.com>
References: <70e8236f05090513381584dda0@mail.gmail.com>
	<70e8236f0509051350e020f76@mail.gmail.com>
	<70e8236f05091016251510408c@mail.gmail.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0
	(harmony.bsdimp.com [127.0.0.1]);
	Sat, 10 Sep 2005 21:09:17 -0600 (MDT)
Cc: freebsd-current@freebsd.org, mike@sentex.net
Subject: Re: 6.0-CURRENT SNAP004 hangs on amr (patch)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Sep 2005 03:10:54 -0000

In message: <70e8236f05091016251510408c@mail.gmail.com>
            Joao Barros <joao.barros@gmail.com> writes:
: I believe a workaround for this issue would be verifying before
: disabling the device, that no more that one device shares that
: particular pci slot.
: 
: Comments?

No.  That's not a fair workaround.  There's too many other cases that
this would break.  Amrs are farily rare, and having a workaround that
negatively affects other hardware is undesirable.

The problem is that the AMR device attaches to only one of the PCI
devices, when it should attach a dummy driver to the second one.  This
is due to flaws in the amr hardware design, which we've also seen in
the aac cards.

Warner