linux-next - DEBUG_MUTEX=y causes message flood

2019-11-20 Thread Valdis Klētnieks
I haven't narrowed down when this started, other than "sometime between 10/23 and 11/13". Looks to me like something in the i915/DRM arena doesn't play nice with mutex debugging. The system still acts fine, but my /var partition filled up due to gigabytes of the following two warning calls repeat

next-20230726 and later - crash in radeon module during init

2023-08-10 Thread Valdis Klētnieks
I am seeing the following consistent crash at boot: [ 61.211213][ T819] [drm] radeon kernel modesetting enabled. [ 61.584870][ T819] vga_switcheroo: detected switching method \_SB_.PCI0.GFX0.ATPX handle [ 61.667507][ T819] ATPX version 1, functions 0x0033 [ 61.748228][ T819] gener

Re: next-20230726 and later - crash in radeon module during init

2023-08-10 Thread Valdis Klētnieks
On Thu, 10 Aug 2023 05:35:02 -0400, "Valdis Klētnieks" said: > I am seeing the following consistent crash at boot: > Some quick digging indicates the most likely culprit is: > > commit cbd0606e6a776bf2ba10d4a6957bb7628c0da947 > Author: Srinivasan Shanmugam > Date: Thu Jul 20 15:39:24 2023 +05

linux-next 20200508 - build failure in kernel/resource.c w/ SPARSEMEM=n

2020-05-09 Thread Valdis Klētnieks
So I did a 'make allmodconfig' and then a 'make' on an RPi4 ARM box, and it decided that CONFIG_SPARSEMEM=n was OK (so an include of linux/mmzone.h doesn't define some needed values). The offending code in resource.c is wrapped in a #ifdef CONFIG_DEVICE_PRIVATE, which throws a whinge during 'make