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 107] obtain list of operators / control operator
selection ([EMAIL PROTECTED])
2. [Bug 100] Implement Cell Broadcast support
([EMAIL PROTECTED])
3. [Bug 562] gsmd init script causes sysrq message
([EMAIL PROTECTED])
4. [Bug 562] gsmd init script causes sysrq message
([EMAIL PROTECTED])
5. [Bug 788] Starting or stopping gsmd completely locks up the
Neo ([EMAIL PROTECTED])
6. [Bug 889] New: 8 seconds power button timeout no longer
working (regression) ([EMAIL PROTECTED])
7. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
8. [Bug 741] Image of Neo hardware shows debug board
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=107
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-09-21 15:11 -------
Checked in revision 2713 and 2725.
------- 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=100
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-09-21 15:22 -------
Checked in revision 2721 and 2723.
------- 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=562
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
------- Additional Comments From [EMAIL PROTECTED] 2007-09-21 16:48 -------
I'm seeing it happen with the 2007-09-17 rootfs and 2.6.22.5 and .6 kernels
during boot. I managed to reproduce it with a very verbose debugging kernel
that showed what the serial driver is doing when it happens. Starting from the
moment when "/etc/init.d/gsmd start" is issued, chronologically:
- s3c24xx_serial_set_termios is called (CRTSCTS is unset in .c_cflag).
- s3c24xx_serial_set_mctrl is called with mctrl value 6.
- The following three lines are printed in the dmesg:
<6>gta01-pm-gsm gta01-pm-gsm.0: powered down GSM, thus enabling serial console
<6>gta01-pm-gsm gta01-pm-gsm.0: powering up GSM, thus disconnecting serial
console
<7>modem wakeup interrupt
- s3c24xx_serial_rx_chars is called to handle an Rx IRQ. It reads the UART0
UERSTAT and URXH registers. URXH (the character received) is 0x00 and UERSTAT
(Rx error status) is 0xe which means that a Frame-error, a Break-condition and a
Parity-error are present (in the 2410A datasheet version that I have, bits 1 and
3 are reserved, but in the driver they are Break and Parity bits). The break
condition is remembered by the SysRq mechanism so that the next character
received will be treated as a SysRq. The 0x00 char is ignored.
- s3c24xx_serial_set_termios is called again (CRTSCTS is unset in .c_cflag).
- s3c24xx_serial_set_termios is called again (CRTSCTS is set in .c_cflag).
- s3c24xx_serial_get_mctrl is called and the CTS bit is one in UART0 UMSTAT
register.
- s3c24xx_serial_rx_chars is called to handle the second Rx IRQ. This time the
character received is the 'A' (from "AT-Command Interpreter ready") and there's
no error (UERSTAT is 0). At this point handle_sysrq() is called by the
s3c24xx_serial driver with the 'A' as parameter:
<6>SysRq : HELP : loglevel0-8 reBoot Crashdump tErm Full kIll saK showMem Nice
powerOff showPc show-all-timers(Q) unRaw Sync showTasks Unmount
shoW-blocked-tasks
The 'A' is ignored and the remaining "T-Command Interpreter ready" chars are
then received as usually.
------- 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=562
------- Additional Comments From [EMAIL PROTECTED] 2007-09-21 17:41 -------
When testing I still had "console=ttyS0" in the boot parameters. When I removed
it, as suggested by Daniel Willmann, the serial driver now receives two Rx
interrupts and the SysRq message went away. At the first interrupt it reads a
character 0xe0 from the modem, with no error indicated in UERSTAT - I don't know
where this may be coming from. Then immediately after, a second IRQ comes and
UERSTAT now indicates a Break-condition, a Parity-error and a Frame-error like
before. However, the 'A' character that comes next doesn't trigger the SysRq
message anymore, maybe the period between the break condition and the 'A' is now
longer (there's a timeout check in the code).
I should note that it only happens after the battery had been removed before
turning the phone on. The behavior was identical all four times I tried booting
after removing the console on ttyS0.
------- 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-21 20:22 -------
Created an attachment (id=317)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=317&action=view)
gsm_serial_console_lockup patch using unregister/register serial
This implements Harald's idea using register_console and unregister_console.
I guess that also solves the possible resume console race condition, as there
is not risk the console gets re-enabled by accident during resume process.
I did some basic testing : which means with this patch there are not more
lockups.
------- 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=889
Summary: 8 seconds power button timeout no longer working
(regression)
Product: OpenMoko
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Usually, after a couple of seconds holding the powerbutton, init was signalized
a reboot. if that doesn't react, the system was shut down. This no longer works.
When I keep pressing the power button, I see the kernel incrementing the seconds
counter, but the system just doesn't shut down nor does it turn off.
------- 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=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
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=800
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=835
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=846
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=847
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=862
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=864
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=865
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=741
------- Additional Comments From [EMAIL PROTECTED] 2007-09-22 09:09 -------
Hi Liane,
Just to clarify, the image on the website is of the wrong thing. It needs to be
a picture of the GTA01 handset board, not the debug board.
An example of what it should look like is on the Wiki:
http://wiki.openmoko.org/wiki/Image:Gta01b_v4_front.jpg
------- 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
