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 799] data abort while reading from SD Cards
([EMAIL PROTECTED])
2. [Bug 1003] GSM modem is not powered down when Linux is shut
down ([EMAIL PROTECTED])
3. [Bug 1004] Dialer keypad is leaking memory on normal presses
([EMAIL PROTECTED])
4. [Bug 1004] Dialer keypad is leaking memory on normal presses
([EMAIL PROTECTED])
5. [Bug 1003] GSM modem is not powered down when Linux is shut
down ([EMAIL PROTECTED])
6. [Bug 788] Starting or stopping gsmd completely locks up the
Neo ([EMAIL PROTECTED])
7. [Bug 1005] U-boot passthrough does not work for current gsmd
([EMAIL PROTECTED])
8. [Bug 788] Starting or stopping gsmd completely locks up the
Neo ([EMAIL PROTECTED])
9. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
10. [Bug 1003] GSM modem is not powered down when Linux is shut
down ([EMAIL PROTECTED])
11. [Bug 788] Starting or stopping gsmd completely locks up the
Neo ([EMAIL PROTECTED])
12. [Bug 1003] GSM modem is not powered down when Linux is shut
down ([EMAIL PROTECTED])
13. [Bug 990] Missing libxod.tar.gz while building openmoko from
scratch ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=799
------- Additional Comments From [EMAIL PROTECTED] 2007-11-12 13:34 -------
U-Boot 1.2.0-moko9_r13_0_2632_0 is OK here with the bundled 512M Card, but i get
timeouts with a hama 2G Micro SD Card.
------- 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=1003
------- Additional Comments From [EMAIL PROTECTED] 2007-11-12 15:28 -------
I had tried this and there would be two problems with this script. First, the
later GSM firmware will fall into sleep mode, so we could not make sure if
"echo [EMAIL PROTECTED]" is successful or not each time. Besides each machine
should have
its specific power management so I think this part should be done in machine
plugin within gsmd. Second, "echo 0 > power_on" will cause kernel panic right
now, I still have no idea why. Actually, we don't need to do that , when system
power off, the pin will still be pulled low.
------- 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=1004
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
------- Additional Comments From [EMAIL PROTECTED] 2007-11-12 15:34 -------
Actually, the data->value also needs to be freed, so we will have to add a
custom function to free all the data.
------- 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=1004
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-11-12 16:37 -------
Sorry, I think I was confused by some valgrind output. Your patch was fine as
before.
------- 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=1003
------- Additional Comments From [EMAIL PROTECTED] 2007-11-13 03:46 -------
I cannot comment on the "sleep mode", but I vehemently disagree that this
power-off should be in gsmd. This is a phone, not a desktop device with
outboard peripherals with separate power supplies. When the user turns off the
phone, they expect that the GSM modem is also powered off, regardless of who
(gsmd or other) turned it on. Even if it was turned on by gsmd, gsmd has a
distressing tendency to segfault, which would end up leaving the modem turned on
as well. In fact, I argue that this power-off should be part of the kernel's
serial port power-off code, so that even if user-space is so totally botched
that no scripts can run, at least an effort is made to power-off the GSM modem.
Regarding the crashes, that sounds a lot like bug #788 to me - can you test if
one of the resolutions listed therein works, and if so, I guess bug #788 should
be associated with this one.
------- 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-11-13 03:50 -------
Respectfully, I disagree. The correct place to fix this is in the kernel, with
the posted kernel patches.
User-space commands, especially ones that are required to be issued in order to
make certain vital components functional, should NEVER cause the kernel to
crash.
------- 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=1005
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
URL| |http://lists.openmoko.org/pi
| |permail/openmoko-uboot/2007-
| |September/000125.html
Component|gsmd |u-boot
OS/Version|Linux |All
Platform|PC |Neo1973
------- Additional Comments From [EMAIL PROTECTED] 2007-11-13 04:18 -------
Reassigning to u-boot component as this is by no means a gsmd bug. It's a
problem in u-boot passthrough which will affect any serial port communication,
not only GSM. We proposed a fix back in Sept., which is posted at
http://lists.openmoko.org/pipermail/openmoko-uboot/2007-September/000125.html
with a bug description. It can also be worked around in gsmd (we have a patch)
but that's a wrong thing to do.
------- 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-11-13 04:36 -------
In my opinion. Both Mickey and Mike are right.
In the point of view of robust, phone service device should has a watchdog
scheme to monitor if gsmd is still working.
In the point of view of finding root cause, it's obviously something wrong in
kernel. And we should find out the root cause and release a kernel patch.
However, in the point of view of making whole project runs well, I think we
should put the Neo into a safe area, which let Neo can work well and that
further develop can go on, if we can, and mark all the bugs we found. Enlarge
the safe area step by step by solving each bug.
I think we can solving the issue with the following steps.
1. Since we know pull down the power pin will crash the system, we shall not
pull down this pin in the script. (For Neo's stability) (For not blocking
non-gsmd developers)
2. Phone service daemon shall monitor if gsmd is still alive.
3. Let gsmd work for the first initialization
4. Gsmd introduces timeout and error detection (handling) scheme. (For stability
and robust)
5. Fix the system hang bug from kernel. (For Kernel and GSMD developers)
6. Adding the pull pin scheme back to script if needed. (Enlarge the safe area)
All the error detection and handling schemes shall be left there, but warnings
and errors should be reported so that we have clues to solve them.
I may be wrong, it's just my opinion and proposal. How you guys think?
We can improve this together.
------- 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=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=847
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=864
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=881
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=882
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=888
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=933
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=961
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=978
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1003
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED]
Status|ASSIGNED |NEW
------- 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-11-13 05:56 -------
I think there's been some confusion, probably because there are just too many
comments on this bug - 28 of them.
This *IS* a bug in the kernel, it is well understood, and has been fixed. A
patch is attached to this bug, and is currently applied in OE. The patch has
not been accepted into the Openmoko svn repository, presumably because Harald
indicated that he would review this or do something with this.
I think the only thing preventing this bug from being closed is the review of
the patch, and acceptance of same into the openmoko svn tree.
------- 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=1003
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- 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=990
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|major |critical
------- 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
