Re: April 2025 stabilization week

From: Vladimir Kondratyev <wulf_at_FreeBSD.org>
Date: Sun, 27 Apr 2025 19:50:56 UTC
On 4/27/25 19:57, Gleb Smirnoff wrote:
> On Sun, Apr 27, 2025 at 03:38:46PM +0000, Dave Cottlehuber wrote:
> D> On Sat, 26 Apr 2025, at 16:19, Vladimir Kondratyev wrote:
> D> > On 4/24/25 21:46, Gleb Smirnoff wrote:
> D> >> On Thu, Apr 24, 2025 at 05:48:46PM +0000, Dave Cottlehuber wrote:
> D> >> D> On Thu, 24 Apr 2025, at 17:31, Gleb Smirnoff wrote:
> D> >> D> > D> This issue actually came up last month but I had no time to
> D> >> D> > investigate
> D> >> D> > D> then, details
> D> >> D> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286045
> D> >> D> >
> D> >> D> > Is this regression since last stabweek or from an earlier point?
> D> >> D>
> D> >> D> Just since March stabweek.
> D> >>
> D> >> There were no changes to the driver :(
> D> >>
> D> >> Any chance you can make a bisect?
> D> >>
> D> >
> D> > I think it is regression from daa098cc37b9
> 
> Great that the problem has been solved, but there is still an inconsistency.
> Dave says this was a regression since March stabweek.  But the daa098cc37b9 was
> already there.
> 

I see 3 possible reasons:

1. Pre-daa098cc37b9 system running during March stabweek.
2. Different touchpad hardware.
3. Something else. E.g. a luck.

-- 
WBR
Vladimir Kondratyev