[OpenWrt-Devel] FS#1567 reported: making openrwrt unusable (BT Home Hub 5) since between r6080 and r7050
jaapbuurman at gmail.com
Mon May 28 09:32:08 EDT 2018
On Mon, May 28, 2018 at 3:27 PM, Mauro Mozzarelli <mauro at ezplanet.org> wrote:
> I will be happy to help. How do I do it?
> I mean, I have a backup of the master folder for r6080, since I keep a full
> copy of every successful build that I then run on my routers. How do I pull
> just one release at a time, like r6081, r6082, etc.? That is the best I
> could do, build the releases one by one until I find the one that fails.
> On 28/05/18 14:17, Jaap Buurman wrote:
>> On Mon, May 28, 2018 at 3:12 PM, Mauro Mozzarelli <mauro at ezplanet.org>
>>> This does not make sense, is the alternative to write off openwrt?
>>> if ADSL + PPPoA do not work, then it is useless.
>>> As a minimum I would expect a developer to look at the commits between
>>> and r7050 to see what has changed and roll-back.
>>> Also if you need any further information, just ask and provide guidance
>>> how to get it.
>>> If you would like the hardware I can arrange for it to be shipped to you.
>>> On 28/05/18 14:02, Jo-Philipp Wich wrote:
>>>>> Is anyone looking into it?
>>>> I doubt it, unfortunately the info in the ticket is too vague to work
>>>> with. Personally I don't have any hardware to debug this.
>>>> ~ Jo
>>>> openwrt-devel mailing list
>>>> openwrt-devel at lists.openwrt.org
>>> openwrt-devel mailing list
>>> openwrt-devel at lists.openwrt.org
>> Dear Mauro,
>> Going through nearly 1000 commits without knowing what to look for is
>> very difficult and not very time efficient. The easiest way for you to
>> help track down this issue would be to do a Git bisect from r6080 to
>> r7050 until you find the specific commit that breaks PPPoA. It would
>> be much easier to debug/fix if a developer knows which particular
>> commit breaks stuff :)
>> Yours sincerely,
>> Jaap Buurman
I don't know the commands by heart, so you will have to look up the
specific commands. But basically:
1) use git to clone the repository
2) mark the last known good commit
3) mark the first known bad commit
4) git will then pick one commit in the middle, so in this case
r6500ish. You compile that image:
5) you test the image and mark it as good/bad. Git will then pick a
new commit r6250ish or 6750ish depending on whether the previous one
Since you halve the search space each attempt, it shouldn't take that
many attempts to track down the specific commit that broke it within
Good luck :)
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
More information about the openwrt-devel