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 789] New: Occasional phone crash on X startup
([EMAIL PROTECTED])
2. [Bug 790] New: system clock not reset on resume
([EMAIL PROTECTED])
3. [Bug 788] Starting or stopping gsmd completely locks up the
Neo ([EMAIL PROTECTED])
4. [Bug 704] /etc/init.d/gsmd kills self.
([EMAIL PROTECTED])
5. [Bug 788] Starting or stopping gsmd completely locks up the
Neo ([EMAIL PROTECTED])
6. [Bug 788] Starting or stopping gsmd completely locks up the
Neo ([EMAIL PROTECTED])
7. [Bug 788] Starting or stopping gsmd completely locks up the
Neo ([EMAIL PROTECTED])
8. [Bug 770] Battery discharging while phone is off (GSM part)
([EMAIL PROTECTED])
9. [Bug 791] New: webkit-gtk won't link
([EMAIL PROTECTED])
10. [Bug 791] webkit-gtk won't link
([EMAIL PROTECTED])
11. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
12. [Bug 53] DTMF tones during call
([EMAIL PROTECTED])
13. [Bug 205] add code to u-boot to query hardware revision and
serial number from GSM Modem ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=789
Summary: Occasional phone crash on X startup
Product: OpenMoko
Version: current svn head
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: critical
Priority: P2
Component: kernel
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Hi,
For an unknown reason, my Neo would occasionally crash during X startup (either
after phone reboot, or after manual X server restart).
The only way to reboot the phone is to to a long press on the power key, or to
remove the battery.
The issue is not systematic, but I get the issue once every 4 to 5 times i start
the X server.
I have no idea how i can provide more precise information, if there is anything
i can do to help just let me know ;-)
Kernel and root image have just been rebuilt from head SVN and head mtn
repositories.
regards,
Fabien
------- 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=790
Summary: system clock not reset on resume
Product: OpenMoko
Version: 2007.2
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P3
Component: kernel
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
after a successful suspend/resume cycle the system clock is still at the suspend
time. Executing 'hwclock --hctosys' via a shell fixes this, so the hardware
clock is fine, it's just that the kernel needs to update the system clock from
hardware on resume.
------- 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-09-02 13:35 -------
Hi Mike,
Looks like this bug is a regression introduced by the rewriting of gsmd init
script (see bug #704)
Cheers,
Fabien
------- 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=704
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #269 is|0 |1
obsolete| |
------- Additional Comments From [EMAIL PROTECTED] 2007-09-02 17:34 -------
(From update of attachment 269)
Other than pulseaudio gsmd does not go into daemonmode. So '-b' must be added
or we stick with '&' - there will be no valid $? anyway.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
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
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
------- Additional Comments From [EMAIL PROTECTED] 2007-09-02 20:38 -------
Stopping a hand-started foreground gsmd (after the previous one quit due to the
alive timer timeout) with Ctrl-C also completely locked up my Neo. So, I'd guess
it's not the powering off of the modem, but the killing of the gsmd that's
locking up the Neo.
------- 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-09-02 20:52 -------
More details on the issue:
In fact neo crashes during gsmd init script stop.
The line that triggers neo crashes is :
echo "0" > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on
I managed to reproduce it quite reliably doing the folloging:
echo "1" > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on
start gsmd
stop gsmd
echo "0" > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on
The funny thing is that if gsmd is not started and stopped (step 2 and 3), then
the 4th step does not trigger the crash.
I attached the debug board and did a bt to see where we are:
(gdb) target remote localhost:3333
Remote debugging using localhost:3333
warning: shared library handler failed to enable breakpoint
s3c24xx_serial_console_putchar (port=0xc033b080, ch=48) at
drivers/serial/s3c2410.c:1706
1706 ufstat = rd_regl(port, S3C2410_UFSTAT);
(gdb) l
1701 unsigned long ufstat, utrstat;
1702
1703 if (ufcon & S3C2410_UFCON_FIFOMODE) {
1704 /* fifo mode - check ammount of data in fifo
registers... */
1705
1706 ufstat = rd_regl(port, S3C2410_UFSTAT);
1707 return (ufstat & info->tx_fifofull) ? 0 : 1;
1708 }
1709
1710 /* in non-fifo mode, we go and use the tx buffer empty */
(gdb) bt
#0 s3c24xx_serial_console_putchar (port=0xc033b080, ch=48) at
drivers/serial/s3c2410.c:1706
#1 0xc01851bc in uart_console_write (port=0xc033b080,
s=0xc034cfa3 "gta01-pm-gsm gta01-pm-gsm.0: powered down GSM, thus enabhling
seial console\n", count=76,
putchar=0xc018829c <s3c24xx_serial_console_putchar>) at
drivers/serial/serial_core.c:1785
#2 0xc01888d0 in s3c24xx_serial_console_write (co=<value optimized out>, s=0x30
<Address 0x30 out of bounds>,
count=520) at drivers/serial/s3c2410.c:1729
Cannot access memory at address 0xe89da7fc
(gdb)
Does any experienced (==> not me ;-) ) kernel hacker see where that could come
from ?
Cheers,
Fabien
------- 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-09-02 21:16 -------
Yet again some more precisions.
This time i had to add a fifth step : echo "1" > .....
to be able to crash the phone.
openocd gives me:
(gdb) target remote localhost:3333
Remote debugging using localhost:3333
warning: shared library handler failed to enable breakpoint
0xc01882f0 in s3c24xx_serial_console_putchar (port=0xc033b080, ch=97) at
drivers/serial/s3c2410.c:1720
1720 while (!s3c24xx_serial_console_txrdy(port, ufcon))
(gdb) bt
#
Looks like we're busy looping on calling the s3c24xx_serial_console_txrdy that
never returns true !!
------- 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=770
------- Additional Comments From [EMAIL PROTECTED] 2007-09-02 21:21 -------
Didn't make any progress, due to bug #788 insisting on crashing my phone.
My 0.02 cents about layering violation concerns:
It looks like the gsmd init scripts is responsible for power management, so we
have either to make the init script aware of AT commands or the gsmd aware of
power management: i don't know which is the worst ;-)
Cheers,
Fabien
------- 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=791
Summary: webkit-gtk won't link
Product: OpenMoko
Version: 2007.2
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-webbrowser
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
A couple of days ago, trying a build of open-moko-devel-image began failling
with the following:
|
/home/pfeiffer/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/lib/libicui18n.so:
undefined reference to `operator delete(void*)@GLIBCXX_3.4'
|
/home/pfeiffer/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/lib/libicui18n.so:
undefined reference to `vtable for __cxxabiv1::[EMAIL PROTECTED]'
|
/home/pfeiffer/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/lib/libicui18n.so:
undefined reference to [EMAIL PROTECTED]'
|
/home/pfeiffer/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/lib/libicui18n.so:
undefined reference to [EMAIL PROTECTED]'
|
/home/pfeiffer/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/lib/libicui18n.so:
undefined reference to `vtable for __cxxabiv1::[EMAIL PROTECTED]'
|
/home/pfeiffer/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/lib/libicui18n.so:
undefined reference to `vtable for __cxxabiv1::[EMAIL PROTECTED]'
|
/home/pfeiffer/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/lib/libicui18n.so:
undefined reference to [EMAIL PROTECTED]'
| collect2: ld returned 1 exit status
| make[2]: *** [../testkjs] Error 1
| make[2]: Leaving directory
`/home/pfeiffer/openmoko/build/tmp/work/armv4t-angstrom-linux-gnueabi/webkit-gtk-0.0+svn20070902-r1/WebKitBuilds/Debug/JavaScriptCore/kjs'
| make[1]: *** [sub-JavaScriptCore-kjs-testkjs-pro-make_default-ordered] Error 2
| make[1]: Leaving directory
`/home/pfeiffer/openmoko/build/tmp/work/armv4t-angstrom-linux-gnueabi/webkit-gtk-0.0+svn20070902-r1/WebKitBuilds/Debug'
| FATAL: oe_runmake failed
NOTE: Task failed:
/home/pfeiffer/openmoko/build/tmp/work/armv4t-angstrom-linux-gnueabi/webkit-gtk-0.0+svn20070902-r1/temp/log.do_compile.25391
NOTE: package webkit-gtk-0.0+svn20070902-r1: task do_compile: failed
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
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=791
------- Additional Comments From [EMAIL PROTECTED] 2007-09-03 00:51 -------
A few days ago, gcc was upgraded in the openembedded tree. Try nuking the whole
build (make clobber or rm -rf build/tmp) and starting from scratch.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
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=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=589
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=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=742
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=53
------- Additional Comments From [EMAIL PROTECTED] 2007-09-03 07:47 -------
Using the 2nd tab during a call would be great, but (on my device: GTA01BV4 w/
20070831 kernel+rootfs snapshot image) pressing the number buttons does not
send a tone.
------- 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=205
------- Additional Comments From [EMAIL PROTECTED] 2007-09-03 11:38 -------
Using AT+CGMR can get the info, so try to send this command at u-boot
AT+CGMR
+CGMR: "HW: GTA01Bv4, GSM:
gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko1"
------- 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
