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. Re: Openmoko Bug #1766: GSM Antenna Signal (Openmoko Public Trac)
2. Re: Openmoko Bug #1734: [Exposure] wifi show up "unknown"
(Openmoko Public Trac)
3. Re: Openmoko Bug #1813: Excessive enlightenment. CPU/syscalls
(Openmoko Public Trac)
4. Re: Openmoko Bug #1734: [settings] wifi show up "unknown"
(was: [Exposure] wifi show up "unknown") (Openmoko Public Trac)
5. Re: Openmoko Bug #1814: Broken mplayer package dependenties
(Openmoko Public Trac)
6. Re: Openmoko Bug #1809: buildhost builds incorrect qtopia-x11
image which is not ASU (Openmoko Public Trac)
7. Re: Openmoko Bug #1734: [settings] wifi show up "unknown"
(Openmoko Public Trac)
8. Re: Openmoko Bug #1622: bash -c crashes without $PWD
(Openmoko Public Trac)
--- Begin Message ---
#1766: GSM Antenna Signal
--------------------------------+-------------------------------------------
Reporter: dexteruk | Owner: zecke
Type: defect | Status: accepted
Priority: high | Milestone:
Component: Qtopia | Version: GTA02v6
Severity: normal | Resolution:
Keywords: GSM Antenna Signal | Blocking:
Blockedby: |
--------------------------------+-------------------------------------------
Comment(by sonicated):
queen6, can you tell me exactly which kernel you used from
buildhost.openmoko.org to fix this?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1766#comment:16>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1734: [Exposure] wifi show up "unknown"
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: marek
Type: defect | Status: in_testing
Priority: high | Milestone: Om2008.9
Component: Exposure | Version:
Severity: major | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Comment(by slozano):
I flashed the phone using NOR Flash and the Om_2008.8 page mentions to
flash using NAND, would this generate the WIFI unknown problem?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1734#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1813: Excessive enlightenment. CPU/syscalls
----------------------+-----------------------------------------------------
Reporter: alvieboy | Owner: openmoko-devel
Type: defect | Status: closed
Priority: normal | Milestone: Om2008.8
Component: unknown | Version: OM-2008.08
Severity: normal | Resolution: fixed
Keywords: | Blocking:
Blockedby: |
----------------------+-----------------------------------------------------
Changes (by raster):
* status: new => closed
* version: GTA02v5 => OM-2008.08
* resolution: => fixed
Comment:
ok. going to have to disagree. 6%?
here: not actually doing anything (like playing with the shelf or
launching apps or anything):
top - 09:34:51 up 4:51, 1 user, load average: 0.31, 0.28, 0.22
Tasks: 62 total, 1 running, 61 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.5%us, 0.8%sy, 0.0%ni, 98.7%id, 0.0%wa, 0.0%hi, 0.0%si,
0.0%st
Mem: 123920k total, 99176k used, 24744k free, 148k buffers
Swap: 0k total, 0k used, 0k free, 57708k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1732 root 20 0 2252 1100 888 R 1.1 0.9 0:01.50 top
5 root 15 -5 0 0 0 S 0.1 0.0 0:21.06 events/0
1408 root 20 0 16844 7588 4700 S 0.1 6.1 1:20.25 enlightenment
that's asu.dev (not 2008.08 - the e version etc. there is different, it
was not the release i prepared for asu but some earlier snap).
that's top with a poll interval of 10 seconds. so over 10 seconds, 0.1%
cpu... not 6. :(
secondly - stat() is an absolute must. that file can change. whenever data
is requested from a theme file - the file needs to be stat()ed before
being open()'d to see if the modified time has changed (and thus if the
internally cached data is to be used or to be dirtied and a new fresh off-
disk version be used). without that you will get stale cache entries.
example. in code you delete a file - .edj, .png, .jpg - doesn't matter
(.edj files are image file - they contain multiple images encoded in
sections), now you replace that with some new image (untarred, copied,
written - doesn't matter) and you then want to load it - but you loaded it
before you overwrote it so it's in cache. if you DONT stat(), you will not
get the changed/new image you wrote, but an old stale cache entry. so it's
not "stupid". it's necessary. just looking at strace without knowing what
the code does is not the greatest of things to do. (i see it all the
time!). also the walking of the usb stuff is the bluetooth status gadget -
it checks to find a bluetooth usb device and looks if it's powered on or
not - can't remember the poll interval but it is every few seconds. i
suspect that the version shipping in 2008.08 of illume/e simply doesn't
contain a lot of changes i made the week before release. it's possibly
some theme animation spinning that is doing things - but you can't see it
(thus the stat's), or something else, but i can't reproduce. e is nice and
dead quiet for me (see above and below). considering it handles a mountain
of stuff (from monitoring battery, gsm signal, the clock, bluetooth power
on/off, monitor for .desktop file changes, the launcher, window management
and all the window property changes, and client requests etc.).
also.. i get nowhere near the amount of activity compared to you:
[EMAIL PROTECTED]:~# time strace -c -p 1408
Process 1408 attached - interrupt to quit
Process 1408 detached
% time seconds usecs/call calls errors syscall
------ ----------- ----------- --------- --------- ----------------
45.87 0.002514 229 11 write
23.94 0.001312 55 24 gettimeofday
18.35 0.001006 59 17 1 read
11.84 0.000649 130 5 fcntl64
0.00 0.000000 0 15 5 open
0.00 0.000000 0 10 close
0.00 0.000000 0 17 ioctl
0.00 0.000000 0 5 munmap
0.00 0.000000 0 7 select
0.00 0.000000 0 5 mmap2
0.00 0.000000 0 1 stat64
0.00 0.000000 0 10 fstat64
0.00 0.000000 0 10 getdents64
0.00 0.000000 0 1 accept
0.00 0.000000 0 1 getpeername
------ ----------- ----------- --------- --------- ----------------
100.00 0.005481 139 6 total
real 0m 10.35s
user 0m 0.04s
sys 0m 0.16s
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1813#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1734: [settings] wifi show up "unknown"
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: marek
Type: defect | Status: in_testing
Priority: high | Milestone: Om2008.9
Component: Assassin | Version:
Severity: major | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Changes (by marek):
* component: Exposure => Assassin
Comment:
Please be more precise otherwise it is hard to help you.
What did you flash and how can you trigger the "wifi unknown problem" ?
The QA team provided a step by step instruction. If you _can't_ reproduce
this open another bug.
In general it does not matter how you flash but what you flash ...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1734#comment:11>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1814: Broken mplayer package dependenties
---------------------------------------------------------+------------------
Reporter: lock | Owner:
julian_chu
Type: defect | Status:
closed
Priority: normal | Milestone:
Component: Distro | Version:
Severity: normal | Resolution:
wontfix
Keywords: mplayer, libxv, libmp3lame0, broken package | Blocking:
Blockedby: |
---------------------------------------------------------+------------------
Changes (by marek):
* status: new => closed
* resolution: => wontfix
Comment:
buildhost.om.org (almost) builds OE upstream - this is VERY unstable. If
you want support for that, please contact Graeme.
The current buildhost setup will change soon to avoid future confusion.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1814#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1809: buildhost builds incorrect qtopia-x11 image which is not ASU
---------------------+------------------------------------------------------
Reporter: rwhitby | Owner: marek
Type: task | Status: accepted
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
---------------------+------------------------------------------------------
Changes (by marek):
* owner: graeme => marek
* priority: highest => normal
* status: assigned => accepted
* severity: critical => normal
* type: defect => task
Comment:
We are aware of this problem and are working on it. First we were focussed
on the release and now we can address the next issues. This confusion will
be fixed in the coming days.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1809#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1734: [settings] wifi show up "unknown"
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: marek
Type: defect | Status: in_testing
Priority: high | Milestone: Om2008.9
Component: Exposure | Version:
Severity: major | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Changes (by marek):
* component: Assassin => Exposure
Comment:
Sorry, don't know why it changed to Assassin.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1734#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1622: bash -c crashes without $PWD
-----------------------------------------------------------+----------------
Reporter: hah | Owner:
openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Resolution:
Keywords: bash segfault crash PWD ssh scp default shell | Blocking:
Blockedby: |
-----------------------------------------------------------+----------------
Comment(by hah):
'''Quick-fix script "/bin/bash-fixed", version 2:'''
{{{
#!/bin/sh
export PWD
if tty | grep -q '/dev/pts/'; then
exec /bin/bash --login "$@"
else
exec /bin/bash "$@"
fi
}}}
Previous version of the script did not start a proper login-shell.
Probably because argument zero is not passed to /bin/bash. From {{{man
bash}}}:
{{{
A login shell is one whose first character of argument
zero is a -, or one started with the --login option.
}}}
With the old script, PATH was not exported, causing opkg to segfault:
{{{
# opkg upgrade
Segmentation fault
}}}
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1622#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
