From: Michael Ellerman <mpe@ellerman•id.au>
To: Murphy Zhou <jencce.kernel@gmail•com>,
Bagas Sanjaya <bagasdotme@gmail•com>
Cc: Linux-Next <linux-next@vger•kernel.org>, linuxppc-dev@lists•ozlabs.org
Subject: Re: linux-next tree panic on ppc64le
Date: Thu, 23 Feb 2023 16:10:17 +1100 [thread overview]
Message-ID: <87a615arwm.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <CADJHv_u7CGt9oM68YCLSmZTJvdq0rXcVu_1VMT=a9R3VNf8pKg@mail.gmail.com>
Murphy Zhou <jencce.kernel@gmail•com> writes:
> On Wed, Feb 22, 2023 at 10:35 AM Bagas Sanjaya <bagasdotme@gmail•com> wrote:
>> On 2/22/23 07:55, Murphy Zhou wrote:
>> > [ 59.558339] ------------[ cut here ]------------
>> > [ 59.558361] kernel BUG at arch/powerpc/kernel/syscall.c:34!
>> > [ 59.558373] Oops: Exception in kernel mode, sig: 5 [#1]
>> > [ 59.558384] LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=2048 NUMA PowerNV
>> > [ 59.558397] Modules linked in: rfkill i2c_dev sunrpc ast
>> > i2c_algo_bit drm_shmem_helper drm_kms_helper ext4 syscopyarea
>> > sysfillrect sysimgblt ofpart ses powernv_flash enclosure
>> > scsi_transport_sas ipmi_powernv at24 mbcache jbd2 ipmi_devintf
>> > regmap_i2c opal_prd ipmi_msghandler mtd ibmpowernv drm fuse
>> > drm_panel_orientation_quirks xfs libcrc32c sd_mod t10_pi
>> > crc64_rocksoft_generic crc64_rocksoft crc64 sg i40e aacraid vmx_crypto
>> > [ 59.558494] CPU: 29 PID: 6366 Comm: kexec Not tainted 6.2.0-next-20230221 #1
...
>> > [ 60.564336]
>> > [ 61.564343] Kernel panic - not syncing: Fatal exception
>>
>> Panic on what linux-next tag? Can you test powerpc/next tree?
> powerpc/next tree does not panic.
Because I applied the fix last night :)
Which is:
f82cdc37c4bd ("powerpc/pseries: Avoid hcall in plpks_is_available() on non-pseries")
Thanks for the report.
cheers
prev parent reply other threads:[~2023-02-23 5:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 0:55 linux-next tree panic on ppc64le Murphy Zhou
2023-02-22 2:35 ` Bagas Sanjaya
2023-02-22 9:13 ` Murphy Zhou
2023-02-22 12:21 ` Bagas Sanjaya
2023-02-22 23:52 ` Murphy Zhou
2023-02-23 5:10 ` 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=87a615arwm.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=bagasdotme@gmail$(echo .)com \
--cc=jencce.kernel@gmail$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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