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. [Bug 788] Starting or stopping gsmd completely locks up the
      Neo ([EMAIL PROTECTED])
   2. [Bug 788] Starting or stopping gsmd completely locks up the
      Neo ([EMAIL PROTECTED])
   3. [Bug 805] New: lgsm_get_signal_quality() defined but not
      implemented ([EMAIL PROTECTED])
   4. [Bug 758] libmokogsmd2 doesn't handle CB and DS events
      ([EMAIL PROTECTED])
   5. [Bug 758] libmokogsmd2 doesn't handle CB and DS events
      ([EMAIL PROTECTED])
   6. [Bug 784] webkit build fails
      ([EMAIL PROTECTED])
   7. [Bug 802] openmoko-dialer2 segfaults when first digit entered
      is '#' ([EMAIL PROTECTED])
   8. [Bug 729] in Call History Mode there is no time/date info
      ([EMAIL PROTECTED])
   9. [Bug 731] sending numbers with DTMF
      ([EMAIL PROTECTED])
  10. [Bug 781] LM4857 should be turned off on a reboot notifier
      ([EMAIL PROTECTED])
  11. [Bug 709] headset.state file missing, needed for headphone
      output ([EMAIL PROTECTED])
  12. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
  13. [Bug 766] gsmd misbehaves on back-to-back AT+CFUN=1/AT+COPS=0
      ([EMAIL PROTECTED])
  14. [Bug 766] gsmd misbehaves on back-to-back AT+CFUN=1/AT+COPS=0
      ([EMAIL PROTECTED])
  15. [Bug 789] Occasional phone crash on X startup
      ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=788





------- Additional Comments From [EMAIL PROTECTED]  2007-09-07 12:34 -------
I altered my /etc/init.d/gsmd script as suggested to prevent the modem being
powered down, but I still experience the original issue when running gsmd 
restart.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=788





------- Additional Comments From [EMAIL PROTECTED]  2007-09-07 13:43 -------
Chris, 
Could you explain what you think usb has to do with it ?
I would have though it was only an UART related issue.

>I altered my /etc/init.d/gsmd script as suggested to prevent the modem being
>powered down, but I still experience the original issue when running gsmd 
>restart.

Yes, that's definately not a fix for this issue, it's more a "half working
workaround" ;-)

Cheers,

Fabien




------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=805

           Summary: lgsm_get_signal_quality() defined but not implemented
           Product: OpenMoko
           Version: current svn head
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libgsmd
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


The lgsm_get_signal_quality() function is defined in libgsmd/misc.h but it is
not implemented anywhere.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=758

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|[EMAIL PROTECTED]        |[EMAIL PROTECTED]
          Component|libgsmd                     |openmoko-libs





------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=758





------- Additional Comments From [EMAIL PROTECTED]  2007-09-07 16:54 -------
Please attach patches to bugzilla by using the "Create a New Attachment" feature
and marking the attachement as a patch.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=784

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From [EMAIL PROTECTED]  2007-09-07 17:43 -------
This turned-out to be an issue with the build-tree. "touch"ing the bitbake
recipe file (e.g. openembedded/packages/webkit/webkit-gtk_svn.bb) solved the
problem for this and other packages, as well as doing make
clean-package-<package> for failing packages.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=802





------- Additional Comments From [EMAIL PROTECTED]  2007-09-07 18:04 -------
It's very repeatable, even immediately after a reboot.

Unfortunately I don't see any logs that might shed more light on the situation.
 All I get on the terminal display -- if I happened to have restarted
openmoko-dialer from there -- is the segfault message.  And I should add,
sometimes it takes other things down with it, such as the Window Manager.

I have seen a lot of check-ins on the dialer lately, so I'll verify again after
I'm able to upgrade it.  (I haven't been able to complete a build in the last
couple of days, I think because of ${SRCREV} gremlins.)



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=729

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |REMIND



------- Additional Comments From [EMAIL PROTECTED]  2007-09-07 18:15 -------
Would be nice, but I am not sure there is much space to add that information
into the list.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=731

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |LATER



