linuxptp-users Mailing List for linuxptp (Page 141)
PTP IEEE 1588 stack for Linux
Brought to you by:
rcochran
You can subscribe to this list here.
2012 |
Jan
|
Feb
(10) |
Mar
(47) |
Apr
|
May
(26) |
Jun
(10) |
Jul
(4) |
Aug
(2) |
Sep
(2) |
Oct
(20) |
Nov
(14) |
Dec
(8) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2013 |
Jan
(6) |
Feb
(18) |
Mar
(27) |
Apr
(57) |
May
(32) |
Jun
(21) |
Jul
(79) |
Aug
(108) |
Sep
(13) |
Oct
(73) |
Nov
(51) |
Dec
(24) |
2014 |
Jan
(24) |
Feb
(41) |
Mar
(39) |
Apr
(5) |
May
(6) |
Jun
(2) |
Jul
(5) |
Aug
(15) |
Sep
(7) |
Oct
(6) |
Nov
|
Dec
(7) |
2015 |
Jan
(27) |
Feb
(18) |
Mar
(37) |
Apr
(8) |
May
(13) |
Jun
(44) |
Jul
(4) |
Aug
(50) |
Sep
(35) |
Oct
(6) |
Nov
(24) |
Dec
(19) |
2016 |
Jan
(30) |
Feb
(30) |
Mar
(23) |
Apr
(4) |
May
(12) |
Jun
(19) |
Jul
(26) |
Aug
(13) |
Sep
|
Oct
(23) |
Nov
(37) |
Dec
(15) |
2017 |
Jan
(33) |
Feb
(19) |
Mar
(20) |
Apr
(43) |
May
(39) |
Jun
(23) |
Jul
(20) |
Aug
(27) |
Sep
(10) |
Oct
(15) |
Nov
|
Dec
(24) |
2018 |
Jan
(3) |
Feb
(10) |
Mar
(34) |
Apr
(34) |
May
(28) |
Jun
(50) |
Jul
(27) |
Aug
(75) |
Sep
(21) |
Oct
(42) |
Nov
(25) |
Dec
(31) |
2019 |
Jan
(39) |
Feb
(28) |
Mar
(19) |
Apr
(7) |
May
(30) |
Jun
(22) |
Jul
(54) |
Aug
(36) |
Sep
(19) |
Oct
(33) |
Nov
(36) |
Dec
(32) |
2020 |
Jan
(29) |
Feb
(38) |
Mar
(29) |
Apr
(30) |
May
(39) |
Jun
(45) |
Jul
(31) |
Aug
(52) |
Sep
(40) |
Oct
(8) |
Nov
(48) |
Dec
(30) |
2021 |
Jan
(35) |
Feb
(32) |
Mar
(23) |
Apr
(55) |
May
(43) |
Jun
(63) |
Jul
(17) |
Aug
(24) |
Sep
(9) |
Oct
(31) |
Nov
(67) |
Dec
(55) |
2022 |
Jan
(31) |
Feb
(48) |
Mar
(76) |
Apr
(18) |
May
(13) |
Jun
(46) |
Jul
(75) |
Aug
(54) |
Sep
(59) |
Oct
(65) |
Nov
(44) |
Dec
(7) |
2023 |
Jan
(38) |
Feb
(32) |
Mar
(35) |
Apr
(23) |
May
(46) |
Jun
(53) |
Jul
(18) |
Aug
(10) |
Sep
(24) |
Oct
(15) |
Nov
(40) |
Dec
(6) |
From: Gabe B. <Gab...@jd...> - 2013-10-29 15:13:40
|
Thanks, I may consider filing a bug if it works out of the box in another distribution. I did try compiling the igb driver, but it gave so many compile errors when I tried to use the CFLAGS_EXTRA=-DIGB_PTP. After fixing a static check for a version greater than the 2.6 kernel redhat supplies in the igb code, I got a ton of compile errors. I decided not to pursue all the missing PTP related constants... (driver compiles fine without defining IGB_PTP). Gabe > -----Original Message----- > From: Vick, Matthew [mailto:mat...@in...] > Sent: Tuesday, October 29, 2013 9:08 AM > To: Ledda William EXT; Gabe Black; Keller, Jacob E > Cc: lin...@li... > Subject: Re: [Linuxptp-users] Which distributions have native ptp > support? > > Gabe, > > To chime in as well, if you continue to have problems I would recommend > filing a Bugzilla with Red Hat. They own the version of igb and ptp4l > included in their kernel and it could be something else in their stack > interfering specifically with your configuration. > > Another option for you to try is the latest version of igb from > SourceForge (5.0.6) and compiling with "CFLAGS_EXTRA=-DIGB_PTP make" to > see if that works for you. > > I'm not sure what all the VM changes (other than obviously introducing > some delay around when the app can run), but I would hope the device > continues to operate correctly. > > Cheers, > Matthew > > Matthew Vick > Linux Development > Networking Division > Intel Corporation > > > On 10/29/13, 1:11 AM, "Ledda William EXT" <Wil...@it...> > wrote: > > >Dear all, > >Have you check the firewall? Is it enabled? The only problem that I > had > >(initially) was related to the firewall. After disabling the firewall > >everything works! > > > >I worked without problem with the version released with RH 6.4 > >(linuxptp-0-0.6.20121114gite6bbbb.el6.x86_64) but I have also work > with > >1.2 and now I'm working with 1.3 without any problem. > >How do you have compiled version 1.3? Do you have disabled the one > step > >option or do you have define HWTSTAMP_TX_ONESTEP_SYNC symbol? Base > >kernel > >2.36.32 haven't HWTSTAMP_TX_ONESTEP_SYNC in linux/net_tstamp.h, so in > >order to compile, you should define this symbol or change the sk.c in > >order to don't check for one step clocks. > > > >My syetem configuration: > > > >$ uname -a > >Linux fc-vitro-tcn.codac.iter.org 2.6.32-358.2.1.el6.x86_64 #1 SMP Wed > >Feb 20 12:17:37 EST 2013 x86_64 x86_64 x86_64 GNU/Linux > > > >$ ethtool -i eth1 > >driver: igb > >version: 4.0.1-k > >firmware-version: 1.61, 0x090f8000 > >bus-info: 0000:10:00.1 > >supports-statistics: yes > >supports-test: yes > >supports-eeprom-access: yes > >supports-register-dump: yes > >supports-priv-flags: no > > > >$ ethtool -T eth1 > >Time stamping parameters for eth1: > >Capabilities: > > hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE) > > hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE) > > hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE) > >PTP Hardware Clock: 1 > >Hardware Transmit Timestamp Modes: > > off (HWTSTAMP_TX_OFF) > > on (HWTSTAMP_TX_ON) > >Hardware Receive Filter Modes: > > none (HWTSTAMP_FILTER_NONE) > > all (HWTSTAMP_FILTER_ALL) > > > > > >-----Original Message----- > >From: Gabe Black [mailto:Gab...@jd...] > >Sent: 29 October 2013 01:18 > >To: Gabe Black; Keller, Jacob E > >Cc: lin...@li... > >Subject: Re: [Linuxptp-users] Which distributions have native ptp > support? > > > >I downloaded ptp4l and compiled and ran it. The behavior is the same, > >except now poll times out. I have increased the timeout and even > >modified the code to see what packet was getting transmitted to verify > >things. > > > >I verified that in wireshark I see the delay req message go out, and > >the delay response as well. > > > >Looking at the code and reading Documentation/networking/timestamping > >it looks like the code is trying to get the transmit timestamp of the > >packet which is expected to be found in the socket error queue. > > > >So this leads me to believe that the timestamp is simply not making it > >in to the MSG_ERRQUEUE... Again, I have the default RH6.4 > >kernel/install and the igb driver seems to have support for it as > shown below: > > > >ethtool -T eth3 > >Time stamping parameters for eth3: > >Capabilities: > > hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE) > > hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE) > > hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE) > >PTP Hardware Clock: 1 > >Hardware Transmit Timestamp Modes: > > off (HWTSTAMP_TX_OFF) > > on (HWTSTAMP_TX_ON) > >Hardware Receive Filter Modes: > > none (HWTSTAMP_FILTER_NONE) > > all (HWTSTAMP_FILTER_ALL) > > > >ethtool -I eth3 > >driver: igb > >version: 4.0.1-k > > > >Since RH6.4 still is on 2.6.32 kernel, I'm guessing they had to do a > >bunch of work to back-port the stuff to get things like "ethtool -T" > to > >work. Probably still buggy... > > > >Anyway, not sure what William did to get it to work... I think I am > >going to just switch to a different distribution that has it supported > >out of the box as well. Apparently on this thread Fedora 19 and > >OpenSuse have it. > > > >Oh, I am running in a virtualized environment using DirectPath I/O > >(a.k.a > >"passthrough") to assign the I350 driver directly to the VM. Maybe > >that matters; but I'm fairly certain that DirectPath presents the > >hardware registers/configuration in all its glory to the VM, thus > >letting the igb-driver operate the device. The software is the same, > >so we should be getting timestamps... > > > >Oh well, on to the next distribution! > > > >Thanks! > >Gabe > > > > > > > >> -----Original Message----- > >> From: Gabe Black [mailto:Gab...@jd...] > >> Sent: Monday, October 28, 2013 5:19 PM > >> To: Keller, Jacob E > >> Cc: lin...@li... > >> Subject: Re: [Linuxptp-users] Which distributions have native ptp > >> support? > >> > >> I am using the version that comes with a fresh install of the RH 6.4 > >> release: > >> > >> rpm -qa | grep ptp > >> linuxptp-0-0.6.20121114gite6bbbb.el6.x86_64 > >> > >> ptp4l doesn't appear to have a version option (in this release) and > >> the readme file in /usr/shar/doc/linuxptp-0/README.org doesn't > either. > >> > >> At any rate, I will get the latest version and try that and report. > >> > >> Thank you for the feedback! > >> > >> > -----Original Message----- > >> > From: Keller, Jacob E [mailto:jac...@in...] > >> > Sent: Monday, October 28, 2013 4:37 PM > >> > To: Gabe Black > >> > Cc: Ledda William EXT; lin...@li... > >> > Subject: Re: [Linuxptp-users] Which distributions have native ptp > >> > support? > >> > > >> > What version of linuxPTP are you using? > >> > > >> > It appears you aren't using the 1.3 version as we moved to a > method > >> > for obtaining the Tx timestamp that uses the poll() call. That > >> > might fix your issue. > >> > > >> > The other option would be to increase the tx_timestamp_timeout > >> > value, but I think moving to the newest Linux PTP should be a fix. > >> > > >> > Regards, > >> > Jake > >> > > >> > On Mon, 2013-10-28 at 21:35 +0000, Gabe Black wrote: > >> > > Nm, it was right. We have two subnets that will route to the > >> > meinberg, and they both work... So that means I still I don't > >> > know what it is... > >> > > > >> > > strace it shows: > >> > > sendto(11, > >> > > > >> > > >> > "\1\2\0,\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\2406\237\377\376\30*\213\0\1 > >> \ > >> > > 0\0"..., 44, 0, {sa_family=AF_INET, sin_port=htons(319), > >> > > sin_addr=inet_addr("224.0.1.129")}, 16) = \ > >> > > 44 > >> > > Followed by a bunch of: > >> > > > >> > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource > >> > temporarily unavailable) > >> > > nanosleep({0, 1000}, NULL) = 0 > >> > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource > >> > temporarily unavailable) > >> > > nanosleep({0, 1000}, NULL) = 0 > >> > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource > >> > temporarily unavailable) > >> > > nanosleep({0, 1000}, NULL) = 0 > >> > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource > >> > > temporarily unavailable) ... > >> > > > >> > > > >> > > > >> > > > -----Original Message----- > >> > > > From: Gabe Black > >> > > > Sent: Monday, October 28, 2013 2:20 PM > >> > > > To: Gabe Black; 'Keller, Jacob E' > >> > > > Cc: 'Ledda William EXT'; 'linuxptp- > us...@li...' > >> > > > Subject: RE: [Linuxptp-users] Which distributions have native > >> > > > ptp support? > >> > > > > >> > > > Oh sheesh.. I had a typo and was on the wrong subnet... > >> > > > > >> > > > It is working now! > >> > > > > >> > > > > -----Original Message----- > >> > > > > From: Gabe Black > >> > > > > Sent: Monday, October 28, 2013 1:18 PM > >> > > > > To: 'Keller, Jacob E' > >> > > > > Cc: Ledda William EXT; lin...@li... > >> > > > > Subject: RE: [Linuxptp-users] Which distributions have > native > >> > > > > ptp support? > >> > > > > > >> > > > > > -----Original Message----- > >> > > > > > From: Keller, Jacob E [mailto:jac...@in...] > You > >> > > > > > shouldn't have to, however, I would suggest disabling EEE > >> > > > > > support, as this has been known to cause issues on the > i350 > >> > > > > > > >> > > > > > ethtool --set-eee device eee off > >> > > > > > > >> > > > > > This should fix your issue, if not please me know. > >> > > > > > >> > > > > Thank you for the reply. > >> > > > > > >> > > > > That option does not appear to be available with the stock > >> > > > > igb driver of RH6.4 > >> > > > > > >> > > > > [root@ network-scripts]# ethtool -i eth3 > >> > > > > driver: igb > >> > > > > version: 4.0.1-k > >> > > > > firmware-version: 0.1470, 0x05fc8000 ... > >> > > > > [root@ network-scripts]# ethtool --show-eee eth3 Cannot get > >> > > > > EEE > >> > > > > settings: Operation not supported > >> > > > > > >> > > > > Is there another way to disable EEE? Or would not having > that > >> > > > > option in ethtool mean it is off? > >> > > > > > >> > > > > Gabe > >> > > > > > >> > > > > > On Mon, 2013-10-28 at 15:29 +0000, Gabe Black wrote: > >> > > > > > > Hi William, > >> > > > > > > > >> > > > > > > I installed redhat 6.4 and have the intel i350 (with igb > >> > > > > > > driver) > >> > > > > and > >> > > > > > am having trouble getting it to work with a meinberg > master. > >> > > > > > > > >> > > > > > > The output I get is: > >> > > > > > > > >> > > > > > > ptp4l[246980.523]: selected /dev/ptp1 as PTP clock > >> > > > > > > ptp4l[246980.525]: port 1: INITIALIZING to LISTENING on > >> > > > INITIALIZE > >> > > > > > > ptp4l[246980.526]: port 0: INITIALIZING to LISTENING on > >> > > > INITIALIZE > >> > > > > > > ptp4l[246980.773]: port 1: new foreign master > >> > > > > > > 00606e.fffe.7c230e- > >> > > > 1 > >> > > > > > > ptp4l[246985.014]: selected best master clock > >> > > > > > > 00606e.fffe.7c230e > >> > > > > > > ptp4l[246985.014]: foreign master not using PTP > timescale > >> > > > > > > ptp4l[246985.014]: running in a temporal vortex > >> > > > > > > ptp4l[246985.014]: port 1: LISTENING to UNCALIBRATED on > >> > > > > > > RS_SLAVE > >> > > > > > > ptp4l[246985.989]: recvmsg tx timestamp failed: Resource > >> > > > > temporarily > >> > > > > > > unavailable > >> > > > > > > ptp4l[246985.989]: port 1: send delay request failed > >> > > > > > > ptp4l[246985.989]: port 1: UNCALIBRATED to FAULTY on > >> > > > > > > FAULT_DETECTED > >> > > > > > > > >> > > > > > > Did you have to do anything differently on the stock > >> > > > > > > RH6.4 > >> > > > install > >> > > > > > > to > >> > > > > > get it to work? > >> > > > > > > > >> > > > > > > Thanks, > >> > > > > > > Gabe > >> > > > > > > > >> > > > > > > > -----Original Message----- > >> > > > > > > > From: Ledda William EXT > [mailto:Wil...@it...] > >> > > > > > > > Sent: Monday, October 21, 2013 1:02 AM > >> > > > > > > > To: Richard Cochran; Gabe Black > >> > > > > > > > Cc: lin...@li... > >> > > > > > > > Subject: RE: [Linuxptp-users] Which distributions have > >> > > > > > > > native ptp support? > >> > > > > > > > > >> > > > > > > > I'm currently using RH 6.4 with Intel i350 (igb > driver) > >> > with > >> > > > > > success > >> > > > > > > > (no need to recompile the kernel). About RH 6.5 I know > >> > > > > > > > that there will be many improvements, more eth driver > >> > > > > > > > supported, and it should include version 1.3 of > >> > > > > > > > linuxptp > >> package. > >> > > > > > > > > >> > > > > > > > William > >> > > > > > > > > >> > > > >> > > >> > >> -------------------------------------------------------------------- > - > >> - > >> - > >> ------- > >> Android is increasing in popularity, but the open development > >> platform that developers love is also attractive to malware > creators. > >> Download this white paper to learn more about secure code signing > >> practices that can help keep Android apps secure. > >> > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg. > >> c > >> l > >> ktrk > >> _______________________________________________ > >> Linuxptp-users mailing list > >> Lin...@li... > >> https://lists.sourceforge.net/lists/listinfo/linuxptp-users > > > >---------------------------------------------------------------------- > - > >--- > >---- > >Android is increasing in popularity, but the open development platform > >that developers love is also attractive to malware creators. Download > >this white paper to learn more about secure code signing practices > that > >can help keep Android apps secure. > >http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.c > l > >ktr > >k > >_______________________________________________ > >Linuxptp-users mailing list > >Lin...@li... > >https://lists.sourceforge.net/lists/listinfo/linuxptp-users > > > >---------------------------------------------------------------------- > - > >--- > >---- > >Android is increasing in popularity, but the open development platform > >that developers love is also attractive to malware creators. Download > >this white paper to learn more about secure code signing practices > that > >can help keep Android apps secure. > >http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.c > l > >ktr > >k > >_______________________________________________ > >Linuxptp-users mailing list > >Lin...@li... > >https://lists.sourceforge.net/lists/listinfo/linuxptp-users |
From: Vick, M. <mat...@in...> - 2013-10-29 15:08:00
|
Gabe, To chime in as well, if you continue to have problems I would recommend filing a Bugzilla with Red Hat. They own the version of igb and ptp4l included in their kernel and it could be something else in their stack interfering specifically with your configuration. Another option for you to try is the latest version of igb from SourceForge (5.0.6) and compiling with "CFLAGS_EXTRA=-DIGB_PTP make" to see if that works for you. I'm not sure what all the VM changes (other than obviously introducing some delay around when the app can run), but I would hope the device continues to operate correctly. Cheers, Matthew Matthew Vick Linux Development Networking Division Intel Corporation On 10/29/13, 1:11 AM, "Ledda William EXT" <Wil...@it...> wrote: >Dear all, >Have you check the firewall? Is it enabled? The only problem that I had >(initially) was related to the firewall. After disabling the firewall >everything works! > >I worked without problem with the version released with RH 6.4 >(linuxptp-0-0.6.20121114gite6bbbb.el6.x86_64) but I have also work with >1.2 and now I'm working with 1.3 without any problem. >How do you have compiled version 1.3? Do you have disabled the one step >option or do you have define HWTSTAMP_TX_ONESTEP_SYNC symbol? Base kernel >2.36.32 haven't HWTSTAMP_TX_ONESTEP_SYNC in linux/net_tstamp.h, so in >order to compile, you should define this symbol or change the sk.c in >order to don't check for one step clocks. > >My syetem configuration: > >$ uname -a >Linux fc-vitro-tcn.codac.iter.org 2.6.32-358.2.1.el6.x86_64 #1 SMP Wed >Feb 20 12:17:37 EST 2013 x86_64 x86_64 x86_64 GNU/Linux > >$ ethtool -i eth1 >driver: igb >version: 4.0.1-k >firmware-version: 1.61, 0x090f8000 >bus-info: 0000:10:00.1 >supports-statistics: yes >supports-test: yes >supports-eeprom-access: yes >supports-register-dump: yes >supports-priv-flags: no > >$ ethtool -T eth1 >Time stamping parameters for eth1: >Capabilities: > hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE) > hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE) > hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE) >PTP Hardware Clock: 1 >Hardware Transmit Timestamp Modes: > off (HWTSTAMP_TX_OFF) > on (HWTSTAMP_TX_ON) >Hardware Receive Filter Modes: > none (HWTSTAMP_FILTER_NONE) > all (HWTSTAMP_FILTER_ALL) > > >-----Original Message----- >From: Gabe Black [mailto:Gab...@jd...] >Sent: 29 October 2013 01:18 >To: Gabe Black; Keller, Jacob E >Cc: lin...@li... >Subject: Re: [Linuxptp-users] Which distributions have native ptp support? > >I downloaded ptp4l and compiled and ran it. The behavior is the same, >except now poll times out. I have increased the timeout and even >modified the code to see what packet was getting transmitted to verify >things. > >I verified that in wireshark I see the delay req message go out, and the >delay response as well. > >Looking at the code and reading Documentation/networking/timestamping it >looks like the code is trying to get the transmit timestamp of the packet >which is expected to be found in the socket error queue. > >So this leads me to believe that the timestamp is simply not making it in >to the MSG_ERRQUEUE... Again, I have the default RH6.4 kernel/install >and the igb driver seems to have support for it as shown below: > >ethtool -T eth3 >Time stamping parameters for eth3: >Capabilities: > hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE) > hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE) > hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE) >PTP Hardware Clock: 1 >Hardware Transmit Timestamp Modes: > off (HWTSTAMP_TX_OFF) > on (HWTSTAMP_TX_ON) >Hardware Receive Filter Modes: > none (HWTSTAMP_FILTER_NONE) > all (HWTSTAMP_FILTER_ALL) > >ethtool -I eth3 >driver: igb >version: 4.0.1-k > >Since RH6.4 still is on 2.6.32 kernel, I'm guessing they had to do a >bunch of work to back-port the stuff to get things like "ethtool -T" to >work. Probably still buggy... > >Anyway, not sure what William did to get it to work... I think I am >going to just switch to a different distribution that has it supported >out of the box as well. Apparently on this thread Fedora 19 and OpenSuse >have it. > >Oh, I am running in a virtualized environment using DirectPath I/O (a.k.a >"passthrough") to assign the I350 driver directly to the VM. Maybe that >matters; but I'm fairly certain that DirectPath presents the hardware >registers/configuration in all its glory to the VM, thus letting the >igb-driver operate the device. The software is the same, so we should be >getting timestamps... > >Oh well, on to the next distribution! > >Thanks! >Gabe > > > >> -----Original Message----- >> From: Gabe Black [mailto:Gab...@jd...] >> Sent: Monday, October 28, 2013 5:19 PM >> To: Keller, Jacob E >> Cc: lin...@li... >> Subject: Re: [Linuxptp-users] Which distributions have native ptp >> support? >> >> I am using the version that comes with a fresh install of the RH 6.4 >> release: >> >> rpm -qa | grep ptp >> linuxptp-0-0.6.20121114gite6bbbb.el6.x86_64 >> >> ptp4l doesn't appear to have a version option (in this release) and >> the readme file in /usr/shar/doc/linuxptp-0/README.org doesn't either. >> >> At any rate, I will get the latest version and try that and report. >> >> Thank you for the feedback! >> >> > -----Original Message----- >> > From: Keller, Jacob E [mailto:jac...@in...] >> > Sent: Monday, October 28, 2013 4:37 PM >> > To: Gabe Black >> > Cc: Ledda William EXT; lin...@li... >> > Subject: Re: [Linuxptp-users] Which distributions have native ptp >> > support? >> > >> > What version of linuxPTP are you using? >> > >> > It appears you aren't using the 1.3 version as we moved to a method >> > for obtaining the Tx timestamp that uses the poll() call. That might >> > fix your issue. >> > >> > The other option would be to increase the tx_timestamp_timeout >> > value, but I think moving to the newest Linux PTP should be a fix. >> > >> > Regards, >> > Jake >> > >> > On Mon, 2013-10-28 at 21:35 +0000, Gabe Black wrote: >> > > Nm, it was right. We have two subnets that will route to the >> > meinberg, and they both work... So that means I still I don't know >> > what it is... >> > > >> > > strace it shows: >> > > sendto(11, >> > > >> > >> "\1\2\0,\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\2406\237\377\376\30*\213\0\1\ >> > > 0\0"..., 44, 0, {sa_family=AF_INET, sin_port=htons(319), >> > > sin_addr=inet_addr("224.0.1.129")}, 16) = \ >> > > 44 >> > > Followed by a bunch of: >> > > >> > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource >> > temporarily unavailable) >> > > nanosleep({0, 1000}, NULL) = 0 >> > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource >> > temporarily unavailable) >> > > nanosleep({0, 1000}, NULL) = 0 >> > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource >> > temporarily unavailable) >> > > nanosleep({0, 1000}, NULL) = 0 >> > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource >> > > temporarily unavailable) ... >> > > >> > > >> > > >> > > > -----Original Message----- >> > > > From: Gabe Black >> > > > Sent: Monday, October 28, 2013 2:20 PM >> > > > To: Gabe Black; 'Keller, Jacob E' >> > > > Cc: 'Ledda William EXT'; 'lin...@li...' >> > > > Subject: RE: [Linuxptp-users] Which distributions have native >> > > > ptp support? >> > > > >> > > > Oh sheesh.. I had a typo and was on the wrong subnet... >> > > > >> > > > It is working now! >> > > > >> > > > > -----Original Message----- >> > > > > From: Gabe Black >> > > > > Sent: Monday, October 28, 2013 1:18 PM >> > > > > To: 'Keller, Jacob E' >> > > > > Cc: Ledda William EXT; lin...@li... >> > > > > Subject: RE: [Linuxptp-users] Which distributions have native >> > > > > ptp support? >> > > > > >> > > > > > -----Original Message----- >> > > > > > From: Keller, Jacob E [mailto:jac...@in...] You >> > > > > > shouldn't have to, however, I would suggest disabling EEE >> > > > > > support, as this has been known to cause issues on the i350 >> > > > > > >> > > > > > ethtool --set-eee device eee off >> > > > > > >> > > > > > This should fix your issue, if not please me know. >> > > > > >> > > > > Thank you for the reply. >> > > > > >> > > > > That option does not appear to be available with the stock igb >> > > > > driver of RH6.4 >> > > > > >> > > > > [root@ network-scripts]# ethtool -i eth3 >> > > > > driver: igb >> > > > > version: 4.0.1-k >> > > > > firmware-version: 0.1470, 0x05fc8000 ... >> > > > > [root@ network-scripts]# ethtool --show-eee eth3 Cannot get >> > > > > EEE >> > > > > settings: Operation not supported >> > > > > >> > > > > Is there another way to disable EEE? Or would not having that >> > > > > option in ethtool mean it is off? >> > > > > >> > > > > Gabe >> > > > > >> > > > > > On Mon, 2013-10-28 at 15:29 +0000, Gabe Black wrote: >> > > > > > > Hi William, >> > > > > > > >> > > > > > > I installed redhat 6.4 and have the intel i350 (with igb >> > > > > > > driver) >> > > > > and >> > > > > > am having trouble getting it to work with a meinberg master. >> > > > > > > >> > > > > > > The output I get is: >> > > > > > > >> > > > > > > ptp4l[246980.523]: selected /dev/ptp1 as PTP clock >> > > > > > > ptp4l[246980.525]: port 1: INITIALIZING to LISTENING on >> > > > INITIALIZE >> > > > > > > ptp4l[246980.526]: port 0: INITIALIZING to LISTENING on >> > > > INITIALIZE >> > > > > > > ptp4l[246980.773]: port 1: new foreign master >> > > > > > > 00606e.fffe.7c230e- >> > > > 1 >> > > > > > > ptp4l[246985.014]: selected best master clock >> > > > > > > 00606e.fffe.7c230e >> > > > > > > ptp4l[246985.014]: foreign master not using PTP timescale >> > > > > > > ptp4l[246985.014]: running in a temporal vortex >> > > > > > > ptp4l[246985.014]: port 1: LISTENING to UNCALIBRATED on >> > > > > > > RS_SLAVE >> > > > > > > ptp4l[246985.989]: recvmsg tx timestamp failed: Resource >> > > > > temporarily >> > > > > > > unavailable >> > > > > > > ptp4l[246985.989]: port 1: send delay request failed >> > > > > > > ptp4l[246985.989]: port 1: UNCALIBRATED to FAULTY on >> > > > > > > FAULT_DETECTED >> > > > > > > >> > > > > > > Did you have to do anything differently on the stock RH6.4 >> > > > install >> > > > > > > to >> > > > > > get it to work? >> > > > > > > >> > > > > > > Thanks, >> > > > > > > Gabe >> > > > > > > >> > > > > > > > -----Original Message----- >> > > > > > > > From: Ledda William EXT [mailto:Wil...@it...] >> > > > > > > > Sent: Monday, October 21, 2013 1:02 AM >> > > > > > > > To: Richard Cochran; Gabe Black >> > > > > > > > Cc: lin...@li... >> > > > > > > > Subject: RE: [Linuxptp-users] Which distributions have >> > > > > > > > native ptp support? >> > > > > > > > >> > > > > > > > I'm currently using RH 6.4 with Intel i350 (igb driver) >> > with >> > > > > > success >> > > > > > > > (no need to recompile the kernel). About RH 6.5 I know >> > > > > > > > that there will be many improvements, more eth driver >> > > > > > > > supported, and it should include version 1.3 of linuxptp >> package. >> > > > > > > > >> > > > > > > > William >> > > > > > > > >> > > >> > >> >> ---------------------------------------------------------------------- >> - >> ------- >> Android is increasing in popularity, but the open development platform >> that developers love is also attractive to malware creators. Download >> this white paper to learn more about secure code signing practices >> that can help keep Android apps secure. >> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.c >> l >> ktrk >> _______________________________________________ >> Linuxptp-users mailing list >> Lin...@li... >> https://lists.sourceforge.net/lists/listinfo/linuxptp-users > >-------------------------------------------------------------------------- >---- >Android is increasing in popularity, but the open development platform >that developers love is also attractive to malware creators. Download >this white paper to learn more about secure code signing practices that >can help keep Android apps secure. >http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktr >k >_______________________________________________ >Linuxptp-users mailing list >Lin...@li... >https://lists.sourceforge.net/lists/listinfo/linuxptp-users > >-------------------------------------------------------------------------- >---- >Android is increasing in popularity, but the open development platform >that >developers love is also attractive to malware creators. Download this >white >paper to learn more about secure code signing practices that can help keep >Android apps secure. >http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktr >k >_______________________________________________ >Linuxptp-users mailing list >Lin...@li... >https://lists.sourceforge.net/lists/listinfo/linuxptp-users |
From: Ledda W. E. <Wil...@it...> - 2013-10-29 08:11:51
|
Dear all, Have you check the firewall? Is it enabled? The only problem that I had (initially) was related to the firewall. After disabling the firewall everything works! I worked without problem with the version released with RH 6.4 (linuxptp-0-0.6.20121114gite6bbbb.el6.x86_64) but I have also work with 1.2 and now I'm working with 1.3 without any problem. How do you have compiled version 1.3? Do you have disabled the one step option or do you have define HWTSTAMP_TX_ONESTEP_SYNC symbol? Base kernel 2.36.32 haven't HWTSTAMP_TX_ONESTEP_SYNC in linux/net_tstamp.h, so in order to compile, you should define this symbol or change the sk.c in order to don't check for one step clocks. My syetem configuration: $ uname -a Linux fc-vitro-tcn.codac.iter.org 2.6.32-358.2.1.el6.x86_64 #1 SMP Wed Feb 20 12:17:37 EST 2013 x86_64 x86_64 x86_64 GNU/Linux $ ethtool -i eth1 driver: igb version: 4.0.1-k firmware-version: 1.61, 0x090f8000 bus-info: 0000:10:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no $ ethtool -T eth1 Time stamping parameters for eth1: Capabilities: hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE) hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE) hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE) PTP Hardware Clock: 1 Hardware Transmit Timestamp Modes: off (HWTSTAMP_TX_OFF) on (HWTSTAMP_TX_ON) Hardware Receive Filter Modes: none (HWTSTAMP_FILTER_NONE) all (HWTSTAMP_FILTER_ALL) -----Original Message----- From: Gabe Black [mailto:Gab...@jd...] Sent: 29 October 2013 01:18 To: Gabe Black; Keller, Jacob E Cc: lin...@li... Subject: Re: [Linuxptp-users] Which distributions have native ptp support? I downloaded ptp4l and compiled and ran it. The behavior is the same, except now poll times out. I have increased the timeout and even modified the code to see what packet was getting transmitted to verify things. I verified that in wireshark I see the delay req message go out, and the delay response as well. Looking at the code and reading Documentation/networking/timestamping it looks like the code is trying to get the transmit timestamp of the packet which is expected to be found in the socket error queue. So this leads me to believe that the timestamp is simply not making it in to the MSG_ERRQUEUE... Again, I have the default RH6.4 kernel/install and the igb driver seems to have support for it as shown below: ethtool -T eth3 Time stamping parameters for eth3: Capabilities: hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE) hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE) hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE) PTP Hardware Clock: 1 Hardware Transmit Timestamp Modes: off (HWTSTAMP_TX_OFF) on (HWTSTAMP_TX_ON) Hardware Receive Filter Modes: none (HWTSTAMP_FILTER_NONE) all (HWTSTAMP_FILTER_ALL) ethtool -I eth3 driver: igb version: 4.0.1-k Since RH6.4 still is on 2.6.32 kernel, I'm guessing they had to do a bunch of work to back-port the stuff to get things like "ethtool -T" to work. Probably still buggy... Anyway, not sure what William did to get it to work... I think I am going to just switch to a different distribution that has it supported out of the box as well. Apparently on this thread Fedora 19 and OpenSuse have it. Oh, I am running in a virtualized environment using DirectPath I/O (a.k.a "passthrough") to assign the I350 driver directly to the VM. Maybe that matters; but I'm fairly certain that DirectPath presents the hardware registers/configuration in all its glory to the VM, thus letting the igb-driver operate the device. The software is the same, so we should be getting timestamps... Oh well, on to the next distribution! Thanks! Gabe > -----Original Message----- > From: Gabe Black [mailto:Gab...@jd...] > Sent: Monday, October 28, 2013 5:19 PM > To: Keller, Jacob E > Cc: lin...@li... > Subject: Re: [Linuxptp-users] Which distributions have native ptp > support? > > I am using the version that comes with a fresh install of the RH 6.4 > release: > > rpm -qa | grep ptp > linuxptp-0-0.6.20121114gite6bbbb.el6.x86_64 > > ptp4l doesn't appear to have a version option (in this release) and > the readme file in /usr/shar/doc/linuxptp-0/README.org doesn't either. > > At any rate, I will get the latest version and try that and report. > > Thank you for the feedback! > > > -----Original Message----- > > From: Keller, Jacob E [mailto:jac...@in...] > > Sent: Monday, October 28, 2013 4:37 PM > > To: Gabe Black > > Cc: Ledda William EXT; lin...@li... > > Subject: Re: [Linuxptp-users] Which distributions have native ptp > > support? > > > > What version of linuxPTP are you using? > > > > It appears you aren't using the 1.3 version as we moved to a method > > for obtaining the Tx timestamp that uses the poll() call. That might > > fix your issue. > > > > The other option would be to increase the tx_timestamp_timeout > > value, but I think moving to the newest Linux PTP should be a fix. > > > > Regards, > > Jake > > > > On Mon, 2013-10-28 at 21:35 +0000, Gabe Black wrote: > > > Nm, it was right. We have two subnets that will route to the > > meinberg, and they both work... So that means I still I don't know > > what it is... > > > > > > strace it shows: > > > sendto(11, > > > > > > "\1\2\0,\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\2406\237\377\376\30*\213\0\1\ > > > 0\0"..., 44, 0, {sa_family=AF_INET, sin_port=htons(319), > > > sin_addr=inet_addr("224.0.1.129")}, 16) = \ > > > 44 > > > Followed by a bunch of: > > > > > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource > > temporarily unavailable) > > > nanosleep({0, 1000}, NULL) = 0 > > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource > > temporarily unavailable) > > > nanosleep({0, 1000}, NULL) = 0 > > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource > > temporarily unavailable) > > > nanosleep({0, 1000}, NULL) = 0 > > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource > > > temporarily unavailable) ... > > > > > > > > > > > > > -----Original Message----- > > > > From: Gabe Black > > > > Sent: Monday, October 28, 2013 2:20 PM > > > > To: Gabe Black; 'Keller, Jacob E' > > > > Cc: 'Ledda William EXT'; 'lin...@li...' > > > > Subject: RE: [Linuxptp-users] Which distributions have native > > > > ptp support? > > > > > > > > Oh sheesh.. I had a typo and was on the wrong subnet... > > > > > > > > It is working now! > > > > > > > > > -----Original Message----- > > > > > From: Gabe Black > > > > > Sent: Monday, October 28, 2013 1:18 PM > > > > > To: 'Keller, Jacob E' > > > > > Cc: Ledda William EXT; lin...@li... > > > > > Subject: RE: [Linuxptp-users] Which distributions have native > > > > > ptp support? > > > > > > > > > > > -----Original Message----- > > > > > > From: Keller, Jacob E [mailto:jac...@in...] You > > > > > > shouldn't have to, however, I would suggest disabling EEE > > > > > > support, as this has been known to cause issues on the i350 > > > > > > > > > > > > ethtool --set-eee device eee off > > > > > > > > > > > > This should fix your issue, if not please me know. > > > > > > > > > > Thank you for the reply. > > > > > > > > > > That option does not appear to be available with the stock igb > > > > > driver of RH6.4 > > > > > > > > > > [root@ network-scripts]# ethtool -i eth3 > > > > > driver: igb > > > > > version: 4.0.1-k > > > > > firmware-version: 0.1470, 0x05fc8000 ... > > > > > [root@ network-scripts]# ethtool --show-eee eth3 Cannot get > > > > > EEE > > > > > settings: Operation not supported > > > > > > > > > > Is there another way to disable EEE? Or would not having that > > > > > option in ethtool mean it is off? > > > > > > > > > > Gabe > > > > > > > > > > > On Mon, 2013-10-28 at 15:29 +0000, Gabe Black wrote: > > > > > > > Hi William, > > > > > > > > > > > > > > I installed redhat 6.4 and have the intel i350 (with igb > > > > > > > driver) > > > > > and > > > > > > am having trouble getting it to work with a meinberg master. > > > > > > > > > > > > > > The output I get is: > > > > > > > > > > > > > > ptp4l[246980.523]: selected /dev/ptp1 as PTP clock > > > > > > > ptp4l[246980.525]: port 1: INITIALIZING to LISTENING on > > > > INITIALIZE > > > > > > > ptp4l[246980.526]: port 0: INITIALIZING to LISTENING on > > > > INITIALIZE > > > > > > > ptp4l[246980.773]: port 1: new foreign master > > > > > > > 00606e.fffe.7c230e- > > > > 1 > > > > > > > ptp4l[246985.014]: selected best master clock > > > > > > > 00606e.fffe.7c230e > > > > > > > ptp4l[246985.014]: foreign master not using PTP timescale > > > > > > > ptp4l[246985.014]: running in a temporal vortex > > > > > > > ptp4l[246985.014]: port 1: LISTENING to UNCALIBRATED on > > > > > > > RS_SLAVE > > > > > > > ptp4l[246985.989]: recvmsg tx timestamp failed: Resource > > > > > temporarily > > > > > > > unavailable > > > > > > > ptp4l[246985.989]: port 1: send delay request failed > > > > > > > ptp4l[246985.989]: port 1: UNCALIBRATED to FAULTY on > > > > > > > FAULT_DETECTED > > > > > > > > > > > > > > Did you have to do anything differently on the stock RH6.4 > > > > install > > > > > > > to > > > > > > get it to work? > > > > > > > > > > > > > > Thanks, > > > > > > > Gabe > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: Ledda William EXT [mailto:Wil...@it...] > > > > > > > > Sent: Monday, October 21, 2013 1:02 AM > > > > > > > > To: Richard Cochran; Gabe Black > > > > > > > > Cc: lin...@li... > > > > > > > > Subject: RE: [Linuxptp-users] Which distributions have > > > > > > > > native ptp support? > > > > > > > > > > > > > > > > I'm currently using RH 6.4 with Intel i350 (igb driver) > > with > > > > > > success > > > > > > > > (no need to recompile the kernel). About RH 6.5 I know > > > > > > > > that there will be many improvements, more eth driver > > > > > > > > supported, and it should include version 1.3 of linuxptp > package. > > > > > > > > > > > > > > > > William > > > > > > > > > > > > > > > ---------------------------------------------------------------------- > - > ------- > Android is increasing in popularity, but the open development platform > that developers love is also attractive to malware creators. Download > this white paper to learn more about secure code signing practices > that can help keep Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.c > l > ktrk > _______________________________________________ > Linuxptp-users mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxptp-users ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Linuxptp-users mailing list Lin...@li... https://lists.sourceforge.net/lists/listinfo/linuxptp-users |
From: Gabe B. <Gab...@jd...> - 2013-10-29 00:18:37
|
I downloaded ptp4l and compiled and ran it. The behavior is the same, except now poll times out. I have increased the timeout and even modified the code to see what packet was getting transmitted to verify things. I verified that in wireshark I see the delay req message go out, and the delay response as well. Looking at the code and reading Documentation/networking/timestamping it looks like the code is trying to get the transmit timestamp of the packet which is expected to be found in the socket error queue. So this leads me to believe that the timestamp is simply not making it in to the MSG_ERRQUEUE... Again, I have the default RH6.4 kernel/install and the igb driver seems to have support for it as shown below: ethtool -T eth3 Time stamping parameters for eth3: Capabilities: hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE) hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE) hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE) PTP Hardware Clock: 1 Hardware Transmit Timestamp Modes: off (HWTSTAMP_TX_OFF) on (HWTSTAMP_TX_ON) Hardware Receive Filter Modes: none (HWTSTAMP_FILTER_NONE) all (HWTSTAMP_FILTER_ALL) ethtool -I eth3 driver: igb version: 4.0.1-k Since RH6.4 still is on 2.6.32 kernel, I'm guessing they had to do a bunch of work to back-port the stuff to get things like "ethtool -T" to work. Probably still buggy... Anyway, not sure what William did to get it to work... I think I am going to just switch to a different distribution that has it supported out of the box as well. Apparently on this thread Fedora 19 and OpenSuse have it. Oh, I am running in a virtualized environment using DirectPath I/O (a.k.a "passthrough") to assign the I350 driver directly to the VM. Maybe that matters; but I'm fairly certain that DirectPath presents the hardware registers/configuration in all its glory to the VM, thus letting the igb-driver operate the device. The software is the same, so we should be getting timestamps... Oh well, on to the next distribution! Thanks! Gabe > -----Original Message----- > From: Gabe Black [mailto:Gab...@jd...] > Sent: Monday, October 28, 2013 5:19 PM > To: Keller, Jacob E > Cc: lin...@li... > Subject: Re: [Linuxptp-users] Which distributions have native ptp > support? > > I am using the version that comes with a fresh install of the RH 6.4 > release: > > rpm -qa | grep ptp > linuxptp-0-0.6.20121114gite6bbbb.el6.x86_64 > > ptp4l doesn't appear to have a version option (in this release) and the > readme file in /usr/shar/doc/linuxptp-0/README.org doesn't either. > > At any rate, I will get the latest version and try that and report. > > Thank you for the feedback! > > > -----Original Message----- > > From: Keller, Jacob E [mailto:jac...@in...] > > Sent: Monday, October 28, 2013 4:37 PM > > To: Gabe Black > > Cc: Ledda William EXT; lin...@li... > > Subject: Re: [Linuxptp-users] Which distributions have native ptp > > support? > > > > What version of linuxPTP are you using? > > > > It appears you aren't using the 1.3 version as we moved to a method > > for obtaining the Tx timestamp that uses the poll() call. That might > > fix your issue. > > > > The other option would be to increase the tx_timestamp_timeout value, > > but I think moving to the newest Linux PTP should be a fix. > > > > Regards, > > Jake > > > > On Mon, 2013-10-28 at 21:35 +0000, Gabe Black wrote: > > > Nm, it was right. We have two subnets that will route to the > > meinberg, and they both work... So that means I still I don't know > > what it is... > > > > > > strace it shows: > > > sendto(11, > > > > > > "\1\2\0,\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\2406\237\377\376\30*\213\0\1\ > > > 0\0"..., 44, 0, {sa_family=AF_INET, sin_port=htons(319), > > > sin_addr=inet_addr("224.0.1.129")}, 16) = \ > > > 44 > > > Followed by a bunch of: > > > > > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource > > temporarily unavailable) > > > nanosleep({0, 1000}, NULL) = 0 > > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource > > temporarily unavailable) > > > nanosleep({0, 1000}, NULL) = 0 > > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource > > temporarily unavailable) > > > nanosleep({0, 1000}, NULL) = 0 > > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource > > > temporarily unavailable) ... > > > > > > > > > > > > > -----Original Message----- > > > > From: Gabe Black > > > > Sent: Monday, October 28, 2013 2:20 PM > > > > To: Gabe Black; 'Keller, Jacob E' > > > > Cc: 'Ledda William EXT'; 'lin...@li...' > > > > Subject: RE: [Linuxptp-users] Which distributions have native ptp > > > > support? > > > > > > > > Oh sheesh.. I had a typo and was on the wrong subnet... > > > > > > > > It is working now! > > > > > > > > > -----Original Message----- > > > > > From: Gabe Black > > > > > Sent: Monday, October 28, 2013 1:18 PM > > > > > To: 'Keller, Jacob E' > > > > > Cc: Ledda William EXT; lin...@li... > > > > > Subject: RE: [Linuxptp-users] Which distributions have native > > > > > ptp support? > > > > > > > > > > > -----Original Message----- > > > > > > From: Keller, Jacob E [mailto:jac...@in...] You > > > > > > shouldn't have to, however, I would suggest disabling EEE > > > > > > support, as this has been known to cause issues on the i350 > > > > > > > > > > > > ethtool --set-eee device eee off > > > > > > > > > > > > This should fix your issue, if not please me know. > > > > > > > > > > Thank you for the reply. > > > > > > > > > > That option does not appear to be available with the stock igb > > > > > driver of RH6.4 > > > > > > > > > > [root@ network-scripts]# ethtool -i eth3 > > > > > driver: igb > > > > > version: 4.0.1-k > > > > > firmware-version: 0.1470, 0x05fc8000 ... > > > > > [root@ network-scripts]# ethtool --show-eee eth3 Cannot get EEE > > > > > settings: Operation not supported > > > > > > > > > > Is there another way to disable EEE? Or would not having that > > > > > option in ethtool mean it is off? > > > > > > > > > > Gabe > > > > > > > > > > > On Mon, 2013-10-28 at 15:29 +0000, Gabe Black wrote: > > > > > > > Hi William, > > > > > > > > > > > > > > I installed redhat 6.4 and have the intel i350 (with igb > > > > > > > driver) > > > > > and > > > > > > am having trouble getting it to work with a meinberg master. > > > > > > > > > > > > > > The output I get is: > > > > > > > > > > > > > > ptp4l[246980.523]: selected /dev/ptp1 as PTP clock > > > > > > > ptp4l[246980.525]: port 1: INITIALIZING to LISTENING on > > > > INITIALIZE > > > > > > > ptp4l[246980.526]: port 0: INITIALIZING to LISTENING on > > > > INITIALIZE > > > > > > > ptp4l[246980.773]: port 1: new foreign master > > > > > > > 00606e.fffe.7c230e- > > > > 1 > > > > > > > ptp4l[246985.014]: selected best master clock > > > > > > > 00606e.fffe.7c230e > > > > > > > ptp4l[246985.014]: foreign master not using PTP timescale > > > > > > > ptp4l[246985.014]: running in a temporal vortex > > > > > > > ptp4l[246985.014]: port 1: LISTENING to UNCALIBRATED on > > > > > > > RS_SLAVE > > > > > > > ptp4l[246985.989]: recvmsg tx timestamp failed: Resource > > > > > temporarily > > > > > > > unavailable > > > > > > > ptp4l[246985.989]: port 1: send delay request failed > > > > > > > ptp4l[246985.989]: port 1: UNCALIBRATED to FAULTY on > > > > > > > FAULT_DETECTED > > > > > > > > > > > > > > Did you have to do anything differently on the stock RH6.4 > > > > install > > > > > > > to > > > > > > get it to work? > > > > > > > > > > > > > > Thanks, > > > > > > > Gabe > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: Ledda William EXT [mailto:Wil...@it...] > > > > > > > > Sent: Monday, October 21, 2013 1:02 AM > > > > > > > > To: Richard Cochran; Gabe Black > > > > > > > > Cc: lin...@li... > > > > > > > > Subject: RE: [Linuxptp-users] Which distributions have > > > > > > > > native ptp support? > > > > > > > > > > > > > > > > I'm currently using RH 6.4 with Intel i350 (igb driver) > > with > > > > > > success > > > > > > > > (no need to recompile the kernel). About RH 6.5 I know > > > > > > > > that there will be many improvements, more eth driver > > > > > > > > supported, and it should include version 1.3 of linuxptp > package. > > > > > > > > > > > > > > > > William > > > > > > > > > > > > > > > ----------------------------------------------------------------------- > ------- > Android is increasing in popularity, but the open development platform > that developers love is also attractive to malware creators. Download > this white paper to learn more about secure code signing practices that > can help keep Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.cl > ktrk > _______________________________________________ > Linuxptp-users mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxptp-users |
From: Gabe B. <Gab...@jd...> - 2013-10-28 23:18:58
|
I am using the version that comes with a fresh install of the RH 6.4 release: rpm -qa | grep ptp linuxptp-0-0.6.20121114gite6bbbb.el6.x86_64 ptp4l doesn't appear to have a version option (in this release) and the readme file in /usr/shar/doc/linuxptp-0/README.org doesn't either. At any rate, I will get the latest version and try that and report. Thank you for the feedback! > -----Original Message----- > From: Keller, Jacob E [mailto:jac...@in...] > Sent: Monday, October 28, 2013 4:37 PM > To: Gabe Black > Cc: Ledda William EXT; lin...@li... > Subject: Re: [Linuxptp-users] Which distributions have native ptp > support? > > What version of linuxPTP are you using? > > It appears you aren't using the 1.3 version as we moved to a method for > obtaining the Tx timestamp that uses the poll() call. That might fix > your issue. > > The other option would be to increase the tx_timestamp_timeout value, > but I think moving to the newest Linux PTP should be a fix. > > Regards, > Jake > > On Mon, 2013-10-28 at 21:35 +0000, Gabe Black wrote: > > Nm, it was right. We have two subnets that will route to the > meinberg, and they both work... So that means I still I don't know > what it is... > > > > strace it shows: > > sendto(11, > > > "\1\2\0,\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\2406\237\377\376\30*\213\0\1\ > > 0\0"..., 44, 0, {sa_family=AF_INET, sin_port=htons(319), > > sin_addr=inet_addr("224.0.1.129")}, 16) = \ > > 44 > > Followed by a bunch of: > > > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource > temporarily unavailable) > > nanosleep({0, 1000}, NULL) = 0 > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource > temporarily unavailable) > > nanosleep({0, 1000}, NULL) = 0 > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource > temporarily unavailable) > > nanosleep({0, 1000}, NULL) = 0 > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource > > temporarily unavailable) ... > > > > > > > > > -----Original Message----- > > > From: Gabe Black > > > Sent: Monday, October 28, 2013 2:20 PM > > > To: Gabe Black; 'Keller, Jacob E' > > > Cc: 'Ledda William EXT'; 'lin...@li...' > > > Subject: RE: [Linuxptp-users] Which distributions have native ptp > > > support? > > > > > > Oh sheesh.. I had a typo and was on the wrong subnet... > > > > > > It is working now! > > > > > > > -----Original Message----- > > > > From: Gabe Black > > > > Sent: Monday, October 28, 2013 1:18 PM > > > > To: 'Keller, Jacob E' > > > > Cc: Ledda William EXT; lin...@li... > > > > Subject: RE: [Linuxptp-users] Which distributions have native ptp > > > > support? > > > > > > > > > -----Original Message----- > > > > > From: Keller, Jacob E [mailto:jac...@in...] You > > > > > shouldn't have to, however, I would suggest disabling EEE > > > > > support, as this has been known to cause issues on the i350 > > > > > > > > > > ethtool --set-eee device eee off > > > > > > > > > > This should fix your issue, if not please me know. > > > > > > > > Thank you for the reply. > > > > > > > > That option does not appear to be available with the stock igb > > > > driver of RH6.4 > > > > > > > > [root@ network-scripts]# ethtool -i eth3 > > > > driver: igb > > > > version: 4.0.1-k > > > > firmware-version: 0.1470, 0x05fc8000 ... > > > > [root@ network-scripts]# ethtool --show-eee eth3 Cannot get EEE > > > > settings: Operation not supported > > > > > > > > Is there another way to disable EEE? Or would not having that > > > > option in ethtool mean it is off? > > > > > > > > Gabe > > > > > > > > > On Mon, 2013-10-28 at 15:29 +0000, Gabe Black wrote: > > > > > > Hi William, > > > > > > > > > > > > I installed redhat 6.4 and have the intel i350 (with igb > > > > > > driver) > > > > and > > > > > am having trouble getting it to work with a meinberg master. > > > > > > > > > > > > The output I get is: > > > > > > > > > > > > ptp4l[246980.523]: selected /dev/ptp1 as PTP clock > > > > > > ptp4l[246980.525]: port 1: INITIALIZING to LISTENING on > > > INITIALIZE > > > > > > ptp4l[246980.526]: port 0: INITIALIZING to LISTENING on > > > INITIALIZE > > > > > > ptp4l[246980.773]: port 1: new foreign master > > > > > > 00606e.fffe.7c230e- > > > 1 > > > > > > ptp4l[246985.014]: selected best master clock > > > > > > 00606e.fffe.7c230e > > > > > > ptp4l[246985.014]: foreign master not using PTP timescale > > > > > > ptp4l[246985.014]: running in a temporal vortex > > > > > > ptp4l[246985.014]: port 1: LISTENING to UNCALIBRATED on > > > > > > RS_SLAVE > > > > > > ptp4l[246985.989]: recvmsg tx timestamp failed: Resource > > > > temporarily > > > > > > unavailable > > > > > > ptp4l[246985.989]: port 1: send delay request failed > > > > > > ptp4l[246985.989]: port 1: UNCALIBRATED to FAULTY on > > > > > > FAULT_DETECTED > > > > > > > > > > > > Did you have to do anything differently on the stock RH6.4 > > > install > > > > > > to > > > > > get it to work? > > > > > > > > > > > > Thanks, > > > > > > Gabe > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: Ledda William EXT [mailto:Wil...@it...] > > > > > > > Sent: Monday, October 21, 2013 1:02 AM > > > > > > > To: Richard Cochran; Gabe Black > > > > > > > Cc: lin...@li... > > > > > > > Subject: RE: [Linuxptp-users] Which distributions have > > > > > > > native ptp support? > > > > > > > > > > > > > > I'm currently using RH 6.4 with Intel i350 (igb driver) > with > > > > > success > > > > > > > (no need to recompile the kernel). About RH 6.5 I know that > > > > > > > there will be many improvements, more eth driver supported, > > > > > > > and it should include version 1.3 of linuxptp package. > > > > > > > > > > > > > > William > > > > > > > > > > |
From: Keller, J. E <jac...@in...> - 2013-10-28 22:37:17
|
What version of linuxPTP are you using? It appears you aren't using the 1.3 version as we moved to a method for obtaining the Tx timestamp that uses the poll() call. That might fix your issue. The other option would be to increase the tx_timestamp_timeout value, but I think moving to the newest Linux PTP should be a fix. Regards, Jake On Mon, 2013-10-28 at 21:35 +0000, Gabe Black wrote: > Nm, it was right. We have two subnets that will route to the meinberg, and they both work... So that means I still I don't know what it is... > > strace it shows: > sendto(11, "\1\2\0,\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\2406\237\377\376\30*\213\0\1\0\0"..., 44, 0, {sa_family=AF_INET, sin_port=htons(319), sin_addr=inet_addr("224.0.1.129")}, 16) = \ > 44 > Followed by a bunch of: > > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource temporarily unavailable) > nanosleep({0, 1000}, NULL) = 0 > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource temporarily unavailable) > nanosleep({0, 1000}, NULL) = 0 > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource temporarily unavailable) > nanosleep({0, 1000}, NULL) = 0 > recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource temporarily unavailable) > ... > > > > > -----Original Message----- > > From: Gabe Black > > Sent: Monday, October 28, 2013 2:20 PM > > To: Gabe Black; 'Keller, Jacob E' > > Cc: 'Ledda William EXT'; 'lin...@li...' > > Subject: RE: [Linuxptp-users] Which distributions have native ptp > > support? > > > > Oh sheesh.. I had a typo and was on the wrong subnet... > > > > It is working now! > > > > > -----Original Message----- > > > From: Gabe Black > > > Sent: Monday, October 28, 2013 1:18 PM > > > To: 'Keller, Jacob E' > > > Cc: Ledda William EXT; lin...@li... > > > Subject: RE: [Linuxptp-users] Which distributions have native ptp > > > support? > > > > > > > -----Original Message----- > > > > From: Keller, Jacob E [mailto:jac...@in...] You > > > > shouldn't have to, however, I would suggest disabling EEE support, > > > > as this has been known to cause issues on the i350 > > > > > > > > ethtool --set-eee device eee off > > > > > > > > This should fix your issue, if not please me know. > > > > > > Thank you for the reply. > > > > > > That option does not appear to be available with the stock igb driver > > > of RH6.4 > > > > > > [root@ network-scripts]# ethtool -i eth3 > > > driver: igb > > > version: 4.0.1-k > > > firmware-version: 0.1470, 0x05fc8000 > > > ... > > > [root@ network-scripts]# ethtool --show-eee eth3 Cannot get EEE > > > settings: Operation not supported > > > > > > Is there another way to disable EEE? Or would not having that option > > > in ethtool mean it is off? > > > > > > Gabe > > > > > > > On Mon, 2013-10-28 at 15:29 +0000, Gabe Black wrote: > > > > > Hi William, > > > > > > > > > > I installed redhat 6.4 and have the intel i350 (with igb driver) > > > and > > > > am having trouble getting it to work with a meinberg master. > > > > > > > > > > The output I get is: > > > > > > > > > > ptp4l[246980.523]: selected /dev/ptp1 as PTP clock > > > > > ptp4l[246980.525]: port 1: INITIALIZING to LISTENING on > > INITIALIZE > > > > > ptp4l[246980.526]: port 0: INITIALIZING to LISTENING on > > INITIALIZE > > > > > ptp4l[246980.773]: port 1: new foreign master 00606e.fffe.7c230e- > > 1 > > > > > ptp4l[246985.014]: selected best master clock 00606e.fffe.7c230e > > > > > ptp4l[246985.014]: foreign master not using PTP timescale > > > > > ptp4l[246985.014]: running in a temporal vortex > > > > > ptp4l[246985.014]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE > > > > > ptp4l[246985.989]: recvmsg tx timestamp failed: Resource > > > temporarily > > > > > unavailable > > > > > ptp4l[246985.989]: port 1: send delay request failed > > > > > ptp4l[246985.989]: port 1: UNCALIBRATED to FAULTY on > > > > > FAULT_DETECTED > > > > > > > > > > Did you have to do anything differently on the stock RH6.4 > > install > > > > > to > > > > get it to work? > > > > > > > > > > Thanks, > > > > > Gabe > > > > > > > > > > > -----Original Message----- > > > > > > From: Ledda William EXT [mailto:Wil...@it...] > > > > > > Sent: Monday, October 21, 2013 1:02 AM > > > > > > To: Richard Cochran; Gabe Black > > > > > > Cc: lin...@li... > > > > > > Subject: RE: [Linuxptp-users] Which distributions have native > > > > > > ptp support? > > > > > > > > > > > > I'm currently using RH 6.4 with Intel i350 (igb driver) with > > > > success > > > > > > (no need to recompile the kernel). About RH 6.5 I know that > > > > > > there will be many improvements, more eth driver supported, and > > > > > > it should include version 1.3 of linuxptp package. > > > > > > > > > > > > William > > > > > > > |
From: Gabe B. <Gab...@jd...> - 2013-10-28 21:35:54
|
Nm, it was right. We have two subnets that will route to the meinberg, and they both work... So that means I still I don't know what it is... strace it shows: sendto(11, "\1\2\0,\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\2406\237\377\376\30*\213\0\1\0\0"..., 44, 0, {sa_family=AF_INET, sin_port=htons(319), sin_addr=inet_addr("224.0.1.129")}, 16) = \ 44 Followed by a bunch of: recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource temporarily unavailable) nanosleep({0, 1000}, NULL) = 0 recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource temporarily unavailable) nanosleep({0, 1000}, NULL) = 0 recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource temporarily unavailable) nanosleep({0, 1000}, NULL) = 0 recvmsg(11, 0x7fff67459250, MSG_ERRQUEUE) = -1 EAGAIN (Resource temporarily unavailable) ... > -----Original Message----- > From: Gabe Black > Sent: Monday, October 28, 2013 2:20 PM > To: Gabe Black; 'Keller, Jacob E' > Cc: 'Ledda William EXT'; 'lin...@li...' > Subject: RE: [Linuxptp-users] Which distributions have native ptp > support? > > Oh sheesh.. I had a typo and was on the wrong subnet... > > It is working now! > > > -----Original Message----- > > From: Gabe Black > > Sent: Monday, October 28, 2013 1:18 PM > > To: 'Keller, Jacob E' > > Cc: Ledda William EXT; lin...@li... > > Subject: RE: [Linuxptp-users] Which distributions have native ptp > > support? > > > > > -----Original Message----- > > > From: Keller, Jacob E [mailto:jac...@in...] You > > > shouldn't have to, however, I would suggest disabling EEE support, > > > as this has been known to cause issues on the i350 > > > > > > ethtool --set-eee device eee off > > > > > > This should fix your issue, if not please me know. > > > > Thank you for the reply. > > > > That option does not appear to be available with the stock igb driver > > of RH6.4 > > > > [root@ network-scripts]# ethtool -i eth3 > > driver: igb > > version: 4.0.1-k > > firmware-version: 0.1470, 0x05fc8000 > > ... > > [root@ network-scripts]# ethtool --show-eee eth3 Cannot get EEE > > settings: Operation not supported > > > > Is there another way to disable EEE? Or would not having that option > > in ethtool mean it is off? > > > > Gabe > > > > > On Mon, 2013-10-28 at 15:29 +0000, Gabe Black wrote: > > > > Hi William, > > > > > > > > I installed redhat 6.4 and have the intel i350 (with igb driver) > > and > > > am having trouble getting it to work with a meinberg master. > > > > > > > > The output I get is: > > > > > > > > ptp4l[246980.523]: selected /dev/ptp1 as PTP clock > > > > ptp4l[246980.525]: port 1: INITIALIZING to LISTENING on > INITIALIZE > > > > ptp4l[246980.526]: port 0: INITIALIZING to LISTENING on > INITIALIZE > > > > ptp4l[246980.773]: port 1: new foreign master 00606e.fffe.7c230e- > 1 > > > > ptp4l[246985.014]: selected best master clock 00606e.fffe.7c230e > > > > ptp4l[246985.014]: foreign master not using PTP timescale > > > > ptp4l[246985.014]: running in a temporal vortex > > > > ptp4l[246985.014]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE > > > > ptp4l[246985.989]: recvmsg tx timestamp failed: Resource > > temporarily > > > > unavailable > > > > ptp4l[246985.989]: port 1: send delay request failed > > > > ptp4l[246985.989]: port 1: UNCALIBRATED to FAULTY on > > > > FAULT_DETECTED > > > > > > > > Did you have to do anything differently on the stock RH6.4 > install > > > > to > > > get it to work? > > > > > > > > Thanks, > > > > Gabe > > > > > > > > > -----Original Message----- > > > > > From: Ledda William EXT [mailto:Wil...@it...] > > > > > Sent: Monday, October 21, 2013 1:02 AM > > > > > To: Richard Cochran; Gabe Black > > > > > Cc: lin...@li... > > > > > Subject: RE: [Linuxptp-users] Which distributions have native > > > > > ptp support? > > > > > > > > > > I'm currently using RH 6.4 with Intel i350 (igb driver) with > > > success > > > > > (no need to recompile the kernel). About RH 6.5 I know that > > > > > there will be many improvements, more eth driver supported, and > > > > > it should include version 1.3 of linuxptp package. > > > > > > > > > > William > > > > > |
From: Keller, J. E <jac...@in...> - 2013-10-28 21:28:40
|
On Mon, 2013-10-28 at 19:17 +0000, Gabe Black wrote: > > -----Original Message----- > > From: Keller, Jacob E [mailto:jac...@in...] > > You shouldn't have to, however, I would suggest disabling EEE support, > > as this has been known to cause issues on the i350 > > > > ethtool --set-eee device eee off > > > > This should fix your issue, if not please me know. > > Thank you for the reply. > > That option does not appear to be available with the stock igb driver of RH6.4 > > [root@ network-scripts]# ethtool -i eth3 > driver: igb > version: 4.0.1-k > firmware-version: 0.1470, 0x05fc8000 > ... > [root@ network-scripts]# ethtool --show-eee eth3 > Cannot get EEE settings: Operation not supported > > Is there another way to disable EEE? Or would not having that option in ethtool mean it is off? > > Gabe I am not certain. I believe it would simply be off. At any rate looks like you got the issue fixed. Regards, Jake |
From: Gabe B. <Gab...@jd...> - 2013-10-28 20:20:40
|
Oh sheesh.. I had a typo and was on the wrong subnet... It is working now! > -----Original Message----- > From: Gabe Black > Sent: Monday, October 28, 2013 1:18 PM > To: 'Keller, Jacob E' > Cc: Ledda William EXT; lin...@li... > Subject: RE: [Linuxptp-users] Which distributions have native ptp > support? > > > -----Original Message----- > > From: Keller, Jacob E [mailto:jac...@in...] You shouldn't > > have to, however, I would suggest disabling EEE support, as this has > > been known to cause issues on the i350 > > > > ethtool --set-eee device eee off > > > > This should fix your issue, if not please me know. > > Thank you for the reply. > > That option does not appear to be available with the stock igb driver > of RH6.4 > > [root@ network-scripts]# ethtool -i eth3 > driver: igb > version: 4.0.1-k > firmware-version: 0.1470, 0x05fc8000 > ... > [root@ network-scripts]# ethtool --show-eee eth3 Cannot get EEE > settings: Operation not supported > > Is there another way to disable EEE? Or would not having that option in > ethtool mean it is off? > > Gabe > > > On Mon, 2013-10-28 at 15:29 +0000, Gabe Black wrote: > > > Hi William, > > > > > > I installed redhat 6.4 and have the intel i350 (with igb driver) > and > > am having trouble getting it to work with a meinberg master. > > > > > > The output I get is: > > > > > > ptp4l[246980.523]: selected /dev/ptp1 as PTP clock > > > ptp4l[246980.525]: port 1: INITIALIZING to LISTENING on INITIALIZE > > > ptp4l[246980.526]: port 0: INITIALIZING to LISTENING on INITIALIZE > > > ptp4l[246980.773]: port 1: new foreign master 00606e.fffe.7c230e-1 > > > ptp4l[246985.014]: selected best master clock 00606e.fffe.7c230e > > > ptp4l[246985.014]: foreign master not using PTP timescale > > > ptp4l[246985.014]: running in a temporal vortex > > > ptp4l[246985.014]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE > > > ptp4l[246985.989]: recvmsg tx timestamp failed: Resource > temporarily > > > unavailable > > > ptp4l[246985.989]: port 1: send delay request failed > > > ptp4l[246985.989]: port 1: UNCALIBRATED to FAULTY on FAULT_DETECTED > > > > > > Did you have to do anything differently on the stock RH6.4 install > > > to > > get it to work? > > > > > > Thanks, > > > Gabe > > > > > > > -----Original Message----- > > > > From: Ledda William EXT [mailto:Wil...@it...] > > > > Sent: Monday, October 21, 2013 1:02 AM > > > > To: Richard Cochran; Gabe Black > > > > Cc: lin...@li... > > > > Subject: RE: [Linuxptp-users] Which distributions have native ptp > > > > support? > > > > > > > > I'm currently using RH 6.4 with Intel i350 (igb driver) with > > success > > > > (no need to recompile the kernel). About RH 6.5 I know that there > > > > will be many improvements, more eth driver supported, and it > > > > should include version 1.3 of linuxptp package. > > > > > > > > William > > > > |
From: Gabe B. <Gab...@jd...> - 2013-10-28 19:18:43
|
> -----Original Message----- > From: Keller, Jacob E [mailto:jac...@in...] > You shouldn't have to, however, I would suggest disabling EEE support, > as this has been known to cause issues on the i350 > > ethtool --set-eee device eee off > > This should fix your issue, if not please me know. Thank you for the reply. That option does not appear to be available with the stock igb driver of RH6.4 [root@ network-scripts]# ethtool -i eth3 driver: igb version: 4.0.1-k firmware-version: 0.1470, 0x05fc8000 ... [root@ network-scripts]# ethtool --show-eee eth3 Cannot get EEE settings: Operation not supported Is there another way to disable EEE? Or would not having that option in ethtool mean it is off? Gabe > On Mon, 2013-10-28 at 15:29 +0000, Gabe Black wrote: > > Hi William, > > > > I installed redhat 6.4 and have the intel i350 (with igb driver) and > am having trouble getting it to work with a meinberg master. > > > > The output I get is: > > > > ptp4l[246980.523]: selected /dev/ptp1 as PTP clock > > ptp4l[246980.525]: port 1: INITIALIZING to LISTENING on INITIALIZE > > ptp4l[246980.526]: port 0: INITIALIZING to LISTENING on INITIALIZE > > ptp4l[246980.773]: port 1: new foreign master 00606e.fffe.7c230e-1 > > ptp4l[246985.014]: selected best master clock 00606e.fffe.7c230e > > ptp4l[246985.014]: foreign master not using PTP timescale > > ptp4l[246985.014]: running in a temporal vortex > > ptp4l[246985.014]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE > > ptp4l[246985.989]: recvmsg tx timestamp failed: Resource temporarily > > unavailable > > ptp4l[246985.989]: port 1: send delay request failed > > ptp4l[246985.989]: port 1: UNCALIBRATED to FAULTY on FAULT_DETECTED > > > > Did you have to do anything differently on the stock RH6.4 install to > get it to work? > > > > Thanks, > > Gabe > > > > > -----Original Message----- > > > From: Ledda William EXT [mailto:Wil...@it...] > > > Sent: Monday, October 21, 2013 1:02 AM > > > To: Richard Cochran; Gabe Black > > > Cc: lin...@li... > > > Subject: RE: [Linuxptp-users] Which distributions have native ptp > > > support? > > > > > > I'm currently using RH 6.4 with Intel i350 (igb driver) with > success > > > (no need to recompile the kernel). About RH 6.5 I know that there > > > will be many improvements, more eth driver supported, and it should > > > include version 1.3 of linuxptp package. > > > > > > William > > > |
From: Keller, J. E <jac...@in...> - 2013-10-28 18:22:12
|
You shouldn't have to, however, I would suggest disabling EEE support, as this has been known to cause issues on the i350 ethtool --set-eee device eee off This should fix your issue, if not please me know. Regards, Jake On Mon, 2013-10-28 at 15:29 +0000, Gabe Black wrote: > Hi William, > > I installed redhat 6.4 and have the intel i350 (with igb driver) and am having trouble getting it to work with a meinberg master. > > The output I get is: > > ptp4l[246980.523]: selected /dev/ptp1 as PTP clock > ptp4l[246980.525]: port 1: INITIALIZING to LISTENING on INITIALIZE > ptp4l[246980.526]: port 0: INITIALIZING to LISTENING on INITIALIZE > ptp4l[246980.773]: port 1: new foreign master 00606e.fffe.7c230e-1 > ptp4l[246985.014]: selected best master clock 00606e.fffe.7c230e > ptp4l[246985.014]: foreign master not using PTP timescale > ptp4l[246985.014]: running in a temporal vortex > ptp4l[246985.014]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE > ptp4l[246985.989]: recvmsg tx timestamp failed: Resource temporarily unavailable > ptp4l[246985.989]: port 1: send delay request failed > ptp4l[246985.989]: port 1: UNCALIBRATED to FAULTY on FAULT_DETECTED > > Did you have to do anything differently on the stock RH6.4 install to get it to work? > > Thanks, > Gabe > > > -----Original Message----- > > From: Ledda William EXT [mailto:Wil...@it...] > > Sent: Monday, October 21, 2013 1:02 AM > > To: Richard Cochran; Gabe Black > > Cc: lin...@li... > > Subject: RE: [Linuxptp-users] Which distributions have native ptp > > support? > > > > I'm currently using RH 6.4 with Intel i350 (igb driver) with success > > (no need to recompile the kernel). About RH 6.5 I know that there will > > be many improvements, more eth driver supported, and it should include > > version 1.3 of linuxptp package. > > > > William > > > > ----Original Message----- > > From: Richard Cochran [mailto:ric...@gm...] > > Sent: 19 October 2013 08:01 > > To: Gabe Black > > Cc: lin...@li... > > Subject: Re: [Linuxptp-users] Which distributions have native ptp > > support? > > > > On Thu, Oct 10, 2013 at 07:18:29PM +0000, Gabe Black wrote: > > > > > I've been trying to search and find which distributions have native > > > ptp support. I am finding it difficult to find out without actually > > > installing the distribution. > > > > > > So far I have found that Redhat 6.5 will have support (according to > > > their release notes). Are there any others? > > > > There are a few distro people on this list, but they are all silent :( > > > > I can only say that I use debian or my own SLIM for embedded (github), > > but on debian I compile my own kernel and also linuxptp. > > > > In general, I think the distros will need more time, since you really > > want at least kernel 3.5 for ETHTOOL_GET_TS_INFO, and 3.9 for the > > latest drivers. > > > > Thanks, > > Richard > > > > ----------------------------------------------------------------------- > > ------- > > October Webinars: Code for Performance > > Free Intel webinars can help you accelerate application performance. > > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the > > most from the latest Intel processors and coprocessors. See abstracts > > and register > > > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.cl > > ktrk > > _______________________________________________ > > Linuxptp-users mailing list > > Lin...@li... > > https://lists.sourceforge.net/lists/listinfo/linuxptp-users > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Linuxptp-users mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxptp-users |
From: Vick, M. <mat...@in...> - 2013-10-28 17:43:36
|
On 10/28/13, 9:53 AM, "Jean-Baptiste Maillet" <jea...@pa...> wrote: >On 10/28/2013 05:41 PM, Jean-Baptiste Maillet wrote: >> On 10/25/2013 06:12 PM, Vick, Matthew wrote: >> ... >>> I210 should definitely be working in the upstream Linux kernel. Please >>>let >>> me know if it is not. >> >> I think there is a problem. >> ptp4l "poll tx timestamp timeout" 100% >> igb driver on i210 "Detected Tx Unit Hang" 100% >> >> Tested here with a freshly built 3.10.2 fetched from kernel.org. >... >> >>> I'm uncertain what the Debian kernel version of igb looks like. It's >>> possible some critical patch is missing. You can try the latest version >>> (5.0.6) from e1000.sf.net and compiling with CFLAGS_EXTRA=-DIGB_PTP to >>>see >>> if that driver works for you. >> >> Will do. > >Done. >Good news: same results. >Should this go to e1000-devel instead? That's really strange. It looks like the device's transmit unit is hanging on the first few packets you attempt to send, which is why ptp4l is failing. Yes, please do send along all of your information to e1000-devel and we'll have some more Intel folks look at it. A few other bits that would be helpful are the lspci -vvv output before and after the error occurs as well as whether this failure occurs with any other traffic (i.e. ping). Thank you! Cheers, Matthew |
From: Jean-Baptiste M. <jea...@pa...> - 2013-10-28 16:53:40
|
On 10/28/2013 05:41 PM, Jean-Baptiste Maillet wrote: > On 10/25/2013 06:12 PM, Vick, Matthew wrote: > ... >> I210 should definitely be working in the upstream Linux kernel. Please let >> me know if it is not. > > I think there is a problem. > ptp4l "poll tx timestamp timeout" 100% > igb driver on i210 "Detected Tx Unit Hang" 100% > > Tested here with a freshly built 3.10.2 fetched from kernel.org. ... > >> I'm uncertain what the Debian kernel version of igb looks like. It's >> possible some critical patch is missing. You can try the latest version >> (5.0.6) from e1000.sf.net and compiling with CFLAGS_EXTRA=-DIGB_PTP to see >> if that driver works for you. > > Will do. Done. Good news: same results. Should this go to e1000-devel instead? $ make CFLAGS_EXTRA=-DIGB_PTP make -C /lib/modules/3.10.2-vanilla-686-pae/build SUBDIRS=/home/jbmaillet/sandbox/igb-5.0.6/src modules ... $ modinfo /home/jbmaillet/sandbox/igb-5.0.6/src/igb.ko filename: /home/jbmaillet/sandbox/igb-5.0.6/src/igb.ko version: 5.0.6 license: GPL description: Intel(R) Gigabit Ethernet Network Driver author: Intel Corporation, <e10...@li...> srcversion: 55D8265EA2BD13346D24336 ... # insmod /home/jbmaillet/sandbox/igb-5.0.6/src/igb.ko (root@sumo) (/home/jbmaillet/sandbox/linuxptp-git) # ifconfig eth2-igb 192.168.100.2 up (root@sumo) (/home/jbmaillet/sandbox/linuxptp-git) # ./ptp4l -i eth2-igb -m -l 7 ptp4l[14466.673]: selected /dev/ptp0 as PTP clock ptp4l[14466.673]: PI servo: sync interval 1.000 kp 0.700 ki 0.300000 ptp4l[14466.674]: driver changed our HWTSTAMP options ptp4l[14466.674]: tx_type 1 not 1 ptp4l[14466.674]: rx_filter 1 not 12 ptp4l[14466.674]: port 1: INITIALIZING to LISTENING on INITIALIZE ptp4l[14466.675]: port 0: INITIALIZING to LISTENING on INITIALIZE ptp4l[14472.675]: port 1: announce timeout ptp4l[14472.675]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES ptp4l[14472.675]: selected best master clock a0369f.fffe.1c38a8 ptp4l[14472.675]: assuming the grand master role ptp4l[14472.676]: port 1: master tx announce timeout ptp4l[14472.676]: port 1: setting asCapable ptp4l[14473.675]: port 1: master sync timeout ptp4l[14473.676]: poll tx timestamp timeout ptp4l[14473.676]: port 1: send sync failed ptp4l[14473.676]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED) ptp4l[14473.676]: waiting 2^{4} seconds to clear fault on port 1 ^Cptp4l[14476.358]: caught signal 2 (root@sumo) (/home/jbmaillet/sandbox/linuxptp-git) # dmesg [14469.599074] Intel(R) Gigabit Ethernet Network Driver - version 5.0.6 [14469.599085] Copyright (c) 2007-2013 Intel Corporation. [14469.599969] igb 0000:03:00.0: irq 43 for MSI/MSI-X [14469.599989] igb 0000:03:00.0: irq 44 for MSI/MSI-X [14469.682421] igb 0000:03:00.0: added PHC on eth0 [14469.682433] igb 0000:03:00.0: Intel(R) Gigabit Ethernet Network Connection [14469.682440] igb 0000:03:00.0: eth0: (PCIe:2.5GT/s:Width x1) [14469.682447] igb 0000:03:00.0: eth0: MAC: [14469.682451] a0:36:9f:1c:38:a8 [14469.682664] igb 0000:03:00.0: eth0: PBA No: G69016-001 [14469.688917] igb 0000:03:00.0: LRO is disabled [14469.688931] igb 0000:03:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s) [14469.701223] systemd-udevd[13872]: renamed network interface eth0 to eth2-igb [14474.746458] IPv6: ADDRCONF(NETDEV_UP): eth2-igb: link is not ready [14477.545681] igb: eth2-igb NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [14477.545956] IPv6: ADDRCONF(NETDEV_CHANGE): eth2-igb: link becomes ready [14479.744322] igb 0000:03:00.0: Detected Tx Unit Hang ... -- JB |
From: Jean-Baptiste M. <jea...@pa...> - 2013-10-28 16:41:59
|
On 10/25/2013 06:12 PM, Vick, Matthew wrote: ... > I210 should definitely be working in the upstream Linux kernel. Please let > me know if it is not. I think there is a problem. ptp4l "poll tx timestamp timeout" 100% igb driver on i210 "Detected Tx Unit Hang" 100% Tested here with a freshly built 3.10.2 fetched from kernel.org. # uname -a Linux sumo 3.10.2-vanilla-686-pae #2 SMP Mon Oct 28 11:21:13 CET 2013 i686 GNU/Linux # modinfo /lib/modules/3.10.2-vanilla-686-pae/kernel/drivers/net/ethernet/intel/igb/igb.ko filename: /lib/modules/3.10.2-vanilla-686-pae/kernel/drivers/net/ethernet/intel/igb/igb.ko version: 5.0.3-k license: GPL description: Intel(R) Gigabit Ethernet Network Driver author: Intel Corporation, <e10...@li...> srcversion: 8251E5B658798814C71FD34 ... For ptp4l: # git log -n 1 --pretty=oneline 52c5e0cfc972c3e2b65ca492eecbff6edb8b2aaf Don't calculate delay with old master's sync time stamp. Setup: # rmmod igb # dmesg -c # dmesg -n 7 # modprobe igb (for the braves out here, contact me for the "debug=16" dmesg output bellow) # ifconfig eth2-igb 192.168.100.2 up Then: # ./ptp4l -i eth2-igb -m -l 7 ptp4l[12963.591]: selected /dev/ptp0 as PTP clock ptp4l[12963.592]: PI servo: sync interval 1.000 kp 0.700 ki 0.300000 ptp4l[12963.592]: driver changed our HWTSTAMP options ptp4l[12963.593]: tx_type 1 not 1 ptp4l[12963.593]: rx_filter 1 not 12 ptp4l[12963.593]: port 1: INITIALIZING to LISTENING on INITIALIZE ptp4l[12963.593]: port 0: INITIALIZING to LISTENING on INITIALIZE ptp4l[12969.593]: port 1: announce timeout ptp4l[12969.593]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES ptp4l[12969.593]: selected best master clock a0369f.fffe.1c38a8 ptp4l[12969.593]: assuming the grand master role ptp4l[12969.594]: port 1: master tx announce timeout ptp4l[12969.594]: port 1: setting asCapable ptp4l[12970.593]: port 1: master sync timeout ptp4l[12970.594]: poll tx timestamp timeout ptp4l[12970.594]: port 1: send sync failed ptp4l[12970.594]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED) ptp4l[12970.594]: waiting 2^{4} seconds to clear fault on port 1 ^Cptp4l[12972.061]: caught signal 2 # dmesg [12955.198501] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.0.3-k [12955.198511] igb: Copyright (c) 2007-2013 Intel Corporation. [12955.199411] igb 0000:03:00.0: irq 43 for MSI/MSI-X [12955.199432] igb 0000:03:00.0: irq 44 for MSI/MSI-X [12955.199450] igb 0000:03:00.0: irq 45 for MSI/MSI-X [12955.199467] igb 0000:03:00.0: irq 46 for MSI/MSI-X [12955.199487] igb 0000:03:00.0: irq 47 for MSI/MSI-X [12955.284305] igb 0000:03:00.0: added PHC on eth0 [12955.284317] igb 0000:03:00.0: Intel(R) Gigabit Ethernet Network Connection [12955.284326] igb 0000:03:00.0: eth0: (PCIe:2.5Gb/s:Width x1) a0:36:9f:1c:38:a8 [12955.284532] igb 0000:03:00.0: eth0: PBA No: G69016-001 [12955.284539] igb 0000:03:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s) [12955.311533] systemd-udevd[11676]: renamed network interface eth0 to eth2-igb [12962.123669] IPv6: ADDRCONF(NETDEV_UP): eth2-igb: link is not ready [12964.333099] igb: eth2-igb NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [12964.333533] IPv6: ADDRCONF(NETDEV_CHANGE): eth2-igb: link becomes ready [12966.207446] igb 0000:03:00.0: Detected Tx Unit Hang [12966.207446] Tx Queue <2> [12966.207446] TDH <0> [12966.207446] TDT <1> [12966.207446] next_to_use <1> [12966.207446] next_to_clean <0> [12966.207446] buffer_info[next_to_clean] [12966.207446] time_stamp <30429e> [12966.207446] next_to_watch <eedcc000> [12966.207446] jiffies <304470> [12966.207446] desc.status <168000> [12968.208531] igb 0000:03:00.0: Detected Tx Unit Hang [12968.208531] Tx Queue <2> [12968.208531] TDH <0> [12968.208531] TDT <1> [12968.208531] next_to_use <1> [12968.208531] next_to_clean <0> [12968.208531] buffer_info[next_to_clean] [12968.208531] time_stamp <30429e> [12968.208531] next_to_watch <eedcc000> [12968.208531] jiffies <304664> [12968.208531] desc.status <168000> [12970.210527] igb 0000:03:00.0: Detected Tx Unit Hang [12970.210527] Tx Queue <2> [12970.210527] TDH <0> [12970.210527] TDT <1> [12970.210527] next_to_use <1> [12970.210527] next_to_clean <0> [12970.210527] buffer_info[next_to_clean] [12970.210527] time_stamp <30429e> [12970.210527] next_to_watch <eedcc000> [12970.210527] jiffies <304858> [12970.210527] desc.status <168000> [12972.212578] igb 0000:03:00.0: Detected Tx Unit Hang [12972.212578] Tx Queue <1> [12972.212578] TDH <0> [12972.212578] TDT <1> [12972.212578] next_to_use <1> [12972.212578] next_to_clean <0> [12972.212578] buffer_info[next_to_clean] [12972.212578] time_stamp <304790> [12972.212578] next_to_watch <eec1d000> [12972.212578] jiffies <304a4c> [12972.212578] desc.status <d8000> [12972.212594] igb 0000:03:00.0: Detected Tx Unit Hang [12972.212594] Tx Queue <2> [12972.212594] TDH <0> [12972.212594] TDT <1> [12972.212594] next_to_use <1> [12972.212594] next_to_clean <0> [12972.212594] buffer_info[next_to_clean] [12972.212594] time_stamp <30429e> [12972.212594] next_to_watch <eedcc000> [12972.212594] jiffies <304a4c> [12972.212594] desc.status <168000> [12974.214274] igb 0000:03:00.0 eth2-igb: Reset adapter [12978.014992] igb: eth2-igb NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [12982.234731] igb 0000:03:00.0: Detected Tx Unit Hang [12982.234731] Tx Queue <2> [12982.234731] TDH <0> [12982.234731] TDT <1> [12982.234731] next_to_use <1> [12982.234731] next_to_clean <0> [12982.234731] buffer_info[next_to_clean] [12982.234731] time_stamp <3052a1> [12982.234731] next_to_watch <eedcc000> [12982.234731] jiffies <305413> [12982.234731] desc.status <1ac000> [12984.236804] igb 0000:03:00.0: Detected Tx Unit Hang [12984.236804] Tx Queue <2> [12984.236804] TDH <0> [12984.236804] TDT <1> [12984.236804] next_to_use <1> [12984.236804] next_to_clean <0> [12984.236804] buffer_info[next_to_clean] [12984.236804] time_stamp <3052a1> [12984.236804] next_to_watch <eedcc000> [12984.236804] jiffies <305607> [12984.236804] desc.status <1ac000> [12986.238813] igb 0000:03:00.0: Detected Tx Unit Hang [12986.238813] Tx Queue <3> [12986.238813] TDH <0> [12986.238813] TDT <2> [12986.238813] next_to_use <2> [12986.238813] next_to_clean <0> [12986.238813] buffer_info[next_to_clean] [12986.238813] time_stamp <3055a0> [12986.238813] next_to_watch <ef523010> [12986.238813] jiffies <3057fb> [12986.238813] desc.status <158200> [12986.238828] igb 0000:03:00.0: Detected Tx Unit Hang [12986.238828] Tx Queue <2> [12986.238828] TDH <0> [12986.238828] TDT <1> [12986.238828] next_to_use <1> [12986.238828] next_to_clean <0> [12986.238828] buffer_info[next_to_clean] [12986.238828] time_stamp <3052a1> [12986.238828] next_to_watch <eedcc000> [12986.238828] jiffies <3057fb> [12986.238828] desc.status <1ac000> [12986.238843] igb 0000:03:00.0: Detected Tx Unit Hang [12986.238843] Tx Queue <1> [12986.238843] TDH <0> [12986.238843] TDT <1> [12986.238843] next_to_use <1> [12986.238843] next_to_clean <0> [12986.238843] buffer_info[next_to_clean] [12986.238843] time_stamp <3055a2> [12986.238843] next_to_watch <eec1d000> [12986.238843] jiffies <3057fb> [12986.238843] desc.status <f8000> [12988.240845] igb 0000:03:00.0: Detected Tx Unit Hang [12988.240845] Tx Queue <2> [12988.240845] TDH <0> [12988.240845] TDT <1> [12988.240845] next_to_use <1> [12988.240845] next_to_clean <0> [12988.240845] buffer_info[next_to_clean] [12988.240845] time_stamp <3052a1> [12988.240845] next_to_watch <eedcc000> [12988.240845] jiffies <3059ef> [12988.240845] desc.status <1ac000> [12988.240860] igb 0000:03:00.0: Detected Tx Unit Hang [12988.240860] Tx Queue <3> [12988.240860] TDH <0> [12988.240860] TDT <2> [12988.240860] next_to_use <2> [12988.240860] next_to_clean <0> [12988.240860] buffer_info[next_to_clean] [12988.240860] time_stamp <3055a0> [12988.240860] next_to_watch <ef523010> [12988.240860] jiffies <3059ef> [12988.240860] desc.status <158200> [12988.240875] igb 0000:03:00.0: Detected Tx Unit Hang [12988.240875] Tx Queue <1> [12988.240875] TDH <0> [12988.240875] TDT <1> [12988.240875] next_to_use <1> [12988.240875] next_to_clean <0> [12988.240875] buffer_info[next_to_clean] [12988.240875] time_stamp <3055a2> [12988.240875] next_to_watch <eec1d000> [12988.240875] jiffies <3059ef> [12988.240875] desc.status <f8000> [12988.244531] igb 0000:03:00.0 eth2-igb: Reset adapter > I'm uncertain what the Debian kernel version of igb looks like. It's > possible some critical patch is missing. You can try the latest version > (5.0.6) from e1000.sf.net and compiling with CFLAGS_EXTRA=-DIGB_PTP to see > if that driver works for you. Will do. -- JB |
From: Jon D. <jl...@ya...> - 2013-10-28 15:49:20
|
I'm working on a project using linuxptp where I may need to set up multiple clock synchronization domains on the same subnet. I may have two (or more) masters and will need to specify on the slaves which master to synchronize with. It seems like using something like the "priority" variable in the BMC algorithm would be useful for this, but I don't believe that it is something I can specify on a per-slave basis - it appears to be a constant on the master instead. I'd almost want to bypass the BMC algorithm altogether and manually specify the "best" clock for each slave. Is this even possible with PTP? Does anyone have an idea as to what I should be investigating? |
From: Gabe B. <Gab...@jd...> - 2013-10-28 15:30:15
|
Hi William, I installed redhat 6.4 and have the intel i350 (with igb driver) and am having trouble getting it to work with a meinberg master. The output I get is: ptp4l[246980.523]: selected /dev/ptp1 as PTP clock ptp4l[246980.525]: port 1: INITIALIZING to LISTENING on INITIALIZE ptp4l[246980.526]: port 0: INITIALIZING to LISTENING on INITIALIZE ptp4l[246980.773]: port 1: new foreign master 00606e.fffe.7c230e-1 ptp4l[246985.014]: selected best master clock 00606e.fffe.7c230e ptp4l[246985.014]: foreign master not using PTP timescale ptp4l[246985.014]: running in a temporal vortex ptp4l[246985.014]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE ptp4l[246985.989]: recvmsg tx timestamp failed: Resource temporarily unavailable ptp4l[246985.989]: port 1: send delay request failed ptp4l[246985.989]: port 1: UNCALIBRATED to FAULTY on FAULT_DETECTED Did you have to do anything differently on the stock RH6.4 install to get it to work? Thanks, Gabe > -----Original Message----- > From: Ledda William EXT [mailto:Wil...@it...] > Sent: Monday, October 21, 2013 1:02 AM > To: Richard Cochran; Gabe Black > Cc: lin...@li... > Subject: RE: [Linuxptp-users] Which distributions have native ptp > support? > > I'm currently using RH 6.4 with Intel i350 (igb driver) with success > (no need to recompile the kernel). About RH 6.5 I know that there will > be many improvements, more eth driver supported, and it should include > version 1.3 of linuxptp package. > > William > > ----Original Message----- > From: Richard Cochran [mailto:ric...@gm...] > Sent: 19 October 2013 08:01 > To: Gabe Black > Cc: lin...@li... > Subject: Re: [Linuxptp-users] Which distributions have native ptp > support? > > On Thu, Oct 10, 2013 at 07:18:29PM +0000, Gabe Black wrote: > > > I've been trying to search and find which distributions have native > > ptp support. I am finding it difficult to find out without actually > > installing the distribution. > > > > So far I have found that Redhat 6.5 will have support (according to > > their release notes). Are there any others? > > There are a few distro people on this list, but they are all silent :( > > I can only say that I use debian or my own SLIM for embedded (github), > but on debian I compile my own kernel and also linuxptp. > > In general, I think the distros will need more time, since you really > want at least kernel 3.5 for ETHTOOL_GET_TS_INFO, and 3.9 for the > latest drivers. > > Thanks, > Richard > > ----------------------------------------------------------------------- > ------- > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the > most from the latest Intel processors and coprocessors. See abstracts > and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.cl > ktrk > _______________________________________________ > Linuxptp-users mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxptp-users |
From: Keller, J. E <jac...@in...> - 2013-10-28 10:10:57
|
Hi, > -----Original Message----- > From: Vick, Matthew [mailto:mat...@in...] > Sent: Friday, October 25, 2013 9:13 AM > To: Jean-Baptiste Maillet; lin...@li... > Subject: Re: [Linuxptp-users] "poll tx timestamp timeout", problem since > v1.2, igb, stmmac > > On 10/25/13, 8:47 AM, "Jean-Baptiste Maillet" > <jea...@pa...> wrote: > > >On 10/25/2013 05:09 PM, Richard Cochran wrote: > > [...] > > >> I don't really trust the Debian kernels. I would try the igb driver > >> from a recent mainline kernel. The igb driver really should be working > >> in mainline Linux. > > > >OK, will do. I need a hardware and upstream reference point known to > work. > >It's (bad) luck I didn't tried the Debian igb driver right away but the > >highly experimental > >igb_avb first. My only suspect was stmmac. > > > >BTW igb support 2-3 families of chip (82575, 82576, 82580, then i210, > >i211, and i350, i354): > >do any users out there can share their experience using it specifically > >with i210? > > I210 should definitely be working in the upstream Linux kernel. Please let > me know if it is not. > > I'm uncertain what the Debian kernel version of igb looks like. It's > possible some critical patch is missing. You can try the latest version > (5.0.6) from e1000.sf.net and compiling with CFLAGS_EXTRA=-DIGB_PTP > to see > if that driver works for you. > > Cheers, > Matthew > > Matthew Vick > Linux Development > Networking Division > Intel Corporation > I second this. The igb driver definitely had some fixes in place over time, which may be the case that the debian kernel didn't manage to include (or included with bugs). My guess is the avb driver has the proper code to fix this issue. In general, since we moved to using poll() for a longer period of time, this error indicates a more serious issue, and I am thinking of submitting a patch to update the error text to be more indicative of what happened. Regards, Jake |
From: Jean-Baptiste M. <jea...@pa...> - 2013-10-28 09:06:39
|
On 10/27/2013 07:35 AM, Richard Cochran wrote: > On Fri, Oct 25, 2013 at 04:10:36PM +0200, Jean-Baptiste Maillet wrote: > >> Intel igb_avb is fine, yet both vanilla igb and stmmac fail with a >> "poll tx timestamp timeout" 100% reproducible. >> Increasing the tx_timestamp_timeout does not help. > > Your command line > >> $ sudo ./ptp4l -i eth2-igb -m -l 7 > > does not show that you used "-f config" to specify a configuration > file. The ptp4l program does not scan any config files by default. It > just uses built in defaults. So, if you did not use the "-f" command > line switch, then you also did not change the tx_timestamp_timeout > value. Yes, I got that - that was a simplification (rather than explaining "...and then to setup a tx_timestamp_timeout different from the efault zero, providing this config file blablabla and then using this command line blablabla). But thanks for asking, yes, that may have been a mistake. JB |
From: Richard C. <ric...@gm...> - 2013-10-27 16:34:22
|
On Sun, Oct 27, 2013 at 06:24:53AM -0700, Raymond Guo wrote: > I cannot find any reference that says the linux kernel or the hardware or > the ethernet driver is not supposed to pass up the FCS to apps when > communicating over raw sockets. I found this: http://wiki.wireshark.org/Ethernet As the Ethernet hardware filters the preamble, it is not given to Wireshark or any other application. Most Ethernet interfaces also either don't supply the FCS to Wireshark or other applications, or aren't configured by their driver to do so; therefore, Wireshark will typically only be given the green fields, although on some platforms, with some interfaces, the FCS will be supplied on incoming packets. > Is this an issue lying in the kernel, ethernet driver or hardware which is > not supposed to deliver the FCS? I would bet this is a driver issue. What kernel and driver are you using? > Otherwise is ptp4l supposed to properly handle the FCS (such as ignoring > the last 4 bytes), or setting a socket option (if one exists) to kernel to > ask it to discard the FCS before delivering to user space? AFAICT, there is no such socket option. Sorry, Richard |
From: Raymond G. <ray...@ya...> - 2013-10-27 13:28:00
|
Hi, We are trying to run ptp4l (linuxptp-1.3) over ethernet (the -2 option). On the slave side, we use the command: "./ptp4l -H -2 -H -i eth0 -s -l 7 -m -q -p /dev/ptp0". However because of some "bad message" errors (see below), the slave side is not working. ptp4l[63896.503]: PI servo: sync interval 1.000 kp 0.100 ki 0.001000 ptp4l[63896.503]: port 1: get_ts_info not supported ptp4l[63896.600]: port 1: INITIALIZING to LISTENING on INITIALIZE ptp4l[63896.600]: port 0: INITIALIZING to LISTENING on INITIALIZE ptp4l[63897.324]: port 1: setting asCapable ptp4l[63897.324]: port 1: new foreign master 080028.fffe.329976-1 ptp4l[63897.526]: port 1: bad message We notice that the "bad message" is caused by the slave side receiving frames that includes the FCS. This FCS is treated as TLV, for example in a follow_up message from host side, in the suffix processing function suffix_post_recv. We experimented by letting ptp4l ignore the last 4 bytes of FCS in the messages received, then it works fine. I cannot find any reference that says the linux kernel or the hardware or the ethernet driver is not supposed to pass up the FCS to apps when communicating over raw sockets. Is this an issue lying in the kernel, ethernet driver or hardware which is not supposed to deliver the FCS? Otherwise is ptp4l supposed to properly handle the FCS (such as ignoring the last 4 bytes), or setting a socket option (if one exists) to kernel to ask it to discard the FCS before delivering to user space? Any suggestion will be appreciated. Thanks Raymond |
From: Richard C. <ric...@gm...> - 2013-10-27 06:35:26
|
On Fri, Oct 25, 2013 at 04:10:36PM +0200, Jean-Baptiste Maillet wrote: > Intel igb_avb is fine, yet both vanilla igb and stmmac fail with a > "poll tx timestamp timeout" 100% reproducible. > Increasing the tx_timestamp_timeout does not help. Your command line > $ sudo ./ptp4l -i eth2-igb -m -l 7 does not show that you used "-f config" to specify a configuration file. The ptp4l program does not scan any config files by default. It just uses built in defaults. So, if you did not use the "-f" command line switch, then you also did not change the tx_timestamp_timeout value. Thanks, Richard |
From: Ledda W. E. <Wil...@it...> - 2013-10-26 09:26:25
|
Also Open Suse has the support for PTP! I have verified on a notebook with 12.2 installed with kernel 3.4.6 William -----Original Message----- From: Ledda William EXT [mailto:Wil...@it...] Sent: 21 October 2013 09:02 To: Richard Cochran; Gabe Black Cc: lin...@li... Subject: Re: [Linuxptp-users] Which distributions have native ptp support? I'm currently using RH 6.4 with Intel i350 (igb driver) with success (no need to recompile the kernel). About RH 6.5 I know that there will be many improvements, more eth driver supported, and it should include version 1.3 of linuxptp package. William ----Original Message----- From: Richard Cochran [mailto:ric...@gm...] Sent: 19 October 2013 08:01 To: Gabe Black Cc: lin...@li... Subject: Re: [Linuxptp-users] Which distributions have native ptp support? On Thu, Oct 10, 2013 at 07:18:29PM +0000, Gabe Black wrote: > I've been trying to search and find which distributions have native > ptp support. I am finding it difficult to find out without actually > installing the distribution. > > So far I have found that Redhat 6.5 will have support (according to > their release notes). Are there any others? There are a few distro people on this list, but they are all silent :( I can only say that I use debian or my own SLIM for embedded (github), but on debian I compile my own kernel and also linuxptp. In general, I think the distros will need more time, since you really want at least kernel 3.5 for ETHTOOL_GET_TS_INFO, and 3.9 for the latest drivers. Thanks, Richard ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk _______________________________________________ Linuxptp-users mailing list Lin...@li... https://lists.sourceforge.net/lists/listinfo/linuxptp-users ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk _______________________________________________ Linuxptp-users mailing list Lin...@li... https://lists.sourceforge.net/lists/listinfo/linuxptp-users |
From: Vick, M. <mat...@in...> - 2013-10-25 16:13:14
|
On 10/25/13, 8:47 AM, "Jean-Baptiste Maillet" <jea...@pa...> wrote: >On 10/25/2013 05:09 PM, Richard Cochran wrote: [...] >> I don't really trust the Debian kernels. I would try the igb driver >> from a recent mainline kernel. The igb driver really should be working >> in mainline Linux. > >OK, will do. I need a hardware and upstream reference point known to work. >It's (bad) luck I didn't tried the Debian igb driver right away but the >highly experimental >igb_avb first. My only suspect was stmmac. > >BTW igb support 2-3 families of chip (82575, 82576, 82580, then i210, >i211, and i350, i354): >do any users out there can share their experience using it specifically >with i210? I210 should definitely be working in the upstream Linux kernel. Please let me know if it is not. I'm uncertain what the Debian kernel version of igb looks like. It's possible some critical patch is missing. You can try the latest version (5.0.6) from e1000.sf.net and compiling with CFLAGS_EXTRA=-DIGB_PTP to see if that driver works for you. Cheers, Matthew Matthew Vick Linux Development Networking Division Intel Corporation |
From: Jean-Baptiste M. <jea...@pa...> - 2013-10-25 15:47:33
|
On 10/25/2013 05:09 PM, Richard Cochran wrote: > On Fri, Oct 25, 2013 at 04:10:36PM +0200, Jean-Baptiste Maillet wrote: >> >> On the kernel side, for driver/ptp/ I'm on 0d8c3e7 "ptp_pch: fix error handling in pch_probe()" for stmmac, >> Debian 3.10.7-1 for i210. > > So 0d8c3e7 means a pure mainstream kernel (v3.10-rc5~25^2~36)? Nope, the sha is just the reference to where I am regarding ptp compared to upstream. This is a SoC with specific BSP and platform drivers. > And Debian kernel is from testing or unstable? Testing (but at least pure Debian upstream). > I don't really trust the Debian kernels. I would try the igb driver > from a recent mainline kernel. The igb driver really should be working > in mainline Linux. OK, will do. I need a hardware and upstream reference point known to work. It's (bad) luck I didn't tried the Debian igb driver right away but the highly experimental igb_avb first. My only suspect was stmmac. BTW igb support 2-3 families of chip (82575, 82576, 82580, then i210, i211, and i350, i354): do any users out there can share their experience using it specifically with i210? > Regarding the stmmac, although I reviewed the patches, I never tested > them (no hardware to try), and so I would not be surprised if it had > bugs. > >> To this point, I think this is a hardware driver issue (not really ptp4l nor ptp driver, and hoping this is not >> a combination of the 3) but any suggestion would be welcome. > > If not a hardware issue, then probably a driver/kernel issue. The > ptp4l program hasn't really ever substantially changed the way the > transmit time stamps are read. Thanks -- JB |
From: Richard C. <ric...@gm...> - 2013-10-25 15:09:39
|
On Fri, Oct 25, 2013 at 04:10:36PM +0200, Jean-Baptiste Maillet wrote: > > On the kernel side, for driver/ptp/ I'm on 0d8c3e7 "ptp_pch: fix error handling in pch_probe()" for stmmac, > Debian 3.10.7-1 for i210. So 0d8c3e7 means a pure mainstream kernel (v3.10-rc5~25^2~36)? And Debian kernel is from testing or unstable? I don't really trust the Debian kernels. I would try the igb driver from a recent mainline kernel. The igb driver really should be working in mainline Linux. Regarding the stmmac, although I reviewed the patches, I never tested them (no hardware to try), and so I would not be surprised if it had bugs. > To this point, I think this is a hardware driver issue (not really ptp4l nor ptp driver, and hoping this is not > a combination of the 3) but any suggestion would be welcome. If not a hardware issue, then probably a driver/kernel issue. The ptp4l program hasn't really ever substantially changed the way the transmit time stamps are read. Thanks, Richard |