<GitHub121>
[rtems-yaffs2/master] add rtems-mkyaffs2image support - Xiangfu Liu
<GitHub161>
[scripts] xiangfu pushed 1 new commit to master: http://git.io/NwjZvw
<GitHub161>
[scripts/master] update to last rtems-mkyaffs2image - Xiangfu Liu
<GitHub9>
[scripts] xiangfu force-pushed master from c88c4dd to 901cb33: http://git.io/DOsw5Q
<GitHub9>
[scripts/master] update to last rtems-mkyaffs2image - Xiangfu Liu
<wpwrak>
phew. finally the corruption is back. even got three in a just ~220 cycles. don't quite trust my luck. next run, before trying countermeasures ...
<kristianpaul>
back how? did you did something?
<wpwrak>
i ran the most extensive and primitive loop
<wpwrak>
the one that goes all the way to rendering
<kristianpaul>
ah, interesting and if i remenber last test you did was not up to render right?
<wpwrak>
all i did for ~the last week was just into booting of rtems. of course, also that used to produce corruption
<kristianpaul>
hum..
<kristianpaul>
too soon to speak again :)
<wpwrak>
it also looks like a triple hit. kinda unusual.
<wpwrak>
but maybe that's just all the badness collected from the days of absence of corruption :)
<wpwrak>
hates stochastic bugs
<wpwrak>
at least this one happened within a run time of ~5 hours. the first 1.5 hours were "clean"