From owner-freebsd-current@freebsd.org Sun Oct 28 16:39:09 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1274C10D89B8 for ; Sun, 28 Oct 2018 16:39:09 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8FE408C50B; Sun, 28 Oct 2018 16:39:08 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 3194021F82; Sun, 28 Oct 2018 12:39:02 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sun, 28 Oct 2018 12:39:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm3; bh=QogpoLC2Jw+JiKI21vF2ToEoNYh V5oO0SE1upQiGjoU=; b=Kc9HEJwLsNS4mQmb9gtxQaJz7YZSWwLuZSrZL3ETXGH BWrZJBDTGRfy+NMWbVUCBAgOTmDMBsKzbL26gqY+ylLgjy5/GNQi0O6qFdxvhgbQ ZUYwOzGL932iXWXcJ4Jh/Q93R5IKO3uQhNkn7oUX2HvxT74MXdxfDnt707NQabZO cZXoECo2EOFGDZRLLz4OTYOC+f01TxRJ98pQHy/lBuR8liLQ2d3nzW2zx8PEw2Fv f9IQLfOMhQNi8B5Ga00Y6j+z8ak8i2MwupDQcqEDrxR4R/z4HRhGBccUyAn1UzKA BR3NNzfcejU+vzf9D3Z/ibisSmVA2P6EDofSkM7NeKQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=QogpoL C2Jw+JiKI21vF2ToEoNYhV5oO0SE1upQiGjoU=; b=lqTqmukerF8WQZnfgrwvk0 oPyUyJM3+kr9Um7Xbne4mvSkAw9sOAtHkGHTLOBFpYnhDxZk5GohceHbxxU+NwV7 uGyj7CZiUiFEU8wXMOerSL4NMRlAVOmR7JIm4xMsRfFyG5wNztFuwDqb2sDTrFTe eDV7VzXQ3Whp76fR/OyY+FcbBmPPS/QymaTAaIkFO7yWhO78OwTsGVKQASD83dx9 Xb2qvd+tzddgiAHF12lkw80NBpkyOsl2v8i+D3OnraDXXV0ZqHc54upG73Urklla MgaiqZ/uS8kbpe2i1v5y/RBZ4aX+Cnfwr4huewMneXjDc0vIbxLBBWekQVl5F/DA == X-ME-Sender: X-ME-Proxy: Received: from [192.168.1.2] (unknown [178.34.115.95]) by mail.messagingengine.com (Postfix) with ESMTPA id 0E43A102E0; Sun, 28 Oct 2018 12:38:58 -0400 (EDT) Subject: Re: UEFI boot hangs after loader To: Jung-uk Kim , Warner Losh , Harry Newton Cc: Kyle Evans , Toomas Soome , FreeBSD Current References: <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> <2c936e35-7bcf-95f9-f99d-60d3c9408d39@FreeBSD.org> From: Yuri Pankov Openpgp: preference=signencrypt Autocrypt: addr=yuripv@yuripv.net; keydata= xsBNBFu8u6IBCADB11gP0QwnorrHjqAtKLHKHNHskhy0s7jqJKfx0YqXgVBKGLJ9/mjLAz0F CBNvemHSDDTs0mEZ9cBKKi6cmsav6+UQgr//yai6hvXLBJqKchSFO4MhmdvBtsGFq1yKz5Zi uhjmimKyIpgBgvMdbgGbGq6cnSB2uEPmZuJr419SVRODOkXukU+F5WHgaHzDdHAIu1asCt2B +6msxqIqlFWcXyZyTGicTGGvC/PFIsVRUtD1dIJANTC876g7DTb7LZXWiWwJpSJ4GKMXMHVX Ct9BoQ4i3nhKbOxb6Io1wsy+NFyWsTJ9KYrxKKPJP3oG8BWb/cqlFqnE4eNSsiq2q7krABEB AAHNH1l1cmkgUGFua292IDx5dXJpcHZAeXVyaXB2Lm5ldD7CwJcEEwEIAEECGwMFCQWjmoAF CwkIBwMFFQoJCAsFFgMCAQACHgECF4AWIQT4arc+w94tPi0v/3CTi+B/sSrhbAUCW708wAIZ AQAKCRCTi+B/sSrhbPxBB/961alcU091O+yKT5/oReHVc/PX0Tz4sW3V44AcgLfYlrZavCro EFz90qmCrl0xqEwuAKcC4bjmL8SjPWAhSN6IH9nxdw+HeZnAPiHm/q679Bu47+nHBl3qD/9p +t1PkKeKZfaWToFMt1nq06ytSu6VLMCwLdlDNe6DReX0ex/afEqKsuaIZSKL4UYjRwklp8PU Uf98QkrfapyHB67hQMzfI4tPeJaYyv0cTgfq3kUWJx1V6Xi0b6Zxj4ZrB2TXvaMO5g7yhU9E E3WWAvoe4FgB3a7dHe8atnHhq5+Cuvm6+LD4Jh7jvMAE5UMN+xxQpnGpNghHjaCy4vXrLRBZ nhRYzsBNBFu8u6IBCADKih3Q933rDNj4ZA8FhBQ2RlmBgvwOLcDPIL3h0V7h38y3+HisgFSc XACDsdrTlYZ1bRXkD9FHENynBcv0l/3uGJDk8jaGIDE0TP8OQBRp+IaU9/BHnAqrKxTJGIol Dahy2m+yx2yhdc6B4ujWMDqCF1rWOD+ymOWw+VLllOkrHcZa5PJtX9UOGbApZl8ZTM8El4CA NN8F1bg9MWzUi+8LYoGWGc+BwsFS1OUB1c4SPgMu5fD4Wfsr9yRl06fdpEA2YT7B/j5/5RSC 0sE2Zs/tmJ/JRflHJ12ycj59ma2xQMfEJF40hZDpMFQmZvbVqgEg3ocQcltjbxlIKZ/mjC4z ABEBAAHCwHwEGAEKACYWIQT4arc+w94tPi0v/3CTi+B/sSrhbAUCW7y7ogIbDAUJBaOagAAK CRCTi+B/sSrhbIDcCACqAZMcoxUBLZa40a5b24j5i1jplvCYYb3h+Q5lt5+BFJ87kCb4dJuU D3kh2i29BrxWQWa9WNue9ozxeYkbkfXubQYXexVolRsnh64OdGsE8KvorBFBB3zdK/GRt2Jy +jsnTfUWuQllbzMP0MfhCDMk1Mo8WvDH2/cOEP/yLKf20a+cd6nLs7bidjmGXo9pyuBKAtV6 Kv+VRu54AL+A/UBYu/eB3Dtvzcnut+1Zq6KaP++kUwPwINLIk04OBDwN0zRNTiqMAFYYyz2v ZHBB6E1th/l//ZC5b9Dk0ZpFI1bYdL9ymnrZe1MqbGPnDCToQxu00T/pZCm6Z92YrZQYuNwl Message-ID: Date: Sun, 28 Oct 2018 19:38:50 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <2c936e35-7bcf-95f9-f99d-60d3c9408d39@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Yjg1kRMFnydxiJEaVyp2LZmoeHMnXaOhW" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Sun, 28 Oct 2018 16:39:09 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Yjg1kRMFnydxiJEaVyp2LZmoeHMnXaOhW Content-Type: multipart/mixed; boundary="bvXOeNfLQ5U7LSw4TMDrD4jUvpCJLynZD"; protected-headers="v1" From: Yuri Pankov To: Jung-uk Kim , Warner Losh , Harry Newton Cc: Kyle Evans , Toomas Soome , FreeBSD Current Message-ID: Subject: Re: UEFI boot hangs after loader References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> <2c936e35-7bcf-95f9-f99d-60d3c9408d39@FreeBSD.org> In-Reply-To: <2c936e35-7bcf-95f9-f99d-60d3c9408d39@FreeBSD.org> --bvXOeNfLQ5U7LSw4TMDrD4jUvpCJLynZD Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Jung-uk Kim wrote: > On 18. 10. 24., Warner Losh wrote: >> On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote= : >> >>> gryphon# efivar -N --hex $(efivar | grep Boot0002) >>> 0000: 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3a 00 >>> 0010: 20 00 4b 00 69 00 6e 00 67 00 73 00 74 00 6f 00 >>> 0020: 6e 00 44 00 61 00 74 00 61 00 54 00 72 00 61 00 >>> 0030: 76 00 65 00 6c 00 65 00 72 00 20 00 32 00 2e 00 >>> 0040: 30 00 31 00 2e 00 30 00 30 00 00 00 02 01 0c 00 >>> 0050: d0 41 03 0a 00 00 00 00 01 01 06 00 00 14 03 05 >>> 0060: 06 00 03 00 04 01 2a 00 01 00 00 00 01 00 00 00 >>> 0070: 00 00 00 00 40 06 00 00 00 00 00 00 90 90 90 90 >>> 0080: 00 00 00 00 00 00 00 00 00 00 00 00 01 01 7f ff >>> 0090: 04 00 01 04 4e 00 ef 47 64 2d c9 3b a0 41 ac 19 >>> 00a0: 4d 51 d0 1b 4c e6 4b 00 69 00 6e 00 67 00 73 00 >>> 00b0: 74 00 6f 00 6e 00 44 00 61 00 74 00 61 00 54 00 >>> 00c0: 72 00 61 00 76 00 65 00 6c 00 65 00 72 00 20 00 >>> 00d0: 32 00 2e 00 30 00 31 00 2e 00 30 00 30 00 00 00 >>> 00e0: 7f ff 04 00 00 00 42 4f >>> gryphon# >>> >> >> Perfect. I'll decode this and see if I can figure out where we're goin= g AFU. >=20 > It looks familiar. >=20 > http://docs.freebsd.org/cgi/mid.cgi?eadf5d63-a65a-338e-a3e0-f91b410052f= a I have an output looking similar, but not exactly: 0000: 01 00 00 00 62 00 55 00 45 00 46 00 49 00 20 00 0010: 4f 00 53 00 00 00 04 01 2a 00 01 00 00 00 28 00 0020: 00 00 00 00 00 00 00 40 06 00 00 00 00 00 f1 84 0030: d7 13 ca da e8 11 94 1d 30 85 a9 40 0a 5c 02 02 0040: 04 04 30 00 5c 00 45 00 46 00 49 00 5c 00 42 00 0050: 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 0060: 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 0070: 7f ff 04 00 aa 55 18 0f Same problem with ASUS P8H77-I. >>> On 24 October 2018 at 15:09, Warner Losh wrote: >>> >>>> >>>> >>>> On Wed, Oct 24, 2018 at 7:05 AM Harry Newton wrot= e: >>>> >>>>> Booted with the installer image makes efibootmgr to work as you sai= d: >>>>> >>>>> gryphon# efibootmgr -v >>>>> BootCurrent: 0002 >>>>> Timeout : 2 seconds >>>>> BootOrder : 0001, 0002 >>>>> Boot0001* UEFI OS >>>>> >>>>> HD(1,GPT,b19ccd5d-7c6a-11e7-ae3e-28b2bde107e4,0x28,0x640)/File(\EFI= \BOOT\BOOTX64.EFI) >>>>> ada0p1:/EFI/BOOT/BOOTX64.EFI (null) >>>>> >>>>> However it (efibootmgr) hangs and doesn't return to the shell, thou= gh it >>>>> is >>>>> interruptible with ^C. >>>>> >>>>> The partition listed against Boot0001 is my efi partition. >>>>> >>>> >>>> Can you do something like: >>>> >>>> sudo efivar -N --hex `sudo efivar | grep Boot0002` >>>> >>>> so I can have an example of a naughty boot variable? That's almost >>>> certainly causing the heart-burn. >>>> >>>> Warner >>>> >>>> >>>> >>>>> /H >>>>> >>>>> On 23 October 2018 at 22:51, Kyle Evans wrote:= >>>>> >>>>>> Hi, >>>>>> >>>>>> I suspect 4th vs. lua has no impact here, given the output shown -= - >>>>>> can you throw one of the installer images [0] on some removable me= dia >>>>>> and give that a shot for booting? If that works, we can explore UE= FI >>>>>> variables from there. >>>>>> >>>>>> efibootmgr will only work on a successful UEFI boot, unfortunately= - if >>>>>> we didn't make uefi loader -> kernel transition, then we don't hav= e >>>>>> access to runtime services. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Kyle Evans >>>>>> >>>>>> [0] >>>>> https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/12= =2E0/ >>>>>> >>>>>> On Tue, Oct 23, 2018 at 4:23 PM Harry Newton wr= ote: >>>>>>> >>>>>>> I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and >>>>> re-made >>>>>> the >>>>>>> binaries in /boot but this doesn't solve the problem. It did cop= y >>>>>>> /boot/loader_4th.efi to /boot/loader.efi which is (according to >>>>> uefi(8) >>>>>>> which is what is called from /boot/boot1.efi and which contains t= he >>>>>> strings >>>>>>> I see on the console before the hang. But it must then call / re= ad >>>>>>> something else and I don't think it can find it. Not sure why it= >>>>> doesn't >>>>>>> produce an error message. I *think* it may be something to do wi= th >>>>> EFI >>>>>>> variables, but as efibootmgr doesn't work I can't explore this, >>>>> despite >>>>>>> efirt being in the kernel. >>>>>>> >>>>>>> Suggestions received welcomed, and new suggestions / leads to fol= low >>>>> also >>>>>>> very much welcomed. >>>>>>> >>>>>>> /H >>>>>>> >>>>>>> >>>>>>> On 23 October 2018 at 21:33, Harry Newton wrot= e: >>>>>>> >>>>>>>> Right ... I've the binaries in /boot, freshly made. This might = be >>>>> a >>>>>> silly >>>>>>>> question ... do I not need to copy them (or dd the boot1.efifat >>>>> image) >>>>>> to >>>>>>>> the EFI partition ? >>>>>>>> >>>>>>>> /H >>>>>>>> >>>>>>>> On 23 October 2018 at 21:30, Toomas Soome wrote:= >>>>>>>> >>>>>>>>> you should have the binaries in boot - just ln (or copy) one to= >>>>>> loader.efi >>>>>>>>> >>>>>>>>> rgds, >>>>>>>>> toomas >>>>>>>>> >>>>>>>>> >>>>>>>>> On 23 Oct 2018, at 23:22, Harry Newton wrote= : >>>>>>>>> >>>>>>>>> Yes ... so as everything is built, can I just alter >>>>>> LOADER_DEFAULT_INTERP >>>>>>>>> in /etc/make.conf and then reinstall just the loader and boot >>>>> parts >>>>>> onto >>>>>>>>> the UEFI partition ? If so, how ? >>>>>>>>> >>>>>>>>> >>>>>>>>> On 23 October 2018 at 21:17, Toomas Soome wrote= : >>>>>>>>> >>>>>>>>>> ok, in that case I=E2=80=99d suggest to test out if forth base= d one is >>>>> still >>>>>>>>>> working - at least you can get the bootable system. And then >>>>> there >>>>>> is a >>>>>>>>>> chance to debug the lua version too (note it should be possibl= e >>>>> to >>>>>> chain >>>>>>>>>> /boot/loader_lua.efi). >>>>>>>>>> >>>>>>>>>> rgds, >>>>>>>>>> toomas >>>>>>>>>> >>>>>>>>>>> On 23 Oct 2018, at 23:08, Harry Newton >>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> So it's got FORTH in it, but my loader is lua based, and also= >>>>>> doesn't >>>>>>>>>>> appear to read loader.rc. >>>>>>>>>>> >>>>>>>>>>> /H >>>>>>>>>>> >>>>>>>>>>> On 23 October 2018 at 21:03, Toomas Soome >>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> hm. in that case, whats the content of /boot/loader.rc ? >>>>>>>>>>>> >>>>>>>>>>>> rgds, >>>>>>>>>>>> toomas >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 23 Oct 2018, at 23:01, Harry Newton >>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> If boot menu is the screen where you get the options for >>>>> various >>>>>>>>>> kernels >>>>>>>>>>>> and the picture of the daemon head, no. It stops at the >>>>> point in >>>>>> my >>>>>>>>>> email >>>>>>>>>>>> =E2=80=94 though not as I said just before the kernel is loa= ded but in >>>>>> point >>>>>>>>>> of >>>>>>>>>>>> fact before the menu. >>>>>>>>>>>> >>>>>>>>>>>> I've also rebuilt the kernel and still can't use efibootmgr >>>>> which >>>>>> is >>>>>>>>>>>> puzzling me. >>>>>>>>>>>> >>>>>>>>>>>> /H >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 23 October 2018 at 20:56, Toomas Soome >>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Do you get boot menu? if so, press esc to get to ok prompt,= >>>>> then >>>>>> type >>>>>>>>>>>>> start - if its bootfort based loader, it will load the >>>>> kernel and >>>>>>>>>> modules. >>>>>>>>>>>>> lsmod will then list the loaded files. >>>>>>>>>>>>> >>>>>>>>>>>>> If the loader prompt is still usable, then next command >>>>> would be: >>>>>>>>>> boot >>>>>>>>>>>>> >>>>>>>>>>>>> rgds, >>>>>>>>>>>>> toomas >>>>>>>>>>>>> >>>>>>>>>>>>>> On 23 Oct 2018, at 20:45, Harry Newton >>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to >>>>>> 12.0-BETA1 >>>>>>>>>>>>> r339529 >>>>>>>>>>>>>> by source. Have a problem with booting which hangs after:= >>>>>>>>>>>>>> >>>>>>>>>>>>>>>> FreeBSD EFI boot block >>>>>>>>>>>>>> Loader path: /boot/loader.efi >>>>>>>>>>>>>> >>>>>>>>>>>>>> Initializing modules: ZFS UFS >>>>>>>>>>>>>> Probing 5 block devices ... done >>>>>>>>>>>>>> ZFS found the following pools: zroot >>>>>>>>>>>>>> UFS found no partitions >>>>>>>>>>>>>> Consoles: EFI console >>>>>>>>>>>>>> FreeBSD/amd64 EFI loader, Revision 1.1 >>>>>>>>>>>>>> >>>>>>>>>>>>>> Command line arguments: loader.efi >>>>>>>>>>>>>> EFI version 2.31 >>>>>>>>>>>>>> EFI Firmware: American Megatrends (rev 4.654) >>>>>>>>>>>>>> Console: efi(0) >>>>>>>>>>>>>> Load Path: HD(4, GPT [ ... ] >>>>>>>>>>>>>> Load Device: Pci Root [ ... ] >>>>>>>>>>>>>> Boot Current: 0001 >>>>>>>>>>>>>> Boot Order: 0001 [x] >>>>>>>>>>>>>> Boot Info Path: HS(1, GPT, [ ... ] >>>>> /\EFI\BOOT\BOOTX64.EFI >>>>>>>>>>>>>> - >>>>>>>>>>>>>> >>>>>>>>>>>>>> So it gets into loader.efi which runs but stops I think ju= st >>>>>> before >>>>>>>>>>>>> loading >>>>>>>>>>>>>> the kernel. Partitions: >>>>>>>>>>>>>> >>>>>>>>>>>>>> =3D> 40 250069600 ada0 GPT (119G) >>>>>>>>>>>>>> 40 1600 1 efi (800K) >>>>>>>>>>>>>> 1640 1024 2 freebsd-boot (512K) >>>>>>>>>>>>>> 2664 1432 - free - (716K) >>>>>>>>>>>>>> 4096 4194304 3 freebsd-swap (2.0G) >>>>>>>>>>>>>> 4198400 245870592 4 freebsd-zfs (117G) >>>>>>>>>>>>>> 250068992 648 - free - (324K) >>>>>>>>>>>>>> >>>>>>>>>>>>>> and the EFI partition is FAT 12. >>>>>>>>>>>>>> >>>>>>>>>>>>>> I can't provide (at the moment) any output from efibootmgr= : >>>>>>>>>>>>>> >>>>>>>>>>>>>> root@gryphon:~ # efibootmgr -v >>>>>>>>>>>>>> efibootmgr: efi variables not supported on this system. >>>>> root? >>>>>>>>>> kldload >>>>>>>>>>>>> efirt? >>>>>>>>>>>>>> root@gryphon:~ # kldload efirt >>>>>>>>>>>>>> kldload: can't load efirt: module already loaded or in >>>>> kernel >>>>>>>>>>>>>> >>>>>>>>>>>>>> which I don't understand. >>>>>>>>>>>>>> >>>>>>>>>>>>>> I'm going to rebuild the kernel (currently GENERIC) and se= e >>>>> if >>>>>> that >>>>>>>>>>>>> allows >>>>>>>>>>>>>> me to load efirt / use efibootmgr. >>>>>>>>>>>>>> >>>>>>>>>>>>>> In the meantime, I should be very grateful for any advice.= >>>>>>>>>>>>>> >>>>>>>>>>>>>> ( Currently booting using a 11-RELEASE memstick image and >>>>>> dropping >>>>>>>>>> into >>>>>>>>>>>>> its >>>>>>>>>>>>>> loader to get to the installed 12-STABLE ). >>>>>>>>>>>>>> >>>>>>>>>>>>>> /Harry >=20 --bvXOeNfLQ5U7LSw4TMDrD4jUvpCJLynZD-- --Yjg1kRMFnydxiJEaVyp2LZmoeHMnXaOhW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+Gq3PsPeLT4tL/9wk4vgf7Eq4WwFAlvV5iEACgkQk4vgf7Eq 4Wy4HAf9EvVgV2fvQHNzYjH/zljFcMlrrrAyif9xaq6SaFjq50bNw+GxRw4XF4Ou LwZb15iduGBX3Woiod1kr+PQvsA0Ueq0nJHac2VNLhj2Ko9lMbSxdG3rW3/MM4C+ k+ork108Q6WHlMuY/xggD782F5FnS8ioytGwXnvB8v6iTO4XIORs22dURW7PnvE/ HRP5LyKRM+fPce7GWtdtL6kdFtv8c+bIvFpRWMmFBp4WpAqZLVr+8B9673XA3gPi zkuzRq5bs4KNjx35GNKVqoLme8DW0zt2Lvs4CjetrYaRMWHQu6+TzGdWOOiZ4EVr emOtDcJD6WQ6thdlM+xMzsW/umZprw== =Antu -----END PGP SIGNATURE----- --Yjg1kRMFnydxiJEaVyp2LZmoeHMnXaOhW--