RE: nfs boot problem

Fri, 07 Mar 2008 21:20:12 -0800

Hi,

 

Thanks phil, what u have said is correct "you can't put variables into the kernel command " :).Now my board is working fine.Thanks alot for the suggestion.There is a problem with DHCP also after i solved it, again the board gave kerel panic.But once i replaced the variables with original contnent it started mounting the nfs file system.

 

Now the problem boils down to U-Boot unable to interpret the variables properly that means U-Boot was corrupted.

will come soon with some other problem .. :)

 

thanks

regds

gopi k

--- On Wed, 5/3/08, Phil Quiney <[EMAIL PROTECTED]> wrote:

From: Phil Quiney <[EMAIL PROTECTED]>
Subject: RE: nfs boot problem
To: [EMAIL PROTECTED], "davinci" <[email protected]>
Date: Wednesday, 5 March, 2008, 2:38 PM

Hi Gopi,

Whoever mentioned the fact that you can't put variables into the kernel command line was correct (sorry I have deleted the e-mail so can't credit the person).

The minicom output is showing this as the kernel command line:

Kernel command line: console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=116M

As you can see the $nfshost & $rootpath variables are not being expanded - you will have to hard code them. Still your problem seems to be DHCP related - the kernel should get an IP address but with the above command line it will then fail....as shown below - I put your command line into my DM355
 
NET: Registered protocol family 17
eth0: link down
Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 0.0.0.0, my address is 172.18.128.164
IP-Config: Complete:
      device=eth0, addr=172.18.128.164, mask=255.255.0.0, gw=172.18.0.254,
     host=172.18.128.164, domain=trinity.local, nis-domain=(none),
     bootserver=0.0.0.0, rootserver=0.0.0.0, rootpath=
Looking up port of RPC 100003/2 on 0.0.0.0
RPC: sendmsg returned error 22
portmap: RPC call returned error 22
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 0.0.0.0
RPC: sendmsg returned error 22
portmap: RPC call returned error 22
Root-NFS: Unable to get mountd port number from server, using default
RPC: sendmsg returned error 22
mount: RPC call returned error 22
Root-NFS: Server returned error -22 while mounting /tftpboot/$(nfshost):$(roootp
ath)
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
 <6>eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
 
Can you confirm that the ethernet interface actually works - can you download a file with tftp (having set an addres for 'ipaddr' and 'serverip' in u-boot)?
 
Can you try the 'dhcp' command in u-boot. For reference my board does this...
 
DM355 EVM # dhcp
BOOTP broadcast 1
DHCP client bound to address 172.18.128.166
TFTP from server 172.18.1.49; our IP address is 172.18.128.166
Filename 'uImage'.
Load address: 0x80700000
Loading: *
TFTP error: 'Only absolute filenames allowed' (2)
Starting again
The above tftp command fails because the DHCP server does not pass a filename (it has not been configured to do so) however it does get an address, which is to be expected. From the command output it would seem that the u-boot 'dhcp' command is using BOOTP rather than DHCP. From memory the 'standard' Linux DHCP server will not allow BOOTP requests by default - there is an option 'allow bootp' to turn this on.
 
You may need to speak to whoever manages the DHCP server on your network to confirn that BOOTP will work. If this is you then you are out of luck seeking advice ;-)
 
If you are relying on a ADSL router box (or similar) to do the DHCP server duty, you may need to consider switching to a dedicated Linux box. You can use the 'dnsmasq' package rather than the full DHCP server. This is a lot easier to set up although not as flexible as it is really there to do dynamic DNS for a local network - the DHCP functionality is secondary to this.
 
Regards
 
Phil Q
 
Phil Quiney, Senior Software Engineer
Trinity Convergence
Cambridge Business Park
Cowley Road
Cambridge CB4 0WZ, UK
T: +44(0)1223-435536
F: +44(0)1223-435560
 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of kaja gopi
Sent: 05 March 2008 06:23
To: davinci
Subject: nfs boot problem

Hi,

 

here is the minicom output while booting dm355evm board also printenv output.

any body tell me wts the problem exactly is..

it says bad block found on nand does it have to do any thing with booting..

 

 

printenv :

 

bootdelay=3

baudrate=115200

bootfile="uImage"

