[Bug 201953] System freeze/hang during shutdown/restart (at " sd 0:0:0:0: [sda] Stopping disk")

[Bug 201953] System freeze/hang during shutdown/restart (at " sd 0:0:0:0: [sda] Stopping disk")

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=201953

Vladimir (svv75@mail.ru) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |svv75@mail.ru

--- Comment #1 from Vladimir (svv75@mail.ru) ---
I have the same problem. Shutdown gets stuck on "stopping disk". Kernel version
4.19.80

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 201953] System freeze/hang during shutdown/restart (at " sd 0:0:0:0: [sda] Stopping disk")

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=201953

das (sivadasrajan007@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INSUFFICIENT_DATA

--- Comment #2 from das (sivadasrajan007@gmail.com) ---
#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.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.