On 2/20/19 1:17 PM, Przemek Socha wrote:
Greetings,
recently, after resume from hibernation I'm getting a strange warning in my
dmesg output.
The whole process (hibernate/resume) triggers WARN_ON_ONCE at line 2600 in
scsi_lib.c file.
It is a Lenovo g50-45 netbook with sata ssd (micron 1100) and amd fch ahci
piix4 (1022:7801) sata controller. Scheduler is bfq.
Here is the WARNING part from machine's log:
[ 95.680910] WARNING: CPU: 2 PID: 11303 at drivers/scsi/scsi_lib.c:2600
scsi_device_resume+0x4f/0x58
[ 95.680912] Modules linked in: rfcomm nf_tables ebtable_nat ip_set
nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables overlay squashfs
loop bnep ipv6 ath3k btusb btintel bluetooth ecdh_generic rtsx_usb_sdmmc
rtsx_usb_ms memstick rtsx_usb uvcvideo videobuf2_vmalloc videobuf2_memops
videobuf2_v4l2 videobuf2_common videodev media kvm_amd ath9k ath9k_common
ath9k_hw kvm sdhci_pci cqhci irqbypass crc32_pclmul sdhci mac80211
ghash_clmulni_intel serio_raw mmc_core ath sp5100_tco amdgpu xhci_pci ehci_pci
ehci_hcd mfd_core cfg80211 chash xhci_hcd gpu_sched ttm
[ 95.680959] CPU: 2 PID: 11303 Comm: kworker/u8:70 Not tainted 5.0.0-rc1+
#50
[ 95.680961] Hardware name: LENOVO 80E3/Lancer 5B2, BIOS A2CN45WW(V2.13)
08/04/2016
[ 95.680966] Workqueue: events_unbound async_run_entry_fn
[ 95.680971] RIP: 0010:scsi_device_resume+0x4f/0x58
[ 95.680974] Code: 00 00 00 00 48 8b 7b 08 e8 96 33 e6 ff 83 bb d0 07 00 00
05 75 0a c7 83 d0 07 00 00 02 00 00 00 48 89 ef 5b 5d e9 d9 71 25 00 <0f> 0b
eb cb 0f 1f 44 00 00 eb a6 66 0f 1f 44 00 00 48 c7 c2 80 51
[ 95.680976] RSP: 0018:ffffba5482167e50 EFLAGS: 00010246
[ 95.680979] RAX: 0000000000000000 RBX: ffff9dff5610c800 RCX: 0000000000000000
[ 95.680980] RDX: ffff9dfef2dfc240 RSI: ffffffffaae8abc0 RDI: ffff9dff5610cfb0
[ 95.680982] RBP: ffff9dff5610cfb0 R08: 0000000000000008 R09: 0000646e756f626e
[ 95.680984] R10: 8080808080808080 R11: 0000000000000010 R12: ffff9dff56816000
[ 95.680986] R13: 0000000000000000 R14: ffff9dff276736c0 R15: 0ffff9dff5681600
[ 95.680988] FS: 0000000000000000(0000) GS:ffff9dff57b00000(0000) knlGS:
0000000000000000
[ 95.680990] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 95.680992] CR2: 0000000000000000 CR3: 00000001dfc0e000 CR4:
00000000000406e0
[ 95.680993] Call Trace:
[ 95.681003] scsi_dev_type_resume+0x2e/0x60
[ 95.681007] async_run_entry_fn+0x32/0xd8
[ 95.681012] process_one_work+0x1f4/0x420
[ 95.681016] worker_thread+0x28/0x3c0
[ 95.681020] ? rescuer_thread+0x330/0x330
[ 95.681023] kthread+0x118/0x130
[ 95.681027] ? kthread_create_on_node+0x60/0x60
[ 95.681033] ret_from_fork+0x22/0x40
[ 95.681038] ---[ end trace c27b17349dc21611 ]---
Hi Przemek,
Is this something that occurs systematically or only sporadically?
If it occurs systematically, did this behavior start with kernel
v5.0-rc1 or did it also occur with older kernel versions? Does this
behavior only occur with the BFQ I/O scheduler or does it also occur
with other I/O schedulers?
Thanks,
Bart.
