public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"Theodore Ts'o" <tytso@mit.edu>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Oops/Warning report for the week of September 10th, 2008
Date: Wed, 10 Sep 2008 21:52:55 -0700	[thread overview]
Message-ID: <20080911045255.GD6863@suse.de> (raw)
In-Reply-To: <48C81D20.9040302@linux.intel.com>

On Wed, Sep 10, 2008 at 12:16:48PM -0700, Arjan van de Ven wrote:
>
> Rank 2: sysfs_add_one (warning)
> 	Reported 215 times (3751 total reports)
> 	Duplicate sysfs registration; mostly in USB audio
> 	This warning was last seen in version 2.6.27-rc5, and first seen in 
> 2.6.24-rc6.
> 	More info: http://www.kerneloops.org/searchweek.php?search=sysfs_add_one

This one is going to be a bit tough to track over time as it is the low
level sysfs code complaining that a user of it is doing something wrong.
So you can get all sorts of different callers causing the same warning,
we just have to look at the backtrace to get a hint of who is causing
the problem.

Is there any way to break this one down further by caller so we can try
to narrow it down?  I thought you did that for other types of warnings
in the past (may_sleep(), etc.)

thanks,

greg k-h

  parent reply	other threads:[~2008-09-11  5:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10 19:16 Oops/Warning report for the week of September 10th, 2008 Arjan van de Ven
2008-09-10 19:36 ` Thomas Gleixner
2008-09-11  4:52 ` Greg KH [this message]
2008-09-11 13:23   ` Arjan van de Ven
2008-09-11 13:56   ` Arjan van de Ven
2008-09-11 20:52     ` Greg KH
2008-09-11 20:54       ` Arjan van de Ven
2008-09-11 21:53         ` Greg KH

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=20080911045255.GD6863@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox