(In reply to comment #9)
> (In reply to comment #8)
> > Jordi, we will figure out the details about how to add the patch in the
> > dowstream report (to keep noise down here).
> > Ling, can we try the patch against 2.7.1, or do we have to get git-master to
> > test?
>
> yes, you can try the patch against 2.7.1.
>
> I also can not find any differnece between 2.2.1 and 2.4.1.
> Because we have no hardware, would you please like to do git bisec to find
> which patch caused the regression between two versions
>
> Michael mentioned 7b6f4d22211d71480caf6335a3eacaacff369371 ?
>
> Thanks for your help.
> Ma Ling
>
yes, Ubuntu didn't just take our original 2.4.1 release, but cheery picked more in post-2.4.1 master, such as the commit 7b6f.. I think. check out the link I posted in comment# 6...
(In reply to comment #9) 80caf6335a3eaca acff369371 ?
> (In reply to comment #8)
> > Jordi, we will figure out the details about how to add the patch in the
> > dowstream report (to keep noise down here).
> > Ling, can we try the patch against 2.7.1, or do we have to get git-master to
> > test?
>
> yes, you can try the patch against 2.7.1.
>
> I also can not find any differnece between 2.2.1 and 2.4.1.
> Because we have no hardware, would you please like to do git bisec to find
> which patch caused the regression between two versions
>
> Michael mentioned 7b6f4d22211d714
>
> Thanks for your help.
> Ma Ling
>
yes, Ubuntu didn't just take our original 2.4.1 release, but cheery picked more in post-2.4.1 master, such as the commit 7b6f.. I think. check out the link I posted in comment# 6...