Date: Tue, 17 Nov 2009 19:17:41 -0200 From: Gonzalo Nemmi <gnemmi@gmail.com> To: pyunyh@gmail.com Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: Call for bge(4) testers Message-ID: <200911171917.41906.gnemmi@gmail.com> In-Reply-To: <20091117193208.GI1262@michelle.cdnetworks.com> References: <20091111223751.GE15449@michelle.cdnetworks.com> <200911171650.06834.gnemmi@gmail.com> <20091117193208.GI1262@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 BTW: is there an easy way to unroll the patches so I get a pristine copy=20 back and apply the patch over it again? Im asking because the 3rd chunk=20 of your patch ( bge_reset(sc); ) didn't apply cleanly and I had to edit=20 if_bge.c by hand to add that line in the right place. Still willing to keep on trying and awaiting orders :) Best Regards Gonzalo Nemmi > > in there, I found there are problems resuming umass devices as > > well ... ) > > Probably Hans can help you on USB issues. > > > Line 42 to 53 correspond to "kldnuload if_bge" .. which, by the > > way, once unloaded, I could load it again but bge0 never showed on > > "ifconfig". > > > > Line 54 till the end correspond to "umount_msdos /dev/ad0s1" ... > > which ended with pulling the pendrive out as the system coldn't > > umount it ... > > > > I also found I get wpi0 messages on resume .. it spouts: > > wpi0 could not lock memory > > wpi0 could not lock memory > > wpi0 could not lock memory > > wpi0 could not lock memory > > wpi0 could not lock memory > > wpi0 could not lock memory > > wpi0 could not lock memory > > and then it let's the system resume. > > Don't know what it really means. You'd be better to ask wpi(4) > author Benjamin Close(benjsc@). > > > All in all .. there's _a_lot_of_problems_on_resume_ > > > > > > Pyun, if you'd like me to try a new patch or to do some tests or > > whatever, just let me know. I'm here awaiting orders :) > > > > Best Regards > > Gonzalo Nemmi =2D-=20 Blessings Gonzalo Nemmi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200911171917.41906.gnemmi>