Date: Tue, 14 May 2013 08:38:10 +0200 From: Kamil Czekirda <kczekirda@gmail.com> To: Jack Vogel <jfvogel@gmail.com> Cc: Jack F Vogel <jfv@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: FreeBSD & Intel AMT Message-ID: <CADSgWNERBNb04wxESfif8fyATdi1=PTzDBC9hikj0XkQBT2kdw@mail.gmail.com> In-Reply-To: <CAFOYbcni395dLAjJM%2Bk9LudU3JzO%2BzOKKvgPLicx-K3EKwi7mg@mail.gmail.com> References: <CADSgWNGRRnuEz-gbFRcvzu=%2B%2BcAHB68EftLw7jwBPL2nC5o1Tw@mail.gmail.com> <201304291221.19725.jhb@freebsd.org> <CADSgWNH6=xE7BwJ5FmqzhovaHgZkUH%2B8ET4UUt918S0GQLnTxQ@mail.gmail.com> <201305090816.11525.jhb@freebsd.org> <CADSgWNGYbt5QQezaKusg=LrTxV_2YS9tvD-Xwm6-Ws=pTaCSzw@mail.gmail.com> <CAFOYbcni395dLAjJM%2Bk9LudU3JzO%2BzOKKvgPLicx-K3EKwi7mg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Motherboard: Intel DQ77KB, the latest BIOS & AMT fw. both ethernet interfaces connected, DHCP configured only the the first (managment) or only the second - the same result: after appr. 5 min ? AMT can't be accesed. (Same result on a few such a PCs which we have about ten in lab) FreeBSD: 9.1 amd64, SVN-updated and recompiled (kernel+world) on 11 May: if_em driver: em0: <Intel(R) PRO/1000 Network Connection 7.3.7> port 0xf080-0xf09f mem 0xf7e00000-0xf7e1ffff, 0xf7e39000-0xf7e39fff irq 20 at d em1: <Intel(R) PRO/1000 Network Connection 7.3.7> port 0xe000-0xe01f mem 0xf7c00000-0xf7c1ffff,0xf7c20000-0xf7c23fff irq 18 at d k1% uname -a FreeBSD k1 9.1-STABLE FreeBSD 9.1-STABLE #0: Sat May 11 23:22:00 CEST 2013 k1% biosver Version: KBQ7710H.86A.0049.2013.0130.1732 Release Date: 01/30/2013 smbios.bios.reldate="01/30/2013" smbios.bios.vendor="Intel Corp." smbios.bios.version="KBQ7710H.86A.0049.2013.0130.1732" smbios.chassis.maker=" " smbios.chassis.serial=" " smbios.chassis.tag=" " smbios.chassis.version=" " smbios.memory.enabled="4194304" smbios.planar.maker="Intel Corporation" smbios.planar.product="DQ77KB" smbios.planar.serial="BTKB22100SUJ" smbios.planar.version="AAG40294-401" smbios.socket.enabled="1" smbios.socket.populated="1" smbios.system.maker=" " smbios.system.product=" " smbios.system.serial=" " smbios.system.uuid="7fe1575d-31a4-e111-9b80-6431503407e9" smbios.system.version=" " smbios.version="2.7" k1% # lspci 00:00.0 Host bridge: Intel Corporation Ivy Bridge DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Ivy Bridge Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation Panther Point USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation Panther Point MEI Controller #1 (rev 04) 00:16.3 Serial controller: Intel Corporation Panther Point KT Controller (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation Panther Point High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 1 (rev c4) 00:1c.2 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 3 (rev c4) 00:1c.6 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 7 (rev c4) 00:1d.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #1 (rev 04) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4) 00:1f.0 ISA bridge: Intel Corporation Panther Point LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation Panther Point 6 port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation Panther Point SMBus Controller (rev 04) 02:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35) 03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection I can provide you all info, and ssh/vnc acces (with root) to this diskeless PCs if you prefer. 2013/5/14 Jack Vogel <jfvogel@gmail.com> > I need to know the details on the hardware this is on, and was it working > on some previous > version of FreeBSD and broke in STABLE or what? > > Jack > > > > On Mon, May 13, 2013 at 2:44 PM, Kamil Czekirda <kczekirda@gmail.com>wrote: > >> Jack, do you have any ideas to resolve problem, on new Debian 7 and >> Ubuntu 13.10 AMT working fine. >> >> >> 2013/5/9 John Baldwin <jhb@freebsd.org> >> >>> On Thursday, May 09, 2013 4:34:16 am Kamil Czekirda wrote: >>> > Do you have any ideas to resolve the problem? >>> >>> I have no idea what part of e1000 common code deals with AMT/IPMI and >>> what you >>> might need to do to make this work. I was hoping Jack would be be able to >>> respond here. >>> >>> > 2013/4/29 John Baldwin <jhb@freebsd.org> >>> > >>> > > On Friday, April 26, 2013 5:17:34 pm Kamil Czekirda wrote: >>> > > > We have a problem with Intel AMT and FreeBSD. We have AMT version: >>> > > > 8.1.20-build 1336. AMT stop responding about five minutes after >>> booting >>> > > > FreeBSD, it's FreeBSD 9.1-STABLE, 64 bit. >>> > > > On Linux AMT works fine. We suspect driver, but it's similar like >>> on >>> > > Linux. >>> > > > Can you show us the way to resolve this problem? >>> > > >>> > > While the e1000 drivers share the same common code, there are some >>> > > differences >>> > > in the OS-dependent bits (e.g. if_igb.c, etc.). I've cc'd Jack >>> Vogel who >>> > > maintains the e1000 drivers in FreeBSD. >>> > > >>> > > -- >>> > > John Baldwin >>> > > >>> > >>> >>> -- >>> John Baldwin >>> >> >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADSgWNERBNb04wxESfif8fyATdi1=PTzDBC9hikj0XkQBT2kdw>