From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 217914] New: scsi_eh_1 process high cpu after upgrading to 6.5
Date: Fri, 15 Sep 2023 19:33:01 +0000 [thread overview]
Message-ID: <bug-217914-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=217914
Bug ID: 217914
Summary: scsi_eh_1 process high cpu after upgrading to 6.5
Product: IO/Storage
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: high
Priority: P3
Component: SCSI
Assignee: linux-scsi@vger.kernel.org
Reporter: laktak@cdak.net
Regression: Yes
Bisected 624885209f31eb9985bf51abe204ecbffe2fdeea
commit-id:
Overview:
Several users report that after upgrading from 6.4.12 to 6.5 the process
scsi_eh_1 will constantly consume >10% CPU resources. This happens most often
in VMs.
Steps to Reproduce:
- Create a VM (e.g. VMware Fusion)
- Create an SCSI disk
- Connect a virtual CD ROM (IDE)
- Boot a 6.4.12 kernel
- Boot a 6.5 kernel
Actual Results:
- no issues for the 6.4.12 kernel
- scsi_eh consumes too much CPU with the 6.5 kernel
Expected Results:
scsi_eh should not consume significant resources.
Build Date & Hardware:
Linux arch 6.5.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 06 Sep 2023 21:01:01 +0000
x86_64 GNU/Linux
inside a VMware Fusion VM
Additional Builds and Platforms:
Other users were able to reproduce the error on bare metal hardware.
Additional Information:
More details can be found in this thread:
https://bbs.archlinux.org/viewtopic.php?id=288723
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
good: 6.4.0-rc1-1-00007-g152e52fb6ff1
bad: 6.4.0-rc1-1-00008-g624885209f31
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-09-15 19:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 19:33 bugzilla-daemon [this message]
2023-09-15 20:42 ` [Bug 217914] New: scsi_eh_1 process high cpu after upgrading to 6.5 Bart Van Assche
2023-09-15 20:55 ` Laurence Oberman
2023-09-15 22:01 ` Niklas Cassel
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=bug-217914-11613@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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;
as well as URLs for NNTP newsgroup(s).