From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "bugzilla-daemon@kernel.org" <bugzilla-daemon@kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [Bug 217914] New: scsi_eh_1 process high cpu after upgrading to 6.5
Date: Fri, 15 Sep 2023 22:01:37 +0000 [thread overview]
Message-ID: <ZQTUQGG0Q5k+CMSV@x1-carbon> (raw)
In-Reply-To: <41689a20-af9d-420f-af4f-72e299a765b7@acm.org>
On Fri, Sep 15, 2023 at 01:42:18PM -0700, Bart Van Assche wrote:
> On 9/15/23 12:33, bugzilla-daemon@kernel.org wrote:
> > The users loqs and leonshaw helped to narrow it down to this commit:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=624885209f31eb9985bf51abe204ecbffe2fdeea
>
> Damien, can you please take a look?
>
Hello Bart,
It seems like:
https://lore.kernel.org/linux-scsi/20230915022034.678121-1-dlemoal@kernel.org/
Solves the problem.
From a quick look at the logs with extra log leves enabled:
https://pastebin.com/f2LQ8kQD
it appears that the MAINTENANCE_IN / MI_REPORT_SUPPORTED_OPERATION_CODES
command with a non-zero service action issued by scsi_cdl_check() fails,
and will be added to SCSI EH over and over.
Kind regards,
Niklas
next prev parent reply other threads:[~2023-09-15 22:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 19:33 [Bug 217914] New: scsi_eh_1 process high cpu after upgrading to 6.5 bugzilla-daemon
2023-09-15 20:42 ` Bart Van Assche
2023-09-15 20:55 ` Laurence Oberman
2023-09-15 22:01 ` Niklas Cassel [this message]
2023-09-15 22:10 ` Damien Le Moal
2023-09-15 22:46 ` Damien Le Moal
2023-09-15 20:42 ` [Bug 217914] " bugzilla-daemon
2023-09-15 20:55 ` bugzilla-daemon
2023-09-15 21:06 ` bugzilla-daemon
2023-09-15 22:01 ` bugzilla-daemon
2023-09-15 22:10 ` bugzilla-daemon
2023-09-15 22:46 ` bugzilla-daemon
2023-11-13 3:30 ` bugzilla-daemon
2023-11-13 11:53 ` Niklas Cassel
2023-11-13 11:53 ` bugzilla-daemon
2023-11-13 12:02 ` bugzilla-daemon
2023-11-27 9:50 ` bugzilla-daemon
2024-11-21 9:32 ` bugzilla-daemon
2024-11-21 19:30 ` bugzilla-daemon
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=ZQTUQGG0Q5k+CMSV@x1-carbon \
--to=niklas.cassel@wdc.com \
--cc=bugzilla-daemon@kernel.org \
--cc=bvanassche@acm.org \
--cc=dlemoal@kernel.org \
--cc=linux-scsi@vger.kernel.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