https://bugzilla.kernel.org/show_bug.cgi?id=207855 --- Comment #11 from Janpieter Sollie (janpieter.sollie@xxxxxxxxx) --- the issue seems to be related to: > [59502.794967] Call Trace: > [59502.794967] _raw_spin_lock_irqsave+0x20/0x30 > [59502.794968] __scsi_iterate_devices+0x22/0x80 > [59502.794968] scsi_eh_ready_devs+0x129/0x7c0 > [59502.794968] ? __pm_runtime_resume+0x54/0x70 > [59502.794968] scsi_error_handler+0x394/0x3a0 > [59502.794969] kthread+0xf3/0x130 > [59502.794969] ? scsi_eh_get_sense+0x120/0x120 > [59502.794969] ? kthread_park+0x80/0x80 > [59502.794970] ret_from_fork+0x1f/0x30 As far as I see, this stack blocks the entire scsi subsystem. I do not see why: the scsi_error_handler runs in a separate kthread, so it *should* not block the IO subsystem ... but it definitely does: all storage devices on all SAS/SATA controllers (even USB) become inaccessible. I managed to get a dmesg out of it, but "echo 1 > /sys/class/pci_bus/0000\:04/device/reset" never completed. this command was issued over a running SSH session. A new session could not be established any longer. But it proves the PCI subsystem is partially intact. is it possible the raw_spin_lock_irqsave hurts when the adapter is not ready yet? and as such locks a device but never completes? -- You are receiving this mail because: You are the assignee for the bug.
