[Bug 707] modem/gsmd does not start in a reliable way (if at all) on boot
bugzilla-daemon at bugzilla.openmoko.org
bugzilla-daemon at bugzilla.openmoko.org
Sat Nov 3 17:58:23 CET 2007
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=707
------- Additional Comments From tick at openmoko.com 2007-11-03 17:58 -------
After some testing I found some strange properties, and that may be the rule
cause why gsmd cannot starts up well.
The following is my way to test modem behaviour.
kernel:
Linux fic-gta01 2.6.22.5-moko11 #1 PREEMPT Mon Oct 22 09:44:05 UTC 2007 armv4tl
unknown
Neo: GTA01v3
1. Not allow /etc/init.d/gsmd be called before I test.
find -name '*35gsmd' -exec rm -rf {} \;
find -name '*99xserver*' -exec rm -rf {} \;
to ensure the environment is clean
2. poweroff & remove usb cable & remove battery
then put everything back and turn on my neo
3. Turn on modem
echo 1 > /sys/devices/platform/gta01-pm-gsm.0/power_on
4. ./tickminicom <-- a tiny minicom program with exactly the same uart initial
flow as gsmd
Then I will get a lot of message dump from /dev/ttySAC0 (I do not input anything
yet.)
You can find the source code at
http://linuxocarina.blogspot.com/2007/09/minicom.html
I do not input anything, but I get so many response comes from nowhere.
No wonder gsmd will out of control for the first time initiate.
The following is what I get:
----------------------------------------------------------
root at fic-gta01:~$ echo 1 > /sys/devices/platform/gta01-pm-gsm.0/power_on
root at fic-gta01:~$ ./tickminicom
DEBUG: (util.c, 69): open_device: Try to open device /dev/ttySAC0!
DEBUG: (util.c, 48): set_baud: Open uart with speed 115200
DEBUG: (tick_minicom.c, 71): main: Open Uart and set baud rate OK!!
T-Command Interpreter ready
aterpreter ready
ERROR
ERROR
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
----------------------------------------------------------------------------
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the buglog
mailing list