From: Guenter Roeck <linux@roeck-us.net>
To: Helge Deller <deller@gmx.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org
Cc: patches@lists.linux.dev, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@denx.de,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org,
Oleg Nesterov <oleg@redhat.com>,
linux-parisc@vger.kernel.org,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH 6.1 000/217] 6.1.95-rc1 review [parisc64/C3700 boot failures]
Date: Sat, 22 Jun 2024 09:37:54 -0700 [thread overview]
Message-ID: <11983f65-ec2f-4092-917f-7a09bae7c4b2@roeck-us.net> (raw)
In-Reply-To: <48aa5db8-2605-42e3-a1e3-1bf3428380ee@gmx.de>
On 6/22/24 08:49, Helge Deller wrote:
> On 6/22/24 17:34, Guenter Roeck wrote:
>> On 6/22/24 08:13, Helge Deller wrote:
>>> On 6/22/24 16:58, Guenter Roeck wrote:
>>>> [ Copying parisc maintainers - maybe they can test on real hardware ]
>>>>
>>>> On 6/19/24 05:54, Greg Kroah-Hartman wrote:
>>>>> This is the start of the stable review cycle for the 6.1.95 release.
>>>>> There are 217 patches in this series, all will be posted as a response
>>>>> to this one. If anyone has any issues with these being applied, please
>>>>> let me know.
>>>>>
>>>>> Responses should be made by Fri, 21 Jun 2024 12:55:11 +0000.
>>>>> Anything received after that time might be too late.
>>>>>
>>>> ...
>>>>> Oleg Nesterov <oleg@redhat.com>
>>>>> zap_pid_ns_processes: clear TIF_NOTIFY_SIGNAL along with TIF_SIGPENDING
>>>>>
>>>>
>>>> I can not explain it, but this patch causes all my parisc64 (C3700)
>>>> boot tests to crash. There are lots of memory corruption BUGs such as
>>>>
>>>> [ 0.000000] =============================================================================
>>>> [ 0.000000] BUG kmalloc-96 (Not tainted): Padding overwritten. 0x0000000043411dd0-0x0000000043411f5f @offset=3536
>>>>
>>>> ultimately followed by
>>>>
>>>> [ 0.462562] Unaligned handler failed, ret = -14
>>>> ...
>>>> [ 0.469160] IAOQ[0]: idr_alloc_cyclic+0x48/0x118
>>>> [ 0.469372] IAOQ[1]: idr_alloc_cyclic+0x54/0x118
>>>> [ 0.469548] RP(r2): __kernfs_new_node.constprop.0+0x160/0x420
>>>> [ 0.469782] Backtrace:
>>>> [ 0.469928] [<00000000404af108>] __kernfs_new_node.constprop.0+0x160/0x420
>>>> [ 0.470285] [<00000000404b0cac>] kernfs_new_node+0xbc/0x118
>>>> [ 0.470523] [<00000000404b158c>] kernfs_create_empty_dir+0x54/0xf0
>>>> [ 0.470756] [<00000000404b665c>] sysfs_create_mount_point+0x4c/0xb0
>>>> [ 0.470996] [<00000000401181cc>] cgroup_init+0x5b4/0x738
>>>> [ 0.471213] [<0000000040102220>] start_kernel+0x1238/0x1308
>>>> [ 0.471429] [<0000000040107c90>] start_parisc+0x188/0x1d0
>>>> ...
>>>> [ 0.474956] Kernel panic - not syncing: Attempted to kill the idle task!
>>>> SeaBIOS wants SYSTEM RESET.
>>>>
>>>> This is with qemu v9.0.1.
>>>
>>> Just to be sure, did you tested the same kernel on physical hardware as well?
>>>
>>
>> No, I don't have hardware. I only have qemu. That is why I copied you and
>> the parisc mailing list.
>
> Yes, sorry, I saw your top line in the mail after I already sent my reply....
>
>> I would hope that someone can either confirm that
>> this is a real problem or that it is qemu related. If it is qemu related,
>> I'll just stop testing c3700 64-bit support with qemu on v6.1.y and other
>> branches if/when the problem shows up there as well.
>
> I just booted 6.1.95 successfully in qemu and on my physical C3700 machine.
> I assume the problem can be reproduced with your .config ?
> Please send it to me off-list, then I can try again.
>
Done.
Thanks,
Guenter
next prev parent reply other threads:[~2024-06-22 16:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 12:54 [PATCH 6.1 000/217] 6.1.95-rc1 review Greg Kroah-Hartman
2024-06-19 14:22 ` Florian Fainelli
2024-06-19 17:06 ` SeongJae Park
2024-06-19 19:52 ` Jon Hunter
2024-06-19 20:53 ` Pavel Machek
2024-06-19 21:13 ` Allen
2024-06-20 3:43 ` Kelsey Steele
2024-06-20 11:41 ` Mark Brown
2024-06-20 14:34 ` Ron Economos
2024-06-20 16:23 ` Naresh Kamboju
2024-06-20 17:32 ` Sven Joachim
2024-06-20 20:08 ` Peter Schneider
2024-06-20 21:39 ` Shuah Khan
2024-06-22 14:58 ` [PATCH 6.1 000/217] 6.1.95-rc1 review [parisc64/C3700 boot failures] Guenter Roeck
2024-06-22 15:13 ` Helge Deller
2024-06-22 15:34 ` Guenter Roeck
2024-06-22 15:49 ` Helge Deller
2024-06-22 16:37 ` Guenter Roeck [this message]
2024-06-22 17:21 ` Guenter Roeck
2024-06-23 14:28 ` Guenter Roeck
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=11983f65-ec2f-4092-917f-7a09bae7c4b2@roeck-us.net \
--to=linux@roeck-us.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=deller@gmx.de \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=oleg@redhat.com \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®