[Sugar-devel] Wanting to know a bit of (NetworkManager) workflow upon resume-from-suspend

[Ajay Garg]

Hi Kevin.

Following are the steps and observations ::

a)
Booted with mesh-disabled (via "options libertas libertas_disablemesh=1").

b)
In Neighborhood-View, "wifi" and three "adhoc" network icons were present.

c)
Then, I turned wifi-radio off, discarded network history. Now, only
three "adhoc" network icons were present in Neighborhood-View.

d)
After some time, turned wifi-radio on. Now, "wifi" and three "adhoc"
network icons could be seen.

e)
Again, I turned wifi-radio off, discarded network history. Again, only
three "adhoc" network icons could be seen in Neighborhood-View.

f)
Rebooted.

g)
Only three "adhoc" network icons were seen in Neighborhood-View.

h)
After some time, turned wifi-radio on. Now, "wifi" and three "adhoc"
network icons could be seen in Neighborhood-View.


So, it works fine I guess (note that, mesh-icons were NOT seen anytime
in the above steps) :)


Regards,
Ajay

On Sat, May 5, 2012 at 6:43 PM, Kevin Gordon <kgordon420 at gmail.com> wrote:
>
>
> On Sat, May 5, 2012 at 6:26 AM, Ajay Garg <ajaygargnsit at gmail.com> wrote:
>>
>> Well,
>>
>> I tried once again the "Case 2"; and upon resume-from-suspend, the
>> icons appeared fine at my end.
>>
>> So, the problem was at my end.
>> So, it seems that nothing needs to be done right now.
>>
>> If I face the unusual result for "Case 2" again, I will post the
>> "/var/log/messages", which may be scrutinized.
>> If someone else faces the same, she/he may do the same.
>>
>> Till that time, I guess nothing needs to be done.
>
>
> Ajay:
>
> Since you've already installed the patch, could I be lazy and ask you a
> favour?   In the scenario where you have booted with mesh disabled, could
> you go over to the Sugar control/panel settings Network applet, turn the
> radio off,  discard network history, turn the radio back on, wait a bit, and
> see what icons appear in the neighbourhood view?
>
> Curious to see what happens here.  I'll do some more testing using this
> kernel/patch on both gnome and sugar next week, but thought if you had a few
> seconds I could get a 'head start' at looking at this situation.  If not, no
> big deal - what's done is already really neat!  Thanks.
>
> Cheers,
>
> KG
>
>>
>> Sorry Sascha, and everyone.
>>
>> Regards,
>> Ajay
>>
>> On Sat, May 5, 2012 at 2:15 PM, Martin Abente
>> <martin.abente.lahaye at gmail.com> wrote:
>> > just in case, did you try this combination:
>> >
>> > libertas(without the patch) + disable_mesh.sh(removed) +
>> > resume-from-suspend
>> > (?)
>> >
>> > IF NM still crashes then we have been looking in the wrong direction, if
>> > not
>> > then we need to look deeper into the patch probably (@silbe ;)).
>> >
>> >
>> > On Fri, May 4, 2012 at 10:20 PM, Ajay Garg <ajaygargnsit at gmail.com>
>> > wrote:
>> >>
>> >> On Sat, May 5, 2012 at 3:42 AM, Martin Abente
>> >> <martin.abente.lahaye at gmail.com> wrote:
>> >> > Did you remove the disable mesh.script for the testing?
>> >>
>> >> Yes.
>> >>
>> >> Both from ::
>> >>
>> >> a)
>> >> my custom added in '/etc/init.d/NetworkManager'.
>> >>
>> >> b)
>> >> '/etc/powed/postresume.d/disable_mesh.sh'
>> >>
>> >>
>> >> Regards,
>> >> Ajay
>> >> >
>> >> > El may 4, 2012 10:39 p.m., "Ajay Garg" <ajaygargnsit at gmail.com>
>> >> > escribió:
>> >> >>
>> >> >> On Sat, May 5, 2012 at 2:03 AM, Sascha Silbe
>> >> >> <silbe at activitycentral.com>
>> >> >> wrote:
>> >> >> > Ajay Garg <ajaygargnsit at gmail.com> writes:
>> >> >> >
>> >> >> > [...]
>> >> >> >> b)
>> >> >> >> Ensured that '/etc/modprobe.d/libertas.conf' contained only the
>> >> >> >> following line ::
>> >> >> >>
>> >> >> >>               options libertas libertas_disablemesh=0
>> >> >> > [...]
>> >> >> >> f)
>> >> >> >> Upon resume-from-suspend, NO ICONS COULD BE SEEN IN NEIGHBORHOOD
>> >> >> >> VIEW.
>> >> >> >
>> >> >> > Interesting.
>> >> >> >
>> >> >> >> g)
>> >> >> >> Observations e) and f) were observed, _every single time_.
>> >> >> >
>> >> >> > OK, I suppose you repeated this often enough and using exactly the
>> >> >> > same
>> >> >> > environment and procedures as the other test cases? I.e. you are
>> >> >> > sure
>> >> >> > that it's really specific to libertas_disablemesh=0 rather than
>> >> >> > just
>> >> >> > occurring at random even without the libertas_disablemesh setting
>> >> >> > or
>> >> >> > based on how the suspend / resume was triggered (e.g. idle suspend
>> >> >> > vs. lid or power switch)?
>> >> >>
>> >> >> I tried 3 times, and it happened every time. (I tried with the "lid"
>> >> >> approach every time, under identical conditions and set of
>> >> >> procedures.).
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> >
>> >> >> > I don't see anything in the patch or the module params code that
>> >> >> > would
>> >> >> > explain this behaviour. If it's reproducible, I'll have to dive
>> >> >> > into
>> >> >> > it
>> >> >> > and debug a bit...
>> >> >>
>> >> >> It is reproducible every time (at least at my end). :)
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> >
>> >> >> > Thanks for testing, BTW!
>> >> >>
>> >> >> My pleasure :)
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> >
>> >> >> > Sascha
>> >> >> >
>> >> >> > --
>> >> >> > http://sascha.silbe.org/
>> >> >> > http://www.infra-silbe.de/
>> >> >>
>> >> >>
>> >> >> Regards,
>> >> >> Ajay
>> >> >> _______________________________________________
>> >> >> Sugar-devel mailing list
>> >> >> Sugar-devel at lists.sugarlabs.org
>> >> >> http://lists.sugarlabs.org/listinfo/sugar-devel
>> >
>> >
>> _______________________________________________
>> Devel mailing list
>> Devel at lists.laptop.org
>> http://lists.laptop.org/listinfo/devel
>
>