From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: v3.4 boot failure on qemu-system-arm -M versatilepb
Date: Tue, 29 May 2012 15:02:41 -0500 [thread overview]
Message-ID: <4FC52B61.2000604@gmail.com> (raw)
In-Reply-To: <XNM1$5$0$1$$3$9$0$A$8005401U4fc38a01@hitachi.com>
Adding linux-arm-kernel...
On 05/28/2012 09:22 AM, takuo.koguchi.sw at hitachi.com 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
>
>
> ----------- Uncompressing Linux... done, booting the kernel. Booting
> Linux on physical CPU 0 Initializing cgroup subsys cpuset
> Initializing cgroup subsys cpu Linux version 3.4.0-yocto-standard
> (koguchi at mg70k) (gcc version 4.5.2 (Sourcery G++ Lite 2011.03-41) )
> #37 PREEMPT Sun May 27 22:36:22 JST 2012 CPU: ARM926EJ-S [41069265]
> revision 5 (ARMv5TEJ), cr=00093177 CPU: VIVT data cache, VIVT
> instruction cache Machine: ARM-Versatile PB ... eth0: link up
> IP-Config: Complete: device=eth0, addr=192.168.7.3,
> mask=255.255.255.0, gw=192.168.7.1 host=192.168.7.3, domain=,
> nis-domain=(none) bootserver=255.255.255.255,
> rootserver=255.255.255.255, rootpath= input: AT Raw Set 2 keyboard as
> /devices/fpga:06/serio0/input/input0 md: Skipping autodetection of
> RAID arrays. (raid=autodetect will force) VFS: Cannot open root
> device "0x0800" or unknown-block(8,0): error -6 Please append a
> correct "root=" boot option; here are the available partitions:
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(8,0) [<c0013870>] (unwind_backtrace+0x0/0xec) from
> [<c0389b68>] (dump_stack+0x20/0x24) [<c0389b68>]
> (dump_stack+0x20/0x24) from [<c0389bf4>] (panic+0x88/0x1c4)
> [<c0389bf4>] (panic+0x88/0x1c4) from [<c04fbde8>]
> (mount_block_root+0x240/0x290) [<c04fbde8>]
> (mount_block_root+0x240/0x290) from [<c04fbf80>]
> (mount_root+0x50/0x68) [<c04fbf80>] (mount_root+0x50/0x68) from
> [<c04fc108>] (prepare_namespace+0x170/0x1d0) [<c04fc108>]
> (prepare_namespace+0x170/0x1d0) from [<c04fba08>]
> (kernel_init+0x1bc/0x204) [<c04fba08>] (kernel_init+0x1bc/0x204) from
> [<c000e7dc>] (kernel_thread_exit+0x0/0x8)
>
>
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robherring2@gmail.com>
To: takuo.koguchi.sw@hitachi.com
Cc: linux-kernel@vger.kernel.org, linus.walleij@linaro.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: v3.4 boot failure on qemu-system-arm -M versatilepb
Date: Tue, 29 May 2012 15:02:41 -0500 [thread overview]
Message-ID: <4FC52B61.2000604@gmail.com> (raw)
In-Reply-To: <XNM1$5$0$1$$3$9$0$A$8005401U4fc38a01@hitachi.com>
Adding linux-arm-kernel...
On 05/28/2012 09:22 AM, takuo.koguchi.sw@hitachi.com 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
>
>
> ----------- Uncompressing Linux... done, booting the kernel. Booting
> Linux on physical CPU 0 Initializing cgroup subsys cpuset
> Initializing cgroup subsys cpu Linux version 3.4.0-yocto-standard
> (koguchi@mg70k) (gcc version 4.5.2 (Sourcery G++ Lite 2011.03-41) )
> #37 PREEMPT Sun May 27 22:36:22 JST 2012 CPU: ARM926EJ-S [41069265]
> revision 5 (ARMv5TEJ), cr=00093177 CPU: VIVT data cache, VIVT
> instruction cache Machine: ARM-Versatile PB ... eth0: link up
> IP-Config: Complete: device=eth0, addr=192.168.7.3,
> mask=255.255.255.0, gw=192.168.7.1 host=192.168.7.3, domain=,
> nis-domain=(none) bootserver=255.255.255.255,
> rootserver=255.255.255.255, rootpath= input: AT Raw Set 2 keyboard as
> /devices/fpga:06/serio0/input/input0 md: Skipping autodetection of
> RAID arrays. (raid=autodetect will force) VFS: Cannot open root
> device "0x0800" or unknown-block(8,0): error -6 Please append a
> correct "root=" boot option; here are the available partitions:
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(8,0) [<c0013870>] (unwind_backtrace+0x0/0xec) from
> [<c0389b68>] (dump_stack+0x20/0x24) [<c0389b68>]
> (dump_stack+0x20/0x24) from [<c0389bf4>] (panic+0x88/0x1c4)
> [<c0389bf4>] (panic+0x88/0x1c4) from [<c04fbde8>]
> (mount_block_root+0x240/0x290) [<c04fbde8>]
> (mount_block_root+0x240/0x290) from [<c04fbf80>]
> (mount_root+0x50/0x68) [<c04fbf80>] (mount_root+0x50/0x68) from
> [<c04fc108>] (prepare_namespace+0x170/0x1d0) [<c04fc108>]
> (prepare_namespace+0x170/0x1d0) from [<c04fba08>]
> (kernel_init+0x1bc/0x204) [<c04fba08>] (kernel_init+0x1bc/0x204) from
> [<c000e7dc>] (kernel_thread_exit+0x0/0x8)
>
>
>
>
next prev parent reply other threads:[~2012-05-29 20:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 14:22 v3.4 boot failure on qemu-system-arm -M versatilepb takuo.koguchi.sw
2012-05-29 20:02 ` Rob Herring [this message]
2012-05-29 20:02 ` Rob Herring
2012-05-30 9:33 ` Re[2]: " takuo.koguchi.sw
2012-05-30 15:37 ` Re[3]: " takuo.koguchi.sw at hitachi.com
2012-05-30 15:37 ` takuo.koguchi.sw
2012-06-11 8:15 ` Ben Dooks
2012-06-11 8:28 ` Russell King - ARM Linux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FC52B61.2000604@gmail.com \
--to=robherring2@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.