From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=209.132.183.28; helo=mx1.redhat.com; envelope-from=lersek@redhat.com; receiver=edk2-devel@lists.01.org Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (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 82B0D211982CF for ; Mon, 3 Dec 2018 01:56:52 -0800 (PST) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id EB3423002E00; Mon, 3 Dec 2018 09:56:51 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-120-61.rdu2.redhat.com [10.10.120.61]) by smtp.corp.redhat.com (Postfix) with ESMTP id AA0725D738; Mon, 3 Dec 2018 09:56:50 +0000 (UTC) To: Udit Kumar , "afish@apple.com" Cc: "Ni, Ruiyu" , "edk2-devel@lists.01.org" , "Zeng, Star" References: <2EF700E0-AF34-498C-B740-406BE5BA0839@apple.com> <80adb57c-ffa2-d5d6-5d14-eeb9513a1328@redhat.com> <8ea4f231-a264-cd85-1392-9fabe77613f5@redhat.com> From: Laszlo Ersek Message-ID: <3cf90372-14d4-3726-eab3-ab1e87836694@redhat.com> Date: Mon, 3 Dec 2018 10:56:49 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.43]); Mon, 03 Dec 2018 09:56:52 +0000 (UTC) Subject: Re: Help on boot manager 'Boot Manager Menu' and direct boot X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Dec 2018 09:56:52 -0000 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 11/30/18 10:13, Udit Kumar wrote: > Thanks Laszlo/Andrew > Finally I manage to get logs from user-space, problem was fifo of PL011 uart was not getting enable in case of direct boot. > But in case of boot via UiApp, some piece of code was setting serial port attribute to enable this ( I still to figure out from where). > OS rely on boot-loader to enable this bit. Are you using the latest edk2? I vaguely recall some refactoring around PL011 (and in general, serial) attributes from a year (or more?) ago. Hmm.... b462f25a21e1 MdeModulePkg/SerialDxe: Describe correctly EFI_DEVICE_ERROR for SetAttributes 13d378fc82d4 MdeModulePkg/SerialDxe: Fix return valued in SerialSetAttributes 7ce5af40c98b MdeModulePkg/SerialDxe: Do not fail reset when SetAttributes is not supported and 91cc526b15ff MdeModulePkg/SerialDxe: Fix not able to change serial attributes Thanks Laszlo >> -----Original Message----- >> From: Laszlo Ersek >> Sent: Thursday, November 29, 2018 11:31 PM >> To: Udit Kumar ; afish@apple.com >> Cc: Ni, Ruiyu ; edk2-devel@lists.01.org; Zeng, Star >> >> Subject: Re: [edk2] Help on boot manager 'Boot Manager Menu' and direct boot >> >> On 11/29/18 14:12, Udit Kumar wrote: >>> Thanks Laszlo, >>> >>> >>>> I can only think of some terminal control sequences that are *not* >>>> printed to the terminal when you don't enter UiApp manually. I don't >>>> understand how that could cause the exact symptom you describe, but I have >> no better explanation. >>>> >>>> Can you try other serial communication programs on your desktop? Such >>>> as "minicom" or "screen"? >>> >>> Screen didn't help. >>> Moreover , using different OS distributions show same similar behavior !! >>> >>>> Also, can you try changing your "console=..." kernel param(s)? >>> >>> You meant baud-rate ? >> >> Yes, and more. The options that the "console=" kernel parameter takes. >> >>> >>> On uefi side, could you help me if there is some extra information >>> passed to OS in path UiApp -> BootDevice, >> >> I don't think so. Nothing comes to my mind anyway. >> >>> I could see , some of additional protocols are installed in above >>> path, I am not sure if those are used by OS or OS Loader (grub in my case) >> somehow. >> >> Well, UiApp generally connects all drivers to all devices -- normally a platform >> BDS would not want to do this, for the sake of booting quickly --, which likely >> results in more protocol instances being installed in the system. That shouldn't >> cause a difference for how serial behaves once the OS has booted. >> >> Thanks >> Laszlo