On Thu, May 16, 2024, Dave Airlie wrote:
> On Thu, 16 May 2024 at 08:56, Linus Torvalds
> wrote:
> > If the *main* CONFIG_WERROR is on, then it does NOT MATTER if somebody
> > sets CONFIG_DRM_WERROR or not. It's a no-op. It's pointless.
+1
> It's also possible it's just that hey there's a few o
On Thu, May 16, 2024 at 4:42 AM Jani Nikula wrote:
>
> On Wed, 15 May 2024, Linus Torvalds wrote:
> > On Wed, 15 May 2024 at 16:17, Dave Airlie wrote:
> >> AMDGPU, I915 and XE all have !COMPILE_TEST on their variants
> >
> > Hmm. It turns out that I didn't notice the AMDGPU one because my
> > T
On Wed, 15 May 2024, Linus Torvalds wrote:
> On Wed, 15 May 2024 at 16:17, Dave Airlie wrote:
>> AMDGPU, I915 and XE all have !COMPILE_TEST on their variants
>
> Hmm. It turns out that I didn't notice the AMDGPU one because my
> Threadripper - that has AMDGPU enabled - I have actually turned off
On 5/16/2024 8:12 AM, Dave Airlie wrote:
On Thu, 16 May 2024 at 10:06, Dave Airlie wrote:
On Thu, 16 May 2024 at 09:50, Dave Airlie wrote:
On Thu, 16 May 2024 at 06:29, Linus Torvalds
wrote:
On Wed, 15 May 2024 at 13:24, Linus Torvalds
wrote:
I have to revert both
a68c7eaa7a8f ("dr
On Thu, 16 May 2024 at 10:06, Dave Airlie wrote:
>
> On Thu, 16 May 2024 at 09:50, Dave Airlie wrote:
> >
> > On Thu, 16 May 2024 at 06:29, Linus Torvalds
> > wrote:
> > >
> > > On Wed, 15 May 2024 at 13:24, Linus Torvalds
> > > wrote:
> > > >
> > > > I have to revert both
> > > >
> > > > a68
On Thu, 16 May 2024 at 09:50, Dave Airlie wrote:
>
> On Thu, 16 May 2024 at 06:29, Linus Torvalds
> wrote:
> >
> > On Wed, 15 May 2024 at 13:24, Linus Torvalds
> > wrote:
> > >
> > > I have to revert both
> > >
> > > a68c7eaa7a8f ("drm/amdgpu: Enable clear page functionality")
> > > e362b7c8
On Wed, 15 May 2024 at 16:51, Dave Airlie wrote:
>
> > Let's see if the machine ends up being stable now. It took several
> > hours for the "scary messages" state to turn into the "hung machine"
> > state, so they *could* have been independent issues, but it seems a
> > bit unlikely.
>
> This worr
On Wed, 15 May 2024 at 16:17, Dave Airlie wrote:
>
> It's also possible it's just that hey there's a few others in the tree
>
> KVM_WERROR not tied to it
> PPC_WERROR (why does CXL uses this?)
Yeah, that should be fixed too, but at least KVM_WERROR predates the
whole-kernel WERROR.
And PPC_WERRO
On Thu, 16 May 2024 at 06:29, Linus Torvalds
wrote:
>
> On Wed, 15 May 2024 at 13:24, Linus Torvalds
> wrote:
> >
> > I have to revert both
> >
> > a68c7eaa7a8f ("drm/amdgpu: Enable clear page functionality")
> > e362b7c8f8c7 ("drm/amdgpu: Modify the contiguous flags behaviour")
> >
> > to ma
On Thu, 16 May 2024 at 06:29, Linus Torvalds
wrote:
>
> On Wed, 15 May 2024 at 13:24, Linus Torvalds
> wrote:
> >
> > I have to revert both
> >
> > a68c7eaa7a8f ("drm/amdgpu: Enable clear page functionality")
> > e362b7c8f8c7 ("drm/amdgpu: Modify the contiguous flags behaviour")
> >
> > to ma
On Thu, 16 May 2024 at 08:56, Linus Torvalds
wrote:
>
> On Wed, 15 May 2024 at 15:45, Dave Airlie wrote:
> >
> > The drm subsystem enables more warnings than the kernel default,
> > so
> > this config option is disabled by default.
>
> Irrelevant.
>
> If the *main* CONFIG_WER
On Wed, 15 May 2024 at 15:45, Dave Airlie wrote:
>
> The drm subsystem enables more warnings than the kernel default, so
> this config option is disabled by default.
Irrelevant.
If the *main* CONFIG_WERROR is on, then it does NOT MATTER if somebody
sets CONFIG_DRM_WERROR or n
On Thu, 16 May 2024 at 06:43, Linus Torvalds
wrote:
>
> On Tue, 14 May 2024 at 23:21, Dave Airlie wrote:
> >
> > This is the main pull request for the drm subsystems for 6.10.
>
> .. and now that I look more at this pull request, I find other things wrong.
>
> Why is the DRM code asking if I want
On Tue, 14 May 2024 at 23:21, Dave Airlie wrote:
>
> This is the main pull request for the drm subsystems for 6.10.
.. and now that I look more at this pull request, I find other things wrong.
Why is the DRM code asking if I want to enable -Werror? I have Werror
enabled *already*.
I hate stupid
On Wed, 15 May 2024 at 13:24, Linus Torvalds
wrote:
>
> I have to revert both
>
> a68c7eaa7a8f ("drm/amdgpu: Enable clear page functionality")
> e362b7c8f8c7 ("drm/amdgpu: Modify the contiguous flags behaviour")
>
> to make things build cleanly. Next step: see if it boots and fixes the
> probl
On Wed, 15 May 2024 at 13:21, Linus Torvalds
wrote:
>
> I guess I'll try to revert the later commit that enables it for amdgpu
> (commit a68c7eaa7a8f) and see if it at least makes the horrendous
> messages go away.
I have to revert both
a68c7eaa7a8f ("drm/amdgpu: Enable clear page functionalit
On Wed, 15 May 2024 at 13:06, Linus Torvalds
wrote:
>
> Hmm. There's something seriously wrong with amdgpu.
>
> I'm getting a ton of__force_merge warnings:
>
> WARNING: CPU: 0 PID: 1069 at drivers/gpu/drm/drm_buddy.c:199
> __force_merge+0x14f/0x180 [drm_buddy]
Adding likely culprits to the part
On Tue, 14 May 2024 at 23:21, Dave Airlie wrote:
>
> In drivers the main thing is a new driver for ARM Mali firmware based
> GPUs, otherwise there are a lot of changes to amdgpu/xe/i915/msm and
> scattered changes to everything else.
Hmm. There's something seriously wrong with amdgpu.
I'm gettin
The pull request you sent on Wed, 15 May 2024 16:20:56 +1000:
> https://gitlab.freedesktop.org/drm/kernel.git tags/drm-next-2024-05-15
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/db5d28c0bfe566908719bec8e25443aabecbb802
Thank you!
--
Deet-doot-dot, I am a bot.
ht
19 matches
Mail list logo
