| qi-bot | The build was successfull, see images here: http://fidelio.qi-hardware.com/~xiangfu/build-milkymist/milkymist-openwrt.minimal-09132011-0250/ | 01:45 |
|---|---|---|
| GitHub121 | [rtems-yaffs2] xiangfu pushed 1 new commit to master: https://github.com/milkymist/rtems-yaffs2/commit/4f5938aebf5d14197c1a8de8531184fe4f12cbca | 03:29 |
| GitHub121 | [rtems-yaffs2/master] add rtems-mkyaffs2image support - Xiangfu Liu | 03:29 |
| GitHub161 | [scripts] xiangfu pushed 1 new commit to master: http://git.io/NwjZvw | 03:31 |
| GitHub161 | [scripts/master] update to last rtems-mkyaffs2image - Xiangfu Liu | 03:31 |
| GitHub9 | [scripts] xiangfu force-pushed master from c88c4dd to 901cb33: http://git.io/DOsw5Q | 03:35 |
| GitHub9 | [scripts/master] update to last rtems-mkyaffs2image - Xiangfu Liu | 03:35 |
| 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 ... | 03:52 |
| kristianpaul | back how? did you did something? | 03:56 |
| wpwrak | i ran the most extensive and primitive loop | 03:59 |
| wpwrak | the one that goes all the way to rendering | 03:59 |
| kristianpaul | ah, interesting and if i remenber last test you did was not up to render right? | 04:00 |
| wpwrak | all i did for ~the last week was just into booting of rtems. of course, also that used to produce corruption | 04:01 |
| kristianpaul | hum.. | 04:01 |
| kristianpaul | too soon to speak again :) | 04:01 |
| wpwrak | it also looks like a triple hit. kinda unusual. | 04:02 |
| wpwrak | but maybe that's just all the badness collected from the days of absence of corruption :) | 04:03 |
| Action: wpwrak hates stochastic bugs | 04:04 | |
| wpwrak | at least this one happened within a run time of ~5 hours. the first 1.5 hours were "clean" | 04:06 |
| kristianpaul | wtf? | 04:37 |
| kristianpaul | ip_output no HDR | 04:37 |
| kristianpaul | fatal error, exiting | 04:37 |
| kristianpaul | just after rtem shell started | 04:37 |
| kristianpaul | hum, may be my fault :) | 04:40 |
| GitHub9 | [rtems-yaffs2] xiangfu pushed 1 new commit to master: https://github.com/milkymist/rtems-yaffs2/commit/5e31a3f5b662d4e013d0eab968be9c9bc206a671 | 08:40 |
| GitHub9 | [rtems-yaffs2/master] rename rtems-mkyaffs2image to nor-mkyaffs2image - Xiangfu Liu | 08:40 |
| GitHub167 | [milkymist] sbourdeauducq pushed 7 new commits to master: http://git.io/vjrjEg | 10:37 |
| GitHub167 | [milkymist/master] uart: add status and control register - Michael Walle | 10:37 |
| GitHub167 | [milkymist/master] update header files for new uart core - Michael Walle | 10:37 |
| GitHub167 | [milkymist/master] libhpdmc: support new uart core - Michael Walle | 10:37 |
| wpwrak | yay ! another corruption :) after 613-639 loops (~14 h) this time. | 17:48 |
| wpwrak | one or two more and i can do some meaningful testing again | 17:48 |
| wpwrak | lekernel: would the shutdown that should make it safe to power down correspond to the "halt" command in rtems ? | 21:49 |
| lekernel | I don't know what the 'halt' command does... but the 'shutdown' button in FN does go back to the standby bitstream | 22:46 |
| wpwrak | hmm, now how do i automate the "shutdown" button ... ? :) | 22:49 |
| mwalle | wpwrak: is raw memory access possible on the rtems shell? | 23:22 |
| mwalle | if its possible do the same as the shutdown button :) | 23:22 |
| mwalle | eg write the reconfigure request via sysctl | 23:23 |
| mwalle | gn8 | 23:24 |
| wpwrak | mwalle: hmm, would commanding the reconfig via jtag be the same ? | 23:26 |
| errordeveloper | has anyone seen it ? | 23:28 |
| errordeveloper | .. http://lubyk.org/en | 23:28 |
| errordeveloper | quite insteresting ... | 23:28 |
| errordeveloper | I came across it while looking for some zeromq related stuff .. | 23:28 |
| --- Wed Sep 14 2011 | 00:00 | |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!