From: "Arnd Bergmann" <arnd@arndb.de>
To: "Naresh Kamboju" <naresh.kamboju@linaro.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Guenter Roeck" <linux@roeck-us.net>, shuah <shuah@kernel.org>,
patches@kernelci.org, lkft-triage@lists.linaro.org,
"Pavel Machek" <pavel@denx.de>,
"Jon Hunter" <jonathanh@nvidia.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Sudip Mukherjee" <sudipm.mukherjee@gmail.com>,
srw@sladewatkins.net, rwarsow@gmx.de,
"Conor Dooley" <conor@kernel.org>, Allen <allen.lkml@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
linux-block <linux-block@vger.kernel.org>,
"Jens Axboe" <axboe@kernel.dk>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Anders Roxell" <anders.roxell@linaro.org>,
"Can Guo" <quic_cang@quicinc.com>,
"Ziqi Chen" <quic_ziqichen@quicinc.com>,
"Bart Van Assche" <bvanassche@acm.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 6.9 000/222] 6.9.8-rc1 review
Date: Wed, 03 Jul 2024 11:24:29 +0200 [thread overview]
Message-ID: <c440be12-3c22-4bb6-9a10-e3fd03b87974@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYuK+dFrz3dcuUkxbP3R-5NUiSVNJ3tAcRc=Wn=Hs0C5ng@mail.gmail.com>
On Wed, Jul 3, 2024, at 11:08, Naresh Kamboju wrote:
> On Tue, 2 Jul 2024 at 22:36, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
>>
>> This is the start of the stable review cycle for the 6.9.8 release.
>> There are 222 patches in this series, all will be posted as a response
>> to this one. If anyone has any issues with these being applied, please
>> let me know.
>>
>> Responses should be made by Thu, 04 Jul 2024 17:01:55 +0000.
>> Anything received after that time might be too late.
>>
>> The whole patch series can be found in one patch at:
>> https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.9.8-rc1.gz
>> or in the git tree and branch at:
>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.9.y
>> and the diffstat can be found below.
>>
>> thanks,
>>
>> greg k-h
>>
>
> The following kernel warning was noticed on arm64 Qualcomm db845c device while
> booting stable-rc 6.9.8-rc1.
>
> This is not always a reproducible warning.
I see that commit 77691af484e2 ("scsi: ufs: core: Quiesce request
queues before checking pending cmds") got backported, and
this adds direct calls to the function that warns, so this
is my first suspicion without having done a detailed analysis.
Adding everyone from that commit to Cc.
Naresh, could you try reverting that commit?
Arnd
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Boot log:
> ------
> [ 0.000000] Linux version 6.9.8-rc1 (tuxmake@tuxmake) (Debian clang
> version 18.1.8 (++20240615103650+3b5b5c1ec4a3-1~exp1~20240615223815.136),
> Debian LLD 18.1.8) #1 SMP PREEMPT @1719942561
> [ 0.000000] KASLR enabled
> [ 0.000000] Machine model: Thundercomm Dragonboard 845c
> ...
> [ 7.097994] ------------[ cut here ]------------
> [ 7.097997] WARNING: CPU: 5 PID: 418 at block/blk-mq.c:262
> blk_mq_unquiesce_tagset (/builds/linux/block/blk-mq.c:295
> /builds/linux/block/blk-mq.c:297)
> [ 7.098009] Modules linked in: drm_display_helper qcom_q6v5_mss
> camcc_sdm845 i2c_qcom_geni videobuf2_memops qcom_rng bluetooth
> videobuf2_common spi_geni_qcom qrtr gpi phy_qcom_qmp_usb aux_bridge
> stm_core slim_qcom_ngd_ctrl qcrypto phy_qcom_qmp_ufs cfg80211 rfkill
> icc_osm_l3 phy_qcom_qmp_pcie lmh ufs_qcom slimbus qcom_wdt
> pdr_interface llcc_qcom qcom_q6v5_pas(+) qcom_pil_info icc_bwmon
> qcom_q6v5 display_connector qcom_sysmon qcom_common drm_kms_helper
> qcom_glink_smem mdt_loader qmi_helpers drm backlight socinfo rmtfs_mem
> [ 7.098062] Hardware name: Thundercomm Dragonboard 845c (DT)
> [ 7.098064] Workqueue: devfreq_wq devfreq_monitor
> [ 7.098071] pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 7.098074] pc : blk_mq_unquiesce_tagset
> (/builds/linux/block/blk-mq.c:295 /builds/linux/block/blk-mq.c:297)
> [ 7.098077] lr : blk_mq_unquiesce_tagset
> (/builds/linux/block/blk-mq.c:262 /builds/linux/block/blk-mq.c:297)
> [ 7.098080] sp : ffff8000812f3b40
> [ 7.098081] x29: ffff8000812f3b40 x28: 00000000000f4240 x27: 20c49ba5e353f7cf
> [ 7.098086] x26: 0000000000000000 x25: 0000000000000000 x24: ffff5bbe0a2e9910
> [ 7.098089] x23: ffff5bbe01f1a170 x22: ffff5bbe0a2e9220 x21: 0000000000000000
> [ 7.098093] x20: ffff5bbe0a2e9620 x19: ffff5bbe01f1a0e0 x18: 0000000000000002
> [ 7.098096] x17: 0000000000000400 x16: 0000000000000400 x15: 00000000a63e566e
> [ 7.098099] x14: 0000000000015eb9 x13: ffff8000812f0000 x12: ffff8000812f4000
> [ 7.098103] x11: 7cea885bfc7e6700 x10: ffffb0c2e5eb69ac x9 : 0000000000000000
> [ 7.098106] x8 : ffff5bbe0a2e9624 x7 : ffff5bbe0c828000 x6 : 0000000000000003
> [ 7.098110] x5 : 00000000000009d3 x4 : 000000000000039e x3 : ffff8000812f3af0
> [ 7.098113] x2 : ffff5bbe0a2acc00 x1 : 0000000000000000 x0 : 0000000000000000
> [ 7.098117] Call trace:
> [ 7.098118] blk_mq_unquiesce_tagset
> (/builds/linux/block/blk-mq.c:295 /builds/linux/block/blk-mq.c:297)
> [ 7.098121] ufshcd_devfreq_scale
> (/builds/linux/drivers/ufs/core/ufshcd.c:2050
> /builds/linux/drivers/ufs/core/ufshcd.c:1426
> /builds/linux/drivers/ufs/core/ufshcd.c:1472)
> [ 7.098126] ufshcd_devfreq_target
> (/builds/linux/drivers/ufs/core/ufshcd.c:1581)
> [ 7.098129] devfreq_set_target (/builds/linux/drivers/devfreq/devfreq.c:364)
> [ 7.098132] devfreq_update_target (/builds/linux/drivers/devfreq/devfreq.c:0)
> [ 7.098134] devfreq_monitor (/builds/linux/drivers/devfreq/devfreq.c:461)
> [ 7.098136] process_scheduled_works
> (/builds/linux/kernel/workqueue.c:3272
> /builds/linux/kernel/workqueue.c:3348)
> [ 7.098141] worker_thread (/builds/linux/include/linux/list.h:373
> /builds/linux/kernel/workqueue.c:955
> /builds/linux/kernel/workqueue.c:3430)
> [ 7.098143] kthread (/builds/linux/kernel/kthread.c:390)
> [ 7.098146] ret_from_fork (/builds/linux/arch/arm64/kernel/entry.S:861)
> [ 7.098150] ---[ end trace 0000000000000000 ]---
>
>
> Full boot log link:
> -
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.9.y/build/v6.9.7-223-g03247eed042d/testrun/24504400/suite/log-parser-boot/test/check-kernel-exception/log
> - https://lkft.validation.linaro.org/scheduler/job/7711345#L5312
>
> Details of build and test environment:
> -
> https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/tests/2ihUJNrmztabOMpKVRNzLpixoUR
>
> Build, vmlinux, System.map and Image,
> -
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2ihUHH774XQWba653iwCVtCnpjl/
>
> metadata:
> -------
> git_describe: v6.9.7-223-g03247eed042d
> git_repo:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> git_sha: 03247eed042d6a770c3a2adaeed6b7b4a0f0b46c
> kernel-config:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2ihUHH774XQWba653iwCVtCnpjl/config
> kernel_version: 6.9.8-rc1
> toolchain: clang-18
> build-url:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2ihUHH774XQWba653iwCVtCnpjl/
> build_name: clang-18-lkftconfig
>
> --
> Linaro LKFT
> https://lkft.linaro.org
next prev parent reply other threads:[~2024-07-03 9:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 17:00 Greg Kroah-Hartman
2024-07-02 19:19 ` SeongJae Park
2024-07-02 21:38 ` Mark Brown
2024-07-02 22:32 ` Christian Heusel
2024-07-02 23:40 ` Shuah Khan
2024-07-03 4:25 ` Bagas Sanjaya
2024-07-03 8:13 ` Jon Hunter
2024-07-03 9:08 ` Naresh Kamboju
2024-07-03 9:24 ` Arnd Bergmann [this message]
2024-07-03 17:51 ` Naresh Kamboju
2024-07-03 13:40 ` Justin Forbes
2024-07-03 16:49 ` Pavel Machek
2024-07-03 16:54 ` Peter Schneider
2024-07-03 17:32 ` Kelsey Steele
2024-07-03 21:14 ` Ron Economos
2024-07-04 7:01 ` Naresh Kamboju
2024-07-04 19:52 ` Florian Fainelli
2024-07-02 18:31 Ronald Warsow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c440be12-3c22-4bb6-9a10-e3fd03b87974@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=anders.roxell@linaro.org \
--cc=axboe@kernel.dk \
--cc=broonie@kernel.org \
--cc=bvanassche@acm.org \
--cc=conor@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=martin.petersen@oracle.com \
--cc=naresh.kamboju@linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=quic_cang@quicinc.com \
--cc=quic_ziqichen@quicinc.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®