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 1309] gprs dialin responses "ERROR"
([EMAIL PROTECTED])
2. [Bug 1371] New: receiving nmea has errors when debug board is
connected ([EMAIL PROTECTED])
3. [Bug 1372] New: complete freeze of freerunner prottype #47
([EMAIL PROTECTED])
4. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
5. [Bug 1371] receiving nmea has errors when debug board is
connected ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1309
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2008-04-27 14:36 -------
found a workaround for this problem. issuing some at-command before the dialing
that already took place in another logical channel allows to dial as expected.
------- 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=1371
Summary: receiving nmea has errors when debug board is connected
Product: Neo1973 Hardware
Version: GTA02v4
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: GPS
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
i receive wrong nmea sentances with incorrect checksums. it seems that
null-bytes are inserted and/or characters are missing when the debugboard is
connected.
has someone else similar expiriences? did someone play around with gsp, nmea
with the debugboard connected?
------- 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=1372
Summary: complete freeze of freerunner prottype #47
Product: Neo1973 Hardware
Version: GTA02v4
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Core System
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
since 2 weeks or so i have complete freezes with my freerunner (prototype #47).
sometimes the device works for 2 days, sometime the crash comes minutes after
reboot. because i am activly developing my softwarestack the circumstances are
changing all the time. i use nearly the whole hardware in the neo:
- gsm with the muxer
- 2 channel for the gsmd
- 1 channel for steady on gprs
- gps
- udp over usb to the host for syslog
- grafic with evas with animation initiated by incomming messages
- sd card access for the underlaying database
i tried to not use one or more components to determine which component was the
cause of the failure but because i have to develop my software it is difficult
to say something deterministic about it.
- when the muxer is running in verbose mode, it logs more to syslog and the
freeze happened more often
- often the freeze happened when messages arrived which triggered animation and
stored on sd
- while my gpsd makes comparable high load, it seemed not to be involved
because in the office i don't use it and see freezes
i am completly lost and would be happy about any help on this issue. i am not an
hw guy and am helpless when using the debugboard (my first impressions see under
bug #1371 ).
------- 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 ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1371
------- Additional Comments From [EMAIL PROTECTED] 2008-04-28 10:27 -------
Someone should verify this with a debug board v3 and a pre-MP model.
------- 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