------- Additional Comments From [EMAIL PROTECTED]  2007-09-07 18:17 -------
This would only work if the receiver also has an OpenMoko based phone, which
would probably not be the case most of the time. To be honest, I can't see this
as a very useful feature, so marking as LATER in case anyone wants to implement
it for another version of the software.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=781





------- Additional Comments From [EMAIL PROTECTED]  2007-09-07 20:09 -------
Created an attachment (id=276)
 --> 
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=276&action=view)
some changes about Alex's patch

Hi Alex,

Thanks for your advice. According to i2c_driver structure, I modify your patch.
The lm4857_suspend and lm4857_shutdown can be executed. :)

I test our neo1973 steps (shutdown mode)as follows
1. Cut off power for GSM. So GSM module can't work.
2. Power on GTA01, then enter into x-windows and press menu item "power off".
3. This time, power supply displays 0 mV.

Another test steps (suspend/resume mode) as follows
1. Cut off power for GSM. So GSM module can't work.
2. Power on GTA01, then enter into x-windows and press menu item "lock phone".
3. This time, power supply displays 39.6 mV.
4. Then press power key, and resume the neo1973. 

I think our neo1973 in suspend mode wastes a lot of power. But it's another
issue.




------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=709

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From [EMAIL PROTECTED]  2007-09-07 23:11 -------
Confirmed, sound now switches between speakers and headphones as I would expect.




------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla 
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.

All of these bugs are in the NEW state, and have not been touched
in 7 days or more.  You need to take a look at them, and 
decide on an initial action.

Generally, this means one of three things:

(1) You decide this bug is really quick to deal with (like, it's INVALID),
    and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
    else.  (Hint: if you don't know who to reassign it to, make sure that
    the Component field seems reasonable, and then use the "Reassign bug to
    owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
    Just use the "Accept bug" command.

To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):

    
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL 
PROTECTED]

Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.

Appended below are the individual URLs to get to all of your NEW bugs that 
haven't been touched for a week or more.

You will get this message once a day until you've dealt with these bugs!

  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=41
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=69
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=112
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=114
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=129
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=141
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=181
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=276
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=301
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=340
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=448
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=466
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=555
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=572
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=589
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=624
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=630
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=661
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=675
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=696
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=714
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=727
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=742



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=766





------- Additional Comments From [EMAIL PROTECTED]  2007-09-08 07:09 -------
Created an attachment (id=277)
 --> 
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=277&action=view)
Patch to work around this issue

This patch makes registering work even if you send the O/r commands as fast as
possible:

echo -e 'O\nr' | libgsmd-tool -m shell

It, however, is still not enough to prevent gsmd from being confused by
something else; I still have to kill gsmd (or wait for its alive timer to
expire) and start it again in a non-confused state before testing.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=766





------- Additional Comments From [EMAIL PROTECTED]  2007-09-08 07:57 -------
I think I understand now why does gsmd submit two commands back-to-back, even
when there's a break on atcmd_select_cb() commented as /* we only send one cmd
at the moment */, which should make it send only one command at a time.

After the break, select() is told to not generate a write event on the socket:

/* Either pending_atcmds is empty or a command has to wait */
g->gfd_uart.when &= ~GSMD_FD_WRITE;

However, g->pending_atcmds is now empty (the command was moved from it to
g->busy_atcmds just before the break). When it is empty, atcmd_submit() enables
GSMD_FD_WRITE, which makes the command be sent immediately, without waiting for
the command to receive its response.

So, if we want to enforce one-command-at-a-time behaviour for every command, we
should also check for llist_empty(&g->busy_atcmds) on atcmd_submit() (the patch
I attached to this bug should not be needed then). I will test it later today.


While looking at this, I found another potential bug: the return value for the
write(fd, "\r", 1) on atcmd_select_cb() is never checked, which could result on
a CR being dropped on a short write.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=789

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE



------- Additional Comments From [EMAIL PROTECTED]  2007-09-08 10:37 -------
triggered by gsmd restart via xsession

*** This bug has been marked as a duplicate of 788 ***



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog

Reply via email to