linuxptp-users Mailing List for linuxptp (Page 143)
PTP IEEE 1588 stack for Linux
Brought to you by:
rcochran
Menu
▾
▴
linuxptp-users — Open discussion on using the linuxptp software.
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: Miroslav L. <mli...@re...> - 2013-10-21 10:25:27
|
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? Fedora 19 includes linuxptp-1.3 and a recent kernel with PTP enabled. It should work out of the box. -- Miroslav Lichvar |
|
From: Ledda W. E. <Wil...@it...> - 2013-10-21 07:10:49
|
Ciao Frabrizio, Have you tried to discover the timestamp capabilities with ethtool -T eth0? William From: Fabrizio Giordano [mailto:Fab...@ri...] Sent: 19 October 2013 02:28 To: lin...@li... Subject: [Linuxptp-users] Issues with linuxptp and Intel 82574 Hello everyone, I've been trying to use linux with my Intel 82574 with no much luck. First I've tried to use it with software timestamping since the version of e1000e I was using didn't support HW timestamping. This is what I get: [root@199-dorothy13 ~]# ptp4l -i eth0 -v -S ptp4l[25333.043]: port 1: INITIALIZING to LISTENING on INITIALIZE ptp4l[25333.043]: port 0: INITIALIZING to LISTENING on INITIALIZE ptp4l[25334.561]: port 1: new foreign master 003048.fffe.9ea9d6-1 ptp4l[25338.561]: selected best master clock 003048.fffe.9ea9d6 ptp4l[25338.561]: port 1: LISTENING to GRAND_MASTER on RS_GRAND_MASTER ptp4l[25339.567]: recvmsg tx timestamp failed: Resource temporarily unavailable ptp4l[25339.567]: port 1: send sync failed ptp4l[25339.567]: port 1: GRAND_MASTER to FAULTY on FAULT_DETECTED ptp4l[25354.574]: port 1: FAULTY to LISTENING on FAULT_CLEARED What is that supposed to mean? Resource temporarily unavailable? So I decided to update my e1000e driver to the latest version available (2.5.4) and use HW timestamping. After rebooting my machine I try to run it with HW support (no option -S) and this is what I get: ptp4l[25432.718]: driver rejected most general HWTSTAMP filter ptp4l[25432.718]: ioctl SIOCSHWTSTAMP failed: Numerical result out of range ptp4l[25432.722]: port 1: INITIALIZING to FAULTY on INITIALIZE ptp4l[25432.722]: port 0: INITIALIZING to LISTENING on INITIALIZE Does anyone know what's going on? Thank you very much! Fabrizio |
|
From: Ledda W. E. <Wil...@it...> - 2013-10-21 07:02:05
|
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 |
|
From: Richard C. <ric...@gm...> - 2013-10-19 06:01:42
|
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 |
|
From: Fabrizio G. <Fab...@ri...> - 2013-10-19 00:28:25
|
Hello everyone, I've been trying to use linux with my Intel 82574 with no much luck. First I've tried to use it with software timestamping since the version of e1000e I was using didn't support HW timestamping. This is what I get: [root@199-dorothy13 ~]# ptp4l -i eth0 -v -S ptp4l[25333.043]: port 1: INITIALIZING to LISTENING on INITIALIZE ptp4l[25333.043]: port 0: INITIALIZING to LISTENING on INITIALIZE ptp4l[25334.561]: port 1: new foreign master 003048.fffe.9ea9d6-1 ptp4l[25338.561]: selected best master clock 003048.fffe.9ea9d6 ptp4l[25338.561]: port 1: LISTENING to GRAND_MASTER on RS_GRAND_MASTER ptp4l[25339.567]: recvmsg tx timestamp failed: Resource temporarily unavailable ptp4l[25339.567]: port 1: send sync failed ptp4l[25339.567]: port 1: GRAND_MASTER to FAULTY on FAULT_DETECTED ptp4l[25354.574]: port 1: FAULTY to LISTENING on FAULT_CLEARED What is that supposed to mean? Resource temporarily unavailable? So I decided to update my e1000e driver to the latest version available (2.5.4) and use HW timestamping. After rebooting my machine I try to run it with HW support (no option -S) and this is what I get: ptp4l[25432.718]: driver rejected most general HWTSTAMP filter ptp4l[25432.718]: ioctl SIOCSHWTSTAMP failed: Numerical result out of range ptp4l[25432.722]: port 1: INITIALIZING to FAULTY on INITIALIZE ptp4l[25432.722]: port 0: INITIALIZING to LISTENING on INITIALIZE Does anyone know what's going on? Thank you very much! Fabrizio |
|
From: Gabe B. <Gab...@jd...> - 2013-10-10 19:32:05
|
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? Thanks, Gabe |
|
From: Richard C. <ric...@gm...> - 2013-10-04 17:16:29
|
On Tue, Oct 01, 2013 at 08:00:02AM +0000, Ledda William EXT wrote: > Dear all linuxptp users, > I have a question about the statistics collected by ptp4l. Is there any particular reason why the value of summary_interval must be expressed as power of two? The only reason is that we treat this interval like the sync interval (and using some of the same code). Maybe that is not a very good reason, and it could be changed with a little work. Thanks, Richard |
|
From: Ledda W. E. <Wil...@it...> - 2013-10-01 08:00:11
|
Dear all linuxptp users, I have a question about the statistics collected by ptp4l. Is there any particular reason why the value of summary_interval must be expressed as power of two? I mean, I need to have the statistics of 600 samples at 1Hz (10 minutes). I can produce these statistics using phc2sys but not with ptp4l (2^9 = 512 is the nearest value to 600) Thank you all William |
|
From: Richard C. <ric...@gm...> - 2013-09-10 06:19:57
|
On Mon, Sep 09, 2013 at 08:33:24PM -0500, David Bourgoyne wrote: > phc2sys will synchronize the Linux CLOCK_REALTIME to PHC. But what > about CLOCK_MONOTONIC? Will it adjust as a result of CLOCK_REALTIME > being synchronized to PHC? Will CLOCK_MONOTONIC slow or speed up to > match PHC? Yes, CLOCK_MONOTONIC is syntonized (frequency locked) to CLOCK_REALTIME by the kernel. Thanks, Richard |
|
From: David B. <dbo...@gm...> - 2013-09-10 01:33:31
|
phc2sys will synchronize the Linux CLOCK_REALTIME to PHC. But what about CLOCK_MONOTONIC? Will it adjust as a result of CLOCK_REALTIME being synchronized to PHC? Will CLOCK_MONOTONIC slow or speed up to match PHC? I'm using GStreamer for media playback and it uses CLOCK_MONOTONIC for its default system clock. I'd like to have two GStreamer pipelines on two separate computers synchronized as close as possible. Thanks, David |
|
From: Vick, M. <mat...@in...> - 2013-09-06 15:31:38
|
Aman, Thank you for the additional information! Based on your feedback, I have a few more questions: 1. Are you running the in-kernel driver or the driver from e1000.sf.net? 2. Are you performing any configuration of the device prior to running traffic (bonding, ethtool configuration, running ptp4l, etc.)? Please note that the in-kernel driver for PTP on I210 on 3.5 will not work. We did not add the full functionality for I210 until 3.7. If you would like the support on your kernel, please use the driver from e1000.sf.net and compile it with the following command: $ CFLAGS_EXTRA=-DIGB_PTP make Cheers, Matthew From: Aman Sharma <ama...@gm...<mailto:ama...@gm...>> Date: Thursday, September 5, 2013 10:07 PM To: Matthew Vick <mat...@in...<mailto:mat...@in...>> Cc: Jacob E Keller <jac...@in...<mailto:jac...@in...>>, "lin...@li...<mailto:lin...@li...>" <lin...@li...<mailto:lin...@li...>> Subject: Re: [Linuxptp-users] Issue in running gPTP Hi Vick, Thanks for your Response. I am using Intel i210 NIC card having interface eth4. But when I connect lan wire to eth4 interface then it shows the dmesg shown below and I am not able to ping the ip address of that interface from other connected machine. So I want to say that pinging is not working on I210 interface. Please provide the sufficient information for this so that I can solve the issue. Below is the output of Following: #dmesg /home/vvdn# dmesg [ 375.840141] igb: eth4 NIC Link is Down [ 394.036531] igb: eth4 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX [ 397.992150] igb 0000:01:00.0: Detected Tx Unit Hang [ 397.992150] Tx Queue <1> [ 397.992150] TDH <0> [ 397.992150] TDT <1> [ 397.992150] next_to_use <1> [ 397.992150] next_to_clean <0> [ 397.992150] buffer_info[next_to_clean] [ 397.992150] time_stamp <5da4> [ 397.992150] next_to_watch <ecee9000> [ 397.992150] jiffies <5fb2> [ 397.992150] desc.status <a8000> [ 399.992147] igb 0000:01:00.0: Detected Tx Unit Hang [ 399.992147] Tx Queue <1> [ 399.992147] TDH <0> [ 399.992147] TDT <1> [ 399.992147] next_to_use <1> [ 399.992147] next_to_clean <0> [ 399.992147] buffer_info[next_to_clean] [ 399.992147] time_stamp <5da4> [ 399.992147] next_to_watch <ecee9000> [ 399.992147] jiffies <61a6> [ 399.992147] desc.status <a8000> [ 401.992147] igb 0000:01:00.0: Detected Tx Unit Hang [ 401.992147] Tx Queue <1> [ 401.992147] TDH <0> [ 401.992147] TDT <1> [ 401.992147] next_to_use <1> [ 401.992147] next_to_clean <0> [ 401.992147] buffer_info[next_to_clean] [ 401.992147] time_stamp <5da4> [ 401.992147] next_to_watch <ecee9000> [ 401.992147] jiffies <639a> [ 401.992147] desc.status <a8000> [ 403.992150] igb 0000:01:00.0: Detected Tx Unit Hang [ 403.992150] Tx Queue <1> [ 403.992150] TDH <0> [ 403.992150] TDT <1> [ 403.992150] next_to_use <1> [ 403.992150] next_to_clean <0> [ 403.992150] buffer_info[next_to_clean] [ 403.992150] time_stamp <5da4> [ 403.992150] next_to_watch <ecee9000> [ 403.992150] jiffies <658e> [ 403.992150] desc.status <a8000> [ 404.000026] igb 0000:01:00.0: eth4: Reset adapter [ 421.720537] igb: eth4 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX [ 426.004151] igb 0000:01:00.0: Detected Tx Unit Hang [ 426.004151] Tx Queue <0> [ 426.004151] TDH <0> [ 426.004151] TDT <2> [ 426.004151] next_to_use <2> [ 426.004151] next_to_clean <0> [ 426.004151] buffer_info[next_to_clean] [ 426.004151] time_stamp <786a> [ 426.004151] next_to_watch <ecf67010> [ 426.004151] jiffies <7b0d> [ 426.004151] desc.status <144200> [ 428.004169] igb 0000:01:00.0: Detected Tx Unit Hang [ 428.004169] Tx Queue <0> [ 428.004169] TDH <0> [ 428.004169] TDT <2> [ 428.004169] next_to_use <2> [ 428.004169] next_to_clean <0> [ 428.004169] buffer_info[next_to_clean] [ 428.004169] time_stamp <786a> [ 428.004169] next_to_watch <ecf67010> [ 428.004169] jiffies <7d01> [ 428.004169] desc.status <144200> [ 430.004149] igb 0000:01:00.0: Detected Tx Unit Hang [ 430.004149] Tx Queue <0> [ 430.004149] TDH <0> [ 430.004149] TDT <2> [ 430.004149] next_to_use <2> [ 430.004149] next_to_clean <0> [ 430.004149] buffer_info[next_to_clean] [ 430.004149] time_stamp <786a> [ 430.004149] next_to_watch <ecf67010> [ 430.004149] jiffies <7ef5> [ 430.004149] desc.status <144200> [ 432.004157] igb 0000:01:00.0: Detected Tx Unit Hang [ 432.004157] Tx Queue <0> [ 432.004157] TDH <0> [ 432.004157] TDT <2> [ 432.004157] next_to_use <2> [ 432.004157] next_to_clean <0> [ 432.004157] buffer_info[next_to_clean] [ 432.004157] time_stamp <786a> [ 432.004157] next_to_watch <ecf67010> [ 432.004157] jiffies <80e9> [ 432.004157] desc.status <144200> [ 432.016030] igb 0000:01:00.0: eth4: Reset adapter [ 449.672530] igb: eth4 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX #lspci -vvv lspci -vvv 00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller (rev 10) Subsystem: Giga-byte Technology Device 5000 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx- Latency: 0 Capabilities: [e0] Vendor Specific Information: Len=0b <?> Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 10) (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device d000 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 49 Region 0: Memory at fdf00000 (32-bit, non-prefetchable) [size=512K] Region 1: I/O ports at ff00 [size=8] Region 2: Memory at d0000000 (32-bit, prefetchable) [size=256M] Region 3: Memory at fdc00000 (32-bit, non-prefetchable) [size=1M] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0100c Data: 41b1 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: i915 Kernel modules: i915 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01) Subsystem: Giga-byte Technology Device a002 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 4 bytes Interrupt: pin A routed to IRQ 48 Region 0: Memory at fdff8000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee0300c Data: 41a9 Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us ExtTag- RBE- FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #0, Speed unknown, Width x0, ASPM unknown, Latency L0 <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed unknown, Width x0, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- VC1: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=1 ArbSelect=Fixed TC/VC=80 Status: NegoPending- InProgress- Capabilities: [130 v1] Root Complex Link Desc: PortNumber=0f ComponentID=02 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=02 AssocRCRB- LinkType=MemMapped LinkValid+ Addr: 00000000fed1c000 Kernel driver in use: snd_hda_intel Kernel modules: snd-hda-intel 00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 4 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 0000c000-0000cfff Memory behind bridge: fd700000-fd9fffff Prefetchable memory behind bridge: 00000000fd600000-00000000fd6fffff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited ExtTag- RBE- FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s, Latency L0 <256ns, L1 <4us ClockPM- Surprise- LLActRep+ BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Slot #16, PowerLimit 10.000W; Interlock- NoCompl- SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState+ RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID 0000, PMEStatus- PMEPending- Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 4161 Capabilities: [90] Subsystem: Giga-byte Technology Device 5001 Capabilities: [a0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed+ WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- VC1: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable- ID=0 ArbSelect=Fixed TC/VC=00 Status: NegoPending- InProgress- Capabilities: [180 v1] Root Complex Link Desc: PortNumber=01 ComponentID=02 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=02 AssocRCRB- LinkType=MemMapped LinkValid+ Addr: 00000000fed1c001 Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 4 bytes Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 0000b000-0000bfff Memory behind bridge: fde00000-fdefffff Prefetchable memory behind bridge: 00000000fdd00000-00000000fddfffff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited ExtTag- RBE- FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x1, ASPM L0s, Latency L0 <256ns, L1 <4us ClockPM- Surprise- LLActRep+ BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Slot #17, PowerLimit 10.000W; Interlock- NoCompl- SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState+ RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID 0000, PMEStatus- PMEPending- Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 4169 Capabilities: [90] Subsystem: Giga-byte Technology Device 5001 Capabilities: [a0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed+ WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- VC1: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable- ID=0 ArbSelect=Fixed TC/VC=00 Status: NegoPending- InProgress- Capabilities: [180 v1] Root Complex Link Desc: PortNumber=02 ComponentID=02 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=02 AssocRCRB- LinkType=MemMapped LinkValid+ Addr: 00000000fed1c001 Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 01) (prog-if 00 [UHCI]) Subsystem: Giga-byte Technology Device 5004 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 23 Region 4: I/O ports at fe00 [size=32] Kernel driver in use: uhci_hcd 00:1d.1 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 01) (prog-if 00 [UHCI]) Subsystem: Giga-byte Technology Device 5004 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 19 Region 4: I/O ports at fd00 [size=32] Kernel driver in use: uhci_hcd 00:1d.2 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 01) (prog-if 00 [UHCI]) Subsystem: Giga-byte Technology Device 5004 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin C routed to IRQ 18 Region 4: I/O ports at fc00 [size=32] Kernel driver in use: uhci_hcd 00:1d.3 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 01) (prog-if 00 [UHCI]) Subsystem: Giga-byte Technology Device 5004 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin D routed to IRQ 16 Region 4: I/O ports at fb00 [size=32] Kernel driver in use: uhci_hcd 00:1d.7 USB controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 01) (prog-if 20 [EHCI]) Subsystem: Giga-byte Technology Device 5006 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 23 Region 0: Memory at fdfff000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: ehci_hcd 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1) (prog-if 01 [Subtractive decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=32 I/O behind bridge: 0000d000-0000dfff Memory behind bridge: fdb00000-fdbfffff Prefetchable memory behind bridge: 00000000fda00000-00000000fdafffff Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [50] Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard 00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01) Subsystem: Giga-byte Technology Device 5001 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Capabilities: [e0] Vendor Specific Information: Len=0c <?> Kernel driver in use: lpc_ich Kernel modules: leds-ss4200, lpc_ich, intel-rng 00:1f.2 IDE interface: Intel Corporation N10/ICH7 Family SATA Controller [IDE mode] (rev 01) (prog-if 80 [Master]) Subsystem: Giga-byte Technology Device b002 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx+ Latency: 0 Interrupt: pin B routed to IRQ 19 Region 0: I/O ports at 01f0 [size=8] Region 1: I/O ports at 03f4 [size=1] Region 2: I/O ports at 0170 [size=8] Region 3: I/O ports at 0374 [size=1] Region 4: I/O ports at f800 [size=16] Capabilities: [70] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: ata_piix 00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 01) Subsystem: Giga-byte Technology GA-8I945PG-RH Mainboard Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin B routed to IRQ 11 Region 4: I/O ports at 0500 [size=32] Kernel modules: i2c-i801 01:00.0 Ethernet controller: Intel Corporation Device 1533 (rev 03) Subsystem: Intel Corporation Device 0002 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 4 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at fd800000 (32-bit, non-prefetchable) [size=1M] Region 3: Memory at fd9fc000 (32-bit, non-prefetchable) [size=16K] [virtual] Expansion ROM at fd600000 [disabled] [size=1M] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+ Address: 0000000000000000 Data: 0000 Masking: 00000000 Pending: 00000000 Capabilities: [70] MSI-X: Enable+ Count=5 Masked- Vector table: BAR=3 offset=00000000 PBA: BAR=3 offset=00002000 Capabilities: [a0] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <2us, L1 <16us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB Capabilities: [100 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [140 v1] Device Serial Number a0-36-9f-ff-ff-1c-dc-4b Capabilities: [1a0 v1] Transaction Processing Hints Device specific mode supported Steering table in TPH capability structure Kernel driver in use: igb Kernel modules: igb 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 4 bytes Interrupt: pin A routed to IRQ 42 Region 0: I/O ports at be00 [size=256] Region 2: Memory at fddff000 (64-bit, prefetchable) [size=4K] Region 4: Memory at fdde0000 (64-bit, prefetchable) [size=64K] [virtual] Expansion ROM at fdd00000 [disabled] [size=64K] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+ Address: 00000000fee0200c Data: 4171 Capabilities: [70] Express (v1) Endpoint, MSI 01 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1 <8us ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 4096 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us ClockPM+ Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [b0] MSI-X: Enable- Count=2 Masked- Vector table: BAR=4 offset=00000000 PBA: BAR=4 offset=00000800 Capabilities: [d0] Vital Product Data Unknown small resource type 00, will not decode more. Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr+ BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [140 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [160 v1] Device Serial Number 12-34-56-78-12-34-56-78 Kernel driver in use: r8169 Kernel modules: r8169 03:00.0 Ethernet controller: D-Link System Inc DGE-530T Gigabit Ethernet Adapter (rev 11) (rev 11) Subsystem: D-Link System Inc DGE-530T Gigabit Ethernet Adapter (rev 11) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 32 (5750ns min, 7750ns max), Cache Line Size: 4 bytes Interrupt: pin A routed to IRQ 20 Region 0: Memory at fdbfc000 (32-bit, non-prefetchable) [size=16K] Region 1: I/O ports at de00 [size=256] [virtual] Expansion ROM at fda00000 [disabled] [size=128K] Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Product Name: DGE-530T Gigabit Ethernet Adapter Read-only fields: [PN] Part number: DGE-530T [EC] Engineering changes: Rev. 1.1 [MN] Manufacture ID: 44 2d 4c 69 6e 6b [SN] Serial number: DGE530T70E359 [CP] Extended capability: 01 10 cc 03 [RV] Reserved: checksum good, 31 byte(s) reserved Read/write fields: [RW] Read-write area: 121 byte(s) free End Kernel driver in use: skge Kernel modules: skge #uname -a uname -a Linux vvdnovs 3.5.0 #3 SMP Wed Sep 4 14:21:03 IST 2013 i686 i686 i386 GNU/Linux On Thu, Sep 5, 2013 at 11:20 PM, Vick, Matthew <mat...@in...<mailto:mat...@in...>> wrote: Aman, We will need some more information before we can help you out with your problem. Can you please provide the output from the following commands? # dmesg # lspci -vvv $ uname -a Also, please provide some additional details about your configuration, steps to reproduce the issue, etc. Which device are you seeing this on? Cheers, Matthew Matthew Vick Linux Development Networking Division Intel Corporation From: Aman Sharma <ama...@gm...<mailto:ama...@gm...>> Date: Wednesday, September 4, 2013 8:42 PM To: Jacob E Keller <jac...@in...<mailto:jac...@in...>> Cc: "lin...@li...<mailto:lin...@li...>" <lin...@li...<mailto:lin...@li...>> Subject: Re: [Linuxptp-users] Issue in running gPTP Hi Jacob/Suresh, Thanks for your reply. Now its working fine.Actually hardware clock is disabled in kernel. But now I am getting one more error message i.e. igb: eth4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [67378.092992] r8169 0000:02:00.0: eth0: link up [67379.993212] igb 0000:01:00.0: Detected Tx Unit Hang [67379.993212] Tx Queue <0> [67379.993212] TDH <0> [67379.993212] TDT <1> [67379.993212] next_to_use <1> [67379.993212] next_to_clean <0> [67379.993212] buffer_info[next_to_clean] [67379.993212] time_stamp <ffe28e> [67379.993212] next_to_watch <ed7e4000> [67379.993212] jiffies <ffe3ce> [67379.993212] desc.status <a8000> buffer_info[next_to_clean] [67410.993266] time_stamp <10000fc> [67410.993266] next_to_watch <ed7e4000> [67410.993266] jiffies <1000214> [67410.993266] desc.status <a8000> [67412.992265] igb 0000:01:00.0: Detected Tx Unit Hang [67412.992265] Tx Queue <0> [67412.992265] TDH <0> [67412.992265] TDT <1> [67412.992265] next_to_use <1> [67412.992265] next_to_clean <0> [67412.992265] buffer_info[next_to_clean] [67412.992265] time_stamp <10000fc> [67412.992265] next_to_watch <ed7e4000> [67412.992265] jiffies <1000408> [67412.992265] desc.status <a8000> [67414.992274] igb 0000:01:00.0: Detected Tx Unit Hang [67414.992274] Tx Queue <0> [67414.992274] TDH <0> [67414.992274] TDT <1> [67414.992274] next_to_use <1> [67414.992274] next_to_clean <0> [67414.992274] buffer_info[next_to_clean] [67414.992274] time_stamp <10000fc> [67414.992274] next_to_watch <ed7e4000> [67414.992274] jiffies <10005fc> [67414.992274] desc.status <a8000> Can you Please check this. -- With Regards Aman Sharma On Wed, Sep 4, 2013 at 11:02 PM, Keller, Jacob E <jac...@in...<mailto:jac...@in...>> wrote: Hello, Aman mentioned in his email that he already did enable PTP in the kernel... Aman, Did you install the driver from sourceforge? or are you using the in-kernel driver? If you are using the sourceforge driver you need to compile it with "CFLAGS_EXTRA=-DIGB_PTP make" instead of the normal "make". This is because PTP is not enabled in the source forge driver by default.. Also, unsure if its true for igb, but for ixgbe I know that you have to get link up before PTP devices will appear... Thanks, Jake On Wed, 2013-09-04 at 05:53 +0000, sur...@wi...<mailto:sur...@wi...> wrote: > Hi Amar, > > Enable PTP and PPS while compiling the kernel and try it out > > > > Thanks and Regards > Suresh > > ______________________________________________________________________ > From: Aman Sharma [ama...@gm...<mailto:ama...@gm...>] > Sent: Wednesday, September 04, 2013 10:06 AM > To: lin...@li...<mailto:lin...@li...> > Subject: [Linuxptp-users] Issue in running gPTP > > > > Hi All, > > > > > We want to run linuxPTP with intel i210 NIC cards.For this , We > compiled the linux kernel with version 3.5.0 and enabled PTP in it and > also installed igb driver in the machine.But when running linuxPTP > with command: > > > ./ptp4l -f gPTP.cfg -i eth4 > > > then it shows message PTP device is not specified and automatic > determination is not supported.Please specify PTP device . > > > But when I check for PTP device in the folder /dev/ , there is no PTP > device specified. > > > Can anyone Please help me in this. > > > Thanks for your help in advance. > > > regards > Aman > ------------------------------------------------------------------------------ > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk > _______________________________________________ > Linuxptp-users mailing list > Lin...@li...<mailto:Lin...@li...> > https://lists.sourceforge.net/lists/listinfo/linuxptp-users |
|
From: Aman S. <ama...@gm...> - 2013-09-06 05:07:58
|
Hi Vick,
Thanks for your Response.
I am using Intel i210 NIC card having interface eth4. But when I connect
lan wire to eth4 interface then it shows the dmesg shown below and I am not
able to ping the ip address of that interface from other connected machine.
So I want to say that pinging is not working on I210 interface.
Please provide the sufficient information for this so that I can solve the
issue.
Below is the output of Following:
*#dmesg*
/home/vvdn# dmesg
[ 375.840141] igb: eth4 NIC Link is Down
[ 394.036531] igb: eth4 NIC Link is Up 100 Mbps Full Duplex, Flow Control:
RX/TX
[ 397.992150] igb 0000:01:00.0: Detected Tx Unit Hang
[ 397.992150] Tx Queue <1>
[ 397.992150] TDH <0>
[ 397.992150] TDT <1>
[ 397.992150] next_to_use <1>
[ 397.992150] next_to_clean <0>
[ 397.992150] buffer_info[next_to_clean]
[ 397.992150] time_stamp <5da4>
[ 397.992150] next_to_watch <ecee9000>
[ 397.992150] jiffies <5fb2>
[ 397.992150] desc.status <a8000>
[ 399.992147] igb 0000:01:00.0: Detected Tx Unit Hang
[ 399.992147] Tx Queue <1>
[ 399.992147] TDH <0>
[ 399.992147] TDT <1>
[ 399.992147] next_to_use <1>
[ 399.992147] next_to_clean <0>
[ 399.992147] buffer_info[next_to_clean]
[ 399.992147] time_stamp <5da4>
[ 399.992147] next_to_watch <ecee9000>
[ 399.992147] jiffies <61a6>
[ 399.992147] desc.status <a8000>
[ 401.992147] igb 0000:01:00.0: Detected Tx Unit Hang
[ 401.992147] Tx Queue <1>
[ 401.992147] TDH <0>
[ 401.992147] TDT <1>
[ 401.992147] next_to_use <1>
[ 401.992147] next_to_clean <0>
[ 401.992147] buffer_info[next_to_clean]
[ 401.992147] time_stamp <5da4>
[ 401.992147] next_to_watch <ecee9000>
[ 401.992147] jiffies <639a>
[ 401.992147] desc.status <a8000>
[ 403.992150] igb 0000:01:00.0: Detected Tx Unit Hang
[ 403.992150] Tx Queue <1>
[ 403.992150] TDH <0>
[ 403.992150] TDT <1>
[ 403.992150] next_to_use <1>
[ 403.992150] next_to_clean <0>
[ 403.992150] buffer_info[next_to_clean]
[ 403.992150] time_stamp <5da4>
[ 403.992150] next_to_watch <ecee9000>
[ 403.992150] jiffies <658e>
[ 403.992150] desc.status <a8000>
[ 404.000026] igb 0000:01:00.0: eth4: Reset adapter
[ 421.720537] igb: eth4 NIC Link is Up 100 Mbps Full Duplex, Flow Control:
RX/TX
[ 426.004151] igb 0000:01:00.0: Detected Tx Unit Hang
[ 426.004151] Tx Queue <0>
[ 426.004151] TDH <0>
[ 426.004151] TDT <2>
[ 426.004151] next_to_use <2>
[ 426.004151] next_to_clean <0>
[ 426.004151] buffer_info[next_to_clean]
[ 426.004151] time_stamp <786a>
[ 426.004151] next_to_watch <ecf67010>
[ 426.004151] jiffies <7b0d>
[ 426.004151] desc.status <144200>
[ 428.004169] igb 0000:01:00.0: Detected Tx Unit Hang
[ 428.004169] Tx Queue <0>
[ 428.004169] TDH <0>
[ 428.004169] TDT <2>
[ 428.004169] next_to_use <2>
[ 428.004169] next_to_clean <0>
[ 428.004169] buffer_info[next_to_clean]
[ 428.004169] time_stamp <786a>
[ 428.004169] next_to_watch <ecf67010>
[ 428.004169] jiffies <7d01>
[ 428.004169] desc.status <144200>
[ 430.004149] igb 0000:01:00.0: Detected Tx Unit Hang
[ 430.004149] Tx Queue <0>
[ 430.004149] TDH <0>
[ 430.004149] TDT <2>
[ 430.004149] next_to_use <2>
[ 430.004149] next_to_clean <0>
[ 430.004149] buffer_info[next_to_clean]
[ 430.004149] time_stamp <786a>
[ 430.004149] next_to_watch <ecf67010>
[ 430.004149] jiffies <7ef5>
[ 430.004149] desc.status <144200>
[ 432.004157] igb 0000:01:00.0: Detected Tx Unit Hang
[ 432.004157] Tx Queue <0>
[ 432.004157] TDH <0>
[ 432.004157] TDT <2>
[ 432.004157] next_to_use <2>
[ 432.004157] next_to_clean <0>
[ 432.004157] buffer_info[next_to_clean]
[ 432.004157] time_stamp <786a>
[ 432.004157] next_to_watch <ecf67010>
[ 432.004157] jiffies <80e9>
[ 432.004157] desc.status <144200>
[ 432.016030] igb 0000:01:00.0: eth4: Reset adapter
[ 449.672530] igb: eth4 NIC Link is Up 100 Mbps Full Duplex, Flow Control:
RX/TX
*#lspci -vvv*
lspci -vvv
00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM
Controller (rev 10)
Subsystem: Giga-byte Technology Device 5000
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort+ >SERR- <PERR- INTx-
Latency: 0
Capabilities: [e0] Vendor Specific Information: Len=0b <?>
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
Integrated Graphics Controller (rev 10) (prog-if 00 [VGA controller])
Subsystem: Giga-byte Technology Device d000
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 49
Region 0: Memory at fdf00000 (32-bit, non-prefetchable) [size=512K]
Region 1: I/O ports at ff00 [size=8]
Region 2: Memory at d0000000 (32-bit, prefetchable) [size=256M]
Region 3: Memory at fdc00000 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0100c Data: 41b1
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: i915
Kernel modules: i915
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition
Audio Controller (rev 01)
Subsystem: Giga-byte Technology Device a002
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 4 bytes
Interrupt: pin A routed to IRQ 48
Region 0: Memory at fdff8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee0300c Data: 41a9
Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1
<1us
ExtTag- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+
TransPend-
LnkCap: Port #0, Speed unknown, Width x0, ASPM unknown, Latency
L0 <64ns, L1 <1us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed unknown, Width x0, TrErr- Train- SlotClk-
DLActive- BWMgmt- ABWMgmt-
Capabilities: [100 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status: NegoPending- InProgress-
VC1: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=1 ArbSelect=Fixed TC/VC=80
Status: NegoPending- InProgress-
Capabilities: [130 v1] Root Complex Link
Desc: PortNumber=0f ComponentID=02 EltType=Config
Link0: Desc: TargetPort=00 TargetComponent=02 AssocRCRB-
LinkType=MemMapped LinkValid+
Addr: 00000000fed1c000
Kernel driver in use: snd_hda_intel
Kernel modules: snd-hda-intel
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1
(rev 01) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 4 bytes
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: fd700000-fd9fffff
Prefetchable memory behind bridge: 00000000fd600000-00000000fd6fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
unlimited, L1 unlimited
ExtTag- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+
TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s, Latency L0
<256ns, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive+ BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+
Surprise+
Slot #16, PowerLimit 10.000W; Interlock- NoCompl-
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+
Interlock-
Changed: MRL- PresDet+ LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna-
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0300c Data: 4161
Capabilities: [90] Subsystem: Giga-byte Technology Device 5001
Capabilities: [a0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed+ WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status: NegoPending- InProgress-
VC1: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable- ID=0 ArbSelect=Fixed TC/VC=00
Status: NegoPending- InProgress-
Capabilities: [180 v1] Root Complex Link
Desc: PortNumber=01 ComponentID=02 EltType=Config
Link0: Desc: TargetPort=00 TargetComponent=02 AssocRCRB-
LinkType=MemMapped LinkValid+
Addr: 00000000fed1c001
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2
(rev 01) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 4 bytes
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: fde00000-fdefffff
Prefetchable memory behind bridge: 00000000fdd00000-00000000fddfffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
unlimited, L1 unlimited
ExtTag- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+
TransPend-
LnkCap: Port #2, Speed 2.5GT/s, Width x1, ASPM L0s, Latency L0
<256ns, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive+ BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+
Surprise+
Slot #17, PowerLimit 10.000W; Interlock- NoCompl-
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+
Interlock-
Changed: MRL- PresDet+ LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna-
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0300c Data: 4169
Capabilities: [90] Subsystem: Giga-byte Technology Device 5001
Capabilities: [a0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed+ WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status: NegoPending- InProgress-
VC1: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable- ID=0 ArbSelect=Fixed TC/VC=00
Status: NegoPending- InProgress-
Capabilities: [180 v1] Root Complex Link
Desc: PortNumber=02 ComponentID=02 EltType=Config
Link0: Desc: TargetPort=00 TargetComponent=02 AssocRCRB-
LinkType=MemMapped LinkValid+
Addr: 00000000fed1c001
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI
Controller #1 (rev 01) (prog-if 00 [UHCI])
Subsystem: Giga-byte Technology Device 5004
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 23
Region 4: I/O ports at fe00 [size=32]
Kernel driver in use: uhci_hcd
00:1d.1 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI
Controller #2 (rev 01) (prog-if 00 [UHCI])
Subsystem: Giga-byte Technology Device 5004
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 19
Region 4: I/O ports at fd00 [size=32]
Kernel driver in use: uhci_hcd
00:1d.2 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI
Controller #3 (rev 01) (prog-if 00 [UHCI])
Subsystem: Giga-byte Technology Device 5004
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin C routed to IRQ 18
Region 4: I/O ports at fc00 [size=32]
Kernel driver in use: uhci_hcd
00:1d.3 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI
Controller #4 (rev 01) (prog-if 00 [UHCI])
Subsystem: Giga-byte Technology Device 5004
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin D routed to IRQ 16
Region 4: I/O ports at fb00 [size=32]
Kernel driver in use: uhci_hcd
00:1d.7 USB controller: Intel Corporation N10/ICH 7 Family USB2 EHCI
Controller (rev 01) (prog-if 20 [EHCI])
Subsystem: Giga-byte Technology Device 5006
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 23
Region 0: Memory at fdfff000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1) (prog-if 01
[Subtractive decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=32
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: fdb00000-fdbfffff
Prefetchable memory behind bridge: 00000000fda00000-00000000fdafffff
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Subsystem: Giga-byte Technology GA-EP45-DS5
Motherboard
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC
Interface Bridge (rev 01)
Subsystem: Giga-byte Technology Device 5001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Capabilities: [e0] Vendor Specific Information: Len=0c <?>
Kernel driver in use: lpc_ich
Kernel modules: leds-ss4200, lpc_ich, intel-rng
00:1f.2 IDE interface: Intel Corporation N10/ICH7 Family SATA Controller
[IDE mode] (rev 01) (prog-if 80 [Master])
Subsystem: Giga-byte Technology Device b002
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx+
Latency: 0
Interrupt: pin B routed to IRQ 19
Region 0: I/O ports at 01f0 [size=8]
Region 1: I/O ports at 03f4 [size=1]
Region 2: I/O ports at 0170 [size=8]
Region 3: I/O ports at 0374 [size=1]
Region 4: I/O ports at f800 [size=16]
Capabilities: [70] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: ata_piix
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 01)
Subsystem: Giga-byte Technology GA-8I945PG-RH Mainboard
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin B routed to IRQ 11
Region 4: I/O ports at 0500 [size=32]
Kernel modules: i2c-i801
01:00.0 Ethernet controller: Intel Corporation Device 1533 (rev 03)
Subsystem: Intel Corporation Device 0002
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 4 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at fd800000 (32-bit, non-prefetchable) [size=1M]
Region 3: Memory at fd9fc000 (32-bit, non-prefetchable) [size=16K]
[virtual] Expansion ROM at fd600000 [disabled] [size=1M]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Address: 0000000000000000 Data: 0000
Masking: 00000000 Pending: 00000000
Capabilities: [70] MSI-X: Enable+ Count=5 Masked-
Vector table: BAR=3 offset=00000000
PBA: BAR=3 offset=00002000
Capabilities: [a0] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <512ns,
L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+
DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+
Unsupported+
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency
L0 <2us, L1 <16us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Range ABCD, TimeoutDis+
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-,
Selectable De-emphasis: -6dB
Transmit Margin: Normal Operating Range,
EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB
Capabilities: [100 v2] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF-
MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF-
MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+
MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [140 v1] Device Serial Number a0-36-9f-ff-ff-1c-dc-4b
Capabilities: [1a0 v1] Transaction Processing Hints
Device specific mode supported
Steering table in TPH capability structure
Kernel driver in use: igb
Kernel modules: igb
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B
PCI Express Gigabit Ethernet controller (rev 02)
Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 4 bytes
Interrupt: pin A routed to IRQ 42
Region 0: I/O ports at be00 [size=256]
Region 2: Memory at fddff000 (64-bit, prefetchable) [size=4K]
Region 4: Memory at fdde0000 (64-bit, prefetchable) [size=64K]
[virtual] Expansion ROM at fdd00000 [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+
Address: 00000000fee0200c Data: 4171
Capabilities: [70] Express (v1) Endpoint, MSI 01
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns,
L1 <8us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 4096 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency
L0 <512ns, L1 <64us
ClockPM+ Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
Capabilities: [b0] MSI-X: Enable- Count=2 Masked-
Vector table: BAR=4 offset=00000000
PBA: BAR=4 offset=00000800
Capabilities: [d0] Vital Product Data
Unknown small resource type 00, will not decode more.
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF-
MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF-
MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+
MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr+ BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [140 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
Capabilities: [160 v1] Device Serial Number 12-34-56-78-12-34-56-78
Kernel driver in use: r8169
Kernel modules: r8169
03:00.0 Ethernet controller: D-Link System Inc DGE-530T Gigabit Ethernet
Adapter (rev 11) (rev 11)
Subsystem: D-Link System Inc DGE-530T Gigabit Ethernet Adapter (rev 11)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (5750ns min, 7750ns max), Cache Line Size: 4 bytes
Interrupt: pin A routed to IRQ 20
Region 0: Memory at fdbfc000 (32-bit, non-prefetchable) [size=16K]
Region 1: I/O ports at de00 [size=256]
[virtual] Expansion ROM at fda00000 [disabled] [size=128K]
Capabilities: [48] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [50] Vital Product Data
Product Name: DGE-530T Gigabit Ethernet Adapter
Read-only fields:
[PN] Part number: DGE-530T
[EC] Engineering changes: Rev. 1.1
[MN] Manufacture ID: 44 2d 4c 69 6e 6b
[SN] Serial number: DGE530T70E359
[CP] Extended capability: 01 10 cc 03
[RV] Reserved: checksum good, 31 byte(s) reserved
Read/write fields:
[RW] Read-write area: 121 byte(s) free
End
Kernel driver in use: skge
Kernel modules: skge
*#uname -a*
uname -a
Linux vvdnovs 3.5.0 #3 SMP Wed Sep 4 14:21:03 IST 2013 i686 i686 i386
GNU/Linux
On Thu, Sep 5, 2013 at 11:20 PM, Vick, Matthew <mat...@in...>wrote:
> Aman,
>
> We will need some more information before we can help you out with your
> problem. Can you please provide the output from the following commands?
> # dmesg
> # lspci -vvv
> $ uname -a
>
> Also, please provide some additional details about your configuration,
> steps to reproduce the issue, etc.
>
> Which device are you seeing this on?
>
> Cheers,
> Matthew
>
> Matthew Vick
> Linux Development
> Networking Division
> Intel Corporation
>
> From: Aman Sharma <ama...@gm...>
> Date: Wednesday, September 4, 2013 8:42 PM
> To: Jacob E Keller <jac...@in...>
> Cc: "lin...@li..." <
> lin...@li...>
> Subject: Re: [Linuxptp-users] Issue in running gPTP
>
> Hi Jacob/Suresh,
>
>
> Thanks for your reply.
> Now its working fine.Actually hardware clock is disabled in kernel.
>
> But now I am getting one more error message i.e.
>
> igb: eth4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
> [67378.092992] r8169 0000:02:00.0: eth0: link up
> [67379.993212] igb 0000:01:00.0: Detected Tx Unit Hang
> [67379.993212] Tx Queue <0>
> [67379.993212] TDH <0>
> [67379.993212] TDT <1>
> [67379.993212] next_to_use <1>
> [67379.993212] next_to_clean <0>
> [67379.993212] buffer_info[next_to_clean]
> [67379.993212] time_stamp <ffe28e>
> [67379.993212] next_to_watch <ed7e4000>
> [67379.993212] jiffies <ffe3ce>
> [67379.993212] desc.status <a8000>
> buffer_info[next_to_clean]
> [67410.993266] time_stamp <10000fc>
> [67410.993266] next_to_watch <ed7e4000>
> [67410.993266] jiffies <1000214>
> [67410.993266] desc.status <a8000>
> [67412.992265] igb 0000:01:00.0: Detected Tx Unit Hang
> [67412.992265] Tx Queue <0>
> [67412.992265] TDH <0>
> [67412.992265] TDT <1>
> [67412.992265] next_to_use <1>
> [67412.992265] next_to_clean <0>
> [67412.992265] buffer_info[next_to_clean]
> [67412.992265] time_stamp <10000fc>
> [67412.992265] next_to_watch <ed7e4000>
> [67412.992265] jiffies <1000408>
> [67412.992265] desc.status <a8000>
> [67414.992274] igb 0000:01:00.0: Detected Tx Unit Hang
> [67414.992274] Tx Queue <0>
> [67414.992274] TDH <0>
> [67414.992274] TDT <1>
> [67414.992274] next_to_use <1>
> [67414.992274] next_to_clean <0>
> [67414.992274] buffer_info[next_to_clean]
> [67414.992274] time_stamp <10000fc>
> [67414.992274] next_to_watch <ed7e4000>
> [67414.992274] jiffies <10005fc>
> [67414.992274] desc.status <a8000>
>
>
> Can you Please check this.
>
> --
> With Regards
> Aman Sharma
>
>
> On Wed, Sep 4, 2013 at 11:02 PM, Keller, Jacob E <jac...@in...
> > wrote:
>
>> Hello,
>>
>> Aman mentioned in his email that he already did enable PTP in the
>> kernel...
>>
>> Aman,
>>
>> Did you install the driver from sourceforge? or are you using the
>> in-kernel driver?
>>
>> If you are using the sourceforge driver you need to compile it with
>> "CFLAGS_EXTRA=-DIGB_PTP make" instead of the normal "make". This is
>> because PTP is not enabled in the source forge driver by default..
>>
>> Also, unsure if its true for igb, but for ixgbe I know that you have to
>> get link up before PTP devices will appear...
>>
>> Thanks,
>> Jake
>>
>> On Wed, 2013-09-04 at 05:53 +0000, sur...@wi... wrote:
>> > Hi Amar,
>> >
>> > Enable PTP and PPS while compiling the kernel and try it out
>> >
>> >
>> >
>> > Thanks and Regards
>> > Suresh
>> >
>> > ______________________________________________________________________
>> > From: Aman Sharma [ama...@gm...]
>> > Sent: Wednesday, September 04, 2013 10:06 AM
>> > To: lin...@li...
>> > Subject: [Linuxptp-users] Issue in running gPTP
>> >
>> >
>> >
>> > Hi All,
>> >
>> >
>> >
>> >
>> > We want to run linuxPTP with intel i210 NIC cards.For this , We
>> > compiled the linux kernel with version 3.5.0 and enabled PTP in it and
>> > also installed igb driver in the machine.But when running linuxPTP
>> > with command:
>> >
>> >
>> > ./ptp4l -f gPTP.cfg -i eth4
>> >
>> >
>> > then it shows message PTP device is not specified and automatic
>> > determination is not supported.Please specify PTP device .
>> >
>> >
>> > But when I check for PTP device in the folder /dev/ , there is no PTP
>> > device specified.
>> >
>> >
>> > Can anyone Please help me in this.
>> >
>> >
>> > Thanks for your help in advance.
>> >
>> >
>> > regards
>> > Aman
>> >
>> ------------------------------------------------------------------------------
>> > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
>> > Discover the easy way to master current and previous Microsoft
>> technologies
>> > and advance your career. Get an incredible 1,500+ hours of step-by-step
>> > tutorial videos with LearnDevNow. Subscribe today and save!
>> >
>> http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
>> > _______________________________________________
>> > Linuxptp-users mailing list
>> > Lin...@li...
>> > https://lists.sourceforge.net/lists/listinfo/linuxptp-users
>>
>>
>
|
|
From: Vick, M. <mat...@in...> - 2013-09-05 17:51:07
|
Aman, We will need some more information before we can help you out with your problem. Can you please provide the output from the following commands? # dmesg # lspci -vvv $ uname -a Also, please provide some additional details about your configuration, steps to reproduce the issue, etc. Which device are you seeing this on? Cheers, Matthew Matthew Vick Linux Development Networking Division Intel Corporation From: Aman Sharma <ama...@gm...<mailto:ama...@gm...>> Date: Wednesday, September 4, 2013 8:42 PM To: Jacob E Keller <jac...@in...<mailto:jac...@in...>> Cc: "lin...@li...<mailto:lin...@li...>" <lin...@li...<mailto:lin...@li...>> Subject: Re: [Linuxptp-users] Issue in running gPTP Hi Jacob/Suresh, Thanks for your reply. Now its working fine.Actually hardware clock is disabled in kernel. But now I am getting one more error message i.e. igb: eth4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [67378.092992] r8169 0000:02:00.0: eth0: link up [67379.993212] igb 0000:01:00.0: Detected Tx Unit Hang [67379.993212] Tx Queue <0> [67379.993212] TDH <0> [67379.993212] TDT <1> [67379.993212] next_to_use <1> [67379.993212] next_to_clean <0> [67379.993212] buffer_info[next_to_clean] [67379.993212] time_stamp <ffe28e> [67379.993212] next_to_watch <ed7e4000> [67379.993212] jiffies <ffe3ce> [67379.993212] desc.status <a8000> buffer_info[next_to_clean] [67410.993266] time_stamp <10000fc> [67410.993266] next_to_watch <ed7e4000> [67410.993266] jiffies <1000214> [67410.993266] desc.status <a8000> [67412.992265] igb 0000:01:00.0: Detected Tx Unit Hang [67412.992265] Tx Queue <0> [67412.992265] TDH <0> [67412.992265] TDT <1> [67412.992265] next_to_use <1> [67412.992265] next_to_clean <0> [67412.992265] buffer_info[next_to_clean] [67412.992265] time_stamp <10000fc> [67412.992265] next_to_watch <ed7e4000> [67412.992265] jiffies <1000408> [67412.992265] desc.status <a8000> [67414.992274] igb 0000:01:00.0: Detected Tx Unit Hang [67414.992274] Tx Queue <0> [67414.992274] TDH <0> [67414.992274] TDT <1> [67414.992274] next_to_use <1> [67414.992274] next_to_clean <0> [67414.992274] buffer_info[next_to_clean] [67414.992274] time_stamp <10000fc> [67414.992274] next_to_watch <ed7e4000> [67414.992274] jiffies <10005fc> [67414.992274] desc.status <a8000> Can you Please check this. -- With Regards Aman Sharma On Wed, Sep 4, 2013 at 11:02 PM, Keller, Jacob E <jac...@in...<mailto:jac...@in...>> wrote: Hello, Aman mentioned in his email that he already did enable PTP in the kernel... Aman, Did you install the driver from sourceforge? or are you using the in-kernel driver? If you are using the sourceforge driver you need to compile it with "CFLAGS_EXTRA=-DIGB_PTP make" instead of the normal "make". This is because PTP is not enabled in the source forge driver by default.. Also, unsure if its true for igb, but for ixgbe I know that you have to get link up before PTP devices will appear... Thanks, Jake On Wed, 2013-09-04 at 05:53 +0000, sur...@wi...<mailto:sur...@wi...> wrote: > Hi Amar, > > Enable PTP and PPS while compiling the kernel and try it out > > > > Thanks and Regards > Suresh > > ______________________________________________________________________ > From: Aman Sharma [ama...@gm...<mailto:ama...@gm...>] > Sent: Wednesday, September 04, 2013 10:06 AM > To: lin...@li...<mailto:lin...@li...> > Subject: [Linuxptp-users] Issue in running gPTP > > > > Hi All, > > > > > We want to run linuxPTP with intel i210 NIC cards.For this , We > compiled the linux kernel with version 3.5.0 and enabled PTP in it and > also installed igb driver in the machine.But when running linuxPTP > with command: > > > ./ptp4l -f gPTP.cfg -i eth4 > > > then it shows message PTP device is not specified and automatic > determination is not supported.Please specify PTP device . > > > But when I check for PTP device in the folder /dev/ , there is no PTP > device specified. > > > Can anyone Please help me in this. > > > Thanks for your help in advance. > > > regards > Aman > ------------------------------------------------------------------------------ > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk > _______________________________________________ > Linuxptp-users mailing list > Lin...@li...<mailto:Lin...@li...> > https://lists.sourceforge.net/lists/listinfo/linuxptp-users |
|
From: Aman S. <ama...@gm...> - 2013-09-05 03:42:35
|
Hi Jacob/Suresh, Thanks for your reply. Now its working fine.Actually hardware clock is disabled in kernel. But now I am getting one more error message i.e. igb: eth4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [67378.092992] r8169 0000:02:00.0: eth0: link up [67379.993212] igb 0000:01:00.0: Detected Tx Unit Hang [67379.993212] Tx Queue <0> [67379.993212] TDH <0> [67379.993212] TDT <1> [67379.993212] next_to_use <1> [67379.993212] next_to_clean <0> [67379.993212] buffer_info[next_to_clean] [67379.993212] time_stamp <ffe28e> [67379.993212] next_to_watch <ed7e4000> [67379.993212] jiffies <ffe3ce> [67379.993212] desc.status <a8000> buffer_info[next_to_clean] [67410.993266] time_stamp <10000fc> [67410.993266] next_to_watch <ed7e4000> [67410.993266] jiffies <1000214> [67410.993266] desc.status <a8000> [67412.992265] igb 0000:01:00.0: Detected Tx Unit Hang [67412.992265] Tx Queue <0> [67412.992265] TDH <0> [67412.992265] TDT <1> [67412.992265] next_to_use <1> [67412.992265] next_to_clean <0> [67412.992265] buffer_info[next_to_clean] [67412.992265] time_stamp <10000fc> [67412.992265] next_to_watch <ed7e4000> [67412.992265] jiffies <1000408> [67412.992265] desc.status <a8000> [67414.992274] igb 0000:01:00.0: Detected Tx Unit Hang [67414.992274] Tx Queue <0> [67414.992274] TDH <0> [67414.992274] TDT <1> [67414.992274] next_to_use <1> [67414.992274] next_to_clean <0> [67414.992274] buffer_info[next_to_clean] [67414.992274] time_stamp <10000fc> [67414.992274] next_to_watch <ed7e4000> [67414.992274] jiffies <10005fc> [67414.992274] desc.status <a8000> Can you Please check this. -- With Regards Aman Sharma On Wed, Sep 4, 2013 at 11:02 PM, Keller, Jacob E <jac...@in...>wrote: > Hello, > > Aman mentioned in his email that he already did enable PTP in the > kernel... > > Aman, > > Did you install the driver from sourceforge? or are you using the > in-kernel driver? > > If you are using the sourceforge driver you need to compile it with > "CFLAGS_EXTRA=-DIGB_PTP make" instead of the normal "make". This is > because PTP is not enabled in the source forge driver by default.. > > Also, unsure if its true for igb, but for ixgbe I know that you have to > get link up before PTP devices will appear... > > Thanks, > Jake > > On Wed, 2013-09-04 at 05:53 +0000, sur...@wi... wrote: > > Hi Amar, > > > > Enable PTP and PPS while compiling the kernel and try it out > > > > > > > > Thanks and Regards > > Suresh > > > > ______________________________________________________________________ > > From: Aman Sharma [ama...@gm...] > > Sent: Wednesday, September 04, 2013 10:06 AM > > To: lin...@li... > > Subject: [Linuxptp-users] Issue in running gPTP > > > > > > > > Hi All, > > > > > > > > > > We want to run linuxPTP with intel i210 NIC cards.For this , We > > compiled the linux kernel with version 3.5.0 and enabled PTP in it and > > also installed igb driver in the machine.But when running linuxPTP > > with command: > > > > > > ./ptp4l -f gPTP.cfg -i eth4 > > > > > > then it shows message PTP device is not specified and automatic > > determination is not supported.Please specify PTP device . > > > > > > But when I check for PTP device in the folder /dev/ , there is no PTP > > device specified. > > > > > > Can anyone Please help me in this. > > > > > > Thanks for your help in advance. > > > > > > regards > > Aman > > > ------------------------------------------------------------------------------ > > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > > Discover the easy way to master current and previous Microsoft > technologies > > and advance your career. Get an incredible 1,500+ hours of step-by-step > > tutorial videos with LearnDevNow. Subscribe today and save! > > > http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk > > _______________________________________________ > > Linuxptp-users mailing list > > Lin...@li... > > https://lists.sourceforge.net/lists/listinfo/linuxptp-users > > |
|
From: Keller, J. E <jac...@in...> - 2013-09-04 17:32:29
|
Hello, Aman mentioned in his email that he already did enable PTP in the kernel... Aman, Did you install the driver from sourceforge? or are you using the in-kernel driver? If you are using the sourceforge driver you need to compile it with "CFLAGS_EXTRA=-DIGB_PTP make" instead of the normal "make". This is because PTP is not enabled in the source forge driver by default.. Also, unsure if its true for igb, but for ixgbe I know that you have to get link up before PTP devices will appear... Thanks, Jake On Wed, 2013-09-04 at 05:53 +0000, sur...@wi... wrote: > Hi Amar, > > Enable PTP and PPS while compiling the kernel and try it out > > > > Thanks and Regards > Suresh > > ______________________________________________________________________ > From: Aman Sharma [ama...@gm...] > Sent: Wednesday, September 04, 2013 10:06 AM > To: lin...@li... > Subject: [Linuxptp-users] Issue in running gPTP > > > > Hi All, > > > > > We want to run linuxPTP with intel i210 NIC cards.For this , We > compiled the linux kernel with version 3.5.0 and enabled PTP in it and > also installed igb driver in the machine.But when running linuxPTP > with command: > > > ./ptp4l -f gPTP.cfg -i eth4 > > > then it shows message PTP device is not specified and automatic > determination is not supported.Please specify PTP device . > > > But when I check for PTP device in the folder /dev/ , there is no PTP > device specified. > > > Can anyone Please help me in this. > > > Thanks for your help in advance. > > > regards > Aman > ------------------------------------------------------------------------------ > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk > _______________________________________________ > Linuxptp-users mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxptp-users |
|
From: Richard C. <ric...@gm...> - 2013-09-04 16:01:51
|
On Wed, Sep 04, 2013 at 10:06:34AM +0530, Aman Sharma wrote: > Hi All, > > > We want to run linuxPTP with intel i210 NIC cards.For this , We compiled > the linux kernel with version 3.5.0 and enabled PTP in it and also > installed igb driver in the machine.But when running linuxPTP with command: > > *./ptp4l -f gPTP.cfg -i eth4* > > then it shows message PTP device is not specified and automatic > determination is not supported.Please specify PTP device . > > But when I check for PTP device in the folder /dev/ , there is no PTP > device specified. > > Can anyone Please help me in this. Maybe you are not running the kernel that you think? Show us the output of: uname -a dmesg lsmod cat /proc/devices ./ptp4l -f gPTP.cfg -i eth4 Thanks, Richard |
|
From: Miroslav L. <mli...@re...> - 2013-09-04 08:29:31
|
On Wed, Sep 04, 2013 at 07:41:32AM +0000, Ledda William EXT wrote: > Hi all, > I have seen from the source code that it is possible to collect and logs some statistics information about the offset, the delay and some other parameter with ptp4l and phc2sys, but to enable this statistics the max_count value of the stats field of the clock structure must be > 1. I can't find any command line option to set this max_count. Do I have to modify the source code or there is some option that I'm missing? > > I'm using version 1.2, I haven't tried with 1.3. It's set by the summary_interval option for ptp4l and the -u option for phc2sys. For example, to print the statistics every 64 seconds, set summary_interval to 6. -- Miroslav Lichvar |
|
From: Ledda W. E. <Wil...@it...> - 2013-09-04 07:41:41
|
Hi all, I have seen from the source code that it is possible to collect and logs some statistics information about the offset, the delay and some other parameter with ptp4l and phc2sys, but to enable this statistics the max_count value of the stats field of the clock structure must be > 1. I can't find any command line option to set this max_count. Do I have to modify the source code or there is some option that I'm missing? I'm using version 1.2, I haven't tried with 1.3. Thanks William |
|
From: Aman S. <ama...@gm...> - 2013-09-04 07:19:41
|
Hi Suresh, Actually both PTP and PPS are already enabled. Thanks for your reply. Thanks Aman On Wed, Sep 4, 2013 at 11:23 AM, <sur...@wi...> wrote: > Hi Amar, > > Enable PTP and PPS while compiling the kernel and try it out > > > > Thanks and Regards > Suresh > ------------------------------ > *From:* Aman Sharma [ama...@gm...] > *Sent:* Wednesday, September 04, 2013 10:06 AM > *To:* lin...@li... > *Subject:* [Linuxptp-users] Issue in running gPTP > > Hi All, > > > We want to run linuxPTP with intel i210 NIC cards.For this , We compiled > the linux kernel with version 3.5.0 and enabled PTP in it and also > installed igb driver in the machine.But when running linuxPTP with command: > > *./ptp4l -f gPTP.cfg -i eth4* > > then it shows message PTP device is not specified and automatic > determination is not supported.Please specify PTP device . > > But when I check for PTP device in the folder /dev/ , there is no PTP > device specified. > > Can anyone Please help me in this. > > Thanks for your help in advance. > > regards > Aman > > The information contained in this electronic message and any attachments > to this message are intended for the exclusive use of the addressee(s) and > may contain proprietary, confidential or privileged information. If you are > not the intended recipient, you should not disseminate, distribute or copy > this e-mail. Please notify the sender immediately and destroy all copies of > this message and any attachments. > > WARNING: Computer viruses can be transmitted via email. The recipient > should check this email and any attachments for the presence of viruses. > The company accepts no liability for any damage caused by any virus > transmitted by this email. > > www.wipro.com > > The information contained in this electronic message and any attachments > to this message are intended for the exclusive use of the addressee(s) and > may contain proprietary, confidential or privileged information. If you are > not the intended recipient, you should not disseminate, distribute or copy > this e-mail. Please notify the sender immediately and destroy all copies of > this message and any attachments. > > WARNING: Computer viruses can be transmitted via email. The recipient > should check this email and any attachments for the presence of viruses. > The company accepts no liability for any damage caused by any virus > transmitted by this email. > > www.wipro.com > |
|
From: <sur...@wi...> - 2013-09-04 05:54:13
|
Hi Amar, Enable PTP and PPS while compiling the kernel and try it out Thanks and Regards Suresh ________________________________ From: Aman Sharma [ama...@gm...] Sent: Wednesday, September 04, 2013 10:06 AM To: lin...@li... Subject: [Linuxptp-users] Issue in running gPTP Hi All, We want to run linuxPTP with intel i210 NIC cards.For this , We compiled the linux kernel with version 3.5.0 and enabled PTP in it and also installed igb driver in the machine.But when running linuxPTP with command: ./ptp4l -f gPTP.cfg -i eth4 then it shows message PTP device is not specified and automatic determination is not supported.Please specify PTP device . But when I check for PTP device in the folder /dev/ , there is no PTP device specified. Can anyone Please help me in this. Thanks for your help in advance. regards Aman |
|
From: Aman S. <ama...@gm...> - 2013-09-04 04:36:43
|
Hi All, We want to run linuxPTP with intel i210 NIC cards.For this , We compiled the linux kernel with version 3.5.0 and enabled PTP in it and also installed igb driver in the machine.But when running linuxPTP with command: *./ptp4l -f gPTP.cfg -i eth4* then it shows message PTP device is not specified and automatic determination is not supported.Please specify PTP device . But when I check for PTP device in the folder /dev/ , there is no PTP device specified. Can anyone Please help me in this. Thanks for your help in advance. regards Aman |
|
From: Richard C. <ric...@gm...> - 2013-08-30 17:16:41
|
On Fri, Aug 30, 2013 at 02:46:35PM +0000, sur...@wi... wrote: > > Linuxptp web tells that davinci TI board is supported. > http://linuxptp.sourceforge.net/ > --------------------------------------------------------------------------- > davinci_emac TI DaVinci, Sitara SW N Y 3.1 ^^ This means that software time stamping is supported. And, as Delio said, this support is in the emac driver. There is mainline kernel support for the PTP capabilities of the cpsw/cpts, but only for the am33xx. I can't really help you with your vendor kernel. Sorry, Richard |
|
From: Delio B. <dbr...@au...> - 2013-08-30 15:32:09
|
On Aug 30, 2013, at 4:51 PM, <sur...@wi...> wrote: > SOC > DAVINCI > TI81xx Yes, but what are the "xx"? ;-) > kernel-2.6.37 This does not help me knowing which kernel you are using, but then I saw your forum post. See below. From your other email: > We are refering to this website where it is suggested to use linuxptp for TI boards > > http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/p/204024/859216.aspx#859216 Oh I see, you were talking about TI's forum. > Linuxptp web tells that davinci TI board is supported. > http://linuxptp.sourceforge.net/ > --------------------------------------------------------------------------- > davinci_emac TI DaVinci, Sitara SW N Y 3.1 > ---------------------------------------------------------------------------- AFAIK TI81XX SoCs (the 'DaVinci' name on those is misleading) do not use the davinci_emac driver, rather they use the cpsw driver. From your forum post I see you are using a kernel from ezsdk 5_05_02_00. I cannot be sure without downloading/unpacking and checking, but I suspect the timestamping in the cpsw driver shipped with that kernel does not work well. You may want to try this repo <http://arago-project.org/git/projects/linux-omap3.git> (branch ti81xx-master), it *may* work better. HTH -- Delio > ________________________________________ > From: Delio Brignoli [dbr...@au...] > Sent: Friday, August 30, 2013 7:19 PM > To: Suresh Udipi (WT01 - PES) > Cc: lin...@li... > Subject: Re: [Linuxptp-users] PTP on Davinci(TI81xx) > > Hi Suresh, > > On Aug 30, 2013, at 2:51 PM, <sur...@wi...> wrote: > >> Hi, >> >> We are trying to bring up linuxptp on Ti81xx board (Davinci) board > > Which SoC is it exactly and which kernel (compiled from which source repository/branch) are you using? > >> In the wiki it is mentioned that it is already been tested and working on Davinci/Sitara... > > What are the URLs of the relevant wiki pages? > >> But we are not able to bring it up. >> >> Please let us know the usage of the ptp binaries on this boards. > > [...] > >> On client side we are getting the error >> port 1: received SYNC without timestamp >> ptp4l[1473.607]: port 1: bad message >> >> >> Server is able to send the Anounce /SYNC / Follow UP message. But client is not responding..?/ >> >> Is the usage of ptp is correct? > > linuxptp's command line options look OK to me (of course that depends on what you are trying to do). There is a problem with packet timestamping though. > > Regards > -- > Delio > > |
|
From: <sur...@wi...> - 2013-08-30 14:55:13
|
SOC DAVINCI TI81xx kernel-2.6.37 ________________________________________ From: Delio Brignoli [dbr...@au...] Sent: Friday, August 30, 2013 7:19 PM To: Suresh Udipi (WT01 - PES) Cc: lin...@li... Subject: Re: [Linuxptp-users] PTP on Davinci(TI81xx) Hi Suresh, On Aug 30, 2013, at 2:51 PM, <sur...@wi...> wrote: > Hi, > > We are trying to bring up linuxptp on Ti81xx board (Davinci) board Which SoC is it exactly and which kernel (compiled from which source repository/branch) are you using? > In the wiki it is mentioned that it is already been tested and working on Davinci/Sitara... What are the URLs of the relevant wiki pages? > But we are not able to bring it up. > > Please let us know the usage of the ptp binaries on this boards. [...] > On client side we are getting the error > port 1: received SYNC without timestamp > ptp4l[1473.607]: port 1: bad message > > > Server is able to send the Anounce /SYNC / Follow UP message. But client is not responding..?/ > > Is the usage of ptp is correct? linuxptp's command line options look OK to me (of course that depends on what you are trying to do). There is a problem with packet timestamping though. Regards -- Delio |
|
From: <sur...@wi...> - 2013-08-30 14:49:05
|
Hi, We are refering to this website where it is suggested to use linuxptp for TI boards http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/p/204024/859216.aspx#859216 Linuxptp web tells that davinci TI board is supported. http://linuxptp.sourceforge.net/ --------------------------------------------------------------------------- davinci_emac TI DaVinci, Sitara SW N Y 3.1 ---------------------------------------------------------------------------- We are trying to sync the PTP clock on boards. Thanks and Regards Suresh ________________________________________ From: Delio Brignoli [dbr...@au...] Sent: Friday, August 30, 2013 7:19 PM To: Suresh Udipi (WT01 - PES) Cc: lin...@li... Subject: Re: [Linuxptp-users] PTP on Davinci(TI81xx) Hi Suresh, On Aug 30, 2013, at 2:51 PM, <sur...@wi...> wrote: > Hi, > > We are trying to bring up linuxptp on Ti81xx board (Davinci) board Which SoC is it exactly and which kernel (compiled from which source repository/branch) are you using? > In the wiki it is mentioned that it is already been tested and working on Davinci/Sitara... What are the URLs of the relevant wiki pages? > But we are not able to bring it up. > > Please let us know the usage of the ptp binaries on this boards. [...] > On client side we are getting the error > port 1: received SYNC without timestamp > ptp4l[1473.607]: port 1: bad message > > > Server is able to send the Anounce /SYNC / Follow UP message. But client is not responding..?/ > > Is the usage of ptp is correct? linuxptp's command line options look OK to me (of course that depends on what you are trying to do). There is a problem with packet timestamping though. Regards -- Delio |
27 messages has been excluded from this view by a project administrator.
