From: Arjan van de Ven <arjan@linux.intel.com>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: linville@tuxdriver.com, linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Oops/Warning report of the week of July 4th 2008
Date: Fri, 04 Jul 2008 15:56:54 -0700 [thread overview]
Message-ID: <486EAAB6.2070000@linux.intel.com> (raw)
In-Reply-To: <200807050038.49712.IvDoorn@gmail.com>
Ivo van Doorn wrote:
> Hi,
>
>> Rank 12: flush_workqueue (oops)
>> Reported 39 times
>> Bug in the rt25xx driver passing NULL to the flush_workqueue() function
>> This oops was last seen in version 2.6.25.9, and first seen in 2.6.25.9.
>> More info: http://www.kerneloops.org/searchweek.php?search=flush_workqueue
>
> Hmm, interesting I hadn't received such reports yet..
it only very recently showed up on kerneloops.org (the .9 release from Fedora is only a 2 or 3 days old).
In addition, while I monitor what's going on, oops patterns need to cross roughly a 25/week pattern for
me to notice them as standing out...
If I see other patterns come up I'll send out email again ;-)
prev parent reply other threads:[~2008-07-04 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <486EA0D6.2040504@linux.intel.com>
2008-07-04 22:38 ` Oops/Warning report of the week of July 4th 2008 Ivo van Doorn
2008-07-04 22:56 ` Arjan van de Ven [this message]
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=486EAAB6.2070000@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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;
as well as URLs for NNTP newsgroup(s).