LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Andrea Righi <andrea.righi@canonical.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	Nicholas Piggin <npiggin@gmail.com>,
	Oleg Nesterov <oleg@redhat.com>
Subject: Re: boot regression on ppc64 with linux 6.2
Date: Thu, 16 Mar 2023 11:33:59 +1100	[thread overview]
Message-ID: <87zg8dmt54.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <ZBFhUAlL+1ZVKcwQ@righiandr-XPS-13-7390>

Andrea Righi <andrea.righi@canonical.com> writes:
> On Wed, Mar 15, 2023 at 02:30:53PM +1100, Michael Ellerman wrote:
>> Andrea Righi <andrea.righi@canonical.com> writes:
>> > I'm triggering the following bug when booting my qemu powerpc VM:
>> 
>> I'm not seeing that here :/
>> 
>> Can you give a bit more detail?
>>  - qemu version
>>  - qemu command line
>>  - what userspace are you using?
>>  - full dmesg of the failing case
>
> Yeah, ignore this for now, it could be related to another custom patch
> that I had applied (and forgot about it sorry), this one:
> https://lore.kernel.org/lkml/20230119155709.20d87e35.gary@garyguo.net/T/

OK. Did you do the bisect with that patch applied though?

> That is causing other issues on ppc64, so I think it might be related to
> that, I'll do more tests making sure I use a vanilla kernel.

I don't see an obvious connection between the modversions stuff and this
crash, but I guess it's possible.

cheers

      parent reply	other threads:[~2023-03-16  0:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13  9:08 boot regression on ppc64 with linux 6.2 Andrea Righi
2023-03-15  3:30 ` Michael Ellerman
2023-03-15  6:10   ` Andrea Righi
2023-03-15  6:42     ` Andrea Righi
2023-03-16  0:33     ` Michael Ellerman [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=87zg8dmt54.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=andrea.righi@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=npiggin@gmail.com \
    --cc=oleg@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox