M5485EVB based custom board, Linux BSP w/ kernel 2.6.10, hangs when syslogd and klogd try to start

[jkimble]

I'm working with a custom board w/ the mcf5484 coldfire (Vs the mcf5485 on the eval board). The things starts to boot and manages to get through the nfs mount process (I see it succesfully mount in my servers log file) but then it goest to start the syslog stuff and starts giving the messages:

nfs: server 137.237.242.42 not responding, still trying
NETDEV WATCHDOG: eth0: transmit timed out

The nfs not responding only repeats twice but the NETDEV message just goes on forever. I don't get it. I was thinking maybe this is a permissions issue on the server side but my evaluation board works fine and it's permissions are identical. Any help/suggestion would be much appreciated...

James Kimble

[kwong]

If you're using LTIB, I would take a look at the network configuration within LTIB.  By default, it'll reset the IP settings of the board which has always caused me to lose my nfs connection.

Ken.

[jkimble]

Yeah, that caught me too. Gave a different message though (kernel panic). This is just weird. I can actually bring my evaluation board up on exactly the same nfs filesystem mount and it runs fine. That tells me it's not an nfs or file permissions issue.

One thing I'm unsure of is the need for flash memory for Linux to run. The flash on my board is configured differently than that on the evaluation board. I made it work with the boot loader (Colilo) but I just turned off MTD support in the kernel so it wouldn't try to use it. I don't know if Linux can work correctly without it. The boot up doesn't have any hickups until it tries to work with syslogd and klogd. When I turn that off it gets to the point it tries to add a static rout to the gateway and hangs up there with the same messages.

Very weird...

[kwong]

You don't need flash in order to start up Linux.  Especially if you shut off the MTD kernel config options.

I don't think it's your server, if it was, you would've gotten a kernel panic on the getgo.  The fact that you got as far as starting up syslogd means that the nfs connection was successful.

How about you post:
- the last 20 lines of startup messages on your custom board
- the IP configuration for your board (what you think it should be)
- and the defconfig.dev file for your platform?

We should be able to figure out what the problem is from that information.

[jkimble]

My ip configuration is (or should be) what the boot loader displays below when the kernel is uploaded to SDRAM. Note that this configuration is identical to that of my evaluation board that works.

IP: 137.237.242.200

MAC: 00:CF:54:85:CF:01

Netmask: 255.255.255.0

Gateway: 137.237.242.13

TFTP Server: 137.237.242.42

If you can solve this for me I'll owe you one heck of a big THANK YOU! It's had me stuck for days.

My boot sequence follows the defconfig file.

My platform is in /arch/m68k and the defconfig file from that directory is below.

Code:

