All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 94725] Nouveau driver fails to poweron GPU on GM204 after dynamic poweroff
Date: Tue, 20 Sep 2016 08:48:11 +0000	[thread overview]
Message-ID: <bug-94725-8800-nRDtSyGr7f@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94725-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #25 from Perry Yuan <perry_yuan-8PEkshWhKlo@public.gmane.org> ---
HI guys .
The Bug  is similar with my graphics panic , so I add related logs here .
When I boot up system ,system will hang at nouveau driver panic , repeat print
nouveau driver  panic info , I must force down the system . 
If i add nouveau.runpm=0  ,system  can boot up normally  without panic .


My graphics : NVIDIA  GM107 


And the panic info is related to pci op.
---------------------------------------------------
[   21.303467] Bluetooth: RFCOMM socket layer initialized
[   21.303471] Bluetooth: RFCOMM ver 1.11
[   22.095603] nouveau 0000:01:00.0: DRM: evicting buffers...
[   22.095605] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go
idle...
[   22.095622] nouveau 0000:01:00.0: DRM: suspending client object trees...
[   22.098407] nouveau 0000:01:00.0: DRM: suspending kernel object tree...
[   22.220120] FAT-fs (sdb1): Volume was not properly unmounted. Some data may
be corrupt. Please run fsck.
[   23.669052] Non-volatile memory driver v1.3
[   24.083662] pci_raw_set_power_state: 48 callbacks suppressed
[   24.083665] nouveau 0000:01:00.0: Refused to change power state, currently
in D3
[   24.159560] nouveau 0000:01:00.0: Refused to change power state, currently
in D3
[   24.179571] nouveau 0000:01:00.0: Refused to change power state, currently
in D3
[   24.179575] nouveau 0000:01:00.0: DRM: resuming kernel object tree...
[   24.179617] nouveau 0000:01:00.0: pci: failed to adjust cap speed
[   24.179618] nouveau 0000:01:00.0: pci: failed to adjust lnkctl speed
[   24.317867] wlp2s0: authenticate with f0:b4:29:87:9e:e4
---------------------------------------------------
and the frequently panic is :


