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 1150] OE don' t create root image with ext3 FS on AMD64
([EMAIL PROTECTED])
2. [Bug 1152] openmoko-terminal2 is missing vala dependancy
([EMAIL PROTECTED])
3. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
4. [Bug 1152] openmoko-terminal2 is missing vala dependancy
([EMAIL PROTECTED])
5. [Bug 1154] New: gsmd at 100% CPU (sigsegv-handling problem)
([EMAIL PROTECTED])
6. [Bug 1117] Call forwading support
([EMAIL PROTECTED])
7. [Bug 1152] openmoko-terminal2 is missing vala dependancy
([EMAIL PROTECTED])
8. [Bug 1149] Incoming calls work perfectly, but outgoing calls
silently fail. ([EMAIL PROTECTED])
9. [Bug 1152] openmoko-terminal2 is missing vala dependancy
([EMAIL PROTECTED])
10. [Bug 1154] gsmd at 100% CPU (sigsegv-handling problem)
([EMAIL PROTECTED])
11. [Bug 1152] openmoko-terminal2 is missing vala dependancy
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1150
------- Additional Comments From [EMAIL PROTECTED] 2008-01-02 18:15 -------
option go on if i modify:
IMAGE_ROOTFS_SIZE_ext2=102400 for ext2
I see for ext3 i must define
IMAGE_ROOTFS_SIZE_ext3=102400
Many thanks!
------- 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=1152
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED],
| |[EMAIL PROTECTED]
------- Additional Comments From [EMAIL PROTECTED] 2008-01-02 19:24 -------
Good question -- John and Graeme, what's your opinion on that?
------- 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=934
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=935
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
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1152
------- Additional Comments From [EMAIL PROTECTED] 2008-01-03 05:11 -------
2 situations I could think of should be reported here at OM bugzilla:
1. bugs introduced by modifications only on OM mtn.
2. OM mtn cannot build on a particular system.
3. (please add if I missed)
The rest should be directed to OE and get fixed there.
Including moko-autorev.inc often introduces new revs that depend on the later
version of OE. These problems will be fixed on next sync and personnally I
won't fix them between syncs.
------- 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=1154
Summary: gsmd at 100% CPU (sigsegv-handling problem)
Product: OpenMoko
Version: current svn head
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: gsmd
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
A few times now I have seen my recent MokoMakefile-built gsmd (package version
0.1+svnr3759-r40) get stuck at 100% CPU. I ran 'strace -p' on its PID and saw
lots of the following:
Process 2353 attached - interrupt to quit
--- SIGSTOP (Stopped (signal)) @ 0 (0) ---
--- SIGSTOP (Stopped (signal)) @ 0 (0) ---
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn() = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn() = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn() = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn() = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn() = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn() = ? (mask now [])
The gsmd.c code calls "signal(SIGSEGV, sig_handler);" (along with 4 other
signals), but the switch statement in the sig_handler() function does not have a
case for SIGSEGV. I do not know what initially triggered the problem, but it
looks like an un-handled segfault is causing the 100%-CPU looping.
------- 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=1117
------- Additional Comments From [EMAIL PROTECTED] 2008-01-03 10:11 -------
Created an attachment (id=469)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=469&action=view)
2nd try Call Forwarding
as title
------- 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=1152
------- Additional Comments From [EMAIL PROTECTED] 2008-01-03 10:19 -------
So basically, I should not be using monotone.openmoko.org for development work?
------- 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=1149
------- Additional Comments From [EMAIL PROTECTED] 2008-01-03 10:38 -------
Thanks a lot, Andrew!
if possible, please try to follow these scenario:
1. Use other phone to call your NEO
2. When you see the incoming call page, press 'Hangup'!
3. Then, dial out a phone call by NEO
4. Do you see any outgoing call page? Do you receive this phone call?
5. if it's still not working, could you upload gsm.log to bugzilla again?
we really appreciate your kindly helps! :)
------- 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=1152
------- Additional Comments From [EMAIL PROTECTED] 2008-01-03 10:51 -------
If monotone.om.org tree doesnt build then bug should be reported here. John can
then investigate and esculate to bugs.oe.org if it turns out failure is from OE
upstream.
Bugs against mtn.om.org should be rare as the build is checked before update.
So Thomas you should be using mtn.om.org for app development.
------- 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=1154
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED]
------- 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=1152
------- Additional Comments From [EMAIL PROTECTED] 2008-01-03 11:47 -------
If we want to use OM mtn for development, the policy should be clear that ALL OM
related packages cannot commit code that depends on upstream OE instead of OM
mtn. There's no way we could maintain a stable daily build if we keep changing
the outside dependency.
------- 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