## Automatically generated make config: don't edit# Linux kernel version: 2.6.10-m68k# Sun Dec 26 11:23:36 2004#CONFIG_M68K=yCONFIG_MMU=yCONFIG_UID16=yCONFIG_RWSEM_GENERIC_SPINLOCK=y## Code maturity level options#CONFIG_EXPERIMENTAL=yCONFIG_CLEAN_COMPILE=yCONFIG_BROKEN_ON_SMP=y## General setup#CONFIG_LOCALVERSION=""CONFIG_SWAP=yCONFIG_SYSVIPC=y# CONFIG_POSIX_MQUEUE is not set# CONFIG_BSD_PROCESS_ACCT is not setCONFIG_SYSCTL=y# CONFIG_AUDIT is not setCONFIG_LOG_BUF_SHIFT=14# CONFIG_HOTPLUG is not setCONFIG_KOBJECT_UEVENT=y# CONFIG_IKCONFIG is not set# CONFIG_EMBEDDED is not setCONFIG_KALLSYMS=y# CONFIG_KALLSYMS_EXTRA_PASS is not setCONFIG_FUTEX=yCONFIG_EPOLL=y# CONFIG_CC_OPTIMIZE_FOR_SIZE is not setCONFIG_SHMEM=yCONFIG_CC_ALIGN_FUNCTIONS=0CONFIG_CC_ALIGN_LABELS=0CONFIG_CC_ALIGN_LOOPS=0CONFIG_CC_ALIGN_JUMPS=0# CONFIG_TINY_SHMEM is not set## Loadable module support## CONFIG_MODULES is not set## Platform dependent setup## CONFIG_SUN3 is not setCONFIG_AMIGA=y# CONFIG_ATARI is not set# CONFIG_MAC is not set# CONFIG_APOLLO is not set# CONFIG_VME is not set# CONFIG_HP300 is not set# CONFIG_SUN3X is not set# CONFIG_Q40 is not set## Processor type#CONFIG_M68020=yCONFIG_M68030=yCONFIG_M68040=y# CONFIG_M68060 is not setCONFIG_MMU_MOTOROLA=y# CONFIG_M68KFPU_EMU is not set# CONFIG_ADVANCED is not set## General setup#CONFIG_BINFMT_ELF=yCONFIG_BINFMT_AOUT=y# CONFIG_BINFMT_MISC is not setCONFIG_ZORRO=y# CONFIG_AMIGA_PCMCIA is not set# CONFIG_HEARTBEAT is not setCONFIG_PROC_HARDWARE=y# CONFIG_ZORRO_NAMES is not set## Device Drivers### Generic Driver Options#CONFIG_STANDALONE=yCONFIG_PREVENT_FIRMWARE_BUILD=y## Memory Technology Devices (MTD)## CONFIG_MTD is not set## Parallel port support## CONFIG_PARPORT is not set## Plug and Play support### Block devices#CONFIG_AMIGA_FLOPPY=y# CONFIG_AMIGA_Z2RAM is not set# CONFIG_BLK_DEV_LOOP is not set# CONFIG_BLK_DEV_NBD is not setCONFIG_BLK_DEV_RAM=yCONFIG_BLK_DEV_RAM_COUNT=16CONFIG_BLK_DEV_RAM_SIZE=4096CONFIG_BLK_DEV_INITRD=yCONFIG_INITRAMFS_SOURCE=""CONFIG_CDROM_PKTCDVD=yCONFIG_CDROM_PKTCDVD_BUFFERS=8# CONFIG_CDROM_PKTCDVD_WCACHE is not set## IO Schedulers#CONFIG_IOSCHED_NOOP=yCONFIG_IOSCHED_AS=yCONFIG_IOSCHED_DEADLINE=yCONFIG_IOSCHED_CFQ=y## ATA/ATAPI/MFM/RLL support## CONFIG_IDE is not set## SCSI device support#CONFIG_SCSI=yCONFIG_SCSI_PROC_FS=y## SCSI support type (disk, tape, CD-ROM)#CONFIG_BLK_DEV_SD=yCONFIG_CHR_DEV_ST=y# CONFIG_CHR_DEV_OSST is not setCONFIG_BLK_DEV_SR=y# CONFIG_BLK_DEV_SR_VENDOR is not set# CONFIG_CHR_DEV_SG is not set## Some SCSI devices (e.g. CD jukebox) support multiple LUNs## CONFIG_SCSI_MULTI_LUN is not setCONFIG_SCSI_CONSTANTS=y# CONFIG_SCSI_LOGGING is not set## SCSI Transport Attributes## CONFIG_SCSI_SPI_ATTRS is not set# CONFIG_SCSI_FC_ATTRS is not set## SCSI low-level drivers## CONFIG_SCSI_SATA is not set# CONFIG_SCSI_DEBUG is not setCONFIG_A3000_SCSI=yCONFIG_A2091_SCSI=yCONFIG_GVP11_SCSI=y# CONFIG_CYBERSTORM_SCSI is not set# CONFIG_CYBERSTORMII_SCSI is not set# CONFIG_BLZ2060_SCSI is not set# CONFIG_BLZ1230_SCSI is not set# CONFIG_FASTLANE_SCSI is not setCONFIG_SCSI_AMIGA7XX=y# CONFIG_OKTAGON_SCSI is not setCONFIG_SCSI_NCR53C7xx_FAST=y## Multi-device support (RAID and LVM)## CONFIG_MD is not set## Fusion MPT device support### IEEE 1394 (FireWire) support### I2O device support### Networking support#CONFIG_NET=y## Networking options#CONFIG_PACKET=y# CONFIG_PACKET_MMAP is not set# CONFIG_NETLINK_DEV is not setCONFIG_UNIX=y# CONFIG_NET_KEY is not setCONFIG_INET=y# CONFIG_IP_MULTICAST is not set# CONFIG_IP_ADVANCED_ROUTER is not set# CONFIG_IP_PNP is not set# CONFIG_NET_IPIP is not set# CONFIG_NET_IPGRE is not set# CONFIG_ARPD is not set# CONFIG_SYN_COOKIES is not set# CONFIG_INET_AH is not set# CONFIG_INET_ESP is not set# CONFIG_INET_IPCOMP is not set# CONFIG_INET_TUNNEL is not setCONFIG_IP_TCPDIAG=y# CONFIG_IP_TCPDIAG_IPV6 is not set# CONFIG_IPV6 is not set# CONFIG_NETFILTER is not set## SCTP Configuration (EXPERIMENTAL)## CONFIG_IP_SCTP is not set# CONFIG_ATM is not set# CONFIG_BRIDGE is not set# CONFIG_VLAN_8021Q is not set# CONFIG_DECNET is not set# CONFIG_LLC2 is not set# CONFIG_IPX is not set# CONFIG_ATALK is not set# CONFIG_X25 is not set# CONFIG_LAPB is not set# CONFIG_NET_DIVERT is not set# CONFIG_ECONET is not set# CONFIG_WAN_ROUTER is not set## QoS and/or fair queueing## CONFIG_NET_SCHED is not set# CONFIG_NET_CLS_ROUTE is not set## Network testing## CONFIG_NET_PKTGEN is not set# CONFIG_NETPOLL is not set# CONFIG_NET_POLL_CONTROLLER is not set# CONFIG_HAMRADIO is not set# CONFIG_IRDA is not set# CONFIG_BT is not setCONFIG_NETDEVICES=y# CONFIG_DUMMY is not set# CONFIG_BONDING is not set# CONFIG_EQUALIZER is not set# CONFIG_TUN is not set## Ethernet (10 or 100Mbit)## CONFIG_NET_ETHERNET is not set## Ethernet (1000 Mbit)### Ethernet (10000 Mbit)### Token Ring devices### Wireless LAN (non-hamradio)## CONFIG_NET_RADIO is not set## Wan interfaces## CONFIG_WAN is not set# CONFIG_PPP is not set# CONFIG_SLIP is not set# CONFIG_SHAPER is not set# CONFIG_NETCONSOLE is not set## ISDN subsystem## CONFIG_ISDN is not set## Telephony Support## CONFIG_PHONE is not set## Input device support#CONFIG_INPUT=y## Userland interfaces#CONFIG_INPUT_MOUSEDEV=yCONFIG_INPUT_MOUSEDEV_PSAUX=yCONFIG_INPUT_MOUSEDEV_SCREEN_X=1024CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768# CONFIG_INPUT_JOYDEV is not set# CONFIG_INPUT_TSDEV is not set# CONFIG_INPUT_EVDEV is not set# CONFIG_INPUT_EVBUG is not set## Input I/O drivers## CONFIG_GAMEPORT is not setCONFIG_SOUND_GAMEPORT=yCONFIG_SERIO=yCONFIG_SERIO_SERPORT=y# CONFIG_SERIO_CT82C710 is not set# CONFIG_SERIO_RAW is not set## Input Device Drivers#CONFIG_INPUT_KEYBOARD=yCONFIG_KEYBOARD_ATKBD=y# CONFIG_KEYBOARD_SUNKBD is not set# CONFIG_KEYBOARD_LKKBD is not set# CONFIG_KEYBOARD_XTKBD is not set# CONFIG_KEYBOARD_NEWTON is not set# CONFIG_KEYBOARD_AMIGA is not setCONFIG_INPUT_MOUSE=yCONFIG_MOUSE_PS2=y# CONFIG_MOUSE_SERIAL is not set# CONFIG_MOUSE_AMIGA is not set# CONFIG_MOUSE_VSXXXAA is not set# CONFIG_INPUT_JOYSTICK is not set# CONFIG_INPUT_TOUCHSCREEN is not set# CONFIG_INPUT_MISC is not set## Character devices#CONFIG_VT=yCONFIG_VT_CONSOLE=yCONFIG_HW_CONSOLE=y# CONFIG_SERIAL_NONSTANDARD is not set# CONFIG_A2232 is not set## Serial drivers## CONFIG_SERIAL_8250 is not set## Non-8250 serial port support#CONFIG_UNIX98_PTYS=yCONFIG_LEGACY_PTYS=yCONFIG_LEGACY_PTY_COUNT=256## IPMI## CONFIG_IPMI_HANDLER is not set## Watchdog Cards## CONFIG_WATCHDOG is not set# CONFIG_GEN_RTC is not set# CONFIG_DTLK is not set# CONFIG_R3964 is not set## Ftape, the floppy tape device driver## CONFIG_DRM is not set# CONFIG_RAW_DRIVER is not set## I2C support## CONFIG_I2C is not set## Dallas's 1-wire bus## CONFIG_W1 is not set## Misc devices### Multimedia devices## CONFIG_VIDEO_DEV is not set## Digital Video Broadcasting Devices## CONFIG_DVB is not set## Graphics support#CONFIG_FB=yCONFIG_FB_MODE_HELPERS=y# CONFIG_FB_TILEBLITTING is not set# CONFIG_FB_CIRRUS is not setCONFIG_FB_AMIGA=yCONFIG_FB_AMIGA_OCS=yCONFIG_FB_AMIGA_ECS=yCONFIG_FB_AMIGA_AGA=y# CONFIG_FB_FM2 is not set# CONFIG_FB_VIRTUAL is not set## Console display driver support#CONFIG_DUMMY_CONSOLE=y# CONFIG_FRAMEBUFFER_CONSOLE is not set## Logo configuration## CONFIG_LOGO is not set## Sound## CONFIG_SOUND is not set## USB support## CONFIG_USB_ARCH_HAS_HCD is not set# CONFIG_USB_ARCH_HAS_OHCI is not set## NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' may also be needed; see USB_STORAGE Help for more information### USB Gadget Support## CONFIG_USB_GADGET is not set## MMC/SD Card support## CONFIG_MMC is not set## Character devices#CONFIG_AMIGA_BUILTIN_SERIAL=y# CONFIG_MULTIFACE_III_TTY is not set# CONFIG_GVPIOEXT is not set# CONFIG_SERIAL_CONSOLE is not set## File systems#CONFIG_EXT2_FS=y# CONFIG_EXT2_FS_XATTR is not set# CONFIG_EXT3_FS is not set# CONFIG_JBD is not set# CONFIG_REISERFS_FS is not set# CONFIG_JFS_FS is not set# CONFIG_XFS_FS is not setCONFIG_MINIX_FS=y# CONFIG_ROMFS_FS is not set# CONFIG_QUOTA is not setCONFIG_DNOTIFY=y# CONFIG_AUTOFS_FS is not set# CONFIG_AUTOFS4_FS is not set## CD-ROM/DVD Filesystems## CONFIG_ISO9660_FS is not set# CONFIG_UDF_FS is not set## DOS/FAT/NT Filesystems#CONFIG_FAT_FS=yCONFIG_MSDOS_FS=y# CONFIG_VFAT_FS is not setCONFIG_FAT_DEFAULT_CODEPAGE=437# CONFIG_NTFS_FS is not set## Pseudo filesystems#CONFIG_PROC_FS=yCONFIG_PROC_KCORE=yCONFIG_SYSFS=y# CONFIG_DEVFS_FS is not set# CONFIG_DEVPTS_FS_XATTR is not set# CONFIG_TMPFS is not set# CONFIG_HUGETLB_PAGE is not setCONFIG_RAMFS=y## Miscellaneous filesystems## CONFIG_ADFS_FS is not set# CONFIG_AFFS_FS is not set# CONFIG_HFS_FS is not set# CONFIG_HFSPLUS_FS is not set# CONFIG_BEFS_FS is not set# CONFIG_BFS_FS is not set# CONFIG_EFS_FS is not set# CONFIG_CRAMFS is not set# CONFIG_VXFS_FS is not set# CONFIG_HPFS_FS is not set# CONFIG_QNX4FS_FS is not set# CONFIG_SYSV_FS is not set# CONFIG_UFS_FS is not set## Network File Systems#CONFIG_NFS_FS=y# CONFIG_NFS_V3 is not set# CONFIG_NFS_V4 is not set# CONFIG_NFS_DIRECTIO is not set# CONFIG_NFSD is not setCONFIG_LOCKD=y# CONFIG_EXPORTFS is not setCONFIG_SUNRPC=y# CONFIG_RPCSEC_GSS_KRB5 is not set# CONFIG_RPCSEC_GSS_SPKM3 is not set# CONFIG_SMB_FS is not set# CONFIG_CIFS is not set# CONFIG_NCP_FS is not set# CONFIG_CODA_FS is not set# CONFIG_AFS_FS is not set## Partition Types## CONFIG_PARTITION_ADVANCED is not setCONFIG_AMIGA_PARTITION=yCONFIG_MSDOS_PARTITION=y## Native Language Support#CONFIG_NLS=yCONFIG_NLS_DEFAULT="iso8859-1"CONFIG_NLS_CODEPAGE_437=y# CONFIG_NLS_CODEPAGE_737 is not set# CONFIG_NLS_CODEPAGE_775 is not set# CONFIG_NLS_CODEPAGE_850 is not set# CONFIG_NLS_CODEPAGE_852 is not set# CONFIG_NLS_CODEPAGE_855 is not set# CONFIG_NLS_CODEPAGE_857 is not set# CONFIG_NLS_CODEPAGE_860 is not set# CONFIG_NLS_CODEPAGE_861 is not set# CONFIG_NLS_CODEPAGE_862 is not set# CONFIG_NLS_CODEPAGE_863 is not set# CONFIG_NLS_CODEPAGE_864 is not set# CONFIG_NLS_CODEPAGE_865 is not set# CONFIG_NLS_CODEPAGE_866 is not set# CONFIG_NLS_CODEPAGE_869 is not set# CONFIG_NLS_CODEPAGE_936 is not set# CONFIG_NLS_CODEPAGE_950 is not set# CONFIG_NLS_CODEPAGE_932 is not set# CONFIG_NLS_CODEPAGE_949 is not set# CONFIG_NLS_CODEPAGE_874 is not set# CONFIG_NLS_ISO8859_8 is not set# CONFIG_NLS_CODEPAGE_1250 is not set# CONFIG_NLS_CODEPAGE_1251 is not set# CONFIG_NLS_ASCII is not set# CONFIG_NLS_ISO8859_1 is not set# CONFIG_NLS_ISO8859_2 is not set# CONFIG_NLS_ISO8859_3 is not set# CONFIG_NLS_ISO8859_4 is not set# CONFIG_NLS_ISO8859_5 is not set# CONFIG_NLS_ISO8859_6 is not set# CONFIG_NLS_ISO8859_7 is not set# CONFIG_NLS_ISO8859_9 is not set# CONFIG_NLS_ISO8859_13 is not set# CONFIG_NLS_ISO8859_14 is not set# CONFIG_NLS_ISO8859_15 is not set# CONFIG_NLS_KOI8_R is not set# CONFIG_NLS_KOI8_U is not set# CONFIG_NLS_UTF8 is not set## Kernel hacking## CONFIG_DEBUG_KERNEL is not set## Security options## CONFIG_KEYS is not set# CONFIG_SECURITY is not set## Cryptographic options## CONFIG_CRYPTO is not set## Library routines## CONFIG_CRC_CCITT is not setCONFIG_CRC32=y# CONFIG_LIBCRC32C is not set## CodeTEST setup#CONFIG_CODETEST=y

 Boot sequence from kernel download to network connection failure:

