Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Openmoko Bug #2321: any user can run wmiconfig -i eth0
--power maxperf (Openmoko Public Trac)
2. Re: Openmoko Bug #2320: icmp ping RTT over wifi plotted over
time forms a sawtooth wave (Openmoko Public Trac)
3. Re: Openmoko Bug #2320: icmp ping RTT over wifi plotted over
time forms a sawtooth wave (Openmoko Public Trac)
--- Begin Message ---
#2321: any user can run wmiconfig -i eth0 --power maxperf
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: low | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
I think
wmiconfig -i eth0 --power maxperf
should only work as root but it seems to have an effect even if I run it
as a normal user.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2321>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2320: icmp ping RTT over wifi plotted over time forms a sawtooth wave
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords: wifi latency kernel
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Comment(by lindi):
Ok, thanks! After ./wmiconfig -i eth0 --power maxperf I get
{{{
64 bytes from 192.168.2.1: icmp_seq=219 ttl=64 time=7.45 ms
64 bytes from 192.168.2.1: icmp_seq=220 ttl=64 time=15.2 ms
64 bytes from 192.168.2.1: icmp_seq=221 ttl=64 time=5.51 ms
64 bytes from 192.168.2.1: icmp_seq=222 ttl=64 time=5.48 ms
64 bytes from 192.168.2.1: icmp_seq=223 ttl=64 time=15.3 ms
64 bytes from 192.168.2.1: icmp_seq=224 ttl=64 time=10.2 ms
64 bytes from 192.168.2.1: icmp_seq=225 ttl=64 time=10.0 ms
64 bytes from 192.168.2.1: icmp_seq=226 ttl=64 time=11.3 ms
64 bytes from 192.168.2.1: icmp_seq=227 ttl=64 time=10.2 ms
64 bytes from 192.168.2.1: icmp_seq=228 ttl=64 time=15.3 ms
64 bytes from 192.168.2.1: icmp_seq=229 ttl=64 time=6.90 ms
64 bytes from 192.168.2.1: icmp_seq=230 ttl=64 time=14.7 ms
64 bytes from 192.168.2.1: icmp_seq=231 ttl=64 time=15.3 ms
64 bytes from 192.168.2.1: icmp_seq=232 ttl=64 time=10.2 ms
64 bytes from 192.168.2.1: icmp_seq=233 ttl=64 time=15.4 ms
64 bytes from 192.168.2.1: icmp_seq=234 ttl=64 time=10.1 ms
64 bytes from 192.168.2.1: icmp_seq=235 ttl=64 time=10.2 ms
64 bytes from 192.168.2.1: icmp_seq=236 ttl=64 time=10.2 ms
64 bytes from 192.168.2.1: icmp_seq=237 ttl=64 time=9.91 ms
64 bytes from 192.168.2.1: icmp_seq=238 ttl=64 time=10.1 ms
64 bytes from 192.168.2.1: icmp_seq=239 ttl=64 time=10.0 ms
64 bytes from 192.168.2.1: icmp_seq=240 ttl=64 time=10.2 ms
64 bytes from 192.168.2.1: icmp_seq=241 ttl=64 time=10.2 ms
64 bytes from 192.168.2.1: icmp_seq=242 ttl=64 time=6.56 ms
64 bytes from 192.168.2.1: icmp_seq=243 ttl=64 time=17.0 ms
64 bytes from 192.168.2.1: icmp_seq=244 ttl=64 time=14.1 ms
64 bytes from 192.168.2.1: icmp_seq=245 ttl=64 time=15.4 ms
64 bytes from 192.168.2.1: icmp_seq=246 ttl=64 time=10.2 ms
}}}
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2320#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2320: icmp ping RTT over wifi plotted over time forms a sawtooth wave
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords: wifi latency kernel
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Comment(by BillK):
I should have posted a link as well as its a standard - basic explanation
here:
"http://features.techworld.com/mobile-wireless/4103/a-guide-to-wi-fi-
power-save-technologies/"
Contrary to article, powersaving can be quite large (as it is in the
moko). Downside is not only the effects you noticed, but inability to
connect to some AP's, poor performance in general, poor(er) sensitivity in
low signal conditions and "odd things happening with the link :)"
Usually first thing I check when a laptop does not work well over wifi, as
it seems to often be the cause of the trouble.
BillK
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2320#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
