From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 046C741BBD; Fri, 3 Feb 2023 15:43:23 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A249D4067B; Fri, 3 Feb 2023 15:43:23 +0100 (CET) Received: from mail-yw1-f174.google.com (mail-yw1-f174.google.com [209.85.128.174]) by mails.dpdk.org (Postfix) with ESMTP id 411CC4021E for ; Fri, 3 Feb 2023 15:43:22 +0100 (CET) Received: by mail-yw1-f174.google.com with SMTP id 00721157ae682-4b718cab0e4so70740477b3.9 for ; Fri, 03 Feb 2023 06:43:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=nnaQrdaOvhpZQNg2Kbw4BWixNLltEXy7k08uDrZEzCI=; b=fb4zAeNSa7p4n7DWIim3zgbUVrTmGBKi6gvq1vUpcTMfMYJRJvhA0R+IT2T+dcJkNp a+F5VlOc6KGZVOG38DZoXSdJ+Awl+wn2djXKUFEWhGbO7OjIBft2mQESSVefwPhoFlP7 ez43LmTGLWu27XUjVCsn7kx6zeUBS2hHPutUsN3AvQo5tPqGA/JeiYiqVvt78JP/RtqD s6Oq2c8P9coHovbKoSlPUfdGqZrBcWldRBzD8nzTeJTBHAErWzAVVffxro3PFZyCKWzG mYPdtTGv+5MWdqFpYD2IEvWJvet3u0np1pW6HpfeN87dAfmFdXbGpnbPjadiXpqUXbTu n6Kw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=nnaQrdaOvhpZQNg2Kbw4BWixNLltEXy7k08uDrZEzCI=; b=JGxJrAgOCkV8L2zco5dL+b996SvMwyn1bYg9vfDVd+3zbFy7KaK47lc90oFFBCrF2r 31cxBcDxhMV8SO0R0dt9nCm3qqzWY7RSAbc2Qmp+FEaaq7R10XO0xrXMqqbJU5WcsBRZ DL9j6nP16htef7s1+3Oy0Xk2AG2YL7gnxzzJSbwR6qNLeBbq+eOMyFBcekTT8n/Ww+Al utx1k4V2BwbmEbQwOKuLvohR4g2W8trNbJzHZJEPzWng6e1j75BBnupLb2B9EYSKfU67 kGaBlkkW6VdOJi5U/l0OumVoMjhGuaCgGrvXC2kxxGWiMAlKJNrP1gi7yQz2c35IRxqH /CTw== X-Gm-Message-State: AO0yUKVqSRgBN4b3cScvYyPYLb9PcLyiIBtZHmd8ftP1aUqkrjr7h04l eKWGBtwAkNsKo0wdy4r8ssS9U8ndc6Xw/88/hMY= X-Google-Smtp-Source: AK7set9aoq0hJwUe0PSGlf7xg554enXWXgjsCSBtNH/8pOoiVgj6Muhj23S64Mx7zSFVdSk61NP2bT6/K/5TwQDTLbg= X-Received: by 2002:a81:c242:0:b0:506:6364:fda3 with SMTP id t2-20020a81c242000000b005066364fda3mr997388ywg.72.1675435401401; Fri, 03 Feb 2023 06:43:21 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ben Magistro Date: Fri, 3 Feb 2023 09:43:09 -0500 Message-ID: Subject: Re: ICE DDP Load assistance To: "Zhang, Qi Z" Cc: "dev@dpdk.org" , "Magistro, Benjamin" , Stefan Baranoff Content-Type: multipart/alternative; boundary="000000000000f1db6e05f3ccb30b" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --000000000000f1db6e05f3ccb30b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Just to close the loop on this, most of our nics have been dual port. When looking at this I forgot/didn't realize this one was a quad port nic so some ports were still controlled by the kernel which explains the observed behavior. Also thanks for the explanation around an existing DDP being found. On Mon, Jan 23, 2023 at 8:52 PM Zhang, Qi Z wrote: > Both kernel ice and DPDK ice driver will try to load DDP package from > below folder > > #define ICE_PKG_FILE_DEFAULT "/lib/firmware/intel/ice/ddp/ice.pkg" > > #define ICE_PKG_FILE_UPDATES "/lib/firmware/updates/intel/ice/ddp/ice.pkg= " > > > > And only the first PF driver be probed will load DDP package. > > If the driver found a DDP package already be loaded, it just check if it > is compatible with current required version and will not overwrite it. > > > > So to upgrade DDP package, we need to make sure no active driver is > stilling using the old package, so we may need =E2=80=9Crmmod ice=E2=80= =9D first > > > > Regard > > Qi > > > > *From:* Ben Magistro > *Sent:* Friday, January 20, 2023 11:48 PM > *To:* dev@dpdk.org > *Cc:* Magistro, Benjamin ; Stefan Baranoff > > *Subject:* Re: ICE DDP Load assistance > > > > Okay, believe we have tracked down and can explain most of the current > behavior. The question I have now is, is this really what is desired or > should it be possible for DPDK be passed a flag and load a DDPK file > anyways, or should it always try to update the DDP if a newer one is > found. In our case we are unlikely to utilize the ICE based driver in th= e > OS and would only be using it with DPDK. To me, in this scenario, it mak= es > little sense to maintain/think about the OS driver and related items. > > > > With some increased logging from testpmd and looking at the ICE PMD sourc= e > it was identified that we are hitting `ICE_ERR_AQ_NO_WORK` in `ice_ddp.c = -> > ice_acquire_global_cfg_lock:2232` which indicates that another driver has > already written the package or has found that no update was necessary. M= y > uneducated guess is this is happening as the OS starts up and then > transitions the device over to vfio-pci which would also explain why the > initial firmware load was resolved after running dracut. In the log > scenario below, an update should definitely be necessary still as 1.3.30 = is > found but 1.3.26 is loaded. > > > > ---- > > > > 1822 pkg: /lib/firmware/updates/intel/ice/ddp/ice-40a6b7ffff8437f8.pkg > 1829 pkg: /lib/firmware/intel/ice/ddp/ice-40a6b7ffff8437f8.pkg > 1835 pkg: /lib/firmware/updates/intel/ice/ddp/ice.pkg > 1847 pkg: /lib/firmware/updates/intel/ice/ddp/ice.pkg > ice_load_pkg(): DDP package name: > /lib/firmware/updates/intel/ice/ddp/ice.pkg > init enter > ice_find_seg_in_pkg(): ice 00.0 Package format version: 1.0.0.0 > ice_init_pkg_info(): ice 00.0 Pkg using segment id: 0x00000010 > ice_find_seg_in_pkg(): ice 00.0 Package format version: 1.0.0.0 > ice_init_pkg_info(): ice 00.0 Pkg: 1.3.30.0, ICE OS Default Package > ice_init_pkg_info(): ice 00.0 Ice Seg: 1.0.1.0, ICE Configuration Data > ice_find_seg_in_pkg(): ice 00.0 Package format version: 1.0.0.0 > ice_clean_sq(): ice 00.0 ntc 10 head 11. > ice_sq_send_cmd_nolock(): ice 00.0 ATQ: Control Send queue desc and buffe= r: > ice_sq_send_cmd_nolock(): ice 00.0 ATQ: desc and buffer writeback: > dl w sig > ice_download_pkg_with_sig_seg(): ice 00.0 Segment ID 16 > ice_download_pkg_with_sig_seg(): ice 00.0 Signature type 1 > ice_acquire_res(): ice 00.0 ice_acquire_res > ice_aq_req_res(): ice 00.0 ice_aq_req_res > ice_clean_sq(): ice 00.0 ntc 11 head 12. > ice_sq_send_cmd_nolock(): ice 00.0 ATQ: Control Send queue desc and buffe= r: > ice_sq_send_cmd_nolock(): ice 00.0 ATQ: desc and buffer writeback: > ice_acquire_res(): ice 00.0 resource indicates no work to do. > ice_acquire_global_cfg_lock(): ice 00.0 Global config lock: No work to do > ice_clean_sq(): ice 00.0 ntc 12 head 13. > ice_sq_send_cmd_nolock(): ice 00.0 ATQ: Control Send queue desc and buffe= r: > ice_sq_send_cmd_nolock(): ice 00.0 ATQ: desc and buffer writeback: > ice_clean_sq(): ice 00.0 ntc 13 head 14. > ice_sq_send_cmd_nolock(): ice 00.0 ATQ: Control Send queue desc and buffe= r: > ice_sq_send_cmd_nolock(): ice 00.0 ATQ: desc and buffer writeback: > ice_clean_sq(): ice 00.0 ntc 14 head 15. > ice_sq_send_cmd_nolock(): ice 00.0 ATQ: Control Send queue desc and buffe= r: > ice_sq_send_cmd_nolock(): ice 00.0 ATQ: desc and buffer writeback: > ice_init_pkg(): ice 00.0 package previously loaded - no work. > ice_clean_sq(): ice 00.0 ntc 15 head 16. > ice_sq_send_cmd_nolock(): ice 00.0 ATQ: Control Send queue desc and buffe= r: > ice_sq_send_cmd_nolock(): ice 00.0 ATQ: desc and buffer writeback: > ice_get_pkg_info(): ice 00.0 Pkg[0]: 1.0.0.17,ICE NVM Package,BMN > ice_get_pkg_info(): ice 00.0 Pkg[1]: 1.3.26.0,ICE OS Default Package,A > init end > ice_load_pkg_type(): Active package is: 1.3.26.0, ICE OS Default Package > (single VLAN mode) > > > > On Thu, Jan 19, 2023 at 9:14 AM Ben Magistro wrote: > > Hello, > > > > We are still trying to track this down but want to reach out to the > community and see if there is something obvious we are missing. This > happens to be a CentOS 7 based host with DPDK 22.11.1 in use. We have > obtained the latest compatible Intel drivers and DDP from > https://sourceforge.net/projects/e1000/files/ice%20stable/ , at this time > that is version 1.6.7 with DDP 1.3.26.0. As best as we can tell, testpmd > is still loading the OS default DDP 1.3.4.0. The updated DDP package is > located in /usr/lib/firmware/updates/intel/ice/ddp/ice.pkg. > > > > I've added some additional log lines to ice_ethdev.c and ice_ddp.c to try > and start debugging. I've attached what I believe is the relevant > information below. Quickly jumping out at me is that the pkg_name going > into `load_fw` in ice_ethdev.c appears to be the desired path however in > `ice_download_pkg` says it does not include a signature. The hex dump fr= om > the desired file appears to show a signature which makes us think this fi= le > isn't actually being loaded/utilized. > > > > We will continue trying to debug this too but any additional assistance > would be greatly appreciated. > > > > ---- > > > > EAL: Probe PCI driver: net_ice (8086:1593) device: 0000:ca:00.2 (socket 1= ) > 1822 pkg: /lib/firmware/updates/intel/ice/ddp/ice-40a6b7ffff843810.pkg > 1829 pkg: /lib/firmware/intel/ice/ddp/ice-40a6b7ffff843810.pkg > 1835 pkg: /lib/firmware/updates/intel/ice/ddp/ice.pkg > 1846 pkg: /lib/firmware/updates/intel/ice/ddp/ice.pkg > dl wo sig > ice_load_pkg_type(): Active package is: 1.3.4.0, ICE OS Default Package > (single VLAN mode) > > > ls -l /usr/lib/firmware/updates/intel/ice/ddp/ > total 624 > -rwxr-xr-x. 1 root root 635256 Jan 18 15:53 ice-1.3.26.0.pkg > lrwxrwxrwx. 1 root root 56 Jan 18 15:55 ice.pkg -> > /usr/lib/firmware/updates/intel/ice/ddp/ice-1.3.26.0.pkg > > > xxd /usr/lib/firmware/updates/intel/ice/ddp/ice.pkg | head -n 17 > 0000000: 0100 0000 0400 0000 1800 0000 6c00 0000 ............l... > 0000010: d000 0000 4031 0000 0100 0000 0100 0000 ....@1.......... > 0000020: 5400 0000 476c 6f62 616c 204d 6574 6164 T...Global Metad > 0000030: 6174 6100 0000 0000 0000 0000 0000 0000 ata............. > 0000040: 0000 0000 0103 1a00 ffff ffff 4943 4520 ............ICE > 0000050: 4f53 2044 6566 6175 6c74 2050 6163 6b61 OS Default Packa > 0000060: 6765 0000 0000 0000 0000 0000 0200 0000 ge.............. > 0000070: 0100 0000 6400 0000 4e6f 7465 7300 0000 ....d...Notes... > 0000080: 0000 0000 0000 0000 0000 0000 0000 0000 ................ > 0000090: 0000 0000 0000 0000 496e 7465 6c28 5229 ........Intel(R) > 00000a0: 2043 6f6e 6669 6775 7261 626c 6520 5069 Configurable Pi > 00000b0: 7065 6c69 6e65 2054 6f6f 6c20 5665 7273 peline Tool Vers > 00000c0: 696f 6e20 322e 312e 302e 3330 0a00 ffff ion 2.1.0.30.... > 00000d0: 0010 0000 0100 0000 7030 0000 5253 412d ........p0..RSA- > 00000e0: 324b 2053 6967 6e61 7475 7265 2053 6567 2K Signature Seg > 00000f0: 6d65 6e74 0000 0000 0000 0000 1000 0000 ment............ > 0000100: 0100 0000 0300 0000 0300 0000 0000 0000 ................ > > --000000000000f1db6e05f3ccb30b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Just to close the loop on this, most of our nics have been= dual port.=C2=A0 When looking at this I forgot/didn't realize this one= was a quad port nic so some ports were still controlled by the kernel whic= h explains the observed behavior.=C2=A0 Also thanks for the explanation aro= und an existing DDP being found.

