From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 217914] scsi_eh_1 process high cpu after upgrading to 6.5
Date: Fri, 15 Sep 2023 21:06:07 +0000 [thread overview]
Message-ID: <bug-217914-11613-bOnMBR6Gu3@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217914-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217914
loberman@redhat.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |loberman@redhat.com
--- Comment #3 from loberman@redhat.com ---
Not reproducible generically for me
[root@penguin8 ~]# uname -a
Linux penguin8 6.5.0+ #2 SMP PREEMPT_DYNAMIC
[root@penguin8 ~]# lsscsi
[0:0:0:0] disk ATA Samsung SSD 850 3B6Q /dev/sdb
[1:0:0:0] disk ATA Samsung SSD 850 3B6Q /dev/sda
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1649 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_0]
root 1651 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_1]
root 1653 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_2]
root 1655 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_3]
root 1668 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_4]
root 1670 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_5]
root 1672 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_6]
root 1674 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_7]
root 1866 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_8]
root 1887 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_9]
root 1649 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_0]
root 1651 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_1]
root 1653 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_2]
root 1655 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_3]
root 1668 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_4]
root 1670 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_5]
root 1672 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_6]
root 1674 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_7]
root 1866 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_8]
root 1887 0.0 0.0 0 0 ? S 16:58 0:00 [scsi_eh_9]
I Have no CDROm so I think its the virtual cdrom.
In VMware the CDROM will continuously get probed and log errors due to no media
and every time that happens it will call the cdl stuff.
I will bring up a Virtual guest now, will take time as I will have to build
upstream kernels.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-09-15 21:07 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
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 [this message]
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-bOnMBR6Gu3@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).