Displaying 3 results from an estimated 3 matches for "86a04561920b".
2019 Dec 19
3
Tracking down severe regression in 5.3-rc4/5.4 for TU116 - assistance needed
...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). The build from the previous commit
86a04561920b works fine.
> narrowed the range). Also I'd recommend ensuring that the good kernel
> is really good and the bad kernel is really bad -- boot them a few
> times.
Well, this problem is reproducible in 100% in newer kernels. I see the
errors on boot logs and after login to Gnome Shell...
2019 Dec 19
0
Tracking down severe regression in 5.3-rc4/5.4 for TU116 - assistance needed
...t fails
Took me a while, but this is the end of the hash. Normally you list
the start of the hash (and that's what all the git tools accept). In
this case this is commit
0acf5676dc0ffe0683543a20d5ecbd112af5b8ee
> miserably (as previously described). The build from the previous commit
> 86a04561920b works fine.
e577dc152e232c78e5774e4c9b5486a04561920b
>
> > narrowed the range). Also I'd recommend ensuring that the good kernel
> > is really good and the bad kernel is really bad -- boot them a few
> > times.
>
> Well, this problem is reproducible in 100% in newer...
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