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 #2257: gsm0710muxd: "Modem does not respond to
AT commands" (Openmoko Public Trac)
2. Re: Openmoko Bug #2257: gsm0710muxd: "Modem does not respond
to AT commands" (Openmoko Public Trac)
3. Re: Openmoko Bug #2257: gsm0710muxd: "Modem does not respond
to AT commands" (Openmoko Public Trac)
4. Re: Openmoko Bug #2257: gsm0710muxd: "Modem does not respond
to AT commands" (Openmoko Public Trac)
5. Re: Openmoko Bug #2257: gsm0710muxd: "Modem does not respond
to AT commands" (Openmoko Public Trac)
6. Re: Openmoko Bug #2257: gsm0710muxd: "Modem does not respond
to AT commands" (Openmoko Public Trac)
7. Re: Openmoko Bug #2257: gsm0710muxd: "Modem does not respond
to AT commands" (Openmoko Public Trac)
8. Re: Openmoko Bug #2257: gsm0710muxd: "Modem does not respond
to AT commands" (Openmoko Public Trac)
9. Re: Openmoko Bug #2235: Monochrome display on resume
(Openmoko Public Trac)
--- Begin Message ---
#2257: gsm0710muxd: "Modem does not respond to AT commands"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
calypso/ttySAC0 seems to sometimes go to a state where even repeated
invocations of gsm0710muxd fail with "Modem does not respond to AT
commands". However, if I "echo 0 > power_on; sleep 3; echo 1 > power_on;
echo 1 > reset" I can use
{{{
socat - file:/dev/ttySAC0,crtscts,crnl,b115200
}}}
just fine to talk to the modem. After that also gsm0710muxd is able to
talk to it.
I am using gsm0710muxd abcbcd7cc532a8834906de3fc24c8f8fe7643cd4 and kernel
from andy-tracking c1b03e4da22e8dd7a6caccb9e39a9201535ced11
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2257>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2257: gsm0710muxd: "Modem does not respond to AT commands"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
This is reminding me of the overrun trac, the errors there went away when
the GSM firmware was updated to MOKO11 which operated the handshakes
properly. What's the patchlevel in the Calypso that's making this
problem?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2257#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2257: gsm0710muxd: "Modem does not respond to AT commands"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
I upgraded to gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko11b1
several weeks ago.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2257#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2257: gsm0710muxd: "Modem does not respond to AT commands"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
OK... on #2180 they also talk about 11beta1 making it go away.
On that bug though they had some kind of syslog or non-strace dump of the
serial traffic, it was possible to see the brokenness from that. Can you
maybe try to capture that?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2257#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2257: gsm0710muxd: "Modem does not respond to AT commands"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
In my case select always timeouts so gsm0710muxd does not even try to read
data from the serial port. Thus there is nothing to log, right?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2257#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2257: gsm0710muxd: "Modem does not respond to AT commands"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
Oh so it is never even able to get started even once?
Maybe the problem is about the delays in the selftimed modem startup stuff
added recently, such that the modem is not properly started: does it fit
your understanding of the problem?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2257#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2257: gsm0710muxd: "Modem does not respond to AT commands"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
Many times gsm0710muxd works after boot. However, sometimes it goes to a
state where even restarting gsm0710muxd won't be able to read anything
from the modem. I will revert into using known-to-work kernel
b8b36e5ec3db71d5 for a while. I'll report back after a week or so.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2257#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2257: gsm0710muxd: "Modem does not respond to AT commands"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
OK, thanks for reporting about it as always.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2257#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2235: Monochrome display on resume
-----------------------------+----------------------------------------------
Reporter: zeroedout | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: display, resume
Haspatch: 1 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by zeroedout):
Looks like the patch worked for my phone! Fixed with uImage-moredrivers-
GTA02_andy-tracking-5457a45a5d4ca2c3.bin Full colour after resume, yay!
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2235#comment:15>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
