Re[2]: v3.4 boot failure on qemu-system-arm -M versatilepb

[takuo.koguchi.sw]

Hi Rob,

Thank you for your attention.

>What config are you using, and what is your kernel command line?

I used versatile_defconfig.
And I invoked qemu as follows,
$ sudo qemu-system-arm -machine versatilepb -kernel ~/linux/arch/arm/boot/zImage -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=no,downscript=no -hda output/images/rootfs.ext2 -append "console=ttyAMA0 root=0x0800 ip=192.168.7.3::192.168.7.1:255.255.255.0 raid=noautodetect"

The result is the same even if root=/dev/sda.

currently __io(a) is defined in arch/arm/include/asm/io.h
#define __io(a)		__typesafe_io((a) & IO_SPACE_LIMIT)
...

As CONFIG_PCI is defined in the config, IO_SPACE_LIMIT is defined as 0xffff and failed to boot.
The kernel can mount rootfs when I defined IO_SPACE_LIMIT as follows,
#define IO_SPACE_LIMIT ((resource_size_t)0xffffffff)

It may be related only to qemu and not to real versatile board.

Takuo Koguchi





>Adding linux-arm-kernel...
>
>On 05/28/2012 09:22 AM, takuo.koguchi.sw@xxxxxxxxxxx wrote:
>> Hi,
>> 
>> I found linux-3.4 kernel fails to mount the rootfs on
>> "qemu-system-arm -M versatile."
>> 
>> Git bisect shows commit c334bc1 cause this first.
>> 
>> So I tried to revert it by putting
>> arch/arm/mach-versatile/include/mach/io.h and adding select
>> NEED_MACH_IO_H in the section of ARCH_VERSATILE in arch/arm/Kconfig,
>> then the kernel can mount the rootfs.
>> 
>> Can someone confirm and fix this?
>> 
>
>What config are you using, and what is your kernel command line?
>
>Rob
>
>> Takuo Koguchi
>> 
>>