All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Roberto Oppedisano <roppedisano@infracomspa.it>
Cc: LKML <linux-kernel@vger.kernel.org>,
	dri-devel@lists.sourceforge.net, Dave Airlie <airlied@linux.ie>
Subject: Re: [PATCH] rate limit drm:radeon_cp_idle/reset errors
Date: Mon, 8 Sep 2008 21:08:36 -0700	[thread overview]
Message-ID: <20080908210836.fc5df672.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080906091919.GA5021@infracomspa.it>

On Sat, 6 Sep 2008 11:19:19 +0200 Roberto Oppedisano <roppedisano@infracomspa.it> wrote:

> When switching from kwin composite wm (KDE 4.1) to compiz I often hit the
> following error:
> 
> Sep  6 10:24:31 poppero1 kernel: [  186.138203] [drm:radeon_cp_idle] *ERROR* radeon_cp_idle called without lock held, held  0 owner f726bc80 f68f6840
> Sep  6 10:24:31 poppero1 kernel: [  186.138568] [drm:radeon_cp_reset] *ERROR* radeon_cp_reset called without lock held, held  0 owner f726bc80 f68f6840
> 
> probably due to broken X drivers/apps; after hitting this the error my laptop
> (hp nx7010) is totally unresponsitive to keyboard/mouse, also if it can be 
> shut down via the power button:
> 
> Sep  6 10:24:59 poppero1 powersave-wm_shutdown[4843]: DIAG: Process script for event button.power ID 10
> Sep  6 10:24:59 poppero1 powersave-wm_shutdown[4843]: INFO: Event: BUTTON_POWER occured.
> Sep  6 10:24:59 poppero1 powersave-wm_shutdown[4843]: INFO: Parameters: Event - button.power; Current Active Scheme: scheme_performance - ACPI event line: button/power PWRF 00000080
> 00000001
> Sep  6 10:25:00 poppero1 shutdown[4852]: shutting down for system halt
> ...
> 
> Without the attached patch, which rate limits DRM_ERROR, the syslog is flooded
> by thuosands of messages; here's the output with the patch applied.
> 
> Sep  6 10:24:31 poppero1 kernel: [  186.138774] [drm:radeon_cp_start] *ERROR* radeon_cp_start called without lock held, held  0 owner f726bc80 f68f6840
> Sep  6 10:24:31 poppero1 kernel: [  186.138968] [drm:radeon_cp_idle] *ERROR* radeon_cp_idle called without lock held, held  0 owner f726bc80 f68f6840
> Sep  6 10:24:31 poppero1 kernel: [  186.139214] [drm:radeon_cp_reset] *ERROR* radeon_cp_reset called without lock held, held  0 owner f726bc80 f68f6840
> Sep  6 10:24:31 poppero1 kernel: [  186.139408] [drm:radeon_cp_start] *ERROR* radeon_cp_start called without lock held, held  0 owner f726bc80 f68f6840
> Sep  6 10:24:31 poppero1 kernel: [  186.139601] [drm:radeon_cp_idle] *ERROR* radeon_cp_idle called without lock held, held  0 owner f726bc80 f68f6840
> Sep  6 10:24:31 poppero1 kernel: [  186.139866] [drm:radeon_cp_reset] *ERROR* radeon_cp_reset called without lock held, held  0 owner f726bc80 f68f6840
> Sep  6 10:24:31 poppero1 kernel: [  186.140072] [drm:radeon_cp_start] *ERROR* radeon_cp_start called without lock held, held  0 owner f726bc80 f68f6840
> Sep  6 10:24:31 poppero1 kernel: [  186.140467] [drm:radeon_cp_idle] *ERROR* radeon_cp_idle called without lock held, held  0 owner f726bc80 f68f6840
> Sep  6 10:24:36 poppero1 kernel: [  191.139019] __ratelimit: 253431 callbacks suppressed
> Sep  6 10:24:36 poppero1 kernel: [  191.139030] [drm:radeon_cp_reset] *ERROR* radeon_cp_reset called without lock held, held  0 owner f726bc80 f68f6840
> Sep  6 10:24:36 poppero1 kernel: [  191.139314] [drm:radeon_cp_start] *ERROR* radeon_cp_start called without lock held, held  0 owner f726bc80 f68f6840
> 
> Also if it doesn't solve a bug I think it may still be worth applying it. 
> Patch is against current git.
> 
> Signed-off-by: Roberto Oppedisano <roberto.oppedisano@infracom.it>
> 
> diff --git a/include/drm/drmP.h b/include/drm/drmP.h
> index 1c1b13e..1107361 100644
> --- a/include/drm/drmP.h
> +++ b/include/drm/drmP.h
> @@ -162,7 +162,8 @@ struct drm_device;
>   * \param arg arguments
>   */
>  #define DRM_ERROR(fmt, arg...) \
> -	printk(KERN_ERR "[" DRM_NAME ":%s] *ERROR* " fmt , __func__ , ##arg)
> +	if (printk_ratelimit()) \
> +		printk(KERN_ERR "[" DRM_NAME ":%s] *ERROR* " fmt , __func__ , ##arg)
>  
>  /**
>   * Memory error output.
> 

Which kernel version(s)?

  reply	other threads:[~2008-09-09  4:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-06  9:19 [PATCH] rate limit drm:radeon_cp_idle/reset errors Roberto Oppedisano
2008-09-09  4:08 ` Andrew Morton [this message]
2008-09-09  7:37   ` Roberto Oppedisano
2008-09-09  8:12     ` Andrew Morton
2008-09-09  8:15       ` Dave Airlie
2008-09-09 10:08         ` Roberto Oppedisano
2009-07-30  9:00         ` drm:radeon_cp_idle/reset error storm, console lockup (-rc4 git) Andreas Mohr
2009-07-30  9:10           ` Andreas Mohr
2009-07-30  9:21           ` Dave Airlie
2009-07-30  9:36             ` Andreas Mohr

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=20080908210836.fc5df672.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roppedisano@infracomspa.it \
    /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.