From: Marcel Holtmann <holtmann@linux.intel.com>
To: Zhu Yi <yi.zhu@intel.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Crash with 2.6.27-rc6 with iwlwifi
Date: Fri, 12 Sep 2008 03:47:40 +0200 [thread overview]
Message-ID: <1221184060.11498.3.camel@californication> (raw)
In-Reply-To: <1221123779.2513.88.camel@debian.sh.intel.com>
Hi Yi,
> It should be triggered by the BUG_ON() in the function. Are you able to
> confirm it with netconsole or maybe even a frame buffer enabled console
> (it just shows more lines)? If this is the culprit, Tomas has been
> already working on it. But your BT coexist finding should help us
> reproducing the bug.
> http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1703
so I was looking through the bug and switched some options around based
on wild assumptions made in that bug. The current settings are this:
CONFIG_IWLWIFI=m
CONFIG_IWLCORE=m
# CONFIG_IWLWIFI_LEDS is not set
CONFIG_IWLWIFI_RFKILL=y
# CONFIG_IWLWIFI_DEBUG is not set
CONFIG_IWLAGN=m
# CONFIG_IWLAGN_SPECTRUM_MEASUREMENT is not set
# CONFIG_IWLAGN_LEDS is not set
CONFIG_IWL4965=y
# CONFIG_IWL5000 is not set
# CONFIG_IWL3945 is not set
these seem to be stable and have no problems. I tried to crash the
kernel, but didn't manage it.
Previously I had IWLWIFI_RFKILL off (wich was an oversight) and
IWLAGN_LEDS on.
So my guess is either disabling RFKILL or enabling LEDS makes the
difference. This is another reason to not have all these config options,
because nobody find any bugs :(
Regards
Marcel
next prev parent reply other threads:[~2008-09-11 23:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 8:04 Crash with 2.6.27-rc6 with iwlwifi Marcel Holtmann
2008-09-11 9:02 ` Zhu Yi
2008-09-11 15:06 ` Marcel Holtmann
2008-09-12 1:47 ` Marcel Holtmann [this message]
2008-09-12 2:10 ` Marcel Holtmann
2008-09-12 7:49 ` Johannes Berg
2008-10-06 12:30 ` Johannes Berg
2008-10-06 12:32 ` Johannes Berg
2008-10-06 12:36 ` Johannes Berg
2008-10-06 13:07 ` Johannes Berg
2008-10-06 13:21 ` Johannes Berg
2008-10-06 12:36 ` Marcel Holtmann
2008-10-06 12:39 ` Johannes Berg
2008-10-06 13:01 ` Marcel Holtmann
2008-10-06 13:04 ` Johannes Berg
2008-10-06 16:52 ` Luis R. Rodriguez
2008-10-06 16:55 ` Johannes Berg
2008-09-11 10:36 ` Johannes Berg
2008-09-11 15:03 ` Marcel Holtmann
2008-09-11 15:46 ` Johannes Berg
2008-09-24 20:14 ` Johannes Berg
2008-09-24 23:00 ` Ian Schram
2008-09-25 4:28 ` Johannes Berg
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=1221184060.11498.3.camel@californication \
--to=holtmann@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=yi.zhu@intel.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