topic Re: tee /sys/class/scsi_host builds up in HPE Morpheus VM Essentials Software

tee /sys/class/scsi_host builds up

JS75 — Fri, 17 Jul 2026 07:21:26 GMT

Hello,

We are now running an internal PoC and I've found the nodes to run 'tee' every 2 minutes. They are never finished and piling up, increasing load to 1000s after a few days and blocking reboots since even kill -9 does not kill them. Is it a known problem? I've seen it with 8.1.2 and now with 9.0 as well.

root 223698 223690 0 08:08 ? 00:00:00 sudo tee /sys/class/scsi_host/host1/scan
root 223699 223698 0 08:08 ? 00:00:00 tee /sys/class/scsi_host/host1/scan
root 224170 224162 0 08:10 ? 00:00:00 sudo tee /sys/class/scsi_host/host1/scan
root 224171 224170 0 08:10 ? 00:00:00 tee /sys/class/scsi_host/host1/scan
root 224792 224784 0 08:12 ? 00:00:00 sudo tee /sys/class/scsi_host/host1/scan
root 224793 224792 0 08:12 ? 00:00:00 tee /sys/class/scsi_host/host1/scan
root 225266 225258 0 08:14 ? 00:00:00 sudo tee /sys/class/scsi_host/host1/scan
root 225267 225266 0 08:14 ? 00:00:00 tee /sys/class/scsi_host/host1/scan
root 225733 225725 0 08:17 ? 00:00:00 sudo tee /sys/class/scsi_host/host1/scan
root 225734 225733 0 08:17 ? 00:00:00 tee /sys/class/scsi_host/host1/scan
root 226209 226201 0 08:19 ? 00:00:00 sudo tee /sys/class/scsi_host/host1/scan
root 226210 226209 0 08:19 ? 00:00:00 tee /sys/class/scsi_host/host1/scan
root 226692 226684 0 08:21 ? 00:00:00 sudo tee /sys/class/scsi_host/host1/scan
root 226693 226692 0 08:21 ? 00:00:00 tee /sys/class/scsi_host/host1/scan
root 227279 19366 0 08:22 pts/1 00:00:00 grep --color=auto tee
root@chdc2hvm01:/home/superuser# ps -ef|grep tee|wc -l
805

Re: tee /sys/class/scsi_host builds up

DiegoDelgado — Mon, 20 Jul 2026 15:28:51 GMT

I’ve seen something intermittent in the past.
Can you please check the kernel version in the hosts using “uname -a”?

It might also be worth it updating the packages in the host by running:

sudo apt update

sudo apt upgrade

Re: tee /sys/class/scsi_host builds up

DavidL1987 — Tue, 28 Jul 2026 09:06:55 GMT

Good morning,

We have the same issue with 2 customers.

Both customers are using the following kernel (all hosts are updated with apt update && apt upgrade):

6.8.0-117-generic

Both are also using the smartpqi driver:

version: 2.1.26-030
description: Driver for Microchip Smart Family Controller version 2.1.26-030
srcversion: 4E3F014CA5DB70DCF642B3B
vermagic: 6.8.0-117-generic SMP preempt mod_unload modversions

1 customer is a GFS2 2-node cluster with a SAS attached MSA2070
1 customer is a single node with local storage.

Another customer that is using the megaraid_sas driver does not have this issue.

I have now created a ticket for both.

Ynt: tee /sys/class/scsi_host builds up

duru19 — Tue, 28 Jul 2026 10:22:54 GMT

Hello,

The following command is normally used to trigger a SCSI bus rescan and discover new LUNs;

echo "- - -" | sudo tee /sys/class/scsi_host/host1/scan

In this case, the SCSI scan appears to become blocked inside the kernel or storage driver. The tee process is therefore likely entering an uninterruptible sleep state (D state). Processes in this state cannot be terminated with kill -9 until the underlying kernel operation returns.

Since another scan is initiated approximately every two minutes, the blocked processes continue to accumulate. This also explains the extremely high load average, as uninterruptible I/O processes are included in the Linux load calculation.

Similar behavior has been reported on VM Essentials 8.1.x and 9.0, including HPE Support Case 5402620210. Recent reports show a

