[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1291930010.7960.30.camel@nimitz>
Date: Thu, 09 Dec 2010 13:26:50 -0800
From: Dave Hansen <dave@...1.net>
To: "John W. Linville" <linville@...driver.com>,
Johannes Berg <johannes@...solutions.net>,
Brett Rudley <brudley@...adcom.com>,
Henry Ptasinski <henryp@...adcom.com>,
Nohee Ko <noheek@...adcom.com>,
Greg Kroah-Hartman <gregkh@...e.de>,
Jason Cooper <jason@...edaemon.net>,
Mike Rapoport <mike.rapoport@...il.com>,
Andy Shevchenko <andy.shevchenko@...il.com>,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
devel@...verdev.osuosl.org
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: brcm80211 hangs when disabling wireless
I've been getting hard hangs when I toggle the wireless on a Lenovo
S10-3. It happens both with the physical switch and the Fn-F5 key
combo. It's quite repeatable. The system is quite stable when I'm not
trying to disable the wireless, though.
I've been able to get some screenshots, but the console messages don't
make it out to the disk:
http://picasaweb.google.com/hansendc/BrcmOops#
netconsole also isn't working on this hardware. Any other suggestions
for getting an oops out of a serial-port-challenged netbook?
It isn't completely clear to me where this bug actually is. The stack
dump looks almost completely confined to net/mac80211/ functions, but
there are a few error printk's from brcm80211.
The first printk's are from this code, but it's apparently trying to
transmit in the mac80211 stack anyway:
static int wl_ops_tx(struct ieee80211_hw *hw, struct sk_buff *skb)
{
int status;
wl_info_t *wl = hw->priv;
WL_LOCK(wl);
if (!wl->pub->up) {
WL_ERROR(("ops->tx called while down\n"));
status = -ENETDOWN;
goto done;
}
status = wl_start(skb, wl);
done:
WL_UNLOCK(wl);
return status;
}
I'm not completely sure that this is what is causing the hang that I'm
seeing, but it's certainly the last thing I see on the console.
With the hardware driver in -staging, I don't expect anybody to jump out
of their seats to fix this, I just figured someone might want to see the
bug report.
-- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists