On 19/06/2023 12:23, sai krishna Allu wrote:
Hi Ralf,

I have attached the hypervisor.o and I have taken the dump of that which is also attached too.
I have below command to extract, let me know is it ok or not.

ubuntu@ubuntu:~$ aarch64-linux-gnu-objdump -d jailhouse/hypervisor/hypervisor.o|tee hypervisor_dump.txt

ubuntu@ubuntu:~$ cat hypervisor_dump.txt -n |grep "ffffc0203820"
*3338    ffffc0203820:       f9400282        ldr     x2, [x20]*
ubuntu@ubuntu:~$ vi hypervisor_dump.txt +3338
       patch+0x218>
  3334     ffffc0203810:       f9400282        ldr     x2, [x20]
  3335     ffffc0203814:       f9400842        ldr     x2, [x2, #16]
  3336     ffffc0203818:       8a130042        and     x2, x2, x19
  3337     ffffc020381c:       f90a4002        str     x2, [x0, #5248]
* 3338     ffffc0203820:       f9400282        ldr     x2, [x20]*
  3339     ffffc0203824:       f9400c42        ldr     x2, [x2, #24]
  3340     ffffc0203828:       8a130053        and     x19, x2, x19
  3341     ffffc020382c:       52800022        mov     w2, #0x1

The instruction at ffffc0203820 means it Load x2 from contents of x20 register.
Please suggest how to fix this.

Keep calm, I'm still trying to figure out where the problem exactly is.

Now I know the line of code, where the exception exactly happens. It's in hypervisor/arch/arm-common/psci.c:39

ldr x2, [x20] <- Here we likely load ctx->regs[2], and the only variant how this could fail is that ctx points to somewhere. Here we're inside the routine psci_emulate_cpu_on, which shouldn't even be called when enabling the hypervisor. I don't know yet what could be the issue.

Before we keep on debugging: I saw that you use Jailhouse v0.12.

Could you please switch to the master and/or next branch of jailhouse, and see if the error still occurs there?

Thanks,
  Ralf


Regards,
Sai Krishna

On Saturday, June 17, 2023 at 8:59:56 PM UTC+5:30 Ralf Ramsauer wrote:

    Hi,

    On 15/06/2023 10:11, sai krishna Allu wrote:
     > Hi Team,
     >
     > I have Raspberry Pi 4, which is installed with Ubuntu 20.04.5 LTS
    64 bit.
     > after loading the jailhouse.ko file, when I gave following
    command I am
     > getting the exception.
     >
     > ubuntu@ubuntu:~/jailhouse$ sudo jailhouse enable
    configs/arm64/rpi4.cell
     >
     > Initializing Jailhouse hypervisor v0.12 (0-g92db71f2) on CPU 0
     > Code location: 0x0000ffffc0200800
     > Page pool usage after early setup: mem 39/994, remap 0/131072
     > Initializing processors:
     >  CPU 0...
     > FATAL: Unhandled HYP exception: synchronous abort from EL2

    Synchronous abort from EL2 means that we have a fatal error inside
    Jailhouse (e.g., segfault).

     >  pc: 0000ffffc0203820   lr: 0000ffffc020380c spsr: 800003c9     EL2

    Could you please disassemble your hypervisor binary, and see where the
    exception exactly occurs? Do this with:

    aarch64-objdump -d hypervisor/hypervisor.o

    And see what code executes behind 0x0000ffffc0203820. Alternatively,
    you
    can also attach the hypervisor.o.

    Thanks,
    Ralf

     >  sp: 0000ffffc021ee40  esr: 00 1 0000000
     >  x0: 0000000084000000   x1: 0000000000000008   x2: 0000000080003580
     >  x3: 0000ffffc020e170   x4: 0000000000000014   x5: 000003ffffffffff
     >  x6: 0000000000000029   x7: 0000ffffc0219d30   x8: 000000000000002a
     >  x9: 0000000000000000  x10: 0000000000000000  x11: 0000000000000001
     > x12: 0000000000000015  x13: 0000000000000001  x14: 0000ffffc0219000
     > x15: 0000ffffc0015040  x16: 0000ffffc020d1fc  x17: ffffbcae22826688
     > x18: 0000000000000001  x19: 0000ffffc021e000  x20: 0000ffffc0219000
     > x21: 0000ffffc0200000  x22: 0000ffffc0219000  x23: 0000000000000000
     > x24: 0000000000000001  x25: 0000ffffc021e000  x26: 0000ffffc021f000
     > x27: 0000ffffc020f000  x28: 0000ffffc0218000  x29: 0000ffffc021ee40
     >
     > Hypervisor stack before exception Stopping CPU 0 (Cell:
    "Raspberry-Pi4")
     >
     >
     > Please suggest how to fix this problem.
     >
     > Regards,
     > Sai Krishna
     >
     > --
     > You received this message because you are subscribed to the Google
     > Groups "Jailhouse" group.
     > To unsubscribe from this group and stop receiving emails from it,
    send
     > an email to [email protected]
     > <mailto:[email protected]>.
     > To view this discussion on the web visit
     >
    
https://groups.google.com/d/msgid/jailhouse-dev/3e6d4f38-5938-4da0-9666-9093a0b76300n%40googlegroups.com 
<https://groups.google.com/d/msgid/jailhouse-dev/3e6d4f38-5938-4da0-9666-9093a0b76300n%40googlegroups.com>
 
<https://groups.google.com/d/msgid/jailhouse-dev/3e6d4f38-5938-4da0-9666-9093a0b76300n%40googlegroups.com?utm_medium=email&utm_source=footer
 
<https://groups.google.com/d/msgid/jailhouse-dev/3e6d4f38-5938-4da0-9666-9093a0b76300n%40googlegroups.com?utm_medium=email&utm_source=footer>>.

--
You received this message because you are subscribed to the Google Groups "Jailhouse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/jailhouse-dev/bdaa1499-4532-423f-a59d-812557f8162an%40googlegroups.com <https://groups.google.com/d/msgid/jailhouse-dev/bdaa1499-4532-423f-a59d-812557f8162an%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/0f73d59b-4574-17c9-e2da-68c52222be44%40oth-regensburg.de.

Reply via email to