[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG=yYwmY7_iqUTG9m1yPyaSNFqMTsNCTz-Yx=H6=rU_HeXxygg@mail.gmail.com>
Date: Wed, 17 Dec 2025 23:34:55 +0530
From: Jeffrin Thalakkottoor <jeffrin@...agiritech.edu.in>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: 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 000/506] 6.17.13-rc2 review
On Wed, Dec 17, 2025 at 8:34 PM Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
>
> On Wed, Dec 17, 2025 at 08:24:15PM +0530, Jeffrin Thalakkottoor wrote:
> > On Wed, Dec 17, 2025 at 1:09 PM Jeffrin Thalakkottoor
> > <jeffrin@...agiritech.edu.in> wrote:
> > >
> > > hello
> > >
> > > Compiled and booted 6.17.13-rc2+
> > >
> > > dmesg shows error... file attached
> > >
> > > As per dmidecode command.
> > > Version: AMD Ryzen 3 3250U with Radeon Graphics
> > >
> > > Processor Information
> > > Socket Designation: FP5
> > > Type: Central Processor
> > > Family: Zen
> > > Manufacturer: Advanced Micro Devices, Inc.
> > > ID: 81 0F 81 00 FF FB 8B 17
> > > Signature: Family 23, Model 24, Stepping 1
> > >
> > > Tested-by: Jeffrin Jose T <jeffrin@...agiritech.edu.in>
> >
> > i have done a git bisect and the log is attached.
> > THANKS
> >
> >
> > --
> > software engineer
> > rajagiri school of engineering and technology
>
> > git bisect start
> > # status: waiting for both good and bad commits
> > # bad: [f89c72a532b507111acfe1b83ff4855dc6772043] Linux 6.17.13-rc2
> > git bisect bad f89c72a532b507111acfe1b83ff4855dc6772043
> > # status: waiting for good commit(s), bad commit known
> > # good: [6fedb515e7f90986da3de36a35752e6dc2e0c911] Linux 6.17.12
> > git bisect good 6fedb515e7f90986da3de36a35752e6dc2e0c911
> > # good: [6fedb515e7f90986da3de36a35752e6dc2e0c911] Linux 6.17.12
> > git bisect good 6fedb515e7f90986da3de36a35752e6dc2e0c911
> > # good: [bef2390379e56d44e5fed5400bba2f6c2486cd6c] tracefs: fix a leak in eventfs_create_events_dir()
> > git bisect good bef2390379e56d44e5fed5400bba2f6c2486cd6c
> > # good: [16be45fa274beefba34a25da3551276b9fb48382] vhost: Fix kthread worker cgroup failure handling
> > git bisect good 16be45fa274beefba34a25da3551276b9fb48382
> > # good: [3e619964439334c23c079ff3986fd62d94d8c842] NFS: Initialise verifiers for visible dentries in _nfs4_open_and_get_state
> > git bisect good 3e619964439334c23c079ff3986fd62d94d8c842
> > # good: [9786c2e58c42de159067fa3ae7a5b1e029bdcab1] rtc: gamecube: Check the return value of ioremap()
> > git bisect good 9786c2e58c42de159067fa3ae7a5b1e029bdcab1
> > # good: [96b48878043620b06e74f5e435f0caf16105db8d] scsi: imm: Fix use-after-free bug caused by unfinished delayed work
> > git bisect good 96b48878043620b06e74f5e435f0caf16105db8d
> > # good: [299f05075dfe002156bbc46ba7da2a89357fe94f] usb: phy: Initialize struct usb_phy list_head
> > git bisect good 299f05075dfe002156bbc46ba7da2a89357fe94f
> > # good: [0ecfb458bae89e7cc2ceca578405a014a7090c33] ALSA: hda/realtek: Add match for ASUS Xbox Ally projects
> > git bisect good 0ecfb458bae89e7cc2ceca578405a014a7090c33
> > # good: [25b1100cb9ff0dcbd7263ab57fcede673be0ecc4] ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_hda_read_acpi()
> > git bisect good 25b1100cb9ff0dcbd7263ab57fcede673be0ecc4
> > # good: [5f0bc5d1d892e7bd28dab743c9e8dce2b6596fbc] ALSA: wavefront: Fix integer overflow in sample size validation
> > git bisect good 5f0bc5d1d892e7bd28dab743c9e8dce2b6596fbc
> > # first bad commit: [f89c72a532b507111acfe1b83ff4855dc6772043] Linux 6.17.13-rc2
>
> So the change that sets the makefile is the bad commit? I don't think
> the testing went correct for some reason :(
>
>
Actually i think that the problem was with my kernel config and
during the test process
i was requested to at least change the config if i wanted . I
accepted the default values.
I booted with the new configuration and dmesg -l err was clean.THANKS
for helping me :)
--
software engineer
rajagiri school of engineering and technology
Powered by blists - more mailing lists