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 79] suspend/resume to RAM support
([EMAIL PROTECTED])
2. [Bug 1355] unable to enter PIN after suspend
([EMAIL PROTECTED])
3. [Bug 79] suspend/resume to RAM support
([EMAIL PROTECTED])
4. [Bug 79] suspend/resume to RAM support
([EMAIL PROTECTED])
5. [Bug 1353] No sound after resume from suspend
([EMAIL PROTECTED])
6. [Bug 1359] New: Unable to unload the GTA01 audio module
snd_soc_neo1973_wm8753 ([EMAIL PROTECTED])
7. [Bug 1359] Unable to unload the GTA01 audio module
snd_soc_neo1973_wm8753 ([EMAIL PROTECTED])
8. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
9. [Bug 79] suspend/resume to RAM support
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=79
------- Additional Comments From [EMAIL PROTECTED] 2008-04-19 14:29 -------
I test this... now neo is booting.
I enter the PIN. (Btw: there is a click when i touch the screen)
Now i use my other phone (nokia) to call the neo:
Neo rings and vibrates ... i catch it up: Hrm ... to late! :-(
Again:
Neo rings and vibrates ... i catch it up: Ok, this time it works!
I knock the nokia on the table and can hear this on the neo.
I knock the neo on the table and can hear this on the nokia.
If i puff in the phone and not knock the phone, i get the same result.
Now i use the neo to call the nokia:
Nokia rings and vibrates ... i catch it up:
Same tests, same results! And, btw the voice quality seems very good!
Now i pres the power-btn and my patched neod brings up a nice menu in wich i
press "Suspend Phone". Now the goes with ne "apm -s" command in suspens.
... tuedelue ...
Wake up with Power-Button:
Now there is no click when i touch the screen anymore!
I use my nokia to call the neo:
Neo _doesn't ring_ but vibrates ... i catch it up:
I knock the nokia on the table and can hear this on the neo.
I knock the neo on the table and _can't_ hear this on the nokia.
If i puff in the phone and not knock the phone, i get the same result.
Now i use the neo to call the nokia:
Nokia rings and vibrates ... i catch it up:
I knock the nokia on the table and can hear this on the neo.
I knock the neo on the table and _can't_ hear this on the nokia.
If i puff in the phone and not knock the phone, i get the same result.
Ok, the bug is still there and now i will enter alsactl restore via ssh.
The touchscreen click isn't there.
I use the nokia to call the neo:
Neo _doesn't ring_ but vibrates ... i catch it up:
I knock the nokia on the table and can hear this on the neo.
I knock the neo on the table and can hear this on the nokia.
If i puff in the phone and not knock the phone, i get the same result.
Seems that the alsactl helps with the mic, but not the ringing and clicking.
Could this be a pulseaudio error?
But generall i think it's not correct to restore the alsa state after 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=1355
------- Additional Comments From [EMAIL PROTECTED] 2008-04-19 16:20 -------
For a short time after wake up, i could see the PIN dialog, but i then
disapears.
------- 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=79
------- Additional Comments From [EMAIL PROTECTED] 2008-04-19 17:26 -------
Using the alsa utils to save and restore the volume settings is the right thing
to do. For some reason that's unknown to me, the alsa developers have decided
that post-resume, output should be muted, not restored to the pre-resume values.
Then again, from what you describe it sounds to me like the volume might already
be being restored. *shrug*
------- 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=79
------- Additional Comments From [EMAIL PROTECTED] 2008-04-19 20:16 -------
But i think pulseaudio don't likes the suspending:
I started pulseaudio:
/usr/bin/pulseaudio -vvvv --no-cpu-limit --resample-method=trivial -nF
/etc/pulse/session
suspend/resume and then i get:
W: module-alsa-sink.c: Got POLLERR from ALSA
A little google told me, that this could be an alsa bug. Pulseaudio can just
reinit the audio, but as i saw this in our version this is already implemented
but didn't help!
------- 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=1353
------- Additional Comments From [EMAIL PROTECTED] 2008-04-19 20:20 -------
If the alsactl restore doesn't help you could test if it's the same issue we
have in the #79 bug.
To find out if it is just do the following:
"/etc/init.d/xserver-nodm stop"
"/etc/init.d/pulseaudio stop"
"/usr/bin/pulseaudio -vvvv --no-cpu-limit --resample-method=trivial -nF
/etc/pulse/session"
then on another terminal:
"/etc/init.d/xserver-nodm start"
if you can see a message like: "W: module-alsa-sink.c: Got POLLERR from ALSA" in
the pulseaudio output, it is the same issue!
------- 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=1359
Summary: Unable to unload the GTA01 audio module
snd_soc_neo1973_wm8753
Product: OpenMoko
Version: current svn head
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
I was unable to unload the snd_soc_neo1973_wm8753 module.
I have written a little patch wich resolves this, it appends also some debug
messages.
I'm also wondering that the kernel never calls the suspend/resume functions in
this module!
------- 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=1359
------- Additional Comments From [EMAIL PROTECTED] 2008-04-19 20:29 -------
Created an attachment (id=600)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=600&action=view)
Patch mentioned in the Text
------- 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=1012
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1081
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1107
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1127
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1133
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1136
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1158
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1162
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1189
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1193
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1197
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1199
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1200
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1201
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1206
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1212
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1215
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1216
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1217
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1218
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1276
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1292
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=79
------- Additional Comments From [EMAIL PROTECTED] 2008-04-20 06:03 -------
Current status: In additional to all the patches to date on this bug report, one
must currently remove ttySAC0 from the boot parameters in u-boot. There remains
a race condition wherein the console is re-activated at resume time despite
being disabled when the GSM is powered up.
I have strong feelings about a solution to this, but this probably isn't a good
forum for that discussion, so for the moment users need to edit their u-boot
environment to remove the ttySAC0 from the bootargs.
------- 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
