linux-kernel - Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aTnET5C2PGiKsW_2@auntie>
Date: Wed, 10 Dec 2025 19:04:47 +0000
From: Brett A C Sheffield <bacs@...recast.net>
To: Jeffrin Thalakkottoor <jeffrin@...agiritech.edu.in>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, stable@...r.kernel.org,
	patches@...ts.linux.dev, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	linux@...ck-us.net, shuah@...nel.org, patches@...nelci.org,
	lkft-triage@...ts.linaro.org, pavel@...x.de, jonathanh@...dia.com,
	f.fainelli@...il.com, sudipm.mukherjee@...il.com, rwarsow@....de,
	conor@...nel.org, hargar@...rosoft.com, broonie@...nel.org,
	achill@...ill.org, sr@...dewatkins.com
Subject: Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

On 2025-12-10 19:13, Jeffrin Thalakkottoor wrote:
> On Wed, Dec 10, 2025 at 6:17 PM Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> >
> > On Wed, Dec 10, 2025 at 04:22:21PM +0530, Jeffrin Thalakkottoor wrote:
> > >  compiled and booted 6.17.12-rc1+
> > > Version: AMD A4-4000 APU with Radeon(tm) HD Graphics
> > >
> > > sudo dmesg -l errr  shows  error
> > >
> > > j$sudo dmesg -l err
> > > [   39.915487] Error: Driver 'pcspkr' is already registered, aborting...
> > > $
> >
> > Is ths new?  if so, can you bisect?
> 
> this is new related. Previous stable release err and warn disappeared
> (i think i changed  .config)
> 
> can you give me a  step by step tutorial  for git bisect

1) cd to wherever you have your kernel checked out

2) `git bisect start`

3) if you're already on a known-bad commit, then mark it as such:

  `git bisect bad`

4) Mark the last known good commit as such:

  `git bisect good <commit / tag>`

git bisect will choose a commit to test.

5) Build, install and boot your kernel as you usually do

6) Run whatever test you need to determine if the booted kernel is good or bad
(check dmesg in this case)

7) Mark the commit as good or bad. Git will choose another commit for you.

8) Goto 5.

`git help bisect` will give you more information.

At the end of the process git will tell you the first bad commit found.  You can
dump the bisection log with:

`git bisect log`

which you can reply here with.

HTH.

Cheers,


Brett