From owner-freebsd-current@FreeBSD.ORG Sun Sep 11 05:10:02 2005 Return-Path: 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 C370916A41F; Sun, 11 Sep 2005 05:10:02 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EC9743D46; Sun, 11 Sep 2005 05:09:55 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j8B59qGJ053976; Sat, 10 Sep 2005 23:09:53 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4323BC24.9020902@samsco.org> Date: Sat, 10 Sep 2005 23:09:56 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <70e8236f05090513381584dda0@mail.gmail.com> <70e8236f0509051350e020f76@mail.gmail.com> <70e8236f05091016251510408c@mail.gmail.com> <20050910.210859.133432771.imp@bsdimp.com> In-Reply-To: <20050910.210859.133432771.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: joao.barros@gmail.com, 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2005 05:10:02 -0000 M. Warner Losh wrote: > In message: <70e8236f05091016251510408c@mail.gmail.com> > Joao Barros 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 I don't really care if you think that it's a flaw. What it comes down to is that it's a problem with FreeBSD. Scott