I am trying to run X86 full system. I am stuck at "mounting filesystems.."
for over a day now. Is this normal?
CMD:
./build/X86/gem5.opt configs/example/fs.py --caches
--disk-image=$M5_PATH/disks/linux-x86.img
--kernel=$M5_PATH/binaries/x86_64-vmlinux-2.6.22.9
I have not made any modifications
Looks like this is the instruction causing the assertion failure
MOV_R_M : ld r9, DS:[rdx + 0x10]
On Wed, Sep 11, 2019 at 5:20 PM Pouya Fotouhi wrote:
> If you use --debug-flags=ExecAll,Decode and narrow down your trace to the
> Ticks that you know the load is failing with --debug-start
Your disk isn't getting set up by the kernel either at all, or at a device
name different from what you're (through the config scripts) specifying in
the kernel's command line. Either the disk is failing to get set up (check
for messages earlier in the console output), or it's getting named
Hi Gabe.
Thank you for the clarification, greatly appreciated . I will make a record
of this, and attempt to implement it as soon as possible.
Best,
On Thu, Sep 12, 2019 at 3:52 PM Gabe Black wrote:
> It's been a while, but I think your interpretation is correct. It looks
> like O3 doesn't
It's been a while, but I think your interpretation is correct. It looks
like O3 doesn't check for NO_ACCESS and so will likely go ahead and do the
access regardless. That will possibly lead to bad things happening, and
would probably be worth fixing if you're trying to use x86 with O3.
Gabe
On
No, that's probably not normal, although I think the "INIT: version 2.86
booting" likely comes from something that ran from the disk. You may have a
problem with your disk image, or your init scripts may be messed up somehow.
Gabe
On Thu, Sep 12, 2019 at 7:34 AM Eleanor wrote:
> I am trying to
