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. Re: Openmoko Bug #2217: Noise screen of death: Freerunner
looses SDIO connection (Openmoko Public Trac)
2. Re: Openmoko Bug #2217: Noise screen of death: Freerunner
looses SDIO connection (Openmoko Public Trac)
3. Re: Openmoko Bug #2073: voice-recording.state + arecord:
Unable to handle kernel NULL pointer dereference at virtual
address 00000000 (Openmoko Public Trac)
4. Re: Openmoko Bug #2217: Noise screen of death: Freerunner
looses SDIO connection (Openmoko Public Trac)
5. Re: Openmoko Bug #2217: Noise screen of death: Freerunner
looses SDIO connection (Openmoko Public Trac)
6. Re: Openmoko Bug #2217: Noise screen of death: Freerunner
looses SDIO connection (Openmoko Public Trac)
7. Re: Openmoko Bug #2217: Noise screen of death: Freerunner
looses SDIO connection (Openmoko Public Trac)
8. Re: Openmoko Bug #2073: voice-recording.state + arecord:
Unable to handle kernel NULL pointer dereference at virtual
address 00000000 (Openmoko Public Trac)
--- Begin Message ---
#2217: Noise screen of death: Freerunner looses SDIO connection
-----------------------------+----------------------------------------------
Reporter: xbaldauf | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by xbaldauf):
With "glamo_core.slow_memory=1 glamo3362.slow_memory=1" on the kernel
command line and kernel
http://git.openmoko.org/?p=kernel.git;a=commit;h=4e9be3539e402cb2b9aa9caf5050756916b9345e
(Thu, 5 Feb 2009 21:11:28 +0000 (21:11 +0000)), I still get the noise
screen of death and this in the log file:
[ 3879.530000] glamo-mci glamo-mci.0: Error after cmd: 0x302
[ 3879.530000] mmcblk0: retrying using single block read
[ 3879.540000] glamo-mci glamo-mci.0: Error after cmd: 0x8020
[ 3879.540000] glamo-mci glamo-mci.0: Error after cmd: 0x8122
[ 3879.550000] glamo-mci glamo-mci.0: Error after cmd: 0x4302
[ 3879.550000] mmcblk0: error -84 sending status comand<3>mmcblk0: error
-84 sending read/write command, response 0x0, card status 0x0
[ 3879.565000] end_request: I/O error, dev mmcblk0, sector 14732172
[ 3879.575000] glamo-mci glamo-mci.0: Error after cmd: 0x8020
[ 3879.575000] glamo-mci glamo-mci.0: Error after cmd: 0x8122
[ 3879.595000] glamo-mci glamo-mci.0: Error after cmd: 0x4302
:-(
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2217#comment:13>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2217: Noise screen of death: Freerunner looses SDIO connection
-----------------------------+----------------------------------------------
Reporter: xbaldauf | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by tilman):
This just looks like the problems created by GSM interference... try
setting glamo_mci.sd_max_clk=1000000 on the kernel command line to rule
out that it has anything to do with it.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2217#comment:14>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2073: voice-recording.state + arecord: Unable to handle kernel NULL pointer
dereference at virtual address 00000000
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: ALSA
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Changes (by arhuaco):
* cc: joerg (added)
Comment:
Replying to [comment:13 lindi]:
> Graeme just pointed out I should use voip-handset.state. And indeed,
"arecord | aplay" works perfectly with that!
I've was asked about the voip-handset.state file and Joerg tells me there
are a few versions of it. Is there a link to the version that is working
for you? / the one you think is good?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2073#comment:18>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2217: Noise screen of death: Freerunner looses SDIO connection
-----------------------------+----------------------------------------------
Reporter: xbaldauf | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by xbaldauf):
Well... running the kernel with parameter "glamo_mci.sd_max_clk=1000000"
makes booting really painfully slow. But additionally, this does not fix
the problem.
After entering the PIN (e.g. connecting to GSM), I get these error
messages.
[ 939.205000] glamo-mci glamo-mci.0: Error after cmd: 0x8302
[ 939.205000] mmcblk0: retrying using single block read
[ 939.220000] glamo-mci glamo-mci.0: Error after cmd: 0x120
[ 939.220000] mmcblk0: error -110 sending read/write command, response
0x0, card status 0x40400b00
[ 939.230000] end_request: I/O error, dev mmcblk0, sector 11188690
[ 939.240000] glamo-mci glamo-mci.0: Error after cmd: 0x120
[ 939.240000] mmcblk0: error -110 sending read/write command, response
0x0, card status 0x400b00
[ 939.260000] end_request: I/O error, dev mmcblk0, sector 11188691
[ 939.260000] glamo-mci glamo-mci.0: Error after cmd: 0x120
[ 939.275000] mmcblk0: error -110 sending read/write command, response
0x0, card status 0x400b00
[ 939.295000] end_request: I/O error, dev mmcblk0, sector 11188692
[ 939.295000] glamo-mci glamo-mci.0: Error after cmd: 0x120
[ 939.310000] mmcblk0: error -110 sending read/write command, response
0x0, card status 0x400b00
[ 939.315000] end_request: I/O error, dev mmcblk0, sector 11188693
[ 939.330000] glamo-mci glamo-mci.0: Error after cmd: 0x120
So the problem may indeed be GSM-related. However, your suggested fix does
not seem to work.
(My relevant kernel command line parameters are now
"glamo_core.slow_memory=1 glamo3362.slow_memory=1
glamo_mci.sd_max_clk=1000000".)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2217#comment:15>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2217: Noise screen of death: Freerunner looses SDIO connection
-----------------------------+----------------------------------------------
Reporter: xbaldauf | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by xbaldauf):
Interestingly, however, it looks like that, by using
glamo_mci.sd_max_clk=1000000, I can raise the probability of getting such
a crash like above to 100%. The crash happens always at GSM-login-time.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2217#comment:16>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2217: Noise screen of death: Freerunner looses SDIO connection
-----------------------------+----------------------------------------------
Reporter: xbaldauf | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
Holy crap, not liking the sound of this.
GSM taking a dump on SDIO communication is one thing, but this problem is
to do with either CPU <-> Glamo communications or Glamo <-> internal
memory another way.
It's a new thing in the world if we are saying GSM TX impacts either of
those.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2217#comment:17>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2217: Noise screen of death: Freerunner looses SDIO connection
-----------------------------+----------------------------------------------
Reporter: xbaldauf | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
Replying to [comment:16 xbaldauf]:
> Interestingly, however, it looks like that, by using
glamo_mci.sd_max_clk=1000000, I can raise the probability of getting such
a crash like above to 100%. The crash happens always at GSM-login-time.
To be clear, at the time of this "crash", you have the permanent noisy
screen business?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2217#comment:18>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2073: voice-recording.state + arecord: Unable to handle kernel NULL pointer
dereference at virtual address 00000000
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: ALSA
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Comment(by arhuaco):
Joerg,
I think it would be safe for us to assume that the file is
/usr/share/openmoko/scenarios/voip-handset.stat , don't you think?
This program is working and it wouldn't work otherwise:
http://wiki.openmoko.org/wiki/Voicenote
If there is some improvement about this file I guess we will be notified
somehow anyway.
I apologize if I wasted somebody's time with this question.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2073#comment:19>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
