From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.20; helo=mga02.intel.com; envelope-from=ting.ye@intel.com; receiver=edk2-devel@ml01.01.org Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 6BEB32096F32B for ; Tue, 3 Jul 2018 20:17:13 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jul 2018 20:17:12 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,306,1526367600"; d="scan'208";a="54953741" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by orsmga006.jf.intel.com with ESMTP; 03 Jul 2018 20:17:12 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 3 Jul 2018 20:17:12 -0700 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.81]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.17]) with mapi id 14.03.0319.002; Wed, 4 Jul 2018 11:17:02 +0800 From: "Ye, Ting" To: xujiawu , "edk2-devel@ml01.01.org" Thread-Topic: [edk2] report an issue about edk2 iscsi Thread-Index: AdKOacEi9vPHfQMETfq6ve1g/1hJNAAAXejwYTP9TiAAAjG3oA== Date: Wed, 4 Jul 2018 03:17:01 +0000 Message-ID: References: In-Reply-To: Accept-Language: zh-CN, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: report an issue about edk2 iscsi X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 03:17:13 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Robin, Since you configured the attempt as following: Set: Connection retry count: 5, connection establishing timeout to [5000= ] iSCSI driver will try to connect to iSCSI target in 6 times, each time it u= ses 5 seconds as the timeout value. So you need hold > 30 seconds in your case. Thanks, Ting -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of xuji= awu Sent: Wednesday, July 4, 2018 10:25 AM To: edk2-devel@ml01.01.org Subject: [edk2] report an issue about edk2 iscsi =20 Hello, edk2-devel, I want to report a issue about edk2 iscsi: Set timeout to 5S and copy a big file from iscsi HDD, disconnect Lan cable >>5S then connect again, the big file still copy successfully. =20 BIOS: the latest EDK2 =20 Test steps: 1.Power on and press Hotkey to bios setup, in Advanced menu->iscsi configuration->mac address. 2.ISCSI initiator name: iqn. 3. Add an attempt:=20 set: iscsi attempt name: 1 set: iscsi mode: enable/enable for mpio, internet protocol ipv4 Set: Connection retry count: 5, connection establishing timeout to [5000= ] Set: enable DHCP, enable get target info via DHCP Set: authentication type: none 4. Saved and exit, reboot. 5. Boot to shell, type: fs2:(ISCSI HDD). 6. Plug USB 3.0 flash disk to board. 7. Copy a big file from ISCSI HDD to usb. 8. Plug out LAN cable and hold some time( >> timeout time 5s), then plug in= again. =20 Actual result: The copy file still can successful with ISCSI after timeout. =20 Expected result: The copy file is copied fail with iSCSI after timeout. =20 =20 Thanks, Robin _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel