Bug 201953

Summary:	System freeze/hang during shutdown/restart (at " sd 0:0:0:0: [sda] Stopping disk")
Product:	SCSI Drivers	Reporter:	Statstical anomaly (sivadasrajan007)
Component:	Other	Assignee:	scsi_drivers-other
Status:	RESOLVED INSUFFICIENT_DATA
Severity:	high	CC:	sivadasrajan007, svv75
Priority:	P1
Hardware:	Intel
OS:	Linux
Kernel Version:	4.* ish (i checked many distros and everything has it))	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	phphoto of frozen screen during shutdown(screen is black during restart hang)

Description Statstical anomaly 2018-12-10 17:15:08 UTC

Created attachment 279923 [details]
phphoto of frozen screen during shutdown(screen is black during restart hang)

I was using kali linux 2018.2 on my laptop(hardware specs at the end) without any problem. then i replaced my hard disk with an ssd and this problem started during 95% of shutdowns/restart

                                                                            
The real problem
================

1)When i shutdown the system hangs at this specific step(photo of frozen screen during shutdown is  attached,for restart screen goes black and hang)

2)when i restart screen turns off (goes black/backlight turns off) but still frozen (hdd/wifi/numlock leds stuck)

the last messege on screen is the following

 "sd 0:0:0:0:  [sda] Stopping disk"


  i tried the following distros and all has the same problem (why i 
    concluded this is a kernel issue)
   => kali 2018.2 
   => ubuntu 18.4 LTS
   => fedora workstation 29-1.2
   => openSUSE Tumbleweed 20181120 (netinstall)

NOTE:
1) this system used to have a baytrail cstate freeze bug 
   https://bugzilla.kernel.org/show_bug.cgi?id=109051

   and fixed with the boot parameter



you may find the following info useful 


HARDWARE of my SYSTEM
=====================

i use a laptop HP-15-r250tu with the following hardware

 cpu: intel pentum N3540
 ram: 4gb samsung ddr3 
 graphics: intel hd graphics (Vendor ID: 0x8086,Device ID: 0x0F31)
 storage: KINGSTON A400 SSD 240GB (SA400S37/240g) 



===========================================================================

My findings:(maybe somone find this useful,probably not for experts )
--------------------------------------

i have no prior experiance with linux kernel code. but i downloaded linux source v4.19.8 and found these

 *) the kernel module that issue this "Stop disk" command is 
    sd (drivers/scsi/sd.c)

  *)and this traces to a general function call to execute all scsi commands
     which is 
     "scsi_execute(sdp, cmd, DMA_NONE, NULL, 0, NULL, &sshdr,SD_TIMEOUT, 
      SD_MAX_RETRIES, 0, RQF_PM, NULL)"
  
My conclusion(from my knowledge and understanding :-) )
------------------------

   probably cause is "scsi_execute" function not returning, so that  it put the system in a very long wait .






THats all i have 
hope we togather can fix this

Comment 1 Vladimir 2021-06-19 08:53:54 UTC

I have the same problem. Shutdown gets stuck on "stopping disk". Kernel version 4.19.80

Comment 2 Statstical anomaly 2021-06-19 10:10:57 UTC

#I currently may have a solution for this problem.
  It works for me just fine.
##The solution
As i explained above this problem exist in my hp laptop.
Which happened to have an insyde H2O bios.  In the bios settings there is a setting called **USB3.0 Configuration in Pre-OS** which is by default set to **Auto**.
The key is to turn this to either **On** or **Off**. 
###Steps (works for Insyde H20 bios)
 - Enter BIOS 
 - Go to **System configuration**
 - change the setting **USB3.0 Configuration in Pre-OS** to either **On** or **Off**
 - Save the settings and reboot.
I only have a sample size of one so i don't know if this will work for all systems or all scenarios. I saw the same problem on reddit and suggested the same fix. but the person who was facing the issue had no luck with this .So your milage may vary.

Apparently the kernel doesn't like it to be set to **Auto**.
AFAICT this comes down more towards the vendor's implementation rather than a linux bug. So I conclude there is insufficient data to call it a linux bug.