From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 9 17:03:26 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 A795B106568B for ; Mon, 9 Nov 2009 17:03:26 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mx01.netsrc.de (mx01.netsrc.de [89.107.71.100]) by mx1.freebsd.org (Postfix) with ESMTP id 523E38FC15 for ; Mon, 9 Nov 2009 17:03:26 +0000 (UTC) Received: from jessie.localnet (unknown [212.185.121.50]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.netsrc.de (Postfix) with ESMTP id 281F1192FD9; Mon, 9 Nov 2009 18:03:25 +0100 (CET) From: Bernhard Schmidt To: John Baldwin Date: Mon, 9 Nov 2009 18:03:18 +0100 User-Agent: KMail/1.12.1 (Linux/2.6.30-2-686; KDE/4.3.2; i686; ; ) References: <200911081219.09397.bschmidt@techwires.net> <200911090743.48565.jhb@freebsd.org> In-Reply-To: <200911090743.48565.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200911091803.19057.bschmidt@techwires.net> Cc: freebsd-acpi@freebsd.org 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 17:03:26 -0000 On Monday 09 November 2009 13:43:48 John Baldwin wrote: > 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. The complete pciconf before suspend: http://techwires.net/~bschmidt/pciconf.before.txt The complete pciconf after resume: http://techwires.net/~bschmidt/pciconf.after.txt Comparing both yields exactly those 4 lines missing. -- Bernhard