Armadilloフォーラム

電源ON時、kernel panicがでて起動できない

m.takahashi

2014年6月17日 12時17分

高橋と申します。

今まで、armadillo-440のmicroSDにdevianを構築して開発を行っていたのですが、
このたびフラッシュメモリからの起動を行おうと、
保守モードで起動し、下記コマンドを打ち込んだところ、

>setbootdevice flash
>clearev
>boot

下記のようなエラーが出て途中で止まってしまいました。

No iflesystem could mount root, tried: ext3 ext2 msdos vfat
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

起動に必要なファイルが壊れてしまったのかと思い、
【Armadillo-400 シリーズソフトウェアマニュアル】に基づいて

6.6.ブートローダーを出荷状態に戻す
6.フラッシュメモリの書き換え方法

を試してみましたが、状態は変わりませんでした。
どうしたらフラッシュメモリからの起動ができるようになるでしょうか?

組み込み開発にもlinuxにも不慣れなため、質問も曖昧かもしれませんが、
アドバイスをいただきたいとおもいます。

以下起動時のログになります。

------------------------------------------------------------------------------------------------------------------------------------

Linux version 2.6.26-at18 (2.6.26) (atmark@atde3) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 PREEMPT Tue Jun 4 13:43:16 JST 2013
CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177
Machine: Armadillo-440
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
Kernel command line: console=ttymxc1,115200
MXC IRQ initialized
PID hash table entries: 512 (order: 9, 2048 bytes)
MXC GPT timer initialized, rate = 133000000
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 75600KB available (3260K code, 225K data, 128K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 480 bytes
NET: Registered protocol family 16
MXC WDOG1 Enabled
CPU is i.MX25 Revision 1.2
Clock input source is 24000000
MXC GPIO hardware
GPIO-56 autorequested
Using SDMA I.API
MXC DMA API initialized
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
MXC I2C driver
MXC I2C driver
MXC I2C driver
MC34704 regulator successfully probed
mc34704 0-0054: Loaded
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
NET: Registered protocol family 1
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd
Freeing initrd memory: 50574K
usb: Host 2 host (serial) registered
usb: DR host (utmi) registered
msgmni has been set to 246
io scheduler noop registered
io scheduler cfq registered (default)
mx2fb: Unable to set clock to 0
Console: switching to colour frame buffer device 60x17
mxc_sdc_fb mxc_sdc_fb.0: fb0: DISP0 BG fb device registered successfully.
mxc_sdc_fb mxc_sdc_fb.0: fb1: DISP0 FG fb device registered successfully.
Serial: MXC Internal UART driver
mxcintuart.1: ttymxc1 at MMIO 0x43f94000 (irq = 32) is a Freescale MXC
console [ttymxc1] enabled
mxcintuart.2: ttymxc2 at MMIO 0x5000c000 (irq = 18) is a Freescale MXC
mxcintuart.4: ttymxc4 at MMIO 0x5002c000 (irq = 40) is a Freescale MXC
brd: module loaded
loop: module loaded
FEC Ethernet Driver
PPP generic driver version 2.4.2
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
Driver 'sd' needs updating - please use bus_type methods
armadillo-nor: Found 1 x16 devices at 0x0 in 16-bit bank
Intel/Sharp Extended Query Table at 0x010A
Intel/Sharp Extended Query Table at 0x010A
Intel/Sharp Extended Query Table at 0x010A
Intel/Sharp Extended Query Table at 0x010A
Intel/Sharp Extended Query Table at 0x010A
Using buffer write method
Using auto-unlock on power-up/resume
cfi_cmdset_0001: Erase suspend on write enabled
armadillo-nor: use default partitions(4)
Creating 4 MTD partitions on "armadillo-nor":
0x00000000-0x00020000 : "nor.bootloader"
0x00020000-0x00220000 : "nor.kernel"
0x00220000-0x01fe0000 : "nor.userland"
0x01fe0000-0x02000000 : "nor.config"
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.0: irq 35, io mem 0x53ff4400
fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
fsl-ehci fsl-ehci.1: irq 37, io mem 0x53ff4000
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
input: gpio-keys as /devices/platform/gpio-keys.0/input/input0
rtc-s35390a 1-0030: error resetting chip
rtc-s35390a: probe of 1-0030 failed with error -5
rtc-s35390a 2-0030: rtc core: registered rtc-s35390a as rtc0
i2c /dev entries driver
mxsdhci: MXC Secure Digital Host Controller Interface driver
mxsdhci: MXC SDHCI Controller Driver.
mmc0: SDHCI detect irq 159 irq 9 INTERNAL DMA
Registered led device: red
Registered led device: green
Registered led device: yellow
usb 2-1: new low speed USB device using fsl-ehci and address 2
usb 2-1: configuration #1 chosen from 1 choice
input: CHICONY USB NetVista Full Width Keyboard as /devices/platform/fsl-ehci.1/usb2/2-1/2-1:1.0/input/input1
input: USB HID v1.10 Keyboard [CHICONY USB NetVista Full Width Keyboard] on usb-fsl-ehci.1-1
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
i.MX ADC at 0x50030000 irq 46
Advanced Linux Sound Architecture Driver Version 1.0.16.
usbcore: registered new interface driver snd-usb-audio
usbcore: registered new interface driver snd-usb-caiaq
ASoC version 0.13.2
wm8978: WM8978 Audio Codec v0.2
asoc: WM8978 HiFi <-> imx-i2s-1 mapping ok
ALSA device list:
#0: armadillo440 (WM8978)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Static Power Management for Freescale i.MX25
input: imx_adc_ts as /devices/virtual/input/input2
i.MX ADC input touchscreen loaded.
rtc-s35390a 2-0030: setting system clock to 2000-01-01 00:23:15 UTC (946686195)
RAMDISK: ext2 filesystem found at block 0
RAMDISK: image too big! (50574KiB/32768KiB)
List of all partitions:
1f00 128 mtdblock0 (driver?)
1f01 2048 mtdblock1 (driver?)
1f02 30464 mtdblock2 (driver?)
1f03 128 mtdblock3 (driver?)
No filesystem could mount root, tried: ext3 ext2 msdos vfat
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

------------------------------------------------------------------------------------------------------------------------------------

以上よろしくお願いいたします。

コメント

高橋です。自己解決しました。

大変申し訳ありません。下記のページをみて原因がわかりました。

【Howto : Armadillo-440でQt! 第1回】
http://armadillo.atmark-techno.com/howto/armadillo-440-qt-1

「RAMDISK: image too big!」とのメッセージが示すように、RAMDISKのデフォルトサイズ(32MB)をオーバーしていたようです。
このページに従い、【RAMDISKのサイズを64MB(61440kB)に設定】したところ、解決しました。

大変お騒がせいたしました。

> 高橋と申します。
>
> 今まで、armadillo-440のmicroSDにdevianを構築して開発を行っていたのですが、
> このたびフラッシュメモリからの起動を行おうと、
> 保守モードで起動し、下記コマンドを打ち込んだところ、
>
> >setbootdevice flash
> >clearev
> >boot
>
> 下記のようなエラーが出て途中で止まってしまいました。
>
> No iflesystem could mount root, tried: ext3 ext2 msdos vfat
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
>
> 起動に必要なファイルが壊れてしまったのかと思い、
> 【Armadillo-400 シリーズソフトウェアマニュアル】に基づいて
>
> 6.6.ブートローダーを出荷状態に戻す
> 6.フラッシュメモリの書き換え方法
>
> を試してみましたが、状態は変わりませんでした。
> どうしたらフラッシュメモリからの起動ができるようになるでしょうか?
>
> 組み込み開発にもlinuxにも不慣れなため、質問も曖昧かもしれませんが、
> アドバイスをいただきたいとおもいます。
>
> 以下起動時のログになります。
>
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Linux version 2.6.26-at18 (2.6.26) (atmark@atde3) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 PREEMPT Tue Jun 4 13:43:16 JST 2013
> CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177
> Machine: Armadillo-440
> Memory policy: ECC disabled, Data cache writeback
> CPU0: D VIVT write-back cache
> CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
> CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
> Kernel command line: console=ttymxc1,115200
> MXC IRQ initialized
> PID hash table entries: 512 (order: 9, 2048 bytes)
> MXC GPT timer initialized, rate = 133000000
> Console: colour dummy device 80x30
> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> Memory: 128MB = 128MB total
> Memory: 75600KB available (3260K code, 225K data, 128K init)
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> net_namespace: 480 bytes
> NET: Registered protocol family 16
> MXC WDOG1 Enabled
> CPU is i.MX25 Revision 1.2
> Clock input source is 24000000
> MXC GPIO hardware
> GPIO-56 autorequested
> Using SDMA I.API
> MXC DMA API initialized
> SCSI subsystem initialized
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> MXC I2C driver
> MXC I2C driver
> MXC I2C driver
> MC34704 regulator successfully probed
> mc34704 0-0054: Loaded
> NET: Registered protocol family 2
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> TCP established hash table entries: 4096 (order: 3, 32768 bytes)
> TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
> TCP: Hash tables configured (established 4096 bind 4096)
> TCP reno registered
> NET: Registered protocol family 1
> checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd
> Freeing initrd memory: 50574K
> usb: Host 2 host (serial) registered
> usb: DR host (utmi) registered
> msgmni has been set to 246
> io scheduler noop registered
> io scheduler cfq registered (default)
> mx2fb: Unable to set clock to 0
> Console: switching to colour frame buffer device 60x17
> mxc_sdc_fb mxc_sdc_fb.0: fb0: DISP0 BG fb device registered successfully.
> mxc_sdc_fb mxc_sdc_fb.0: fb1: DISP0 FG fb device registered successfully.
> Serial: MXC Internal UART driver
> mxcintuart.1: ttymxc1 at MMIO 0x43f94000 (irq = 32) is a Freescale MXC
> console [ttymxc1] enabled
> mxcintuart.2: ttymxc2 at MMIO 0x5000c000 (irq = 18) is a Freescale MXC
> mxcintuart.4: ttymxc4 at MMIO 0x5002c000 (irq = 40) is a Freescale MXC
> brd: module loaded
> loop: module loaded
> FEC Ethernet Driver
> PPP generic driver version 2.4.2
> Linux video capture interface: v2.00
> usbcore: registered new interface driver uvcvideo
> USB Video Class driver (v0.1.0)
> Driver 'sd' needs updating - please use bus_type methods
> armadillo-nor: Found 1 x16 devices at 0x0 in 16-bit bank
> Intel/Sharp Extended Query Table at 0x010A
> Intel/Sharp Extended Query Table at 0x010A
> Intel/Sharp Extended Query Table at 0x010A
> Intel/Sharp Extended Query Table at 0x010A
> Intel/Sharp Extended Query Table at 0x010A
> Using buffer write method
> Using auto-unlock on power-up/resume
> cfi_cmdset_0001: Erase suspend on write enabled
> armadillo-nor: use default partitions(4)
> Creating 4 MTD partitions on "armadillo-nor":
> 0x00000000-0x00020000 : "nor.bootloader"
> 0x00020000-0x00220000 : "nor.kernel"
> 0x00220000-0x01fe0000 : "nor.userland"
> 0x01fe0000-0x02000000 : "nor.config"
> fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
> fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
> fsl-ehci fsl-ehci.0: irq 35, io mem 0x53ff4400
> fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
> usb usb1: configuration #1 chosen from 1 choice
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 1 port detected
> fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
> fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
> fsl-ehci fsl-ehci.1: irq 37, io mem 0x53ff4000
> fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
> usb usb2: configuration #1 chosen from 1 choice
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 1 port detected
> Initializing USB Mass Storage driver...
> usbcore: registered new interface driver usb-storage
> USB Mass Storage support registered.
> input: gpio-keys as /devices/platform/gpio-keys.0/input/input0
> rtc-s35390a 1-0030: error resetting chip
> rtc-s35390a: probe of 1-0030 failed with error -5
> rtc-s35390a 2-0030: rtc core: registered rtc-s35390a as rtc0
> i2c /dev entries driver
> mxsdhci: MXC Secure Digital Host Controller Interface driver
> mxsdhci: MXC SDHCI Controller Driver.
> mmc0: SDHCI detect irq 159 irq 9 INTERNAL DMA
> Registered led device: red
> Registered led device: green
> Registered led device: yellow
> usb 2-1: new low speed USB device using fsl-ehci and address 2
> usb 2-1: configuration #1 chosen from 1 choice
> input: CHICONY USB NetVista Full Width Keyboard as /devices/platform/fsl-ehci.1/usb2/2-1/2-1:1.0/input/input1
> input: USB HID v1.10 Keyboard [CHICONY USB NetVista Full Width Keyboard] on usb-fsl-ehci.1-1
> usbcore: registered new interface driver usbhid
> usbhid: v2.6:USB HID core driver
> i.MX ADC at 0x50030000 irq 46
> Advanced Linux Sound Architecture Driver Version 1.0.16.
> usbcore: registered new interface driver snd-usb-audio
> usbcore: registered new interface driver snd-usb-caiaq
> ASoC version 0.13.2
> wm8978: WM8978 Audio Codec v0.2
> asoc: WM8978 HiFi <-> imx-i2s-1 mapping ok
> ALSA device list:
> #0: armadillo440 (WM8978)
> ip_tables: (C) 2000-2006 Netfilter Core Team
> TCP cubic registered
> NET: Registered protocol family 17
> NET: Registered protocol family 15
> Static Power Management for Freescale i.MX25
> input: imx_adc_ts as /devices/virtual/input/input2
> i.MX ADC input touchscreen loaded.
> rtc-s35390a 2-0030: setting system clock to 2000-01-01 00:23:15 UTC (946686195)
> RAMDISK: ext2 filesystem found at block 0
> RAMDISK: image too big! (50574KiB/32768KiB)
> List of all partitions:
> 1f00 128 mtdblock0 (driver?)
> 1f01 2048 mtdblock1 (driver?)
> 1f02 30464 mtdblock2 (driver?)
> 1f03 128 mtdblock3 (driver?)
> No filesystem could mount root, tried: ext3 ext2 msdos vfat
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
>
>
> ------------------------------------------------------------------------------------------------------------------------------------
>
> 以上よろしくお願いいたします。
>