possible correlation with;

Kernel: 6.8.0-117-generic
Driver: smartpqi 2.1.26-030
Smart Array/local storage and SAS-attached MSA environments

A comparable environment using the megaraid_sas driver reportedly did not experience the issue. However, this correlation has not yet been published as a confirmed root cause by HPE.

Could you please collect the following outputs from an affected host?

uname -a

cat /sys/class/scsi_host/host1/proc_name

readlink -f /sys/class/scsi_host/host1/device/driver

modinfo smartpqi | egrep "filename|version|srcversion|vermagic"

lspci -nnk | grep -A4 -Ei "RAID|SAS|SCSI"

ps -eo pid,ppid,stat,wchan:40,etime,cmd | grep -E "tee|scsi_host"

pstree -aps <TEE_PID>

sudo cat /proc/<TEE_PID>/stack

In particular, please check whether the tee processes are in D state and whether their kernel stacks contain scsi_scan, smartpqi, or pqi functions.

As immediate precautions, we recommend;

Do not initiate any additional manual SCSI scans.
Identify the process or HVM Agent task launching the scan by checking its parent process.
Do not stop or disable the HVM Agent without HPE guidance, as this may affect management and HA functions.
If a reboot is required, migrate or safely shut down the workloads and place the host into maintenance mode first.
Open an HPE support case and reference the similar case 5402620210.
Ask HPE whether the VM Essentials v9.0.0_2 hotfix includes a correction for this issue.
Update the kernel, smartpqi driver, or controller firmware only after confirming compatibility with the installed VM Essentials version.

Based on the available evidence, this should be investigated as a possible smartpqi/kernel-level SCSI scan issue. The accumulating tee processes appear to be a symptom rather than the actual cause.

Ynt: tee /sys/class/scsi_host builds up

DavidL1987 — Tue, 28 Jul 2026 11:29:45 GMT

Good afternoon,

Below is the output of the requested commands. I'm also going to add the mentioned casenumber and potential hotfix to the support case I have running. Some commands I have cropped the output due to the character limit.

uname -a

Linux fs-hvm-01-26 6.8.0-117-generic #117-Ubuntu SMP PREEMPT_DYNAMIC Tue May 5 19:26:24 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux

cat /sys/class/scsi_host/host0/proc_name

smartpqi

readlink -f /sys/class/scsi_host/host0/device/driver

/sys/devices/pci0000:b0/0000:b0:00.0/0000:b1:00.0/host0/driver

modinfo smartpqi | egrep "filename|version|srcversion|vermagic"

filename: /lib/modules/6.8.0-117-generic/kernel/drivers/scsi/smartpqi/smartpqi.ko.zst

version: 2.1.26-030

description: Driver for Microchip Smart Family Controller version 2.1.26-030

srcversion: 4E3F014CA5DB70DCF642B3B

vermagic: 6.8.0-117-generic SMP preempt mod_unload modversions

lspci -nnk | grep -A4 -Ei "RAID|SAS|SCSI"

b1:00.0 Serial Attached SCSI controller [0107]: Adaptec Smart Storage PQI SAS [9005:028f] (rev 01)

DeviceName: Embedded RAID 1

Subsystem: Hewlett-Packard Company Smart Array P408i-a SR Gen10 [103c:0602]

Kernel driver in use: smartpqi

Kernel modules: smartpqi

b2:00.0 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)

ps -eo pid,ppid,stat,wchan:40,etime,cmd | grep -E "tee|scsi_host"

8833 8828 S - 1-10:29:21 sudo tee /sys/class/scsi_host/host0/scan

8834 8833 R - 1-10:29:21 tee /sys/class/scsi_host/host0/scan

946021 946020 D - 01:19:55 tee /sys/class/scsi_host/host0/scan

949119 949114 S - 01:13:25 sudo tee /sys/class/scsi_host/host0/scan

949120 949119 D - 01:13:25 tee /sys/class/scsi_host/host0/scan

952178 952173 S - 01:06:55 sudo tee /sys/class/scsi_host/host0/scan

952179 952178 D - 01:06:55 tee /sys/class/scsi_host/host0/scan

