All of lore.kernel.org
 help / color / mirror / Atom feed
From: subashab@codeaurora.org
To: Johannes Berg <johannes@sipsolutions.net>
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 14:07:27 -0600	[thread overview]
Message-ID: <2b6a7ddddbec7c610340e1e8c0eaf5fa@codeaurora.org> (raw)
In-Reply-To: <6442ec0e5e2cf55990b43ff178023fd6050e63fb.camel@sipsolutions.net>

On 2021-07-13 13:22, Johannes Berg wrote:
> On Sat, 2021-07-10 at 15:00 -0600, subashab@codeaurora.org wrote:
>> 
>> I have reverted the following patches (to allow for a clean revert)
>> and I don't see the panic anymore -
>> 
>> bfc58e2b98e99737409cd9f4d86a79677c5b887c
>> dc01a3b9db43abf95b801c9694980777a329e303
>> 9f0b4807a44ff81cf59421c8a86641efec586610
>> 84b2789d61156db0224724806b20110c0d34b07c
> 
> Out of those 4, the last ("separate child and...") seems actually less
> intrusive than the previous one. If you revert only the first three of
> this list, does it still happen?
> 

If only the first three reverts are applied, UML seems to hang during 
initialization-

printk: console [mc-1] enabled
EXT4-fs (ubda): mounting ext3 file system using the ext4 subsystem
EXT4-fs (ubda): mounted filesystem with ordered data mode. Opts: (null). 
Quota mode: none.
VFS: Mounted root (ext3 filesystem) readonly on device 98:0.
devtmpfs: mounted
This architecture does not have kernel memory protection.
Run /sbin/init as init process
INIT: version 2.88 booting
copy_context_skas0 - stub-parent reports error 3
INIT: cannot fork, retry..
copy_context_skas0 - stub-parent reports error 3
INIT: cannot fork, retry..
copy_context_skas0 - stub-parent reports error 3
INIT: cannot fork, retry..
random: fast init done
random: crng init done
copy_context_skas0 - stub-parent reports error 3
INIT: cannot fork, retry..
copy_context_skas0 - stub-parent reports error 3
INIT: cannot fork, retry..


> Does it still happen if you unset CONFIG_CC_OPTIMIZE_FOR_SIZE and do
> CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE instead?
> 
> johannes

If none of the reverts are applied and I set 
CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE,
I still see the initialization crash.

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um


      parent reply	other threads:[~2021-07-13 20:07 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
2021-07-13 20:16     ` subashab
2021-07-13 20:07   ` subashab [this message]

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=2b6a7ddddbec7c610340e1e8c0eaf5fa@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 \
    /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.