LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware > Linux - Embedded & Single-board computer
User Name
Password
Linux - Embedded & Single-board computer This forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.

Notices


Reply
  Search this Thread
Old 06-05-2015, 07:41 PM   #1
tilman1
Member
 
Registered: Mar 2007
Location: Stuttgart, Germany
Distribution: gentoo
Posts: 72

Rep: Reputation: 15
Linux kernel cannot mount jffs2 image


Hello

The LCU1 is a single board computer produced by ELV. The processor is a ARM926EJ-S, RAM size is 64 MB, the root file system (Jffs2) is on a 256 MiB NAND, and the kernel and u-boot loader are stored in a AT45DB642.

ELV provides a firmware package based on buildroot (version from 2011), and kernel version 2.6.31.6-svn45943. The tool chain is outdated, and hence the firmware did not compile any more on an ubunutu 14.04 host. I swapped buildroot for a more recent version from February 2015. The tool chain now compiles and produces a jffs2 image. The kernel seems however not be able to mount it and reboots:

Code:
...
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc-at91sam9 at91_rtt.0: setting system clock to 1970-01-01 11:44:30 UTC (42270)
VFS: Mounted root (jffs2 filesystem) readonly on device 31:0.
Freeing init memory: 132K
Kernel panic - not syncing: Attempted to kill init!
Backtrace: 
[<c002d7dc>] (dump_backtrace+0x0/0x10c) from [<c02961c4>] (dump_stack+0x18/0x1c)
 r7:c3825ed4 r6:c3822000 r5:c3822000 r4:c033fe98
[<c02961ac>] (dump_stack+0x0/0x1c) from [<c0296218>] (panic+0x50/0x12c)
[<c02961c8>] (panic+0x0/0x12c) from [<c0043cf4>] (do_exit+0x6c/0x658)
 r3:c033fe98 r2:00000000 r1:c3825d10 r0:c02f88c3
[<c0043c88>] (do_exit+0x0/0x658) from [<c00443a0>] (do_group_exit+0xc0/0xf4)
[<c00442e0>] (do_group_exit+0x0/0xf4) from [<c004f8dc>] (get_signal_to_deliver+0x3d4/0x434)
 r4:c3824000
[<c004f508>] (get_signal_to_deliver+0x0/0x434) from [<c002c0e8>] (do_signal+0x58/0x524)
[<c002c090>] (do_signal+0x0/0x524) from [<c002c5e0>] (do_notify_resume+0x2c/0x30)
[<c002c5b4>] (do_notify_resume+0x0/0x30) from [<c0029eec>] (work_pending+0x1c/0x20)
RomBOOT
AT91Bootstrap-2.10...AT45DB642D detected
>From:  [0x00008400] To:        [0x23F00000] Size:      [0x00040000] 
........SUCCESS
>Start: [0x23F00000] 

U-Boot 2009.08-svn47665 (Jun 20 2011 - 11:08:57)

DRAM:  64 MB
NAND:  256 MiB
DataFlash:AT45DB642
Nb pages:   8192
Page Size:   1056
Size= 8650752 bytes
Logical address: 0xC0000000
Area 0: C0000000 to C00041FF (RO) Bootstrap
Area 1: C0004200 to C00083FF      Environment
Area 2: C0008400 to C0041FFF (RO) U-Boot
Area 3: C0042000 to C0251FFF      Kernel
Area 4: C0252000 to C0461FFF      Rescue-Kernel
In:    serial
Out:   serial
Err:   serial
Net:   dm9000
dm9000 i/o: 0x30000000, id: 0x90000a46 
DM9000: running in 16 bit mode
Does anybody have suggestions on how to fix it ? Do, for instance, the kernel versions, their respective jffs2 drivers, and the tool 'mkfs.jffs2' that produces the image need to match, i.e. does the new version of mkfs.jffs2 produce an jffs2 image that the jffs2 driver of the old 2.6.31 kernel cannot read ?

Thanks

Tilman
 
Old 06-14-2015, 11:41 AM   #2
Keruskerfuerst
Senior Member
 
Registered: Oct 2005
Location: Horgau, Germany
Distribution: Manjaro KDE, Win 10
Posts: 2,199

Rep: Reputation: 164Reputation: 164
It seems your kernel is not build correctly.
 
Old 06-15-2015, 08:09 AM   #3
tilman1
Member
 
Registered: Mar 2007
Location: Stuttgart, Germany
Distribution: gentoo
Posts: 72

Original Poster
Rep: Reputation: 15
Not sure if the kernel does not build correctly:
- The kernel boots and mounts a jffs image generated with an old build-root chain from 2009. Unfortunately, I have no old distribution at my disposal, o I cannot try to regenerate the kernal image.
- If I flash the newly created rootfs (generated by a recent build-root version from early 2015) than the boot process stops.
- The error message(oops-message) of the kernel suggest that the init process terminates.

I would hence think the root-file-system has a problem. I am not sure however how to tackle this. Suggestions are welcome...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Unable to mount NOR Flash (mount -t jffs2 /dev/mtdblock0 /mnt) cruiser Linux - Embedded & Single-board computer 2 08-28-2012 10:50 PM
JFFS2 [VFS mount root /dev/mtdblock2 ok] - kernel panic on running init process sud_vijay Linux - Kernel 0 03-05-2008 11:05 AM
Redboot - Loading Kernel Image & File Jffs2 MKSrivastava Debian 1 04-21-2007 08:03 PM
tool to write JFFS2 image on CF newbieMhke Linux - Software 1 07-25-2006 10:03 AM
How do I create a jffs2 loopback image? rjlee Linux - General 0 04-22-2006 01:02 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware > Linux - Embedded & Single-board computer

All times are GMT -5. The time now is 04:25 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration