BUILD: 1.9_M3.rc1: meta-intel: cea00968b858b60222d68103491f076067d73876 poky: ea562de57590c966cd5a75fda8defecd397e6436 IMAGE: core-image-sato-sdk ENVIRONMENT: intel-quark on Galileo v.2 STEPS TO REPRODUCE: Parse dmesg log and all log files in /var/log for keywords like: "error" , "failed" , "cannot", "can't" etc. Filter out the known and invalid errors or errors that appear in certain situations and need to be ignored. EXPECTED OUTCOME: No errors or fails should be present in logs ACTUAL OUTCOME: This error appears on dmesg log: Log: dmesg ----------------------- Central error: [ 9.473989] stmmaceth 0000:00:14.6: stmmac_dvr_probe: warning: cannot get CSR clock *********************** [ 9.413328] intel_quark_mfd_i2c_gpio 0000:00:15.2: enabling device (0000 -> 0002) [ 9.424827] Uniform Multi-Platform E-IDE driver [ 9.429464] ide-gd driver 1.18 [ 9.431837] ide-cd driver 5.00 [ 9.437171] CAN device driver interface [ 9.440705] pcnet32: pcnet32.c:v1.35 21.Apr.2008 tsbogend@alpha.franken.de [ 9.447662] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI [ 9.453794] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 9.459117] pch_gbe: EG20T PCH Gigabit Ethernet Driver - version 1.01 [ 9.466003] stmmaceth 0000:00:14.6: enabling device (0000 -> 0002) [ 9.473989] stmmaceth 0000:00:14.6: stmmac_dvr_probe: warning: cannot get CSR clock [ 9.480787] stmmaceth 0000:00:14.6: no reset control found [ 9.485213] stmmac - user ID: 0x10, Synopsys ID: 0x37 [ 9.489153] Ring mode enabled [ 9.491200] DMA HW capability register supported [ 9.494514] Enhanced/Alternate descriptors [ 9.497878] Enabled extended descriptors [ 9.500898] RX Checksum Offload Engine supported (type 2) [ 9.505300] TX Checksum insertion supported [ 9.508443] Enable RX Mitigation via HW Watchdog Timer [ 9.529857] libphy: stmmac: probed
Based on my research into the stmmac driver and code history this is a benign message and can be ignored (and whitelisted in our test system). The comment after this warning: /* If failed to obtain stmmac_clk and specific clk_csr value * is NOT passed from the platform, probe fail. The clk_csr value is passed and is valid so the probe continues successfully.
As per last comment set it as verified.