Re: [Linuxptp-users] phc2sys[273995.639]: failed to read clock: Invalid argument

[Pham, C. <Cal...@ne...>]

Hi Richard,
Below is the outputs of the commands. The current ethtool version doesn't support -T option so I have to compile version 3.7 and run for the source directory. Thanks for your help! 
     > the output of uname -a
	[root@V4-CALVIN ~]# uname -a
	Linux V4-CALVIN 3.7.5 #1 SMP Tue Feb 26 16:40:13 MST 2013 x86_64 x86_64 x86_64 GNU/Linux
   >  ethtool -T eth0
	[root@V4-CALVIN ethtool-3.7]# ./ethtool -T eth0
	Time stamping parameters for eth0:
	Capabilities:
      	  hardware-transmit     (SOF_TIMESTAMPING_TX_HARDWARE)
        	software-transmit     (SOF_TIMESTAMPING_TX_SOFTWARE)
        	hardware-receive      (SOF_TIMESTAMPING_RX_HARDWARE)
       	 software-receive      (SOF_TIMESTAMPING_RX_SOFTWARE)
        	software-system-clock (SOF_TIMESTAMPING_SOFTWARE)
       	 hardware-raw-clock    (SOF_TIMESTAMPING_RAW_HARDWARE)
	PTP Hardware Clock: 0
	Hardware Transmit Timestamp Modes:
        	off                   (HWTSTAMP_TX_OFF)
        	on                    (HWTSTAMP_TX_ON)
	Hardware Receive Filter Modes:
       	 none                  (HWTSTAMP_FILTER_NONE)
       	 all                   (HWTSTAMP_FILTER_ALL)

 > testptp -g
	[root@V4-CALVIN ptp]# ./testptp -g
	gettime: CLK_ID 0xffffffe3
	clock time: 1393941119.523279956 or Tue Mar  4 08:51:59 2014
	clock_gettime %m: Invalid argument

> ethtool -i eth0
[root@V4-CALVIN ptp]# ethtool -i eth0
driver: igb
version: 5.0.6
firmware-version: 1.61, 0x8000090e
bus-info: 0000:08:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes


-----Original Message-----
From: Richard Cochran [mailto:ric...@gm...] 
Sent: Tuesday, March 04, 2014 4:27 AM
To: Pham, Calvin
Cc: lin...@li...
Subject: Re: [Linuxptp-users] phc2sys[273995.639]: failed to read clock: Invalid argument

On Mon, Mar 03, 2014 at 09:06:37PM +0000, Pham, Calvin wrote:
> I forced the code to ignore the error by commenting out "return 0", phc2sys seemed to work fine; I mean the system clock was able to sync to /dev/ptp0 fine.  Does anyone know why?

This sounds like a driver bug. Can you give the output of the following commands?

     uname -a

     ethtool -T eth0
     testptp -g

Thanks,
Richard