Bug 5362 - Failure to boot keystone over NFS
Summary: Failure to boot keystone over NFS
Status: RESOLVED OBSOLETE
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-ti (show other bugs)
Version: unspecified
Hardware: Other arm
: Medium normal
Target Milestone: 1.6
Assignee: Denys Dmytriyenko
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-10-17 06:17 UTC by George Nita
Modified: 2014-05-06 15:17 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description George Nita 2013-10-17 06:17:25 UTC
I did the following changes to recipes-kernel/linux/linux-keystone_3.8.4.bb in order to get kernel NFS boot option:
BRANCH = "sept-2013b/master"
SRCREV = "5349052e6eb19f496fdf7b1734ce55b217010339"


The board hangs immediately after U-boot initiates boot:
TCI6638 EVM # install_skern 0xc5f0000
## Starting boot kernel at 0x0c5f0000 ...
## Started boot kernel successfully
TCI6638 EVM # bootm 0x88000000 - 0x87000000
## Booting kernel from Legacy Image at 88000000 ...
   Image Name:   Linux-3.8.4
   Created:      2013-10-17   5:46:50 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3989704 Bytes = 3.8 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 87000000
   Booting using the fdt blob at 0x87000000
   Loading Kernel Image ... OK
OK
   Loading Device Tree to 87ed3000, end 87ee0e3c ... OK

Starting kernel ...
Comment 1 George Nita 2013-10-17 07:00:03 UTC
After changing gcc tool to version 4.7 the board attempts to boot over nfs, but hangs as it gets no reply to first request from the server:
[    0.758571] Sending DHCP requests ., OK
[    1.388557] IP-Config: Got DHCP answer from 172.24.31.254, my address is 172.24.31.237
[    2.649710] libphy: gpio-ffffffed:00 - Link is Up - 1000/Full
[    2.659703] libphy: gpio-ffffffed:01 - Link is Up - 1000/Full
[    2.798581] net eth0: removing rx vlan id: 0
[    3.088573] net eth2: removing rx vlan id: 0
[    3.408574] net eth3: removing rx vlan id: 0
[    3.409301] IP-Config: Complete:
[    3.409731]      device=eth1, hwaddr=02:18:31:7e:3e:6f, ipaddr=172.24.31.237, mask=255.255.254.0, gw=172.24.31.254
[    3.411104]      host=172.24.31.237, domain=stolab01.enea.se enea.se, nis-domain=(none)
[    3.412166]      bootserver=0.0.0.0, rootserver=172.21.3.145, rootpath=
[    3.413021]      nameserver0=172.24.0.1

The tcpdump log shows that the request has invalid checksum:
08:57:38.759181 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto UDP (17), length 120)
    172.24.31.237.55335 > sestofb10.enea.se.sunrpc: [bad udp cksum 0x7c21 -> 0x4736!] UDP, length 92
	0x0000:  4500 0078 0000 4000 3e11 c0c9 ac18 1fed  E..x..@.>.......
	0x0010:  ac15 0391 d827 006f 0064 7c21 42d0 5764  .....'.o.d|!B.Wd
	0x0020:  0000 0000 0000 0002 0001 86a0 0000 0002  ................
	0x0030:  0000 0003 0000 0001 0000 0024 028f 5b28  ...........$..[(
	0x0040:  0000 000d 3137 322e 3234 2e33 312e 3233  ....172.24.31.23
	0x0050:  3700 0000 0000 0000 0000 0000 0000 0000  7...............
	0x0060:  0000 0000 0000 0000 0001 86a5 0000 0001  ................
	0x0070:  0000 0011 0000 0000                      ........
08:58:16.394252 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto UDP (17), length 120)
    172.24.31.237.55335 > sestofb10.enea.se.sunrpc: [bad udp cksum 0x7c21 -> 0x4731!] UDP, length 92
	0x0000:  4500 0078 0000 4000 3e11 c0c9 ac18 1fed  E..x..@.>.......
	0x0010:  ac15 0391 d827 006f 0064 7c21 42d0 5764  .....'.o.d|!B.Wd
	0x0020:  0000 0000 0000 0002 0001 86a0 0000 0002  ................
	0x0030:  0000 0003 0000 0001 0000 0024 028f 5b2d  ...........$..[-
	0x0040:  0000 000d 3137 322e 3234 2e33 312e 3233  ....172.24.31.23
	0x0050:  3700 0000 0000 0000 0000 0000 0000 0000  7...............
	0x0060:  0000 0000 0000 0000 0001 86a5 0000 0001  ................
	0x0070:  0000 0011 0000 0000                      ........
Comment 2 Tudor Florea 2013-10-18 06:46:31 UTC
I found that temporarily reverting commit that enabled HW checksum offload ( http://arago-project.org/git/projects/?p=linux-keystone.git;a=commit;h=03334006a4882cd23b33f55cfd90dccdc3704ecf ) hide out the issue.
Comment 3 Denys Dmytriyenko 2014-05-06 15:17:27 UTC
linux-3.10.x is the latest supported version for keystone. 3.8 is obsolete now.