From: Bob Copeland <me@bobcopeland.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, tglx@tglx.de,
alan@lxorguk.ukuu.org.uk, rjw@sisk.pl, netdev@vger.kernel.org,
mingo@elte.hu, dwmw2@infradead.org, alsa-devel@alsa-project.org,
dri-devel@lists.sourceforge.net
Subject: Re: kerneloops.org report for the week of June 14 2009
Date: Thu, 18 Jun 2009 13:08:39 -0400 [thread overview]
Message-ID: <b6c5339f0906181008v1cd4b06aof866ea9a91d2eb84@mail.gmail.com> (raw)
In-Reply-To: <20090614173331.18f01123@infradead.org>
On Sun, Jun 14, 2009 at 8:33 PM, Arjan van de Ven<arjan@infradead.org> wrote:
> Rank 9: minstrel_get_rate (warning)
> Reported 64 times (384 total reports)
> Issue with the ath5k driver
> This warning was last seen in version 2.6.30-rc3, and first seen in 2.6.27.12.
> More info: http://www.kerneloops.org/searchweek.php?search=minstrel_get_rate
I believe this is fixed by http://lkml.org/lkml/2009/6/5/269, now
in pre-2.6.31. Hmm, odd though, we should be seeing reports from
other wireless drivers since it's a general memory corruption
unrelated to ath5k (but not all use the mac80211 rate controllers).
(2.6.27.12 must be a backport, minstrel didn't exist until .29)
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2009-06-18 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 0:33 kerneloops.org report for the week of June 14 2009 Arjan van de Ven
2009-06-15 5:53 ` Takashi Iwai
2009-06-15 7:06 ` Stefan Schmidt
2009-06-16 7:11 ` WARN_ON's in i915_gem_tiling.c Stefan Schmidt
2009-06-18 17:08 ` Bob Copeland [this message]
2009-06-19 5:32 ` kerneloops.org report for the week of June 14 2009 Arjan van de Ven
2009-06-28 9:11 ` Bob Copeland
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=b6c5339f0906181008v1cd4b06aof866ea9a91d2eb84@mail.gmail.com \
--to=me@bobcopeland.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=arjan@infradead.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tglx@tglx.de \
--cc=torvalds@linux-foundation.org \
/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).