Code:

********************************************************************************Colilo >tftp 0x1000TFTP download:Download address:1000Using FEC:0Board MAC: '00:CF:54:85:CF:01'Board IP: '137.237.242.200'Board netmask:'255.255.255.0'Board gateway:'137.237.242.13'TFTP server:'137.237.242.42'Image:'vmlinux.bin'Initializing TCP/IP stack...Receiving file 'vmlinux.bin' from '137.237.242.42'/Image size = 2437120 bytes=================================================================Colilo >set cl mac0=00:CF:54:85:CF:01 noinitrd root=/dev/nfs rw nfsroot=137.237.242.42:/tftpboot/ltib ip=137.237.242.200:137.237.242.42:137.237.242.13:255.255.255.0:ColdFire:eth0:off mtdparts=phys_mapped_flash:256k(Colilo),2816k(User)Command line:'mac0=00:CF:54:85:CF:01 noinitrd root=/dev/nfs rw nfsroot=137.237.242.42:/tftpboot/ltib ip=137.237.242.200:137.237.242.42:137.237.242.13:255.255.255.0:ColdFire:eth0:off mtdparts=phys_mapped_flash:256k(Colilo),2816k(User)'Colilo >g 0x2000Linux version 2.6.10 (jkimble@sc020702-udp067736uds.cs.myharris.net) (gcc version 3.4.0) #2 Thu Nov 8 16:45:34 EST 2007starting up linux rev 0.2: startmem 0xc0256000, size 61MBBuilt 1 zonelistsKernel command line: mac0=00:CF:54:85:CF:01 noinitrd root=/dev/nfs rw nfsroot=137.237.242.42:/tftpboot/ltib ip=137.237.242.200:137.237.242.42:137.237.242.13:255.255.255.0:ColdFire:eth0:off mtdparts=phys_mapped_flash:256k(Colilo),2816k(User)PID hash table entries: 512 (order: 9, 8192 bytes)RTC driver is not initialized yet, returning 1970.Console: colour dummy device 80x25Dentry cache hash table entries: 16384 (order: 3, 65536 bytes)Inode-cache hash table entries: 8192 (order: 2, 32768 bytes)Memory: 62632k/65536k available (1904k kernel code, 816k data, 88k init)Mount-cache hash table entries: 1024 (order: 0, 8192 bytes)NET: Registered protocol family 16SCSI subsystem initializedNET: Registered protocol family 23Initialize Multi-channel DMA API Alpha v0.3 (2004-04-26)Initializing Cryptographic APIrtc: RV5C387 RTC driver successfully loadedColdFire watchdog driver is loaded.MCF547x/8x DSPI device driver installedColdfire DSPI driver is loadedColdFire internal UART serial driver version 1.00ttyS0 at 0xe0008600 (irq = 99) is a builtin ColdFire UARTttyS1 at 0xe0008700 (irq = 98) is a builtin ColdFire UARTttyS2 at 0xe0008800 (irq = 97) is a builtin ColdFire UARTttyS3 at 0xe0008900 (irq = 96) is a builtin ColdFire UARTio scheduler noop registeredio scheduler anticipatory registeredio scheduler deadline registeredio scheduler cfq registeredRAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksizeloop: loaded (max 8 devices)ColdFire internal FEC driver version 0.11mice: PS/2 mouse device common for all micei2c /dev entries driveri2c-algo-mcf.o: I2C ColdFire algorithm module is loaded.NET: Registered protocol family 2IP: routing cache hash table of 1024 buckets, 8KbytesTCP: Hash tables configured (established 8192 bind 16384)Initializing IPsec netlink socketNET: Registered protocol family 1NET: Registered protocol family 17NET: Registered protocol family 15IrCOMM protocol (Dag Brattli)IP-Config: Complete:      device=eth0, addr=137.237.242.200, mask=255.255.255.0,gw=137.237.242.13,     host=ColdFire, domain=, nis-domain=(none),     bootserver=137.237.242.42, rootserver=137.237.242.42, rootpath=Looking up port of RPC 100003/2 on 137.237.242.42Looking up port of RPC 100005/1 on 137.237.242.42VFS: Mounted root (nfs filesystem).Setting the hostname to freescaleMounting filesystemsmount: Mounting usbfs on /proc/bus/usb failed: No such file or directoryStarting syslogd and klogdnfs: server 137.237.242.42 not responding, still tryingNETDEV WATCHDOG: eth0: transmit timed outnfs: server 137.237.242.42 not responding, still tryingNETDEV WATCHDOG: eth0: transmit timed outNETDEV WATCHDOG: eth0: transmit timed outNETDEV WATCHDOG: eth0: transmit timed out********************************************************************************