On Mon, Jan 23, 2023 at 8:52 PM Zhang, Qi Z= <qi.z.zhang@intel.com> w= rote:

Both kernel ice and DPDK ice driver will try to load= DDP package from below folder

#define ICE_PKG_FILE_DEFAULT "/lib/firmware/int= el/ice/ddp/ice.pkg"

#define ICE_PKG_FILE_UPDATES "/lib/firmware/upd= ates/intel/ice/ddp/ice.pkg"

=C2=A0

And only the first PF driver be probed will load DDP= package.

If the driver found a DDP package already be loaded,= it just check if it is compatible with current required version and will n= ot overwrite it.

=C2=A0

So to upgrade DDP package, we need to make sure no a= ctive driver is stilling using the old package, so we may need =E2=80=9Crmm= od ice=E2=80=9D first

=C2=A0

Regard

Qi

=C2=A0

From: Ben Magistro <koncept1@gmail.com>
Sent: Friday, January 20, 2023 11:48 PM
To: dev@dpdk.org
Cc: Magistro, Benjamin <ben.magistro@trinitycyber.com>; Stefan Bar= anoff <stefan.baranoff@trinitycyber.com>
Subject: Re: ICE DDP Load assistance

=C2=A0

Okay, believe we have tracked down and can explain m= ost of the current behavior. The question I have now is, is this really wha= t is desired or should it be possible for DPDK be passed a flag and load a = DDPK file anyways, or should it always try to update the DDP if a newer=C2=A0one is found.=C2=A0 In our case we a= re unlikely to utilize the ICE based driver in the OS and would only be usi= ng it with DPDK.=C2=A0 To me, in this scenario, it makes little sense to ma= intain/think about the OS driver and related items.

