sdhci_send_command: Controller never released inhibit bit(s)

[Stéphane R.]

Hi,

I'm using version v0.3.0 of xvisor and I have this type of errors happening when i'm installing openjdk in my linux guest

sdhci_send_command: Controller never released inhibit bit(s)

Other types of errors i've met are:

[guest0/uart0] [  702.335900] Buffer I/O error on device vda, logical block 66459

[guest0/uart0] [  774.103202] JBD2: Detected IO errors while flushing file data on vda-8

I launched my guest OS with the same kernel file in qemu and tried the installation of openjdk and I don't meet these errors, are they linked to xvisor ?

I've read that the first error had already been met before, do I have to use xvisor-next?

Regards,

Stéphane Richardson

[Anup Patel]

Hi Stephane R,

Strangely, I never saw this issues with Xvisor-0.3.0 on RPi3.

Do you see the same issue on the latest Xvisor-next repo ??

Regards,
Anup

> --
> You received this message because you are subscribed to the Google Groups "Xvisor Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to xvisor-devel...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/xvisor-devel/CACvx%3D6n%3DNBimaZdTohPTH7q_9Gu1P4Vs4PSqKZ-YHFcK%3DkA_tg%40mail.gmail.com.

[Stéphane R.]

Hi,

Actually, I tried using the xvisor-next repo but I couldn't boot. It's stuck at Starting kernel ...

I used the same steps as I used with the normal repo, I just compiled the uvmm.bin file from the next repo and used the other files from my previous compilations.

Regards,

Stéphane

U-Boot 2017.09 (Jul 09 2020 - 19:20:55 +0200)

DRAM:  960 MiB
RPI 3 Model B (0xa02082)
MMC:   sdhci@7e300000: 0
reading uboot.env
In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   No ethernet found.
starting USB...
USB0:   Core Release: 2.80a
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
U-Boot> mmc dev 0:0
switch to partitions #0, OK
mmc0 is current device
U-Boot> ext4load mmc 0:2 0x200000 uvmmnext.bin
1594184 bytes read in 164 ms (9.3 MiB/s)
U-Boot> ext4load mmc 0:2 0x2000000 udisk_512M.img
33554496 bytes read in 2042 ms (15.7 MiB/s)
U-Boot> ext4load mmc 0:2 0x800000 bcm2837-rpi-3-b.dtb
3787 bytes read in 38 ms (96.7 KiB/s)
U-Boot> bootm 0x200000 0x2000000 0x800000
## Booting kernel from Legacy Image at 00200000 ...
   Image Name:   Xvisor
   Image Type:   AArch64 Linux Kernel Image (uncompressed)
   Data Size:    1594120 Bytes = 1.5 MiB
   Load Address: 00080000
   Entry Point:  00080000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02000000 ...
   Image Name:   Xvisor Ramdisk
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    33554432 Bytes = 32 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 00800000
   Booting using the fdt blob at 0x800000
   Loading Kernel Image ... OK
   reserving fdt memory region: addr=0 size=8000
   Using Device Tree in place at 0000000000800000, end 0000000000803eca

Starting kernel ...

To view this discussion on the web visit https://groups.google.com/d/msgid/xvisor-devel/CAAhSdy11zoAg7783Os8CNo3a_PDvUU0WqP8Yovgg06mxxymz8Q%40mail.gmail.com.

[Stéphane R.]

Hi,

When I changed u-boot version to 2020 version, it boots but my problem is with the u-boot-2020 I can't see the partitions of my SD card then I can't pursue the steps I did before with the fs on SD. I don't know if this aspect is u-boot's problem or xvisor's.

Regards

[Anup Patel]

Hi Stephane,

Thanks for investigating it. Currently, I don't have access to my RPi3
board but I have requested Bhargav to look into this.

My apologies for the slow response.

Regards,
Anup

On Tue, Jul 28, 2020 at 7:12 PM Stéphane R.

> To view this discussion on the web visit https://groups.google.com/d/msgid/xvisor-devel/CACvx%3D6mg-f3d7wpVpNXReDb-KwEgwMfhHN%3DzFQMxgHPxALFXmA%40mail.gmail.com.