955035 955030 S - 01:00:25 sudo tee /sys/class/scsi_host/host0/scan

955036 955035 D - 01:00:25 tee /sys/class/scsi_host/host0/scan

958027 958022 S - 53:55 sudo tee /sys/class/scsi_host/host0/scan

958028 958027 D - 53:55 tee /sys/class/scsi_host/host0/scan

961086 961081 S - 47:25 sudo tee /sys/class/scsi_host/host0/scan

961087 961086 D - 47:25 tee /sys/class/scsi_host/host0/scan

963944 963939 S - 40:54 sudo tee /sys/class/scsi_host/host0/scan

963947 963944 D - 40:54 tee /sys/class/scsi_host/host0/scan

967010 967005 S - 34:24 sudo tee /sys/class/scsi_host/host0/scan

967011 967010 D - 34:24 tee /sys/class/scsi_host/host0/scan

969950 969945 S - 27:54 sudo tee /sys/class/scsi_host/host0/scan

969951 969950 D - 27:54 tee /sys/class/scsi_host/host0/scan

972864 972859 S - 21:24 sudo tee /sys/class/scsi_host/host0/scan

972865 972864 D - 21:24 tee /sys/class/scsi_host/host0/scan

975877 975872 S - 14:54 sudo tee /sys/class/scsi_host/host0/scan

975878 975877 D - 14:54 tee /sys/class/scsi_host/host0/scan

979260 979255 S - 08:24 sudo tee /sys/class/scsi_host/host0/scan

979261 979260 D - 08:24 tee /sys/class/scsi_host/host0/scan

982204 982199 S - 01:54 sudo tee /sys/class/scsi_host/host0/scan

982205 982204 D - 01:54 tee /sys/class/scsi_host/host0/scan

983458 980595 S+ pipe_read 00:00 grep --color=auto -E tee|scsi_host

pstree -aps 8834

systemd,1 ---

└─bash,8828 -l

└─sudo,8833 tee /sys/class/scsi_host/host0/scan

└─tee,8834 /sys/class/scsi_host/host0/scan

sudo cat /proc/PID/stack

no output for 8834

Below output for 8833

[<0>] do_poll.constprop.0+0x319/0x3c0

[<0>] do_sys_poll+0x1ef/0x290

[<0>] __x64_sys_ppoll+0xde/0x170

[<0>] x64_sys_call+0x2343/0x25a0

[<0>] do_syscall_64+0x7f/0x180

[<0>] entry_SYSCALL_64_after_hwframe+0x78/0x80

sudo journalctl -k -b | egrep -i \

Jul 26 17:56:08 fs-hvm-01-26 kernel: SCSI subsystem initialized

Jul 26 17:56:08 fs-hvm-01-26 kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243)

Jul 26 17:56:08 fs-hvm-01-26 kernel: Microchip SmartPQI Driver (v2.1.26-030)

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: Microchip Smart Family Controller found

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: enabling device (0140 -> 0142)

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: Online Firmware Activation not supported by controller

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: Maximum Known Feature not supported by controller

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: RAID 0 Read Bypass not supported by controller

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: RAID 1 Read Bypass not supported by controller

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: RAID 5 Read Bypass not supported by controller

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: RAID 6 Read Bypass not supported by controller

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: RAID 0 Write Bypass not supported by controller

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: RAID 1 Write Bypass not supported by controller

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: RAID 5 Write Bypass not supported by controller

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: RAID 6 Write Bypass not supported by controller

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: RAID Bypass on encrypted logical volumes on NVMe not supported by controller

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: RPL Extended Formats 4 and 5 not supported by controller

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: Serial Management Protocol enabled

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: New Soft Reset Handshake enabled

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: RAID IU Timeout enabled

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: TMF IU Timeout enabled

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: Firmware Triage enabled

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: Multi-LUN Target enabled

Jul 26 17:56:08 fs-hvm-01-26 kernel: scsi host0: smartpqi

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: Firmware version: 8.00

Jul 26 17:56:08 fs-hvm-01-26 kernel: scsi 0:0:0:0: Enclosure HPE Smart Adapter 8.00 PQ: 0 ANSI: 5

