From: "Michael Büsch" <m@bues.ch>
To: Wirz <spam@lukas-wirz.de>
Cc: b43-dev@lists.infradead.org,
linux-wireless <linux-wireless@vger.kernel.org>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Larry Finger" <Larry.Finger@lwfinger.net>
Subject: Re: b43 crashes on rmmod (bcm4331)
Date: Sat, 9 Jun 2018 17:11:59 +0200 [thread overview]
Message-ID: <20180609171159.59b5209c@wiggum> (raw)
In-Reply-To: <d9896c10-87bb-8362-f302-8b1888c3421c@lukas-wirz.de>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
On Sat, 9 Jun 2018 15:08:24 +0300
Wirz <spam@lukas-wirz.de> wrote:
> The regression I reported a few weeks ago for 4.15, exists also in 4.16.
> That is, with a bcm4331/ht-phy b43 can be loaded and used without
> problems, but the driver crashes when it gets unloaded (making a hard
> reset of the machine necessary). This problem has been introduced
> between 4.14 and 4.15.
Thanks for your report.
I just checked the diff between 4.14 and 4.15 for b43 and bcma. It's
pretty small and there's no obvious candidate to me that could cause
such a regression.
This might be a change outside of b43 and bcma that triggered this
behavior.
Is is possible for you to create a git bisect to find the change that
actually broke this?
That would be really helpful.
--
Michael
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-09 15:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 19:55 b43 crashes on rmmod (bcm4331) Wirz
2018-06-09 12:08 ` Wirz
2018-06-09 15:11 ` Michael Büsch [this message]
2018-06-09 19:46 ` Wirz
2018-06-09 20:01 ` Michael Büsch
2018-06-11 20:09 ` Wirz
2018-06-11 20:46 ` Michael Büsch
2018-06-13 9:25 ` Wirz
2018-06-13 10:27 ` Michael Büsch
2018-06-13 11:01 ` Wirz
2018-06-13 11:09 ` Michael Büsch
2018-06-13 12:01 ` Michael Büsch
2018-06-13 13:07 ` Wirz
2018-06-13 13:28 ` Michael Büsch
2018-06-14 9:47 ` Wirz
2018-06-14 16:26 ` Michael Büsch
2018-06-14 19:18 ` Wirz
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=20180609171159.59b5209c@wiggum \
--to=m@bues.ch \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=spam@lukas-wirz.de \
--cc=zajec5@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).