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 809] missing dependancy on vte
([EMAIL PROTECTED])
2. [Bug 775] bluetooth can not be enabled (kernel
2.6.22.5-moko11 / 20070829) ([EMAIL PROTECTED])
3. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
4. [Bug 758] libmokogsmd2 doesn't handle CB and DS events
([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 811] New: Make u-boot build script sh compatible
([EMAIL PROTECTED])
8. [Bug 811] Make u-boot build script sh compatible
([EMAIL PROTECTED])
9. [Bug 812] New: "neo1973 gsm version" command does not respond
([EMAIL PROTECTED])
10. [Bug 812] "neo1973 gsm version" command does not respond
([EMAIL PROTECTED])
11. [Bug 705] gsmd quits ([EMAIL PROTECTED])
12. [Bug 705] gsmd does not process responses from the modem
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=809
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-09-10 17:59 -------
This bug is now fixed in oe.dev.
vte is now listed as RDEPENDS
------- 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=775
------- Additional Comments From [EMAIL PROTECTED] 2007-09-10 18:08 -------
Yes, closing is fine.
------- 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=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=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=742
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=758
------- Additional Comments From [EMAIL PROTECTED] 2007-09-11 07:08 -------
commited as r2948 - still needs proper implementation
------- 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-11 07:12 -------
Created an attachment (id=284)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=284&action=view)
/etc/init.d/gsmd script
------- 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-11 07:13 -------
The root problem has been determined to be that enabling hardware flow control
on the console (not the GSM modem) will result in the system becoming
unresponsive to user input.
OVERVIEW: Upon starting, gsmd will set the the ttySAC0 port to enable hardware
flow control. When gsmd exits, or is killed, it leaves the port with hardware
flow control enabled. In and of itself, this situation is not a problem, as
long as the port remains switched to the GSM modem. However, as soon as the
/etc/init.d/gsmd script (or the user) turns off the GSM modem, the port is
switched to the console, hardware flow control is left enabled, and the first
kernel message printed to the console port will result in the device locking up
in a loop in the serial driver, presumably waiting for the correct modem control
lines to signal that it is ok to send data -- an event that won't happen on a
standard P1 device.
-----
WORKAROUND: the simple workaround is to explicitly set the port to disable
hardware flow control before the GSM modem is powered off and switched back to
the console. This can be accomplished by editing the /etc/init.d/gsmd script,
and changing the startup as follows:
case "$1" in
start)
stty -F /dev/ttySAC0 -crtscts
[ -n "$GSM_POW" ] && ( echo "0" >$GSM_POW; sleep 1 )
[ -n "$GSM_POW" ] && ( echo "1" >$GSM_POW; sleep 1 )
It is also necessary to change the shutdown as follows:
stop)
echo -n "Stopping GSM daemon: "
start-stop-daemon -K -x /usr/sbin/gsmd
stty -F /dev/ttySAC0 -crtscts
[ -n "$GSM_POW" ] && echo "0" >$GSM_POW
echo "gsmd."
For convenience, a suitably modified (and tested) gsmd script is attached to
this bug.
-----
LONG-TERM SOLUTION: It seems probable that there are multiple issues here. In
the first place, it seems unreasonable that the device becomes completely
unresponsive in the event that the console is flow-controlled. This may be a
bug in the console driver, or the serial driver.
However, the contention between the console and gsmd over the port settings is
an issue that needs resolution. Disabling the console completely is one
solution, but that makes kernel debugging work difficult at best. Adding logic
to ensure that gsmd resets the flow control on the port before exiting is a poor
solution, as there are numerous failure modes for gsmd that would not permit it
to perform such a reset, resulting in the same problem. In addition, since gsmd
does not actually do the power-on of the GSM modem, simply starting gsmd without
powering on the GSM modem will result in the same lock-up of the device. Thus,
it seems logical that the code that switches the gsm modem should also ensure
that the port flow-control settings (at least) are switched as appropriate,
rather than rely on separate user actions, or on gsmd. This would mean that
powering up the GSM modem would also require that flow control be enabled, and
conversely powering down would disable flow control.
-----
OTHER CONSIDERATIONS: The current console/GSM modem switch code is extremely
limited. It might be worthwhile considering a more ambitious architecture, one
that would be more flexible. For example, in the event of a kernel oops, it
would not be unreasonable to forcibly switch the console on and power off the
GSM modem, thus enabling the kernel to display the oops output.
------- 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=811
Summary: Make u-boot build script sh compatible
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: FreeBSD
Status: NEW
Severity: trivial
Priority: P2
Component: u-boot
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
The board/neo1973/gta0[1-2]/split_by_variant.sh scripts use a bash'ism but this
isn't necessary and the script is invoked with sh. A POSIX compatible sh will
fail.
------- 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=811
------- Additional Comments From [EMAIL PROTECTED] 2007-09-11 09:56 -------
Created an attachment (id=285)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=285&action=view)
Patch to correct the script
------- 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=812
Summary: "neo1973 gsm version" command does not respond
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: u-boot
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
The following sequence entered into the u-boot console causes u-boot to become
unresponsive:
GTA01Bv4 # neo1973 gsm on
GTA01Bv4 # neo1973 gsm version
switching s3ser0 from console into GSM mode
GSM firmware version:
------- 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=812
------- Additional Comments From [EMAIL PROTECTED] 2007-09-11 10:17 -------
U-Boot GTA01Bv4 # version
U-Boot 1.2.0-g60174746-dirty-moko11 (Sep 5 2007 - 00:53:30)
------- 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=705
------- Additional Comments From [EMAIL PROTECTED] 2007-09-11 10:23 -------
Comments #1 and #2 appear to be different issues from the one described in this
bug. This bug describes gsmd not processing any response from the modem. I also
have this problem at the moment with gsmd from current SVN.
------- 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=705
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|gsmd quits |gsmd does not process
| |responses from the modem
------- Additional Comments From [EMAIL PROTECTED] 2007-09-11 10:29 -------
Updating summary to be more specific.
I have used a terminal to send AT commands to the modem and got a successful
response. However, if I connect gsmd to the same device, it does not process any
responses.
------- 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
