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

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, booting th e kernel. Linux version 2.4.27-uc1 (dchou@localhost) (gcc version 3.3.2) #3 Wed Nov 23 15:

09:23 PST 2005 CPU: XScale-IXP4xx/IXC11xx revision 1 Machine: Intel IXDP425 Development Platform Warning: bad configuration page, trying to continue alloc_bootmem_low memtable_init On node 0 totalpages: 4096 zone(0): 4096 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: console=ttyS0,115200 root=/dev/ram0 initrd=0x00200000,4M me m=16M@0x00000000 Calibrating delay loop... 266.24 BogoMIPS Memory: 16MB = 16MB total Memory: 10616KB available (1153K code, 239K data, 64K init) Dentry cache hash table entries: 2048 (order: 2, 16384 bytes) Inode cache hash table entries: 1024 (order: 1, 8192 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table entries: 4096 (order: 2, 16384 bytes) POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis Communications AB. pty: 256 Unix98 ptys configured Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI en abled ttyS00 at 0xff000003 (irq = 15) is a XScale UART ttyS01 at 0xff001003 (irq = 13) is a XScale UART ttyS02 at 0xf1000003 (irq = 6) is a TI16750 ttyS03 at 0xf2000003 (irq = 6) is a TI16750 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize cfi_cmdset_0001: Erase suspend on write enabled Using buffer write method Creating 5 MTD partitions on "IXP425 Flash": 0x00000000-0x00040000 : "RedBoot" 0x00040000-0x000e0000 : "zimage" 0x000e0000-0x002e0000 : "ramdisk" 0x003e0000-0x003ff000 : "FIS directory" mtd: partition "FIS directory" doesn't end on an erase block -- force read-only 0x003ff000-0x00400000 : "RedBoot config" mtd: partition "RedBoot config" doesn't start on an erase block boundary -- forc e read-only NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 1024 bind 2048) NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. NetWinder Floating Point Emulator V0.97 (double precision) 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
Reply to
dchou4u
Loading thread data ...

snip...

4096K

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

Reply to
Chuck Gales

Chuck:

Thanks for the tip. Can you please advise which file I should change? I searched for the tree for this symbol and found multiple places where it is defined for my target.

Thanks a million!

Reply to
dchou4u

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.