Jul 26 17:56:08 fs-hvm-01-26 kernel: scsi host1: usb-storage 3-4:1.0

Jul 26 17:56:08 fs-hvm-01-26 kernel: scsi 0:0:0:0: Attached scsi generic sg0 type 13

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: added 0:0:0:0 51402ec0167a27a80000000000000000 Enclosure HPE Smart Adapter AIO-

Jul 26 17:56:08 fs-hvm-01-26 kernel: scsi 0:1:0:0: Direct-Access HPE LOGICAL VOLUME 8.00 PQ: 0 ANSI: 5

Jul 26 17:56:08 fs-hvm-01-26 kernel: sd 0:1:0:0: Attached scsi generic sg1 type 0

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: added 0:1:0:0 4000000000000000 Direct-Access HPE LOGICAL VOLUME SSDSmartPathCap+ En+ RAID-1(1+0)

Jul 26 17:56:08 fs-hvm-01-26 kernel: scsi 0:1:0:1: Direct-Access HPE LOGICAL VOLUME 8.00 PQ: 0 ANSI: 5

Jul 26 17:56:08 fs-hvm-01-26 kernel: sd 0:1:0:0: [sda] Attached SCSI disk

Jul 26 17:56:08 fs-hvm-01-26 kernel: scsi 1:0:0:0: Direct-Access Generic- SD/MMC CRW 1.00 PQ: 0 ANSI: 6

Jul 26 17:56:08 fs-hvm-01-26 kernel: sd 1:0:0:0: Attached scsi generic sg2 type 0

Jul 26 17:56:08 fs-hvm-01-26 kernel: sd 1:0:0:0: [sdb] Attached SCSI removable disk

Jul 26 17:56:08 fs-hvm-01-26 kernel: sd 0:1:0:1: Attached scsi generic sg3 type 0

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: added 0:1:0:1 4000000100000000 Direct-Access HPE LOGICAL VOLUME SSDSmartPathCap- En- RAID-5

Jul 26 17:56:08 fs-hvm-01-26 kernel: scsi 0:2:0:0: RAID HPE P408i-a SR Gen10 8.00 PQ: 0 ANSI: 5

Jul 26 17:56:08 fs-hvm-01-26 kernel: sd 0:1:0:1: [sdc] Attached SCSI disk

Jul 26 17:56:08 fs-hvm-01-26 kernel: scsi 0:2:0:0: Attached scsi generic sg4 type 12

Jul 26 17:56:08 fs-hvm-01-26 kernel: smartpqi 0000:b1:00.0: added 0:2:0:0 0000000000000000 RAID HPE P408i-a SR Gen10

Jul 26 17:56:10 fs-hvm-01-26 kernel: Timeout policy base is empty

Jul 26 18:22:40 fs-hvm-01-26 kernel: INFO: task tee:11915 blocked for more than 122 seconds.

Jul 26 18:22:40 fs-hvm-01-26 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Jul 26 18:22:40 fs-hvm-01-26 kernel: scsi_scan_target+0x70/0x100

Jul 26 18:22:40 fs-hvm-01-26 kernel: scan_channel_zero+0x8c/0x90 [scsi_transport_sas]

Jul 26 18:22:40 fs-hvm-01-26 kernel: sas_user_scan+0x76/0x100 [scsi_transport_sas]

Jul 26 18:24:43 fs-hvm-01-26 kernel: INFO: task tee:11915 blocked for more than 245 seconds.

Jul 26 18:24:43 fs-hvm-01-26 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Jul 26 18:24:43 fs-hvm-01-26 kernel: scsi_scan_target+0x70/0x100

Jul 26 18:24:43 fs-hvm-01-26 kernel: scan_channel_zero+0x8c/0x90 [scsi_transport_sas]

Jul 26 18:24:43 fs-hvm-01-26 kernel: sas_user_scan+0x76/0x100 [scsi_transport_sas]

Jul 26 18:26:45 fs-hvm-01-26 kernel: INFO: task tee:11915 blocked for more than 368 seconds.

Jul 26 18:26:45 fs-hvm-01-26 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Jul 26 18:26:45 fs-hvm-01-26 kernel: scsi_scan_target+0x70/0x100

