From: Seth Forshee <seth.forshee@canonical.com>
To: Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Arend van Spriel <arend@broadcom.com>
Subject: Re: [BUG] Problem with commit cf03c5dac83609f09d9f0e9fa3c09d86daed614d
Date: Thu, 26 Jul 2012 08:49:26 -0500 [thread overview]
Message-ID: <20120726134926.GA10452@thinkpad-t410> (raw)
In-Reply-To: <gik3xqtzw3.fsf@karga.hank.lab>
On Thu, Jul 26, 2012 at 03:28:44PM +0200, Dirk Gouders wrote:
> Hi Seth,
>
> today, I noticed a problem with the current kernel
> (3.5.0-04773-gbdc0077): my laptop hangs during boot -- the last message
> on the console is printed just before invoking `udevadm trigger'.
>
> I bisected the problem and ended at commit
> cf03c5dac83609f09d9f0e9fa3c09d86daed614d (brcm80211: smac: inform
> mac80211 of the X2 regulatory domain). However, I'm not sure that this
> commit really is the reason for my problems, because the behaviour is a
> bit different: at that state the machine not just hangs but the console
> shows a trace which I append to the end of this mail -- but the trace
> happens at the same state during the boot process.
Hi Dirk,
The NULL pointer dereference in wlc_phy_chanspec_band_validch is already
fixed in edc7651f3a4ffa7fca37d92401562694121512ad. There was also
another related crash that appeared after the introduction of 802.11ad
support that's fixed in 32c336a5dfd16b4645c8a0dbc534efd02f079e02.
So in all likelihood whatever problem your seeing in current -git is a
different issue. One easy way to test this would be to prevent the
brcmsmac module from loading and verify that you still get the hang,
then rerun the bisection that way to keep those bugs from affecting your
results.
Cheers,
Seth
next prev parent reply other threads:[~2012-07-26 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 13:28 Dirk Gouders
2012-07-26 13:49 ` Seth Forshee [this message]
2012-07-26 15:07 ` Dirk Gouders
2012-07-26 15:21 ` Seth Forshee
2012-07-26 17:53 ` Dirk Gouders
2012-07-27 6:24 ` Dirk Gouders
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=20120726134926.GA10452@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=arend@broadcom.com \
--cc=gouders@et.bocholt.fh-gelsenkirchen.de \
--cc=linux-kernel@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
Powered by JetHome