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 #2148: [2009.11 testing] Settings
application fails to open (Openmoko Public Trac)
2. Openmoko Bug #2149: USB Port broken off (Openmoko Public Trac)
3. Re: Openmoko Bug #2078: glamo-mci.0: ****** insanity timeout
(Openmoko Public Trac)
4. Re: Openmoko Bug #2078: glamo-mci.0: ****** insanity timeout
(Openmoko Public Trac)
5. Re: Openmoko Bug #2078: glamo-mci.0: ****** insanity timeout
(Openmoko Public Trac)
6. Re: Openmoko Bug #2078: glamo-mci.0: ****** insanity timeout
(Openmoko Public Trac)
7. Openmoko Bug #2150: package illume-0.0+svnr35818-r13: task
do_fetch: failed (Openmoko Public Trac)
8. Re: Openmoko Bug #2078: glamo-mci.0: ****** insanity timeout
(Openmoko Public Trac)
--- Begin Message ---
#2148: [2009.11 testing] Settings application fails to open
-------------------------+--------------------------------------------------
Reporter: iknowjoseph | Owner: julian_chu
Type: defect | Status: accepted
Priority: normal | Milestone:
Component: Distro | Version: Om2008.9-dev
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-------------------------+--------------------------------------------------
Changes (by julian_chu):
* status: new => accepted
Comment:
There is a strange problem in the configure file of building system. John
and me found that and fixed it. Just wait and see if it is fixed or not
tomorrow.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2148#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2149: USB Port broken off
----------------------+-----------------------------------------------------
Reporter: tom | Owner: hardware
Type: defect | Status: new
Priority: normal | Milestone:
Component: hardware | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
----------------------+-----------------------------------------------------
USB Port loose, no data / power connection possible.
After opening device, port broke off. Looks like it was glued not soldered
to the board.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2149>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2078: glamo-mci.0: ****** insanity timeout
-----------------------------+----------------------------------------------
Reporter: Sprite_tm | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
I have similar experience. With stable-tracking at 80f4b57fef5dcffb access
to SD card stops with errors like
{{{
[21474629.595000] glamo-mci glamo-mci.0: ****** insanity timeout
[21474629.600000] glamo-mci glamo-mci.0: Error after cmd: 0x4300
[21474629.605000] mmcblk0: error -110 sending read/write command
[21474629.610000] end_request: I/O error, dev mmcblk0, sector 2141144
[21474629.610000] Buffer I/O error on device mmcblk0p2, logical block
265683
[21474662.305000] S3C24XX RTC, (c) 2004,2006 Simtec Electronics
}}}
and
{{{
[ 128.140000] glamo-mci glamo-mci.0: ****** insanity timeout
[ 128.140000] glamo-mci glamo-mci.0: Error after cmd: 0xc300
[ 128.145000] mmcblk0: error -110 sending read/write command
}}}
Also here 2.6.24-20081103.git7172ec57 from debian seems to work just fine
vrt. SD use. I am attaching full dmesg output from a bootup where the SD
becomes unusable quite soon (I think I tried to edit a small text file).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2078#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2078: glamo-mci.0: ****** insanity timeout
-----------------------------+----------------------------------------------
Reporter: Sprite_tm | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
Forgot to mention: I have a 2G SD card so this problem is not limited to
larger cards.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2078#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2078: glamo-mci.0: ****** insanity timeout
-----------------------------+----------------------------------------------
Reporter: Sprite_tm | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by Sprite_tm):
I just compiled a kernel with a small hack: instead of erroring out on the
insanity timeout, I let the code-flow continue as if nothing happened. In
glamo-mci.c:
if (insanity_timeout < 0) {
- cmd->error = -ETIMEDOUT;
+ //cmd->error = -ETIMEDOUT;
dev_err(&host->pdev->dev, "****** insanity timeout\n");
It seems like this has a good effect. I tried dd'ing my 64MB boot
partition to md5sum twice, and both times the md5sum was the same, while
multiple insanity timeouts were in the dmesg after each time. Assuming the
insanity timeouts aren't based on a sector (which I highly doubt, the
insanity timeouts seem to be random) this does solve the problem, albeit
in an extremely hackish and dirty way.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2078#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2078: glamo-mci.0: ****** insanity timeout
-----------------------------+----------------------------------------------
Reporter: Sprite_tm | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
Thanks a lot for your efforts! I tested your hack with stable-tracking
80f4b57fef5dcffb and
{{{
sudo pv /dev/mmcblk0 > /dev/null
}}}
completed in 27 minutes (I have 2G card) and triggered 11 insanity
timeouts:
{{{
Dec 1 23:32:22 ginger authpriv.notice sudo: lindi : TTY=pts/1 ;
PWD=/home/lindi ; USER=root ; COMMAND=/usr/bin/pv /dev/mmcblk0
Dec 1 23:34:17 ginger user.err kernel: [ 37.915000] glamo-mci glamo-
mci.0: ****** insanity timeout
Dec 1 23:36:05 ginger user.err kernel: [ 146.065000] glamo-mci glamo-
mci.0: ****** insanity timeout
Dec 1 23:39:53 ginger user.err kernel: [ 374.095000] fbcon_event_notify
action=9, data=c7027e08
Dec 1 23:40:25 ginger user.err kernel: [ 405.600000] glamo-mci glamo-
mci.0: ****** insanity timeout
Dec 1 23:40:40 ginger user.err kernel: [ 420.240000] glamo-mci glamo-
mci.0: ****** insanity timeout
Dec 1 23:42:59 ginger user.err kernel: [ 559.235000] glamo-mci glamo-
mci.0: ****** insanity timeout
Dec 1 23:43:07 ginger user.err kernel: [ 567.750000] glamo-mci glamo-
mci.0: ****** insanity timeout
Dec 1 23:43:21 ginger user.err kernel: [ 581.490000] glamo-mci glamo-
mci.0: ****** insanity timeout
Dec 1 23:48:20 ginger user.err kernel: [ 881.040000] glamo-mci glamo-
mci.0: ****** insanity timeout
Dec 1 23:49:54 ginger user.err kernel: [ 974.250000] fbcon_event_notify
action=9, data=c7027e08
Dec 1 23:52:50 ginger user.err kernel: [ 1151.170000] glamo-mci glamo-
mci.0: ****** insanity timeout
Dec 1 23:57:24 ginger user.err kernel: [ 1424.705000] glamo-mci glamo-
mci.0: ****** insanity timeout
Dec 1 23:59:54 ginger user.err kernel: [ 1574.405000] fbcon_event_notify
action=9, data=c7027e08
Dec 1 23:59:57 ginger user.err kernel: [ 1577.255000] glamo-mci glamo-
mci.0: ****** insanity timeout
Dec 2 00:00:12 ginger authpriv.notice sudo: lindi : TTY=pts/1 ;
PWD=/home/lindi ; USER=root ; COMMAND=/bin/true
}}}
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2078#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2150: package illume-0.0+svnr35818-r13: task do_fetch: failed
-------------------------+--------------------------------------------------
Reporter: frankmpunkt | Owner: julian_chu
Type: defect | Status: new
Priority: normal | Milestone:
Component: Distro | Version: unspecified
Severity: normal | Keywords: illume fetch build
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-------------------------+--------------------------------------------------
the illume sources are no longer to be found at this location:
svn://svn.enlightenment.org/svn/e/trunk;module=illume;proto=http
unfortunately the repository here
svn://svn.enlightenment.org/svn/e/trunk/e/src/modules/illume
does not have the requested revision (35818)
openembedded/packages/e17/illume_svn.bb
needs to be updated
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2150>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2078: glamo-mci.0: ****** insanity timeout
-----------------------------+----------------------------------------------
Reporter: Sprite_tm | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
Thanks for reporting the downgrading of this to a warning hiding the
problem, since passing the timeout up is going to be fatal and it seems we
can stumble on with no indication from Glamo it completed and work around
it.
If you have a minute please patchify the change and send it on the kernel
list; if you'd rather it get done for you let me know and I'll sort it out
tomorrow.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2078#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
