Created attachment 121235 [details] Complete dmesg Running Arch Linux (4.3.3-3-ARCH) on a GA-X79S-UP5-WIFI with a GTX Titan and a 8600 GTS, nouveau seems to oops on load: BUG: unable to handle kernel paging request at ffff88110fa7cffc IP: [<ffffffffa0c868aa>] evo_wait+0x5a/0x130 [nouveau] PGD 2b3f067 PUD 0 Oops: 0002 [#1] PREEMPT SMP CPU: 7 PID: 340 Comm: systemd-udevd Not tainted 4.3.3-3-ARCH #1 Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./X79S-UP5, BIOS F5f 03/19/2014 task: ffff881013c40000 ti: ffff881013c4c000 task.ti: ffff881013c4c000 RIP: 0010:[<ffffffffa0c868aa>] [<ffffffffa0c868aa>] evo_wait+0x5a/0x130 [nouveau] RSP: 0018:ffff881013c4f878 EFLAGS: 00010202 RAX: ffff88100fa7d000 RBX: 000000003fffffff RCX: 0000000000000000 RDX: ffffc90006b24000 RSI: 0000000000000008 RDI: ffff88101569a498 RBP: ffff881013c4f8a0 R08: ffffffffa0c36ad0 R09: ffff88101388a9c0 R10: 0000000000019ca4 R11: 00000000000004d6 R12: ffff88101569a408 R13: ffff88100d00a0d8 R14: 0000000040000007 R15: ffff88101569a498 FS: 00007f6d7c64e7c0(0000) GS:ffff88105fce0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff88110fa7cffc CR3: 000000101671f000 CR4: 00000000001406e0 Stack: ffff88100d00c000 ffff88101569a400 ffff88100d00a0d8 ffff88101569a408 ffff88100d00a878 ffff881013c4f8d0 ffffffffa0c871a7 ffff88100d00c000 ffff881016b6fb80 ffffffffa0cec660 ffff88100d00a000 ffff881013c4f8f8 Call Trace: [<ffffffffa0c871a7>] evo_sync+0x37/0xf0 [nouveau] [<ffffffffa0c874a8>] nv50_crtc_disable+0x28/0x90 [nouveau] [<ffffffffa04ec466>] __drm_helper_disable_unused_functions+0xa6/0xe0 [drm_kms_helper] [<ffffffffa04ec4ba>] drm_helper_disable_unused_functions+0x1a/0x30 [drm_kms_helper] [<ffffffffa0c8c114>] nouveau_fbcon_init+0xd4/0x110 [nouveau] [<ffffffffa0c792a3>] nouveau_drm_load+0x2f3/0x940 [nouveau] [<ffffffffa04724d7>] drm_dev_register+0xa7/0xb0 [drm] [<ffffffffa0474d63>] drm_get_pci_dev+0xd3/0x1e0 [drm] [<ffffffffa0c78ab0>] nouveau_drm_probe+0x220/0x240 [nouveau] [<ffffffff813063d5>] local_pci_probe+0x45/0xa0 [<ffffffff81306320>] ? pci_match_device+0xe0/0x110 [<ffffffff81307563>] pci_device_probe+0x103/0x150 [<ffffffff813e01f2>] driver_probe_device+0x222/0x490 [<ffffffff813e04e4>] __driver_attach+0x84/0x90 [<ffffffff813e0460>] ? driver_probe_device+0x490/0x490 [<ffffffff813dde2c>] bus_for_each_dev+0x6c/0xc0 [<ffffffff813df9ae>] driver_attach+0x1e/0x20 [<ffffffff813df4fb>] bus_add_driver+0x1eb/0x280 [<ffffffff813e0df0>] driver_register+0x60/0xe0 [<ffffffff81305c4c>] __pci_register_driver+0x4c/0x50 [<ffffffffa0474f50>] drm_pci_init+0xe0/0x110 [drm] [<ffffffffa09c6000>] ? 0xffffffffa09c6000 [<ffffffffa09c6216>] nouveau_drm_init+0x216/0x1000 [nouveau] [<ffffffff81002123>] do_one_initcall+0xb3/0x200 [<ffffffff8119e491>] ? __vunmap+0x91/0xe0 [<ffffffff8115d510>] do_init_module+0x5f/0x1ef [<ffffffff810f9897>] load_module+0x2197/0x27e0 [<ffffffff810f66e0>] ? symbol_put_addr+0x50/0x50 [<ffffffff810fa02e>] SyS_init_module+0x14e/0x190 [<ffffffff81583d2e>] entry_SYSCALL_64_fastpath+0x12/0x71 Code: 8d bc 24 90 00 00 00 c1 e8 02 89 c3 4c 89 ff 41 01 de e8 9a b2 8f e0 89 d8 48 c1 e0 02 41 81 fe f7 03 00 00 76 7e 49 8b 44 24 38 <c7> 04 98 00 00 00 20 49 8b 74 24 18 48 85 f6 0f 84 95 00 00 00 RIP [<ffffffffa0c868aa>] evo_wait+0x5a/0x130 [nouveau] RSP <ffff881013c4f878> CR2: ffff88110fa7cffc ---[ end trace cf00f17e0e1d2606 ]--- % lspci -nn -d 10de: 04:00.0 VGA compatible controller [0300]: NVIDIA Corporation G84 [GeForce 8600 GTS] [10de:0400] (rev a1) 05:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK110 [GeForce GTX TITAN] [10de:1005] (rev a1) 05:00.1 Audio device [0403]: NVIDIA Corporation GK110 HDMI Audio [10de:0e1a] (rev a1)
The problem seemingly disappeared after a power cycle. Worth noting that I had loaded the nvidia binary blob before uninstalling, rebooting, and encountering the nouveau oops. Repeated reboots persisted the fault; the power cycle seemed to have cleared it.
Sorry, please ignore my last comment. After getting nouveau to load once, I was unable to do it again, even after power cycle. My best guess currently is that it's random.
Which could occur in other spot, that why flaw is in the lock code, lock is potentially undermined, at that point netflow_scan_and_export crashes when endeavor to utilize debased lock. Not really netflow_scan_and_export is connected at all with the reason for defilement. https://www.assignmentland.co.uk
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/252.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.