firesim / FireMarshal

Software workload management tool for RISC-V based SoC research. This is the default workload management tool for Chipyard and FireSim.
https://docs.fires.im/en/latest/Advanced-Usage/Workloads/index.html
Other
74 stars 49 forks source link

[Firesim][VCU118][firesim runworkload] Can not see linux booting and be presented with a login prompt #286

Open nguyensinhton opened 1 year ago

nguyensinhton commented 1 year ago

Hi everyone, I am following the guide, in the step "firesim runworkload" (https://docs.fires.im/en/latest/Getting-Started-Guides/On-Premises-FPGA-Getting-Started/Running-Simulations/Running-Single-Node-Simulation-Xilinx-VCU118.html).

I am facing a problem related to "Linux booting." When I executed the command "screen -r fsim0" to directly attach to the console of the simulated system, However, the system froze, and I received the following message:

Script started, file is uartlog Using: 0000:01:00.0, BAR ID: 0, PCI Vendor ID: 0x10ee, PCI Device ID: 0x903f Opening /sys/bus/pci/devices/0000:01:00.0/vendor Opening /sys/bus/pci/devices/0000:01:00.0/device examining xdma/. examining xdma/.. examining xdma/xdma0_h2c_0 Using xdma write queue: /dev/xdma0_h2c_0 Using xdma read queue: /dev/xdma0_c2h_0 command line for program 0. argc=29: +permissive +macaddr0=00:12:6D:00:00:02 +blkdev0=linux-uniform0-br-base.img +niclog0=niclog0 +blkdev-log0=blkdev-log0 +trace-select=1 +trace-start=0 +trace-end=-1 +trace-output-format=0 +dwarf-file-name=linux-uniform0-br-base-bin-dwarf +autocounter-readrate=0 +autocounter-filename-base=AUTOCOUNTERFILE +drj_dtb=linux-uniform0-br-base-bin.dtb +drj_bin=linux-uniform0-br-base-bin +drj_rom=linux-uniform0-br-base-bin.rom +print-start=0 +print-end=-1 +linklatency0=6405 +netbw0=200 +shmemportname0=default +domain=0x0000 +bus=0x01 +device=0x00 +function=0x0 +bar=0x0 +pci-vendor=0x10ee +pci-device=0x903f +permissive-off linux-uniform0-br-base-bin UART0 is here (stdin/stdout). TraceRV 0: Tracing disabled, since +tracefile was not provided.

The boot process freezes at this point, and I'm unable to see linux booting. I checked dmesg and got a ERROR as below :

[T4 Thg 8 2 14:05:13 2023] i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A (start=470390 end=470391) time 6197 us, min 1073, max 1079, scanline start 834, end 39 [T4 Thg 8 2 14:05:14 2023] i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A (start=470423 end=470424) time 5546 us, min 1073, max 1079, scanline start 931, end 145 [T4 Thg 8 2 14:05:14 2023] i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A (start=470450 end=470451) time 4330 us, min 1073, max 1079, scanline start 982, end 112 [T4 Thg 8 2 14:05:15 2023] i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A (start=470496 end=470497) time 3497 us, min 1073, max 1079, scanline start 843, end 1080 [T4 Thg 8 2 14:05:16 2023] i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A (start=470534 end=470535) time 4839 us, min 1073, max 1079, scanline start 761, end 1088

After a brief investigation, I think that it might be related to the Workload in Firemarshal. https://firemarshal.readthedocs.io/en/latest/Tutorials/quickstart.html

I have no idea how to resolve it now. Could you kindly recommend a solution? Thank you !