=C2=A0

With some increased logging from testpmd and looking= at the ICE PMD source it was identified that we are hitting `ICE_ERR_AQ_NO= _WORK` in `ice_ddp.c -> ice_acquire_global_cfg_lock:2232` which indicate= s that another driver has already written the package or has found that no update was necessary.=C2=A0 My uneducated= guess is this is happening as the OS starts up and then transitions the=C2= =A0device over to vfio-pci which would also=C2=A0explain=C2=A0why the initi= al firmware load=C2=A0was resolved after running dracut.=C2=A0 In the log scenario below, an update should definitely be necessary still = as 1.3.30 is found but 1.3.26 is loaded.

=C2=A0

----

=C2=A0

1822 pkg: /lib/firmware/updates/intel/ice/ddp/ice-40= a6b7ffff8437f8.pkg
1829 pkg: /lib/firmware/intel/ice/ddp/ice-40a6b7ffff8437f8.pkg
1835 pkg: /lib/firmware/updates/intel/ice/ddp/ice.pkg
1847 pkg: /lib/firmware/updates/intel/ice/ddp/ice.pkg
ice_load_pkg(): DDP package name: /lib/firmware/updates/intel/ice/ddp/ice.p= kg
init enter
ice_find_seg_in_pkg(): ice 00.0 Package format version: 1.0.0.0
ice_init_pkg_info(): ice 00.0 Pkg using segment id: 0x00000010
ice_find_seg_in_pkg(): ice 00.0 Package format version: 1.0.0.0
ice_init_pkg_info(): ice 00.0 Pkg: 1.3.30.0, ICE OS Default Package
ice_init_pkg_info(): ice 00.0 Ice Seg: 1.0.1.0, ICE Configuration Data
ice_find_seg_in_pkg(): ice 00.0 Package format version: 1.0.0.0
ice_clean_sq(): ice 00.0 ntc 10 head 11.
ice_sq_send_cmd_nolock(): ice 00.0 ATQ: Control Send queue desc and buffer:=
ice_sq_send_cmd_nolock(): ice 00.0 ATQ: desc and buffer writeback:
dl w sig
ice_download_pkg_with_sig_seg(): ice 00.0 Segment ID 16
ice_download_pkg_with_sig_seg(): ice 00.0 Signature type 1
ice_acquire_res(): ice 00.0 ice_acquire_res
ice_aq_req_res(): ice 00.0 ice_aq_req_res
ice_clean_sq(): ice 00.0 ntc 11 head 12.
ice_sq_send_cmd_nolock(): ice 00.0 ATQ: Control Send queue desc and buffer:=
ice_sq_send_cmd_nolock(): ice 00.0 ATQ: desc and buffer writeback:
ice_acquire_res(): ice 00.0 resource indicates no work to do.
ice_acquire_global_cfg_lock(): ice 00.0 Global config lock: No work to do ice_clean_sq(): ice 00.0 ntc 12 head 13.
ice_sq_send_cmd_nolock(): ice 00.0 ATQ: Control Send queue desc and buffer:=
ice_sq_send_cmd_nolock(): ice 00.0 ATQ: desc and buffer writeback:
ice_clean_sq(): ice 00.0 ntc 13 head 14.
ice_sq_send_cmd_nolock(): ice 00.0 ATQ: Control Send queue desc and buffer:=
ice_sq_send_cmd_nolock(): ice 00.0 ATQ: desc and buffer writeback:
ice_clean_sq(): ice 00.0 ntc 14 head 15.
ice_sq_send_cmd_nolock(): ice 00.0 ATQ: Control Send queue desc and buffer:=
ice_sq_send_cmd_nolock(): ice 00.0 ATQ: desc and buffer writeback:
ice_init_pkg(): ice 00.0 package previously loaded - no work.
ice_clean_sq(): ice 00.0 ntc 15 head 16.
ice_sq_send_cmd_nolock(): ice 00.0 ATQ: Control Send queue desc and buffer:=
ice_sq_send_cmd_nolock(): ice 00.0 ATQ: desc and buffer writeback:
ice_get_pkg_info(): ice 00.0 Pkg[0]: 1.0.0.17,ICE NVM Package,BMN
ice_get_pkg_info(): ice 00.0 Pkg[1]: 1.3.26.0,ICE OS Default Package,A
init end
ice_load_pkg_type(): Active package is: 1.3.26.0, ICE OS Default Package (s= ingle VLAN mode)

