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>
Subject: Re: b43 crashes on rmmod (bcm4331)
Date: Sat, 9 Jun 2018 22:01:30 +0200 [thread overview]
Message-ID: <20180609220130.3ceb834f@wiggum> (raw)
In-Reply-To: <6a78c68e-1062-5ad8-876c-f7d4c49ea492@lukas-wirz.de>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
On Sat, 9 Jun 2018 22:46:58 +0300
Wirz <spam@lukas-wirz.de> wrote:
> > Is is possible for you to create a git bisect to find the change that
> > actually broke this?
> > That would be really helpful.
>
> I can try that. What is the most efficient way to unload/recompile/load
> a single module without rebooting the machine too often? And it'll be a
> lot of hard resets ...
A git bisect is really only possible in the full kernel tree.
But it won't take a lot of steps to get a result, because you already
narrowed it down to 4.14-4.15. It might take 10 iterations or so (git
will tell you). Due to incremental builds that can be done pretty
quickly. As the whole kernel is searched for a change, a reboot is
usually needed after each iteration step.
There are a couple of howtos on the web regarding git bisect:
https://duckduckgo.com/?q=git+bisect+kernel
--
Michael
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-09 20:02 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
2018-06-09 19:46 ` Wirz
2018-06-09 20:01 ` Michael Büsch [this message]
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=20180609220130.3ceb834f@wiggum \
--to=m@bues.ch \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=spam@lukas-wirz.de \
/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).