Discussion:
[Qemu-discuss] Unable to boot imx6q base sabrelite linux kernel on QEMU.
Bilal, Muhammad
2018-11-27 06:28:41 UTC
Permalink
Hi,


What is the right command to emulate linux kernel for sabrelite machine ?


I'm trying to emulate imx6q linux kernel with following command line.


qemu-system-arm -m 1G -M sabrelite -kernel zImage -drive file=console-image-mx6q-rootfs.ext3,format=raw,id=mycard -device sd-card,drive=mycard -append "console=ttymxc0 rootfstype=ext4 root=/dev/mmcblk0p0 rw rootwait init=/sbin/init" -nographic -dtb zImage-imx6q-sabrelite.dtb -smp 4

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 4.1.37 (***@svr-pkl-qatools-2) (gcc version 6.2.0 (Sourcery CodeBench 2016.11-98) ) #1 SMP PREEMPT Fri May 25 15:56:29 PKT 2018
[ 0.000000] CPU: ARMv7 Processor [410fc090] revision 0 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine model: Freescale i.MX6 Quad SABRE Lite Board
[ 0.000000] Reserved memory: created CMA memory pool at 0x2a000000, size 320 MiB


......


it starts to boot up just fine. But then:




[ 5.460895] usbcore: registered new interface driver bcm203x
[ 5.462092] usbcore: registered new interface driver btusb
[ 5.463196] usbcore: registered new interface driver ath3k
[ 5.471001] sdhci: Secure Digital Host Controller Interface driver
[ 5.471435] sdhci: Copyright(c) Pierre Ossman
[ 5.471829] sdhci-pltfm: SDHCI platform and OF driver helper
[ 5.481562] /soc/aips-***@02100000/***@02198000: voltage-ranges unspecified
[ 5.482463] sdhci-esdhc-imx 2198000.usdhc: could not get ultra high speed state, work on normal mode
[ 5.485128] sdhci-esdhc-imx 2198000.usdhc: Got CD GPIO
[ 5.486055] sdhci-esdhc-imx 2198000.usdhc: Got WP GPIO
[ 5.494484] sdhci-esdhc-imx 2198000.usdhc: No vqmmc regulator found
[ 5.623722] mmc0: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA
[ 5.629278] /soc/aips-***@02100000/***@0219c000: voltage-ranges unspecified
[ 5.629725] sdhci-esdhc-imx 219c000.usdhc: could not get ultra high speed state, work on normal mode
[ 5.630417] sdhci-esdhc-imx 219c000.usdhc: Got CD GPIO
[ 5.632790] sdhci-esdhc-imx 219c000.usdhc: No vqmmc regulator found
[ 5.786895] mmc1: SDHCI controller on 219c000.usdhc [219c000.usdhc] using ADMA
[ 5.810687] mxc_vpu 2040000.vpu_fsl: VPU initialized
[ 5.819767] mxc_vdoa 21e4000.vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
[ 5.830917] Galcore version 5.0.11.41671
[ 15.631444] mmc0: Timeout waiting for hardware interrupt. retries left=0 opcode=34
[ 15.856535] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=34
[ 15.898265] mmc1: host does not support reading read-only switch, assuming write-enable
[ 15.900140] mmc1: Problem switching card into high-speed mode!
[ 15.906535] mmc1: new SD card at address 4567
[ 15.918145] mmcblk1: mmc1:4567 QEMU! 396 MiB
[ 25.710192] mmc0: Timeout waiting for hardware interrupt. retries left=0 opcode=34
[ 35.791966] mmc0: Timeout waiting for hardware interrupt. retries left=0 opcode=34
[ 45.872764] mmc0: Timeout waiting for hardware interrupt. retries left=0 opcode=34



Keeps waiting forever here ...


Can anyone please suggest what's going wrong here ?


Thanks,
-Bilal
Peter Maydell
2018-11-27 09:53:18 UTC
Permalink
On Tue, 27 Nov 2018 at 06:29, Bilal, Muhammad <***@mentor.com> wrote:

> [ 15.631444] mmc0: Timeout waiting for hardware interrupt. retries left=0 opcode=34
> [ 15.856535] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=34
> [ 15.898265] mmc1: host does not support reading read-only switch, assuming write-enable
> [ 15.900140] mmc1: Problem switching card into high-speed mode!
> [ 15.906535] mmc1: new SD card at address 4567
> [ 15.918145] mmcblk1: mmc1:4567 QEMU! 396 MiB
> [ 25.710192] mmc0: Timeout waiting for hardware interrupt. retries left=0 opcode=34
> [ 35.791966] mmc0: Timeout waiting for hardware interrupt. retries left=0 opcode=34
> [ 45.872764] mmc0: Timeout waiting for hardware interrupt. retries left=0 opcode=34
>
>
>
> Keeps waiting forever here ...

Which QEMU version are you running? We did fix a bug in
the imx mmc controller emulation; the fix for that is in
2.12 or later. Try the current 3.0 rc2 if you aren't already,
just to check if it's something we've fixed.

thanks
-- PMM
Bilal, Muhammad
2018-11-27 10:04:21 UTC
Permalink
sorry, but i'm already using current 3.1 rc2 for this.

________________________________________
From: Peter Maydell <***@linaro.org>
Sent: Tuesday, November 27, 2018 2:53 PM
To: Bilal, Muhammad
Cc: qemu-discuss
Subject: Re: [Qemu-discuss] Unable to boot imx6q base sabrelite linux kernel on QEMU.

On Tue, 27 Nov 2018 at 06:29, Bilal, Muhammad <***@mentor.com> wrote:

> [ 15.631444] mmc0: Timeout waiting for hardware interrupt. retries left=0 opcode=34
> [ 15.856535] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=34
> [ 15.898265] mmc1: host does not support reading read-only switch, assuming write-enable
> [ 15.900140] mmc1: Problem switching card into high-speed mode!
> [ 15.906535] mmc1: new SD card at address 4567
> [ 15.918145] mmcblk1: mmc1:4567 QEMU! 396 MiB
> [ 25.710192] mmc0: Timeout waiting for hardware interrupt. retries left=0 opcode=34
> [ 35.791966] mmc0: Timeout waiting for hardware interrupt. retries left=0 opcode=34
> [ 45.872764] mmc0: Timeout waiting for hardware interrupt. retries left=0 opcode=34
>
>
>
> Keeps waiting forever here ...

Which QEMU version are you running? We did fix a bug in
the imx mmc controller emulation; the fix for that is in
2.12 or later. Try the current 3.0 rc2 if you aren't already,
just to check if it's something we've fixed.

thanks
-- PMM
Loading...