From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by ml01.01.org (Postfix) with ESMTP id B84561A1DF5 for ; Thu, 11 Aug 2016 17:19:42 -0700 (PDT) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 11 Aug 2016 17:19:42 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,507,1464678000"; d="scan'208";a="1012931889" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by orsmga001.jf.intel.com with ESMTP; 11 Aug 2016 17:19:42 -0700 Received: from fmsmsx152.amr.corp.intel.com (10.18.125.5) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 11 Aug 2016 17:19:42 -0700 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by FMSMSX152.amr.corp.intel.com (10.18.125.5) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 11 Aug 2016 17:19:41 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.181]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.8]) with mapi id 14.03.0248.002; Fri, 12 Aug 2016 08:19:39 +0800 From: "Wu, Jiaxin" To: "Cohen, Eugene" , "edk2-devel@lists.01.org" Thread-Topic: IP4 Config Troubles with DHCP Thread-Index: AdHzLtnEw2gfDCBbQ1OtxXknLLKMhQAabX6gABD3ncAAFJsNEA== Date: Fri, 12 Aug 2016 00:19:39 +0000 Message-ID: <895558F6EA4E3B41AC93A00D163B7274137C63B0@SHSMSX103.ccr.corp.intel.com> References: <895558F6EA4E3B41AC93A00D163B7274137C5EF1@SHSMSX103.ccr.corp.intel.com> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZjM1ZjVhM2QtMDcyYS00OGViLTllYjEtZGY5Mzk2MDBhMGZjIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IlNJVFpmYzJzcG9PKzV2YVh2V2Y0eTZYeFJSNSs5OEVPU1hhOWQ1U0c4MlU9In0= x-ctpclassification: CTP_IC x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: IP4 Config Troubles with DHCP X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Aug 2016 00:19:42 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Thanks Eugene, I will try to reproduce the issue and dig it out. Any proces= s will inform you. Best Regards! Jiaxin > -----Original Message----- > From: Cohen, Eugene [mailto:eugene@hp.com] > Sent: Thursday, August 11, 2016 10:31 PM > To: Wu, Jiaxin ; edk2-devel@lists.01.org > Subject: RE: IP4 Config Troubles with DHCP >=20 > Jianxin, >=20 > > I want to confirm with you the steps to reproduce the issue: > > > > 1. Set policy to DHCP. > > 2. If DHCP process is not complete yet, then run one App to invoke the > > UDP4 Configure with "UseDefaultAddress =3D TRUE" (loop to keep calling > > Udp4->Configure until Ip4Mode.IsConfigured changes to TRUE) > > 3. Even DHCP succeed but Ip4Mode.IsConfigured flag never set to > > TRUE ---- failure here!!! > > > > Above steps right? >=20 > Yes, that summarizes it well. >=20 > > Actually, you don't need to retry the UDP configuration loop according > > the Ip4Mode.IsConfigured flag. You are only recommended to set a timer > > to check the mapping status after the configuration: >=20 > This is exactly what we used to do. Recently it stopped working which is= why > we now have to re-do service binding creation and configuration. >=20 > > If DHCP process succeed, Ip4Mode.IsConfigured should be updated. If > > not, any bug may be existed. >=20 > From the traces I've looked at I can clearly see that the DHCP process as > finished (lease acquired) and that Ip4Mode.IsConfigured is still FALSE. = I'll send > you a detailed trace of this separately. >=20 > So yes, I think there is a bug that crept in. >=20 > Eugene