From: Linus Torvalds <torvalds@linux-foundation.org>
To: Guenter Roeck <linux@roeck-us.net>,
Harry Wentland <harry.wentland@amd.com>,
Leo Li <sunpeng.li@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Balbir Singh <bsingharora@gmail.com>,
Daniel Axtens <dja@axtens.net>,
Paul Mackerras <paulus@ozlabs.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: Linux 5.19-rc6
Date: Wed, 13 Jul 2022 12:36:50 -0700 [thread overview]
Message-ID: <CAHk-=widUqghhXus_GCM9+FESa5vHqMb_pO3=0dGYH8C+yix2w@mail.gmail.com> (raw)
In-Reply-To: <20220713050724.GA2471738@roeck-us.net>
On Tue, Jul 12, 2022 at 10:07 PM Guenter Roeck <linux@roeck-us.net> wrote:
>
> Same problems as every week.
>
> Building powerpc:allmodconfig ... failed
Ok, this has been going on since -rc1, which is much too long.
From your patch submission that that was rejected:
> The problem was introduced with commit 41b7a347bf14 ("powerpc: Book3S
> 64-bit outline-only KASAN support") which adds support for KASAN. This
> commit in turn enables DRM_AMD_DC_DCN because KCOV_INSTRUMENT_ALL and
> KCOV_ENABLE_COMPARISONS are no longer enabled. As result, new files are
> compiled which lack the selection of hard-float.
And considering that neither the ppc people nor the drm people seem
interested in fixing this, and it doesn't revert cleanly I think the
sane solution seems to be to just remove PPC64 support for DRM_AMD_DC
entirely.
IOW, does something like this (obviously nor a proper patch, but you
get the idea) fix the ppc build for you?
@@ -6,7 +6,7 @@ config DRM_AMD_DC
bool "AMD DC - Enable new display engine"
default y
select SND_HDA_COMPONENT if SND_HDA_CORE
- select DRM_AMD_DC_DCN if (X86 || PPC64) &&
!(KCOV_INSTRUMENT_ALL && KCOV_ENABLE_COMPARISONS)
+ select DRM_AMD_DC_DCN if X86 && !(KCOV_INSTRUMENT_ALL &&
KCOV_ENABLE_COMPARISONS)
help
Choose this option if you want to use the new display engine
support for AMDGPU. This adds required support for Vega and
> OF: amba_device_add() failed (-19) for /amba/smc@10100000
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 1 at lib/refcount.c:28 of_platform_bus_create+0x33c/0x3dc
> refcount_t: underflow; use-after-free.
This too has been going on since -rc1, but it's not obvious what caused it.
At a guess, looking around the amba changes, I'm assuming it's
7719a68b2fa4 ("ARM: 9192/1: amba: fix memory leak in amba_device_try_add()")
Does reverting that commit make it go away?
Linus
next prev parent reply other threads:[~2022-07-13 19:37 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 21:54 Linux 5.19-rc6 Linus Torvalds
2022-07-11 6:44 ` Build regressions/improvements in v5.19-rc6 Geert Uytterhoeven
2022-07-13 5:07 ` Linux 5.19-rc6 Guenter Roeck
2022-07-13 19:36 ` Linus Torvalds [this message]
2022-07-13 19:48 ` Russell King (Oracle)
2022-07-13 20:21 ` Linus Torvalds
2022-07-13 20:40 ` Guenter Roeck
2022-07-13 20:42 ` Linus Torvalds
2022-07-14 12:20 ` Russell King (Oracle)
2022-07-14 12:14 ` Russell King (Oracle)
2022-07-13 21:36 ` Sudip Mukherjee
2022-07-13 21:45 ` Linus Torvalds
2022-07-13 21:50 ` Sudip Mukherjee
2022-07-13 22:56 ` Guenter Roeck
2022-07-13 23:09 ` Sudip Mukherjee
2022-07-13 23:12 ` Guenter Roeck
2022-07-13 23:26 ` Sudip Mukherjee
2022-07-13 23:44 ` Guenter Roeck
2022-07-13 23:02 ` Guenter Roeck
2022-07-14 1:30 ` Kefeng Wang
2022-07-13 19:53 ` Alex Deucher
2022-07-13 20:22 ` Linus Torvalds
2022-07-13 20:45 ` Guenter Roeck
2022-07-13 20:46 ` Guenter Roeck
2022-07-13 20:50 ` Linus Torvalds
2022-07-13 21:00 ` Alex Deucher
2022-07-13 21:32 ` Linus Torvalds
2022-07-14 7:23 ` Geert Uytterhoeven
2022-07-14 13:20 ` Guenter Roeck
2022-07-14 13:56 ` Geert Uytterhoeven
2022-07-14 16:48 ` Linus Torvalds
2022-07-14 17:24 ` Guenter Roeck
2022-07-14 17:37 ` Linus Torvalds
2022-07-15 7:26 ` Geert Uytterhoeven
2022-07-14 16:52 ` Alex Deucher
2022-07-14 23:16 ` Russell Currey
2022-07-15 9:33 ` Sudip Mukherjee
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='CAHk-=widUqghhXus_GCM9+FESa5vHqMb_pO3=0dGYH8C+yix2w@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bsingharora@gmail.com \
--cc=dja@axtens.net \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mpe@ellerman.id.au \
--cc=paulus@ozlabs.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=sunpeng.li@amd.com \
--cc=wangkefeng.wang@huawei.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;
as well as URLs for NNTP newsgroup(s).