From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 9 18:33:57 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 ADDA4106566B; Mon, 9 Nov 2009 18:33:57 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154]) by mx1.freebsd.org (Postfix) with ESMTP id 1493C8FC17; Mon, 9 Nov 2009 18:33:56 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id e12so749782fga.13 for ; Mon, 09 Nov 2009 10:33:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:references:in-reply-to :mime-version:content-type:message-id:content-transfer-encoding:cc :from:subject:date:to:x-mailer; bh=WSomzzKl+NJ/3/d/0vIimtY0mI/tDGYpzqsq2XrjVPE=; b=xe2UxBgEcHX2nDYVc7Sd0YKZe8brQoitdk8jdNdh2Dhjk11dCTQNZZeUUN7jLztOlb HnicUf77WYZZaips5cVTpnE31aKe/3dw9mrtym+oGI8yu7jW/oC/f1n2wBk26ZH1luFC pHgBmzZyW66VhS8CHHrAjuH8fXAz3tDHoGmsA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:from:subject:date:to:x-mailer; b=FH+a7ZcB9G5M4ijo0Ga1KCa/ryThYpUzrafIITXRWuSK5GUZHUJNn3llnRAAARqu8i LJKUke/rPgAebBLQex1CqRKg0+E5bg5tw9Lw/4SxvhjguOWt7s6bd7RJo+uWpSEQtR/H RxbT1Fjy3+wfNH5A4e8LRBmuabxRJnxsVqCzE= Received: by 10.86.13.37 with SMTP id 37mr1063918fgm.58.1257791636129; Mon, 09 Nov 2009 10:33:56 -0800 (PST) Received: from rui-macbook.lan (bl7-119-16.dsl.telepac.pt [85.240.119.16]) by mx.google.com with ESMTPS id l12sm7330354fgb.17.2009.11.09.10.33.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 09 Nov 2009 10:33:55 -0800 (PST) Sender: Rui Paulo References: <200911081219.09397.bschmidt@techwires.net> <200911090743.48565.jhb@freebsd.org> <200911091803.19057.bschmidt@techwires.net> In-Reply-To: <200911091803.19057.bschmidt@techwires.net> Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Message-Id: <71290651-9DBE-4B3E-81A5-10023E90B43D@FreeBSD.org> Content-Transfer-Encoding: 7bit From: Rui Paulo Date: Mon, 9 Nov 2009 18:33:53 +0000 To: Bernhard Schmidt X-Mailer: Apple Mail (2.1076) 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 18:33:57 -0000 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 ? -- Rui Paulo