From: Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: Arend van Spriel <arend@broadcom.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] Problem with commit cf03c5dac83609f09d9f0e9fa3c09d86daed614d
Date: Thu, 26 Jul 2012 19:53:57 +0200 [thread overview]
Message-ID: <gizk6mjtmy.fsf@mx10.gouders.net> (raw)
In-Reply-To: <20120726152121.GB10452@thinkpad-t410> (Seth Forshee's message of "Thu, 26 Jul 2012 10:21:21 -0500")
Seth Forshee <seth.forshee@canonical.com> writes:
> On Thu, Jul 26, 2012 at 05:07:57PM +0200, Dirk Gouders wrote:
>> Hi Seth,
>>
>> thanks for your reply and sorry for the noise.
>>
>> I followed your advice and tried to boot with the WLAN interface turned
>> off, and the problem still exists. I'll start a new bisect session,
>> probably with one of the commits you mentioned as the first good commit.
>
> Just to make sure three's not any confusion ...
>
> What I was suggesting was not just disabling the network interface but
> completely preventing brcmsmac from being loaded. The oops you saw
> happens in the context of the driver's probe function and would happen
> regardless of whether or not the interface is enabled.
Sorry for the confusion.
I already started a new bisect session, with a bad commit I disabled
brcmsmac in the kernel config and the problem still exists. Now, I
continue with brcmsmac disabled and will see where the bisect ends.
Dirk
next prev parent reply other threads:[~2012-07-26 17:54 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
2012-07-26 15:07 ` Dirk Gouders
2012-07-26 15:21 ` Seth Forshee
2012-07-26 17:53 ` Dirk Gouders [this message]
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=gizk6mjtmy.fsf@mx10.gouders.net \
--to=gouders@et.bocholt.fh-gelsenkirchen.de \
--cc=arend@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seth.forshee@canonical.com \
/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
all inboxes | Powered by JetHome®