regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	 Zhen Lei <thunder.leizhen@huawei.com>,
	Jeff Dike <jdike@addtoit.com>,
	 anton ivanov <anton.ivanov@cambridgegreys.com>,
	 Andrew Morton <akpm@linux-foundation.org>,
	 Eduard-Gabriel Munteanu <maxdamage@aladin.ro>,
	 linux-um <linux-um@lists.infradead.org>,
	 linux-kernel <linux-kernel@vger.kernel.org>,
	 Nick Desaulniers <ndesaulniers@google.com>,
	 regressions <regressions@lists.linux.dev>
Subject: Re: [PATCH 1/1] um: fix error return code in winch_tramp()
Date: Mon, 11 Apr 2022 20:45:24 +0200 (CEST)	[thread overview]
Message-ID: <1287561645.244713.1649702724736.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <YlRp9KR1mp3/4Txo@thelio-3990X>

----- Ursprüngliche Mail -----
> Von: "Nathan Chancellor" <nathan@kernel.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

  reply	other threads:[~2022-04-11 18:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210508032239.2177-1-thunder.leizhen@huawei.com>
2022-03-23 19:41 ` [PATCH 1/1] um: fix error return code in winch_tramp() Nathan Chancellor
2022-03-24 12:40   ` Thorsten Leemhuis
2022-05-31  8:17     ` [PATCH 1/1] um: fix error return code in winch_tramp() #forregzbot Thorsten Leemhuis
2022-04-10  8:41   ` [PATCH 1/1] um: fix error return code in winch_tramp() Thorsten Leemhuis
2022-04-10  9:33     ` Richard Weinberger
2022-04-11 17:48       ` Nathan Chancellor
2022-04-11 18:45         ` Richard Weinberger [this message]
2022-05-20  6:08           ` Thorsten Leemhuis
2022-05-20 15:55             ` Nathan Chancellor
2022-05-20 17:18               ` Johannes Berg
2022-05-20 17:31                 ` Nathan Chancellor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1287561645.244713.1649702724736.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=akpm@linux-foundation.org \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=maxdamage@aladin.ro \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=thunder.leizhen@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).