Date: Fri, 09 Jul 2010 15:55:34 +0300 From: Shtorm <admin@shtorm.com> To: Mike Tancsa <mike@sentex.net> Cc: freebsd-net@freebsd.org Subject: Re: Intel 82574L Gigabit Ethernet Controller Message-ID: <1278680134.20612.21.camel@stormi-desktop> In-Reply-To: <AANLkTimJXKSm0tTljQx-csIId5NcuQme0fTU-Os-uIMn@mail.gmail.com> References: <1278330234.10826.18.camel@stormi-desktop> <AANLkTinePfVRKHdd5FHXEA1YXW9NvDo8mz48hoBgkZ9c@mail.gmail.com> <1278356796.10826.35.camel@stormi-desktop> <AANLkTilVYjuRGtE3gtcRhxIS4FBEAkiBqEPcxCgBh2Hk@mail.gmail.com> <1278404933.20433.26.camel@stormi-desktop> <AANLkTildoiVeA47P47wo027BI5NlppOCNgrV56O-cGaW@mail.gmail.com> <1278496982.21743.50.camel@stormi-desktop> <201007071336.o67DaaNZ031733@lava.sentex.ca> <AANLkTimJXKSm0tTljQx-csIId5NcuQme0fTU-Os-uIMn@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2010-07-07 at 09:22 -0700, Jack Vogel wrote: > Interesting, didn't know any vendor had combined PCH and 82574 on one board, > yes, they are > completely different, as you can see the one only supports MSI, its a client > NIC. > > I would agree with Mike, disable anything having to do with IPMI if it > exists and see if that > helps. Also you did not comment on the flow control setting, how about > turning that on? > > Jack Flow control does not matter, I have timeouts with and without them. I've updated bios to latest version, all IPMI stuff was already disabled - we do not use it anyway. If it matters, motherboard have dedicated ethernet port for IPMI. Log shows watchdog timeouts from em0 and em1. Jul 8 07:22:26 <kern.crit> server kernel: em1: Watchdog timeout -- resetting Jul 8 07:22:26 <kern.notice> server kernel: em1: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1028: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1020: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1005: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1029: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1021: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1004: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1030: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1022: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1007: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1031: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1023: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1006: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1024: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1016: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1001: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1025: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1017: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1000: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1026: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1018: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1003: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1027: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1019: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1002: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1012: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1013: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1014: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1015: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1032: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1008: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1033: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1009: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1010: link state changed to DOWN Jul 8 07:22:26 <kern.notice> server kernel: vlan1011: link state changed to DOWN Jul 8 07:22:30 <kern.notice> server kernel: em1: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1028: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1020: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1005: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1029: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1021: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1004: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1030: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1022: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1007: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1031: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1023: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1006: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1024: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1016: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1001: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1025: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1017: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1000: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1026: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1018: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1003: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1027: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1019: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1002: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1012: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1013: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1014: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1015: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1032: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1008: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1033: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1009: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1010: link state changed to UP Jul 8 07:22:30 <kern.notice> server kernel: vlan1011: link state changed to UP Jul 8 07:23:40 <kern.crit> server kernel: em0: Watchdog timeout -- resetting Jul 8 07:23:40 <kern.notice> server kernel: em0: link state changed to DOWN Jul 8 07:23:43 <kern.notice> server kernel: em0: link state changed to UP Jul 8 07:23:56 <ntp.crit> server ntpd[3687]: 2 out of 3 peers valid Jul 8 07:23:56 <ntp.crit> server ntpd[3687]: bad peer from pool pool.ntp.org (195.214.215.17) Jul 8 07:27:15 <kern.crit> server kernel: em0: Watchdog timeout -- resetting Jul 8 07:27:15 <kern.notice> server kernel: em0: link state changed to DOWN Jul 8 07:27:18 <kern.notice> server kernel: em0: link state changed to UP > > > On Wed, Jul 7, 2010 at 6:36 AM, Mike Tancsa <mike@sentex.net> wrote: > > > At 06:03 AM 7/7/2010, Shtorm wrote: > > > > > Yow, 30 vlans, but only em1 is using vlans not em0? > >> > > >> > Is only em1 having watchdogs? I noticed you appear to > >> > have flow control off, maybe turning it on would help. > >> > > >> > I would like to see the log messages from the watchdogs. > >> > Jack > >> > >> Yes, em0 - plain untagged traffic to border router, em1 - tagged - one > >> vlan per 200-300 pppoe clients. Anyway, I saw watchdogs on em0 too, > >> there is no logs for it because remote syslog server connected via em0 > >> and it looses messages during card reset, will enable local logs to get > >> some info. > >> > > > > I only have one board that has a pair of these NICs, but I noticed that in > > the BIOS, there is an option to enable or disable the Option ROM to do > > things like WOL, some sort of IPMI and other functions / features I am not > > familiar with and dont use. > > > > > > | |ROM for the onboard > > | > > | Maximize Memory below [Disabled] |network controllers. > > | > > | Memory Mapped I/O abo [Disabled] |Warning: If > > [Disabled] | > > | Onboard Video [Enabled] |is selected, NIC2 can > > | > > | Dual Monitor Video [Disabled] |not be used to boot > > or | > > | Onboard NIC1 ROM [Enabled] |wake the system. > > | > > | Onboard NIC2 ROM [Enabled] | > > | > > | Onboard NIC iSCSI ROM [Disabled] | > > | > > | | | > > | NIC1 MAC Address 001517C84B98 |>< Select Screen > > | > > | NIC2 MAC Address 001517C84B99 |^v Select Item > > | > > | |+/- Change Value > > | > > > > If you have such features, perhaps try disabling them in the BIOS ? > > > > On mine, the two nics dont come up the same... Not sure if their > > capabilities are the same even ? > > > > em2@pci0:0:25:0: class=0x020000 card=0x34ec8086 chip=0x10ef8086 > > rev=0x05 hdr=0x00 > > vendor = 'Intel Corporation' > > class = network > > subclass = ethernet > > cap 01[c8] = powerspec 2 supports D0 D3 current D0 > > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message > > cap 13[e0] = PCI Advanced Features: FLR TP > > > > > > em3@pci0:3:0:0: class=0x020000 card=0x34ec8086 chip=0x10d38086 rev=0x00 > > hdr=0x00 > > > > vendor = 'Intel Corporation' > > device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' > > class = network > > subclass = ethernet > > cap 01[c8] = powerspec 2 supports D0 D3 current D0 > > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message > > cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) > > cap 11[a0] = MSI-X supports 5 messages in map 0x1c > > > > em2: <Intel(R) PRO/1000 Network Connection 7.0.5> port 0x3040-0x305f mem > > 0xb1b00000-0xb1b1ffff,0xb1b25000-0xb1b25fff irq 16 at device 25.0 on pci0 > > em2: Using MSI interrupt > > em2: [FILTER] > > em2: Ethernet address: 00:15:17:c8:4b:99 > > > > em3: <Intel(R) PRO/1000 Network Connection 7.0.5> port 0x1000-0x101f mem > > 0xb1900000-0xb191ffff,0xb1920000-0xb1923fff irq 16 at device 0.0 on pci3 > > em3: Using MSI interrupt > > em3: [FILTER] > > em3: Ethernet address: 00:15:17:c8:4b:98 > > > > > > ---Mike > > > > > > -------------------------------------------------------------------- > > Mike Tancsa, tel +1 519 651 3400 > > Sentex Communications, mike@sentex.net > > Providing Internet since 1994 www.sentex.net > > Cambridge, Ontario Canada www.sentex.net/mike > > > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1278680134.20612.21.camel>