bootcmd=nboot 0x80700000 0 0x400000;bootm

rootpath=/home/confident/workdir/filesys

nfshost=192.168.100.1

bootargs=console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=116M

stdin=serial

stdout=serial

stderr=serial

videostd=pal

Environment size: 318/16380 bytes

 

 

 

minicom output :

 

Welcome to minicom 2.2

OPTIONS: I18n

Compiled on Nov 26 2006, 02:42:19.

Port /dev/ttyS0

Press CTRL-A Z for help on special keys

.. this is MT29F16G08FAA device

UBL: detected valid U-Boot magic number

UBL: booting to U-Boot

 

U-Boot 1.2.0 (Oct 17 2007 - 15:38:02)

DRAM: 128 MB

NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit)

Bad block table found at page 524224, version 0x01

Bad block table found at page 524160, version 0x01

nand_read_bbt: Bad block at 0x10120000

nand_read_bbt: Bad block at 0x1d4e0000

nand_read_bbt: Bad block at 0x1f120000

nand_read_bbt: Bad block at 0x3d240000

NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit)

Bad block table found at page 524160, version 0x01

Bad block table found at page 524096, version 0x01

nand_read_bbt: Bad block at 0x19ea0000

nand_read_bbt: Bad block at 0x1d020000

nand_read_bbt: Bad block at 0x27aa0000

nand_read_bbt: Bad block at 0x3ffe0000

2048 MiB

In: serial

Out: serial

Err: serial

ARM Clock :- 216MHz

DDR Clock :- 171MHz

Hit any key to stop autoboot: 0

Loading from NAND 1GiB 3,3V 8-bit, offset 0x400000

Image Name: Linux-2.6.10_mvl401

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 1585240 Bytes = 1.5 MB

Load Address: 80008000

Entry Point: 80008000

## Booting image at 80700000 ...

Image Name: Linux-2.6.10_mvl401

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 1585240 Bytes = 1.5 MB

Load Address: 80008000

Entry Point: 80008000

Verifying Checksum ... OK

OK

Starting kernel ...

Linux version 2.6.10_mvl401 ([EMAIL PROTECTED]) (gcc version 3.4.3 (MontaVista 3.4.3-25.0.104.0600975 2006-07-06)) #1 Wed Oct 17 15:44:12 7

CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ)

CPU0: D VIVT write-back cache

CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets

CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets

Machine: DaVinci DM355 EVM

Memory policy: ECC disabled, Data cache writeback

DM0350

Built 1 zonelists

Kernel command line: console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=116M

PID hash table entries: 512 (order: 9, 8192 bytes)

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: 116MB = 116MB total

Memory: 114176KB available (2762K code, 585K data, 164K init)

Mount-cache hash table entries: 512 (order: 0, 4096 bytes)

CPU: Testing write buffer coherency: ok

spawn_desched_task(00000000)

desched cpu_callback 3/00000000

ksoftirqd started up.

desched cpu_callback 2/00000000

desched thread 0 started up.

NET: Registered protocol family 16

Registering platform device 'serial8250.0'. Parent at platform

Registering platform device 'nand_davinci.0'. Parent at platform

Registering platform device 'dm9000.0'. Parent at platform

Registering platform device 'mmc.0'. Parent at platform

Registering platform device 'mmc.1'. Parent at platform

DaVinci I2C DEBUG: 15:42:09 Oct 17 2007

Registering platform device 'i2c'. Parent at platform

SCSI subsystem initialized

usbcore: registered new driver usbfs

usbcore: registered new driver hub

musb_hdrc: version 2.2a/db-0.4.8 [pio] [host] [debug=0]

Registering platform device 'musb_hdrc'. Parent at platform

musb_hdrc: USB Host mode controller at c7800000 using PIO, IRQ 12

musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:123 dm355_spi_board_init

arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:129 REG BOARD ret 0

Registering platform device 'dm_spi.0'. Parent at platform

arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:136 REGISTER DEVICE ret 0

NetWinder Floating Point Emulator V0.97 (double precision)

JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.

yaffs Oct 17 2007 15:41:45 Installing.

Initializing Cryptographic API

Registering platform device 'dm355fb.0'. Parent at platform

Console: switching to colour frame buffer device 90x30

