From: Johannes Berg <johannes@sipsolutions.net>
To: subashab@codeaurora.org
Cc: jdike@addtoit.com, richard@nod.at,
anton.ivanov@cambridgegreys.com, linux-um@lists.infradead.org
Subject: Re: UML kernel panic on initialization
Date: Tue, 13 Jul 2021 22:41:51 +0200 [thread overview]
Message-ID: <87c5c7bcfc4ee0e6e006b50ea35b4710340ffd99.camel@sipsolutions.net> (raw)
In-Reply-To: <067d008eef6bd19e6fee22f16db40628@codeaurora.org>
On Tue, 2021-07-13 at 14:40 -0600, subashab@codeaurora.org wrote:
> > [snip]
> >
> > And as yet another experiment in this area, does it work again if
> > you
> > apply this patch?
> >
> > https://patchwork.ozlabs.org/project/linux-um/patch/20210303155523.124277-11-benjamin@sipsolutions.net/
> >
> > Not sure it applies as-is, but you can see the schema there.
> >
> > johannes
>
> If this patch is applied without any reverts the crash is seen.
> If patch is applied with the 3 reverts applied, the initialization
> is hanging.
>
IOW, it didn't change anything :)
Thanks for all the experiments, we're looking at the compilation
especially wrt. that one reverted hunk now.
johannes
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2021-07-13 20:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 21:00 UML kernel panic on initialization subashab
2021-07-11 20:27 ` YiFei Zhu
2021-07-12 18:19 ` subashab
2021-07-13 4:04 ` YiFei Zhu
2021-07-13 13:50 ` Anton Ivanov
2021-07-13 14:03 ` Richard Weinberger
2021-07-13 18:02 ` subashab
2021-07-13 18:32 ` Johannes Berg
2021-07-13 18:54 ` subashab
2021-07-13 19:17 ` Johannes Berg
2021-07-13 20:00 ` subashab
2021-07-13 20:52 ` YiFei Zhu
2021-07-13 22:14 ` Richard Weinberger
2021-07-13 17:47 ` subashab
2021-07-13 19:22 ` Johannes Berg
2021-07-13 19:26 ` Johannes Berg
2021-07-13 19:28 ` Johannes Berg
2021-07-13 20:40 ` subashab
2021-07-13 20:41 ` Johannes Berg [this message]
2021-07-13 20:16 ` subashab
2021-07-13 20:07 ` subashab
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=87c5c7bcfc4ee0e6e006b50ea35b4710340ffd99.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=anton.ivanov@cambridgegreys.com \
--cc=jdike@addtoit.com \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
--cc=subashab@codeaurora.org \
/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).