Displaying 3 results from an estimated 3 matches for "bd112af5b8ee".
2019 Dec 19
3
Tracking down severe regression in 5.3-rc4/5.4 for TU116 - assistance needed
On 2019-12-16 19:45, Ilia Mirkin wrote:
> The obvious candidate based on a quick scan is
> 0acf5676dc0ffe0683543a20d5ecbd112af5b8ee -- it merges a fix that
> messes with PCI stuff, and there lie dragons. You could try building
> that commit, and if things still work, then I have no idea (and you've
Nice shot Ilia!
I managed to build kernel from suspected bd112af5b8ee and it fails
miserably (as previously described)....
2019 Dec 19
0
Tracking down severe regression in 5.3-rc4/5.4 for TU116 - assistance needed
...ert 0617bdede5114a0002298b12cd0ca2b0cfd0395d" works
well for you.
On Thu, Dec 19, 2019 at 3:27 PM Marcin Zaj?czkowski <mszpak at wp.pl> wrote:
>
> On 2019-12-16 19:45, Ilia Mirkin wrote:
> > The obvious candidate based on a quick scan is
> > 0acf5676dc0ffe0683543a20d5ecbd112af5b8ee -- it merges a fix that
> > messes with PCI stuff, and there lie dragons. You could try building
> > that commit, and if things still work, then I have no idea (and you've
>
> Nice shot Ilia!
>
> I managed to build kernel from suspected bd112af5b8ee and it fails
Took me...
2019 Dec 16
2
Tracking down severe regression in 5.3-rc4/5.4 for TU116 - assistance needed
On 2019-12-16 18:08, Ilia Mirkin wrote:
> Hi Marcin,
>
> You should do a git bisect rather than guessing about commits. I
> suspect that searching for "kernel git bisect fedora" should prove
> instructive if you're not sure how to do this.
Thanks for your suggestion. I realize that I can do it at the Git level
and it is the ultimate way to go. However, building the