From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: iwl5000 oopses with Linus's tree
Date: Mon, 06 Oct 2008 14:29:02 +0200 [thread overview]
Message-ID: <1223296142.15196.4.camel@johannes.berg> (raw)
In-Reply-To: <1217937364.3603.37.camel@johannes.berg> (sfid-20080805_135654_962503_852A6EC4)
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
On Tue, 2008-08-05 at 13:56 +0200, Johannes Berg wrote:
> Regardless of whether it is enabled or not, this shouldn't happen:
>
> [ 373.387834] iwl4965: uCode did not respond OK.
> [ 373.387959] iwl4965: Error wrong command queue 0 command id 0x1
> [ 373.388032] ------------[ cut here ]------------
> [ 373.388058] kernel BUG at drivers/net/wireless/iwlwifi/iwl-tx.c:1163!
> [ 373.388102] Oops: Exception in kernel mode, sig: 5 [#1]
>
> This is kernel 2.6.27-rc1-00504-g2b12a4c-dirty
I just found another thing that seems critical to this issue (I now am
using kernel 2.6.27-rc6-wl-01382-g0bea1f7-dirty):
It goes away completely when I use 4K-pages instead of 64K-pages.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2008-10-06 12:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 11:56 iwl5000 oopses with Linus's tree Johannes Berg
2008-08-05 12:22 ` iwl5000 oopses (was: iwl5000 oopses with Linus's tree) Johannes Berg
2008-08-05 15:20 ` Tomas Winkler
2008-08-28 10:36 ` Johannes Berg
2008-08-28 11:39 ` Tomas Winkler
2008-08-28 12:17 ` Johannes Berg
2008-08-28 14:52 ` Tomas Winkler
2008-08-28 15:44 ` iwl5000 oopses Ian Schram
2008-08-28 21:30 ` Tomas Winkler
2008-08-28 23:58 ` Ian Schram
2008-08-29 0:15 ` Tomas Winkler
2008-08-29 7:30 ` Johannes Berg
2008-10-06 12:29 ` Johannes Berg [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=1223296142.15196.4.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@gmail.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).