From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1ns4yd-00DMEH-AK for linux-um@lists.infradead.org; Fri, 20 May 2022 15:55:44 +0000 Date: Fri, 20 May 2022 08:55:40 -0700 From: Nathan Chancellor Subject: Re: [PATCH 1/1] um: fix error return code in winch_tramp() Message-ID: References: <20210508032239.2177-1-thunder.leizhen@huawei.com> <1b03d888-cea3-3e6f-087f-daeb5642a975@leemhuis.info> <1087614384.239493.1649583213699.JavaMail.zimbra@nod.at> <1287561645.244713.1649702724736.JavaMail.zimbra@nod.at> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: "linux-um" Errors-To: linux-um-bounces+geert=linux-m68k.org@lists.infradead.org To: Thorsten Leemhuis Cc: Richard Weinberger , Zhen Lei , Jeff Dike , anton ivanov , Andrew Morton , Eduard-Gabriel Munteanu , linux-um , linux-kernel , Nick Desaulniers , regressions On Fri, May 20, 2022 at 08:08:01AM +0200, Thorsten Leemhuis wrote: > On 11.04.22 20:45, Richard Weinberger wrote: > > ----- Urspr=FCngliche Mail ----- > >> Von: "Nathan Chancellor" > >> I attempted to print out the error code but it seems like there is no > >> output in the console after "reboot: System halted". If I add an > >> unconditional print right before the call to os_set_fd_block(), I see = it > >> during start up but I do not see it during shutdown. Is there some way > >> to see that console output during shutdown? > > = > > I think in this case the easiest way is attaching gdb with a breakpoint. > = > I noticed this in my list of open regressions. It seems there wasn't any > progress to get this regression fixed (please let me know in case I > missed something), but I guess nobody considered it urgent which is > likely not that much of a problem in this case. Yes, sorry, I tried to get gdb to reveal something but I couldn't get it to work then I had to move onto other work. We have worked around this for the time being but it would still be nice to figure out what is going on here; I am just not sure when I am going to have time to participate in that process. Cheers, Nathan _______________________________________________ linux-um mailing list linux-um@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-um