On Sun, Jun 18, 2023 at 08:15:43AM +0900, Mike Hommey wrote:
> On Sun, Jun 18, 2023 at 06:09:57AM +0900, Mike Hommey wrote:
> > On Sat, Jun 17, 2023 at 01:20:30AM +0200, Diederik de Haas wrote:
> > > Control: tag -1 -moreinfo
> > > Control: found -1 6.1.20-1
> > > 
> > > On Saturday, 17 June 2023 01:00:58 CEST Mike Hommey wrote:
> > > > > 6.1.12-1 and 6.1.15-1 are good. 6.1.20-1 is the first broken one.
> > > 
> > > Excellent, thanks. This is already very useful.
> > > 
> > > > > > A `git bisect` would be best, but grabbing these intermediate 
> > > > > > versions
> > > > > > (from snapshot.debian.org) is the quickest way to narrow the range.
> > > > > 
> > > > > Last time I tried to build Debian linux kernels, it was spending a 
> > > > > large
> > > > > amount of time building packages I don't need, and finding the right
> > > > > incantation to reduce that load was not straightforward, and I can't
> > > > > find my notes, unfortunately. If you have instructions I can use to go
> > > > > through a bisect in a quick manner, I'm all ears.
> > > > 
> > > > Although, if you have instructions to just build the one module and 
> > > > avoid
> > > > rebooting, that would be even better.
> > > 
> > > I _think_ building just one module or without rebooting is not possible.
> > > 
> > > The 'official' instructions: 
> > > https://wiki.debian.org/DebianKernel/GitBisect
> > > 
> > > I know some things to reduce what gets build, like f.e. what's described 
> > > here:
> > > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.7
> > > And there's also a facility to work with _build profiles_.
> > > But I don't know if or how that could be applied to the 'official' 
> > > instructions
> > > as that deals with the upstream kernel source directly.
> > > 
> > > Hopefully one of the (more) experienced people chimes in with 
> > > actual useful things ...
> > 
> > I was able to build the relevant module only. The regression comes from
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=337c3624bcb008f92bab38c8fc4cdf97ae5313a2
> 
> I sent a patch upstream, but it's not showing up on the archives yet.
> I'll update with a link when I have one.

Here we go:
https://patchwork.kernel.org/project/linux-input/patch/20230617230957.6mx73th4blv7o...@glandium.org/

Mike

Reply via email to