All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Daniel Vetter <daniel@ffwll.ch>,
	Jim Cromie <jim.cromie@gmail.com>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	stable@vger.kernel.org, David Airlie <airlied@gmail.com>
Subject: Re: [Intel-gfx] [PATCH] drm: Disable dynamic debug as broken
Date: Mon, 13 Feb 2023 18:43:31 +0200	[thread overview]
Message-ID: <875yc5v7m4.fsf@intel.com> (raw)
In-Reply-To: <878rh5x032.fsf@intel.com>

On Fri, 10 Feb 2023, Jani Nikula <jani.nikula@intel.com> wrote:
> On Tue, 07 Feb 2023, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>> On Tue, Feb 07, 2023 at 04:33:37PM +0200, Jani Nikula wrote:
>>> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>> 
>>> CONFIG_DRM_USE_DYNAMIC_DEBUG breaks debug prints for (at least modular)
>>> drm drivers. The debug prints can be reinstated by manually frobbing
>>> /sys/module/drm/parameters/debug after the fact, but at that point the
>>> damage is done and all debugs from driver probe are lost. This makes
>>> drivers totally undebuggable.
>>> 
>>> There's a more complete fix in progress [1], with further details, but
>>> we need this fixed in stable kernels. Mark the feature as broken and
>>> disable it by default, with hopes distros follow suit and disable it as
>>> well.
>>> 
>>> [1] https://lore.kernel.org/r/20230125203743.564009-1-jim.cromie@gmail.com
>>> 
>>> Fixes: 84ec67288c10 ("drm_print: wrap drm_*_dbg in dyndbg descriptor factory macro")
>>> Cc: Jim Cromie <jim.cromie@gmail.com>
>>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>>> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>>> Cc: Maxime Ripard <mripard@kernel.org>
>>> Cc: Thomas Zimmermann <tzimmermann@suse.de>
>>> Cc: David Airlie <airlied@gmail.com>
>>> Cc: Daniel Vetter <daniel@ffwll.ch>
>>> Cc: dri-devel@lists.freedesktop.org
>>> Cc: <stable@vger.kernel.org> # v6.1+
>>> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>>> ---
>>>  drivers/gpu/drm/Kconfig | 3 ++-
>>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>> 
>>> diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
>>> index f42d4c6a19f2..dc0f94f02a82 100644
>>> --- a/drivers/gpu/drm/Kconfig
>>> +++ b/drivers/gpu/drm/Kconfig
>>> @@ -52,7 +52,8 @@ config DRM_DEBUG_MM
>>>  
>>>  config DRM_USE_DYNAMIC_DEBUG
>>>  	bool "use dynamic debug to implement drm.debug"
>>> -	default y
>>> +	default n
>>> +	depends on BROKEN
>>>  	depends on DRM
>>>  	depends on DYNAMIC_DEBUG || DYNAMIC_DEBUG_CORE
>>>  	depends on JUMP_LABEL
>>
>> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> Thanks Greg, any more acks from anyone?
>
> Maxime, since there's going to be an -rc8, I suggest taking this via
> drm-misc-fixes. Is that okay with you? (You're doing drm-misc-fixes this
> round, right?)

Pushed to drm-misc-fixes with Maxime's IRC ack and Jim's ack elsewhere
in the thread. Thanks.

BR,
Jani.


>
> BR,
> Jani.

-- 
Jani Nikula, Intel Open Source Graphics Center

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	Thomas Zimmermann <tzimmermann@suse.de>,
	stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm: Disable dynamic debug as broken
Date: Mon, 13 Feb 2023 18:43:31 +0200	[thread overview]
Message-ID: <875yc5v7m4.fsf@intel.com> (raw)
In-Reply-To: <878rh5x032.fsf@intel.com>

On Fri, 10 Feb 2023, Jani Nikula <jani.nikula@intel.com> wrote:
> On Tue, 07 Feb 2023, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>> On Tue, Feb 07, 2023 at 04:33:37PM +0200, Jani Nikula wrote:
>>> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>> 
>>> CONFIG_DRM_USE_DYNAMIC_DEBUG breaks debug prints for (at least modular)
>>> drm drivers. The debug prints can be reinstated by manually frobbing
>>> /sys/module/drm/parameters/debug after the fact, but at that point the
>>> damage is done and all debugs from driver probe are lost. This makes
>>> drivers totally undebuggable.
>>> 
>>> There's a more complete fix in progress [1], with further details, but
>>> we need this fixed in stable kernels. Mark the feature as broken and
>>> disable it by default, with hopes distros follow suit and disable it as
>>> well.
>>> 
>>> [1] https://lore.kernel.org/r/20230125203743.564009-1-jim.cromie@gmail.com
>>> 
>>> Fixes: 84ec67288c10 ("drm_print: wrap drm_*_dbg in dyndbg descriptor factory macro")
>>> Cc: Jim Cromie <jim.cromie@gmail.com>
>>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>>> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>>> Cc: Maxime Ripard <mripard@kernel.org>
>>> Cc: Thomas Zimmermann <tzimmermann@suse.de>
>>> Cc: David Airlie <airlied@gmail.com>
>>> Cc: Daniel Vetter <daniel@ffwll.ch>
>>> Cc: dri-devel@lists.freedesktop.org
>>> Cc: <stable@vger.kernel.org> # v6.1+
>>> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>>> ---
>>>  drivers/gpu/drm/Kconfig | 3 ++-
>>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>> 
>>> diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
>>> index f42d4c6a19f2..dc0f94f02a82 100644
>>> --- a/drivers/gpu/drm/Kconfig
>>> +++ b/drivers/gpu/drm/Kconfig
>>> @@ -52,7 +52,8 @@ config DRM_DEBUG_MM
>>>  
>>>  config DRM_USE_DYNAMIC_DEBUG
>>>  	bool "use dynamic debug to implement drm.debug"
>>> -	default y
>>> +	default n
>>> +	depends on BROKEN
>>>  	depends on DRM
>>>  	depends on DYNAMIC_DEBUG || DYNAMIC_DEBUG_CORE
>>>  	depends on JUMP_LABEL
>>
>> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> Thanks Greg, any more acks from anyone?
>
> Maxime, since there's going to be an -rc8, I suggest taking this via
> drm-misc-fixes. Is that okay with you? (You're doing drm-misc-fixes this
> round, right?)

Pushed to drm-misc-fixes with Maxime's IRC ack and Jim's ack elsewhere
in the thread. Thanks.

BR,
Jani.


>
> BR,
> Jani.

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2023-02-13 16:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 14:33 [Intel-gfx] [PATCH] drm: Disable dynamic debug as broken Jani Nikula
2023-02-07 14:33 ` Jani Nikula
2023-02-07 14:33 ` Jani Nikula
2023-02-07 17:47 ` [Intel-gfx] " Greg Kroah-Hartman
2023-02-07 17:47   ` Greg Kroah-Hartman
2023-02-07 17:47   ` Greg Kroah-Hartman
2023-02-10 10:54   ` [Intel-gfx] " Jani Nikula
2023-02-10 10:54     ` Jani Nikula
2023-02-10 10:54     ` Jani Nikula
2023-02-13 16:43     ` Jani Nikula [this message]
2023-02-13 16:43       ` [Intel-gfx] " Jani Nikula
2023-02-07 17:50 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2023-02-07 18:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-02-07 21:03 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-02-10 17:26 ` [Intel-gfx] [PATCH] " jim.cromie
2023-02-10 17:26   ` jim.cromie
2023-02-10 17:26   ` jim.cromie

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=875yc5v7m4.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jim.cromie@gmail.com \
    --cc=mripard@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tzimmermann@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.