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

[Brett A C Sheffield <bacs@librecast.net>]

On 2025-12-11 21:09, Jeffrin Thalakkottoor wrote:
> On Thu, Dec 11, 2025 at 12:35 AM Brett A C Sheffield <bacs@librecast.net> wrote:
> >
> > On 2025-12-10 19:13, Jeffrin Thalakkottoor wrote:
> > > On Wed, Dec 10, 2025 at 6:17 PM Greg Kroah-Hartman
> > > <gregkh@linuxfoundation.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
> Thnaks for the tutorial  :)
> 1. should i start with the bad commit first ?

You start by marking one good (past) commit and one bad commit. It doesn't
matter what order.

You have at least one "bad" commit you know of: 4112049d7836ad4233321c3d2b6853db1627c49c

This is the 6.12.62-rc1 commit that you reported had the error.

So, in your kernel worktree:

`git bisect start`
`git bisect bad 4112049d7836ad4233321c3d2b6853db1627c49c`

Now we need to tell git bisect the most recent "good" commit we know of (where
the error didn't occur).

If you already know the commit or tag of a previous version where you did not get the
error, mark that as good. If not, pick a previous release, check it out, and go
to step 5.

> 2. how to move forward or backward in commits ?

git bisect will do that for you as soon as you mark a good and bad commit. If
you want to manually test a specific commit, just `git checkout <ref>` as usual, and
continue at step 5 in the instructions I gave you.

> 3. what is the point in re-compiling the kernel  if it cannot narrow
> down and  test news lines of code

We're narrowing down the error to a specific kernel commit. Once we know which
specific commit introduced the error, we can look at the lines changed and try
to understand why.  We need your help to find that commit, because it's
happening on your system.

Please do read `git help bisect` (man 1 git-bisect). It explains all this better
than I can.

Thanks for testing and good luck!


Brett