[Bug 90423] New: [NVAA]: Shutdown (poweroff) get stuck when runtime PM is enabled - bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 90423] New: [NVAA]: Shutdown (poweroff) get stuck when runtime PM is enabled
Date: Tue, 12 May 2015 16:04:45 +0000	[thread overview]
Message-ID: <bug-90423-8800@http.bugs.freedesktop.org/> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 1896 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=90423

            Bug ID: 90423
           Summary: [NVAA]: Shutdown (poweroff) get stuck when runtime PM
                    is enabled
           Product: xorg
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: alexanders83-S0/GAf8tV78@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

I'm currently running a 3.19 kernel where I looked into the problem that one of
my systems doesn't shutdown cleanly most of the time. THis behavior started
from some older kernels, I _guess_ it's 5addcf0a5f0fadc ("nouveau: add runtime
PM support (v0.9").
My board is a Asus M3N78-EM with a
> 02:00.0 VGA compatible controller: NVIDIA Corporation C77 [GeForce 8300] (rev a2)

During shutdown dmesg shows the following:
[   38.476675] systemd-shutdown[1]: Powering off.
[   38.536997] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[   38.542522] sd 1:0:0:0: [sdb] Stopping disk
[   41.069224] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[   41.074745] sd 0:0:0:0: [sda] Stopping disk

That's all.

I added some printk to my source tree and could trace the shutdown execution
path down to __pm_runtime_barrier where dev->power.runtime_status == 3. The
call to schedule() finally seems to be the deadlock.
Of course, if I compile my kernel with CONFIG_PM=n everything is fine.
Reenabling it again the problem occurs again.
A workaround suggested on IRC is to set runpm=0. This seems to work as the
system did clean shutdowns from this change on.
As I consider this really as a workaround I would like to fix this.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3158 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau