This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/AM3352: Ethernet issues

Part Number: AM3352

Tool/software: Linux

Hi Sitara support Team,

My customer is facing that the Ethernet the mass-produced AM3352 board can not be connected.

Here are the status.

-When it operates continuously, the initialized network setting is occurred very rarely.

-From the following kernel message, it seems to operate again that the processing should do only at the power on.

*Linux kernel message*
[20.831927] net eth0: initializing cpsw version 1.12 (0)
[20.883872] net eth0: initialized cpsw ale version 1.4
[20.942486] net eth0: ALE Table size 1024
[21.086731] SMSC LAN8710/LAN8720 4a101000.mdio:00: attached PHY driver
[SMSC LAN8710/LAN8720] (mii_bus:phy_addr=4a101000.mdio:00, irq=-1)
[21.153309] libphy: PHY 4a101000.mdio:01 not found
[21.183308] net eth0: phy "4a101000.mdio:01" not found on slave 1, err -19
[21.292622] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[23.206769] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
[23.214724] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

-PHY device: LAN8710 

-CPU, OS information;
 Linux version 4.9.28-geed43d1050 (Custom@ubuntu) (gcc version 6.2.1
 20161016 (Linaro GCC 6.2-2016.11) ) #1 PREEMPT Thu Jul 27 10:21:18 JST 2017
 CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
 OF: fdt:Machine model: TI AM335x [Custom info]

[Question]
1. Could you please provide me the way of verification?
2. Was there similar report so far?

I will post the other information such as the frequency of connection error, the boot log,
their file system after getting the reply from my customer. 

