From: "Arend van Spriel" <arend@broadcom.com>
To: "Helmut Jarausch" <jarausch@igpm.rwth-aachen.de>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: brcmsmac crashed 3.3-rc5 kernel
Date: Thu, 1 Mar 2012 13:58:25 +0100 [thread overview]
Message-ID: <4F4F7271.8080900@broadcom.com> (raw)
In-Reply-To: <jinmr4$pej$1@dough.gmane.org>
On 03/01/2012 12:33 PM, Helmut Jarausch wrote:
> Hi,
>
> on an HP625 I have the following device
>
> 06:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/
> n Wireless LAN Controller [14e4:4727] (rev 01)
> Subsystem: Hewlett-Packard Company Device [103c:145c]
> Kernel driver in use: bcma-pci-bridge
>
>
> This device isn't recognized by the brcmfmac driver but only by the
> brcmsfac driver.
That is expected. brcmfmac is support sdio/usb cards. brcmsmac is used
for bcm4313 card.
> My kernel configuration is
>
> # Broadcom specific AMBA
> #
> CONFIG_BCMA=y
> CONFIG_BCMA_HOST_PCI_POSSIBLE=y
> CONFIG_BCMA_HOST_PCI=y
> # CONFIG_BCMA_DEBUG is not set
>
> # CONFIG_B43 is not set
> # CONFIG_B43LEGACY is not set
> CONFIG_BRCMUTIL=m
> CONFIG_BRCMSMAC=m
> # CONFIG_BRCMFMAC is not set
> CONFIG_BRCMDBG=y
>
looks ok.
>
> but doing /etc/init.d/net.wlan0 start
> crashes the kernel - even<Ctrl><Alt><Shift><SysRq> doesn't work anymore.
> I've tried strace, but the output file doesn't get closed so it's missing
> after reboot.
You could try some kernel hacking features. Some can help to get some
vital info on screen.
> Any help is very much appreciated.
>
> P.S. the GRML64 live CD system does work on that hardware but it uses a
> 3.1 kernel and a staging driver.
>
> Since I'd like to use BTRFS I'd like to use a 3.3 kernel.
> Helmut.
Some more details would certainly increase my ability to help you.
Gr. AvS
prev parent reply other threads:[~2012-03-01 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 11:33 brcmsmac crashed 3.3-rc5 kernel Helmut Jarausch
2012-03-01 12:58 ` Arend van Spriel [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=4F4F7271.8080900@broadcom.com \
--to=arend@broadcom.com \
--cc=jarausch@igpm.rwth-aachen.de \
--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 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).