All of lore.kernel.org
 help / color / mirror / Atom feed
From: mbrugger@suse.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: undefined instruction d5380001 (arm64 mrs emulation)
Date: Fri, 6 Oct 2017 15:57:57 +0200	[thread overview]
Message-ID: <27e1bd48-3b6c-5dec-2fb4-cf4625ca5299@suse.com> (raw)
In-Reply-To: <20171006131343.rs7ig4owz4anw3cl@armageddon.cambridge.arm.com>



On 10/06/2017 03:13 PM, Catalin Marinas wrote:
> On Fri, Oct 06, 2017 at 02:05:09PM +0200, Matthias Brugger wrote:
>> On 10/05/2017 06:16 PM, Catalin Marinas wrote:
>>> On Thu, Oct 05, 2017 at 04:54:09PM +0200, Matthias Brugger wrote:
>>>> We also hit this bug in openSUSE Tumbleweed:
>>>> https://bugzilla.suse.com/show_bug.cgi?id=1061188
>>>
>>> As Mark replied, we are still debating why this happens and whether the
>>> above fix is sufficient. As we were digging further, we realised there
>>> is no clear init level after which user space can be invoked, which
>>> means Suzuki's patch may not always be sufficient.
>>>
>>> I proposed something as a way of spotting this issue early [1] but I
>>> need to post it on the linux-arch to get some consensus.
>>>
>>> Can you post the full kernel log somewhere? I'm trying to figure out
>>> what trigged the modprobe during the kernel boot.
>>>
>>
>> You can find the kernel log here:
>> https://bugzilla.suse.com/attachment.cgi?id=743311
> 
> Thanks, it seems that ipv6 module loading triggered this.
> 
> Talking to Suzuki, we came to the conclusion that such thing cannot
> happen before rootfs_initcall, so his original core_initcall change
> should suffice. I'll push a patch out, hopefully for -rc4 and cc stable.
> 

Thanks for the info.
Matthias

      reply	other threads:[~2017-10-06 13:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-29 19:23 undefined instruction d5380001 Matwey V. Kornilov
2017-10-02 11:24 ` Dave Martin
2017-10-02 14:11   ` undefined instruction d5380001 (arm64 mrs emulation) James Morse
2017-10-02 15:56     ` Suzuki K Poulose
2017-10-04  9:11       ` Matwey V. Kornilov
2017-10-05 14:54         ` Matthias Brugger
2017-10-05 14:59           ` Mark Rutland
2017-10-05 16:16           ` Catalin Marinas
2017-10-06 12:05             ` Matthias Brugger
2017-10-06 13:13               ` Catalin Marinas
2017-10-06 13:57                 ` Matthias Brugger [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=27e1bd48-3b6c-5dec-2fb4-cf4625ca5299@suse.com \
    --to=mbrugger@suse.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.