Jul 26 18:26:45 fs-hvm-01-26 kernel: scan_channel_zero+0x8c/0x90 [scsi_transport_sas]

Jul 26 18:26:45 fs-hvm-01-26 kernel: sas_user_scan+0x76/0x100 [scsi_transport_sas]

Jul 26 18:28:48 fs-hvm-01-26 kernel: INFO: task tee:11915 blocked for more than 491 seconds.

Jul 26 18:28:48 fs-hvm-01-26 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Jul 26 18:28:48 fs-hvm-01-26 kernel: scsi_scan_target+0x70/0x100

Jul 26 18:28:48 fs-hvm-01-26 kernel: scan_channel_zero+0x8c/0x90 [scsi_transport_sas]

Jul 26 18:28:48 fs-hvm-01-26 kernel: sas_user_scan+0x76/0x100 [scsi_transport_sas]

Jul 26 18:28:48 fs-hvm-01-26 kernel: INFO: task tee:15046 blocked for more than 122 seconds.

Jul 26 18:28:48 fs-hvm-01-26 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Jul 26 18:28:48 fs-hvm-01-26 kernel: sas_user_scan+0x68/0x100 [scsi_transport_sas]

Jul 26 18:30:51 fs-hvm-01-26 kernel: INFO: task tee:11915 blocked for more than 614 seconds.

Jul 26 18:30:51 fs-hvm-01-26 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Jul 26 18:30:51 fs-hvm-01-26 kernel: scsi_scan_target+0x70/0x100

Jul 26 18:30:51 fs-hvm-01-26 kernel: scan_channel_zero+0x8c/0x90 [scsi_transport_sas]

Jul 26 18:30:51 fs-hvm-01-26 kernel: sas_user_scan+0x76/0x100 [scsi_transport_sas]

Jul 26 18:30:51 fs-hvm-01-26 kernel: INFO: task tee:15046 blocked for more than 245 seconds.

Jul 26 18:30:51 fs-hvm-01-26 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Jul 26 18:30:51 fs-hvm-01-26 kernel: sas_user_scan+0x68/0x100 [scsi_transport_sas]

Jul 26 18:32:54 fs-hvm-01-26 kernel: INFO: task tee:11915 blocked for more than 737 seconds.

Jul 26 18:32:54 fs-hvm-01-26 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Jul 26 18:32:54 fs-hvm-01-26 kernel: scsi_scan_target+0x70/0x100

Jul 26 18:32:54 fs-hvm-01-26 kernel: scan_channel_zero+0x8c/0x90 [scsi_transport_sas]

Jul 26 18:32:54 fs-hvm-01-26 kernel: sas_user_scan+0x76/0x100 [scsi_transport_sas]

Jul 26 18:32:54 fs-hvm-01-26 kernel: INFO: task tee:15046 blocked for more than 368 seconds.

Jul 26 18:32:54 fs-hvm-01-26 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Jul 26 18:32:54 fs-hvm-01-26 kernel: sas_user_scan+0x68/0x100 [scsi_transport_sas]

Jul 26 18:34:57 fs-hvm-01-26 kernel: INFO: task tee:11915 blocked for more than 860 seconds.

Jul 26 18:34:57 fs-hvm-01-26 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Jul 26 18:34:57 fs-hvm-01-26 kernel: scsi_scan_target+0x70/0x100

Jul 26 18:34:57 fs-hvm-01-26 kernel: scan_channel_zero+0x8c/0x90 [scsi_transport_sas]

Jul 26 18:34:57 fs-hvm-01-26 kernel: sas_user_scan+0x76/0x100 [scsi_transport_sas]

Jul 26 18:34:57 fs-hvm-01-26 kernel: Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings

Jul 27 01:59:58 fs-hvm-01-26 kernel: sysrq: Show Blocked State

Jul 27 01:59:58 fs-hvm-01-26 kernel: scsi_scan_target+0x70/0x100

Jul 27 01:59:58 fs-hvm-01-26 kernel: scan_channel_zero+0x8c/0x90 [scsi_transport_sas]

Jul 27 01:59:58 fs-hvm-01-26 kernel: sas_user_scan+0x76/0x100 [scsi_transport_sas]

