Re: ERROR: 01:00: rw=0, want=5218, limit=4096

From: Chuck Gales (cgales_at_gmail.com)
Date: 11/24/05


Date: Thu, 24 Nov 2005 11:18:23 GMT

On Wed, 23 Nov 2005 17:59:23 -0800, dchou4u wrote:

> I have a embedded systems board running Redhat Linux 2.4 kernel. The
> processor is the Intel xscale ARM. The Linux is booted using Redboot,
> and my ramdisk and zimage are both in flash. I am getting the
> want=5128, limit=4096 error and eventually the box hangs.
>
> Any help will be appreciated. Thanks a million!
>
> ####################################################################
> RedBoot>
> Trying NPE-B...success. Using NPE-B with PHY 17.
> Ethernet eth0: MAC address 00:20:4a:ff:ff:15
> IP: 192.168.0.222/255.255.255.0, Gateway: 192.168.0.1 Default server:
> 192.168.0.132
>
> RedBoot(tm) bootstrap and debug environment [ROM] Red Hat certified
> release, version 2.01 - built 21:29:30, Oct 3 2005
>
> Platform: Lantronix 4Port Device Server (XScale) BE Copyright (C) 2000,
> 2001, 2002, 2003, 2004 Red Hat, Inc.
>
> RAM: 0x00000000-0x01000000, [0x000219f0-0x00fc1000] available
> FLASH: 0x50000000 - 0x50400000, 32 blocks of 0x00020000 bytes each.
> == Executing boot script in 1.000 seconds - enter ^C to abort
> RedBoot> fis load ramdisk
> RedBoot> fis load zimage
> RedBoot> go -n 0xc00000
> Uncompressing Linux............................................ done,
snip...
> RAMDISK: Compressed image found at block 0 Freeing initrd memory:
4096K
> VFS: Mounted root (ext2 filesystem) readonly. Freeing init memory: 64K
> attempt to access beyond end of device 01:00: rw=0, want=5218,
> limit=4096
> attempt to access beyond end of device 01:00: rw=0, want=5218,
> limit=4096
> attempt to access beyond end of device 01:00: rw=0, want=5197,
> limit=4096
> attempt to access beyond end of device 01:00: rw=0, want=5197,
> limit=4096
> attempt to access beyond end of device 01:00: rw=0, want=4097,
> limit=4096
> attempt to access beyond end of device 01:00: rw=0, want=4097,
> limit=4096
> attempt to access beyond end of device 01:00: rw=0, want=4097,
> limit=4096

The problem is that your initial ramdisk image is greater than the 4MB you
specified in your kernel configuration. Your best action is to increase
the initial ramdisk size specified in the kernel using the
CONFIG_BLK_DEV_RAM_SIZE parameter. Or, you can reduce the size of your
ramdisk image.

Chuck



Relevant Pages

  • kernel panic when trying to netboot ixp425
    ... it with a custom ramdisk image. ... PCI: IXP4xx Using direct access for memory space ... usbcore: registered new driver usbfs ... Searching for RedBoot partition table in IXP4XX-Flash.0 at offset ...
    (Debian-User)
  • ERROR: 01:00: rw=0, want=5218, limit=4096
    ... I have a embedded systems board running Redhat Linux 2.4 kernel. ... The Linux is booted using Redboot, ... and my ramdisk and zimage are both in flash. ... partition "RedBoot config" doesn't start on an erase block ...
    (comp.os.linux.embedded)
  • Re: Help with using JFFS2 as root filesystem
    ... Ramdisk based file system, how do I link to it once the Linux is ... Or does it have to be done during the kernel configuration? ...
    (comp.os.linux.embedded)