Openmoko Bug #2078: glamo-mci.0: ****** insanity timeout
Openmoko Public Trac
bugs at docs.openmoko.org
Mon Dec 1 22:05:53 CET 2008
#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
More information about the buglog
mailing list