[kwong]

hmm... looks like its more than just a configuration issue. 

We had a problem with similar symptoms a while ago.  It turned out that we were subject to Item #12 in the MCF5475 Device Errata.  The problem manifested itself with the

NETDEV WATCHDOG: eth0: transmit timed out
NETDEV WATCHDOG: eth0: transmit timed out

messages you've been seeing.

To fix the problem, we modified the fec driver in the linux kernel so that the FECTFCR[TXW_MASK] bit was turned on during FEC initialization.  Here's the patch:

diff --exclude CVS -uNr linux-2.6.10/drivers/net/fec/fec.h linux-2.6.10.modified/drivers/net/fec/fec.h
--- linux-2.6.10/drivers/net/fec/fec.h  2007-04-08 13:59:54.000000000 -0400
+++ linux-2.6.10.modified/drivers/net/fec/fec.h 2007-04-08 12:48:39.000000000 -0400
@@ -81,13 +81,14 @@
 #define   FEC_RCR_DRT                       (0x00000002)
 #define   FEC_EIMR_MASK                     (FEC_EIR_RL | FEC_EIR_HBERR)
 #define   FEC_ECR_ETHEREN                   (0x00000002)
-#define   FEC_FECTFCR_MSK                   (0x00F80000)
+#define   FEC_FECTFCR_MSK                   (0x00FC0000)
 #define   FEC_FECRFCR_MSK                   (0x00F80000)
 #define   FEC_EIR_GRA                       (0x10000000)
 #define   FEC_TCR_GTS                       (0x00000001)
 #define   FEC_MIBC_ENABLE                   (0x00000000)
 #define   FEC_MIB_LEN                       (228)
-#define   FEC_PHY_ADDR                      (0x01)
+#define   FEC_PHY_ADDR0                     (0x01)
+#define   FEC_PHY_ADDR1                     (0x03)

 #define FEC_RX_DMA_PRI                      (6)
 #define FEC_TX_DMA_PRI                      (6)

The lines of interest are the FEC_FECTFCR_MSK lines...

Hope this helps,

Ken.

[jkimble]

Wow! That worked, sort of....

Firstly the rc.conf file was wrong so the thing failed to boot when I first attempted to run the reconfigured kernel. I saw messages telling me where to look so it was simple to see the problem and I copied the file from the file system I use for the evaluation board. After that the system booted to a shell prompt (Woo Hoo!). I was able to run some simple commands and it appeared to be doing ok. Then I rebooted the system, loaded the kernel and started again and it stopped for a very long time trying when it reached the boa web server. Then I saw the message:

"nfs: server 137.237.242.42 not responding, still trying"

eventually it does get to a shell prompt but it acts unstable. I think I have a network issue of some kind. It's like the NFS connection is not reliable and the kernel is getting hung up waiting for the file system to respond to it. The thing is the evaluation board works fine on the same connection....  I've used two different versions of my hardware so I don't tihnk it's a hardware thing (still could be though....).

Anyway, this was great progress and I REALLY appreciate your help! I'd have never found that errata information. Thanks tons!!

