From owner-freebsd-current@FreeBSD.ORG Mon Jun 17 21:13:23 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5CC105CE; Mon, 17 Jun 2013 21:13:23 +0000 (UTC) (envelope-from kczekirda@gmail.com) Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by mx1.freebsd.org (Postfix) with ESMTP id C1E321FF2; Mon, 17 Jun 2013 21:13:22 +0000 (UTC) Received: by mail-wi0-f175.google.com with SMTP id m6so2777047wiv.2 for ; Mon, 17 Jun 2013 14:13:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WB/I4zn+lH4R070Quou2y4NbnaAas+e1H7Q6KXAmluM=; b=MC+6k5dSbnkQgXx7roUxquZju74cawwAs+spuKLp+9M5nbsxv4lw/AkefGYLWw6HLi GVZpemnI4Z/SX2D2YPJ6zdT0zGJOVktRyHPQjW4HexpD84vVMX+CcEQFZn/nkmsAfTHS hSf3sk9Ak3HC7vw+5eJbxd1X01SA9ZWnl1Z3A0OmVxETXoAeLJ0UqOL0ufra2zg05iVB Q5MbbDXoO8J1o6EmmykpXAM0rqM4VadnzJBK3S18VEDslRBX8PLOiZDQINzVTQQBGoke C5HeUzwiPq7sMnVMTe+vgBMewfiMz1zn87fZtUClKJpy3GNmo71s85zXqejqGu0iCAR+ KFUQ== MIME-Version: 1.0 X-Received: by 10.194.77.99 with SMTP id r3mr1030623wjw.5.1371503601971; Mon, 17 Jun 2013 14:13:21 -0700 (PDT) Received: by 10.194.121.226 with HTTP; Mon, 17 Jun 2013 14:13:21 -0700 (PDT) In-Reply-To: References: <201304291221.19725.jhb@freebsd.org> <201305090816.11525.jhb@freebsd.org> Date: Mon, 17 Jun 2013 23:13:21 +0200 Message-ID: Subject: Re: FreeBSD & Intel AMT From: Kamil Czekirda To: Jack Vogel Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jun 2013 21:13:23 -0000 When I switched on tso on debian AMT stopped too. 2013/5/27 Kamil Czekirda : > From observation: > > volt% amttool-tng k5 rem_control info > ## 'k5' :: AMT Remote Control > FAULT: 500 Can't connect to k5:16992 (Invalid argument) > (1) > > k5% sudo ifconfig em0 > em0: flags=8843 metric 0 mtu 1500 > options=4219b > ether e8:40:f2:ec:60:5e > inet 10.146.103.5 netmask 255.255.0.0 broadcast 10.146.255.255 > media: Ethernet autoselect (1000baseT ) > status: active > k5% sudo ifconfig em0 -tso4 > > Doesn't work immediately, but AMT starts to work. > > volt% amttool-tng k5 rem_control info > ## 'k5' :: AMT Remote Control > > FAULT: 500 Can't connect to k5:16992 (Invalid argument) > (1) > > volt% amttool-tng k5 rem_control info > ## 'k5' :: AMT Remote Control > # Remote Control Info :: AMT Remote Control > Powerstate: S0 > Watchdog Expired: No > Power Source: AC > Remote Control Capabilities: > Control Commands Supported powerCycle powerDown powerUp reset > IanaOemNumber 343 > Special Commands Supported PXE-boot HD-boot CD-boot > Special Commands (Oem) IDER SOL BiosReflash BiosSetup BiosPause > SystemFirmwareCapabilities LockKeyboard UserPasswordBypass > ForcedProgressEvents VerbosityVerbose VerbosityQuiet > VerbosityScreenBlank > > Is it normal? > > When KVM sesion is open network card works only on 10baseT standard. > You cannot change speed: > > k8% # ifconfig em0 media 1000baseT & > k8% # lo kernel -2 > May 25 01:01:14 k8 kernel: em0: Media change is blocked due to > SOL/IDER session. > May 25 01:02:16 k8 kernel: em0: Media change is blocked due to > SOL/IDER session. > > After closig KVM connection with VNC Viewer: > > k8% # ifconfig em0 media 1000baseT > k8% ifconfig em0 > em0: flags=8843 metric 0 mtu 1500 > options=4219b > inet 10.146.103.8 netmask 255.255.0.0 broadcast 10.146.255.255 > media: Ethernet 1000baseT (1000baseT ) > status: active > > And very important: after speed change AMT works fine. > > Any kind of reset network card makes AMT good, for example: > > ifconfig em0 -txcsum > > 2013/5/14 Kamil Czekirda : >> 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: port 0xf080-0xf09f mem >> 0xf7e00000-0xf7e1ffff, >> 0xf7e39000-0xf7e39fff irq 20 at d >> em1: 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 >>> >>> 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 >>> 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 >>>>> >>>>> 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 >>>>> > >>>>> > > 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 >>>> >>>> >>> >>