=C2=A0

On Thu, Jan 19, 2023 at 9:14 AM Ben Magistro <koncept1@gmail.com= > wrote:

Hello,

=C2=A0

We are still trying to track this down but want to r= each out to the community and see if there is something obvious we are miss= ing.=C2=A0 This happens to be a CentOS 7 based host with DPDK 22.11.1 in us= e.=C2=A0 We have obtained=C2=A0the latest compatible Intel drivers and DDP from=C2=A0https://sourceforge.net/proj= ects/e1000/files/ice%20stable/ , at this time that is version 1.6.7 wit= h DDP 1.3.26.0.=C2=A0 As best as we can tell, testpmd is still loading the OS=C2=A0default DDP 1.3.4.0.=C2=A0 The update= d DDP package is located in /usr/lib/firmware/updates/intel/ice/ddp/ice.pkg= .

=C2=A0

I've added some additional log lines to ice_ethd= ev.c and ice_ddp.c to try and start debugging.=C2=A0 I've attached what= I believe is the relevant information below.=C2=A0 Quickly jumping out at = me is that the pkg_name going into `load_fw` in ice_ethdev.c appears to be the desired path however in `ice_download_pkg` says it does = not include a signature.=C2=A0 The hex dump from the desired file appears t= o show a signature which makes us think this file isn't actually being = loaded/utilized.

=C2=A0

We will continue trying to debug this too but any ad= ditional assistance would be greatly appreciated.

=C2=A0

----

=C2=A0

EAL: Probe PCI driver: net_ice (8086:1593) device: 0= 000:ca:00.2 (socket 1)
1822 pkg: /lib/firmware/updates/intel/ice/ddp/ice-40a6b7ffff843810.pkg
1829 pkg: /lib/firmware/intel/ice/ddp/ice-40a6b7ffff843810.pkg
1835 pkg: /lib/firmware/updates/intel/ice/ddp/ice.pkg
1846 pkg: /lib/firmware/updates/intel/ice/ddp/ice.pkg
dl wo sig
ice_load_pkg_type(): Active package is: 1.3.4.0, ICE OS Default Package (si= ngle VLAN mode)

> ls -l /usr/lib/firmware/updates/intel/ice/ddp/
total 624
-rwxr-xr-x. 1 root root 635256 Jan 18 15:53 ice-1.3.26.0.pkg
lrwxrwxrwx. 1 root root =C2=A0 =C2=A0 56 Jan 18 15:55 ice.pkg -> /usr/li= b/firmware/updates/intel/ice/ddp/ice-1.3.26.0.pkg

> xxd /usr/lib/firmware/updates/intel/ice/ddp/ice.pkg | head -n 17
0000000: 0100 0000 0400 0000 1800 0000 6c00 0000 =C2=A0............l...
0000010: d000 0000 4031 0000 0100 0000 0100 0000 =C2=A0....@1..........
0000020: 5400 0000 476c 6f62 616c 204d 6574 6164 =C2=A0T...Global Metad
0000030: 6174 6100 0000 0000 0000 0000 0000 0000 =C2=A0ata.............
0000040: 0000 0000 0103 1a00 ffff ffff 4943 4520 =C2=A0............ICE
0000050: 4f53 2044 6566 6175 6c74 2050 6163 6b61 =C2=A0OS Default Packa
0000060: 6765 0000 0000 0000 0000 0000 0200 0000 =C2=A0ge..............
0000070: 0100 0000 6400 0000 4e6f 7465 7300 0000 =C2=A0....d...Notes...
0000080: 0000 0000 0000 0000 0000 0000 0000 0000 =C2=A0................
0000090: 0000 0000 0000 0000 496e 7465 6c28 5229 =C2=A0........Intel(R)
00000a0: 2043 6f6e 6669 6775 7261 626c 6520 5069 =C2=A0 Configurable Pi
00000b0: 7065 6c69 6e65 2054 6f6f 6c20 5665 7273 =C2=A0peline Tool Vers
00000c0: 696f 6e20 322e 312e 302e 3330 0a00 ffff =C2=A0ion 2.1.0.30....
00000d0: 0010 0000 0100 0000 7030 0000 5253 412d =C2=A0........p0..RSA-
00000e0: 324b 2053 6967 6e61 7475 7265 2053 6567 =C2=A02K Signature Seg
00000f0: 6d65 6e74 0000 0000 0000 0000 1000 0000 =C2=A0ment............
0000100: 0100 0000 0300 0000 0300 0000 0000 0000 =C2=A0................<= /u>

--000000000000f1db6e05f3ccb30b--