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

[Jeffrin Thalakkottoor]

On Thu, Dec 11, 2025 at 12:35 AM Brett A C Sheffield <bacs@xxxxxxxxxxxxx> wrote:
>
> On 2025-12-10 19:13, Jeffrin Thalakkottoor wrote:
> > On Wed, Dec 10, 2025 at 6:17 PM Greg Kroah-Hartman
> > <gregkh@xxxxxxxxxxxxxxxxxxx> 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 ?
2. how to move forward or backward in commits ?
3. what is the point in re-compiling the kernel  if it cannot narrow
down and  test news lines of code







-- 
software engineer
rajagiri school of engineering and technology