Jul 27 01:59:58 fs-hvm-01-26 kernel: sas_user_scan+0x68/0x100 [scsi_transport_sas]

Jul 27 02:00:03 fs-hvm-01-26 kernel: schedule_hrtimeout_range_clock+0x132/0x140

Jul 27 02:00:03 fs-hvm-01-26 kernel: schedule_hrtimeout_range+0x13/0x30

Jul 27 02:00:03 fs-hvm-01-26 kernel: schedule_timeout+0x95/0x170

Jul 27 02:00:03 fs-hvm-01-26 kernel: ? __pfx_process_timeout+0x10/0x10

Jul 27 02:00:03 fs-hvm-01-26 kernel: task:khungtaskd state:S stack:0 pid:114 tgid:114 ppid:2 flags:0x00004000

Jul 27 02:00:03 fs-hvm-01-26 kernel: schedule_timeout+0x95/0x170

Jul 27 02:00:03 fs-hvm-01-26 kernel: ? __pfx_process_timeout+0x10/0x10

Jul 27 02:00:03 fs-hvm-01-26 kernel: schedule_timeout_interruptible+0x1e/0x30

Jul 27 02:00:03 fs-hvm-01-26 kernel: schedule_timeout+0x95/0x170

Jul 27 02:00:03 fs-hvm-01-26 kernel: ? __pfx_process_timeout+0x10/0x10

Jul 27 02:00:03 fs-hvm-01-26 kernel: schedule_timeout+0x95/0x170

Jul 27 02:00:03 fs-hvm-01-26 kernel: ? __pfx_process_timeout+0x10/0x10

Jul 27 02:00:03 fs-hvm-01-26 kernel: schedule_timeout+0x95/0x170

Jul 27 02:00:03 fs-hvm-01-26 kernel: ? __pfx_process_timeout+0x10/0x10

Jul 27 02:00:03 fs-hvm-01-26 kernel: task:scsi_eh_0 state:S stack:0 pid:291 tgid:291 ppid:2 flags:0x00004000

Jul 27 02:00:03 fs-hvm-01-26 kernel: ? __pfx_scsi_error_handler+0x10/0x10

Jul 27 02:00:03 fs-hvm-01-26 kernel: scsi_error_handler+0xd6/0x1f0

Jul 27 02:00:03 fs-hvm-01-26 kernel: task:kworker/R-scsi_ state:I stack:0 pid:292 tgid:292 ppid:2 flags:0x00004000

Jul 27 02:00:03 fs-hvm-01-26 kernel: task:scsi_eh_1 state:S stack:0 pid:293 tgid:293 ppid:2 flags:0x00004000

Jul 27 02:00:03 fs-hvm-01-26 kernel: ? __pfx_scsi_error_handler+0x10/0x10

Jul 27 02:00:03 fs-hvm-01-26 kernel: scsi_error_handler+0xd6/0x1f0

Jul 27 02:00:03 fs-hvm-01-26 kernel: task:kworker/R-scsi_ state:I stack:0 pid:294 tgid:294 ppid:2 flags:0x00004000

Jul 27 02:00:03 fs-hvm-01-26 kernel: schedule_timeout+0x157/0x170

Jul 27 02:00:03 fs-hvm-01-26 kernel: schedule_hrtimeout_range_clock+0x132/0x140

Jul 27 02:00:03 fs-hvm-01-26 kernel: schedule_hrtimeout_range+0x13/0x30

Jul 27 02:00:03 fs-hvm-01-26 kernel: schedule_hrtimeout_range_clock+0xe2/0x140

Jul 27 02:00:03 fs-hvm-01-26 kernel: schedule_hrtimeout_range+0x13/0x30

Jul 27 02:00:03 fs-hvm-01-26 kernel: schedule_hrtimeout_range_clock+0x132/0x140

Jul 27 02:00:03 fs-hvm-01-26 kernel: schedule_hrtimeout_range+0x13/0x30

Jul 27 02:00:03 fs-hvm-01-26 kernel: schedule_timeout+0x157/0x170

Jul 27 02:00:03 fs-hvm-01-26 kernel: ? __update_blocked_fair+0xa4/0x600