On Fri, Nov 29, 2024 at 4:57 PM Linus Torvalds
wrote:
>
> On Thu, 28 Nov 2024 at 12:42, Dave Airlie wrote:
> >
> > Merge window fixes, mostly amdgpu and xe, with a few other minor ones,
> > all looks fairly normal,
>
> Hmm. I've pulled this, but do note the report by Sasha.
>
> The
>
> if
On Fri, 29 Nov 2024 at 14:59, Sasha Levin wrote:
>
> I should be able to reuse their config and just add debug info, no?
Sadly, no. Not unless you exactly match their compiler version. And it
looks like you don't, because the line numbers make no sense.
For example, this is the thing I would exp
On Fri, Nov 29, 2024 at 01:31:37PM -0800, Linus Torvalds wrote:
Sasha - it would help if your warning stack dumps had line numbers
(using decode_stacktrace.sh, which you should be familiar with, since
you wrote it...)
I realize that requires some debug info, which might slow down builds
etc, but
The pull request you sent on Fri, 29 Nov 2024 06:42:18 +1000:
> https://gitlab.freedesktop.org/drm/kernel.git tags/drm-next-2024-11-29
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2ba9f676d0a2e408aef14d679984c26373bf37b7
Thank you!
--
Deet-doot-dot, I am a bot.
ht
On Thu, 28 Nov 2024 at 12:42, Dave Airlie wrote:
>
> Merge window fixes, mostly amdgpu and xe, with a few other minor ones,
> all looks fairly normal,
Hmm. I've pulled this, but do note the report by Sasha.
The
if (WARN_ON(!work->func))
return false;
from __flush_work()
On Fri, Nov 29, 2024 at 06:42:18AM +1000, Dave Airlie wrote:
Hi Linus,
Merge window fixes, mostly amdgpu and xe, with a few other minor ones,
all looks fairly normal,
Hi folks,
I've also started seeing the following warning after the merge into
linus-next:
[4.495349] UBSAN: shift-out-of-
[+cc Alex]
On Fri, Nov 29, 2024 at 06:42:18AM +1000, Dave Airlie wrote:
Alex Deucher (3):
drm/amdgpu/jpeg: cancel the jpeg worker
Hi folks,
When merging this PR into linus-next I've started the following warning
triggered by the commit above:
[4.356975] WARNING: CPU: 1 PID: 1 at ker
