mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
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>,
	Andrew Morton <akpm@linux-foundation.org>,
	NetDev <netdev@vger.kernel.org>
Subject: Re: Top 10 kernel oopses for the week ending January 5th, 2008
Date: Wed, 09 Jan 2008 15:12:30 +0100	[thread overview]
Message-ID: <1199887950.6762.26.camel@johannes.berg> (raw)
In-Reply-To: <477FF149.4070609@linux.intel.com> (sfid-20080105_210825_521052_738F2802)

[-- Attachment #1: Type: text/plain, Size: 670 bytes --]


> Rank 1: __ieee80211_rx
> 	Warning at net/mac80211/rx.c:1672
> 	Reported 6 times (11 total reports)
> 	Same issue that was ranked 2nd last week
> 	Johannes has diagnosed this as a driver bug in the iwlwifi drivers
> 	More info: http://www.kerneloops.org/search.php?search=__ieee80211_rx

Note that because we don't get the module list for WARN_ON, we don't
actually know whether all of these instances are from the iwlwifi
drivers. A few other drivers suffer from the same problem. In one of
these cases, iwlwifi was contained in the stack trace, but in the common
case that isn't happening because packet processing is delayed to a
tasklet.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  parent reply	other threads:[~2008-01-09 14:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-05 21:06 Arjan van de Ven
2008-01-05 21:26 ` Al Viro
2008-01-05 21:39 ` Al Viro
2008-01-07 17:44   ` J. Bruce Fields
2008-01-08  1:19     ` Kevin Winchester
2008-01-08  3:26       ` Linus Torvalds
2008-01-08  5:59         ` Al Viro
2008-01-08  7:33           ` Jarek Poplawski
2008-01-10  4:13           ` Neil Brown
2008-01-10  5:53             ` Al Viro
2008-01-14  1:36               ` Neil Brown
2008-01-08 16:14         ` Randy Dunlap
2008-01-08 17:42           ` Arjan van de Ven
2008-01-08 18:08             ` Linus Torvalds
2008-01-08 18:16               ` Arjan van de Ven
2008-01-08 18:27                 ` Linus Torvalds
2008-01-08 19:05                   ` Arjan van de Ven
2008-01-08 19:31                     ` Linus Torvalds
2008-01-08 22:56                       ` Rafael J. Wysocki
2008-01-08 17:08         ` Andi Kleen
2008-01-06  3:30 ` Andi Kleen
2008-01-06  3:31   ` Arjan van de Ven
2008-01-06  3:50     ` Andi Kleen
2008-01-09 14:12 ` Johannes Berg [this message]
2008-01-09 15:28   ` Arjan van de Ven

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=1199887950.6762.26.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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
all inboxes | Powered by JetHome®