Best regards,
Kanae

  • Please complete this checklist and post the results here: processors.wiki.ti.com/.../5x_CPSW
  • Hi Biser,

    Here are additional information from my customer.

    [Status Details]

    -Test units:                 6 systems
    -Operating time:                137 hours
    -The initialized occurred:   2 units occurred once, 1 unit occurred twice, 3 units not occurred

    -Required info by "Ethernet Triage Checklist for AM3x/4x/5x CPSW"

    "ethtool eth0" → log_ethtool.txt 

    log_ethtool.txt
    Settings for eth0:
    	Supported ports: [ TP MII ]
    	Supported link modes:   10baseT/Half 10baseT/Full 
    	                        100baseT/Half 100baseT/Full 
    	Supported pause frame use: Symmetric Receive-only
    	Supports auto-negotiation: Yes
    	Advertised link modes:  10baseT/Half 10baseT/Full 
    	                        100baseT/Half 100baseT/Full 
    	Advertised pause frame use: Symmetric Receive-only
    	Advertised auto-negotiation: Yes
    	Link partner advertised link modes:  10baseT/Half 10baseT/Full 
    	                                     100baseT/Half 100baseT/Full 
    	Link partner advertised pause frame use: No
    	Link partner advertised auto-negotiation: Yes
    	Speed: 100Mb/s
    	Duplex: Full
    	Port: MII
    	PHYAD: 0
    	Transceiver: external
    	Auto-negotiation: on
    	Supports Wake-on: d
    	Wake-on: d
    	Current message level: 0x00000000 (0)
    			       
    	Link detected: yes
    

    "ethtool -S eth0" → log_ethtool_s.txt 

    log_ethtool_s.txt
    NIC statistics:
         Good Rx Frames: 70125
         Broadcast Rx Frames: 42409
         Multicast Rx Frames: 4116
         Pause Rx Frames: 0
         Rx CRC Errors: 0
         Rx Align/Code Errors: 0
         Oversize Rx Frames: 0
         Rx Jabbers: 0
         Undersize (Short) Rx Frames: 0
         Rx Fragments: 0
         Rx Octets: 4941384
         Good Tx Frames: 33971
         Broadcast Tx Frames: 2
         Multicast Tx Frames: 35
         Pause Tx Frames: 0
         Deferred Tx Frames: 0
         Collisions: 0
         Single Collision Tx Frames: 0
         Multiple Collision Tx Frames: 0
         Excessive Collisions: 0
         Late Collisions: 0
         Tx Underrun: 0
         Carrier Sense Errors: 0
         Tx Octets: 2644286
         Rx + Tx 64 Octet Frames: 66058
         Rx + Tx 65-127 Octet Frames: 37423
         Rx + Tx 128-255 Octet Frames: 518
         Rx + Tx 256-511 Octet Frames: 19
         Rx + Tx 512-1023 Octet Frames: 13
         Rx + Tx 1024-Up Octet Frames: 65
         Net Octets: 7585670
         Rx Start of Frame Overruns: 0
         Rx Middle of Frame Overruns: 0
         Rx DMA Overruns: 0
         Rx DMA chan 0: head_enqueue: 2
         Rx DMA chan 0: tail_enqueue: 121071
         Rx DMA chan 0: pad_enqueue: 0
         Rx DMA chan 0: misqueued: 0
         Rx DMA chan 0: desc_alloc_fail: 0
         Rx DMA chan 0: pad_alloc_fail: 0
         Rx DMA chan 0: runt_receive_buf: 0
         Rx DMA chan 0: runt_transmit_bu: 0
         Rx DMA chan 0: empty_dequeue: 0
         Rx DMA chan 0: busy_dequeue: 95260
         Rx DMA chan 0: good_dequeue: 120818
         Rx DMA chan 0: requeue: 1
         Rx DMA chan 0: teardown_dequeue: 127
         Tx DMA chan 0: head_enqueue: 61755
         Tx DMA chan 0: tail_enqueue: 97
         Tx DMA chan 0: pad_enqueue: 0
         Tx DMA chan 0: misqueued: 79
         Tx DMA chan 0: desc_alloc_fail: 0
         Tx DMA chan 0: pad_alloc_fail: 0
         Tx DMA chan 0: runt_receive_buf: 0
         Tx DMA chan 0: runt_transmit_bu: 22568
         Tx DMA chan 0: empty_dequeue: 61756
         Tx DMA chan 0: busy_dequeue: 10
         Tx DMA chan 0: good_dequeue: 61852
         Tx DMA chan 0: requeue: 1
         Tx DMA chan 0: teardown_dequeue: 0
    

    "ifconfig eth0" → log_ifconfig.txt 

    log_ifconfig.txt
    eth0      Link encap:Ethernet  HWaddr 00:10:B1:0E:40:0A  
              inet addr:192.168.0.21  Bcast:0.0.0.0  Mask:255.255.255.0
              inet6 addr: fe80::210:b1ff:fe0e:400a%3068249184/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:121012 errors:0 dropped:0 overruns:0 frame:0
              TX packets:61957 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:7605149 (7.2 MiB)  TX bytes:4538268 (4.3 MiB)
              Interrupt:174 
    
    

    "dmesg" command → log_kernel.txt 

    log_kernel.txt
    [    0.000000] Booting Linux on physical CPU 0x0
    [    0.000000] Linux version 4.9.28-geed43d1050 (fora@ubuntu) (gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11) ) #1 PREEMPT Thu Jul 27 10:21:18 JST 2017
    [    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
    [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
    [    0.000000] OF: fdt:Machine model: TI AM335x ForAUSF
    [    0.000000] efi: Getting EFI parameters from FDT:
    [    0.000000] efi: UEFI not found.
    [    0.000000] cma: Reserved 48 MiB at 0x8a800000
    [    0.000000] Memory policy: Data cache writeback
    [    0.000000] On node 0 totalpages: 65536
    [    0.000000] free_area_init_node: node 0, pgdat c0c439b8, node_mem_map cfda1000
    [    0.000000]   Normal zone: 576 pages used for memmap
    [    0.000000]   Normal zone: 0 pages reserved
    [    0.000000]   Normal zone: 65536 pages, LIFO batch:15
    [    0.000000] CPU: All CPU(s) started in SVC mode.
    [    0.000000] AM335X ES2.1 (neon)
    [    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
    [    0.000000] pcpu-alloc: [0] 0 
    [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 64960
    [    0.000000] Kernel command line: console=ttyO0,115200n8 root=PARTUUID=7ab85957-02 rw rootfstype=ext4 rootwait
    [    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
    [    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
    [    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
    [    0.000000] Memory: 198336K/262144K available (7168K kernel code, 279K rwdata, 2348K rodata, 1024K init, 272K bss, 14656K reserved, 49152K cma-reserved, 0K highmem)
    [    0.000000] Virtual kernel memory layout:
                       vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                       fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                       vmalloc : 0xd0800000 - 0xff800000   ( 752 MB)
                       lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
                       pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
                       modules : 0xbf000000 - 0xbfe00000   (  14 MB)
                         .text : 0xc0008000 - 0xc0800000   (8160 kB)
                         .init : 0xc0b00000 - 0xc0c00000   (1024 kB)
                         .data : 0xc0c00000 - 0xc0c45f10   ( 280 kB)
                          .bss : 0xc0c45f10 - 0xc0c8a1b4   ( 273 kB)
    [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
    [    0.000000] Preemptible hierarchical RCU implementation.
    [    0.000000] 	Build-time adjustment of leaf fanout to 32.
    [    0.000000] NR_IRQS:16 nr_irqs:16 16
    [    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
    [    0.000000] OMAP clockevent source: timer2 at 24000000 Hz
    [    0.000019] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
    [    0.000042] clocksource: timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
    [    0.000053] OMAP clocksource: timer1 at 24000000 Hz
    [    0.000236] clocksource_probe: no matching clocksources found
    [    0.000434] Console: colour dummy device 80x30
    [    0.000464] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
    [    0.000472] This ensures that you still see kernel messages. Please
    [    0.000478] update your kernel commandline.
    [    0.000503] Calibrating delay loop... 795.44 BogoMIPS (lpj=3977216)
    [    0.089061] pid_max: default: 32768 minimum: 301
    [    0.089203] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
    [    0.089215] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
    [    0.090104] CPU: Testing write buffer coherency: ok
    [    0.090547] Setting up static identity map for 0x80100000 - 0x80100060
    [    0.091499] EFI services will not be available.
    [    0.092913] devtmpfs: initialized
    [    0.105238] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
    [    0.105637] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
    [    0.105670] futex hash table entries: 256 (order: -1, 3072 bytes)
    [    0.110138] pinctrl core: initialized pinctrl subsystem
    [    0.111572] NET: Registered protocol family 16
    [    0.113719] DMA: preallocated 256 KiB pool for atomic coherent allocations
    [    0.129320] omap_hwmod: debugss: _wait_target_disable failed
    [    0.209059] cpuidle: using governor ladder
    [    0.239043] cpuidle: using governor menu
    [    0.243632] gpio gpiochip0: (gpio): added GPIO chardev (254:0)
    [    0.244066] gpiochip_setup_dev: registered GPIOs 0 to 31 on device: gpiochip0 (gpio)
    [    0.245604] OMAP GPIO hardware version 0.1
    [    0.246530] gpio gpiochip1: (gpio): added GPIO chardev (254:1)
    [    0.246885] gpiochip_setup_dev: registered GPIOs 32 to 63 on device: gpiochip1 (gpio)
    [    0.248953] gpio gpiochip2: (gpio): added GPIO chardev (254:2)
    [    0.249501] gpiochip_setup_dev: registered GPIOs 64 to 95 on device: gpiochip2 (gpio)
    [    0.251660] gpio gpiochip3: (gpio): added GPIO chardev (254:3)
    [    0.252002] gpiochip_setup_dev: registered GPIOs 96 to 127 on device: gpiochip3 (gpio)
    [    0.260248] omap-gpmc 50000000.gpmc: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/gpmc_pins, deferring probe
    [    0.262816] hw-breakpoint: debug architecture 0x4 unsupported.
    [    0.307884] edma 49000000.edma: TI EDMA DMA engine driver
    [    0.308264] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/fixedregulator0[0]'
    [    0.308607] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/fixedregulator1[0]'
    [    0.308916] of_get_named_gpiod_flags: parsed 'gpio' property of node '/fixedregulator2[0]' - status (0)
    [    0.312359] omap_i2c 44e0b000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_i2c0_pins, deferring probe
    [    0.312427] omap_i2c 4819c000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_i2c2_pins, deferring probe
    [    0.312560] media: Linux media interface: v0.10
    [    0.312620] Linux video capture interface: v2.00
    [    0.312668] pps_core: LinuxPPS API ver. 1 registered
    [    0.312676] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
    [    0.312703] PTP clock support registered
    [    0.312747] EDAC MC: Ver: 3.0.0
    [    0.314017] omap-mailbox 480c8000.mailbox: omap mailbox rev 0x400
    [    0.314402] Advanced Linux Sound Architecture Driver Initialized.
    [    0.315842] clocksource: Switched to clocksource timer1
    [    0.327212] NET: Registered protocol family 2
    [    0.328105] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
    [    0.328142] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
    [    0.328171] TCP: Hash tables configured (established 2048 bind 2048)
    [    0.328254] UDP hash table entries: 256 (order: 0, 4096 bytes)
    [    0.328274] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
    [    0.328413] NET: Registered protocol family 1
    [    0.328920] RPC: Registered named UNIX socket transport module.
    [    0.328937] RPC: Registered udp transport module.
    [    0.328944] RPC: Registered tcp transport module.
    [    0.328952] RPC: Registered tcp NFSv4.1 backchannel transport module.
    [    0.328968] PCI: CLS 0 bytes, default 64
    [    0.330002] hw perfevents: enabled with armv7_cortex_a8 PMU driver, 5 counters available
    [    0.332581] workingset: timestamp_bits=14 max_order=16 bucket_order=2
    [    0.340961] squashfs: version 4.0 (2009/01/31) Phillip Lougher
    [    0.342034] NFS: Registering the id_resolver key type
    [    0.342084] Key type id_resolver registered
    [    0.342093] Key type id_legacy registered
    [    0.342148] ntfs: driver 2.1.32 [Flags: R/O].
    [    0.344271] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
    [    0.344295] io scheduler noop registered
    [    0.344304] io scheduler deadline registered
    [    0.344471] io scheduler cfq registered (default)
    [    0.345533] pinctrl-single 44e10800.pinmux: please update dts to use #pinctrl-cells = <1>
    [    0.346239] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
    [    0.348384] pwm-backlight backlight: GPIO lookup for consumer enable
    [    0.348398] pwm-backlight backlight: using device tree for GPIO lookup
    [    0.348412] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/backlight[0]'
    [    0.348420] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/backlight[0]'
    [    0.348426] pwm-backlight backlight: using lookup tables for GPIO lookup
    [    0.348434] pwm-backlight backlight: lookup for GPIO enable failed
    [    0.348460] backlight supply power not found, using dummy regulator
    [    0.414740] Serial: 8250/16550 driver, 10 ports, IRQ sharing disabled
    [    0.419251] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158, base_baud = 3000000) is a 8250
    [    1.037086] console [ttyS0] enabled
    [    1.042578] omap_rng 48310000.rng: OMAP Random Number Generator ver. 20
    [    1.049441] [drm] Initialized
    [    1.067913] brd: module loaded
    [    1.078258] loop: module loaded
    [    1.084707] m25p80 spi1.0: n25q128a13 (16384 Kbytes)
    [    1.089960] 6 ofpart partitions found on MTD device spi1.0
    [    1.095474] Creating 6 MTD partitions on "spi1.0":
    [    1.100329] 0x000000000000-0x000000020000 : "MLO.byteswap"
    [    1.107347] 0x000000020000-0x0000000a0000 : "u-boot.img"
    [    1.113952] 0x0000000a0000-0x0000000c0000 : "1st u-boot env"
    [    1.120967] 0x0000000c0000-0x0000000e0000 : "2nd u-boot env"
    [    1.127889] 0x0000000e0000-0x000000442000 : "Linux Kernel"
    [    1.133408] mtd: partition "Linux Kernel" doesn't end on an erase block -- force read-only
    [    1.142957] 0x000000442000-0x000001000000 : "Userland"
    [    1.148195] mtd: partition "Userland" doesn't start on an erase block boundary -- force read-only
    [    1.158991] m25p80 spi1.1: unrecognized JEDEC id bytes: ff, ff, ff
    [    1.166431] libphy: Fixed MDIO Bus: probed
    [    1.245935] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
    [    1.252080] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
    [    1.259390] libphy: 4a101000.mdio: probed
    [    1.263439] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
    [    1.273613] cpsw 4a100000.ethernet: Detected MACID = 60:64:05:fa:97:ac
    [    1.280461] cpsw 4a100000.ethernet: cpts: overflow check period 500 (jiffies)
    [    1.289699] mousedev: PS/2 mouse device common for all mice
    [    1.295738] i2c /dev entries driver
    [    1.301344] cpuidle: enable-method property 'ti,am3352' found operations
    [    1.309158] omap_hsmmc 48060000.mmc: GPIO lookup for consumer cd
    [    1.309169] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
    [    1.309203] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/ocp/mmc@48060000[0]' - status (0)
    [    1.309297] omap_hsmmc 48060000.mmc: Got CD GPIO
    [    1.313952] omap_hsmmc 48060000.mmc: GPIO lookup for consumer wp
    [    1.313957] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
    [    1.313966] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@48060000[0]'
    [    1.313974] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@48060000[0]'
    [    1.313980] omap_hsmmc 48060000.mmc: using lookup tables for GPIO lookup
    [    1.313988] omap_hsmmc 48060000.mmc: lookup for GPIO wp failed
    [    1.336597] ledtrig-cpu: registered to indicate activity on CPUs
    [    1.344918] NET: Registered protocol family 10
    [    1.351103] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
    [    1.358089] NET: Registered protocol family 17
    [    1.362888] Key type dns_resolver registered
    [    1.367734] omap_voltage_late_init: Voltage driver support not added
    [    1.380524] omap-gpmc 50000000.gpmc: GPMC revision 6.0
    [    1.385722] gpmc_mem_init: disabling cs 0 mapped at 0x0-0x1000000
    [    1.392062] gpiochip_find_base: found new base at 510
    [    1.392117] gpio gpiochip4: (omap-gpmc): added GPIO chardev (254:4)
    [    1.392550] gpiochip_setup_dev: registered GPIOs 510 to 511 on device: gpiochip4 (omap-gpmc)
    [    1.392678] gpmc_read_settings_dt: page/burst-length set but not used!
    [    1.426090] tps65910 0-002d: No interrupt support, no core IRQ
    [    1.432204] tps65910-gpio tps65910-gpio: ti,en-gpio-sleep not specified
    [    1.432234] gpiochip_find_base: found new base at 504
    [    1.432270] gpio gpiochip5: (tps65910): added GPIO chardev (254:5)
    [    1.432599] gpiochip_setup_dev: registered GPIOs 504 to 509 on device: gpiochip5 (tps65910)
    [    1.434142] vrtc: supplied by vbat
    [    1.441426] vio: supplied by vbat
    [    1.446323] vdd1: supplied by vbat
    [    1.451577] vdd2: supplied by vbat
    [    1.458193] random: fast init done
    [    1.461759] vdig1: supplied by vbat
    [    1.466705] vdig2: supplied by vbat
    [    1.471608] vpll: supplied by vbat
    [    1.476427] vdac: supplied by vbat
    [    1.481238] vaux1: supplied by vbat
    [    1.486149] vaux2: supplied by vbat
    [    1.491054] vaux33: supplied by vbat
    [    1.496062] vmmc: supplied by vbat
    [    1.500868] vbb: supplied by vbat
    [    1.505413] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
    [    1.512430] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 400 kHz
    [    1.518362] pwm-backlight backlight: GPIO lookup for consumer enable
    [    1.518371] pwm-backlight backlight: using device tree for GPIO lookup
    [    1.518385] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/backlight[0]'
    [    1.518393] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/backlight[0]'
    [    1.518400] pwm-backlight backlight: using lookup tables for GPIO lookup
    [    1.518408] pwm-backlight backlight: lookup for GPIO enable failed
    [    1.518447] backlight supply power not found, using dummy regulator
    [    1.527125] omap_hsmmc 48060000.mmc: GPIO lookup for consumer cd
    [    1.527138] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
    [    1.527172] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/ocp/mmc@48060000[0]' - status (0)
    [    1.527261] omap_hsmmc 48060000.mmc: Got CD GPIO
    [    1.531918] omap_hsmmc 48060000.mmc: GPIO lookup for consumer wp
    [    1.531924] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
    [    1.531932] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@48060000[0]'
    [    1.531939] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@48060000[0]'
    [    1.531945] omap_hsmmc 48060000.mmc: using lookup tables for GPIO lookup
    [    1.531953] omap_hsmmc 48060000.mmc: lookup for GPIO wp failed
    [    1.586586] pwm-backlight backlight: GPIO lookup for consumer enable
    [    1.586603] pwm-backlight backlight: using device tree for GPIO lookup
    [    1.586618] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/backlight[0]'
    [    1.586627] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/backlight[0]'
    [    1.586636] pwm-backlight backlight: using lookup tables for GPIO lookup
    [    1.586645] pwm-backlight backlight: lookup for GPIO enable failed
    [    1.586679] backlight supply power not found, using dummy regulator
    [    1.594332] hctosys: unable to open rtc device (rtc0)
    [    1.601480] lis3_reg: disabling
    [    1.606783] wlan-en-regulator: disabling
    [    1.610984] ALSA device list:
    [    1.614028]   No soundcards found.
    [    1.618910] Waiting for root device PARTUUID=7ab85957-02...
    [    1.663645] mmc0: host does not support reading read-only switch, assuming write-enable
    [    1.674241] mmc0: new high speed SDHC card at address 0260
    [    1.680749] mmcblk0: mmc0:0260 HSS08 7.21 GiB 
    [    1.687941]  mmcblk0: p1 p2
    [    1.692329] pwm-backlight backlight: GPIO lookup for consumer enable
    [    1.692343] pwm-backlight backlight: using device tree for GPIO lookup
    [    1.692359] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/backlight[0]'
    [    1.692369] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/backlight[0]'
    [    1.692377] pwm-backlight backlight: using lookup tables for GPIO lookup
    [    1.692387] pwm-backlight backlight: lookup for GPIO enable failed
    [    1.692433] backlight supply power not found, using dummy regulator
    [    1.898870] EXT4-fs (mmcblk0p2): recovery complete
    [    1.906747] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
    [    1.915034] VFS: Mounted root (ext4 filesystem) on device 179:2.
    [    1.928697] devtmpfs: mounted
    [    1.936136] Freeing unused kernel memory: 1024K (c0b00000 - c0c00000)
    [    2.315240] systemd[1]: System time before build time, advancing clock.
    [    2.428643] systemd[1]: systemd 230 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
    [    2.447759] systemd[1]: Detected architecture arm.
    [    2.487831] systemd[1]: Set hostname to <am335x-evm>.
    [    2.983170] systemd[1]: Configuration file /etc/systemd/system/usf106udc_apl.service is marked executable. Please remove executable permission bits. Proceeding anyway.
    [    3.188343] systemd[1]: sysinit.target: Found ordering cycle on sysinit.target/start
    [    3.196358] systemd[1]: sysinit.target: Found dependency on alignment.service/start
    [    3.204090] systemd[1]: sysinit.target: Found dependency on basic.target/start
    [    3.211476] systemd[1]: sysinit.target: Found dependency on sysinit.target/start
    [    3.218961] systemd[1]: sysinit.target: Breaking ordering cycle by deleting job alignment.service/start
    [    3.228444] systemd[1]: alignment.service: Job alignment.service/start deleted to break ordering cycle starting with sysinit.target/start
    [    3.634414] cryptodev: loading out-of-tree module taints kernel.
    [    3.669627] cryptodev: driver 1.8 loaded.
    [    3.911594] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
    [    5.064377] systemd-journald[103]: Received request to flush runtime journal from PID 1
    [    6.681975] of_get_named_gpiod_flags: parsed 'row-gpios' property of node '/matrix_keypad0[0]' - status (0)
    [    6.682012] of_get_named_gpiod_flags: parsed 'row-gpios' property of node '/matrix_keypad0[1]' - status (0)
    [    6.682036] of_get_named_gpiod_flags: parsed 'row-gpios' property of node '/matrix_keypad0[2]' - status (0)
    [    6.682049] of_get_named_gpiod_flags: parsed 'col-gpios' property of node '/matrix_keypad0[0]' - status (0)
    [    6.682067] of_get_named_gpiod_flags: parsed 'col-gpios' property of node '/matrix_keypad0[1]' - status (0)
    [    6.682549] input: matrix_keypad0 as /devices/platform/matrix_keypad0/input/input0
    [    6.795421] pwm-backlight backlight: GPIO lookup for consumer enable
    [    6.795443] pwm-backlight backlight: using device tree for GPIO lookup
    [    6.795460] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/backlight[0]'
    [    6.795469] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/backlight[0]'
    [    6.795475] pwm-backlight backlight: using lookup tables for GPIO lookup
    [    6.795484] pwm-backlight backlight: lookup for GPIO enable failed
    [    6.795527] backlight supply power not found, using dummy regulator
    [    6.875823] rtc rtc0: 44e3e000.rtc: dev (253:0)
    [    6.876109] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
    [    6.883714] pwm-backlight backlight: GPIO lookup for consumer enable
    [    6.883725] pwm-backlight backlight: using device tree for GPIO lookup
    [    6.883741] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/backlight[0]'
    [    6.883749] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/backlight[0]'
    [    6.883757] pwm-backlight backlight: using lookup tables for GPIO lookup
    [    6.883765] pwm-backlight backlight: lookup for GPIO enable failed
    [    6.883809] backlight supply power not found, using dummy regulator
    [    6.915740] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
    [    6.923332] pwm-backlight backlight: GPIO lookup for consumer enable
    [    6.923340] pwm-backlight backlight: using device tree for GPIO lookup
    [    6.923354] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/backlight[0]'
    [    6.923361] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/backlight[0]'
    [    6.923367] pwm-backlight backlight: using lookup tables for GPIO lookup
    [    6.923375] pwm-backlight backlight: lookup for GPIO enable failed
    [    6.923417] backlight supply power not found, using dummy regulator
    [    7.077492] pwm-backlight backlight: GPIO lookup for consumer enable
    [    7.077508] pwm-backlight backlight: using device tree for GPIO lookup
    [    7.077523] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/backlight[0]'
    [    7.077530] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/backlight[0]'
    [    7.077538] pwm-backlight backlight: using lookup tables for GPIO lookup
    [    7.077546] pwm-backlight backlight: lookup for GPIO enable failed
    [    7.077588] backlight supply power not found, using dummy regulator
    [    8.107192] CAN device driver interface
    [    8.271008] c_can_platform 481d0000.can: c_can_platform device registered (regs=fa1d0000, irq=163)
    [    8.536445] pwm-backlight backlight: GPIO lookup for consumer enable
    [    8.536461] pwm-backlight backlight: using device tree for GPIO lookup
    [    8.536476] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/backlight[0]'
    [    8.536484] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/backlight[0]'
    [    8.536491] pwm-backlight backlight: using lookup tables for GPIO lookup
    [    8.536500] pwm-backlight backlight: lookup for GPIO enable failed
    [    8.536544] backlight supply power not found, using dummy regulator
    [    9.168471] pwm-backlight backlight: GPIO lookup for consumer enable
    [    9.168492] pwm-backlight backlight: using device tree for GPIO lookup
    [    9.168507] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/backlight[0]'
    [    9.168515] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/backlight[0]'
    [    9.168522] pwm-backlight backlight: using lookup tables for GPIO lookup
    [    9.168531] pwm-backlight backlight: lookup for GPIO enable failed
    [    9.168572] backlight supply power not found, using dummy regulator
    [    9.195392] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
    [    9.400477] pwm-backlight backlight: GPIO lookup for consumer enable
    [    9.400499] pwm-backlight backlight: using device tree for GPIO lookup
    [    9.400515] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/backlight[0]'
    [    9.400524] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/backlight[0]'
    [    9.400531] pwm-backlight backlight: using lookup tables for GPIO lookup
    [    9.400539] pwm-backlight backlight: lookup for GPIO enable failed
    [    9.400581] backlight supply power not found, using dummy regulator
    [    9.410223] omap_hwmod: pruss: _wait_target_ready failed: -16
    [    9.410239] pruss-soc-bus 4a326000.pruss-soc-bus: use pm_runtime_put_sync_suspend() in driver?
    [    9.410248] pruss-soc-bus 4a326000.pruss-soc-bus: couldn't enable module
    [    9.410294] pruss-soc-bus: probe of 4a326000.pruss-soc-bus failed with error -16
    [    9.410486] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
    [    9.430156] omap-aes 53500000.aes: will run requests pump with realtime priority
    [    9.537748] omap_hwmod: gfx: failed to hardreset
    [    9.588983] remoteproc remoteproc0: wkup_m3 is available
    [    9.727950] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
    [    9.747064] pvrsrvkm 56000000.sgx: Unable to reset SGX!
    [    9.766345] omap_hwmod: gfx: _wait_target_ready failed: -16
    [    9.826543] pvrsrvkm 56000000.sgx: use pm_runtime_put_sync_suspend() in driver?
    [    9.826578] PVR_K:(Error): EnableSGXClocks: pm_runtime_get_sync failed (16)
    [    9.826593] PVR_K:(Error): SysInitialise: Failed to Enable system clocks (175)
    [    9.962694] remoteproc remoteproc0: powering up wkup_m3
    [   10.008669] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 224344
    [   10.008959] remoteproc remoteproc0: remote processor wkup_m3 is now up
    [   10.008987] wkup_m3_ipc 44e11324.wkup_m3_ipc: CM3 Firmware Version = 0x192
    [   10.030373] PM: bootloader does not support rtc-only!
    [   12.097136] pwm-backlight backlight: GPIO lookup for consumer enable
    [   12.097154] pwm-backlight backlight: using device tree for GPIO lookup
    [   12.097168] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/backlight[0]'
    [   12.097176] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/backlight[0]'
    [   12.097183] pwm-backlight backlight: using lookup tables for GPIO lookup
    [   12.097191] pwm-backlight backlight: lookup for GPIO enable failed
    [   12.097233] backlight supply power not found, using dummy regulator
    [   14.199125] NET: Registered protocol family 15
    [   15.208738] Initializing XFRM netlink socket
    [   18.345987] random: crng init done
    [   19.538335] pwm-backlight backlight: GPIO lookup for consumer enable
    [   19.538356] pwm-backlight backlight: using device tree for GPIO lookup
    [   19.538371] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/backlight[0]'
    [   19.538379] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/backlight[0]'
    [   19.538386] pwm-backlight backlight: using lookup tables for GPIO lookup
    [   19.538395] pwm-backlight backlight: lookup for GPIO enable failed
    [   19.538438] backlight supply power not found, using dummy regulator
    [   20.446925] c_can_platform 481d0000.can can0: setting BTR=2701 BRPE=0000
    [   20.626315] can: controller area network core (rev 20120528 abi 9)
    [   20.632722] NET: Registered protocol family 29
    [   20.765125] can: raw protocol (rev 20120528)
    [   22.571000] net eth0: initializing cpsw version 1.12 (0)
    [   22.619813] net eth0: initialized cpsw ale version 1.4
    [   22.625008] net eth0: ALE Table size 1024
    [   22.776705] SMSC LAN8710/LAN8720 4a101000.mdio:00: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=4a101000.mdio:00, irq=-1)
    [   22.812784] libphy: PHY 4a101000.mdio:01 not found
    [   22.836099] net eth0: phy "4a101000.mdio:01" not found on slave 1, err -19
    [   22.900257] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [   28.006683] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
    [   28.026041] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [34067.173814] net eth0: initializing cpsw version 1.12 (0)
    [34067.180790] net eth0: initialized cpsw ale version 1.4
    [34067.190767] net eth0: ALE Table size 1024
    [34067.306469] SMSC LAN8710/LAN8720 4a101000.mdio:00: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=4a101000.mdio:00, irq=-1)
    [34067.320852] libphy: PHY 4a101000.mdio:01 not found
    [34067.332925] net eth0: phy "4a101000.mdio:01" not found on slave 1, err -19
    [34067.371006] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [34069.366686] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
    [34069.388364] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    

    "uname -a" command → log_uname.txt 

    log_uname.txt
    Linux am335x-evm 4.9.28-geed43d1050 #1 PREEMPT Thu Jul 27 10:21:18 JST 2017 armv7l GNU/Linux
    

    Device tree source file →device_tree.zip device_tree.zip

     

    If you need other info, please let me know.

    Best regards,
    Kanae

  • Hi,

    The initialization problem you are experiencing, is eth0 not coming up or is it eth1 not coming up? The text in the first message seems to indicate that the issue is eth1.

    Thanks for posting the requested data. overall the data shows an interface operating normally. Could you please describe the test for that is being done, is this problem occurring while operating? During a reboot?

    Best Regards,
    Schuyler
  • Hi Schuyler,
    Thank you for your reply.

    As my first post described, the status is ...

    *****
    -When it operates continuously, the initialized network setting is occurred very rarely.

    -From the following kernel message, it seems to operate again
     that the processing should do only at the power on.

    *Linux kernel message*
    [20.831927] net eth0: initializing cpsw version 1.12 (0)
    [20.883872] net eth0: initialized cpsw ale version 1.4
    [20.942486] net eth0: ALE Table size 1024
    [21.086731] SMSC LAN8710/LAN8720 4a101000.mdio:00: attached PHY driver
    [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=4a101000.mdio:00, irq=-1)
    [21.153309] libphy: PHY 4a101000.mdio:01 not found
    [21.183308] net eth0: phy "4a101000.mdio:01" not found on slave 1, err -19
    [21.292622] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [23.206769] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
    [23.214724] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    ******
     
    So, the initialization occurring problem my customer are experiencing is
    that eth0 is starting to initialize during the operating.

    The test applications are the control by mainly using GPMC bus and the CAN communications.
    They are always-on during the operation.
     
    Best regards,
    Kanae

  • Hi Kanae,
    I am still not sure I understand the issue that the customer is experiencing. The kernel log looks to be the boot time of eth0 initialization as you say. But the issue is that the eth0 does a link down and then re-initializes during testing? I am guessing that the customer does not perform an link up/down with ifconfig on eth0. Is there a way to capture the log file of all eth0 messages during operation? It looks like it is a long test time, but the if the link is re-initializing the link must have gone down at some point.

    So eth1 is not used in the customer's testing at all?

    Best Regards,
    Schuyler
  •  

    Hi Schuyler,

    Thank you for your quick reply!

     As you post, the issue is that the eth0 does a link down and then re-initializes during testing.
    I suppose that the eth0 was set proper from log_ifconfig.txt I attached.
    Do you think there is some problem?

    I will ask my customer to capture the log file of all eth0 messages during operation,
    and not to be use eth1 in the customer's testing at all.

    If you need other information, please let me know.

    Best regards,
    Kanae

     

  • Hi Kanae,

    Looking at the posted log file again there does not appear to be a reason for the network interface to be re-initialized. There was not a link down reported by Linux. Does the application do a net restart for any kind of detected error? What kind of problem does the network reinitialization cause?

    Best Regards,
    Schuyler
  • Hi Kanae,

    I looked through the log post again and I don't see this message. This is the message that we are looking for, one that indicates the link went down.

    cpsw 4a100000.ethernet eth0: Link is Down

    There is a long time gap in the log file between the boot and the interface being reinitialized, was the file edited by chance to just show the re-initialization? If the log file was edited the link down message may have be removed by the edit.

    Also please use this command to see what might have been captured by the systemd-networkd:

    systemctl status systemd-networkd

    Best Regards,
    Schuyler
  • Hi Schuyler,

    I appreciate your kind support.

     

    I am asking my customer to your above requests.

     

    Regarding your questions in the before last post,

    unfortunately, my customer cannot connect a serial cable to their system

    to capture the log file of all eth0 messages during operation,

    And the eth1 is not used at all.

     

    Best regards,

    Kanae

  • Hi Kanae,

    How are they getting the logs now? They try to telnet into the system if they have a telnet server running in their system.

    Best Regards,
    Schuyler
  •  

    Hi Schuyler,

    I have got some information from my customer.

     

    1. "Does the application do a net restart for any kind of detected error?"

       -Their application does not have the process of a net restart except for the powered-on.

     

    2. "What kind of problem does the network reinitialization cause?"

       - The system communicates periodically from the device connected through a local network,

        and it has the problem rarely that the communication is extremely slow.

         After the network analysis, there are the evidence of network restart at occuring the problem.

         Therefore my customer is investigating the cause of this problem.

     

    3. Regarding a long time gap in the log file; log_kernel.txt,

       my customer has just captured "dmesg" output. So he does not edit the file at all.

     

    4. Regarding systemctl status systemd-networkd command,

      my customer has just run command "systemctl status systemd-networkd"

      to their system which has not occurred re-initialized error.

      The result is as follows.

      ===========================================================

      systemd-networkd.service - Network Service

       Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; vendor preset: enabled)

       Active: inactive (dead)

         Docs: man:systemd-networkd.service(8)

      ===========================================================

     

    5. Regarding to capture the log file of all eth0 messages during operation",

      due to their machine system status, the system was powered down,

      now therefore my customer cannot get the log after the restart.

      The system is continuously running again,

      so my customer will try to get the log after re-initialized error.

     

     

    I will check about "telnet" you asked later.

     

    Best regards,

    Kanae

  • Hi Kanae,

    One other log to attach is the results of this:

    journalctl | grep networkd

    We are looking for any indication that the link went down, either from dmesg or the application.

    Best Regards,
    Schuyler
  • Hi Schuyler,

     

    Thank you for your support!

    I will ask my customer to get the log by "journalctl | grep networkd" command.

     

    Here is answer for your question in your post dated the 19-March.

     

    Q. How are they getting the logs now?

     They try to telnet into the system if they have a telnet server running in their system."

     

    A. My customer get SSH protocol using TeraTerm.

     Their system cannot run a telnet server.

     

    Best regards,

    Kanae

  • Hi Schuyler,

     

    I have got the log of the error occurred units from my customer.

    The re-initialized error have occurred 63 units out of every 102 units

    at operating time is 15 days 18 hours.

    Number of occurrence depends on the unit from once to fifth.

     

    Here is a part of the log attached "192_168_0_14_kernel.txt".

    192_168_0_14_kernel.txt

    ...

    [696213.894449] net eth0: initializing cpsw version 1.12 (0)

    [696213.901557] net eth0: initialized cpsw ale version 1.4

    [696213.910965] net eth0: ALE Table size 1024

    [696214.034021] SMSC LAN8710/LAN8720 4a101000.mdio:00: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=4a101000.mdio:00, irq=-1)

    [696214.049555] libphy: PHY 4a101000.mdio:01 not found

    [696214.063263] net eth0: phy "4a101000.mdio:01" not found on slave 1, err -19

    [696214.099280] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

    [696217.204024] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off

    [696217.214126] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

    ...

     

     

    Please refer the details the attached 192.168.0.14.zip file for this unit.

    This unit have occurred the re-initialized error once.

    192.168.0.14.zip

     

    I attach the log data; 192.168.0.117.zip for your reference.

    This unit have occurred the re-initialized error fifth.

    192.168.0.117.zip 

     

    Question:

    At what kind of condition is the log above-mentioned output?

     

    If you need the other units log data, I got all 63 units log,

    so please let me know. I will share them via private message.

     

    Best regards,

    Kanae

     

  • Hi Kanae,
    Thanks for the log files. There is a new issue in that one of the boards is showing EXT4 FS errors, is this issue being looked at by the customer? Is there any environmental testing being performed as part of this test? Can they please provide a "ps aux" listing of the threads on one of the affected systems?

    At the moment I can't see what is causing what looks to be a network reset. The results of the "journalctl | grep networkd" might indicate if the link is going down. The kernel logs don't show a reason.

    Best Regards,
    Schuyler

  • Hi Schuyler,
    Thank you for your reply.

    Regarding "EXT4 FS errors", all boards (units) are showing this error in the kernel log.
    I will ask my customer whether he has already looked at this error.

    And also I will ask about the following your question/request.
    -Is there any environmental testing being performed as part of this test?
    -Can they please provide a "ps aux" listing of the threads on one of the affected systems?

    Please wait for the result of the "journalctl | grep networkd" on their affected system.

    I understand it is difficult to find the causes to start the re-initialization by part of system logs.
    My customer expects your experiences will be suggested any clue to solve this issue.

    Best regards,
    Kanae