From: subashab@codeaurora.org
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Richard Weinberger <richard@nod.at>,
anton ivanov <anton.ivanov@cambridgegreys.com>,
YiFei Zhu <zhuyifei1999@gmail.com>, Jeff Dike <jdike@addtoit.com>,
linux-um <linux-um@lists.infradead.org>,
stranche@codeaurora.org
Subject: Re: UML kernel panic on initialization
Date: Tue, 13 Jul 2021 12:54:04 -0600 [thread overview]
Message-ID: <5a402bd444a2c9926f9b3945beb4b5a2@codeaurora.org> (raw)
In-Reply-To: <66cdf3de4a10308be633b1dc40567857c55df9aa.camel@sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 203 bytes --]
> Well, I think Richard meant your *hosts* ld.so, not your rootfs inside
> the guest/VM.
>
> FWIW, even with your config I cannot reproduce this.
>
> johannes
Sure, I have attached the host ld.so now.
[-- Attachment #2: ld-2.23.so --]
[-- Type: application/x-sharedlib, Size: 162632 bytes --]
[-- Attachment #3: Type: text/plain, Size: 152 bytes --]
_______________________________________________
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 18:54 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 [this message]
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
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=5a402bd444a2c9926f9b3945beb4b5a2@codeaurora.org \
--to=subashab@codeaurora.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=jdike@addtoit.com \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
--cc=stranche@codeaurora.org \
--cc=zhuyifei1999@gmail.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.