[Nouveau] INFO: task echo:622 blocked for more than 120 seconds. - 3.18.0-0.rc0.git
02:00.0 VGA compatible controller:
NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1)
Chipset: G98 (NV98)
Family : NV50
The same for all four kernel:
- 3.18.0-0.rc0.git8.1.fc22.x86_64
- 3.18.0-0.rc0.git9.1.fc22.x86_64
- 3.18.0-0.rc0.git9.3.fc22.x86_64
- 3.18.0-0.rc0.git9.4.fc22.x86_64
after
fb: switching to nouveaufb from VESA VGA
display is powered off.
The magic SysRq key sequence is necessary to reboot.
Yet reached this this one recital:
...
[5.860996] [drm] Initialized nouveau 1.2.1 20120801 for :02:00.0 on
minor 0
...
[ 240.229058] INFO: task echo:622 blocked for more than 120 seconds.
[ 240.229594] Not tainted 3.18.0-0.rc0.git9.3.fc22.x86_64 #1
[ 240.230149] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this
message.
[ 240.230661] echoD 8800c82a3480 12472 622 1 0x0004
[ 240.231230] 8800ca2e3ac8 0096 8800c82a3480
001d5f00
[ 240.231784] 8800ca2e3fd8 001d5f00 880128bf
8800c82a3480
[ 240.232344] 82c30990 7fff 81ee2698
81ee2690
[ 240.232931] Call Trace:
[ 240.233467] [8185baf9] schedule+0x29/0x70
[ 240.234025] [81860d1c] schedule_timeout+0x26c/0x410
[ 240.234562] [81028c4a] ? native_sched_clock+0x2a/0xa0
[ 240.235118] [811078bc] ? mark_held_locks+0x7c/0xb0
[ 240.235645] [81861da0] ? _raw_spin_unlock_irq+0x30/0x50
[ 240.236198] [81107a4d] ? trace_hardirqs_on_caller+0x15d/0x200
[ 240.236729] [8185d52c] wait_for_completion+0x10c/0x150
[ 240.237290] [810e51f0] ? wake_up_state+0x20/0x20
[ 240.237842] [8112a559] _rcu_barrier+0x159/0x200
[ 240.238375] [8112a655] rcu_barrier+0x15/0x20
[ 240.238913] [8171813f] netdev_run_todo+0x6f/0x310
[ 240.239449] [817251ae] rtnl_unlock+0xe/0x10
[ 240.23] [8170ea35] unregister_netdev+0x25/0x30
[ 240.240546] [a00222d2] rtl_remove_one+0x62/0x230 [r8169]
[ 240.241104] [814682cf] pci_device_remove+0x3f/0xc0
[ 240.241642] [8155b34f] __device_release_driver+0x7f/0xf0
[ 240.242180] [8155b3e5] device_release_driver+0x25/0x40
[ 240.242712] [8146234c] pci_stop_bus_device+0x9c/0xb0
[ 240.243259] [8146248e]
pci_stop_and_remove_bus_device_locked+0x1e/0x40
[ 240.243785] [8146b44c] remove_store+0x7c/0x90
[ 240.244321] [81555f98] dev_attr_store+0x18/0x30
[ 240.244858] [81302789] sysfs_kf_write+0x49/0x60
[ 240.245375] [81301ac9] kernfs_fop_write+0xf9/0x180
[ 240.245921] [8127305a] vfs_write+0xba/0x200
[ 240.246439] [8186379c] ? retint_swapgs+0x13/0x1b
[ 240.246978] [81273bac] SyS_write+0x5c/0xd0
[ 240.247491] [81862b69] system_call_fastpath+0x12/0x17
[ 240.248025] 6 locks held by echo/622:
[ 240.248532] #0: (sb_writers#3){.+.+.+}, at: [81273143]
vfs_write+0x1a3/0x200
[ 240.249104] #1: (of-mutex){+.+.+.}, at: [81301a97]
kernfs_fop_write+0xc7/0x180
[ 240.249651] #2: (s_active#131){++}, at: [81300ce4]
kernfs_remove_self+0xf4/0x170
[ 240.250229] #3: (pci_rescan_remove_lock){+.+.+.}, at: [8145f167]
pci_lock_rescan_remove+0x17/0x20
[ 240.250779] #4: (dev-mutex){..}, at: [8155b3dd]
device_release_driver+0x1d/0x40
[ 240.251358] #5: (rcu_sched_state.barrier_mutex){+.+...}, at:
[8112a435] _rcu_barrier+0x35/0x200
[ 241.303095] systemd[1]: start request repeated too quickly for
lightdm.service
[ 241.323052] systemd[1]: Unit lightdm.service entered failed state.
[ 241.333101] systemd[1]: lightdm.service failed.
[ 359.038325] INFO: task kworker/u16:2:81 blocked for more than 120 seconds.
[ 359.039475] Not tainted 3.18.0-0.rc0.git9.3.fc22.x86_64 #1
[ 359.040004] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this
message.
[ 359.040571] kworker/u16:2 D 880128131a40 1089681 2 0x
[ 359.041162] Workqueue: netns cleanup_net
[ 359.041701] 8801275bba88 0096 880128131a40
001d5f00
[ 359.042280] 8801275bbfd8 001d5f00 880128bf3480
880128131a40
[ 359.042856] 880128131a40 81ee25e8 0246
880128131a40
[ 359.043436] Call Trace:
[ 359.043975] [8185c0a1] schedule_preempt_disabled+0x31/0x80
[ 359.044542] [8185d8f3] mutex_lock_nested+0x183/0x440
[ 359.045108] [8112a435] ? _rcu_barrier+0x35/0x200
[ 359.045647] [81028c4a] ? native_sched_clock+0x2a/0xa0
[ 359.046218] [8112a435] ? _rcu_barrier+0x35/0x200
[ 359.046767] [8185f914] ? __mutex_unlock_slowpath+0xc4/0x1c0
[ 359.047333] [8112a435] _rcu_barrier+0x35/0x200
[ 359.047875] [8112a655] rcu_barrier+0x15/0x20
[ 359.048433] [8171813f] netdev_run_todo+0x6f/0x310
[ 359.048969] [8170cd35] ? rollback_registered_many+0x265/0x2e0
[ 359.049528]
[Nouveau] VGA resume thaw (wake up from S3 S4) broken - reloaded
On 20.10.2014 08:13, poma wrote: 02:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) Chipset: G98 (NV98) Family : NV50 The same for all four kernel: - 3.18.0-0.rc0.git8.1.fc22.x86_64 - 3.18.0-0.rc0.git9.1.fc22.x86_64 - 3.18.0-0.rc0.git9.3.fc22.x86_64 - 3.18.0-0.rc0.git9.4.fc22.x86_64 after fb: switching to nouveaufb from VESA VGA display is powered off. The magic SysRq key sequence is necessary to reboot. ... This is what I've tested so far: http://cgit.freedesktop.org/~airlied/linux/log/?h=drm-next git clone -b drm-next git://people.freedesktop.org/~airlied/linux 1. git-e94654e-1st-test-nouveau 2. git-996f5a0-2nd-test-nouveau drm/nouveau/core: pass related object into notify constructor http://cgit.freedesktop.org/~airlied/linux/commit/?h=drm-nextid=996f5a0 3. git-b38a232-3rd-test-nouveau drm/nv50-/disp: add support for completion events http://cgit.freedesktop.org/~airlied/linux/commit/?h=drm-nextid=b38a232 4. git-dfda0df-4th-test-nouveau The Last of the Mohicans Unlike the above mentioned Fedora kernels, all four drm-next kernels have no problemos with booting from soft-off(S5). However The Last of the Mohicans has broken resume from suspend(S3)/hibernate(S4). This has been seen recently. poma ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - reloaded Fedora kernels 3.18 boot from soft-off(S5) broken
On 20.10.2014 21:30, poma wrote: On 20.10.2014 08:13, poma wrote: 02:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) Chipset: G98 (NV98) Family : NV50 The same for all four kernel: - 3.18.0-0.rc0.git8.1.fc22.x86_64 - 3.18.0-0.rc0.git9.1.fc22.x86_64 - 3.18.0-0.rc0.git9.3.fc22.x86_64 - 3.18.0-0.rc0.git9.4.fc22.x86_64 after fb: switching to nouveaufb from VESA VGA display is powered off. The magic SysRq key sequence is necessary to reboot. ... This is what I've tested so far: http://cgit.freedesktop.org/~airlied/linux/log/?h=drm-next git clone -b drm-next git://people.freedesktop.org/~airlied/linux 1. git-e94654e-1st-test-nouveau 2. git-996f5a0-2nd-test-nouveau drm/nouveau/core: pass related object into notify constructor http://cgit.freedesktop.org/~airlied/linux/commit/?h=drm-nextid=996f5a0 3. git-b38a232-3rd-test-nouveau drm/nv50-/disp: add support for completion events http://cgit.freedesktop.org/~airlied/linux/commit/?h=drm-nextid=b38a232 4. git-dfda0df-4th-test-nouveau The Last of the Mohicans Unlike the above mentioned Fedora kernels, all four drm-next kernels have no problemos with booting from soft-off(S5). However The Last of the Mohicans has broken resume from suspend(S3)/hibernate(S4). This has been seen recently. Summa summarum With the above mentioned drm-next kernels at least works boot from soft-off(S5). However broken are resume from suspend(S3) hibernate(S4). The above mentioned Fedora kernels including 3.18.0-0.rc1.git0.1.fc22.x86_64, based on linux-next derivatives, all broke boot from soft-off(S5) - after fb: switching to nouveaufb from VESA VGA you can only get WhoTF turned out the lights! What the circus. What is the best, I've compared the last working kernel and first broken, guess what, no diff within gpu/drm/nouveau/ branch. BTW (kernel_hibernate) Hibernation issue tracker bug https://bugzilla.redhat.com/show_bug.cgi?id=781749 Are you really such opportunists? poma ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - reloaded Fedora kernels 3.18 boot from soft-off(S5) broken
On 21.10.2014 02:23, poma wrote: On 20.10.2014 21:30, poma wrote: On 20.10.2014 08:13, poma wrote: 02:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) Chipset: G98 (NV98) Family : NV50 The same for all four kernel: - 3.18.0-0.rc0.git8.1.fc22.x86_64 - 3.18.0-0.rc0.git9.1.fc22.x86_64 - 3.18.0-0.rc0.git9.3.fc22.x86_64 - 3.18.0-0.rc0.git9.4.fc22.x86_64 after fb: switching to nouveaufb from VESA VGA display is powered off. The magic SysRq key sequence is necessary to reboot. ... This is what I've tested so far: http://cgit.freedesktop.org/~airlied/linux/log/?h=drm-next git clone -b drm-next git://people.freedesktop.org/~airlied/linux 1. git-e94654e-1st-test-nouveau 2. git-996f5a0-2nd-test-nouveau drm/nouveau/core: pass related object into notify constructor http://cgit.freedesktop.org/~airlied/linux/commit/?h=drm-nextid=996f5a0 3. git-b38a232-3rd-test-nouveau drm/nv50-/disp: add support for completion events http://cgit.freedesktop.org/~airlied/linux/commit/?h=drm-nextid=b38a232 4. git-dfda0df-4th-test-nouveau The Last of the Mohicans Unlike the above mentioned Fedora kernels, all four drm-next kernels have no problemos with booting from soft-off(S5). However The Last of the Mohicans has broken resume from suspend(S3)/hibernate(S4). This has been seen recently. Summa summarum With the above mentioned drm-next kernels at least works boot from soft-off(S5). However broken are resume from suspend(S3) hibernate(S4). The above mentioned Fedora kernels including 3.18.0-0.rc1.git0.1.fc22.x86_64, based on linux-next derivatives, all broke boot from soft-off(S5) - after fb: switching to nouveaufb from VESA VGA you can only get WhoTF turned out the lights! What the circus. What is the best, I've compared the last working kernel and first broken, guess what, no diff within gpu/drm/nouveau/ branch. Oh yeah! With 3.18.0-0.rc1.git0.1.fc22.x86_64 even the magic SysRq key sequence is broken. :) Vorsprung durch technik ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
