From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 9 19:58:03 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 0AE5E1065679; Mon, 9 Nov 2009 19:58:03 +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 85CEF8FC08; Mon, 9 Nov 2009 19:58:02 +0000 (UTC) Received: from maja.lab.techwires.net (p54B4DBF9.dip.t-dialin.net [84.180.219.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.netsrc.de (Postfix) with ESMTP id 5ACB019300D; Mon, 9 Nov 2009 20:58:01 +0100 (CET) Received: from maja.lab.techwires.net (localhost [127.0.0.1]) by maja.lab.techwires.net (8.14.3/8.14.3) with ESMTP id nA9Jw0BC002785; Mon, 9 Nov 2009 20:58:00 +0100 (CET) (envelope-from bschmidt@techwires.net) Received: (from bschmidt@localhost) by maja.lab.techwires.net (8.14.3/8.14.3/Submit) id nA9JneOv002618; Mon, 9 Nov 2009 20:49:40 +0100 (CET) (envelope-from bschmidt@techwires.net) X-Authentication-Warning: maja.lab.techwires.net: bschmidt set sender to bschmidt@techwires.net using -f From: Bernhard Schmidt To: Rui Paulo Date: Mon, 9 Nov 2009 20:49:35 +0100 User-Agent: KMail/1.12.1 (FreeBSD/9.0-CURRENT; KDE/4.3.1; amd64; ; ) References: <200911081219.09397.bschmidt@techwires.net> <200911091803.19057.bschmidt@techwires.net> <71290651-9DBE-4B3E-81A5-10023E90B43D@FreeBSD.org> In-Reply-To: <71290651-9DBE-4B3E-81A5-10023E90B43D@FreeBSD.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200911092049.35249.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 19:58:03 -0000 On Monday 09 November 2009 19:33:53 Rui Paulo wrote: > On 9 Nov 2009, at 17:03, Bernhard Schmidt wrote: > > 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. > > We should check if the device driver is doing something evil on > suspend/resume. Can you boot without iwn loaded and suspend/resume ? I'm sorry if it might came out wrong in my first email. It's Mykola Dzham's system which has those issue, I'm posting all information on prior discussions with him. I can suspend/resume with iwn loaded, device works after resume as its supposed to. For him kldload/kldunload does work too, those issues just come up after suspend. Based on that I had doubts that it is a general issue with the iwn driver. -- Bernhard