From: Arjan van de Ven <arjan@linux.intel.com>
To: Greg KH <gregkh@suse.de>
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: Thu, 11 Sep 2008 06:56:25 -0700 [thread overview]
Message-ID: <48C92389.7070209@linux.intel.com> (raw)
In-Reply-To: <20080911045255.GD6863@suse.de>
Greg KH wrote:
> 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
>
>
> 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.)
ok I think I got this one sorted;
your entry is now replaced by
Rank 4: snd_card_register (warning)
Reported 146 times (2594 total reports)
This warning was last seen in version 2.6.25.14, and first seen in 2.6.24.
More info: http://www.kerneloops.org/searchweek.php?search=snd_card_register
which is ALL usb audio... (so I might have to also skip snd_card_register in the backtrace, but I'll leave that between you and the alsa guys)
next prev parent reply other threads:[~2008-09-11 13:56 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
2008-09-11 13:23 ` Arjan van de Ven
2008-09-11 13:56 ` Arjan van de Ven [this message]
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=48C92389.7070209@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--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