James Kimble

[kwong]

Out of curiousity, what was it in the rc.conf file that caused the problem?

As for NFS being a little flakey, I noticed that running NFS over UDP didn't always work out so well in the network environment here.  So, I always mount using the following options:

nolock,hard,tcp

The key one being "tcp"... that seemed to solve all of our flakey NFS issues.

Glad the work is moving forward!

Ken.

[jkimble]

You're a wealth of info Ken! I'll give the tcp thing a try. Where are you setting that? The exports file doesn't like those options. Are you putting those on the BSP's root filesystem in /etc/fstab (please show me and example, mine looks odd...).

The rc.conf was set to default IP values. Very weird because I just created this build tree from scratch two days ago. I recreated it to elimate my fear of permissions issues. I configured it with the menu system just as I did for the evaluation boards build tree. The file looked like this:

Code:

export HOSTNAME=freescaleexport INTERFACE=eth0export IPADDR=export NETMASK=255.255.255.0export BROADCAST=192.168.0.255export GATEWAY=192.168.0.1export NAMESERVER=192.168.0.1export NTP_SERVER=ntp.cs.strath.ac.ukexport MODLIST=""export RAMDIRS=""export TMPFS="ramfs"export READONLY_FS="n"export SYSLOG_SOCKET_FILE=""export SYSCFG_DHCPC_CMD="udhcpc -b -i"all_services="hostname filesystems syslog depmod modules network settime inetd portmap dropbear boa dhcpd"all_services_r="dhcpd boa dropbear portmap inetd settime network modules depmod syslog filesystems hostname"cfg_services="hostname filesystems syslog depmod modules network settime inetd portmap dropbear boa dhcpd"cfg_services_r="dhcpd boa dropbear portmap inetd settime network modules depmod syslog filesystems hostname"

 
Thanks again!

James Kimble

[kwong]

If you've got the kernel source handy, take a look at: Documentation/nfsroot.txt

If you don't try:

http://lxr.linux.no/source/Documentation/nfsroot.txt

To specify the tcp option, I think it's just a matter of changing your kernel commandline to have:

nfsroot=<ipadress>:<mountpoint>,tcp

Ken.

[jkimble]

Now I've got another very wierd problem. My kernel boots up and the board is responsive to most commands with a few odd exceptions. I can't login via ssh. The board doesn't respond. It responds to telnet but when I try to run passwd to change the root password (which I don't know) the program prompts me for new password but when I give it the new password the second time the program never returns to a shell prompt. It just sits and gives me "nfs not responding" errors. The web server doesn't respond either. I ran top and just let it run over night and most of today and when I got back to it (like 16 hours later) it was still responding and running fine. This has got to be a network thing but I don't get what could cause such odd behaviour.

Obviously something else is wrong with the network connection. I tried adding tcp to the command line options for the nfs mount but the kernel will not boot. I see the NFS mount worked but it never  gets to a shell prompt. I'm going to look at the network traffic with ethereal but I don't get it . Could this be another FEC configuration thing? I noticed that the fec.h diff you sent me showed:

    #define   FEC_PHY_ADDR0
    #define   FEC_PHY_ADDR1

whereas mine just has

    #define   FEC_PHY_ADDR

Is it possible I'm running some older rev of this driver? My kernel version shows as:

    Linux version 2.6.10

Any ideas??

James

[kwong]

The change in the kernel that you're referring to was required due to how our custom boards were designed. All the testing that we've done has indicated that the driver in the 2.6.10 kernel seems fine, so it shouldn't be that.

One of the things that you may want to try (this will seem a little condescending) is to ping the board after you lose your nfs/webserver connections.   Pings are handled from within the kernel so you'd be eliminating the "userspace" variable from your testing.  If the ping works, then your kernel is fine.

Thinking along the same vein, I'd say that all of your problems seem to hinge on the nfs mounting "instability".  I don't suppose there could be another board on your network with the same IP address/MAC address?  The MAC address thing has bitten us in the past since the MAC address is software controllable.

Ken.

[jkimble]

I'll try the ping. That'll narrow it down.

Another thing I'm unsure of. We changed the bus speed on our hardware from the 200MHz on the eval board to 172MHz (no idea why...) on our board.  Of course I had to adjust the clock on the serial port but I would have thought the ethernet would be more flexible. I wouldn't think this would cause the type of behaviour we're seeing but what do you think?

James

[kwong]

I'm guessing that you're TFTP'ing your kernel over to the board via colilo.  If that's been working successfully then I think your Ethernet hardware can be considered fine.

So, even with the change in clock speed, I wouldn't worry about it too much.

Ken.

[jkimble]

I am able to ping without problem so at least at the kernel level things are behaving. I wrote a little test program to read and write to the nfs mounted file system. I can read from it but the thing just hangs when it goes to write to it. Oddly enough I can create and write to files with vi (??!!) but nothing else seems to be able to write to the file system.

Very weird....

James

[jkimble]

You're a life saver! Thanks for all your help.

[jkimble]

Yeah, that caught me too. Gave a different message though (kernel panic). This is just weird. I can actually bring my evaluation board up on exactly the same nfs filesystem mount and it runs fine. That tells me it's not an nfs or file permissions issue.

One thing I'm unsure of is the need for flash memory for Linux to run. The flash on my board is configured differently than that on the evaluation board. I made it work with the boot loader (Colilo) but I just turned off MTD support in the kernel so it wouldn't try to use it. I don't know if Linux can work correctly without it. The boot up doesn't have any hickups until it tries to work with syslogd and klogd. When I turn that off it gets to the point it tries to add a static rout to the gateway and hangs up there with the same messages.

Very weird...