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 #1315: xglamo: Performance decreases after a
while (Openmoko Public Trac)
3. Re: Openmoko Bug #1315: xglamo: Performance decreases after a
while (Openmoko Public Trac)
4. Re: Openmoko Bug #1315: xglamo: Performance decreases after a
while (Openmoko Public Trac)
5. Re: Openmoko Bug #1315: xglamo: Performance decreases after a
while (Openmoko Public Trac)
6. Openmoko Bug #1833: Getting rid of battery and usb useless
dbus related debug output (Openmoko Public Trac)
7. Re: Openmoko Bug #1833: Getting rid of battery and usb
useless dbus related debug output (Openmoko Public Trac)
8. Re: Openmoko Bug #1833: Getting rid of battery and usb
useless dbus related debug output (Openmoko Public Trac)
--- Begin Message ---
#1766: GSM Antenna Signal
-----------------------------------+----------------------------------------
Reporter: dexteruk | Owner: zecke
Type: defect | Status: in_testing
Priority: high | Milestone:
Component: Qtopia | Version: GTA02v6
Severity: normal | Resolution:
Keywords: GSM Antenna Signal | Blockedby:
Reproducible: | Blocking:
-----------------------------------+----------------------------------------
Comment(by hedora):
Dialing a number that doesn't start with * works. Opened new bug: #1832
-Rusty
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1766#comment:27>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1315: xglamo: Performance decreases after a while
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: Xfbdev (kdrive), Xglamo | Version: Om2008.8
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
----------------------------------------+-----------------------------------
Comment(by denver):
Is there some way I can log the commands sent by Xglamo? I am seeing this
bug periodically (more specifically I'm seeing #1296, but this is similar)
and I'd like to help debug it. Looking at the command log was suggested
by cjb on #openmoko.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1315#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1315: xglamo: Performance decreases after a while
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: Xfbdev (kdrive), Xglamo | Version: Om2008.8
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
----------------------------------------+-----------------------------------
Comment(by zecke):
Well, the log will be quite big and you would need the exact point where
things got wrong. So currently the most wanted thing is an easy way to
reproduce this.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1315#comment:13>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1315: xglamo: Performance decreases after a while
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: Xfbdev (kdrive), Xglamo | Version: Om2008.8
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
----------------------------------------+-----------------------------------
Comment(by denver):
Here are some more details on the specific problem I am encountering:
When running a recently-updated 2007.2 build, the device becomes
unresponsive to touchscreen taps after a few hours of being on (the exact
number of hours varies). This seems to occur at random; it even occurs
when there is no apparent activity on the unit (screen has not been
updated and touchscreen has not being pressed for several minutes). The
unit still responds to SSH while unresponsive to the touchscreen. Running
top shows that Xglamo is consuming a lot of CPU (presumably spinning).
After a few minutes (about 5), Xglamo stops consuming CPU. The unit will
then respond with an audible click when pressing the touchscreen (and the
screen turns on if dimmed), but Xglamo immediately starts hogging the CPU
again and the screen becomes unresponsive. After a few minutes, Xglamo
stops hogging the CPU again and the cycle continues.
Even if one does not press the touchscreen once Xglamo stops hogging the
CPU, Xglamo can start spinning again at random. Again, it will stop
hogging the CPU after a few minutes but starts spinning immediately after
the touchscreen is pressed.
The problem can be corrected by stopping and starting the X server.
However, you must either send Xglamo a SIGKILL or wait for it to stop
spinning (at which point it exits) following "/etc/init.d/xserver-nodm
stop".
Attaching to Xglamo with gdb while it's spinning tends to show Xglamo in
gettimeofday or GLAMOEngineWait, much like in the gdb output of comment 6.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1315#comment:14>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1315: xglamo: Performance decreases after a while
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: Xfbdev (kdrive), Xglamo | Version: Om2008.8
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
----------------------------------------+-----------------------------------
Comment(by denver):
zecke: It depends what you mean by reproducible. As you can see in my
problem description, Xglamo stops spinning for a while and then starts
again when you press the touchscreen. So activating the spinning is
reproducible. If there's an easy way to turn on logging after the initial
spinning, then I can get a concise log around the point where it starts
spinning again. But if you need me to run a modified Xglamo binary that
has logging turned on all the time, then the reproducibility I have
doesn't help much. Hopefully there will be a way to turn on the logging
while Xglamo is running.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1315#comment:15>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1833: Getting rid of battery and usb useless dbus related debug output
-----------------------+----------------------------------------------------
Reporter: LeRoutier | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Keywords:
Blockedby: | Reproducible:
Blocking: |
-----------------------+----------------------------------------------------
Both matchbox's applets for USB and Battery fill logs because of the way
they handle DBus messages.
They recieve messages from everyone, not only for the waited Interface.
So, each time a Hal or Freesmartphone or whatever dbus message arrives,
they put a "Unknown dbus message, ignoring" in /tmp/x.log, making it
useless.
The following patches would limit the noise.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1833>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1833: Getting rid of battery and usb useless dbus related debug output
--------------------------+-------------------------------------------------
Reporter: LeRoutier | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
--------------------------+-------------------------------------------------
Comment(by LeRoutier):
To be more precise, for each unknown dbus message, we had :
** (matchbox-panel-2:1542): DEBUG: battery_applet: signal_filter
** (matchbox-panel-2:1542): DEBUG: (unknown dbus message, ignoring)
** (matchbox-panel-2:1542): DEBUG: usb_applet: signal_filter
** (matchbox-panel-2:1542): DEBUG: (unknown dbus message, ignoring)
in /tmp/x.log
Whatever the source or dest of the message was
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1833#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1833: Getting rid of battery and usb useless dbus related debug output
--------------------------+-------------------------------------------------
Reporter: LeRoutier | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
--------------------------+-------------------------------------------------
Comment(by LeRoutier):
Please note that openmoko-dialer2 (phone-kit) needs the same kind of love
:
if ( !g_strcmp0( dbus_message_get_interface(msg),
"org.openmoko.PhoneKit.Headset" ) ) { ... }
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1833#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
