From owner-freebsd-acpi@FreeBSD.ORG Thu Aug 23 22:07:23 2007 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA42016A41B for ; Thu, 23 Aug 2007 22:07:23 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 5EDA113C45D for ; Thu, 23 Aug 2007 22:07:23 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8k) with ESMTP id 204898437-1834499 for multiple; Thu, 23 Aug 2007 18:07:27 -0400 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l7NM7GQw021635; Thu, 23 Aug 2007 18:07:18 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: "William Grzybowski" Date: Thu, 23 Aug 2007 15:24:50 -0400 User-Agent: KMail/1.9.6 References: <632825b40708210457r50b22cf9xd55fa88b569e3b5b@mail.gmail.com> <632825b40708221504oa35fcfbgc02eba47c82eb93b@mail.gmail.com> <632825b40708230435x2b32d73clfcd88b766e171c46@mail.gmail.com> In-Reply-To: <632825b40708230435x2b32d73clfcd88b766e171c46@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708231524.51244.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 23 Aug 2007 18:07:18 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4037/Thu Aug 23 15:08:22 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-acpi@freebsd.org Subject: Re: msk dev problem with acpi X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 22:07:23 -0000 On Thursday 23 August 2007 07:35:15 am William Grzybowski wrote: > On 8/22/07, William Grzybowski wrote: > > > > On 8/22/07, John Baldwin wrote: > > > > > On Wednesday 22 August 2007 04:19:38 pm William Grzybowski wrote: > > > > Hi, i was testing a verbose boot with acpi and without acpi, i noted a > > > > "requested unsupported memory range" with acpi... > > > > > > Yes, this is why your device doesn't work. Verbose dmesg's for both > > > cases > > > would be useful. > > > > > > Hi, i am sending the both verbose dmesg's: > > http://www.inf.ufpr.br/wg06/dmesg-verbose-acpi.gz > > http://www.inf.ufpr.br/wg06/dmesg-verbose-noacpi.gz > > > > I hope it helps.. tell me if you need anything more > > thanks all :) > > > > -- > > > John Baldwin > > > > > > Hi, i just verified it, the links which i gave hadn't the full dmesg, if you > already saw this links, please, see it again. > It is more informative :) > http://www.inf.ufpr.br/wg06/dmesg-verbose-acpi.gz > http://www.inf.ufpr.br/wg06/dmesg-verbose-noacpi.gz > > Thanks again and sorry for multiple messages and annoying :S ACPI is clearing the resources in the PCI-PCI bridge (and the msk(4) device), presumably during an _INI routine and FreeBSD can't currently cope with that. I couldn't really find where in your ASL it clears the BAR. You can try bugging warner losh (imp@). In this case it should be easier to handle as the PCI-PCI bridge has no resources at all, so it should be able to recurse up ok. -- John Baldwin