element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Software Application Development XilinxLinux 2013.4 Kernel Panic
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Avnet Boards Forums requires membership for participation - click to join
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 6 replies
  • Subscribers 303 subscribers
  • Views 538 views
  • Users 0 members are here
Related

XilinxLinux 2013.4 Kernel Panic

Former Member
Former Member over 11 years ago

Hi.
I have a big problem using Xilinx Linux - branch Xilinx-v2013.4
First, I successfully finished Speedway tutorial and my linux has run on target.
Now I want to use the latest stable version of Xilinx Linux for ZedBoard. Result:
Kernel Panic!
In detail, my problem looks like:

[...]
RAMDISK: gzip image found at block 0
RAMDISK: incomplete write (18154 != 32768)
write error
VFS: Mounted root (ext2 filesystem) on device 1:0.
EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=6145, block=24708
devtmpfs: error mounting -5
Freeing unused kernel memory: 172K (c056b000 - c0596000)
EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=4097, block=16387
EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=4097, block=16387
EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=4097, block=16387
Kernel panic - not syncing: No init found.  Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
CPU0: stopping
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.12.0-xilinx #1
[<c0014ef8>] (unwind_backtrace+0x0/0x11c) from [<c0011404>] (show_stack+0x10/0x14)
[<c0011404>] (show_stack+0x10/0x14) from [<c03ea514>] (dump_stack+0x84/0xc8)
[<c03ea514>] (dump_stack+0x84/0xc8) from [<c00137b0>] (ipi_cpu_stop+0x3c/0x6c)
[<c00137b0>] (ipi_cpu_stop+0x3c/0x6c) from [<c0013dc0>] (handle_IPI+0x64/0xa8)
[<c0013dc0>] (handle_IPI+0x64/0xa8) from [<c00084e0>] (gic_handle_irq+0x54/0x5c)
[<c00084e0>] (gic_handle_irq+0x54/0x5c) from [<c0011e80>] (__irq_svc+0x40/0x70)
Exception stack(0xc0599f70 to 0xc0599fb8)
9f60:                                     c0a0c9f0 00000000 00000000 00000000
9f80: c0599fc0 00000000 ffffffff c058d950 c0a09200 413fc090 00000000 00000000
9fa0: c0a0c9fc c0599fb8 c000ef9c c000efa0 60000113 ffffffff
[<c0011e80>] (__irq_svc+0x40/0x70) from [<c000efa0>] (arch_cpu_idle+0x24/0x2c)
[<c000efa0>] (arch_cpu_idle+0x24/0x2c) from [<c0052e64>] (cpu_startup_entry+0xb8/0x12c)
[<c0052e64>] (cpu_startup_entry+0xb8/0x12c) from [<c056ba2c>] (start_kernel+0x2b0/0x304)


What I did:
* built my fsbl, bitstream and u-boot (same branch as mentioned above), merged it to the boot.bin with sdk-xilinx tools...
* built my ramdisk image, like it is described in speedway tutorial, and wrapped it with u-boot tools to uramdisk...
* built the kernel with additional arguments for u-boot header (...0x8000 ...)
* built the device tree with modified parameters for:
->uFFFCbootargs = "console=ttyPS0,115200 root=/dev/ram rw ip=192.168.1.10 earlyp- rintk";

->mdio:
mdio {
tttt#address-cells = <1>;
tttt#size-cells = <0>;
ttttphy0: phy@0 {
tttttcompatible = "marvell,88e1510";
tttttdevice_type = "ethernet-phy";
tttttreg = <0>;
tttttmarvell,reg-init = <3 16 0xff00 0x1e 3 17 0xff0 0x0a>;
tttt} ;
and sdio frequency, set to 33333000

It is still not working.
Does anybody know y?
Thanks in advance

  • Sign in to reply
  • Cancel
Parents
  • Former Member
    0 Former Member over 11 years ago

    Modify the file as follw:
    /linux-xlnx-xilinxv14.7/arch/arm/configs/xilinx_zynq_defconfig

    The contents that will be changed as follow:
    CONFIG_BLK_DEV_RAM_COUNT=8
    CONFIG_BLK_DEV_RAM_SIZE=32768

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • Former Member
    0 Former Member over 11 years ago

    Modify the file as follw:
    /linux-xlnx-xilinxv14.7/arch/arm/configs/xilinx_zynq_defconfig

    The contents that will be changed as follow:
    CONFIG_BLK_DEV_RAM_COUNT=8
    CONFIG_BLK_DEV_RAM_SIZE=32768

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube