[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1287561645.244713.1649702724736.JavaMail.zimbra@nod.at>
Date: Mon, 11 Apr 2022 20:45:24 +0200 (CEST)
From: Richard Weinberger <richard@....at>
To: Nathan Chancellor <nathan@...nel.org>
Cc: Thorsten Leemhuis <regressions@...mhuis.info>,
Zhen Lei <thunder.leizhen@...wei.com>,
Jeff Dike <jdike@...toit.com>,
anton ivanov <anton.ivanov@...bridgegreys.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Eduard-Gabriel Munteanu <maxdamage@...din.ro>,
linux-um <linux-um@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
regressions <regressions@...ts.linux.dev>
Subject: Re: [PATCH 1/1] um: fix error return code in winch_tramp()
----- Ursprüngliche Mail -----
> Von: "Nathan Chancellor" <nathan@...nel.org>
> 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.
Thanks,
//richard
Powered by blists - more mailing lists