From: Nathan Chancellor <nathan@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Richard Weinberger <richard@nod.at>,
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: Fri, 20 May 2022 08:55:40 -0700 [thread overview]
Message-ID: <Yoe5/HwL9DXhaw7Z@dev-arch.thelio-3990X> (raw)
In-Reply-To: <e9597cbc-cabb-facf-deb6-662d40cf16a3@leemhuis.info>
On Fri, May 20, 2022 at 08:08:01AM +0200, Thorsten Leemhuis wrote:
> On 11.04.22 20:45, Richard Weinberger wrote:
> > ----- 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.
>
> 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
WARNING: multiple messages have this Message-ID (diff)
From: Nathan Chancellor <nathan@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Richard Weinberger <richard@nod.at>,
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: Fri, 20 May 2022 08:55:40 -0700 [thread overview]
Message-ID: <Yoe5/HwL9DXhaw7Z@dev-arch.thelio-3990X> (raw)
In-Reply-To: <e9597cbc-cabb-facf-deb6-662d40cf16a3@leemhuis.info>
On Fri, May 20, 2022 at 08:08:01AM +0200, Thorsten Leemhuis wrote:
> On 11.04.22 20:45, Richard Weinberger wrote:
> > ----- 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.
>
> 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
next prev parent reply other threads:[~2022-05-20 15:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 3:22 [PATCH 1/1] um: fix error return code in winch_tramp() Zhen Lei
2021-05-08 3:22 ` Zhen Lei
2021-05-08 9:13 ` Anton Ivanov
2021-05-08 9:13 ` Anton Ivanov
2022-03-23 19:41 ` Nathan Chancellor
2022-03-23 19:41 ` Nathan Chancellor
2022-03-24 12:40 ` Thorsten Leemhuis
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 8:41 ` Thorsten Leemhuis
2022-04-10 9:33 ` Richard Weinberger
2022-04-10 9:33 ` Richard Weinberger
2022-04-11 17:48 ` Nathan Chancellor
2022-04-11 17:48 ` Nathan Chancellor
2022-04-11 18:45 ` Richard Weinberger
2022-04-11 18:45 ` Richard Weinberger
2022-05-20 6:08 ` Thorsten Leemhuis
2022-05-20 6:08 ` Thorsten Leemhuis
2022-05-20 15:55 ` Nathan Chancellor [this message]
2022-05-20 15:55 ` Nathan Chancellor
2022-05-20 17:18 ` Johannes Berg
2022-05-20 17:18 ` Johannes Berg
2022-05-20 17:31 ` Nathan Chancellor
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=Yoe5/HwL9DXhaw7Z@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--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=ndesaulniers@google.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=richard@nod.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.