From: Kalle Valo <kvalo@codeaurora.org>
To: James Hogan <jhogan@kernel.org>
Cc: Adric Blake <promarbler14@gmail.com>,
m@bues.ch, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: B43 driver no longer works in Linux 4.15 (bisected)
Date: Mon, 12 Feb 2018 17:08:10 +0200 [thread overview]
Message-ID: <87sha68cv9.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20180205183324.GD8479@saruman> (James Hogan's message of "Mon, 5 Feb 2018 18:33:25 +0000")
James Hogan <jhogan@kernel.org> writes:
> Hi Adric,
>
> On Mon, Feb 05, 2018 at 01:23:31PM -0500, Adric Blake wrote:
>> In the time between Linux 4.15-rc8 and -rc9, my wireless driver, b43,
>> would no longer load automatically. When I modprobe the b43 (and ssb)
>> modules, the device still didn't appear in NetworkManager. Comparing
>> the kernel logs between working (4.14.16-lts) and nonworking (4.15)
>> kernels reveals that there is zero output from the ssb module, and no
>> devices recognized by the b43 driver:
>
> ...
>
>> I had my suspicions at this point, but I had a lull and decided to
>> bisect it anyways.
>> I bisected to this "first bad commit:"
>>
>> commit 58eae1416b804d900014d84feadda7195007cc30
>> Author: James Hogan <jhogan@kernel.org>
>> Date: Mon Jan 15 21:17:14 2018 +0000
>>
>> ssb: Disable PCI host for PCI_DRIVERS_GENERIC
>
> Yes, really sorry about that and thanks for going to the effort of
> bisecting. There is a patch here:
> https://patchwork.kernel.org/patch/10185397/
>
> which is applied to linux-next as commit
> a9e6d44ddeccd3522670e641f1ed9b068e746ff7, and is tagged for stable,
> though I've just noticed the stable email address is incorrect... I'll
> make sure it gets applied to the 4.15 stable branch though as soon as
> I notice its merged.
The commit is now in v4.16-rc1.
--
Kalle Valo
next prev parent reply other threads:[~2018-02-12 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 18:23 B43 driver no longer works in Linux 4.15 (bisected) Adric Blake
2018-02-05 18:33 ` James Hogan
2018-02-12 15:08 ` Kalle Valo [this message]
2018-02-12 15:22 ` James Hogan
2018-02-13 15:41 ` Greg Kroah-Hartman
[not found] <CAE1jjefXcbuz5nWxo-BOPBRC7EM6KrXd=G7u-4b74tB5DuYGCQ@mail.gmail.com>
2018-02-05 18:22 ` Michael Büsch
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=87sha68cv9.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m@bues.ch \
--cc=promarbler14@gmail.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;
as well as URLs for NNTP newsgroup(s).