[#6621] kernel xip fail to mount nfs filesystem on bf548-ezkit/bf561-ezkit
Submitted By: Vivi Li
Open Date
2011-06-01 06:14:57 Close Date
2011-08-29 04:06:13
Priority:
Medium Assignee:
Vivi Li
steven miao
Status:
Closed Fixed In Release:
N/A
Found In Release:
2011R1 Release:
Category:
N/A Board:
N/A
Processor:
BF548 Silicon Revision:
Is this bug repeatable?:
Yes Resolution:
Not reproducible
Uboot version or rev.:
Toolchain version or rev.:
gcc4.3-2010_Dec_09
App binary format:
N/A
Summary: kernel xip fail to mount nfs filesystem on bf548-ezkit/bf561-ezkit
Details:
Kernel xip fail to mount nfs filesystem on bf548-ezkit/bf561-ezkit, with both fdpic and shared-flat formats.
This happened when update kernel from 2.6.37.4 to 2.6.38 on Mar.
Bellow is the log on bf548-ezkit:
--
U-Boot 2010.06-svn2467 (ADI-2010R1) (Oct 08 2010 - 16:04:41)
CPU: ADSP bf548-0.0 (Detected Rev: 0.2) (parallel flash boot)
Board: ADI BF548 EZ-Kit board
Support: http://blackfin.uclinux.org/
Clock: VCO: 525 MHz, Core: 525 MHz, System: 131.250 MHz
RAM: 64 MiB
Flash: 16 MiB
NAND: 256 MiB
MMC: Blackfin SDH: 0
In: serial
Out: serial
Err: serial
KGDB: [on serial] ready
Net: smc911x-0
Hit any key to stop autoboot: 5 ^H^H^H 0
bfin> tftpboot 0x1000000 vmImage
smc911x: detected LAN9218 controller
smc911x: phy initialized
smc911x: MAC 00:e0:22:fe:bf:4e
Using smc911x-0 device
TFTP from server 10.100.4.174; our IP address is 10.100.4.50
Filename 'vmImage'.
Load address: 0x1000000
Loading: *^H#################################################################
#################################################################
##########################################################
done
Bytes transferred = 2748672 (29f100 hex)
bfin> protect off 20080000 20ffffff
............................................................................................................................... done
Un-Protected 127 sectors
bfin> erase 20080000 20ffffff
............................................................................................................................... done
Erased 127 sectors
bfin> cp.b 0x1000000 20080000 0x29f100
Copy to Flash... done
bfin> set bootargs root=/dev/nfs rw nfsroot=$(serverip):/tftpboot/romfs console=ttyBF1,57600
bfin> run addip
bfin> bootm 20080000
## Booting kernel from Legacy Image at 20080000 ...
Image Name: bf548-0.2-2.6.39-ADI-2011R1-pre-
Created: 2011-05-31 9:13:59 UTC
Image Type: Blackfin Linux Kernel Image (uncompressed)
Data Size: 2748608 Bytes = 2.6 MiB
Load Address: 20080040
Entry Point: 2024c29c
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting Kernel at = 2024c29c
console [ttyBF1] enabled, bootconsole disabled
Calibrating delay loop... 1032.19 BogoMIPS (lpj=2064384)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
Blackfin Scratchpad data SRAM: 4 KB
Blackfin L1 Data A SRAM: 16 KB (16 KB free)
Blackfin L1 Data B SRAM: 16 KB (16 KB free)
Blackfin L1 Instruction SRAM: 48 KB (41 KB free)
Blackfin L2 SRAM: 128 KB (128 KB free)
NET: Registered protocol family 16
Blackfin DMA Controller
ezkit_init(): registering device resources
bio: create slab <bio-0> at 0
SCSI subsystem initialized
i2c-bfin-twi i2c-bfin-twi.0: Blackfin BF5xx on-chip I2C TWI Contoller, regs_base@ffc00700
i2c-bfin-twi i2c-bfin-twi.1: Blackfin BF5xx on-chip I2C TWI Contoller, regs_base@ffc02200
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
debug-mmrs: setting up Blackfin MMR debugfs
msgmni has been set to 122
io scheduler noop registered (default)
bfin-uart: Blackfin serial driver
bfin-uart.1: ttyBF1 at MMIO 0xffc02000 (irq = 48) is a BFIN-UART
bfin-otp: initialized
brd: module loaded
register bfin atapi driver
scsi0 : pata-bf54x
ata1: PATA max UDMA/66 irq 68
BF5xx on-chip NAND FLash Controller Driver, Version 1.2 (c) 2007 Analog Devices, Inc.
bf5xx-nand bf5xx-nand.0: data_width=8, wr_dly=3, rd_dly=3
NAND device: Manufacturer ID: 0x20, Chip ID: 0xda (ST Micro NAND 256MiB 3,3V 8-bit)
Creating 3 MTD partitions on "NAND 256MiB 3,3V 8-bit":
0x000000000000-0x000000080000 : "bootloader(nand)"
0x000000080000-0x000000480000 : "linux kernel(nand)"
0x000000480000-0x000010000000 : "file system(nand)"
smsc911x: Driver version 2008-10-21.
smsc911x smsc911x.0: eth0: Features changed: 0x00004800 -> 0x00004000
smsc911x-mdio: probed
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1)
net eth0: MAC Address: 00:e0:22:fe:bf:4e
i2c /dev entries driver
dma_alloc_init: dma_page @ 0x021fe000 - 512 pages at 0x03e00000
TCP cubic registered
NET: Registered protocol family 17
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new SD card at address e624
ata1.00: ATA-6: TOSHIBA MK4032GAX, AD101A, max UDMA/100
ata1.00: 78140160 sectors, multi 16: LBA48
ata1.00: configured for UDMA/66
blk_queue_max_segments: set to minimum 1
scsi 0:0:0:0: Direct-Access ATA TOSHIBA MK4032GA AD10 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 78140160 512-byte logical blocks: (40.0 GB/37.2 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: detected capacity change from 0 to 40007761920
sda: sda1 sda2
sd 0:0:0:0: [sda] Attached SCSI disk
net eth0: SMSC911x/921x identified at 0x24000000, IRQ: 175
IP-Config: Complete:
device=eth0, addr=10.100.4.50, mask=255.255.255.0, gw=10.100.4.174,
host=bf548-ezkit, domain=, nis-domain=(none),
bootserver=10.100.4.174, rootserver=10.100.4.174, rootpath=
VFS: Mounted root (nfs filesystem) on device 0:12.
nfs: server 10.100.4.174 not responding, still trying
nfs: server 10.100.4.174 OK
nfs: server 10.100.4.174 not responding, still trying
nfs: server 10.100.4.174 OK
--
Follow-ups
--- Mike Frysinger 2011-06-01 06:33:29
it seems you're using udp to mount things. udp even on a desktop system
performs horribly. please change all your tests to use tcp instead.
--- Sonic Zhang 2011-07-01 04:08:37
Vivi needs to update the uboot parameter to enable TCP mode in NFS.
--- Vivi Li 2011-07-15 01:34:12
Kernel_xip test script is updated by using TCP to mount NFS server.
--- Vivi Li 2011-08-29 04:06:13
OK now. Close it.
Files
Changes
Commits
Dependencies
Duplicates
Associations
Tags
File Name File Type File Size Posted By
config.config.kernel_xip.shared-flat application/octet-stream 48215 Vivi Li
config.linux.kernel_xip.shared-flat application/octet-stream 35473 Vivi Li