From owner-freebsd-current@FreeBSD.ORG Wed Nov 18 03:11:47 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 292A31065670 for ; Wed, 18 Nov 2009 03:11:47 +0000 (UTC) (envelope-from gnemmi@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by mx1.freebsd.org (Postfix) with ESMTP id A813C8FC25 for ; Wed, 18 Nov 2009 03:11:46 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id e12so1802478fga.13 for ; Tue, 17 Nov 2009 19:11:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=hWzkSQcx1SBNE6yGsYkrHmr3t8bovrYZhYxjRGE2E20=; b=Vj6C1MxypaY6NalYMBPNaOpLGt/7GGip09T9jGkVu52HcpV7uvIiVBGRdqDN6v1xqM Y+bo8bhUPOps1uX0C6+hIRrsGarwV3FnzM5yvBxcDrVvsUWzvaQVALN0/UgOeYAYbsn0 jOiuW7jg3zpWReQDw1uTm9VocZNqF/cUOHLfA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=pV0ZYkekngl022pMNKpg07vskVHlDju8kb0AdyeaWN93YYtz9uhGdN6Ixly9CY6DbC 5kYiSwQy+hLAYZXLEm7MzqlOUx0aV7XzC494tEXhxkBrn7ka02eChzCZ2Gvk1ezOe/iW iPAUge1UPWYQzV0inph4SEBcTnyQZw1/cfg3E= MIME-Version: 1.0 Received: by 10.103.48.17 with SMTP id a17mr525628muk.82.1258513905595; Tue, 17 Nov 2009 19:11:45 -0800 (PST) In-Reply-To: <20091117232347.GJ1262@michelle.cdnetworks.com> References: <20091111223751.GE15449@michelle.cdnetworks.com> <200911171650.06834.gnemmi@gmail.com> <20091117193208.GI1262@michelle.cdnetworks.com> <200911171917.41906.gnemmi@gmail.com> <20091117232347.GJ1262@michelle.cdnetworks.com> Date: Wed, 18 Nov 2009 00:11:45 -0300 Message-ID: <19e9a5dc0911171911l6803c9dbkd8dde1b9f54e701@mail.gmail.com> From: Gonzalo Nemmi To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Call for bge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2009 03:11:47 -0000 On Tue, Nov 17, 2009 at 8:23 PM, Pyun YongHyeon wrote: > On Tue, Nov 17, 2009 at 07:17:41PM -0200, Gonzalo Nemmi wrote: > > On Tuesday 17 November 2009 5:32:08 pm Pyun YongHyeon wrote: > > > On Tue, Nov 17, 2009 at 04:50:06PM -0200, Gonzalo Nemmi wrote: > > > > > > [...] > > > > > > > Well, I proceeded as I told you I would, applied your patch and > > > > even if it didn't solve the problem (bge still doesn't resume) at > > > > least it improved the previous situation given that now it doesn't > > > > loop timing out once and again as before. > > > > > > > > You can find a tail from /var/log/messages in here: > > > > http://pastebin.com/f643555f7 > > > > > > > > As you can see, the first 3 lines corresponds to "kldload if_bge" > > > > Line number 4 is "acpiconf -s3" > > > > > > > > At line number 17 bge0 finally fails and let's the machine wake up > > > > at line 18. > > > > > > > > Then, as soon as I could I issued a "ifconfig bge0" to see what I > > > > could get .. that's what you can see from line 20 to line 41. (as > > > > you can see > > > > > > Ok, would you try this one? I guess bge(4) register access method > > > could be in uninitialized state after resume. > > > > Just did .. same result .. you=B4ll find the messages here: > > http://pastebin.com/f38369b3c > > > > 1.- root login > > 2 to 9.- "kldload if_bge" > > 10.- "acpiconf -s3" > > 11 to 13.- wpi0 messages before suspending > > 14 to 23.- bge0 messages upon resume > > 24.- wakeup > > > > Can you remove wpi(4) in kernel configuration and try again? > I don't think wpi(4) can interfere bge(4) resume but just want to > clear it. > > Just did .. got rid of wpi, wpifw, firmware, recompile, reinstalled and got the same result: http://pastebin.com/f5933192d > > BTW: is there an easy way to unroll the patches so I get a pristine cop= y > > back and apply the patch over it again? Im asking because the 3rd chunk > > of your patch ( bge_reset(sc); ) didn't apply cleanly and I had to edit > > if_bge.c by hand to add that line in the right place. > > > > There is option -R in patch(1) so I think you can safely undo > applied patches if you have previous patch in your box. > > Did that .. cd /usr/src && patch -R < /path/to/patch It apllied like a charm :) > Still have no clue yet. This kind of debugging really need hardware > access to experiment various things but let's try narrow down > possible cause of problem. > I might be able to fix that if you really care about fixing this bug .. I can set you up a ssh account and give you root acces to this machine if you need to :) Just let me know ;) Best Regards Gonzalo Nemmi