Commit Graph

61 Commits

Author SHA1 Message Date
dc8a8c2ce9 Build OpenSBI with the generic platform 2024-07-12 12:20:03 +02:00
8c2b28cf21 Enable systemd debug log and all-in-order 2024-07-12 10:50:28 +02:00
c23d33a51c Update to OpenSBI 1.5 2024-07-12 09:34:45 +02:00
9f6f8bcddc Don't use DTB in U-Boot, read it from OpenSBI 2024-07-11 16:05:05 +02:00
1a15ddc0e7 Restore support for huge pages 2024-07-11 15:37:41 +02:00
b7dba89d63 Reduce RAM to 768 MiB to avoid a memory problem 2024-07-10 18:04:11 +02:00
28efecdbc7 Enable U-Boot mtest command 2024-07-10 17:32:58 +02:00
31f8557799 Open interactive shell on start 2024-07-10 14:20:39 +02:00
b7d02f867a Disable support for huge pages 2024-07-10 14:19:49 +02:00
4c2e21033b Try tracing handle_page_fault 2024-07-10 13:02:43 +02:00
9ee8fb06dc Try again the fill test but with all-in-order 2024-07-10 12:21:24 +02:00
93936cbe14 Trace function graph after a page fault 2024-07-10 11:34:40 +02:00
91080535f8 Add fill mode in memtool 2024-07-10 11:05:20 +02:00
813e7cae2f Increase memtool max block size to 512 K 2024-07-09 20:58:55 +02:00
9ed8f812c8 Make our own init script
The problem with the Stage 1 script is that is spawning another tee
process to forward the output to the console, but this is not required.
So let's only keep the memtool running by creating our own init script.
2024-07-09 20:54:55 +02:00
c6726cce28 Reduce blocksize in memtool to 64K
Let's see if we can hang a bit later on.
2024-07-09 17:58:12 +02:00
4707a8b143 Simplify boot parameters and document options 2024-07-09 17:27:07 +02:00
b8f1ca672f Run the memtool as first program 2024-07-09 17:25:48 +02:00
d488c0b3b7 Always run memtool at the start 2024-07-09 17:06:50 +02:00
f617efdcac Add memtool program to test the memory 2024-07-09 15:16:05 +02:00
82630f3eef Enable CONFIG_BUG again
It doesn't seem to make any difference, and it would be good in case it
catches a bug.
2024-07-09 12:35:53 +02:00
5b34b3b97b Add csrtool to view and change CSR registers 2024-07-08 19:19:05 +02:00
bef5a6eac5 Disable CONFIG_BUG
It may be causing a loop on WARN_ON_ONCE() and page fults trying to
write to the console.
2024-07-08 18:27:29 +02:00
5f90528b51 Add bootrom support 2024-07-08 18:11:11 +02:00
66ec07a0cb Switch to two uarts bitstream 2024-07-08 13:48:20 +02:00
1f0ac64631 Add bitstream to Nix 2024-07-08 13:46:37 +02:00
6721e1e22c Revert "Try to use openpiton based OpenSBI config"
This reverts commit 931244a355.
2024-07-08 10:03:48 +02:00
931244a355 Try to use openpiton based OpenSBI config
The seem to be doing PLIC initialization based on the device tree, which
may be relevant as that is where we are defining the interruptions.
2024-07-08 09:49:34 +02:00
87b4c91813 Dump stack trace on hvc_remove 2024-07-08 08:55:50 +02:00
b903eae7e5 Disable ftrace for now as it hangs the boot 2024-07-05 16:24:51 +02:00
7e6fdff142 Disable proactive compation
I see a lot of kcompactd0 entries in sched_switch log, so disable it for
now.
2024-07-05 15:57:18 +02:00
32f4d117db Only enable sched_switch events
As sched_stat_runtime is flooding the console.
2024-07-05 15:37:50 +02:00
bc05dc2676 Mount debugfs first 2024-07-05 15:36:42 +02:00
934b67ac0b Trace sched events from stage1
Events from the kthread that dumps the buffer to the console are
filtered, otherwise we make an infinite loop.
2024-07-05 15:36:42 +02:00
f509a0a517 Enable ftrace at boot
For now we only show init calls.
2024-07-05 15:36:37 +02:00
504c4aca3c Make the counter silent by spawning another shell 2024-07-05 12:57:10 +02:00
48688594bf Add a heartbeat counter to check the kernel 2024-07-05 12:45:32 +02:00
d541462b4c Stop in the stage 1 debug shell 2024-07-04 17:28:15 +02:00
9b37e2aed0 Use the hvc0 console for the kernel 2024-07-04 17:27:43 +02:00
471207c64a Allow access to all memory from userspace
> If this option is disabled, you allow userspace (root) access to all
> of memory, including kernel and userspace memory

Currently is failing:

    ~ # cat /proc/iomem
    40001000-400010ff : serial
    60000000-7fffffff : Reserved
    80000000-ffefffff : System RAM
      80201000-81fa0b87 : Kernel image
        80201000-80cb177f : Kernel code
        81400000-819fffff : Kernel rodata
        81c00000-81f18747 : Kernel data
        81f19000-81fa0b87 : Kernel bss
    100000000-1bfffffff : namespace0.0

    ~ # devmem 0x40001000
    devmem: mmap: Operation not permitted
2024-07-04 12:45:41 +02:00
4826396962 Try enabling polling in the serial console 2024-07-04 11:39:35 +02:00
b1755354d0 Add support for ftrace at boot time 2024-07-03 19:36:38 +02:00
427859818c Disable SMP
The IPI extension is being used to multiplex IPI interruptions and we
don't need it as we only have one CPU.
2024-07-03 19:31:30 +02:00
30703d1715 Use the ttyS0 device for the console
For now it seems to be outputting the log properly, but it doesn't read
anything in the initrd input console.
2024-07-03 16:09:38 +02:00
d7669671f6 Enable 8250 console driver 2024-07-03 14:09:52 +02:00
7c25f76f8b Bake the git commit inside the uboot env file 2024-07-03 14:09:48 +02:00
2442bdf3f5 Disable lock torture test 2024-07-03 13:44:02 +02:00
93e83f52e8 Add busybox patch to see debug lines: initrd sh ok
The switch_root command seems to hang in the execv() syscall.
2024-07-03 13:43:41 +02:00
109dea5b4e Enable kernel and busybox debug
Continues to hang in switch_root and no luck trying to send a magic
sysrq via serial port.
2024-07-01 18:00:54 +02:00
917cbf3439 Revert to upstream busybox 2024-07-01 14:53:08 +02:00