From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 9 15:50:20 2009 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 2C88A1065676 for ; Mon, 9 Nov 2009 15:50:20 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id F2BC78FC2B for ; Mon, 9 Nov 2009 15:50:19 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id ED51546B1A; Mon, 9 Nov 2009 10:50:18 -0500 (EST) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 1AEB88A01D; Mon, 9 Nov 2009 10:50:18 -0500 (EST) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Mon, 9 Nov 2009 07:43:48 -0500 User-Agent: KMail/1.9.7 References: <200911081219.09397.bschmidt@techwires.net> In-Reply-To: <200911081219.09397.bschmidt@techwires.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911090743.48565.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 09 Nov 2009 10:50:18 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00, DATE_IN_PAST_03_06,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Subject: Re: general issue with suspend/resume with iwn(4)/bge(4) 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: Mon, 09 Nov 2009 15:50:20 -0000 On Sunday 08 November 2009 6:19:09 am Bernhard Schmidt wrote: > Hi, > > I hope this is the correct list for an issue like that, if not, a pointer > would be appreciated. > > I've been in contact with Mykola Dzham quite some time now and we are trying > to figure out a resume issue on his iwn(4) device. It does seem that this > device does not come up correctly after suspend. The interesting part is, that > even pciconf -l -bcv ist not able to get all information. > > Before suspend: > iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 > rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' > class = network > bar [10] = type Memory, range 64, base 0xec800000, size 8192, enabled > cap 01[c8] = powerspec 3 supports D0 D3 current D0 > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message > cap 10[e0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) > > After resume: > iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 > rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' > class = network Are you sure you didn't forget the extra options to pciconf here? The bar should definitely not disappear since we save that state in software, not in hardware. Also, the capability pointer register is set by the hardware, software never changes it. -- John Baldwin