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 1380] GSM modem sleeps on virtual channels in MUX
([EMAIL PROTECTED])
2. [Bug 1289] PSC (power saving commands in muxer mode) seems to
be broken ([EMAIL PROTECTED])
3. [Bug 1383] GSM functions fail after several hours
([EMAIL PROTECTED])
4. [Bug 1195] gsmd can't pass pressure testing
([EMAIL PROTECTED])
5. [Bug 958] GSM modem dead ([EMAIL PROTECTED])
6. [Bug 562] gsmd init script causes sysrq message
([EMAIL PROTECTED])
7. [Bug 707] modem/gsmd does not start in a reliable way (if at
all) on boot ([EMAIL PROTECTED])
8. [Bug 705] gsmd does not process responses from the modem
([EMAIL PROTECTED])
9. [Bug 1192] unknown reason cause TI GSM modem always return
"+CME ERROR: 512" ([EMAIL PROTECTED])
10. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1380
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|critical |normal
Status|ASSIGNED |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From [EMAIL PROTECTED] 2008-05-19 14:38 -------
For the records, EOF (\x1a) seems to also wakeup the modem and in contrast to
\r\n, it does not emit an 'OK' if the modem is already woken up.
With that and a global modem communication timestamp, I think we can settle this
issue. Since I'm pretty sure that no one inside Openmoko nor TI will attempt to
fix this properly (see #1289), I will now close this as WONTFIX and limit the
severity since we have a workaround.
------- 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=1289
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From [EMAIL PROTECTED] 2008-05-19 14:48 -------
I agree that there is a bug and I follow your analysis, Michael. Unfortunately,
this seems to be a limitation of the TI Calypso firmware and since this product
is end-of-life, we will not see a fix for it. Therefore, I'm closing this as
WONTFIX.
------- 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=1383
------- Additional Comments From [EMAIL PROTECTED] 2008-05-19 14:51 -------
We need to reproduce this in MUXing mode. Please test and report again with the
first framework-testing image (due to release in early June).
------- 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=1195
------- Additional Comments From [EMAIL PROTECTED] 2008-05-19 14:52 -------
This needs to be reproduced in MUXing mode. Since gsmd is phasing out, we better
test this with the framework-testing image (due to release early June).
------- 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=958
------- Additional Comments From [EMAIL PROTECTED] 2008-05-19 14:53 -------
Ever since starting to operate the modem in MUXing mode, I could no longer see
this behaviour. I'm tempted to close it as FIXED, if no one objects.
------- 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=562
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2008-05-19 14:55 -------
Keeping the kernel console quiet seems to fix this condition where we switch the
state of the multiplexed port. I consider this being FIXED.
------- 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=707
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2008-05-19 14:57 -------
In MUXing mode, this will be a non-issue, since the multiplexer can and does a
reset on activation. I consider this being FIXED then.
------- 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=705
Bug 705 depends on bug 707, which changed state.
Bug 707 Summary: modem/gsmd does not start in a reliable way (if at all) on boot
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=707
What |Old Value |New Value
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- 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=1192
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From [EMAIL PROTECTED] 2008-05-19 20:56 -------
Ok, I just managed to get to this state again. I did multiple sequences of
at+cops=? followed by cancelling (sending any other character) the command. It
seems the AT interpreter or firmware state machine inside the modem just hangs
somewhere undefined.
Additional remarks:
* There does not seem to be a concrete way to trigger this state. It seems
unrelated to any sequence of commands. It's just that commands with long
execution time seem to trigger it more often.
* It also happens in MUXing mode and it only renders one channel unusable. The
other channels still work as expected.
* There does not seem a way to recover from this state. Even closing and
reopening the virtual channel does not fix the problem. Even waiting one hour
does not fix the problem. The only way to recover is doing a modem power cycle.
Since the TI Calypso is end-of-life it's highly unlikely that someone will look
into this problem. Since it occurs very rare and also can be detected by a good
parser (which could then transparently trigger the modem power cycle), I'll
close this as WONTFIX.
------- 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=1012
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1081
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1107
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1127
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1133
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1136
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1158
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1162
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1189
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1193
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1197
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1199
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1200
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1201
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1206
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1212
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1215
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1216
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1217
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1218
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1276
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1292
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
