From: Serge Belyshev <belyshev@depni•sinp.msu.ru>
To: Christophe Leroy <christophe.leroy@csgroup•eu>
Cc: Paul Mackerras <paulus@samba•org>,
Andreas Schwab <schwab@linux-m68k•org>,
linuxppc-dev@lists•ozlabs.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH] powerpc/32s: Setup the early hash table at all time.
Date: Wed, 04 Nov 2020 17:53:01 +0300 [thread overview]
Message-ID: <87pn4tkwc2.fsf@depni.sinp.msu.ru> (raw)
In-Reply-To: <87wnz1lbce.fsf@depni.sinp.msu.ru> (Serge Belyshev's message of "Wed, 04 Nov 2020 12:28:49 +0300")
>>> To be sure we are not in front of a long lasting bug, could you try
>>> CONFIG_KASAN=y on v5.9 ?
>>
>> Indeed it started to fail somewhere between v5.6 and v5.7.
>>
>> v5.7 fails early with few messages on the console with reboot, v5.8 and
>> later hang right at bootloader.
>>
>> I'm bisecting now.
>
> (side note: I tried FB_OF=y instead of DRM_RADEON + DRM_FBDEV_* to speed
> up bisection and it turns out in that configuration KASAN never worked,
> down to commit 305d600123046, hanging right after bootloader or even
> with invalid access in the bootloader itself).
My bisection ended up nowhere (at net-next merge with 2k commits), and
given the above failure with unrelated configuration change, I conclude
that KASAN=y was always broken on this box.
next prev parent reply other threads:[~2020-11-04 14:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 15:35 [PATCH] powerpc/32s: Setup the early hash table at all time Christophe Leroy
2020-10-09 6:03 ` Michael Ellerman
2020-10-29 21:07 ` Andreas Schwab
2020-10-30 5:19 ` Michael Ellerman
2020-10-30 9:09 ` Andreas Schwab
2020-10-30 13:00 ` Christophe Leroy
2020-10-30 13:11 ` Andreas Schwab
2020-11-03 7:41 ` Christophe Leroy
2020-11-03 8:43 ` Andreas Schwab
2020-11-03 8:56 ` Andreas Schwab
2020-11-03 18:58 ` Serge Belyshev
2020-11-04 6:44 ` Christophe Leroy
2020-11-04 7:57 ` Serge Belyshev
2020-11-04 9:28 ` Serge Belyshev
2020-11-04 14:53 ` Serge Belyshev [this message]
2020-11-07 9:12 ` Christophe Leroy
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=87pn4tkwc2.fsf@depni.sinp.msu.ru \
--to=belyshev@depni$(echo .)sinp.msu.ru \
--cc=christophe.leroy@csgroup$(echo .)eu \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=paulus@samba$(echo .)org \
--cc=schwab@linux-m68k$(echo .)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