Linux wireless drivers development
 help / color / mirror / Atom feed
From: Krzysztof Mazur <krzysiek@podlesie.net>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: peizhao.research@gmail.com, linux-wireless@vger.kernel.org,
	nbd@openwrt.org
Subject: Re: kernel panic on 3.10.0-rc7
Date: Mon, 15 Jul 2013 10:52:39 +0200	[thread overview]
Message-ID: <20130715085239.GA31630@shrek.podlesie.net> (raw)
In-Reply-To: <CA+icZUUQHySKu=qEW3xfheg3DSMuvgB7Dp5PzVGOaiziAPTa5g@mail.gmail.com>

On Mon, Jul 01, 2013 at 09:37:19AM +0200, Sedat Dilek wrote:
> On Mon, Jul 1, 2013 at 8:55 AM, Peizhao Hu <peizhao.research@gmail.com> wrote:
> > Hi,
> >
> > Is there anyone has the same problem with me? I have a cm9 radio card with
> > the node.
> >
> > The kernel compiled and booted alright, but crashed short after I set it up
> > in the ad hoc mode. From the debug message output, it looks like something
> > wrong with the rate control mechanism when it is trying to the rate
> > (minstreal_get_rate function in this case).
> >
> > Is this a bug?
> >
> > Kernel version
> > 3.10.0-rc7
> >
> 
> Please, always add your kernel-config and some outputs like dmesg and
> lspci/lsusb for better understanding.
> 2nd, try v3.10 (released a few hours ago)... There were wireless
> patches pushed after v3.10-rc7.
> Then report again.
> 

I have the same problem. I'm using:

02:04.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
	Subsystem: Hewlett-Packard Company Broadcom 802.11b/g WLAN
	Flags: bus master, fast devsel, latency 64, IRQ 21
	Memory at d0000000 (32-bit, non-prefetchable) [size=8K]
	Kernel driver in use: b43-pci-bridge

with b43 driver and I can easily trigger similar Oops with:
# ip link set wlan0 up
# iwlist scan

The bug is introduced by commit 06d961a8e210035bff7e82f466107f9ab4a8fd94
("mac80211/minstrel: use the new rate control API").
The v3.9 is ok and the v3.11-rc1 is still bad. I haven't checked
wireless tree yet.

Wireless related part of my .config:
[...]
CONFIG_WIRELESS=y
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_CFG80211=y
CONFIG_CFG80211_DEFAULT_PS=y
CONFIG_CFG80211_WEXT=y
CONFIG_MAC80211=y
CONFIG_MAC80211_HAS_RC=y
CONFIG_MAC80211_RC_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel"
CONFIG_RFKILL=y
CONFIG_RFKILL_INPUT=y
[...]
CONFIG_WLAN=y
CONFIG_B43=y
CONFIG_B43_SSB=y
CONFIG_B43_PCI_AUTOSELECT=y
CONFIG_B43_PCICORE_AUTOSELECT=y
CONFIG_B43_PIO=y
CONFIG_B43_PHY_LP=y

Krzysiek

  reply	other threads:[~2013-07-15  8:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01  6:55 kernel panic on 3.10.0-rc7 Peizhao Hu
2013-07-01  7:37 ` Sedat Dilek
2013-07-15  8:52   ` Krzysztof Mazur [this message]
2013-07-15  9:06     ` Felix Fietkau
2013-07-15  9:27       ` Krzysztof Mazur
2013-07-15  9:35         ` Krzysztof Mazur
2013-07-15  9:48           ` Felix Fietkau
2013-07-15 11:25             ` Krzysztof Mazur

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=20130715085239.GA31630@shrek.podlesie.net \
    --to=krzysiek@podlesie.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.org \
    --cc=peizhao.research@gmail.com \
    --cc=sedat.dilek@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