ul 21 18:38:50 localhost kernel: [<ffffffffa03c463b>] ?
nv04_timer_read+0x2b/0x70 [nouveau]
Jul 21 18:38:50 localhost kernel: [<ffffffffa03c41af>] nvkm_timer_read+0xf/0x20
[nouveau]
Jul 21 18:38:50 localhost kernel: [<ffffffffa03bc598>] nvkm_pmu_init+0x58/0x480
[nouveau]
Jul 21 18:38:50 localhost kernel: [<ffffffffa0374e8e>]
nvkm_subdev_init+0xee/0x230 [nouveau]
Jul 21 18:38:50 localhost kernel: [<ffffffffa03c84df>]
nvkm_device_init+0x18f/0x280 [nouveau]
Jul 21 18:38:50 localhost kernel: [<ffffffffa03cc138>]
nvkm_udevice_init+0x48/0x60 [nouveau]
Jul 21 18:38:50 localhost kernel: [<ffffffffa03736c0>]
nvkm_object_init+0x50/0x1c0 [nouveau]
Jul 21 18:38:50 localhost kernel: [<ffffffffa0373705>]
nvkm_object_init+0x95/0x1c0 [nouveau]
Jul 21 18:38:50 localhost kernel: [<ffffffffa037062e>]
nvkm_client_init+0xe/0x10 [nouveau]
Jul 21 18:38:50 localhost kernel: [<ffffffffa04125fe>]
nvkm_client_resume+0xe/0x10 [nouveau]
Jul 21 18:38:50 localhost kernel: [<ffffffffa036f7b4>]
nvif_client_resume+0x14/0x20 [nouveau]
Jul 21 18:38:50 localhost kernel: [<ffffffffa040fbed>]
nouveau_do_resume+0x4d/0x130 [nouveau]
Jul 21 18:38:50 localhost kernel: [<ffffffffa041000c>]
nouveau_pmops_runtime_resume+0x7c/0x120 [nouveau]
Jul 21 18:38:50 localhost kernel: [<ffffffff81350c8b>]
pci_pm_runtime_resume+0x7b/0xc0
Jul 21 18:38:50 localhost kernel: [<ffffffff81350c10>] ?
pci_restore_standard_config+0x40/0x40
Jul 21 18:38:50 localhost kernel: [<ffffffff8142ddb6>] __rpm_callback+0x36/0xc0
Jul 21 18:38:50 localhost kernel: [<ffffffff8142de64>] rpm_callback+0x24/0x80
Jul 21 18:38:50 localhost kernel: [<ffffffff8142ee39>] rpm_resume+0x4e9/0x670
Jul 21 18:38:50 localhost kernel: [<ffffffff812a7ffb>] ?
cred_has_capability+0x6b/0x120
Jul 21 18:38:50 localhost kernel: [<ffffffff8142f00f>]
__pm_runtime_resume+0x4f/0x80
Jul 21 18:38:50 localhost kernel: [<ffffffffa04107bb>]
nouveau_drm_open+0x3b/0x1b0 [nouveau]
Jul 21 18:38:50 localhost kernel: [<ffffffff812a80de>] ?
selinux_capable+0x2e/0x40
Jul 21 18:38:50 localhost kernel: [<ffffffff812a1cc8>] ?
security_capable+0x18/0x20
Jul 21 18:38:50 localhost kernel: [<ffffffffa008add6>] drm_open+0x1f6/0x470
[drm]
Jul 21 18:38:50 localhost kernel: [<ffffffffa0091759>] drm_stub_open+0xa9/0x120
[drm]
Jul 21 18:38:50 localhost kernel: [<ffffffff811fc4b1>] chrdev_open+0xa1/0x1e0
Jul 21 18:38:50 localhost kernel: [<ffffffff811f5567>]
do_dentry_open+0x1a7/0x2e0
Jul 21 18:38:50 localhost kernel: [<ffffffff812a21ac>] ?
security_inode_permission+0x1c/0x30
Jul 21 18:38:50 localhost kernel: [<ffffffff811fc410>] ? cdev_put+0x30/0x30
Jul 21 18:38:50 localhost kernel: [<ffffffff811f573d>] vfs_open+0x5d/0xd0
Jul 21 18:38:50 localhost kernel: [<ffffffff81203058>] ? may_open+0x68/0x110
Jul 21 18:38:50 localhost kernel: [<ffffffff81206b3d>] do_last+0x1ed/0x12a0
Jul 21 18:38:50 localhost kernel: [<ffffffff811d9c96>] ?
kmem_cache_alloc_trace+0x1d6/0x200
Jul 21 18:38:50 localhost kernel: [<ffffffff81207cb2>] path_openat+0xc2/0x490
Jul 21 18:38:50 localhost kernel: [<ffffffff8120947b>] do_filp_open+0x4b/0xb0
Jul 21 18:38:50 localhost kernel: [<ffffffff812160a7>] ? __alloc_fd+0xa7/0x130
Jul 21 18:38:50 localhost kernel: [<ffffffff811f6a93>] do_sys_open+0xf3/0x1f0
Jul 21 18:38:50 localhost kernel: [<ffffffff811f6bae>] SyS_open+0x1e/0x20
Jul 21 18:38:50 localhost kernel: [<ffffffff816956c9>]
system_call_fastpath+0x16/0x1b

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

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

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

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

  parent reply	other threads:[~2016-09-20  8:48 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-27 16:28 [Bug 94725] New: Nouveau driver fails to load on GM204 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-94725-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-03-27 17:23   ` [Bug 94725] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-27 17:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-27 17:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-28  2:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-30 19:11   ` [Bug 94725] Nouveau driver fails to poweron GPU on GM204 after dynamic poweroff bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-30 22:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-01  3:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-01  3:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-01  6:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-01  6:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-01  7:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-01  8:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-01 13:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-01 15:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found]     ` <bug-94725-8800-0111GoOQVN-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-04-05  1:25       ` Efrem Mc
2016-04-05  1:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06  1:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06  4:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06  4:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06 12:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-05 12:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-05 12:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-05 15:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-05 15:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-01 12:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-16 17:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-20  8:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2016-11-10 14:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-02  9:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-02 10:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-02 15:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-04  9:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-02 10:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-94725-8800-nRDtSyGr7f@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.