Same hang with all-in-order configuration

JOURNAL.md

@@ -1133,3 +1133,34 @@ after booting with the `tp_printk trace_buf_size=1M` boot options:
     echo do_page_fault > $td/set_graph_function
     echo function_graph > $td/current_tracer
 
+### OBSERVATION: Using all-in-order causes the hang in the same place
+
+After setting the CSR 0x801 register to 0x7, the all-in-order configuration, the
+memtool fill tests continues to hang in the same position:
+
+    + csrtool all-in-order
+    CSR 0x801 = 7u
+    + memtool fill 536870912
+    memtool v0.0.1 - Rodrigo Arias Mallo <rodrigo.arias@bsc.es>
+    mode fill: nbytes=512M, n=134217728
+    written=0K, addr=0x3f8d600020 OK
+    written=4096K, addr=0x3f8da00020 OK
+    written=8192K, addr=0x3f8de00020 OK
+    written=12288K, addr=0x3f8e200020 OK
+    written=16384K, addr=0x3f8e600020 OK
+    written=20480K, addr=0x3f8ea00020 OK
+    written=24576K, addr=0x3f8ee00020 OK
+    written=28672K, addr=0x3f8f200020 OK
+    written=32768K, addr=0x3f8f600020 OK
+    written=36864K, addr=0x3f8fa00020 OK
+    written=40960K, addr=0x3f8fe00020 OK
+    written=45056K, addr=0x3f90200020 OK
+    written=49152K, addr=0x3f90600020 OK
+    written=53248K, addr=0x3f90a00020 OK
+    written=57344K, addr=0x3f90e00020 OK
+
+It doesn't seem to have any observable effect with this test, other than going
+more slow.
+
+Interesting [article](https://wiki.osdev.org/RISC-V_Bare_Bones) on how to write
+a simple bootrom that outputs some ASCII text into the console.