All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Honse <calcprogrammer1@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: brcmsmac causes soft lockup in 3.12-rc1
Date: Sun, 22 Sep 2013 05:33:29 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130922T072315-740@post.gmane.org> (raw)
In-Reply-To: 20130921223440.GA5297@mail.catnarok.net

I'm having the same issues on my laptop.  Under Debian, Ubuntu, and Arch I
had the same problem in every kernel release I tried brcmsmac on in that the
range is very poor.  My router in the basement was intermittent upstairs in
the room directly above the router, and got barely enough signal to work
reliably sitting next to it.  I just switched the machine back to Ubuntu
(GNOME Remix) today to test the Radeon drivers but upon installing 3.12 I'm
getting the same soft-lockup bug, crashes the whole PC before I can log in
and even see what's going on.  The closed source Broadcom STA driver works
fine on supported kernels.

Laptop is an HP dv6z-7000 with:

AMD A10-4600 APU / Radeon 7660G
Radeon 7730M
Broadcom BCM4313

Ubuntu GNOME Remix 13.10 daily, up to date
Linux 3.11.0 from main repos (working, poor signal)
Linux 3.12-rc1 from Ubuntu kernel PPA (crashes, CPU #1 lockup)

The machine has Bluetooth as well and I don't know if that's part of the
BCM4313 or not.  hciconfig says that hci0 is on Bus: USB while the 4313 is
on PCI according to lspci, but if it uses both buses on the same mini-PCIe
card I don't know.

I can provide other files if necessary.

Thanks,
Adam


  reply	other threads:[~2013-09-22  5:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-21 22:34 brcmsmac causes soft lockup in 3.12-rc1 Michael Stolovitzsky
2013-09-22  5:33 ` Adam Honse [this message]
2013-09-22 12:32   ` Michael Stolovitzsky
2013-09-22 17:26     ` Adam Honse
2013-09-23  8:13 ` Arend van Spriel
2013-09-24  0:52   ` Michael Stolovitzsky
2013-09-24  7:53     ` Arend van Spriel
2013-09-25 18:00       ` Michael Stolovitzsky
2013-09-30 23:32         ` Adam Honse

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=loom.20130922T072315-740@post.gmane.org \
    --to=calcprogrammer1@gmail.com \
    --cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.