From owner-freebsd-acpi@FreeBSD.ORG Fri Jan 2 19:09:11 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 F223D1065670 for ; Fri, 2 Jan 2009 19:09:10 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.247]) by mx1.freebsd.org (Postfix) with ESMTP id 9F4748FC1A for ; Fri, 2 Jan 2009 19:09:10 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by an-out-0708.google.com with SMTP id c2so2303419anc.13 for ; Fri, 02 Jan 2009 11:09:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:x-mailer :mime-version:subject:date:cc; bh=v4ygFvTVW7Sc2izxdPLwJ6rB5HonLIkUB6oMgfBhC78=; b=X9Db6saF4TEarw2XLB2OsQ4a2k8sPACS4DseoeB6qmEhA/RuwNR+3bi2BzErHNMHVm t4HfUDRZi4CZdiAqHt1+M3Gy9qfOFnJIPQTCFL8o7dNLwof3w0RUe7YcNvhl6h7J3hyz 0nCNgQwq+ucw59JQSP1PsrT75PR8cDHrwrSfs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:x-mailer:mime-version:subject:date:cc; b=Krabmjw7uRgmwL/Gpst4MqiIkwy0hpSAg0GUfHEsHg4UjcPGJCX2yjnUMiz+qWLGwl VWyQO4dgBThme3Zbf8Ix0Hvjvrhf0VpnARy65JbwD2/LWfDPfufN23FdvRG0sZ0pQ69B qgF7yfuVDQEv52tFgU9i8VrumzAfmUfx9lWqE= Received: by 10.100.128.2 with SMTP id a2mr9946682and.93.1230923349789; Fri, 02 Jan 2009 11:09:09 -0800 (PST) Received: from ?10.88.62.48? ([32.156.137.7]) by mx.google.com with ESMTPS id b29sm31961512ana.33.2009.01.02.11.09.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 02 Jan 2009 11:09:08 -0800 (PST) References: <1230564886.2280.11.camel@localhost> <4958F887.2010203@root.org> <1230579699.2386.5.camel@localhost> <49593036.4030306@root.org> <1230662172.1702.2.camel@localhost> <495A7309.2060400@root.org> <1230915992.4841.4.camel@localhost> Message-Id: <3533670F-754C-40C8-B76A-0C17333E7569@gmail.com> From: Garrett Cooper To: Coleman Kane In-Reply-To: <1230915992.4841.4.camel@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (5G77) Mime-Version: 1.0 (iPhone Mail 5G77) Date: Fri, 2 Jan 2009 11:08:56 -0800 Cc: "freebsd-acpi@FreeBSD.org" Subject: Re: amd64 S3 patch on HP 6715b: NICs won't work after resume from S3 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: Fri, 02 Jan 2009 19:09:11 -0000 On Jan 2, 2009, at 9:06, Coleman Kane wrote: > On Tue, 2008-12-30 at 11:14 -0800, Nate Lawson wrote: >> Coleman Kane wrote: >>> On Mon, 2008-12-29 at 12:16 -0800, Nate Lawson wrote: >>>> Coleman Kane wrote: >>>>> On Mon, 2008-12-29 at 08:19 -0800, Nate Lawson wrote: >>>>>> Coleman Kane wrote: >>>>>>> I've been testing Jung-uk Kim's recent amd64 suspend patch on >>>>>>> my HP >>>>>>> notebook, and it seems to be very close to working well. >>>>>>> >>>>>>> The notebook goes into S3 state properly, but when it comes >>>>>>> back out it >>>>>>> seems that the hardware is left in a bad state. I cannot >>>>>>> attach my >>>>>>> if_bge and if_ndis network drivers after a resume. >>>>>> Dump the pci config register states for those devices both >>>>>> before and >>>>>> after the resume. Where the bits differ is probably where >>>>>> you'll find >>>>>> the problem. >>>>>> >>>>>> Example to read 256 bytes: >>>>>> pciconf -r pci0:4:0 0:256 >>>>>> >>>>> Tried that, and I also tried to use pciconf -w to set the >>>>> registers to >>>>> the initial state of the hardware before if_bge is loaded. I >>>>> still get >>>>> the following messages when I attempt to reload the kld after the >>>>> resume, followed by a failed attach: >>>>> >>>>> bge0: mem >>>>> 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16 >>>>> bge0: firmware handshake timed out, found 0x4b657654 >>>>> bge0: firmware handshake timed out, found 0x4b657654 >>>>> bge0: RX CPU self-diagnostics failed! >>>>> bge0: chip initialization failed >>>>> device_attach: bge0 attach returned 6 >>>>> >>>>> Anyone have success with S3 on amd64 or i386 with if_bge cards? >>>> Did you post the register states before and after? >>>> >>> Attached are the before and after snapshots of the device's PCI >>> register >>> space. I need to track down a good table to mate these with. In this >>> case, I didn't unload the driver, as the if_bge driver is supposed >>> to be >>> able to properly handle suspend/resume now. >>> >>> These are dumps of the whole 256-byte register space, using: >>> pciconf -r -b pci0:16:0:0 0:0x100 >> >> Great. So far in FreeBSD, anything after the first 64 bytes is the >> driver's responsibility. According to your dump, that is where all >> the >> differences are. >> > > So, my guess is that the bge_suspend and bge_resume methods in the bge > driver need some tweaking to support my hardware (the BCM5754/5787) > when > it comes out of resume... > > Any pointers on who I might be able to work on this with? Dumb observation: driver maintainer? -Garrett