watchdog: TI DaVinci Watchdog Timer: timer margin 64 sec

Registering platform device 'davinci_pwm0.0'. Parent at platform

Registering platform device 'davinci_pwm1.1'. Parent at platform

Registering platform device 'davinci_pwm2.2'. Parent at platform

Registering platform device 'davinci_pwm3.3'. Parent at platform

Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled

Registering platform device 'serial8250'. Parent at platform

ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A

ttyS1 at MMIO 0x1c20400 (irq = 41) is a 16550A

ttyS2 at MMIO 0x1e06000 (irq = 14) is a 16550A

io scheduler noop registered

io scheduler anticipatory registered

RAMDISK driver initialized: 1 RAM disks of 32768K size 1024 blocksize

loop: loaded (max 8 devices)

dm9000 Ethernet Driver

eth0: dm9000 at c7862000,c7864002 IRQ 45 MAC: 00:0e:99:02:c1:2f

i2c /dev entries driver

Linux video capture interface: v1.00

Registering platform device 'vpfe.1'. Parent at platform

vpfe vpfe.1: DaVinci v4l2 capture driver V1.0 loaded

ipipe major#: 253, minor# 0

Registering platform device 'dm355_ipipe.2'. Parent at platform

ipipe driver registered

af major#: 252, minor# 0

Registering platform device 'dm355_af.2'. Parent at platform

aew major#: 251, minor# 0

Registering platform device 'dm355_aew.2'. Parent at platform

elevator: using anticipatory as default io scheduler

at25xxA_spi_eeprom init

nand_davinci nand_davinci.0: Using 4-bit hardware ECC

NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit)

2 NAND chips detected

nand_bbt: ECC error while reading bad block table

nand_bbt: ECC error while reading bad block table

Creating 5 MTD partitions on "nand_davinci.0":

0x00000000-0x003c0000 : "bootloader"

0x003c0000-0x00400000 : "params"

0x00400000-0x00800000 : "kernel"

0x00800000-0x20800000 : "filesystem1"

0x20800000-0x80000000 : "filesystem2"

nand_davinci nand_davinci.0: hardware revision: 2.3

scan_boardinfo:<NULL>:-1067858964

modias <NULL> irq 2000000 max_speed 65535 bus_num 0 chip_select 0 mode -1068867824

drivers/spi/spi.cat25xxA_spi_eeprom device register Succeeded

dm_spi.0: dm355 SPI Controller driver at 0xc7866000 (irq = 42)

Initializing USB Mass Storage driver...

usbcore: registered new driver usb-storage

USB Mass Storage support registered.

usbcore: registered new driver usbhid

drivers/usb/input/hid-core.c: v2.0:USB HID core driver

mice: PS/2 mouse device common for all mice

mmc mmc.0: Supporting 4-bit mode

mmc mmc.0: Using DMA mode

mmc mmc.1: Supporting 4-bit mode

mmc mmc.1: Using DMA mode

Registering platform device 'davinci-audio.0'. Parent at platform

NET: Registered protocol family 2

IP: routing cache hash table of 512 buckets, 4Kbytes

TCP: Hash tables configured (established 8192 bind 16384)

Initializing XFRM netlink socket

NET: Registered protocol family 1

NET: Registered protocol family 10

IPv6 over IPv4 tunneling driver

NET: Registered protocol family 17

eth0: link down

Sending DHCP requests .<6>eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

..<7>eth0: no IPv6 routers present

... timed out!

IP-Config: Retrying forever (NFS root)...

eth0: link down

Sending DHCP requests .<6>eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

..<7>eth0: no IPv6 routers present

... timed out!

IP-Config: Retrying forever (NFS root)...

eth0: link down

Sending DHCP requests .<6>eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

..<7>eth0: no IPv6 routers present

... timed out!

IP-Config: Retrying forever (NFS root)...

eth0: link down

Sending DHCP requests .<6>eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

..<7>eth0: no IPv6 routers present

... timed out!

IP-Config: Retrying forever (NFS root)...

eth0: link down

Sending DHCP requests .<6>eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

..<7>eth0: no IPv6 routers present

... timed out!

 

 

thanks

regds

gopi k


Save all your chat conversations. Find them online.

Forgot the famous last words? Access your message archive online. Click here. 
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to