public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom•com>
To: "Helmut Jarausch" <jarausch@igpm•rwth-aachen.de>,
	"netdev@vger•kernel.org" <netdev@vger•kernel.org>
Subject: Re: brcmsmac crashed 3.3-rc5 kernel
Date: Wed, 7 Mar 2012 18:57:02 +0100	[thread overview]
Message-ID: <4F57A16E.8010701@broadcom.com> (raw)
In-Reply-To: <1331136086.2168.0@numa-i>

On 03/07/2012 05:01 PM, Helmut Jarausch wrote:
> Hi Arend,
> thanks for your interest.
>
> Unfortunately, I have no experience in kernel debugging.
> If I switch on several flags in the 'kernel hacking' section, I get
> losts of information on screen - but I don't know how capture these on
> disk.

Sometimes your last resort is using a digital camera to capture what is 
showing on your screen. Can you do that and sent me the picture?

> Meanwhile I have found out that the brcmsmac driver does work under
> special circumstances.
>
> My notebook (HP 625) has to NICs - ethernet and Wlan (BCM4313).
> If I disconnect my PC from the internet, or configure it not to start
> the ethernet connection, then I can start the WLAN successfully - and
> it even seems to be stable.

What happens when you start ethernet after WLAN?

> On the other hand, if I start the ethernet (RTL8101E/RTL8102E) first
> and try to start the WLAN next, the kernel crashes each time as
> reported.

Maybe an issue with shared interrupts. Can you provide the lspci output 
(ie. lspci -v) to me.

> I can live with this situation but if you like me to find out what's
> going on I'm willing to help. But for that I need your help on kernel
> debugging first (currently 3.3-rc6)

Safe the good stuff for later ;-)

Gr. AvS

           reply	other threads:[~2012-03-07 17:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1331136086.2168.0@numa-i>]

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=4F57A16E.8010701@broadcom.com \
    --to=arend@broadcom$(echo .)com \
    --cc=jarausch@igpm$(echo .)rwth-aachen.de \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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